
From yaacov.weingarten@nsn.com  Mon Jan  3 23:49:06 2011
Return-Path: <yaacov.weingarten@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 275113A6B51; Mon,  3 Jan 2011 23:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[AWL=2.510,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtR0GYlwPvSt; Mon,  3 Jan 2011 23:49:05 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 02DD73A6B4E; Mon,  3 Jan 2011 23:49:04 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p047p8Nj005842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Jan 2011 08:51:08 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p047p4Rf024217; Tue, 4 Jan 2011 08:51:07 +0100
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 4 Jan 2011 08:51:06 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 4 Jan 2011 08:51:04 +0100
Message-ID: <62D9AC1F11702146A0387CBFF3A8CD3D03215CDE@DEMUEXC030.nsn-intra.net>
In-Reply-To: <20110102083001.32530.72516.idtracker@localhost>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] I-D Action:draft-ietf-mpls-tp-oam-analysis-03.txt
Thread-Index: AcuqV7X8bfpWd1xBTum8n6lnnJcXDgBjCMCA
References: <20110102083001.32530.72516.idtracker@localhost>
From: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>
To: <mpls@ietf.org>, <mpls-tp@ietf.org>
X-OriginalArrivalTime: 04 Jan 2011 07:51:06.0086 (UTC) FILETIME=[24587060:01CBABE4]
Subject: Re: [mpls-tp] [mpls] I-D Action:draft-ietf-mpls-tp-oam-analysis-03.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 07:49:06 -0000

Hi all,

We have updated this draft to prevent it from expiring.  This version
addresses some of the comments received during the WG LC.  We will
republish when we have completed addressing all of the comments.

Best Regards,
The Editors

>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>> Of ext Internet-Drafts@ietf.org
>> Sent: Sunday, January 02, 2011 10:30 AM
>> To: i-d-announce@ietf.org
>> Cc: mpls@ietf.org
>> Subject: [mpls] I-D Action:draft-ietf-mpls-tp-oam-analysis-03.txt
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Multiprotocol Label Switching
Working
>> Group of the IETF.
>>=20
>>=20
>> 	Title           : OAM functions in MPLS based transport network
>> 	Author(s)       : N. Sprecher, et al.
>> 	Filename        : draft-ietf-mpls-tp-oam-analysis-03.txt
>> 	Pages           : 14
>> 	Date            : 2011-01-02
>>=20
>> This document describes the outcome of the discussions on the
>> necessary OAM functionality for the first release of MPLS based
>> transport networks.  The discussion is based on the set of
>> requirements for Operations, Administration, and Maintenance (OAM)
>> for MPLS based transport networks as defined in [MPLS-TP OAM Reqs].
>> An important aspect was to evaluate whether existing OAM tools from
>> the current MPLS protocol suite can be used to fulfill these
>> requirements.  Eventually, the purpose of the document is to map the
>> set of functions to a set of tools based on the existing OAM tool-
>> set.
>>=20
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-oam-analysis-
>> 03.txt
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.

From yaacov.weingarten@nsn.com  Mon Jan  3 23:58:20 2011
Return-Path: <yaacov.weingarten@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39E5F3A6B5D; Mon,  3 Jan 2011 23:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.246
X-Spam-Level: 
X-Spam-Status: No, score=-4.246 tagged_above=-999 required=5 tests=[AWL=2.352,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZ9eI1t9B98M; Mon,  3 Jan 2011 23:58:16 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 927E33A6B4E; Mon,  3 Jan 2011 23:58:15 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0480LfL026199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Jan 2011 09:00:21 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0480LJZ025408; Tue, 4 Jan 2011 09:00:21 +0100
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 4 Jan 2011 09:00:21 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBABE5.6EEBD34C"
Date: Tue, 4 Jan 2011 09:00:19 +0100
Message-ID: <62D9AC1F11702146A0387CBFF3A8CD3D03215CF1@DEMUEXC030.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New version of draft-weingarten-mpls-tp-ring-protection-04
Thread-Index: Acur5W5MixiV9EijSkqw7jb+0SO5/g==
From: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>
To: <mpls-tp@ietf.org>, <mpls@ietf.org>
X-OriginalArrivalTime: 04 Jan 2011 08:00:21.0131 (UTC) FILETIME=[6F2D95B0:01CBABE5]
Subject: [mpls-tp] New version of draft-weingarten-mpls-tp-ring-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 07:58:20 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBABE5.6EEBD34C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello all,

We have submitted a new version of the ring protection draft, mainly to
prevent the draft from expiring.  However, there is one significant
change from the previous version in the section on p2mp steering
protection - where the description now references the concept of
context-labels in order to explain the working of the working and
protection SPME.  Any comments regarding this section especially would
be appreciated, as the editors are still discussing how to improve the
description.

Best regards,
Yaacov Weingarten
Nokia Siemens Networks
Industry Environment, PTE
ph#:  +972-9-775 1827
mob#: +972-54-220 0977



------_=_NextPart_001_01CBABE5.6EEBD34C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>New version of =
draft-weingarten-mpls-tp-ring-protection-04</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">H</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">ello all,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">We have =
submitted a new version of the ring protection draft, mainly to prevent =
the draft from expiring.&nbsp; However</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">, there is one significant =
change from the previous version in the section on p2mp steering =
protection</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">&#8211;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> where the description now references the concept of =
context-labels in order to explain the working of the working and =
protection SPME.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 =
FACE=3D"Arial"> Any comments regarding this section especially would be =
appreciated, as the editors are still discussing how to improve the =
description</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Best =
regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B><I></I></B></SPAN><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><B><I><SPAN =
LANG=3D"de-de"></SPAN></I></B><B><I><SPAN LANG=3D"de-de"><FONT =
COLOR=3D"#800080" FACE=3D"Lucida Calligraphy">Yaacov =
Weingarten</FONT></SPAN></I></B><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"de-de"></SPAN></B></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">Nokia Siemens Networks</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">Industry Environment, PTE</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">ph#:&nbsp; +972-9-775 1827</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">mob#: +972-54-220 0977</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01CBABE5.6EEBD34C--

From yaakov_s@rad.com  Tue Jan  4 08:25:03 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D8C53A6CE3; Tue,  4 Jan 2011 08:25:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level: 
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3youokUSrZ4n; Tue,  4 Jan 2011 08:25:01 -0800 (PST)
Received: from antivir2.rad.co.il (mx2-q.rad.co.il [80.74.100.144]) by core3.amsl.com (Postfix) with ESMTP id 5EEAD3A6CC0; Tue,  4 Jan 2011 08:24:58 -0800 (PST)
Received: from unknown (HELO EXRAD5.ad.rad.co.il) ([192.114.24.28]) by antivir2.rad.co.il with ESMTP; 04 Jan 2011 18:26:50 +0200
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 4 Jan 2011 18:26:28 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Tue, 4 Jan 2011 18:26:28 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "neil.2.harrison@bt.com" <neil.2.harrison@bt.com>
Thread-Topic: [PWE3] VCCV usage
Thread-Index: AQHLhgiDxE/GLhOI3kefbzvPaVR2G5N1DKwAgAARnICAAAFMAIAAaBKggBL67gCAArdUEIAACG0ggDYHgUA=
Date: Tue, 4 Jan 2011 16:26:26 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC919188C@EXRAD5.ad.rad.co.il>
References: <A3C5DF08D38B6049839A6F553B331C76D5CE389931@ILPTMAIL02.ecitele.com>, <OFBC9BCFE0.4D1C5353-ON482577DE.0025FF7B-482577DE.00270EC4@zte.com.cn> <A3C5DF08D38B6049839A6F553B331C76D5CE389932@ILPTMAIL02.ecitele.com> <07F7D7DED63154409F13298786A2ADC9179B9C@EXRAD5.ad.rad.co.il> <4CF3C348.4000602@cisco.com> <07F7D7DED63154409F13298786A2ADC9186466@EXRAD5.ad.rad.co.il> <6D3D47CB84BDE349BC23BF1C94E316E440039D57EF@EMV62-UKRD.domain1.systemhost.net>
In-Reply-To: <6D3D47CB84BDE349BC23BF1C94E316E440039D57EF@EMV62-UKRD.domain1.systemhost.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [PWE3] VCCV usage
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 16:25:03 -0000

Neil

Sorry that it took me some time to get back to reading PWE email ...

First, what I questioned was not the CI per se,
but the processing required for it. While I wholeheartedly agree
with your remark on the value of consistent CI,
I don't agree with the requirement that in every case
the processing has to be the same.

Second, as you mention yourself, very early on in PWE we decided
to follow the MPLS tradition of not having self-describing packets.
I was very much against this decision (you may recall that my early version
of the control word had a type identifier), but once this decision was take=
n=20
it obviated any further requirement of consistency.

Third, I was not speaking specifically of MPLS-TP.
I was speaking of the deployment of PWs over IP using RFC 4023.
This has been around for years.

Y(J)S

-----Original Message-----
From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]=20
Sent: Wednesday, December 01, 2010 09:48
To: Yaakov Stein
Cc: pwe3@ietf.org; mpls-tp@ietf.org
Subject: RE: [PWE3] VCCV usage

Hi Yaakov...you may like to ponder on this point (I have raised it several =
times before, but for some reason it gets ignored...I wonder why? ;-)) ....


Any layer network SHOULD (though this really ought to be MUST) have consist=
ent CI (Characteristic Information).  There are many reasons for this rathe=
r obvious requirement statement, but a key one is that if misconnectivity o=
ccurs, then wherever the misdirected DP traffic units and OAM arrive they c=
an be correctly processed...this means that all the functional fields of DP=
 traffic units and DP OAM MUST have unambiguous functional meaning.  I thin=
k this statement is so obviously true that no sane person could disagree wi=
th it.

Aside=3D> The above requirement is true for all 3 network modes, but it is =
most important in a co-ps mode network (as this has the richest potential s=
et of misconnectivity defects) where short-cuts have been taken on child tr=
affic unit labelling (ie omit SA label, DA label reduced to link significan=
t, omit PID label) due to the a-priori-known single-source property of the =
parent connection.  However, this a-priori-known single-source property of =
a parent connection is broken under misconnectivity defects and cannot, ind=
eed MUST NOT, be assumed...ergo why child traffic units and OAM MUST have c=
onsistent CI.

You are raising one case below where there is non-consistent CI.....but the=
re are many more.  Even the 'label' (there is only one) in an MPLS traffic =
unit is not consistent of its meaning.  Then we have lots of choices for OA=
M.  Now factor-in mixed cases of LSP sublayering and LSP layering...the for=
mer LSPs reside in the *same layer network* whilst the latter LSPs reside i=
n *different layer networks* (this is a rather more serious self-inflicted =
consequential problem BTW).

Do you think it is sensible given the above is 'known' (and for some time) =
that such mistakes should be carried over into MPLS-TP?....esp given this i=
s supposed to be a transparent transport network (hint=3D> this should neve=
r have sublayering and esp not PWs as all clients MUST be treated equally..=
.else we do not have a transparent transport network).

Please excuse me copying this to the MPLS-TP list as my observation is clea=
rly germane to that WG too.

regards, Neil

=20

From daniel@olddog.co.uk  Wed Jan  5 04:17:13 2011
Return-Path: <daniel@olddog.co.uk>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49C6B3A6B81; Wed,  5 Jan 2011 04:17:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.961
X-Spam-Level: 
X-Spam-Status: No, score=-101.961 tagged_above=-999 required=5 tests=[AWL=0.638, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-BRT31rdHWD; Wed,  5 Jan 2011 04:17:12 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id E939E3A6B71; Wed,  5 Jan 2011 04:17:11 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id p05CJGdU010947;  Wed, 5 Jan 2011 12:19:16 GMT
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id p05CJEQj010927;  Wed, 5 Jan 2011 12:19:14 GMT
From: "Daniel King" <daniel@olddog.co.uk>
To: <mpls-tp@ietf.org>, <mpls@ietf.org>
Date: Wed, 5 Jan 2011 12:19:12 -0000
Message-ID: <011901cbacd2$c31fc560$495f5020$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Acus0NoSIwL/giWgSQWF+O1iF7AaCg==
Content-Language: en-gb
Subject: [mpls-tp] New version of draft-ietf-mpls-tp-mib-management-overview (01)
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 12:17:13 -0000

Hi All, 

Happy New Year!

Please note that the authors of draft-ietf-mpls-tp-mib-management-overview
have issued a new version of said document. Updates include:

- Cleaned up Abstract. 
- Included GMPLS TC references where relevant. 
- Updated Pseudowire Module section.
- Added significant text (tables) to the Fault Management and Performance
Management section.
- Updated MPLS-TP Gap Analysis section. 
- Added a new co-author. 
- Addressed various grammar and nits. 
  	
We have also identified the need for an MPLS-TP abstract model document.
This new draft will provide an abstract model and use a formal language to
define the terminology, the information that must be retrieved and stored.
It will also list the new MPLS-TP MIB modules, identified as part of the gap
analysis in  draft-ietf-mpls-tp-mib-management-overview. 

Br, Dan. 

-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: 05 January 2011 12:00
To: i-d-announce@ietf.org
Cc: mpls@ietf.org
Subject: I-D Action:draft-ietf-mpls-tp-mib-management-overview-01.txt

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


	Title           : Multiprotocol Label Switching Transport Profile
(MPLS-TP) MIB-based Management Overview
	Author(s)       : A. Farrel, et al.
	Filename        : draft-ietf-mpls-tp-mib-management-overview-01.txt
	Pages           : 22
	Date            : 2011-01-05

A range of Management Information Base (MIB) modules has been developed to
help model and manage the various aspects of Multiprotocol Label Switching
(MPLS) networks.  These MIB modules are defined in separate documents that
focus on the specific areas of responsibility of the modules that they
describe.

The MPLS Transport Profile (MPLS-TP) is a profile of MPLS functionality
specific to the construction of packet-switched transport networks.

This document describes the MIB-based management architecture for MPLS-TP,
indicates the interrelationships between different existing MIB modules that
can be leveraged for MPLS-TP network management and identifies areas where
additional MIB modules would be required.

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

This Informational Internet-Draft is aimed at achieving IETF Consensus
before publication as an RFC and will be subject to an IETF Last Call.

[RFC Editor, please remove this note before publication as an RFC and insert
the correct Streams Boilerplate to indicate that the published RFC has IETF
Consensus.]









King & Venkatesan,  et al.











 [page 1]

draft-ietf-mpls-tp-mib-management-overview-01.txt


January 2011

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-mib-management-overvi
ew-01.txt

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

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


From Alexander.Vainshtein@ecitele.com  Thu Jan  6 22:46:43 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 383503A67C1; Thu,  6 Jan 2011 22:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level: 
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NhtbkWS2p98P; Thu,  6 Jan 2011 22:46:40 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 2C2603A67B2; Thu,  6 Jan 2011 22:46:38 -0800 (PST)
X-AuditID: 93eaf2e7-b7c8fae000002726-39-4d26b74e838f
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id BD.D2.10022.E47B62D4; Fri,  7 Jan 2011 08:48:46 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Fri, 7 Jan 2011 08:50:23 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Linda Dunbar <ldunbar@huawei.com>
Date: Fri, 7 Jan 2011 08:48:42 +0200
Thread-Topic: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
Thread-Index: Acut+GY8NiB+SQfOSi+H6qHdg0HkpwAPVrOB
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6B8336307@ILPTMAIL02.ecitele.com>
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com>
In-Reply-To: <002901cbadf8$66783640$790c7c0a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A3C5DF08D38B6049839A6F553B331C76D6B8336307ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 06:46:43 -0000

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

Linda,
Please see my comment inline below.

Regards,
     Sasha

________________________________
From: mpls-bounces@ietf.org [mpls-bounces@ietf.org] On Behalf Of Linda Dunb=
ar [ldunbar@huawei.com]
Sent: Friday, January 07, 2011 1:21 AM
To: mpls-tp@ietf.org; mpls@ietf.org; 'Dan Frost'; 'Stewart Bryant'
Subject: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"


Dan and Stewart,

I have a few questions and some suggestions on your recent draft:

Section 2 (Overview),

there are several references of measuring =93packets=94 without specifying =
if the packets are LM/DM packets or actual data plane packets. Such Page 7 =
first paragraph: =93 the count of packets received prior to time T2 over th=
e channel from A (B_RxP),=94

Is this the intent? So that LM can be used to either measuring the LM losse=
s and data plane loss?

Section 2.7.1 Types of Channels:

It stated that LM and DM flow over MPLS G-Ach. Since packets over G-Ach mig=
ht encounter extra processing on intermediate nodes, the Delay measured ove=
r G-Ach channel might be slightly different from the data plane channel. Wi=
ll it be a problem?

[[Sasha]] IMHO packets running over G-ACh SHOULD NOT experience any special=
 processing in the intermediate nodes because GAL (and, by implication G-AC=
h) will not be exposed to these nodes. However, this is only true if the ov=
erall depth of the label stack (GAL included) does not exceed the limit on =
the number of labels these nodes are ready to treat normally.

What happens if this limit is exceeded is implementation-specific and may b=
e as severe as dropping offending packets unconditionally. Other known case=
s include ignoring extra labels, slowing down processing etc.

AFAIK, MPLS-TP development had, so far, ignored this problem. Maybe it is h=
igh time to recognize it?



Section 2.7.6. Loss Measurement Modes

Under the =93direct mode=94, I interpret it as measuring the data plane pac=
kets, is it correct?

Counting data plane packets can be process intensive.  Usually the each nod=
e (or line card) can only do actual packet counting for limited number of L=
SPs. Therefore, I suggest allowing B node to ignore A node=92s LM when B is=
 not ready to do the counting or send back a reply to indicate the =93not r=
eady status=94.

o       Several options are possible for the negotiation: egress simply ign=
ore the request when it is not ready, egress sends back an error, etc. Ingr=
ess node doesn=92t need to start counting traffic until it gets confirmatio=
n from the egress node.

Should allow options of either byte counter or packet counter.

Thank you very much.

Linda Dunbar

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

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta content=3D"MSHTML 6.00.6000.17063" name=3D"GENERATOR">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P =
{
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<div style=3D"FONT-SIZE: 16px; COLOR: #000000; DIRECTION: ltr; FONT-FAMILY:=
 Times New Roman">
<div>Linda,</div>
<div><font face=3D"times new roman">Please see my comment<a></a> inline bel=
ow.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">Regards,</font></div>
<div><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</font></=
div>
<div dir=3D"ltr"><font face=3D"Times New Roman" color=3D"#000000" size=3D"3=
"></font>&nbsp;</div>
<div id=3D"divRpF337040" style=3D"DIRECTION: ltr">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" color=3D"#000000" size=3D"2"><b>From:</b> mpls-bounce=
s@ietf.org [mpls-bounces@ietf.org] On Behalf Of Linda Dunbar [ldunbar@huawe=
i.com]<br>
<b>Sent:</b> Friday, January 07, 2011 1:21 AM<br>
<b>To:</b> mpls-tp@ietf.org; mpls@ietf.org; 'Dan Frost'; 'Stewart Bryant'<b=
r>
<b>Subject:</b> [mpls] Questions on &quot;draft-ietf-mpls-loss-delay-00&quo=
t;<br>
</font><br>
</div>
<div></div>
<div>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">Dan and Stewart, <=
/font></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">I have a few quest=
ions</font></span><span lang=3D"en-us">
<font face=3D"Arial">and some suggestions</font></span><span lang=3D"en-us"=
> <font face=3D"Arial">
on your recent</font> <font face=3D"Arial">draf</font></span><span lang=3D"=
en-us"><font face=3D"Arial">t</font><font face=3D"Arial">:</font></span><sp=
an lang=3D"en-us"><font face=3D"Arial">
</font></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">Section 2 (</font>=
</span><span lang=3D"en-us"><font face=3D"Arial">Overview</font></span><spa=
n lang=3D"en-us"><font face=3D"Arial">)</font></span><span lang=3D"en-us"><=
font face=3D"Arial">,</font></span><span lang=3D"en-us">
</span></p>
<ul dir=3D"ltr">
<ul dir=3D"ltr">
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">there are several =
reference</font></span><span lang=3D"en-us"><font face=3D"Arial">s</font></=
span><span lang=3D"en-us"><font face=3D"Arial"> of</font>
<font face=3D"Arial">measuring</font><font face=3D"Arial"></font></span><sp=
an lang=3D"en-us">
<font face=3D"Arial">=93</font></span><span lang=3D"en-us"><font face=3D"Ar=
ial">packets</font></span><span lang=3D"en-us"><font face=3D"Arial">=94</fo=
nt></span><span lang=3D"en-us"><font face=3D"Arial"> without</font></span><=
span lang=3D"en-us">
<font face=3D"Arial">s</font><font face=3D"Arial">pecifying if the packets =
are LM/DM packets or actual data plane packets.</font><font face=3D"Arial">=
</font>
<font face=3D"Arial">Such Page 7</font></span><span lang=3D"en-us"><font fa=
ce=3D"Arial"> first paragraph:</font></span><span lang=3D"en-us"><font face=
=3D"Arial"></font></span><span lang=3D"en-us">
<font face=3D"Arial">=93</font></span><span lang=3D"en-us"><font face=3D"Ar=
ial"></font></span><span lang=3D"en-us"><i></i></span><span lang=3D"en-us">=
<i>
<font face=3D"Courier" color=3D"#0000ff" size=3D"2">the count of packets re=
ceived prior</font></i></span><span lang=3D"en-us"><i></i></span><span lang=
=3D"en-us"><i><font face=3D"Courier" color=3D"#0000ff" size=3D"2"></font></=
i></span><span lang=3D"en-us"><i></i></span><span lang=3D"en-us"><i>
<font face=3D"Courier" color=3D"#0000ff" size=3D"2">to time T2 over the cha=
nnel from A (B_RxP)</font></i></span><span lang=3D"en-us"></span><span lang=
=3D"en-us"><font face=3D"Courier" size=3D"2">,</font></span><span lang=3D"e=
n-us"></span><span lang=3D"en-us"><font face=3D"Courier" size=3D"2">=94</fo=
nt></span><span lang=3D"en-us"></span><span lang=3D"en-us"></span></p>
</ul>
</ul>
<p dir=3D"ltr"><span lang=3D"en-us"></span></p>
<ul dir=3D"ltr">
<ul dir=3D"ltr">
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">Is</font></span><s=
pan lang=3D"en-us">
<font face=3D"Arial">t</font><font face=3D"Arial">his</font></span><span la=
ng=3D"en-us"><font face=3D"Arial"> the intent?</font>
<font face=3D"Arial">S</font><font face=3D"Arial">o</font></span><span lang=
=3D"en-us"> <font face=3D"Arial">
that LM can be used to either measuring the LM losses and data plane loss? =
</font>
</span></p>
</ul>
</ul>
<p dir=3D"ltr"><span lang=3D"en-us"></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">Section</font> <fo=
nt face=3D"Arial">
2.7.1 Types of Channels</font><font face=3D"Arial">: </font></span></p>
<ul dir=3D"ltr">
<ul dir=3D"ltr">
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">It</font></span><s=
pan lang=3D"en-us">
<font face=3D"Arial">stated</font></span><span lang=3D"en-us"><font face=3D=
"Arial"></font>
<font face=3D"Arial">that LM and DM</font></span><span lang=3D"en-us"> <fon=
t face=3D"Arial">
flow over MPLS G-Ach.</font> <font face=3D"Arial">S</font><font face=3D"Ari=
al">ince packets over G-Ach might encounter extra processing on intermediat=
e nodes</font></span><span lang=3D"en-us"><font face=3D"Arial">,</font></sp=
an><span lang=3D"en-us"><font face=3D"Arial">
 the</font></span><span lang=3D"en-us"> <font face=3D"Arial">Delay measured=
 over G-Ach channel might be slightly different from</font></span><span lan=
g=3D"en-us">
<font face=3D"Arial">the</font></span><span lang=3D"en-us"><font face=3D"Ar=
ial"></font>
<font face=3D"Arial">data pla</font><font face=3D"Arial">ne channel</font><=
/span><span lang=3D"en-us"><font face=3D"Arial">. Will it be a problem?</fo=
nt></span><span lang=3D"en-us">
</span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"times new roman" color=3D=
"#0000ff">[[Sasha]] IMHO packets running over G-ACh SHOULD NOT experience a=
ny special processing in the intermediate nodes because GAL (and, by implic=
ation G-ACh) will not be exposed to these
 nodes. However, this is only true <em>if the overall depth of the label st=
ack (GAL included) does not exceed the limit on the number of labels these =
nodes are ready to treat normally</em>.
</font></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"times new roman" color=3D=
"#0000ff">What happens if this limit is exceeded is implementation-specific=
 and may be as severe as dropping offending packets unconditionally. Other =
known cases include ignoring extra labels,
 slowing down processing etc.</font></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"times new roman" color=3D=
"#0000ff">AFAIK, MPLS-TP development had, so far, ignored this problem. May=
be it is high time to recognize it?</font></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"times new roman" color=3D=
"#0000ff"></font></span>&nbsp;</p>
</ul>
</ul>
<p dir=3D"ltr"><span lang=3D"en-us"></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">Section 2.7.6. Los=
s Measurement Modes</font></span></p>
<ul dir=3D"ltr">
<ul dir=3D"ltr">
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">U</font><font face=
=3D"Arial">nde</font><font face=3D"Arial">r t</font><font face=3D"Arial">he=
</font></span><span lang=3D"en-us">
<font face=3D"Arial">=93</font></span><span lang=3D"en-us"><font face=3D"Ar=
ial">dire</font><font face=3D"Arial">ct</font>
<font face=3D"Arial">mod</font><font face=3D"Arial">e</font></span><span la=
ng=3D"en-us"><font face=3D"Arial">=94</font></span><span lang=3D"en-us"><fo=
nt face=3D"Arial">,</font></span><span lang=3D"en-us">
<font face=3D"Arial">I interpre</font><font face=3D"Arial">t it as measurin=
g the data plane</font>
<font face=3D"Arial">packets, is it correct? </font></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">C</font><font face=
=3D"Arial">ounting</font></span><span lang=3D"en-us"><font face=3D"Arial"> =
data plane packets</font>
<font face=3D"Arial">can be process intensive</font></span><span lang=3D"en=
-us"><font face=3D"Arial">.</font></span><span lang=3D"en-us"><font face=3D=
"Arial"></font></span><span lang=3D"en-us">&nbsp;<font face=3D"Arial"></fon=
t></span><span lang=3D"en-us">
<font face=3D"Arial">Usually the each</font></span><span lang=3D"en-us"> <f=
ont face=3D"Arial">
node (or</font></span><span lang=3D"en-us"> <font face=3D"Arial">line card<=
/font></span><span lang=3D"en-us"><font face=3D"Arial">)</font></span><span=
 lang=3D"en-us"><font face=3D"Arial"> can only</font></span><span lang=3D"e=
n-us">
<font face=3D"Arial">d</font><font face=3D"Arial">o actual packet</font></s=
pan><span lang=3D"en-us"><font face=3D"Arial"></font>
<font face=3D"Arial">counting for</font> <font face=3D"Arial">limited numbe=
r of</font>
<font face=3D"Arial">LSPs.</font></span><span lang=3D"en-us"> <font face=3D=
"Arial">T</font><font face=3D"Arial">herefore, I suggest</font>
<font face=3D"Arial">allowing</font><font face=3D"Arial"> B node to ignore =
A node</font></span><span lang=3D"en-us"><font face=3D"Arial">=92</font></s=
pan><span lang=3D"en-us"><font face=3D"Arial">s LM when B</font>
<font face=3D"Arial">is not ready to do the counting</font></span><span lan=
g=3D"en-us"><font face=3D"Arial"> or send back a reply to indicate the</fon=
t></span><span lang=3D"en-us">
<font face=3D"Arial">=93</font></span><span lang=3D"en-us"><font face=3D"Ar=
ial">not ready status</font></span><span lang=3D"en-us"><font face=3D"Arial=
">=94</font></span><span lang=3D"en-us"><font face=3D"Arial">.</font></span=
><span lang=3D"en-us">
</span></p>
</ul>
</ul>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Courier New">o&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;</font></span><span lang=3D"en-us">
<font face=3D"Arial">Several options are possible for the negotiation: egre=
ss simply ignore the request when it is not ready, egress sends back an err=
or, e</font><font face=3D"Arial">tc. Ingress node doesn</font><font face=3D=
"Arial">=92</font><font face=3D"Arial">t need
 to start counting traffic until it gets confirmation from the egress node.=
</font></span><span lang=3D"en-us">
</span></p>
<p dir=3D"ltr"><span lang=3D"en-us"></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">Should allow optio=
ns of either byte counter or packet counter.
</font></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">Thank you very muc=
h. </font></span></p>
<p dir=3D"ltr"><span lang=3D"en-us"><font face=3D"Arial">Linda Dunbar</font=
></span><span lang=3D"en-us"></span></p>
</div>
</div>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C76D6B8336307ILPTMAIL02eci_--

From neil.2.harrison@bt.com  Fri Jan  7 00:25:35 2011
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16FCA3A67DF; Fri,  7 Jan 2011 00:25:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.87
X-Spam-Level: 
X-Spam-Status: No, score=-1.87 tagged_above=-999 required=5 tests=[AWL=0.175,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qeLtwOuvMdgY; Fri,  7 Jan 2011 00:25:29 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtp64.intersmtp.COM [62.239.224.237]) by core3.amsl.com (Postfix) with ESMTP id 5F0393A67AC; Fri,  7 Jan 2011 00:25:28 -0800 (PST)
Received: from EVMHT66-UKRD.domain1.systemhost.net (10.36.3.103) by RDW083A008ED64.smtp-e4.hygiene.service (10.187.98.13) with Microsoft SMTP Server (TLS) id 8.3.106.1; Fri, 7 Jan 2011 08:27:34 +0000
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.1.45]) by EVMHT66-UKRD.domain1.systemhost.net ([10.36.3.103]) with mapi; Fri, 7 Jan 2011 08:27:34 +0000
From: <neil.2.harrison@bt.com>
To: <Alexander.Vainshtein@ecitele.com>, <ldunbar@huawei.com>
Date: Fri, 7 Jan 2011 08:27:27 +0000
Thread-Topic: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
Thread-Index: Acut+GY8NiB+SQfOSi+H6qHdg0HkpwAPVrOBAANRHhA=
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E44010665838@EMV62-UKRD.domain1.systemhost.net>
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <A3C5DF08D38B6049839A6F553B331C76D6B8336307@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D6B8336307@ILPTMAIL02.ecitele.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: multipart/alternative; boundary="_000_6D3D47CB84BDE349BC23BF1C94E316E44010665838EMV62UKRDdoma_"
MIME-Version: 1.0
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 08:25:35 -0000

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

Sasha, are you only considering sublayering (same layer network instance), =
or are you considering both sublayering and layering (different layer netwo=
rk instances) wrt depth of label stack (these are technically quite differe=
nt cases even though they may look alike in the DP, though a pukka transpor=
t network should not have sublayering as I have noted previously)?

regards, Neil

________________________________
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: 07 January 2011 06:49
To: Linda Dunbar
Cc: 'Stewart Bryant'; mpls@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"

Linda,
Please see my comment inline below.

Regards,
     Sasha

________________________________
From: mpls-bounces@ietf.org [mpls-bounces@ietf.org] On Behalf Of Linda Dunb=
ar [ldunbar@huawei.com]
Sent: Friday, January 07, 2011 1:21 AM
To: mpls-tp@ietf.org; mpls@ietf.org; 'Dan Frost'; 'Stewart Bryant'
Subject: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"


Dan and Stewart,

I have a few questions and some suggestions on your recent draft:

Section 2 (Overview),

there are several references of measuring "packets" without specifying if t=
he packets are LM/DM packets or actual data plane packets. Such Page 7 firs=
t paragraph: " the count of packets received prior to time T2 over the chan=
nel from A (B_RxP),"

Is this the intent? So that LM can be used to either measuring the LM losse=
s and data plane loss?

Section 2.7.1 Types of Channels:

It stated that LM and DM flow over MPLS G-Ach. Since packets over G-Ach mig=
ht encounter extra processing on intermediate nodes, the Delay measured ove=
r G-Ach channel might be slightly different from the data plane channel. Wi=
ll it be a problem?

[[Sasha]] IMHO packets running over G-ACh SHOULD NOT experience any special=
 processing in the intermediate nodes because GAL (and, by implication G-AC=
h) will not be exposed to these nodes. However, this is only true if the ov=
erall depth of the label stack (GAL included) does not exceed the limit on =
the number of labels these nodes are ready to treat normally.

What happens if this limit is exceeded is implementation-specific and may b=
e as severe as dropping offending packets unconditionally. Other known case=
s include ignoring extra labels, slowing down processing etc.

AFAIK, MPLS-TP development had, so far, ignored this problem. Maybe it is h=
igh time to recognize it?



Section 2.7.6. Loss Measurement Modes

Under the "direct mode", I interpret it as measuring the data plane packets=
, is it correct?

Counting data plane packets can be process intensive.  Usually the each nod=
e (or line card) can only do actual packet counting for limited number of L=
SPs. Therefore, I suggest allowing B node to ignore A node's LM when B is n=
ot ready to do the counting or send back a reply to indicate the "not ready=
 status".

o       Several options are possible for the negotiation: egress simply ign=
ore the request when it is not ready, egress sends back an error, etc. Ingr=
ess node doesn't need to start counting traffic until it gets confirmation =
from the egress node.

Should allow options of either byte counter or packet counter.

Thank you very much.

Linda Dunbar

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=3Dltr><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE id=3DowaTempEditStyle></STYLE>

<STYLE title=3DowaParaStyle><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></STYLE>
</HEAD>
<BODY ocsi=3D"x">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D921181508-07012011><FONT face=3DV=
erdana>Sasha,=20
are you only considering sublayering (same layer network instance), or&nbsp=
;are=20
you considering both sublayering and layering (different layer network=20
instances) wrt depth of label stack (these are technically quite different =
cases=20
even though they may look alike in the DP, though a pukka transport network=
=20
should not have sublayering as I have noted previously)?</FONT></SPAN></DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D921181508-07012011><FONT=20
face=3DVerdana></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D921181508-07012011><FONT=20
face=3DVerdana>regards, Neil</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> mpls-bounces@ietf.org=20
  [mailto:mpls-bounces@ietf.org] <B>On Behalf Of </B>Alexander=20
  Vainshtein<BR><B>Sent:</B> 07 January 2011 06:49<BR><B>To:</B> Linda=20
  Dunbar<BR><B>Cc:</B> 'Stewart Bryant'; mpls@ietf.org;=20
  mpls-tp@ietf.org<BR><B>Subject:</B> Re: [mpls] Questions on=20
  "draft-ietf-mpls-loss-delay-00"<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV=20
  style=3D"FONT-SIZE: 16px; COLOR: #000000; DIRECTION: ltr; FONT-FAMILY: Ti=
mes New Roman">
  <DIV>Linda,</DIV>
  <DIV><FONT face=3D"times new roman">Please see my comment<A></A> inline=20
  below.</FONT></DIV>
  <DIV><FONT face=3D"times new roman"></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"times new roman">Regards,</FONT></DIV>
  <DIV><FONT face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT>=
</DIV>
  <DIV dir=3Dltr><FONT face=3D"Times New Roman" size=3D3></FONT>&nbsp;</DIV=
>
  <DIV id=3DdivRpF337040 style=3D"DIRECTION: ltr">
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> mpls-bounces@ietf.org=20
  [mpls-bounces@ietf.org] On Behalf Of Linda Dunbar=20
  [ldunbar@huawei.com]<BR><B>Sent:</B> Friday, January 07, 2011 1:21=20
  AM<BR><B>To:</B> mpls-tp@ietf.org; mpls@ietf.org; 'Dan Frost'; 'Stewart=20
  Bryant'<BR><B>Subject:</B> [mpls] Questions on=20
  "draft-ietf-mpls-loss-delay-00"<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>Dan and Stewart,=20
  </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>I have a few=20
  questions</FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial>and some=20
  suggestions</FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial>on your=20
  recent</FONT> <FONT face=3DArial>draf</FONT></SPAN><SPAN lang=3Den-us><FO=
NT=20
  face=3DArial>t</FONT><FONT face=3DArial>:</FONT></SPAN><SPAN lang=3Den-us=
><FONT=20
  face=3DArial> </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>Section 2 (</FONT></SP=
AN><SPAN=20
  lang=3Den-us><FONT face=3DArial>Overview</FONT></SPAN><SPAN lang=3Den-us>=
<FONT=20
  face=3DArial>)</FONT></SPAN><SPAN lang=3Den-us><FONT=20
  face=3DArial>,</FONT></SPAN><SPAN lang=3Den-us> </SPAN></P>
  <UL dir=3Dltr>
    <UL dir=3Dltr>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>there are several=
=20
      reference</FONT></SPAN><SPAN lang=3Den-us><FONT=20
      face=3DArial>s</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DArial> of=
</FONT>=20
      <FONT face=3DArial>measuring</FONT><FONT face=3DArial></FONT></SPAN><=
SPAN=20
      lang=3Den-us> <FONT face=3DArial>&#8220;</FONT></SPAN><SPAN lang=3Den=
-us><FONT=20
      face=3DArial>packets</FONT></SPAN><SPAN lang=3Den-us><FONT=20
      face=3DArial>&#8221;</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DAri=
al>=20
      without</FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial>s</FONT><=
FONT=20
      face=3DArial>pecifying if the packets are LM/DM packets or actual dat=
a plane=20
      packets.</FONT><FONT face=3DArial></FONT> <FONT face=3DArial>Such Pag=
e=20
      7</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DArial> first=20
      paragraph:</FONT></SPAN><SPAN lang=3Den-us><FONT=20
      face=3DArial></FONT></SPAN><SPAN lang=3Den-us> <FONT=20
      face=3DArial>&#8220;</FONT></SPAN><SPAN lang=3Den-us><FONT=20
      face=3DArial></FONT></SPAN><SPAN lang=3Den-us><I></I></SPAN><SPAN=20
      lang=3Den-us><I> <FONT face=3DCourier color=3D#0000ff size=3D2>the co=
unt of=20
      packets received prior</FONT></I></SPAN><SPAN=20
      lang=3Den-us><I></I></SPAN><SPAN lang=3Den-us><I><FONT face=3DCourier=
=20
      color=3D#0000ff size=3D2></FONT></I></SPAN><SPAN=20
      lang=3Den-us><I></I></SPAN><SPAN lang=3Den-us><I> <FONT face=3DCourie=
r=20
      color=3D#0000ff size=3D2>to time T2 over the channel from A=20
      (B_RxP)</FONT></I></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us=
><FONT=20
      face=3DCourier size=3D2>,</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPA=
N=20
      lang=3Den-us><FONT face=3DCourier size=3D2>&#8221;</FONT></SPAN><SPAN=
=20
      lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN></P></UL></UL>
  <P dir=3Dltr><SPAN lang=3Den-us></SPAN></P>
  <UL dir=3Dltr>
    <UL dir=3Dltr>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>Is</FONT></SPAN><S=
PAN=20
      lang=3Den-us> <FONT face=3DArial>t</FONT><FONT=20
      face=3DArial>his</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DArial> =
the=20
      intent?</FONT> <FONT face=3DArial>S</FONT><FONT=20
      face=3DArial>o</FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial>th=
at LM can=20
      be used to either measuring the LM losses and data plane loss?=20
      </FONT></SPAN></P></UL></UL>
  <P dir=3Dltr><SPAN lang=3Den-us></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>Section</FONT> <FONT=20
  face=3DArial>2.7.1 Types of Channels</FONT><FONT face=3DArial>: </FONT></=
SPAN></P>
  <UL dir=3Dltr>
    <UL dir=3Dltr>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>It</FONT></SPAN><S=
PAN=20
      lang=3Den-us> <FONT face=3DArial>stated</FONT></SPAN><SPAN lang=3Den-=
us><FONT=20
      face=3DArial></FONT> <FONT face=3DArial>that LM and DM</FONT></SPAN><=
SPAN=20
      lang=3Den-us> <FONT face=3DArial>flow over MPLS G-Ach.</FONT> <FONT=20
      face=3DArial>S</FONT><FONT face=3DArial>ince packets over G-Ach might=
=20
      encounter extra processing on intermediate nodes</FONT></SPAN><SPAN=20
      lang=3Den-us><FONT face=3DArial>,</FONT></SPAN><SPAN lang=3Den-us><FO=
NT=20
      face=3DArial> the</FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial=
>Delay=20
      measured over G-Ach channel might be slightly different=20
      from</FONT></SPAN><SPAN lang=3Den-us> <FONT=20
      face=3DArial>the</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DArial><=
/FONT>=20
      <FONT face=3DArial>data pla</FONT><FONT face=3DArial>ne=20
      channel</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DArial>. Will it =
be a=20
      problem?</FONT></SPAN><SPAN lang=3Den-us> </SPAN></P>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"times new roman"=20
      color=3D#0000ff>[[Sasha]] IMHO packets running over G-ACh SHOULD NOT=
=20
      experience any special processing in the intermediate nodes because G=
AL=20
      (and, by implication G-ACh) will not be exposed to these nodes. Howev=
er,=20
      this is only true <EM>if the overall depth of the label stack (GAL=20
      included) does not exceed the limit on the number of labels these nod=
es=20
      are ready to treat normally</EM>. </FONT></SPAN></P>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"times new roman"=20
      color=3D#0000ff>What happens if this limit is exceeded is=20
      implementation-specific and may be as severe as dropping offending pa=
ckets=20
      unconditionally. Other known cases include ignoring extra labels, slo=
wing=20
      down processing etc.</FONT></SPAN></P>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"times new roman"=20
      color=3D#0000ff>AFAIK, MPLS-TP development had, so far, ignored this=
=20
      problem. Maybe it is high time to recognize it?</FONT></SPAN></P>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"times new roman"=20
      color=3D#0000ff></FONT></SPAN>&nbsp;</P></UL></UL>
  <P dir=3Dltr><SPAN lang=3Den-us></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>Section 2.7.6. Loss Me=
asurement=20
  Modes</FONT></SPAN></P>
  <UL dir=3Dltr>
    <UL dir=3Dltr>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>U</FONT><FONT=20
      face=3DArial>nde</FONT><FONT face=3DArial>r t</FONT><FONT=20
      face=3DArial>he</FONT></SPAN><SPAN lang=3Den-us> <FONT=20
      face=3DArial>&#8220;</FONT></SPAN><SPAN lang=3Den-us><FONT=20
      face=3DArial>dire</FONT><FONT face=3DArial>ct</FONT> <FONT=20
      face=3DArial>mod</FONT><FONT face=3DArial>e</FONT></SPAN><SPAN=20
      lang=3Den-us><FONT face=3DArial>&#8221;</FONT></SPAN><SPAN lang=3Den-=
us><FONT=20
      face=3DArial>,</FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial>I=
=20
      interpre</FONT><FONT face=3DArial>t it as measuring the data plane</F=
ONT>=20
      <FONT face=3DArial>packets, is it correct? </FONT></SPAN></P>
      <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>C</FONT><FONT=20
      face=3DArial>ounting</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DAri=
al> data=20
      plane packets</FONT> <FONT face=3DArial>can be process=20
      intensive</FONT></SPAN><SPAN lang=3Den-us><FONT=20
      face=3DArial>.</FONT></SPAN><SPAN lang=3Den-us><FONT=20
      face=3DArial></FONT></SPAN><SPAN lang=3Den-us>&nbsp;<FONT=20
      face=3DArial></FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial>Usu=
ally the=20
      each</FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial>node=20
      (or</FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial>line=20
      card</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DArial>)</FONT></SPA=
N><SPAN=20
      lang=3Den-us><FONT face=3DArial> can only</FONT></SPAN><SPAN lang=3De=
n-us> <FONT=20
      face=3DArial>d</FONT><FONT face=3DArial>o actual packet</FONT></SPAN>=
<SPAN=20
      lang=3Den-us><FONT face=3DArial></FONT> <FONT face=3DArial>counting f=
or</FONT>=20
      <FONT face=3DArial>limited number of</FONT> <FONT=20
      face=3DArial>LSPs.</FONT></SPAN><SPAN lang=3Den-us> <FONT=20
      face=3DArial>T</FONT><FONT face=3DArial>herefore, I suggest</FONT> <F=
ONT=20
      face=3DArial>allowing</FONT><FONT face=3DArial> B node to ignore A=20
      node</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DArial>&#8217;</FONT=
></SPAN><SPAN=20
      lang=3Den-us><FONT face=3DArial>s LM when B</FONT> <FONT face=3DArial=
>is not=20
      ready to do the counting</FONT></SPAN><SPAN lang=3Den-us><FONT face=
=3DArial>=20
      or send back a reply to indicate the</FONT></SPAN><SPAN lang=3Den-us>=
 <FONT=20
      face=3DArial>&#8220;</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DAri=
al>not ready=20
      status</FONT></SPAN><SPAN lang=3Den-us><FONT face=3DArial>&#8221;</FO=
NT></SPAN><SPAN=20
      lang=3Den-us><FONT face=3DArial>.</FONT></SPAN><SPAN lang=3Den-us>=20
  </SPAN></P></UL></UL>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT=20
  face=3D"Courier New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><=
SPAN=20
  lang=3Den-us> <FONT face=3DArial>Several options are possible for the neg=
otiation:=20
  egress simply ignore the request when it is not ready, egress sends back =
an=20
  error, e</FONT><FONT face=3DArial>tc. Ingress node doesn</FONT><FONT=20
  face=3DArial>&#8217;</FONT><FONT face=3DArial>t need to start counting tr=
affic until it=20
  gets confirmation from the egress node.</FONT></SPAN><SPAN lang=3Den-us>=
=20
  </SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>Should allow options o=
f either=20
  byte counter or packet counter. </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>Thank you very much.=20
  </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial>Linda Dunbar</FONT></S=
PAN><SPAN=20
  lang=3Den-us></SPAN></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>

--_000_6D3D47CB84BDE349BC23BF1C94E316E44010665838EMV62UKRDdoma_--

From danfrost@cisco.com  Fri Jan  7 03:24:36 2011
Return-Path: <danfrost@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDA513A681A; Fri,  7 Jan 2011 03:24:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.348
X-Spam-Level: 
X-Spam-Status: No, score=-10.348 tagged_above=-999 required=5 tests=[AWL=0.252, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H15muk7WEqZ5; Fri,  7 Jan 2011 03:24:35 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id A7EBB3A67E3; Fri,  7 Jan 2011 03:24:35 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 07 Jan 2011 11:26:42 +0000
Received: from isolaria.cisco.com (isolaria.cisco.com [64.100.19.13]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p07BQg5o020665; Fri, 7 Jan 2011 11:26:42 GMT
Received: from isolaria.cisco.com (isolaria [127.0.0.1]) by isolaria.cisco.com (8.13.1/8.13.1) with ESMTP id p07BQg6Z021025; Fri, 7 Jan 2011 06:26:42 -0500
Received: (from danfrost@localhost) by isolaria.cisco.com (8.13.1/8.13.1/Submit) id p07BQfod021024; Fri, 7 Jan 2011 11:26:41 GMT
Date: Fri, 7 Jan 2011 11:26:41 +0000
From: Dan Frost <danfrost@cisco.com>
To: Linda Dunbar <ldunbar@huawei.com>
Message-ID: <20110107112641.GA20790@cisco.com>
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002901cbadf8$66783640$790c7c0a@china.huawei.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 11:24:36 -0000

Hi Linda,

On Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:
> Section 2 (Overview), 
> 		there are several references of measuring "packets" without
> specifying if the packets are LM/DM packets or actual data plane packets.
> Such Page 7 first paragraph: " the count of packets received prior to time
> T2 over the channel from A (B_RxP),"
> 
> 		Is this the intent? So that LM can be used to either
> measuring the LM losses and data plane loss? 

Yes, this is intentional in the overview, because as the rest of the
document makes clear, several options for what exactly to measure exist.

> Section 2.7.1 Types of Channels: 
> 		It stated that LM and DM flow over MPLS G-Ach. Since packets
> over G-Ach might encounter extra processing on intermediate nodes, the Delay
> measured over G-Ach channel might be slightly different from the data plane
> channel. Will it be a problem? 

If a node is truly intermediate and not itself the target of the
measurement operation, I see no reason why the packet would "encounter
extra processing" there, any more than any other packet label-switched
through the node.

> Section 2.7.6. Loss Measurement Modes
> 		Under the "direct mode", I interpret it as measuring the
> data plane packets, is it correct? 

Yes.  This is the meaning of the definition in the text:

   If the counted packets are the packets flowing over the channel in the
   data plane, the loss measurement is said to operate in "direct mode".

> 		Counting data plane packets can be process intensive.
> Usually the each node (or line card) can only do actual packet counting for
> limited number of LSPs. Therefore, I suggest allowing B node to ignore A
> node's LM when B is not ready to do the counting or send back a reply to
> indicate the "not ready status". 
> 
> o	Several options are possible for the negotiation: egress simply
> ignore the request when it is not ready, egress sends back an error, etc.
> Ingress node doesn't need to start counting traffic until it gets
> confirmation from the egress node. 

Indeed, and the last paragraph of Section 4.1.1 says as much.  This was
added as a result of our discussion.

> Should allow options of either byte counter or packet counter. 

This is also in the text; see Section 1, the last paragraph of Section
2.1, and the 'B' data format flag (DFlag) in Section 3.1.

> Thank you very much. 

Thanks for your review!

-d

> Linda Dunbar

From adrian@olddog.co.uk  Fri Jan  7 12:22:04 2011
Return-Path: <adrian@olddog.co.uk>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E21E3A6959; Fri,  7 Jan 2011 12:22:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sl+EnJAUkaA2; Fri,  7 Jan 2011 12:22:02 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by core3.amsl.com (Postfix) with ESMTP id F00963A6973; Fri,  7 Jan 2011 12:21:49 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id p07KNlT8000965;  Fri, 7 Jan 2011 20:23:47 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id p07KNkDb000957;  Fri, 7 Jan 2011 20:23:46 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Alexander Vainshtein'" <Alexander.Vainshtein@ecitele.com>, "'Linda Dunbar'" <ldunbar@huawei.com>
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <A3C5DF08D38B6049839A6F553B331C76D6B8336307@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D6B8336307@ILPTMAIL02.ecitele.com>
Date: Fri, 7 Jan 2011 20:23:43 -0000
Message-ID: <0bbf01cbaea8$c7e714e0$57b53ea0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-index: AQIlvlBV59Kxf6Q5WY9TKG4IStLt2wIG6rkpkwGboKA=
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 20:22:04 -0000

Hi Sasha,

[Major snipping - and conversion to plain text]

> [[Sasha]] IMHO packets running over G-ACh SHOULD NOT experience any 
> special processing in the intermediate nodes because GAL (and, by implication
> G-ACh) will not be exposed to these nodes. However, this is only true if the
> overall depth of the label stack (GAL included) does not exceed the limit on
> the number of labels these nodes are ready to treat normally. 
> What happens if this limit is exceeded is implementation-specific and may
> be as severe as dropping offending packets unconditionally. Other known
> cases include ignoring extra labels, slowing down processing etc.
>
> AFAIK, MPLS-TP development had, so far, ignored this problem. Maybe it
> is high time to recognize it?

There seems (to me) to be a contradiction in what you say.
You say that the GAL is not exposed at intermediate nodes (I agree), but you
imply that the change in the label stack depth will be noticed at the
intermediate nodes.
AFAICS, this would only happen on boxes doing DPI (stay calm, Neil!), and
frankly those boxes *do* "expose" the GAL.

Can you help me by explaining how a transit node could suffer from the increase
the number of labels that a transit node has to "treat normally"?

Thanks,
Adrian




From ldunbar@huawei.com  Fri Jan  7 15:03:41 2011
Return-Path: <ldunbar@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C09E03A68C5; Fri,  7 Jan 2011 15:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.041
X-Spam-Level: 
X-Spam-Status: No, score=-106.041 tagged_above=-999 required=5 tests=[AWL=0.557, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dkLt56phjzX3; Fri,  7 Jan 2011 15:03:33 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 33D2D28C15D; Fri,  7 Jan 2011 15:02:56 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEO001TYDGDSJ@usaga02-in.huawei.com>; Fri, 07 Jan 2011 15:05:02 -0800 (PST)
Received: from L735042 ([10.124.12.121]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LEO00E43DGDAP@usaga02-in.huawei.com>; Fri, 07 Jan 2011 15:05:01 -0800 (PST)
Date: Fri, 07 Jan 2011 17:05:00 -0600
From: Linda Dunbar <ldunbar@huawei.com>
In-reply-to: <20110107112641.GA20790@cisco.com>
To: 'Dan Frost' <danfrost@cisco.com>
Message-id: <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_eVeDEc+zwdtLwBitSOnugg)"
Thread-index: AcuuXdIVgul8EEmhSnuJvY/GqCq6BgAXchGA
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com>
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 23:03:41 -0000

This is a multi-part message in MIME format.

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

Dan, 

Thank you very much for the reply. 

As for Section 4.1.1, may I suggest some wording changes (in blue)? 

				When initiating an LM operation, the far end
may require a period of time to become ready for the requested measurement
operation or the far end may not be able to support the requested
measurement. During this period Under those circumstances, LM queries MAY
simply be discarded, and the querier expecting a response SHOULD be prepared
for this situation, for example by stopping sending LMs after X (e.g. 3)
number of LMs being sent without positive feedback. The initial LM interval
before any response being received could be longer than normal to minimize
the querier's resource consumption. setting a timer to differentiate between
an acceptable initialization delay and a permanent unavailability condition
at the far end. Alternatively, the receiver MAY respond, possibly in a
rate-limited manner, to queries received during this period with an
appropriate notification code. Since counting transmitted packets at querier
side will cost extra resources (or is not free), the querier should delay
counting its transmitted packets until receiving a positive feedback from
the far-end. 

Another comment: 
		I think the document should add a description on the range
of allowed LM/DM intervals. The shorter the interval, the higher the
processing loads on line cards. Therefore, it is necessary to describe the
minimum (and maximum) intervals for LM/DM in the draft, and specifying the
unit (like ms or second). IEEE802.ag specifies its CCM's minimum interval to
be 3ms. To optimize the bits utilization, IEEE802.1Qbg uses 2x format. 

		Since the processing capability on the initiating node (the
querier) and the far end (receiving) node could be different, the receiver
(far end node) may indicate in the response a minimum interval it can
support and the querier may adjust the LM interval to any desired value
greater than that. Therefore, the interval value should be encoded in the
LM/DM message. 

		I suggest adding a section (e.g. 2.7.10) to describe the
LM/DM interval and add a field in the message for interval. 

Linda Dunbar

-----Original Message-----
From: Dan Frost [mailto:danfrost@cisco.com] 
Sent: Friday, January 07, 2011 5:27 AM
To: Linda Dunbar
Cc: mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'
Subject: Re: Questions on "draft-ietf-mpls-loss-delay-00"

Hi Linda,

On Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:
> Section 2 (Overview), 
> 		there are several references of measuring "packets" without
> specifying if the packets are LM/DM packets or actual data plane packets.
> Such Page 7 first paragraph: " the count of packets received prior to time
> T2 over the channel from A (B_RxP),"
> 
> 		Is this the intent? So that LM can be used to either
> measuring the LM losses and data plane loss? 

Yes, this is intentional in the overview, because as the rest of the
document makes clear, several options for what exactly to measure exist.

> Section 2.7.1 Types of Channels: 
> 		It stated that LM and DM flow over MPLS G-Ach. Since packets
> over G-Ach might encounter extra processing on intermediate nodes, the
Delay
> measured over G-Ach channel might be slightly different from the data
plane
> channel. Will it be a problem? 

If a node is truly intermediate and not itself the target of the
measurement operation, I see no reason why the packet would "encounter
extra processing" there, any more than any other packet label-switched
through the node.

> Section 2.7.6. Loss Measurement Modes
> 		Under the "direct mode", I interpret it as measuring the
> data plane packets, is it correct? 

Yes.  This is the meaning of the definition in the text:

   If the counted packets are the packets flowing over the channel in the
   data plane, the loss measurement is said to operate in "direct mode".

> 		Counting data plane packets can be process intensive.
> Usually the each node (or line card) can only do actual packet counting
for
> limited number of LSPs. Therefore, I suggest allowing B node to ignore A
> node's LM when B is not ready to do the counting or send back a reply to
> indicate the "not ready status". 
> 
> o	Several options are possible for the negotiation: egress simply
> ignore the request when it is not ready, egress sends back an error, etc.
> Ingress node doesn't need to start counting traffic until it gets
> confirmation from the egress node. 

Indeed, and the last paragraph of Section 4.1.1 says as much.  This was
added as a result of our discussion.

> Should allow options of either byte counter or packet counter. 

This is also in the text; see Section 1, the last paragraph of Section
2.1, and the 'B' data format flag (DFlag) in Section 3.1.

> Thank you very much. 

Thanks for your review!

-d

> Linda Dunbar

--Boundary_(ID_eVeDEc+zwdtLwBitSOnugg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7036.0">
<TITLE>RE: Questions on =
&quot;draft-ietf-mpls-loss-delay-00&quot;</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Dan, =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">Thank</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">you very</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New"></FONT> <FONT FACE=3D"Courier New">much for the =
reply.</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">As for =
Section 4.1.1,</FONT> <FONT FACE=3D"Courier New">may I suggest some =
wording changes</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New"> (in blue)</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">?</FONT><FONT FACE=3D"Courier New"> </FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR><UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier">When initiating an LM operation,</FONT> <FONT SIZE=3D2 =
FACE=3D"Courier">the far end may require a period of time to become =
ready for the requested measurement operation</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">or the far end may not be able to support the =
requested measurement</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier">.</FONT></SPAN><SPAN =
LANG=3D"en-us"><STRIKE></STRIKE></SPAN><SPAN LANG=3D"en-us"><STRIKE> =
<FONT SIZE=3D2 FACE=3D"Courier">During this =
period</FONT></STRIKE></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier"></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">Under those circumstances</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier">, LM queries MAY simply be discarded, and the</FONT> =
<FONT SIZE=3D2 FACE=3D"Courier">querier expecting a response SHOULD be =
prepared for this situation, for example by</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">stopping sending LMs after X (e.g. 3) number =
of LMs being sent without positive feedback.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">The</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">initial</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">LM =
interval</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">before =
any response</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">being</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">received could be long</FONT><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">er than normal to minimize the =
querier</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">&#8217;</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">s resource consumption.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier"></FONT></SPAN><SPAN =
LANG=3D"en-us"><STRIKE></STRIKE></SPAN><SPAN LANG=3D"en-us"><STRIKE> =
<FONT SIZE=3D2 FACE=3D"Courier">setting a timer to differentiate between =
an acceptable initialization delay and a permanent unavailability =
condition at the far end</FONT></STRIKE></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier"> Alternatively, the receiver MAY respond, possibly in a =
rate-</FONT><FONT SIZE=3D2 FACE=3D"Courier">limited manner, to queries =
received during this period with an appropriate notification =
code.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"> Since =
counting transmitted packets at querier side will cost extra resources =
(or is not free), the querier</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">should</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">delay =
counting its transmitted packets</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">until receiving a positive feedback from the =
far-end</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">. =
</FONT></SPAN></P>
</UL></UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">A</FONT><FONT FACE=3D"Courier New">nother comment: =
</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">I think the =
document should</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">a</FONT><FONT FACE=3D"Courier New">dd a description on</FONT><FONT =
FACE=3D"Courier New"> the</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New"> range of allowed</FONT><FONT FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">LM/DM</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">interval</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">s</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">.</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New"></FONT> <FONT FACE=3D"Courier New">T</FONT><FONT FACE=3D"Courier =
New">he</FONT> <FONT FACE=3D"Courier New">s</FONT><FONT FACE=3D"Courier =
New">horter</FONT><FONT FACE=3D"Courier New"> the</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT FACE=3D"Courier New">interval, the higher</FONT> =
<FONT FACE=3D"Courier New">t</FONT><FONT FACE=3D"Courier =
New">he</FONT><FONT FACE=3D"Courier New"> processing =
loads</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New"> on =
line card</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">s</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">.</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">Therefore,</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">it is necessary to describe</FONT></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">the</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
FACE=3D"Courier New">minimum</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
FACE=3D"Courier New">(</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">and maximum</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">)</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New"> intervals for LM/DM</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> in the =
draft</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">,</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">a</FONT><FONT FACE=3D"Courier New">nd</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> specifying the unit (like ms =
or second)</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">.</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">IEEE8</FONT><FONT FACE=3D"Courier New">02.ag</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> specifies =
its</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">C</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">C</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">M</FONT><FONT FACE=3D"Courier New">&#8217;</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New">s</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT FACE=3D"Courier New">minimum =
interval</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">t</FONT><FONT FACE=3D"Courier New">o be</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> 3ms</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New">. To optimize the =
bits</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New"> =
utilization</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">, IEEE802.1Qbg uses 2</FONT></SPAN><SPAN LANG=3D"en-us"><SUP><FONT =
FACE=3D"Courier New">x</FONT></SUP></SPAN><SPAN =
LANG=3D"en-us"><SUP><FONT FACE=3D"Courier New"></FONT></SUP></SPAN><SPAN =
LANG=3D"en-us"> <FONT FACE=3D"Courier New">format.</FONT></SPAN><SPAN =
LANG=3D"en-us"><SUP><FONT FACE=3D"Courier New"></FONT></SUP></SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Since =
the</FONT> <FONT FACE=3D"Courier New">processing capability on =
the</FONT> <FONT FACE=3D"Courier New">initiating node (the =
querier)</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New"> =
and the far end (receiving) node</FONT><FONT FACE=3D"Courier New"> could =
be different</FONT><FONT FACE=3D"Courier New">,</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT FACE=3D"Courier New">t</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New">he receiver (far end node) may =
indicate in the response a minimum interval it can support and =
the</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">q</FONT><FONT FACE=3D"Courier New">uerier</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> may adjust the LM interval to =
any desired value greater than that.</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"></FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT FACE=3D"Courier New">Therefore,</FONT> <FONT =
FACE=3D"Courier New">t</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">he interval</FONT></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">value</FONT></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">should be encoded in the LM</FONT><FONT =
FACE=3D"Courier New">/DM</FONT><FONT FACE=3D"Courier New"> =
message.</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">I suggest =
add</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">ing</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New"> a =
section</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">(e.g</FONT><FONT FACE=3D"Courier New">.</FONT><FONT FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">2.7.10</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">)</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New"> to =
describe the LM/DM interva</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">l and add a field in the message for =
interval.</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN></P>
</UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Linda =
Dunbar</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">-----Original Message-----<BR>
</FONT><FONT FACE=3D"Courier New">From:</FONT><FONT FACE=3D"Courier =
New"> Dan Frost [<A =
HREF=3D"mailto:danfrost@cisco.com">mailto:danfrost@cisco.com</A>]<BR>
</FONT><FONT FACE=3D"Courier New">Sent:</FONT><FONT FACE=3D"Courier =
New"> Friday, January 07, 2011 5:27 AM<BR>
</FONT><FONT FACE=3D"Courier New">To:</FONT><FONT FACE=3D"Courier New"> =
Linda Dunbar<BR>
</FONT><FONT FACE=3D"Courier New">Cc:</FONT><FONT FACE=3D"Courier New"> =
mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'<BR>
</FONT><FONT FACE=3D"Courier New">Subject:</FONT><FONT FACE=3D"Courier =
New"> Re: Questions on =
&quot;draft-ietf-mpls-loss-delay-00&quot;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Hi =
Linda,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">On Thu, Jan =
06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Section 2 (Over</FONT><FONT FACE=3D"Courier New">view), =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; there are several references =
of measuring &quot;packets&quot; without</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
specifying if the packets are LM/DM packets or actual data plane =
packets.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Such =
Page 7 first paragraph: &quot; the count of packets received prior to =
time</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; T2 =
over the channel from A (B_RxP),&quot;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is this the intent? So that =
LM can be used to either</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
measuring the LM losses and data plane loss? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Yes, this =
is intentional in the overview, because as the rest of =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">document =
makes clear, several options f</FONT><FONT FACE=3D"Courier New">or what =
exactly to measure exist.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Section 2.7.1 Types of Channels: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It stated that LM and DM flow =
over MPLS G-Ach. Since packets</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; over =
G-Ach might encounter extra processing on intermediate nodes, the =
Delay</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
measured over G-Ach channel might be sl</FONT><FONT FACE=3D"Courier =
New">ightly different from the data plane</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
channel. Will it be a problem? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">If a node =
is truly intermediate and not itself the target of the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">measurement =
operation, I see no reason why the packet would =
&quot;encounter</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">extra =
processing&quot; there, any more than any other</FONT><FONT =
FACE=3D"Courier New"> packet label-switched</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">through the =
node.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Section 2.7.6. Loss Measurement Modes</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Under the &quot;direct =
mode&quot;, I interpret it as measuring the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; data =
plane packets, is it correct? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Yes.&nbsp; =
This is the meaning of the definition in the text:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">&nbsp;&nbsp; If the counte</FONT><FONT FACE=3D"Courier New">d =
packets are the packets flowing over the channel in =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">&nbsp;&nbsp; data plane, the loss measurement is said to operate in =
&quot;direct mode&quot;.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Counting data plane packets =
can be process intensive.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Usually the each node (or line card) can only do actual packet counting =
for</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
limited number of LSPs. Therefore, I suggest allowing B node to ignore =
A</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; node's =
LM when B is not ready to do the counting or send back a reply =
to</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
indicate the &quot;not ready st</FONT><FONT FACE=3D"Courier =
New">atus&quot;. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
o&nbsp;&nbsp;&nbsp;&nbsp; Several options are possible for the =
negotiation: egress simply</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; ignore =
the request when it is not ready, egress sends back an error, =
etc.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Ingress node doesn't need to start counting traffic until it =
gets</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
confirmation from the egress no</FONT><FONT FACE=3D"Courier New">de. =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Indeed, and =
the last paragraph of Section 4.1.1 says as much.&nbsp; This =
was</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">added as a =
result of our discussion.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Should =
allow options of either byte counter or packet counter. =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">This is =
also in the text; see Section 1, the last paragraph of =
Section</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">2.</FONT><FONT FACE=3D"Courier New">1, and the 'B' data format flag =
(DFlag) in Section 3.1.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Thank =
you very much. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Thanks for =
your review!</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">-d</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Linda =
Dunbar</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>=

--Boundary_(ID_eVeDEc+zwdtLwBitSOnugg)--

From gregimirsky@gmail.com  Sat Jan  8 13:41:59 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4676B28C0EF; Sat,  8 Jan 2011 13:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.739
X-Spam-Level: 
X-Spam-Status: No, score=-2.739 tagged_above=-999 required=5 tests=[AWL=0.259,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_73=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RKMsWsdo4MA1; Sat,  8 Jan 2011 13:41:57 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 428B23A683E; Sat,  8 Jan 2011 13:41:54 -0800 (PST)
Received: by vws7 with SMTP id 7so7415616vws.31 for <multiple recipients>; Sat, 08 Jan 2011 13:44:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=XicBjZVXGD9zWrLb2JTEwAmsuSV3Y6nrX6WE9apKDlQ=; b=c3xtIaO4Amy8tfmsbSKb+iGYvshJGPl0GCB9R/IaYT02TTBOkMUeYxqjX0RrBsl8OD rkd0QiEAHmkdfNlccxSmjR0swPQY0sFaZtlAr8J5ZCyiOHROlWudAmTe5mmBhnmulu4c OPA54NCK/j48QYdOL1HKnZTKhma+STuJ1lzao=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hZex/9AxD0xlTFCFCOFnQdzfHHdPYvbefN048DE6P/vQPbqZb5tP2+0NBCjhR0v4hu hlv5UIbuP7dLDC0HBOrSbmLy+LtTXsdyH8isGD0Dve2NQ3+tBTGNr8/p5ZkWtevX4p0I S0AwEyJwNi+djN7quk29YOvoL3d4RGS1VAHk8=
MIME-Version: 1.0
Received: by 10.220.193.131 with SMTP id du3mr5356869vcb.118.1294523042013; Sat, 08 Jan 2011 13:44:02 -0800 (PST)
Received: by 10.220.103.4 with HTTP; Sat, 8 Jan 2011 13:44:01 -0800 (PST)
In-Reply-To: <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com>
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com> <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com>
Date: Sat, 8 Jan 2011 13:44:01 -0800
Message-ID: <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Linda Dunbar <ldunbar@huawei.com>
Content-Type: multipart/alternative; boundary=e0cb4e3857a412a33504995ca2fb
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jan 2011 21:41:59 -0000

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

Dear Linda,
I think that specifying particular minimum interval might become too
restrictive when higher bandwidth links become available.

Regards,
Greg

On Fri, Jan 7, 2011 at 3:05 PM, Linda Dunbar <ldunbar@huawei.com> wrote:

>  Dan,
>
> Thank you very much for the reply.
>
> As for Section 4.1.1, may I suggest some wording changes (in blue)?
>
>    When initiating an LM operation, the far end may require a period of
>             time to become ready for the requested measurement operation =
or
>             the far end may not be able to support the requested measurem=
ent
>             . During this period Under those circumstances, LM queries MA=
Y
>             simply be discarded, and the querier expecting a response
>             SHOULD be prepared for this situation, for example by stoppin=
g
>             sending LMs after X (e.g. 3) number of LMs being sent without=
 positive
>             feedback. The initial LM interval before any response being r=
eceived
>             could be longer than normal to minimize the querier=92s resou=
rce
>             consumption. setting a timer to differentiate between an
>             acceptable initialization delay and a permanent unavailabilit=
y condition at
>             the far end. Alternatively, the receiver MAY respond, possibl=
y
>             in a rate-limited manner, to queries received during this
>             period with an appropriate notification code. Since counting
>             transmitted packets at querier side will cost extra resources=
 (or is not
>             free), the querier should delay counting its transmitted
>             packets until receiving a positive feedback from the far-end.
>
>  Another comment:
>
>    I think the document should add a description on the range of allowed
>       LM/DM intervals. The shorter the interval, the higher the processin=
g
>       loads on line cards. Therefore, it is necessary to describe the
>       minimum (and maximum) intervals for LM/DM in the draft, andspecifyi=
ng the unit (like ms or second)
>       . IEEE802.ag specifies its CCM=92s minimum interval to be 3ms. To
>       optimize the bits utilization, IEEE802.1Qbg uses 2x format.
>
>       Since the processing capability on the initiating node (the querier=
)and the far end (receiving) nodecould be different
>       , the receiver (far end node) may indicate in the response a minimu=
m
>       interval it can support and the querier may adjust the LM interval
>       to any desired value greater than that. Therefore, the interval
>       value should be encoded in the LM/DM message.
>
>       I suggest adding a section (e.g. 2.7.10) to describe the LM/DM
>       interval and add a field in the message for interval.
>
>  Linda Dunbar
>
> -----Original Message-----
> From: Dan Frost [mailto:danfrost@cisco.com <danfrost@cisco.com>]
> Sent: Friday, January 07, 2011 5:27 AM
> To: Linda Dunbar
> Cc: mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'
> Subject: Re: Questions on "draft-ietf-mpls-loss-delay-00"
>
> Hi Linda,
>
> On Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:
>
> > Section 2 (Overview),
>
> >               there are several references of measuring "packets" witho=
ut
>
> > specifying if the packets are LM/DM packets or actual data plane packet=
s.
>
> > Such Page 7 first paragraph: " the count of packets received prior to
> time
>
> > T2 over the channel from A (B_RxP),"
>
> >
>
> >               Is this the intent? So that LM can be used to either
>
> > measuring the LM losses and data plane loss?
>
> Yes, this is intentional in the overview, because as the rest of the
>
> document makes clear, several options for what exactly to measure exist.
>
> > Section 2.7.1 Types of Channels:
>
> >               It stated that LM and DM flow over MPLS G-Ach. Since
> packets
>
> > over G-Ach might encounter extra processing on intermediate nodes, the
> Delay
>
> > measured over G-Ach channel might be slightly different from the data
> plane
>
> > channel. Will it be a problem?
>
> If a node is truly intermediate and not itself the target of the
>
> measurement operation, I see no reason why the packet would "encounter
>
> extra processing" there, any more than any other packet label-switched
>
> through the node.
>
> > Section 2.7.6. Loss Measurement Modes
>
> >               Under the "direct mode", I interpret it as measuring the
>
> > data plane packets, is it correct?
>
> Yes.  This is the meaning of the definition in the text:
>
>    If the counted packets are the packets flowing over the channel in the
>
>    data plane, the loss measurement is said to operate in "direct mode".
>
> >               Counting data plane packets can be process intensive.
>
> > Usually the each node (or line card) can only do actual packet counting
> for
>
> > limited number of LSPs. Therefore, I suggest allowing B node to ignore =
A
>
> > node's LM when B is not ready to do the counting or send back a reply t=
o
>
> > indicate the "not ready status".
>
> >
>
> > o     Several options are possible for the negotiation: egress simply
>
> > ignore the request when it is not ready, egress sends back an error, et=
c.
>
> > Ingress node doesn't need to start counting traffic until it gets
>
> > confirmation from the egress node.
>
> Indeed, and the last paragraph of Section 4.1.1 says as much.  This was
>
> added as a result of our discussion.
>
> > Should allow options of either byte counter or packet counter.
>
> This is also in the text; see Section 1, the last paragraph of Section
>
> 2.1, and the 'B' data format flag (DFlag) in Section 3.1.
>
> > Thank you very much.
>
> Thanks for your review!
>
> -d
>
> > Linda Dunbar
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>

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

Dear Linda,<br>I think that specifying particular minimum interval might be=
come too restrictive when higher bandwidth links become available.<br><br>R=
egards,<br>Greg<br><br><div class=3D"gmail_quote">On Fri, Jan 7, 2011 at 3:=
05 PM, Linda Dunbar <span dir=3D"ltr">&lt;<a href=3D"mailto:ldunbar@huawei.=
com">ldunbar@huawei.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">






<div>


<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Dan, </font>=
</span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Thank</font>=
</span><span lang=3D"en-us"> <font face=3D"Courier New">you very</font></sp=
an><span lang=3D"en-us"><font face=3D"Courier New"></font> <font face=3D"Co=
urier New">much for the reply.</font></span><span lang=3D"en-us"> </span></=
p>


<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">As for Secti=
on 4.1.1,</font> <font face=3D"Courier New">may I suggest some wording chan=
ges</font></span><span lang=3D"en-us"><font face=3D"Courier New"> (in blue)=
</font></span><span lang=3D"en-us"><font face=3D"Courier New">?</font><font=
 face=3D"Courier New"> </font></span></p>

<ul dir=3D"LTR"><ul dir=3D"LTR"><ul dir=3D"LTR"><ul dir=3D"LTR">
<p dir=3D"LTR"><span lang=3D"en-us"></span><span lang=3D"en-us"></span><spa=
n lang=3D"en-us"><font face=3D"Courier" size=3D"2">When initiating an LM op=
eration,</font> <font face=3D"Courier" size=3D"2">the far end may require a=
 period of time to become ready for the requested measurement operation</fo=
nt></span><span lang=3D"en-us"></span><span lang=3D"en-us"> <font color=3D"=
#0000ff" face=3D"Courier" size=3D"2">or the far end may not be able to supp=
ort the requested measurement</font></span><span lang=3D"en-us"></span><spa=
n lang=3D"en-us"><font face=3D"Courier" size=3D"2">.</font></span><span lan=
g=3D"en-us"><strike></strike></span><span lang=3D"en-us"><strike> <font fac=
e=3D"Courier" size=3D"2">During this period</font></strike></span><span lan=
g=3D"en-us"></span><span lang=3D"en-us"><font face=3D"Courier" size=3D"2"><=
/font></span><span lang=3D"en-us"></span><span lang=3D"en-us"> <font color=
=3D"#0000ff" face=3D"Courier" size=3D"2">Under those circumstances</font></=
span><span lang=3D"en-us"></span><span lang=3D"en-us"><font face=3D"Courier=
" size=3D"2">, LM queries MAY simply be discarded, and the</font> <font fac=
e=3D"Courier" size=3D"2">querier expecting a response SHOULD be prepared fo=
r this situation, for example by</font></span><span lang=3D"en-us"></span><=
span lang=3D"en-us"> <font color=3D"#0000ff" face=3D"Courier" size=3D"2">st=
opping sending LMs after X (e.g. 3) number of LMs being sent without positi=
ve feedback.</font></span><span lang=3D"en-us"></span><span lang=3D"en-us">=
<font face=3D"Courier" size=3D"2"></font></span><span lang=3D"en-us"></span=
><span lang=3D"en-us"> <font color=3D"#0000ff" face=3D"Courier" size=3D"2">=
The</font></span><span lang=3D"en-us"></span><span lang=3D"en-us"> <font co=
lor=3D"#0000ff" face=3D"Courier" size=3D"2">initial</font></span><span lang=
=3D"en-us"></span><span lang=3D"en-us"> <font color=3D"#0000ff" face=3D"Cou=
rier" size=3D"2">LM interval</font> <font color=3D"#0000ff" face=3D"Courier=
" size=3D"2">before any response</font></span><span lang=3D"en-us"></span><=
span lang=3D"en-us"> <font color=3D"#0000ff" face=3D"Courier" size=3D"2">be=
ing</font></span><span lang=3D"en-us"></span><span lang=3D"en-us"> <font co=
lor=3D"#0000ff" face=3D"Courier" size=3D"2">received could be long</font><f=
ont color=3D"#0000ff" face=3D"Courier" size=3D"2">er than normal to minimiz=
e the querier</font><font color=3D"#0000ff" face=3D"Courier" size=3D"2">=92=
</font><font color=3D"#0000ff" face=3D"Courier" size=3D"2">s resource consu=
mption.</font></span><span lang=3D"en-us"></span><span lang=3D"en-us"><font=
 face=3D"Courier" size=3D"2"></font></span><span lang=3D"en-us"><strike></s=
trike></span><span lang=3D"en-us"><strike> <font face=3D"Courier" size=3D"2=
">setting a timer to differentiate between an acceptable initialization del=
ay and a permanent unavailability condition at the far end</font></strike><=
/span><span lang=3D"en-us"></span><span lang=3D"en-us"><font color=3D"#0000=
ff" face=3D"Courier" size=3D"2">.</font></span><span lang=3D"en-us"></span>=
<span lang=3D"en-us"><font face=3D"Courier" size=3D"2"> Alternatively, the =
receiver MAY respond, possibly in a rate-</font><font face=3D"Courier" size=
=3D"2">limited manner, to queries received during this period with an appro=
priate notification code.</font></span><span lang=3D"en-us"></span><span la=
ng=3D"en-us"><font color=3D"#0000ff" face=3D"Courier" size=3D"2"> Since cou=
nting transmitted packets at querier side will cost extra resources (or is =
not free), the querier</font></span><span lang=3D"en-us"></span><span lang=
=3D"en-us"> <font color=3D"#0000ff" face=3D"Courier" size=3D"2">should</fon=
t><font color=3D"#0000ff" face=3D"Courier" size=3D"2"></font></span><span l=
ang=3D"en-us"></span><span lang=3D"en-us"> <font color=3D"#0000ff" face=3D"=
Courier" size=3D"2">delay counting its transmitted packets</font> <font col=
or=3D"#0000ff" face=3D"Courier" size=3D"2">until receiving a positive feedb=
ack from the far-end</font><font color=3D"#0000ff" face=3D"Courier" size=3D=
"2">. </font></span></p>

</ul></ul></ul></ul>
<p dir=3D"LTR"><span lang=3D"en-us"></span><span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">A</font><fon=
t face=3D"Courier New">nother comment: </font></span></p>
<ul dir=3D"LTR"><ul dir=3D"LTR">
<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">I think the =
document should</font></span><span lang=3D"en-us"> <font face=3D"Courier Ne=
w">a</font><font face=3D"Courier New">dd a description on</font><font face=
=3D"Courier New"> the</font></span><span lang=3D"en-us"><font face=3D"Couri=
er New"> range of allowed</font><font face=3D"Courier New"></font></span><s=
pan lang=3D"en-us"> <font face=3D"Courier New">LM/DM</font></span><span lan=
g=3D"en-us"> <font face=3D"Courier New">interval</font></span><span lang=3D=
"en-us"><font face=3D"Courier New">s</font></span><span lang=3D"en-us"><fon=
t face=3D"Courier New">.</font></span><span lang=3D"en-us"><font face=3D"Co=
urier New"></font> <font face=3D"Courier New">T</font><font face=3D"Courier=
 New">he</font> <font face=3D"Courier New">s</font><font face=3D"Courier Ne=
w">horter</font><font face=3D"Courier New"> the</font></span><span lang=3D"=
en-us"> <font face=3D"Courier New">interval, the higher</font> <font face=
=3D"Courier New">t</font><font face=3D"Courier New">he</font><font face=3D"=
Courier New"> processing loads</font></span><span lang=3D"en-us"><font face=
=3D"Courier New"> on line card</font></span><span lang=3D"en-us"><font face=
=3D"Courier New">s</font></span><span lang=3D"en-us"><font face=3D"Courier =
New">.</font></span><span lang=3D"en-us"><font face=3D"Courier New"></font>=
</span><span lang=3D"en-us"> <font face=3D"Courier New">Therefore,</font></=
span><span lang=3D"en-us"> <font face=3D"Courier New">it is necessary to de=
scribe</font></span><span lang=3D"en-us"> <font face=3D"Courier New">the</f=
ont></span><span lang=3D"en-us"> <font face=3D"Courier New">minimum</font><=
/span><span lang=3D"en-us"> <font face=3D"Courier New">(</font></span><span=
 lang=3D"en-us"><font face=3D"Courier New">and maximum</font></span><span l=
ang=3D"en-us"><font face=3D"Courier New">)</font></span><span lang=3D"en-us=
"><font face=3D"Courier New"> intervals for LM/DM</font></span><span lang=
=3D"en-us"><font face=3D"Courier New"> in the draft</font></span><span lang=
=3D"en-us"><font face=3D"Courier New">,</font></span><span lang=3D"en-us"> =
<font face=3D"Courier New">a</font><font face=3D"Courier New">nd</font></sp=
an><span lang=3D"en-us"><font face=3D"Courier New"> specifying the unit (li=
ke ms or second)</font></span><span lang=3D"en-us"><font face=3D"Courier Ne=
w">.</font></span><span lang=3D"en-us"> <font face=3D"Courier New">IEEE8</f=
ont><font face=3D"Courier New"><a href=3D"http://02.ag" target=3D"_blank">0=
2.ag</a></font></span><span lang=3D"en-us"><font face=3D"Courier New"> spec=
ifies its</font></span><span lang=3D"en-us"> <font face=3D"Courier New">C</=
font></span><span lang=3D"en-us"><font face=3D"Courier New">C</font></span>=
<span lang=3D"en-us"><font face=3D"Courier New">M</font><font face=3D"Couri=
er New">=92</font></span><span lang=3D"en-us"><font face=3D"Courier New">s<=
/font></span><span lang=3D"en-us"> <font face=3D"Courier New">minimum inter=
val</font></span><span lang=3D"en-us"> <font face=3D"Courier New">t</font><=
font face=3D"Courier New">o be</font></span><span lang=3D"en-us"><font face=
=3D"Courier New"> 3ms</font></span><span lang=3D"en-us"><font face=3D"Couri=
er New">. To optimize the bits</font></span><span lang=3D"en-us"><font face=
=3D"Courier New"> utilization</font></span><span lang=3D"en-us"><font face=
=3D"Courier New">, IEEE802.1Qbg uses 2</font></span><span lang=3D"en-us"><s=
up><font face=3D"Courier New">x</font></sup></span><span lang=3D"en-us"><su=
p><font face=3D"Courier New"></font></sup></span><span lang=3D"en-us"> <fon=
t face=3D"Courier New">format.</font></span><span lang=3D"en-us"><sup><font=
 face=3D"Courier New"></font></sup></span><span lang=3D"en-us"> </span></p>


<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Since the</f=
ont> <font face=3D"Courier New">processing capability on the</font> <font f=
ace=3D"Courier New">initiating node (the querier)</font></span><span lang=
=3D"en-us"><font face=3D"Courier New"> and the far end (receiving) node</fo=
nt><font face=3D"Courier New"> could be different</font><font face=3D"Couri=
er New">,</font></span><span lang=3D"en-us"> <font face=3D"Courier New">t</=
font></span><span lang=3D"en-us"><font face=3D"Courier New">he receiver (fa=
r end node) may indicate in the response a minimum interval it can support =
and the</font></span><span lang=3D"en-us"> <font face=3D"Courier New">q</fo=
nt><font face=3D"Courier New">uerier</font></span><span lang=3D"en-us"><fon=
t face=3D"Courier New"> may adjust the LM interval to any desired value gre=
ater than that.</font></span><span lang=3D"en-us"><font face=3D"Courier New=
"></font></span><span lang=3D"en-us"> <font face=3D"Courier New">Therefore,=
</font> <font face=3D"Courier New">t</font></span><span lang=3D"en-us"><fon=
t face=3D"Courier New">he interval</font></span><span lang=3D"en-us"> <font=
 face=3D"Courier New">value</font></span><span lang=3D"en-us"> <font face=
=3D"Courier New">should be encoded in the LM</font><font face=3D"Courier Ne=
w">/DM</font><font face=3D"Courier New"> message.</font></span><span lang=
=3D"en-us"> </span></p>


<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">I suggest ad=
d</font></span><span lang=3D"en-us"><font face=3D"Courier New">ing</font></=
span><span lang=3D"en-us"><font face=3D"Courier New"> a section</font></spa=
n><span lang=3D"en-us"> <font face=3D"Courier New">(e.g</font><font face=3D=
"Courier New">.</font><font face=3D"Courier New"></font></span><span lang=
=3D"en-us"> <font face=3D"Courier New">2.7.10</font></span><span lang=3D"en=
-us"><font face=3D"Courier New">)</font></span><span lang=3D"en-us"><font f=
ace=3D"Courier New"> to describe the LM/DM interva</font></span><span lang=
=3D"en-us"><font face=3D"Courier New">l and add a field in the message for =
interval.</font></span><span lang=3D"en-us"> </span></p>

</ul></ul>
<p dir=3D"LTR"><span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Linda Dunbar=
</font></span><font color=3D"#888888"><span lang=3D"en-us"></span></font></=
p><div><div></div><div class=3D"h5">

<p dir=3D"LTR"><span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">-----Origina=
l Message-----<br>
</font><font face=3D"Courier New">From:</font><font face=3D"Courier New"> D=
an Frost [<a href=3D"mailto:danfrost@cisco.com" target=3D"_blank">mailto:da=
nfrost@cisco.com</a>]<br>
</font><font face=3D"Courier New">Sent:</font><font face=3D"Courier New"> F=
riday, January 07, 2011 5:27 AM<br>
</font><font face=3D"Courier New">To:</font><font face=3D"Courier New"> Lin=
da Dunbar<br>
</font><font face=3D"Courier New">Cc:</font><font face=3D"Courier New"> <a =
href=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.org</a>; <a=
 href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>; &#39;St=
ewart Bryant&#39;<br>

</font><font face=3D"Courier New">Subject:</font><font face=3D"Courier New"=
> Re: Questions on &quot;draft-ietf-mpls-loss-delay-00&quot;</font></span><=
span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Hi Linda,</f=
ont></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">On Thu, Jan =
06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Section=
 2 (Over</font><font face=3D"Courier New">view), </font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; =A0=A0=
=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 there are several references of measuring &=
quot;packets&quot; without</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; specify=
ing if the packets are LM/DM packets or actual data plane packets.</font></=
span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Such Pa=
ge 7 first paragraph: &quot; the count of packets received prior to time</f=
ont></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; T2 over=
 the channel from A (B_RxP),&quot;</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; </font>=
</span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; =A0=A0=
=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 Is this the intent? So that LM can be used =
to either</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; measuri=
ng the LM losses and data plane loss? </font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Yes, this is=
 intentional in the overview, because as the rest of the</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">document mak=
es clear, several options f</font><font face=3D"Courier New">or what exactl=
y to measure exist.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Section=
 2.7.1 Types of Channels: </font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; =A0=A0=
=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 It stated that LM and DM flow over MPLS G-A=
ch. Since packets</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; over G-=
Ach might encounter extra processing on intermediate nodes, the Delay</font=
></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; measure=
d over G-Ach channel might be sl</font><font face=3D"Courier New">ightly di=
fferent from the data plane</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; channel=
. Will it be a problem? </font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">If a node is=
 truly intermediate and not itself the target of the</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">measurement =
operation, I see no reason why the packet would &quot;encounter</font></spa=
n></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">extra proces=
sing&quot; there, any more than any other</font><font face=3D"Courier New">=
 packet label-switched</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">through the =
node.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Section=
 2.7.6. Loss Measurement Modes</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; =A0=A0=
=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 Under the &quot;direct mode&quot;, I interp=
ret it as measuring the</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; data pl=
ane packets, is it correct? </font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Yes.=A0 This=
 is the meaning of the definition in the text:</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">=A0=A0 If th=
e counte</font><font face=3D"Courier New">d packets are the packets flowing=
 over the channel in the</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">=A0=A0 data =
plane, the loss measurement is said to operate in &quot;direct mode&quot;.<=
/font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; =A0=A0=
=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 Counting data plane packets can be process =
intensive.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Usually=
 the each node (or line card) can only do actual packet counting for</font>=
</span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; limited=
 number of LSPs. Therefore, I suggest allowing B node to ignore A</font></s=
pan></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; node&#3=
9;s LM when B is not ready to do the counting or send back a reply to</font=
></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; indicat=
e the &quot;not ready st</font><font face=3D"Courier New">atus&quot;. </fon=
t></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; </font>=
</span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; o=A0=A0=
=A0=A0 Several options are possible for the negotiation: egress simply</fon=
t></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; ignore =
the request when it is not ready, egress sends back an error, etc.</font></=
span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Ingress=
 node doesn&#39;t need to start counting traffic until it gets</font></span=
></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; confirm=
ation from the egress no</font><font face=3D"Courier New">de. </font></span=
></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Indeed, and =
the last paragraph of Section 4.1.1 says as much.=A0 This was</font></span>=
</p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">added as a r=
esult of our discussion.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Should =
allow options of either byte counter or packet counter. </font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">This is also=
 in the text; see Section 1, the last paragraph of Section</font></span></p=
>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">2.</font><fo=
nt face=3D"Courier New">1, and the &#39;B&#39; data format flag (DFlag) in =
Section 3.1.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Thank y=
ou very much. </font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">Thanks for y=
our review!</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">-d</font></s=
pan></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Courier New">&gt; Linda D=
unbar</font></span><span lang=3D"en-us"></span></p>

</div></div></div>
<br>_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
<br></blockquote></div><br>

--e0cb4e3857a412a33504995ca2fb--

From ben@niven-jenkins.co.uk  Sat Jan  8 14:50:53 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 392543A68C8; Sat,  8 Jan 2011 14:50:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.315
X-Spam-Level: 
X-Spam-Status: No, score=-102.315 tagged_above=-999 required=5 tests=[AWL=-0.316, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VjfG8WcdgMf3; Sat,  8 Jan 2011 14:50:52 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id A32183A68BD; Sat,  8 Jan 2011 14:50:51 -0800 (PST)
Received: from cpc22-cmbg15-2-0-cust173.5-4.cable.virginmedia.com ([86.27.176.174] helo=[192.168.0.205]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1Pbhec-0004cF-SU; Sat, 08 Jan 2011 22:52:59 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=windows-1252
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com>
Date: Sat, 8 Jan 2011 22:52:54 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BCECFE9-04D8-4E8F-A01A-55D76C0E64C9@niven-jenkins.co.uk>
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com> <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com> <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jan 2011 22:50:53 -0000

Linda, colleagues,

4 comments:

1) The edits suggested by Linda change the semantics from suggesting a =
querier maintain a timer to allow for the receiving end to "get its act =
together" to if the receiving end doesn't get its act together within X =
packets stop sending LM. Is that really what's intended? I would expect =
the time taken for the receiving end "to get its act together" would not =
be a function of the LM transmission rate and therefore using =
transmission rate to guess whether the receiving end is dead Vs getting =
itself ready doesn't sound sensible.

2) I don't like the final sentence suggesting queriers should delay =
counting transmitted packets until receiving a positive response because =
doing so costs resources. It sounds like an internal implementation =
decision that has nothing to do with interoperability and therefore =
irrelevant.

3) I am not sure of the value of specifically calling out =
minimum/maximum intervals in the draft. Section 2.1 already describes =
how to calculate theoretical min/max values as a function of counter =
size, packet size & link speed, further restricting the set to specific =
numbers doesn't seem helpful.
On 8 Jan 2011, at 21:44, Greg Mirsky wrote:

4) Giving the receiving end the opportunity to reply with "I can;t =
support the rate you're asking for it's too fast for me" sounds =
attractive but I am not sure it is in practice if one thinks how such =
functionality is likely to be used. If an operator is going to turn it =
on with the thinking that performing LM of some sort is important =
regardless of the LM interval then negotiating a shorter interval may =
have value. However I don't expect that to be the case. I would expect =
an operator to pre-plan what interval they need given their knowledge of =
their network and the accuracy they desire, having the network change =
that may well cause unexpected consequences. In such a scenario I think =
it's better to let the receiver "hard fail" and the operator can =
investigate rather than have the network re-configure and the =
re-configuration go unnoticed, after all LM failing does not impact the =
ability of the network to actually forward packets.

Ben

> Dear Linda,
> I think that specifying particular minimum interval might become too =
restrictive when higher bandwidth links become available.
>=20
> Regards,
> Greg
>=20
> On Fri, Jan 7, 2011 at 3:05 PM, Linda Dunbar <ldunbar@huawei.com> =
wrote:
> Dan,
>=20
> Thank you very much for the reply.
>=20
> As for Section 4.1.1, may I suggest some wording changes (in blue)?
>=20
> When initiating an LM operation, the far end may require a period of =
time to become ready for the requested measurement operation or the far =
end may not be able to support the requested measurement. During this =
period Under those circumstances, LM queries MAY simply be discarded, =
and the querier expecting a response SHOULD be prepared for this =
situation, for example by stopping sending LMs after X (e.g. 3) number =
of LMs being sent without positive feedback. The initial LM interval =
before any response being received could be longer than normal to =
minimize the querier=92s resource consumption. setting a timer to =
differentiate between an acceptable initialization delay and a permanent =
unavailability condition at the far end. Alternatively, the receiver MAY =
respond, possibly in a rate-limited manner, to queries received during =
this period with an appropriate notification code. Since counting =
transmitted packets at querier side will cost extra resources (or is not =
free), the querier should delay counting its transmitted packets until =
receiving a positive feedback from the far-end.
>=20
>=20
> Another comment:
>=20
> I think the document should add a description on the range of allowed =
LM/DM intervals. The shorter the interval, the higher the processing =
loads on line cards. Therefore, it is necessary to describe the minimum =
(and maximum) intervals for LM/DM in the draft, and specifying the unit =
(like ms or second). IEEE802.ag specifies its CCM=92s minimum interval =
to be 3ms. To optimize the bits utilization, IEEE802.1Qbg uses 2x =
format.
>=20
> Since the processing capability on the initiating node (the querier) =
and the far end (receiving) node could be different, the receiver (far =
end node) may indicate in the response a minimum interval it can support =
and the querier may adjust the LM interval to any desired value greater =
than that. Therefore, the interval value should be encoded in the LM/DM =
message.
>=20
> I suggest adding a section (e.g. 2.7.10) to describe the LM/DM =
interval and add a field in the message for interval.
>=20
>=20
> Linda Dunbar
>=20
>=20
> -----Original Message-----
> From: Dan Frost [mailto:danfrost@cisco.com]
> Sent: Friday, January 07, 2011 5:27 AM
> To: Linda Dunbar
> Cc: mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'
> Subject: Re: Questions on "draft-ietf-mpls-loss-delay-00"
>=20
> Hi Linda,
>=20
> On Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:
>=20
> > Section 2 (Overview),
>=20
> >               there are several references of measuring "packets" =
without
>=20
> > specifying if the packets are LM/DM packets or actual data plane =
packets.
>=20
> > Such Page 7 first paragraph: " the count of packets received prior =
to time
>=20
> > T2 over the channel from A (B_RxP),"
>=20
> >
>=20
> >               Is this the intent? So that LM can be used to either
>=20
> > measuring the LM losses and data plane loss?
>=20
> Yes, this is intentional in the overview, because as the rest of the
>=20
> document makes clear, several options for what exactly to measure =
exist.
>=20
> > Section 2.7.1 Types of Channels:
>=20
> >               It stated that LM and DM flow over MPLS G-Ach. Since =
packets
>=20
> > over G-Ach might encounter extra processing on intermediate nodes, =
the Delay
>=20
> > measured over G-Ach channel might be slightly different from the =
data plane
>=20
> > channel. Will it be a problem?
>=20
> If a node is truly intermediate and not itself the target of the
>=20
> measurement operation, I see no reason why the packet would "encounter
>=20
> extra processing" there, any more than any other packet label-switched
>=20
> through the node.
>=20
> > Section 2.7.6. Loss Measurement Modes
>=20
> >               Under the "direct mode", I interpret it as measuring =
the
>=20
> > data plane packets, is it correct?
>=20
> Yes.  This is the meaning of the definition in the text:
>=20
>    If the counted packets are the packets flowing over the channel in =
the
>=20
>    data plane, the loss measurement is said to operate in "direct =
mode".
>=20
> >               Counting data plane packets can be process intensive.
>=20
> > Usually the each node (or line card) can only do actual packet =
counting for
>=20
> > limited number of LSPs. Therefore, I suggest allowing B node to =
ignore A
>=20
> > node's LM when B is not ready to do the counting or send back a =
reply to
>=20
> > indicate the "not ready status".
>=20
> >
>=20
> > o     Several options are possible for the negotiation: egress =
simply
>=20
> > ignore the request when it is not ready, egress sends back an error, =
etc.
>=20
> > Ingress node doesn't need to start counting traffic until it gets
>=20
> > confirmation from the egress node.
>=20
> Indeed, and the last paragraph of Section 4.1.1 says as much.  This =
was
>=20
> added as a result of our discussion.
>=20
> > Should allow options of either byte counter or packet counter.
>=20
> This is also in the text; see Section 1, the last paragraph of Section
>=20
> 2.1, and the 'B' data format flag (DFlag) in Section 3.1.
>=20
> > Thank you very much.
>=20
> Thanks for your review!
>=20
> -d
>=20
> > Linda Dunbar
>=20
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20
>=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


From ldunbar@huawei.com  Mon Jan 10 08:26:21 2011
Return-Path: <ldunbar@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7529D3A67FA; Mon, 10 Jan 2011 08:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.774
X-Spam-Level: 
X-Spam-Status: No, score=-105.774 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id noLyyo+m+Ohq; Mon, 10 Jan 2011 08:26:10 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 4AB4D3A67ED; Mon, 10 Jan 2011 08:26:10 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LET00CWZF3BWH@usaga02-in.huawei.com>; Mon, 10 Jan 2011 08:28:24 -0800 (PST)
Received: from L735042 ([10.124.12.121]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LET001M3F3BE4@usaga02-in.huawei.com>; Mon, 10 Jan 2011 08:28:23 -0800 (PST)
Date: Mon, 10 Jan 2011 10:28:23 -0600
From: Linda Dunbar <ldunbar@huawei.com>
In-reply-to: <9BCECFE9-04D8-4E8F-A01A-55D76C0E64C9@niven-jenkins.co.uk>
To: 'Ben Niven-Jenkins' <ben@niven-jenkins.co.uk>, 'Greg Mirsky' <gregimirsky@gmail.com>
Message-id: <009501cbb0e3$665cbe90$790c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_Qo+4zvuSWR1RKSG7WSb6lg)"
Thread-index: Acuvhs9iO3lG3SG2QdOktkR92i+tTwBWhasg
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com> <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com> <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com> <9BCECFE9-04D8-4E8F-A01A-55D76C0E64C9@niven-jenkins.co.uk>
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 16:26:21 -0000

This is a multi-part message in MIME format.

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

Ben, 

Answers to your questions and comments are inserted below in Blue. 

-----Original Message-----
From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk] 
Sent: Saturday, January 08, 2011 4:53 PM
To: Greg Mirsky
Cc: Linda Dunbar; mpls@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"

Linda, colleagues,

4 comments:

1) The edits suggested by Linda change the semantics from suggesting a
querier maintain a timer to allow for the receiving end to "get its act
together" to if the receiving end doesn't get its act together within X
packets stop sending LM. Is that really what's intended? I would expect the
time taken for the receiving end "to get its act together" would not be a
function of the LM transmission rate and therefore using transmission rate
to guess whether the receiving end is dead Vs getting itself ready doesn't
sound sensible.

[Linda] The reason for suggesting Initiator to have slower transmission rate
is to minimize processing needed at the Initiator before Far End committing
to the counting. 
We have considered implementing this feature on our products and discovered
that it DOES take some time for the Central CPU to receive the Counting
Request (as LM in this draft), check if the requested Counting can be
supported, pass the request to the corresponding line card, and get
confirmation from the Line card. Sometimes, the Far End can't perform the
requested Counting because it is performing counting for requests from other
nodes. 




2) I don't like the final sentence suggesting queriers should delay counting
transmitted packets until receiving a positive response because doing so
costs resources. It sounds like an internal implementation decision that has
nothing to do with interoperability and therefore irrelevant.

[Linda]I agree with your point that that the Source Node performing or not
performing the counting before receiving the positive feedback from Far End
is not interoperability issue. Maybe it can be a recommendation? 

But it is necessary for Source node to abort the effort after not receiving
the positive feedback after sometime (like X number of LM or timer expires).



3) I am not sure of the value of specifically calling out minimum/maximum
intervals in the draft. Section 2.1 already describes how to calculate
theoretical min/max values as a function of counter size, packet size & link
speed, further restricting the set to specific numbers doesn't seem helpful.
On 8 Jan 2011, at 21:44, Greg Mirsky wrote:

[Linda]I don't have strong feeling about specifying Min/Max intervals in the
draft. 
But it is very important to have the interval specified in the Message
because Far End needs to know in preparing for the counting, and there is a
possibility that Far End may not be able to support the interval initiated
by the Querier. 

4) Giving the receiving end the opportunity to reply with "I can;t support
the rate you're asking for it's too fast for me" sounds attractive but I am
not sure it is in practice if one thinks how such functionality is likely to
be used. If an operator is going to turn it on with the thinking that
performing LM of some sort is important regardless of the LM interval then
negotiating a shorter interval may have value. However I don't expect that
to be the case. I would expect an operator to pre-plan what interval they
need given their knowledge of their network and the accuracy they desire,
having the network change that may well cause unexpected consequences. In
such a scenario I think it's better to let the receiver "hard fail" and the
operator can investigate rather than have the network re-configure and the
re-configuration go unnoticed, after all LM failing does not impact the
ability of the network to actually forward packets.

[Linda] Do you mean that Receiver can ignore the LMs if the Interval
specified in the message is more than it can handle? 


Ben

> Dear Linda,
> I think that specifying particular minimum interval might become too
restrictive when higher bandwidth links become available.
> 
> Regards,
> Greg
> 
> On Fri, Jan 7, 2011 at 3:05 PM, Linda Dunbar <ldunbar@huawei.com> wrote:
> Dan,
> 
> Thank you very much for the reply.
> 
> As for Section 4.1.1, may I suggest some wording changes (in blue)?
> 
> When initiating an LM operation, the far end may require a period of time
to become ready for the requested measurement operation or the far end may
not be able to support the requested measurement. During this period Under
those circumstances, LM queries MAY simply be discarded, and the querier
expecting a response SHOULD be prepared for this situation, for example by
stopping sending LMs after X (e.g. 3) number of LMs being sent without
positive feedback. The initial LM interval before any response being
received could be longer than normal to minimize the querier's resource
consumption. setting a timer to differentiate between an acceptable
initialization delay and a permanent unavailability condition at the far
end. Alternatively, the receiver MAY respond, possibly in a rate-limited
manner, to queries received during this period with an appropriate
notification code. Since counting transmitted packets at querier side will
cost extra resources (or is not free), the querier should delay counting its
transmitted packets until receiving a positive feedback from the far-end.
> 
> 
> Another comment:
> 
> I think the document should add a description on the range of allowed
LM/DM intervals. The shorter the interval, the higher the processing loads
on line cards. Therefore, it is necessary to describe the minimum (and
maximum) intervals for LM/DM in the draft, and specifying the unit (like ms
or second). IEEE802.ag specifies its CCM's minimum interval to be 3ms. To
optimize the bits utilization, IEEE802.1Qbg uses 2x format.
> 
> Since the processing capability on the initiating node (the querier) and
the far end (receiving) node could be different, the receiver (far end node)
may indicate in the response a minimum interval it can support and the
querier may adjust the LM interval to any desired value greater than that.
Therefore, the interval value should be encoded in the LM/DM message.
> 
> I suggest adding a section (e.g. 2.7.10) to describe the LM/DM interval
and add a field in the message for interval.
> 
> 
> Linda Dunbar
> 
> 
> -----Original Message-----
> From: Dan Frost [mailto:danfrost@cisco.com]
> Sent: Friday, January 07, 2011 5:27 AM
> To: Linda Dunbar
> Cc: mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'
> Subject: Re: Questions on "draft-ietf-mpls-loss-delay-00"
> 
> Hi Linda,
> 
> On Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:
> 
> > Section 2 (Overview),
> 
> >               there are several references of measuring "packets"
without
> 
> > specifying if the packets are LM/DM packets or actual data plane
packets.
> 
> > Such Page 7 first paragraph: " the count of packets received prior to
time
> 
> > T2 over the channel from A (B_RxP),"
> 
> >
> 
> >               Is this the intent? So that LM can be used to either
> 
> > measuring the LM losses and data plane loss?
> 
> Yes, this is intentional in the overview, because as the rest of the
> 
> document makes clear, several options for what exactly to measure exist.
> 
> > Section 2.7.1 Types of Channels:
> 
> >               It stated that LM and DM flow over MPLS G-Ach. Since
packets
> 
> > over G-Ach might encounter extra processing on intermediate nodes, the
Delay
> 
> > measured over G-Ach channel might be slightly different from the data
plane
> 
> > channel. Will it be a problem?
> 
> If a node is truly intermediate and not itself the target of the
> 
> measurement operation, I see no reason why the packet would "encounter
> 
> extra processing" there, any more than any other packet label-switched
> 
> through the node.
> 
> > Section 2.7.6. Loss Measurement Modes
> 
> >               Under the "direct mode", I interpret it as measuring the
> 
> > data plane packets, is it correct?
> 
> Yes.  This is the meaning of the definition in the text:
> 
>    If the counted packets are the packets flowing over the channel in the
> 
>    data plane, the loss measurement is said to operate in "direct mode".
> 
> >               Counting data plane packets can be process intensive.
> 
> > Usually the each node (or line card) can only do actual packet counting
for
> 
> > limited number of LSPs. Therefore, I suggest allowing B node to ignore A
> 
> > node's LM when B is not ready to do the counting or send back a reply to
> 
> > indicate the "not ready status".
> 
> >
> 
> > o     Several options are possible for the negotiation: egress simply
> 
> > ignore the request when it is not ready, egress sends back an error,
etc.
> 
> > Ingress node doesn't need to start counting traffic until it gets
> 
> > confirmation from the egress node.
> 
> Indeed, and the last paragraph of Section 4.1.1 says as much.  This was
> 
> added as a result of our discussion.
> 
> > Should allow options of either byte counter or packet counter.
> 
> This is also in the text; see Section 1, the last paragraph of Section
> 
> 2.1, and the 'B' data format flag (DFlag) in Section 3.1.
> 
> > Thank you very much.
> 
> Thanks for your review!
> 
> -d
> 
> > Linda Dunbar
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
> 
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


--Boundary_(ID_Qo+4zvuSWR1RKSG7WSb6lg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7036.0">
<TITLE>RE: [mpls-tp] [mpls] Questions on =
&quot;draft-ietf-mpls-loss-delay-00&quot;</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">Ben, </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">Answers to your questions and comments are inserted =
below in Blue.</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">-----Original Message-----<BR>
</FONT><FONT FACE=3D"Courier New">From:</FONT><FONT FACE=3D"Courier =
New"> Ben Niven-Jenkins [<A =
HREF=3D"mailto:ben@niven-jenkins.co.uk">mailto:ben@niven-jenkins.co.uk</A=
>]<BR>
</FONT><FONT FACE=3D"Courier New">Sent:</FONT><FONT FACE=3D"Courier =
New"> Saturday, January 08, 2011 4:53 PM<BR>
</FONT><FONT FACE=3D"Courier New">To:</FONT><FONT FACE=3D"Courier New"> =
Greg Mirsky<BR>
</FONT><FONT FACE=3D"Courier New">Cc:</FONT><FONT FACE=3D"Courier New"> =
Linda Dunbar; mpls@ietf.org; mpls-tp@ietf.org<BR>
</FONT><FONT FACE=3D"Courier New">Subject:</FONT><FONT FACE=3D"Courier =
New"> Re: [mpls-tp] [mpls] Questions on =
&quot;draft-ietf-mpls-loss-delay-00&quot;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Linda, =
colleagues,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">4 =
comments:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">1) The =
edits suggested by Linda change the semantics from suggesting a querier =
maintain a time</FONT><FONT FACE=3D"Courier New">r to allow for the =
receiving end to &quot;get its act together&quot; to if the receiving =
end doesn't get its act together within X packets stop sending LM. Is =
that really what's intended? I would expect the time taken for the =
receiving end &quot;to get its act together&quot;</FONT><FONT =
FACE=3D"Courier New"></FONT> <FONT FACE=3D"Courier New">would not be a =
function of the LM transmission rate and therefore using transmission =
rate to guess whether the receiving end is dead Vs getting itself ready =
doesn't sound sensible.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">[Linda]</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New"> The reason for suggesting =
Initiator to have slower transmission rate is to minimize processing =
needed at the Initiator before Far End commit</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">ting</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> to the counting.</FONT></SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">W</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">e have considered implementing this feature on our =
produc</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier New">ts and =
discovered that</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">it DOES take some time for the =
Central CPU</FONT> <FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">to</FONT> <FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">receive</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier New"> the =
Counting Request (</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">a</FONT><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">s LM in this draft</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" FACE=3D"Courier New">), check if =
the requested Counting can be supported,</FONT> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">pass the request to the corresponding line =
card</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">, and get confirmation</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" FACE=3D"Courier New"> from the =
Line card</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">.</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">Sometimes, the Far End =
can't</FONT> <FONT COLOR=3D"#0000FF" FACE=3D"Courier New">p</FONT><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">erform the requested =
Counting</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> because it is performing counting for</FONT> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">requests</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" FACE=3D"Courier New"> from other =
nodes</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">2) I don't =
like the final sentence suggesting queriers should delay counting =
transmitted packets until receiving a positive response because doing so =
costs resources. It sounds like an internal implementation decision that =
has nothing to do with interoper</FONT><FONT FACE=3D"Courier =
New">a</FONT><FONT FACE=3D"Courier New">bility and therefore =
irrelevant.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">[Linda]</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">I agree with your point =
that</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">that</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">the Source =
Node</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">perform</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">ing</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" FACE=3D"Courier New"> or not =
perform</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">ing</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New"> the</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> counting</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">before</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" FACE=3D"Courier New">receiving =
the positive feedback from Far End is</FONT></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" FACE=3D"Courier New">not interoperability =
issue.</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">M</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">aybe it can be a recommendation?</FONT></SPAN><SPAN LANG=3D"en-us"> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">But it is necessary for Source node =
to</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">a</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">bort</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> the effort after not receiving the positive =
feedback</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">after sometime (like X number of LM or timer =
expires).</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">3) I am not =
sure of the value of specifically calling out minimum/maximum intervals =
in the draft. Section 2.1 already describes how to calculate theoretical =
min/max values as a function of counter size, packet size &amp; =
link</FONT> <FONT FACE=3D"Courier New">speed, further restricting the =
set to specific numbers doesn't seem helpful.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">On 8 Jan =
2011, at 21:44, Greg Mirsky wrote:</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">[Linda]</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">I don't have strong feeling about =
specifying Min/Max intervals in the draft.</FONT></SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">B</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">ut it is very important to have the interval specified in the =
Message because Far End</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">need</FONT><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">s</FONT><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> to know in preparing for the counting, and there =
is a possibility that Far End</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">may not be able to support the =
interval initiated by the Querier.</FONT></SPAN><SPAN LANG=3D"en-us"> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">4) Giving =
the receiving end the opportunity to reply with &quot;I can;t support =
the rate you're asking for it's too fast for me&quot; sounds =
att</FONT><FONT FACE=3D"Courier New">ractive but I am not sure it is in =
practice if one thinks how such functionality is likely to be used. If =
an operator is going to turn it on with the thinking that performing LM =
of some sort is important regardless of the LM interval then negotiating =
a sh</FONT><FONT FACE=3D"Courier New">o</FONT><FONT FACE=3D"Courier =
New">rter interval may have value. However I don't expect that to be the =
case. I would expect an operator to pre-plan what interval they need =
given their knowledge of their network and the accuracy they desire, =
having the network change that may well cause une</FONT><FONT =
FACE=3D"Courier New">x</FONT><FONT FACE=3D"Courier New">pected =
consequences. In such a scenario I think it's better to let the receiver =
&quot;hard fail&quot; and the operator can investigate rather than have =
the network re-configure and the re-configuration go unnoticed, after =
all LM failing does not impact the ability</FONT> <FONT FACE=3D"Courier =
New">o</FONT><FONT FACE=3D"Courier New">f the network to actually =
forward packets.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">[Linda] Do you mean that Receiver can ignore the =
LMs if the Interval specified in</FONT></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" FACE=3D"Courier New">the</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">message is more than it can handle? =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">Ben</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Dear =
Linda,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; I =
think that specifying particular minimum interval might become too =
restrictive when higher bandwidth links become =
available.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Greg</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; On =
Fri, Jan 7, 2011 at 3:05 PM, Linda</FONT> <FONT FACE=3D"Courier =
New">Dunbar &lt;ldunbar@huawei.com&gt; wrote:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Dan,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Thank =
you very much for the reply.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; As for =
Section 4.1.1, may I suggest some wording changes (in =
blue)?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; When =
initiating an LM operation, the far end may require a period of time to =
become ready for th</FONT><FONT FACE=3D"Courier New">e requested =
measurement operation or the far end may not be able to support the =
requested measurement. During this period Under those circumstances, LM =
queries MAY simply be discarded, and the querier expecting a response =
SHOULD be prepared for this situa</FONT><FONT FACE=3D"Courier =
New">t</FONT><FONT FACE=3D"Courier New">ion, for example by stopping =
sending LMs after X (e.g. 3) number of LMs being sent without positive =
feedback. The initial LM interval before any response being received =
could be longer than normal to minimize the querier</FONT><FONT =
FACE=3D"Courier New">&#8217;</FONT><FONT FACE=3D"Courier New">s resource =
consumption. setting a</FONT> <FONT FACE=3D"Courier New">t</FONT><FONT =
FACE=3D"Courier New">imer to differentiate between an acceptable =
initialization delay and a permanent unavailability condition at the far =
end. Alternatively, the receiver MAY respond, possibly in a rate-limited =
manner, to queries received during this period with an =
appropriat</FONT><FONT FACE=3D"Courier New">e</FONT><FONT =
FACE=3D"Courier New"> notification code. Since counting transmitted =
packets at querier side will cost extra resources (or is not free), the =
querier should delay counting its transmitted packets until receiving a =
positive feedback from the far-end.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Another comment:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">&gt;</FONT><FONT FACE=3D"Courier New"> I think the document should =
add a description on the range of allowed LM/DM intervals. The shorter =
the interval, the higher the processing loads on line cards. Therefore, =
it is necessary to describe the minimum (and maximum) intervals for =
LM/DM in the dr</FONT><FONT FACE=3D"Courier New">a</FONT><FONT =
FACE=3D"Courier New">ft, and specifying the unit (like ms or second). =
IEEE802.ag specifies its CCM</FONT><FONT FACE=3D"Courier =
New">&#8217;</FONT><FONT FACE=3D"Courier New">s minimum interval to be =
3ms. To optimize the bits utilization, IEEE802.1Qbg uses 2x =
format.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Since =
the processing capability on the initiating node (the querier) and the =
far end (receiving) node could be different, the receiver (far end node) =
may indicate in the response a minimum interval it can support and the =
querier may adjust the LM interv</FONT><FONT FACE=3D"Courier =
New">a</FONT><FONT FACE=3D"Courier New">l to any desired value greater =
than that. Therefore, the interval value should be encoded in the LM/DM =
message.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; I =
suggest adding a section (e.g. 2.7.10) to describe the LM/DM interval =
and add a field in the message for interval.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Linda =
Dunbar</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">&gt;</FONT><FONT FACE=3D"Courier New"> </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
-----Original Message-----</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; From: =
Dan Frost [<A =
HREF=3D"mailto:danfrost@cisco.com">mailto:danfrost@cisco.com</A>]</FONT><=
/SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Sent: =
Friday, January 07, 2011 5:27 AM</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; To: =
Linda Dunbar</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Cc: =
mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Subject: Re: Questions on =
&quot;draft-ietf-mpls-loss-delay-00&quot;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Hi =
Linda,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; On =
Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar =
wrote:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Section 2 (Overview),</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; there are several references of measuring =
&quot;packets&quot; without</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
specifying if the packets are LM/DM packets or actual dat</FONT><FONT =
FACE=3D"Courier New">a plane packets.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Such Page 7 first paragraph: &quot; the count of packets received prior =
to time</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
T2 over the channel from A (B_RxP),&quot;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Is this the intent? So that LM can be used to =
either</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
measuring the LM losses and data plane loss?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Yes, =
this is intentional in the overview, because as the rest of =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
document makes clear, several options for what exactly to measure =
exist.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Section 2.7.1 Types of Channels:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It stated that LM =
and DM flow over MPLS G-Ach. Since packets</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
over G-Ach might encounter extra processing on intermediate nodes, the =
Delay</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
measured over G-Ach channel might be slightly different from the data =
plane</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
channel. Will i</FONT><FONT FACE=3D"Courier New">t be a =
problem?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; If a =
node is truly intermediate and not itself the target of =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
measurement operation, I see no reason why the packet would =
&quot;encounter</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; extra =
processing&quot; there, any more than any other packet =
label-switched</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
through the n</FONT><FONT FACE=3D"Courier New">ode.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Section 2.7.6. Loss Measurement Modes</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Under the &quot;direct mode&quot;, I interpret it as =
measuring the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
data plane packets, is it correct?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Yes.&nbsp; This is the meaning of the definition in the =
text:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">&gt;&nbsp;&nbsp;&nbsp; If the counted packets are the packets =
flowing over the channel in the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">&gt;&nbsp;&nbsp;&nbsp; data plane, the loss measurement is said to =
operate in &quot;direct mode&quot;.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Counting data plane packets can be process =
intensive.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Usually the each nod</FONT><FONT FACE=3D"Courier New">e (or line card) =
can only do actual packet counting for</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
limited number of LSPs. Therefore, I suggest allowing B node to ignore =
A</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
node's LM when B is not ready to do the counting or send back a reply =
to</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
indicate the &quot;not ready status&quot;.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
o&nbsp;&nbsp;&nbsp;&nbsp; Several options are possible for the =
negotiation: egress simply</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
ignore the request when it is not ready, egress sends back an error, =
etc.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Ingress node doesn't need to start counting traffic until it =
gets</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
confirmation from the egress node.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
Indeed, and the last paragraph of Section 4.1.1 says as much.&nbsp; This =
was</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; added =
as a result of our discussion.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Should allow options of either byte counter or packet =
counter.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; This =
is also in the tex</FONT><FONT FACE=3D"Courier New">t; see Section 1, =
the last paragraph of Section</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; 2.1, =
and the 'B' data format flag (DFlag) in Section 3.1.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Thank you very much.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; Thanks =
for your review!</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
-d</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; &gt; =
Linda Dunbar</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
_______________________________________________</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
mp</FONT><FONT FACE=3D"Courier New">ls mailing list</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
mpls@ietf.org</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; <A =
HREF=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</A></FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
_______________________________________________</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
mpls-tp mailing list</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
mpls-tp@ietf.org</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; <A =
HREF=3D"https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ietf.o=
rg/mailman/listinfo/mpls-tp</A></FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>=

--Boundary_(ID_Qo+4zvuSWR1RKSG7WSb6lg)--

From ldunbar@huawei.com  Mon Jan 10 08:28:13 2011
Return-Path: <ldunbar@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F165B3A6803; Mon, 10 Jan 2011 08:28:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.086
X-Spam-Level: 
X-Spam-Status: No, score=-106.086 tagged_above=-999 required=5 tests=[AWL=0.512, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9gbEU6SZkDmJ; Mon, 10 Jan 2011 08:28:04 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id AEEB13A67FA; Mon, 10 Jan 2011 08:28:04 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LET00CCLF6IWH@usaga02-in.huawei.com>; Mon, 10 Jan 2011 08:30:18 -0800 (PST)
Received: from L735042 ([10.124.12.121]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LET001ZHF6IE4@usaga02-in.huawei.com>; Mon, 10 Jan 2011 08:30:18 -0800 (PST)
Date: Mon, 10 Jan 2011 10:30:18 -0600
From: Linda Dunbar <ldunbar@huawei.com>
In-reply-to: <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com>
To: 'Greg Mirsky' <gregimirsky@gmail.com>
Message-id: <009a01cbb0e3$aafa0d50$790c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_P8AeheEXRLliOdtlqme/tw)"
Thread-index: AcuvfTcTlsihga7rS2KFE3ZunmNe1QBZjcFg
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com> <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com> <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com>
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 16:28:14 -0000

This is a multi-part message in MIME format.

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

Greg, 

 

Even though I don't have strong feeling about specifying the Min interval in
the draft, you will find that any interval less than 3ms is not realistic. 

 

Linda 

 

  _____  

From: Greg Mirsky [mailto:gregimirsky@gmail.com] 
Sent: Saturday, January 08, 2011 3:44 PM
To: Linda Dunbar
Cc: Dan Frost; mpls@ietf.org; Stewart Bryant; mpls-tp@ietf.org
Subject: Re: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"

 

Dear Linda,
I think that specifying particular minimum interval might become too
restrictive when higher bandwidth links become available.

Regards,
Greg

On Fri, Jan 7, 2011 at 3:05 PM, Linda Dunbar <ldunbar@huawei.com> wrote:

Dan, 

Thank you very much for the reply. 

As for Section 4.1.1, may I suggest some wording changes (in blue)? 

When initiating an LM operation, the far end may require a period of time to
become ready for the requested measurement operation or the far end may not
be able to support the requested measurement. During this period Under those
circumstances, LM queries MAY simply be discarded, and the querier expecting
a response SHOULD be prepared for this situation, for example by stopping
sending LMs after X (e.g. 3) number of LMs being sent without positive
feedback. The initial LM interval before any response being received could
be longer than normal to minimize the querier's resource consumption.
setting a timer to differentiate between an acceptable initialization delay
and a permanent unavailability condition at the far end. Alternatively, the
receiver MAY respond, possibly in a rate-limited manner, to queries received
during this period with an appropriate notification code. Since counting
transmitted packets at querier side will cost extra resources (or is not
free), the querier should delay counting its transmitted packets until
receiving a positive feedback from the far-end. 

Another comment: 

I think the document should add a description on the range of allowed LM/DM
intervals. The shorter the interval, the higher the processing loads on line
cards. Therefore, it is necessary to describe the minimum (and maximum)
intervals for LM/DM in the draft, and specifying the unit (like ms or
second). IEEE802.ag specifies its CCM's minimum interval to be 3ms. To
optimize the bits utilization, IEEE802.1Qbg uses 2x format. 

Since the processing capability on the initiating node (the querier) and the
far end (receiving) node could be different, the receiver (far end node) may
indicate in the response a minimum interval it can support and the querier
may adjust the LM interval to any desired value greater than that.
Therefore, the interval value should be encoded in the LM/DM message. 

I suggest adding a section (e.g. 2.7.10) to describe the LM/DM interval and
add a field in the message for interval. 

Linda Dunbar

-----Original Message-----
From: Dan Frost [mailto:danfrost@cisco.com]
Sent: Friday, January 07, 2011 5:27 AM
To: Linda Dunbar
Cc: mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'
Subject: Re: Questions on "draft-ietf-mpls-loss-delay-00"

Hi Linda,

On Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:

> Section 2 (Overview), 

>               there are several references of measuring "packets" without

> specifying if the packets are LM/DM packets or actual data plane packets.

> Such Page 7 first paragraph: " the count of packets received prior to time

> T2 over the channel from A (B_RxP),"

> 

>               Is this the intent? So that LM can be used to either

> measuring the LM losses and data plane loss? 

Yes, this is intentional in the overview, because as the rest of the

document makes clear, several options for what exactly to measure exist.

> Section 2.7.1 Types of Channels: 

>               It stated that LM and DM flow over MPLS G-Ach. Since packets

> over G-Ach might encounter extra processing on intermediate nodes, the
Delay

> measured over G-Ach channel might be slightly different from the data
plane

> channel. Will it be a problem? 

If a node is truly intermediate and not itself the target of the

measurement operation, I see no reason why the packet would "encounter

extra processing" there, any more than any other packet label-switched

through the node.

> Section 2.7.6. Loss Measurement Modes

>               Under the "direct mode", I interpret it as measuring the

> data plane packets, is it correct? 

Yes.  This is the meaning of the definition in the text:

   If the counted packets are the packets flowing over the channel in the

   data plane, the loss measurement is said to operate in "direct mode".

>               Counting data plane packets can be process intensive.

> Usually the each node (or line card) can only do actual packet counting
for

> limited number of LSPs. Therefore, I suggest allowing B node to ignore A

> node's LM when B is not ready to do the counting or send back a reply to

> indicate the "not ready status". 

> 

> o     Several options are possible for the negotiation: egress simply

> ignore the request when it is not ready, egress sends back an error, etc.

> Ingress node doesn't need to start counting traffic until it gets

> confirmation from the egress node. 

Indeed, and the last paragraph of Section 4.1.1 says as much.  This was

added as a result of our discussion.

> Should allow options of either byte counter or packet counter. 

This is also in the text; see Section 1, the last paragraph of Section

2.1, and the 'B' data format flag (DFlag) in Section 3.1.

> Thank you very much. 

Thanks for your review!

-d

> Linda Dunbar


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

 


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

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:244844521;
	mso-list-template-ids:1131994112;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1
	{mso-list-id:981426505;
	mso-list-template-ids:-642635648;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=blue>

<div class=Section1>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'>Greg, <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'>Even though I don&#8217;t have strong feeling
about specifying the Min interval in the draft, you will find that any interval
less than 3ms is not realistic. <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'>Linda <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=MsoNormal align=center style='margin-left:.5in;text-align:center'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>

<hr size=2 width="100%" align=center tabindex=-1>

</span></font></div>

<p class=MsoNormal style='margin-left:.5in'><b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Greg
Mirsky [mailto:gregimirsky@gmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Saturday, January 08, 2011
3:44 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Linda Dunbar<br>
<b><span style='font-weight:bold'>Cc:</span></b> Dan Frost; mpls@ietf.org;
Stewart Bryant; mpls-tp@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [mpls] Questions on
&quot;draft-ietf-mpls-loss-delay-00&quot;</span></font><o:p></o:p></p>

</div>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>Dear Linda,<br>
I think that specifying particular minimum interval might become too
restrictive when higher bandwidth links become available.<br>
<br>
Regards,<br>
Greg<o:p></o:p></span></font></p>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>On Fri, Jan 7, 2011 at 3:05 PM, Linda Dunbar &lt;<a
href="mailto:ldunbar@huawei.com">ldunbar@huawei.com</a>&gt; wrote:<o:p></o:p></span></font></p>

<div>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Dan, </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Thank</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>you very</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>much for the
reply.</span></font> <o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>As for Section 4.1.1,</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>may I suggest
some wording changes (in blue)? </span></font><o:p></o:p></p>

<p style='margin-left:2.5in'><font size=2 face=Courier><span style='font-size:
10.0pt;font-family:Courier'>When initiating an LM operation,</span></font> <font
size=2 face=Courier><span style='font-size:10.0pt;font-family:Courier'>the far
end may require a period of time to become ready for the requested measurement
operation</span></font> <font size=2 color=blue face=Courier><span
style='font-size:10.0pt;font-family:Courier;color:blue'>or the far end may not
be able to support the requested measurement</span></font><font size=2
face=Courier><span style='font-size:10.0pt;font-family:Courier'>.</span></font><s>
</s><s><font size=2 face=Courier><span style='font-size:10.0pt;font-family:
Courier'>During this period</span></font></s> <font size=2 color=blue
face=Courier><span style='font-size:10.0pt;font-family:Courier;color:blue'>Under
those circumstances</span></font><font size=2 face=Courier><span
style='font-size:10.0pt;font-family:Courier'>, LM queries MAY simply be
discarded, and the</span></font> <font size=2 face=Courier><span
style='font-size:10.0pt;font-family:Courier'>querier expecting a response
SHOULD be prepared for this situation, for example by</span></font> <font
size=2 color=blue face=Courier><span style='font-size:10.0pt;font-family:Courier;
color:blue'>stopping sending LMs after X (e.g. 3) number of LMs being sent
without positive feedback.</span></font> <font size=2 color=blue face=Courier><span
style='font-size:10.0pt;font-family:Courier;color:blue'>The</span></font> <font
size=2 color=blue face=Courier><span style='font-size:10.0pt;font-family:Courier;
color:blue'>initial</span></font> <font size=2 color=blue face=Courier><span
style='font-size:10.0pt;font-family:Courier;color:blue'>LM interval</span></font>
<font size=2 color=blue face=Courier><span style='font-size:10.0pt;font-family:
Courier;color:blue'>before any response</span></font> <font size=2 color=blue
face=Courier><span style='font-size:10.0pt;font-family:Courier;color:blue'>being</span></font>
<font size=2 color=blue face=Courier><span style='font-size:10.0pt;font-family:
Courier;color:blue'>received could be longer than normal to minimize the
querier&#8217;s resource consumption.</span></font><s> </s><s><font size=2
face=Courier><span style='font-size:10.0pt;font-family:Courier'>setting a timer
to differentiate between an acceptable initialization delay and a permanent
unavailability condition at the far end</span></font></s><font size=2
color=blue face=Courier><span style='font-size:10.0pt;font-family:Courier;
color:blue'>.</span></font><font size=2 face=Courier><span style='font-size:
10.0pt;font-family:Courier'> Alternatively, the receiver MAY respond, possibly
in a rate-limited manner, to queries received during this period with an
appropriate notification code.<font color=blue><span style='color:blue'> Since
counting transmitted packets at querier side will cost extra resources (or is
not free), the querier</span></font></span></font> <font size=2 color=blue
face=Courier><span style='font-size:10.0pt;font-family:Courier;color:blue'>should</span></font>
<font size=2 color=blue face=Courier><span style='font-size:10.0pt;font-family:
Courier;color:blue'>delay counting its transmitted packets</span></font> <font
size=2 color=blue face=Courier><span style='font-size:10.0pt;font-family:Courier;
color:blue'>until receiving a positive feedback from the far-end. </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Another comment: </span></font><o:p></o:p></p>

<p style='margin-left:1.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>I think the document should</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>add a
description on the range of allowed</span></font> <font face="Courier New"><span
style='font-family:"Courier New"'>LM/DM</span></font> <font face="Courier New"><span
style='font-family:"Courier New"'>intervals.</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>The</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>shorter the</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>interval, the
higher</span></font> <font face="Courier New"><span style='font-family:"Courier New"'>the
processing loads on line cards.</span></font> <font face="Courier New"><span
style='font-family:"Courier New"'>Therefore,</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>it is necessary to
describe</span></font> <font face="Courier New"><span style='font-family:"Courier New"'>the</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>minimum</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>(and maximum)
intervals for LM/DM in the draft,</span></font> <font face="Courier New"><span
style='font-family:"Courier New"'>and specifying the unit (like ms or second).</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>IEEE8<a
href="http://02.ag" target="_blank">02.ag</a> specifies its</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>CCM&#8217;s</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>minimum interval</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>to be 3ms. To
optimize the bits utilization, IEEE802.1Qbg uses 2<sup>x</sup></span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>format.</span></font>
<o:p></o:p></p>

<p style='margin-left:1.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Since the</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>processing
capability on the</span></font> <font face="Courier New"><span
style='font-family:"Courier New"'>initiating node (the querier) and the far end
(receiving) node could be different,</span></font> <font face="Courier New"><span
style='font-family:"Courier New"'>the receiver (far end node) may indicate in
the response a minimum interval it can support and the</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>querier may adjust
the LM interval to any desired value greater than that.</span></font> <font
face="Courier New"><span style='font-family:"Courier New"'>Therefore,</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>the interval</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>value</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>should be
encoded in the LM/DM message.</span></font> <o:p></o:p></p>

<p style='margin-left:1.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>I suggest adding a section</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>(e.g.</span></font>
<font face="Courier New"><span style='font-family:"Courier New"'>2.7.10) to
describe the LM/DM interval and add a field in the message for interval.</span></font>
<o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Linda Dunbar</span></font><o:p></o:p></p>

<div>

<div>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>-----Original Message-----<br>
From: Dan Frost [<a href="mailto:danfrost@cisco.com" target="_blank">mailto:danfrost@cisco.com</a>]<br>
Sent: Friday, January 07, 2011 5:27 AM<br>
To: Linda Dunbar<br>
Cc: <a href="mailto:mpls-tp@ietf.org" target="_blank">mpls-tp@ietf.org</a>; <a
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>; 'Stewart Bryant'<br>
Subject: Re: Questions on &quot;draft-ietf-mpls-loss-delay-00&quot;</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Hi Linda,</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>On Thu, Jan 06, 2011 at
05:21:09PM -0600, Linda Dunbar wrote:</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Section 2 (Overview), </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; there
are several references of measuring &quot;packets&quot; without</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; specifying if the
packets are LM/DM packets or actual data plane packets.</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Such Page 7 first
paragraph: &quot; the count of packets received prior to time</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; T2 over the channel
from A (B_RxP),&quot;</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is
this the intent? So that LM can be used to either</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; measuring the LM losses
and data plane loss? </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Yes, this is intentional in
the overview, because as the rest of the</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>document makes clear,
several options for what exactly to measure exist.</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Section 2.7.1 Types of
Channels: </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It
stated that LM and DM flow over MPLS G-Ach. Since packets</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; over G-Ach might
encounter extra processing on intermediate nodes, the Delay</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; measured over G-Ach
channel might be slightly different from the data plane</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; channel. Will it be a
problem? </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>If a node is truly
intermediate and not itself the target of the</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>measurement operation, I see
no reason why the packet would &quot;encounter</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>extra processing&quot;
there, any more than any other packet label-switched</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>through the node.</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Section 2.7.6. Loss
Measurement Modes</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Under
the &quot;direct mode&quot;, I interpret it as measuring the</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; data plane packets, is
it correct? </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Yes.&nbsp; This is the
meaning of the definition in the text:</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&nbsp;&nbsp; If the counted
packets are the packets flowing over the channel in the</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&nbsp;&nbsp; data plane, the
loss measurement is said to operate in &quot;direct mode&quot;.</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Counting data plane packets can be process intensive.</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Usually the each node
(or line card) can only do actual packet counting for</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; limited number of LSPs.
Therefore, I suggest allowing B node to ignore A</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; node's LM when B is not
ready to do the counting or send back a reply to</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; indicate the &quot;not
ready status&quot;. </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt;
o&nbsp;&nbsp;&nbsp;&nbsp; Several options are possible for the negotiation:
egress simply</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; ignore the request when
it is not ready, egress sends back an error, etc.</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Ingress node doesn't
need to start counting traffic until it gets</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; confirmation from the
egress node. </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Indeed, and the last
paragraph of Section 4.1.1 says as much.&nbsp; This was</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>added as a result of our
discussion.</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Should allow options of
either byte counter or packet counter. </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>This is also in the text;
see Section 1, the last paragraph of Section</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>2.1, and the 'B' data format
flag (DFlag) in Section 3.1.</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Thank you very much. </span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>Thanks for your review!</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>-d</span></font><o:p></o:p></p>

<p style='margin-left:.5in'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'>&gt; Linda Dunbar</span></font><o:p></o:p></p>

</div>

</div>

</div>

<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><br>
_______________________________________________<br>
mpls mailing list<br>
<a href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/mpls" target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></font></p>

</div>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_P8AeheEXRLliOdtlqme/tw)--

From eosborne@cisco.com  Mon Jan 10 08:34:22 2011
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57E6E3A680B; Mon, 10 Jan 2011 08:34:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.469
X-Spam-Level: 
X-Spam-Status: No, score=-10.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUCK0KDfzqag; Mon, 10 Jan 2011 08:34:21 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id C0E7F3A67FA; Mon, 10 Jan 2011 08:34:20 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALbEKk2tJV2a/2dsb2JhbACkR3OjK5dwhUwEhGeJSYJw
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-2.cisco.com with ESMTP; 10 Jan 2011 16:36:34 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p0AGaYMS009670;  Mon, 10 Jan 2011 16:36:34 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 10 Jan 2011 10:36:34 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 Jan 2011 10:36:32 -0600
Message-ID: <D29E470202D67745B61059870F433B5403F778FF@XMB-RCD-202.cisco.com>
In-Reply-To: <009a01cbb0e3$aafa0d50$790c7c0a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
Thread-Index: AcuvfTcTlsihga7rS2KFE3ZunmNe1QBZjcFgAAAfUEA=
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com><20110107112641.GA20790@cisco.com><014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com><AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com> <009a01cbb0e3$aafa0d50$790c7c0a@china.huawei.com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Linda Dunbar" <ldunbar@huawei.com>, "Greg Mirsky" <gregimirsky@gmail.com>
X-OriginalArrivalTime: 10 Jan 2011 16:36:34.0194 (UTC) FILETIME=[8B0A6F20:01CBB0E4]
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 16:34:22 -0000

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
> Linda Dunbar
> Sent: Monday, January 10, 2011 11:30 AM
> To: 'Greg Mirsky'
> Cc: mpls@ietf.org; mpls-tp@ietf.org; Stewart Bryant (stbryant)
> Subject: Re: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
>=20
> Greg,
>=20
>=20
>=20
> Even though I don't have strong feeling about specifying the Min
interval
> in the draft, you will find that any interval less than 3ms is not
> realistic.
>=20

I don't have particular feelings about this draft, but I've discovered
the one of the things I'm particularly bad at is deciding what operators
will never, ever want to do at some point in the future.  If you want to
declare minimum and maximum ranges, I think it's always best practice to
say something like "an implement SHOULD support an interval range from
<bottom> to <top>" - this leaves room for implementations to both exceed
the spec if desired and to do something other than what's specified if
there is a good reason to.





eric


>=20
>=20
> Linda
>=20
>=20
>=20
> ________________________________
>=20
> From: Greg Mirsky [mailto:gregimirsky@gmail.com]
> Sent: Saturday, January 08, 2011 3:44 PM
> To: Linda Dunbar
> Cc: Dan Frost; mpls@ietf.org; Stewart Bryant; mpls-tp@ietf.org
> Subject: Re: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
>=20
>=20
>=20
> Dear Linda,
> I think that specifying particular minimum interval might become too
> restrictive when higher bandwidth links become available.
>=20
> Regards,
> Greg
>=20
> On Fri, Jan 7, 2011 at 3:05 PM, Linda Dunbar <ldunbar@huawei.com>
wrote:
>=20
> Dan,
>=20
> Thank you very much for the reply.
>=20
> As for Section 4.1.1, may I suggest some wording changes (in blue)?
>=20
> When initiating an LM operation, the far end may require a period of
time
> to become ready for the requested measurement operation or the far end
may
> not be able to support the requested measurement. During this period
Under
> those circumstances, LM queries MAY simply be discarded, and the
querier
> expecting a response SHOULD be prepared for this situation, for
example by
> stopping sending LMs after X (e.g. 3) number of LMs being sent without
> positive feedback. The initial LM interval before any response being
> received could be longer than normal to minimize the querier's
resource
> consumption. setting a timer to differentiate between an acceptable
> initialization delay and a permanent unavailability condition at the
far
> end. Alternatively, the receiver MAY respond, possibly in a
rate-limited
> manner, to queries received during this period with an appropriate
> notification code. Since counting transmitted packets at querier side
will
> cost extra resources (or is not free), the querier should delay
counting
> its transmitted packets until receiving a positive feedback from the
far-
> end.
>=20
> Another comment:
>=20
> I think the document should add a description on the range of allowed
> LM/DM intervals. The shorter the interval, the higher the processing
loads
> on line cards. Therefore, it is necessary to describe the minimum (and
> maximum) intervals for LM/DM in the draft, and specifying the unit
(like
> ms or second). IEEE802.ag specifies its CCM's minimum interval to be
3ms.
> To optimize the bits utilization, IEEE802.1Qbg uses 2x format.
>=20
> Since the processing capability on the initiating node (the querier)
and
> the far end (receiving) node could be different, the receiver (far end
> node) may indicate in the response a minimum interval it can support
and
> the querier may adjust the LM interval to any desired value greater
than
> that. Therefore, the interval value should be encoded in the LM/DM
> message.
>=20
> I suggest adding a section (e.g. 2.7.10) to describe the LM/DM
interval
> and add a field in the message for interval.
>=20
> Linda Dunbar
>=20
> -----Original Message-----
> From: Dan Frost [mailto:danfrost@cisco.com]
> Sent: Friday, January 07, 2011 5:27 AM
> To: Linda Dunbar
> Cc: mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'
> Subject: Re: Questions on "draft-ietf-mpls-loss-delay-00"
>=20
> Hi Linda,
>=20
> On Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:
>=20
> > Section 2 (Overview),
>=20
> >               there are several references of measuring "packets"
> without
>=20
> > specifying if the packets are LM/DM packets or actual data plane
> packets.
>=20
> > Such Page 7 first paragraph: " the count of packets received prior
to
> time
>=20
> > T2 over the channel from A (B_RxP),"
>=20
> >
>=20
> >               Is this the intent? So that LM can be used to either
>=20
> > measuring the LM losses and data plane loss?
>=20
> Yes, this is intentional in the overview, because as the rest of the
>=20
> document makes clear, several options for what exactly to measure
exist.
>=20
> > Section 2.7.1 Types of Channels:
>=20
> >               It stated that LM and DM flow over MPLS G-Ach. Since
> packets
>=20
> > over G-Ach might encounter extra processing on intermediate nodes,
the
> Delay
>=20
> > measured over G-Ach channel might be slightly different from the
data
> plane
>=20
> > channel. Will it be a problem?
>=20
> If a node is truly intermediate and not itself the target of the
>=20
> measurement operation, I see no reason why the packet would "encounter
>=20
> extra processing" there, any more than any other packet label-switched
>=20
> through the node.
>=20
> > Section 2.7.6. Loss Measurement Modes
>=20
> >               Under the "direct mode", I interpret it as measuring
the
>=20
> > data plane packets, is it correct?
>=20
> Yes.  This is the meaning of the definition in the text:
>=20
>    If the counted packets are the packets flowing over the channel in
the
>=20
>    data plane, the loss measurement is said to operate in "direct
mode".
>=20
> >               Counting data plane packets can be process intensive.
>=20
> > Usually the each node (or line card) can only do actual packet
counting
> for
>=20
> > limited number of LSPs. Therefore, I suggest allowing B node to
ignore A
>=20
> > node's LM when B is not ready to do the counting or send back a
reply to
>=20
> > indicate the "not ready status".
>=20
> >
>=20
> > o     Several options are possible for the negotiation: egress
simply
>=20
> > ignore the request when it is not ready, egress sends back an error,
> etc.
>=20
> > Ingress node doesn't need to start counting traffic until it gets
>=20
> > confirmation from the egress node.
>=20
> Indeed, and the last paragraph of Section 4.1.1 says as much.  This
was
>=20
> added as a result of our discussion.
>=20
> > Should allow options of either byte counter or packet counter.
>=20
> This is also in the text; see Section 1, the last paragraph of Section
>=20
> 2.1, and the 'B' data format flag (DFlag) in Section 3.1.
>=20
> > Thank you very much.
>=20
> Thanks for your review!
>=20
> -d
>=20
> > Linda Dunbar
>=20
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20
>=20


From ben@niven-jenkins.co.uk  Mon Jan 10 09:26:49 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F6DF3A681F; Mon, 10 Jan 2011 09:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.621
X-Spam-Level: 
X-Spam-Status: No, score=-102.621 tagged_above=-999 required=5 tests=[AWL=-0.622, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id db0yQvr51vqp; Mon, 10 Jan 2011 09:26:48 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by core3.amsl.com (Postfix) with ESMTP id B309A3A681A; Mon, 10 Jan 2011 09:26:47 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-122-devlan.cachelogic.com) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1PcLYC-0003qn-I5; Mon, 10 Jan 2011 17:29:00 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <009501cbb0e3$665cbe90$790c7c0a@china.huawei.com>
Date: Mon, 10 Jan 2011 17:29:00 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <48AA81F4-C02E-48F5-95BF-0159CFAB682C@niven-jenkins.co.uk>
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com> <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com> <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com> <9BCECFE9-04D8-4E8F-A01A-55D76C0E64C9@niven-jenkins.co.uk> <009501cbb0e3$665cbe90$790c7c0a@china.huawei.com>
To: Linda Dunbar <ldunbar@huawei.com>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: mpls-tp@ietf.org, mpls@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 17:26:49 -0000

Linda,

On 10 Jan 2011, at 16:28, Linda Dunbar wrote:
> From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk]
>=20
> 1) The edits suggested by Linda change the semantics from suggesting a =
querier maintain a timer to allow for the receiving end to "get its act =
together" to if the receiving end doesn't get its act together within X =
packets stop sending LM. Is that really what's intended? I would expect =
the time taken for the receiving end "to get its act together" would not =
be a function of the LM transmission rate and therefore using =
transmission rate to guess whether the receiving end is dead Vs getting =
itself ready doesn't sound sensible.
>=20
>=20
> [Linda] The reason for suggesting Initiator to have slower =
transmission rate is to minimize processing needed at the Initiator =
before Far End committing to the counting.
>=20

But you suggest edit does not suggest a slower transmission rate it =
states the querier should stop transmission!

> We have considered implementing this feature on our products and =
discovered that it DOES take some time for the Central CPU to receive =
the Counting Request (as LM in this draft), check if the requested =
Counting can be supported, pass the request to the corresponding line =
card, and get confirmation from the Line card. Sometimes, the Far End =
can't perform the requested Counting because it is performing counting =
for requests from other nodes.
>=20

I accept that a receiver may take some time to configure itself for =
counting and that the time it takes may be a function of other things it =
is doing. What I am saying is that the time it takes is never a function =
of the interval being configured.

> 2) I don't like the final sentence suggesting queriers should delay =
counting transmitted packets until receiving a positive response because =
doing so costs resources. It sounds like an internal implementation =
decision that has nothing to do with interoperability and therefore =
irrelevant.
>=20
>=20
> [Linda]I agree with your point that that the Source Node performing or =
not performing the counting before receiving the positive feedback from =
Far End is not interoperability issue. Maybe it can be a recommendation?
>=20
> But it is necessary for Source node to abort the effort after not =
receiving the positive feedback after sometime (like X number of LM or =
timer expires).
>=20

At some point, if the querier has not received a positive response it =
must abort the operation. The original text suggest maintaing a timer. =
Your edit suggested making ti a function of packets sent. I am saying =
the former seems more sensible than the latter to me.

> 4) Giving the receiving end the opportunity to reply with "I can;t =
support the rate you're asking for it's too fast for me" sounds =
attractive but I am not sure it is in practice if one thinks how such =
functionality is likely to be used. If an operator is going to turn it =
on with the thinking that performing LM of some sort is important =
regardless of the LM interval then negotiating a shorter interval may =
have value. However I don't expect that to be the case. I would expect =
an operator to pre-plan what interval they need given their knowledge of =
their network and the accuracy they desire, having the network change =
that may well cause unexpected consequences. In such a scenario I think =
it's better to let the receiver "hard fail" and the operator can =
investigate rather than have the network re-configure and the =
re-configuration go unnoticed, after all LM failing does not impact the =
ability of the network to actually forward packets.
>=20
>=20
> [Linda] Do you mean that Receiver can ignore the LMs if the Interval =
specified in the message is more than it can handle?

That is one option.

The background to my thinking is:

I assume that LM will be turned on explicitly (i.e. it will not be on by =
default)
I assume that LM is turned on for a reason, e.g. because an operator =
needs to support an SLA involving packet loss.
The interval may affect the accuracy of the packet loss count.
I expect operators would rather LM "hard fail" rather than have the =
network re-configure automatically to a different interval because an =
SLA calculation (or whatever else is relying on the LM) could become =
inaccurate and no-one would know unless they really dug deep into what =
the network was doing.

The network re-configuring itself in order to repair itself so it can =
continue to forward packets is one thing.

The network reconfiguring non-forwarding related features itself because =
it believes it knows what to do better than the person who designed & =
configured it could lead to all sorts of trouble in the field IMO.

Ben

=20


From ldunbar@huawei.com  Tue Jan 11 07:36:44 2011
Return-Path: <ldunbar@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B82F53A6809; Tue, 11 Jan 2011 07:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.113
X-Spam-Level: 
X-Spam-Status: No, score=-106.113 tagged_above=-999 required=5 tests=[AWL=0.486, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vENr7tbxR04F; Tue, 11 Jan 2011 07:36:43 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 58C2E3A67A8; Tue, 11 Jan 2011 07:36:43 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEV001A67GZBZ@usaga02-in.huawei.com>; Tue, 11 Jan 2011 07:39:00 -0800 (PST)
Received: from L735042 ([10.124.12.121]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LEV00I547GZ4O@usaga02-in.huawei.com>; Tue, 11 Jan 2011 07:38:59 -0800 (PST)
Date: Tue, 11 Jan 2011 09:38:59 -0600
From: Linda Dunbar <ldunbar@huawei.com>
In-reply-to: <D29E470202D67745B61059870F433B5403F778FF@XMB-RCD-202.cisco.com>
To: "'Eric Osborne (eosborne)'" <eosborne@cisco.com>, 'Greg Mirsky' <gregimirsky@gmail.com>
Message-id: <004701cbb1a5$aa47e630$790c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcuvfTcTlsihga7rS2KFE3ZunmNe1QBZjcFgAAAfUEAAMF7hAA==
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com> <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com> <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com> <009a01cbb0e3$aafa0d50$790c7c0a@china.huawei.com> <D29E470202D67745B61059870F433B5403F778FF@XMB-RCD-202.cisco.com>
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 15:36:44 -0000

Eric, 

That is a good suggestion. 
Linda 

-----Original Message-----
From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com] 
Sent: Monday, January 10, 2011 10:37 AM
To: Linda Dunbar; Greg Mirsky
Cc: mpls@ietf.org; mpls-tp@ietf.org; Stewart Bryant (stbryant)
Subject: RE: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"



> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
> Linda Dunbar
> Sent: Monday, January 10, 2011 11:30 AM
> To: 'Greg Mirsky'
> Cc: mpls@ietf.org; mpls-tp@ietf.org; Stewart Bryant (stbryant)
> Subject: Re: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
> 
> Greg,
> 
> 
> 
> Even though I don't have strong feeling about specifying the Min
interval
> in the draft, you will find that any interval less than 3ms is not
> realistic.
> 

I don't have particular feelings about this draft, but I've discovered
the one of the things I'm particularly bad at is deciding what operators
will never, ever want to do at some point in the future.  If you want to
declare minimum and maximum ranges, I think it's always best practice to
say something like "an implement SHOULD support an interval range from
<bottom> to <top>" - this leaves room for implementations to both exceed
the spec if desired and to do something other than what's specified if
there is a good reason to.





eric


> 
> 
> Linda
> 
> 
> 
> ________________________________
> 
> From: Greg Mirsky [mailto:gregimirsky@gmail.com]
> Sent: Saturday, January 08, 2011 3:44 PM
> To: Linda Dunbar
> Cc: Dan Frost; mpls@ietf.org; Stewart Bryant; mpls-tp@ietf.org
> Subject: Re: [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
> 
> 
> 
> Dear Linda,
> I think that specifying particular minimum interval might become too
> restrictive when higher bandwidth links become available.
> 
> Regards,
> Greg
> 
> On Fri, Jan 7, 2011 at 3:05 PM, Linda Dunbar <ldunbar@huawei.com>
wrote:
> 
> Dan,
> 
> Thank you very much for the reply.
> 
> As for Section 4.1.1, may I suggest some wording changes (in blue)?
> 
> When initiating an LM operation, the far end may require a period of
time
> to become ready for the requested measurement operation or the far end
may
> not be able to support the requested measurement. During this period
Under
> those circumstances, LM queries MAY simply be discarded, and the
querier
> expecting a response SHOULD be prepared for this situation, for
example by
> stopping sending LMs after X (e.g. 3) number of LMs being sent without
> positive feedback. The initial LM interval before any response being
> received could be longer than normal to minimize the querier's
resource
> consumption. setting a timer to differentiate between an acceptable
> initialization delay and a permanent unavailability condition at the
far
> end. Alternatively, the receiver MAY respond, possibly in a
rate-limited
> manner, to queries received during this period with an appropriate
> notification code. Since counting transmitted packets at querier side
will
> cost extra resources (or is not free), the querier should delay
counting
> its transmitted packets until receiving a positive feedback from the
far-
> end.
> 
> Another comment:
> 
> I think the document should add a description on the range of allowed
> LM/DM intervals. The shorter the interval, the higher the processing
loads
> on line cards. Therefore, it is necessary to describe the minimum (and
> maximum) intervals for LM/DM in the draft, and specifying the unit
(like
> ms or second). IEEE802.ag specifies its CCM's minimum interval to be
3ms.
> To optimize the bits utilization, IEEE802.1Qbg uses 2x format.
> 
> Since the processing capability on the initiating node (the querier)
and
> the far end (receiving) node could be different, the receiver (far end
> node) may indicate in the response a minimum interval it can support
and
> the querier may adjust the LM interval to any desired value greater
than
> that. Therefore, the interval value should be encoded in the LM/DM
> message.
> 
> I suggest adding a section (e.g. 2.7.10) to describe the LM/DM
interval
> and add a field in the message for interval.
> 
> Linda Dunbar
> 
> -----Original Message-----
> From: Dan Frost [mailto:danfrost@cisco.com]
> Sent: Friday, January 07, 2011 5:27 AM
> To: Linda Dunbar
> Cc: mpls-tp@ietf.org; mpls@ietf.org; 'Stewart Bryant'
> Subject: Re: Questions on "draft-ietf-mpls-loss-delay-00"
> 
> Hi Linda,
> 
> On Thu, Jan 06, 2011 at 05:21:09PM -0600, Linda Dunbar wrote:
> 
> > Section 2 (Overview),
> 
> >               there are several references of measuring "packets"
> without
> 
> > specifying if the packets are LM/DM packets or actual data plane
> packets.
> 
> > Such Page 7 first paragraph: " the count of packets received prior
to
> time
> 
> > T2 over the channel from A (B_RxP),"
> 
> >
> 
> >               Is this the intent? So that LM can be used to either
> 
> > measuring the LM losses and data plane loss?
> 
> Yes, this is intentional in the overview, because as the rest of the
> 
> document makes clear, several options for what exactly to measure
exist.
> 
> > Section 2.7.1 Types of Channels:
> 
> >               It stated that LM and DM flow over MPLS G-Ach. Since
> packets
> 
> > over G-Ach might encounter extra processing on intermediate nodes,
the
> Delay
> 
> > measured over G-Ach channel might be slightly different from the
data
> plane
> 
> > channel. Will it be a problem?
> 
> If a node is truly intermediate and not itself the target of the
> 
> measurement operation, I see no reason why the packet would "encounter
> 
> extra processing" there, any more than any other packet label-switched
> 
> through the node.
> 
> > Section 2.7.6. Loss Measurement Modes
> 
> >               Under the "direct mode", I interpret it as measuring
the
> 
> > data plane packets, is it correct?
> 
> Yes.  This is the meaning of the definition in the text:
> 
>    If the counted packets are the packets flowing over the channel in
the
> 
>    data plane, the loss measurement is said to operate in "direct
mode".
> 
> >               Counting data plane packets can be process intensive.
> 
> > Usually the each node (or line card) can only do actual packet
counting
> for
> 
> > limited number of LSPs. Therefore, I suggest allowing B node to
ignore A
> 
> > node's LM when B is not ready to do the counting or send back a
reply to
> 
> > indicate the "not ready status".
> 
> >
> 
> > o     Several options are possible for the negotiation: egress
simply
> 
> > ignore the request when it is not ready, egress sends back an error,
> etc.
> 
> > Ingress node doesn't need to start counting traffic until it gets
> 
> > confirmation from the egress node.
> 
> Indeed, and the last paragraph of Section 4.1.1 says as much.  This
was
> 
> added as a result of our discussion.
> 
> > Should allow options of either byte counter or packet counter.
> 
> This is also in the text; see Section 1, the last paragraph of Section
> 
> 2.1, and the 'B' data format flag (DFlag) in Section 3.1.
> 
> > Thank you very much.
> 
> Thanks for your review!
> 
> -d
> 
> > Linda Dunbar
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
> 



From ldunbar@huawei.com  Tue Jan 11 11:53:44 2011
Return-Path: <ldunbar@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B46CC3A67D2; Tue, 11 Jan 2011 11:53:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.837
X-Spam-Level: 
X-Spam-Status: No, score=-105.837 tagged_above=-999 required=5 tests=[AWL=0.161, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXy6uf3e1xjv; Tue, 11 Jan 2011 11:53:35 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id C06E63A6AA0; Tue, 11 Jan 2011 11:53:35 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEV00MA8JD4RH@usaga02-in.huawei.com>; Tue, 11 Jan 2011 11:55:53 -0800 (PST)
Received: from L735042 ([10.124.12.121]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LEV0084QJD3QI@usaga02-in.huawei.com>; Tue, 11 Jan 2011 11:55:52 -0800 (PST)
Date: Tue, 11 Jan 2011 13:55:51 -0600
From: Linda Dunbar <ldunbar@huawei.com>
In-reply-to: <48AA81F4-C02E-48F5-95BF-0159CFAB682C@niven-jenkins.co.uk>
To: 'Ben Niven-Jenkins' <ben@niven-jenkins.co.uk>
Message-id: <00bc01cbb1c9$8ceac4d0$790c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_aiZ8cClfPmqLJcHkHVMzAA)"
Thread-index: Acuw7A+P5Ld48maVS9u8IMoWvmCnMQAzrYbg
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com> <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com> <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com> <9BCECFE9-04D8-4E8F-A01A-55D76C0E64C9@niven-jenkins.co.uk> <009501cbb0e3$665cbe90$790c7c0a@china.huawei.com> <48AA81F4-C02E-48F5-95BF-0159CFAB682C@niven-jenkins.co.uk>
Cc: mpls-tp@ietf.org, mpls@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 19:53:44 -0000

This is a multi-part message in MIME format.

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

Ben and colleagues: 

You said " But you suggest edit does not suggest a slower transmission rate
it states the querier should stop transmission", 

Two comments: 
1.	I think "slower transmission rate by querier" should be included in
the text. 
2.	I suggested that querier may choose not starting counting (not
transmission) until a positive feedback from Far End has been received. 

Based on the discussion over this email thread, do people think the
following text is more appropriate? 


		When initiating an LM operation, the far end may require a
period of time to become ready for the requested measurement operation or
the far end may not be able to support the requested measurement. During
this period Under those circumstances, LM queries MAY simply be discarded,
and the querier expecting a response SHOULD be prepared for this situation.
The frequency of the initial LM for requesting starting the measurement
should be slow, so that there is enough time for far end to check if the
requested measurement can be done. The querier should abort the measurement
after not receiving any positive feedback when a specified timer expires.
setting a timer to differentiate between an acceptable initialization delay
and a permanent unavailability condition at the far end. Alternatively, the
receiver MAY respond, possibly in a rate-limited manner, to queries received
during this period with an appropriate notification code. Since counting
transmitted packets at querier side will cost extra resources (or is not
free), the querier doesn't need to start counting its transmitted packets
until receiving a positive feedback from the far-end.


Suggested text for LM/DM Interval:

		2.7.10: LM Interval
		
		The interval may affect the accuracy of the packet loss
count. From implementation point of view, the shorter the interval, the
higher the processing cost to equipment. Querier should encode its intended
interval in its LM Message. If the interval specified by the LM message
can't be supported by the far end, the far end can simply ignore the LM
requests by not responding anything or respond with an appropriate
notification code indicating its minimum allowed LM interval.   

In the Section 3.1 LM Message Format, add an 8 (or 16) bits field for LM
Interval. The Interval Unit should be in ms. 

Linda Dunbar

-----Original Message-----
From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk] 
Sent: Monday, January 10, 2011 11:29 AM
To: Linda Dunbar
Cc: 'Greg Mirsky'; mpls@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"

Linda,

On 10 Jan 2011, at 16:28, Linda Dunbar wrote:
> From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk]
> 
> 1) The edits suggested by Linda change the semantics from suggesting a
querier maintain a timer to allow for the receiving end to "get its act
together" to if the receiving end doesn't get its act together within X
packets stop sending LM. Is that really what's intended? I would expect the
time taken for the receiving end "to get its act together" would not be a
function of the LM transmission rate and therefore using transmission rate
to guess whether the receiving end is dead Vs getting itself ready doesn't
sound sensible.
> 
> 
> [Linda] The reason for suggesting Initiator to have slower transmission
rate is to minimize processing needed at the Initiator before Far End
committing to the counting.
> 

But you suggest edit does not suggest a slower transmission rate it states
the querier should stop transmission!

> We have considered implementing this feature on our products and
discovered that it DOES take some time for the Central CPU to receive the
Counting Request (as LM in this draft), check if the requested Counting can
be supported, pass the request to the corresponding line card, and get
confirmation from the Line card. Sometimes, the Far End can't perform the
requested Counting because it is performing counting for requests from other
nodes.
> 

I accept that a receiver may take some time to configure itself for counting
and that the time it takes may be a function of other things it is doing.
What I am saying is that the time it takes is never a function of the
interval being configured.

> 2) I don't like the final sentence suggesting queriers should delay
counting transmitted packets until receiving a positive response because
doing so costs resources. It sounds like an internal implementation decision
that has nothing to do with interoperability and therefore irrelevant.
> 
> 
> [Linda]I agree with your point that that the Source Node performing or not
performing the counting before receiving the positive feedback from Far End
is not interoperability issue. Maybe it can be a recommendation?
> 
> But it is necessary for Source node to abort the effort after not
receiving the positive feedback after sometime (like X number of LM or timer
expires).
> 

At some point, if the querier has not received a positive response it must
abort the operation. The original text suggest maintaing a timer. Your edit
suggested making ti a function of packets sent. I am saying the former seems
more sensible than the latter to me.

> 4) Giving the receiving end the opportunity to reply with "I can;t support
the rate you're asking for it's too fast for me" sounds attractive but I am
not sure it is in practice if one thinks how such functionality is likely to
be used. If an operator is going to turn it on with the thinking that
performing LM of some sort is important regardless of the LM interval then
negotiating a shorter interval may have value. However I don't expect that
to be the case. I would expect an operator to pre-plan what interval they
need given their knowledge of their network and the accuracy they desire,
having the network change that may well cause unexpected consequences. In
such a scenario I think it's better to let the receiver "hard fail" and the
operator can investigate rather than have the network re-configure and the
re-configuration go unnoticed, after all LM failing does not impact the
ability of the network to actually forward packets.
> 
> 
> [Linda] Do you mean that Receiver can ignore the LMs if the Interval
specified in the message is more than it can handle?

That is one option.

The background to my thinking is:

I assume that LM will be turned on explicitly (i.e. it will not be on by
default)
I assume that LM is turned on for a reason, e.g. because an operator needs
to support an SLA involving packet loss.
The interval may affect the accuracy of the packet loss count.
I expect operators would rather LM "hard fail" rather than have the network
re-configure automatically to a different interval because an SLA
calculation (or whatever else is relying on the LM) could become inaccurate
and no-one would know unless they really dug deep into what the network was
doing.

The network re-configuring itself in order to repair itself so it can
continue to forward packets is one thing.

The network reconfiguring non-forwarding related features itself because it
believes it knows what to do better than the person who designed &
configured it could lead to all sorts of trouble in the field IMO.

Ben

 


--Boundary_(ID_aiZ8cClfPmqLJcHkHVMzAA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7036.0">
<TITLE>RE: [mpls-tp] [mpls] Questions on =
&quot;draft-ietf-mpls-loss-delay-00&quot;</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">Ben</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New"> and</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">colleagues</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">:</FONT></SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">Y</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">ou said</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier New"> =
&quot;</FONT></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"><I> <FONT FACE=3D"Courier =
New">But you suggest edit does not suggest a =
slower</FONT></I></SPAN><SPAN LANG=3D"en-us"><I><FONT FACE=3D"Courier =
New"></FONT></I></SPAN><SPAN LANG=3D"en-us"><I> <FONT FACE=3D"Courier =
New">transmission rate it states the q</FONT><FONT FACE=3D"Courier =
New">uerier should stop transmissio</FONT><FONT FACE=3D"Courier =
New">n</FONT></I></SPAN><SPAN LANG=3D"en-us"><I><FONT FACE=3D"Courier =
New">&quot;, </FONT></I></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">T</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">w</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier New">o comments: =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">I</FONT> <FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">t</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">hink</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">&#8220;</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">slower transmission rate by =
querier</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">&#8221;</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New"> should be included =
in</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">the</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New"></FONT> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">text. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" FACE=3D"Courier New">I =
suggest</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">ed</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New"> that querier</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" FACE=3D"Courier New">may =
choose</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">not starting counting (not transmission) until a =
positive feedback from Far End has been received. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">Based on</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">t</FONT><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">he discussion over this</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" FACE=3D"Courier New"> email =
thread</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier New">, =
do</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">p</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">eople</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> think the following text</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">i</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">s</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> more appropriate? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Courier">When initiating an LM operation, the far end =
may require a period of time to become ready for the requested =
measurement operation</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">or the =
far end may not be able to support the requested =
measurement</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier">.</FONT></SPAN><SPAN =
LANG=3D"en-us"><STRIKE></STRIKE></SPAN><SPAN LANG=3D"en-us"><STRIKE> =
<FONT SIZE=3D2 FACE=3D"Courier">During this =
period</FONT></STRIKE></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier"></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">Under those circumstances</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier">, LM queri</FONT><FONT SIZE=3D2 FACE=3D"Courier">es MAY =
simply be discarded, and the querier expecting a response SHOULD be =
prepared for this situation</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">T</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">he =
frequency of the initial LM</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier"> for requesting starting the measurement should be =
slow, so that there is enough time for</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">far end</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier"></FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">to check if the requested measurement can be =
done</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">T</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">he querier should</FONT> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">abort the measurement after =
not</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"> receiving any positive =
feedback when</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">a</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"> =
specified timer expires</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier"></FONT></SPAN><SPAN =
LANG=3D"en-us"><STRIKE></STRIKE></SPAN><SPAN LANG=3D"en-us"><STRIKE> =
<FONT SIZE=3D2 FACE=3D"Courier">setting a timer to differentiate between =
an acceptable initialization delay and a permanent unavailability =
condition at the far end</FONT></STRIKE></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier"> Alternatively, the receiver MAY respond, possibly in a =
rate-limited manner, to queries received during this period with an =
appropriate notification code.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier"> Since counting transmitted packets at querier =
side will cost extra resources (or is not free), the qu</FONT><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">erier</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">d</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">oesn</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">&#8217;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">t need =
to</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"> start =
counting</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"> its =
transmitted packets until receiving a positive feedback from the =
far-end.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>
</UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">Suggested text for LM/DM =
Interval:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">2.7.10: LM</FONT><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"> Interval</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">The interval may affect the =
accuracy of the packet loss co</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">unt</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"> =
F</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">rom =
implementation point of view,</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">t</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">he shorter the interval, the higher the =
processing</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">c</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">ost to</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">equipment</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier"></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">Q</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">uerier</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier"> should</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">encode its intended interva</FONT><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">l</FONT><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"> in its</FONT> <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">LM =
Message</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">If =
the</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"></FONT> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">interval</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier"></FONT> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">specified by the LM =
message can</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">&#8217;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">t =
be</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">supported by =
the far end,</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">the</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">far =
end can</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">simply ignore the LM =
requests</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">by not =
responding</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">anything</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">or</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">respond</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier">with =
an appropriate notification code indicating its</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">minimum allowed</FONT> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier">LM</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">interval</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier">.</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>
</UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">In the</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New">Section 3.1 LM Message Format, =
add</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">an</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Courier New"> 8</FONT><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> (or 16)</FONT><FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New"> bit</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">s</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier New"> =
field</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
FACE=3D"Courier New">for</FONT> <FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">LM Interval.</FONT> <FONT COLOR=3D"#0000FF" FACE=3D"Courier =
New">T</FONT><FONT COLOR=3D"#0000FF" FACE=3D"Courier New">he Interval =
Unit should be in ms. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Linda =
Dunbar</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">-----Original Message-----<BR>
</FONT><FONT FACE=3D"Courier New">From:</FONT><FONT FACE=3D"Courier =
New"> Ben Niven-Jenkins [<A =
HREF=3D"mailto:ben@niven-jenkins.co.uk">mailto:ben@niven-jenkins.co.uk</A=
>]<BR>
</FONT><FONT FACE=3D"Courier New">Sent:</FONT><FONT FACE=3D"Courier =
New"> Monday, January 10, 2011 11:29 AM<BR>
</FONT><FONT FACE=3D"Courier New">To</FONT><FONT FACE=3D"Courier =
New">:</FONT><FONT FACE=3D"Courier New"> Linda Dunbar<BR>
</FONT><FONT FACE=3D"Courier New">Cc:</FONT><FONT FACE=3D"Courier New"> =
'Greg Mirsky'; mpls@ietf.org; mpls-tp@ietf.org<BR>
</FONT><FONT FACE=3D"Courier New">Subject:</FONT><FONT FACE=3D"Courier =
New"> Re: [mpls-tp] [mpls] Questions on =
&quot;draft-ietf-mpls-loss-delay-00&quot;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">Linda,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">On 10 Jan =
2011, at 16:28, Linda D</FONT><FONT FACE=3D"Courier New">unbar =
wrote:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; From: =
Ben Niven-Jenkins [<A =
HREF=3D"mailto:ben@niven-jenkins.co.uk">mailto:ben@niven-jenkins.co.uk</A=
>]</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; 1) The =
edits suggested by Linda change the semantics from suggesting a querier =
maintain a timer to allow for the receiving end to &quot;get its act =
together&quot; to if the receiving end do</FONT><FONT FACE=3D"Courier =
New">esn't get its act together within X packets stop sending LM. Is =
that really what's intended? I would expect the time taken for the =
receiving end &quot;to get its act together&quot; would not be a =
function of the LM transmission rate and therefore using =
transmission</FONT><FONT FACE=3D"Courier New"></FONT> <FONT =
FACE=3D"Courier New">rate to guess whether the receiving end is dead Vs =
getting itself ready doesn't sound sensible.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
[Linda] The reason for suggesting Initiator to have slower transmission =
rate is to minimize processing needed at the Initiator before Far End =
committing to the counting.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">But you =
suggest edit does not suggest a slower transmission rate it states the =
q</FONT><FONT FACE=3D"Courier New">uerier should stop =
transmission!</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; We =
have considered implementing this feature on our products and discovered =
that it DOES take some time for the Central CPU to receive the Counting =
Request (as LM in this draft), check if the requested Counting can be =
su</FONT><FONT FACE=3D"Courier New">pported, pass the request to the =
corresponding line card, and get confirmation from the Line card. =
Sometimes, the Far End can't perform the requested Counting because it =
is performing counting for requests from other nodes.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">I accept =
that a receiver may</FONT><FONT FACE=3D"Courier New"> take some time to =
configure itself for counting and that the time it takes may be a =
function of other things it is doing. What I am saying is that the time =
it takes is never a function of the interval being =
configured.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; 2) I =
don't like the final sentenc</FONT><FONT FACE=3D"Courier New">e =
suggesting queriers should delay counting transmitted packets until =
receiving a positive response because doing so costs resources. It =
sounds like an internal implementation decision that has nothing to do =
with interoperability and therefore irrelevant.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
[Linda]I agree with your point that that the Source Node performing or =
not performing the counting before receiving the positive feedback from =
Far End is not interoperability issue. Maybe it can be a =
recommendation?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; But it =
is necessary for Sou</FONT><FONT FACE=3D"Courier New">rce node to abort =
the effort after not receiving the positive feedback after sometime =
(like X number of LM or timer expires).</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">At some =
point, if the querier has not received a positive response it must abort =
the operation. The original text suggest main</FONT><FONT =
FACE=3D"Courier New">taing a timer. Your edit suggested making ti a =
function of packets sent. I am saying the former seems more sensible =
than the latter to me.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; 4) =
Giving the receiving end the opportunity to reply with &quot;I can;t =
support the rate you're asking for it's too fas</FONT><FONT =
FACE=3D"Courier New">t for me&quot; sounds attractive but I am not sure =
it is in practice if one thinks how such functionality is likely to be =
used. If an operator is going to turn it on with the thinking that =
performing LM of some sort is important regardless of the LM interval =
t</FONT><FONT FACE=3D"Courier New">h</FONT><FONT FACE=3D"Courier New">en =
negotiating a shorter interval may have value. However I don't expect =
that to be the case. I would expect an operator to pre-plan what =
interval they need given their knowledge of their network and the =
accuracy they desire, having the network change tha</FONT><FONT =
FACE=3D"Courier New">t</FONT><FONT FACE=3D"Courier New"> may well cause =
unexpected consequences. In such a scenario I think it's better to let =
the receiver &quot;hard fail&quot; and the operator can investigate =
rather than have the network re-configure and the re-configuration go =
unnoticed, after all LM failing does not</FONT><FONT FACE=3D"Courier =
New"></FONT> <FONT FACE=3D"Courier New">impact the ability of the =
network to actually forward packets.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">&gt; =
[Linda] Do you mean that Receiver can ignore the LMs if the Interval =
specified in the message is more than it can handle?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">That is one =
option.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">The =
background to my thinking is:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">I assume =
that LM will be turned on explicitly (i.e. it will not be on by =
default)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">I assume =
that LM is turned on for a reason, e.g. because an operator needs to =
support an SLA involving packet loss.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">The =
interval may affect the accuracy of the packet loss co</FONT><FONT =
FACE=3D"Courier New">unt.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">I expect =
operators would rather LM &quot;hard fail&quot; rather than have the =
network re-configure automatically to a different interval because an =
SLA calculation (or whatever else is relying on the LM) could become =
inaccurate and no-one would know unless they</FONT><FONT FACE=3D"Courier =
New"> really dug deep into what the network was doing.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">The network =
re-configuring itself in order to repair itself so it can continue to =
forward packets is one thing.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">The network =
reconfiguring non-forwarding related features itself because it believes =
it know</FONT><FONT FACE=3D"Courier New">s what to do better than the =
person who designed &amp; configured it could lead to all sorts of =
trouble in the field IMO.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">Ben</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>=

--Boundary_(ID_aiZ8cClfPmqLJcHkHVMzAA)--

From jingr@ties.itu.ch  Thu Jan 13 00:07:16 2011
Return-Path: <jingr@ties.itu.ch>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1311D3A6ABC for <mpls-tp@core3.amsl.com>; Thu, 13 Jan 2011 00:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SPE9arydi2Am for <mpls-tp@core3.amsl.com>; Thu, 13 Jan 2011 00:07:15 -0800 (PST)
Received: from mail9.itu.ch (mail9.itu.ch [156.106.192.39]) by core3.amsl.com (Postfix) with ESMTP id ACBA73A6AB3 for <mpls-tp@ietf.org>; Thu, 13 Jan 2011 00:07:14 -0800 (PST)
Received: from ties.itu.ch (ties.itu.ch [156.106.192.33]) by mail9.itu.ch (8.13.8/8.14.4) with ESMTP id p0D89Ysb021330 for <mpls-tp@ietf.org>; Thu, 13 Jan 2011 09:09:35 +0100
Received: from localhost (tokaj.itu.ch [156.106.192.34]) by ties.itu.ch (8.14.3/8.14.3) with ESMTP id p0D89XMs319807; Thu, 13 Jan 2011 09:09:34 +0100 (CET)
Received: from 156.106.192.159 ( [156.106.192.159]) as user jingr@ties.itu.ch by gold.itu.ch with HTTP; Thu, 13 Jan 2011 09:09:33 +0100
Message-ID: <1294906173.4d2eb33dd1ffa@gold.itu.ch>
Date: Thu, 13 Jan 2011 09:09:33 +0100
From: ruiquan.jing@ties.itu.int
To: jingr@ties.itu.ch
References: <1294885988.4d2e64642cd0e@gold.itu.ch>
In-Reply-To: <1294885988.4d2e64642cd0e@gold.itu.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.0
X-Originating-IP: 156.106.192.159
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (mail9.itu.ch [156.106.192.39]); Thu, 13 Jan 2011 09:09:35 +0100 (CET)
Cc: mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 08:07:16 -0000

Resend to mpls-tp list.

Quoting jingr@ties.itu.ch:

> Hi Stewart Bryant,
> 
> I don¡¯t agree with the current LS text.
> 
> China Telecom support the standardization of Y.1731 based MPLS-TP OAM tools
> in 
> the ITU-T to meet the urgent and increasing requirements for PTN deployment. 
> 
> It¡¯s a multi-vendor supported, interoperability certificated and feasible 
> solution.  It had been specified in both CCSA (China Communications Standards
> 
> Association) and China Telecom¡¯s PTN standard as the only standard OAM 
> mechanism.
> 
>  
> 
> Best Regards
> 
> Jing Ruiquan
> 
> China¡¡Telecom  Beijing  Research¡¡Institute
> 
> ------------------------------------------------------------------------------
--
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Stewart 
> Bryant
> Sent: Monday, January 10, 2011 6:57 PM
> To: mpls@ietf.org
> Subject: [mpls] Draft: Response to Updated draft Recommendation G.tpoam 
> [Ref043.02]
> 
> 
> I propose to send the following Liaison Response to the ITU-T on Friday 
> 14th January and am posting it to the MPLS WG list for review. 
> 
> ======= 
> 
> Response to Updated draft Recommendation G.tpoam [Ref 043.02] 
> 
> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com 
> To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, IAB@ietf.org 
> CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com 
> stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org 
> yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com 
> ghani.abbas@ericsson.com, hhelvoort@huawei.com 
> malcolm.betts@zte.com.cn, kam.lam@alcatel-lucent.com 
> 
> For Action 
> 
> The MPLS Working Group notes that this document contains text describing 
> MPLS-TP OAM protocols not designed and standardized using the IETF 
> Standards process. Specifically it uses material from 
> draft-bhh-mpls-tp-oam-y1731-06. 
> 
> We wish to draw your attention to the status section of 
> draft-bhh-mpls-tp-oam-y1731-06 which states: 
> 
> "Internet-Drafts are draft documents valid for a maximum of six months 
> and may be updated, replaced, or obsoleted by other documents at any 
> time. It is inappropriate to use Internet-Drafts as reference material 
> or to cite them other than as "work in progress". 
> 
> Please also note that since the draft filename starts with the prefix 
> string "draft-bhh" this clearly identifies it to the reader as a 
> document expressing the personal technical views of the authors and 
> hence hence as a document that that does not have any acknowledged level 
> of IETF consensus. 
> 
> Since the text of draft Recommendation for G.tpoam is based on an 
> MPLS-TP OAM protocol not designed within the IETF Standards Process this 
> is a breach of the SG15 agreement with the IETF as published in Report 
> of the first meeting of Working Party 3/15 Transport network structures 
> (2009-2012) (Geneva, 1 ¨C 12 December 2008) which can be found at 
> http://www.itu.int/md/T09-SG15-R-0004/en 
> 
> Please confirm that the ITU-T intends to continue with the joint work on 
> MPLS-TP and that the ITU-T will align this recommendation with the IETF 
> MPLS-TP OAM design before advancing this document through the ITU-T 
> publication process. 
> 
> The MPLS Working Group would also like to draw the attention of ITU-T 
> SG15 to the IETF copyright rules. Please see 
> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-
> 20091228.htm 
> for further details. 
> 
> Since this draft Recommendation contains text in which the ITU-T SG15 
> has proposed making changes to IETF protocols without the approval of 
> the IETF, the MPLS Working Group have referred this liaison to the IAB 
> for their consideration. 
> 
> 
> 
> ========= 
> _______________________________________________ 
> mpls mailing list 
> mpls@ietf.org 
> https://www.ietf.org/mailman/listinfo/mpls 
> 
> 
> 




From Feng.f.Huang@alcatel-sbell.com.cn  Thu Jan 13 01:32:31 2011
Return-Path: <Feng.f.Huang@alcatel-sbell.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D57A63A6AF1; Thu, 13 Jan 2011 01:32:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.465
X-Spam-Level: 
X-Spam-Status: No, score=0.465 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uuygv1w93QbC; Thu, 13 Jan 2011 01:32:29 -0800 (PST)
Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by core3.amsl.com (Postfix) with ESMTP id 694B73A6AC5; Thu, 13 Jan 2011 01:32:28 -0800 (PST)
X-AuditID: ac189297-b7cc5ae00000285e-bb-4d2ec73857ab
Received: from cnshgsbhs01.ad4.ad.alcatel.com (smtp.cn.alcatel-lucent.com [172.24.146.145]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Brightmail Gateway) with SMTP id 68.1C.10334.837CE2D4; Thu, 13 Jan 2011 17:34:48 +0800 (HKT)
Received: from CNSHGSMBS01.ad4.ad.alcatel.com ([172.24.146.171]) by cnshgsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 13 Jan 2011 17:34:38 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 13 Jan 2011 17:34:37 +0800
Message-ID: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AB3@CNSHGSMBS01.ad4.ad.alcatel.com>
In-Reply-To: <077E41CFFD002C4CAB7DFA4386A53264033050A2@DEMUEXC014.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
Thread-Index: AcuwtRGLd9xxAStESUK8g5O/l8FWKgCRGKOQAAJfcJA=
References: <4D2AE5E0.90703@cisco.com> <077E41CFFD002C4CAB7DFA4386A53264033050A2@DEMUEXC014.nsn-intra.net>
From: "HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, <stbryant@cisco.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 13 Jan 2011 09:34:38.0788 (UTC) FILETIME=[191F4840:01CBB305]
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 09:32:31 -0000

Hi,Nurit,
   I can't agree with you.
   Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet =
Transport Network by many applications and public demo and it has many =
supporters. I am wondering why  this solutions is not  standardized in =
ietf?=20
    Further more,  I really don't agree with your last sentence, this =
solution is asked by customers in Industry, you can see at least 7 =
providers in global support this solution.

B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
Sprecher, Nurit (NSN - IL/Hod HaSharon)
Sent: 2011=C4=EA1=D4=C213=C8=D5 16:18
To: stbryant@cisco.com; mpls@ietf.org
Subject: Re: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam[Ref043.02]

Hi,
I support the proposal.
We have a cooperative agreement with the ITU-T concerning the work on =
MPLS-TP.=20
The agreement recognizes the design authority of the IETF for MPLS and =
it is agreed that the development of the protocol should be done in the =
IETF using the IETF processes. The ITU-T should not take any =
uncoordinated action in the development of the MPLS_TP protocol.=20
We would appreciate if the ITU-T continues (as it committed to) with the =
collaborative work with the IETF on MPLS_TP and contributes from its =
expertise to the development of the protocol using the IETF processes.=20
We would also not like to see two competing solutions which may confuse =
the Industry, bloat operational and capital expenses and badly affect =
the end customer.=20
Best regards,
Nurit

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
ext Stewart Bryant
Sent: Monday, January 10, 2011 12:57 PM
To: mpls@ietf.org
Subject: [mpls] Draft: Response to Updated draft Recommendation G.tpoam =
[Ref043.02]

I propose to send the following Liaison Response to the ITU-T on Friday =
14th January and am posting it to the MPLS WG list for review.

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

Response to Updated draft Recommendation G.tpoam [Ref 043.02]

From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, =
IAB@ietf.org
CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com =
stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org =
yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
ghani.abbas@ericsson.com, hhelvoort@huawei.com malcolm.betts@zte.com.cn, =
kam.lam@alcatel-lucent.com

For Action

The MPLS Working Group notes that this document contains text describing

MPLS-TP OAM protocols not designed and standardized using the IETF =
Standards process. Specifically it uses material from =
draft-bhh-mpls-tp-oam-y1731-06.

We wish to draw your attention to the status section of
draft-bhh-mpls-tp-oam-y1731-06 which states:

"Internet-Drafts are draft documents valid for a maximum of six months =
and may be updated, replaced, or obsoleted by other documents at any =
time. It is inappropriate to use Internet-Drafts as reference material =
or to cite them other than as "work in progress".

Please also note that since the draft filename starts with the prefix =
string "draft-bhh" this clearly identifies it to the reader as a =
document expressing the personal technical views of the authors and =
hence hence as a document that that does not have any acknowledged level

of IETF consensus.

Since the text of draft Recommendation for G.tpoam is based on an =
MPLS-TP OAM protocol not designed within the IETF Standards Process this

is a breach of the SG15 agreement with the IETF as published in Report =
of the first meeting of Working Party 3/15 Transport network structures
(2009-2012) (Geneva, 1 - 12 December 2008) which can be found at =
http://www.itu.int/md/T09-SG15-R-0004/en

Please confirm that the ITU-T intends to continue with the joint work on

MPLS-TP and that the ITU-T will align this recommendation with the IETF =
MPLS-TP OAM design before advancing this document through the ITU-T =
publication process.

The MPLS Working Group would also like to draw the attention of ITU-T
SG15 to the IETF copyright rules. Please see
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
0091228.htm
for further details.

Since this draft Recommendation contains text in which the ITU-T SG15 =
has proposed making changes to IETF protocols without the approval of =
the IETF, the MPLS Working Group have referred this liaison to the IAB =
for their consideration.


=3D=3D=3D=3D=3D=3D=3D=3D=3D
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From nurit.sprecher@nsn.com  Thu Jan 13 01:45:03 2011
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA1103A6AE3; Thu, 13 Jan 2011 01:45:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.214
X-Spam-Level: 
X-Spam-Status: No, score=-4.214 tagged_above=-999 required=5 tests=[AWL=1.785,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLyb7EBlcPyc; Thu, 13 Jan 2011 01:45:02 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id B25983A69E5; Thu, 13 Jan 2011 01:45:01 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0D9jC3D026559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Jan 2011 10:45:12 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0D9jApU009968; Thu, 13 Jan 2011 10:45:11 +0100
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 13 Jan 2011 10:45:10 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Jan 2011 10:45:09 +0100
Message-ID: <077E41CFFD002C4CAB7DFA4386A53264033051E3@DEMUEXC014.nsn-intra.net>
In-Reply-To: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AB3@CNSHGSMBS01.ad4.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
Thread-Index: AcuwtRGLd9xxAStESUK8g5O/l8FWKgCRGKOQAAJfcJAAAJGFwA==
References: <4D2AE5E0.90703@cisco.com> <077E41CFFD002C4CAB7DFA4386A53264033050A2@DEMUEXC014.nsn-intra.net> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AB3@CNSHGSMBS01.ad4.ad.alcatel.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>, <stbryant@cisco.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 13 Jan 2011 09:45:10.0233 (UTC) FILETIME=[917E2490:01CBB306]
Cc: mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 09:45:03 -0000

Hi Feng,
I did not refer to specific solution, validity and acceptance of a solution, so I cannot see to what you disagree and how your response fit to mine. 
If you think that you have a good solution which is proven and supported please discuss it in the IETF and try to get support for it! 
I would like the ITU-T to continue with its collaborative agreement with the IETF and ensure that the development of the protocol is done as agreed and supported by SG15 using the IETF processes.
I will support a single global solution interoperable solution (whatever the solution is). 
Best regards,
Nurit

-----Original Message-----
From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn] 
Sent: Thursday, January 13, 2011 11:35 AM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; mpls@ietf.org
Cc: mpls-tp@ietf.org
Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]

Hi,Nurit,
   I can't agree with you.
   Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet Transport Network by many applications and public demo and it has many supporters. I am wondering why  this solutions is not  standardized in ietf? 
    Further more,  I really don't agree with your last sentence, this solution is asked by customers in Industry, you can see at least 7 providers in global support this solution.

B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Sprecher, Nurit (NSN - IL/Hod HaSharon)
Sent: 2011$BG/(J1$B7n(J13$BF|(J 16:18
To: stbryant@cisco.com; mpls@ietf.org
Subject: Re: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]

Hi,
I support the proposal.
We have a cooperative agreement with the ITU-T concerning the work on MPLS-TP. 
The agreement recognizes the design authority of the IETF for MPLS and it is agreed that the development of the protocol should be done in the IETF using the IETF processes. The ITU-T should not take any uncoordinated action in the development of the MPLS_TP protocol. 
We would appreciate if the ITU-T continues (as it committed to) with the collaborative work with the IETF on MPLS_TP and contributes from its expertise to the development of the protocol using the IETF processes. 
We would also not like to see two competing solutions which may confuse the Industry, bloat operational and capital expenses and badly affect the end customer. 
Best regards,
Nurit

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of ext Stewart Bryant
Sent: Monday, January 10, 2011 12:57 PM
To: mpls@ietf.org
Subject: [mpls] Draft: Response to Updated draft Recommendation G.tpoam [Ref043.02]

I propose to send the following Liaison Response to the ITU-T on Friday 14th January and am posting it to the MPLS WG list for review.

=======

Response to Updated draft Recommendation G.tpoam [Ref 043.02]

From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, IAB@ietf.org
CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
ghani.abbas@ericsson.com, hhelvoort@huawei.com malcolm.betts@zte.com.cn, kam.lam@alcatel-lucent.com

For Action

The MPLS Working Group notes that this document contains text describing

MPLS-TP OAM protocols not designed and standardized using the IETF Standards process. Specifically it uses material from draft-bhh-mpls-tp-oam-y1731-06.

We wish to draw your attention to the status section of
draft-bhh-mpls-tp-oam-y1731-06 which states:

"Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress".

Please also note that since the draft filename starts with the prefix string "draft-bhh" this clearly identifies it to the reader as a document expressing the personal technical views of the authors and hence hence as a document that that does not have any acknowledged level

of IETF consensus.

Since the text of draft Recommendation for G.tpoam is based on an MPLS-TP OAM protocol not designed within the IETF Standards Process this

is a breach of the SG15 agreement with the IETF as published in Report of the first meeting of Working Party 3/15 Transport network structures
(2009-2012) (Geneva, 1 - 12 December 2008) which can be found at http://www.itu.int/md/T09-SG15-R-0004/en

Please confirm that the ITU-T intends to continue with the joint work on

MPLS-TP and that the ITU-T will align this recommendation with the IETF MPLS-TP OAM design before advancing this document through the ITU-T publication process.

The MPLS Working Group would also like to draw the attention of ITU-T
SG15 to the IETF copyright rules. Please see
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
0091228.htm
for further details.

Since this draft Recommendation contains text in which the ITU-T SG15 has proposed making changes to IETF protocols without the approval of the IETF, the MPLS Working Group have referred this liaison to the IAB for their consideration.


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

From Feng.f.Huang@alcatel-sbell.com.cn  Thu Jan 13 02:29:08 2011
Return-Path: <Feng.f.Huang@alcatel-sbell.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7B443A6B60; Thu, 13 Jan 2011 02:29:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.462
X-Spam-Level: 
X-Spam-Status: No, score=0.462 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4Q8KZ8gep7q; Thu, 13 Jan 2011 02:29:07 -0800 (PST)
Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by core3.amsl.com (Postfix) with ESMTP id A75BF3A6B58; Thu, 13 Jan 2011 02:29:06 -0800 (PST)
X-AuditID: ac189297-b7cc5ae00000285e-82-4d2ed47f07cc
Received: from cnshgsbhs01.ad4.ad.alcatel.com (smtp.cn.alcatel-lucent.com [172.24.146.145]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Brightmail Gateway) with SMTP id F4.8F.10334.F74DE2D4; Thu, 13 Jan 2011 18:31:27 +0800 (HKT)
Received: from CNSHGSMBS01.ad4.ad.alcatel.com ([172.24.146.171]) by cnshgsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 13 Jan 2011 18:31:17 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 13 Jan 2011 18:31:15 +0800
Message-ID: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AF8@CNSHGSMBS01.ad4.ad.alcatel.com>
In-Reply-To: <077E41CFFD002C4CAB7DFA4386A53264033051E3@DEMUEXC014.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
Thread-Index: AcuwtRGLd9xxAStESUK8g5O/l8FWKgCRGKOQAAJfcJAAAJGFwAABmzRA
References: <4D2AE5E0.90703@cisco.com> <077E41CFFD002C4CAB7DFA4386A53264033050A2@DEMUEXC014.nsn-intra.net> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AB3@CNSHGSMBS01.ad4.ad.alcatel.com> <077E41CFFD002C4CAB7DFA4386A53264033051E3@DEMUEXC014.nsn-intra.net>
From: "HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, <stbryant@cisco.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 13 Jan 2011 10:31:17.0394 (UTC) FILETIME=[02D96720:01CBB30D]
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 10:29:09 -0000

Hi, Nurit,
   Please see in line.
B.R.
Feng
=20

-----Original Message-----
From: Sprecher, Nurit (NSN - IL/Hod HaSharon) =
[mailto:nurit.sprecher@nsn.com]=20
Sent: 2011=C4=EA1=D4=C213=C8=D5 17:45
To: HUANG Feng F; stbryant@cisco.com; mpls@ietf.org
Cc: mpls-tp@ietf.org
Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam[Ref043.02]

Hi Feng,
I did not refer to specific solution, validity and acceptance of a =
solution, so I cannot see to what you disagree and how your response fit =
to mine.=20
If you think that you have a good solution which is proven and supported =
please discuss it in the IETF and try to get support for it!=20

HF> The solution has been submitted to ietf for 2 year!

I would like the ITU-T to continue with its collaborative agreement with =
the IETF and ensure that the development of the protocol is done as =
agreed and supported by SG15 using the IETF processes.

HF> I can't image the meaning of cooperation is that ITU-T do nothing =
and just obey IETF's process!

I will support a single global solution interoperable solution (whatever =
the solution is).=20
Best regards,
Nurit

-----Original Message-----
From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
Sent: Thursday, January 13, 2011 11:35 AM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; =
mpls@ietf.org
Cc: mpls-tp@ietf.org
Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam[Ref043.02]

Hi,Nurit,
   I can't agree with you.
   Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet =
Transport Network by many applications and public demo and it has many =
supporters. I am wondering why  this solutions is not  standardized in =
ietf?=20
    Further more,  I really don't agree with your last sentence, this =
solution is asked by customers in Industry, you can see at least 7 =
providers in global support this solution.

B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
Sprecher, Nurit (NSN - IL/Hod HaSharon)
Sent: 2011=C4=EA1=D4=C213=C8=D5 16:18
To: stbryant@cisco.com; mpls@ietf.org
Subject: Re: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam[Ref043.02]

Hi,
I support the proposal.
We have a cooperative agreement with the ITU-T concerning the work on =
MPLS-TP.=20
The agreement recognizes the design authority of the IETF for MPLS and =
it is agreed that the development of the protocol should be done in the =
IETF using the IETF processes. The ITU-T should not take any =
uncoordinated action in the development of the MPLS_TP protocol.=20
We would appreciate if the ITU-T continues (as it committed to) with the =
collaborative work with the IETF on MPLS_TP and contributes from its =
expertise to the development of the protocol using the IETF processes.=20
We would also not like to see two competing solutions which may confuse =
the Industry, bloat operational and capital expenses and badly affect =
the end customer.=20
Best regards,
Nurit

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
ext Stewart Bryant
Sent: Monday, January 10, 2011 12:57 PM
To: mpls@ietf.org
Subject: [mpls] Draft: Response to Updated draft Recommendation G.tpoam =
[Ref043.02]

I propose to send the following Liaison Response to the ITU-T on Friday =
14th January and am posting it to the MPLS WG list for review.

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

Response to Updated draft Recommendation G.tpoam [Ref 043.02]

From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, =
IAB@ietf.org
CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com =
stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org =
yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
ghani.abbas@ericsson.com, hhelvoort@huawei.com malcolm.betts@zte.com.cn, =
kam.lam@alcatel-lucent.com

For Action

The MPLS Working Group notes that this document contains text describing

MPLS-TP OAM protocols not designed and standardized using the IETF =
Standards process. Specifically it uses material from =
draft-bhh-mpls-tp-oam-y1731-06.

We wish to draw your attention to the status section of
draft-bhh-mpls-tp-oam-y1731-06 which states:

"Internet-Drafts are draft documents valid for a maximum of six months =
and may be updated, replaced, or obsoleted by other documents at any =
time. It is inappropriate to use Internet-Drafts as reference material =
or to cite them other than as "work in progress".

Please also note that since the draft filename starts with the prefix =
string "draft-bhh" this clearly identifies it to the reader as a =
document expressing the personal technical views of the authors and =
hence hence as a document that that does not have any acknowledged level

of IETF consensus.

Since the text of draft Recommendation for G.tpoam is based on an =
MPLS-TP OAM protocol not designed within the IETF Standards Process this

is a breach of the SG15 agreement with the IETF as published in Report =
of the first meeting of Working Party 3/15 Transport network structures
(2009-2012) (Geneva, 1 - 12 December 2008) which can be found at =
http://www.itu.int/md/T09-SG15-R-0004/en

Please confirm that the ITU-T intends to continue with the joint work on

MPLS-TP and that the ITU-T will align this recommendation with the IETF =
MPLS-TP OAM design before advancing this document through the ITU-T =
publication process.

The MPLS Working Group would also like to draw the attention of ITU-T
SG15 to the IETF copyright rules. Please see
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
0091228.htm
for further details.

Since this draft Recommendation contains text in which the ITU-T SG15 =
has proposed making changes to IETF protocols without the approval of =
the IETF, the MPLS Working Group have referred this liaison to the IAB =
for their consideration.


=3D=3D=3D=3D=3D=3D=3D=3D=3D
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From nurit.sprecher@nsn.com  Thu Jan 13 04:52:00 2011
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 755F63A6B79; Thu, 13 Jan 2011 04:52:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.271
X-Spam-Level: 
X-Spam-Status: No, score=-4.271 tagged_above=-999 required=5 tests=[AWL=1.728,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wyjtQXxtU-b0; Thu, 13 Jan 2011 04:51:59 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 8C3AE3A6B76; Thu, 13 Jan 2011 04:51:58 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0DCsC9L028832 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Jan 2011 13:54:12 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0DCs6nZ029522; Thu, 13 Jan 2011 13:54:12 +0100
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 13 Jan 2011 13:54:09 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Jan 2011 13:54:05 +0100
Message-ID: <077E41CFFD002C4CAB7DFA4386A53264033054B9@DEMUEXC014.nsn-intra.net>
In-Reply-To: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AF8@CNSHGSMBS01.ad4.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
Thread-Index: AcuwtRGLd9xxAStESUK8g5O/l8FWKgCRGKOQAAJfcJAAAJGFwAABmzRAAAQptcA=
References: <4D2AE5E0.90703@cisco.com> <077E41CFFD002C4CAB7DFA4386A53264033050A2@DEMUEXC014.nsn-intra.net> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AB3@CNSHGSMBS01.ad4.ad.alcatel.com> <077E41CFFD002C4CAB7DFA4386A53264033051E3@DEMUEXC014.nsn-intra.net> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AF8@CNSHGSMBS01.ad4.ad.alcatel.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>, <stbryant@cisco.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 13 Jan 2011 12:54:09.0802 (UTC) FILETIME=[F8670EA0:01CBB320]
Cc: mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 12:52:00 -0000

Hi Feng,
	You say " HF> I can't image the meaning of cooperation is that ITU-T do nothing and just obey IETF's process!"
It seems that you are not familiar with the agreement on the joint work. The ITU-T experts are called to contribute to (also by the SG15) to assist in the development the development of the protocol in the IETF using the IETF standard processes...
Best regards,
Nurit


-----Original Message-----
From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn] 
Sent: Thursday, January 13, 2011 12:31 PM
To: Sprecher,
 Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; mpls@ietf.org
Cc: mpls-tp@ietf.org
Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]

Hi, Nurit,
   Please see in line.
B.R.
Feng
 

-----Original Message-----
From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.com] 
Sent: 2011$BG/(J1$B7n(J13$BF|(J 17:45
To: HUANG Feng F; stbryant@cisco.com; mpls@ietf.org
Cc: mpls-tp@ietf.org
Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]

Hi Feng,
I did not refer to specific solution, validity and acceptance of a solution, so I cannot see to what you disagree and how your response fit to mine. 
If you think that you have a good solution which is proven and supported please discuss it in the IETF and try to get support for it! 

HF> The solution has been submitted to ietf for 2 year!

I would like the ITU-T to continue with its collaborative agreement with the IETF and ensure that the development of the protocol is done as agreed and supported by SG15 using the IETF processes.

HF> I can't image the meaning of cooperation is that ITU-T do nothing and just obey IETF's process!

I will support a single global solution interoperable solution (whatever the solution is). 
Best regards,
Nurit

-----Original Message-----
From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
Sent: Thursday, January 13, 2011 11:35 AM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; mpls@ietf.org
Cc: mpls-tp@ietf.org
Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]

Hi,Nurit,
   I can't agree with you.
   Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet Transport Network by many applications and public demo and it has many supporters. I am wondering why  this solutions is not  standardized in ietf? 
    Further more,  I really don't agree with your last sentence, this solution is asked by customers in Industry, you can see at least 7 providers in global support this solution.

B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Sprecher, Nurit (NSN - IL/Hod HaSharon)
Sent: 2011$BG/(J1$B7n(J13$BF|(J 16:18
To: stbryant@cisco.com; mpls@ietf.org
Subject: Re: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]

Hi,
I support the proposal.
We have a cooperative agreement with the ITU-T concerning the work on MPLS-TP. 
The agreement recognizes the design authority of the IETF for MPLS and it is agreed that the development of the protocol should be done in the IETF using the IETF processes. The ITU-T should not take any uncoordinated action in the development of the MPLS_TP protocol. 
We would appreciate if the ITU-T continues (as it committed to) with the collaborative work with the IETF on MPLS_TP and contributes from its expertise to the development of the protocol using the IETF processes. 
We would also not like to see two competing solutions which may confuse the Industry, bloat operational and capital expenses and badly affect the end customer. 
Best regards,
Nurit

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of ext Stewart Bryant
Sent: Monday, January 10, 2011 12:57 PM
To: mpls@ietf.org
Subject: [mpls] Draft: Response to Updated draft Recommendation G.tpoam [Ref043.02]

I propose to send the following Liaison Response to the ITU-T on Friday 14th January and am posting it to the MPLS WG list for review.

=======

Response to Updated draft Recommendation G.tpoam [Ref 043.02]

From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, IAB@ietf.org
CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
ghani.abbas@ericsson.com, hhelvoort@huawei.com malcolm.betts@zte.com.cn, kam.lam@alcatel-lucent.com

For Action

The MPLS Working Group notes that this document contains text describing

MPLS-TP OAM protocols not designed and standardized using the IETF Standards process. Specifically it uses material from draft-bhh-mpls-tp-oam-y1731-06.

We wish to draw your attention to the status section of
draft-bhh-mpls-tp-oam-y1731-06 which states:

"Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress".

Please also note that since the draft filename starts with the prefix string "draft-bhh" this clearly identifies it to the reader as a document expressing the personal technical views of the authors and hence hence as a document that that does not have any acknowledged level

of IETF consensus.

Since the text of draft Recommendation for G.tpoam is based on an MPLS-TP OAM protocol not designed within the IETF Standards Process this

is a breach of the SG15 agreement with the IETF as published in Report of the first meeting of Working Party 3/15 Transport network structures
(2009-2012) (Geneva, 1 - 12 December 2008) which can be found at http://www.itu.int/md/T09-SG15-R-0004/en

Please confirm that the ITU-T intends to continue with the joint work on

MPLS-TP and that the ITU-T will align this recommendation with the IETF MPLS-TP OAM design before advancing this document through the ITU-T publication process.

The MPLS Working Group would also like to draw the attention of ITU-T
SG15 to the IETF copyright rules. Please see
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
0091228.htm
for further details.

Since this draft Recommendation contains text in which the ITU-T SG15 has proposed making changes to IETF protocols without the approval of the IETF, the MPLS Working Group have referred this liaison to the IAB for their consideration.


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

From ben@niven-jenkins.co.uk  Thu Jan 13 05:50:26 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B0233A6B89; Thu, 13 Jan 2011 05:50:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.052
X-Spam-Level: 
X-Spam-Status: No, score=-101.052 tagged_above=-999 required=5 tests=[AWL=-2.103, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, J_CHICKENPOX_25=0.6, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-pwhW+LgcXf; Thu, 13 Jan 2011 05:50:24 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id 191733A6B8A; Thu, 13 Jan 2011 05:50:24 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-122-devlan.cachelogic.com) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1PdNbW-00080J-Vn; Thu, 13 Jan 2011 13:52:45 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=GB2312
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AF8@CNSHGSMBS01.ad4.ad.alcatel.com>
Date: Thu, 13 Jan 2011 13:52:40 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FECBFEC-25A5-4EAC-974F-9FD432D1068B@niven-jenkins.co.uk>
References: <4D2AE5E0.90703@cisco.com> <077E41CFFD002C4CAB7DFA4386A53264033050A2@DEMUEXC014.nsn-intra.net> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AB3@CNSHGSMBS01.ad4.ad.alcatel.com> <077E41CFFD002C4CAB7DFA4386A53264033051E3@DEMUEXC014.nsn-intra.net> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AF8@CNSHGSMBS01.ad4.ad.alcatel.com>
To: HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 13:50:26 -0000

Feng, colleagues,

On 13 Jan 2011, at 10:31, HUANG Feng F wrote:
> -----Original Message-----
> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) =
[mailto:nurit.sprecher@nsn.com]=20
> Sent: 2011=C4=EA1=D4=C213=C8=D5 17:45
> To: HUANG Feng F; stbryant@cisco.com; mpls@ietf.org
> Cc: mpls-tp@ietf.org
> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam[Ref043.02]
>=20
> Hi Feng,
> I did not refer to specific solution, validity and acceptance of a =
solution, so I cannot see to what you disagree and how your response fit =
to mine.=20
> If you think that you have a good solution which is proven and =
supported please discuss it in the IETF and try to get support for it!=20=

>=20
> HF> The solution has been submitted to ietf for 2 year!
>=20

We seem to be going round the same loop we've being going round for a =
while.

An OAM solution (draft-bhh) was submitted for consideration and the MPLS =
WG decided to select a different proposal for MPLS-TP OAM. That's life, =
that's how standards development works because standards development is =
"design by committee" and that means that the decisions of the =
"committee" are unlikely to please everyone all of the time.

> I would like the ITU-T to continue with its collaborative agreement =
with the IETF and ensure that the development of the protocol is done as =
agreed and supported by SG15 using the IETF processes.
>=20
> HF> I can't image the meaning of cooperation is that ITU-T do nothing =
and just obey IETF's process!
>=20

It isn't, but that collaborative agreement recognised IETF as being the =
protocol design authority for MPLS & MPLS-TP, which means IETF have the =
final decision on what the MPLS-TP protocols are and how they work.

What you seem to be arguing for is that IETF just obey the demands of =
other organisations, i.e. to paraphrase your argument: "CCSA have used =
draft-bhh in one of their standards so IETF must rubber stamp it as =
being part of MPLS-TP".

It was similar behaviour (ITU-T defining MPLS extensions without =
consultation with IETF) that causes the original bun fight that lead to =
the JWT etc being formed and much time being expended on politics rather =
than technical work to get us to where we are.

I suggest we stop trying to re-ignite a debate as to whether the MPLS-TP =
OAM solution should include draft-bhh or not as the decision has been =
made. Let's accept that decision.

In future if another standards body wants to use an Internet-Draft as =
the basis for one of their standards they would be well advised to =
enquire of the IETF as to the status and likely future of the =
Internet-Draft before making any decisions and we could avoid these =
sorts of situations occurring in the first place.

Ben

P.S. I think the original liaison text is fine as-is.


> I will support a single global solution interoperable solution =
(whatever the solution is).=20
> Best regards,
> Nurit
>=20
> -----Original Message-----
> From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
> Sent: Thursday, January 13, 2011 11:35 AM
> To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; =
mpls@ietf.org
> Cc: mpls-tp@ietf.org
> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam[Ref043.02]
>=20
> Hi,Nurit,
>   I can't agree with you.
>   Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet =
Transport Network by many applications and public demo and it has many =
supporters. I am wondering why  this solutions is not  standardized in =
ietf?=20
>    Further more,  I really don't agree with your last sentence, this =
solution is asked by customers in Industry, you can see at least 7 =
providers in global support this solution.
>=20
> B.R.
> Feng
>=20
>=20
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of Sprecher, Nurit (NSN - IL/Hod HaSharon)
> Sent: 2011=C4=EA1=D4=C213=C8=D5 16:18
> To: stbryant@cisco.com; mpls@ietf.org
> Subject: Re: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam[Ref043.02]
>=20
> Hi,
> I support the proposal.
> We have a cooperative agreement with the ITU-T concerning the work on =
MPLS-TP.=20
> The agreement recognizes the design authority of the IETF for MPLS and =
it is agreed that the development of the protocol should be done in the =
IETF using the IETF processes. The ITU-T should not take any =
uncoordinated action in the development of the MPLS_TP protocol.=20
> We would appreciate if the ITU-T continues (as it committed to) with =
the collaborative work with the IETF on MPLS_TP and contributes from its =
expertise to the development of the protocol using the IETF processes.=20=

> We would also not like to see two competing solutions which may =
confuse the Industry, bloat operational and capital expenses and badly =
affect the end customer.=20
> Best regards,
> Nurit
>=20
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of ext Stewart Bryant
> Sent: Monday, January 10, 2011 12:57 PM
> To: mpls@ietf.org
> Subject: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam [Ref043.02]
>=20
> I propose to send the following Liaison Response to the ITU-T on =
Friday 14th January and am posting it to the MPLS WG list for review.
>=20
> =3D=3D=3D=3D=3D=3D=3D
>=20
> Response to Updated draft Recommendation G.tpoam [Ref 043.02]
>=20
> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
> To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, =
IAB@ietf.org
> CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com =
stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org =
yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
> ghani.abbas@ericsson.com, hhelvoort@huawei.com =
malcolm.betts@zte.com.cn, kam.lam@alcatel-lucent.com
>=20
> For Action
>=20
> The MPLS Working Group notes that this document contains text =
describing
>=20
> MPLS-TP OAM protocols not designed and standardized using the IETF =
Standards process. Specifically it uses material from =
draft-bhh-mpls-tp-oam-y1731-06.
>=20
> We wish to draw your attention to the status section of
> draft-bhh-mpls-tp-oam-y1731-06 which states:
>=20
> "Internet-Drafts are draft documents valid for a maximum of six months =
and may be updated, replaced, or obsoleted by other documents at any =
time. It is inappropriate to use Internet-Drafts as reference material =
or to cite them other than as "work in progress".
>=20
> Please also note that since the draft filename starts with the prefix =
string "draft-bhh" this clearly identifies it to the reader as a =
document expressing the personal technical views of the authors and =
hence hence as a document that that does not have any acknowledged level
>=20
> of IETF consensus.
>=20
> Since the text of draft Recommendation for G.tpoam is based on an =
MPLS-TP OAM protocol not designed within the IETF Standards Process this
>=20
> is a breach of the SG15 agreement with the IETF as published in Report =
of the first meeting of Working Party 3/15 Transport network structures
> (2009-2012) (Geneva, 1 - 12 December 2008) which can be found at =
http://www.itu.int/md/T09-SG15-R-0004/en
>=20
> Please confirm that the ITU-T intends to continue with the joint work =
on
>=20
> MPLS-TP and that the ITU-T will align this recommendation with the =
IETF MPLS-TP OAM design before advancing this document through the ITU-T =
publication process.
>=20
> The MPLS Working Group would also like to draw the attention of ITU-T
> SG15 to the IETF copyright rules. Please see
> =
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
> 0091228.htm
> for further details.
>=20
> Since this draft Recommendation contains text in which the ITU-T SG15 =
has proposed making changes to IETF protocols without the approval of =
the IETF, the MPLS Working Group have referred this liaison to the IAB =
for their consideration.
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From Alexander.Vainshtein@ecitele.com  Thu Jan 13 06:05:50 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C0153A6B27; Thu, 13 Jan 2011 06:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.786
X-Spam-Level: 
X-Spam-Status: No, score=-1.786 tagged_above=-999 required=5 tests=[AWL=-0.387, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, J_CHICKENPOX_25=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQ2nc+T022vx; Thu, 13 Jan 2011 06:05:48 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id AF6A83A6B2C; Thu, 13 Jan 2011 06:05:47 -0800 (PST)
X-AuditID: 93eaf2e7-b7c67ae0000028de-ca-4d2f074ba9f2
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id B0.15.10462.B470F2D4; Thu, 13 Jan 2011 16:08:11 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Thu, 13 Jan 2011 16:08:07 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Thu, 13 Jan 2011 16:09:51 +0200
Thread-Topic: [mpls] Draft: Response to Updated draft Recommendation G.tpoam[Ref043.02]
Thread-Index: AcuzKS0sCnEzojKMRA2BY4fOGvXd7QAAiPEA
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6B87734B7@ILPTMAIL02.ecitele.com>
References: <4D2AE5E0.90703@cisco.com> <077E41CFFD002C4CAB7DFA4386A53264033050A2@DEMUEXC014.nsn-intra.net> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AB3@CNSHGSMBS01.ad4.ad.alcatel.com> <077E41CFFD002C4CAB7DFA4386A53264033051E3@DEMUEXC014.nsn-intra.net> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AF8@CNSHGSMBS01.ad4.ad.alcatel.com> <2FECBFEC-25A5-4EAC-974F-9FD432D1068B@niven-jenkins.co.uk>
In-Reply-To: <2FECBFEC-25A5-4EAC-974F-9FD432D1068B@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAhcg2WYXIYuT
Cc: "mpls@ietf.org" <mpls@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation	G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 14:05:50 -0000

Ben, all,

It has been said that design of standards by committee is the worst form of=
 design except all those other forms that have been tried from time to time=
...

Regards,
     Sasha


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Ben=
 Niven-Jenkins
Sent: Thursday, January 13, 2011 3:53 PM
To: HUANG Feng F
Cc: mpls@ietf.org; mpls-tp@ietf.org; stbryant@cisco.com
Subject: Re: [mpls] Draft: Response to Updated draft Recommendation G.tpoam=
[Ref043.02]

Feng, colleagues,

On 13 Jan 2011, at 10:31, HUANG Feng F wrote:
> -----Original Message-----
> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.=
com]=20
> Sent: 2011=1B$BG/=1B(B1=1B$B7n=1B(B13=1B$BF|=1B(B 17:45
> To: HUANG Feng F; stbryant@cisco.com; mpls@ietf.org
> Cc: mpls-tp@ietf.org
> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpo=
am[Ref043.02]
>=20
> Hi Feng,
> I did not refer to specific solution, validity and acceptance of a soluti=
on, so I cannot see to what you disagree and how your response fit to mine.=
=20
> If you think that you have a good solution which is proven and supported =
please discuss it in the IETF and try to get support for it!=20
>=20
> HF> The solution has been submitted to ietf for 2 year!
>=20

We seem to be going round the same loop we've being going round for a while=
.

An OAM solution (draft-bhh) was submitted for consideration and the MPLS WG=
 decided to select a different proposal for MPLS-TP OAM. That's life, that'=
s how standards development works because standards development is "design =
by committee" and that means that the decisions of the "committee" are unli=
kely to please everyone all of the time.

> I would like the ITU-T to continue with its collaborative agreement with =
the IETF and ensure that the development of the protocol is done as agreed =
and supported by SG15 using the IETF processes.
>=20
> HF> I can't image the meaning of cooperation is that ITU-T do nothing and=
 just obey IETF's process!
>=20

It isn't, but that collaborative agreement recognised IETF as being the pro=
tocol design authority for MPLS & MPLS-TP, which means IETF have the final =
decision on what the MPLS-TP protocols are and how they work.

What you seem to be arguing for is that IETF just obey the demands of other=
 organisations, i.e. to paraphrase your argument: "CCSA have used draft-bhh=
 in one of their standards so IETF must rubber stamp it as being part of MP=
LS-TP".

It was similar behaviour (ITU-T defining MPLS extensions without consultati=
on with IETF) that causes the original bun fight that lead to the JWT etc b=
eing formed and much time being expended on politics rather than technical =
work to get us to where we are.

I suggest we stop trying to re-ignite a debate as to whether the MPLS-TP OA=
M solution should include draft-bhh or not as the decision has been made. L=
et's accept that decision.

In future if another standards body wants to use an Internet-Draft as the b=
asis for one of their standards they would be well advised to enquire of th=
e IETF as to the status and likely future of the Internet-Draft before maki=
ng any decisions and we could avoid these sorts of situations occurring in =
the first place.

Ben

P.S. I think the original liaison text is fine as-is.


> I will support a single global solution interoperable solution (whatever =
the solution is).=20
> Best regards,
> Nurit
>=20
> -----Original Message-----
> From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
> Sent: Thursday, January 13, 2011 11:35 AM
> To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; mpls@iet=
f.org
> Cc: mpls-tp@ietf.org
> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpo=
am[Ref043.02]
>=20
> Hi,Nurit,
>   I can't agree with you.
>   Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet Transp=
ort Network by many applications and public demo and it has many supporters=
. I am wondering why  this solutions is not  standardized in ietf?=20
>    Further more,  I really don't agree with your last sentence, this solu=
tion is asked by customers in Industry, you can see at least 7 providers in=
 global support this solution.
>=20
> B.R.
> Feng
>=20
>=20
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of S=
precher, Nurit (NSN - IL/Hod HaSharon)
> Sent: 2011=1B$BG/=1B(B1=1B$B7n=1B(B13=1B$BF|=1B(B 16:18
> To: stbryant@cisco.com; mpls@ietf.org
> Subject: Re: [mpls] Draft: Response to Updated draft Recommendation G.tpo=
am[Ref043.02]
>=20
> Hi,
> I support the proposal.
> We have a cooperative agreement with the ITU-T concerning the work on MPL=
S-TP.=20
> The agreement recognizes the design authority of the IETF for MPLS and it=
 is agreed that the development of the protocol should be done in the IETF =
using the IETF processes. The ITU-T should not take any uncoordinated actio=
n in the development of the MPLS_TP protocol.=20
> We would appreciate if the ITU-T continues (as it committed to) with the =
collaborative work with the IETF on MPLS_TP and contributes from its expert=
ise to the development of the protocol using the IETF processes.=20
> We would also not like to see two competing solutions which may confuse t=
he Industry, bloat operational and capital expenses and badly affect the en=
d customer.=20
> Best regards,
> Nurit
>=20
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of e=
xt Stewart Bryant
> Sent: Monday, January 10, 2011 12:57 PM
> To: mpls@ietf.org
> Subject: [mpls] Draft: Response to Updated draft Recommendation G.tpoam [=
Ref043.02]
>=20
> I propose to send the following Liaison Response to the ITU-T on Friday 1=
4th January and am posting it to the MPLS WG list for review.
>=20
> =3D=3D=3D=3D=3D=3D=3D
>=20
> Response to Updated draft Recommendation G.tpoam [Ref 043.02]
>=20
> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
> To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, IAB@ietf.or=
g
> CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com stbryant@cisc=
o.com, adrian.farrel@huawei.com, mpls@ietf.org yoichi.maeda@ttc.or.jp, stev=
e.trowbridge@alcatel-lucent.com
> ghani.abbas@ericsson.com, hhelvoort@huawei.com malcolm.betts@zte.com.cn, =
kam.lam@alcatel-lucent.com
>=20
> For Action
>=20
> The MPLS Working Group notes that this document contains text describing
>=20
> MPLS-TP OAM protocols not designed and standardized using the IETF Standa=
rds process. Specifically it uses material from draft-bhh-mpls-tp-oam-y1731=
-06.
>=20
> We wish to draw your attention to the status section of
> draft-bhh-mpls-tp-oam-y1731-06 which states:
>=20
> "Internet-Drafts are draft documents valid for a maximum of six months an=
d may be updated, replaced, or obsoleted by other documents at any time. It=
 is inappropriate to use Internet-Drafts as reference material or to cite t=
hem other than as "work in progress".
>=20
> Please also note that since the draft filename starts with the prefix str=
ing "draft-bhh" this clearly identifies it to the reader as a document expr=
essing the personal technical views of the authors and hence hence as a doc=
ument that that does not have any acknowledged level
>=20
> of IETF consensus.
>=20
> Since the text of draft Recommendation for G.tpoam is based on an MPLS-TP=
 OAM protocol not designed within the IETF Standards Process this
>=20
> is a breach of the SG15 agreement with the IETF as published in Report of=
 the first meeting of Working Party 3/15 Transport network structures
> (2009-2012) (Geneva, 1 - 12 December 2008) which can be found at http://w=
ww.itu.int/md/T09-SG15-R-0004/en
>=20
> Please confirm that the ITU-T intends to continue with the joint work on
>=20
> MPLS-TP and that the ITU-T will align this recommendation with the IETF M=
PLS-TP OAM design before advancing this document through the ITU-T publicat=
ion process.
>=20
> The MPLS Working Group would also like to draw the attention of ITU-T
> SG15 to the IETF copyright rules. Please see
> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
> 0091228.htm
> for further details.
>=20
> Since this draft Recommendation contains text in which the ITU-T SG15 has=
 proposed making changes to IETF protocols without the approval of the IETF=
, the MPLS Working Group have referred this liaison to the IAB for their co=
nsideration.
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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

From larryli888@yahoo.com.cn  Thu Jan 13 06:53:16 2011
Return-Path: <larryli888@yahoo.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DCC428C0DB for <mpls-tp@core3.amsl.com>; Thu, 13 Jan 2011 06:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.073
X-Spam-Level: 
X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cmhyAsdUrD52 for <mpls-tp@core3.amsl.com>; Thu, 13 Jan 2011 06:53:15 -0800 (PST)
Received: from web15605.mail.cnb.yahoo.com (web15605.mail.cnb.yahoo.com [202.165.102.59]) by core3.amsl.com (Postfix) with SMTP id 706FF28C0E3 for <mpls-tp@ietf.org>; Thu, 13 Jan 2011 06:53:14 -0800 (PST)
Received: (qmail 56841 invoked by uid 60001); 13 Jan 2011 14:55:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.cn; s=s1024; t=1294930531; bh=6UmjHEMTc1iq3ioFKoMGK6N+kZvp10dnpCJLR8n+B6U=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ka/wvzssMSqlWH/IbCxjrr6LAeltheZdAc9AUhMZM2+PS0IJj47znmuMGOx9mNUkxZv1I0nX12KuYVmpE2is7dayB9584Eja2QyhlWWiz/AVJBA4iCTgA6/frUOsvyRR7UBggWuSP5IA75mftxssXfUebXcuktwc+grmb6Ldv8I=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.cn; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vYy652xcB2kju3mk+z3IqEC+vJOe61yS7Cq3J7SE8VI7RiarKg3cJBIVQX3pKpZFulUfOPGozfULWFRyMrYaJf7is5Q1/GW3h2icfZXFhmtqZeCeWEPTgLWDpw09ugb9HLKVmssXprx+s0cWn3BpLVfGeOwHn0omPbNOogVk9u0=;
Message-ID: <526321.56478.qm@web15605.mail.cnb.yahoo.com>
X-YMail-OSG: jz0jIGoVM1nXK3dqnXMM7RFZ9eztXc2sGKMbUtafPLk6qN1 BUp_.A7wvNgLWgl6b7qwmfW35tA0q.1tZqxHSlR3x0DuCYblgaPPx2Ub9rsZ XUk.a8aKvqxkKwa4zwhxuhVyMiVwvendwOrO82rwaKVMVg1tmC1.tPhETkTh OrozDzvEJQd2OIfM1r8u72fq.0IXjHqZdhT3G5EewxxXC9PepQpYLWmBsgtl BE1ftUAcfZm1GFemUQZn0pvVAj0TxhxtdydpAaHRydwcMAML0E1A-
Received: from [211.160.76.213] by web15605.mail.cnb.yahoo.com via HTTP; Thu, 13 Jan 2011 22:55:31 CST
X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.107.285259
Date: Thu, 13 Jan 2011 22:55:31 +0800 (CST)
From: Larry <larryli888@yahoo.com.cn>
To: jingr@ties.itu.ch, ruiquan.jing@ties.itu.int
In-Reply-To: <1294906173.4d2eb33dd1ffa@gold.itu.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 14:53:16 -0000

Hi,

    I don't think it is proper to send the LS to ITU-T because the text doe=
sn't reflect the requirement from providers.
    Apparently, draft-bhh based OAM is the most mature solution currently. =
It has been proved by more than 200,000 applications and is supported by a =
lot of operators and vendors.=20
   =20
Best regards,

              Han Li

*************************************************************************
Han Li, Ph.D=20
China Mobile Research Institute
Unit 2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China=20
Fax: +86 10 63601087=20
MOBILE: 13501093385=20
*************************************************************************


--- 11=E5=B9=B41=E6=9C=8813=E6=97=A5=EF=BC=8C=E5=91=A8=E5=9B=9B, ruiquan.ji=
ng@ties.itu.int <ruiquan.jing@ties.itu.int> =E5=86=99=E9=81=93=EF=BC=9A

> =E5=8F=91=E4=BB=B6=E4=BA=BA: ruiquan.jing@ties.itu.int <ruiquan.jing@ties=
.itu.int>
> =E4=B8=BB=E9=A2=98: Re: [mpls-tp] [mpls] Draft: Response to Updated draft=
 Recommendation G.tpoam [Ref043.02]
> =E6=94=B6=E4=BB=B6=E4=BA=BA: jingr@ties.itu.ch
> =E6=8A=84=E9=80=81: mpls-tp@ietf.org
> =E6=97=A5=E6=9C=9F: 2011=E5=B9=B41=E6=9C=8813=E6=97=A5,=E5=91=A8=E5=9B=9B=
,=E4=B8=8B=E5=8D=884:09
> Resend to mpls-tp list.
>=20
> Quoting jingr@ties.itu.ch:
>=20
> > Hi Stewart Bryant,
> >=20
> > I don=E2=80=99t agree with the current LS text.
> >=20
> > China Telecom support the standardization of Y.1731
> based MPLS-TP OAM tools
> > in=20
> > the ITU-T to meet the urgent and increasing
> requirements for PTN deployment.=20
> >=20
> > It=E2=80=99s a multi-vendor supported, interoperability
> certificated and feasible=20
> > solution.=C2=A0 It had been specified in both CCSA
> (China Communications Standards
> >=20
> > Association) and China Telecom=E2=80=99s PTN standard as the
> only standard OAM=20
> > mechanism.
> >=20
> >=C2=A0=20
> >=20
> > Best Regards
> >=20
> > Jing Ruiquan
> >=20
> > China=E3=80=80Telecom=C2=A0 Beijing=C2=A0
> Research=E3=80=80Institute
> >=20
> >
> -------------------------------------------------------------------------=
-----
> --
> > From: mpls-bounces@ietf.org
> [mailto:mpls-bounces@ietf.org]
> On Behalf Of
> > Stewart=20
> > Bryant
> > Sent: Monday, January 10, 2011 6:57 PM
> > To: mpls@ietf.org
> > Subject: [mpls] Draft: Response to Updated draft
> Recommendation G.tpoam=20
> > [Ref043.02]
> >=20
> >=20
> > I propose to send the following Liaison Response to
> the ITU-T on Friday=20
> > 14th January and am posting it to the MPLS WG list for
> review.=20
> >=20
> > =3D=3D=3D=3D=3D=3D=3D=20
> >=20
> > Response to Updated draft Recommendation G.tpoam [Ref
> 043.02]=20
> >=20
> > From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>=20
> > To: tsbsg15@itu.int,
> greg.jones@itu.int,
> hiroshi.ota@itu.int,
> IAB@ietf.org=20
> > CC: Greg Jones, swallow@cisco.com,
> loa@pi.nu, paf@cisco.com=20
> > stbryant@cisco.com,
> adrian.farrel@huawei.com,
> mpls@ietf.org=20
> > yoichi.maeda@ttc.or.jp,
> steve.trowbridge@alcatel-lucent.com
>=20
> > ghani.abbas@ericsson.com,
> hhelvoort@huawei.com
>=20
> > malcolm.betts@zte.com.cn,
> kam.lam@alcatel-lucent.com
>=20
> >=20
> > For Action=20
> >=20
> > The MPLS Working Group notes that this document
> contains text describing=20
> > MPLS-TP OAM protocols not designed and standardized
> using the IETF=20
> > Standards process. Specifically it uses material from
>=20
> > draft-bhh-mpls-tp-oam-y1731-06.=20
> >=20
> > We wish to draw your attention to the status section
> of=20
> > draft-bhh-mpls-tp-oam-y1731-06 which states:=20
> >=20
> > "Internet-Drafts are draft documents valid for a
> maximum of six months=20
> > and may be updated, replaced, or obsoleted by other
> documents at any=20
> > time. It is inappropriate to use Internet-Drafts as
> reference material=20
> > or to cite them other than as "work in progress".=20
> >=20
> > Please also note that since the draft filename starts
> with the prefix=20
> > string "draft-bhh" this clearly identifies it to the
> reader as a=20
> > document expressing the personal technical views of
> the authors and=20
> > hence hence as a document that that does not have any
> acknowledged level=20
> > of IETF consensus.=20
> >=20
> > Since the text of draft Recommendation for G.tpoam is
> based on an=20
> > MPLS-TP OAM protocol not designed within the IETF
> Standards Process this=20
> > is a breach of the SG15 agreement with the IETF as
> published in Report=20
> > of the first meeting of Working Party 3/15 Transport
> network structures=20
> > (2009-2012) (Geneva, 1 =E2=80=93 12 December 2008) which can
> be found at=20
> > http://www.itu.int/md/T09-SG15-R-0004/en
>=20
> >=20
> > Please confirm that the ITU-T intends to continue with
> the joint work on=20
> > MPLS-TP and that the ITU-T will align this
> recommendation with the IETF=20
> > MPLS-TP OAM design before advancing this document
> through the ITU-T=20
> > publication process.=20
> >=20
> > The MPLS Working Group would also like to draw the
> attention of ITU-T=20
> > SG15 to the IETF copyright rules. Please see=20
> > http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-
> > 20091228.htm=20
> > for further details.=20
> >=20
> > Since this draft Recommendation contains text in which
> the ITU-T SG15=20
> > has proposed making changes to IETF protocols without
> the approval of=20
> > the IETF, the MPLS Working Group have referred this
> liaison to the IAB=20
> > for their consideration.=20
> >=20
> >=20
> >=20
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=20
> > _______________________________________________=20
> > mpls mailing list=20
> > mpls@ietf.org=20
> > https://www.ietf.org/mailman/listinfo/mpls=20
> >=20
> >=20
> >=20
>=20
>=20
>=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> =0A=0A=0A      

From lufang@cisco.com  Thu Jan 13 06:59:21 2011
Return-Path: <lufang@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B61A28C0DB; Thu, 13 Jan 2011 06:59:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, J_CHICKENPOX_25=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfqKKYZgJdhD; Thu, 13 Jan 2011 06:59:19 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id CDF803A6B9A; Thu, 13 Jan 2011 06:59:18 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPSiLk2tJXHB/2dsb2JhbACECKA/c6QuilABjhGBHoM3dwSEaIlQ
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rtp-iport-1.cisco.com with ESMTP; 13 Jan 2011 15:01:40 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p0DF1eG9001736;  Thu, 13 Jan 2011 15:01:40 GMT
Received: from xmb-rcd-201.cisco.com ([72.163.62.208]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 13 Jan 2011 09:01:40 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Jan 2011 09:01:38 -0600
Message-ID: <238542D917511A45B6B8AA806E875E25041C4A04@XMB-RCD-201.cisco.com>
In-Reply-To: <2FECBFEC-25A5-4EAC-974F-9FD432D1068B@niven-jenkins.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [mpls] Draft: Response to Updated draftRecommendation G.tpoam[Ref043.02]
Thread-Index: AcuzKTZq2jnBERhwR6aVB5jHpXiUDgAAP+ng
References: <4D2AE5E0.90703@cisco.com><077E41CFFD002C4CAB7DFA4386A53264033050A2@DEMUEXC014.nsn-intra.net><FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AB3@CNSHGSMBS01.ad4.ad.alcatel.com><077E41CFFD002C4CAB7DFA4386A53264033051E3@DEMUEXC014.nsn-intra.net><FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9AF8@CNSHGSMBS01.ad4.ad.alcatel.com> <2FECBFEC-25A5-4EAC-974F-9FD432D1068B@niven-jenkins.co.uk>
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk>, "HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>, "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
X-OriginalArrivalTime: 13 Jan 2011 15:01:40.0334 (UTC) FILETIME=[C87998E0:01CBB332]
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draftRecommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 14:59:21 -0000

Well said, Ben and Nurit.

I support the proposal Stewart sent.

Let's reiterate the IETF process here.

IETF has published a number of RFCs that specify the procedures for external bodies to request the modification of IETF protocols.

[RFC 4775] $B!H(JProcedures for Protocol Extensions and Variations$B!I(J lays down the guideline and procedures for protocols extensions. It recommends that major extensions to or variations of IETF protocols only take place through normal IETF processes or in coordination with IETF. This document is directed principally at other SDOs and vendors considering extensions to IETF protocols.

[RFC 4929] specifies the change process for MPLS, GMPLS protocols and procedures. It indicates the definition and publishing of non-standard extension by other fora without IETF review, and outside of IETF publication process, regardless if rationalized as limited to use among fora vendors, or limited to a particular application, or rationalized as allowing timely demos, has the unfortunate potential to hinder interoperability and increase complexity, sows confusion in the industry, and circumvents the Internet standards process that exists to ensure protocol implementability.

As described in [RFC4775] and [RFC 4929], any non-standard extensions to IETF protocols, including experimental values, are not to be portrayed as industrial standards whether by an individual vendor, an industry forum, or a standards body. Standard extensions to IETF protocols must be reviewed and published by IETF. Extensions to MPLS(-TP) protocols made outside of IETF creates a great risk of interoperability.

How could any other SDOs standardize something that extend IETF MPLS protocols without IETF's agreement, nor IANA issued code point?

The process issue was the reason for IETF/ITU-T agreements for joint development for MPLS-TP two years ago. 

In Beijing IETF 79, November 2011, IETF Chair Russ Housley said clearly in the MPLS WG meeting that IETF decided to support one MPLS-TP OAM solution only. 

We all heard that, let's move on.

You can do things elsewhere if not extending/modifying IETF protocols.

Luyuan
 

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Ben Niven-Jenkins
Sent: 13 January 2011 08:53
To: HUANG Feng F
Cc: mpls@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draftRecommendation G.tpoam[Ref043.02]

Feng, colleagues,

On 13 Jan 2011, at 10:31, HUANG Feng F wrote:
> -----Original Message-----
> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) 
> [mailto:nurit.sprecher@nsn.com]
> Sent: 2011$BG/(J1$B7n(J13$BF|(J 17:45
> To: HUANG Feng F; stbryant@cisco.com; mpls@ietf.org
> Cc: mpls-tp@ietf.org
> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation 
> G.tpoam[Ref043.02]
> 
> Hi Feng,
> I did not refer to specific solution, validity and acceptance of a solution, so I cannot see to what you disagree and how your response fit to mine. 
> If you think that you have a good solution which is proven and supported please discuss it in the IETF and try to get support for it! 
> 
> HF> The solution has been submitted to ietf for 2 year!
> 

We seem to be going round the same loop we've being going round for a while.

An OAM solution (draft-bhh) was submitted for consideration and the MPLS WG decided to select a different proposal for MPLS-TP OAM. That's life, that's how standards development works because standards development is "design by committee" and that means that the decisions of the "committee" are unlikely to please everyone all of the time.

> I would like the ITU-T to continue with its collaborative agreement with the IETF and ensure that the development of the protocol is done as agreed and supported by SG15 using the IETF processes.
> 
> HF> I can't image the meaning of cooperation is that ITU-T do nothing and just obey IETF's process!
> 

It isn't, but that collaborative agreement recognised IETF as being the protocol design authority for MPLS & MPLS-TP, which means IETF have the final decision on what the MPLS-TP protocols are and how they work.

What you seem to be arguing for is that IETF just obey the demands of other organisations, i.e. to paraphrase your argument: "CCSA have used draft-bhh in one of their standards so IETF must rubber stamp it as being part of MPLS-TP".

It was similar behaviour (ITU-T defining MPLS extensions without consultation with IETF) that causes the original bun fight that lead to the JWT etc being formed and much time being expended on politics rather than technical work to get us to where we are.

I suggest we stop trying to re-ignite a debate as to whether the MPLS-TP OAM solution should include draft-bhh or not as the decision has been made. Let's accept that decision.

In future if another standards body wants to use an Internet-Draft as the basis for one of their standards they would be well advised to enquire of the IETF as to the status and likely future of the Internet-Draft before making any decisions and we could avoid these sorts of situations occurring in the first place.

Ben

P.S. I think the original liaison text is fine as-is.


> I will support a single global solution interoperable solution (whatever the solution is). 
> Best regards,
> Nurit
> 
> -----Original Message-----
> From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
> Sent: Thursday, January 13, 2011 11:35 AM
> To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; 
> mpls@ietf.org
> Cc: mpls-tp@ietf.org
> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation 
> G.tpoam[Ref043.02]
> 
> Hi,Nurit,
>   I can't agree with you.
>   Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet Transport Network by many applications and public demo and it has many supporters. I am wondering why  this solutions is not  standardized in ietf? 
>    Further more,  I really don't agree with your last sentence, this solution is asked by customers in Industry, you can see at least 7 providers in global support this solution.
> 
> B.R.
> Feng
> 
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf 
> Of Sprecher, Nurit (NSN - IL/Hod HaSharon)
> Sent: 2011$BG/(J1$B7n(J13$BF|(J 16:18
> To: stbryant@cisco.com; mpls@ietf.org
> Subject: Re: [mpls] Draft: Response to Updated draft Recommendation 
> G.tpoam[Ref043.02]
> 
> Hi,
> I support the proposal.
> We have a cooperative agreement with the ITU-T concerning the work on MPLS-TP. 
> The agreement recognizes the design authority of the IETF for MPLS and it is agreed that the development of the protocol should be done in the IETF using the IETF processes. The ITU-T should not take any uncoordinated action in the development of the MPLS_TP protocol. 
> We would appreciate if the ITU-T continues (as it committed to) with the collaborative work with the IETF on MPLS_TP and contributes from its expertise to the development of the protocol using the IETF processes. 
> We would also not like to see two competing solutions which may confuse the Industry, bloat operational and capital expenses and badly affect the end customer. 
> Best regards,
> Nurit
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf 
> Of ext Stewart Bryant
> Sent: Monday, January 10, 2011 12:57 PM
> To: mpls@ietf.org
> Subject: [mpls] Draft: Response to Updated draft Recommendation 
> G.tpoam [Ref043.02]
> 
> I propose to send the following Liaison Response to the ITU-T on Friday 14th January and am posting it to the MPLS WG list for review.
> 
> =======
> 
> Response to Updated draft Recommendation G.tpoam [Ref 043.02]
> 
> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
> To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, 
> IAB@ietf.org
> CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com 
> stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org 
> yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
> ghani.abbas@ericsson.com, hhelvoort@huawei.com 
> malcolm.betts@zte.com.cn, kam.lam@alcatel-lucent.com
> 
> For Action
> 
> The MPLS Working Group notes that this document contains text 
> describing
> 
> MPLS-TP OAM protocols not designed and standardized using the IETF Standards process. Specifically it uses material from draft-bhh-mpls-tp-oam-y1731-06.
> 
> We wish to draw your attention to the status section of
> draft-bhh-mpls-tp-oam-y1731-06 which states:
> 
> "Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress".
> 
> Please also note that since the draft filename starts with the prefix 
> string "draft-bhh" this clearly identifies it to the reader as a 
> document expressing the personal technical views of the authors and 
> hence hence as a document that that does not have any acknowledged 
> level
> 
> of IETF consensus.
> 
> Since the text of draft Recommendation for G.tpoam is based on an 
> MPLS-TP OAM protocol not designed within the IETF Standards Process 
> this
> 
> is a breach of the SG15 agreement with the IETF as published in Report 
> of the first meeting of Working Party 3/15 Transport network 
> structures
> (2009-2012) (Geneva, 1 - 12 December 2008) which can be found at 
> http://www.itu.int/md/T09-SG15-R-0004/en
> 
> Please confirm that the ITU-T intends to continue with the joint work 
> on
> 
> MPLS-TP and that the ITU-T will align this recommendation with the IETF MPLS-TP OAM design before advancing this document through the ITU-T publication process.
> 
> The MPLS Working Group would also like to draw the attention of ITU-T
> SG15 to the IETF copyright rules. Please see
> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy
> -2
> 0091228.htm
> for further details.
> 
> Since this draft Recommendation contains text in which the ITU-T SG15 has proposed making changes to IETF protocols without the approval of the IETF, the MPLS Working Group have referred this liaison to the IAB for their consideration.
> 
> 
> =========
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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

From nurit.sprecher@nsn.com  Thu Jan 13 07:28:32 2011
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45B2D3A6B3F; Thu, 13 Jan 2011 07:28:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.325
X-Spam-Level: 
X-Spam-Status: No, score=-4.325 tagged_above=-999 required=5 tests=[AWL=1.673,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbx-ivxjL9Z4; Thu, 13 Jan 2011 07:28:30 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 3DFE33A69B9; Thu, 13 Jan 2011 07:28:29 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0DFUob5024072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Jan 2011 16:30:50 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0DFUnHd004187; Thu, 13 Jan 2011 16:30:50 +0100
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 13 Jan 2011 16:30:41 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBB336.D57B1EC7"
Date: Thu, 13 Jan 2011 16:30:32 +0100
Message-ID: <077E41CFFD002C4CAB7DFA4386A53264033056FB@DEMUEXC014.nsn-intra.net>
In-Reply-To: <526321.56478.qm@web15605.mail.cnb.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [mpls] Draft: Response to Updated draftRecommendation G.tpoam [Ref043.02]
Thread-Index: AcuzMfUF0Qh1GFyISiuucMDLFyKA0AAAz/Zg
References: <1294906173.4d2eb33dd1ffa@gold.itu.ch> <526321.56478.qm@web15605.mail.cnb.yahoo.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Larry" <larryli888@yahoo.com.cn>, <jingr@ties.itu.ch>, <ruiquan.jing@ties.itu.int>
X-OriginalArrivalTime: 13 Jan 2011 15:30:41.0061 (UTC) FILETIME=[D6077550:01CBB336]
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draftRecommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 15:28:32 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBB336.D57B1EC7
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SGFuIExpLA0KDQpQbGVhc2Ugbm90ZSB0aGF0IHRoaXMgbGlhaXNvbiBpcyBub3QgaW50ZW5kZWQg
dG8gZ2V0IGludG8gdGVjaG5pY2FsIGRpc2N1c3Npb24gb3IgaW50byBTUHMnIHJlcXVpcmVtZW50
cy4gDQoNCkl0IGlzIG1vcmUgb24gdGhlIHByb2NlZHVyZXMgYW5kIHByb2Nlc3Nlcy4uLi4NCg0K
QWNjb3JkaW5nIHRvIHRoZSBjb2xsYWJvcmF0aXZlIGFncmVlbWVudCBiZXR3ZWVuIHRoZSBJVFUt
VCBhbmQgdGhlIElFVEYgKHdoaWNoIHdhcyBhY2NlcHRlZCBieSBJVFUtVCBTRzE1IGluIERlY2Vt
YmVyIDIwMDgpLCB0aGUgZGV2ZWxvcG1lbnQgb2YgdGhlIHByb3RvY29sIHNob3VsZCBiZSBkb25l
IGluIHRoZSBJRVRGIHVzaW5nIHRoZSBJRVRGIHByb2Nlc3Nlcy4gVGhlIElUVS1UIGRvY3VtZW50
cyBzaG91bGQgcmVmZXIgdG8gdGhlIElFVEYgc29sdXRpb25zLiANCg0KV2Ugbm90ZSBhIGRvY3Vt
ZW50ICh1bmRlciBkZXZlbG9wbWVudCkgaW4gdGhlIElUVS1UIChnLnRwb2FtKSwgd2hpY2ggaW5j
bHVkZXMgdGhlIGRlZmluaXRpb24gb2YgbWVzc2FnZXMgYW5kIHByb2NlZHVyZXMgZm9yIE1TUEwt
VFAgd2hpY2ggd2VyZSBub3QgZGV2ZWxvcGVkIHVzaW5nIHRoZSBJRVRGIHN0YW5kYXJkIHByb2Nl
c3NlcyBhbmQgZG9lcyBub3QgZm9sbG93IHRoZSBJRVRGIGNoYW5nZS9leHRlbnNpb24gcHJvY2Vz
c2VzLiBUaGlzIGlzIGNvbnRyYXJ5IHRvIHRoZSBhZ3JlZW1lbnQgYmV0d2VlbiB0aGUgSUVURiBh
bmQgdGhlIElUVS1UIGZyb20gRGVjZW1iZXIgMjAwOC4gDQoNCldlIGFyZSByZXNwb25kaW5nIG9u
IHRoZSBwcm9jZXNzIGFuZCB3YW50IHRvIGJlIHN1cmUgKGFuZCBob3BlKSB0aGF0IHRoZSBJVFUt
VCBpbnRlbmRzIHRvIGNvbnRpbnVlIHdpdGggdGhlIGpvaW50IHdvcmsgb24gTVBMUy1UUCBhcyBh
Z3JlZWQgb24gaW4gRGVjZW1iZXIgMjAwOC4gDQoNCkkgdGhpbmsgdGhlIGxpYWlzb24gaXMgdmVy
eSB3ZWxsIHdyaXR0ZW4hDQoNCkJlc3QgcmVnYXJkcywNCg0KTnVyaXQNCg0KIA0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogbXBscy10cC1ib3VuY2VzQGlldGYub3JnIFttYWls
dG86bXBscy10cC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgZXh0IExhcnJ5DQpTZW50
OiBUaHVyc2RheSwgSmFudWFyeSAxMywgMjAxMSA0OjU2IFBNDQpUbzogamluZ3JAdGllcy5pdHUu
Y2g7IHJ1aXF1YW4uamluZ0B0aWVzLml0dS5pbnQNCkNjOiBtcGxzQGlldGYub3JnOyBtcGxzLXRw
QGlldGYub3JnDQpTdWJqZWN0OiBSZTogW21wbHMtdHBdIFttcGxzXSBEcmFmdDogUmVzcG9uc2Ug
dG8gVXBkYXRlZCBkcmFmdFJlY29tbWVuZGF0aW9uIEcudHBvYW0gW1JlZjA0My4wMl0NCg0KIA0K
DQpIaSwNCg0KIA0KDQogICAgSSBkb24ndCB0aGluayBpdCBpcyBwcm9wZXIgdG8gc2VuZCB0aGUg
TFMgdG8gSVRVLVQgYmVjYXVzZSB0aGUgdGV4dCBkb2Vzbid0IHJlZmxlY3QgdGhlIHJlcXVpcmVt
ZW50IGZyb20gcHJvdmlkZXJzLg0KDQogICAgQXBwYXJlbnRseSwgZHJhZnQtYmhoIGJhc2VkIE9B
TSBpcyB0aGUgbW9zdCBtYXR1cmUgc29sdXRpb24gY3VycmVudGx5LiBJdCBoYXMgYmVlbiBwcm92
ZWQgYnkgbW9yZSB0aGFuIDIwMCwwMDAgYXBwbGljYXRpb25zIGFuZCBpcyBzdXBwb3J0ZWQgYnkg
YSBsb3Qgb2Ygb3BlcmF0b3JzIGFuZCB2ZW5kb3JzLiANCg0KICAgIA0KDQpCZXN0IHJlZ2FyZHMs
DQoNCiANCg0KICAgICAgICAgICAgICBIYW4gTGkNCg0KIA0KDQoqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQoN
CkhhbiBMaSwgUGguRCANCg0KQ2hpbmEgTW9iaWxlIFJlc2VhcmNoIEluc3RpdHV0ZQ0KDQpVbml0
IDIsIDI4IFh1YW53dW1lbnhpIEF2ZSwgWHVhbnd1IERpc3RyaWN0LCBCZWlqaW5nIDEwMDA1Mywg
Q2hpbmEgDQoNCkZheDogKzg2IDEwIDYzNjAxMDg3IA0KDQpNT0JJTEU6IDEzNTAxMDkzMzg1IA0K
DQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqDQoNCiANCg0KIA0KDQotLS0gMTHlubQx5pyIMTPml6XvvIzlkajl
m5ssIHJ1aXF1YW4uamluZ0B0aWVzLml0dS5pbnQgPHJ1aXF1YW4uamluZ0B0aWVzLml0dS5pbnQ+
IOWGmemBk++8mg0KDQogDQoNCj4g5Y+R5Lu25Lq6OiBydWlxdWFuLmppbmdAdGllcy5pdHUuaW50
IDxydWlxdWFuLmppbmdAdGllcy5pdHUuaW50Pg0KDQo+IOS4u+mimDogUmU6IFttcGxzLXRwXSBb
bXBsc10gRHJhZnQ6IFJlc3BvbnNlIHRvIFVwZGF0ZWQgZHJhZnQgUmVjb21tZW5kYXRpb24gRy50
cG9hbSBbUmVmMDQzLjAyXQ0KDQo+IOaUtuS7tuS6ujogamluZ3JAdGllcy5pdHUuY2gNCg0KPiDm
ioTpgIE6IG1wbHMtdHBAaWV0Zi5vcmcNCg0KPiDml6XmnJ86IDIwMTHlubQx5pyIMTPml6Us5ZGo
5ZubLOS4i+WNiDQ6MDkNCg0KPiBSZXNlbmQgdG8gbXBscy10cCBsaXN0Lg0KDQo+IA0KDQo+IFF1
b3RpbmcgamluZ3JAdGllcy5pdHUuY2g6DQoNCj4gDQoNCj4gPiBIaSBTdGV3YXJ0IEJyeWFudCwN
Cg0KPiA+IA0KDQo+ID4gSSBkb27igJl0IGFncmVlIHdpdGggdGhlIGN1cnJlbnQgTFMgdGV4dC4N
Cg0KPiA+IA0KDQo+ID4gQ2hpbmEgVGVsZWNvbSBzdXBwb3J0IHRoZSBzdGFuZGFyZGl6YXRpb24g
b2YgWS4xNzMxDQoNCj4gYmFzZWQgTVBMUy1UUCBPQU0gdG9vbHMNCg0KPiA+IGluIA0KDQo+ID4g
dGhlIElUVS1UIHRvIG1lZXQgdGhlIHVyZ2VudCBhbmQgaW5jcmVhc2luZw0KDQo+IHJlcXVpcmVt
ZW50cyBmb3IgUFROIGRlcGxveW1lbnQuIA0KDQo+ID4gDQoNCj4gPiBJdOKAmXMgYSBtdWx0aS12
ZW5kb3Igc3VwcG9ydGVkLCBpbnRlcm9wZXJhYmlsaXR5DQoNCj4gY2VydGlmaWNhdGVkIGFuZCBm
ZWFzaWJsZSANCg0KPiA+IHNvbHV0aW9uLiAgSXQgaGFkIGJlZW4gc3BlY2lmaWVkIGluIGJvdGgg
Q0NTQQ0KDQo+IChDaGluYSBDb21tdW5pY2F0aW9ucyBTdGFuZGFyZHMNCg0KPiA+IA0KDQo+ID4g
QXNzb2NpYXRpb24pIGFuZCBDaGluYSBUZWxlY29t4oCZcyBQVE4gc3RhbmRhcmQgYXMgdGhlDQoN
Cj4gb25seSBzdGFuZGFyZCBPQU0gDQoNCj4gPiBtZWNoYW5pc20uDQoNCj4gPiANCg0KPiA+ICAN
Cg0KPiA+IA0KDQo+ID4gQmVzdCBSZWdhcmRzDQoNCj4gPiANCg0KPiA+IEppbmcgUnVpcXVhbg0K
DQo+ID4gDQoNCj4gPiBDaGluYeOAgFRlbGVjb20gIEJlaWppbmcgDQoNCj4gUmVzZWFyY2jjgIBJ
bnN0aXR1dGUNCg0KPiA+IA0KDQo+ID4NCg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KPiAt
LQ0KDQo+ID4gRnJvbTogbXBscy1ib3VuY2VzQGlldGYub3JnDQoNCj4gW21haWx0bzptcGxzLWJv
dW5jZXNAaWV0Zi5vcmddDQoNCj4gT24gQmVoYWxmIE9mDQoNCj4gPiBTdGV3YXJ0IA0KDQo+ID4g
QnJ5YW50DQoNCj4gPiBTZW50OiBNb25kYXksIEphbnVhcnkgMTAsIDIwMTEgNjo1NyBQTQ0KDQo+
ID4gVG86IG1wbHNAaWV0Zi5vcmcNCg0KPiA+IFN1YmplY3Q6IFttcGxzXSBEcmFmdDogUmVzcG9u
c2UgdG8gVXBkYXRlZCBkcmFmdA0KDQo+IFJlY29tbWVuZGF0aW9uIEcudHBvYW0gDQoNCj4gPiBb
UmVmMDQzLjAyXQ0KDQo+ID4gDQoNCj4gPiANCg0KPiA+IEkgcHJvcG9zZSB0byBzZW5kIHRoZSBm
b2xsb3dpbmcgTGlhaXNvbiBSZXNwb25zZSB0bw0KDQo+IHRoZSBJVFUtVCBvbiBGcmlkYXkgDQoN
Cj4gPiAxNHRoIEphbnVhcnkgYW5kIGFtIHBvc3RpbmcgaXQgdG8gdGhlIE1QTFMgV0cgbGlzdCBm
b3INCg0KPiByZXZpZXcuIA0KDQo+ID4gDQoNCj4gPiA9PT09PT09IA0KDQo+ID4gDQoNCj4gPiBS
ZXNwb25zZSB0byBVcGRhdGVkIGRyYWZ0IFJlY29tbWVuZGF0aW9uIEcudHBvYW0gW1JlZg0KDQo+
IDA0My4wMl0gDQoNCj4gPiANCg0KPiA+IEZyb206IElFVEYgTGlhaXNvbiB0byBJVFUtVCBvbiBN
UExTIHN0YnJ5YW50QGNpc2NvLmNvbQ0KDQo+IA0KDQo+ID4gVG86IHRzYnNnMTVAaXR1LmludCwN
Cg0KPiBncmVnLmpvbmVzQGl0dS5pbnQsDQoNCj4gaGlyb3NoaS5vdGFAaXR1LmludCwNCg0KPiBJ
QUJAaWV0Zi5vcmcgDQoNCj4gPiBDQzogR3JlZyBKb25lcywgc3dhbGxvd0BjaXNjby5jb20sDQoN
Cj4gbG9hQHBpLm51LCBwYWZAY2lzY28uY29tIA0KDQo+ID4gc3RicnlhbnRAY2lzY28uY29tLA0K
DQo+IGFkcmlhbi5mYXJyZWxAaHVhd2VpLmNvbSwNCg0KPiBtcGxzQGlldGYub3JnIA0KDQo+ID4g
eW9pY2hpLm1hZWRhQHR0Yy5vci5qcCwNCg0KPiBzdGV2ZS50cm93YnJpZGdlQGFsY2F0ZWwtbHVj
ZW50LmNvbQ0KDQo+IA0KDQo+ID4gZ2hhbmkuYWJiYXNAZXJpY3Nzb24uY29tLA0KDQo+IGhoZWx2
b29ydEBodWF3ZWkuY29tDQoNCj4gDQoNCj4gPiBtYWxjb2xtLmJldHRzQHp0ZS5jb20uY24sDQoN
Cj4ga2FtLmxhbUBhbGNhdGVsLWx1Y2VudC5jb20NCg0KPiANCg0KPiA+IA0KDQo+ID4gRm9yIEFj
dGlvbiANCg0KPiA+IA0KDQo+ID4gVGhlIE1QTFMgV29ya2luZyBHcm91cCBub3RlcyB0aGF0IHRo
aXMgZG9jdW1lbnQNCg0KPiBjb250YWlucyB0ZXh0IGRlc2NyaWJpbmcgDQoNCj4gPiBNUExTLVRQ
IE9BTSBwcm90b2NvbHMgbm90IGRlc2lnbmVkIGFuZCBzdGFuZGFyZGl6ZWQNCg0KPiB1c2luZyB0
aGUgSUVURiANCg0KPiA+IFN0YW5kYXJkcyBwcm9jZXNzLiBTcGVjaWZpY2FsbHkgaXQgdXNlcyBt
YXRlcmlhbCBmcm9tDQoNCj4gDQoNCj4gPiBkcmFmdC1iaGgtbXBscy10cC1vYW0teTE3MzEtMDYu
IA0KDQo+ID4gDQoNCj4gPiBXZSB3aXNoIHRvIGRyYXcgeW91ciBhdHRlbnRpb24gdG8gdGhlIHN0
YXR1cyBzZWN0aW9uDQoNCj4gb2YgDQoNCj4gPiBkcmFmdC1iaGgtbXBscy10cC1vYW0teTE3MzEt
MDYgd2hpY2ggc3RhdGVzOiANCg0KPiA+IA0KDQo+ID4gIkludGVybmV0LURyYWZ0cyBhcmUgZHJh
ZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhDQoNCj4gbWF4aW11bSBvZiBzaXggbW9udGhzIA0KDQo+
ID4gYW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyDQoN
Cj4gZG9jdW1lbnRzIGF0IGFueSANCg0KPiA+IHRpbWUuIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8g
dXNlIEludGVybmV0LURyYWZ0cyBhcw0KDQo+IHJlZmVyZW5jZSBtYXRlcmlhbCANCg0KPiA+IG9y
IHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzIi4gDQoNCj4gPiAN
Cg0KPiA+IFBsZWFzZSBhbHNvIG5vdGUgdGhhdCBzaW5jZSB0aGUgZHJhZnQgZmlsZW5hbWUgc3Rh
cnRzDQoNCj4gd2l0aCB0aGUgcHJlZml4IA0KDQo+ID4gc3RyaW5nICJkcmFmdC1iaGgiIHRoaXMg
Y2xlYXJseSBpZGVudGlmaWVzIGl0IHRvIHRoZQ0KDQo+IHJlYWRlciBhcyBhIA0KDQo+ID4gZG9j
dW1lbnQgZXhwcmVzc2luZyB0aGUgcGVyc29uYWwgdGVjaG5pY2FsIHZpZXdzIG9mDQoNCj4gdGhl
IGF1dGhvcnMgYW5kIA0KDQo+ID4gaGVuY2UgaGVuY2UgYXMgYSBkb2N1bWVudCB0aGF0IHRoYXQg
ZG9lcyBub3QgaGF2ZSBhbnkNCg0KPiBhY2tub3dsZWRnZWQgbGV2ZWwgDQoNCj4gPiBvZiBJRVRG
IGNvbnNlbnN1cy4gDQoNCj4gPiANCg0KPiA+IFNpbmNlIHRoZSB0ZXh0IG9mIGRyYWZ0IFJlY29t
bWVuZGF0aW9uIGZvciBHLnRwb2FtIGlzDQoNCj4gYmFzZWQgb24gYW4gDQoNCj4gPiBNUExTLVRQ
IE9BTSBwcm90b2NvbCBub3QgZGVzaWduZWQgd2l0aGluIHRoZSBJRVRGDQoNCj4gU3RhbmRhcmRz
IFByb2Nlc3MgdGhpcyANCg0KPiA+IGlzIGEgYnJlYWNoIG9mIHRoZSBTRzE1IGFncmVlbWVudCB3
aXRoIHRoZSBJRVRGIGFzDQoNCj4gcHVibGlzaGVkIGluIFJlcG9ydCANCg0KPiA+IG9mIHRoZSBm
aXJzdCBtZWV0aW5nIG9mIFdvcmtpbmcgUGFydHkgMy8xNSBUcmFuc3BvcnQNCg0KPiBuZXR3b3Jr
IHN0cnVjdHVyZXMgDQoNCj4gPiAoMjAwOS0yMDEyKSAoR2VuZXZhLCAxIOKAkyAxMiBEZWNlbWJl
ciAyMDA4KSB3aGljaCBjYW4NCg0KPiBiZSBmb3VuZCBhdCANCg0KPiA+IGh0dHA6Ly93d3cuaXR1
LmludC9tZC9UMDktU0cxNS1SLTAwMDQvZW4NCg0KPiANCg0KPiA+IA0KDQo+ID4gUGxlYXNlIGNv
bmZpcm0gdGhhdCB0aGUgSVRVLVQgaW50ZW5kcyB0byBjb250aW51ZSB3aXRoDQoNCj4gdGhlIGpv
aW50IHdvcmsgb24gDQoNCj4gPiBNUExTLVRQIGFuZCB0aGF0IHRoZSBJVFUtVCB3aWxsIGFsaWdu
IHRoaXMNCg0KPiByZWNvbW1lbmRhdGlvbiB3aXRoIHRoZSBJRVRGIA0KDQo+ID4gTVBMUy1UUCBP
QU0gZGVzaWduIGJlZm9yZSBhZHZhbmNpbmcgdGhpcyBkb2N1bWVudA0KDQo+IHRocm91Z2ggdGhl
IElUVS1UIA0KDQo+ID4gcHVibGljYXRpb24gcHJvY2Vzcy4gDQoNCj4gPiANCg0KPiA+IFRoZSBN
UExTIFdvcmtpbmcgR3JvdXAgd291bGQgYWxzbyBsaWtlIHRvIGRyYXcgdGhlDQoNCj4gYXR0ZW50
aW9uIG9mIElUVS1UIA0KDQo+ID4gU0cxNSB0byB0aGUgSUVURiBjb3B5cmlnaHQgcnVsZXMuIFBs
ZWFzZSBzZWUgDQoNCj4gPiBodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8vYXJj
aGl2ZS9JRVRGLVRydXN0LUxpY2Vuc2UtUG9saWN5LQ0KDQo+ID4gMjAwOTEyMjguaHRtIA0KDQo+
ID4gZm9yIGZ1cnRoZXIgZGV0YWlscy4gDQoNCj4gPiANCg0KPiA+IFNpbmNlIHRoaXMgZHJhZnQg
UmVjb21tZW5kYXRpb24gY29udGFpbnMgdGV4dCBpbiB3aGljaA0KDQo+IHRoZSBJVFUtVCBTRzE1
IA0KDQo+ID4gaGFzIHByb3Bvc2VkIG1ha2luZyBjaGFuZ2VzIHRvIElFVEYgcHJvdG9jb2xzIHdp
dGhvdXQNCg0KPiB0aGUgYXBwcm92YWwgb2YgDQoNCj4gPiB0aGUgSUVURiwgdGhlIE1QTFMgV29y
a2luZyBHcm91cCBoYXZlIHJlZmVycmVkIHRoaXMNCg0KPiBsaWFpc29uIHRvIHRoZSBJQUIgDQoN
Cj4gPiBmb3IgdGhlaXIgY29uc2lkZXJhdGlvbi4gDQoNCj4gPiANCg0KPiA+IA0KDQo+ID4gDQoN
Cj4gPiA9PT09PT09PT0gDQoNCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXyANCg0KPiA+IG1wbHMgbWFpbGluZyBsaXN0IA0KDQo+ID4gbXBsc0BpZXRm
Lm9yZyANCg0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscyAN
Cg0KPiA+IA0KDQo+ID4gDQoNCj4gPiANCg0KPiANCg0KPiANCg0KPiANCg0KPiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQo+IG1wbHMtdHAgbWFpbGlu
ZyBsaXN0DQoNCj4gbXBscy10cEBpZXRmLm9yZw0KDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vbXBscy10cA0KDQo+IA0KDQogDQoNCiANCg0KICAgICAgDQoNCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCm1wbHMtdHAgbWFp
bGluZyBsaXN0DQoNCm1wbHMtdHBAaWV0Zi5vcmcNCg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9tcGxzLXRwDQoNCg==

------_=_NextPart_001_01CBB336.D57B1EC7
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOnA9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206
b2ZmaWNlOnBvd2VycG9pbnQiIHhtbG5zOmE9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2Zm
aWNlOmFjY2VzcyIgeG1sbnM6ZHQ9InV1aWQ6QzJGNDEwMTAtNjVCMy0xMWQxLUEyOUYtMDBBQTAw
QzE0ODgyIiB4bWxuczpzPSJ1dWlkOkJEQzZFM0YwLTZEQTMtMTFkMS1BMkEzLTAwQUEwMEMxNDg4
MiIgeG1sbnM6cnM9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206cm93c2V0IiB4bWxuczp6PSIj
Um93c2V0U2NoZW1hIiB4bWxuczpiPSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpw
dWJsaXNoZXIiIHhtbG5zOnNzPSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpzcHJl
YWRzaGVldCIgeG1sbnM6Yz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6Y29tcG9u
ZW50OnNwcmVhZHNoZWV0IiB4bWxuczpvZGM9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2Zm
aWNlOm9kYyIgeG1sbnM6b2E9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOmFjdGl2
YXRpb24iIHhtbG5zOmh0bWw9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1odG1sNDAiIHhtbG5z
OnE9Imh0dHA6Ly9zY2hlbWFzLnhtbHNvYXAub3JnL3NvYXAvZW52ZWxvcGUvIiB4bWxuczpydGM9
Imh0dHA6Ly9taWNyb3NvZnQuY29tL29mZmljZW5ldC9jb25mZXJlbmNpbmciIHhtbG5zOkQ9IkRB
VjoiIHhtbG5zOlJlcGw9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vcmVwbC8iIHhtbG5z
Om10PSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL3NoYXJlcG9pbnQvc29hcC9tZWV0aW5n
cy8iIHhtbG5zOngyPSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS9leGNlbC8y
MDAzL3htbCIgeG1sbnM6cHBkYT0iaHR0cDovL3d3dy5wYXNzcG9ydC5jb20vTmFtZVNwYWNlLnhz
ZCIgeG1sbnM6b2lzPSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL3NoYXJlcG9pbnQvc29h
cC9vaXMvIiB4bWxuczpkaXI9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2lu
dC9zb2FwL2RpcmVjdG9yeS8iIHhtbG5zOmRzPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwLzA5L3ht
bGRzaWcjIiB4bWxuczpkc3A9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2lu
dC9kc3AiIHhtbG5zOnVkYz0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9kYXRhL3VkYyIg
eG1sbnM6eHNkPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYSIgeG1sbnM6c3ViPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL3NoYXJlcG9pbnQvc29hcC8yMDAyLzEvYWxlcnRz
LyIgeG1sbnM6ZWM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvMDQveG1sZW5jIyIgeG1sbnM6c3A9
Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2ludC8iIHhtbG5zOnNwcz0iaHR0
cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9zaGFyZXBvaW50L3NvYXAvIiB4bWxuczp4c2k9Imh0
dHA6Ly93d3cudzMub3JnLzIwMDEvWE1MU2NoZW1hLWluc3RhbmNlIiB4bWxuczp1ZGNzPSJodHRw
Oi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL2RhdGEvdWRjL3NvYXAiIHhtbG5zOnVkY3hmPSJodHRw
Oi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL2RhdGEvdWRjL3htbGZpbGUiIHhtbG5zOnVkY3AycD0i
aHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9kYXRhL3VkYy9wYXJ0dG9wYXJ0IiB4bWxuczp3
Zj0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9zaGFyZXBvaW50L3NvYXAvd29ya2Zsb3cv
IiB4bWxuczpkc3NzPSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA2L2Rp
Z3NpZy1zZXR1cCIgeG1sbnM6ZHNzaT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9vZmZp
Y2UvMjAwNi9kaWdzaWciIHhtbG5zOm1kc3NpPSJodHRwOi8vc2NoZW1hcy5vcGVueG1sZm9ybWF0
cy5vcmcvcGFja2FnZS8yMDA2L2RpZ2l0YWwtc2lnbmF0dXJlIiB4bWxuczptdmVyPSJodHRwOi8v
c2NoZW1hcy5vcGVueG1sZm9ybWF0cy5vcmcvbWFya3VwLWNvbXBhdGliaWxpdHkvMjAwNiIgeG1s
bnM6bT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4
bWxuczptcmVscz0iaHR0cDovL3NjaGVtYXMub3BlbnhtbGZvcm1hdHMub3JnL3BhY2thZ2UvMjAw
Ni9yZWxhdGlvbnNoaXBzIiB4bWxuczpzcHdwPSJodHRwOi8vbWljcm9zb2Z0LmNvbS9zaGFyZXBv
aW50L3dlYnBhcnRwYWdlcyIgeG1sbnM6ZXgxMnQ9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vZXhjaGFuZ2Uvc2VydmljZXMvMjAwNi90eXBlcyIgeG1sbnM6ZXgxMm09Imh0dHA6Ly9zY2hl
bWFzLm1pY3Jvc29mdC5jb20vZXhjaGFuZ2Uvc2VydmljZXMvMjAwNi9tZXNzYWdlcyIgeG1sbnM6
cHB0c2w9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2ludC9zb2FwL1NsaWRl
TGlicmFyeS8iIHhtbG5zOnNwc2w9Imh0dHA6Ly9taWNyb3NvZnQuY29tL3dlYnNlcnZpY2VzL1No
YXJlUG9pbnRQb3J0YWxTZXJ2ZXIvUHVibGlzaGVkTGlua3NTZXJ2aWNlIiB4bWxuczpaPSJ1cm46
c2NoZW1hcy1taWNyb3NvZnQtY29tOiIgeG1sbnM6c3Q9IiYjMTsiIHhtbG5zPSJodHRwOi8vd3d3
LnczLm9yZy9UUi9SRUMtaHRtbDQwIj48aGVhZD48bWV0YSBodHRwLWVxdWl2PUNvbnRlbnQtVHlw
ZSBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjxtZXRhIG5hbWU9R2VuZXJhdG9y
IGNvbnRlbnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj48c3R5bGU+PCEt
LQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiTVMg
R290aGljIjsNCglwYW5vc2UtMToyIDExIDYgOSA3IDIgNSA4IDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5Ok1pbmdMaVU7DQoJcGFub3NlLTE6MiAyIDMgOSAwIDAgMCAwIDAgMDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5Ok1pbmdMaVU7DQoJcGFub3NlLTE6MiAyIDMgOSAwIDAg
MCAwIDAgMDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6
MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xh
czsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OiJcQE1TIEdvdGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDkgNyAyIDUgOCAyIDQ7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEBNaW5nTGlVIjsNCglwYW5vc2UtMToyIDIgMyA5
IDAgMCAwIDAgMCAwO30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGku
TXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTou
MDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNp
dGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb1BsYWlu
VGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFyIjsNCgltYXJnaW46MGNt
Ow0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuNXB0Ow0KCWZvbnQtZmFt
aWx5OkNvbnNvbGFzO30NCnNwYW4uUGxhaW5UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxh
aW4gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6
IlBsYWluIFRleHQiOw0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCi5Nc29DaHBEZWZhdWx0DQoJ
e21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXpl
OjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3Mi4wcHQgOTAuMHB0O30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRt
YXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRh
PSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPjwvaGVhZD48Ym9keSBs
YW5nPUVOLVVTIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+PGRpdiBjbGFzcz1Xb3JkU2VjdGlvbjE+
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PkhhbiBMaSw8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+UGxlYXNlIG5vdGUgdGhhdCB0aGlzIGxpYWlzb24gaXMgbm90IGludGVuZGVkIHRv
IGdldCBpbnRvIHRlY2huaWNhbCBkaXNjdXNzaW9uIG9yIGludG8gU1BzJyByZXF1aXJlbWVudHMu
IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD5JdCBpcyBtb3JlIG9uIHRoZSBw
cm9jZWR1cmVzIGFuZCBwcm9jZXNzZXMuLi4uPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxh
aW5UZXh0PkFjY29yZGluZyB0byB0aGUgY29sbGFib3JhdGl2ZSBhZ3JlZW1lbnQgYmV0d2VlbiB0
aGUgSVRVLVQgYW5kIHRoZSBJRVRGICh3aGljaCB3YXMgYWNjZXB0ZWQgYnkgSVRVLVQgU0cxNSBp
biBEZWNlbWJlciAyMDA4KSwgdGhlIGRldmVsb3BtZW50IG9mIHRoZSBwcm90b2NvbCBzaG91bGQg
YmUgZG9uZSBpbiB0aGUgSUVURiB1c2luZyB0aGUgPGI+PHU+SUVURiBwcm9jZXNzZXM8L3U+PC9i
Pi4gVGhlIElUVS1UIGRvY3VtZW50cyBzaG91bGQgcmVmZXIgdG8gdGhlIElFVEYgc29sdXRpb25z
LiA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+V2Ugbm90ZSBhIGRvY3VtZW50
ICh1bmRlciBkZXZlbG9wbWVudCkgaW4gdGhlIElUVS1UIChnLnRwb2FtKSwgd2hpY2ggaW5jbHVk
ZXMgdGhlIGRlZmluaXRpb24gb2YgbWVzc2FnZXMgYW5kIHByb2NlZHVyZXMgZm9yIE1TUEwtVFAg
d2hpY2ggd2VyZSBub3QgZGV2ZWxvcGVkIHVzaW5nIHRoZSBJRVRGIHN0YW5kYXJkIHByb2Nlc3Nl
cyBhbmQgZG9lcyBub3QgZm9sbG93IHRoZSBJRVRGIGNoYW5nZS9leHRlbnNpb24gcHJvY2Vzc2Vz
LiBUaGlzIGlzIGNvbnRyYXJ5IHRvIHRoZSBhZ3JlZW1lbnQgYmV0d2VlbiB0aGUgSUVURiBhbmQg
dGhlIElUVS1UIGZyb20gRGVjZW1iZXIgMjAwOC4gPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNv
UGxhaW5UZXh0PldlIGFyZSByZXNwb25kaW5nIG9uIHRoZSBwcm9jZXNzIGFuZCB3YW50IHRvIGJl
IHN1cmUgKGFuZCBob3BlKSB0aGF0IHRoZSBJVFUtVCBpbnRlbmRzIHRvIGNvbnRpbnVlIHdpdGgg
dGhlIGpvaW50IHdvcmsgb24gTVBMUy1UUCBhcyBhZ3JlZWQgb24gaW4gRGVjZW1iZXIgMjAwOC4g
PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PkkgdGhpbmsgdGhlIGxpYWlzb24g
aXMgdmVyeSB3ZWxsIHdyaXR0ZW4hPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0
PkJlc3QgcmVnYXJkcyw8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+TnVyaXQ8
bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+
PHAgY2xhc3M9TXNvUGxhaW5UZXh0Pi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPkZyb206
IG1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOm1wbHMtdHAtYm91bmNlc0BpZXRmLm9y
Z10gT24gQmVoYWxmIE9mIGV4dCBMYXJyeTxicj5TZW50OiBUaHVyc2RheSwgSmFudWFyeSAxMywg
MjAxMSA0OjU2IFBNPGJyPlRvOiBqaW5nckB0aWVzLml0dS5jaDsgcnVpcXVhbi5qaW5nQHRpZXMu
aXR1LmludDxicj5DYzogbXBsc0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZzxicj5TdWJqZWN0
OiBSZTogW21wbHMtdHBdIFttcGxzXSBEcmFmdDogUmVzcG9uc2UgdG8gVXBkYXRlZCBkcmFmdFJl
Y29tbWVuZGF0aW9uIEcudHBvYW0gW1JlZjA0My4wMl08bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1N
c29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0Pkhp
LDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwv
cD48cCBjbGFzcz1Nc29QbGFpblRleHQ+wqDCoMKgIEkgZG9uJ3QgdGhpbmsgaXQgaXMgcHJvcGVy
IHRvIHNlbmQgdGhlIExTIHRvIElUVS1UIGJlY2F1c2UgdGhlIHRleHQgZG9lc24ndCByZWZsZWN0
IHRoZSByZXF1aXJlbWVudCBmcm9tIHByb3ZpZGVycy48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1N
c29QbGFpblRleHQ+wqDCoMKgIEFwcGFyZW50bHksIGRyYWZ0LWJoaCBiYXNlZCBPQU0gaXMgdGhl
IG1vc3QgbWF0dXJlIHNvbHV0aW9uIGN1cnJlbnRseS4gSXQgaGFzIGJlZW4gcHJvdmVkIGJ5IG1v
cmUgdGhhbiAyMDAsMDAwIGFwcGxpY2F0aW9ucyBhbmQgaXMgc3VwcG9ydGVkIGJ5IGEgbG90IG9m
IG9wZXJhdG9ycyBhbmQgdmVuZG9ycy4gPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5U
ZXh0PsKgwqDCoMKgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PkJlc3QgcmVn
YXJkcyw8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286
cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIEhh
biBMaTxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpw
PjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+KioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKjxvOnA+PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD5IYW4gTGksIFBoLkQgPG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvUGxhaW5UZXh0PkNoaW5hIE1vYmlsZSBSZXNlYXJjaCBJbnN0aXR1dGU8bzpwPjwvbzpw
PjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+VW5pdCAyLCAyOCBYdWFud3VtZW54aSBBdmUsIFh1
YW53dSBEaXN0cmljdCwgQmVpamluZyAxMDAwNTMsIENoaW5hIDxvOnA+PC9vOnA+PC9wPjxwIGNs
YXNzPU1zb1BsYWluVGV4dD5GYXg6ICs4NiAxMCA2MzYwMTA4NyA8bzpwPjwvbzpwPjwvcD48cCBj
bGFzcz1Nc29QbGFpblRleHQ+TU9CSUxFOiAxMzUwMTA5MzM4NSA8bzpwPjwvbzpwPjwvcD48cCBj
bGFzcz1Nc29QbGFpblRleHQ+KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz
PU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+
PG86cD4mbmJzcDs8L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0Pi0tLSAxMTxzcGFuIHN0
eWxlPSdmb250LWZhbWlseToiTVMgR290aGljIic+5bm0PC9zcGFuPjE8c3BhbiBzdHlsZT0nZm9u
dC1mYW1pbHk6Ik1TIEdvdGhpYyInPuaciDwvc3Bhbj4xMzxzcGFuIHN0eWxlPSdmb250LWZhbWls
eToiTVMgR290aGljIic+5pel77yM5ZGo5ZubPC9zcGFuPiwgcnVpcXVhbi5qaW5nQHRpZXMuaXR1
LmludCAmbHQ7cnVpcXVhbi5qaW5nQHRpZXMuaXR1LmludCZndDsgPHNwYW4gc3R5bGU9J2ZvbnQt
ZmFtaWx5OiJNUyBHb3RoaWMiJz7lhpnpgZPvvJo8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4mZ3Q7IDxzcGFuIHN0eWxlPSdmb250LWZhbWlseTpNaW5nTGlVJz7lj5Hku7bkuro8L3NwYW4+
OiBydWlxdWFuLmppbmdAdGllcy5pdHUuaW50ICZsdDtydWlxdWFuLmppbmdAdGllcy5pdHUuaW50
Jmd0OzxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxzcGFuIHN0eWxl
PSdmb250LWZhbWlseToiTVMgR290aGljIic+5Li7PC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LWZh
bWlseTpNaW5nTGlVJz7popg8L3NwYW4+OiBSZTogW21wbHMtdHBdIFttcGxzXSBEcmFmdDogUmVz
cG9uc2UgdG8gVXBkYXRlZCBkcmFmdCBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtIFtSZWYwNDMuMDJd
PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPHNwYW4gc3R5bGU9J2Zv
bnQtZmFtaWx5OiJNUyBHb3RoaWMiJz7mlLbku7bkuro8L3NwYW4+OiBqaW5nckB0aWVzLml0dS5j
aDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxzcGFuIHN0eWxlPSdm
b250LWZhbWlseToiTVMgR290aGljIic+5oqE6YCBPC9zcGFuPjogbXBscy10cEBpZXRmLm9yZzxv
OnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxzcGFuIHN0eWxlPSdmb250
LWZhbWlseToiTVMgR290aGljIic+5pel5pyfPC9zcGFuPjogMjAxMTxzcGFuIHN0eWxlPSdmb250
LWZhbWlseToiTVMgR290aGljIic+5bm0PC9zcGFuPjE8c3BhbiBzdHlsZT0nZm9udC1mYW1pbHk6
Ik1TIEdvdGhpYyInPuaciDwvc3Bhbj4xMzxzcGFuIHN0eWxlPSdmb250LWZhbWlseToiTVMgR290
aGljIic+5pelPC9zcGFuPiw8c3BhbiBzdHlsZT0nZm9udC1mYW1pbHk6Ik1TIEdvdGhpYyInPuWR
qOWbmzwvc3Bhbj4sPHNwYW4gc3R5bGU9J2ZvbnQtZmFtaWx5OiJNUyBHb3RoaWMiJz7kuIvljYg8
L3NwYW4+NDowOTxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IFJlc2Vu
ZCB0byBtcGxzLXRwIGxpc3QuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgUXVvdGluZyBqaW5n
ckB0aWVzLml0dS5jaDo8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8
bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IEhpIFN0ZXdhcnQg
QnJ5YW50LDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgPG86
cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBJIGRvbuKAmXQgYWdy
ZWUgd2l0aCB0aGUgY3VycmVudCBMUyB0ZXh0LjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7ICZndDsgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgJmd0OyBDaGluYSBUZWxlY29tIHN1cHBvcnQgdGhlIHN0YW5kYXJkaXphdGlvbiBvZiBZLjE3
MzE8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBiYXNlZCBNUExTLVRQ
IE9BTSB0b29sczxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsg
aW4gPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyB0aGUgSVRV
LVQgdG8gbWVldCB0aGUgdXJnZW50IGFuZCBpbmNyZWFzaW5nPG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDsgcmVxdWlyZW1lbnRzIGZvciBQVE4gZGVwbG95bWVudC4gPG86
cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwv
cD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IEl04oCZcyBhIG11bHRpLXZlbmRvciBz
dXBwb3J0ZWQsIGludGVyb3BlcmFiaWxpdHk8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jmd0OyBjZXJ0aWZpY2F0ZWQgYW5kIGZlYXNpYmxlIDxvOnA+PC9vOnA+PC9wPjxwIGNs
YXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgc29sdXRpb24uJm5ic3A7IEl0IGhhZCBiZWVuIHNw
ZWNpZmllZCBpbiBib3RoIENDU0E8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+
Jmd0OyAoQ2hpbmEgQ29tbXVuaWNhdGlvbnMgU3RhbmRhcmRzPG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jmd0OyAmZ3Q7IEFzc29jaWF0aW9uKSBhbmQgQ2hpbmEgVGVsZWNvbeKAmXMgUFROIHN0
YW5kYXJkIGFzIHRoZTxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IG9u
bHkgc3RhbmRhcmQgT0FNIDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
ICZndDsgbWVjaGFuaXNtLjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
ICZndDsgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyZuYnNw
OyA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxvOnA+PC9v
OnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgQmVzdCBSZWdhcmRzPG86cD48
L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwvcD48
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IEppbmcgUnVpcXVhbjxvOnA+PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgPG86cD48L286cD48L3A+PHAgY2xhc3M9
TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBDaGluYTxzcGFuIHN0eWxlPSdmb250LWZhbWlseToiTVMg
R290aGljIic+44CAPC9zcGFuPlRlbGVjb20mbmJzcDsgQmVpamluZyZuYnNwOzxvOnA+PC9vOnA+
PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IFJlc2VhcmNoPHNwYW4gc3R5bGU9J2ZvbnQt
ZmFtaWx5OiJNUyBHb3RoaWMiJz7jgIA8L3NwYW4+SW5zdGl0dXRlPG86cD48L286cD48L3A+PHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+Jmd0OyAmZ3Q7PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5U
ZXh0PiZndDsgLS08bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7
IEZyb206IG1wbHMtYm91bmNlc0BpZXRmLm9yZzxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7IFttYWlsdG86bXBscy1ib3VuY2VzQGlldGYub3JnXTxvOnA+PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IE9uIEJlaGFsZiBPZjxvOnA+PC9vOnA+PC9wPjxw
IGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgU3Rld2FydCA8bzpwPjwvbzpwPjwvcD48cCBj
bGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IEJyeWFudDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz
PU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgU2VudDogTW9uZGF5LCBKYW51YXJ5IDEwLCAyMDExIDY6
NTcgUE08bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IFRvOiBt
cGxzQGlldGYub3JnPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0
OyBTdWJqZWN0OiBbbXBsc10gRHJhZnQ6IFJlc3BvbnNlIHRvIFVwZGF0ZWQgZHJhZnQ8bzpwPjwv
bzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBSZWNvbW1lbmRhdGlvbiBHLnRwb2Ft
IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgW1JlZjA0My4w
Ml08bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxvOnA+PC9v
OnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgPG86cD48L286cD48L3A+PHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBJIHByb3Bvc2UgdG8gc2VuZCB0aGUgZm9sbG93
aW5nIExpYWlzb24gUmVzcG9uc2UgdG88bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyB0aGUgSVRVLVQgb24gRnJpZGF5IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7ICZndDsgMTR0aCBKYW51YXJ5IGFuZCBhbSBwb3N0aW5nIGl0IHRvIHRoZSBN
UExTIFdHIGxpc3QgZm9yPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
cmV2aWV3LiA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxv
OnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgPT09PT09PSA8bzpw
PjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxvOnA+PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgUmVzcG9uc2UgdG8gVXBkYXRlZCBkcmFm
dCBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtIFtSZWY8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+Jmd0OyAwNDMuMDJdIDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4mZ3Q7ICZndDsgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0
OyBGcm9tOiBJRVRGIExpYWlzb24gdG8gSVRVLVQgb24gTVBMUyBzdGJyeWFudEBjaXNjby5jb208
bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD48
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IFRvOiB0c2JzZzE1QGl0dS5pbnQsPG86cD48
L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgZ3JlZy5qb25lc0BpdHUuaW50LDxv
OnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IGhpcm9zaGkub3RhQGl0dS5p
bnQsPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgSUFCQGlldGYub3Jn
IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgQ0M6IEdyZWcg
Sm9uZXMsIHN3YWxsb3dAY2lzY28uY29tLDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IGxvYUBwaS5udSwgcGFmQGNpc2NvLmNvbSA8bzpwPjwvbzpwPjwvcD48cCBjbGFz
cz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IHN0YnJ5YW50QGNpc2NvLmNvbSw8bzpwPjwvbzpwPjwv
cD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBhZHJpYW4uZmFycmVsQGh1YXdlaS5jb20sPG86
cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgbXBsc0BpZXRmLm9yZyA8bzpw
PjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IHlvaWNoaS5tYWVkYUB0
dGMub3IuanAsPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgc3RldmUu
dHJvd2JyaWRnZUBhbGNhdGVsLWx1Y2VudC5jb208bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAm
Z3Q7IGdoYW5pLmFiYmFzQGVyaWNzc29uLmNvbSw8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+Jmd0OyBoaGVsdm9vcnRAaHVhd2VpLmNvbTxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz
PU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7ICZndDsgbWFsY29sbS5iZXR0c0B6dGUuY29tLmNuLDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz
PU1zb1BsYWluVGV4dD4mZ3Q7IGthbS5sYW1AYWxjYXRlbC1sdWNlbnQuY29tPG86cD48L286cD48
L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNv
UGxhaW5UZXh0PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+
Jmd0OyAmZ3Q7IEZvciBBY3Rpb24gPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0
PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7
IFRoZSBNUExTIFdvcmtpbmcgR3JvdXAgbm90ZXMgdGhhdCB0aGlzIGRvY3VtZW50PG86cD48L286
cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgY29udGFpbnMgdGV4dCBkZXNjcmliaW5n
IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgTVBMUy1UUCBP
QU0gcHJvdG9jb2xzIG5vdCBkZXNpZ25lZCBhbmQgc3RhbmRhcmRpemVkPG86cD48L286cD48L3A+
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgdXNpbmcgdGhlIElFVEYgPG86cD48L286cD48L3A+
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBTdGFuZGFyZHMgcHJvY2Vzcy4gU3BlY2lm
aWNhbGx5IGl0IHVzZXMgbWF0ZXJpYWwgZnJvbTxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZn
dDsgZHJhZnQtYmhoLW1wbHMtdHAtb2FtLXkxNzMxLTA2LiA8bzpwPjwvbzpwPjwvcD48cCBjbGFz
cz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7ICZndDsgV2Ugd2lzaCB0byBkcmF3IHlvdXIgYXR0ZW50aW9uIHRvIHRoZSBzdGF0
dXMgc2VjdGlvbjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IG9mIDxv
OnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgZHJhZnQtYmhoLW1w
bHMtdHAtb2FtLXkxNzMxLTA2IHdoaWNoIHN0YXRlczogPG86cD48L286cD48L3A+PHAgY2xhc3M9
TXNvUGxhaW5UZXh0PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyAmZ3Q7ICZxdW90O0ludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZh
bGlkIGZvciBhPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgbWF4aW11
bSBvZiBzaXggbW9udGhzIDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
ICZndDsgYW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVy
PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgZG9jdW1lbnRzIGF0IGFu
eSA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IHRpbWUuIEl0
IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhczxvOnA+PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHJlZmVyZW5jZSBtYXRlcmlhbCA8bzpwPjwvbzpw
PjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IG9yIHRvIGNpdGUgdGhlbSBvdGhl
ciB0aGFuIGFzICZxdW90O3dvcmsgaW4gcHJvZ3Jlc3MmcXVvdDsuIDxvOnA+PC9vOnA+PC9wPjxw
IGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNv
UGxhaW5UZXh0PiZndDsgJmd0OyBQbGVhc2UgYWxzbyBub3RlIHRoYXQgc2luY2UgdGhlIGRyYWZ0
IGZpbGVuYW1lIHN0YXJ0czxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
IHdpdGggdGhlIHByZWZpeCA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0
OyAmZ3Q7IHN0cmluZyAmcXVvdDtkcmFmdC1iaGgmcXVvdDsgdGhpcyBjbGVhcmx5IGlkZW50aWZp
ZXMgaXQgdG8gdGhlPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgcmVh
ZGVyIGFzIGEgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBk
b2N1bWVudCBleHByZXNzaW5nIHRoZSBwZXJzb25hbCB0ZWNobmljYWwgdmlld3Mgb2Y8bzpwPjwv
bzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyB0aGUgYXV0aG9ycyBhbmQgPG86cD48
L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBoZW5jZSBoZW5jZSBhcyBh
IGRvY3VtZW50IHRoYXQgdGhhdCBkb2VzIG5vdCBoYXZlIGFueTxvOnA+PC9vOnA+PC9wPjxwIGNs
YXNzPU1zb1BsYWluVGV4dD4mZ3Q7IGFja25vd2xlZGdlZCBsZXZlbCA8bzpwPjwvbzpwPjwvcD48
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IG9mIElFVEYgY29uc2Vuc3VzLiA8bzpwPjwv
bzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxvOnA+PC9vOnA+PC9wPjxw
IGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgU2luY2UgdGhlIHRleHQgb2YgZHJhZnQgUmVj
b21tZW5kYXRpb24gZm9yIEcudHBvYW0gaXM8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jmd0OyBiYXNlZCBvbiBhbiA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyAmZ3Q7IE1QTFMtVFAgT0FNIHByb3RvY29sIG5vdCBkZXNpZ25lZCB3aXRoaW4gdGhl
IElFVEY8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBTdGFuZGFyZHMg
UHJvY2VzcyB0aGlzIDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZn
dDsgaXMgYSBicmVhY2ggb2YgdGhlIFNHMTUgYWdyZWVtZW50IHdpdGggdGhlIElFVEYgYXM8bzpw
PjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBwdWJsaXNoZWQgaW4gUmVwb3J0
IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgb2YgdGhlIGZp
cnN0IG1lZXRpbmcgb2YgV29ya2luZyBQYXJ0eSAzLzE1IFRyYW5zcG9ydDxvOnA+PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IG5ldHdvcmsgc3RydWN0dXJlcyA8bzpwPjwvbzpw
PjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7ICgyMDA5LTIwMTIpIChHZW5ldmEs
IDEg4oCTIDEyIERlY2VtYmVyIDIwMDgpIHdoaWNoIGNhbjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz
PU1zb1BsYWluVGV4dD4mZ3Q7IGJlIGZvdW5kIGF0IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1z
b1BsYWluVGV4dD4mZ3Q7ICZndDsgaHR0cDovL3d3dy5pdHUuaW50L21kL1QwOS1TRzE1LVItMDAw
NC9lbjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+
PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgPG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBQbGVhc2UgY29uZmlybSB0aGF0IHRoZSBJVFUtVCBp
bnRlbmRzIHRvIGNvbnRpbnVlIHdpdGg8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyB0aGUgam9pbnQgd29yayBvbiA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jmd0OyAmZ3Q7IE1QTFMtVFAgYW5kIHRoYXQgdGhlIElUVS1UIHdpbGwgYWxpZ24gdGhp
czxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHJlY29tbWVuZGF0aW9u
IHdpdGggdGhlIElFVEYgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
Jmd0OyBNUExTLVRQIE9BTSBkZXNpZ24gYmVmb3JlIGFkdmFuY2luZyB0aGlzIGRvY3VtZW50PG86
cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgdGhyb3VnaCB0aGUgSVRVLVQg
PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBwdWJsaWNhdGlv
biBwcm9jZXNzLiA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7
IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgVGhlIE1QTFMg
V29ya2luZyBHcm91cCB3b3VsZCBhbHNvIGxpa2UgdG8gZHJhdyB0aGU8bzpwPjwvbzpwPjwvcD48
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBhdHRlbnRpb24gb2YgSVRVLVQgPG86cD48L286cD48
L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyBTRzE1IHRvIHRoZSBJRVRGIGNvcHly
aWdodCBydWxlcy4gUGxlYXNlIHNlZSA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyAmZ3Q7IGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mby9hcmNoaXZl
L0lFVEYtVHJ1c3QtTGljZW5zZS1Qb2xpY3ktPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgJmd0OyAyMDA5MTIyOC5odG0gPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNv
UGxhaW5UZXh0PiZndDsgJmd0OyBmb3IgZnVydGhlciBkZXRhaWxzLiA8bzpwPjwvbzpwPjwvcD48
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1z
b1BsYWluVGV4dD4mZ3Q7ICZndDsgU2luY2UgdGhpcyBkcmFmdCBSZWNvbW1lbmRhdGlvbiBjb250
YWlucyB0ZXh0IGluIHdoaWNoPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgdGhlIElUVS1UIFNHMTUgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgJmd0OyBoYXMgcHJvcG9zZWQgbWFraW5nIGNoYW5nZXMgdG8gSUVURiBwcm90b2NvbHMgd2l0
aG91dDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHRoZSBhcHByb3Zh
bCBvZiA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IHRoZSBJ
RVRGLCB0aGUgTVBMUyBXb3JraW5nIEdyb3VwIGhhdmUgcmVmZXJyZWQgdGhpczxvOnA+PC9vOnA+
PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IGxpYWlzb24gdG8gdGhlIElBQiA8bzpwPjwv
bzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IGZvciB0aGVpciBjb25zaWRl
cmF0aW9uLiA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxv
OnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgPG86cD48L286cD48
L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwvcD48cCBjbGFz
cz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7ID09PT09PT09PSA8bzpwPjwvbzpwPjwvcD48cCBjbGFz
cz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fIDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
ICZndDsgbXBscyBtYWlsaW5nIGxpc3QgPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5U
ZXh0PiZndDsgJmd0OyBtcGxzQGlldGYub3JnIDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7ICZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9t
cGxzIDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZndDsgPG86cD48
L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgJmd0OyA8bzpwPjwvbzpwPjwvcD48
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyAmZ3Q7IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1z
b1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
IDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgbXBscy10cCBtYWlsaW5nIGxpc3Q8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyBtcGxzLXRwQGlldGYub3JnPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5U
ZXh0PiZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzLXRwPG86
cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48L3A+PHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+wqDCoMKgwqDC
oCA8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+X19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX188bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+bXBscy10cCBtYWlsaW5nIGxpc3Q8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+bXBscy10cEBpZXRmLm9yZzxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMtdHA8bzpwPjwv
bzpwPjwvcD48L2Rpdj48L2JvZHk+PC9odG1sPg==

------_=_NextPart_001_01CBB336.D57B1EC7--

From ben@niven-jenkins.co.uk  Thu Jan 13 07:39:30 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 611053A6BA8; Thu, 13 Jan 2011 07:39:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.822
X-Spam-Level: 
X-Spam-Status: No, score=-101.822 tagged_above=-999 required=5 tests=[AWL=-1.219, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MuAqir8aTlUR; Thu, 13 Jan 2011 07:39:29 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.64]) by core3.amsl.com (Postfix) with ESMTP id AD9423A6B60; Thu, 13 Jan 2011 07:39:28 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-122-devlan.cachelogic.com) by mail10.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1PdPJ6-0002QR-0n; Thu, 13 Jan 2011 15:41:50 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=utf-8
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <526321.56478.qm@web15605.mail.cnb.yahoo.com>
Date: Thu, 13 Jan 2011 15:41:46 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC7945C9-3C51-42A1-8CA8-692A94B28F2C@niven-jenkins.co.uk>
References: <526321.56478.qm@web15605.mail.cnb.yahoo.com>
To: Larry <larryli888@yahoo.com.cn>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: mpls@ietf.org, jingr@ties.itu.ch, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 15:39:30 -0000

Larry,

On 13 Jan 2011, at 14:55, Larry wrote:

> Hi,
>=20
>    I don't think it is proper to send the LS to ITU-T because the text =
doesn't reflect the requirement from providers.
>    Apparently, draft-bhh based OAM is the most mature solution =
currently. It has been proved by more than 200,000 applications and is =
supported by a lot of operators and vendors.=20
>=20

That may or may not be true, but either way it is irrelevant to the =
liaison.

ITU liaised G.tpoam to IETF. The liaison response Stewart has drafted =
points out that G.tpoam uses technology (draft-bhh) that is not endorsed =
by IETF consensus and points to some risks of doing so, including breach =
of a prior ITU-IETF agreement on how to progress MPLS-TP development.

Everything in the liaison is fact. Whether draft-bhh is good/bad/ugly, =
deployed, supported by operators, etc. is irrelevant, it is not endorsed =
by IETF as a MPLS-TP OAM solution and all the liaison does is point out =
that fact.

FWIW this isn't the first time a group of operators have brought a =
proposal to IETF only to find that the IETF has decided to do something =
else, and I'm sure it won't be the last.=20

Ben

P.S. for some reason email chains related to draft-bhh remind me of this =
Dilbert cartoon http://www.dilbert.com/2010-12-22/



> Best regards,
>=20
>              Han Li
>=20
> =
*************************************************************************
> Han Li, Ph.D=20
> China Mobile Research Institute
> Unit 2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China=20
> Fax: +86 10 63601087=20
> MOBILE: 13501093385=20
> =
*************************************************************************
>=20
>=20
> --- 11=E5=B9=B41=E6=9C=8813=E6=97=A5=EF=BC=8C=E5=91=A8=E5=9B=9B, =
ruiquan.jing@ties.itu.int <ruiquan.jing@ties.itu.int> =E5=86=99=E9=81=93=EF=
=BC=9A
>=20
>> =E5=8F=91=E4=BB=B6=E4=BA=BA: ruiquan.jing@ties.itu.int =
<ruiquan.jing@ties.itu.int>
>> =E4=B8=BB=E9=A2=98: Re: [mpls-tp] [mpls] Draft: Response to Updated =
draft Recommendation G.tpoam [Ref043.02]
>> =E6=94=B6=E4=BB=B6=E4=BA=BA: jingr@ties.itu.ch
>> =E6=8A=84=E9=80=81: mpls-tp@ietf.org
>> =E6=97=A5=E6=9C=9F: 2011=E5=B9=B41=E6=9C=8813=E6=97=A5,=E5=91=A8=E5=9B=9B=
,=E4=B8=8B=E5=8D=884:09
>> Resend to mpls-tp list.
>>=20
>> Quoting jingr@ties.itu.ch:
>>=20
>>> Hi Stewart Bryant,
>>>=20
>>> I don=E2=80=99t agree with the current LS text.
>>>=20
>>> China Telecom support the standardization of Y.1731
>> based MPLS-TP OAM tools
>>> in=20
>>> the ITU-T to meet the urgent and increasing
>> requirements for PTN deployment.=20
>>>=20
>>> It=E2=80=99s a multi-vendor supported, interoperability
>> certificated and feasible=20
>>> solution.  It had been specified in both CCSA
>> (China Communications Standards
>>>=20
>>> Association) and China Telecom=E2=80=99s PTN standard as the
>> only standard OAM=20
>>> mechanism.
>>>=20
>>>  =20
>>>=20
>>> Best Regards
>>>=20
>>> Jing Ruiquan
>>>=20
>>> China=E3=80=80Telecom  Beijing=20
>> Research=E3=80=80Institute
>>>=20
>>>=20
>> =
--------------------------------------------------------------------------=
----
>> --
>>> From: mpls-bounces@ietf.org
>> [mailto:mpls-bounces@ietf.org]
>> On Behalf Of
>>> Stewart=20
>>> Bryant
>>> Sent: Monday, January 10, 2011 6:57 PM
>>> To: mpls@ietf.org
>>> Subject: [mpls] Draft: Response to Updated draft
>> Recommendation G.tpoam=20
>>> [Ref043.02]
>>>=20
>>>=20
>>> I propose to send the following Liaison Response to
>> the ITU-T on Friday=20
>>> 14th January and am posting it to the MPLS WG list for
>> review.=20
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=20
>>>=20
>>> Response to Updated draft Recommendation G.tpoam [Ref
>> 043.02]=20
>>>=20
>>> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>>=20
>>> To: tsbsg15@itu.int,
>> greg.jones@itu.int,
>> hiroshi.ota@itu.int,
>> IAB@ietf.org=20
>>> CC: Greg Jones, swallow@cisco.com,
>> loa@pi.nu, paf@cisco.com=20
>>> stbryant@cisco.com,
>> adrian.farrel@huawei.com,
>> mpls@ietf.org=20
>>> yoichi.maeda@ttc.or.jp,
>> steve.trowbridge@alcatel-lucent.com
>>=20
>>> ghani.abbas@ericsson.com,
>> hhelvoort@huawei.com
>>=20
>>> malcolm.betts@zte.com.cn,
>> kam.lam@alcatel-lucent.com
>>=20
>>>=20
>>> For Action=20
>>>=20
>>> The MPLS Working Group notes that this document
>> contains text describing=20
>>> MPLS-TP OAM protocols not designed and standardized
>> using the IETF=20
>>> Standards process. Specifically it uses material from
>>=20
>>> draft-bhh-mpls-tp-oam-y1731-06.=20
>>>=20
>>> We wish to draw your attention to the status section
>> of=20
>>> draft-bhh-mpls-tp-oam-y1731-06 which states:=20
>>>=20
>>> "Internet-Drafts are draft documents valid for a
>> maximum of six months=20
>>> and may be updated, replaced, or obsoleted by other
>> documents at any=20
>>> time. It is inappropriate to use Internet-Drafts as
>> reference material=20
>>> or to cite them other than as "work in progress".=20
>>>=20
>>> Please also note that since the draft filename starts
>> with the prefix=20
>>> string "draft-bhh" this clearly identifies it to the
>> reader as a=20
>>> document expressing the personal technical views of
>> the authors and=20
>>> hence hence as a document that that does not have any
>> acknowledged level=20
>>> of IETF consensus.=20
>>>=20
>>> Since the text of draft Recommendation for G.tpoam is
>> based on an=20
>>> MPLS-TP OAM protocol not designed within the IETF
>> Standards Process this=20
>>> is a breach of the SG15 agreement with the IETF as
>> published in Report=20
>>> of the first meeting of Working Party 3/15 Transport
>> network structures=20
>>> (2009-2012) (Geneva, 1 =E2=80=93 12 December 2008) which can
>> be found at=20
>>> http://www.itu.int/md/T09-SG15-R-0004/en
>>=20
>>>=20
>>> Please confirm that the ITU-T intends to continue with
>> the joint work on=20
>>> MPLS-TP and that the ITU-T will align this
>> recommendation with the IETF=20
>>> MPLS-TP OAM design before advancing this document
>> through the ITU-T=20
>>> publication process.=20
>>>=20
>>> The MPLS Working Group would also like to draw the
>> attention of ITU-T=20
>>> SG15 to the IETF copyright rules. Please see=20
>>> =
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-
>>> 20091228.htm=20
>>> for further details.=20
>>>=20
>>> Since this draft Recommendation contains text in which
>> the ITU-T SG15=20
>>> has proposed making changes to IETF protocols without
>> the approval of=20
>>> the IETF, the MPLS Working Group have referred this
>> liaison to the IAB=20
>>> for their consideration.=20
>>>=20
>>>=20
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=20
>>> _______________________________________________=20
>>> mpls mailing list=20
>>> mpls@ietf.org=20
>>> https://www.ietf.org/mailman/listinfo/mpls=20
>>>=20
>>>=20
>>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>=20
>=20
>=20
>=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


From huubatwork@gmail.com  Thu Jan 13 14:16:34 2011
Return-Path: <huubatwork@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E62C3A6BF9; Thu, 13 Jan 2011 14:16:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.481
X-Spam-Level: 
X-Spam-Status: No, score=-3.481 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pU+5JzmK9tJ; Thu, 13 Jan 2011 14:16:33 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id B20223A6BF8; Thu, 13 Jan 2011 14:16:32 -0800 (PST)
Received: by ewy8 with SMTP id 8so1215638ewy.31 for <multiple recipients>; Thu, 13 Jan 2011 14:18:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:disposition-notification-to:date :from:user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=yZEKO+tVFbDsWHA//ZOUrEkkgW2k7cOHVex4FJkeZNU=; b=q+XFgDgIq6zLWUJhA9dHlWlDL8g/CNrPeL/0So6ST624JeJNDX/NnMTrNF2999AVo2 MtlysCa6jygr7Qjftzd44YA62FbiVg/8WmzGRJOOf1qJIa3u6rNQ6q3zaUgr7VkxTrwa lZoLstrJC2khNRIc0s42mW278N/9MB/+jZ7Zs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; b=fbpgkRLTzA7iCAkk/rCV6l3GKMbJvIBYSYP5bYiNE7WPHHKmJpv0aTd93ZyGnkydVr JLW2z6TlmCfvrhftbJ1CrX60MorTZuDIl5tiCai3VLkeX7wf7ubSafq/1R92ZeKg4liy MB20IfvePm+LQlpjQuiLpdce6rIDwrwrOmP78=
Received: by 10.213.23.7 with SMTP id p7mr147613ebb.79.1294957135203; Thu, 13 Jan 2011 14:18:55 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl [77.250.51.60]) by mx.google.com with ESMTPS id t5sm407305eeh.20.2011.01.13.14.18.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 13 Jan 2011 14:18:54 -0800 (PST)
Message-ID: <4D2F7A4C.80304@gmail.com>
Date: Thu, 13 Jan 2011 23:18:52 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: mpls@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
References: <4D2AE56A.3060200@cisco.com>
In-Reply-To: <4D2AE56A.3060200@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 22:16:34 -0000

Hello Stewart,

You wrote:

> I propose to send the following Liaison Response to the ITU-T on Friday
> 14th January and am posting it to the MPLS WG list for review.

I do not support sending the liaison as proposed.

We should restrict it to the first paragraph noting that the file
that should be reviewed is missing and ask for sending the missing
file so it can be reviewed by the WG.

The remainder of the text is based on assumptions and not on facts.

Regards, Huub.


> =========
>
> Response to Updated draft Recommendation G.8121 [Ref 042.02]
>
> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
> To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, IAB@ietf.org
> CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com
> stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org
> yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
> ghani.abbas@ericsson.com, hhelvoort@huawei.com
> malcolm.betts@zte.com.cn, kam.lam@alcatel-lucent.com
>
> For Action
>
> Unfortunately ITU-T document WD19r2 was not attached to this liaison,
> and thus the MPLS Working Group is unable to comment on its content at
> this time.
>
> It is stated in the liaison that the modifications to this draft
> Recommendation are based on draft-bhh-mpls-tp-oam-y1731-06. Please may
> we draw your attention to the status section of
> draft-bhh-mpls-tp-oam-y1731-06 which states
>
> "Internet-Drafts are draft documents valid for a maximum of six months
> and may be updated, replaced, or obsoleted by other documents at any
> time. It is inappropriate to use Internet-Drafts as reference material
> or to cite them other than as "work in progress".
>
> Please also note that since the draft filename starts with the prefix
> string "draft-bhh" this clearly identifies it to the reader as a
> document expressing the personal technical views of the authors and
> hence hence as a document that that does not have any acknowledged level
> of IETF consensus.
>
> If this draft Recommendation for G.8121 is based on an MPLS-TP OAM
> protocol not designed within the IETF Standards Process, the MPLS
> Working Group believe that this would be in breach of the SG15 agreement
> with the IETF as published in Report of the first meeting of Working
> Party 3/15 Transport network structures (2009-2012) (Geneva, 1 – 12
> December 2008) which can be found at
> http://www.itu.int/md/T09-SG15-R-0004/en
>
> The MPLS Working Group would also like to draw the attention of ITU-T
> SG15 to the IETF copyright rules. Please see
> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.htm
> for further details.
>
> We have referred this liaison to the IAB for their consideration.
>
>
> ===========
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


-- 
*****************************************************************
                          我爱外点一七三一

From jdrake@juniper.net  Thu Jan 13 14:26:58 2011
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79EAE3A6C02; Thu, 13 Jan 2011 14:26:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oqdrrlxe0bug; Thu, 13 Jan 2011 14:26:57 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by core3.amsl.com (Postfix) with ESMTP id B55FF3A6BFE; Thu, 13 Jan 2011 14:26:56 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKTS98wKKtDwwS3neUDs93rx1f3xjCqZrr@postini.com; Thu, 13 Jan 2011 14:29:20 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Thu, 13 Jan 2011 14:25:01 -0800
From: John E Drake <jdrake@juniper.net>
To: Huub van Helvoort <huubatwork@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>,  "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Thu, 13 Jan 2011 14:26:57 -0800
Thread-Topic: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
Thread-Index: Acuzb61fIYYPAbIKTHyDcIrIhN6cKQAARNSw
Message-ID: <5E893DB832F57341992548CDBB33316398C6F3BCCC@EMBX01-HQ.jnpr.net>
References: <4D2AE56A.3060200@cisco.com> <4D2F7A4C.80304@gmail.com>
In-Reply-To: <4D2F7A4C.80304@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 22:26:58 -0000

SW5saW5lDQoNClNlbnQgZnJvbSBteSBpUGhvbmUNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+IEZyb206IG1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOm1wbHMtdHAt
Ym91bmNlc0BpZXRmLm9yZ10gT24NCj4gQmVoYWxmIE9mIEh1dWIgdmFuIEhlbHZvb3J0DQo+IFNl
bnQ6IFRodXJzZGF5LCBKYW51YXJ5IDEzLCAyMDExIDI6MTkgUE0NCj4gVG86IG1wbHNAaWV0Zi5v
cmc7IG1wbHMtdHBAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFttcGxzLXRwXSBbbXBsc10gRHJh
ZnQ6IFJlc3BvbnNlIHRvIFVwZGF0ZWQgZHJhZnQNCj4gUmVjb21tZW5kYXRpb24gRy44MTIxIFtS
ZWYgMDQyLjAyXQ0KPiANCj4gSGVsbG8gU3Rld2FydCwNCj4gDQo+IFlvdSB3cm90ZToNCj4gDQo+
ID4gSSBwcm9wb3NlIHRvIHNlbmQgdGhlIGZvbGxvd2luZyBMaWFpc29uIFJlc3BvbnNlIHRvIHRo
ZSBJVFUtVCBvbg0KPiBGcmlkYXkNCj4gPiAxNHRoIEphbnVhcnkgYW5kIGFtIHBvc3RpbmcgaXQg
dG8gdGhlIE1QTFMgV0cgbGlzdCBmb3IgcmV2aWV3Lg0KPiANCj4gSSBkbyBub3Qgc3VwcG9ydCBz
ZW5kaW5nIHRoZSBsaWFpc29uIGFzIHByb3Bvc2VkLg0KPiANCj4gV2Ugc2hvdWxkIHJlc3RyaWN0
IGl0IHRvIHRoZSBmaXJzdCBwYXJhZ3JhcGggbm90aW5nIHRoYXQgdGhlIGZpbGUNCj4gdGhhdCBz
aG91bGQgYmUgcmV2aWV3ZWQgaXMgbWlzc2luZyBhbmQgYXNrIGZvciBzZW5kaW5nIHRoZSBtaXNz
aW5nDQo+IGZpbGUgc28gaXQgY2FuIGJlIHJldmlld2VkIGJ5IHRoZSBXRy4NCj4gDQo+IFRoZSBy
ZW1haW5kZXIgb2YgdGhlIHRleHQgaXMgYmFzZWQgb24gYXNzdW1wdGlvbnMgYW5kIG5vdCBvbiBm
YWN0cy4NCg0KSkQ6ICBUaGUgYWJvdmUgc3RhdGVtZW50IGlzIGFuIGFzc2VydGlvbiBub3Qgc3Vw
cG9ydGVkIGJ5IGZhY3RzLg0KDQo+IA0KPiBSZWdhcmRzLCBIdXViLg0KPiANCj4gDQo=

From huubatwork@gmail.com  Thu Jan 13 14:30:28 2011
Return-Path: <huubatwork@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9A7728B56A; Thu, 13 Jan 2011 14:30:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.191
X-Spam-Level: 
X-Spam-Status: No, score=-3.191 tagged_above=-999 required=5 tests=[AWL=-0.192, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OwEIj9JVIFTg; Thu, 13 Jan 2011 14:30:27 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id AC61B3A6C06; Thu, 13 Jan 2011 14:30:26 -0800 (PST)
Received: by eyd10 with SMTP id 10so1225929eyd.31 for <multiple recipients>; Thu, 13 Jan 2011 14:32:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:disposition-notification-to:date :from:user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=IkTaytcFV7wMpkVwDzK+eGDIfYeJ36km1DIcJy/thaw=; b=vLs6nLCQSBiOBYgQVZjJcDSM+1Nky6GVzMdi1yxAMykyGa/eWSmhfm+XMbYDAgpHyH N132oADYO2ky0ZTJu3/iZOHBf1FempvOCJG7Aov8HKlXmlZPpbtvols+ZMn69XV1GOrV dF64TJYVP42ZlqiUS709nMHv+Ze5VrBsvO4IU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; b=I+NbHAjal+961Vgd/OOPnqgxykSWxiPiSr3mU+37e02cOuNIGuZmN8u7aefHJTDVSv ZGHVHABrBxkMsWU+Oexj5SPaQfC5DbTpi5EgEIy9oKDtJr3hP/4k1eZiHk4PA7t5qCMU eoQHHpEPeGM1yf0EJkBakY+XTiR3nWLLvJIFo=
Received: by 10.213.4.198 with SMTP id 6mr984583ebs.74.1294957969688; Thu, 13 Jan 2011 14:32:49 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl [77.250.51.60]) by mx.google.com with ESMTPS id x54sm415404eeh.23.2011.01.13.14.32.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 13 Jan 2011 14:32:48 -0800 (PST)
Message-ID: <4D2F7D8E.9040505@gmail.com>
Date: Thu, 13 Jan 2011 23:32:46 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: mpls@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
References: <526321.56478.qm@web15605.mail.cnb.yahoo.com>	<EC7945C9-3C51-42A1-8CA8-692A94B28F2C@niven-jenkins.co.uk>	<4D2F27F1.1070209@cisco.com>	<6873FACCBB5DDD4D88AABD78A8E483A468CE4D0311@EUSAACMS0703.eamcs.ericsson.se> <4D2F47F9.8040701@cisco.com>
In-Reply-To: <4D2F47F9.8040701@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft	Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 22:30:29 -0000

Hello Stewart,

You asked:

> Does anyone disagree with the statement that David makes?

I disagree with this statement in relation to this liaison.

The draft recommendation G.tpoam that was sent for review does
not contain a reference to draft-bhh at all.

Also the statements about validity and copyright are irrelevant.

Regards, Huub.


==============
> On 13/01/2011 17:09, David Sinicrope wrote:
>> It seems that reference and use of draft-bhh is in violation of the
>> ITU-T external cooperation agreement "Referencing A.5 Qualified
>> Organizations" text found at
>> http://www.itu.int/en/ITU-T/extcoop/Pages/sdo.aspx under the
>> Referencing IETF Documents link.
>> In particular clause 10 of this document states: (See 2nd sentence.)
>>
>> "10 Other: If a study group decides to make the reference to an IETF
>> RFC, the reference should always be made by RFC number (and not by
>> other designations such as STD, BCP, etc.). References should not be
>> made to documents referred to as "Internet Drafts" or to IETF RFCs
>> categorized as Historic or Experimental. Normative references must
>> only be made to IETF RFCs that are Standards Track or to Informational
>> RFCs that have IETF consensus."
>>
>> Is this not correct? If correct, shouldn't this also be pointed out in
>> the liaison?
>> Dave
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>> Of Stewart Bryant
>> Sent: Thursday, January 13, 2011 11:27 AM
>> To: mpls@ietf.org
>> Subject: Re: [mpls] [mpls-tp] Draft: Response to Updated draft
>> Recommendation G.tpoam [Ref043.02]
>>
>> Exactly Ben.
>>
>> The Liaison is list of statements of relevant facts, and none of the
>> contra points dispute those facts.
>>
>> Stewart
>>
>> On 13/01/2011 15:41, Ben Niven-Jenkins wrote:
>>> Larry,
>>>
>>> On 13 Jan 2011, at 14:55, Larry wrote:
>>>
>>>> Hi,
>>>>
>>>> I don't think it is proper to send the LS to ITU-T because the text
>>>> doesn't reflect the requirement from providers.
>>>> Apparently, draft-bhh based OAM is the most mature solution
>>>> currently. It has been proved by more than 200,000 applications and
>>>> is supported by a lot of operators and vendors.
>>>>
>>> That may or may not be true, but either way it is irrelevant to the
>>> liaison.
>>>
>>> ITU liaised G.tpoam to IETF. The liaison response Stewart has drafted
>>> points out that G.tpoam uses technology (draft-bhh) that is not
>>> endorsed by IETF consensus and points to some risks of doing so,
>>> including breach of a prior ITU-IETF agreement on how to progress
>>> MPLS-TP development.
>>>
>>> Everything in the liaison is fact. Whether draft-bhh is
>>> good/bad/ugly, deployed, supported by operators, etc. is irrelevant,
>>> it is not endorsed by IETF as a MPLS-TP OAM solution and all the
>>> liaison does is point out that fact.
>>>
>>> FWIW this isn't the first time a group of operators have brought a
>>> proposal to IETF only to find that the IETF has decided to do
>>> something else, and I'm sure it won't be the last.
>>>
>>> Ben
>>>
>>> P.S. for some reason email chains related to draft-bhh remind me of
>>> this Dilbert cartoon http://www.dilbert.com/2010-12-22/
>>>
>>>
>>>
>>>> Best regards,
>>>>
>>>> Han Li
>>>>
>>>> *********************************************************************
>>>> ****
>>>> Han Li, Ph.D
>>>> China Mobile Research Institute
>>>> Unit 2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China
>>>> Fax: +86 10 63601087
>>>> MOBILE: 13501093385
>>>> *********************************************************************
>>>> ****
>>>>
>>>>
>>>> --- 11年1月13日，周四,
>>>> ruiquan.jing@ties.itu.int<ruiquan.jing@ties.itu.int>
>>>> 写道：
>>>>
>>>>> 发件人: ruiquan.jing@ties.itu.int<ruiquan.jing@ties.itu.int>
>>>>> 主题: Re: [mpls-tp] [mpls] Draft: Response to Updated draft
>>>>> Recommendation G.tpoam [Ref043.02]
>>>>> 收件人: jingr@ties.itu.ch
>>>>> 抄送: mpls-tp@ietf.org
>>>>> 日期: 2011年1月13日,周四,下午4:09
>>>>> Resend to mpls-tp list.
>>>>>
>>>>> Quoting jingr@ties.itu.ch:
>>>>>
>>>>>> Hi Stewart Bryant,
>>>>>>
>>>>>> I don’t agree with the current LS text.
>>>>>>
>>>>>> China Telecom support the standardization of Y.1731
>>>>> based MPLS-TP OAM tools
>>>>>> in
>>>>>> the ITU-T to meet the urgent and increasing
>>>>> requirements for PTN deployment.
>>>>>> It’s a multi-vendor supported, interoperability
>>>>> certificated and feasible
>>>>>> solution. It had been specified in both CCSA
>>>>> (China Communications Standards
>>>>>> Association) and China Telecom’s PTN standard as the
>>>>> only standard OAM
>>>>>> mechanism.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Best Regards
>>>>>>
>>>>>> Jing Ruiquan
>>>>>>
>>>>>> China　Telecom Beijing
>>>>> Research　Institute
>>>>> --------------------------------------------------------------------
>>>>> ----------
>>>>> --
>>>>>> From: mpls-bounces@ietf.org
>>>>> [mailto:mpls-bounces@ietf.org]
>>>>> On Behalf Of
>>>>>> Stewart
>>>>>> Bryant
>>>>>> Sent: Monday, January 10, 2011 6:57 PM
>>>>>> To: mpls@ietf.org
>>>>>> Subject: [mpls] Draft: Response to Updated draft
>>>>> Recommendation G.tpoam
>>>>>> [Ref043.02]
>>>>>>
>>>>>>
>>>>>> I propose to send the following Liaison Response to
>>>>> the ITU-T on Friday
>>>>>> 14th January and am posting it to the MPLS WG list for
>>>>> review.
>>>>>> =======
>>>>>>
>>>>>> Response to Updated draft Recommendation G.tpoam [Ref
>>>>> 043.02]
>>>>>> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>>>>>> To: tsbsg15@itu.int,
>>>>> greg.jones@itu.int,
>>>>> hiroshi.ota@itu.int,
>>>>> IAB@ietf.org
>>>>>> CC: Greg Jones, swallow@cisco.com,
>>>>> loa@pi.nu, paf@cisco.com
>>>>>> stbryant@cisco.com,
>>>>> adrian.farrel@huawei.com,
>>>>> mpls@ietf.org
>>>>>> yoichi.maeda@ttc.or.jp,
>>>>> steve.trowbridge@alcatel-lucent.com
>>>>>
>>>>>> ghani.abbas@ericsson.com,
>>>>> hhelvoort@huawei.com
>>>>>
>>>>>> malcolm.betts@zte.com.cn,
>>>>> kam.lam@alcatel-lucent.com
>>>>>
>>>>>> For Action
>>>>>>
>>>>>> The MPLS Working Group notes that this document
>>>>> contains text describing
>>>>>> MPLS-TP OAM protocols not designed and standardized
>>>>> using the IETF
>>>>>> Standards process. Specifically it uses material from
>>>>>> draft-bhh-mpls-tp-oam-y1731-06.
>>>>>>
>>>>>> We wish to draw your attention to the status section
>>>>> of
>>>>>> draft-bhh-mpls-tp-oam-y1731-06 which states:
>>>>>>
>>>>>> "Internet-Drafts are draft documents valid for a
>>>>> maximum of six months
>>>>>> and may be updated, replaced, or obsoleted by other
>>>>> documents at any
>>>>>> time. It is inappropriate to use Internet-Drafts as
>>>>> reference material
>>>>>> or to cite them other than as "work in progress".
>>>>>>
>>>>>> Please also note that since the draft filename starts
>>>>> with the prefix
>>>>>> string "draft-bhh" this clearly identifies it to the
>>>>> reader as a
>>>>>> document expressing the personal technical views of
>>>>> the authors and
>>>>>> hence hence as a document that that does not have any
>>>>> acknowledged level
>>>>>> of IETF consensus.
>>>>>>
>>>>>> Since the text of draft Recommendation for G.tpoam is
>>>>> based on an
>>>>>> MPLS-TP OAM protocol not designed within the IETF
>>>>> Standards Process this
>>>>>> is a breach of the SG15 agreement with the IETF as
>>>>> published in Report
>>>>>> of the first meeting of Working Party 3/15 Transport
>>>>> network structures
>>>>>> (2009-2012) (Geneva, 1 – 12 December 2008) which can
>>>>> be found at
>>>>>> http://www.itu.int/md/T09-SG15-R-0004/en
>>>>>> Please confirm that the ITU-T intends to continue with
>>>>> the joint work on
>>>>>> MPLS-TP and that the ITU-T will align this
>>>>> recommendation with the IETF
>>>>>> MPLS-TP OAM design before advancing this document
>>>>> through the ITU-T
>>>>>> publication process.
>>>>>>
>>>>>> The MPLS Working Group would also like to draw the
>>>>> attention of ITU-T
>>>>>> SG15 to the IETF copyright rules. Please see
>>>>>> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Pol
>>>>>> icy-
>>>>>> 20091228.htm
>>>>>> for further details.
>>>>>>
>>>>>> Since this draft Recommendation contains text in which
>>>>> the ITU-T SG15
>>>>>> has proposed making changes to IETF protocols without
>>>>> the approval of
>>>>>> the IETF, the MPLS Working Group have referred this
>>>>> liaison to the IAB
>>>>>> for their consideration.
>>>>>>
>>>>>>
>>>>>>
>>>>>> =========
>>>>>> _______________________________________________
>>>>>> mpls mailing list
>>>>>> mpls@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> mpls-tp mailing list
>>>>> mpls-tp@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>>>>
>>>>
>>>> _______________________________________________
>>>> mpls-tp mailing list
>>>> mpls-tp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>
>> --
>> For corporate legal information go to:
>>
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>


-- 
*****************************************************************
                          我爱外点一七三一

From nurit.sprecher@nsn.com  Thu Jan 13 14:42:31 2011
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2902128B56A; Thu, 13 Jan 2011 14:42:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.654
X-Spam-Level: 
X-Spam-Status: No, score=-4.654 tagged_above=-999 required=5 tests=[AWL=1.945,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOtdtozws7ZS; Thu, 13 Jan 2011 14:42:30 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 5F7DE28B23E; Thu, 13 Jan 2011 14:42:29 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0DMimki022729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Jan 2011 23:44:48 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0DMilOs029332; Thu, 13 Jan 2011 23:44:48 +0100
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 13 Jan 2011 23:44:20 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Thu, 13 Jan 2011 23:44:20 +0100
Message-ID: <077E41CFFD002C4CAB7DFA4386A532640332E310@DEMUEXC014.nsn-intra.net>
In-Reply-To: <4D2F7A4C.80304@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
Thread-Index: Acuzb+Nb8KRr+mUjSkyFe5VeJgEzywAARscg
References: <4D2AE56A.3060200@cisco.com> <4D2F7A4C.80304@gmail.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Huub van Helvoort" <huubatwork@gmail.com>, <mpls@ietf.org>, <mpls-tp@ietf.org>
X-OriginalArrivalTime: 13 Jan 2011 22:44:20.0962 (UTC) FILETIME=[6B194420:01CBB373]
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 22:42:31 -0000

SHV1YiwNCkRvIHlvdSBzYXkgdGhhdCB0aGUgcGFyYWdyYXBoIHNheWluZyAiSXQgaXMgc3RhdGVk
IGluIHRoZSBsaWFpc29uIHRoYXQgdGhlIG1vZGlmaWNhdGlvbnMgdG8gdGhpcyBkcmFmdCBSZWNv
bW1lbmRhdGlvbiBhcmUgYmFzZWQgb24gZHJhZnQtYmhoLW1wbHMtdHAtb2FtLXkxNzMxLTA2IiBp
cyBhbiBhc3N1bXB0aW9uPw0KSXQgd2FzIHN0YXRlZCBpbiB0aGUgbGlhaXNvbiBhcyB3ZWxsIGFz
IGluIHRoZSBCZXJsaW4gbWVldGluZyByZXBvcnQuDQpJdCBpcyBhIGZhY3QhDQpJIHRoaW5rIHRo
YXQgYWxsIHRoZSByZXN0IG9mIHRoZSBwYXJhZ3JhcGhzIGFyZSBmYWN0cyBhcyB3ZWxsIQ0KQmVz
dCByZWdhcmRzLA0KTnVyaXQNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IG1w
bHMtdHAtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOm1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mIGV4dCBIdXViIHZhbiBIZWx2b29ydA0KU2VudDogRnJpZGF5LCBKYW51YXJ5
IDE0LCAyMDExIDEyOjE5IEFNDQpUbzogbXBsc0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0K
U3ViamVjdDogUmU6IFttcGxzLXRwXSBbbXBsc10gRHJhZnQ6IFJlc3BvbnNlIHRvIFVwZGF0ZWQg
ZHJhZnQgUmVjb21tZW5kYXRpb24gRy44MTIxIFtSZWYgMDQyLjAyXQ0KDQpIZWxsbyBTdGV3YXJ0
LA0KDQpZb3Ugd3JvdGU6DQoNCj4gSSBwcm9wb3NlIHRvIHNlbmQgdGhlIGZvbGxvd2luZyBMaWFp
c29uIFJlc3BvbnNlIHRvIHRoZSBJVFUtVCBvbiBGcmlkYXkNCj4gMTR0aCBKYW51YXJ5IGFuZCBh
bSBwb3N0aW5nIGl0IHRvIHRoZSBNUExTIFdHIGxpc3QgZm9yIHJldmlldy4NCg0KSSBkbyBub3Qg
c3VwcG9ydCBzZW5kaW5nIHRoZSBsaWFpc29uIGFzIHByb3Bvc2VkLg0KDQpXZSBzaG91bGQgcmVz
dHJpY3QgaXQgdG8gdGhlIGZpcnN0IHBhcmFncmFwaCBub3RpbmcgdGhhdCB0aGUgZmlsZQ0KdGhh
dCBzaG91bGQgYmUgcmV2aWV3ZWQgaXMgbWlzc2luZyBhbmQgYXNrIGZvciBzZW5kaW5nIHRoZSBt
aXNzaW5nDQpmaWxlIHNvIGl0IGNhbiBiZSByZXZpZXdlZCBieSB0aGUgV0cuDQoNClRoZSByZW1h
aW5kZXIgb2YgdGhlIHRleHQgaXMgYmFzZWQgb24gYXNzdW1wdGlvbnMgYW5kIG5vdCBvbiBmYWN0
cy4NCg0KUmVnYXJkcywgSHV1Yi4NCg0KDQo+ID09PT09PT09PQ0KPg0KPiBSZXNwb25zZSB0byBV
cGRhdGVkIGRyYWZ0IFJlY29tbWVuZGF0aW9uIEcuODEyMSBbUmVmIDA0Mi4wMl0NCj4NCj4gRnJv
bTogSUVURiBMaWFpc29uIHRvIElUVS1UIG9uIE1QTFMgc3RicnlhbnRAY2lzY28uY29tDQo+IFRv
OiB0c2JzZzE1QGl0dS5pbnQsIGdyZWcuam9uZXNAaXR1LmludCwgaGlyb3NoaS5vdGFAaXR1Lmlu
dCwgSUFCQGlldGYub3JnDQo+IENDOiBHcmVnIEpvbmVzLCBzd2FsbG93QGNpc2NvLmNvbSwgbG9h
QHBpLm51LCBwYWZAY2lzY28uY29tDQo+IHN0YnJ5YW50QGNpc2NvLmNvbSwgYWRyaWFuLmZhcnJl
bEBodWF3ZWkuY29tLCBtcGxzQGlldGYub3JnDQo+IHlvaWNoaS5tYWVkYUB0dGMub3IuanAsIHN0
ZXZlLnRyb3dicmlkZ2VAYWxjYXRlbC1sdWNlbnQuY29tDQo+IGdoYW5pLmFiYmFzQGVyaWNzc29u
LmNvbSwgaGhlbHZvb3J0QGh1YXdlaS5jb20NCj4gbWFsY29sbS5iZXR0c0B6dGUuY29tLmNuLCBr
YW0ubGFtQGFsY2F0ZWwtbHVjZW50LmNvbQ0KPg0KPiBGb3IgQWN0aW9uDQo+DQo+IFVuZm9ydHVu
YXRlbHkgSVRVLVQgZG9jdW1lbnQgV0QxOXIyIHdhcyBub3QgYXR0YWNoZWQgdG8gdGhpcyBsaWFp
c29uLA0KPiBhbmQgdGh1cyB0aGUgTVBMUyBXb3JraW5nIEdyb3VwIGlzIHVuYWJsZSB0byBjb21t
ZW50IG9uIGl0cyBjb250ZW50IGF0DQo+IHRoaXMgdGltZS4NCj4NCj4gSXQgaXMgc3RhdGVkIGlu
IHRoZSBsaWFpc29uIHRoYXQgdGhlIG1vZGlmaWNhdGlvbnMgdG8gdGhpcyBkcmFmdA0KPiBSZWNv
bW1lbmRhdGlvbiBhcmUgYmFzZWQgb24gZHJhZnQtYmhoLW1wbHMtdHAtb2FtLXkxNzMxLTA2LiBQ
bGVhc2UgbWF5DQo+IHdlIGRyYXcgeW91ciBhdHRlbnRpb24gdG8gdGhlIHN0YXR1cyBzZWN0aW9u
IG9mDQo+IGRyYWZ0LWJoaC1tcGxzLXRwLW9hbS15MTczMS0wNiB3aGljaCBzdGF0ZXMNCj4NCj4g
IkludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0g
b2Ygc2l4IG1vbnRocw0KPiBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0
ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0KPiB0aW1lLiBJdCBpcyBpbmFwcHJvcHJpYXRl
IHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlIG1hdGVyaWFsDQo+IG9yIHRvIGNp
dGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzIi4NCj4NCj4gUGxlYXNlIGFs
c28gbm90ZSB0aGF0IHNpbmNlIHRoZSBkcmFmdCBmaWxlbmFtZSBzdGFydHMgd2l0aCB0aGUgcHJl
Zml4DQo+IHN0cmluZyAiZHJhZnQtYmhoIiB0aGlzIGNsZWFybHkgaWRlbnRpZmllcyBpdCB0byB0
aGUgcmVhZGVyIGFzIGENCj4gZG9jdW1lbnQgZXhwcmVzc2luZyB0aGUgcGVyc29uYWwgdGVjaG5p
Y2FsIHZpZXdzIG9mIHRoZSBhdXRob3JzIGFuZA0KPiBoZW5jZSBoZW5jZSBhcyBhIGRvY3VtZW50
IHRoYXQgdGhhdCBkb2VzIG5vdCBoYXZlIGFueSBhY2tub3dsZWRnZWQgbGV2ZWwNCj4gb2YgSUVU
RiBjb25zZW5zdXMuDQo+DQo+IElmIHRoaXMgZHJhZnQgUmVjb21tZW5kYXRpb24gZm9yIEcuODEy
MSBpcyBiYXNlZCBvbiBhbiBNUExTLVRQIE9BTQ0KPiBwcm90b2NvbCBub3QgZGVzaWduZWQgd2l0
aGluIHRoZSBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLCB0aGUgTVBMUw0KPiBXb3JraW5nIEdyb3Vw
IGJlbGlldmUgdGhhdCB0aGlzIHdvdWxkIGJlIGluIGJyZWFjaCBvZiB0aGUgU0cxNSBhZ3JlZW1l
bnQNCj4gd2l0aCB0aGUgSUVURiBhcyBwdWJsaXNoZWQgaW4gUmVwb3J0IG9mIHRoZSBmaXJzdCBt
ZWV0aW5nIG9mIFdvcmtpbmcNCj4gUGFydHkgMy8xNSBUcmFuc3BvcnQgbmV0d29yayBzdHJ1Y3R1
cmVzICgyMDA5LTIwMTIpIChHZW5ldmEsIDEg4oCTIDEyDQo+IERlY2VtYmVyIDIwMDgpIHdoaWNo
IGNhbiBiZSBmb3VuZCBhdA0KPiBodHRwOi8vd3d3Lml0dS5pbnQvbWQvVDA5LVNHMTUtUi0wMDA0
L2VuDQo+DQo+IFRoZSBNUExTIFdvcmtpbmcgR3JvdXAgd291bGQgYWxzbyBsaWtlIHRvIGRyYXcg
dGhlIGF0dGVudGlvbiBvZiBJVFUtVA0KPiBTRzE1IHRvIHRoZSBJRVRGIGNvcHlyaWdodCBydWxl
cy4gUGxlYXNlIHNlZQ0KPiBodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8vYXJj
aGl2ZS9JRVRGLVRydXN0LUxpY2Vuc2UtUG9saWN5LTIwMDkxMjI4Lmh0bQ0KPiBmb3IgZnVydGhl
ciBkZXRhaWxzLg0KPg0KPiBXZSBoYXZlIHJlZmVycmVkIHRoaXMgbGlhaXNvbiB0byB0aGUgSUFC
IGZvciB0aGVpciBjb25zaWRlcmF0aW9uLg0KPg0KPg0KPiA9PT09PT09PT09PQ0KPiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBtcGxzIG1haWxpbmcg
bGlzdA0KPiBtcGxzQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbXBscw0KDQoNCi0tIA0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCiAgICAgICAgICAgICAgICAgICAgICAgICAg
5oiR54ix5aSW54K55LiA5LiD5LiJ5LiADQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KbXBscy10cCBtYWlsaW5nIGxpc3QNCm1wbHMtdHBAaWV0Zi5vcmcN
Cmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscy10cA0K

From eosborne@cisco.com  Thu Jan 13 14:49:13 2011
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D18F28C0DD; Thu, 13 Jan 2011 14:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.177
X-Spam-Level: 
X-Spam-Status: No, score=-10.177 tagged_above=-999 required=5 tests=[AWL=-0.178, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAhvMgejN9GZ; Thu, 13 Jan 2011 14:49:12 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 87ED728B23E; Thu, 13 Jan 2011 14:49:11 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFcRL02tJXG+/2dsb2JhbACECJ9hZHOkHIpVjWCBIYM3dASEaIlQ
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rtp-iport-2.cisco.com with ESMTP; 13 Jan 2011 22:51:34 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p0DMpYps013548;  Thu, 13 Jan 2011 22:51:34 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 13 Jan 2011 16:51:34 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Thu, 13 Jan 2011 16:51:32 -0600
Message-ID: <D29E470202D67745B61059870F433B54040D8FB2@XMB-RCD-202.cisco.com>
In-Reply-To: <4D2F7D8E.9040505@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [mpls] Draft: Response to Updated draft	Recommendation G.tpoam [Ref043.02]
Thread-Index: AcuzcdYOACJqkL8SQ1KnmKq/hzcCPgAAFzOA
References: <526321.56478.qm@web15605.mail.cnb.yahoo.com>	<EC7945C9-3C51-42A1-8CA8-692A94B28F2C@niven-jenkins.co.uk>	<4D2F27F1.1070209@cisco.com>	<6873FACCBB5DDD4D88AABD78A8E483A468CE4D0311@EUSAACMS0703.eamcs.ericsson.se><4D2F47F9.8040701@cisco.com> <4D2F7D8E.9040505@gmail.com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Huub van Helvoort" <huubatwork@gmail.com>, <mpls@ietf.org>, <mpls-tp@ietf.org>
X-OriginalArrivalTime: 13 Jan 2011 22:51:34.0250 (UTC) FILETIME=[6D5BC4A0:01CBB374]
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft	Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 22:49:13 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogbXBscy10cC1ib3VuY2Vz
QGlldGYub3JnIFttYWlsdG86bXBscy10cC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYNCj4g
T2YgSHV1YiB2YW4gSGVsdm9vcnQNCj4gU2VudDogVGh1cnNkYXksIEphbnVhcnkgMTMsIDIwMTEg
NTozMyBQTQ0KPiBUbzogbXBsc0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KPiBTdWJqZWN0
OiBSZTogW21wbHMtdHBdIFttcGxzXSBEcmFmdDogUmVzcG9uc2UgdG8gVXBkYXRlZCBkcmFmdA0K
PiBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtIFtSZWYwNDMuMDJdDQo+IA0KPiBIZWxsbyBTdGV3YXJ0
LA0KPiANCj4gWW91IGFza2VkOg0KPiANCj4gPiBEb2VzIGFueW9uZSBkaXNhZ3JlZSB3aXRoIHRo
ZSBzdGF0ZW1lbnQgdGhhdCBEYXZpZCBtYWtlcz8NCj4gDQo+IEkgZGlzYWdyZWUgd2l0aCB0aGlz
IHN0YXRlbWVudCBpbiByZWxhdGlvbiB0byB0aGlzIGxpYWlzb24uDQo+IA0KPiBUaGUgZHJhZnQg
cmVjb21tZW5kYXRpb24gRy50cG9hbSB0aGF0IHdhcyBzZW50IGZvciByZXZpZXcgZG9lcyBub3Qg
Y29udGFpbg0KPiBhIHJlZmVyZW5jZSB0byBkcmFmdC1iaGggYXQgYWxsLg0KDQpUaGUgbGlhc29u
IGlzIGhlcmU6IFtodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2xpYWlzb24vOTgzL10NCmFu
ZCBpdCByZWZlcmVuY2VzICJMUzIzMyAtIFVwZGF0ZWQgZHJhZnQgUmVjb21tZW5kYXRpb24gRy50
cG9hbSBbUmVmIDA0My4wMV0gLSBwZGYgYm9keSIgW2h0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZG9jdW1lbnRzL0xJQUlTT04vZmlsZTExNTEucGRmXQ0Kd2hpY2ggc2F5cw0KDQotLS0tDQpB
dCB0aGUgQmVybGluIGludGVyaW0gbWVldGluZyBvbiBNUExTLVRQIGZ1cnRoZXIgd29yayB3YXMg
dW5kZXJ0YWtlbiBvbiB0aGUgZGV2ZWxvcG1lbnQgb2YgdGhlIA0KT0FNIFJlY29tbWVuZGF0aW9u
IEcudHBvYW0uICBUaGlzIHZlcnNpb24gd2FzIGRldmVsb3BlZCB1c2luZyBhbGwgb2YgdGhlIHJl
bGV2YW50IGlucHV0IA0KZG9jdW1lbnRzIHRvIHRoZSBtZWV0aW5nIGFuZCBpcyBiYXNlZCBvbiBk
cmFmdC1iaGgtbXBscy10cC1vYW0teTE3MzEtMDYuICBXZSBpbnZpdGUgeW91ciANCmNvbW1lbnRz
IG9uIHRoaXMgZG9jdW1lbnQNCi0tLS0NCg0KV2hpbGUgeW91IGFyZSB0ZWNobmljYWxseSBjb3Jy
ZWN0IHRoYXQgRy50cG9hbSBkb2VzIG5vdCBpdHNlbGYgY29udGFpbiBhIHJlZmVyZW5jZSB0byBk
cmFmdC1iaGgsIGhvdyBhcmUgd2UgdG8gaW50ZXJwcmV0IHRoZSBsaWFzb24gc3RhdGVtZW50IHdo
aWNoIGNsYWltcyBhIGNsZWFyIGxpbmVhZ2UgYmV0d2VlbiBkcmFmdC1iaGggYW5kIEcudHBvYW0/
DQoNCj4gQWxzbyB0aGUgc3RhdGVtZW50cyBhYm91dCB2YWxpZGl0eSBhbmQgY29weXJpZ2h0IGFy
ZSBpcnJlbGV2YW50Lg0KPiANCg0KQ2FuIHdlIGFzc3VtZSB0aGF0IHlvdSBhZ3JlZSB0aGV5IGFy
ZSBjb3JyZWN0LCByZWdhcmRsZXNzIG9mIHJlbGV2YW5jZT8NCg0KDQoNCmVyaWMNCg0KDQo+IFJl
Z2FyZHMsIEh1dWIuDQo+IA0KPiANCj4gPT09PT09PT09PT09PT0NCj4gPiBPbiAxMy8wMS8yMDEx
IDE3OjA5LCBEYXZpZCBTaW5pY3JvcGUgd3JvdGU6DQo+ID4+IEl0IHNlZW1zIHRoYXQgcmVmZXJl
bmNlIGFuZCB1c2Ugb2YgZHJhZnQtYmhoIGlzIGluIHZpb2xhdGlvbiBvZiB0aGUNCj4gPj4gSVRV
LVQgZXh0ZXJuYWwgY29vcGVyYXRpb24gYWdyZWVtZW50ICJSZWZlcmVuY2luZyBBLjUgUXVhbGlm
aWVkDQo+ID4+IE9yZ2FuaXphdGlvbnMiIHRleHQgZm91bmQgYXQNCj4gPj4gaHR0cDovL3d3dy5p
dHUuaW50L2VuL0lUVS1UL2V4dGNvb3AvUGFnZXMvc2RvLmFzcHggdW5kZXIgdGhlDQo+ID4+IFJl
ZmVyZW5jaW5nIElFVEYgRG9jdW1lbnRzIGxpbmsuDQo+ID4+IEluIHBhcnRpY3VsYXIgY2xhdXNl
IDEwIG9mIHRoaXMgZG9jdW1lbnQgc3RhdGVzOiAoU2VlIDJuZCBzZW50ZW5jZS4pDQo+ID4+DQo+
ID4+ICIxMCBPdGhlcjogSWYgYSBzdHVkeSBncm91cCBkZWNpZGVzIHRvIG1ha2UgdGhlIHJlZmVy
ZW5jZSB0byBhbiBJRVRGDQo+ID4+IFJGQywgdGhlIHJlZmVyZW5jZSBzaG91bGQgYWx3YXlzIGJl
IG1hZGUgYnkgUkZDIG51bWJlciAoYW5kIG5vdCBieQ0KPiA+PiBvdGhlciBkZXNpZ25hdGlvbnMg
c3VjaCBhcyBTVEQsIEJDUCwgZXRjLikuIFJlZmVyZW5jZXMgc2hvdWxkIG5vdCBiZQ0KPiA+PiBt
YWRlIHRvIGRvY3VtZW50cyByZWZlcnJlZCB0byBhcyAiSW50ZXJuZXQgRHJhZnRzIiBvciB0byBJ
RVRGIFJGQ3MNCj4gPj4gY2F0ZWdvcml6ZWQgYXMgSGlzdG9yaWMgb3IgRXhwZXJpbWVudGFsLiBO
b3JtYXRpdmUgcmVmZXJlbmNlcyBtdXN0DQo+ID4+IG9ubHkgYmUgbWFkZSB0byBJRVRGIFJGQ3Mg
dGhhdCBhcmUgU3RhbmRhcmRzIFRyYWNrIG9yIHRvDQo+ID4+IEluZm9ybWF0aW9uYWwgUkZDcyB0
aGF0IGhhdmUgSUVURiBjb25zZW5zdXMuIg0KPiA+Pg0KPiA+PiBJcyB0aGlzIG5vdCBjb3JyZWN0
PyBJZiBjb3JyZWN0LCBzaG91bGRuJ3QgdGhpcyBhbHNvIGJlIHBvaW50ZWQgb3V0DQo+ID4+IGlu
IHRoZSBsaWFpc29uPw0KPiA+PiBEYXZlDQo+ID4+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+ID4+IEZyb206IG1wbHMtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOm1wbHMtYm91
bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmDQo+ID4+IE9mIFN0ZXdhcnQgQnJ5YW50DQo+ID4+IFNl
bnQ6IFRodXJzZGF5LCBKYW51YXJ5IDEzLCAyMDExIDExOjI3IEFNDQo+ID4+IFRvOiBtcGxzQGll
dGYub3JnDQo+ID4+IFN1YmplY3Q6IFJlOiBbbXBsc10gW21wbHMtdHBdIERyYWZ0OiBSZXNwb25z
ZSB0byBVcGRhdGVkIGRyYWZ0DQo+ID4+IFJlY29tbWVuZGF0aW9uIEcudHBvYW0gW1JlZjA0My4w
Ml0NCj4gPj4NCj4gPj4gRXhhY3RseSBCZW4uDQo+ID4+DQo+ID4+IFRoZSBMaWFpc29uIGlzIGxp
c3Qgb2Ygc3RhdGVtZW50cyBvZiByZWxldmFudCBmYWN0cywgYW5kIG5vbmUgb2YgdGhlDQo+ID4+
IGNvbnRyYSBwb2ludHMgZGlzcHV0ZSB0aG9zZSBmYWN0cy4NCj4gPj4NCj4gPj4gU3Rld2FydA0K
PiA+Pg0KPiA+PiBPbiAxMy8wMS8yMDExIDE1OjQxLCBCZW4gTml2ZW4tSmVua2lucyB3cm90ZToN
Cj4gPj4+IExhcnJ5LA0KPiA+Pj4NCj4gPj4+IE9uIDEzIEphbiAyMDExLCBhdCAxNDo1NSwgTGFy
cnkgd3JvdGU6DQo+ID4+Pg0KPiA+Pj4+IEhpLA0KPiA+Pj4+DQo+ID4+Pj4gSSBkb24ndCB0aGlu
ayBpdCBpcyBwcm9wZXIgdG8gc2VuZCB0aGUgTFMgdG8gSVRVLVQgYmVjYXVzZSB0aGUgdGV4dA0K
PiA+Pj4+IGRvZXNuJ3QgcmVmbGVjdCB0aGUgcmVxdWlyZW1lbnQgZnJvbSBwcm92aWRlcnMuDQo+
ID4+Pj4gQXBwYXJlbnRseSwgZHJhZnQtYmhoIGJhc2VkIE9BTSBpcyB0aGUgbW9zdCBtYXR1cmUg
c29sdXRpb24NCj4gPj4+PiBjdXJyZW50bHkuIEl0IGhhcyBiZWVuIHByb3ZlZCBieSBtb3JlIHRo
YW4gMjAwLDAwMCBhcHBsaWNhdGlvbnMgYW5kDQo+ID4+Pj4gaXMgc3VwcG9ydGVkIGJ5IGEgbG90
IG9mIG9wZXJhdG9ycyBhbmQgdmVuZG9ycy4NCj4gPj4+Pg0KPiA+Pj4gVGhhdCBtYXkgb3IgbWF5
IG5vdCBiZSB0cnVlLCBidXQgZWl0aGVyIHdheSBpdCBpcyBpcnJlbGV2YW50IHRvIHRoZQ0KPiA+
Pj4gbGlhaXNvbi4NCj4gPj4+DQo+ID4+PiBJVFUgbGlhaXNlZCBHLnRwb2FtIHRvIElFVEYuIFRo
ZSBsaWFpc29uIHJlc3BvbnNlIFN0ZXdhcnQgaGFzDQo+ID4+PiBkcmFmdGVkIHBvaW50cyBvdXQg
dGhhdCBHLnRwb2FtIHVzZXMgdGVjaG5vbG9neSAoZHJhZnQtYmhoKSB0aGF0IGlzDQo+ID4+PiBu
b3QgZW5kb3JzZWQgYnkgSUVURiBjb25zZW5zdXMgYW5kIHBvaW50cyB0byBzb21lIHJpc2tzIG9m
IGRvaW5nIHNvLA0KPiA+Pj4gaW5jbHVkaW5nIGJyZWFjaCBvZiBhIHByaW9yIElUVS1JRVRGIGFn
cmVlbWVudCBvbiBob3cgdG8gcHJvZ3Jlc3MNCj4gPj4+IE1QTFMtVFAgZGV2ZWxvcG1lbnQuDQo+
ID4+Pg0KPiA+Pj4gRXZlcnl0aGluZyBpbiB0aGUgbGlhaXNvbiBpcyBmYWN0LiBXaGV0aGVyIGRy
YWZ0LWJoaCBpcw0KPiA+Pj4gZ29vZC9iYWQvdWdseSwgZGVwbG95ZWQsIHN1cHBvcnRlZCBieSBv
cGVyYXRvcnMsIGV0Yy4gaXMgaXJyZWxldmFudCwNCj4gPj4+IGl0IGlzIG5vdCBlbmRvcnNlZCBi
eSBJRVRGIGFzIGEgTVBMUy1UUCBPQU0gc29sdXRpb24gYW5kIGFsbCB0aGUNCj4gPj4+IGxpYWlz
b24gZG9lcyBpcyBwb2ludCBvdXQgdGhhdCBmYWN0Lg0KPiA+Pj4NCj4gPj4+IEZXSVcgdGhpcyBp
c24ndCB0aGUgZmlyc3QgdGltZSBhIGdyb3VwIG9mIG9wZXJhdG9ycyBoYXZlIGJyb3VnaHQgYQ0K
PiA+Pj4gcHJvcG9zYWwgdG8gSUVURiBvbmx5IHRvIGZpbmQgdGhhdCB0aGUgSUVURiBoYXMgZGVj
aWRlZCB0byBkbw0KPiA+Pj4gc29tZXRoaW5nIGVsc2UsIGFuZCBJJ20gc3VyZSBpdCB3b24ndCBi
ZSB0aGUgbGFzdC4NCj4gPj4+DQo+ID4+PiBCZW4NCj4gPj4+DQo+ID4+PiBQLlMuIGZvciBzb21l
IHJlYXNvbiBlbWFpbCBjaGFpbnMgcmVsYXRlZCB0byBkcmFmdC1iaGggcmVtaW5kIG1lIG9mDQo+
ID4+PiB0aGlzIERpbGJlcnQgY2FydG9vbiBodHRwOi8vd3d3LmRpbGJlcnQuY29tLzIwMTAtMTIt
MjIvDQo+ID4+Pg0KPiA+Pj4NCj4gPj4+DQo+ID4+Pj4gQmVzdCByZWdhcmRzLA0KPiA+Pj4+DQo+
ID4+Pj4gSGFuIExpDQo+ID4+Pj4NCj4gPj4+PiAqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQo+ID4+Pj4gKioNCj4gPj4+
PiAqKioqDQo+ID4+Pj4gSGFuIExpLCBQaC5EDQo+ID4+Pj4gQ2hpbmEgTW9iaWxlIFJlc2VhcmNo
IEluc3RpdHV0ZQ0KPiA+Pj4+IFVuaXQgMiwgMjggWHVhbnd1bWVueGkgQXZlLCBYdWFud3UgRGlz
dHJpY3QsIEJlaWppbmcgMTAwMDUzLCBDaGluYQ0KPiA+Pj4+IEZheDogKzg2IDEwIDYzNjAxMDg3
DQo+ID4+Pj4gTU9CSUxFOiAxMzUwMTA5MzM4NQ0KPiA+Pj4+ICoqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCj4gPj4+PiAq
Kg0KPiA+Pj4+ICoqKioNCj4gPj4+Pg0KPiA+Pj4+DQo+ID4+Pj4gLS0tIDEx5bm0MeaciDEz5pel
77yM5ZGo5ZubLA0KPiA+Pj4+IHJ1aXF1YW4uamluZ0B0aWVzLml0dS5pbnQ8cnVpcXVhbi5qaW5n
QHRpZXMuaXR1LmludD4NCj4gPj4+PiDlhpnpgZPvvJoNCj4gPj4+Pg0KPiA+Pj4+PiDlj5Hku7bk
uro6IHJ1aXF1YW4uamluZ0B0aWVzLml0dS5pbnQ8cnVpcXVhbi5qaW5nQHRpZXMuaXR1LmludD4N
Cj4gPj4+Pj4g5Li76aKYOiBSZTogW21wbHMtdHBdIFttcGxzXSBEcmFmdDogUmVzcG9uc2UgdG8g
VXBkYXRlZCBkcmFmdA0KPiA+Pj4+PiBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtIFtSZWYwNDMuMDJd
DQo+ID4+Pj4+IOaUtuS7tuS6ujogamluZ3JAdGllcy5pdHUuY2gNCj4gPj4+Pj4g5oqE6YCBOiBt
cGxzLXRwQGlldGYub3JnDQo+ID4+Pj4+IOaXpeacnzogMjAxMeW5tDHmnIgxM+aXpSzlkajlm5ss
5LiL5Y2INDowOQ0KPiA+Pj4+PiBSZXNlbmQgdG8gbXBscy10cCBsaXN0Lg0KPiA+Pj4+Pg0KPiA+
Pj4+PiBRdW90aW5nIGppbmdyQHRpZXMuaXR1LmNoOg0KPiA+Pj4+Pg0KPiA+Pj4+Pj4gSGkgU3Rl
d2FydCBCcnlhbnQsDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gSSBkb27igJl0IGFncmVlIHdpdGggdGhl
IGN1cnJlbnQgTFMgdGV4dC4NCj4gPj4+Pj4+DQo+ID4+Pj4+PiBDaGluYSBUZWxlY29tIHN1cHBv
cnQgdGhlIHN0YW5kYXJkaXphdGlvbiBvZiBZLjE3MzENCj4gPj4+Pj4gYmFzZWQgTVBMUy1UUCBP
QU0gdG9vbHMNCj4gPj4+Pj4+IGluDQo+ID4+Pj4+PiB0aGUgSVRVLVQgdG8gbWVldCB0aGUgdXJn
ZW50IGFuZCBpbmNyZWFzaW5nDQo+ID4+Pj4+IHJlcXVpcmVtZW50cyBmb3IgUFROIGRlcGxveW1l
bnQuDQo+ID4+Pj4+PiBJdOKAmXMgYSBtdWx0aS12ZW5kb3Igc3VwcG9ydGVkLCBpbnRlcm9wZXJh
YmlsaXR5DQo+ID4+Pj4+IGNlcnRpZmljYXRlZCBhbmQgZmVhc2libGUNCj4gPj4+Pj4+IHNvbHV0
aW9uLiBJdCBoYWQgYmVlbiBzcGVjaWZpZWQgaW4gYm90aCBDQ1NBDQo+ID4+Pj4+IChDaGluYSBD
b21tdW5pY2F0aW9ucyBTdGFuZGFyZHMNCj4gPj4+Pj4+IEFzc29jaWF0aW9uKSBhbmQgQ2hpbmEg
VGVsZWNvbeKAmXMgUFROIHN0YW5kYXJkIGFzIHRoZQ0KPiA+Pj4+PiBvbmx5IHN0YW5kYXJkIE9B
TQ0KPiA+Pj4+Pj4gbWVjaGFuaXNtLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+ID4+Pj4+Pg0KPiA+
Pj4+Pj4gQmVzdCBSZWdhcmRzDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gSmluZyBSdWlxdWFuDQo+ID4+
Pj4+Pg0KPiA+Pj4+Pj4gQ2hpbmHjgIBUZWxlY29tIEJlaWppbmcNCj4gPj4+Pj4gUmVzZWFyY2jj
gIBJbnN0aXR1dGUNCj4gPj4+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4+Pj4+IC0tDQo+ID4+Pj4+IC0tLS0t
LS0tLS0NCj4gPj4+Pj4gLS0NCj4gPj4+Pj4+IEZyb206IG1wbHMtYm91bmNlc0BpZXRmLm9yZw0K
PiA+Pj4+PiBbbWFpbHRvOm1wbHMtYm91bmNlc0BpZXRmLm9yZ10NCj4gPj4+Pj4gT24gQmVoYWxm
IE9mDQo+ID4+Pj4+PiBTdGV3YXJ0DQo+ID4+Pj4+PiBCcnlhbnQNCj4gPj4+Pj4+IFNlbnQ6IE1v
bmRheSwgSmFudWFyeSAxMCwgMjAxMSA2OjU3IFBNDQo+ID4+Pj4+PiBUbzogbXBsc0BpZXRmLm9y
Zw0KPiA+Pj4+Pj4gU3ViamVjdDogW21wbHNdIERyYWZ0OiBSZXNwb25zZSB0byBVcGRhdGVkIGRy
YWZ0DQo+ID4+Pj4+IFJlY29tbWVuZGF0aW9uIEcudHBvYW0NCj4gPj4+Pj4+IFtSZWYwNDMuMDJd
DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IEkgcHJvcG9zZSB0byBzZW5kIHRoZSBmb2xs
b3dpbmcgTGlhaXNvbiBSZXNwb25zZSB0bw0KPiA+Pj4+PiB0aGUgSVRVLVQgb24gRnJpZGF5DQo+
ID4+Pj4+PiAxNHRoIEphbnVhcnkgYW5kIGFtIHBvc3RpbmcgaXQgdG8gdGhlIE1QTFMgV0cgbGlz
dCBmb3INCj4gPj4+Pj4gcmV2aWV3Lg0KPiA+Pj4+Pj4gPT09PT09PQ0KPiA+Pj4+Pj4NCj4gPj4+
Pj4+IFJlc3BvbnNlIHRvIFVwZGF0ZWQgZHJhZnQgUmVjb21tZW5kYXRpb24gRy50cG9hbSBbUmVm
DQo+ID4+Pj4+IDA0My4wMl0NCj4gPj4+Pj4+IEZyb206IElFVEYgTGlhaXNvbiB0byBJVFUtVCBv
biBNUExTIHN0YnJ5YW50QGNpc2NvLmNvbQ0KPiA+Pj4+Pj4gVG86IHRzYnNnMTVAaXR1LmludCwN
Cj4gPj4+Pj4gZ3JlZy5qb25lc0BpdHUuaW50LA0KPiA+Pj4+PiBoaXJvc2hpLm90YUBpdHUuaW50
LA0KPiA+Pj4+PiBJQUJAaWV0Zi5vcmcNCj4gPj4+Pj4+IENDOiBHcmVnIEpvbmVzLCBzd2FsbG93
QGNpc2NvLmNvbSwNCj4gPj4+Pj4gbG9hQHBpLm51LCBwYWZAY2lzY28uY29tDQo+ID4+Pj4+PiBz
dGJyeWFudEBjaXNjby5jb20sDQo+ID4+Pj4+IGFkcmlhbi5mYXJyZWxAaHVhd2VpLmNvbSwNCj4g
Pj4+Pj4gbXBsc0BpZXRmLm9yZw0KPiA+Pj4+Pj4geW9pY2hpLm1hZWRhQHR0Yy5vci5qcCwNCj4g
Pj4+Pj4gc3RldmUudHJvd2JyaWRnZUBhbGNhdGVsLWx1Y2VudC5jb20NCj4gPj4+Pj4NCj4gPj4+
Pj4+IGdoYW5pLmFiYmFzQGVyaWNzc29uLmNvbSwNCj4gPj4+Pj4gaGhlbHZvb3J0QGh1YXdlaS5j
b20NCj4gPj4+Pj4NCj4gPj4+Pj4+IG1hbGNvbG0uYmV0dHNAenRlLmNvbS5jbiwNCj4gPj4+Pj4g
a2FtLmxhbUBhbGNhdGVsLWx1Y2VudC5jb20NCj4gPj4+Pj4NCj4gPj4+Pj4+IEZvciBBY3Rpb24N
Cj4gPj4+Pj4+DQo+ID4+Pj4+PiBUaGUgTVBMUyBXb3JraW5nIEdyb3VwIG5vdGVzIHRoYXQgdGhp
cyBkb2N1bWVudA0KPiA+Pj4+PiBjb250YWlucyB0ZXh0IGRlc2NyaWJpbmcNCj4gPj4+Pj4+IE1Q
TFMtVFAgT0FNIHByb3RvY29scyBub3QgZGVzaWduZWQgYW5kIHN0YW5kYXJkaXplZA0KPiA+Pj4+
PiB1c2luZyB0aGUgSUVURg0KPiA+Pj4+Pj4gU3RhbmRhcmRzIHByb2Nlc3MuIFNwZWNpZmljYWxs
eSBpdCB1c2VzIG1hdGVyaWFsIGZyb20NCj4gPj4+Pj4+IGRyYWZ0LWJoaC1tcGxzLXRwLW9hbS15
MTczMS0wNi4NCj4gPj4+Pj4+DQo+ID4+Pj4+PiBXZSB3aXNoIHRvIGRyYXcgeW91ciBhdHRlbnRp
b24gdG8gdGhlIHN0YXR1cyBzZWN0aW9uDQo+ID4+Pj4+IG9mDQo+ID4+Pj4+PiBkcmFmdC1iaGgt
bXBscy10cC1vYW0teTE3MzEtMDYgd2hpY2ggc3RhdGVzOg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+ICJJ
bnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYQ0KPiA+Pj4+PiBt
YXhpbXVtIG9mIHNpeCBtb250aHMNCj4gPj4+Pj4+IGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFj
ZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlcg0KPiA+Pj4+PiBkb2N1bWVudHMgYXQgYW55DQo+ID4+
Pj4+PiB0aW1lLiBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMN
Cj4gPj4+Pj4gcmVmZXJlbmNlIG1hdGVyaWFsDQo+ID4+Pj4+PiBvciB0byBjaXRlIHRoZW0gb3Ro
ZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcyIuDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gUGxlYXNl
IGFsc28gbm90ZSB0aGF0IHNpbmNlIHRoZSBkcmFmdCBmaWxlbmFtZSBzdGFydHMNCj4gPj4+Pj4g
d2l0aCB0aGUgcHJlZml4DQo+ID4+Pj4+PiBzdHJpbmcgImRyYWZ0LWJoaCIgdGhpcyBjbGVhcmx5
IGlkZW50aWZpZXMgaXQgdG8gdGhlDQo+ID4+Pj4+IHJlYWRlciBhcyBhDQo+ID4+Pj4+PiBkb2N1
bWVudCBleHByZXNzaW5nIHRoZSBwZXJzb25hbCB0ZWNobmljYWwgdmlld3Mgb2YNCj4gPj4+Pj4g
dGhlIGF1dGhvcnMgYW5kDQo+ID4+Pj4+PiBoZW5jZSBoZW5jZSBhcyBhIGRvY3VtZW50IHRoYXQg
dGhhdCBkb2VzIG5vdCBoYXZlIGFueQ0KPiA+Pj4+PiBhY2tub3dsZWRnZWQgbGV2ZWwNCj4gPj4+
Pj4+IG9mIElFVEYgY29uc2Vuc3VzLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IFNpbmNlIHRoZSB0ZXh0
IG9mIGRyYWZ0IFJlY29tbWVuZGF0aW9uIGZvciBHLnRwb2FtIGlzDQo+ID4+Pj4+IGJhc2VkIG9u
IGFuDQo+ID4+Pj4+PiBNUExTLVRQIE9BTSBwcm90b2NvbCBub3QgZGVzaWduZWQgd2l0aGluIHRo
ZSBJRVRGDQo+ID4+Pj4+IFN0YW5kYXJkcyBQcm9jZXNzIHRoaXMNCj4gPj4+Pj4+IGlzIGEgYnJl
YWNoIG9mIHRoZSBTRzE1IGFncmVlbWVudCB3aXRoIHRoZSBJRVRGIGFzDQo+ID4+Pj4+IHB1Ymxp
c2hlZCBpbiBSZXBvcnQNCj4gPj4+Pj4+IG9mIHRoZSBmaXJzdCBtZWV0aW5nIG9mIFdvcmtpbmcg
UGFydHkgMy8xNSBUcmFuc3BvcnQNCj4gPj4+Pj4gbmV0d29yayBzdHJ1Y3R1cmVzDQo+ID4+Pj4+
PiAoMjAwOS0yMDEyKSAoR2VuZXZhLCAxIOKAkyAxMiBEZWNlbWJlciAyMDA4KSB3aGljaCBjYW4N
Cj4gPj4+Pj4gYmUgZm91bmQgYXQNCj4gPj4+Pj4+IGh0dHA6Ly93d3cuaXR1LmludC9tZC9UMDkt
U0cxNS1SLTAwMDQvZW4NCj4gPj4+Pj4+IFBsZWFzZSBjb25maXJtIHRoYXQgdGhlIElUVS1UIGlu
dGVuZHMgdG8gY29udGludWUgd2l0aA0KPiA+Pj4+PiB0aGUgam9pbnQgd29yayBvbg0KPiA+Pj4+
Pj4gTVBMUy1UUCBhbmQgdGhhdCB0aGUgSVRVLVQgd2lsbCBhbGlnbiB0aGlzDQo+ID4+Pj4+IHJl
Y29tbWVuZGF0aW9uIHdpdGggdGhlIElFVEYNCj4gPj4+Pj4+IE1QTFMtVFAgT0FNIGRlc2lnbiBi
ZWZvcmUgYWR2YW5jaW5nIHRoaXMgZG9jdW1lbnQNCj4gPj4+Pj4gdGhyb3VnaCB0aGUgSVRVLVQN
Cj4gPj4+Pj4+IHB1YmxpY2F0aW9uIHByb2Nlc3MuDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gVGhlIE1Q
TFMgV29ya2luZyBHcm91cCB3b3VsZCBhbHNvIGxpa2UgdG8gZHJhdyB0aGUNCj4gPj4+Pj4gYXR0
ZW50aW9uIG9mIElUVS1UDQo+ID4+Pj4+PiBTRzE1IHRvIHRoZSBJRVRGIGNvcHlyaWdodCBydWxl
cy4gUGxlYXNlIHNlZQ0KPiA+Pj4+Pj4gaHR0cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1p
bmZvL2FyY2hpdmUvSUVURi1UcnVzdC1MaWNlbnNlLVANCj4gPj4+Pj4+IG9sDQo+ID4+Pj4+PiBp
Y3ktDQo+ID4+Pj4+PiAyMDA5MTIyOC5odG0NCj4gPj4+Pj4+IGZvciBmdXJ0aGVyIGRldGFpbHMu
DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gU2luY2UgdGhpcyBkcmFmdCBSZWNvbW1lbmRhdGlvbiBjb250
YWlucyB0ZXh0IGluIHdoaWNoDQo+ID4+Pj4+IHRoZSBJVFUtVCBTRzE1DQo+ID4+Pj4+PiBoYXMg
cHJvcG9zZWQgbWFraW5nIGNoYW5nZXMgdG8gSUVURiBwcm90b2NvbHMgd2l0aG91dA0KPiA+Pj4+
PiB0aGUgYXBwcm92YWwgb2YNCj4gPj4+Pj4+IHRoZSBJRVRGLCB0aGUgTVBMUyBXb3JraW5nIEdy
b3VwIGhhdmUgcmVmZXJyZWQgdGhpcw0KPiA+Pj4+PiBsaWFpc29uIHRvIHRoZSBJQUINCj4gPj4+
Pj4+IGZvciB0aGVpciBjb25zaWRlcmF0aW9uLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+ID4+Pj4+
Pg0KPiA+Pj4+Pj4gPT09PT09PT09DQo+ID4+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPiA+Pj4+Pj4gbXBscyBtYWlsaW5nIGxpc3QNCj4gPj4+
Pj4+IG1wbHNAaWV0Zi5vcmcNCj4gPj4+Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vbXBscw0KPiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pg0KPiA+
Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+
Pj4+PiBtcGxzLXRwIG1haWxpbmcgbGlzdA0KPiA+Pj4+PiBtcGxzLXRwQGlldGYub3JnDQo+ID4+
Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscy10cA0KPiA+Pj4+
Pg0KPiA+Pj4+DQo+ID4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4gPj4+PiBtcGxzLXRwIG1haWxpbmcgbGlzdA0KPiA+Pj4+IG1wbHMtdHBAaWV0
Zi5vcmcNCj4gPj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMt
dHANCj4gPj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+ID4+PiBtcGxzIG1haWxpbmcgbGlzdA0KPiA+Pj4gbXBsc0BpZXRmLm9yZw0KPiA+Pj4gaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo+ID4+DQo+ID4+IC0tDQo+
ID4+IEZvciBjb3Jwb3JhdGUgbGVnYWwgaW5mb3JtYXRpb24gZ28gdG86DQo+ID4+DQo+ID4+IGh0
dHA6Ly93d3cuY2lzY28uY29tL3dlYi9hYm91dC9kb2luZ19idXNpbmVzcy9sZWdhbC9jcmkvaW5k
ZXguaHRtbA0KPiA+Pg0KPiA+Pg0KPiA+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPiA+PiBtcGxzIG1haWxpbmcgbGlzdA0KPiA+PiBtcGxzQGlldGYu
b3JnDQo+ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0KPiA+
DQo+ID4NCj4gDQo+IA0KPiAtLQ0KPiAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKg0KPiAgICAgICAgICAgICAgICAgICAgICAg
ICAgIOaIkeeIseWklueCueS4gOS4g+S4ieS4gA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPiBtcGxzLXRwIG1haWxpbmcgbGlzdA0KPiBtcGxzLXRw
QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscy10
cA0K

From jdrake@juniper.net  Thu Jan 13 14:49:18 2011
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A073928C105; Thu, 13 Jan 2011 14:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.812
X-Spam-Level: 
X-Spam-Status: No, score=-5.812 tagged_above=-999 required=5 tests=[AWL=0.187,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ZehPndIqAQb; Thu, 13 Jan 2011 14:49:17 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by core3.amsl.com (Postfix) with ESMTP id E83EA28B23E; Thu, 13 Jan 2011 14:49:16 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTS+B+/Tj0SBUSZqTgaVApNjXo82N9RUE@postini.com; Thu, 13 Jan 2011 14:51:41 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Thu, 13 Jan 2011 14:47:13 -0800
From: John E Drake <jdrake@juniper.net>
To: Huub van Helvoort <huubatwork@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>,  "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Thu, 13 Jan 2011 14:49:09 -0800
Thread-Topic: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam [Ref043.02]
Thread-Index: AcuzcZ91cyVLfJeKTGmQ0aLyJTWuzwAAV5zA
Message-ID: <5E893DB832F57341992548CDBB33316398C6F3BD48@EMBX01-HQ.jnpr.net>
References: <526321.56478.qm@web15605.mail.cnb.yahoo.com> <EC7945C9-3C51-42A1-8CA8-692A94B28F2C@niven-jenkins.co.uk> <4D2F27F1.1070209@cisco.com> <6873FACCBB5DDD4D88AABD78A8E483A468CE4D0311@EUSAACMS0703.eamcs.ericsson.se> <4D2F47F9.8040701@cisco.com> <4D2F7D8E.9040505@gmail.com>
In-Reply-To: <4D2F7D8E.9040505@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft	Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 22:49:18 -0000

VGhpcyBsaWFzb24sIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvbGlhaXNvbi85ODMvLCBp
bmNsdWRlcyB0aGUgZm9sbG93aW5nIHN0YXRlbWVudDoNCg0KIkF0IHRoZSBCZXJsaW4gaW50ZXJp
bSBtZWV0aW5nIG9uIE1QTFMtVFAgZnVydGhlciB3b3JrIHdhcyB1bmRlcnRha2VuIG9uIHRoZSBk
ZXZlbG9wbWVudCBvZiB0aGUgT0FNIFJlY29tbWVuZGF0aW9uIEcudHBvYW0uIFRoaXMgdmVyc2lv
biB3YXMgZGV2ZWxvcGVkIHVzaW5nIGFsbCBvZiB0aGUgcmVsZXZhbnQgaW5wdXQgZG9jdW1lbnRz
IHRvIHRoZSBtZWV0aW5nIGFuZCBpcyBiYXNlZCBvbiBkcmFmdC1iaGgtbXBscy10cC1vYW0teTE3
MzEtMDYuIFdlIGludml0ZSB5b3VyIGNvbW1lbnRzIG9uIHRoaXMgZG9jdW1lbnQuIg0KDQpTbyB5
b3VyIHN0YXRlbWVudCBtYXkgYmUgZmFjdHVhbGx5IGNvcnJlY3QgYnV0IG1pc2xlYWRpbmcuIA0K
DQpTZW50IGZyb20gbXkgaVBob25lDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
PiBGcm9tOiBtcGxzLXRwLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzptcGxzLXRwLWJvdW5jZXNA
aWV0Zi5vcmddIE9uDQo+IEJlaGFsZiBPZiBIdXViIHZhbiBIZWx2b29ydA0KPiBTZW50OiBUaHVy
c2RheSwgSmFudWFyeSAxMywgMjAxMSAyOjMzIFBNDQo+IFRvOiBtcGxzQGlldGYub3JnOyBtcGxz
LXRwQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbbXBscy10cF0gW21wbHNdIERyYWZ0OiBSZXNw
b25zZSB0byBVcGRhdGVkIGRyYWZ0DQo+IFJlY29tbWVuZGF0aW9uIEcudHBvYW0gW1JlZjA0My4w
Ml0NCj4gDQo+IEhlbGxvIFN0ZXdhcnQsDQo+IA0KPiBZb3UgYXNrZWQ6DQo+IA0KPiA+IERvZXMg
YW55b25lIGRpc2FncmVlIHdpdGggdGhlIHN0YXRlbWVudCB0aGF0IERhdmlkIG1ha2VzPw0KPiAN
Cj4gSSBkaXNhZ3JlZSB3aXRoIHRoaXMgc3RhdGVtZW50IGluIHJlbGF0aW9uIHRvIHRoaXMgbGlh
aXNvbi4NCj4gDQo+IFRoZSBkcmFmdCByZWNvbW1lbmRhdGlvbiBHLnRwb2FtIHRoYXQgd2FzIHNl
bnQgZm9yIHJldmlldyBkb2VzDQo+IG5vdCBjb250YWluIGEgcmVmZXJlbmNlIHRvIGRyYWZ0LWJo
aCBhdCBhbGwuDQo+IA0KPiBBbHNvIHRoZSBzdGF0ZW1lbnRzIGFib3V0IHZhbGlkaXR5IGFuZCBj
b3B5cmlnaHQgYXJlIGlycmVsZXZhbnQuDQo+IA0KPiBSZWdhcmRzLCBIdXViLg0KPiANCj4gDQo+
ID09PT09PT09PT09PT09DQo+ID4gT24gMTMvMDEvMjAxMSAxNzowOSwgRGF2aWQgU2luaWNyb3Bl
IHdyb3RlOg0KPiA+PiBJdCBzZWVtcyB0aGF0IHJlZmVyZW5jZSBhbmQgdXNlIG9mIGRyYWZ0LWJo
aCBpcyBpbiB2aW9sYXRpb24gb2YgdGhlDQo+ID4+IElUVS1UIGV4dGVybmFsIGNvb3BlcmF0aW9u
IGFncmVlbWVudCAiUmVmZXJlbmNpbmcgQS41IFF1YWxpZmllZA0KPiA+PiBPcmdhbml6YXRpb25z
IiB0ZXh0IGZvdW5kIGF0DQo+ID4+IGh0dHA6Ly93d3cuaXR1LmludC9lbi9JVFUtVC9leHRjb29w
L1BhZ2VzL3Nkby5hc3B4IHVuZGVyIHRoZQ0KPiA+PiBSZWZlcmVuY2luZyBJRVRGIERvY3VtZW50
cyBsaW5rLg0KPiA+PiBJbiBwYXJ0aWN1bGFyIGNsYXVzZSAxMCBvZiB0aGlzIGRvY3VtZW50IHN0
YXRlczogKFNlZSAybmQgc2VudGVuY2UuKQ0KPiA+Pg0KPiA+PiAiMTAgT3RoZXI6IElmIGEgc3R1
ZHkgZ3JvdXAgZGVjaWRlcyB0byBtYWtlIHRoZSByZWZlcmVuY2UgdG8gYW4gSUVURg0KPiA+PiBS
RkMsIHRoZSByZWZlcmVuY2Ugc2hvdWxkIGFsd2F5cyBiZSBtYWRlIGJ5IFJGQyBudW1iZXIgKGFu
ZCBub3QgYnkNCj4gPj4gb3RoZXIgZGVzaWduYXRpb25zIHN1Y2ggYXMgU1RELCBCQ1AsIGV0Yy4p
LiBSZWZlcmVuY2VzIHNob3VsZCBub3QgYmUNCj4gPj4gbWFkZSB0byBkb2N1bWVudHMgcmVmZXJy
ZWQgdG8gYXMgIkludGVybmV0IERyYWZ0cyIgb3IgdG8gSUVURiBSRkNzDQo+ID4+IGNhdGVnb3Jp
emVkIGFzIEhpc3RvcmljIG9yIEV4cGVyaW1lbnRhbC4gTm9ybWF0aXZlIHJlZmVyZW5jZXMgbXVz
dA0KPiA+PiBvbmx5IGJlIG1hZGUgdG8gSUVURiBSRkNzIHRoYXQgYXJlIFN0YW5kYXJkcyBUcmFj
ayBvciB0bw0KPiBJbmZvcm1hdGlvbmFsDQo+ID4+IFJGQ3MgdGhhdCBoYXZlIElFVEYgY29uc2Vu
c3VzLiINCj4gPj4NCj4gPj4gSXMgdGhpcyBub3QgY29ycmVjdD8gSWYgY29ycmVjdCwgc2hvdWxk
bid0IHRoaXMgYWxzbyBiZSBwb2ludGVkIG91dA0KPiBpbg0KPiA+PiB0aGUgbGlhaXNvbj8NCj4g
Pj4gRGF2ZQ0KPiA+Pg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9t
OiBtcGxzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzptcGxzLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZg0KPiA+PiBPZiBTdGV3YXJ0IEJyeWFudA0KPiA+PiBTZW50OiBUaHVyc2RheSwgSmFu
dWFyeSAxMywgMjAxMSAxMToyNyBBTQ0KPiA+PiBUbzogbXBsc0BpZXRmLm9yZw0KPiA+PiBTdWJq
ZWN0OiBSZTogW21wbHNdIFttcGxzLXRwXSBEcmFmdDogUmVzcG9uc2UgdG8gVXBkYXRlZCBkcmFm
dA0KPiA+PiBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtIFtSZWYwNDMuMDJdDQo+ID4+DQo+ID4+IEV4
YWN0bHkgQmVuLg0KPiA+Pg0KPiA+PiBUaGUgTGlhaXNvbiBpcyBsaXN0IG9mIHN0YXRlbWVudHMg
b2YgcmVsZXZhbnQgZmFjdHMsIGFuZCBub25lIG9mIHRoZQ0KPiA+PiBjb250cmEgcG9pbnRzIGRp
c3B1dGUgdGhvc2UgZmFjdHMuDQo+ID4+DQo+ID4+IFN0ZXdhcnQNCj4gPj4NCj4gPj4gT24gMTMv
MDEvMjAxMSAxNTo0MSwgQmVuIE5pdmVuLUplbmtpbnMgd3JvdGU6DQo+ID4+PiBMYXJyeSwNCj4g
Pj4+DQo+ID4+PiBPbiAxMyBKYW4gMjAxMSwgYXQgMTQ6NTUsIExhcnJ5IHdyb3RlOg0KPiA+Pj4N
Cj4gPj4+PiBIaSwNCj4gPj4+Pg0KPiA+Pj4+IEkgZG9uJ3QgdGhpbmsgaXQgaXMgcHJvcGVyIHRv
IHNlbmQgdGhlIExTIHRvIElUVS1UIGJlY2F1c2UgdGhlDQo+IHRleHQNCj4gPj4+PiBkb2Vzbid0
IHJlZmxlY3QgdGhlIHJlcXVpcmVtZW50IGZyb20gcHJvdmlkZXJzLg0KPiA+Pj4+IEFwcGFyZW50
bHksIGRyYWZ0LWJoaCBiYXNlZCBPQU0gaXMgdGhlIG1vc3QgbWF0dXJlIHNvbHV0aW9uDQo+ID4+
Pj4gY3VycmVudGx5LiBJdCBoYXMgYmVlbiBwcm92ZWQgYnkgbW9yZSB0aGFuIDIwMCwwMDAgYXBw
bGljYXRpb25zDQo+IGFuZA0KPiA+Pj4+IGlzIHN1cHBvcnRlZCBieSBhIGxvdCBvZiBvcGVyYXRv
cnMgYW5kIHZlbmRvcnMuDQo+ID4+Pj4NCj4gPj4+IFRoYXQgbWF5IG9yIG1heSBub3QgYmUgdHJ1
ZSwgYnV0IGVpdGhlciB3YXkgaXQgaXMgaXJyZWxldmFudCB0byB0aGUNCj4gPj4+IGxpYWlzb24u
DQo+ID4+Pg0KPiA+Pj4gSVRVIGxpYWlzZWQgRy50cG9hbSB0byBJRVRGLiBUaGUgbGlhaXNvbiBy
ZXNwb25zZSBTdGV3YXJ0IGhhcw0KPiBkcmFmdGVkDQo+ID4+PiBwb2ludHMgb3V0IHRoYXQgRy50
cG9hbSB1c2VzIHRlY2hub2xvZ3kgKGRyYWZ0LWJoaCkgdGhhdCBpcyBub3QNCj4gPj4+IGVuZG9y
c2VkIGJ5IElFVEYgY29uc2Vuc3VzIGFuZCBwb2ludHMgdG8gc29tZSByaXNrcyBvZiBkb2luZyBz
bywNCj4gPj4+IGluY2x1ZGluZyBicmVhY2ggb2YgYSBwcmlvciBJVFUtSUVURiBhZ3JlZW1lbnQg
b24gaG93IHRvIHByb2dyZXNzDQo+ID4+PiBNUExTLVRQIGRldmVsb3BtZW50Lg0KPiA+Pj4NCj4g
Pj4+IEV2ZXJ5dGhpbmcgaW4gdGhlIGxpYWlzb24gaXMgZmFjdC4gV2hldGhlciBkcmFmdC1iaGgg
aXMNCj4gPj4+IGdvb2QvYmFkL3VnbHksIGRlcGxveWVkLCBzdXBwb3J0ZWQgYnkgb3BlcmF0b3Jz
LCBldGMuIGlzDQo+IGlycmVsZXZhbnQsDQo+ID4+PiBpdCBpcyBub3QgZW5kb3JzZWQgYnkgSUVU
RiBhcyBhIE1QTFMtVFAgT0FNIHNvbHV0aW9uIGFuZCBhbGwgdGhlDQo+ID4+PiBsaWFpc29uIGRv
ZXMgaXMgcG9pbnQgb3V0IHRoYXQgZmFjdC4NCj4gPj4+DQo+ID4+PiBGV0lXIHRoaXMgaXNuJ3Qg
dGhlIGZpcnN0IHRpbWUgYSBncm91cCBvZiBvcGVyYXRvcnMgaGF2ZSBicm91Z2h0IGENCj4gPj4+
IHByb3Bvc2FsIHRvIElFVEYgb25seSB0byBmaW5kIHRoYXQgdGhlIElFVEYgaGFzIGRlY2lkZWQg
dG8gZG8NCj4gPj4+IHNvbWV0aGluZyBlbHNlLCBhbmQgSSdtIHN1cmUgaXQgd29uJ3QgYmUgdGhl
IGxhc3QuDQo+ID4+Pg0KPiA+Pj4gQmVuDQo+ID4+Pg0KPiA+Pj4gUC5TLiBmb3Igc29tZSByZWFz
b24gZW1haWwgY2hhaW5zIHJlbGF0ZWQgdG8gZHJhZnQtYmhoIHJlbWluZCBtZSBvZg0KPiA+Pj4g
dGhpcyBEaWxiZXJ0IGNhcnRvb24gaHR0cDovL3d3dy5kaWxiZXJ0LmNvbS8yMDEwLTEyLTIyLw0K
PiA+Pj4NCj4gPj4+DQo+ID4+Pg0KPiA+Pj4+IEJlc3QgcmVnYXJkcywNCj4gPj4+Pg0KPiA+Pj4+
IEhhbiBMaQ0KPiA+Pj4+DQo+ID4+Pj4NCj4gKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQo+ID4+Pj4gKioqKg0KPiA+
Pj4+IEhhbiBMaSwgUGguRA0KPiA+Pj4+IENoaW5hIE1vYmlsZSBSZXNlYXJjaCBJbnN0aXR1dGUN
Cj4gPj4+PiBVbml0IDIsIDI4IFh1YW53dW1lbnhpIEF2ZSwgWHVhbnd1IERpc3RyaWN0LCBCZWlq
aW5nIDEwMDA1MywgQ2hpbmENCj4gPj4+PiBGYXg6ICs4NiAxMCA2MzYwMTA4Nw0KPiA+Pj4+IE1P
QklMRTogMTM1MDEwOTMzODUNCj4gPj4+Pg0KPiAqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCj4gPj4+PiAqKioqDQo+
ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4+IC0tLSAxMeW5tDHmnIgxM+aXpe+8jOWRqOWbmywNCj4gPj4+
PiBydWlxdWFuLmppbmdAdGllcy5pdHUuaW50PHJ1aXF1YW4uamluZ0B0aWVzLml0dS5pbnQ+DQo+
ID4+Pj4g5YaZ6YGT77yaDQo+ID4+Pj4NCj4gPj4+Pj4g5Y+R5Lu25Lq6OiBydWlxdWFuLmppbmdA
dGllcy5pdHUuaW50PHJ1aXF1YW4uamluZ0B0aWVzLml0dS5pbnQ+DQo+ID4+Pj4+IOS4u+mimDog
UmU6IFttcGxzLXRwXSBbbXBsc10gRHJhZnQ6IFJlc3BvbnNlIHRvIFVwZGF0ZWQgZHJhZnQNCj4g
Pj4+Pj4gUmVjb21tZW5kYXRpb24gRy50cG9hbSBbUmVmMDQzLjAyXQ0KPiA+Pj4+PiDmlLbku7bk
uro6IGppbmdyQHRpZXMuaXR1LmNoDQo+ID4+Pj4+IOaKhOmAgTogbXBscy10cEBpZXRmLm9yZw0K
PiA+Pj4+PiDml6XmnJ86IDIwMTHlubQx5pyIMTPml6Us5ZGo5ZubLOS4i+WNiDQ6MDkNCj4gPj4+
Pj4gUmVzZW5kIHRvIG1wbHMtdHAgbGlzdC4NCj4gPj4+Pj4NCj4gPj4+Pj4gUXVvdGluZyBqaW5n
ckB0aWVzLml0dS5jaDoNCj4gPj4+Pj4NCj4gPj4+Pj4+IEhpIFN0ZXdhcnQgQnJ5YW50LA0KPiA+
Pj4+Pj4NCj4gPj4+Pj4+IEkgZG9u4oCZdCBhZ3JlZSB3aXRoIHRoZSBjdXJyZW50IExTIHRleHQu
DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gQ2hpbmEgVGVsZWNvbSBzdXBwb3J0IHRoZSBzdGFuZGFyZGl6
YXRpb24gb2YgWS4xNzMxDQo+ID4+Pj4+IGJhc2VkIE1QTFMtVFAgT0FNIHRvb2xzDQo+ID4+Pj4+
PiBpbg0KPiA+Pj4+Pj4gdGhlIElUVS1UIHRvIG1lZXQgdGhlIHVyZ2VudCBhbmQgaW5jcmVhc2lu
Zw0KPiA+Pj4+PiByZXF1aXJlbWVudHMgZm9yIFBUTiBkZXBsb3ltZW50Lg0KPiA+Pj4+Pj4gSXTi
gJlzIGEgbXVsdGktdmVuZG9yIHN1cHBvcnRlZCwgaW50ZXJvcGVyYWJpbGl0eQ0KPiA+Pj4+PiBj
ZXJ0aWZpY2F0ZWQgYW5kIGZlYXNpYmxlDQo+ID4+Pj4+PiBzb2x1dGlvbi4gSXQgaGFkIGJlZW4g
c3BlY2lmaWVkIGluIGJvdGggQ0NTQQ0KPiA+Pj4+PiAoQ2hpbmEgQ29tbXVuaWNhdGlvbnMgU3Rh
bmRhcmRzDQo+ID4+Pj4+PiBBc3NvY2lhdGlvbikgYW5kIENoaW5hIFRlbGVjb23igJlzIFBUTiBz
dGFuZGFyZCBhcyB0aGUNCj4gPj4+Pj4gb25seSBzdGFuZGFyZCBPQU0NCj4gPj4+Pj4+IG1lY2hh
bmlzbS4NCj4gPj4+Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IEJlc3QgUmVnYXJk
cw0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IEppbmcgUnVpcXVhbg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IENo
aW5h44CAVGVsZWNvbSBCZWlqaW5nDQo+ID4+Pj4+IFJlc2VhcmNo44CASW5zdGl0dXRlDQo+ID4+
Pj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQo+IC0tLQ0KPiA+Pj4+PiAtLS0tLS0tLS0tDQo+ID4+Pj4+IC0tDQo+ID4+
Pj4+PiBGcm9tOiBtcGxzLWJvdW5jZXNAaWV0Zi5vcmcNCj4gPj4+Pj4gW21haWx0bzptcGxzLWJv
dW5jZXNAaWV0Zi5vcmddDQo+ID4+Pj4+IE9uIEJlaGFsZiBPZg0KPiA+Pj4+Pj4gU3Rld2FydA0K
PiA+Pj4+Pj4gQnJ5YW50DQo+ID4+Pj4+PiBTZW50OiBNb25kYXksIEphbnVhcnkgMTAsIDIwMTEg
Njo1NyBQTQ0KPiA+Pj4+Pj4gVG86IG1wbHNAaWV0Zi5vcmcNCj4gPj4+Pj4+IFN1YmplY3Q6IFtt
cGxzXSBEcmFmdDogUmVzcG9uc2UgdG8gVXBkYXRlZCBkcmFmdA0KPiA+Pj4+PiBSZWNvbW1lbmRh
dGlvbiBHLnRwb2FtDQo+ID4+Pj4+PiBbUmVmMDQzLjAyXQ0KPiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+
ID4+Pj4+PiBJIHByb3Bvc2UgdG8gc2VuZCB0aGUgZm9sbG93aW5nIExpYWlzb24gUmVzcG9uc2Ug
dG8NCj4gPj4+Pj4gdGhlIElUVS1UIG9uIEZyaWRheQ0KPiA+Pj4+Pj4gMTR0aCBKYW51YXJ5IGFu
ZCBhbSBwb3N0aW5nIGl0IHRvIHRoZSBNUExTIFdHIGxpc3QgZm9yDQo+ID4+Pj4+IHJldmlldy4N
Cj4gPj4+Pj4+ID09PT09PT0NCj4gPj4+Pj4+DQo+ID4+Pj4+PiBSZXNwb25zZSB0byBVcGRhdGVk
IGRyYWZ0IFJlY29tbWVuZGF0aW9uIEcudHBvYW0gW1JlZg0KPiA+Pj4+PiAwNDMuMDJdDQo+ID4+
Pj4+PiBGcm9tOiBJRVRGIExpYWlzb24gdG8gSVRVLVQgb24gTVBMUyBzdGJyeWFudEBjaXNjby5j
b20NCj4gPj4+Pj4+IFRvOiB0c2JzZzE1QGl0dS5pbnQsDQo+ID4+Pj4+IGdyZWcuam9uZXNAaXR1
LmludCwNCj4gPj4+Pj4gaGlyb3NoaS5vdGFAaXR1LmludCwNCj4gPj4+Pj4gSUFCQGlldGYub3Jn
DQo+ID4+Pj4+PiBDQzogR3JlZyBKb25lcywgc3dhbGxvd0BjaXNjby5jb20sDQo+ID4+Pj4+IGxv
YUBwaS5udSwgcGFmQGNpc2NvLmNvbQ0KPiA+Pj4+Pj4gc3RicnlhbnRAY2lzY28uY29tLA0KPiA+
Pj4+PiBhZHJpYW4uZmFycmVsQGh1YXdlaS5jb20sDQo+ID4+Pj4+IG1wbHNAaWV0Zi5vcmcNCj4g
Pj4+Pj4+IHlvaWNoaS5tYWVkYUB0dGMub3IuanAsDQo+ID4+Pj4+IHN0ZXZlLnRyb3dicmlkZ2VA
YWxjYXRlbC1sdWNlbnQuY29tDQo+ID4+Pj4+DQo+ID4+Pj4+PiBnaGFuaS5hYmJhc0Blcmljc3Nv
bi5jb20sDQo+ID4+Pj4+IGhoZWx2b29ydEBodWF3ZWkuY29tDQo+ID4+Pj4+DQo+ID4+Pj4+PiBt
YWxjb2xtLmJldHRzQHp0ZS5jb20uY24sDQo+ID4+Pj4+IGthbS5sYW1AYWxjYXRlbC1sdWNlbnQu
Y29tDQo+ID4+Pj4+DQo+ID4+Pj4+PiBGb3IgQWN0aW9uDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gVGhl
IE1QTFMgV29ya2luZyBHcm91cCBub3RlcyB0aGF0IHRoaXMgZG9jdW1lbnQNCj4gPj4+Pj4gY29u
dGFpbnMgdGV4dCBkZXNjcmliaW5nDQo+ID4+Pj4+PiBNUExTLVRQIE9BTSBwcm90b2NvbHMgbm90
IGRlc2lnbmVkIGFuZCBzdGFuZGFyZGl6ZWQNCj4gPj4+Pj4gdXNpbmcgdGhlIElFVEYNCj4gPj4+
Pj4+IFN0YW5kYXJkcyBwcm9jZXNzLiBTcGVjaWZpY2FsbHkgaXQgdXNlcyBtYXRlcmlhbCBmcm9t
DQo+ID4+Pj4+PiBkcmFmdC1iaGgtbXBscy10cC1vYW0teTE3MzEtMDYuDQo+ID4+Pj4+Pg0KPiA+
Pj4+Pj4gV2Ugd2lzaCB0byBkcmF3IHlvdXIgYXR0ZW50aW9uIHRvIHRoZSBzdGF0dXMgc2VjdGlv
bg0KPiA+Pj4+PiBvZg0KPiA+Pj4+Pj4gZHJhZnQtYmhoLW1wbHMtdHAtb2FtLXkxNzMxLTA2IHdo
aWNoIHN0YXRlczoNCj4gPj4+Pj4+DQo+ID4+Pj4+PiAiSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFm
dCBkb2N1bWVudHMgdmFsaWQgZm9yIGENCj4gPj4+Pj4gbWF4aW11bSBvZiBzaXggbW9udGhzDQo+
ID4+Pj4+PiBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3Ro
ZXINCj4gPj4+Pj4gZG9jdW1lbnRzIGF0IGFueQ0KPiA+Pj4+Pj4gdGltZS4gSXQgaXMgaW5hcHBy
b3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzDQo+ID4+Pj4+IHJlZmVyZW5jZSBtYXRl
cmlhbA0KPiA+Pj4+Pj4gb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndvcmsgaW4gcHJv
Z3Jlc3MiLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IFBsZWFzZSBhbHNvIG5vdGUgdGhhdCBzaW5jZSB0
aGUgZHJhZnQgZmlsZW5hbWUgc3RhcnRzDQo+ID4+Pj4+IHdpdGggdGhlIHByZWZpeA0KPiA+Pj4+
Pj4gc3RyaW5nICJkcmFmdC1iaGgiIHRoaXMgY2xlYXJseSBpZGVudGlmaWVzIGl0IHRvIHRoZQ0K
PiA+Pj4+PiByZWFkZXIgYXMgYQ0KPiA+Pj4+Pj4gZG9jdW1lbnQgZXhwcmVzc2luZyB0aGUgcGVy
c29uYWwgdGVjaG5pY2FsIHZpZXdzIG9mDQo+ID4+Pj4+IHRoZSBhdXRob3JzIGFuZA0KPiA+Pj4+
Pj4gaGVuY2UgaGVuY2UgYXMgYSBkb2N1bWVudCB0aGF0IHRoYXQgZG9lcyBub3QgaGF2ZSBhbnkN
Cj4gPj4+Pj4gYWNrbm93bGVkZ2VkIGxldmVsDQo+ID4+Pj4+PiBvZiBJRVRGIGNvbnNlbnN1cy4N
Cj4gPj4+Pj4+DQo+ID4+Pj4+PiBTaW5jZSB0aGUgdGV4dCBvZiBkcmFmdCBSZWNvbW1lbmRhdGlv
biBmb3IgRy50cG9hbSBpcw0KPiA+Pj4+PiBiYXNlZCBvbiBhbg0KPiA+Pj4+Pj4gTVBMUy1UUCBP
QU0gcHJvdG9jb2wgbm90IGRlc2lnbmVkIHdpdGhpbiB0aGUgSUVURg0KPiA+Pj4+PiBTdGFuZGFy
ZHMgUHJvY2VzcyB0aGlzDQo+ID4+Pj4+PiBpcyBhIGJyZWFjaCBvZiB0aGUgU0cxNSBhZ3JlZW1l
bnQgd2l0aCB0aGUgSUVURiBhcw0KPiA+Pj4+PiBwdWJsaXNoZWQgaW4gUmVwb3J0DQo+ID4+Pj4+
PiBvZiB0aGUgZmlyc3QgbWVldGluZyBvZiBXb3JraW5nIFBhcnR5IDMvMTUgVHJhbnNwb3J0DQo+
ID4+Pj4+IG5ldHdvcmsgc3RydWN0dXJlcw0KPiA+Pj4+Pj4gKDIwMDktMjAxMikgKEdlbmV2YSwg
MSDigJMgMTIgRGVjZW1iZXIgMjAwOCkgd2hpY2ggY2FuDQo+ID4+Pj4+IGJlIGZvdW5kIGF0DQo+
ID4+Pj4+PiBodHRwOi8vd3d3Lml0dS5pbnQvbWQvVDA5LVNHMTUtUi0wMDA0L2VuDQo+ID4+Pj4+
PiBQbGVhc2UgY29uZmlybSB0aGF0IHRoZSBJVFUtVCBpbnRlbmRzIHRvIGNvbnRpbnVlIHdpdGgN
Cj4gPj4+Pj4gdGhlIGpvaW50IHdvcmsgb24NCj4gPj4+Pj4+IE1QTFMtVFAgYW5kIHRoYXQgdGhl
IElUVS1UIHdpbGwgYWxpZ24gdGhpcw0KPiA+Pj4+PiByZWNvbW1lbmRhdGlvbiB3aXRoIHRoZSBJ
RVRGDQo+ID4+Pj4+PiBNUExTLVRQIE9BTSBkZXNpZ24gYmVmb3JlIGFkdmFuY2luZyB0aGlzIGRv
Y3VtZW50DQo+ID4+Pj4+IHRocm91Z2ggdGhlIElUVS1UDQo+ID4+Pj4+PiBwdWJsaWNhdGlvbiBw
cm9jZXNzLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IFRoZSBNUExTIFdvcmtpbmcgR3JvdXAgd291bGQg
YWxzbyBsaWtlIHRvIGRyYXcgdGhlDQo+ID4+Pj4+IGF0dGVudGlvbiBvZiBJVFUtVA0KPiA+Pj4+
Pj4gU0cxNSB0byB0aGUgSUVURiBjb3B5cmlnaHQgcnVsZXMuIFBsZWFzZSBzZWUNCj4gPj4+Pj4+
IGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mby9hcmNoaXZlL0lFVEYtVHJ1c3Qt
TGljZW5zZS0NCj4gUG9sDQo+ID4+Pj4+PiBpY3ktDQo+ID4+Pj4+PiAyMDA5MTIyOC5odG0NCj4g
Pj4+Pj4+IGZvciBmdXJ0aGVyIGRldGFpbHMuDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gU2luY2UgdGhp
cyBkcmFmdCBSZWNvbW1lbmRhdGlvbiBjb250YWlucyB0ZXh0IGluIHdoaWNoDQo+ID4+Pj4+IHRo
ZSBJVFUtVCBTRzE1DQo+ID4+Pj4+PiBoYXMgcHJvcG9zZWQgbWFraW5nIGNoYW5nZXMgdG8gSUVU
RiBwcm90b2NvbHMgd2l0aG91dA0KPiA+Pj4+PiB0aGUgYXBwcm92YWwgb2YNCj4gPj4+Pj4+IHRo
ZSBJRVRGLCB0aGUgTVBMUyBXb3JraW5nIEdyb3VwIGhhdmUgcmVmZXJyZWQgdGhpcw0KPiA+Pj4+
PiBsaWFpc29uIHRvIHRoZSBJQUINCj4gPj4+Pj4+IGZvciB0aGVpciBjb25zaWRlcmF0aW9uLg0K
PiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gPT09PT09PT09DQo+ID4+Pj4+
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+Pj4+
Pj4gbXBscyBtYWlsaW5nIGxpc3QNCj4gPj4+Pj4+IG1wbHNAaWV0Zi5vcmcNCj4gPj4+Pj4+IGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0KPiA+Pj4+Pj4NCj4gPj4+
Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPiA+Pj4+PiBtcGxzLXRwIG1haWxpbmcgbGlzdA0KPiA+
Pj4+PiBtcGxzLXRwQGlldGYub3JnDQo+ID4+Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vbXBscy10cA0KPiA+Pj4+Pg0KPiA+Pj4+DQo+ID4+Pj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj4+PiBtcGxzLXRwIG1haWxp
bmcgbGlzdA0KPiA+Pj4+IG1wbHMtdHBAaWV0Zi5vcmcNCj4gPj4+PiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMtdHANCj4gPj4+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+PiBtcGxzIG1haWxpbmcgbGlzdA0KPiA+
Pj4gbXBsc0BpZXRmLm9yZw0KPiA+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9tcGxzDQo+ID4+DQo+ID4+IC0tDQo+ID4+IEZvciBjb3Jwb3JhdGUgbGVnYWwgaW5mb3Jt
YXRpb24gZ28gdG86DQo+ID4+DQo+ID4+IGh0dHA6Ly93d3cuY2lzY28uY29tL3dlYi9hYm91dC9k
b2luZ19idXNpbmVzcy9sZWdhbC9jcmkvaW5kZXguaHRtbA0KPiA+Pg0KPiA+Pg0KPiA+PiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+PiBtcGxzIG1h
aWxpbmcgbGlzdA0KPiA+PiBtcGxzQGlldGYub3JnDQo+ID4+IGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vbXBscw0KPiA+DQo+ID4NCj4gDQo+IA0KPiAtLQ0KPiAqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
Kg0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgIOaIkeeIseWklueCueS4gOS4g+S4ieS4gA0K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBtcGxz
LXRwIG1haWxpbmcgbGlzdA0KPiBtcGxzLXRwQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vbXBscy10cA0K

From ietf@cdl.asgaard.org  Thu Jan 13 14:51:10 2011
Return-Path: <ietf@cdl.asgaard.org>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4060B3A6BED; Thu, 13 Jan 2011 14:51:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level: 
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bbvc-a5J2zzd; Thu, 13 Jan 2011 14:51:07 -0800 (PST)
Received: from asgaard.org (ratatosk.asgaard.org [204.29.150.73]) by core3.amsl.com (Postfix) with ESMTP id 673AC3A6452; Thu, 13 Jan 2011 14:51:06 -0800 (PST)
Received: from fenrir.asgaard.org (fenrir.asgaard.org [204.29.152.154]) by asgaard.org (Postfix) with ESMTP id 21193A0951B; Thu, 13 Jan 2011 22:53:25 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-139-971899664"
From: Christopher LILJENSTOLPE <ietf@cdl.asgaard.org>
In-Reply-To: <077E41CFFD002C4CAB7DFA4386A53264033056FB@DEMUEXC014.nsn-intra.net>
Date: Fri, 14 Jan 2011 09:53:15 +1100
Message-Id: <616B8263-BEB6-4A15-9F8C-E9798A726CA5@cdl.asgaard.org>
References: <1294906173.4d2eb33dd1ffa@gold.itu.ch> <526321.56478.qm@web15605.mail.cnb.yahoo.com> <077E41CFFD002C4CAB7DFA4386A53264033056FB@DEMUEXC014.nsn-intra.net>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Content-Transfer-Encoding: 7bit
X-Pgp-Agent: GPGMail 1.3.1
X-Mailer: Apple Mail (2.1082)
Cc: mpls@ietf.org, jingr@ties.itu.ch, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draftRecommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 22:51:10 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-139-971899664
Content-Type: multipart/alternative; boundary=Apple-Mail-138-971899564


--Apple-Mail-138-971899564
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I agree with Nurit.

	Christopher LILJENSTOLPE
	Director, Architecture, Telstra


On 14Jan2011, at 02.30, Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:

> Han Li,
>=20
> Please note that this liaison is not intended to get into technical =
discussion or into SPs' requirements.=20
>=20
> It is more on the procedures and processes....
>=20
> According to the collaborative agreement between the ITU-T and the =
IETF (which was accepted by ITU-T SG15 in December 2008), the =
development of the protocol should be done in the IETF using the IETF =
processes. The ITU-T documents should refer to the IETF solutions.=20
>=20
> We note a document (under development) in the ITU-T (g.tpoam), which =
includes the definition of messages and procedures for MSPL-TP which =
were not developed using the IETF standard processes and does not follow =
the IETF change/extension processes. This is contrary to the agreement =
between the IETF and the ITU-T from December 2008.=20
>=20
> We are responding on the process and want to be sure (and hope) that =
the ITU-T intends to continue with the joint work on MPLS-TP as agreed =
on in December 2008.=20
>=20
> I think the liaison is very well written!
>=20
> Best regards,
>=20
> Nurit
>=20
>=20
>=20
> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On =
Behalf Of ext Larry
> Sent: Thursday, January 13, 2011 4:56 PM
> To: jingr@ties.itu.ch; ruiquan.jing@ties.itu.int
> Cc: mpls@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated =
draftRecommendation G.tpoam [Ref043.02]
>=20
>=20
>=20
> Hi,
>=20
>=20
>=20
>    I don't think it is proper to send the LS to ITU-T because the text =
doesn't reflect the requirement from providers.
>=20
>    Apparently, draft-bhh based OAM is the most mature solution =
currently. It has been proved by more than 200,000 applications and is =
supported by a lot of operators and vendors.=20
>=20
>=20
>=20
> Best regards,
>=20
>=20
>=20
>              Han Li
>=20
>=20
>=20
> =
*************************************************************************
>=20
> Han Li, Ph.D=20
>=20
> China Mobile Research Institute
>=20
> Unit 2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China=20
>=20
> Fax: +86 10 63601087=20
>=20
> MOBILE: 13501093385=20
>=20
> =
*************************************************************************
>=20
>=20
>=20
>=20
>=20
> --- 11=E5=B9=B41=E6=9C=8813=E6=97=A5=EF=BC=8C=E5=91=A8=E5=9B=9B, =
ruiquan.jing@ties.itu.int <ruiquan.jing@ties.itu.int> =E5=86=99=E9=81=93=EF=
=BC=9A
>=20
>=20
>=20
>> =E5=8F=91=E4=BB=B6=E4=BA=BA: ruiquan.jing@ties.itu.int =
<ruiquan.jing@ties.itu.int>
>=20
>> =E4=B8=BB=E9=A2=98: Re: [mpls-tp] [mpls] Draft: Response to Updated =
draft Recommendation G.tpoam [Ref043.02]
>=20
>> =E6=94=B6=E4=BB=B6=E4=BA=BA: jingr@ties.itu.ch
>=20
>> =E6=8A=84=E9=80=81: mpls-tp@ietf.org
>=20
>> =E6=97=A5=E6=9C=9F: 2011=E5=B9=B41=E6=9C=8813=E6=97=A5,=E5=91=A8=E5=9B=9B=
,=E4=B8=8B=E5=8D=884:09
>=20
>> Resend to mpls-tp list.
>=20
>>=20
>=20
>> Quoting jingr@ties.itu.ch:
>=20
>>=20
>=20
>>> Hi Stewart Bryant,
>=20
>>>=20
>=20
>>> I don=E2=80=99t agree with the current LS text.
>=20
>>>=20
>=20
>>> China Telecom support the standardization of Y.1731
>=20
>> based MPLS-TP OAM tools
>=20
>>> in=20
>=20
>>> the ITU-T to meet the urgent and increasing
>=20
>> requirements for PTN deployment.=20
>=20
>>>=20
>=20
>>> It=E2=80=99s a multi-vendor supported, interoperability
>=20
>> certificated and feasible=20
>=20
>>> solution.  It had been specified in both CCSA
>=20
>> (China Communications Standards
>=20
>>>=20
>=20
>>> Association) and China Telecom=E2=80=99s PTN standard as the
>=20
>> only standard OAM=20
>=20
>>> mechanism.
>=20
>>>=20
>=20
>>>=20
>=20
>>>=20
>=20
>>> Best Regards
>=20
>>>=20
>=20
>>> Jing Ruiquan
>=20
>>>=20
>=20
>>> China=E3=80=80Telecom  Beijing=20
>=20
>> Research=E3=80=80Institute
>=20
>>>=20
>=20
>>>=20
>=20
>> =
--------------------------------------------------------------------------=
----
>=20
>> --
>=20
>>> From: mpls-bounces@ietf.org
>=20
>> [mailto:mpls-bounces@ietf.org]
>=20
>> On Behalf Of
>=20
>>> Stewart=20
>=20
>>> Bryant
>=20
>>> Sent: Monday, January 10, 2011 6:57 PM
>=20
>>> To: mpls@ietf.org
>=20
>>> Subject: [mpls] Draft: Response to Updated draft
>=20
>> Recommendation G.tpoam=20
>=20
>>> [Ref043.02]
>=20
>>>=20
>=20
>>>=20
>=20
>>> I propose to send the following Liaison Response to
>=20
>> the ITU-T on Friday=20
>=20
>>> 14th January and am posting it to the MPLS WG list for
>=20
>> review.=20
>=20
>>>=20
>=20
>>> =3D=3D=3D=3D=3D=3D=3D=20
>=20
>>>=20
>=20
>>> Response to Updated draft Recommendation G.tpoam [Ref
>=20
>> 043.02]=20
>=20
>>>=20
>=20
>>> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>=20
>>=20
>=20
>>> To: tsbsg15@itu.int,
>=20
>> greg.jones@itu.int,
>=20
>> hiroshi.ota@itu.int,
>=20
>> IAB@ietf.org=20
>=20
>>> CC: Greg Jones, swallow@cisco.com,
>=20
>> loa@pi.nu, paf@cisco.com=20
>=20
>>> stbryant@cisco.com,
>=20
>> adrian.farrel@huawei.com,
>=20
>> mpls@ietf.org=20
>=20
>>> yoichi.maeda@ttc.or.jp,
>=20
>> steve.trowbridge@alcatel-lucent.com
>=20
>>=20
>=20
>>> ghani.abbas@ericsson.com,
>=20
>> hhelvoort@huawei.com
>=20
>>=20
>=20
>>> malcolm.betts@zte.com.cn,
>=20
>> kam.lam@alcatel-lucent.com
>=20
>>=20
>=20
>>>=20
>=20
>>> For Action=20
>=20
>>>=20
>=20
>>> The MPLS Working Group notes that this document
>=20
>> contains text describing=20
>=20
>>> MPLS-TP OAM protocols not designed and standardized
>=20
>> using the IETF=20
>=20
>>> Standards process. Specifically it uses material from
>=20
>>=20
>=20
>>> draft-bhh-mpls-tp-oam-y1731-06.=20
>=20
>>>=20
>=20
>>> We wish to draw your attention to the status section
>=20
>> of=20
>=20
>>> draft-bhh-mpls-tp-oam-y1731-06 which states:=20
>=20
>>>=20
>=20
>>> "Internet-Drafts are draft documents valid for a
>=20
>> maximum of six months=20
>=20
>>> and may be updated, replaced, or obsoleted by other
>=20
>> documents at any=20
>=20
>>> time. It is inappropriate to use Internet-Drafts as
>=20
>> reference material=20
>=20
>>> or to cite them other than as "work in progress".=20
>=20
>>>=20
>=20
>>> Please also note that since the draft filename starts
>=20
>> with the prefix=20
>=20
>>> string "draft-bhh" this clearly identifies it to the
>=20
>> reader as a=20
>=20
>>> document expressing the personal technical views of
>=20
>> the authors and=20
>=20
>>> hence hence as a document that that does not have any
>=20
>> acknowledged level=20
>=20
>>> of IETF consensus.=20
>=20
>>>=20
>=20
>>> Since the text of draft Recommendation for G.tpoam is
>=20
>> based on an=20
>=20
>>> MPLS-TP OAM protocol not designed within the IETF
>=20
>> Standards Process this=20
>=20
>>> is a breach of the SG15 agreement with the IETF as
>=20
>> published in Report=20
>=20
>>> of the first meeting of Working Party 3/15 Transport
>=20
>> network structures=20
>=20
>>> (2009-2012) (Geneva, 1 =E2=80=93 12 December 2008) which can
>=20
>> be found at=20
>=20
>>> http://www.itu.int/md/T09-SG15-R-0004/en
>=20
>>=20
>=20
>>>=20
>=20
>>> Please confirm that the ITU-T intends to continue with
>=20
>> the joint work on=20
>=20
>>> MPLS-TP and that the ITU-T will align this
>=20
>> recommendation with the IETF=20
>=20
>>> MPLS-TP OAM design before advancing this document
>=20
>> through the ITU-T=20
>=20
>>> publication process.=20
>=20
>>>=20
>=20
>>> The MPLS Working Group would also like to draw the
>=20
>> attention of ITU-T=20
>=20
>>> SG15 to the IETF copyright rules. Please see=20
>=20
>>> =
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-
>=20
>>> 20091228.htm=20
>=20
>>> for further details.=20
>=20
>>>=20
>=20
>>> Since this draft Recommendation contains text in which
>=20
>> the ITU-T SG15=20
>=20
>>> has proposed making changes to IETF protocols without
>=20
>> the approval of=20
>=20
>>> the IETF, the MPLS Working Group have referred this
>=20
>> liaison to the IAB=20
>=20
>>> for their consideration.=20
>=20
>>>=20
>=20
>>>=20
>=20
>>>=20
>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=20
>=20
>>> _______________________________________________=20
>=20
>>> mpls mailing list=20
>=20
>>> mpls@ietf.org=20
>=20
>>> https://www.ietf.org/mailman/listinfo/mpls=20
>=20
>>>=20
>=20
>>>=20
>=20
>>>=20
>=20
>>=20
>=20
>>=20
>=20
>>=20
>=20
>> _______________________________________________
>=20
>> mpls-tp mailing list
>=20
>> mpls-tp@ietf.org
>=20
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>=20
>>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
>=20
> mpls-tp mailing list
>=20
> mpls-tp@ietf.org
>=20
> https://www.ietf.org/mailman/listinfo/mpls-tp
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

---
=E6=9D=8E=E6=9F=AF=E7=9D=BF
Check my PGP key here:
https://www.asgaard.org/~cdl/cdl.asc


--Apple-Mail-138-971899564
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
agree with Nurit.<div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Christopher =
LILJENSTOLPE</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Director, Architecture, =
Telstra</div><div><br></div><div><br><div><div>On 14Jan2011, at 02.30, =
Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Han =
Li,<br><br>Please note that this liaison is not intended to get into =
technical discussion or into SPs' requirements. <br><br>It is more on =
the procedures and processes....<br><br>According to the collaborative =
agreement between the ITU-T and the IETF (which was accepted by ITU-T =
SG15 in December 2008), the development of the protocol should be done =
in the IETF using the IETF processes. The ITU-T documents should refer =
to the IETF solutions. <br><br>We note a document (under development) in =
the ITU-T (g.tpoam), which includes the definition of messages and =
procedures for MSPL-TP which were not developed using the IETF standard =
processes and does not follow the IETF change/extension processes. This =
is contrary to the agreement between the IETF and the ITU-T from =
December 2008. <br><br>We are responding on the process and want to be =
sure (and hope) that the ITU-T intends to continue with the joint work =
on MPLS-TP as agreed on in December 2008. <br><br>I think the liaison is =
very well written!<br><br>Best =
regards,<br><br>Nurit<br><br><br><br>-----Original Message-----<br>From: =
<a href=3D"mailto:mpls-tp-bounces@ietf.org">mpls-tp-bounces@ietf.org</a> =
[mailto:mpls-tp-bounces@ietf.org] On Behalf Of ext Larry<br>Sent: =
Thursday, January 13, 2011 4:56 PM<br>To: <a =
href=3D"mailto:jingr@ties.itu.ch">jingr@ties.itu.ch</a>; <a =
href=3D"mailto:ruiquan.jing@ties.itu.int">ruiquan.jing@ties.itu.int</a><br=
>Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br>Subject: Re: =
[mpls-tp] [mpls] Draft: Response to Updated draftRecommendation G.tpoam =
[Ref043.02]<br><br><br><br>Hi,<br><br><br><br> &nbsp;&nbsp;&nbsp;I don't =
think it is proper to send the LS to ITU-T because the text doesn't =
reflect the requirement from providers.<br><br> =
&nbsp;&nbsp;&nbsp;Apparently, draft-bhh based OAM is the most mature =
solution currently. It has been proved by more than 200,000 applications =
and is supported by a lot of operators and vendors. <br><br><br><br>Best =
regards,<br><br><br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;Han =
Li<br><br><br><br>********************************************************=
*****************<br><br>Han Li, Ph.D <br><br>China Mobile Research =
Institute<br><br>Unit 2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing =
100053, China <br><br>Fax: +86 10 63601087 <br><br>MOBILE: 13501093385 =
<br><br>******************************************************************=
*******<br><br><br><br><br><br>--- 11=E5=B9=B41=E6=9C=8813=E6=97=A5=EF=BC=8C=
=E5=91=A8=E5=9B=9B, <a =
href=3D"mailto:ruiquan.jing@ties.itu.int">ruiquan.jing@ties.itu.int</a> =
&lt;<a =
href=3D"mailto:ruiquan.jing@ties.itu.int">ruiquan.jing@ties.itu.int</a>&gt=
; =E5=86=99=E9=81=93=EF=BC=9A<br><br><br><br><blockquote =
type=3D"cite">=E5=8F=91=E4=BB=B6=E4=BA=BA: <a =
href=3D"mailto:ruiquan.jing@ties.itu.int">ruiquan.jing@ties.itu.int</a> =
&lt;<a =
href=3D"mailto:ruiquan.jing@ties.itu.int">ruiquan.jing@ties.itu.int</a>&gt=
;<br></blockquote><br><blockquote type=3D"cite">=E4=B8=BB=E9=A2=98: Re: =
[mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.tpoam =
[Ref043.02]<br></blockquote><br><blockquote type=3D"cite">=E6=94=B6=E4=BB=B6=
=E4=BA=BA: <a =
href=3D"mailto:jingr@ties.itu.ch">jingr@ties.itu.ch</a><br></blockquote><b=
r><blockquote type=3D"cite">=E6=8A=84=E9=80=81: <a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br></blockquote><br>=
<blockquote type=3D"cite">=E6=97=A5=E6=9C=9F: =
2011=E5=B9=B41=E6=9C=8813=E6=97=A5,=E5=91=A8=E5=9B=9B,=E4=B8=8B=E5=8D=884:=
09<br></blockquote><br><blockquote type=3D"cite">Resend to mpls-tp =
list.<br></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote type=3D"cite">Quoting <a =
href=3D"mailto:jingr@ties.itu.ch">jingr@ties.itu.ch</a>:<br></blockquote><=
br><blockquote type=3D"cite"><br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Hi Stewart =
Bryant,<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">I don=E2=80=99t agree with the =
current LS text.<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">China Telecom support the =
standardization of Y.1731<br></blockquote></blockquote><br><blockquote =
type=3D"cite">based MPLS-TP OAM tools<br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">in =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">the ITU-T to meet the urgent and =
increasing<br></blockquote></blockquote><br><blockquote =
type=3D"cite">requirements for PTN deployment. =
<br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">It=E2=80=99s a multi-vendor =
supported, interoperability<br></blockquote></blockquote><br><blockquote =
type=3D"cite">certificated and feasible <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">solution. &nbsp;It had been =
specified in both CCSA<br></blockquote></blockquote><br><blockquote =
type=3D"cite">(China Communications =
Standards<br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Association) and China =
Telecom=E2=80=99s PTN standard as =
the<br></blockquote></blockquote><br><blockquote type=3D"cite">only =
standard OAM <br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">mechanism.<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Best =
Regards<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Jing =
Ruiquan<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">China=E3=80=80Telecom =
&nbsp;Beijing <br></blockquote></blockquote><br><blockquote =
type=3D"cite">Research=E3=80=80Institute<br></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite">------------------------------------------------------------=
------------------<br></blockquote><br><blockquote =
type=3D"cite">--<br></blockquote><br><blockquote type=3D"cite"><blockquote=
 type=3D"cite">From: <a =
href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a><br></block=
quote></blockquote><br><blockquote =
type=3D"cite">[mailto:mpls-bounces@ietf.org]<br></blockquote><br><blockquo=
te type=3D"cite">On Behalf Of<br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Stewart =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">Bryant<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Sent: Monday, January 10, 2011 =
6:57 PM<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">To: <a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br></blockquote></blockquo=
te><br><blockquote type=3D"cite"><blockquote type=3D"cite">Subject: =
[mpls] Draft: Response to Updated =
draft<br></blockquote></blockquote><br><blockquote =
type=3D"cite">Recommendation G.tpoam <br></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">[Ref043.02]<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">I propose to send the following =
Liaison Response to<br></blockquote></blockquote><br><blockquote =
type=3D"cite">the ITU-T on Friday <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">14th January and am posting it =
to the MPLS WG list for<br></blockquote></blockquote><br><blockquote =
type=3D"cite">review. <br></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">=3D=3D=3D=3D=3D=3D=3D =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Response to Updated draft =
Recommendation G.tpoam [Ref<br></blockquote></blockquote><br><blockquote =
type=3D"cite">043.02] <br></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">From: IETF Liaison to ITU-T on =
MPLS <a =
href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a><br></blockquote>=
</blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">To: <a =
href=3D"mailto:tsbsg15@itu.int">tsbsg15@itu.int</a>,<br></blockquote></blo=
ckquote><br><blockquote type=3D"cite"><a =
href=3D"mailto:greg.jones@itu.int">greg.jones@itu.int</a>,<br></blockquote=
><br><blockquote type=3D"cite"><a =
href=3D"mailto:hiroshi.ota@itu.int">hiroshi.ota@itu.int</a>,<br></blockquo=
te><br><blockquote type=3D"cite"><a =
href=3D"mailto:IAB@ietf.org">IAB@ietf.org</a> =
<br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">CC: Greg Jones, <a =
href=3D"mailto:swallow@cisco.com">swallow@cisco.com</a>,<br></blockquote><=
/blockquote><br><blockquote type=3D"cite"><a =
href=3D"mailto:loa@pi.nu">loa@pi.nu</a>, <a =
href=3D"mailto:paf@cisco.com">paf@cisco.com</a> =
<br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>,<br></blockquote=
></blockquote><br><blockquote type=3D"cite"><a =
href=3D"mailto:adrian.farrel@huawei.com">adrian.farrel@huawei.com</a>,<br>=
</blockquote><br><blockquote type=3D"cite"><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> =
<br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"mailto:yoichi.maeda@ttc.or.jp">yoichi.maeda@ttc.or.jp</a>,<br></bl=
ockquote></blockquote><br><blockquote type=3D"cite"><a =
href=3D"mailto:steve.trowbridge@alcatel-lucent.com">steve.trowbridge@alcat=
el-lucent.com</a><br></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"mailto:ghani.abbas@ericsson.com">ghani.abbas@ericsson.com</a>,<br>=
</blockquote></blockquote><br><blockquote type=3D"cite"><a =
href=3D"mailto:hhelvoort@huawei.com">hhelvoort@huawei.com</a><br></blockqu=
ote><br><blockquote type=3D"cite"><br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"mailto:malcolm.betts@zte.com.cn">malcolm.betts@zte.com.cn</a>,<br>=
</blockquote></blockquote><br><blockquote type=3D"cite"><a =
href=3D"mailto:kam.lam@alcatel-lucent.com">kam.lam@alcatel-lucent.com</a><=
br></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">For Action =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">The MPLS Working Group notes =
that this document<br></blockquote></blockquote><br><blockquote =
type=3D"cite">contains text describing <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">MPLS-TP OAM protocols not =
designed and standardized<br></blockquote></blockquote><br><blockquote =
type=3D"cite">using the IETF <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Standards process. Specifically =
it uses material from<br></blockquote></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">draft-bhh-mpls-tp-oam-y1731-06. =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">We wish to draw your attention =
to the status section<br></blockquote></blockquote><br><blockquote =
type=3D"cite">of <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">draft-bhh-mpls-tp-oam-y1731-06 =
which states: <br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">"Internet-Drafts are draft =
documents valid for a<br></blockquote></blockquote><br><blockquote =
type=3D"cite">maximum of six months <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">and may be updated, replaced, or =
obsoleted by other<br></blockquote></blockquote><br><blockquote =
type=3D"cite">documents at any <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">time. It is inappropriate to use =
Internet-Drafts as<br></blockquote></blockquote><br><blockquote =
type=3D"cite">reference material <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">or to cite them other than as =
"work in progress". <br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Please also note that since the =
draft filename starts<br></blockquote></blockquote><br><blockquote =
type=3D"cite">with the prefix <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">string "draft-bhh" this clearly =
identifies it to the<br></blockquote></blockquote><br><blockquote =
type=3D"cite">reader as a <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">document expressing the personal =
technical views of<br></blockquote></blockquote><br><blockquote =
type=3D"cite">the authors and <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">hence hence as a document that =
that does not have any<br></blockquote></blockquote><br><blockquote =
type=3D"cite">acknowledged level <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">of IETF consensus. =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Since the text of draft =
Recommendation for G.tpoam =
is<br></blockquote></blockquote><br><blockquote type=3D"cite">based on =
an <br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">MPLS-TP OAM protocol not designed within the =
IETF<br></blockquote></blockquote><br><blockquote type=3D"cite">Standards =
Process this <br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">is a breach of the SG15 agreement with the IETF =
as<br></blockquote></blockquote><br><blockquote type=3D"cite">published =
in Report <br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">of the first meeting of Working Party 3/15 =
Transport<br></blockquote></blockquote><br><blockquote =
type=3D"cite">network structures <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">(2009-2012) (Geneva, 1 =E2=80=93 =
12 December 2008) which can<br></blockquote></blockquote><br><blockquote =
type=3D"cite">be found at <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"http://www.itu.int/md/T09-SG15-R-0004/en">http://www.itu.int/md/T0=
9-SG15-R-0004/en</a><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Please confirm that the ITU-T =
intends to continue with<br></blockquote></blockquote><br><blockquote =
type=3D"cite">the joint work on <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">MPLS-TP and that the ITU-T will =
align this<br></blockquote></blockquote><br><blockquote =
type=3D"cite">recommendation with the IETF =
<br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">MPLS-TP OAM design before advancing this =
document<br></blockquote></blockquote><br><blockquote =
type=3D"cite">through the ITU-T <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">publication process. =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">The MPLS Working Group would =
also like to draw the<br></blockquote></blockquote><br><blockquote =
type=3D"cite">attention of ITU-T <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">SG15 to the IETF copyright =
rules. Please see <br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Po=
licy-">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Pol=
icy-</a><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">20091228.htm =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">for further details. =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Since this draft Recommendation =
contains text in which<br></blockquote></blockquote><br><blockquote =
type=3D"cite">the ITU-T SG15 <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">has proposed making changes to =
IETF protocols without<br></blockquote></blockquote><br><blockquote =
type=3D"cite">the approval of <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">the IETF, the MPLS Working Group =
have referred this<br></blockquote></blockquote><br><blockquote =
type=3D"cite">liaison to the IAB <br></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">for their consideration. =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">=3D=3D=3D=3D=3D=3D=3D=3D=3D =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">_______________________________________________ =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">mpls mailing list =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> =
<br></blockquote></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/m=
ailman/listinfo/mpls</a> <br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><br><blockquote type=3D"cite">mpls-tp mailing =
list<br></blockquote><br><blockquote type=3D"cite"><a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br></blockquote><br>=
<blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ietf.or=
g/mailman/listinfo/mpls-tp</a><br></blockquote><br><blockquote =
type=3D"cite"><br></blockquote><br><br><br><br><br><br><br>_______________=
________________________________<br><br>mpls-tp mailing list<br><br><a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ietf.or=
g/mailman/listinfo/mpls-tp</a><br><br>____________________________________=
___________<br>mpls mailing =
list<br>mpls@ietf.org<br>https://www.ietf.org/mailman/listinfo/mpls<br></d=
iv></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
"><div>---</div><div>=E6=9D=8E=E6=9F=AF=E7=9D=BF<br>Check my PGP key =
here:<br><font class=3D"Apple-style-span" color=3D"#144FAE"><span =
class=3D"Apple-style-span" style=3D"text-decoration: underline; "><a =
href=3D"https://www.asgaard.org/~cdl/cdl.asc">https://www.asgaard.org/~cdl=
/cdl.asc</a></span></font></div></div></div></div></div></div></span></div=
></span></span>
</div>

<br></div></body></html>=

--Apple-Mail-138-971899564--

--Apple-Mail-139-971899664
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJNL4JiAAoJEGmx2Mt/+Iw/HqcH/0tFTxLD8N3m8kbgIEMCSRYb
rt+PiDVxcRXHJnS/bzbaSDjwNPkNxgOVUsSTOCvWfoqXnqEJVLBZT/LPVtW5RIuA
ExfQZ4XxoFUvUWasKpxH6F0icWhDlUwZJ0KBe/P8qnj7+i0RrpgdM2apjTn81XS5
WEfTCMBFB2dueE2OSdpa0HwvAhQppUV7wzz76+J8tEc6JH2YBBRmIfjdYJfYNXUJ
GwLR5tAPMKWMwT+hITjWSzfs8/isCmF8EC0RXlM84llNPzzjM3aZjaSF/cVXaz1e
kOfjA2CNDX3DYgb2HXQpxpmF0gjRa7iKMK+wOgoiHOFxABgZy3oY5dB70OKXvqs=
=edM8
-----END PGP SIGNATURE-----

--Apple-Mail-139-971899664--

From erminio.ottone_69@libero.it  Thu Jan 13 14:58:23 2011
Return-Path: <erminio.ottone_69@libero.it>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23BCC3A6C0D; Thu, 13 Jan 2011 14:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.269
X-Spam-Level: 
X-Spam-Status: No, score=-0.269 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id np24r9CxuIkw; Thu, 13 Jan 2011 14:58:21 -0800 (PST)
Received: from cp-out4.libero.it (cp-out4.libero.it [212.52.84.104]) by core3.amsl.com (Postfix) with ESMTP id 6DFAE3A6BED; Thu, 13 Jan 2011 14:58:20 -0800 (PST)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B0201.4D2F8400.0151,ss=1,re=0.000,fgs=0
X-libjamoibt: 1419
Received: from wmail62 (172.31.0.59) by cp-out4.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4D10BF99016537E4; Fri, 14 Jan 2011 00:00:16 +0100
Message-ID: <24506674.971481294959616690.JavaMail.defaultUser@defaultHost>
Date: Fri, 14 Jan 2011 00:00:16 +0100 (CET)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <nurit.sprecher@nsn.com>,  ext HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>,  <stbryant@cisco.com>,  <mpls@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-SenderIP: 79.30.163.233
Cc: mpls-tp@ietf.org
Subject: [mpls-tp] R: Re: [mpls] Draft: Response to Updated draft	Recommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 22:58:23 -0000

You forget that ITU-T experts have not been allowed to speak at IETF 79 and=
 a=20
new trend of approving RFCs without resolving ITU-T have been started.

>----Messaggio originale----
>Da: nurit.sprecher@nsn.com
>Data: 13-gen-2011 13.54
>A: "ext HUANG Feng F"<Feng.f.Huang@alcatel-sbell.com.cn>, <stbryant@cisco.
com>, <mpls@ietf.org>
>Cc: <mpls-tp@ietf.org>
>Ogg: Re: [mpls-tp] [mpls] Draft: Response to Updated draft=09Recommendatio=
n G.
tpoam[Ref043.02]
>
>Hi Feng,
>=09You say " HF> I can't image the meaning of cooperation is that ITU-T do=
=20
nothing and just obey IETF's process!"
>It seems that you are not familiar with the agreement on the joint work. T=
he=20
ITU-T experts are called to contribute to (also by the SG15) to assist in t=
he=20
development the development of the protocol in the IETF using the IETF stan=
dard=20
processes...
>Best regards,
>Nurit
>
>
>-----Original Message-----
>From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]=20
>Sent: Thursday, January 13, 2011 12:31 PM
>To: Sprecher,
> Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; mpls@ietf.org
>Cc: mpls-tp@ietf.org
>Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpoa=
m
[Ref043.02]
>
>Hi, Nurit,
>   Please see in line.
>B.R.
>Feng
>=20
>
>-----Original Message-----
>From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.
com]=20
>Sent: 2011=E5=B9=B41=E6=9C=8813=E6=97=A5 17:45
>To: HUANG Feng F; stbryant@cisco.com; mpls@ietf.org
>Cc: mpls-tp@ietf.org
>Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpoa=
m
[Ref043.02]
>
>Hi Feng,
>I did not refer to specific solution, validity and acceptance of a solutio=
n,=20
so I cannot see to what you disagree and how your response fit to mine.=20
>If you think that you have a good solution which is proven and supported=
=20
please discuss it in the IETF and try to get support for it!=20
>
>HF> The solution has been submitted to ietf for 2 year!
>
>I would like the ITU-T to continue with its collaborative agreement with t=
he=20
IETF and ensure that the development of the protocol is done as agreed and=
=20
supported by SG15 using the IETF processes.
>
>HF> I can't image the meaning of cooperation is that ITU-T do nothing and=
=20
just obey IETF's process!
>
>I will support a single global solution interoperable solution (whatever t=
he=20
solution is).=20
>Best regards,
>Nurit
>
>-----Original Message-----
>From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
>Sent: Thursday, January 13, 2011 11:35 AM
>To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; mpls@ietf=
.
org
>Cc: mpls-tp@ietf.org
>Subject: RE: [mpls] Draft: Response to Updated draft Recommendation G.tpoa=
m
[Ref043.02]
>
>Hi,Nurit,
>   I can't agree with you.
>   Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet Transp=
ort=20
Network by many applications and public demo and it has many supporters. I =
am=20
wondering why  this solutions is not  standardized in ietf?=20
>    Further more,  I really don't agree with your last sentence, this=20
solution is asked by customers in Industry, you can see at least 7 provider=
s in=20
global support this solution.
>
>B.R.
>Feng
>
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of=20
Sprecher, Nurit (NSN - IL/Hod HaSharon)
>Sent: 2011=E5=B9=B41=E6=9C=8813=E6=97=A5 16:18
>To: stbryant@cisco.com; mpls@ietf.org
>Subject: Re: [mpls] Draft: Response to Updated draft Recommendation G.tpoa=
m
[Ref043.02]
>
>Hi,
>I support the proposal.
>We have a cooperative agreement with the ITU-T concerning the work on MPLS=
-
TP.=20
>The agreement recognizes the design authority of the IETF for MPLS and it =
is=20
agreed that the development of the protocol should be done in the IETF usin=
g=20
the IETF processes. The ITU-T should not take any uncoordinated action in t=
he=20
development of the MPLS_TP protocol.=20
>We would appreciate if the ITU-T continues (as it committed to) with the=
=20
collaborative work with the IETF on MPLS_TP and contributes from its expert=
ise=20
to the development of the protocol using the IETF processes.=20
>We would also not like to see two competing solutions which may confuse th=
e=20
Industry, bloat operational and capital expenses and badly affect the end=
=20
customer.=20
>Best regards,
>Nurit
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of ex=
t=20
Stewart Bryant
>Sent: Monday, January 10, 2011 12:57 PM
>To: mpls@ietf.org
>Subject: [mpls] Draft: Response to Updated draft Recommendation G.tpoam=20
[Ref043.02]
>
>I propose to send the following Liaison Response to the ITU-T on Friday 14=
th=20
January and am posting it to the MPLS WG list for review.
>
>=3D=3D=3D=3D=3D=3D=3D
>
>Response to Updated draft Recommendation G.tpoam [Ref 043.02]
>
>From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, IAB@ietf.org
>CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com stbryant@cisco=
.
com, adrian.farrel@huawei.com, mpls@ietf.org yoichi.maeda@ttc.or.jp, steve.
trowbridge@alcatel-lucent.com
>ghani.abbas@ericsson.com, hhelvoort@huawei.com malcolm.betts@zte.com.cn, k=
am.
lam@alcatel-lucent.com
>
>For Action
>
>The MPLS Working Group notes that this document contains text describing
>
>MPLS-TP OAM protocols not designed and standardized using the IETF Standar=
ds=20
process. Specifically it uses material from draft-bhh-mpls-tp-oam-y1731-06.
>
>We wish to draw your attention to the status section of
>draft-bhh-mpls-tp-oam-y1731-06 which states:
>
>"Internet-Drafts are draft documents valid for a maximum of six months and=
=20
may be updated, replaced, or obsoleted by other documents at any time. It i=
s=20
inappropriate to use Internet-Drafts as reference material or to cite them=
=20
other than as "work in progress".
>
>Please also note that since the draft filename starts with the prefix stri=
ng=20
"draft-bhh" this clearly identifies it to the reader as a document expressi=
ng=20
the personal technical views of the authors and hence hence as a document t=
hat=20
that does not have any acknowledged level
>
>of IETF consensus.
>
>Since the text of draft Recommendation for G.tpoam is based on an MPLS-TP =
OAM=20
protocol not designed within the IETF Standards Process this
>
>is a breach of the SG15 agreement with the IETF as published in Report of =
the=20
first meeting of Working Party 3/15 Transport network structures
>(2009-2012) (Geneva, 1 - 12 December 2008) which can be found at http://ww=
w.
itu.int/md/T09-SG15-R-0004/en
>
>Please confirm that the ITU-T intends to continue with the joint work on
>
>MPLS-TP and that the ITU-T will align this recommendation with the IETF MP=
LS-
TP OAM design before advancing this document through the ITU-T publication=
=20
process.
>
>The MPLS Working Group would also like to draw the attention of ITU-T
>SG15 to the IETF copyright rules. Please see
>http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
>0091228.htm
>for further details.
>
>Since this draft Recommendation contains text in which the ITU-T SG15 has=
=20
proposed making changes to IETF protocols without the approval of the IETF,=
 the=20
MPLS Working Group have referred this liaison to the IAB for their=20
consideration.
>
>
>=3D=3D=3D=3D=3D=3D=3D=3D=3D
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>_______________________________________________
>mpls-tp mailing list
>mpls-tp@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls-tp
>



From tochio@jp.fujitsu.com  Thu Jan 13 15:08:21 2011
Return-Path: <tochio@jp.fujitsu.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFEC43A6C19; Thu, 13 Jan 2011 15:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level: 
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b9fApTXTzUpK; Thu, 13 Jan 2011 15:08:20 -0800 (PST)
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by core3.amsl.com (Postfix) with ESMTP id 5392C3A6BED; Thu, 13 Jan 2011 15:08:20 -0800 (PST)
Received: from m1.gw.fujitsu.co.jp (unknown [10.0.50.71]) by fgwmail7.fujitsu.co.jp (Postfix) with ESMTP id 34D013EE0B5; Fri, 14 Jan 2011 08:10:43 +0900 (JST)
Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 1D7CD2AEA8D; Fri, 14 Jan 2011 08:10:43 +0900 (JST)
Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id F067445DE54; Fri, 14 Jan 2011 08:10:42 +0900 (JST)
Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id E23EFE08001; Fri, 14 Jan 2011 08:10:42 +0900 (JST)
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id A75391DB8049; Fri, 14 Jan 2011 08:10:42 +0900 (JST)
Received: from vs.kawasaki.flab.fujitsu.co.jp (vs.kawasaki.flab.fujitsu.co.jp [10.25.192.38]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/100813-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id p0DNAghZ015582;  Fri, 14 Jan 2011 08:10:42 +0900 (JST)
X-AuditID: 0a19c026-00000005000001f8-92-4d2f867228ca
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vs.kawasaki.flab.fujitsu.co.jp (Symantec Mail Security) with ESMTP id 3FD042923D; Fri, 14 Jan 2011 08:10:42 +0900 (JST)
Received: from [127.0.0.1] (dhcp98.dream.flab.fujitsu.co.jp [10.25.144.157]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/100813-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id p0DNAfkA015579;  Fri, 14 Jan 2011 08:10:42 +0900 (JST)
X-SecurityPolicyCheck: OK by SHieldMailChecker v1.5.1
Message-ID: <4D2F8669.1090103@jp.fujitsu.com>
Date: Fri, 14 Jan 2011 08:10:33 +0900
From: Yuji Tochio <tochio@jp.fujitsu.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
References: <4D2AE56A.3060200@cisco.com> <4D2F7A4C.80304@gmail.com>
In-Reply-To: <4D2F7A4C.80304@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 23:08:21 -0000

Hi,

As to this response (G.8121), I support Huub's comment.
The important is to review the draft G.8121 so that IETF should
ask for the missing file at first.
In that sense, the first paragraph of LS with asking for the draft
(i.e. wd19r2) is enough.

Of course, ITU-T should have verified that the attachment is
included....

Regards,
Yuji

(2011/01/14 7:18), Huub van Helvoort wrote:
> Hello Stewart,
>
> You wrote:
>
>> I propose to send the following Liaison Response to the ITU-T on Friday
>> 14th January and am posting it to the MPLS WG list for review.
>
> I do not support sending the liaison as proposed.
>
> We should restrict it to the first paragraph noting that the file
> that should be reviewed is missing and ask for sending the missing
> file so it can be reviewed by the WG.
>
> The remainder of the text is based on assumptions and not on facts.
>
> Regards, Huub.
>
>
>> =========
>>
>> Response to Updated draft Recommendation G.8121 [Ref 042.02]
>>
>> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>> To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, IAB@ietf.org
>> CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com
>> stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org
>> yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
>> ghani.abbas@ericsson.com, hhelvoort@huawei.com
>> malcolm.betts@zte.com.cn, kam.lam@alcatel-lucent.com
>>
>> For Action
>>
>> Unfortunately ITU-T document WD19r2 was not attached to this liaison,
>> and thus the MPLS Working Group is unable to comment on its content at
>> this time.
>>
>> It is stated in the liaison that the modifications to this draft
>> Recommendation are based on draft-bhh-mpls-tp-oam-y1731-06. Please may
>> we draw your attention to the status section of
>> draft-bhh-mpls-tp-oam-y1731-06 which states
>>
>> "Internet-Drafts are draft documents valid for a maximum of six months
>> and may be updated, replaced, or obsoleted by other documents at any
>> time. It is inappropriate to use Internet-Drafts as reference material
>> or to cite them other than as "work in progress".
>>
>> Please also note that since the draft filename starts with the prefix
>> string "draft-bhh" this clearly identifies it to the reader as a
>> document expressing the personal technical views of the authors and
>> hence hence as a document that that does not have any acknowledged level
>> of IETF consensus.
>>
>> If this draft Recommendation for G.8121 is based on an MPLS-TP OAM
>> protocol not designed within the IETF Standards Process, the MPLS
>> Working Group believe that this would be in breach of the SG15 agreement
>> with the IETF as published in Report of the first meeting of Working
>> Party 3/15 Transport network structures (2009-2012) (Geneva, 1 – 12
>> December 2008) which can be found at
>> http://www.itu.int/md/T09-SG15-R-0004/en
>>
>> The MPLS Working Group would also like to draw the attention of ITU-T
>> SG15 to the IETF copyright rules. Please see
>> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.htm
>> for further details.
>>
>> We have referred this liaison to the IAB for their consideration.
>>
>>
>> ===========
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>



From nurit.sprecher@nsn.com  Thu Jan 13 15:10:51 2011
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 319CB3A6C13; Thu, 13 Jan 2011 15:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.496
X-Spam-Level: 
X-Spam-Status: No, score=-4.496 tagged_above=-999 required=5 tests=[AWL=1.503,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YtMs-kyu2gPL; Thu, 13 Jan 2011 15:10:46 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id A309A3A6C19; Thu, 13 Jan 2011 15:10:44 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0DND26l016404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 Jan 2011 00:13:02 +0100
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0DND28A030108; Fri, 14 Jan 2011 00:13:02 +0100
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Jan 2011 00:12:56 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Fri, 14 Jan 2011 00:12:53 +0100
Message-ID: <077E41CFFD002C4CAB7DFA4386A532640332E318@DEMUEXC014.nsn-intra.net>
In-Reply-To: <D29E470202D67745B61059870F433B54040D8FB2@XMB-RCD-202.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [mpls-tp] Draft: Response to Updateddraft	Recommendation G.tpoam [Ref043.02]
Thread-Index: AcuzcdYOACJqkL8SQ1KnmKq/hzcCPgAAFzOAAACWA8A=
References: <526321.56478.qm@web15605.mail.cnb.yahoo.com>	<EC7945C9-3C51-42A1-8CA8-692A94B28F2C@niven-jenkins.co.uk>	<4D2F27F1.1070209@cisco.com>	<6873FACCBB5DDD4D88AABD78A8E483A468CE4D0311@EUSAACMS0703.eamcs.ericsson.se><4D2F47F9.8040701@cisco.com><4D2F7D8E.9040505@gmail.com> <D29E470202D67745B61059870F433B54040D8FB2@XMB-RCD-202.cisco.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Eric Osborne (eosborne)" <eosborne@cisco.com>, "Huub van Helvoort" <huubatwork@gmail.com>, <mpls@ietf.org>, <mpls-tp@ietf.org>
X-OriginalArrivalTime: 13 Jan 2011 23:12:56.0270 (UTC) FILETIME=[69807EE0:01CBB377]
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updateddraft	Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 23:10:51 -0000

SHV1YiwNCkkgd291bGQgYWxzbyByZWNvbW1lbmQgeW91IHRvIHJlYWQgdGhlIHJlcG9ydCBvZiB0
aGUgcmFwcG9ydGV1cnMgb2YgUTksIFExMCwgUTEyIGFuZCBRMTQgZnJvbSB0aGUgQmVybGluIG1l
ZXRpbmcuDQpUaGUgcmVwb3J0IGV4cGxpY2l0bHkgc2F5cyB0aGF0IHdvcmsgd2FzIHVuZGVydGFr
ZW4gb24gdGhlIGRldmVsb3BtZW50IG9mIHRoZSBPQU0gcHJvdG9jb2wgRy50cG9hbSwgRy44MTIx
IGFuZCBHLjgxNTEuIFRoZSBkcmFmdHMgb2YgdGhlc2UgZG9jdW1lbnRzIGFyZSBiYXNlZCBvbiBk
cmFmdC1iaGgtbXBscy10cC1vYW0teTE3MzEtMDYuDQpCZXN0IHJlZ2FyZHMsDQpOdXJpdA0KDQot
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogbXBscy1ib3VuY2VzQGlldGYub3JnIFtt
YWlsdG86bXBscy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgZXh0IEVyaWMgT3Nib3Ju
ZSAoZW9zYm9ybmUpDQpTZW50OiBGcmlkYXksIEphbnVhcnkgMTQsIDIwMTEgMTI6NTIgQU0NClRv
OiBIdXViIHZhbiBIZWx2b29ydDsgbXBsc0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KU3Vi
amVjdDogUmU6IFttcGxzXSBbbXBscy10cF0gRHJhZnQ6IFJlc3BvbnNlIHRvIFVwZGF0ZWRkcmFm
dCBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtIFtSZWYwNDMuMDJdDQoNCg0KDQo+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IG1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRv
Om1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmDQo+IE9mIEh1dWIgdmFuIEhlbHZv
b3J0DQo+IFNlbnQ6IFRodXJzZGF5LCBKYW51YXJ5IDEzLCAyMDExIDU6MzMgUE0NCj4gVG86IG1w
bHNAaWV0Zi5vcmc7IG1wbHMtdHBAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFttcGxzLXRwXSBb
bXBsc10gRHJhZnQ6IFJlc3BvbnNlIHRvIFVwZGF0ZWQgZHJhZnQNCj4gUmVjb21tZW5kYXRpb24g
Ry50cG9hbSBbUmVmMDQzLjAyXQ0KPiANCj4gSGVsbG8gU3Rld2FydCwNCj4gDQo+IFlvdSBhc2tl
ZDoNCj4gDQo+ID4gRG9lcyBhbnlvbmUgZGlzYWdyZWUgd2l0aCB0aGUgc3RhdGVtZW50IHRoYXQg
RGF2aWQgbWFrZXM/DQo+IA0KPiBJIGRpc2FncmVlIHdpdGggdGhpcyBzdGF0ZW1lbnQgaW4gcmVs
YXRpb24gdG8gdGhpcyBsaWFpc29uLg0KPiANCj4gVGhlIGRyYWZ0IHJlY29tbWVuZGF0aW9uIEcu
dHBvYW0gdGhhdCB3YXMgc2VudCBmb3IgcmV2aWV3IGRvZXMgbm90IGNvbnRhaW4NCj4gYSByZWZl
cmVuY2UgdG8gZHJhZnQtYmhoIGF0IGFsbC4NCg0KVGhlIGxpYXNvbiBpcyBoZXJlOiBbaHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9saWFpc29uLzk4My9dDQphbmQgaXQgcmVmZXJlbmNlcyAi
TFMyMzMgLSBVcGRhdGVkIGRyYWZ0IFJlY29tbWVuZGF0aW9uIEcudHBvYW0gW1JlZiAwNDMuMDFd
IC0gcGRmIGJvZHkiIFtodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvY3VtZW50cy9MSUFJ
U09OL2ZpbGUxMTUxLnBkZl0NCndoaWNoIHNheXMNCg0KLS0tLQ0KQXQgdGhlIEJlcmxpbiBpbnRl
cmltIG1lZXRpbmcgb24gTVBMUy1UUCBmdXJ0aGVyIHdvcmsgd2FzIHVuZGVydGFrZW4gb24gdGhl
IGRldmVsb3BtZW50IG9mIHRoZSANCk9BTSBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtLsKgIFRoaXMg
dmVyc2lvbiB3YXMgZGV2ZWxvcGVkIHVzaW5nIGFsbCBvZiB0aGUgcmVsZXZhbnQgaW5wdXQgDQpk
b2N1bWVudHMgdG8gdGhlIG1lZXRpbmcgYW5kIGlzIGJhc2VkIG9uIGRyYWZ0LWJoaC1tcGxzLXRw
LW9hbS15MTczMS0wNi7CoCBXZSBpbnZpdGUgeW91ciANCmNvbW1lbnRzIG9uIHRoaXMgZG9jdW1l
bnQNCi0tLS0NCg0KV2hpbGUgeW91IGFyZSB0ZWNobmljYWxseSBjb3JyZWN0IHRoYXQgRy50cG9h
bSBkb2VzIG5vdCBpdHNlbGYgY29udGFpbiBhIHJlZmVyZW5jZSB0byBkcmFmdC1iaGgsIGhvdyBh
cmUgd2UgdG8gaW50ZXJwcmV0IHRoZSBsaWFzb24gc3RhdGVtZW50IHdoaWNoIGNsYWltcyBhIGNs
ZWFyIGxpbmVhZ2UgYmV0d2VlbiBkcmFmdC1iaGggYW5kIEcudHBvYW0/DQoNCj4gQWxzbyB0aGUg
c3RhdGVtZW50cyBhYm91dCB2YWxpZGl0eSBhbmQgY29weXJpZ2h0IGFyZSBpcnJlbGV2YW50Lg0K
PiANCg0KQ2FuIHdlIGFzc3VtZSB0aGF0IHlvdSBhZ3JlZSB0aGV5IGFyZSBjb3JyZWN0LCByZWdh
cmRsZXNzIG9mIHJlbGV2YW5jZT8NCg0KDQoNCmVyaWMNCg0KDQo+IFJlZ2FyZHMsIEh1dWIuDQo+
IA0KPiANCj4gPT09PT09PT09PT09PT0NCj4gPiBPbiAxMy8wMS8yMDExIDE3OjA5LCBEYXZpZCBT
aW5pY3JvcGUgd3JvdGU6DQo+ID4+IEl0IHNlZW1zIHRoYXQgcmVmZXJlbmNlIGFuZCB1c2Ugb2Yg
ZHJhZnQtYmhoIGlzIGluIHZpb2xhdGlvbiBvZiB0aGUNCj4gPj4gSVRVLVQgZXh0ZXJuYWwgY29v
cGVyYXRpb24gYWdyZWVtZW50ICJSZWZlcmVuY2luZyBBLjUgUXVhbGlmaWVkDQo+ID4+IE9yZ2Fu
aXphdGlvbnMiIHRleHQgZm91bmQgYXQNCj4gPj4gaHR0cDovL3d3dy5pdHUuaW50L2VuL0lUVS1U
L2V4dGNvb3AvUGFnZXMvc2RvLmFzcHggdW5kZXIgdGhlDQo+ID4+IFJlZmVyZW5jaW5nIElFVEYg
RG9jdW1lbnRzIGxpbmsuDQo+ID4+IEluIHBhcnRpY3VsYXIgY2xhdXNlIDEwIG9mIHRoaXMgZG9j
dW1lbnQgc3RhdGVzOiAoU2VlIDJuZCBzZW50ZW5jZS4pDQo+ID4+DQo+ID4+ICIxMCBPdGhlcjog
SWYgYSBzdHVkeSBncm91cCBkZWNpZGVzIHRvIG1ha2UgdGhlIHJlZmVyZW5jZSB0byBhbiBJRVRG
DQo+ID4+IFJGQywgdGhlIHJlZmVyZW5jZSBzaG91bGQgYWx3YXlzIGJlIG1hZGUgYnkgUkZDIG51
bWJlciAoYW5kIG5vdCBieQ0KPiA+PiBvdGhlciBkZXNpZ25hdGlvbnMgc3VjaCBhcyBTVEQsIEJD
UCwgZXRjLikuIFJlZmVyZW5jZXMgc2hvdWxkIG5vdCBiZQ0KPiA+PiBtYWRlIHRvIGRvY3VtZW50
cyByZWZlcnJlZCB0byBhcyAiSW50ZXJuZXQgRHJhZnRzIiBvciB0byBJRVRGIFJGQ3MNCj4gPj4g
Y2F0ZWdvcml6ZWQgYXMgSGlzdG9yaWMgb3IgRXhwZXJpbWVudGFsLiBOb3JtYXRpdmUgcmVmZXJl
bmNlcyBtdXN0DQo+ID4+IG9ubHkgYmUgbWFkZSB0byBJRVRGIFJGQ3MgdGhhdCBhcmUgU3RhbmRh
cmRzIFRyYWNrIG9yIHRvDQo+ID4+IEluZm9ybWF0aW9uYWwgUkZDcyB0aGF0IGhhdmUgSUVURiBj
b25zZW5zdXMuIg0KPiA+Pg0KPiA+PiBJcyB0aGlzIG5vdCBjb3JyZWN0PyBJZiBjb3JyZWN0LCBz
aG91bGRuJ3QgdGhpcyBhbHNvIGJlIHBvaW50ZWQgb3V0DQo+ID4+IGluIHRoZSBsaWFpc29uPw0K
PiA+PiBEYXZlDQo+ID4+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZy
b206IG1wbHMtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOm1wbHMtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmDQo+ID4+IE9mIFN0ZXdhcnQgQnJ5YW50DQo+ID4+IFNlbnQ6IFRodXJzZGF5LCBK
YW51YXJ5IDEzLCAyMDExIDExOjI3IEFNDQo+ID4+IFRvOiBtcGxzQGlldGYub3JnDQo+ID4+IFN1
YmplY3Q6IFJlOiBbbXBsc10gW21wbHMtdHBdIERyYWZ0OiBSZXNwb25zZSB0byBVcGRhdGVkIGRy
YWZ0DQo+ID4+IFJlY29tbWVuZGF0aW9uIEcudHBvYW0gW1JlZjA0My4wMl0NCj4gPj4NCj4gPj4g
RXhhY3RseSBCZW4uDQo+ID4+DQo+ID4+IFRoZSBMaWFpc29uIGlzIGxpc3Qgb2Ygc3RhdGVtZW50
cyBvZiByZWxldmFudCBmYWN0cywgYW5kIG5vbmUgb2YgdGhlDQo+ID4+IGNvbnRyYSBwb2ludHMg
ZGlzcHV0ZSB0aG9zZSBmYWN0cy4NCj4gPj4NCj4gPj4gU3Rld2FydA0KPiA+Pg0KPiA+PiBPbiAx
My8wMS8yMDExIDE1OjQxLCBCZW4gTml2ZW4tSmVua2lucyB3cm90ZToNCj4gPj4+IExhcnJ5LA0K
PiA+Pj4NCj4gPj4+IE9uIDEzIEphbiAyMDExLCBhdCAxNDo1NSwgTGFycnkgd3JvdGU6DQo+ID4+
Pg0KPiA+Pj4+IEhpLA0KPiA+Pj4+DQo+ID4+Pj4gSSBkb24ndCB0aGluayBpdCBpcyBwcm9wZXIg
dG8gc2VuZCB0aGUgTFMgdG8gSVRVLVQgYmVjYXVzZSB0aGUgdGV4dA0KPiA+Pj4+IGRvZXNuJ3Qg
cmVmbGVjdCB0aGUgcmVxdWlyZW1lbnQgZnJvbSBwcm92aWRlcnMuDQo+ID4+Pj4gQXBwYXJlbnRs
eSwgZHJhZnQtYmhoIGJhc2VkIE9BTSBpcyB0aGUgbW9zdCBtYXR1cmUgc29sdXRpb24NCj4gPj4+
PiBjdXJyZW50bHkuIEl0IGhhcyBiZWVuIHByb3ZlZCBieSBtb3JlIHRoYW4gMjAwLDAwMCBhcHBs
aWNhdGlvbnMgYW5kDQo+ID4+Pj4gaXMgc3VwcG9ydGVkIGJ5IGEgbG90IG9mIG9wZXJhdG9ycyBh
bmQgdmVuZG9ycy4NCj4gPj4+Pg0KPiA+Pj4gVGhhdCBtYXkgb3IgbWF5IG5vdCBiZSB0cnVlLCBi
dXQgZWl0aGVyIHdheSBpdCBpcyBpcnJlbGV2YW50IHRvIHRoZQ0KPiA+Pj4gbGlhaXNvbi4NCj4g
Pj4+DQo+ID4+PiBJVFUgbGlhaXNlZCBHLnRwb2FtIHRvIElFVEYuIFRoZSBsaWFpc29uIHJlc3Bv
bnNlIFN0ZXdhcnQgaGFzDQo+ID4+PiBkcmFmdGVkIHBvaW50cyBvdXQgdGhhdCBHLnRwb2FtIHVz
ZXMgdGVjaG5vbG9neSAoZHJhZnQtYmhoKSB0aGF0IGlzDQo+ID4+PiBub3QgZW5kb3JzZWQgYnkg
SUVURiBjb25zZW5zdXMgYW5kIHBvaW50cyB0byBzb21lIHJpc2tzIG9mIGRvaW5nIHNvLA0KPiA+
Pj4gaW5jbHVkaW5nIGJyZWFjaCBvZiBhIHByaW9yIElUVS1JRVRGIGFncmVlbWVudCBvbiBob3cg
dG8gcHJvZ3Jlc3MNCj4gPj4+IE1QTFMtVFAgZGV2ZWxvcG1lbnQuDQo+ID4+Pg0KPiA+Pj4gRXZl
cnl0aGluZyBpbiB0aGUgbGlhaXNvbiBpcyBmYWN0LiBXaGV0aGVyIGRyYWZ0LWJoaCBpcw0KPiA+
Pj4gZ29vZC9iYWQvdWdseSwgZGVwbG95ZWQsIHN1cHBvcnRlZCBieSBvcGVyYXRvcnMsIGV0Yy4g
aXMgaXJyZWxldmFudCwNCj4gPj4+IGl0IGlzIG5vdCBlbmRvcnNlZCBieSBJRVRGIGFzIGEgTVBM
Uy1UUCBPQU0gc29sdXRpb24gYW5kIGFsbCB0aGUNCj4gPj4+IGxpYWlzb24gZG9lcyBpcyBwb2lu
dCBvdXQgdGhhdCBmYWN0Lg0KPiA+Pj4NCj4gPj4+IEZXSVcgdGhpcyBpc24ndCB0aGUgZmlyc3Qg
dGltZSBhIGdyb3VwIG9mIG9wZXJhdG9ycyBoYXZlIGJyb3VnaHQgYQ0KPiA+Pj4gcHJvcG9zYWwg
dG8gSUVURiBvbmx5IHRvIGZpbmQgdGhhdCB0aGUgSUVURiBoYXMgZGVjaWRlZCB0byBkbw0KPiA+
Pj4gc29tZXRoaW5nIGVsc2UsIGFuZCBJJ20gc3VyZSBpdCB3b24ndCBiZSB0aGUgbGFzdC4NCj4g
Pj4+DQo+ID4+PiBCZW4NCj4gPj4+DQo+ID4+PiBQLlMuIGZvciBzb21lIHJlYXNvbiBlbWFpbCBj
aGFpbnMgcmVsYXRlZCB0byBkcmFmdC1iaGggcmVtaW5kIG1lIG9mDQo+ID4+PiB0aGlzIERpbGJl
cnQgY2FydG9vbiBodHRwOi8vd3d3LmRpbGJlcnQuY29tLzIwMTAtMTItMjIvDQo+ID4+Pg0KPiA+
Pj4NCj4gPj4+DQo+ID4+Pj4gQmVzdCByZWdhcmRzLA0KPiA+Pj4+DQo+ID4+Pj4gSGFuIExpDQo+
ID4+Pj4NCj4gPj4+PiAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqDQo+ID4+Pj4gKioNCj4gPj4+PiAqKioqDQo+ID4+Pj4g
SGFuIExpLCBQaC5EDQo+ID4+Pj4gQ2hpbmEgTW9iaWxlIFJlc2VhcmNoIEluc3RpdHV0ZQ0KPiA+
Pj4+IFVuaXQgMiwgMjggWHVhbnd1bWVueGkgQXZlLCBYdWFud3UgRGlzdHJpY3QsIEJlaWppbmcg
MTAwMDUzLCBDaGluYQ0KPiA+Pj4+IEZheDogKzg2IDEwIDYzNjAxMDg3DQo+ID4+Pj4gTU9CSUxF
OiAxMzUwMTA5MzM4NQ0KPiA+Pj4+ICoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCj4gPj4+PiAqKg0KPiA+Pj4+ICoqKioN
Cj4gPj4+Pg0KPiA+Pj4+DQo+ID4+Pj4gLS0tIDEx5bm0MeaciDEz5pel77yM5ZGo5ZubLA0KPiA+
Pj4+IHJ1aXF1YW4uamluZ0B0aWVzLml0dS5pbnQ8cnVpcXVhbi5qaW5nQHRpZXMuaXR1LmludD4N
Cj4gPj4+PiDlhpnpgZPvvJoNCj4gPj4+Pg0KPiA+Pj4+PiDlj5Hku7bkuro6IHJ1aXF1YW4uamlu
Z0B0aWVzLml0dS5pbnQ8cnVpcXVhbi5qaW5nQHRpZXMuaXR1LmludD4NCj4gPj4+Pj4g5Li76aKY
OiBSZTogW21wbHMtdHBdIFttcGxzXSBEcmFmdDogUmVzcG9uc2UgdG8gVXBkYXRlZCBkcmFmdA0K
PiA+Pj4+PiBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtIFtSZWYwNDMuMDJdDQo+ID4+Pj4+IOaUtuS7
tuS6ujogamluZ3JAdGllcy5pdHUuY2gNCj4gPj4+Pj4g5oqE6YCBOiBtcGxzLXRwQGlldGYub3Jn
DQo+ID4+Pj4+IOaXpeacnzogMjAxMeW5tDHmnIgxM+aXpSzlkajlm5ss5LiL5Y2INDowOQ0KPiA+
Pj4+PiBSZXNlbmQgdG8gbXBscy10cCBsaXN0Lg0KPiA+Pj4+Pg0KPiA+Pj4+PiBRdW90aW5nIGpp
bmdyQHRpZXMuaXR1LmNoOg0KPiA+Pj4+Pg0KPiA+Pj4+Pj4gSGkgU3Rld2FydCBCcnlhbnQsDQo+
ID4+Pj4+Pg0KPiA+Pj4+Pj4gSSBkb27igJl0IGFncmVlIHdpdGggdGhlIGN1cnJlbnQgTFMgdGV4
dC4NCj4gPj4+Pj4+DQo+ID4+Pj4+PiBDaGluYSBUZWxlY29tIHN1cHBvcnQgdGhlIHN0YW5kYXJk
aXphdGlvbiBvZiBZLjE3MzENCj4gPj4+Pj4gYmFzZWQgTVBMUy1UUCBPQU0gdG9vbHMNCj4gPj4+
Pj4+IGluDQo+ID4+Pj4+PiB0aGUgSVRVLVQgdG8gbWVldCB0aGUgdXJnZW50IGFuZCBpbmNyZWFz
aW5nDQo+ID4+Pj4+IHJlcXVpcmVtZW50cyBmb3IgUFROIGRlcGxveW1lbnQuDQo+ID4+Pj4+PiBJ
dOKAmXMgYSBtdWx0aS12ZW5kb3Igc3VwcG9ydGVkLCBpbnRlcm9wZXJhYmlsaXR5DQo+ID4+Pj4+
IGNlcnRpZmljYXRlZCBhbmQgZmVhc2libGUNCj4gPj4+Pj4+IHNvbHV0aW9uLiBJdCBoYWQgYmVl
biBzcGVjaWZpZWQgaW4gYm90aCBDQ1NBDQo+ID4+Pj4+IChDaGluYSBDb21tdW5pY2F0aW9ucyBT
dGFuZGFyZHMNCj4gPj4+Pj4+IEFzc29jaWF0aW9uKSBhbmQgQ2hpbmEgVGVsZWNvbeKAmXMgUFRO
IHN0YW5kYXJkIGFzIHRoZQ0KPiA+Pj4+PiBvbmx5IHN0YW5kYXJkIE9BTQ0KPiA+Pj4+Pj4gbWVj
aGFuaXNtLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gQmVzdCBSZWdh
cmRzDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gSmluZyBSdWlxdWFuDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4g
Q2hpbmHjgIBUZWxlY29tIEJlaWppbmcNCj4gPj4+Pj4gUmVzZWFyY2jjgIBJbnN0aXR1dGUNCj4g
Pj4+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQo+ID4+Pj4+IC0tDQo+ID4+Pj4+IC0tLS0tLS0tLS0NCj4gPj4+Pj4g
LS0NCj4gPj4+Pj4+IEZyb206IG1wbHMtYm91bmNlc0BpZXRmLm9yZw0KPiA+Pj4+PiBbbWFpbHRv
Om1wbHMtYm91bmNlc0BpZXRmLm9yZ10NCj4gPj4+Pj4gT24gQmVoYWxmIE9mDQo+ID4+Pj4+PiBT
dGV3YXJ0DQo+ID4+Pj4+PiBCcnlhbnQNCj4gPj4+Pj4+IFNlbnQ6IE1vbmRheSwgSmFudWFyeSAx
MCwgMjAxMSA2OjU3IFBNDQo+ID4+Pj4+PiBUbzogbXBsc0BpZXRmLm9yZw0KPiA+Pj4+Pj4gU3Vi
amVjdDogW21wbHNdIERyYWZ0OiBSZXNwb25zZSB0byBVcGRhdGVkIGRyYWZ0DQo+ID4+Pj4+IFJl
Y29tbWVuZGF0aW9uIEcudHBvYW0NCj4gPj4+Pj4+IFtSZWYwNDMuMDJdDQo+ID4+Pj4+Pg0KPiA+
Pj4+Pj4NCj4gPj4+Pj4+IEkgcHJvcG9zZSB0byBzZW5kIHRoZSBmb2xsb3dpbmcgTGlhaXNvbiBS
ZXNwb25zZSB0bw0KPiA+Pj4+PiB0aGUgSVRVLVQgb24gRnJpZGF5DQo+ID4+Pj4+PiAxNHRoIEph
bnVhcnkgYW5kIGFtIHBvc3RpbmcgaXQgdG8gdGhlIE1QTFMgV0cgbGlzdCBmb3INCj4gPj4+Pj4g
cmV2aWV3Lg0KPiA+Pj4+Pj4gPT09PT09PQ0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IFJlc3BvbnNlIHRv
IFVwZGF0ZWQgZHJhZnQgUmVjb21tZW5kYXRpb24gRy50cG9hbSBbUmVmDQo+ID4+Pj4+IDA0My4w
Ml0NCj4gPj4+Pj4+IEZyb206IElFVEYgTGlhaXNvbiB0byBJVFUtVCBvbiBNUExTIHN0YnJ5YW50
QGNpc2NvLmNvbQ0KPiA+Pj4+Pj4gVG86IHRzYnNnMTVAaXR1LmludCwNCj4gPj4+Pj4gZ3JlZy5q
b25lc0BpdHUuaW50LA0KPiA+Pj4+PiBoaXJvc2hpLm90YUBpdHUuaW50LA0KPiA+Pj4+PiBJQUJA
aWV0Zi5vcmcNCj4gPj4+Pj4+IENDOiBHcmVnIEpvbmVzLCBzd2FsbG93QGNpc2NvLmNvbSwNCj4g
Pj4+Pj4gbG9hQHBpLm51LCBwYWZAY2lzY28uY29tDQo+ID4+Pj4+PiBzdGJyeWFudEBjaXNjby5j
b20sDQo+ID4+Pj4+IGFkcmlhbi5mYXJyZWxAaHVhd2VpLmNvbSwNCj4gPj4+Pj4gbXBsc0BpZXRm
Lm9yZw0KPiA+Pj4+Pj4geW9pY2hpLm1hZWRhQHR0Yy5vci5qcCwNCj4gPj4+Pj4gc3RldmUudHJv
d2JyaWRnZUBhbGNhdGVsLWx1Y2VudC5jb20NCj4gPj4+Pj4NCj4gPj4+Pj4+IGdoYW5pLmFiYmFz
QGVyaWNzc29uLmNvbSwNCj4gPj4+Pj4gaGhlbHZvb3J0QGh1YXdlaS5jb20NCj4gPj4+Pj4NCj4g
Pj4+Pj4+IG1hbGNvbG0uYmV0dHNAenRlLmNvbS5jbiwNCj4gPj4+Pj4ga2FtLmxhbUBhbGNhdGVs
LWx1Y2VudC5jb20NCj4gPj4+Pj4NCj4gPj4+Pj4+IEZvciBBY3Rpb24NCj4gPj4+Pj4+DQo+ID4+
Pj4+PiBUaGUgTVBMUyBXb3JraW5nIEdyb3VwIG5vdGVzIHRoYXQgdGhpcyBkb2N1bWVudA0KPiA+
Pj4+PiBjb250YWlucyB0ZXh0IGRlc2NyaWJpbmcNCj4gPj4+Pj4+IE1QTFMtVFAgT0FNIHByb3Rv
Y29scyBub3QgZGVzaWduZWQgYW5kIHN0YW5kYXJkaXplZA0KPiA+Pj4+PiB1c2luZyB0aGUgSUVU
Rg0KPiA+Pj4+Pj4gU3RhbmRhcmRzIHByb2Nlc3MuIFNwZWNpZmljYWxseSBpdCB1c2VzIG1hdGVy
aWFsIGZyb20NCj4gPj4+Pj4+IGRyYWZ0LWJoaC1tcGxzLXRwLW9hbS15MTczMS0wNi4NCj4gPj4+
Pj4+DQo+ID4+Pj4+PiBXZSB3aXNoIHRvIGRyYXcgeW91ciBhdHRlbnRpb24gdG8gdGhlIHN0YXR1
cyBzZWN0aW9uDQo+ID4+Pj4+IG9mDQo+ID4+Pj4+PiBkcmFmdC1iaGgtbXBscy10cC1vYW0teTE3
MzEtMDYgd2hpY2ggc3RhdGVzOg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+ICJJbnRlcm5ldC1EcmFmdHMg
YXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYQ0KPiA+Pj4+PiBtYXhpbXVtIG9mIHNpeCBt
b250aHMNCj4gPj4+Pj4+IGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRl
ZCBieSBvdGhlcg0KPiA+Pj4+PiBkb2N1bWVudHMgYXQgYW55DQo+ID4+Pj4+PiB0aW1lLiBJdCBp
cyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMNCj4gPj4+Pj4gcmVmZXJl
bmNlIG1hdGVyaWFsDQo+ID4+Pj4+PiBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29y
ayBpbiBwcm9ncmVzcyIuDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gUGxlYXNlIGFsc28gbm90ZSB0aGF0
IHNpbmNlIHRoZSBkcmFmdCBmaWxlbmFtZSBzdGFydHMNCj4gPj4+Pj4gd2l0aCB0aGUgcHJlZml4
DQo+ID4+Pj4+PiBzdHJpbmcgImRyYWZ0LWJoaCIgdGhpcyBjbGVhcmx5IGlkZW50aWZpZXMgaXQg
dG8gdGhlDQo+ID4+Pj4+IHJlYWRlciBhcyBhDQo+ID4+Pj4+PiBkb2N1bWVudCBleHByZXNzaW5n
IHRoZSBwZXJzb25hbCB0ZWNobmljYWwgdmlld3Mgb2YNCj4gPj4+Pj4gdGhlIGF1dGhvcnMgYW5k
DQo+ID4+Pj4+PiBoZW5jZSBoZW5jZSBhcyBhIGRvY3VtZW50IHRoYXQgdGhhdCBkb2VzIG5vdCBo
YXZlIGFueQ0KPiA+Pj4+PiBhY2tub3dsZWRnZWQgbGV2ZWwNCj4gPj4+Pj4+IG9mIElFVEYgY29u
c2Vuc3VzLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IFNpbmNlIHRoZSB0ZXh0IG9mIGRyYWZ0IFJlY29t
bWVuZGF0aW9uIGZvciBHLnRwb2FtIGlzDQo+ID4+Pj4+IGJhc2VkIG9uIGFuDQo+ID4+Pj4+PiBN
UExTLVRQIE9BTSBwcm90b2NvbCBub3QgZGVzaWduZWQgd2l0aGluIHRoZSBJRVRGDQo+ID4+Pj4+
IFN0YW5kYXJkcyBQcm9jZXNzIHRoaXMNCj4gPj4+Pj4+IGlzIGEgYnJlYWNoIG9mIHRoZSBTRzE1
IGFncmVlbWVudCB3aXRoIHRoZSBJRVRGIGFzDQo+ID4+Pj4+IHB1Ymxpc2hlZCBpbiBSZXBvcnQN
Cj4gPj4+Pj4+IG9mIHRoZSBmaXJzdCBtZWV0aW5nIG9mIFdvcmtpbmcgUGFydHkgMy8xNSBUcmFu
c3BvcnQNCj4gPj4+Pj4gbmV0d29yayBzdHJ1Y3R1cmVzDQo+ID4+Pj4+PiAoMjAwOS0yMDEyKSAo
R2VuZXZhLCAxIOKAkyAxMiBEZWNlbWJlciAyMDA4KSB3aGljaCBjYW4NCj4gPj4+Pj4gYmUgZm91
bmQgYXQNCj4gPj4+Pj4+IGh0dHA6Ly93d3cuaXR1LmludC9tZC9UMDktU0cxNS1SLTAwMDQvZW4N
Cj4gPj4+Pj4+IFBsZWFzZSBjb25maXJtIHRoYXQgdGhlIElUVS1UIGludGVuZHMgdG8gY29udGlu
dWUgd2l0aA0KPiA+Pj4+PiB0aGUgam9pbnQgd29yayBvbg0KPiA+Pj4+Pj4gTVBMUy1UUCBhbmQg
dGhhdCB0aGUgSVRVLVQgd2lsbCBhbGlnbiB0aGlzDQo+ID4+Pj4+IHJlY29tbWVuZGF0aW9uIHdp
dGggdGhlIElFVEYNCj4gPj4+Pj4+IE1QTFMtVFAgT0FNIGRlc2lnbiBiZWZvcmUgYWR2YW5jaW5n
IHRoaXMgZG9jdW1lbnQNCj4gPj4+Pj4gdGhyb3VnaCB0aGUgSVRVLVQNCj4gPj4+Pj4+IHB1Ymxp
Y2F0aW9uIHByb2Nlc3MuDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gVGhlIE1QTFMgV29ya2luZyBHcm91
cCB3b3VsZCBhbHNvIGxpa2UgdG8gZHJhdyB0aGUNCj4gPj4+Pj4gYXR0ZW50aW9uIG9mIElUVS1U
DQo+ID4+Pj4+PiBTRzE1IHRvIHRoZSBJRVRGIGNvcHlyaWdodCBydWxlcy4gUGxlYXNlIHNlZQ0K
PiA+Pj4+Pj4gaHR0cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvL2FyY2hpdmUvSUVU
Ri1UcnVzdC1MaWNlbnNlLVANCj4gPj4+Pj4+IG9sDQo+ID4+Pj4+PiBpY3ktDQo+ID4+Pj4+PiAy
MDA5MTIyOC5odG0NCj4gPj4+Pj4+IGZvciBmdXJ0aGVyIGRldGFpbHMuDQo+ID4+Pj4+Pg0KPiA+
Pj4+Pj4gU2luY2UgdGhpcyBkcmFmdCBSZWNvbW1lbmRhdGlvbiBjb250YWlucyB0ZXh0IGluIHdo
aWNoDQo+ID4+Pj4+IHRoZSBJVFUtVCBTRzE1DQo+ID4+Pj4+PiBoYXMgcHJvcG9zZWQgbWFraW5n
IGNoYW5nZXMgdG8gSUVURiBwcm90b2NvbHMgd2l0aG91dA0KPiA+Pj4+PiB0aGUgYXBwcm92YWwg
b2YNCj4gPj4+Pj4+IHRoZSBJRVRGLCB0aGUgTVBMUyBXb3JraW5nIEdyb3VwIGhhdmUgcmVmZXJy
ZWQgdGhpcw0KPiA+Pj4+PiBsaWFpc29uIHRvIHRoZSBJQUINCj4gPj4+Pj4+IGZvciB0aGVpciBj
b25zaWRlcmF0aW9uLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gPT09
PT09PT09DQo+ID4+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPiA+Pj4+Pj4gbXBscyBtYWlsaW5nIGxpc3QNCj4gPj4+Pj4+IG1wbHNAaWV0Zi5v
cmcNCj4gPj4+Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0K
PiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4+PiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+Pj4+PiBtcGxzLXRwIG1h
aWxpbmcgbGlzdA0KPiA+Pj4+PiBtcGxzLXRwQGlldGYub3JnDQo+ID4+Pj4+IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscy10cA0KPiA+Pj4+Pg0KPiA+Pj4+DQo+ID4+
Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj4+
PiBtcGxzLXRwIG1haWxpbmcgbGlzdA0KPiA+Pj4+IG1wbHMtdHBAaWV0Zi5vcmcNCj4gPj4+PiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMtdHANCj4gPj4+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+PiBtcGxzIG1h
aWxpbmcgbGlzdA0KPiA+Pj4gbXBsc0BpZXRmLm9yZw0KPiA+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo+ID4+DQo+ID4+IC0tDQo+ID4+IEZvciBjb3Jwb3Jh
dGUgbGVnYWwgaW5mb3JtYXRpb24gZ28gdG86DQo+ID4+DQo+ID4+IGh0dHA6Ly93d3cuY2lzY28u
Y29tL3dlYi9hYm91dC9kb2luZ19idXNpbmVzcy9sZWdhbC9jcmkvaW5kZXguaHRtbA0KPiA+Pg0K
PiA+Pg0KPiA+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiA+PiBtcGxzIG1haWxpbmcgbGlzdA0KPiA+PiBtcGxzQGlldGYub3JnDQo+ID4+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0KPiA+DQo+ID4NCj4gDQo+IA0K
PiAtLQ0KPiAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKg0KPsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg
wqDCoMKgwqDCoMKgwqAg5oiR54ix5aSW54K55LiA5LiD5LiJ5LiADQo+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG1wbHMtdHAgbWFpbGluZyBsaXN0
DQo+IG1wbHMtdHBAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9tcGxzLXRwDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KbXBscyBtYWlsaW5nIGxpc3QNCm1wbHNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0K

From ietf@cdl.asgaard.org  Thu Jan 13 15:15:46 2011
Return-Path: <ietf@cdl.asgaard.org>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 689773A6C13 for <mpls-tp@core3.amsl.com>; Thu, 13 Jan 2011 15:15:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.583
X-Spam-Level: 
X-Spam-Status: No, score=-1.583 tagged_above=-999 required=5 tests=[AWL=-0.185, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, J_CHICKENPOX_25=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCuf4f2NR4V3 for <mpls-tp@core3.amsl.com>; Thu, 13 Jan 2011 15:15:44 -0800 (PST)
Received: from asgaard.org (ratatosk.asgaard.org [204.29.150.73]) by core3.amsl.com (Postfix) with ESMTP id 2C8643A6C11 for <mpls-tp@ietf.org>; Thu, 13 Jan 2011 15:15:44 -0800 (PST)
Received: from fenrir.asgaard.org (fenrir.asgaard.org [204.29.152.154]) by asgaard.org (Postfix) with ESMTP id 5D965A09594 for <mpls-tp@ietf.org>; Thu, 13 Jan 2011 23:18:05 +0000 (UTC)
From: Christopher LILJENSTOLPE <ietf@cdl.asgaard.org>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-157-973386196"
Date: Fri, 14 Jan 2011 10:18:02 +1100
In-Reply-To: <mailman.1527.1294960475.4689.mpls-tp@ietf.org>
To: mpls-tp@ietf.org
References: <mailman.1527.1294960475.4689.mpls-tp@ietf.org>
Message-Id: <501CD922-8C4A-49EC-B44A-DB6A57727CC5@cdl.asgaard.org>
Content-Transfer-Encoding: 7bit
X-Pgp-Agent: GPGMail 1.3.1
X-Mailer: Apple Mail (2.1082)
Subject: Re: [mpls-tp] [mpls] R: Re: Draft: Response to Updated draft	Recommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 23:15:46 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-157-973386196
Content-Type: multipart/alternative; boundary=Apple-Mail-156-973386127


--Apple-Mail-156-973386127
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On 14Jan2011, at 10.14, mpls-tp-owner@ietf.org wrote:

> Erminio,
>=20
> 	I was at the meeting, and I did not see anyone denied a chance =
to approach the mic.  I did see a pair of working group chairs struggle =
to keep a working group on the previously published and agreed upon =
agenda.  The fact that a group of individuals wanted to dramatically =
change the agenda at the beginning of the meeting would have denied the =
other groups who had scheduled time from their allotted segments.  =
Having worked in some SG's in the ITU-T as well, I don't believe that =
behavior would have been any more allowed in an ITU-T meeting, than an =
IETF one (if anything, the ITU-T process probably would have shut it =
down faster). =20
>=20
> 	Christopher
>=20
> On 14Jan2011, at 10.00, erminio.ottone_69@libero.it wrote:
>=20
>> You forget that ITU-T experts have not been allowed to speak at IETF =
79 and a=20
>> new trend of approving RFCs without resolving ITU-T have been =
started.
>>=20
>>> ----Messaggio originale----
>>> Da: nurit.sprecher@nsn.com
>>> Data: 13-gen-2011 13.54
>>> A: "ext HUANG Feng F"<Feng.f.Huang@alcatel-sbell.com.cn>, =
<stbryant@cisco.
>> com>, <mpls@ietf.org>
>>> Cc: <mpls-tp@ietf.org>
>>> Ogg: Re: [mpls-tp] [mpls] Draft: Response to Updated draft	=
Recommendation G.
>> tpoam[Ref043.02]
>>>=20
>>> Hi Feng,
>>> 	You say " HF> I can't image the meaning of cooperation is that =
ITU-T do=20
>> nothing and just obey IETF's process!"
>>> It seems that you are not familiar with the agreement on the joint =
work. The=20
>> ITU-T experts are called to contribute to (also by the SG15) to =
assist in the=20
>> development the development of the protocol in the IETF using the =
IETF standard=20
>> processes...
>>> Best regards,
>>> Nurit
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]=20
>>> Sent: Thursday, January 13, 2011 12:31 PM
>>> To: Sprecher,
>>> Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; mpls@ietf.org
>>> Cc: mpls-tp@ietf.org
>>> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam
>> [Ref043.02]
>>>=20
>>> Hi, Nurit,
>>> Please see in line.
>>> B.R.
>>> Feng
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) =
[mailto:nurit.sprecher@nsn.
>> com]=20
>>> Sent: 2011=E5=B9=B41=E6=9C=8813=E6=97=A5 17:45
>>> To: HUANG Feng F; stbryant@cisco.com; mpls@ietf.org
>>> Cc: mpls-tp@ietf.org
>>> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam
>> [Ref043.02]
>>>=20
>>> Hi Feng,
>>> I did not refer to specific solution, validity and acceptance of a =
solution,=20
>> so I cannot see to what you disagree and how your response fit to =
mine.=20
>>> If you think that you have a good solution which is proven and =
supported=20
>> please discuss it in the IETF and try to get support for it!=20
>>>=20
>>> HF> The solution has been submitted to ietf for 2 year!
>>>=20
>>> I would like the ITU-T to continue with its collaborative agreement =
with the=20
>> IETF and ensure that the development of the protocol is done as =
agreed and=20
>> supported by SG15 using the IETF processes.
>>>=20
>>> HF> I can't image the meaning of cooperation is that ITU-T do =
nothing and=20
>> just obey IETF's process!
>>>=20
>>> I will support a single global solution interoperable solution =
(whatever the=20
>> solution is).=20
>>> Best regards,
>>> Nurit
>>>=20
>>> -----Original Message-----
>>> From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
>>> Sent: Thursday, January 13, 2011 11:35 AM
>>> To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; =
mpls@ietf.
>> org
>>> Cc: mpls-tp@ietf.org
>>> Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam
>> [Ref043.02]
>>>=20
>>> Hi,Nurit,
>>> I can't agree with you.
>>> Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet =
Transport=20
>> Network by many applications and public demo and it has many =
supporters. I am=20
>> wondering why  this solutions is not  standardized in ietf?=20
>>> Further more,  I really don't agree with your last sentence, this=20
>> solution is asked by customers in Industry, you can see at least 7 =
providers in=20
>> global support this solution.
>>>=20
>>> B.R.
>>> Feng
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of=20
>> Sprecher, Nurit (NSN - IL/Hod HaSharon)
>>> Sent: 2011=E5=B9=B41=E6=9C=8813=E6=97=A5 16:18
>>> To: stbryant@cisco.com; mpls@ietf.org
>>> Subject: Re: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam
>> [Ref043.02]
>>>=20
>>> Hi,
>>> I support the proposal.
>>> We have a cooperative agreement with the ITU-T concerning the work =
on MPLS-
>> TP.=20
>>> The agreement recognizes the design authority of the IETF for MPLS =
and it is=20
>> agreed that the development of the protocol should be done in the =
IETF using=20
>> the IETF processes. The ITU-T should not take any uncoordinated =
action in the=20
>> development of the MPLS_TP protocol.=20
>>> We would appreciate if the ITU-T continues (as it committed to) with =
the=20
>> collaborative work with the IETF on MPLS_TP and contributes from its =
expertise=20
>> to the development of the protocol using the IETF processes.=20
>>> We would also not like to see two competing solutions which may =
confuse the=20
>> Industry, bloat operational and capital expenses and badly affect the =
end=20
>> customer.=20
>>> Best regards,
>>> Nurit
>>>=20
>>> -----Original Message-----
>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of ext=20
>> Stewart Bryant
>>> Sent: Monday, January 10, 2011 12:57 PM
>>> To: mpls@ietf.org
>>> Subject: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam=20
>> [Ref043.02]
>>>=20
>>> I propose to send the following Liaison Response to the ITU-T on =
Friday 14th=20
>> January and am posting it to the MPLS WG list for review.
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D
>>>=20
>>> Response to Updated draft Recommendation G.tpoam [Ref 043.02]
>>>=20
>>> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>>> To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, =
IAB@ietf.org
>>> CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com =
stbryant@cisco.
>> com, adrian.farrel@huawei.com, mpls@ietf.org yoichi.maeda@ttc.or.jp, =
steve.
>> trowbridge@alcatel-lucent.com
>>> ghani.abbas@ericsson.com, hhelvoort@huawei.com =
malcolm.betts@zte.com.cn, kam.
>> lam@alcatel-lucent.com
>>>=20
>>> For Action
>>>=20
>>> The MPLS Working Group notes that this document contains text =
describing
>>>=20
>>> MPLS-TP OAM protocols not designed and standardized using the IETF =
Standards=20
>> process. Specifically it uses material from =
draft-bhh-mpls-tp-oam-y1731-06.
>>>=20
>>> We wish to draw your attention to the status section of
>>> draft-bhh-mpls-tp-oam-y1731-06 which states:
>>>=20
>>> "Internet-Drafts are draft documents valid for a maximum of six =
months and=20
>> may be updated, replaced, or obsoleted by other documents at any =
time. It is=20
>> inappropriate to use Internet-Drafts as reference material or to cite =
them=20
>> other than as "work in progress".
>>>=20
>>> Please also note that since the draft filename starts with the =
prefix string=20
>> "draft-bhh" this clearly identifies it to the reader as a document =
expressing=20
>> the personal technical views of the authors and hence hence as a =
document that=20
>> that does not have any acknowledged level
>>>=20
>>> of IETF consensus.
>>>=20
>>> Since the text of draft Recommendation for G.tpoam is based on an =
MPLS-TP OAM=20
>> protocol not designed within the IETF Standards Process this
>>>=20
>>> is a breach of the SG15 agreement with the IETF as published in =
Report of the=20
>> first meeting of Working Party 3/15 Transport network structures
>>> (2009-2012) (Geneva, 1 - 12 December 2008) which can be found at =
http://www.
>> itu.int/md/T09-SG15-R-0004/en
>>>=20
>>> Please confirm that the ITU-T intends to continue with the joint =
work on
>>>=20
>>> MPLS-TP and that the ITU-T will align this recommendation with the =
IETF MPLS-
>> TP OAM design before advancing this document through the ITU-T =
publication=20
>> process.
>>>=20
>>> The MPLS Working Group would also like to draw the attention of =
ITU-T
>>> SG15 to the IETF copyright rules. Please see
>>> =
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
>>> 0091228.htm
>>> for further details.
>>>=20
>>> Since this draft Recommendation contains text in which the ITU-T =
SG15 has=20
>> proposed making changes to IETF protocols without the approval of the =
IETF, the=20
>> MPLS Working Group have referred this liaison to the IAB for their=20
>> consideration.
>>>=20
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D

---
=E6=9D=8E=E6=9F=AF=E7=9D=BF
Check my PGP key here:
https://www.asgaard.org/~cdl/cdl.asc


--Apple-Mail-156-973386127
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 14Jan2011, at 10.14, <a =
href=3D"mailto:mpls-tp-owner@ietf.org">mpls-tp-owner@ietf.org</a> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">Erminio,<br><br><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>I was at the meeting, and I did not see anyone denied a =
chance to approach the mic. &nbsp;I did see a pair of working group =
chairs struggle to keep a working group on the previously published and =
agreed upon agenda. &nbsp;The fact that a group of individuals wanted to =
dramatically change the agenda at the beginning of the meeting would =
have denied the other groups who had scheduled time from their allotted =
segments. &nbsp;Having worked in some SG's in the ITU-T as well, I don't =
believe that behavior would have been any more allowed in an ITU-T =
meeting, than an IETF one (if anything, the ITU-T process probably would =
have shut it down faster). &nbsp;<br><br><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>Christopher<br><br>On 14Jan2011, =
at 10.00,<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_69@libero.it</a=
><span =
class=3D"Apple-converted-space">&nbsp;</span>wrote:<br><br><blockquote =
type=3D"cite">You forget that ITU-T experts have not been allowed to =
speak at IETF 79 and a<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">new trend of approving RFCs without resolving ITU-T have =
been started.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">----Messaggio =
originale----<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Da:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</a><br></blo=
ckquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Data: 13-gen-2011 =
13.54<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">A: "ext HUANG Feng F"&lt;<a =
href=3D"mailto:Feng.f.Huang@alcatel-sbell.com.cn">Feng.f.Huang@alcatel-sbe=
ll.com.cn</a>&gt;, =
&lt;stbryant@cisco.<br></blockquote></blockquote><blockquote =
type=3D"cite">com&gt;, &lt;<a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br></blockquote><block=
quote type=3D"cite"><blockquote type=3D"cite">Cc: &lt;<a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>&gt;<br></blockquote>=
</blockquote><blockquote type=3D"cite"><blockquote type=3D"cite">Ogg: =
Re: [mpls-tp] [mpls] Draft: Response to Updated draft<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>Recommendation G.<br></blockquote></blockquote><blockquote =
type=3D"cite">tpoam[Ref043.02]<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Hi =
Feng,<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">	</span>You say " HF&gt; I can't image the meaning of cooperation =
is that ITU-T do<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">nothing and just obey IETF's =
process!"<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">It seems that you are not familiar with the agreement on =
the joint work. The<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">ITU-T experts are called to contribute to =
(also by the SG15) to assist in the<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">development the development of the protocol in the IETF =
using the IETF standard<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">processes...<br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Best =
regards,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Nurit<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">From: ext HUANG Feng F =
[mailto:Feng.f.Huang@alcatel-sbell.com.cn]<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite"><blockquote type=3D"cite">Sent: Thursday, =
January 13, 2011 12:31 PM<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">To: =
Sprecher,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Nurit (NSN - IL/Hod =
HaSharon);<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br></blockquote></bl=
ockquote><blockquote type=3D"cite"><blockquote type=3D"cite">Subject: =
RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam<br></blockquote></blockquote><blockquote =
type=3D"cite">[Ref043.02]<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Hi, =
Nurit,<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Please see in =
line.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">B.R.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Feng<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">From: Sprecher, Nurit (NSN - =
IL/Hod HaSharon) =
[mailto:nurit.sprecher@nsn.<br></blockquote></blockquote><blockquote =
type=3D"cite">com]<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Sent: 2011=E5=B9=B41=E6=9C=8813=E6=
=97=A5 17:45<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">To: HUANG Feng F;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br></blockquote></bl=
ockquote><blockquote type=3D"cite"><blockquote type=3D"cite">Subject: =
RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam<br></blockquote></blockquote><blockquote =
type=3D"cite">[Ref043.02]<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Hi =
Feng,<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">I did not refer to specific solution, validity and =
acceptance of a solution,<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">so I cannot see to what you disagree and how =
your response fit to mine.<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">If you think that you have a =
good solution which is proven and supported<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">please discuss it in the IETF and try to get =
support for it!<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">HF&gt; The solution has been =
submitted to ietf for 2 year!<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I would like the ITU-T to =
continue with its collaborative agreement with the<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">IETF and ensure that the development of the =
protocol is done as agreed and<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">supported by SG15 using the IETF =
processes.<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">HF&gt; I can't image the meaning =
of cooperation is that ITU-T do nothing and<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">just obey IETF's =
process!<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I will support a single global =
solution interoperable solution (whatever the<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">solution is).<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Best =
regards,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Nurit<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">From: ext HUANG Feng F =
[mailto:Feng.f.Huang@alcatel-sbell.com.cn]<br></blockquote></blockquote><b=
lockquote type=3D"cite"><blockquote type=3D"cite">Sent: Thursday, =
January 13, 2011 11:35 AM<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">To: Sprecher, Nurit (NSN - =
IL/Hod HaSharon);<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>; =
mpls@ietf.<br></blockquote></blockquote><blockquote =
type=3D"cite">org<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Cc:<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br></blockquote></bl=
ockquote><blockquote type=3D"cite"><blockquote type=3D"cite">Subject: =
RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam<br></blockquote></blockquote><blockquote =
type=3D"cite">[Ref043.02]<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Hi,Nurit,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I can't agree with =
you.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Solution of GACH+Y.1731 in G.tpoam is proven work well in =
Packet Transport<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">Network by many applications and public demo =
and it has many supporters. I am<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">wondering why &nbsp;this solutions is not =
&nbsp;standardized in ietf?<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Further more, &nbsp;I really =
don't agree with your last sentence, this<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">solution is asked by customers in Industry, =
you can see at least 7 providers in<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">global support this solution.<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">B.R.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Feng<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">From:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:mpls-bounces@ietf.org=
] On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">Sprecher, Nurit (NSN - IL/Hod =
HaSharon)<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Sent: 2011=E5=B9=B41=E6=9C=8813=E6=97=A5 =
16:18<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">To:<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite">Subject: Re: =
[mpls] Draft: Response to Updated draft Recommendation =
G.tpoam<br></blockquote></blockquote><blockquote =
type=3D"cite">[Ref043.02]<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Hi,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I support the =
proposal.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">We have a cooperative agreement =
with the ITU-T concerning the work on =
MPLS-<br></blockquote></blockquote><blockquote type=3D"cite">TP.<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The agreement recognizes the =
design authority of the IETF for MPLS and it is<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">agreed that the development of the protocol =
should be done in the IETF using<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">the IETF processes. The ITU-T should not take any =
uncoordinated action in the<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">development of the MPLS_TP protocol.<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">We would appreciate if the ITU-T =
continues (as it committed to) with the<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">collaborative work with the IETF on MPLS_TP =
and contributes from its expertise<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">to the development of the protocol using the IETF =
processes.<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">We would also not like to see =
two competing solutions which may confuse the<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">Industry, bloat operational and capital =
expenses and badly affect the end<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">customer.<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Best =
regards,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Nurit<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">From:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:mpls-bounces@ietf.org=
] On Behalf Of ext<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">Stewart Bryant<br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Sent: Monday, January 10, 2011 =
12:57 PM<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">To:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite">Subject: [mpls] =
Draft: Response to Updated draft Recommendation G.tpoam<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">[Ref043.02]<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I propose to send the following =
Liaison Response to the ITU-T on Friday 14th<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">January and am posting it to the MPLS WG list =
for review.<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">=3D=3D=3D=3D=3D=3D=3D<br></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Response to Updated draft =
Recommendation G.tpoam [Ref =
043.02]<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">From: IETF Liaison to ITU-T on =
MPLS<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a><br></blockquote>=
</blockquote><blockquote type=3D"cite"><blockquote type=3D"cite">To:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tsbsg15@itu.int">tsbsg15@itu.int</a>,<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:greg.jones@itu.int">greg.jones@itu.int</a>,<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:hiroshi.ota@itu.int">hiroshi.ota@itu.int</a>,<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:IAB@ietf.org">IAB@ietf.org</a><br></blockquote></blockquote=
><blockquote type=3D"cite"><blockquote type=3D"cite">CC: Greg =
Jones,<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:swallow@cisco.com">swallow@cisco.com</a>,<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:loa@pi.nu">loa@pi.nu</a>,<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:paf@cisco.com">paf@cisco.com</a><span =
class=3D"Apple-converted-space">&nbsp;</span>stbryant@cisco.<br></blockquo=
te></blockquote><blockquote type=3D"cite">com,<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:adrian.farrel@huawei.com">adrian.farrel@huawei.com</a>,<spa=
n class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:yoichi.maeda@ttc.or.jp">yoichi.maeda@ttc.or.jp</a>, =
steve.<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:trowbridge@alcatel-lucent.com">trowbridge@alcatel-lucent.co=
m</a><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"mailto:ghani.abbas@ericsson.com">ghani.abbas@ericsson.com</a>,<spa=
n class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:hhelvoort@huawei.com">hhelvoort@huawei.com</a><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:malcolm.betts@zte.com.cn">malcolm.betts@zte.com.cn</a>, =
kam.<br></blockquote></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:lam@alcatel-lucent.com">lam@alcatel-lucent.com</a><br></blo=
ckquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">For =
Action<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The MPLS Working Group notes =
that this document contains text =
describing<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">MPLS-TP OAM protocols not =
designed and standardized using the IETF Standards<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">process. Specifically it uses material from =
draft-bhh-mpls-tp-oam-y1731-06.<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">We wish to draw your attention =
to the status section of<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">draft-bhh-mpls-tp-oam-y1731-06 =
which states:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">"Internet-Drafts are draft =
documents valid for a maximum of six months and<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">may be updated, replaced, or obsoleted by =
other documents at any time. It is<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">inappropriate to use Internet-Drafts as reference material =
or to cite them<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">other than as "work in =
progress".<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Please also note that since the =
draft filename starts with the prefix string<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">"draft-bhh" this clearly identifies it to the =
reader as a document expressing<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">the personal technical views of the authors and hence =
hence as a document that<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">that does not have any acknowledged =
level<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">of IETF =
consensus.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Since the text of draft =
Recommendation for G.tpoam is based on an MPLS-TP OAM<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">protocol not designed within the IETF =
Standards Process this<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">is a breach of the SG15 =
agreement with the IETF as published in Report of the<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">first meeting of Working Party 3/15 Transport =
network structures<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">(2009-2012) (Geneva, 1 - 12 December 2008) which can be =
found at<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www/">http://www</a>.<br></blockquote></blockquote><blockqu=
ote =
type=3D"cite">itu.int/md/T09-SG15-R-0004/en<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Please confirm that the ITU-T =
intends to continue with the joint work =
on<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">MPLS-TP and that the ITU-T will =
align this recommendation with the IETF =
MPLS-<br></blockquote></blockquote><blockquote type=3D"cite">TP OAM =
design before advancing this document through the ITU-T publication<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">process.<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The MPLS Working Group would =
also like to draw the attention of =
ITU-T<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">SG15 to the IETF copyright rules. Please =
see<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Po=
licy-2">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Po=
licy-2</a><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">0091228.htm<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">for further =
details.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Since this draft Recommendation =
contains text in which the ITU-T SG15 has<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote></blockquote=
><blockquote type=3D"cite">proposed making changes to IETF protocols =
without the approval of the IETF, the<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">MPLS Working Group have referred this liaison to the IAB =
for their<span =
class=3D"Apple-converted-space">&nbsp;</span><br></blockquote><blockquote =
type=3D"cite">consideration.<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">=3D=3D=3D=3D=3D=3D=3D=3D=3D</blockquote></blockquote></span>=
</blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
"><div>---</div><div>=E6=9D=8E=E6=9F=AF=E7=9D=BF<br>Check my PGP key =
here:<br><font class=3D"Apple-style-span" color=3D"#144FAE"><span =
class=3D"Apple-style-span" style=3D"text-decoration: underline; "><a =
href=3D"https://www.asgaard.org/~cdl/cdl.asc">https://www.asgaard.org/~cdl=
/cdl.asc</a></span></font></div></div></div></div></div></div></span></div=
></span></span>
</div>

<br></body></html>=

--Apple-Mail-156-973386127--

--Apple-Mail-157-973386196
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJNL4gqAAoJEGmx2Mt/+Iw/htcH/jtnKhtAyAftBoOu8G1iqxZc
ugJ4uTwFPNkNXfnMQ/roUiDVyrcQDLZKI0P4XH7RdUgWSa9YB2562tq2g23JF/pz
TItCGSr6mt9s9gwVCTqP07FdkzAgo/B5i3/tWqPavNM5wP5VGkbb9vS9BRnTqBbQ
TAHqxraa3OkiTzWzZH5zKOszzFO2kfSHYDDE+68jBnHJQ+RSYgKFvnqr60IVAGdM
V9bKnMIoMznlcnWWYCD5DL84/rILWFBO8uzaKfaYyvdQtt5BBDMJrMBsQzh3Qb0i
MrfecLm3jIyrPszM8zahh3BauIb/q0siXSNHdvEknKxyBZ0MI4u7m41+gIqd3BI=
=Bb+m
-----END PGP SIGNATURE-----

--Apple-Mail-157-973386196--

From tochio@jp.fujitsu.com  Thu Jan 13 15:35:18 2011
Return-Path: <tochio@jp.fujitsu.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A57EC3A6C13; Thu, 13 Jan 2011 15:35:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.79
X-Spam-Level: 
X-Spam-Status: No, score=-99.79 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TReVoq9-T6z7; Thu, 13 Jan 2011 15:35:16 -0800 (PST)
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by core3.amsl.com (Postfix) with ESMTP id F0EAB3A6872; Thu, 13 Jan 2011 15:35:15 -0800 (PST)
Received: from m1.gw.fujitsu.co.jp (unknown [10.0.50.71]) by fgwmail7.fujitsu.co.jp (Postfix) with ESMTP id A2D823EE0AE; Fri, 14 Jan 2011 08:37:39 +0900 (JST)
Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 8426345DE55; Fri, 14 Jan 2011 08:37:39 +0900 (JST)
Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 6E83345DE54; Fri, 14 Jan 2011 08:37:39 +0900 (JST)
Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 639671DB804A; Fri, 14 Jan 2011 08:37:39 +0900 (JST)
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 31E4B1DB804B; Fri, 14 Jan 2011 08:37:39 +0900 (JST)
Received: from vs.kawasaki.flab.fujitsu.co.jp (vs.kawasaki.flab.fujitsu.co.jp [10.25.192.38]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/100813-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id p0DNbdXo018157;  Fri, 14 Jan 2011 08:37:39 +0900 (JST)
X-AuditID: 0a19c026-00000008000001f8-95-4d2f8cc27d74
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vs.kawasaki.flab.fujitsu.co.jp (Symantec Mail Security) with ESMTP id C55D12923D; Fri, 14 Jan 2011 08:37:38 +0900 (JST)
Received: from [127.0.0.1] (dhcp98.dream.flab.fujitsu.co.jp [10.25.144.157]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/100813-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id p0DNbcqs018154;  Fri, 14 Jan 2011 08:37:38 +0900 (JST)
X-SecurityPolicyCheck: OK by SHieldMailChecker v1.5.1
Message-ID: <4D2F8CA4.40402@jp.fujitsu.com>
Date: Fri, 14 Jan 2011 08:37:08 +0900
From: Yuji Tochio <tochio@jp.fujitsu.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
References: <526321.56478.qm@web15605.mail.cnb.yahoo.com>	<EC7945C9-3C51-42A1-8CA8-692A94B28F2C@niven-jenkins.co.uk>	<4D2F27F1.1070209@cisco.com>	<6873FACCBB5DDD4D88AABD78A8E483A468CE4D0311@EUSAACMS0703.eamcs.ericsson.se><4D2F47F9.8040701@cisco.com><4D2F7D8E.9040505@gmail.com>	<D29E470202D67745B61059870F433B54040D8FB2@XMB-RCD-202.cisco.com> <077E41CFFD002C4CAB7DFA4386A532640332E318@DEMUEXC014.nsn-intra.net>
In-Reply-To: <077E41CFFD002C4CAB7DFA4386A532640332E318@DEMUEXC014.nsn-intra.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updateddraft	Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 23:35:18 -0000

Nurit,

You should not discuss on the report of ITU-T interim meeting on
this thread that is for the reviewing LS to ITU-T since the report
was not sent as the part of LS233 from ITU-T.

And it is noted that drafts had been developed using all of the relevant
the input documents to the meeting as well. LSs from ITU-T state
this point as well.

Regards,
Yuji



(2011/01/14 8:12), Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:
> Huub,
> I would also recommend you to read the report of the rapporteurs of Q9, Q10, Q12 and Q14 from the Berlin meeting.
> The report explicitly says that work was undertaken on the development of the OAM protocol G.tpoam, G.8121 and G.8151. The drafts of these documents are based on draft-bhh-mpls-tp-oam-y1731-06.
> Best regards,
> Nurit
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of ext Eric Osborne (eosborne)
> Sent: Friday, January 14, 2011 12:52 AM
> To: Huub van Helvoort; mpls@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [mpls-tp] Draft: Response to Updateddraft Recommendation G.tpoam [Ref043.02]
>
>
>
>> -----Original Message-----
>> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
>> Of Huub van Helvoort
>> Sent: Thursday, January 13, 2011 5:33 PM
>> To: mpls@ietf.org; mpls-tp@ietf.org
>> Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft
>> Recommendation G.tpoam [Ref043.02]
>>
>> Hello Stewart,
>>
>> You asked:
>>
>>> Does anyone disagree with the statement that David makes?
>> I disagree with this statement in relation to this liaison.
>>
>> The draft recommendation G.tpoam that was sent for review does not contain
>> a reference to draft-bhh at all.
> The liason is here: [https://datatracker.ietf.org/liaison/983/]
> and it references "LS233 - Updated draft Recommendation G.tpoam [Ref 043.01] - pdf body" [https://datatracker.ietf.org/documents/LIAISON/file1151.pdf]
> which says
>
> ----
> At the Berlin interim meeting on MPLS-TP further work was undertaken on the development of the
> OAM Recommendation G.tpoam.  This version was developed using all of the relevant input
> documents to the meeting and is based on draft-bhh-mpls-tp-oam-y1731-06.  We invite your
> comments on this document
> ----
>
> While you are technically correct that G.tpoam does not itself contain a reference to draft-bhh, how are we to interpret the liason statement which claims a clear lineage between draft-bhh and G.tpoam?
>
>> Also the statements about validity and copyright are irrelevant.
>>
> Can we assume that you agree they are correct, regardless of relevance?
>
>
>
> eric
>
>
>> Regards, Huub.
>>
>>
>> ==============
>>> On 13/01/2011 17:09, David Sinicrope wrote:
>>>> It seems that reference and use of draft-bhh is in violation of the
>>>> ITU-T external cooperation agreement "Referencing A.5 Qualified
>>>> Organizations" text found at
>>>> http://www.itu.int/en/ITU-T/extcoop/Pages/sdo.aspx under the
>>>> Referencing IETF Documents link.
>>>> In particular clause 10 of this document states: (See 2nd sentence.)
>>>>
>>>> "10 Other: If a study group decides to make the reference to an IETF
>>>> RFC, the reference should always be made by RFC number (and not by
>>>> other designations such as STD, BCP, etc.). References should not be
>>>> made to documents referred to as "Internet Drafts" or to IETF RFCs
>>>> categorized as Historic or Experimental. Normative references must
>>>> only be made to IETF RFCs that are Standards Track or to
>>>> Informational RFCs that have IETF consensus."
>>>>
>>>> Is this not correct? If correct, shouldn't this also be pointed out
>>>> in the liaison?
>>>> Dave
>>>>
>>>> -----Original Message-----
>>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>>>> Of Stewart Bryant
>>>> Sent: Thursday, January 13, 2011 11:27 AM
>>>> To: mpls@ietf.org
>>>> Subject: Re: [mpls] [mpls-tp] Draft: Response to Updated draft
>>>> Recommendation G.tpoam [Ref043.02]
>>>>
>>>> Exactly Ben.
>>>>
>>>> The Liaison is list of statements of relevant facts, and none of the
>>>> contra points dispute those facts.
>>>>
>>>> Stewart
>>>>
>>>> On 13/01/2011 15:41, Ben Niven-Jenkins wrote:
>>>>> Larry,
>>>>>
>>>>> On 13 Jan 2011, at 14:55, Larry wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I don't think it is proper to send the LS to ITU-T because the text
>>>>>> doesn't reflect the requirement from providers.
>>>>>> Apparently, draft-bhh based OAM is the most mature solution
>>>>>> currently. It has been proved by more than 200,000 applications and
>>>>>> is supported by a lot of operators and vendors.
>>>>>>
>>>>> That may or may not be true, but either way it is irrelevant to the
>>>>> liaison.
>>>>>
>>>>> ITU liaised G.tpoam to IETF. The liaison response Stewart has
>>>>> drafted points out that G.tpoam uses technology (draft-bhh) that is
>>>>> not endorsed by IETF consensus and points to some risks of doing so,
>>>>> including breach of a prior ITU-IETF agreement on how to progress
>>>>> MPLS-TP development.
>>>>>
>>>>> Everything in the liaison is fact. Whether draft-bhh is
>>>>> good/bad/ugly, deployed, supported by operators, etc. is irrelevant,
>>>>> it is not endorsed by IETF as a MPLS-TP OAM solution and all the
>>>>> liaison does is point out that fact.
>>>>>
>>>>> FWIW this isn't the first time a group of operators have brought a
>>>>> proposal to IETF only to find that the IETF has decided to do
>>>>> something else, and I'm sure it won't be the last.
>>>>>
>>>>> Ben
>>>>>
>>>>> P.S. for some reason email chains related to draft-bhh remind me of
>>>>> this Dilbert cartoon http://www.dilbert.com/2010-12-22/
>>>>>
>>>>>
>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Han Li
>>>>>>
>>>>>> *******************************************************************
>>>>>> **
>>>>>> ****
>>>>>> Han Li, Ph.D
>>>>>> China Mobile Research Institute
>>>>>> Unit 2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China
>>>>>> Fax: +86 10 63601087
>>>>>> MOBILE: 13501093385
>>>>>> *******************************************************************
>>>>>> **
>>>>>> ****
>>>>>>
>>>>>>
>>>>>> --- 11年1月13日，周四,
>>>>>> ruiquan.jing@ties.itu.int<ruiquan.jing@ties.itu.int>
>>>>>> 写道：
>>>>>>
>>>>>>> 发件人: ruiquan.jing@ties.itu.int<ruiquan.jing@ties.itu.int>
>>>>>>> 主题: Re: [mpls-tp] [mpls] Draft: Response to Updated draft
>>>>>>> Recommendation G.tpoam [Ref043.02]
>>>>>>> 收件人: jingr@ties.itu.ch
>>>>>>> 抄送: mpls-tp@ietf.org
>>>>>>> 日期: 2011年1月13日,周四,下午4:09
>>>>>>> Resend to mpls-tp list.
>>>>>>>
>>>>>>> Quoting jingr@ties.itu.ch:
>>>>>>>
>>>>>>>> Hi Stewart Bryant,
>>>>>>>>
>>>>>>>> I don’t agree with the current LS text.
>>>>>>>>
>>>>>>>> China Telecom support the standardization of Y.1731
>>>>>>> based MPLS-TP OAM tools
>>>>>>>> in
>>>>>>>> the ITU-T to meet the urgent and increasing
>>>>>>> requirements for PTN deployment.
>>>>>>>> It’s a multi-vendor supported, interoperability
>>>>>>> certificated and feasible
>>>>>>>> solution. It had been specified in both CCSA
>>>>>>> (China Communications Standards
>>>>>>>> Association) and China Telecom’s PTN standard as the
>>>>>>> only standard OAM
>>>>>>>> mechanism.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Best Regards
>>>>>>>>
>>>>>>>> Jing Ruiquan
>>>>>>>>
>>>>>>>> China　Telecom Beijing
>>>>>>> Research　Institute
>>>>>>> ------------------------------------------------------------------
>>>>>>> --
>>>>>>> ----------
>>>>>>> --
>>>>>>>> From: mpls-bounces@ietf.org
>>>>>>> [mailto:mpls-bounces@ietf.org]
>>>>>>> On Behalf Of
>>>>>>>> Stewart
>>>>>>>> Bryant
>>>>>>>> Sent: Monday, January 10, 2011 6:57 PM
>>>>>>>> To: mpls@ietf.org
>>>>>>>> Subject: [mpls] Draft: Response to Updated draft
>>>>>>> Recommendation G.tpoam
>>>>>>>> [Ref043.02]
>>>>>>>>
>>>>>>>>
>>>>>>>> I propose to send the following Liaison Response to
>>>>>>> the ITU-T on Friday
>>>>>>>> 14th January and am posting it to the MPLS WG list for
>>>>>>> review.
>>>>>>>> =======
>>>>>>>>
>>>>>>>> Response to Updated draft Recommendation G.tpoam [Ref
>>>>>>> 043.02]
>>>>>>>> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>>>>>>>> To: tsbsg15@itu.int,
>>>>>>> greg.jones@itu.int,
>>>>>>> hiroshi.ota@itu.int,
>>>>>>> IAB@ietf.org
>>>>>>>> CC: Greg Jones, swallow@cisco.com,
>>>>>>> loa@pi.nu, paf@cisco.com
>>>>>>>> stbryant@cisco.com,
>>>>>>> adrian.farrel@huawei.com,
>>>>>>> mpls@ietf.org
>>>>>>>> yoichi.maeda@ttc.or.jp,
>>>>>>> steve.trowbridge@alcatel-lucent.com
>>>>>>>
>>>>>>>> ghani.abbas@ericsson.com,
>>>>>>> hhelvoort@huawei.com
>>>>>>>
>>>>>>>> malcolm.betts@zte.com.cn,
>>>>>>> kam.lam@alcatel-lucent.com
>>>>>>>
>>>>>>>> For Action
>>>>>>>>
>>>>>>>> The MPLS Working Group notes that this document
>>>>>>> contains text describing
>>>>>>>> MPLS-TP OAM protocols not designed and standardized
>>>>>>> using the IETF
>>>>>>>> Standards process. Specifically it uses material from
>>>>>>>> draft-bhh-mpls-tp-oam-y1731-06.
>>>>>>>>
>>>>>>>> We wish to draw your attention to the status section
>>>>>>> of
>>>>>>>> draft-bhh-mpls-tp-oam-y1731-06 which states:
>>>>>>>>
>>>>>>>> "Internet-Drafts are draft documents valid for a
>>>>>>> maximum of six months
>>>>>>>> and may be updated, replaced, or obsoleted by other
>>>>>>> documents at any
>>>>>>>> time. It is inappropriate to use Internet-Drafts as
>>>>>>> reference material
>>>>>>>> or to cite them other than as "work in progress".
>>>>>>>>
>>>>>>>> Please also note that since the draft filename starts
>>>>>>> with the prefix
>>>>>>>> string "draft-bhh" this clearly identifies it to the
>>>>>>> reader as a
>>>>>>>> document expressing the personal technical views of
>>>>>>> the authors and
>>>>>>>> hence hence as a document that that does not have any
>>>>>>> acknowledged level
>>>>>>>> of IETF consensus.
>>>>>>>>
>>>>>>>> Since the text of draft Recommendation for G.tpoam is
>>>>>>> based on an
>>>>>>>> MPLS-TP OAM protocol not designed within the IETF
>>>>>>> Standards Process this
>>>>>>>> is a breach of the SG15 agreement with the IETF as
>>>>>>> published in Report
>>>>>>>> of the first meeting of Working Party 3/15 Transport
>>>>>>> network structures
>>>>>>>> (2009-2012) (Geneva, 1 – 12 December 2008) which can
>>>>>>> be found at
>>>>>>>> http://www.itu.int/md/T09-SG15-R-0004/en
>>>>>>>> Please confirm that the ITU-T intends to continue with
>>>>>>> the joint work on
>>>>>>>> MPLS-TP and that the ITU-T will align this
>>>>>>> recommendation with the IETF
>>>>>>>> MPLS-TP OAM design before advancing this document
>>>>>>> through the ITU-T
>>>>>>>> publication process.
>>>>>>>>
>>>>>>>> The MPLS Working Group would also like to draw the
>>>>>>> attention of ITU-T
>>>>>>>> SG15 to the IETF copyright rules. Please see
>>>>>>>> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-P
>>>>>>>> ol
>>>>>>>> icy-
>>>>>>>> 20091228.htm
>>>>>>>> for further details.
>>>>>>>>
>>>>>>>> Since this draft Recommendation contains text in which
>>>>>>> the ITU-T SG15
>>>>>>>> has proposed making changes to IETF protocols without
>>>>>>> the approval of
>>>>>>>> the IETF, the MPLS Working Group have referred this
>>>>>>> liaison to the IAB
>>>>>>>> for their consideration.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> =========
>>>>>>>> _______________________________________________
>>>>>>>> mpls mailing list
>>>>>>>> mpls@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> mpls-tp mailing list
>>>>>>> mpls-tp@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>>>>>>
>>>>>> _______________________________________________
>>>>>> mpls-tp mailing list
>>>>>> mpls-tp@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>>>> _______________________________________________
>>>>> mpls mailing list
>>>>> mpls@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>> --
>>>> For corporate legal information go to:
>>>>
>>>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>>>
>>>>
>>>> _______________________________________________
>>>> mpls mailing list
>>>> mpls@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>
>>
>> --
>> *****************************************************************
>>                             我爱外点一七三一
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp



From jdrake@juniper.net  Thu Jan 13 16:02:37 2011
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E83DB3A6C16; Thu, 13 Jan 2011 16:02:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.116
X-Spam-Level: 
X-Spam-Status: No, score=-6.116 tagged_above=-999 required=5 tests=[AWL=0.483,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NglsrmsXLS+L; Thu, 13 Jan 2011 16:02:36 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id 537A73A6BC7; Thu, 13 Jan 2011 16:02:36 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTS+TK0/eDpW3HFz3Vj4OBofHzZLVmdQk@postini.com; Thu, 13 Jan 2011 16:05:00 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Thu, 13 Jan 2011 16:03:12 -0800
From: John E Drake <jdrake@juniper.net>
To: Yuji Tochio <tochio@jp.fujitsu.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Thu, 13 Jan 2011 16:05:08 -0800
Thread-Topic: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
Thread-Index: AcuzduoQA61s1qsNQeGAVKUoWQ06fwAAKzrQ
Message-ID: <5E893DB832F57341992548CDBB33316398C702A766@EMBX01-HQ.jnpr.net>
References: <4D2AE56A.3060200@cisco.com> <4D2F7A4C.80304@gmail.com> <4D2F8669.1090103@jp.fujitsu.com>
In-Reply-To: <4D2F8669.1090103@jp.fujitsu.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 00:02:38 -0000

QWN0dWFsbHksIHRoZSBmaXJzdCBwYXJhZ3JhcGggZG9lcyBub3QgYXNrIGZvciB3ZDE5cjIuICBH
aXZlbiB0aGUgc3RhdHVzIG9mIGRyYWZ0IGJoaCBpbiB0aGUgSUVURiBhbmQgZ2l2ZW4gdGhlIHN0
aWxsIGluIGZvcmNlIGFncmVlbWVudCBiZXR3ZWVuIHRoZSBJVFUgYW5kIHRoZSBJRVRGLCB3aHkg
c2hvdWxkIGFueSBJRVRGIGN5Y2xlcyBiZSBzcGVudCByZXZpZXdpbmcgRy44MTIxPw0KDQpTZW50
IGZyb20gbXkgaVBob25lDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTog
bXBscy10cC1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86bXBscy10cC1ib3VuY2VzQGlldGYub3Jn
XSBPbg0KPiBCZWhhbGYgT2YgWXVqaSBUb2NoaW8NCj4gU2VudDogVGh1cnNkYXksIEphbnVhcnkg
MTMsIDIwMTEgMzoxMSBQTQ0KPiBUbzogbXBsc0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0K
PiBTdWJqZWN0OiBSZTogW21wbHMtdHBdIFttcGxzXSBEcmFmdDogUmVzcG9uc2UgdG8gVXBkYXRl
ZCBkcmFmdA0KPiBSZWNvbW1lbmRhdGlvbiBHLjgxMjEgW1JlZiAwNDIuMDJdDQo+IA0KPiBIaSwN
Cj4gDQo+IEFzIHRvIHRoaXMgcmVzcG9uc2UgKEcuODEyMSksIEkgc3VwcG9ydCBIdXViJ3MgY29t
bWVudC4NCj4gVGhlIGltcG9ydGFudCBpcyB0byByZXZpZXcgdGhlIGRyYWZ0IEcuODEyMSBzbyB0
aGF0IElFVEYgc2hvdWxkDQo+IGFzayBmb3IgdGhlIG1pc3NpbmcgZmlsZSBhdCBmaXJzdC4NCj4g
SW4gdGhhdCBzZW5zZSwgdGhlIGZpcnN0IHBhcmFncmFwaCBvZiBMUyB3aXRoIGFza2luZyBmb3Ig
dGhlIGRyYWZ0DQo+IChpLmUuIHdkMTlyMikgaXMgZW5vdWdoLg0KPiANCj4gT2YgY291cnNlLCBJ
VFUtVCBzaG91bGQgaGF2ZSB2ZXJpZmllZCB0aGF0IHRoZSBhdHRhY2htZW50IGlzDQo+IGluY2x1
ZGVkLi4uLg0KPiANCj4gUmVnYXJkcywNCj4gWXVqaQ0KPiANCj4gKDIwMTEvMDEvMTQgNzoxOCks
IEh1dWIgdmFuIEhlbHZvb3J0IHdyb3RlOg0KPiA+IEhlbGxvIFN0ZXdhcnQsDQo+ID4NCj4gPiBZ
b3Ugd3JvdGU6DQo+ID4NCj4gPj4gSSBwcm9wb3NlIHRvIHNlbmQgdGhlIGZvbGxvd2luZyBMaWFp
c29uIFJlc3BvbnNlIHRvIHRoZSBJVFUtVCBvbg0KPiBGcmlkYXkNCj4gPj4gMTR0aCBKYW51YXJ5
IGFuZCBhbSBwb3N0aW5nIGl0IHRvIHRoZSBNUExTIFdHIGxpc3QgZm9yIHJldmlldy4NCj4gPg0K
PiA+IEkgZG8gbm90IHN1cHBvcnQgc2VuZGluZyB0aGUgbGlhaXNvbiBhcyBwcm9wb3NlZC4NCj4g
Pg0KPiA+IFdlIHNob3VsZCByZXN0cmljdCBpdCB0byB0aGUgZmlyc3QgcGFyYWdyYXBoIG5vdGlu
ZyB0aGF0IHRoZSBmaWxlDQo+ID4gdGhhdCBzaG91bGQgYmUgcmV2aWV3ZWQgaXMgbWlzc2luZyBh
bmQgYXNrIGZvciBzZW5kaW5nIHRoZSBtaXNzaW5nDQo+ID4gZmlsZSBzbyBpdCBjYW4gYmUgcmV2
aWV3ZWQgYnkgdGhlIFdHLg0KPiA+DQo+ID4gVGhlIHJlbWFpbmRlciBvZiB0aGUgdGV4dCBpcyBi
YXNlZCBvbiBhc3N1bXB0aW9ucyBhbmQgbm90IG9uIGZhY3RzLg0KPiA+DQo+ID4gUmVnYXJkcywg
SHV1Yi4NCj4gPg0KPiA+DQo+ID4+ID09PT09PT09PQ0KPiA+Pg0KPiA+PiBSZXNwb25zZSB0byBV
cGRhdGVkIGRyYWZ0IFJlY29tbWVuZGF0aW9uIEcuODEyMSBbUmVmIDA0Mi4wMl0NCj4gPj4NCj4g
Pj4gRnJvbTogSUVURiBMaWFpc29uIHRvIElUVS1UIG9uIE1QTFMgc3RicnlhbnRAY2lzY28uY29t
DQo+ID4+IFRvOiB0c2JzZzE1QGl0dS5pbnQsIGdyZWcuam9uZXNAaXR1LmludCwgaGlyb3NoaS5v
dGFAaXR1LmludCwNCj4gSUFCQGlldGYub3JnDQo+ID4+IENDOiBHcmVnIEpvbmVzLCBzd2FsbG93
QGNpc2NvLmNvbSwgbG9hQHBpLm51LCBwYWZAY2lzY28uY29tDQo+ID4+IHN0YnJ5YW50QGNpc2Nv
LmNvbSwgYWRyaWFuLmZhcnJlbEBodWF3ZWkuY29tLCBtcGxzQGlldGYub3JnDQo+ID4+IHlvaWNo
aS5tYWVkYUB0dGMub3IuanAsIHN0ZXZlLnRyb3dicmlkZ2VAYWxjYXRlbC1sdWNlbnQuY29tDQo+
ID4+IGdoYW5pLmFiYmFzQGVyaWNzc29uLmNvbSwgaGhlbHZvb3J0QGh1YXdlaS5jb20NCj4gPj4g
bWFsY29sbS5iZXR0c0B6dGUuY29tLmNuLCBrYW0ubGFtQGFsY2F0ZWwtbHVjZW50LmNvbQ0KPiA+
Pg0KPiA+PiBGb3IgQWN0aW9uDQo+ID4+DQo+ID4+IFVuZm9ydHVuYXRlbHkgSVRVLVQgZG9jdW1l
bnQgV0QxOXIyIHdhcyBub3QgYXR0YWNoZWQgdG8gdGhpcw0KPiBsaWFpc29uLA0KPiA+PiBhbmQg
dGh1cyB0aGUgTVBMUyBXb3JraW5nIEdyb3VwIGlzIHVuYWJsZSB0byBjb21tZW50IG9uIGl0cyBj
b250ZW50DQo+IGF0DQo+ID4+IHRoaXMgdGltZS4NCj4gPj4NCj4gPj4gSXQgaXMgc3RhdGVkIGlu
IHRoZSBsaWFpc29uIHRoYXQgdGhlIG1vZGlmaWNhdGlvbnMgdG8gdGhpcyBkcmFmdA0KPiA+PiBS
ZWNvbW1lbmRhdGlvbiBhcmUgYmFzZWQgb24gZHJhZnQtYmhoLW1wbHMtdHAtb2FtLXkxNzMxLTA2
LiBQbGVhc2UNCj4gbWF5DQo+ID4+IHdlIGRyYXcgeW91ciBhdHRlbnRpb24gdG8gdGhlIHN0YXR1
cyBzZWN0aW9uIG9mDQo+ID4+IGRyYWZ0LWJoaC1tcGxzLXRwLW9hbS15MTczMS0wNiB3aGljaCBz
dGF0ZXMNCj4gPj4NCj4gPj4gIkludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZh
bGlkIGZvciBhIG1heGltdW0gb2Ygc2l4DQo+IG1vbnRocw0KPiA+PiBhbmQgbWF5IGJlIHVwZGF0
ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0KPiA+
PiB0aW1lLiBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVm
ZXJlbmNlDQo+IG1hdGVyaWFsDQo+ID4+IG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3
b3JrIGluIHByb2dyZXNzIi4NCj4gPj4NCj4gPj4gUGxlYXNlIGFsc28gbm90ZSB0aGF0IHNpbmNl
IHRoZSBkcmFmdCBmaWxlbmFtZSBzdGFydHMgd2l0aCB0aGUNCj4gcHJlZml4DQo+ID4+IHN0cmlu
ZyAiZHJhZnQtYmhoIiB0aGlzIGNsZWFybHkgaWRlbnRpZmllcyBpdCB0byB0aGUgcmVhZGVyIGFz
IGENCj4gPj4gZG9jdW1lbnQgZXhwcmVzc2luZyB0aGUgcGVyc29uYWwgdGVjaG5pY2FsIHZpZXdz
IG9mIHRoZSBhdXRob3JzIGFuZA0KPiA+PiBoZW5jZSBoZW5jZSBhcyBhIGRvY3VtZW50IHRoYXQg
dGhhdCBkb2VzIG5vdCBoYXZlIGFueSBhY2tub3dsZWRnZWQNCj4gbGV2ZWwNCj4gPj4gb2YgSUVU
RiBjb25zZW5zdXMuDQo+ID4+DQo+ID4+IElmIHRoaXMgZHJhZnQgUmVjb21tZW5kYXRpb24gZm9y
IEcuODEyMSBpcyBiYXNlZCBvbiBhbiBNUExTLVRQIE9BTQ0KPiA+PiBwcm90b2NvbCBub3QgZGVz
aWduZWQgd2l0aGluIHRoZSBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLCB0aGUgTVBMUw0KPiA+PiBX
b3JraW5nIEdyb3VwIGJlbGlldmUgdGhhdCB0aGlzIHdvdWxkIGJlIGluIGJyZWFjaCBvZiB0aGUg
U0cxNQ0KPiBhZ3JlZW1lbnQNCj4gPj4gd2l0aCB0aGUgSUVURiBhcyBwdWJsaXNoZWQgaW4gUmVw
b3J0IG9mIHRoZSBmaXJzdCBtZWV0aW5nIG9mIFdvcmtpbmcNCj4gPj4gUGFydHkgMy8xNSBUcmFu
c3BvcnQgbmV0d29yayBzdHJ1Y3R1cmVzICgyMDA5LTIwMTIpIChHZW5ldmEsIDEg4oCTIDEyDQo+
ID4+IERlY2VtYmVyIDIwMDgpIHdoaWNoIGNhbiBiZSBmb3VuZCBhdA0KPiA+PiBodHRwOi8vd3d3
Lml0dS5pbnQvbWQvVDA5LVNHMTUtUi0wMDA0L2VuDQo+ID4+DQo+ID4+IFRoZSBNUExTIFdvcmtp
bmcgR3JvdXAgd291bGQgYWxzbyBsaWtlIHRvIGRyYXcgdGhlIGF0dGVudGlvbiBvZiBJVFUtDQo+
IFQNCj4gPj4gU0cxNSB0byB0aGUgSUVURiBjb3B5cmlnaHQgcnVsZXMuIFBsZWFzZSBzZWUNCj4g
Pj4gaHR0cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvL2FyY2hpdmUvSUVURi1UcnVz
dC1MaWNlbnNlLQ0KPiBQb2xpY3ktMjAwOTEyMjguaHRtDQo+ID4+IGZvciBmdXJ0aGVyIGRldGFp
bHMuDQo+ID4+DQo+ID4+IFdlIGhhdmUgcmVmZXJyZWQgdGhpcyBsaWFpc29uIHRvIHRoZSBJQUIg
Zm9yIHRoZWlyIGNvbnNpZGVyYXRpb24uDQo+ID4+DQo+ID4+DQo+ID4+ID09PT09PT09PT09DQo+
ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+
IG1wbHMgbWFpbGluZyBsaXN0DQo+ID4+IG1wbHNAaWV0Zi5vcmcNCj4gPj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo+ID4NCj4gPg0KPiANCj4gDQo+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG1wbHMtdHAgbWFp
bGluZyBsaXN0DQo+IG1wbHMtdHBAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9tcGxzLXRwDQo=

From Feng.f.Huang@alcatel-sbell.com.cn  Thu Jan 13 16:25:13 2011
Return-Path: <Feng.f.Huang@alcatel-sbell.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1166F3A6BFB; Thu, 13 Jan 2011 16:25:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.203
X-Spam-Level: *
X-Spam-Status: No, score=1.203 tagged_above=-999 required=5 tests=[AWL=-0.733,  BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,  J_CHICKENPOX_15=0.6, J_CHICKENPOX_25=0.6, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q3DfolJtr2X1; Thu, 13 Jan 2011 16:25:09 -0800 (PST)
Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by core3.amsl.com (Postfix) with ESMTP id D856628B23E; Thu, 13 Jan 2011 16:25:07 -0800 (PST)
X-AuditID: ac189297-b7cc5ae00000285e-eb-4d2f98702f94
Received: from cnshgsbhs01.ad4.ad.alcatel.com (smtp.cn.alcatel-lucent.com [172.24.146.145]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Brightmail Gateway) with SMTP id 6F.FF.10334.1789F2D4; Fri, 14 Jan 2011 08:27:29 +0800 (HKT)
Received: from CNSHGSMBS01.ad4.ad.alcatel.com ([172.24.146.171]) by cnshgsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 14 Jan 2011 08:27:18 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBB381.CD40B1C0"
Date: Fri, 14 Jan 2011 08:27:17 +0800
Message-ID: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB072B9C1F@CNSHGSMBS01.ad4.ad.alcatel.com>
In-Reply-To: <22AC359C-CD36-4607-87B9-1DE6329096AE@asgaard.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] R: Re: [mpls] Draft: Response to Updated draft	Recommendation G.tpoam[Ref043.02]
Thread-Index: AcuzdzfRunCxMCJNQcivuoBlWMZNxgAB4tmg
References: <24506674.971481294959616690.JavaMail.defaultUser@defaultHost> <22AC359C-CD36-4607-87B9-1DE6329096AE@asgaard.org>
From: "HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>
To: "Christopher LILJENSTOLPE" <cdl@asgaard.org>, <erminio.ottone_69@libero.it>
X-OriginalArrivalTime: 14 Jan 2011 00:27:18.0896 (UTC) FILETIME=[CD6F2F00:01CBB381]
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] R: Re: [mpls] Draft: Response to Updated draft	Recommendation G.tpoam[Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 00:25:13 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBB381.CD40B1C0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Christopher,
   I was at the meeting too.
   Do you forgot that it is in IETF79 plenary in Beijing, the  meeting =
was closed before 5 minutes as it was planed though it was said that =
itu-t expert can present if time is enough?
   Do you forgot that IETF  ignored ITU-T inputs on some RFCs before =
approving them as RFCs such as RFC 5921 and =
draft-ietf-mpls-tp-survivability-framework  etc?  I am wondering whether =
IETF have already break the JWT agreement or not? It is right to accuse =
ITU-T on standardize G.tpoam in the liaison text with agreement.

B.R.
Feng
=20


________________________________

From: Christopher LILJENSTOLPE [mailto:cdl@asgaard.org]=20
Sent: 2011=C4=EA1=D4=C214=C8=D5 7:11
To: erminio.ottone_69@libero.it
Cc: nurit.sprecher@nsn.com; HUANG Feng F; stbryant@cisco.com; =
mpls@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] R: Re: [mpls] Draft: Response to Updated draft =
Recommendation G.tpoam[Ref043.02]


Erminio,=20

I was at the meeting, and I did not see anyone denied a chance to =
approach the mic.  I did see a pair of working group chairs struggle to =
keep a working group on the previously published and agreed upon agenda. =
 The fact that a group of individuals wanted to dramatically change the =
agenda at the beginning of the meeting would have denied the other =
groups who had scheduled time from their allotted segments.  Having =
worked in some SG's in the ITU-T as well, I don't believe that behavior =
would have been any more allowed in an ITU-T meeting, than an IETF one =
(if anything, the ITU-T process probably would have shut it down =
faster). =20

Christopher

On 14Jan2011, at 10.00, erminio.ottone_69@libero.it wrote:


	You forget that ITU-T experts have not been allowed to speak at IETF 79 =
and a=20
	new trend of approving RFCs without resolving ITU-T have been started.
=09
=09

		----Messaggio originale----
	=09

		Da: nurit.sprecher@nsn.com
	=09

		Data: 13-gen-2011 13.54
	=09

		A: "ext HUANG Feng F"<Feng.f.Huang@alcatel-sbell.com.cn>, =
<stbryant@cisco.
	=09

	com>, <mpls@ietf.org>
=09

		Cc: <mpls-tp@ietf.org>
	=09

		Ogg: Re: [mpls-tp] [mpls] Draft: Response to Updated draft =
Recommendation G.
	=09

	tpoam[Ref043.02]
=09


		Hi Feng,
	=09

		You say " HF> I can't image the meaning of cooperation is that ITU-T =
do=20
	=09

	nothing and just obey IETF's process!"
=09

		It seems that you are not familiar with the agreement on the joint =
work. The=20
	=09

	ITU-T experts are called to contribute to (also by the SG15) to assist =
in the=20
	development the development of the protocol in the IETF using the IETF =
standard=20
	processes...
=09

		Best regards,
	=09

		Nurit
	=09



		-----Original Message-----
	=09

		From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]=20
	=09

		Sent: Thursday, January 13, 2011 12:31 PM
	=09

		To: Sprecher,
	=09

		Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; mpls@ietf.org
	=09

		Cc: mpls-tp@ietf.org
	=09

		Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam
	=09

	[Ref043.02]
=09


		Hi, Nurit,
	=09

		 Please see in line.
	=09

		B.R.
	=09

		Feng
	=09



		-----Original Message-----
	=09

		From: Sprecher, Nurit (NSN - IL/Hod HaSharon) =
[mailto:nurit.sprecher@nsn.
	=09

	com]=20
=09

		Sent: 2011=C4=EA1=D4=C213=C8=D5 17:45
	=09

		To: HUANG Feng F; stbryant@cisco.com; mpls@ietf.org
	=09

		Cc: mpls-tp@ietf.org
	=09

		Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam
	=09

	[Ref043.02]
=09


		Hi Feng,
	=09

		I did not refer to specific solution, validity and acceptance of a =
solution,=20
	=09

	so I cannot see to what you disagree and how your response fit to mine. =

=09

		If you think that you have a good solution which is proven and =
supported=20
	=09

	please discuss it in the IETF and try to get support for it!=20
=09


		HF> The solution has been submitted to ietf for 2 year!
	=09


		I would like the ITU-T to continue with its collaborative agreement =
with the=20
	=09

	IETF and ensure that the development of the protocol is done as agreed =
and=20
	supported by SG15 using the IETF processes.
=09


		HF> I can't image the meaning of cooperation is that ITU-T do nothing =
and=20
	=09

	just obey IETF's process!
=09


		I will support a single global solution interoperable solution =
(whatever the=20
	=09

	solution is).=20
=09

		Best regards,
	=09

		Nurit
	=09


		-----Original Message-----
	=09

		From: ext HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
	=09

		Sent: Thursday, January 13, 2011 11:35 AM
	=09

		To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com; =
mpls@ietf.
	=09

	org
=09

		Cc: mpls-tp@ietf.org
	=09

		Subject: RE: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam
	=09

	[Ref043.02]
=09


		Hi,Nurit,
	=09

		 I can't agree with you.
	=09

		 Solution of GACH+Y.1731 in G.tpoam is proven work well in Packet =
Transport=20
	=09

	Network by many applications and public demo and it has many =
supporters. I am=20
	wondering why  this solutions is not  standardized in ietf?=20
=09

		  Further more,  I really don't agree with your last sentence, this=20
	=09

	solution is asked by customers in Industry, you can see at least 7 =
providers in=20
	global support this solution.
=09


		B.R.
	=09

		Feng
	=09



		-----Original Message-----
	=09

		From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of=20
	=09

	Sprecher, Nurit (NSN - IL/Hod HaSharon)
=09

		Sent: 2011=C4=EA1=D4=C213=C8=D5 16:18
	=09

		To: stbryant@cisco.com; mpls@ietf.org
	=09

		Subject: Re: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam
	=09

	[Ref043.02]
=09


		Hi,
	=09

		I support the proposal.
	=09

		We have a cooperative agreement with the ITU-T concerning the work on =
MPLS-
	=09

	TP.=20
=09

		The agreement recognizes the design authority of the IETF for MPLS and =
it is=20
	=09

	agreed that the development of the protocol should be done in the IETF =
using=20
	the IETF processes. The ITU-T should not take any uncoordinated action =
in the=20
	development of the MPLS_TP protocol.=20
=09

		We would appreciate if the ITU-T continues (as it committed to) with =
the=20
	=09

	collaborative work with the IETF on MPLS_TP and contributes from its =
expertise=20
	to the development of the protocol using the IETF processes.=20
=09

		We would also not like to see two competing solutions which may =
confuse the=20
	=09

	Industry, bloat operational and capital expenses and badly affect the =
end=20
	customer.=20
=09

		Best regards,
	=09

		Nurit
	=09


		-----Original Message-----
	=09

		From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of ext=20
	=09

	Stewart Bryant
=09

		Sent: Monday, January 10, 2011 12:57 PM
	=09

		To: mpls@ietf.org
	=09

		Subject: [mpls] Draft: Response to Updated draft Recommendation =
G.tpoam=20
	=09

	[Ref043.02]
=09


		I propose to send the following Liaison Response to the ITU-T on =
Friday 14th=20
	=09

	January and am posting it to the MPLS WG list for review.
=09


		=3D=3D=3D=3D=3D=3D=3D
	=09


		Response to Updated draft Recommendation G.tpoam [Ref 043.02]
	=09


		From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
	=09

		To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int, =
IAB@ietf.org
	=09

		CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com =
stbryant@cisco.
	=09

	com, adrian.farrel@huawei.com, mpls@ietf.org yoichi.maeda@ttc.or.jp, =
steve.
	trowbridge@alcatel-lucent.com
=09

		ghani.abbas@ericsson.com, hhelvoort@huawei.com =
malcolm.betts@zte.com.cn, kam.
	=09

	lam@alcatel-lucent.com
=09


		For Action
	=09


		The MPLS Working Group notes that this document contains text =
describing
	=09


		MPLS-TP OAM protocols not designed and standardized using the IETF =
Standards=20
	=09

	process. Specifically it uses material from =
draft-bhh-mpls-tp-oam-y1731-06.
=09


		We wish to draw your attention to the status section of
	=09

		draft-bhh-mpls-tp-oam-y1731-06 which states:
	=09


		"Internet-Drafts are draft documents valid for a maximum of six months =
and=20
	=09

	may be updated, replaced, or obsoleted by other documents at any time. =
It is=20
	inappropriate to use Internet-Drafts as reference material or to cite =
them=20
	other than as "work in progress".
=09


		Please also note that since the draft filename starts with the prefix =
string=20
	=09

	"draft-bhh" this clearly identifies it to the reader as a document =
expressing=20
	the personal technical views of the authors and hence hence as a =
document that=20
	that does not have any acknowledged level
=09


		of IETF consensus.
	=09


		Since the text of draft Recommendation for G.tpoam is based on an =
MPLS-TP OAM=20
	=09

	protocol not designed within the IETF Standards Process this
=09


		is a breach of the SG15 agreement with the IETF as published in Report =
of the=20
	=09

	first meeting of Working Party 3/15 Transport network structures
=09

		(2009-2012) (Geneva, 1 - 12 December 2008) which can be found at =
http://www.
	=09

	itu.int/md/T09-SG15-R-0004/en
=09


		Please confirm that the ITU-T intends to continue with the joint work =
on
	=09


		MPLS-TP and that the ITU-T will align this recommendation with the =
IETF MPLS-
	=09

	TP OAM design before advancing this document through the ITU-T =
publication=20
	process.
=09


		The MPLS Working Group would also like to draw the attention of ITU-T
	=09

		SG15 to the IETF copyright rules. Please see
	=09

		=
http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-2
	=09

		0091228.htm
	=09

		for further details.
	=09


		Since this draft Recommendation contains text in which the ITU-T SG15 =
has=20
	=09

	proposed making changes to IETF protocols without the approval of the =
IETF, the=20
	MPLS Working Group have referred this liaison to the IAB for their=20
	consideration.
=09



		=3D=3D=3D=3D=3D=3D=3D=3D=3D
	=09

		_______________________________________________
	=09

		mpls mailing list
	=09

		mpls@ietf.org
	=09

		https://www.ietf.org/mailman/listinfo/mpls
	=09

		_______________________________________________
	=09

		mpls mailing list
	=09

		mpls@ietf.org
	=09

		https://www.ietf.org/mailman/listinfo/mpls
	=09

		_______________________________________________
	=09

		mpls-tp mailing list
	=09

		mpls-tp@ietf.org
	=09

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




	_______________________________________________
	mpls-tp mailing list
	mpls-tp@ietf.org
	https://www.ietf.org/mailman/listinfo/mpls-tp
=09


---
=C0=EE=BF=C2=EE=A3
Check my PGP key here:
https://www.asgaard.org/~cdl/cdl.asc


------_=_NextPart_001_01CBB381.CD40B1C0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2900.6049" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D311330500-14012011><FONT=20
face=3D"Times New Roman" =
color=3D#0000ff>Christopher,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D311330500-14012011><FONT=20
face=3D"Times New Roman" color=3D#0000ff>&nbsp;&nbsp; I&nbsp;was at the =
meeting=20
too.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D311330500-14012011><FONT=20
face=3D"Times New Roman" color=3D#0000ff>&nbsp;&nbsp; Do you forgot that =
it is in=20
IETF79 plenary in Beijing, the &nbsp;meeting was closed before 5 minutes =
as=20
it&nbsp;was planed though it&nbsp;was&nbsp;said that itu-t expert can =
present if=20
time is enough?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D311330500-14012011><FONT=20
face=3D"Times New Roman" color=3D#0000ff>&nbsp;&nbsp;&nbsp;Do you forgot =
that IETF=20
&nbsp;ignored ITU-T inputs on some RFCs before approving them as RFCs =
such as=20
RFC 5921 and draft-ietf-mpls-tp-survivability-framework&nbsp; etc? =
&nbsp;I am=20
wondering&nbsp;whether IETF have already break the JWT agreement or not? =
It is=20
right to accuse ITU-T on standardize G.tpoam in the liaison text with=20
agreement.<BR></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D311330500-14012011><FONT=20
face=3D"Times New Roman" color=3D#0000ff>B.R.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D311330500-14012011><FONT=20
face=3D"Times New Roman" color=3D#0000ff>Feng</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D311330500-14012011><FONT =
face=3D=CB=CE=CC=E5=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><FONT =
face=3D=CB=CE=CC=E5 color=3D#0000ff=20
size=3D2></FONT><FONT face=3D=CB=CE=CC=E5 color=3D#0000ff =
size=3D2></FONT><FONT color=3D#0000ff=20
size=3D2></FONT><FONT color=3D#0000ff size=3D2></FONT><FONT =
face=3D"Times New Roman"=20
color=3D#0000ff></FONT><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Christopher LILJENSTOLPE=20
[mailto:cdl@asgaard.org] <BR><B>Sent:</B> 2011=C4=EA1=D4=C214=C8=D5 =
7:11<BR><B>To:</B>=20
erminio.ottone_69@libero.it<BR><B>Cc:</B> nurit.sprecher@nsn.com; HUANG =
Feng F;=20
stbryant@cisco.com; mpls@ietf.org; mpls-tp@ietf.org<BR><B>Subject:</B> =
Re:=20
[mpls-tp] R: Re: [mpls] Draft: Response to Updated draft Recommendation=20
G.tpoam[Ref043.02]<BR></FONT><BR></DIV>
<DIV></DIV>Erminio,
<DIV><BR></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>I =
was at the=20
meeting, and I did not see anyone denied a chance to approach the mic. =
&nbsp;I=20
did see a pair of working group chairs struggle to keep a working group =
on the=20
previously published and agreed upon agenda. &nbsp;The fact that a group =
of=20
individuals wanted to dramatically change the agenda at the beginning of =
the=20
meeting would have denied the other groups who had scheduled time from =
their=20
allotted segments. &nbsp;Having worked in some SG's in the ITU-T as =
well, I=20
don't believe that behavior would have been any more allowed in an ITU-T =

meeting, than an IETF one (if anything, the ITU-T process probably would =
have=20
shut it down faster). &nbsp;</DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3DApple-tab-span=20
style=3D"WHITE-SPACE: pre"></SPAN>Christopher</DIV>
<DIV><BR>
<DIV>
<DIV>On 14Jan2011, at 10.00, <A=20
href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_69@libero.it</=
A>=20
wrote:</DIV><BR class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV>You forget that ITU-T experts have not been allowed to speak at =
IETF 79=20
  and a <BR>new trend of approving RFCs without resolving ITU-T have =
been=20
  started.<BR><BR>
  <BLOCKQUOTE type=3D"cite">----Messaggio originale----<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Da: <A=20
    =
href=3D"mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</A><BR></BL=
OCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Data: 13-gen-2011 13.54<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">A: "ext HUANG Feng F"&lt;<A=20
    =
href=3D"mailto:Feng.f.Huang@alcatel-sbell.com.cn">Feng.f.Huang@alcatel-sb=
ell.com.cn</A>&gt;,=20
    &lt;stbryant@cisco.<BR></BLOCKQUOTE>com&gt;, &lt;<A=20
  href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A>&gt;<BR>
  <BLOCKQUOTE type=3D"cite">Cc: &lt;<A=20
    =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</A>&gt;<BR></BLOCKQUOTE=
>
  <BLOCKQUOTE type=3D"cite">Ogg: Re: [mpls-tp] [mpls] Draft: Response to =
Updated=20
    draft<SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre">=20
    </SPAN>Recommendation G.<BR></BLOCKQUOTE>tpoam[Ref043.02]<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Hi Feng,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
    style=3D"WHITE-SPACE: pre"></SPAN>You say " HF&gt; I can't image the =
meaning=20
    of cooperation is that ITU-T do <BR></BLOCKQUOTE>nothing and just =
obey IETF's=20
  process!"<BR>
  <BLOCKQUOTE type=3D"cite">It seems that you are not familiar with the=20
    agreement on the joint work. The <BR></BLOCKQUOTE>ITU-T experts are =
called to=20
  contribute to (also by the SG15) to assist in the <BR>development the=20
  development of the protocol in the IETF using the IETF standard=20
  <BR>processes...<BR>
  <BLOCKQUOTE type=3D"cite">Best regards,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Nurit<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">-----Original Message-----<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">From: ext HUANG Feng F=20
    [mailto:Feng.f.Huang@alcatel-sbell.com.cn] <BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Sent: Thursday, January 13, 2011 12:31=20
  PM<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">To: Sprecher,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Nurit (NSN - IL/Hod HaSharon); <A=20
    href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</A>; <A=20
    href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Cc: <A=20
    =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</A><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Subject: RE: [mpls] Draft: Response to =
Updated draft=20
    Recommendation G.tpoam<BR></BLOCKQUOTE>[Ref043.02]<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Hi, Nurit,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">&nbsp;Please see in line.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">B.R.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Feng<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">-----Original Message-----<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">From: Sprecher, Nurit (NSN - IL/Hod =
HaSharon)=20
    [mailto:nurit.sprecher@nsn.<BR></BLOCKQUOTE>com] <BR>
  <BLOCKQUOTE type=3D"cite">Sent: 2011=C4=EA1=D4=C213=C8=D5 =
17:45<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">To: HUANG Feng F; <A=20
    href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</A>; <A=20
    href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Cc: <A=20
    =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</A><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Subject: RE: [mpls] Draft: Response to =
Updated draft=20
    Recommendation G.tpoam<BR></BLOCKQUOTE>[Ref043.02]<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Hi Feng,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">I did not refer to specific solution, =
validity and=20
    acceptance of a solution, <BR></BLOCKQUOTE>so I cannot see to what =
you=20
  disagree and how your response fit to mine. <BR>
  <BLOCKQUOTE type=3D"cite">If you think that you have a good solution =
which is=20
    proven and supported <BR></BLOCKQUOTE>please discuss it in the IETF =
and try to=20
  get support for it! <BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">HF&gt; The solution has been submitted to =
ietf for 2=20
    year!<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">I would like the ITU-T to continue with its=20
    collaborative agreement with the <BR></BLOCKQUOTE>IETF and ensure =
that the=20
  development of the protocol is done as agreed and <BR>supported by =
SG15 using=20
  the IETF processes.<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">HF&gt; I can't image the meaning of =
cooperation is=20
    that ITU-T do nothing and <BR></BLOCKQUOTE>just obey IETF's =
process!<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">I will support a single global solution=20
    interoperable solution (whatever the <BR></BLOCKQUOTE>solution is). =
<BR>
  <BLOCKQUOTE type=3D"cite">Best regards,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Nurit<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">-----Original Message-----<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">From: ext HUANG Feng F=20
    [mailto:Feng.f.Huang@alcatel-sbell.com.cn]<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Sent: Thursday, January 13, 2011 11:35=20
  AM<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">To: Sprecher, Nurit (NSN - IL/Hod HaSharon); =
<A=20
    href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</A>;=20
  mpls@ietf.<BR></BLOCKQUOTE>org<BR>
  <BLOCKQUOTE type=3D"cite">Cc: <A=20
    =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</A><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Subject: RE: [mpls] Draft: Response to =
Updated draft=20
    Recommendation G.tpoam<BR></BLOCKQUOTE>[Ref043.02]<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Hi,Nurit,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">&nbsp;I can't agree with =
you.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">&nbsp;Solution of GACH+Y.1731 in G.tpoam is =
proven=20
    work well in Packet Transport <BR></BLOCKQUOTE>Network by many =
applications=20
  and public demo and it has many supporters. I am <BR>wondering why =
&nbsp;this=20
  solutions is not &nbsp;standardized in ietf? <BR>
  <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;Further more, &nbsp;I really =
don't agree=20
    with your last sentence, this <BR></BLOCKQUOTE>solution is asked by =
customers=20
  in Industry, you can see at least 7 providers in <BR>global support =
this=20
  solution.<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">B.R.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Feng<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">-----Original Message-----<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">From: <A=20
    href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</A>=20
    [mailto:mpls-bounces@ietf.org] On Behalf Of =
<BR></BLOCKQUOTE>Sprecher, Nurit=20
  (NSN - IL/Hod HaSharon)<BR>
  <BLOCKQUOTE type=3D"cite">Sent: 2011=C4=EA1=D4=C213=C8=D5 =
16:18<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">To: <A=20
    href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</A>; <A=20
    href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Subject: Re: [mpls] Draft: Response to =
Updated draft=20
    Recommendation G.tpoam<BR></BLOCKQUOTE>[Ref043.02]<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Hi,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">I support the proposal.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">We have a cooperative agreement with the =
ITU-T=20
    concerning the work on MPLS-<BR></BLOCKQUOTE>TP. <BR>
  <BLOCKQUOTE type=3D"cite">The agreement recognizes the design =
authority of the=20
    IETF for MPLS and it is <BR></BLOCKQUOTE>agreed that the development =
of the=20
  protocol should be done in the IETF using <BR>the IETF processes. The =
ITU-T=20
  should not take any uncoordinated action in the <BR>development of the =
MPLS_TP=20
  protocol. <BR>
  <BLOCKQUOTE type=3D"cite">We would appreciate if the ITU-T continues =
(as it=20
    committed to) with the <BR></BLOCKQUOTE>collaborative work with the =
IETF on=20
  MPLS_TP and contributes from its expertise <BR>to the development of =
the=20
  protocol using the IETF processes. <BR>
  <BLOCKQUOTE type=3D"cite">We would also not like to see two competing=20
    solutions which may confuse the <BR></BLOCKQUOTE>Industry, bloat =
operational=20
  and capital expenses and badly affect the end <BR>customer. <BR>
  <BLOCKQUOTE type=3D"cite">Best regards,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Nurit<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">-----Original Message-----<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">From: <A=20
    href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</A>=20
    [mailto:mpls-bounces@ietf.org] On Behalf Of ext =
<BR></BLOCKQUOTE>Stewart=20
  Bryant<BR>
  <BLOCKQUOTE type=3D"cite">Sent: Monday, January 10, 2011 12:57=20
  PM<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">To: <A=20
    href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Subject: [mpls] Draft: Response to Updated =
draft=20
    Recommendation G.tpoam <BR></BLOCKQUOTE>[Ref043.02]<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">I propose to send the following Liaison =
Response to=20
    the ITU-T on Friday 14th <BR></BLOCKQUOTE>January and am posting it =
to the=20
  MPLS WG list for review.<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">=3D=3D=3D=3D=3D=3D=3D<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Response to Updated draft Recommendation =
G.tpoam=20
    [Ref 043.02]<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">From: IETF Liaison to ITU-T on MPLS <A=20
    =
href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</A><BR></BLOCKQUOTE=
>
  <BLOCKQUOTE type=3D"cite">To: <A=20
    href=3D"mailto:tsbsg15@itu.int">tsbsg15@itu.int</A>, <A=20
    href=3D"mailto:greg.jones@itu.int">greg.jones@itu.int</A>, <A=20
    href=3D"mailto:hiroshi.ota@itu.int">hiroshi.ota@itu.int</A>, <A=20
    href=3D"mailto:IAB@ietf.org">IAB@ietf.org</A><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">CC: Greg Jones, <A=20
    href=3D"mailto:swallow@cisco.com">swallow@cisco.com</A>, <A=20
    href=3D"mailto:loa@pi.nu">loa@pi.nu</A>, <A=20
    href=3D"mailto:paf@cisco.com">paf@cisco.com</A>=20
  stbryant@cisco.<BR></BLOCKQUOTE>com, <A=20
  href=3D"mailto:adrian.farrel@huawei.com">adrian.farrel@huawei.com</A>, =
<A=20
  href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A> <A=20
  href=3D"mailto:yoichi.maeda@ttc.or.jp">yoichi.maeda@ttc.or.jp</A>, =
steve.<BR><A=20
  =
href=3D"mailto:trowbridge@alcatel-lucent.com">trowbridge@alcatel-lucent.c=
om</A><BR>
  <BLOCKQUOTE type=3D"cite"><A=20
    =
href=3D"mailto:ghani.abbas@ericsson.com">ghani.abbas@ericsson.com</A>, =
<A=20
    href=3D"mailto:hhelvoort@huawei.com">hhelvoort@huawei.com</A> <A=20
    =
href=3D"mailto:malcolm.betts@zte.com.cn">malcolm.betts@zte.com.cn</A>,=20
  kam.<BR></BLOCKQUOTE><A=20
  href=3D"mailto:lam@alcatel-lucent.com">lam@alcatel-lucent.com</A><BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">For Action<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">The MPLS Working Group notes that this =
document=20
    contains text describing<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">MPLS-TP OAM protocols not designed and =
standardized=20
    using the IETF Standards <BR></BLOCKQUOTE>process. Specifically it =
uses=20
  material from draft-bhh-mpls-tp-oam-y1731-06.<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">We wish to draw your attention to the status =
section=20
    of<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">draft-bhh-mpls-tp-oam-y1731-06 which=20
  states:<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">"Internet-Drafts are draft documents valid =
for a=20
    maximum of six months and <BR></BLOCKQUOTE>may be updated, replaced, =
or=20
  obsoleted by other documents at any time. It is <BR>inappropriate to =
use=20
  Internet-Drafts as reference material or to cite them <BR>other than =
as "work=20
  in progress".<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Please also note that since the draft =
filename=20
    starts with the prefix string <BR></BLOCKQUOTE>"draft-bhh" this =
clearly=20
  identifies it to the reader as a document expressing <BR>the personal=20
  technical views of the authors and hence hence as a document that =
<BR>that=20
  does not have any acknowledged level<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">of IETF consensus.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Since the text of draft Recommendation for =
G.tpoam=20
    is based on an MPLS-TP OAM <BR></BLOCKQUOTE>protocol not designed =
within the=20
  IETF Standards Process this<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">is a breach of the SG15 agreement with the =
IETF as=20
    published in Report of the <BR></BLOCKQUOTE>first meeting of Working =
Party=20
  3/15 Transport network structures<BR>
  <BLOCKQUOTE type=3D"cite">(2009-2012) (Geneva, 1 - 12 December 2008) =
which can=20
    be found at =
http://www.<BR></BLOCKQUOTE>itu.int/md/T09-SG15-R-0004/en<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Please confirm that the ITU-T intends to =
continue=20
    with the joint work on<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">MPLS-TP and that the ITU-T will align this=20
    recommendation with the IETF MPLS-<BR></BLOCKQUOTE>TP OAM design =
before=20
  advancing this document through the ITU-T publication <BR>process.<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">The MPLS Working Group would also like to =
draw the=20
    attention of ITU-T<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">SG15 to the IETF copyright rules. Please=20
  see<BR></BLOCKQUOTE>
  <BLOCKQUOTE=20
    =
type=3D"cite">http://trustee.ietf.org/license-info/archive/IETF-Trust-Lic=
ense-Policy-2<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">0091228.htm<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">for further details.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">Since this draft Recommendation contains =
text in=20
    which the ITU-T SG15 has <BR></BLOCKQUOTE>proposed making changes to =
IETF=20
  protocols without the approval of the IETF, the <BR>MPLS Working Group =
have=20
  referred this liaison to the IAB for their <BR>consideration.<BR>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR></BLOCKQUOTE>
  <BLOCKQUOTE=20
  =
type=3D"cite">_______________________________________________<BR></BLOCKQ=
UOTE>
  <BLOCKQUOTE type=3D"cite">mpls mailing list<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">mpls@ietf.org<BR></BLOCKQUOTE>
  <BLOCKQUOTE=20
  =
type=3D"cite">https://www.ietf.org/mailman/listinfo/mpls<BR></BLOCKQUOTE>=

  <BLOCKQUOTE=20
  =
type=3D"cite">_______________________________________________<BR></BLOCKQ=
UOTE>
  <BLOCKQUOTE type=3D"cite">mpls mailing list<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">mpls@ietf.org<BR></BLOCKQUOTE>
  <BLOCKQUOTE=20
  =
type=3D"cite">https://www.ietf.org/mailman/listinfo/mpls<BR></BLOCKQUOTE>=

  <BLOCKQUOTE=20
  =
type=3D"cite">_______________________________________________<BR></BLOCKQ=
UOTE>
  <BLOCKQUOTE type=3D"cite">mpls-tp mailing list<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">mpls-tp@ietf.org<BR></BLOCKQUOTE>
  <BLOCKQUOTE=20
  =
type=3D"cite">https://www.ietf.org/mailman/listinfo/mpls-tp<BR></BLOCKQUO=
TE>
  <BLOCKQUOTE=20
  =
type=3D"cite"><BR></BLOCKQUOTE><BR><BR>__________________________________=
_____________<BR>mpls-tp=20
  mailing=20
  =
list<BR>mpls-tp@ietf.org<BR>https://www.ietf.org/mailman/listinfo/mpls-tp=
<BR></DIV></BLOCKQUOTE></DIV><BR>
<DIV><SPAN class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV>
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV>
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV>---</DIV>
<DIV>=C0=EE=BF=C2=EE=A3<BR>Check my PGP key here:<BR><FONT =
class=3DApple-style-span=20
color=3D#144fae><SPAN class=3DApple-style-span style=3D"TEXT-DECORATION: =
underline"><A=20
href=3D"https://www.asgaard.org/~cdl/cdl.asc">https://www.asgaard.org/~cd=
l/cdl.asc</A></SPAN></FONT></DIV></DIV></DIV></DIV></DIV></DIV></SPAN></D=
IV></SPAN></SPAN></DIV><BR></DIV></BODY></HTML>

------_=_NextPart_001_01CBB381.CD40B1C0--

From huubatwork@gmail.com  Fri Jan 14 02:14:38 2011
Return-Path: <huubatwork@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F31D73A6AFB; Fri, 14 Jan 2011 02:14:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.176
X-Spam-Level: 
X-Spam-Status: No, score=-3.176 tagged_above=-999 required=5 tests=[AWL=-0.177, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8nVIXod9i0Q; Fri, 14 Jan 2011 02:14:36 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 22A813A6AC9; Fri, 14 Jan 2011 02:14:35 -0800 (PST)
Received: by eyd10 with SMTP id 10so1399289eyd.31 for <multiple recipients>; Fri, 14 Jan 2011 02:17:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:disposition-notification-to:date :from:user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=DDdn1+FdlfZFbVq6weSUAGQ+jTcgiNI+yjahiKwSxCU=; b=dYJirwPjRkroVQpJh5k9vEuAdPqoh1YlAbQeNoIcEuJqTYcLElx9J9DMsXSleBFXKz VasTpV46W/2TtqnjguMOdhGx8RU/UuzjfbxmpYBS0NKVTKlSTxcTUhySL4pJ2XusF72d KsRdmTrz7hiwIyW1Ev/ZqAGx3KfVK3CbkStxE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; b=CzR+VRZSRYs8E/3sPdMMWhAdMiPysd4/RDSLDtzNQeW3Mz1br8r2KG2coauY2xlm6k L7Gc/ApJMZiSHadGxufXWZOZxNGX5AiJRczgdEoJ55grZ3Wkq9KGt7bWm66/y/YW04w6 V/fvIk1Rv9rD1DNNnqW4LU4edOfDDtNcYAW/w=
Received: by 10.14.11.226 with SMTP id 74mr459720eex.5.1295000220241; Fri, 14 Jan 2011 02:17:00 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl [77.250.51.60]) by mx.google.com with ESMTPS id v59sm824435eeh.15.2011.01.14.02.16.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 14 Jan 2011 02:16:59 -0800 (PST)
Message-ID: <4D302299.3020803@gmail.com>
Date: Fri, 14 Jan 2011 11:16:57 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>,  "mpls-tp@ietf.org" <mpls-tp@ietf.org>
References: <4D2AE56A.3060200@cisco.com> <4D2F7A4C.80304@gmail.com>	<4D2F8669.1090103@jp.fujitsu.com> <5E893DB832F57341992548CDBB33316398C702A766@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB33316398C702A766@EMBX01-HQ.jnpr.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 10:14:38 -0000

Hi John,

You wrote:

> Actually, the first paragraph does not ask for wd19r2.
 > Given the status of draft bhh in the IETF and given the still
 > in force agreement between the ITU and the IETF, why should
 > any IETF cycles be spent reviewing G.8121?

If this is a fact,then why is this not mentioned in the liaison.

Proposed text:
"Given the status of draft-bhh in the IETF we do not intend to
review G.8121 nor G.tpoam"

Regards, Huub.

Sent from my MacBook.

>> -----Original Message-----
>> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
>> Behalf Of Yuji Tochio
>> Sent: Thursday, January 13, 2011 3:11 PM
>> To: mpls@ietf.org; mpls-tp@ietf.org
>> Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft
>> Recommendation G.8121 [Ref 042.02]
>>
>> Hi,
>>
>> As to this response (G.8121), I support Huub's comment.
>> The important is to review the draft G.8121 so that IETF should
>> ask for the missing file at first.
>> In that sense, the first paragraph of LS with asking for the draft
>> (i.e. wd19r2) is enough.
>>
>> Of course, ITU-T should have verified that the attachment is
>> included....
>>
>> Regards,
>> Yuji
>>
>> (2011/01/14 7:18), Huub van Helvoort wrote:
>>> Hello Stewart,
>>>
>>> You wrote:
>>>
>>>> I propose to send the following Liaison Response to the ITU-T on
>> Friday
>>>> 14th January and am posting it to the MPLS WG list for review.
>>>
>>> I do not support sending the liaison as proposed.
>>>
>>> We should restrict it to the first paragraph noting that the file
>>> that should be reviewed is missing and ask for sending the missing
>>> file so it can be reviewed by the WG.
>>>
>>> The remainder of the text is based on assumptions and not on facts.
>>>
>>> Regards, Huub.
>>>
>>>
>>>> =========
>>>>
>>>> Response to Updated draft Recommendation G.8121 [Ref 042.02]
>>>>
>>>> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>>>> To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int,
>> IAB@ietf.org
>>>> CC: Greg Jones, swallow@cisco.com, loa@pi.nu, paf@cisco.com
>>>> stbryant@cisco.com, adrian.farrel@huawei.com, mpls@ietf.org
>>>> yoichi.maeda@ttc.or.jp, steve.trowbridge@alcatel-lucent.com
>>>> ghani.abbas@ericsson.com, hhelvoort@huawei.com
>>>> malcolm.betts@zte.com.cn, kam.lam@alcatel-lucent.com
>>>>
>>>> For Action
>>>>
>>>> Unfortunately ITU-T document WD19r2 was not attached to this
>> liaison,
>>>> and thus the MPLS Working Group is unable to comment on its content
>> at
>>>> this time.
>>>>
>>>> It is stated in the liaison that the modifications to this draft
>>>> Recommendation are based on draft-bhh-mpls-tp-oam-y1731-06. Please
>> may
>>>> we draw your attention to the status section of
>>>> draft-bhh-mpls-tp-oam-y1731-06 which states
>>>>
>>>> "Internet-Drafts are draft documents valid for a maximum of six
>> months
>>>> and may be updated, replaced, or obsoleted by other documents at any
>>>> time. It is inappropriate to use Internet-Drafts as reference
>> material
>>>> or to cite them other than as "work in progress".
>>>>
>>>> Please also note that since the draft filename starts with the
>> prefix
>>>> string "draft-bhh" this clearly identifies it to the reader as a
>>>> document expressing the personal technical views of the authors and
>>>> hence hence as a document that that does not have any acknowledged
>> level
>>>> of IETF consensus.
>>>>
>>>> If this draft Recommendation for G.8121 is based on an MPLS-TP OAM
>>>> protocol not designed within the IETF Standards Process, the MPLS
>>>> Working Group believe that this would be in breach of the SG15
>> agreement
>>>> with the IETF as published in Report of the first meeting of Working
>>>> Party 3/15 Transport network structures (2009-2012) (Geneva, 1 – 12
>>>> December 2008) which can be found at
>>>> http://www.itu.int/md/T09-SG15-R-0004/en
>>>>
>>>> The MPLS Working Group would also like to draw the attention of ITU-
>> T
>>>> SG15 to the IETF copyright rules. Please see
>>>> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-
>> Policy-20091228.htm
>>>> for further details.
>>>>
>>>> We have referred this liaison to the IAB for their consideration.
>>>>
>>>>
>>>> ===========
>>>> _______________________________________________
>>>> mpls mailing list
>>>> mpls@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>
>>>
>>
>>
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


-- 
*****************************************************************
                          我爱外点一七三一

From stbryant@cisco.com  Fri Jan 14 02:42:59 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 007FA3A6B67 for <mpls-tp@core3.amsl.com>; Fri, 14 Jan 2011 02:42:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.219
X-Spam-Level: 
X-Spam-Status: No, score=-110.219 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1-L5bS6nF4v for <mpls-tp@core3.amsl.com>; Fri, 14 Jan 2011 02:42:56 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 7E7F13A6AA1 for <mpls-tp@ietf.org>; Fri, 14 Jan 2011 02:42:56 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EADe4L02rR7Hu/2dsb2JhbACEC6BLc6RSglEOAYd1jXGBJIM3dASLFg
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 14 Jan 2011 10:45:21 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0EAjKPP002126 for <mpls-tp@ietf.org>; Fri, 14 Jan 2011 10:45:20 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p0EAjI800322; Fri, 14 Jan 2011 10:45:19 GMT
Message-ID: <4D30293F.1070009@cisco.com>
Date: Fri, 14 Jan 2011 10:45:19 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls-tp@ietf.org
References: <526321.56478.qm@web15605.mail.cnb.yahoo.com>	<EC7945C9-3C51-42A1-8CA8-692A94B28F2C@niven-jenkins.co.uk>	<4D2F27F1.1070209@cisco.com>	<6873FACCBB5DDD4D88AABD78A8E483A468CE4D0311@EUSAACMS0703.eamcs.ericsson.se><4D2F47F9.8040701@cisco.com><4D2F7D8E.9040505@gmail.com>	<D29E470202D67745B61059870F433B54040D8FB2@XMB-RCD-202.cisco.com>	<077E41CFFD002C4CAB7DFA4386A532640332E318@DEMUEXC014.nsn-intra.net> <4D2F8CA4.40402@jp.fujitsu.com>
In-Reply-To: <4D2F8CA4.40402@jp.fujitsu.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updateddraft	Recommendation G.tpoam [Ref043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 10:42:59 -0000

Yuji

Please remember that

1) The Liaison set all say:

At the Berlin interim meeting on MPLS-TP further work was undertaken on 
the development of the  OAM Recommendation G.tpoam.  This version was 
developed using all of the relevant input  documents to the meeting and 
is based on draft-bhh-mpls-tp-oam-y1731-06.

2) ISOC, i.e. the IETF, is an ITU-T sector member and as such has full 
knowledge of the report, and thus is able to use this to understand the 
context of the liaison.

- Stewart



On 13/01/2011 23:37, Yuji Tochio wrote:
> Nurit,
>
> You should not discuss on the report of ITU-T interim meeting on
> this thread that is for the reviewing LS to ITU-T since the report
> was not sent as the part of LS233 from ITU-T.
>
> And it is noted that drafts had been developed using all of the relevant
> the input documents to the meeting as well. LSs from ITU-T state
> this point as well.
>
> Regards,
> Yuji
>
>
>
> (2011/01/14 8:12), Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:
>> Huub,
>> I would also recommend you to read the report of the rapporteurs of 
>> Q9, Q10, Q12 and Q14 from the Berlin meeting.
>> The report explicitly says that work was undertaken on the 
>> development of the OAM protocol G.tpoam, G.8121 and G.8151. The 
>> drafts of these documents are based on draft-bhh-mpls-tp-oam-y1731-06.
>> Best regards,
>> Nurit
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf 
>> Of ext Eric Osborne (eosborne)
>> Sent: Friday, January 14, 2011 12:52 AM
>> To: Huub van Helvoort; mpls@ietf.org; mpls-tp@ietf.org
>> Subject: Re: [mpls] [mpls-tp] Draft: Response to Updateddraft 
>> Recommendation G.tpoam [Ref043.02]
>>
>>
>>
>>> -----Original Message-----
>>> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On 
>>> Behalf
>>> Of Huub van Helvoort
>>> Sent: Thursday, January 13, 2011 5:33 PM
>>> To: mpls@ietf.org; mpls-tp@ietf.org
>>> Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft
>>> Recommendation G.tpoam [Ref043.02]
>>>
>>> Hello Stewart,
>>>
>>> You asked:
>>>
>>>> Does anyone disagree with the statement that David makes?
>>> I disagree with this statement in relation to this liaison.
>>>
>>> The draft recommendation G.tpoam that was sent for review does not 
>>> contain
>>> a reference to draft-bhh at all.
>> The liason is here: [https://datatracker.ietf.org/liaison/983/]
>> and it references "LS233 - Updated draft Recommendation G.tpoam [Ref 
>> 043.01] - pdf body" 
>> [https://datatracker.ietf.org/documents/LIAISON/file1151.pdf]
>> which says
>>
>> ----
>> At the Berlin interim meeting on MPLS-TP further work was undertaken 
>> on the development of the
>> OAM Recommendation G.tpoam.  This version was developed using all of 
>> the relevant input
>> documents to the meeting and is based on 
>> draft-bhh-mpls-tp-oam-y1731-06.  We invite your
>> comments on this document
>> ----
>>
>> While you are technically correct that G.tpoam does not itself 
>> contain a reference to draft-bhh, how are we to interpret the liason 
>> statement which claims a clear lineage between draft-bhh and G.tpoam?
>>
>>> Also the statements about validity and copyright are irrelevant.
>>>
>> Can we assume that you agree they are correct, regardless of relevance?
>>
>>
>>
>> eric
>>
>>
>>> Regards, Huub.
>>>
>>>
>>> ==============
>>>> On 13/01/2011 17:09, David Sinicrope wrote:
>>>>> It seems that reference and use of draft-bhh is in violation of the
>>>>> ITU-T external cooperation agreement "Referencing A.5 Qualified
>>>>> Organizations" text found at
>>>>> http://www.itu.int/en/ITU-T/extcoop/Pages/sdo.aspx under the
>>>>> Referencing IETF Documents link.
>>>>> In particular clause 10 of this document states: (See 2nd sentence.)
>>>>>
>>>>> "10 Other: If a study group decides to make the reference to an IETF
>>>>> RFC, the reference should always be made by RFC number (and not by
>>>>> other designations such as STD, BCP, etc.). References should not be
>>>>> made to documents referred to as "Internet Drafts" or to IETF RFCs
>>>>> categorized as Historic or Experimental. Normative references must
>>>>> only be made to IETF RFCs that are Standards Track or to
>>>>> Informational RFCs that have IETF consensus."
>>>>>
>>>>> Is this not correct? If correct, shouldn't this also be pointed out
>>>>> in the liaison?
>>>>> Dave
>>>>>
>>>>> -----Original Message-----
>>>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>>>>> Of Stewart Bryant
>>>>> Sent: Thursday, January 13, 2011 11:27 AM
>>>>> To: mpls@ietf.org
>>>>> Subject: Re: [mpls] [mpls-tp] Draft: Response to Updated draft
>>>>> Recommendation G.tpoam [Ref043.02]
>>>>>
>>>>> Exactly Ben.
>>>>>
>>>>> The Liaison is list of statements of relevant facts, and none of the
>>>>> contra points dispute those facts.
>>>>>
>>>>> Stewart
>>>>>
>>>>> On 13/01/2011 15:41, Ben Niven-Jenkins wrote:
>>>>>> Larry,
>>>>>>
>>>>>> On 13 Jan 2011, at 14:55, Larry wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I don't think it is proper to send the LS to ITU-T because the text
>>>>>>> doesn't reflect the requirement from providers.
>>>>>>> Apparently, draft-bhh based OAM is the most mature solution
>>>>>>> currently. It has been proved by more than 200,000 applications and
>>>>>>> is supported by a lot of operators and vendors.
>>>>>>>
>>>>>> That may or may not be true, but either way it is irrelevant to the
>>>>>> liaison.
>>>>>>
>>>>>> ITU liaised G.tpoam to IETF. The liaison response Stewart has
>>>>>> drafted points out that G.tpoam uses technology (draft-bhh) that is
>>>>>> not endorsed by IETF consensus and points to some risks of doing so,
>>>>>> including breach of a prior ITU-IETF agreement on how to progress
>>>>>> MPLS-TP development.
>>>>>>
>>>>>> Everything in the liaison is fact. Whether draft-bhh is
>>>>>> good/bad/ugly, deployed, supported by operators, etc. is irrelevant,
>>>>>> it is not endorsed by IETF as a MPLS-TP OAM solution and all the
>>>>>> liaison does is point out that fact.
>>>>>>
>>>>>> FWIW this isn't the first time a group of operators have brought a
>>>>>> proposal to IETF only to find that the IETF has decided to do
>>>>>> something else, and I'm sure it won't be the last.
>>>>>>
>>>>>> Ben
>>>>>>
>>>>>> P.S. for some reason email chains related to draft-bhh remind me of
>>>>>> this Dilbert cartoon http://www.dilbert.com/2010-12-22/
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Best regards,
>>>>>>>
>>>>>>> Han Li
>>>>>>>
>>>>>>> *******************************************************************
>>>>>>> **
>>>>>>> ****
>>>>>>> Han Li, Ph.D
>>>>>>> China Mobile Research Institute
>>>>>>> Unit 2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China
>>>>>>> Fax: +86 10 63601087
>>>>>>> MOBILE: 13501093385
>>>>>>> *******************************************************************
>>>>>>> **
>>>>>>> ****
>>>>>>>
>>>>>>>
>>>>>>> --- 11年1月13日，周四,
>>>>>>> ruiquan.jing@ties.itu.int<ruiquan.jing@ties.itu.int>
>>>>>>> 写道：
>>>>>>>
>>>>>>>> 发件人: ruiquan.jing@ties.itu.int<ruiquan.jing@ties.itu.int>
>>>>>>>> 主题: Re: [mpls-tp] [mpls] Draft: Response to Updated draft
>>>>>>>> Recommendation G.tpoam [Ref043.02]
>>>>>>>> 收件人: jingr@ties.itu.ch
>>>>>>>> 抄送: mpls-tp@ietf.org
>>>>>>>> 日期: 2011年1月13日,周四,下午4:09
>>>>>>>> Resend to mpls-tp list.
>>>>>>>>
>>>>>>>> Quoting jingr@ties.itu.ch:
>>>>>>>>
>>>>>>>>> Hi Stewart Bryant,
>>>>>>>>>
>>>>>>>>> I don’t agree with the current LS text.
>>>>>>>>>
>>>>>>>>> China Telecom support the standardization of Y.1731
>>>>>>>> based MPLS-TP OAM tools
>>>>>>>>> in
>>>>>>>>> the ITU-T to meet the urgent and increasing
>>>>>>>> requirements for PTN deployment.
>>>>>>>>> It’s a multi-vendor supported, interoperability
>>>>>>>> certificated and feasible
>>>>>>>>> solution. It had been specified in both CCSA
>>>>>>>> (China Communications Standards
>>>>>>>>> Association) and China Telecom’s PTN standard as the
>>>>>>>> only standard OAM
>>>>>>>>> mechanism.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Best Regards
>>>>>>>>>
>>>>>>>>> Jing Ruiquan
>>>>>>>>>
>>>>>>>>> China　Telecom Beijing
>>>>>>>> Research　Institute
>>>>>>>> ------------------------------------------------------------------
>>>>>>>> -- 
>>>>>>>> ----------
>>>>>>>> -- 
>>>>>>>>> From: mpls-bounces@ietf.org
>>>>>>>> [mailto:mpls-bounces@ietf.org]
>>>>>>>> On Behalf Of
>>>>>>>>> Stewart
>>>>>>>>> Bryant
>>>>>>>>> Sent: Monday, January 10, 2011 6:57 PM
>>>>>>>>> To: mpls@ietf.org
>>>>>>>>> Subject: [mpls] Draft: Response to Updated draft
>>>>>>>> Recommendation G.tpoam
>>>>>>>>> [Ref043.02]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I propose to send the following Liaison Response to
>>>>>>>> the ITU-T on Friday
>>>>>>>>> 14th January and am posting it to the MPLS WG list for
>>>>>>>> review.
>>>>>>>>> =======
>>>>>>>>>
>>>>>>>>> Response to Updated draft Recommendation G.tpoam [Ref
>>>>>>>> 043.02]
>>>>>>>>> From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com
>>>>>>>>> To: tsbsg15@itu.int,
>>>>>>>> greg.jones@itu.int,
>>>>>>>> hiroshi.ota@itu.int,
>>>>>>>> IAB@ietf.org
>>>>>>>>> CC: Greg Jones, swallow@cisco.com,
>>>>>>>> loa@pi.nu, paf@cisco.com
>>>>>>>>> stbryant@cisco.com,
>>>>>>>> adrian.farrel@huawei.com,
>>>>>>>> mpls@ietf.org
>>>>>>>>> yoichi.maeda@ttc.or.jp,
>>>>>>>> steve.trowbridge@alcatel-lucent.com
>>>>>>>>
>>>>>>>>> ghani.abbas@ericsson.com,
>>>>>>>> hhelvoort@huawei.com
>>>>>>>>
>>>>>>>>> malcolm.betts@zte.com.cn,
>>>>>>>> kam.lam@alcatel-lucent.com
>>>>>>>>
>>>>>>>>> For Action
>>>>>>>>>
>>>>>>>>> The MPLS Working Group notes that this document
>>>>>>>> contains text describing
>>>>>>>>> MPLS-TP OAM protocols not designed and standardized
>>>>>>>> using the IETF
>>>>>>>>> Standards process. Specifically it uses material from
>>>>>>>>> draft-bhh-mpls-tp-oam-y1731-06.
>>>>>>>>>
>>>>>>>>> We wish to draw your attention to the status section
>>>>>>>> of
>>>>>>>>> draft-bhh-mpls-tp-oam-y1731-06 which states:
>>>>>>>>>
>>>>>>>>> "Internet-Drafts are draft documents valid for a
>>>>>>>> maximum of six months
>>>>>>>>> and may be updated, replaced, or obsoleted by other
>>>>>>>> documents at any
>>>>>>>>> time. It is inappropriate to use Internet-Drafts as
>>>>>>>> reference material
>>>>>>>>> or to cite them other than as "work in progress".
>>>>>>>>>
>>>>>>>>> Please also note that since the draft filename starts
>>>>>>>> with the prefix
>>>>>>>>> string "draft-bhh" this clearly identifies it to the
>>>>>>>> reader as a
>>>>>>>>> document expressing the personal technical views of
>>>>>>>> the authors and
>>>>>>>>> hence hence as a document that that does not have any
>>>>>>>> acknowledged level
>>>>>>>>> of IETF consensus.
>>>>>>>>>
>>>>>>>>> Since the text of draft Recommendation for G.tpoam is
>>>>>>>> based on an
>>>>>>>>> MPLS-TP OAM protocol not designed within the IETF
>>>>>>>> Standards Process this
>>>>>>>>> is a breach of the SG15 agreement with the IETF as
>>>>>>>> published in Report
>>>>>>>>> of the first meeting of Working Party 3/15 Transport
>>>>>>>> network structures
>>>>>>>>> (2009-2012) (Geneva, 1 – 12 December 2008) which can
>>>>>>>> be found at
>>>>>>>>> http://www.itu.int/md/T09-SG15-R-0004/en
>>>>>>>>> Please confirm that the ITU-T intends to continue with
>>>>>>>> the joint work on
>>>>>>>>> MPLS-TP and that the ITU-T will align this
>>>>>>>> recommendation with the IETF
>>>>>>>>> MPLS-TP OAM design before advancing this document
>>>>>>>> through the ITU-T
>>>>>>>>> publication process.
>>>>>>>>>
>>>>>>>>> The MPLS Working Group would also like to draw the
>>>>>>>> attention of ITU-T
>>>>>>>>> SG15 to the IETF copyright rules. Please see
>>>>>>>>> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-P
>>>>>>>>> ol
>>>>>>>>> icy-
>>>>>>>>> 20091228.htm
>>>>>>>>> for further details.
>>>>>>>>>
>>>>>>>>> Since this draft Recommendation contains text in which
>>>>>>>> the ITU-T SG15
>>>>>>>>> has proposed making changes to IETF protocols without
>>>>>>>> the approval of
>>>>>>>>> the IETF, the MPLS Working Group have referred this
>>>>>>>> liaison to the IAB
>>>>>>>>> for their consideration.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> =========
>>>>>>>>> _______________________________________________
>>>>>>>>> mpls mailing list
>>>>>>>>> mpls@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> mpls-tp mailing list
>>>>>>>> mpls-tp@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> mpls-tp mailing list
>>>>>>> mpls-tp@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>>>>> _______________________________________________
>>>>>> mpls mailing list
>>>>>> mpls@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>> -- 
>>>>> For corporate legal information go to:
>>>>>
>>>>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> mpls mailing list
>>>>> mpls@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>
>>>
>>> -- 
>>> *****************************************************************
>>>                             我爱外点一七三一
>>> _______________________________________________
>>> mpls-tp mailing list
>>> mpls-tp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>
>
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From stbryant@cisco.com  Fri Jan 14 02:54:19 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 121E53A6B49 for <mpls-tp@core3.amsl.com>; Fri, 14 Jan 2011 02:54:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.217
X-Spam-Level: 
X-Spam-Status: No, score=-110.217 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0q5+xllwA4Y8 for <mpls-tp@core3.amsl.com>; Fri, 14 Jan 2011 02:54:18 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 640C73A69F1 for <mpls-tp@ietf.org>; Fri, 14 Jan 2011 02:54:18 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEFAAe7L02rR7Hu/2dsb2JhbACEC5I1jhZzpEiCUQ4Bh3WNbYEkgzd0BIsW
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 14 Jan 2011 10:56:43 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0EAug2o007197 for <mpls-tp@ietf.org>; Fri, 14 Jan 2011 10:56:42 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p0EAue801047; Fri, 14 Jan 2011 10:56:40 GMT
Message-ID: <4D302BE9.3000908@cisco.com>
Date: Fri, 14 Jan 2011 10:56:41 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls-tp@ietf.org
References: <4D2AE56A.3060200@cisco.com>	<4D2F7A4C.80304@gmail.com>	<4D2F8669.1090103@jp.fujitsu.com>	<5E893DB832F57341992548CDBB33316398C702A766@EMBX01-HQ.jnpr.net> <4D302299.3020803@gmail.com>
In-Reply-To: <4D302299.3020803@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 10:54:19 -0000

On 14/01/2011 10:16, Huub van Helvoort wrote:
> Hi John,
>
> You wrote:
>
>> Actually, the first paragraph does not ask for wd19r2.
> > Given the status of draft bhh in the IETF and given the still
> > in force agreement between the ITU and the IETF, why should
> > any IETF cycles be spent reviewing G.8121?
>
> If this is a fact,then why is this not mentioned in the liaison.
... because grammatically John asked a question.
>
> Proposed text:
> "Given the status of draft-bhh in the IETF we do not intend to
> review G.8121 nor G.tpoam"
... I am confident that the IETF will continue to review documents sent 
to it by SG15.

Stewart



From huubatwork@gmail.com  Fri Jan 14 06:08:10 2011
Return-Path: <huubatwork@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A08893A6B7F for <mpls-tp@core3.amsl.com>; Fri, 14 Jan 2011 06:08:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.863
X-Spam-Level: 
X-Spam-Status: No, score=-3.863 tagged_above=-999 required=5 tests=[AWL=0.536,  BAYES_00=-2.599, GB_I_INVITATION=-2, J_CHICKENPOX_15=0.6, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ddhzF2MVZm9D for <mpls-tp@core3.amsl.com>; Fri, 14 Jan 2011 06:08:09 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 85B923A6B26 for <mpls-tp@ietf.org>; Fri, 14 Jan 2011 06:08:09 -0800 (PST)
Received: by eyd10 with SMTP id 10so1477399eyd.31 for <mpls-tp@ietf.org>; Fri, 14 Jan 2011 06:10:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:disposition-notification-to:date :from:user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=K1Im9R/kKLe/S42OM7yJ3sVGwV4lRD+sDILXnTvTX1U=; b=H11HPisitJMx5ev0crjI3eRgjY+T7njUrDbkt7VtaqJ07R/vq5WlL+48CJoP8F+CAU 6q1Yw3VFUfcv3qo1eerL6Jqi42FxED1TGocL7nzrkbxRdeQZqFq0hAi2tdUHdaM5Ojvq Vamt9C0qDe3AAEtm78GKvWE4f4ZjLWkriv0Zc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; b=BVdQvHQGIMnt1jTu4RLHTWYX16yf69iwz28HCyHfuEvswqpwtcPaXi+5NQRfPDszwZ Ly4TC2Adx+aZLu+yfp5LyypYzj78TiW4pgZCVPqKw46k53qW80ernCrEPl3lGwSYPAKB 7ghZM879bN2PR38fUxrdkmFnm0Qf0MkLB0v7w=
Received: by 10.14.11.147 with SMTP id 19mr662446eex.14.1295014234364; Fri, 14 Jan 2011 06:10:34 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl [77.250.51.60]) by mx.google.com with ESMTPS id t50sm979049eeh.0.2011.01.14.06.10.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 14 Jan 2011 06:10:33 -0800 (PST)
Message-ID: <4D305957.7040500@gmail.com>
Date: Fri, 14 Jan 2011 15:10:31 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: mpls-tp@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
References: <4D2AE56A.3060200@cisco.com>	<4D2F7A4C.80304@gmail.com>	<4D2F8669.1090103@jp.fujitsu.com>	<5E893DB832F57341992548CDBB33316398C702A766@EMBX01-HQ.jnpr.net>	<4D302299.3020803@gmail.com> <4D302BE9.3000908@cisco.com>
In-Reply-To: <4D302BE9.3000908@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [mpls-tp] [mpls] Draft: Response to Updated draft Recommendation G.8121 [Ref 042.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 14:08:10 -0000

Hello Stewart,

You replied:

>>> Actually, the first paragraph does not ask for wd19r2.
>> > Given the status of draft bhh in the IETF and given the still
>> > in force agreement between the ITU and the IETF, why should
>> > any IETF cycles be spent reviewing G.8121?
>>
>> If this is a fact,then why is this not mentioned in the liaison.
 >
> ... because grammatically John asked a question.

[hvh] I had the impression that it was a rethorical question.

>> Proposed text:
>> "Given the status of draft-bhh in the IETF we do not intend to
>> review G.8121 nor G.tpoam"
 >
> ... I am confident that the IETF will continue to review documents
 > sent to it by SG15.

[hvh] OK. However I see no indication that in the reply liaison
that G.tpoam was reviewed. It only responds to the text in the
invitation to review G.tpoam.

[hvh] I did read G.tpoam and have no comments, maybe others have
read it too and had no comments.

Regards, Huub.


-- 
*****************************************************************
                          我爱外点一七三一

From nurit.sprecher@nsn.com  Tue Jan 18 22:10:01 2011
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E9333A6EF5; Tue, 18 Jan 2011 22:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.535
X-Spam-Level: 
X-Spam-Status: No, score=-4.535 tagged_above=-999 required=5 tests=[AWL=1.464,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9G-UZOkTJjOM; Tue, 18 Jan 2011 22:10:00 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id A9F083A70DE; Tue, 18 Jan 2011 22:09:59 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0J6Ca7U020199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Jan 2011 07:12:36 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0J6CXDX021677; Wed, 19 Jan 2011 07:12:36 +0100
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 19 Jan 2011 07:12:25 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Wed, 19 Jan 2011 07:12:21 +0100
Message-ID: <077E41CFFD002C4CAB7DFA4386A532640336B555@DEMUEXC014.nsn-intra.net>
In-Reply-To: <4D3619B1.1090301@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Response to Updated draft Recommendation G.tpoam [Ref 043.02]
Thread-Index: Acu3YmsCQZE7AOU8RnSu3AuQihnbOwANfHSw
References: <DF7F294AF4153D498141CBEFADB177049ACD7D00C5@EMBX01-WF.jnpr.net> <4D3619B1.1090301@gmail.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Huub van Helvoort" <huubatwork@gmail.com>, <mpls@ietf.org>, <mpls-tp@ietf.org>
X-OriginalArrivalTime: 19 Jan 2011 06:12:25.0047 (UTC) FILETIME=[D753D670:01CBB79F]
Subject: Re: [mpls-tp] [mpls] Response to Updated draft Recommendation G.tpoam [Ref 043.02]
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2011 06:10:01 -0000

SGkgSHV1YiwNClJGQyA1ODYwIHNwZWNpZmllcyB0aGUgcmVxdWlyZW1lbnRzIGZvciBNUExTLVRQ
IE9BTSBhbmQgcmVxdWlyZXMgKGFtb25nIHRoZSByZXN0KSB0aGF0IHRoZSBiZWhhdmlvciBhbmQg
b3BlcmF0aW9uYWwgZXhwZXJpZW5jZSB3aWxsIGJlIHNpbWlsYXIgdG8gdGhvc2UgaW4gdHJhbnNw
b3J0IG5ldHdvcmtzLiANClRoZSBzb2x1dGlvbnMgY3VycmVudGx5IGJlaW5nIGRlZmluZWQgKGFu
ZCBJIHdhcm1seSByZWNvbW1lbmQgeW91IHRvIHJldmlldyB0aGUgbGF0ZXN0IHZlcnNpb25zIGFu
ZCBjb21tZW50KSBmdWxseSBzYXRpc2Z5IHRoZXNlIGFuZCBhbGwgdGhlIHJlc3Qgb2YgdGhlIHJl
cXVpcmVtZW50cy4gDQpUaGVyZSBpcyBOTyBqdXN0aWZpY2F0aW9uIGZvciBhZGRpdGlvbmFsIHNv
bHV0aW9uISBUaGVyZSBpcyBubyBqdXN0aWZpY2F0aW9uIHRvIGNvbmZ1c2UgdGhlIEluZHVzdHJ5
LCB0aGVyZSBpcyBubyBqdXN0aWZpY2F0aW9uIHRvIGJsb2F0IG9wZXJhdGlvbiBhbmQgY2FwaXRh
bCBleHBlbnNlcyBhbmQgZXZlbiB0byBoYXZlIGJhZCBpbXBhY3Qgb24gdGhlIGVuZCBjdXN0b21l
ciBiZWNhdXNlIG9mIHRoZSBmb3JtZXIgaXNzdWVzIChjb25mdXNpb24sIGNvc3QsIGV0Yy4pLiAN
Ckkgb2JqZWN0IHRvIGRlZmluZSB0d28gc3RhbmRhcmQgc29sdXRpb25zIGZvciB0aGUgc2FtZSBw
cm9ibGVtLiANClRoZSB0b29sc2V0IGluY2x1ZGVzIGRpZmZlcmVudCB0b29scywgZWFjaCBwcm92
aWRpbmcgYSBkaWZmZXJlbnQgZnVuY3Rpb25hbGl0eSAoc3VjaCBhcyBDViwgcGFja2V0IGxvc3Ms
IGV0Yy4pLiB3ZSBkbyBub3QgaGF2ZSB0d28gdG9vbHMgZG9pbmcgdGhlIHNhbWUgdGhpbmcuDQpU
aGUgbWFpbiBjb25jZXJuIEkgaGF2ZSB3aXRoIHlvdXIgYXBwcm9hY2gsIGlzIHRoYXQgdGhlIGFk
dm9jYXRvcnMgb2YgdGhlIGFsdGVybmF0aXZlIHNvbHV0aW9uIHdlcmUgbmV2ZXIgcmVhZHkgdG8g
Z2V0IGludG8gdGVjaG5pY2FsIGRpc2N1c3Npb24gYW5kIGRpc2N1c3MgaXQgdG9vbCBieSB0b29s
LCB0byBzaG93IHdoYXQgZnVuY3Rpb25hbGl0eSB0aGUgYWx0ZXJuYXRpdmUgcHJvcG9zYWwgcHJv
cG9zZXMgdGhhdCB0aGUgc29sdXRpb24gYmVpbmcgZGVmaW5lZCBkb2VzIG5vdCBwcm92aWRlLCBh
bmQgd2h5IHN1Y2ggYSBnYXAgKGlmIGV4aXN0KSBjYW5ub3QgYmUgcmVzb2x2ZWQgaW4gdGhlIGNv
bnRleHQgb2YgdGhlIHNvbHV0aW9uIGJlaW5nIGRlZmluZWQuIA0KVGhlIHdvcmRzIHlvdSB1c2Ug
YmVsb3cgbG9vayB0byBtZSBzaW1wbHkgYXMgYnV6endvcmRzLi4uLiANCkkgYW0gYWxzbyBleHRy
ZW1lbHkgY29uY2VybmVkIGZyb20gdGhlIHRpbWUgYWxsIHRoaXMgZW5kbGVzcyBkaXNjdXNzaW9u
IHRha2UuLi4ud2UgY291bGQgdXNlIHRoZSB0aW1lIG11Y2ggbW9yZSBlZmZlY3RpdmVseSBpZiB3
ZSB1c2UgaXQgdG8gcmV2aWV3IHRoZSBXRyBkb2N1bWVudHMsIGNvbW1lbnQgYW5kIG1ha2Ugc3Vy
ZSBpdCBhcHByb3ByaWF0ZWx5IHNhdGlzZnkgdGhlIHJlcXVpcmVtZW50cy4uLmFuZCBwcm9ncmVz
cyB0aGUgZG9jdW1lbnRzIGZhc3QgdG8gc2F0aXNmeSB0aGUgdXJnZW50IHJlcXVpcmVtZW50IGZv
ciB0aGUgdG9vbHMuIA0KU28gSSB3YW50IHRvIHdhcm1seSByZWNvbW1lbmQgdGhlIGV4cGVydHMg
dG8gcmV2aWV3IHRoZSBkb2N1bWVudHMgYW5kIHByb3ZpZGUgcHJvZHVjdGl2ZSBjb21tZW50cywg
YW5kIGVuc3VyZSB0aGF0IHdlIGhhdmUgYSBzaW5nbGUgc29sdXRpb24gdGhhdCBzYXRpc2Z5IGFs
bCB0aGUgcmVxdWlyZW1lbnRzIGFuZCBmaXRzIGFsbCBkZXBsb3ltZW50IHNjZW5hcmlvcy4gDQpC
ZXN0IHJlZ2FyZHMsDQpOdXJpdA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9t
OiBtcGxzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzptcGxzLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBleHQgSHV1YiB2YW4gSGVsdm9vcnQNClNlbnQ6IFdlZG5lc2RheSwgSmFudWFy
eSAxOSwgMjAxMSAxMjo1MyBBTQ0KVG86IG1wbHNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbbXBs
c10gUmVzcG9uc2UgdG8gVXBkYXRlZCBkcmFmdCBSZWNvbW1lbmRhdGlvbiBHLnRwb2FtIFtSZWYg
MDQzLjAyXQ0KDQpIZWxsbyBSb3NzLA0KDQpZb3Ugd3JvdGU6DQoNCj4gVGhlcmUgYXJlIGF0IGxl
YXN0IHRocmVlIHF1ZXN0aW9ucyBoZXJlOg0KDQpMZXQgbWUgdHJ5IHRvIGFuc3dlciB0aGVtDQoN
Cj4gICAgICAtIERvIHdlIHdhbnQgb25lIHNvbHV0aW9uIGZvciBNUExTIE9BTSwgb3IgdHdvPw0K
DQpJIHRoaW5rIHdlIHdhbnQgb25lIHRvb2xib3ggd2l0aCBhIHNldCBvZiB0b29scy4NCkl0IG1h
eSBoYXBwZW4gdGhhdCB0aGVyZSBhcmUgdG9vbHMgdGhhdCBvb2sgYWxpa2UgYnV0IG1heSBiZQ0K
ZGlmZmVyZW50IGluIGRldGFpbCBiZWNhdXNlIHRoZXkgYXJlIHVzZWQgaW4gYSBkaWZmZXJlbnQg
Y29udGV4dC4NCg0KPiAgICAgIC0gT25jZSB3ZSBtYWtlIGEgZGVjaXNpb24sIGRvIHdlIGludGVu
ZCB0byB3b3JrIHRvIG1ha2UNCj4gICAgICAgIGl0IGhhcHBlbiwgb3IgdG8gY29udGludWUgdGhl
IGFyZ3VtZW50IGluZGVmaW5pdGVseT8NCg0KSSB3ZSBhZ3JlZSB0aGF0IHRoZXJlIGNhbiBiZSBk
aWZmZXJlbnQgY29udGV4dHMgaW4gd2hpY2ggZGVkaWNhdGVkDQp0b29scyBmcm9tIHRoZSB0b29s
Ym94IGNhbiBiZSB1c2VkIHRoZSBvcHBvc2l0aW9uIGRpc2FwcGVhcnMuDQoNCj4gICAgICAtIERv
IHdlIHdhbnQgc3RhbmRhcmRzIGZvciB0aGUgSUVURiBUQ1AvSVAvTVBMUyBwcm90b2NvbCBzdWl0
ZQ0KPiAgICAgICAgdG8gYmUgZG9uZSBpbiBvbmUgc3RhbmRhcmRzIGJvZHksIG9yIGluZGVwZW5k
ZW50bHkgaW4gdHdvDQo+ICAgICAgICBkaWZmZXJlbnQgZ3JvdXBzIHdpdGggaW5jb21wYXRpYmxl
IHN0YW5kYXJkcyByZXN1bHRpbmc/DQoNCklmIHdlIGFncmVlIHRoYXQgdGhlcmUgYXJlIGRpZmZl
cmVudCBjb250ZXh0cywgaXQgc2hvdWxkIGJlDQpwb3NzaWJsZSB0byBoYXZlIHRoZSBjb250ZXh0
IHNlbnNpdGl2ZSB0b29scyBkZXZlbG9wcGVkIGJ5IHRoZQ0KZXhwZXJ0cyBpbiBhIHBhcnRpY3Vs
YXIgY29udGV4dC9hcmVhLg0KDQpDdXJyZW50bHkgSSBjYW4gaWRlbnRpZnkgdHdvIGNvbnRleHRz
Og0KLTEtIHBhY2tldCBzd2l0Y2hlZCBuZXR3b3JrcywgdGhlIGRlZGljYXRlZCB0b29scyBzaG91
bGQgYmVoYXZlDQogICAgIHNpbWlsYXIgdG8gZXhpc3RpbmcgdG9vbHMNCi0yLSBwYWNrZXQgdHJh
bnNwb3J0IG5ldHdvcmtzLCB0aGUgZGVkaWNhdGVkIHRvb2xzIHNob3VsZCBiZWhhdmUNCiAgICAg
c2ltaWxhciB0byBleGlzdGluZyB0cmFuc3BvcnQgdGVjaG5vbG9naWVzLg0KDQpSZWdhcmRzLCBI
dXViLg0KDQoNCi0tIA0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioNCiAgICAgICAgICAgICAgICAgICAgICAgICAg5oiR54ix
5aSW54K55LiA5LiD5LiJ5LiADQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KbXBscyBtYWlsaW5nIGxpc3QNCm1wbHNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0K

From loa@pi.nu  Sat Jan 22 11:29:07 2011
Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0B313A69F7; Sat, 22 Jan 2011 11:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qFc+ZsMAg0bI; Sat, 22 Jan 2011 11:29:06 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id B12223A69A2; Sat, 22 Jan 2011 11:29:06 -0800 (PST)
Received: from [172.17.113.226] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 20F182A8001; Sat, 22 Jan 2011 20:31:52 +0100 (CET)
Message-ID: <4D3B30A3.1030607@pi.nu>
Date: Sat, 22 Jan 2011 11:31:47 -0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-fang-mpls-tp-security-framework@tools.ietf.org, "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
Subject: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jan 2011 19:29:07 -0000

Working Group,

this is to start a two week poll on making

draft-fang-mpls-tp-security-framework-04

an MPLS working group document!

Please send your responses to the mpls-tp@ietf.org mailing list.

The poll ends Feb 6, 2011.

Loa, George and Ross
mpls wg co-chairs


-- 


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

From nurit.sprecher@nsn.com  Sat Jan 22 12:00:45 2011
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E7C83A69A2 for <mpls-tp@core3.amsl.com>; Sat, 22 Jan 2011 12:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.942
X-Spam-Level: 
X-Spam-Status: No, score=-4.942 tagged_above=-999 required=5 tests=[AWL=1.657,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7p9c1EBBQu-5 for <mpls-tp@core3.amsl.com>; Sat, 22 Jan 2011 12:00:44 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 21B163A69F3 for <mpls-tp@ietf.org>; Sat, 22 Jan 2011 12:00:43 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0MK3WRe027262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 22 Jan 2011 21:03:32 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0MK3W8L023751; Sat, 22 Jan 2011 21:03:32 +0100
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 22 Jan 2011 21:03:32 +0100
Received: from 10.150.128.36 ([10.150.128.36]) by DEMUEXC014.nsn-intra.net ([10.150.128.30]) with Microsoft Exchange Server HTTP-DAV ;  Sat, 22 Jan 2011 20:03:31 +0000
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Loa Andersson" <loa@pi.nu>, <mpls-tp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework -04 a working group document
thread-index: Acu6b3Due6HETjBaR5yrU6UhzQeifA==
Date: Sat, 22 Jan 2011 22:03:26 +0200
Message-ID: <394101cbba6f$70ee7271$2480960a@nsnintra.net>
X-Mailer: EAS Version 1.00
MIME-Version: 1.0
Content-Language: i-default
X-OriginalArrivalTime: 22 Jan 2011 20:03:32.0806 (UTC) FILETIME=[72113E60:01CBBA6F]
Cc: draft-fang-mpls-tp-security-framework@tools.ietf.org
Subject: Re: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework -04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jan 2011 20:00:45 -0000

Support.=20

--- =D7=94=D7=95=D7=93=D7=A2=D7=94 =D7=9E=D7=A7=D7=95=D7=A8=D7=99=D7=AA =
---
=D7=9E=D7=90=D7=AA: "ext Loa Andersson" <loa@pi.nu>
=D7=A0=D7=95=D7=A9=D7=90: [mpls-tp] poll on making =
draft-fang-mpls-tp-security-framework-04 a working group document
=D7=AA=D7=90=D7=A8=D7=99=D7=9A: 22 2011 =D7=99=D7=A0=D7=95=D7=90=D7=A8
=D7=A9=D7=A2=D7=94: 21:32:04

Working Group,

this is to start a two week poll on making

draft-fang-mpls-tp-security-framework-04

an MPLS working group document!

Please send your responses to the mpls-tp@ietf.org mailing list.

The poll ends Feb 6, 2011.

Loa, George and Ross
mpls wg co-chairs


--=20


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

From ben@niven-jenkins.co.uk  Sat Jan 22 15:14:04 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BC113A684A for <mpls-tp@core3.amsl.com>; Sat, 22 Jan 2011 15:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.63
X-Spam-Level: 
X-Spam-Status: No, score=-104.63 tagged_above=-999 required=5 tests=[AWL=-1.031, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RoUDaBYmCAw2 for <mpls-tp@core3.amsl.com>; Sat, 22 Jan 2011 15:14:02 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by core3.amsl.com (Postfix) with ESMTP id B970A3A67F1 for <mpls-tp@ietf.org>; Sat, 22 Jan 2011 15:14:02 -0800 (PST)
Received: from cpc22-cmbg15-2-0-cust173.5-4.cable.virginmedia.com ([86.27.176.174] helo=[192.168.0.203]) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1PgmhP-0008Bw-2Y; Sat, 22 Jan 2011 23:16:51 +0000
References: <4D3B30A3.1030607@pi.nu>
In-Reply-To: <4D3B30A3.1030607@pi.nu>
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
Message-Id: <B9BE8E34-DF77-4AA9-A10B-02A76CBF19BB@niven-jenkins.co.uk>
Content-Transfer-Encoding: 7bit
From: Benjamin Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Sat, 22 Jan 2011 23:16:49 +0000
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1078)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "mpls-tp@ietf.org TP" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [mpls] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jan 2011 23:14:04 -0000

Support (I am a co-author).

Ben

On 22 Jan 2011, at 19:31, Loa Andersson wrote:

> Working Group,
> 
> this is to start a two week poll on making
> 
> draft-fang-mpls-tp-security-framework-04
> 
> an MPLS working group document!
> 
> Please send your responses to the mpls-tp@ietf.org mailing list.
> 
> The poll ends Feb 6, 2011.
> 
> Loa, George and Ross
> mpls wg co-chairs
> 
> 
> -- 
> 
> 
> Loa Andersson                         email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                             +46 767 72 92 13
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From mach@huawei.com  Sun Jan 23 16:34:05 2011
Return-Path: <mach@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73F9A3A69E6; Sun, 23 Jan 2011 16:34:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.772
X-Spam-Level: 
X-Spam-Status: No, score=-1.772 tagged_above=-999 required=5 tests=[AWL=-1.277, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b1jm80auolIf; Sun, 23 Jan 2011 16:34:04 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 671C23A69E0; Sun, 23 Jan 2011 16:34:04 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFI000QD4DBLW@szxga05-in.huawei.com>; Mon, 24 Jan 2011 08:36:47 +0800 (CST)
Received: from C55527A ([10.110.98.37]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LFI00AJI4D515@szxga05-in.huawei.com>; Mon, 24 Jan 2011 08:36:47 +0800 (CST)
Date: Mon, 24 Jan 2011 08:36:41 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <4D3B30A3.1030607@pi.nu>
To: 'Loa Andersson' <loa@pi.nu>, mpls-tp@ietf.org
Message-id: <007001cbbb5e$c614e850$523eb8f0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: Acu6axEFS+70VuPcQkC5cD4yKvVxNgA85nzw
References: <4D3B30A3.1030607@pi.nu>
Cc: mpls@ietf.org, 'MPLS-TP ad hoc team' <ahmpls-tp@lists.itu.int>, draft-fang-mpls-tp-security-framework@tools.ietf.org
Subject: Re: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2011 00:34:05 -0000

Support.

Mach

> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
> Of Loa Andersson
> Sent: Sunday, January 23, 2011 3:32 AM
> To: mpls-tp@ietf.org
> Cc: draft-fang-mpls-tp-security-framework@tools.ietf.org; mpls@ietf.org;
> MPLS-TP ad hoc team
> Subject: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04
a
> working group document
> 
> Working Group,
> 
> this is to start a two week poll on making
> 
> draft-fang-mpls-tp-security-framework-04
> 
> an MPLS working group document!
> 
> Please send your responses to the mpls-tp@ietf.org mailing list.
> 
> The poll ends Feb 6, 2011.
> 
> Loa, George and Ross
> mpls wg co-chairs
> 
> 
> --
> 
> 
> Loa Andersson                         email:
> loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                               +46 767 72 92 13
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp



From wei.hongbo@zte.com.cn  Sun Jan 23 16:38:02 2011
Return-Path: <wei.hongbo@zte.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1631B3A69FC; Sun, 23 Jan 2011 16:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.111
X-Spam-Level: 
X-Spam-Status: No, score=-97.111 tagged_above=-999 required=5 tests=[AWL=-0.965, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYEDJzvrAaBv; Sun, 23 Jan 2011 16:38:01 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 4F5BD3A69F9; Sun, 23 Jan 2011 16:38:00 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 205951911657480; Mon, 24 Jan 2011 08:36:22 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.16] with StormMail ESMTP id 53678.5153815725; Mon, 24 Jan 2011 08:33:19 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p0O0ehSX098841; Mon, 24 Jan 2011 08:40:43 +0800 (GMT-8) (envelope-from wei.hongbo@zte.com.cn)
In-Reply-To: <4D3B30A3.1030607@pi.nu>
To: Loa Andersson <loa@pi.nu>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFAC983A2A.1FF40104-ON48257822.00036CCA-48257822.0003BBC5@zte.com.cn>
From: wei.hongbo@zte.com.cn
Date: Mon, 24 Jan 2011 08:37:47 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-24 08:40:43, Serialize complete at 2011-01-24 08:40:43
Content-Type: multipart/alternative; boundary="=_alternative 0003BBC048257822_="
X-MAIL: mse02.zte.com.cn p0O0ehSX098841
Cc: draft-fang-mpls-tp-security-framework@tools.ietf.org, "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, mpls-tp-bounces@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2011 00:38:02 -0000

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

U3VwcG9ydC4NCg0KQmVzdCByZWdhcmRzLA0Kc3RldmVuDQoNCg0KDQoNCg0KTG9hIEFuZGVyc3Nv
biA8bG9hQHBpLm51PiANCreivP7IyzogIG1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZw0KMjAxMS0w
MS0yMyAwMzozMQ0KDQrK1bz+yMsNCiJtcGxzLXRwQGlldGYub3JnIiA8bXBscy10cEBpZXRmLm9y
Zz4NCrOty80NCmRyYWZ0LWZhbmctbXBscy10cC1zZWN1cml0eS1mcmFtZXdvcmtAdG9vbHMuaWV0
Zi5vcmcsICJtcGxzQGlldGYub3JnIiANCjxtcGxzQGlldGYub3JnPiwgTVBMUy1UUCBhZCBob2Mg
dGVhbSA8YWhtcGxzLXRwQGxpc3RzLml0dS5pbnQ+DQrW98ziDQpbbXBscy10cF0gcG9sbCBvbiBt
YWtpbmcgZHJhZnQtZmFuZy1tcGxzLXRwLXNlY3VyaXR5LWZyYW1ld29yay0wNCBhIA0Kd29ya2lu
ZyBncm91cCBkb2N1bWVudA0KDQoNCg0KDQoNCg0KV29ya2luZyBHcm91cCwNCg0KdGhpcyBpcyB0
byBzdGFydCBhIHR3byB3ZWVrIHBvbGwgb24gbWFraW5nDQoNCmRyYWZ0LWZhbmctbXBscy10cC1z
ZWN1cml0eS1mcmFtZXdvcmstMDQNCg0KYW4gTVBMUyB3b3JraW5nIGdyb3VwIGRvY3VtZW50IQ0K
DQpQbGVhc2Ugc2VuZCB5b3VyIHJlc3BvbnNlcyB0byB0aGUgbXBscy10cEBpZXRmLm9yZyBtYWls
aW5nIGxpc3QuDQoNClRoZSBwb2xsIGVuZHMgRmViIDYsIDIwMTEuDQoNCkxvYSwgR2VvcmdlIGFu
ZCBSb3NzDQptcGxzIHdnIGNvLWNoYWlycw0KDQoNCi0tIA0KDQoNCkxvYSBBbmRlcnNzb24gICAg
ICAgICAgICAgICAgICAgICAgICAgZW1haWw6IGxvYS5hbmRlcnNzb25AZXJpY3Nzb24uY29tDQpT
ciBTdHJhdGVneSBhbmQgU3RhbmRhcmRzIE1hbmFnZXIgICAgICAgICAgICBsb2FAcGkubnUNCkVy
aWNzc29uIEluYyAgICAgICAgICAgICAgICAgICAgICAgICAgcGhvbmU6ICs0NiAxMCA3MTcgNTIg
MTMNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICArNDYgNzY3
IDcyIDkyIDEzDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KbXBscy10cCBtYWlsaW5nIGxpc3QNCm1wbHMtdHBAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscy10cA0KDQoNCg0KDQoNCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpaVEUgSW5mb3JtYXRp
b24gU2VjdXJpdHkgTm90aWNlOiBUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWFp
bCBpcyBzb2xlbHkgcHJvcGVydHkgb2YgdGhlIHNlbmRlcidzIG9yZ2FuaXphdGlvbi4gVGhpcyBt
YWlsIGNvbW11bmljYXRpb24gaXMgY29uZmlkZW50aWFsLiBSZWNpcGllbnRzIG5hbWVkIGFib3Zl
IGFyZSBvYmxpZ2F0ZWQgdG8gbWFpbnRhaW4gc2VjcmVjeSBhbmQgYXJlIG5vdCBwZXJtaXR0ZWQg
dG8gZGlzY2xvc2UgdGhlIGNvbnRlbnRzIG9mIHRoaXMgY29tbXVuaWNhdGlvbiB0byBvdGhlcnMu
DQpUaGlzIGVtYWlsIGFuZCBhbnkgZmlsZXMgdHJhbnNtaXR0ZWQgd2l0aCBpdCBhcmUgY29uZmlk
ZW50aWFsIGFuZCBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwg
b3IgZW50aXR5IHRvIHdob20gdGhleSBhcmUgYWRkcmVzc2VkLiBJZiB5b3UgaGF2ZSByZWNlaXZl
ZCB0aGlzIGVtYWlsIGluIGVycm9yIHBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3Igb2YgdGhl
IG1lc3NhZ2UuIEFueSB2aWV3cyBleHByZXNzZWQgaW4gdGhpcyBtZXNzYWdlIGFyZSB0aG9zZSBv
ZiB0aGUgaW5kaXZpZHVhbCBzZW5kZXIuDQpUaGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBm
b3IgdmlydXNlcyBhbmQgU3BhbSBieSBaVEUgQW50aS1TcGFtIHN5c3RlbS4NCg==
--=_alternative 0003BBC048257822_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlN1cHBvcnQuPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQpCZXN0IHJlZ2FyZHMsPGJyPg0K
c3RldmVuPGJyPg0KPGJyPg0KPC9mb250Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRo
PTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3aWR0aD0zNSU+PGZvbnQgc2l6ZT0xIGZhY2U9
InNhbnMtc2VyaWYiPjxiPkxvYSBBbmRlcnNzb24gJmx0O2xvYUBwaS5udSZndDs8L2I+DQo8L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPreivP7IyzogJm5ic3A7bXBs
cy10cC1ib3VuY2VzQGlldGYub3JnPC9mb250Pg0KPHA+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt
c2VyaWYiPjIwMTEtMDEtMjMgMDM6MzE8L2ZvbnQ+DQo8dGQgd2lkdGg9NjQlPg0KPHRhYmxlIHdp
ZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQg
c2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPsrVvP7IyzwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBz
aXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+JnF1b3Q7bXBscy10cEBpZXRmLm9yZyZxdW90OyAmbHQ7
bXBscy10cEBpZXRmLm9yZyZndDs8L2ZvbnQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYg
YWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPrOty808L2ZvbnQ+PC9k
aXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPmRyYWZ0LWZhbmctbXBscy10
cC1zZWN1cml0eS1mcmFtZXdvcmtAdG9vbHMuaWV0Zi5vcmcsDQomcXVvdDttcGxzQGlldGYub3Jn
JnF1b3Q7ICZsdDttcGxzQGlldGYub3JnJmd0OywgTVBMUy1UUCBhZCBob2MgdGVhbSAmbHQ7YWht
cGxzLXRwQGxpc3RzLml0dS5pbnQmZ3Q7PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8
ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7W98ziPC9mb250
PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5bbXBscy10cF0gcG9s
bCBvbiBtYWtpbmcgZHJhZnQtZmFuZy1tcGxzLXRwLXNlY3VyaXR5LWZyYW1ld29yay0wNA0KYSB3
b3JraW5nIGdyb3VwIGRvY3VtZW50PC9mb250PjwvdGFibGU+DQo8YnI+DQo8dGFibGU+DQo8dHIg
dmFsaWduPXRvcD4NCjx0ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwvdGFibGU+DQo8YnI+DQo8YnI+
DQo8YnI+PGZvbnQgc2l6ZT0yPjx0dD5Xb3JraW5nIEdyb3VwLDxicj4NCjxicj4NCnRoaXMgaXMg
dG8gc3RhcnQgYSB0d28gd2VlayBwb2xsIG9uIG1ha2luZzxicj4NCjxicj4NCmRyYWZ0LWZhbmct
bXBscy10cC1zZWN1cml0eS1mcmFtZXdvcmstMDQ8YnI+DQo8YnI+DQphbiBNUExTIHdvcmtpbmcg
Z3JvdXAgZG9jdW1lbnQhPGJyPg0KPGJyPg0KUGxlYXNlIHNlbmQgeW91ciByZXNwb25zZXMgdG8g
dGhlIG1wbHMtdHBAaWV0Zi5vcmcgbWFpbGluZyBsaXN0Ljxicj4NCjxicj4NClRoZSBwb2xsIGVu
ZHMgRmViIDYsIDIwMTEuPGJyPg0KPGJyPg0KTG9hLCBHZW9yZ2UgYW5kIFJvc3M8YnI+DQptcGxz
IHdnIGNvLWNoYWlyczxicj4NCjxicj4NCjxicj4NCi0tIDxicj4NCjxicj4NCjxicj4NCkxvYSBB
bmRlcnNzb24gJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7IGVtYWlsOiBsb2EuYW5kZXJzc29u
QGVyaWNzc29uLmNvbTxicj4NClNyIFN0cmF0ZWd5IGFuZCBTdGFuZGFyZHMgTWFuYWdlciAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2xvYUBwaS5udTxicj4NCkVyaWNz
c29uIEluYyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7cGhvbmU6ICs0NiAxMCA3
MTcgNTIgMTM8YnI+DQogJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7DQombmJzcDsg
Jm5ic3A7KzQ2IDc2NyA3MiA5MiAxMzxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPGJyPg0KbXBscy10cCBtYWlsaW5nIGxpc3Q8YnI+DQptcGxzLXRw
QGlldGYub3JnPGJyPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxz
LXRwPGJyPg0KPGJyPg0KPC90dD48L2ZvbnQ+DQo8YnI+DQo8YnI+PHByZT4NCi0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpaVEUmbmJzcDtJ
bmZvcm1hdGlvbiZuYnNwO1NlY3VyaXR5Jm5ic3A7Tm90aWNlOiZuYnNwO1RoZSZuYnNwO2luZm9y
bWF0aW9uJm5ic3A7Y29udGFpbmVkJm5ic3A7aW4mbmJzcDt0aGlzJm5ic3A7bWFpbCZuYnNwO2lz
Jm5ic3A7c29sZWx5Jm5ic3A7cHJvcGVydHkmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO3NlbmRlcidz
Jm5ic3A7b3JnYW5pemF0aW9uLiZuYnNwO1RoaXMmbmJzcDttYWlsJm5ic3A7Y29tbXVuaWNhdGlv
biZuYnNwO2lzJm5ic3A7Y29uZmlkZW50aWFsLiZuYnNwO1JlY2lwaWVudHMmbmJzcDtuYW1lZCZu
YnNwO2Fib3ZlJm5ic3A7YXJlJm5ic3A7b2JsaWdhdGVkJm5ic3A7dG8mbmJzcDttYWludGFpbiZu
YnNwO3NlY3JlY3kmbmJzcDthbmQmbmJzcDthcmUmbmJzcDtub3QmbmJzcDtwZXJtaXR0ZWQmbmJz
cDt0byZuYnNwO2Rpc2Nsb3NlJm5ic3A7dGhlJm5ic3A7Y29udGVudHMmbmJzcDtvZiZuYnNwO3Ro
aXMmbmJzcDtjb21tdW5pY2F0aW9uJm5ic3A7dG8mbmJzcDtvdGhlcnMuDQpUaGlzJm5ic3A7ZW1h
aWwmbmJzcDthbmQmbmJzcDthbnkmbmJzcDtmaWxlcyZuYnNwO3RyYW5zbWl0dGVkJm5ic3A7d2l0
aCZuYnNwO2l0Jm5ic3A7YXJlJm5ic3A7Y29uZmlkZW50aWFsJm5ic3A7YW5kJm5ic3A7aW50ZW5k
ZWQmbmJzcDtzb2xlbHkmbmJzcDtmb3ImbmJzcDt0aGUmbmJzcDt1c2UmbmJzcDtvZiZuYnNwO3Ro
ZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtvciZuYnNwO2VudGl0eSZuYnNwO3RvJm5ic3A7d2hvbSZu
YnNwO3RoZXkmbmJzcDthcmUmbmJzcDthZGRyZXNzZWQuJm5ic3A7SWYmbmJzcDt5b3UmbmJzcDto
YXZlJm5ic3A7cmVjZWl2ZWQmbmJzcDt0aGlzJm5ic3A7ZW1haWwmbmJzcDtpbiZuYnNwO2Vycm9y
Jm5ic3A7cGxlYXNlJm5ic3A7bm90aWZ5Jm5ic3A7dGhlJm5ic3A7b3JpZ2luYXRvciZuYnNwO29m
Jm5ic3A7dGhlJm5ic3A7bWVzc2FnZS4mbmJzcDtBbnkmbmJzcDt2aWV3cyZuYnNwO2V4cHJlc3Nl
ZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNwO21lc3NhZ2UmbmJzcDthcmUmbmJzcDt0aG9zZSZuYnNw
O29mJm5ic3A7dGhlJm5ic3A7aW5kaXZpZHVhbCZuYnNwO3NlbmRlci4NClRoaXMmbmJzcDttZXNz
YWdlJm5ic3A7aGFzJm5ic3A7YmVlbiZuYnNwO3NjYW5uZWQmbmJzcDtmb3ImbmJzcDt2aXJ1c2Vz
Jm5ic3A7YW5kJm5ic3A7U3BhbSZuYnNwO2J5Jm5ic3A7WlRFJm5ic3A7QW50aS1TcGFtJm5ic3A7
c3lzdGVtLg0KPC9wcmU+
--=_alternative 0003BBC048257822_=--


From yaacov.weingarten@nsn.com  Sun Jan 23 22:54:14 2011
Return-Path: <yaacov.weingarten@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E88BF3A6A77 for <mpls-tp@core3.amsl.com>; Sun, 23 Jan 2011 22:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.508
X-Spam-Level: 
X-Spam-Status: No, score=-4.508 tagged_above=-999 required=5 tests=[AWL=2.091,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HxRZGMcawi1r for <mpls-tp@core3.amsl.com>; Sun, 23 Jan 2011 22:54:14 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id C288F3A6A73 for <mpls-tp@ietf.org>; Sun, 23 Jan 2011 22:54:13 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0O6v5wp003719 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <mpls-tp@ietf.org>; Mon, 24 Jan 2011 07:57:05 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0O6v5UK000472 for <mpls-tp@ietf.org>; Mon, 24 Jan 2011 07:57:05 +0100
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 24 Jan 2011 07:57:05 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 24 Jan 2011 07:57:02 +0100
Message-ID: <62D9AC1F11702146A0387CBFF3A8CD3D033C0F39@DEMUEXC030.nsn-intra.net>
In-Reply-To: <4D3B30A3.1030607@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
Thread-Index: Acu6aww/MVVClsDaRoC4z1prxQsahABKMV4Q
References: <4D3B30A3.1030607@pi.nu>
From: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>
To: <mpls-tp@ietf.org>
X-OriginalArrivalTime: 24 Jan 2011 06:57:05.0369 (UTC) FILETIME=[E8FD4490:01CBBB93]
Subject: Re: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2011 06:54:15 -0000

Support.

Yaacov Weingarten
NSN

>> -----Original Message-----
>> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
>> Behalf Of ext Loa Andersson
>> Sent: Saturday, January 22, 2011 9:32 PM
>> To: mpls-tp@ietf.org
>> Cc: draft-fang-mpls-tp-security-framework@tools.ietf.org;
>> mpls@ietf.org; MPLS-TP ad hoc team
>> Subject: [mpls-tp] poll on making draft-fang-mpls-tp-security-
>> framework-04 a working group document
>>=20
>> Working Group,
>>=20
>> this is to start a two week poll on making
>>=20
>> draft-fang-mpls-tp-security-framework-04
>>=20
>> an MPLS working group document!
>>=20
>> Please send your responses to the mpls-tp@ietf.org mailing list.
>>=20
>> The poll ends Feb 6, 2011.
>>=20
>> Loa, George and Ross
>> mpls wg co-chairs
>>=20
>>=20
>> --
>>=20
>>=20
>> Loa Andersson                         email:
>> loa.andersson@ericsson.com
>> Sr Strategy and Standards Manager            loa@pi.nu
>> Ericsson Inc                          phone: +46 10 717 52 13
>>                                               +46 767 72 92 13
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp

From zhang.fei3@zte.com.cn  Mon Jan 24 16:22:22 2011
Return-Path: <zhang.fei3@zte.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB0D63A69BF; Mon, 24 Jan 2011 16:22:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.963
X-Spam-Level: 
X-Spam-Status: No, score=-96.963 tagged_above=-999 required=5 tests=[AWL=-1.742, BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJTj3ZoYL2c4; Mon, 24 Jan 2011 16:22:21 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id D923A3A69C0; Mon, 24 Jan 2011 16:22:20 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205952548420933; Tue, 25 Jan 2011 08:20:45 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 96520.5943168287; Tue, 25 Jan 2011 08:25:10 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p0P0P632087349; Tue, 25 Jan 2011 08:25:06 +0800 (GMT-8) (envelope-from zhang.fei3@zte.com.cn)
In-Reply-To: <4D3B30A3.1030607@pi.nu>
To: Loa Andersson <loa@pi.nu>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF0EB46DC7.ECE47652-ON48257823.00024743-48257823.0002BA48@zte.com.cn>
From: zhang.fei3@zte.com.cn
Date: Tue, 25 Jan 2011 08:25:16 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-25 08:25:06, Serialize complete at 2011-01-25 08:25:06
Content-Type: multipart/alternative; boundary="=_alternative 0002BA4148257823_="
X-MAIL: mse01.zte.com.cn p0P0P632087349
Cc: "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, draft-fang-mpls-tp-security-framework@tools.ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, mpls-bounces@ietf.org
Subject: Re: [mpls-tp] [mpls] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2011 00:22:22 -0000

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

U3VwcG9ydA0KDQpGZWkNCg0KDQoNCkxvYSBBbmRlcnNzb24gPGxvYUBwaS5udT4gDQq3orz+yMs6
ICBtcGxzLWJvdW5jZXNAaWV0Zi5vcmcNCjIwMTEtMDEtMjMgMDM6MzENCg0KytW8/sjLDQoibXBs
cy10cEBpZXRmLm9yZyIgPG1wbHMtdHBAaWV0Zi5vcmc+DQqzrcvNDQpkcmFmdC1mYW5nLW1wbHMt
dHAtc2VjdXJpdHktZnJhbWV3b3JrQHRvb2xzLmlldGYub3JnLCAibXBsc0BpZXRmLm9yZyIgDQo8
bXBsc0BpZXRmLm9yZz4sIFJvc3MgQ2FsbG9uIDxyY2FsbG9uQGp1bmlwZXIubmV0PiwgTVBMUy1U
UCBhZCBob2MgdGVhbSANCjxhaG1wbHMtdHBAbGlzdHMuaXR1LmludD4NCtb3zOINClttcGxzXSBw
b2xsIG9uIG1ha2luZyBkcmFmdC1mYW5nLW1wbHMtdHAtc2VjdXJpdHktZnJhbWV3b3JrLTA0IGEg
d29ya2luZyANCmdyb3VwIGRvY3VtZW50DQoNCg0KDQoNCg0KDQpXb3JraW5nIEdyb3VwLA0KDQp0
aGlzIGlzIHRvIHN0YXJ0IGEgdHdvIHdlZWsgcG9sbCBvbiBtYWtpbmcNCg0KZHJhZnQtZmFuZy1t
cGxzLXRwLXNlY3VyaXR5LWZyYW1ld29yay0wNA0KDQphbiBNUExTIHdvcmtpbmcgZ3JvdXAgZG9j
dW1lbnQhDQoNClBsZWFzZSBzZW5kIHlvdXIgcmVzcG9uc2VzIHRvIHRoZSBtcGxzLXRwQGlldGYu
b3JnIG1haWxpbmcgbGlzdC4NCg0KVGhlIHBvbGwgZW5kcyBGZWIgNiwgMjAxMS4NCg0KTG9hLCBH
ZW9yZ2UgYW5kIFJvc3MNCm1wbHMgd2cgY28tY2hhaXJzDQoNCg0KLS0gDQoNCg0KTG9hIEFuZGVy
c3NvbiAgICAgICAgICAgICAgICAgICAgICAgICBlbWFpbDogbG9hLmFuZGVyc3NvbkBlcmljc3Nv
bi5jb20NClNyIFN0cmF0ZWd5IGFuZCBTdGFuZGFyZHMgTWFuYWdlciAgICAgICAgICAgIGxvYUBw
aS5udQ0KRXJpY3Nzb24gSW5jICAgICAgICAgICAgICAgICAgICAgICAgICBwaG9uZTogKzQ2IDEw
IDcxNyA1MiAxMw0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICs0NiA3NjcgNzIgOTIgMTMNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQptcGxzIG1haWxpbmcgbGlzdA0KbXBsc0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQoNCg0KDQo=
--=_alternative 0002BA4148257823_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlN1cHBvcnQ8L2ZvbnQ+DQo8YnI+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkZlaTwvZm9udD4NCjxicj4NCjxi
cj4NCjxicj4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQgd2lkdGg9
MzUlPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj5Mb2EgQW5kZXJzc29uICZsdDts
b2FAcGkubnUmZ3Q7PC9iPg0KPC9mb250Pg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNl
cmlmIj63orz+yMs6ICZuYnNwO21wbHMtYm91bmNlc0BpZXRmLm9yZzwvZm9udD4NCjxwPjxmb250
IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4yMDExLTAxLTIzIDAzOjMxPC9mb250Pg0KPHRkIHdp
ZHRoPTY0JT4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2
IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7K1bz+yMs8L2ZvbnQ+
PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPiZxdW90O21wbHMtdHBA
aWV0Zi5vcmcmcXVvdDsgJmx0O21wbHMtdHBAaWV0Zi5vcmcmZ3Q7PC9mb250Pg0KPHRyIHZhbGln
bj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNl
cmlmIj6zrcvNPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlm
Ij5kcmFmdC1mYW5nLW1wbHMtdHAtc2VjdXJpdHktZnJhbWV3b3JrQHRvb2xzLmlldGYub3JnLA0K
JnF1b3Q7bXBsc0BpZXRmLm9yZyZxdW90OyAmbHQ7bXBsc0BpZXRmLm9yZyZndDssIFJvc3MgQ2Fs
bG9uICZsdDtyY2FsbG9uQGp1bmlwZXIubmV0Jmd0OywNCk1QTFMtVFAgYWQgaG9jIHRlYW0gJmx0
O2FobXBscy10cEBsaXN0cy5pdHUuaW50Jmd0OzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRk
Pg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+1vfM4jwv
Zm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+W21wbHNdIHBv
bGwgb24gbWFraW5nIGRyYWZ0LWZhbmctbXBscy10cC1zZWN1cml0eS1mcmFtZXdvcmstMDQNCmEg
d29ya2luZyBncm91cCBkb2N1bWVudDwvZm9udD48L3RhYmxlPg0KPGJyPg0KPHRhYmxlPg0KPHRy
IHZhbGlnbj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxlPg0KPGJyPg0KPGJy
Pg0KPGJyPjxmb250IHNpemU9Mj48dHQ+V29ya2luZyBHcm91cCw8YnI+DQo8YnI+DQp0aGlzIGlz
IHRvIHN0YXJ0IGEgdHdvIHdlZWsgcG9sbCBvbiBtYWtpbmc8YnI+DQo8YnI+DQpkcmFmdC1mYW5n
LW1wbHMtdHAtc2VjdXJpdHktZnJhbWV3b3JrLTA0PGJyPg0KPGJyPg0KYW4gTVBMUyB3b3JraW5n
IGdyb3VwIGRvY3VtZW50ITxicj4NCjxicj4NClBsZWFzZSBzZW5kIHlvdXIgcmVzcG9uc2VzIHRv
IHRoZSBtcGxzLXRwQGlldGYub3JnIG1haWxpbmcgbGlzdC48YnI+DQo8YnI+DQpUaGUgcG9sbCBl
bmRzIEZlYiA2LCAyMDExLjxicj4NCjxicj4NCkxvYSwgR2VvcmdlIGFuZCBSb3NzPGJyPg0KbXBs
cyB3ZyBjby1jaGFpcnM8YnI+DQo8YnI+DQo8YnI+DQotLSA8YnI+DQo8YnI+DQo8YnI+DQpMb2Eg
QW5kZXJzc29uICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwOyBlbWFpbDogbG9hLmFuZGVyc3Nv
bkBlcmljc3Nvbi5jb208YnI+DQpTciBTdHJhdGVneSBhbmQgU3RhbmRhcmRzIE1hbmFnZXIgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtsb2FAcGkubnU8YnI+DQpFcmlj
c3NvbiBJbmMgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3Bob25lOiArNDYgMTAg
NzE3IDUyIDEzPGJyPg0KICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7
ICZuYnNwOys0NiA3NjcgNzIgOTIgMTM8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXzxicj4NCm1wbHMgbWFpbGluZyBsaXN0PGJyPg0KbXBsc0BpZXRm
Lm9yZzxicj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBsczxicj4N
Cjxicj4NCjwvdHQ+PC9mb250Pg0KPGJyPg0K
--=_alternative 0002BA4148257823_=--


From venkatflex@gmail.com  Mon Jan 24 16:30:08 2011
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDA2A28B23E; Mon, 24 Jan 2011 16:30:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.649
X-Spam-Level: *
X-Spam-Status: No, score=1.649 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_IMAGE_RATIO_02=0.383, HTML_MESSAGE=0.001,  MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LDYyzhAgS2Fz; Mon, 24 Jan 2011 16:30:04 -0800 (PST)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 2901D3A6B05; Mon, 24 Jan 2011 16:30:03 -0800 (PST)
Received: by pvc21 with SMTP id 21so1066857pvc.31 for <multiple recipients>; Mon, 24 Jan 2011 16:32:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=okWmM4PohYmAfU6BYUH6DJDpZCGzrpRhh4u9WFw2Arc=; b=YwPintqairuMBQsG/TopZxQY1UWE5T0WSahcUfa43W5RFug67ZM8RZxxZAl4yM+WYo bZKzYhTVVw6KVDzGJ0qqU78ZlHtmLL6eb2xn5hmLBOpSSRKxmhmM6sh+wCrcDueLpBlC e7z3Y+hYvQ17/tDnauxlYfo8xhKB5yIGL2aiY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Iw6fFVOceTTrqLdQ08MmEO4g2qzpgL8MmxNLTjfurvIoQCKzpqQ1Ytq3rdX71WnnGb 1hH7sCdazWeNMSnyHuNqpDPr1h41uicxdwInNx0YHy+dGVYuT95cITMBIgfR3Rjo6nu5 D3NX+HGoAW+ZMbiYehQH98x7ACRaGahh2Ie90=
MIME-Version: 1.0
Received: by 10.142.161.11 with SMTP id j11mr4558583wfe.60.1295915577930; Mon, 24 Jan 2011 16:32:57 -0800 (PST)
Received: by 10.142.76.10 with HTTP; Mon, 24 Jan 2011 16:32:57 -0800 (PST)
In-Reply-To: <OF0EB46DC7.ECE47652-ON48257823.00024743-48257823.0002BA48@zte.com.cn>
References: <4D3B30A3.1030607@pi.nu> <OF0EB46DC7.ECE47652-ON48257823.00024743-48257823.0002BA48@zte.com.cn>
Date: Mon, 24 Jan 2011 19:32:57 -0500
Message-ID: <AANLkTikBqPXTzhrAeB4ei+cn1C1GEoKijaYaxJTTKqJH@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>,  MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>,  draft-fang-mpls-tp-security-framework@tools.ietf.org,  "mpls-tp@ietf.org" <mpls-tp@ietf.org>, mpls-bounces@ietf.org, Ross Callon <rcallon@juniper.net>
Content-Type: multipart/alternative; boundary=000e0cd32a10ae76f7049aa0db9b
Subject: Re: [mpls-tp] [mpls] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2011 00:30:08 -0000

--000e0cd32a10ae76f7049aa0db9b
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Support.

Regards,
Venkat.

2011/1/24 <zhang.fei3@zte.com.cn>

>
> Support
>
> Fei
>
>
>  *Loa Andersson <loa@pi.nu>*
> =B7=A2=BC=FE=C8=CB:  mpls-bounces@ietf.org
>
> 2011-01-23 03:31
>   =CA=D5=BC=FE=C8=CB
> "mpls-tp@ietf.org" <mpls-tp@ietf.org>
>  =B3=AD=CB=CD
> draft-fang-mpls-tp-security-framework@tools.ietf.org, "mpls@ietf.org" <
> mpls@ietf.org>, Ross Callon <rcallon@juniper.net>, MPLS-TP ad hoc team <
> ahmpls-tp@lists.itu.int>
> =D6=F7=CC=E2
> [mpls] poll on making draft-fang-mpls-tp-security-framework-04 a working
> group document
>
>
>
>
> Working Group,
>
> this is to start a two week poll on making
>
> draft-fang-mpls-tp-security-framework-04
>
> an MPLS working group document!
>
> Please send your responses to the mpls-tp@ietf.org mailing list.
>
> The poll ends Feb 6, 2011.
>
> Loa, George and Ross
> mpls wg co-chairs
>
>
> --
>
>
> Loa Andersson                         email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>


--=20
Best Regards,
Venkatesan Mahalingam.
                                                   <#>
<#>
<#>       <#>

--000e0cd32a10ae76f7049aa0db9b
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Support.<br><br>Regards,<br>Venkat.<br><br><div class=3D"gmail_quote">2011/=
1/24  <span dir=3D"ltr">&lt;<a href=3D"mailto:zhang.fei3@zte.com.cn">zhang.=
fei3@zte.com.cn</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=
=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); p=
adding-left: 1ex;">

<br><font face=3D"sans-serif" size=3D"2">Support</font>
<br>
<br><font face=3D"sans-serif" size=3D"2">Fei</font>
<br>
<br>
<br>
<table width=3D"100%">
<tbody><tr valign=3D"top">
<td width=3D"35%"><div class=3D"im"><font face=3D"sans-serif" size=3D"1"><b=
>Loa Andersson &lt;<a href=3D"mailto:loa@pi.nu" target=3D"_blank">loa@pi.nu=
</a>&gt;</b>
</font>
<br></div><font face=3D"sans-serif" size=3D"1">=B7=A2=BC=FE=C8=CB: &nbsp;<a=
 href=3D"mailto:mpls-bounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.=
org</a></font>
<p></p><div class=3D"im"><font face=3D"sans-serif" size=3D"1">2011-01-23 03=
:31</font>
</div></td><td width=3D"64%">
<table width=3D"100%">
<tbody><tr valign=3D"top">
<td>
<div align=3D"right"><font face=3D"sans-serif" size=3D"1">=CA=D5=BC=FE=C8=
=CB</font></div>
</td><td><div class=3D"im"><font face=3D"sans-serif" size=3D"1">&quot;<a hr=
ef=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.org=
</a>&gt;</font>
</div></td></tr><tr valign=3D"top">
<td>
<div align=3D"right"><font face=3D"sans-serif" size=3D"1">=B3=AD=CB=CD</fon=
t></div>
</td><td><font face=3D"sans-serif" size=3D"1"><a href=3D"mailto:draft-fang-=
mpls-tp-security-framework@tools.ietf.org" target=3D"_blank">draft-fang-mpl=
s-tp-security-framework@tools.ietf.org</a>,
&quot;<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>&=
quot; &lt;<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org<=
/a>&gt;, Ross Callon &lt;<a href=3D"mailto:rcallon@juniper.net" target=3D"_=
blank">rcallon@juniper.net</a>&gt;,
MPLS-TP ad hoc team &lt;<a href=3D"mailto:ahmpls-tp@lists.itu.int" target=
=3D"_blank">ahmpls-tp@lists.itu.int</a>&gt;</font>
</td></tr><tr valign=3D"top">
<td>
<div align=3D"right"><font face=3D"sans-serif" size=3D"1">=D6=F7=CC=E2</fon=
t></div>
</td><td><font face=3D"sans-serif" size=3D"1">[mpls] poll on making draft-f=
ang-mpls-tp-security-framework-04
a working group document</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign=3D"top">
<td>
</td><td></td></tr></tbody></table>
<br></td></tr></tbody></table><div><div></div><div class=3D"h5">
<br>
<br>
<br><font size=3D"2"><tt>Working Group,<br>
<br>
this is to start a two week poll on making<br>
<br>
draft-fang-mpls-tp-security-framework-04<br>
<br>
an MPLS working group document!<br>
<br>
Please send your responses to the <a href=3D"mailto:mpls-tp@ietf.org" targe=
t=3D"_blank">mpls-tp@ietf.org</a> mailing list.<br>
<br>
The poll ends Feb 6, 2011.<br>
<br>
Loa, George and Ross<br>
mpls wg co-chairs<br>
<br>
<br>
-- <br>
<br>
<br>
Loa Andersson &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp; &nbsp; email: <a href=3D"mailto:loa.andersson@ericsson.com" t=
arget=3D"_blank">loa.andersson@ericsson.com</a><br>
Sr Strategy and Standards Manager &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
<a href=3D"mailto:loa@pi.nu" target=3D"_blank">loa@pi.nu</a><br>
Ericsson Inc &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;phone: +46 10 717 52 13<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;
&nbsp; &nbsp;+46 767 72 92 13<br>
_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
<br>
</tt></font>
<br>
</div></div><br>_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Best Regards,<br>Ve=
nkatesan Mahalingam.<br>
<div style=3D"font-size: 11px; visibility: hidden; position: absolute; z-in=
dex: 11000; top: -100px;" id=3D"ArrowLayer1d66kfm"><img style=3D"font-size:=
 11px; width: 0px; height: 0px; position: absolute; z-index: 11001; top: 0p=
x; left: 0px;" id=3D"arrow_bg_image"></div>
<div style=3D"font-size: 11px; visibility: hidden; position: absolute; z-in=
dex: 11000; top: -100px; background-image: url(&quot;sacore:inv.gif&quot;);=
" id=3D"InvLayer1d66kfm"></div><div id=3D"BubbleLayer1d66kfm" style=3D"font=
-size: 11px; text-align: left; visibility: hidden; position: absolute; z-in=
dex: 11002; top: -100px;">
	<div style=3D"position: absolute; left: 18px; top: 2px; height: 50px;" id=
=3D"BALLOONLOGODIV1d66kfm"><table style=3D"height: 100%; border: 0pt none;"=
><tbody><tr><td style=3D"border: 0pt none;" id=3D"BALLOONLOGO1d66kfm"><img =
alt=3D"" src=3D"sacore:empty.gif"></td>
</tr></tbody></table></div>

	<table id=3D"BALLOON1d66kfm" style=3D"width: 100%; cursor: default; -moz-u=
ser-select: none; border-style: none;" border=3D"0" cellpadding=3D"0" cells=
pacing=3D"0">
	    <tbody><tr>
	        <td style=3D"padding: 0pt; border: 0pt none; width: 100%; height: =
51px;">
	            <table id=3D"HEADER_ROW1d66kfm" style=3D"margin: 0pt; border: =
0pt none; width: 100%; height: 100%;" cellpadding=3D"0" cellspacing=3D"0">
	                <tbody><tr>
	                    <td id=3D"HEADER_L1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: no-repeat;" width=3D"18px">&nbsp;</td>
	                    <td id=3D"HEADER_C1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: repeat-x; color: Gray;" align=3D"right">&n=
bsp;</td>
	                    <td id=3D"HEADER_R1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: no-repeat;" align=3D"left" valign=3D"middl=
e" width=3D"38px">
    	                    <img id=3D"closebutton1d66kfm" onclick=3D"BubbleHi=
de()" style=3D"height: 25px; width: 25px;" src=3D"sacore:empty.gif">
	                    </td>
	                </tr>
	            </tbody></table>
	        </td>
	    </tr>
	    <tr>
	        <td style=3D"padding: 0pt; border: 0pt none; width: 100%; height: =
52px;">
	            <table style=3D"margin: 0pt; border: 0pt none; width: 100%; he=
ight: 100%;" cellpadding=3D"0" cellspacing=3D"0">
	                <tbody><tr>
	                    <td id=3D"BANNER_BORDER_L1d66kfm" style=3D"padding: 0p=
t; border: 0pt none; background-repeat: repeat-y;" width=3D"2px">
	                    </td>
	                    <td style=3D"padding: 0pt; border: 0pt none;">
	                        <table id=3D"BANNER_ROW1d66kfm" style=3D"margin: 0=
pt; width: 100%; height: 100%; border: 1px solid White;" cellpadding=3D"0" =
cellspacing=3D"0">
	                            <tbody><tr>
	                                <td id=3D"BANNER_L1d66kfm" style=3D"paddin=
g: 0pt; border: 0pt none; background-repeat: repeat-y;" width=3D"13px">&nbs=
p;</td>
	                                <td id=3D"BANNER_C1d66kfm" style=3D"paddin=
g: 0pt; border: 0pt none; background-repeat: repeat-x;" valign=3D"middle">
	                                <table style=3D"margin: 0pt; border: 0pt n=
one;" cellpadding=3D"0" cellspacing=3D"0" width=3D"100%" height=3D"100%">
	                                    <tbody><tr>
	                                        <td id=3D"ICON1d66kfm" style=3D"pa=
dding: 0pt; border: 0pt none;" width=3D"54px">
        	                                    <img alt=3D"" src=3D"sacore:em=
pty.gif" style=3D"vertical-align: middle;">
	                                        </td>
	                                        <td style=3D"padding: 0pt; border:=
 0pt none;" width=3D"10px">&nbsp;</td>
	                                        <td id=3D"BANNER_SEP1d66kfm" style=
=3D"padding: 0pt; border: 0pt none;" width=3D"10px">
        	                                    <img alt=3D"" src=3D"sacore:em=
pty.gif" style=3D"vertical-align: middle;">
	                                        </td>
	                                        <td style=3D"padding: 0pt; border:=
 0pt none;" width=3D"10px">&nbsp;</td>
	                                        <td id=3D"RECOMMENDATION1d66kfm" c=
lass=3D"sastyle_text_overallrec" style=3D"padding: 0pt; border: 0pt none; c=
olor: White;">&nbsp;</td>
	                                        <td style=3D"padding: 0pt; border:=
 0pt none;" width=3D"10px">&nbsp;</td>
	                                    </tr>
	                                </tbody></table>
            	                   =20
	                                </td>
	                                <td id=3D"BANNER_R1d66kfm" style=3D"paddin=
g: 0pt; border: 0pt none; background-repeat: repeat-y;" width=3D"13px"><img=
 src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></td>
	                            </tr>
	                        </tbody></table>
	                    </td>
	                    <td id=3D"BANNER_BORDER_R1d66kfm" style=3D"padding: 0p=
t; border: 0pt none; background-repeat: repeat-y;" width=3D"2px"><img src=
=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></td>
	                </tr>=20
	            </tbody></table>
	        </td>
	    </tr>
        <tr>
            <td style=3D"padding: 0pt; border: 0pt none; height: 100%; widt=
h: 100%;">
	            <table id=3D"BOTTOM_ROW1d66kfm" class=3D"sastyle_text_contentc=
lass" style=3D"margin: 0pt; border: 0pt none; width: 100%; height: 100%;" c=
ellpadding=3D"0" cellspacing=3D"0">
	                <tbody><tr>
	                    <td id=3D"BOTTOM_L1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: repeat-y;" width=3D"2px"><img src=3D"sacor=
e:empty.gif" width=3D"1px" height=3D"1px"></td>
	                    <td id=3D"BOTTOM_C1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: repeat; background-position: left bottom;"=
>
	                        <table style=3D"margin: 0pt; border: 0pt none;" ce=
llpadding=3D"0" cellspacing=3D"0" width=3D"100%">
	                            <tbody><tr>
	                                <td style=3D"padding: 0pt; border: 0pt non=
e;" width=3D"15px"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1p=
x"></td>
	                                <td id=3D"" style=3D"padding: 0pt; border:=
 0pt none; background-repeat: repeat;">
	                                    <table style=3D"border: 0pt none;" cel=
lpadding=3D"0" cellspacing=3D"0" width=3D"100%">
	                                        <tbody><tr><td style=3D"padding: 0=
pt; border: 0pt none;"><img src=3D"sacore:empty.gif" width=3D"1px" height=
=3D"1px"></td></tr>
	                                        <tr>
	                                            <td id=3D"SATITLE1d66kfm" clas=
s=3D"sastyle_text_contentclass" style=3D"padding: 0pt; border: 0pt none; fo=
nt-weight: bold;">
    	                                            &nbsp;
	                                            </td>
	                                        </tr>
	                                        <tr>
	                                            <td id=3D"DOMAIN1d66kfm" class=
=3D"sastyle_text_contentclass" style=3D"padding: 0pt; border: 0pt none;">
    	                                            &nbsp;
	                                            </td>
	                                        </tr>
											<tr>
	                                            <td id=3D"WARN_TB1d66kfm" clas=
s=3D"sastyle_link_moreinfo" style=3D"padding: 0pt; border: 0pt none;"><a id=
=3D"WARN_LINK1d66kfm" href=3D"#" target=3D"_blank" style=3D"color: rgb(0, 0=
, 222);"></a></td>

	                                        </tr>
	                                        <tr><td style=3D"padding: 0pt; bor=
der: 0pt none;"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px">=
</td></tr>
	                                    </tbody></table>
	                                </td>
	                                <td id=3D"" style=3D"padding: 0pt; border:=
 0pt none; background-repeat: repeat-y;" width=3D"2px"><img src=3D"sacore:e=
mpty.gif" width=3D"1px" height=3D"1px"></td>
	                            </tr>
	                            <tr>
	                                <td style=3D"padding: 0pt; border: 0pt non=
e; height: 40px;"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px=
"></td>
	                                <td style=3D"padding: 0pt; border: 0pt non=
e;">
	                                    <table style=3D"margin: 0pt; border: 0=
pt none;" cellpadding=3D"0" cellspacing=3D"0" width=3D"100%" height=3D"100%=
">
	                                        <tbody><tr>
	                                            <td id=3D"BOTTOM_LEFT1d66kfm" =
style=3D"padding: 0pt; border: 0pt none;" valign=3D"top">
	                                                <table style=3D"margin: 0p=
t; border: 0pt none;" cellpadding=3D"0" cellspacing=3D"0" width=3D"100%" he=
ight=3D"100%">
	                                                    <tbody><tr>
	                                                        <td id=3D"FACET_IM=
AGE_01d66kfm" style=3D"padding: 0pt; border: 0pt none;" valign=3D"middle" w=
idth=3D"21px" height=3D"0px"><img src=3D"sacore:empty.gif" width=3D"1px" he=
ight=3D"1px"></td>
=20
	                                                        <td id=3D"FACET_RE=
CCOMENDATION_01d66kfm" class=3D"sastyle_text_facetrec" style=3D"padding: 0p=
t; border: 0pt none;"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D=
"1px"></td>

	                                                    </tr>
	                                                    <tr>
	                                                        <td id=3D"FACET_IM=
AGE_11d66kfm" style=3D"padding: 0pt; border: 0pt none;" valign=3D"middle" h=
eight=3D"0px"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></=
td>=20
	                                                        <td id=3D"FACET_RE=
CCOMENDATION_11d66kfm" class=3D"sastyle_text_facetrec" style=3D"padding: 0p=
t; border: 0pt none;"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D=
"1px"></td>

	                                                    </tr>
	                                                    <tr>
	                                                        <td id=3D"FACET_IM=
AGE_21d66kfm" style=3D"padding: 0pt; border: 0pt none;" valign=3D"middle" h=
eight=3D"0px"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></=
td>=20
	                                                        <td id=3D"FACET_RE=
CCOMENDATION_21d66kfm" class=3D"sastyle_text_facetrec" style=3D"padding: 0p=
t; border: 0pt none;"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D=
"1px"></td>

	                                                    </tr>
	                                                    <tr>
	                                                        <td colspan=3D"2" =
class=3D"sastyle_link_moreinfo" style=3D"padding: 0pt; border: 0pt none;"><=
a id=3D"DOSSIER_LINK1d66kfm" href=3D"#" target=3D"_blank" style=3D"text-dec=
oration: underline; color: rgb(0, 0, 222);"></a></td>

	                                                    </tr>
	                                                </tbody></table>
	                                            </td>
	                                            <td id=3D"BOTTOM_SEP1d66kfm" s=
tyle=3D"padding: 0pt; border-left: 1px solid Gray; border-bottom: 0pt none;=
 visibility: hidden;" width=3D"10px" height=3D"100%"><img src=3D"sacore:emp=
ty.gif" width=3D"10px" height=3D"1px"></td>

	                                            <td id=3D"BOTTOM_RIGHT1d66kfm"=
 style=3D"padding: 0pt; border: 0pt none;" class=3D"sastyle_text_contentcla=
ss" valign=3D"top" width=3D"50%">
	                                                <table style=3D"margin: 0p=
t; border: 0pt none;" cellpadding=3D"0" cellspacing=3D"0" width=3D"100%">
	                                                    <tbody><tr>
	                                                        <td id=3D"CCHeader=
1d66kfm" colspan=3D"2" class=3D"sastyle_text_contentclass" style=3D"padding=
: 0pt; border: 0pt none; font-weight: bold;" width=3D"100%">
	                                                        </td>
	                                                    </tr>
	                                                    <tr>
	                                                        <td id=3D"CC_IMAGE=
_01d66kfm" style=3D"padding: 0pt; border: 0pt none;" valign=3D"middle" widt=
h=3D"8px" height=3D"0px"><img src=3D"sacore:empty.gif" width=3D"1px" height=
=3D"1px"></td>
=20
	                                                        <td id=3D"CC_DESC_=
01d66kfm" class=3D"sastyle_text_contentclass" style=3D"padding: 0pt; border=
: 0pt none;"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></t=
d>
	                                                    </tr>
	                                                    <tr>
	                                                        <td id=3D"CC_IMAGE=
_11d66kfm" style=3D"padding: 0pt; border: 0pt none;" valign=3D"middle" heig=
ht=3D"0px"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></td>=
=20
	                                                        <td id=3D"CC_DESC_=
11d66kfm" class=3D"sastyle_text_contentclass" style=3D"padding: 0pt; border=
: 0pt none;"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></t=
d>
	                                                    </tr>
	                                                    <tr>
	                                                        <td id=3D"CC_IMAGE=
_21d66kfm" style=3D"padding: 0pt; border: 0pt none;" valign=3D"middle" heig=
ht=3D"0px"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></td>=
=20
	                                                        <td id=3D"CC_DESC_=
21d66kfm" class=3D"sastyle_text_contentclass" style=3D"padding: 0pt; border=
: 0pt none;"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></t=
d>
	                                                    </tr>
	                                                    <tr>
	                                                        <td colspan=3D"2" =
class=3D"sastyle_link_moreinfo" style=3D"padding: 5px 0pt 0pt; border: 0pt =
none;">
	                                                            <a style=3D"te=
xt-decoration: none; margin-right: 10px;" id=3D"CCDesc1d66kfm" href=3D"#" t=
arget=3D"_blank"></a>
	                                                        </td>
	                                                    </tr>	                =
                               =20
	                                                </tbody></table>	         =
                                  =20
	                                            </td>
	                                        </tr>
	                                    </tbody></table>
	                                </td>
	                                <td style=3D"padding: 0pt; border: 0pt non=
e;" width=3D"10px"><img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1p=
x"></td>
	                            </tr>
	                            <tr><td id=3D"UPSELL_BORDER1d66kfm" colspan=3D=
"3" style=3D"padding: 0pt; border-left: 0pt none; border-bottom: 0pt none; =
visibility: hidden;" align=3D"right" width=3D"100%"><img id=3D"UPSELL_SEP1d=
66kfm" src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></td>
</tr>
	                            <tr>
	                                <td id=3D"UPSELL1d66kfm" colspan=3D"3" sty=
le=3D"padding: 0pt; border: 0pt none; text-align: right;" align=3D"right">
	                                    <img src=3D"sacore:empty.gif" width=3D=
"1px" height=3D"1px"><a class=3D"sastyle_link_upsell" style=3D"text-decorat=
ion: none; margin-right: 10px; color: rgb(0, 0, 222);" id=3D"UPSELL_LINK1d6=
6kfm" href=3D"#" target=3D"_blank"></a>
	                                </td>
	                            </tr>
	                        </tbody></table>
	                    </td>
	                    <td id=3D"BOTTOM_R1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: repeat-y;" width=3D"2px"><img src=3D"sacor=
e:empty.gif" width=3D"1px" height=3D"1px"></td>
	                </tr>
	            </tbody></table>           =20
            </td>
        </tr>	   =20
        <tr>
            <td style=3D"padding: 0pt; border: 0pt none; width: 100%;">
	            <table id=3D"FOOTER_ROW1d66kfm" style=3D"margin: 0pt; border: =
0pt none; width: 100%; height: 100%;" cellpadding=3D"0" cellspacing=3D"0">
	                <tbody><tr>
	                    <td id=3D"FOOTER_L1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: no-repeat;" width=3D"9px" height=3D"9px"><=
img src=3D"sacore:empty.gif" width=3D"1px" height=3D"1px"></td>
	                    <td id=3D"FOOTER_C1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: repeat-x;"><img src=3D"sacore:empty.gif" w=
idth=3D"1px" height=3D"1px"></td>
	                    <td id=3D"FOOTER_R1d66kfm" style=3D"padding: 0pt; bord=
er: 0pt none; background-repeat: no-repeat;" width=3D"9px"><img src=3D"saco=
re:empty.gif" width=3D"1px" height=3D"1px"></td>
	                </tr>
	            </tbody></table>           =20
            </td>
        </tr>	   =20
	</tbody></table>


</div>

--000e0cd32a10ae76f7049aa0db9b--

From autumn.liu@ericsson.com  Mon Jan 24 16:49:21 2011
Return-Path: <autumn.liu@ericsson.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE9543A69E2 for <mpls-tp@core3.amsl.com>; Mon, 24 Jan 2011 16:49:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCPUX8xJvULp for <mpls-tp@core3.amsl.com>; Mon, 24 Jan 2011 16:49:21 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id F259F3A698D for <mpls-tp@ietf.org>; Mon, 24 Jan 2011 16:49:20 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p0P1WdhT029123; Mon, 24 Jan 2011 19:32:41 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 24 Jan 2011 19:52:11 -0500
From: Autumn Liu <autumn.liu@ericsson.com>
To: Loa Andersson <loa@pi.nu>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Mon, 24 Jan 2011 19:52:10 -0500
Thread-Topic: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
Thread-Index: Acu6awwdonV20mZWQ/+o3Mpk26xWFABvwPaA
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51CDD60029@EUSAACMS0703.eamcs.ericsson.se>
References: <4D3B30A3.1030607@pi.nu>
In-Reply-To: <4D3B30A3.1030607@pi.nu>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: zh-CN, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2011 00:49:22 -0000

Support.

-Autumn

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf =
Of Loa Andersson
Sent: Saturday, January 22, 2011 11:32 AM
To: mpls-tp@ietf.org
Cc: draft-fang-mpls-tp-security-framework@tools.ietf.org; mpls@ietf.org; MP=
LS-TP ad hoc team
Subject: [mpls-tp] poll on making draft-fang-mpls-tp-security-framework-04 =
a working group document

Working Group,

this is to start a two week poll on making

draft-fang-mpls-tp-security-framework-04

an MPLS working group document!

Please send your responses to the mpls-tp@ietf.org mailing list.

The poll ends Feb 6, 2011.

Loa, George and Ross
mpls wg co-chairs


--=20


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

From talmi@marvell.com  Tue Jan 25 01:17:53 2011
Return-Path: <talmi@marvell.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96E523A697D; Tue, 25 Jan 2011 01:17:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.553
X-Spam-Level: 
X-Spam-Status: No, score=-5.553 tagged_above=-999 required=5 tests=[AWL=0.161,  BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,  RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CcfDZTREyKLA; Tue, 25 Jan 2011 01:17:52 -0800 (PST)
Received: from na3sys009aog101.obsmtp.com (na3sys009aog101.obsmtp.com [74.125.149.67]) by core3.amsl.com (Postfix) with SMTP id 910193A63CB; Tue, 25 Jan 2011 01:17:52 -0800 (PST)
Received: from source ([65.219.4.130]) (using TLSv1) by na3sys009aob101.postini.com ([74.125.148.12]) with SMTP ID DSNKTT6V8RVUe7Qsz5wnivq4GyYyBR0ZW4Ad@postini.com; Tue, 25 Jan 2011 01:20:50 PST
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.2.213.0; Tue, 25 Jan 2011 01:18:56 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Tue, 25 Jan 2011 11:18:54 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Tue, 25 Jan 2011 11:18:55 +0200
Thread-Topic: [OPSAWG] [mpls-tp] New version of draft-ietf-opsawg-oam-overview
Thread-Index: Acu8cOO9h2VkdrA6SP2GTxdBMRAg2w==
Message-ID: <74470498B659FA4687F0B0018C19A89CFCDC146E6C@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89CFCDC146E6CILMB01marvell_"
MIME-Version: 1.0
Subject: [mpls-tp] [OPSAWG]  New version of draft-ietf-opsawg-oam-overview
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2011 09:17:53 -0000

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

Hi,

We have posted an updated version, addressing all of the comments we receiv=
ed for the previous version.
Any further comments will be welcome.
http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-03

Regards,
Tal.


--_000_74470498B659FA4687F0B0018C19A89CFCDC146E6CILMB01marvell_
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=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Device Font 10cpi";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Device Font 10cpi";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>We have posted an updated version, addressing all of the=
 comments
we received for the previous version.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Any further comments will be welcome.<o:p></o:p></span><=
/font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><a
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-03">http:=
//tools.ietf.org/html/draft-ietf-opsawg-oam-overview-03</a><o:p></o:p></spa=
n></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Tal.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Device Font 10cpi"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--_000_74470498B659FA4687F0B0018C19A89CFCDC146E6CILMB01marvell_--

From yaacov.weingarten@nsn.com  Thu Jan 27 00:50:10 2011
Return-Path: <yaacov.weingarten@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 955AF28C113; Thu, 27 Jan 2011 00:50:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.617
X-Spam-Level: 
X-Spam-Status: No, score=-4.617 tagged_above=-999 required=5 tests=[AWL=1.981,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRlWq7d-xJyb; Thu, 27 Jan 2011 00:50:09 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 1FA4F28C114; Thu, 27 Jan 2011 00:50:07 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0R8r9JA022482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 27 Jan 2011 09:53:09 +0100
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0R8r7dG013114; Thu, 27 Jan 2011 09:53:08 +0100
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 27 Jan 2011 09:53:02 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBBDFF.9A652EDF"
Date: Thu, 27 Jan 2011 09:53:00 +0100
Message-ID: <62D9AC1F11702146A0387CBFF3A8CD3D0341CB65@DEMUEXC030.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New version of Linear Protection draft
thread-index: Acu9/5lU5bWoA+wJRx6rfwyPltTfoA==
From: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>
To: <mpls-tp@ietf.org>, <mpls@ietf.org>
X-OriginalArrivalTime: 27 Jan 2011 08:53:02.0191 (UTC) FILETIME=[9AD14FF0:01CBBDFF]
Cc: mpls-chairs@tools.ietf.org
Subject: [mpls-tp] New version of Linear Protection draft
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 08:50:10 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBBDFF.9A652EDF
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

I have just uploaded a new version of
draft-ietf-mpls-tp-linear-protection.  This draft includes some small
changes to the text to reflect comments that were received by the
editors.  In addition, there is a new appendix to the document that
includes a State Machine table that reflects the description of the PSC
operation (as described in section 4.3.3).  This state machine table is
informative, with the text in section 4.3.3 being the normative
description.

Any comments or suggestions for improvements are welcome.

Best regards,
Yaacov Weingarten
Nokia Siemens Networks
Industry Environment, PTE
ph#:  +972-9-775 1827
mob#: +972-54-220 0977



------_=_NextPart_001_01CBBDFF.9A652EDF
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>New version of Linear Protection draft</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Hi all,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I have =
just uploaded a new version of =
draft-ietf-mpls-tp-linear-protection.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> This draft includes =
some small changes to the text to reflect comments that were received by =
the editors.&nbsp; In addition, there is a new appendix to the document =
that includes a State Machine table that re</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">flects the description of =
the PSC operation (as described in section 4.3.3).&nbsp; This state =
machine table is informative, with the text in section 4.3.3 being the =
normative de</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">scription.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Any =
comments or suggestions for improvements are welcome.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Best =
regard</FONT><FONT SIZE=3D2 FACE=3D"Comic Sans MS">s,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B><I></I></B></SPAN><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><B><I><SPAN =
LANG=3D"de-de"></SPAN></I></B><B><I><SPAN LANG=3D"de-de"><FONT =
COLOR=3D"#800080" FACE=3D"Lucida Calligraphy">Yaacov =
Weingarten</FONT></SPAN></I></B><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"de-de"></SPAN></B></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">Nokia Siemens Networks</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">Industry Environment, PTE</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">ph#:&nbsp; +972-9-775 1827</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">mob#: +972-54-220 0977</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01CBBDFF.9A652EDF--

From danfrost@cisco.com  Thu Jan 27 04:22:47 2011
Return-Path: <danfrost@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D803A3A6452 for <mpls-tp@core3.amsl.com>; Thu, 27 Jan 2011 04:22:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.398
X-Spam-Level: 
X-Spam-Status: No, score=-10.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7JodUa1j+Em for <mpls-tp@core3.amsl.com>; Thu, 27 Jan 2011 04:22:47 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 84E5C3A6405 for <mpls-tp@ietf.org>; Thu, 27 Jan 2011 04:22:46 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 27 Jan 2011 12:25:49 +0000
Received: from isolaria.cisco.com (isolaria.cisco.com [64.100.19.13]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0RCPnZX013731; Thu, 27 Jan 2011 12:25:49 GMT
Received: from isolaria.cisco.com (isolaria [127.0.0.1]) by isolaria.cisco.com (8.13.1/8.13.1) with ESMTP id p0RCPnTL029436; Thu, 27 Jan 2011 07:25:49 -0500
Received: (from danfrost@localhost) by isolaria.cisco.com (8.13.1/8.13.1/Submit) id p0RCPmNN029435; Thu, 27 Jan 2011 12:25:48 GMT
Date: Thu, 27 Jan 2011 12:25:48 +0000
From: Dan Frost <danfrost@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <20110127122548.GB27233@cisco.com>
References: <4D40C5DB.4000708@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D40C5DB.4000708@joelhalpern.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] Requested review of draft-frost-mpls-tp-loss-delay-profile-00
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 12:22:48 -0000

Hi Joel,

On Wed, Jan 26, 2011 at 08:09:47PM -0500, Joel M. Halpern wrote:
> At the chairs request, I have reviewed this document.  This document
> appears to be in good shape.  I have three minor comments that may be
> helpful.

Many thanks for your feedback!  Note that the current version of the
document is draft-ietf-mpls-tp-loss-delay-profile-01.

> 1) In the discussion of the delay measurement, the list of parameters
> whose negotiation is to be skipped does not match the list of default
> values.  Specifically, the parameter list does not include the T flag.

This is fixed in the current version.

> 2) There is something slightly confusing in the wording that is used
> in both the loss and delay sections about the setting of these
> parameters.  The wording is: A simple implementation may assume
> externally-determined configuration and need only support the
> functionality required by these defaults.
> 
> The reason I get confused is that "configured" is not the same as
> "forced to the defaults."  I believe that the intent is for something
> like: A simple implementation may assume that external configuration
> will ensure that both ends of the communication are using the default
> values for these parameters.

Your wording is clearer and we'll adopt it; thanks!

> 3) For the Loss measurements, should there be some explanation (a
> single sentence?) for why it is believed that 32 bit counters are
> appropriate when the protocol design allows for 64?  (Or is there
> something elsewhere in the MPLS-TP specs that says that MPLS-TP
> interfaces will always use 32 bit counters?  Or is the intention to
> mandate here such a hardware-oriented restriction?)

I would prefer to remove this parameter from the list, and propose to do
so.  The X flag mechanism is such that LM will work automatically
whether the endpoints have the same 32/64 capability or not, so there
doesn't seem to be a need to declare a default.

Cheers,

-d

> Yours, Joel

From ben@niven-jenkins.co.uk  Fri Jan 28 03:57:43 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36E423A67F6; Fri, 28 Jan 2011 03:57:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.243
X-Spam-Level: 
X-Spam-Status: No, score=-103.243 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PjaxLSGk--2i; Fri, 28 Jan 2011 03:57:41 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id 6B4C13A67C0; Fri, 28 Jan 2011 03:57:41 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-113-devlan.cachelogic.com) by mail6.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1Pin0P-0005t8-QT; Fri, 28 Jan 2011 12:00:46 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=windows-1252
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <00bc01cbb1c9$8ceac4d0$790c7c0a@china.huawei.com>
Date: Fri, 28 Jan 2011 12:00:42 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <C60D23CB-D202-48F5-B925-42E0F4320E72@niven-jenkins.co.uk>
References: <002901cbadf8$66783640$790c7c0a@china.huawei.com> <20110107112641.GA20790@cisco.com> <014901cbaebf$4fc5f0f0$790c7c0a@china.huawei.com> <AANLkTikS9hbL7fFA665qU=TwCVpvOyhsYYkDAtbS8FT-@mail.gmail.com> <9BCECFE9-04D8-4E8F-A01A-55D76C0E64C9@niven-jenkins.co.uk> <009501cbb0e3$665cbe90$790c7c0a@china.huawei.com> <48AA81F4-C02E-48F5-95BF-0159CFAB682C@niven-jenkins.co.uk> <00bc01cbb1c9$8ceac4d0$790c7c0a@china.huawei.com>
To: Linda Dunbar <ldunbar@huawei.com>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: mpls-tp@ietf.org, mpls@ietf.org
Subject: Re: [mpls-tp] [mpls] Questions on "draft-ietf-mpls-loss-delay-00"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jan 2011 11:57:43 -0000

Linda,


On 11 Jan 2011, at 19:55, Linda Dunbar wrote:

> Ben and colleagues:
>=20
> You said " But you suggest edit does not suggest a slower transmission =
rate it states the querier should stop transmission",
>=20
> Two comments:
>=20
> 1.      I think =93slower transmission rate by querier=94 should be =
included in the text.
>=20

So the model would be that a querier starts with a slow transmission =
rate and they increase its transmission rate to the actual desired =
transmission rate over time?

I don't see the need for that.

Your concerns that lead to wanting such behaviour (if I have understood =
them correctly) are:
1) There is a processing cost on the receiver and that cost may be too =
high for a given receiver (e.g. rate is faster than it supports)
2) The sender may waste resources counting before the receiving end is =
ready.

(1) is common in a number of situations (e.g. control packets that need =
to be sent to a central CPU and therefore take a slow path through a =
router) and is generally dealt with by applying a rate limit on that =
particular traffic on the slow path. I'd argue such an approach is =
sufficient for LM.

(2) is a local implementation decision on the querier so let's not bog =
the document down with implementation specifics.

I would therefore suggest the following:

When initiating an LM operation, the far end may require a period of =
time to become ready for the requested measurement operation or the far =
end may not be able to support the requested measurement. Under those =
circumstances, LM queries MAY simply be discarded, and the querier =
expecting a response SHOULD be prepared for this situation. =
Alternatively, the receiver MAY respond, possibly in a rate-limited =
manner, to queries received during this period with an appropriate =
notification code.  The querier should abort the measurement after not =
receiving any positive feedback when a specified timer expires. =20

Your proposed text for 2.7.10 on LM interval looks OK to me.

Ben


> 2.      I suggested that querier may choose not starting counting (not =
transmission) until a positive feedback from Far End has been received.
>=20
>=20
> Based on the discussion over this email thread, do people think the =
following text is more appropriate?
>=20
>=20
> When initiating an LM operation, the far end may require a period of =
time to become ready for the requested measurement operation or the far =
end may not be able to support the requested measurement. During this =
period Under those circumstances, LM queries MAY simply be discarded, =
and the querier expecting a response SHOULD be prepared for this =
situation. The frequency of the initial LM for requesting starting the =
measurement should be slow, so that there is enough time for far end to =
check if the requested measurement can be done. The querier should abort =
the measurement after not receiving any positive feedback when a =
specified timer expires. setting a timer to differentiate between an =
acceptable initialization delay and a permanent unavailability condition =
at the far end. Alternatively, the receiver MAY respond, possibly in a =
rate-limited manner, to queries received during this period with an =
appropriate notification code. Since counting transmitted packets at =
querier side will cost extra resources (or is not free), the querier =
doesn=92t need to start counting its transmitted packets until receiving =
a positive feedback from the far-end.
>=20
>=20
>=20
> Suggested text for LM/DM Interval:
>=20
>=20
> 2.7.10: LM Interval
>=20
>=20
> The interval may affect the accuracy of the packet loss count. =46rom =
implementation point of view, the shorter the interval, the higher the =
processing cost to equipment. Querier should encode its intended =
interval in its LM Message. If the interval specified by the LM message =
can=92t be supported by the far end, the far end can simply ignore the =
LM requests by not responding anything or respond with an appropriate =
notification code indicating its minimum allowed LM interval. =20
>=20
>=20
> In the Section 3.1 LM Message Format, add an 8 (or 16) bits field for =
LM Interval. The Interval Unit should be in ms.
>=20
>=20
> Linda Dunbar
>=20
> -----Original Message-----
> From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk]
> Sent: Monday, January 10, 2011 11:29 AM
> To: Linda Dunbar
> Cc: 'Greg Mirsky'; mpls@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls-tp] [mpls] Questions on =
"draft-ietf-mpls-loss-delay-00"
>=20
> Linda,
>=20
> On 10 Jan 2011, at 16:28, Linda Dunbar wrote:
>=20
> > From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk]
>=20
> >
>=20
> > 1) The edits suggested by Linda change the semantics from suggesting =
a querier maintain a timer to allow for the receiving end to "get its =
act together" to if the receiving end doesn't get its act together =
within X packets stop sending LM. Is that really what's intended? I =
would expect the time taken for the receiving end "to get its act =
together" would not be a function of the LM transmission rate and =
therefore using transmission rate to guess whether the receiving end is =
dead Vs getting itself ready doesn't sound sensible.
>=20
> >
>=20
> >
>=20
> > [Linda] The reason for suggesting Initiator to have slower =
transmission rate is to minimize processing needed at the Initiator =
before Far End committing to the counting.
>=20
> >
>=20
> But you suggest edit does not suggest a slower transmission rate it =
states the querier should stop transmission!
>=20
> > We have considered implementing this feature on our products and =
discovered that it DOES take some time for the Central CPU to receive =
the Counting Request (as LM in this draft), check if the requested =
Counting can be supported, pass the request to the corresponding line =
card, and get confirmation from the Line card. Sometimes, the Far End =
can't perform the requested Counting because it is performing counting =
for requests from other nodes.
>=20
> >
>=20
> I accept that a receiver may take some time to configure itself for =
counting and that the time it takes may be a function of other things it =
is doing. What I am saying is that the time it takes is never a function =
of the interval being configured.
>=20
> > 2) I don't like the final sentence suggesting queriers should delay =
counting transmitted packets until receiving a positive response because =
doing so costs resources. It sounds like an internal implementation =
decision that has nothing to do with interoperability and therefore =
irrelevant.
>=20
> >
>=20
> >
>=20
> > [Linda]I agree with your point that that the Source Node performing =
or not performing the counting before receiving the positive feedback =
from Far End is not interoperability issue. Maybe it can be a =
recommendation?
>=20
> >
>=20
> > But it is necessary for Source node to abort the effort after not =
receiving the positive feedback after sometime (like X number of LM or =
timer expires).
>=20
> >
>=20
> At some point, if the querier has not received a positive response it =
must abort the operation. The original text suggest maintaing a timer. =
Your edit suggested making ti a function of packets sent. I am saying =
the former seems more sensible than the latter to me.
>=20
> > 4) Giving the receiving end the opportunity to reply with "I can;t =
support the rate you're asking for it's too fast for me" sounds =
attractive but I am not sure it is in practice if one thinks how such =
functionality is likely to be used. If an operator is going to turn it =
on with the thinking that performing LM of some sort is important =
regardless of the LM interval then negotiating a shorter interval may =
have value. However I don't expect that to be the case. I would expect =
an operator to pre-plan what interval they need given their knowledge of =
their network and the accuracy they desire, having the network change =
that may well cause unexpected consequences. In such a scenario I think =
it's better to let the receiver "hard fail" and the operator can =
investigate rather than have the network re-configure and the =
re-configuration go unnoticed, after all LM failing does not impact the =
ability of the network to actually forward packets.
>=20
> >
>=20
> >
>=20
> > [Linda] Do you mean that Receiver can ignore the LMs if the Interval =
specified in the message is more than it can handle?
>=20
> That is one option.
>=20
> The background to my thinking is:
>=20
> I assume that LM will be turned on explicitly (i.e. it will not be on =
by default)
>=20
> I assume that LM is turned on for a reason, e.g. because an operator =
needs to support an SLA involving packet loss.
>=20
> The interval may affect the accuracy of the packet loss count.
>=20
> I expect operators would rather LM "hard fail" rather than have the =
network re-configure automatically to a different interval because an =
SLA calculation (or whatever else is relying on the LM) could become =
inaccurate and no-one would know unless they really dug deep into what =
the network was doing.
>=20
> The network re-configuring itself in order to repair itself so it can =
continue to forward packets is one thing.
>=20
> The network reconfiguring non-forwarding related features itself =
because it believes it knows what to do better than the person who =
designed & configured it could lead to all sorts of trouble in the field =
IMO.
>=20
> Ben
>=20
> =20
>=20

