
From daniele.ceccarelli@ericsson.com  Mon Mar  1 01:57:30 2010
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC7B23A8927 for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 01:57:30 -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 EqvfccSAm866 for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 01:57:30 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id E61BB3A8921 for <ccamp@ietf.org>; Mon,  1 Mar 2010 01:57:29 -0800 (PST)
X-AuditID: c1b4fb39-b7c2dae000007b99-d1-4b8b8f88cc7f
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 15.FD.31641.88F8B8B4; Mon,  1 Mar 2010 10:57:28 +0100 (CET)
Received: from EITRMMW021.eemea.ericsson.se ([141.137.48.176]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 1 Mar 2010 10:57:27 +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-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 1 Mar 2010 10:57:26 +0100
Message-ID: <EA652A17BAD6A24DBB3BF8146892D215097F607C@EITRMMW021.eemea.ericsson.se>
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
Thread-Index: Acq3LhTmuSG/kxGCTt+1iMNqBtXcygB93aYg
References: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
From: "Daniele Ceccarelli" <daniele.ceccarelli@ericsson.com>
To: "CCAMP" <ccamp@ietf.org>
X-OriginalArrivalTime: 01 Mar 2010 09:57:27.0971 (UTC) FILETIME=[99DB8730:01CAB925]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [CCAMP] [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 09:57:31 -0000

 Yes/Support

BR
Daniele

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of =
BRUNGARD, DEBORAH A (ATTLABS)
Sent: venerd=EC 26 febbraio 2010 22.53
To: CCAMP
Cc: mpls@ietf.org; pwe3@ietf.org; mpls-tp@ietf.org
Subject: [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework

All,

This is to start a two week working group poll on making =
draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working =
group document. This poll is being initiated at this time as this =
document is part of the MPLS-TP work and it is needed to progress the =
work.

Send your response to the ccamp@ietf.org mailing list (only), indicating =
"yes/support" or "no/do not support".

This poll ends March 12th.

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

From david.i.allan@ericsson.com  Mon Mar  1 07:52:26 2010
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 698F628C3D0; Mon,  1 Mar 2010 07:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ewwq+2LA8J1r; Mon,  1 Mar 2010 07:52:25 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 8542B28C2EC; Mon,  1 Mar 2010 07:52:25 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o21FsQ8n009450; Mon, 1 Mar 2010 09:54:46 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Mon, 1 Mar 2010 10:52:21 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: CCAMP <ccamp@ietf.org>, "ccamp-bounces@ietf.org" <ccamp-bounces@ietf.org>
Date: Mon, 1 Mar 2010 10:52:19 -0500
Thread-Topic: [PWE3] poll on	draft-abfb-mpls-tp-control-plane-framework
Thread-Index: Acq42zJoPTaKvuXeSRmnsscekhwCPQAd72Pw
Message-ID: <60C093A41B5E45409A19D42CF7786DFD4F99126FA5@EUSAACMS0703.eamcs.ericsson.se>
References: <077E41CFFD002C4CAB7DFA4386A5326401E4DB2C@DEMUEXC014.nsn-intra.net> <OF26B22EE7.C97514FF-ON482576D9.0005D830-482576D9.0005B6B4@zte.com.cn>
In-Reply-To: <OF26B22EE7.C97514FF-ON482576D9.0005D830-482576D9.0005B6B4@zte.com.cn>
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_60C093A41B5E45409A19D42CF7786DFD4F99126FA5EUSAACMS0703e_"
MIME-Version: 1.0
Subject: Re: [CCAMP] [PWE3] poll on	draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 15:52:26 -0000

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

Yes/Support

D

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
ext BRUNGARD, DEBORAH A (ATTLABS)
Sent: Friday, February 26, 2010 11:53 PM
To: CCAMP
Cc: mpls@ietf.org; pwe3@ietf.org; mpls-tp@ietf.org
Subject: [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework

All,

This is to start a two week working group poll on making
draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working
group document. This poll is being initiated at this time as this
document is part of the MPLS-TP work and it is needed to progress the
work.

Send your response to the ccamp@ietf.org mailing list (only), indicating
"yes/support" or "no/do not support".

This poll ends March 12th.

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



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18385" name=3DGENERATOR></HEAD>
<BODY>
<DIV><TT><FONT size=3D2><SPAN class=3D791592115-01032010><FONT face=3DArial=
=20
color=3D#0000ff>Yes/Support</FONT></SPAN></FONT></TT></DIV>
<DIV><TT><FONT size=3D2><SPAN=20
class=3D791592115-01032010></SPAN></FONT></TT>&nbsp;</DIV>
<DIV><TT><FONT size=3D2><SPAN class=3D791592115-01032010><FONT face=3DArial=
=20
color=3D#0000ff>D</FONT>&nbsp;</SPAN><BR><BR>-----Original Message-----<BR>=
From:=20
pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of<BR>ext=20
BRUNGARD, DEBORAH A (ATTLABS)<BR>Sent: Friday, February 26, 2010 11:53 PM<B=
R>To:=20
CCAMP<BR>Cc: mpls@ietf.org; pwe3@ietf.org; mpls-tp@ietf.org<BR>Subject: [PW=
E3]=20
poll on draft-abfb-mpls-tp-control-plane-framework<BR><BR>All,<BR><BR>This =
is to=20
start a two week working group poll on=20
making<BR>draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp=20
working<BR>group document. This poll is being initiated at this time as=20
this<BR>document is part of the MPLS-TP work and it is needed to progress=20
the<BR>work.<BR><BR>Send your response to the ccamp@ietf.org mailing list=20
(only), indicating<BR>"yes/support" or "no/do not support".<BR><BR>This pol=
l=20
ends March=20
12th.<BR><BR>Deborah<BR>_______________________________________________<BR>=
pwe3=20
mailing=20
list<BR>pwe3@ietf.org<BR>https://www.ietf.org/mailman/listinfo/pwe3<BR>____=
___________________________________________<BR>CCAMP=20
mailing=20
list<BR>CCAMP@ietf.org<BR>https://www.ietf.org/mailman/listinfo/ccamp<BR><B=
R></FONT></TT><BR></DIV></BODY></HTML>

--_000_60C093A41B5E45409A19D42CF7786DFD4F99126FA5EUSAACMS0703e_--

From jeff.tantsura@ericsson.com  Mon Mar  1 08:55:12 2010
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A9693A8ABB for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 08:55:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IF60KGO7duZF for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 08:55:12 -0800 (PST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id ECA0E3A898D for <ccamp@ietf.org>; Mon,  1 Mar 2010 08:55:11 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id o21GvSb6027590 for <ccamp@ietf.org>; Mon, 1 Mar 2010 10:57:30 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.197]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Mon, 1 Mar 2010 11:55:08 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: CCAMP <ccamp@ietf.org>
Date: Mon, 1 Mar 2010 11:54:55 -0500
Thread-Topic: [CCAMP] [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
Thread-Index: Acq3MCSkoixwZQzcTlCXUPTJHaoW1wCL6SeA
Message-ID: <0ED867EB33AB2B45AAB470D5A64CDBF604817E49FB@EUSAACMS0701.eamcs.ericsson.se>
References: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com> <8c99930d1002261407yc7328c2t128b8a60bfa07095@mail.gmail.com>
In-Reply-To: <8c99930d1002261407yc7328c2t128b8a60bfa07095@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [CCAMP] [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 16:55:12 -0000

yes/support

Regards,
Jeff =20



From lberger@labn.net  Mon Mar  1 09:17:14 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1E8E28C489 for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 09:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.731
X-Spam-Level: 
X-Spam-Status: No, score=-1.731 tagged_above=-999 required=5 tests=[AWL=0.535,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1V-GEcya3jE2 for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 09:17:13 -0800 (PST)
Received: from outbound-mail-01.bluehost.com (outbound-mail-01.bluehost.com [69.89.21.11]) by core3.amsl.com (Postfix) with SMTP id 64FFD28C10C for <ccamp@ietf.org>; Mon,  1 Mar 2010 09:17:13 -0800 (PST)
Received: (qmail 21906 invoked by uid 0); 1 Mar 2010 17:10:34 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy1.bluehost.com with SMTP; 1 Mar 2010 17:10:34 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=O34n6S3aaam2AZg93Y5wqMeD68weUMvoGm6ky6GmzxHXg8JDVDJWLEOu4atkW/2xhL9xRcyXskQ65aonDfZUaCd9vWb1lEIb7dHE5SNW+sv9oAqXzMQroo/CBpnMRUpy;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1Nm98b-0007oK-QO; Mon, 01 Mar 2010 10:10:34 -0700
Message-ID: <4B8BF527.4@labn.net>
Date: Mon, 01 Mar 2010 12:11:03 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20091214 Eudora/3.0b4
MIME-Version: 1.0
To: MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, MPLS-TP <mpls-tp@ietf.org>, CCAMP <ccamp@ietf.org>
References: <4B718C44.90001@labn.net> <4B753224.6070409@pi.nu> <4B756AD8.7090204@labn.net>
In-Reply-To: <4B756AD8.7090204@labn.net>
X-Enigmail-Version: 0.96a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Subject: Re: [CCAMP] EXTENDED: Poll on OAM related drafts to ccamp wg documents
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 17:17:14 -0000

This poll is now closed.

Authors,
	Please republish the drafts as draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext
and draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext with *no* other changes.

Please note that today is the Cut-off for initial document (-00)
submission by 17:00 PST (01:00 Tuesday, March 2 UTC).

Authors of ccamp-rsvp-te-mpls-tp-oam-ext, please also submit a -01
version of the draft-ietf-ccamp to address the comments raised and
discussed on this list once you are ready.

Thank you,
Lou

On 2/12/2010 9:51 AM, Lou Berger wrote:
> CCAMP, MPLS-TP, MPLS-TP ad hoc team,
> 
> Loa (and others) have correctly pointed out that this poll should have
> been announced on all three lists as it includes an MPLS-TP document.
> As the announcement on the other lists was delayed, the comment/poll
> period has been extended through Monday March 1.
> 
> Please send comments to the ccamp list.
> 
> Thank you,
> Lou (CCAMP co-chair)
> 
> On 2/12/2010 5:49 AM, Loa Andersson wrote:
>> MPLS-TP ad hoc team,
>>
>> please note that the ccamp working group in the IETF are polling
>> draft-bellagamba-ccamp-rsvp-te-mpls-tp-oam-ext to become a
>> working group docuemnt.
>>
>> Comments should be sent to ccamp working group mailing list.
>>
>> /Loa
>>
>> Lou Berger wrote:
>>> All,
>>>
>>> The authors of the drafts have stated that they are ready for this
>>> poll to resume.  Therefore:
>>>
>>> This message starts a two week poll on making the documents listed below
>>> ccamp working group documents.  Please send a mail to the mailing list
>>> indicating "yes/support to both" or "no/do not support either".  Of
>>> course, you may also support one but not the other.  (We will assume
>>> that you support/object to both if you don't specify.)  Please send
>>> mail even if you expressed an opinion on the prior poll.
>>>
>>> The documents being polled are:
>>>
>>> http://tools.ietf.org/html/draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext
>>> http://tools.ietf.org/html/draft-bellagamba-ccamp-rsvp-te-mpls-tp-oam-ext
>>>
>>> The poll ends Tuesday February 23.
>>>
>>> Much thanks,
>>> Lou
>>>
>>> -------- Original Message --------
>>> Subject: [CCAMP] Suspended: poll on making
>>> draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext-01.txt ccamp wg document
>>> Date: Tue, 01 Dec 2009 07:07:03 -0500
>>> From: Lou Berger <lberger@labn.net>
>>> To: ccamp@ietf.org
>>>
>>> The document authors have asked that we defer this poll until they make
>>> some further updates to this document.  The plan will be to re-poll the
>>> WG once the document authors inform us that the changes have been made.
>>>   Given recent discussion on the list, I expect that this poll will take
>>> place together with the other technology specific OAM document,
>>> draft-bellagamba-ccamp-rsvp-te-mpls-tp-oam-ext.
>>>
>>> Please keep in mind that becoming a WG document does not mean that the
>>> technical details of a document are frozen.  It does mean that the
>>> working group becomes the authoritative body for technical content,
>>> i.e., WG consensus drives a WG document while author consensus drives an
>>> individual document.
>>>
>>> Lou
>>>
>>> On 11/23/2009 5:20 PM, BRUNGARD, DEBORAH A (ATTLABS) wrote:
>>>> All,
>>>>
>>>> This is to start a two week poll on making
>>>> draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext-01.txt a ccamp working group
>>>> document. Send a mail to the mailing list indicating "yes/support" or
>>>> "no/do not support".
>>>>
>>>> The poll ends Monday, Dec. 7, 2009.
>>>>
>>>> Deborah
>>>> _______________________________________________
>>>> CCAMP mailing list
>>>> CCAMP@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> CCAMP mailing list
>>> CCAMP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>
>>>
>>>
>>> _______________________________________________
>>> CCAMP mailing list
>>> CCAMP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ccamp
>>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
> 
> 
> 

From root@core3.amsl.com  Mon Mar  1 12:15:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id DDFE128C16B; Mon,  1 Mar 2010 12:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100301201501.DDFE128C16B@core3.amsl.com>
Date: Mon,  1 Mar 2010 12:15:01 -0800 (PST)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 20:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : RSVP-TE Extensions for MPLS-TP OAM Configuration
	Author(s)       : E. Bellagamba, et al.
	Filename        : draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-00.txt
	Pages           : 18
	Date            : 2010-03-01

This specification is complementary to the GMPLS OAM Configuration
Framework [OAM-CONF-FWK] and describes technology specific aspects
for the configuration of pro-active MPLS Operations, Administration
and Maintenance (OAM) functions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From root@core3.amsl.com  Mon Mar  1 13:30:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id A5B5128C1C6; Mon,  1 Mar 2010 13:30:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100301213002.A5B5128C1C6@core3.amsl.com>
Date: Mon,  1 Mar 2010 13:30:02 -0800 (PST)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-general-constraint-encode-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 21:30:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : General Network Element Constraint Encoding for GMPLS Controlled Networks
	Author(s)       : G. Bernstein, et al.
	Filename        : draft-ietf-ccamp-general-constraint-encode-00.txt
	Pages           : 27
	Date            : 2010-02-18

Generalized Multiprotocol Label Switching can be used to control a
wide variety of technologies. In some of these technologies network
elements and links may impose additional routing constraints. An
example of such additional constraints occurs in wavelength switched
optical networks (WSON).

This document provides efficient, protocol-agnostic encodings for
general information elements representing connectivity and label
constraints as well as label availability. These encodings are
applicable to a wide range of technologies and not limited to WSON.
It is intended that protocol-specific documents will reference this
memo to describe how information is carried for specific uses.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-general-constraint-encode-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-general-constraint-encode-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From lberger@labn.net  Mon Mar  1 13:42:27 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE13428C1DA for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 13:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1qQyYnIFbDg for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 13:42:26 -0800 (PST)
Received: from outbound-mail-313.bluehost.com (outbound-mail-313.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id D0A9128C1D8 for <ccamp@ietf.org>; Mon,  1 Mar 2010 13:42:26 -0800 (PST)
Received: (qmail 25282 invoked by uid 0); 1 Mar 2010 21:42:27 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 1 Mar 2010 21:42:27 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=ejs8p/SRRfiUre/H/1Dsu14QNkVs7PxwFEy6cakp6KLw8eareRnmk+WgbzvrC+rZYn/ulpueqWKrcFdy7p69N74nLLgpUCEcHr8xHEtNeGGlUL6unBTDw25XpQw/KGTS;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1NmDNj-0007eE-0H for ccamp@ietf.org; Mon, 01 Mar 2010 14:42:27 -0700
Message-ID: <4B8C34D2.9050804@labn.net>
Date: Mon, 01 Mar 2010 16:42:42 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20091214 Eudora/3.0b4
MIME-Version: 1.0
To: CCAMP <ccamp@ietf.org>
References: <20100301213002.A5B5128C1C6@core3.amsl.com>
In-Reply-To: <20100301213002.A5B5128C1C6@core3.amsl.com>
X-Enigmail-Version: 0.96a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Subject: Re: [CCAMP] I-D Action:draft-ietf-ccamp-general-constraint-encode-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 21:42:27 -0000

Ccamp,
	Please note that this document contains material split off from
draft-ietf-ccamp-rwa-wson-encode as discussed at the last ietf.

Lou

On 3/1/2010 4:30 PM, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.
> 
> 
> 	Title           : General Network Element Constraint Encoding for GMPLS Controlled Networks
> 	Author(s)       : G. Bernstein, et al.
> 	Filename        : draft-ietf-ccamp-general-constraint-encode-00.txt
> 	Pages           : 27
> 	Date            : 2010-02-18
> 
> Generalized Multiprotocol Label Switching can be used to control a
> wide variety of technologies. In some of these technologies network
> elements and links may impose additional routing constraints. An
> example of such additional constraints occurs in wavelength switched
> optical networks (WSON).
> 
> This document provides efficient, protocol-agnostic encodings for
> general information elements representing connectivity and label
> constraints as well as label availability. These encodings are
> applicable to a wide range of technologies and not limited to WSON.
> It is intended that protocol-specific documents will reference this
> memo to describe how information is carried for specific uses.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-general-constraint-encode-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> 
> 
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp

From daniel@olddog.co.uk  Mon Mar  1 14:53:12 2010
Return-Path: <daniel@olddog.co.uk>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BB0928C1E5 for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 14:53:12 -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_52=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 ZRZcsckZO-QS for <ccamp@core3.amsl.com>; Mon,  1 Mar 2010 14:53:11 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id 6382928C1DD for <ccamp@ietf.org>; Mon,  1 Mar 2010 14:53:11 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id o21Mqv7A005676;  Mon, 1 Mar 2010 22:52:57 GMT
Received: from JAYNE (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id o21MquEr005667;  Mon, 1 Mar 2010 22:52:56 GMT
From: "Daniel King" <daniel@olddog.co.uk>
To: <ccamp@ietf.org>
References: <003601cab0e7$b5474040$1fd5c0c0$@co.uk>
In-Reply-To: <003601cab0e7$b5474040$1fd5c0c0$@co.uk>
Date: Mon, 1 Mar 2010 22:52:55 -0000
Message-ID: <027c01cab991$ef543470$cdfc9d50$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acqw57TEOgs0P+/hQGW/9xkKgEy11QIqZatg
Content-Language: en-gb
Cc: "'Brungard, Deborah A, ALABS'" <dbrungard@att.com>
Subject: Re: [CCAMP] Agenda Requests for IETF 77
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 22:53:12 -0000

Hello all,

Apologies but I was too generous with the time and we will need to compile
our CCAMP schedule by March 10th. Therefore, if you have not already sent
your request, please send your presentation/time requests by the end of week
(Sunday 7th). 

Thanks,
Dan

-----Original Message-----
From: Daniel King [mailto:daniel@olddog.co.uk] 
Sent: 18 February 2010 22:14
To: ccamp@ietf.org
Cc: 'Brungard, Deborah A, ALABS'; 'Lou Berger'; daniel@olddog.co.uk
Subject: Agenda Requests for IETF 77

Hello CCAMP'rs,

Please let us know if you have an agenda request for our CCAMP sessions at
IETF 77.  Reply to this email (please also CC the co-chairs) with the
desired duration, topic/draft title, and presenter for each slot that you
request. Please let us have your requests by Friday, March 12th. 

Key dates are at: http://www.ietf.org/meeting/cutoff-dates-2010.html#IETF77

2010-02-26 (Friday): Final agenda to be published.
2010-03-01 (Monday): Internet Draft Cut-off for initial document (-00)
submission by 17:00 PST (01:00 Tuesday, March 2 UTC), upload using IETF ID
Submission Tool.
2010-03-08 (Monday): Internet Draft final submission cut-off by 17:00 PST
(01:00 Tuesday, March 9 UTC), upload using IETF ID Submission Tool.

The preliminary agenda is at: https://datatracker.ietf.org/meeting/agenda/

Thanks,
Dan



From dschroet@cisco.com  Tue Mar  2 04:27:37 2010
Return-Path: <dschroet@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 864C43A8692 for <ccamp@core3.amsl.com>; Tue,  2 Mar 2010 04:27:37 -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 aaCpvyDHV1yO for <ccamp@core3.amsl.com>; Tue,  2 Mar 2010 04:27:36 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 627D93A8676 for <ccamp@ietf.org>; Tue,  2 Mar 2010 04:27:36 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.49,566,1262563200";  d="scan'208";a="3918630"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-2.cisco.com with ESMTP; 02 Mar 2010 11:55:01 +0000
Received: from dhcp-10-61-109-167.cisco.com (dhcp-10-61-109-167.cisco.com [10.61.109.167]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o22CRaHc020441; Tue, 2 Mar 2010 12:27:36 GMT
From: Dirk Schroetter <dschroet@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Mar 2010 13:27:35 +0100
Message-Id: <D65F36AB-049A-46C3-A70F-51D81DFB1E7A@cisco.com>
To: ccamp@ietf.org
Mime-Version: 1.0 (Apple Message framework v1077)
X-Mailer: Apple Mail (2.1077)
Subject: [CCAMP] New document uploaded: draft-schroetter-wson-ospf-link-info-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2010 12:27:37 -0000

Fellow CCampers,

I uploaded a new document at:

https://datatracker.ietf.org/doc/draft-schroetter-wson-ospf-link-info/

as a discussion document for the encoding of link information for WSON - =
and just saw that despite all the editing an error did stay in the =
document in that the first "OSPF" should have been a "WSON". My =
apologies.

Please fire away ...

Best Regards,

/Dirk=

From tm-otani@kddi.com  Fri Feb 26 22:32:21 2010
Return-Path: <tm-otani@kddi.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 681B428C398; Fri, 26 Feb 2010 22:32:20 -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 lKLp8p9nK83N; Fri, 26 Feb 2010 22:32:12 -0800 (PST)
Received: from UTMC1101.kddi.com (athena.kddi.com [210.141.112.39]) by core3.amsl.com (Postfix) with ESMTP id F167D28C393; Fri, 26 Feb 2010 22:32:08 -0800 (PST)
Received: from UTMC1133 (unknown [10.5.16.198]) by UTMC1101.kddi.com (Postfix) with SMTP id 8B52D6D3; Sat, 27 Feb 2010 15:34:25 +0900 (JST)
Received: from UTMC1122.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 9DEDC17321; Sat, 27 Feb 2010 15:34:23 +0900 (JST)
Received: from UTMC1118.kddi.com (unknown [10.5.16.33]) by UTMC1122.kddi.com (Postfix) with ESMTP id 811D517303; Sat, 27 Feb 2010 15:34:23 +0900 (JST)
Received: from NTMC1175.kddi.com ([10.5.19.13] [10.5.19.13]) by post-ims.kddi.com; Sat, 27 Feb 2010 15:34:23 +0900
Date: Sat, 27 Feb 2010 15:34:42 +0900
From: tm-otani@kddi.com
To: db3546@att.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-transfer-encoding: 7bit
X-Mailer: SEVEN Enterprise Edition (v. 6.0)
Message-Id: <iss.83bcd309.2e5a.4b88bcef.6937e.a5@post-ims.kddi.com>
X-WAuditID: 1002271534230000300770
X-Mailman-Approved-At: Tue, 02 Mar 2010 10:05:38 -0800
Cc: mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2010 06:32:23 -0000

Hi, 

Yes/support. This is a very good draft. 
Regards,

Tomo 




----- Original Message -----
All, 
 
This is to start a two week working group poll on making 
draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working 
group document. This poll is being initiated at this time as this 
document is part of the MPLS-TP work and it is needed to progress the 
work. 
 
Send your response to the ccamp@ietf.org mailing list (only), indicating 
"yes/support" or "no/do not support". 
 
This poll ends March 12th. 
 
Deborah 
_______________________________________________ 
CCAMP mailing list 
CCAMP@ietf.org 
https://www.ietf.org/mailman/listinfo/ccamp 



From ssaxena@cisco.com  Sat Feb 27 15:31:41 2010
Return-Path: <ssaxena@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42E8F3A8A10; Sat, 27 Feb 2010 15:31:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[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 HCKQlDsBZ6XE; Sat, 27 Feb 2010 15:31:40 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 6DE6F3A8A0B; Sat, 27 Feb 2010 15:31:40 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAD46iUutJV2Y/2dsb2JhbACbHnOgbpd/AoR5BIMX
X-IronPort-AV: E=Sophos;i="4.49,552,1262563200"; d="scan'208";a="242990969"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by sj-iport-2.cisco.com with ESMTP; 27 Feb 2010 23:31:39 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id o1RNVc9U018672;  Sat, 27 Feb 2010 23:31:38 GMT
Received: from xmb-rcd-206.cisco.com ([72.163.62.213]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 27 Feb 2010 17:31:38 -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: Sat, 27 Feb 2010 17:31:36 -0600
Message-ID: <C6921F0EC3DEDB419A67B42AB1EA2138B496BD@XMB-RCD-206.cisco.com>
In-Reply-To: <4B8909D8.9020208@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] poll to make draft-nitinb-mpls-tp-lsp-ping-extensions an mpls working document
Thread-Index: Acq3pNhcUaGGr4lqRn2OuzjT8CR3bgAYCDyg
References: <4B8909D8.9020208@pi.nu>
From: "Shaleen Saxena (ssaxena)" <ssaxena@cisco.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <pwe3@ietf.org>, "CCAMP WG" <ccamp@ietf.org>
X-OriginalArrivalTime: 27 Feb 2010 23:31:38.0834 (UTC) FILETIME=[026A2B20:01CAB805]
X-Mailman-Approved-At: Tue, 02 Mar 2010 10:05:38 -0800
Cc: "Shaleen Saxena \(ssaxena\)" <ssaxena@cisco.com>
Subject: Re: [CCAMP] [mpls] poll to make draft-nitinb-mpls-tp-lsp-ping-extensions an mpls working document
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2010 23:31:41 -0000

Yes/support

Shaleen


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
> Loa Andersson
> Sent: Saturday, February 27, 2010 7:03 AM
> To: mpls-tp@ietf.org; mpls@ietf.org; pwe3@ietf.org; CCAMP WG
> Subject: [mpls] poll to make draft-nitinb-mpls-tp-lsp-ping-extensions
> an mpls working document
>=20
> All,
>=20
> this is to start a poll on accepting
> draft-nitinb-mpls-tp-lsp-ping-extensions-01
> as an mpls working group document.
>=20
> Please respond to the mpls-tp mailing list *only*!
> Indicating "yes/support" or "no/do not support".
>=20
> Technical comments, which are very welcome, should be
> sent to the same list, but with a differnt subject line.
>=20
> The poll ends eob March 12th 2010.
>=20
> /Loa
>=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 mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From marc.rapoport@ericsson.com  Sun Feb 28 19:12:24 2010
Return-Path: <marc.rapoport@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51F593A8A32 for <ccamp@core3.amsl.com>; Sun, 28 Feb 2010 19:12:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nTCQLBIAwzJ5 for <ccamp@core3.amsl.com>; Sun, 28 Feb 2010 19:12:23 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 6C6D33A7B31 for <ccamp@ietf.org>; Sun, 28 Feb 2010 19:12:23 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o213Egpm002097 for <ccamp@ietf.org>; Sun, 28 Feb 2010 21:14:42 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Sun, 28 Feb 2010 22:12:22 -0500
From: Marc Rapoport <marc.rapoport@ericsson.com>
To: "ccamp@ietf.org" <ccamp@ietf.org>
Date: Sun, 28 Feb 2010 22:12:22 -0500
Thread-Topic: poll on draft-abfb-mpls-tp-control-plane-framework
Thread-Index: Acq359pShji2YM54RSqekLX6upCaHQAVNmfw
Message-ID: <CE39F5249064D946AA3535E63A01461960CC58226D@EUSAACMS0703.eamcs.ericsson.se>
References: <mailman.33.1267300807.12497.mpls@ietf.org>
In-Reply-To: <mailman.33.1267300807.12497.mpls@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 02 Mar 2010 10:05:38 -0800
Subject: Re: [CCAMP] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 03:43:39 -0000

Support.

/Marc
--------------------------------------------"

All,

This is to start a two week working group poll on making draft-abfb-mpls-tp=
-control-plane-framework-02.txt as a ccamp working group document. This pol=
l is being initiated at this time as this document is part of the MPLS-TP w=
ork and it is needed to progress the work.

Send your response to the ccamp@ietf.org mailing list (only), indicating "y=
es/support" or "no/do not support".

This poll ends March 12th.

Deborah



From root@core3.amsl.com  Tue Mar  2 15:30:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id D2E873A89A4; Tue,  2 Mar 2010 15:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100302233001.D2E873A89A4@core3.amsl.com>
Date: Tue,  2 Mar 2010 15:30:01 -0800 (PST)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-general-constraint-encode-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2010 23:30:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : General Network Element Constraint Encoding for GMPLS Controlled Networks
	Author(s)       : G. Bernstein, et al.
	Filename        : draft-ietf-ccamp-general-constraint-encode-01.txt
	Pages           : 27
	Date            : 2010-03-02

Generalized Multiprotocol Label Switching can be used to control a
wide variety of technologies. In some of these technologies network
elements and links may impose additional routing constraints such as
asymmetric switch connectivity, label limitation and label
availability on links.

This document provides efficient, protocol-agnostic encodings for
general information elements representing connectivity and label
constraints as well as label availability. These encodings are
applicable to a wide range of technologies and not limited to WSON.
It is intended that protocol-specific documents will reference this
memo to describe how information is carried for specific uses.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-general-constraint-encode-01.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-general-constraint-encode-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From zali@cisco.com  Tue Mar  2 19:08:28 2010
Return-Path: <zali@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 869B828C150; Tue,  2 Mar 2010 19:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hA+KMzdzgWHR; Tue,  2 Mar 2010 19:08:27 -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 DFD8228C0ED; Tue,  2 Mar 2010 19:08:26 -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: AvsEAJphjUtAZnwN/2dsb2JhbACbDHOmFZg9hHsEgxc
X-IronPort-AV: E=Sophos;i="4.49,571,1262563200"; d="scan'208,217";a="90026113"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 03 Mar 2010 03:08:27 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o2338RNI015645; Wed, 3 Mar 2010 03:08:27 GMT
Received: from xmb-rcd-103.cisco.com ([72.163.62.145]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Mar 2010 21:08:27 -0600
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_01CABA7E.CAF16409"
Date: Tue, 2 Mar 2010 21:08:40 -0600
Message-ID: <7CC717E2F49DAA4A827DA3FEA237111BEFC460@XMB-RCD-103.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Request for input on http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02 Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs
Thread-Index: Acq6ftM/d56A9tz1TeOQwAS8hyVlUw==
From: "Zafar Ali (zali)" <zali@cisco.com>
To: <mpls@ietf.org>, <ccamp@ietf.org>
X-OriginalArrivalTime: 03 Mar 2010 03:08:27.0281 (UTC) FILETIME=[CB4AE810:01CABA7E]
Cc: Adrian Farrel <Adrian.Farrel@huawei.com>
Subject: [CCAMP] Request for input on http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02 Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 03:08:28 -0000

This is a multi-part message in MIME format.

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

Dear fellows-

I am planning to update
http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02
"Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs", before
IETF flood gate closes. I would like to address any comments/ input you
have on the draft.=20

Your comments will be greatly appreciated.=20

Thanks

Regards... Zafar=20

------_=_NextPart_001_01CABA7E.CAF16409
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>Request for input on =
http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02 =
Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">Dear fellows-</FONT>
</P>

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">I am planning to =
update </FONT><A =
HREF=3D"http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-ca=
se-02"><U></U><U><FONT COLOR=3D"#0000FF" FACE=3D"Times New =
Roman">http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-cas=
e-02</FONT></U></A><U></U><U><FONT COLOR=3D"#000080" FACE=3D"Times New =
Roman"> &quot;</FONT></U><FONT COLOR=3D"#000080" FACE=3D"Times New =
Roman">Signaled PID When Multiplexing Multiple PIDs over RSVP-TE =
LSPs&quot;, before IETF flood gate closes. I would like to address any =
comments/ input you have on the draft.<B><BR>
</B></FONT>

<BR><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">Your comments will =
be greatly appreciated. </FONT>
</P>

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">Thanks</FONT>
</P>

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">Regards&#8230; Zafar =
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01CABA7E.CAF16409--

From dongjie_dj@huawei.com  Wed Mar  3 00:29:32 2010
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D11E928C2D7; Wed,  3 Mar 2010 00:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNeMoDo70b3W; Wed,  3 Mar 2010 00:29:32 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id ED91628C2CF; Wed,  3 Mar 2010 00:29:31 -0800 (PST)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYP007EX68YBT@szxga01-in.huawei.com>; Wed, 03 Mar 2010 16:29:23 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYP00JZK68Y42@szxga01-in.huawei.com>; Wed, 03 Mar 2010 16:29:22 +0800 (CST)
Received: from d65110 ([10.111.12.191]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KYP00LQX68YVC@szxml06-in.huawei.com>; Wed, 03 Mar 2010 16:29:22 +0800 (CST)
Date: Wed, 03 Mar 2010 16:29:21 +0800
From: Jie Dong <dongjie_dj@huawei.com>
To: ccamp@ietf.org
Message-id: <05d401cabaab$a0348190$bf0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acq6q5/jq8vmnoBDRz2UYkIWxqQ49Q==
Cc: mpls@ietf.org
Subject: [CCAMP] New Draft Notification: draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 08:29:32 -0000

Dear all, 

There is a new internet draft: draft-dong-ccamp-rsvp-te-plr-designation-00:
http://tools.ietf.org/html/draft-dong-ccamp-rsvp-te-plr-designation-00

The abstract is as follows: 

This document defines RSVP-TE extensions which enable the ingress node to
designate particular LSRs along the path as Points of Local Repair (PLRs) of
the protected LSP, and further indicate the protection type of each PLR.
These mechanisms could enhance the control over the establishment of backup
LSPs, and also could save the resources needed for establishing and
maintaining unnecessary backup LSPs.

Comments are appreciated.



Best regards,
Jie



From vishwas.ietf@gmail.com  Wed Mar  3 06:46:48 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5D123A8612 for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 06:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 PxSTu4fLketp for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 06:46:48 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id E2AE93A6C40 for <ccamp@ietf.org>; Wed,  3 Mar 2010 06:46:47 -0800 (PST)
Received: by gyc15 with SMTP id 15so838631gyc.31 for <ccamp@ietf.org>; Wed, 03 Mar 2010 06:46:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=8mGrLqb96wiFrE0SH9A95fQ0G2MIhu/LQPtHctIdRJw=; b=xwG17p7mpsDmpCtQXOgHwZEJEhhc0xvGFlyJNW17QDrWwMUf+2WxqxOsBK0XdYtnLx SW00TwRZy3P9//FEmWEK4Q7PKMrq59zrMPja/KGyN6v0BtB6b2pnHIY00ZS3XQdmQI4D SpKilr3J880BvRBcYM8hRQM6/D7F2uF2IutBk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=a46XpaHYeYnCTBhnYpwwbNrCmp9hdhCboqo7K3u00TDlFedW+Ok3tMcvj4gk93Wm88 pYnF/2byT6rlYLdNubnQB7tWOsiqFlfmzwt7bvlYyTlSKlggZ+rOeldt8TNvmFOkKqMV FWZdmXarV2PxNB4Avfn9nY4hnm3Shl4WtsbUk=
MIME-Version: 1.0
Received: by 10.150.193.9 with SMTP id q9mr1205282ybf.271.1267627605625; Wed,  03 Mar 2010 06:46:45 -0800 (PST)
Date: Wed, 3 Mar 2010 06:46:45 -0800
Message-ID: <77ead0ec1003030646t4ebeb9bfl52154febe69e1dbe@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: ccamp@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd76272240d9d0480e68d2e
Subject: [CCAMP] LMP critical
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 14:46:48 -0000

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

Hi,

I find a basic and critical issue with RFC4204 - LMP.

LMP defines the "Retransmission Algorithm" - Section 10.2, where a node
transmitting a message requiring acknowledgement stops transmiision when a
retry limit is reached.

Now if in the control topology two routers are unable to communicate because
of some intrmediate device not functioning they both timeout the config
sends and stop. If the intermediate link/ device is corrected the IP
reachability between the two nodes is then possible. However the control
channel between the devices never comes up as they both stop the config
message send. Similar issue can happen if a control channel on a device
configured as passive happens after the active device has stopped
retransmission.

I guess it should be added that this algorithm cannot be applied for config
messages.

Thanks,
Vishwas

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

<div>Hi,</div>
<div>=A0</div>
<div>I find a basic and critical issue with RFC4204 - LMP.</div>
<div>=A0</div>
<div>LMP defines the &quot;Retransmission Algorithm&quot; - Section 10.2, w=
here a node transmitting a message requiring acknowledgement stops transmii=
sion when a retry limit is reached.</div>
<div>=A0</div>
<div>Now if in the control topology two routers are unable to communicate b=
ecause of some intrmediate device not functioning they both timeout the con=
fig sends and stop. If the intermediate link/ device is corrected the IP re=
achability between the two nodes is then possible. However the control chan=
nel between the devices never comes up as they both stop the config message=
 send. Similar issue can happen if a control channel on a device configured=
 as passive happens after=A0the active=A0device has stopped retransmission.=
</div>

<div>=A0</div>
<div>I guess it should be added that this algorithm cannot be applied for c=
onfig messages.</div>
<div>=A0</div>
<div>Thanks,</div>
<div>Vishwas</div>

--000e0cd76272240d9d0480e68d2e--

From vishwas.ietf@gmail.com  Wed Mar  3 06:54:12 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03BDD28C3E9 for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 06:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 p-Ssf4K-duoO for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 06:54:11 -0800 (PST)
Received: from mail-yx0-f187.google.com (mail-yx0-f187.google.com [209.85.210.187]) by core3.amsl.com (Postfix) with ESMTP id 3D31B28C3E6 for <ccamp@ietf.org>; Wed,  3 Mar 2010 06:54:11 -0800 (PST)
Received: by yxe17 with SMTP id 17so657837yxe.32 for <ccamp@ietf.org>; Wed, 03 Mar 2010 06:54:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=KGMGaJUJHjHqyfkkH+byktT1Frn221LMoscs9sSMcsc=; b=catMcxdEAoQkKJDgjFBf2wl2crSg4AGM8OVHL38P7ihpfJmYI1yH7EoKF7T9bqtoNc LmMFUAIKfiTgeyda4edgrYj7wIzi58XBr6hvbGzQJps+LRsroL7aAAm+wRqKv+Zezol+ hX1V502a5PFkqET2szXY0KXXDpP6amBqtKG+o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=STWmQk5I7013BE85s/WDWA4++Uwp4fWbC3usVEB9Oy53Gb9APeunNMZFMBXfogr5k9 78ts1SFopQW+psOAk0hnnzTo+d/qEf8ymeJg4NscOz0n6B5GRMHm/8eHD1kCDmNznheq a4OC7XT0g9/IpECCTUx45e+UqRySEQ+hIwHq8=
MIME-Version: 1.0
Received: by 10.150.213.1 with SMTP id l1mr1158155ybg.288.1267628049855; Wed,  03 Mar 2010 06:54:09 -0800 (PST)
Date: Wed, 3 Mar 2010 06:54:09 -0800
Message-ID: <77ead0ec1003030654x515df4a8r12803ad301a2bf23@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: ccamp@ietf.org, donald.fedyk@alcatel-lucent.com,  David Allan I <david.i.allan@ericsson.com>, hshah@force10networks.com,  nabil.n.bitar@verizon.com, attila.takacs@ericsson.com,  diego.caviglia@ericsson.com, alan.mcguire@bt.com, nurit.sprecher@nsn.com, lberger@labn.net
Content-Type: multipart/alternative; boundary=00151748dfb69e77140480e6a79d
Subject: [CCAMP] draft-ietf-ccamp-gmpls-ethernet-pbb-te
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 14:54:12 -0000

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

Hi,

It seems there is no reference to how an LMP test message can be sent over
the PBB-TE link. Doesn't it need to be specified?

Thanks,
Vishwas

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

<div>Hi,</div>
<div>=A0</div>
<div>It seems there is no reference to how an LMP test message can be sent =
over the PBB-TE link. Doesn&#39;t it need to be specified?</div>
<div>=A0</div>
<div>Thanks,</div>
<div>Vishwas</div>
<div>=A0</div>

--00151748dfb69e77140480e6a79d--

From Donald.Fedyk@alcatel-lucent.com  Wed Mar  3 07:21:53 2010
Return-Path: <Donald.Fedyk@alcatel-lucent.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83A4B28C100 for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 07:21:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 AV5JtBMbyszC for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 07:21:49 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by core3.amsl.com (Postfix) with ESMTP id 571A33A8A71 for <ccamp@ietf.org>; Wed,  3 Mar 2010 07:21:45 -0800 (PST)
Received: from horh1.pdc.alcatel-lucent.com (h172-22-218-55.lucent.com [172.22.218.55]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id o23FLbp0025489; Wed, 3 Mar 2010 09:21:37 -0600 (CST)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.pdc.alcatel-lucent.com [172.22.216.19]) by horh1.pdc.alcatel-lucent.com (8.13.8/emsr) with ESMTP id o23FLaQ9026179; Wed, 3 Mar 2010 09:21:37 -0600 (CST)
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.10]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Mar 2010 09:21:36 -0600
Received: from USDALSMBS05.ad3.ad.alcatel.com ([172.22.216.35]) by USDALSMBS03.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Mar 2010 09:21:11 -0600
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_01CABAE5.22905B8C"
Date: Wed, 3 Mar 2010 09:21:00 -0600
Message-ID: <292BD6E016C29243BB231D329D626C8C036DE005@USDALSMBS05.ad3.ad.alcatel.com>
In-Reply-To: <77ead0ec1003030654x515df4a8r12803ad301a2bf23@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ccamp-gmpls-ethernet-pbb-te
Thread-Index: Acq64Wonq5LqZI5mT9KAliBkb/WF2gAAbWNw
References: <77ead0ec1003030654x515df4a8r12803ad301a2bf23@mail.gmail.com>
From: "FEDYK Don" <Donald.Fedyk@alcatel-lucent.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>, <ccamp@ietf.org>, "David Allan I" <david.i.allan@ericsson.com>, <hshah@force10networks.com>, <nabil.n.bitar@verizon.com>, <attila.takacs@ericsson.com>, <diego.caviglia@ericsson.com>, <alan.mcguire@bt.com>, <nurit.sprecher@nsn.com>, <lberger@labn.net>
X-OriginalArrivalTime: 03 Mar 2010 15:21:11.0266 (UTC) FILETIME=[27DEA420:01CABAE5]
X-Scanned-By: MIMEDefang 2.57 on 172.22.12.27
Subject: Re: [CCAMP] draft-ietf-ccamp-gmpls-ethernet-pbb-te
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 15:21:53 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CABAE5.22905B8C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Vishwas
=20
Since this is Ethernet which can easily transport a message on the data
link all you need is the ability to handle a UDP (over Ethernet) message
addressed to the local IP loopback at the other end of the link.=20
=20
Note that these are point to point messages and an IP routing layer is
not required.=20
=20
Don=20


________________________________

	From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]=20
	Sent: Wednesday, March 03, 2010 9:54 AM
	To: ccamp@ietf.org; FEDYK Don; David Allan I;
hshah@force10networks.com; nabil.n.bitar@verizon.com;
attila.takacs@ericsson.com; diego.caviglia@ericsson.com;
alan.mcguire@bt.com; nurit.sprecher@nsn.com; lberger@labn.net
	Subject: draft-ietf-ccamp-gmpls-ethernet-pbb-te
=09
=09
	Hi,
	=20
	It seems there is no reference to how an LMP test message can be
sent over the PBB-TE link. Doesn't it need to be specified?
	=20
	Thanks,
	Vishwas
	=20


------_=_NextPart_001_01CABAE5.22905B8C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16981" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D138410615-03032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Vishwas</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D138410615-03032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D138410615-03032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Since this is Ethernet which can easily =
transport a message=20
on the data link all you need is the ability to handle a UDP (over=20
Ethernet)&nbsp;message addressed to the local IP loopback at the other =
end of=20
the link. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D138410615-03032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D138410615-03032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Note that these are point to point messages and =
an IP=20
routing layer is not required. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D138410615-03032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D138410615-03032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Don </FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; 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> Vishwas Manral=20
  [mailto:vishwas.ietf@gmail.com] <BR><B>Sent:</B> Wednesday, March 03, =
2010=20
  9:54 AM<BR><B>To:</B> ccamp@ietf.org; FEDYK Don; David Allan I;=20
  hshah@force10networks.com; nabil.n.bitar@verizon.com;=20
  attila.takacs@ericsson.com; diego.caviglia@ericsson.com; =
alan.mcguire@bt.com;=20
  nurit.sprecher@nsn.com; lberger@labn.net<BR><B>Subject:</B>=20
  draft-ietf-ccamp-gmpls-ethernet-pbb-te<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>Hi,</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>It seems there is no reference to how an LMP test message can be =
sent=20
  over the PBB-TE link. Doesn't it need to be specified?</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Thanks,</DIV>
  <DIV>Vishwas</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CABAE5.22905B8C--

From gregb@grotto-networking.com  Wed Mar  3 09:32:27 2010
Return-Path: <gregb@grotto-networking.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29D5228C165 for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 09:32:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, J_CHICKENPOX_62=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 IuqCudTgQrjr for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 09:32:25 -0800 (PST)
Received: from mail30c40.carrierzone.com (mail30c40.carrierzone.com [209.235.156.170]) by core3.amsl.com (Postfix) with ESMTP id 1AA2D3A8AAF for <ccamp@ietf.org>; Wed,  3 Mar 2010 09:32:24 -0800 (PST)
X-Authenticated-User: gregb.grotto-networking.com
Received: from [192.168.0.131] (c-71-202-41-133.hsd1.ca.comcast.net [71.202.41.133]) (authenticated bits=0) by mail30c40.carrierzone.com (8.13.6/8.13.1) with ESMTP id o23HW3MD011589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Mar 2010 12:32:06 -0500
Message-ID: <4B8E9D1C.2070102@grotto-networking.com>
Date: Wed, 03 Mar 2010 09:32:12 -0800
From: Greg Bernstein <gregb@grotto-networking.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "PELOSO, PIERRE (PIERRE)" <pierre.peloso@alcatel-lucent.com>
References: <CCBFBB7025DF984494DEC3285C0581521253392E75@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com> <4B83FFEF.3090106@grotto-networking.com> <CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com>
In-Reply-To: <CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------060108050907050706010902"
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [CCAMP] Disscussion and contribution in RWA drafts (encode and info) - switching constraints
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 17:32:27 -0000

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

Hi Pierre, see comments below. Note that all the updated encoding 
documents and background material is also available at: 
http://www.grotto-networking.com/wsonEncode
Also from the high level to more detailed we have the following documents:
                         WSON Framework
                          WSON Information Modeling for RWA
              General Constraint Encoding                         WSON 
Specific Encoding
               General OSPF Ext (not a WG draft yet)       WSON 
Compatibility OSPF Ext

Regards
Greg

PELOSO, PIERRE (PIERRE) wrote:
> Hi Greg and CCAMPers,
>
> For clarification purposes, I've taken the freedom to clean a bit the original email and separate its content in smaller pieces.
> This one deals specifically with the clarification of the node switching constraints and resource identification:
>
> - Pierre
>
> BERNSTEIN, GREG (wrote):
>   
>> Hi Pierre and fellow CCAMPers, see response in line below.
>>
>> Greg
>>
>> PELOSO, PIERRE (PIERRE) wrote:
>>     
>>> Hi Greg, Young and CCAMP'rs,
>>> [...]
>>> 1. The drafts propose different pieces of information to describe the node internal switching structure (and constraints) and to describe the O-E-O resources inside the node. However, they do not describe how these pieces of information fit together in order to build the global picture of the node internal switching constraints. For example, considering  the list of O-E-O resources how you determine which of those are available from a given incoming link to a given outgoing link, what are the associated wavelength restrictions associated, etc...
>>>  
>>>       
>> --> Hmm, maybe this section needs more explanatory text. It looks like you gave the high level summary in your point "2" above. In more detail: we break the resource pool into the largest blocks possible (with identical ingress, egress and wavelength constraints), we specify the ingress connectivity constraints to the blocks and ingress wavelength constraints to each block. Similarly we specify the egress connectivity constraints from each block and any wavelength constraints associated with those. If needed a minimal amount of state information can be associated with each resource block (number of resources available in each block).  We have a paper in progress that shows this technique used to model a fairly wide collection of different combined switch architectures gathered from the literature. We can make a preliminary draft available to those interested in the details.
>>     
>
> PP: I have no issue with the capabilities of your technique to describe a node and its O-E-O resources whatever the architecture used. I am more concerned with the lack of detail provided in current drafts.
> At this stage, there are too many unspecified details for implementing the drafts in a unique manner.
> E.g. There is supposedly a switching matrix information to depict the node internal switching structure.
> Is it supposed to be in [Gen-Encode] draft under preparation? In previous version of the draft this object was refering to "port ID", are those supposed to be "link local/remote identifiers", I understand yes from your last email but would this appear in the draft? Then should'nt there be a recommendation to use "LLRI" in the Link information object as well?
>   
--> [Gen-Encode] is now published. The "Link Set Field" which is used to 
specify the connectivity matrix uses "Link Identifiers" and supports 
different formats including Link Local Identifier.
> When adding the resource pool, things are getting more complex:
> Can there be more than one Resource pool object in the description of a node? Is this object supposed to be a top-level TLV or is it supposed to be a sub-TLV inside a Node object? 
>   
--> The TLV structuring needs to be given in a protocol specific draft 
such as OSPF or IS-IS extension. Young's WG draft on OSPF compatibility 
will be updated to include this as an optional sub-TLV within a Node 
Attributes TLV (http://www.ietf.org/id/draft-ietf-ospf-te-node-addr-07.txt).
> A "resource pool" object is composed of:
>     - A "resource block info" basically a list of resource ID with their features regarding signal (incoming and outgoing)- is that right? Then I imagine that we will have as many resource block info object as there are different combination of signal features in the node.
>   
--> Yes a list of resource IDs group with descriptions of their 
properties, but NOT a set of all combinations.
>     - A "resource block accessibility" basically a list of (resource blocks, switching constraints on each side of the block). Then I imagine that the resource blocks here have nothing to do with the one used for the "resource block info"? Are the switching constraints to be related to the Link information object, then once again the draft would benefit from refering to "link local/remote identifiers"?
>   
--> These are the same blocks as used in the info. The draft uses a 
general Link Identifier that includes the link local identifier.
>     - A "resource wave constraints" basically a resource block with wavelength constraint on each side of the block. Is that to depict: 1.the wavelength constraints of the architecture, 
Yes.
> 2. the limitations of the resources/devices or 
Yes
> 3.the usage of the wavelengths by other resources sharing the same port? 
No.
> Because some of these elements are dynamic and some are static. And the grouping of resources in blocks will follow different rules depending on what is to be depicted with that (leading certainly to a third list of resource blocks). Hence that is giving me the idea that something is missing, as we would certainly like to depict all these 3 constraints and only one can be depicted there, isn't it?
>   
I'm not sure if your third constraint requires us to carry additional 
internal state, or if not it would seem redundant with the wavelength 
usage state of the ingress or egress ports. For details of modeling 
considerations and application to a wide range of switch architectures 
including regenerators or wavelength converters see a draft of our 
paper: 
http://www.grotto-networking.com/sites/default/files/ModelingSwitchesConvertersRegensV02f.pdf
> To summarize, I end up having the impression that a node and its switching matrix is depicted twice in the same object. A first time for the bypassing traffic and a second one comporting the additional information of the resources. 
--> Yes. Typically a ROADM will not have regenerators or wavelength 
converters so the resource pool would not be used. Or in the case of a 
translucent network with OEO switches the connectivity matrix would not 
be used. In the most general case we have both general switching 
constraints and constraints on how we get to/from processing resources.
> Then I have the feeling that gathering all the information relative to the switching constraints in a unique object with more ports would be more efficient as this object would never change and the ports would be defined once and for all. There would be the external ports that are referring to the "WDM link information" and using the LLRI of the WDM links. And there would be the internal ports corresponding to physical pools of ressources.
> This modification is just a minor adaptation of your technique, using most of the same encodings, did you try this direction ?
>   
--> Two issues here. Separating "dynamic" versus "static" information 
with respect to updates, and how to organize sub-TLVs. The dynamic 
information has been separated from the static in encoding the exact 
packaging depends on the routing protocol. In Fatai's OSPF draft we 
propose a multiple LSA instance approach. In addition with Young's 
Compatibility OSPF extensions we will indicate that the pool related 
sub-TLV get incorporated into the same Node Attributes TLV as in Fatai's 
draft.
> Pierre
>
>
>   

-- 
===================================================
Dr Greg Bernstein, Grotto Networking (510) 573-2237



--------------060108050907050706010902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Pierre, see comments below. Note that all the updated encoding
documents and background material is also available at: <a
 href="http://www.grotto-networking.com/wsonEncode">http://www.grotto-networking.com/wsonEncode</a><br>
Also from the high level to more detailed we have the following
documents:<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; WSON Framework<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; WSON Information Modeling for RWA<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; General Constraint Encoding&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; WSON
Specific Encoding<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp; General OSPF Ext (not a WG draft yet)&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; WSON
Compatibility OSPF Ext<br>
<br>
Regards<br>
Greg<br>
<br>
PELOSO, PIERRE (PIERRE) wrote:
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">Hi Greg and CCAMPers,

For clarification purposes, I've taken the freedom to clean a bit the original email and separate its content in smaller pieces.
This one deals specifically with the clarification of the node switching constraints and resource identification:

- Pierre

BERNSTEIN, GREG (wrote):
  </pre>
  <blockquote type="cite">
    <pre wrap="">Hi Pierre and fellow CCAMPers, see response in line below.

Greg

PELOSO, PIERRE (PIERRE) wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">Hi Greg, Young and CCAMP'rs,
[...]
1. The drafts propose different pieces of information to describe the node internal switching structure (and constraints) and to describe the O-E-O resources inside the node. However, they do not describe how these pieces of information fit together in order to build the global picture of the node internal switching constraints. For example, considering  the list of O-E-O resources how you determine which of those are available from a given incoming link to a given outgoing link, what are the associated wavelength restrictions associated, etc...
 
      </pre>
    </blockquote>
    <pre wrap="">--&gt; Hmm, maybe this section needs more explanatory text. It looks like you gave the high level summary in your point "2" above. In more detail: we break the resource pool into the largest blocks possible (with identical ingress, egress and wavelength constraints), we specify the ingress connectivity constraints to the blocks and ingress wavelength constraints to each block. Similarly we specify the egress connectivity constraints from each block and any wavelength constraints associated with those. If needed a minimal amount of state information can be associated with each resource block (number of resources available in each block).  We have a paper in progress that shows this technique used to model a fairly wide collection of different combined switch architectures gathered from the literature. We can make a preliminary draft available to those interested in the details.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
PP: I have no issue with the capabilities of your technique to describe a node and its O-E-O resources whatever the architecture used. I am more concerned with the lack of detail provided in current drafts.
At this stage, there are too many unspecified details for implementing the drafts in a unique manner.
E.g. There is supposedly a switching matrix information to depict the node internal switching structure.
Is it supposed to be in [Gen-Encode] draft under preparation? In previous version of the draft this object was refering to "port ID", are those supposed to be "link local/remote identifiers", I understand yes from your last email but would this appear in the draft? Then should'nt there be a recommendation to use "LLRI" in the Link information object as well?
  </pre>
</blockquote>
--&gt; [Gen-Encode] is now published. The "Link Set Field" which is
used to specify the connectivity matrix uses "Link Identifiers" and
supports different formats including Link Local Identifier.<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">
When adding the resource pool, things are getting more complex:
Can there be more than one Resource pool object in the description of a node? Is this object supposed to be a top-level TLV or is it supposed to be a sub-TLV inside a Node object? 
  </pre>
</blockquote>
--&gt; The TLV structuring needs to be given in a protocol specific
draft such as OSPF or IS-IS extension. Young's WG draft on OSPF
compatibility will be updated to include this as an optional sub-TLV
within a Node Attributes TLV
(<a class="moz-txt-link-freetext" href="http://www.ietf.org/id/draft-ietf-ospf-te-node-addr-07.txt">http://www.ietf.org/id/draft-ietf-ospf-te-node-addr-07.txt</a>).<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">A "resource pool" object is composed of:
    - A "resource block info" basically a list of resource ID with their features regarding signal (incoming and outgoing)- is that right? Then I imagine that we will have as many resource block info object as there are different combination of signal features in the node.
  </pre>
</blockquote>
--&gt; Yes a list of resource IDs group with descriptions of their
properties, but NOT a set of all combinations.<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">    - A "resource block accessibility" basically a list of (resource blocks, switching constraints on each side of the block). Then I imagine that the resource blocks here have nothing to do with the one used for the "resource block info"? Are the switching constraints to be related to the Link information object, then once again the draft would benefit from refering to "link local/remote identifiers"?
  </pre>
</blockquote>
--&gt; These are the same blocks as used in the info. The draft uses a
general Link Identifier that includes the link local identifier.<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">    - A "resource wave constraints" basically a resource block with wavelength constraint on each side of the block. Is that to depict: 1.the wavelength constraints of the architecture, </pre>
</blockquote>
Yes.<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">2. the limitations of the resources/devices or </pre>
</blockquote>
Yes<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">3.the usage of the wavelengths by other resources sharing the same port? </pre>
</blockquote>
No.<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">Because some of these elements are dynamic and some are static. And the grouping of resources in blocks will follow different rules depending on what is to be depicted with that (leading certainly to a third list of resource blocks). Hence that is giving me the idea that something is missing, as we would certainly like to depict all these 3 constraints and only one can be depicted there, isn't it?
  </pre>
</blockquote>
I'm not sure if your third constraint requires us to carry additional
internal state, or if not it would seem redundant with the wavelength
usage state of the ingress or egress ports. For details of modeling
considerations and application to a wide range of switch architectures
including regenerators or wavelength converters see a draft of our
paper: <a
 href="http://www.grotto-networking.com/sites/default/files/ModelingSwitchesConvertersRegensV02f.pdf">http://www.grotto-networking.com/sites/default/files/ModelingSwitchesConvertersRegensV02f.pdf</a><br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">
To summarize, I end up having the impression that a node and its switching matrix is depicted twice in the same object. A first time for the bypassing traffic and a second one comporting the additional information of the resources. </pre>
</blockquote>
--&gt; Yes. Typically a ROADM will not have regenerators or wavelength
converters so the resource pool would not be used. Or in the case of a
translucent network with OEO switches the connectivity matrix would not
be used. In the most general case we have both general switching
constraints and constraints on how we get to/from processing resources.
<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">Then I have the feeling that gathering all the information relative to the switching constraints in a unique object with more ports would be more efficient as this object would never change and the ports would be defined once and for all. There would be the external ports that are referring to the "WDM link information" and using the LLRI of the WDM links. And there would be the internal ports corresponding to physical pools of ressources.
This modification is just a minor adaptation of your technique, using most of the same encodings, did you try this direction ?
  </pre>
</blockquote>
--&gt; Two issues here. Separating "dynamic" versus "static"
information with respect to updates, and how to organize sub-TLVs. The
dynamic information has been separated from the static in encoding the
exact packaging depends on the routing protocol. In Fatai's OSPF draft
we propose a multiple LSA instance approach. In addition with Young's
Compatibility OSPF extensions we will indicate that the pool related
sub-TLV get incorporated into the same Node Attributes TLV as in
Fatai's draft.<br>
<blockquote
 cite="mid:CCBFBB7025DF984494DEC3285C05815212533F027A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com"
 type="cite">
  <pre wrap="">
Pierre


  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
===================================================
Dr Greg Bernstein, Grotto Networking (510) 573-2237

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

--------------060108050907050706010902--

From vishwas.ietf@gmail.com  Wed Mar  3 09:46:16 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 07F8128C1CF for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 09:46:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 7DBJsDHwQJDj for <ccamp@core3.amsl.com>; Wed,  3 Mar 2010 09:46:15 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id E3ECB28C1B8 for <ccamp@ietf.org>; Wed,  3 Mar 2010 09:46:14 -0800 (PST)
Received: by gwb10 with SMTP id 10so906371gwb.31 for <ccamp@ietf.org>; Wed, 03 Mar 2010 09:46:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=J+wpCp2iKNaUn4Jv3T/xNYQdlzWPv8icIJE/FI5DMiA=; b=au+fNZ5/oaNLgzT7+I9FymTcnWJE+GJQ2ZriuZkxGqTRnDgychbBCHVX+ciwEjHDKF mXHB43wvZVPmdPDuDXsC31UgXS87yvMQNciVQOmQ6PVOBPqfOGUkcbuHeSjWG0XW/lUi XtRU6ULu+2D60V/Uss9CTc+lPCTgi+e75uMu4=
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=IzIW9bMMTyFGkY9+zeLRWj1YiGCidMqex2+GVaeA2iRHWLw26D29lQG8JqU/4FV7r8 1Fm6pF0B+Vn39r48+D9Dmx5w5rqm5KvV9y5CfhCdU1M3570kgiMkgjh0IaR/sFzVrMCZ 63ITte3R9sF/He72Di1ZRuOsfwS/xD3XH7ez4=
MIME-Version: 1.0
Received: by 10.101.2.32 with SMTP id e32mr731980ani.239.1267638373658; Wed,  03 Mar 2010 09:46:13 -0800 (PST)
In-Reply-To: <292BD6E016C29243BB231D329D626C8C036DE005@USDALSMBS05.ad3.ad.alcatel.com>
References: <77ead0ec1003030654x515df4a8r12803ad301a2bf23@mail.gmail.com> <292BD6E016C29243BB231D329D626C8C036DE005@USDALSMBS05.ad3.ad.alcatel.com>
Date: Wed, 3 Mar 2010 09:46:13 -0800
Message-ID: <77ead0ec1003030946n79f37e0dg8656338fe078dcc8@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: FEDYK Don <Donald.Fedyk@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=0016368e2a69f730f30480e90ed2
Cc: ccamp@ietf.org, nabil.n.bitar@verizon.com
Subject: Re: [CCAMP] draft-ietf-ccamp-gmpls-ethernet-pbb-te
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 17:46:16 -0000

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

Hi Don,

Interesting. The datalink itself may not have an IP address at all though.

What we are planning to do is use a broadcast IP address as well as
Broadcast MAC address for the destination address and push the packet over
the link. The receiver is using only the physical data channel to determine
the data channel over which the packet came (addreses are themselves not
used).

Maybe you can add some text regarding this in the draft? Do you know of
other implementations of the draft so that we can think of some interops?

Thanks,
Vishwas
On Wed, Mar 3, 2010 at 7:21 AM, FEDYK Don
<Donald.Fedyk@alcatel-lucent.com>wrote:

>  Hi Vishwas
>
> Since this is Ethernet which can easily transport a message on the data
> link all you need is the ability to handle a UDP (over Ethernet) message
> addressed to the local IP loopback at the other end of the link.
>
> Note that these are point to point messages and an IP routing layer is not
> required.
>
> Don
>
>  ------------------------------
> *From:* Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> *Sent:* Wednesday, March 03, 2010 9:54 AM
> *To:* ccamp@ietf.org; FEDYK Don; David Allan I; hshah@force10networks.com;
> nabil.n.bitar@verizon.com; attila.takacs@ericsson.com;
> diego.caviglia@ericsson.com; alan.mcguire@bt.com; nurit.sprecher@nsn.com;
> lberger@labn.net
> *Subject:* draft-ietf-ccamp-gmpls-ethernet-pbb-te
>
>   Hi,
>
> It seems there is no reference to how an LMP test message can be sent over
> the PBB-TE link. Doesn't it need to be specified?
>
> Thanks,
> Vishwas
>
>
>

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

<div>Hi Don,</div>
<div>=A0</div>
<div>Interesting. The datalink itself may not have an IP address at all tho=
ugh.</div>
<div>=A0</div>
<div>What we are planning to do is use a broadcast IP address as well as Br=
oadcast MAC address for the destination address and push the packet over th=
e link. The receiver is using only the physical data channel to determine t=
he data channel over which the packet came (addreses are themselves not use=
d).</div>

<div>=A0</div>
<div>Maybe you can add some text regarding this in the draft? Do you know o=
f other implementations of the draft so that we can think of some interops?=
</div>
<div>=A0</div>
<div>Thanks,</div>
<div>Vishwas<br></div>
<div class=3D"gmail_quote">On Wed, Mar 3, 2010 at 7:21 AM, FEDYK Don <span =
dir=3D"ltr">&lt;<a href=3D"mailto:Donald.Fedyk@alcatel-lucent.com">Donald.F=
edyk@alcatel-lucent.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" size=3D"2" fa=
ce=3D"Arial">Hi Vishwas</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" size=3D"2" fa=
ce=3D"Arial"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" size=3D"2" fa=
ce=3D"Arial">Since this is Ethernet which can easily transport a message on=
 the data link all you need is the ability to handle a UDP (over Ethernet)=
=A0message addressed to the local IP loopback at the other end of the link.=
 </font></span></div>

<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" size=3D"2" fa=
ce=3D"Arial"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" size=3D"2" fa=
ce=3D"Arial">Note that these are point to point messages and an IP routing =
layer is not required. </font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" size=3D"2" fa=
ce=3D"Arial"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font color=3D"#0000ff" size=3D"2" fa=
ce=3D"Arial">Don </font></span></div><br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"en-us" align=3D"left">
<hr>
<font size=3D"2" face=3D"Tahoma"><b>From:</b> Vishwas Manral [mailto:<a hre=
f=3D"mailto:vishwas.ietf@gmail.com" target=3D"_blank">vishwas.ietf@gmail.co=
m</a>] <br><b>Sent:</b> Wednesday, March 03, 2010 9:54 AM<br><b>To:</b> <a =
href=3D"mailto:ccamp@ietf.org" target=3D"_blank">ccamp@ietf.org</a>; FEDYK =
Don; David Allan I; <a href=3D"mailto:hshah@force10networks.com" target=3D"=
_blank">hshah@force10networks.com</a>; <a href=3D"mailto:nabil.n.bitar@veri=
zon.com" target=3D"_blank">nabil.n.bitar@verizon.com</a>; <a href=3D"mailto=
:attila.takacs@ericsson.com" target=3D"_blank">attila.takacs@ericsson.com</=
a>; <a href=3D"mailto:diego.caviglia@ericsson.com" target=3D"_blank">diego.=
caviglia@ericsson.com</a>; <a href=3D"mailto:alan.mcguire@bt.com" target=3D=
"_blank">alan.mcguire@bt.com</a>; <a href=3D"mailto:nurit.sprecher@nsn.com"=
 target=3D"_blank">nurit.sprecher@nsn.com</a>; <a href=3D"mailto:lberger@la=
bn.net" target=3D"_blank">lberger@labn.net</a><br>
<b>Subject:</b> draft-ietf-ccamp-gmpls-ethernet-pbb-te<br></font><br></div>
<div>
<div></div>
<div class=3D"h5">
<div></div>
<div>Hi,</div>
<div>=A0</div>
<div>It seems there is no reference to how an LMP test message can be sent =
over the PBB-TE link. Doesn&#39;t it need to be specified?</div>
<div>=A0</div>
<div>Thanks,</div>
<div>Vishwas</div>
<div>=A0</div></div></div></blockquote></div></blockquote></div><br>

--0016368e2a69f730f30480e90ed2--

From eric.gray@ericsson.com  Thu Mar  4 04:33:25 2010
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0277E3A845B for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 04:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S64W99ABd1oW for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 04:33:23 -0800 (PST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 45C4E3A6774 for <ccamp@ietf.org>; Thu,  4 Mar 2010 04:33:23 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id o24CZobY009800; Thu, 4 Mar 2010 06:35:50 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.197]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Thu, 4 Mar 2010 07:33:22 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>, CCAMP <ccamp@ietf.org>
Date: Thu, 4 Mar 2010 07:33:21 -0500
Thread-Topic: poll on draft-abfb-mpls-tp-control-plane-framework
Thread-Index: Acq3LhTmuSG/kxGCTt+1iMNqBtXcygEaKmFA
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F104368973C3@EUSAACMS0701.eamcs.ericsson.se>
References: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [CCAMP] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2010 12:33:25 -0000

Yes/Support

-----Original Message-----
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of B=
RUNGARD, DEBORAH A (ATTLABS)
Sent: Friday, February 26, 2010 4:53 PM
To: CCAMP
Cc: mpls@ietf.org; pwe3@ietf.org; mpls-tp@ietf.org
Subject: [CCAMP] poll on draft-abfb-mpls-tp-control-plane-framework

All,

This is to start a two week working group poll on making
draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working
group document. This poll is being initiated at this time as this
document is part of the MPLS-TP work and it is needed to progress the
work.

Send your response to the ccamp@ietf.org mailing list (only), indicating
"yes/support" or "no/do not support".

This poll ends March 12th.

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

From jvasseur@cisco.com  Thu Mar  4 06:46:59 2010
Return-Path: <jvasseur@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5025328C15D; Thu,  4 Mar 2010 06:46:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.138
X-Spam-Level: 
X-Spam-Status: No, score=-6.138 tagged_above=-999 required=5 tests=[AWL=-3.540, 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 c2dV2TX4VaIY; Thu,  4 Mar 2010 06:46:58 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id C4E8828C154; Thu,  4 Mar 2010 06:46:57 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtQAADpXj0uQ/uCWe2dsb2JhbACBRJl7FQEBFiQGHJ5bmF2EfAQ
X-IronPort-AV: E=Sophos;i="4.49,581,1262563200"; d="scan'208,217";a="3996980"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-2.cisco.com with ESMTP; 04 Mar 2010 14:14:14 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o24Ekwd7008678; Thu, 4 Mar 2010 14:46:58 GMT
Received: from xfe-ams-202.cisco.com ([144.254.231.96]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Mar 2010 15:46:58 +0100
Received: from ams-jvasseur-8713.cisco.com ([10.55.201.132]) by xfe-ams-202.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Mar 2010 15:46:57 +0100
Message-Id: <B4E97C5E-3860-46B8-A522-579B6400D079@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: Jie Dong <dongjie_dj@huawei.com>
In-Reply-To: <05d401cabaab$a0348190$bf0c6f0a@china.huawei.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-220--503475206
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 4 Mar 2010 15:46:57 +0100
References: <05d401cabaab$a0348190$bf0c6f0a@china.huawei.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 04 Mar 2010 14:46:57.0967 (UTC) FILETIME=[8A6BD3F0:01CABBA9]
Cc: mpls@ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] New Draft Notification: draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2010 14:46:59 -0000

--Apple-Mail-220--503475206
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Dear Jie,

Looking at section 3:

    In some scenarios the ingress node may need to specify particular
    LSRs as PLRs, and the protection type of each particular PLR. This
    can be helpful in many aspects. Firstly, this enables the ingress
    node to setup the backup LSPs in a more controllable way. Secondly,
    this could avoid making LSRs which do not have enough resources to
    provide local protections work as PLRs. Thirdly, this could save
    bandwidth reserved for unnecessary backup LSPs.

First argument: why does the proposal allow the ingress node to set up  
the backup LSP ?
Second and third arguments: If there is not enough backup bandwidth  
for the set of backup LSP, just use the
"bandwidth protection desired" bit. Nothing prevents you for having 0- 
bw backup LSP and non 0 bw backup
LSP that use that bit to only book backup capacity when required.

Thanks.

JP.


On Mar 3, 2010, at 9:29 AM, Jie Dong wrote:

>
> Dear all,
>
> There is a new internet draft: draft-dong-ccamp-rsvp-te-plr- 
> designation-00:
> http://tools.ietf.org/html/draft-dong-ccamp-rsvp-te-plr-designation-00
>
> The abstract is as follows:
>
> This document defines RSVP-TE extensions which enable the ingress  
> node to
> designate particular LSRs along the path as Points of Local Repair  
> (PLRs) of
> the protected LSP, and further indicate the protection type of each  
> PLR.
> These mechanisms could enhance the control over the establishment of  
> backup
> LSPs, and also could save the resources needed for establishing and
> maintaining unnecessary backup LSPs.
>
> Comments are appreciated.
>
>
>
> Best regards,
> Jie
>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp


--Apple-Mail-220--503475206
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Dear =
Jie,<div><br></div><div>Looking at section =
3:</div><div><br></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: Times; font-size: 16px; "><pre class=3D"newpage" =
style=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; =
page-break-before: always; ">   In some scenarios the ingress node may =
need to specify particular
   LSRs as PLRs, and the protection type of each particular PLR. This
   can be helpful in many aspects. Firstly, this enables the ingress
   node to setup the backup LSPs in a more controllable way. Secondly,
   this could avoid making LSRs which do not have enough resources to
   provide local protections work as PLRs. Thirdly, this could save
   bandwidth reserved for unnecessary backup =
LSPs.</pre></span><div><div><br></div><div>First argument: why does the =
proposal allow the ingress node to set up the backup LSP =
?</div><div>Second and third arguments: If there is not enough backup =
bandwidth for the set of backup LSP, just use =
the&nbsp;</div><div>"bandwidth protection desired" bit. Nothing prevents =
you for having 0-bw backup LSP and non 0 bw backup&nbsp;</div><div>LSP =
that use that bit to only book backup capacity when =
required.</div><div><br></div><div>Thanks.</div><div><br></div><div>JP.</d=
iv><div><br></div><div><br></div><div>On Mar 3, 2010, at 9:29 AM, Jie =
Dong wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><br>Dear all, <br><br>There is a new internet draft: =
draft-dong-ccamp-rsvp-te-plr-designation-00:<br><a =
href=3D"http://tools.ietf.org/html/draft-dong-ccamp-rsvp-te-plr-designatio=
n-00">http://tools.ietf.org/html/draft-dong-ccamp-rsvp-te-plr-designation-=
00</a><br><br>The abstract is as follows: <br><br>This document defines =
RSVP-TE extensions which enable the ingress node to<br>designate =
particular LSRs along the path as Points of Local Repair (PLRs) =
of<br>the protected LSP, and further indicate the protection type of =
each PLR.<br>These mechanisms could enhance the control over the =
establishment of backup<br>LSPs, and also could save the resources =
needed for establishing and<br>maintaining unnecessary backup =
LSPs.<br><br>Comments are appreciated.<br><br><br><br>Best =
regards,<br>Jie<br><br><br>_______________________________________________=
<br>CCAMP mailing =
list<br>CCAMP@ietf.org<br>https://www.ietf.org/mailman/listinfo/ccamp<br><=
/div></blockquote></div><br></div></body></html>=

--Apple-Mail-220--503475206--

From vishwas.ietf@gmail.com  Thu Mar  4 07:52:43 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE60B28C1A0 for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 07:52:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 p7r+sO+qKgz7 for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 07:52:42 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id C113D28C1A2 for <ccamp@ietf.org>; Thu,  4 Mar 2010 07:52:42 -0800 (PST)
Received: by gyc15 with SMTP id 15so1498812gyc.31 for <ccamp@ietf.org>; Thu, 04 Mar 2010 07:52:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=3KCDOcT0tB1Mm9PbgHmg4wXwzv0Z3r0MAdFF174tx6c=; b=dfarQc51g1AKsQiEjRwwdU+3/EEdr9yImIxoAGBhOGJ6jBQYNtZisSh4auTXdcbk0x dnrw2Jmmyfv9PnT/6LolyXdZBwwO57UIcmgvMzKrXET3cEk7amwn/WpKqDem61pw8cmE OUvp8ef31fCcNnhRBdCtYI6NCLK3b8xLELxqw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VNpY8LSQU/giNbb+LrXt98N+Y7a1GjdzLVs8sXdtzH5I+udY14YPlBwPAtejobi3dS HYqNHSDf0J+M1enkJLwQ58be4C6RBlA1Cz4HZJn+Hu39f3SrRgtT1ZenpGWJC+etoHSk QT/cowTM2B1fZUdhnukeMUq8+wTeSULIz0sJQ=
MIME-Version: 1.0
Received: by 10.150.128.40 with SMTP id a40mr2595359ybd.5.1267717961865; Thu,  04 Mar 2010 07:52:41 -0800 (PST)
Date: Thu, 4 Mar 2010 07:52:41 -0800
Message-ID: <77ead0ec1003040752y3faf38e6p123b23f19eeed8ce@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: ccamp@ietf.org, jplang@ieee.org, kmitra@earthlink.net, jdrake@calient.net,  Kireeti Kompella <kireeti@juniper.net>, Yakov Rekhter <yakov@juniper.net>, lberger@movaz.com, alex.zinin@alcatel-lucent.com
Content-Type: multipart/alternative; boundary=000e0cd70656cada340480fb9663
Subject: [CCAMP] LMP critical issue
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2010 15:52:43 -0000

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

Reforwarding with the authors in the "To".

On Wed, Mar 3, 2010 at 6:46 AM, Vishwas Manral <vishwas.ietf@gmail.com>wrote:

> Hi,
>
> I find a basic and critical issue with RFC4204 - LMP.
>
> LMP defines the "Retransmission Algorithm" - Section 10.2, where a node
> transmitting a message requiring acknowledgement stops transmiision when a
> retry limit is reached.
>
> Now if in the control topology two routers are unable to communicate
> because of some intrmediate device not functioning they both timeout the
> config sends and stop. If the intermediate link/ device is corrected the IP
> reachability between the two nodes is then possible. However the control
> channel between the devices never comes up as they both stop the config
> message send. Similar issue can happen if a control channel on a device
> configured as passive happens after the active device has stopped
> retransmission.
>
> I guess it should be added that this algorithm cannot be applied for config
> messages.
>
> Thanks,
> Vishwas
>

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

Reforwarding with the authors in the &quot;To&quot;.<br><br>
<div class=3D"gmail_quote">On Wed, Mar 3, 2010 at 6:46 AM, Vishwas Manral <=
span dir=3D"ltr">&lt;<a href=3D"mailto:vishwas.ietf@gmail.com">vishwas.ietf=
@gmail.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div>Hi,</div>
<div>=A0</div>
<div>I find a basic and critical issue with RFC4204 - LMP.</div>
<div>=A0</div>
<div>LMP defines the &quot;Retransmission Algorithm&quot; - Section 10.2, w=
here a node transmitting a message requiring acknowledgement stops transmii=
sion when a retry limit is reached.</div>
<div>=A0</div>
<div>Now if in the control topology two routers are unable to communicate b=
ecause of some intrmediate device not functioning they both timeout the con=
fig sends and stop. If the intermediate link/ device is corrected the IP re=
achability between the two nodes is then possible. However the control chan=
nel between the devices never comes up as they both stop the config message=
 send. Similar issue can happen if a control channel on a device configured=
 as passive happens after=A0the active=A0device has stopped retransmission.=
</div>

<div>=A0</div>
<div>I guess it should be added that this algorithm cannot be applied for c=
onfig messages.</div>
<div>=A0</div>
<div>Thanks,</div>
<div>Vishwas</div></blockquote></div><br>

--000e0cd70656cada340480fb9663--

From francesco.fondelli@gmail.com  Thu Mar  4 08:12:17 2010
Return-Path: <francesco.fondelli@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE91128C1E8; Thu,  4 Mar 2010 08:12:17 -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 9q2F02SI1LSO; Thu,  4 Mar 2010 08:12:16 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id 377C928C1E0; Thu,  4 Mar 2010 08:12:16 -0800 (PST)
Received: by fxm5 with SMTP id 5so2995465fxm.29 for <multiple recipients>; Thu, 04 Mar 2010 08:12:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=poSIUAn+v/agKWYc0G6BkUejBv5DqfGQq0QjJunXMPc=; b=cixUiW2jxFWZaL/lpwyJfcTIgRq22xRBeUb/87SIYFFWVGi0yQ1OB2LVooR/ZvnpRM ofcrbQBJ59Wn2lI3/KG/8YlyM1Mw7rsA0G4lxQBeZmjclXVujabUigs2uUw50BrGQ/im VZbjymUXhvazLNbRq+KRElDIk6ycK3+m9GSJU=
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=Qtn1iicqBgbFygMidsIXdOafdC2KvVHcKmN9SJXTSrW0QbfSM++CGam2CAaFu2JVS3 azYY31uIU28b8s6KdeTkFtQwMhEIjFb2fMNqTDfJomrkSsEVoGzkJLsP1dxEWTYEV0fr 3uro+5SM+XfXyvxbOjP8zzDIaqUScadtLT38s=
MIME-Version: 1.0
Received: by 10.223.6.153 with SMTP id 25mr3854239faz.81.1267719133878; Thu,  04 Mar 2010 08:12:13 -0800 (PST)
In-Reply-To: <B4E97C5E-3860-46B8-A522-579B6400D079@cisco.com>
References: <05d401cabaab$a0348190$bf0c6f0a@china.huawei.com> <B4E97C5E-3860-46B8-A522-579B6400D079@cisco.com>
Date: Thu, 4 Mar 2010 17:12:13 +0100
Message-ID: <7c923b5e1003040812g6e3dec6bh3598a4427be16116@mail.gmail.com>
From: Francesco Fondelli <francesco.fondelli@gmail.com>
To: JP Vasseur <jvasseur@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mpls@ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] New Draft Notification: draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2010 16:12:17 -0000

On Thu, Mar 4, 2010 at 3:46 PM, JP Vasseur <jvasseur@cisco.com> wrote:
> Dear Jie,
> Second and third arguments: If there is not enough backup bandwidth for
[cut]

fourth argument:

Didn't RFC 4873 already "allow (a) the signaling of
desired LSP segment protection type, (b) upstream nodes to optionally
identify where segment protection starts and stops, (c) the optional
identification of hops used on protection segments, and (d) the
reporting of paths used to protect an LSP."?

I believe you can setup and explicitly control backup
LSPs if you follow RFC 4873 *and* RFC 4090... I've never done it,
though.

Ciao
FF

From cfinss@dial.pipex.com  Thu Mar  4 10:24:26 2010
Return-Path: <cfinss@dial.pipex.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 048803A8E14 for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 10:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D6gguCWW1TYA for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 10:24:21 -0800 (PST)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by core3.amsl.com (Postfix) with ESMTP id C50AB3A8E26 for <ccamp@ietf.org>; Thu,  4 Mar 2010 10:24:12 -0800 (PST)
X-Trace: 188172545/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.105.210/None/cfinss@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.105.210
X-IP-MAIL-FROM: cfinss@dial.pipex.com
X-SMTP-AUTH: 
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcGAFOJj0s+vGnS/2dsb2JhbACBeoVYiQ6LT7hPDYRvBA
X-IronPort-AV: E=Sophos;i="4.49,582,1262563200"; d="scan'208";a="188172545"
X-IP-Direction: IN
Received: from 1cust210.tnt2.lnd9.gbr.da.uu.net (HELO allison) ([62.188.105.210]) by smtp.pipex.tiscali.co.uk with SMTP; 04 Mar 2010 18:23:29 +0000
Message-ID: <005a01cabbbf$3ec31380$0601a8c0@allison>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "BRUNGARD, DEBORAH A \(ATTLABS\)" <db3546@att.com>, "CCAMP" <ccamp@ietf.org>
References: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
Date: Thu, 4 Mar 2010 17:44:42 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Re: [CCAMP] [mpls] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2010 18:24:26 -0000

no/do not support

Much if not most of this document seems to be a reproduction of other, existing
mpls-tp documents.  The reproductions do not seem to add value.  Thus I cannot
see how reproducing over 100 requirements already listed elsewhere with an
identifying number and then giving them a new set of numbers which can easily be
confused with the old numbers will advance this work.

Much if not most of this document talks much about matters outside the control
plane and in places would appear to contradict what has already been documented.

There seems little in it that would count as a framework or architecture or
similar construct (compared to e.g draft-ietf-mpls-tp-framework).

Its target status is Informational, which makes it difficult for any Standards
Track document to refer to it, and that seems appropriate.

Tom Petch

----- Original Message -----
From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
To: "CCAMP" <ccamp@ietf.org>
Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <mpls-tp@ietf.org>
Sent: Friday, February 26, 2010 10:53 PM
Subject: [mpls] poll on draft-abfb-mpls-tp-control-plane-framework


> All,
>
> This is to start a two week working group poll on making
> draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working
> group document. This poll is being initiated at this time as this
> document is part of the MPLS-TP work and it is needed to progress the
> work.
>
> Send your response to the ccamp@ietf.org mailing list (only), indicating
> "yes/support" or "no/do not support".
>
> This poll ends March 12th.
>
> Deborah
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From tom.nadeau@bt.com  Thu Mar  4 10:50:49 2010
Return-Path: <tom.nadeau@bt.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B440E28C0D7 for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 10:50:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.532
X-Spam-Level: 
X-Spam-Status: No, score=-1.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVmxfTgTd0dT for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 10:50:48 -0800 (PST)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id E589B3A8E14 for <ccamp@ietf.org>; Thu,  4 Mar 2010 10:50:47 -0800 (PST)
Received: from E03MVA4-UKBR.domain1.systemhost.net ([193.113.197.105]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Mar 2010 18:50:48 +0000
Received: from 217.32.164.181 ([217.32.164.181]) by E03MVA4-UKBR.domain1.systemhost.net ([193.113.197.56]) via Exchange Front-End Server mail.bt.com ([193.113.197.150]) with Microsoft Exchange Server HTTP-DAV ; Thu,  4 Mar 2010 18:50:47 +0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Thu, 04 Mar 2010 13:50:46 -0500
From: "Thomas D. Nadeau" <tom.nadeau@bt.com>
To: "tom.petch" <cfinss@dial.pipex.com>, "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>, CCAMP <ccamp@ietf.org>
Message-ID: <C7B56B36.1B13C%tom.nadeau@bt.com>
Thread-Topic: [CCAMP] [mpls] poll on draft-abfb-mpls-tp-control-plane-framework
Thread-Index: Acq7y5loe+N19eAh7UmsD3pzQ9/Rbw==
In-Reply-To: <005a01cabbbf$3ec31380$0601a8c0@allison>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 04 Mar 2010 18:50:48.0833 (UTC) FILETIME=[9B18CF10:01CABBCB]
Subject: Re: [CCAMP] [mpls] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2010 18:50:49 -0000

    I'd largely agree with Tom on his points. I've just read through the
document and am confused as to what it is trying to accomplish. It seems to
be neither a framework for deploying MPLS-TP, a requirements document for
building MPLS-TP devices, nor a specification for implementing protocols
around MPLS-TP.  IMHO, it seems to be a subset of requirements from 5654
with brief discussions and references. To the reader, this is very confusing
given that the document proclaims that it provides:

the framework for MPLS-TP dynamic provisioning,
   and covers control plane addressing, routing, path computation,
   signaling, traffic engineering,, and path recovery.

    At best, I'd consider the document in its current state as an attempt to
"refine" the requirements from RFC5654 and behave more like a "solution"
document. As an operator, I'd be hard pressed to use the document in its
current state to deploy MPLS-TP.  As someone who has built boxes in the
past, I would be very hard pressed to use this document to build MPLS-TP
boxes, but I will let current vendors speak to that.

    Based on this reading, I'd personally ask the chairs that the document's
structure and purpose be made more clear before proceeding forward with the
draft.

    --Tom



On 3/4/10 11:44 AM, "tom.petch" <cfinss@dial.pipex.com> wrote:

> no/do not support
> 
> Much if not most of this document seems to be a reproduction of other,
> existing
> mpls-tp documents.  The reproductions do not seem to add value.  Thus I cannot
> see how reproducing over 100 requirements already listed elsewhere with an
> identifying number and then giving them a new set of numbers which can easily
> be
> confused with the old numbers will advance this work.
> 
> Much if not most of this document talks much about matters outside the control
> plane and in places would appear to contradict what has already been
> documented.
> 
> There seems little in it that would count as a framework or architecture or
> similar construct (compared to e.g draft-ietf-mpls-tp-framework).
> 
> Its target status is Informational, which makes it difficult for any Standards
> Track document to refer to it, and that seems appropriate.
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
> To: "CCAMP" <ccamp@ietf.org>
> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <mpls-tp@ietf.org>
> Sent: Friday, February 26, 2010 10:53 PM
> Subject: [mpls] poll on draft-abfb-mpls-tp-control-plane-framework
> 
> 
>> All,
>> 
>> This is to start a two week working group poll on making
>> draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working
>> group document. This poll is being initiated at this time as this
>> document is part of the MPLS-TP work and it is needed to progress the
>> work.
>> 
>> Send your response to the ccamp@ietf.org mailing list (only), indicating
>> "yes/support" or "no/do not support".
>> 
>> This poll ends March 12th.
>> 
>> Deborah
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
> 
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp




From lberger@labn.net  Thu Mar  4 14:13:26 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50DA128C123 for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 14:13:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.131
X-Spam-Level: 
X-Spam-Status: No, score=-2.131 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n+33olfcxWm9 for <ccamp@core3.amsl.com>; Thu,  4 Mar 2010 14:13:24 -0800 (PST)
Received: from outbound-mail-313.bluehost.com (outbound-mail-313.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id 149D83A8CA3 for <ccamp@ietf.org>; Thu,  4 Mar 2010 14:13:24 -0800 (PST)
Received: (qmail 5275 invoked by uid 0); 4 Mar 2010 22:13:26 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 4 Mar 2010 22:13:26 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=1SWZJ9mlSlZXC3RmqGteo8SMnqkHA8XZUQoQHoBqN0BaqY/47eRkBVTPyOWC7gSCcA4IGCa68zsE20gbIU5uJnlobVoa8RHx37RNSvluRkD/1WRvfm2GYDS06ElHx8Qs;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1NnJIM-0004v9-7a; Thu, 04 Mar 2010 15:13:26 -0700
Message-ID: <4B90309A.4070107@labn.net>
Date: Thu, 04 Mar 2010 17:13:46 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20091214 Eudora/3.0b4
MIME-Version: 1.0
To: Francesco Fondelli <francesco.fondelli@gmail.com>
References: <05d401cabaab$a0348190$bf0c6f0a@china.huawei.com>	<B4E97C5E-3860-46B8-A522-579B6400D079@cisco.com> <7c923b5e1003040812g6e3dec6bh3598a4427be16116@mail.gmail.com>
In-Reply-To: <7c923b5e1003040812g6e3dec6bh3598a4427be16116@mail.gmail.com>
X-Enigmail-Version: 0.96a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: mpls@ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] New Draft Notification:	draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2010 22:13:26 -0000

Francesco,

If memory serves, you are correct.  See section 2 of RFC4873, search for
4090.

Lou

On 3/4/2010 11:12 AM, Francesco Fondelli wrote:
> On Thu, Mar 4, 2010 at 3:46 PM, JP Vasseur <jvasseur@cisco.com> wrote:
>> Dear Jie,
>> Second and third arguments: If there is not enough backup bandwidth for
> [cut]
> 
> fourth argument:
> 
> Didn't RFC 4873 already "allow (a) the signaling of
> desired LSP segment protection type, (b) upstream nodes to optionally
> identify where segment protection starts and stops, (c) the optional
> identification of hops used on protection segments, and (d) the
> reporting of paths used to protect an LSP."?
> 
> I believe you can setup and explicitly control backup
> LSPs if you follow RFC 4873 *and* RFC 4090... I've never done it,
> though.
> 
> Ciao
> FF
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
> 
> 
> 

From dongjie_dj@huawei.com  Thu Mar  4 22:36:37 2010
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31D223A8EED; Thu,  4 Mar 2010 22:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.846
X-Spam-Level: 
X-Spam-Status: No, score=-0.846 tagged_above=-999 required=5 tests=[AWL=-0.351, 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 A8HmiO+PUo5O; Thu,  4 Mar 2010 22:36:36 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 3324B3A89C7; Thu,  4 Mar 2010 22:36:36 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYS00C24QCPGO@szxga03-in.huawei.com>; Fri, 05 Mar 2010 14:36:25 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYS00H2TQCPX1@szxga03-in.huawei.com>; Fri, 05 Mar 2010 14:36:25 +0800 (CST)
Received: from d65110 ([10.111.12.191]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KYS00GSEQCOI4@szxml06-in.huawei.com>; Fri, 05 Mar 2010 14:36:25 +0800 (CST)
Date: Fri, 05 Mar 2010 14:36:24 +0800
From: Jie Dong <dongjie_dj@huawei.com>
In-reply-to: <B4E97C5E-3860-46B8-A522-579B6400D079@cisco.com>
To: 'JP Vasseur' <jvasseur@cisco.com>
Message-id: <06e501cabc2e$2d855230$bf0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acq7qaN5gSxvUQxDQZWnl9Kdgxy/UQAgPe+w
Cc: mpls@ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] New Draft Notification: draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 06:36:37 -0000

Hi JP,
 
Thanks for your comment. please see my replies begin with [Jie].

First argument: why does the proposal allow the ingress node to set up the
backup LSP ?

[Jie] This draft is not to allow the ingress to explicitly setup backup
LSPs, but to allow it have more control on the establishment of backup LSPs.
Such control may be helpful to reduce unnecessary back LSPs based on
information of the network and operators' policy.

Second and third arguments: If there is not enough backup bandwidth for the
set of backup LSP, just use the 
"bandwidth protection desired" bit. Nothing prevents you for having 0-bw
backup LSP and non 0 bw backup 
LSP that use that bit to only book backup capacity when required.

[Jie] This can be a solution for controlling backup LSPs, but it may not
work in all scenarios. One example is even when there is enough bandwidth,
operators may do not want to reserve such bandwidth for backup LSPs.
	

Best regards,
Jie


	On Mar 3, 2010, at 9:29 AM, Jie Dong wrote:



		Dear all, 
		
		There is a new internet draft:
draft-dong-ccamp-rsvp-te-plr-designation-00:
	
http://tools.ietf.org/html/draft-dong-ccamp-rsvp-te-plr-designation-00
		
		The abstract is as follows: 
		
		This document defines RSVP-TE extensions which enable the
ingress node to
		designate particular LSRs along the path as Points of Local
Repair (PLRs) of
		the protected LSP, and further indicate the protection type
of each PLR.
		These mechanisms could enhance the control over the
establishment of backup
		LSPs, and also could save the resources needed for
establishing and
		maintaining unnecessary backup LSPs.
		
		Comments are appreciated.
		
		
		
		Best regards,
		Jie
		
		
		_______________________________________________
		CCAMP mailing list
		CCAMP@ietf.org
		https://www.ietf.org/mailman/listinfo/ccamp
		




From dongjie_dj@huawei.com  Fri Mar  5 00:19:23 2010
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA66528C1DE; Fri,  5 Mar 2010 00:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.758
X-Spam-Level: 
X-Spam-Status: No, score=-0.758 tagged_above=-999 required=5 tests=[AWL=-0.263, 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 gooi8xzsoAE2; Fri,  5 Mar 2010 00:19:21 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 38FBC3A88C8; Fri,  5 Mar 2010 00:19:21 -0800 (PST)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYS006T9V3YSF@szxga01-in.huawei.com>; Fri, 05 Mar 2010 16:19:11 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYS00E4IV3YJC@szxga01-in.huawei.com>; Fri, 05 Mar 2010 16:19:10 +0800 (CST)
Received: from d65110 ([10.111.12.191]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KYS0012DV3YIA@szxml04-in.huawei.com>; Fri, 05 Mar 2010 16:19:10 +0800 (CST)
Date: Fri, 05 Mar 2010 16:19:10 +0800
From: Jie Dong <dongjie_dj@huawei.com>
In-reply-to: <7c923b5e1003040812g6e3dec6bh3598a4427be16116@mail.gmail.com>
To: 'Francesco Fondelli' <francesco.fondelli@gmail.com>, lberger@labn.net
Message-id: <06f501cabc3c$88881600$bf0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acq7tXktb6fSO9KvQvCyEi66SBsxDQAeMXuQ
Cc: mpls@ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] New Draft Notification: draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 08:19:23 -0000

Hi Francesco, Lou, 

Thanks for your comments and information.

> Didn't RFC 4873 already "allow (a) the signaling of desired 
> LSP segment protection type, (b) upstream nodes to optionally 
> identify where segment protection starts and stops, (c) the 
> optional identification of hops used on protection segments, 
> and (d) the reporting of paths used to protect an LSP."?

RFC 4873 provides a way for GMPLS to explicitly control segment recovery.
But the mechanism in rfc4873 may be a bit complex for fast reroute in packet
switch networks. And I am not sure if currently most routers have
implemented this.

This draft is a simple and backward compatible extension to TE FRR defined
in RFC 4090, and the benefit is similar to RFC4873.

> I believe you can setup and explicitly control backup LSPs if 
> you follow RFC 4873 *and* RFC 4090... I've never done it, though.

For a implementation which support both of this, maybe we can. But  this
draft may still be helpful in environments where only rfc4090 is
implemented.


Best regards,
Jie
 

> -----Original Message-----
> From: Francesco Fondelli [mailto:francesco.fondelli@gmail.com] 
> Sent: Friday, March 05, 2010 12:12 AM
> To: JP Vasseur
> Cc: Jie Dong; mpls@ietf.org; ccamp@ietf.org
> Subject: Re: [CCAMP] New Draft Notification: 
> draft-dong-ccamp-rsvp-te-plr-designation-00
> 
> On Thu, Mar 4, 2010 at 3:46 PM, JP Vasseur <jvasseur@cisco.com> wrote:
> > Dear Jie,
> > Second and third arguments: If there is not enough backup bandwidth 
> > for
> [cut]
> 
> fourth argument:
> 

> 

> 
> Ciao
> FF
> 


From jvasseur@cisco.com  Fri Mar  5 02:09:02 2010
Return-Path: <jvasseur@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9B293A8F48; Fri,  5 Mar 2010 02:09:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.549
X-Spam-Level: 
X-Spam-Status: No, score=-9.549 tagged_above=-999 required=5 tests=[AWL=1.050,  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 hpOaP14XRuvE; Fri,  5 Mar 2010 02:09:01 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id D92DF3A8F47; Fri,  5 Mar 2010 02:09:01 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAI1nkEutJV2d/2dsb2JhbACbRXOccphohH0E
X-IronPort-AV: E=Sophos;i="4.49,586,1262563200"; d="scan'208";a="492079359"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by sj-iport-6.cisco.com with ESMTP; 05 Mar 2010 10:08:58 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id o25A8X4m005221;  Fri, 5 Mar 2010 10:08:57 GMT
Received: from xfe-ams-101.cisco.com ([144.254.231.93]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 5 Mar 2010 11:08:45 +0100
Received: from ams-jvasseur-8713.cisco.com ([10.55.201.132]) by xfe-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 5 Mar 2010 11:08:44 +0100
Message-Id: <C237A2EC-4944-407C-9739-5722CCB56B14@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: Jie Dong <dongjie_dj@huawei.com>
In-Reply-To: <06e501cabc2e$2d855230$bf0c6f0a@china.huawei.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 5 Mar 2010 11:08:41 +0100
References: <06e501cabc2e$2d855230$bf0c6f0a@china.huawei.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 05 Mar 2010 10:08:44.0776 (UTC) FILETIME=[D6EAC680:01CABC4B]
Cc: mpls@ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] New Draft Notification: draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 10:09:02 -0000

On Mar 5, 2010, at 7:36 AM, Jie Dong wrote:

>
> Hi JP,
>
> Thanks for your comment. please see my replies begin with [Jie].
>
> First argument: why does the proposal allow the ingress node to set  
> up the
> backup LSP ?
>
> [Jie] This draft is not to allow the ingress to explicitly setup  
> backup
> LSPs, but to allow it have more control on the establishment of  
> backup LSPs.
> Such control may be helpful to reduce unnecessary back LSPs based on
> information of the network and operators' policy.
>
> Second and third arguments: If there is not enough backup bandwidth  
> for the
> set of backup LSP, just use the
> "bandwidth protection desired" bit. Nothing prevents you for having  
> 0-bw
> backup LSP and non 0 bw backup
> LSP that use that bit to only book backup capacity when required.
>
> [Jie] This can be a solution for controlling backup LSPs, but it may  
> not
> work in all scenarios. One example is even when there is enough  
> bandwidth,
> operators may do not want to reserve such bandwidth for backup LSPs.
> 	

That seems a bit awkward to me. Usually if you provision backup  
capacity and you can accommodate
a primary TE LSP, why would you want not to do it ? Then if you cannot  
accommodate them all, there
many existing techniques.
Last but not least such mechanism requires to know the path in advance  
to be effective. What do you
do when you reroute ?

Thanks.

JP.

>
> Best regards,
> Jie
>
>
> 	On Mar 3, 2010, at 9:29 AM, Jie Dong wrote:
>
>
>
> 		Dear all,
> 		
> 		There is a new internet draft:
> draft-dong-ccamp-rsvp-te-plr-designation-00:
> 	
> http://tools.ietf.org/html/draft-dong-ccamp-rsvp-te-plr-designation-00
> 		
> 		The abstract is as follows:
> 		
> 		This document defines RSVP-TE extensions which enable the
> ingress node to
> 		designate particular LSRs along the path as Points of Local
> Repair (PLRs) of
> 		the protected LSP, and further indicate the protection type
> of each PLR.
> 		These mechanisms could enhance the control over the
> establishment of backup
> 		LSPs, and also could save the resources needed for
> establishing and
> 		maintaining unnecessary backup LSPs.
> 		
> 		Comments are appreciated.
> 		
> 		
> 		
> 		Best regards,
> 		Jie
> 		
> 		
> 		_______________________________________________
> 		CCAMP mailing list
> 		CCAMP@ietf.org
> 		https://www.ietf.org/mailman/listinfo/ccamp
> 		
>
>
>


From dongjie_dj@huawei.com  Fri Mar  5 03:36:56 2010
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AA833A89D1; Fri,  5 Mar 2010 03:36:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.116
X-Spam-Level: 
X-Spam-Status: No, score=-0.116 tagged_above=-999 required=5 tests=[AWL=-0.221, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_56=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tN6nXdj45rNc; Fri,  5 Mar 2010 03:36:55 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 239BC3A879A; Fri,  5 Mar 2010 03:36:55 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYT004UN49AL6@szxga04-in.huawei.com>; Fri, 05 Mar 2010 19:36:47 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYT0085W49AGU@szxga04-in.huawei.com>; Fri, 05 Mar 2010 19:36:46 +0800 (CST)
Received: from d65110 ([10.111.12.191]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KYT009D349ATZ@szxml04-in.huawei.com>; Fri, 05 Mar 2010 19:36:46 +0800 (CST)
Date: Fri, 05 Mar 2010 19:36:46 +0800
From: Jie Dong <dongjie_dj@huawei.com>
In-reply-to: <C237A2EC-4944-407C-9739-5722CCB56B14@cisco.com>
To: 'JP Vasseur' <jvasseur@cisco.com>
Message-id: <071b01cabc58$23430860$bf0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acq8S+mHTK0O9bc9SCKbSiYkCAz4lwAAsbvg
Cc: mpls@ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] New Draft Notification: draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 11:36:56 -0000

> > [Jie] This can be a solution for controlling backup LSPs, 
> but it may 
> > not work in all scenarios. One example is even when there is enough 
> > bandwidth, operators may do not want to reserve such bandwidth for 
> > backup LSPs.
> > 	
> 
> That seems a bit awkward to me. Usually if you provision 
> backup capacity and you can accommodate a primary TE LSP, why 
> would you want not to do it ?
SP can choose to protect some specific nodes based on network topology,
resource, policy, etc. 
Sometimes more protection LSPs do not mean higher availability.
There can be a case like this: 
The SP has the knowledge that some nodes on the path are using some other
mechanisms to insure survivability, thus a local repair for such nodes is
unneeded. Thus explicitly inform this can save resources of establishing and
maintaining unneeded backup LSPs. 
In this case, the key point here is not whether there is enough bandwidth,
but to determine whether backup paths are needed. If such backup LSPs are
unnecessary, there is no need to waste bandwidth on them.

Besides, based on RFC 4090, all the nodes(except the egress) along the LSP
will be candidate PLRs and will spend resources on establishment and
maintenance of backup paths. 
With this draft, non-PLR nodes do not need to participate in fast reroute
processing.

> Then if you cannot accommodate 
> them all, there many existing techniques.
Do you mean RFC 4873? 

> Last but not least such mechanism requires to know the path 
> in advance to be effective. What do you do when you reroute ?
I don't get your point here. Could you please give more clarification?


Best regards,
Jie


> 
> >
> > Best regards,
> > Jie
> >
> >
> > 	On Mar 3, 2010, at 9:29 AM, Jie Dong wrote:
> >
> >
> >
> > 		Dear all,
> > 		
> > 		There is a new internet draft:
> > draft-dong-ccamp-rsvp-te-plr-designation-00:
> > 	
> > 
> http://tools.ietf.org/html/draft-dong-ccamp-rsvp-te-plr-designation-00
> > 		
> > 		The abstract is as follows:
> > 		
> > 		This document defines RSVP-TE extensions which 
> enable the ingress 
> > node to
> > 		designate particular LSRs along the path as 
> Points of Local Repair 
> > (PLRs) of
> > 		the protected LSP, and further indicate the 
> protection type of each 
> > PLR.
> > 		These mechanisms could enhance the control over 
> the establishment of 
> > backup
> > 		LSPs, and also could save the resources needed 
> for establishing and
> > 		maintaining unnecessary backup LSPs.
> > 		
> > 		Comments are appreciated.
> > 		
> > 		
> > 		
> > 		Best regards,
> > 		Jie
> > 		
> > 		
> > 		_______________________________________________
> > 		CCAMP mailing list
> > 		CCAMP@ietf.org
> > 		https://www.ietf.org/mailman/listinfo/ccamp
> > 		
> >
> >
> >
> 


From loa@pi.nu  Fri Mar  5 05:15:43 2010
Return-Path: <loa@pi.nu>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 387CB28C27E; Fri,  5 Mar 2010 05:15:43 -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 LKNinc1NWUBR; Fri,  5 Mar 2010 05:15:42 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 503BB3A8F87; Fri,  5 Mar 2010 05:15:42 -0800 (PST)
Received: from [79.138.206.63] (79.138.206.63.bredband.tre.se [79.138.206.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 291E6D4052; Fri,  5 Mar 2010 14:15:40 +0100 (CET)
Message-ID: <4B91040A.4020100@pi.nu>
Date: Fri, 05 Mar 2010 14:15:54 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, mpls@ietf.org,  CCAMP WG <ccamp@ietf.org>, pwe3@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
References: <4B7C43CF.3070700@pi.nu>
In-Reply-To: <4B7C43CF.3070700@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [CCAMP] Closed - Re: [mpls] poll on draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 13:15:43 -0000

All,

this poll has been closed.

We have accepted the draft as an mpls working group document.

Could the authors please re-publish the draft with no other
changes than file-name and version as:

draft-ietf-mpls-tp-lsp-ping-bfd-procedures-02.txt

/Loa

Loa Andersson wrote:
> All,
> 
> 
> this is to start a two week working group poll on making
> draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-02.txt
> an mpls working group document.
> 
> Send your response to the mpls-tp@ietf.org mailing list
> (only), indicating "yes/support" or "no/do not support".
> 
> The poll ends eob March 5th 2001.
> 
> /Loa

-- 


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 root@core3.amsl.com  Fri Mar  5 08:45:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 2B46D28C1FF; Fri,  5 Mar 2010 08:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100305164502.2B46D28C1FF@core3.amsl.com>
Date: Fri,  5 Mar 2010 08:45:02 -0800 (PST)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-wson-signal-compatibility-ospf-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 16:45:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : OSPF Enhancement for Signal and Network Element Compatibility for Wavelength Switched Optical Networks
	Author(s)       : Y. Lee, G. Bernstein
	Filename        : draft-ietf-ccamp-wson-signal-compatibility-ospf-01.txt
	Pages           : 9
	Date            : 2010-03-05

This document provides GMPLS OSPF routing enhancements to support
signal compatibility constraints associated with WSON network
elements. These routing enhancements are required in common optical
or hybrid electro-optical networks where not all of the optical
signals in the network are compatible with all network elements
participating in the network.

This compatibility constraint model is applicable to common optical
or hybrid electro optical systems such as OEO switches, regenerators,
and wavelength converters since such systems can be limited to
processing only certain types of WSON signals.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-wson-signal-compatibility-ospf-01.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-wson-signal-compatibility-ospf-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From root@core3.amsl.com  Fri Mar  5 09:00:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 21ACF3A8B1D; Fri,  5 Mar 2010 09:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100305170002.21ACF3A8B1D@core3.amsl.com>
Date: Fri,  5 Mar 2010 09:00:02 -0800 (PST)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 17:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : Configuration of pro-active MPLS-TP Operations, Administration, and Maintenance (OAM) Functions Using RSVP-TE or LSP Ping
	Author(s)       : E. Bellagamba, et al.
	Filename        : draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-01.txt
	Pages           : 19
	Date            : 2010-03-05

This specification describes the configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Functions for a
given LSP using a common set of TLVs that is carried on either
RSVP-TE or LSP Ping.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-01.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From loa@pi.nu  Fri Mar  5 10:12:58 2010
Return-Path: <loa@pi.nu>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCE8D3A897A; Fri,  5 Mar 2010 10:12:58 -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 m3i24BEguVgB; Fri,  5 Mar 2010 10:12:57 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 42BA83A8D05; Fri,  5 Mar 2010 10:12:57 -0800 (PST)
Received: from [192.168.0.101] (h133n2fls33o883.telia.com [217.208.62.133]) (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 C19B0D4052; Fri,  5 Mar 2010 19:12:57 +0100 (CET)
Message-ID: <4B9149A8.8020503@pi.nu>
Date: Fri, 05 Mar 2010 19:12:56 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: mpls-chairs@tools.ietf.org, mpls@ietf.org, CCAMP <ccamp@ietf.org>,  pwe3@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [CCAMP] working group last call on draft-ietf-mpls-tp-oam-framework-05.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 18:12:59 -0000

All,


this is to start a two week mpls  working group last call on
draft-ietf-mpls-tp-oam-framework-05.txt.

Please review and send your comments to the mpls-tp@ietf.org mailing list.
Please do not copy the other mailing lists this working group last call
is announced on.

The working group last call ends March 19th.

Loa and George

--

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

From wwwrun@core3.amsl.com  Fri Mar  5 09:55:03 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 2CEAC3A8CDE; Fri,  5 Mar 2010 09:55:03 -0800 (PST)
From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: lberger@labn.net,dbrungard@att.com
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100305175503.2CEAC3A8CDE@core3.amsl.com>
Date: Fri,  5 Mar 2010 09:55:03 -0800 (PST)
X-Mailman-Approved-At: Fri, 05 Mar 2010 13:11:34 -0800
Cc: hiroshi.ota@itu.int, greg.jones@itu.int, steve.trowbridge@alcatel-lucent.com, ccamp@ietf.org, yoichi.maeda@ntt-at.co.jp, paf@cisco.com, adrian.farrel@huawei.com, rcallon@juniper.net, tsbsg15@itu.int
Subject: [CCAMP] New Liaison Statement, "LS138 - Amendment 2 to G.872 OTN          architecture"
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tsbsg15@itu.int
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 17:55:03 -0000

Title: LS138 - Amendment 2 to G.872 OTN architecture
Submission Date: 2010-03-05
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=844 

From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF CCAMP WG(lberger@labn.net,dbrungard@att.com)
Cc: paf@cisco.com
adrian.farrel@huawei.com
rcallon@juniper.net
ccamp@ietf.org
yoichi.maeda@ntt-at.co.jp
steve.trowbridge@alcatel-lucent.com
Reponse Contact: tsbsg15@itu.int
greg.jones@itu.int
hiroshi.ota@itu.int
Technical Contact: malcolm.betts@zte.com.cn
Purpose: For information 
Body: Q12/15 is in the process of updating G.872 the OTN architecture to reflect the changes in the OTN rates and formats defined in G.709.  The most significant additions are the inclusion of the ODU0 and the ODUflex, that allows a flexible use of bandwidth.  The most significant change to the architecture is that we now clarified that the ODU is modelled as a single layer network, with the bit rate (of the client) represented as a parameter.  This evolution of OTN has identified a number of significant new requirements from the perspective of the control plane including:
Support for the new ODU rates, ODU0, ODU4 and ODUflex
Support for the new server layer (OTU4)
The ability to provide the information required for path computation
This includes the requirement to be able to describe the maximum payload bandwidth that can be accommodated on a link as well as the total available bandwidth.
Maintain the independence between the service rate (the rate of the ODU including ODUflex) and the OTU or higher order ODU link that it is carried over.
Provide the information that is necessary to allow each node to compute the number of TS required and the location of the stuff opportunities.
We have attached the current draft of G.872 amendment 2, we hope that you will find this useful in your work on the extension of the GMPLS protocols to support OTN.
Attachment:  WD10r5nc
Attachment(s):
     LS138 - Amendment 2 to G.872 OTN architecture - body pdf (https://datatracker.ietf.org/documents/LIAISON/file956.pdf)
     LS138 - Attach: current draft of G.872 amendment 2 (https://datatracker.ietf.org/documents/LIAISON/file957.pdf)




From loa@pi.nu  Sat Mar  6 09:28:13 2010
Return-Path: <loa@pi.nu>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 746573A8ABC; Sat,  6 Mar 2010 09:28:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19gcyGn-ajCF; Sat,  6 Mar 2010 09:28:12 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id AD58D3A8D7D; Sat,  6 Mar 2010 09:28:12 -0800 (PST)
Received: from [192.168.0.101] (h133n2fls33o883.telia.com [217.208.62.133]) (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 6F6E2D4055; Sat,  6 Mar 2010 18:28:12 +0100 (CET)
Message-ID: <4B9290D1.2080902@pi.nu>
Date: Sat, 06 Mar 2010 18:28:49 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, mpls@ietf.org,  CCAMP <ccamp@ietf.org>, pwe3@ietf.org
References: <20100305191502.17B8F28C0F0@core3.amsl.com>
In-Reply-To: <20100305191502.17B8F28C0F0@core3.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [CCAMP] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2010 17:28:13 -0000

All,

this is to start a three week MPLS working group last call on

http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt

Please review and send your comments only to the mpls-tp@ietf.org
mailing list.

The working group last call end March 28, 2010.

Loa and George


-- 


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 gregimirsky@gmail.com  Sat Mar  6 12:26:48 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2289328C197; Sat,  6 Mar 2010 12:26:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCVKr4OIlKDd; Sat,  6 Mar 2010 12:26:47 -0800 (PST)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id 4FF2F28C0F0; Sat,  6 Mar 2010 12:26:45 -0800 (PST)
Received: by bwz22 with SMTP id 22so1763385bwz.28 for <multiple recipients>; Sat, 06 Mar 2010 12:26:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Uyffio8J6GfUpPeQfJQtAAj9bRa0vjtvAblLKGA4NjI=; b=XT+9Etrnd+8iCFp9PUAJfLTRCx6wf6NipxFX9SXd8oDX6cA4R2fzR73L8IaM/T+CvV yz/Y3Hitu5r0yWZQl3Ax06Y1ZugWGfj2K3geKXOiY28WKmbdyD9Pkvamq8NMx+SUm3cK GEYH0EJZIPsTGuc241Zx32brpZqKgXJfNQUi4=
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=Eydsht6sSgHedEA1WnrsxLMHvph2Z0djBSDRL0tR2jODBfbdjpep8adnTgF1Dgsukx 89NMS9wFI9A2rRa6MiA1sibazjrBNCyEC5cyzCIfJLceGH5I+edEUSy3yVUsobf1Xwl7 83ZZyComK//SyNZftUfV7W1fls8HqNXWOb5l0=
MIME-Version: 1.0
Received: by 10.204.131.82 with SMTP id w18mr2235194bks.29.1267907203777; Sat,  06 Mar 2010 12:26:43 -0800 (PST)
In-Reply-To: <4B9290D1.2080902@pi.nu>
References: <20100305191502.17B8F28C0F0@core3.amsl.com> <4B9290D1.2080902@pi.nu>
Date: Sat, 6 Mar 2010 12:26:43 -0800
Message-ID: <787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Loa Andersson <loa@pi.nu>
Content-Type: multipart/alternative; boundary=00151747bd3a7d47c1048127a621
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, pwe3@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2010 20:26:48 -0000

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

Dear Authors and All,
my question on how the Type range control been organized. Is the whole range
from 0x0000 through 0xffff controlled by IANA? Would we like to leave some
smaller range out for experimental use?

Regards,
Greg

On Sat, Mar 6, 2010 at 9:28 AM, Loa Andersson <loa@pi.nu> wrote:

> All,
>
> this is to start a three week MPLS working group last call on
>
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt
>
> Please review and send your comments only to the mpls-tp@ietf.org
> mailing list.
>
> The working group last call end March 28, 2010.
>
> Loa and George
>
>
> --
>
>
> 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
>

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

Dear Authors and All,<br>my question on how the Type range control been org=
anized. Is the whole range from 0x0000 through 0xffff controlled by IANA? W=
ould we like to leave some smaller range out for experimental use?<br><br>
Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Sat, Mar 6, 2010 at 9=
:28 AM, Loa Andersson <span dir=3D"ltr">&lt;<a href=3D"mailto:loa@pi.nu">lo=
a@pi.nu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padd=
ing-left: 1ex;">
All,<br>
<br>
this is to start a three week MPLS working group last call on<br>
<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-0=
2.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-mpl=
s-tp-ach-tlv-02.txt</a><br>
<br>
Please review and send your comments only to the <a href=3D"mailto:mpls-tp@=
ietf.org" target=3D"_blank">mpls-tp@ietf.org</a><br>
mailing list.<br>
<br>
The working group last call end March 28, 2010.<br>
<br>
Loa and George<br>
<br>
<br>
-- <br><font color=3D"#888888">
<br>
<br>
Loa Andersson =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 email: <a hre=
f=3D"mailto:loa.andersson@ericsson.com" target=3D"_blank">loa.andersson@eri=
csson.com</a><br>
Sr Strategy and Standards Manager =A0 =A0 =A0 =A0 =A0 =A0<a href=3D"mailto:=
loa@pi.nu" target=3D"_blank">loa@pi.nu</a><br>
Ericsson Inc =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phone: +46 =
10 717 52 13<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 +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>
</font></blockquote></div><br>

--00151747bd3a7d47c1048127a621--

From gregimirsky@gmail.com  Sat Mar  6 12:43:05 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03FBD28C203; Sat,  6 Mar 2010 12:43:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.032,  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 vhfatrHoXvi2; Sat,  6 Mar 2010 12:43:04 -0800 (PST)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id 5620528C202; Sat,  6 Mar 2010 12:43:03 -0800 (PST)
Received: by bwz22 with SMTP id 22so1773287bwz.28 for <multiple recipients>; Sat, 06 Mar 2010 12:43:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Y12MLmOvb//LEHMT87WSAqzGd2QB45WZjDv5JNGjqBc=; b=pQWlIS4I++LEfk587Sd+OUHHwZLav1+7j0f6RxN5KeMf3VJdtNBVPqq32o4tv7w9DZ KeugnmcHDqoQPfSj95cO466IYKjb22OkvhDF1jnAVHokaC2O7DzEZpFpNyk+UnXL0+ZX NXdLPQT3vGty442O8sZpgmbrlG+rnyPRCK7K8=
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=sCgHkLVb6yDF4BYIPphRBQ43dXUVqnTldiUxExgPs0SfcPfvAnndVBqrHP6RwTt4jD yC9uyh84lk45AA3tqPM/K2Vq72gj9SygloUWhA7t22S/n/v9oySiYTDE4xOvjnyYVSAo XE0i3D1al4Yrpdpa0SdtwACIODZd0+XHB/MQY=
MIME-Version: 1.0
Received: by 10.204.7.203 with SMTP id e11mr2253392bke.39.1267908182534; Sat,  06 Mar 2010 12:43:02 -0800 (PST)
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
References: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
Date: Sat, 6 Mar 2010 12:43:02 -0800
Message-ID: <787be2781003061243r47bfe558t52855eb9c5468fb2@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
Content-Type: multipart/alternative; boundary=0015174c1972d3ee30048127e090
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2010 20:43:05 -0000

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

yes/support

Regards,
Greg

On Fri, Feb 26, 2010 at 1:53 PM, BRUNGARD, DEBORAH A (ATTLABS) <
db3546@att.com> wrote:

> All,
>
> This is to start a two week working group poll on making
> draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working
> group document. This poll is being initiated at this time as this
> document is part of the MPLS-TP work and it is needed to progress the
> work.
>
> Send your response to the ccamp@ietf.org mailing list (only), indicating
> "yes/support" or "no/do not support".
>
> This poll ends March 12th.
>
> Deborah
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

--0015174c1972d3ee30048127e090
Content-Type: text/html; charset=ISO-8859-1

yes/support<br><br>Regards,<br>Greg<br><br><div class="gmail_quote">On Fri, Feb 26, 2010 at 1:53 PM, BRUNGARD, DEBORAH A (ATTLABS) <span dir="ltr">&lt;<a href="mailto:db3546@att.com">db3546@att.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">All,<br>
<br>
This is to start a two week working group poll on making<br>
draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working<br>
group document. This poll is being initiated at this time as this<br>
document is part of the MPLS-TP work and it is needed to progress the<br>
work.<br>
<br>
Send your response to the <a href="mailto:ccamp@ietf.org">ccamp@ietf.org</a> mailing list (only), indicating<br>
&quot;yes/support&quot; or &quot;no/do not support&quot;.<br>
<br>
This poll ends March 12th.<br>
<br>
Deborah<br>
_______________________________________________<br>
pwe3 mailing list<br>
<a href="mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/pwe3" target="_blank">https://www.ietf.org/mailman/listinfo/pwe3</a><br>
</blockquote></div><br>

--0015174c1972d3ee30048127e090--

From gregimirsky@gmail.com  Sat Mar  6 13:06:51 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 643663A8BD2; Sat,  6 Mar 2010 13:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.030,  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 6eNOxD+kR2tV; Sat,  6 Mar 2010 13:06:50 -0800 (PST)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id 037103A8982; Sat,  6 Mar 2010 13:06:49 -0800 (PST)
Received: by bwz22 with SMTP id 22so1786276bwz.28 for <multiple recipients>; Sat, 06 Mar 2010 13:06:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=dVuptVswlFYKI9bRgMOMlUI/Ubi8t4WsLfmn+DmqeBM=; b=rMhM8HUh9XFyMa+OW/bzopQUhbTAAbza9XDe1LmVQb3v3UkIfDViHSv32Nt1wSSbIu KrgUdPjBKKkHMz5+RGAb6rnKUaiScXZs46c631jmrByeaM0tabXzR0rw7Cp8OCG07je2 66sItg3lSZtbzz6NlIQNXgk2B5HbRrQP6hI7c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=v9CHK2yseHmWkC+MfR1LF5AVymjXCQALCb6UlA7xo3w/qOnVyuUY8jyDMgB/jgSCJV LkmvmgoEP6EZkhHpjfMPkpMEnJZGD4ouxeSMtRvABDVsWdBMRTRoF67LBONuA0beRLhB ECa+MVd5iNeYSbwpDXhOdeDJMYm3Hy7PfFJes=
MIME-Version: 1.0
Received: by 10.204.26.198 with SMTP id f6mr2282137bkc.13.1267909607390; Sat,  06 Mar 2010 13:06:47 -0800 (PST)
Date: Sat, 6 Mar 2010 13:06:46 -0800
Message-ID: <787be2781003061306u348722e7v47c52756adb92f03@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Loa Andersson <loa.andersson@ericsson.com>, Lou Berger <lberger@labn.net>, lufang@cisco.com,  nabil.n.bitar@verizon.com, mpls@ietf.org, mpls-tp@ietf.org, ccamp@ietf.org
Content-Type: multipart/alternative; boundary=000325554b2ec1b4400481283519
Subject: [CCAMP] Question RE: draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2010 21:06:51 -0000

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

Dear Editors, Authors and All,
I've a question about portraying PW sublayer and LDP control plane in
Figures 1 and 2 of the document. Though Section 5 differentiates SS-PW from
MS-PW, mentions differences between S-PE and T-PE, the graphical depictions
of the MPLS-TP Control Plane portray PW and LDP sublayers as single segment,
end-to-end entities. If MS-PW is not outside of the scope of the document,
as I couldn't find that being stated in the text, would it be proper that
the MPLS-TP Control Plane Reference Model reflect the fact that MS-PW being
switched at S-PEs (even if PW Label remains the same)?

Regards,
Greg

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

Dear Editors, Authors and All,<br>I&#39;ve a question about portraying PW s=
ublayer and LDP control plane in Figures 1 and 2 of the document. Though Se=
ction 5 differentiates SS-PW from MS-PW, mentions differences between S-PE =
and T-PE, the graphical depictions of the MPLS-TP Control Plane portray PW =
and LDP sublayers as single segment, end-to-end entities. If MS-PW is not o=
utside of the scope of the document, as I couldn&#39;t find that being stat=
ed in the text, would it be proper that the MPLS-TP Control Plane Reference=
 Model reflect the fact that MS-PW being switched at S-PEs (even if PW Labe=
l remains the same)?<br>
<br>Regards,<br>Greg<br>

--000325554b2ec1b4400481283519--

From stbryant@cisco.com  Sat Mar  6 14:30:34 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1385B3A9015; Sat,  6 Mar 2010 14:30:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.365
X-Spam-Level: 
X-Spam-Status: No, score=-7.365 tagged_above=-999 required=5 tests=[AWL=3.234,  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 cbgva4oSD9eG; Sat,  6 Mar 2010 14:30:33 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 0CE113A900B; Sat,  6 Mar 2010 14:30:31 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuAAAHJmkkuQ/uCWe2dsb2JhbACbSRUBAQsLJAYcnimBOgoBlksChHYE
X-IronPort-AV: E=Sophos;i="4.49,596,1262563200"; d="scan'208";a="57779976"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 06 Mar 2010 22:30:33 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o26MUVC3001071; Sat, 6 Mar 2010 22:30:31 GMT
Received: from Stewarts-Computer-2.local (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o26MUUX19409; Sat, 6 Mar 2010 22:30:30 GMT
Message-ID: <4B92D785.7050600@cisco.com>
Date: Sat, 06 Mar 2010 22:30:29 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <20100305191502.17B8F28C0F0@core3.amsl.com>	<4B9290D1.2080902@pi.nu> <787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com>
In-Reply-To: <787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, pwe3@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] WG Last Call on	draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2010 22:30:34 -0000

Greg Mirsky wrote:
> Dear Authors and All,
> my question on how the Type range control been organized. Is the whole 
> range from 0x0000 through 0xffff controlled by IANA? 
> Would we like to leave some smaller range out for experimental use?
>
I imagine that we could allocate a small number (say 8) for experimental 
in the same way that we did for for the ACH itself.

- Stewart

> Regards,
> Greg
>
> On Sat, Mar 6, 2010 at 9:28 AM, Loa Andersson <loa@pi.nu 
> <mailto:loa@pi.nu>> wrote:
>
>     All,
>
>     this is to start a three week MPLS working group last call on
>
>     http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt
>
>     Please review and send your comments only to the mpls-tp@ietf.org
>     <mailto:mpls-tp@ietf.org>
>     mailing list.
>
>     The working group last call end March 28, 2010.
>
>     Loa and George
>
>
>     -- 
>
>
>     Loa Andersson                         email:
>     loa.andersson@ericsson.com <mailto:loa.andersson@ericsson.com>
>     Sr Strategy and Standards Manager            loa@pi.nu
>     <mailto:loa@pi.nu>
>     Ericsson Inc                          phone: +46 10 717 52 13
>                                                 +46 767 72 92 13
>     _______________________________________________
>     mpls mailing list
>     mpls@ietf.org <mailto:mpls@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mpls
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
>   


From curtis@occnc.com  Sun Mar  7 13:44:51 2010
Return-Path: <curtis@occnc.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FEB53A91B0; Sun,  7 Mar 2010 13:44:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[AWL=0.315,  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 VUqvEaVJm46T; Sun,  7 Mar 2010 13:44:50 -0800 (PST)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 7F6983A91B2; Sun,  7 Mar 2010 13:44:50 -0800 (PST)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o27LiqYp038299; Sun, 7 Mar 2010 16:44:52 -0500 (EST) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201003072144.o27LiqYp038299@harbor.orleans.occnc.com>
To: Loa Andersson <loa@pi.nu>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Sat, 06 Mar 2010 18:28:49 +0100." <4B9290D1.2080902@pi.nu> 
Date: Sun, 07 Mar 2010 16:44:52 -0500
Sender: curtis@occnc.com
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, pwe3@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 21:44:51 -0000

In message <4B9290D1.2080902@pi.nu>
Loa Andersson writes:
>  
> All,
>  
> this is to start a three week MPLS working group last call on
>  
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt
>  
> Please review and send your comments only to the mpls-tp@ietf.org
> mailing list.
>  
> The working group last call end March 28, 2010.
>  
> Loa and George


This would be a good time to define a capabilities TLV with wording to
indicate that IANA will assign capabilities identifiers.

  x.x  Capabilities

    This TLV specifies a set of capabilities to be defined as needed
    if an when it becomes advantageous for each end to agree on the
    use of specific protocol extensions.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         AchTlvType = TBD      |        Length = 2             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    Capability Number    |E|Req|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Capability Number - To be assigned by IANA as needed by future
      RFCs

      E - the enabled bit

        0 - currently disabled
	1 - currently enabled

      Req - requirement code

        11 - requires that thie capability ben enabled
	10 - requires that this capability be disabled
	01 - prefer that this capability be enabled
	00 - don't care if capability is enabled or disabled

    The Req bits contain a "prefer" and a "don't care" so that a
    difference of preference resolves to "enable".  If one end
    indicated Req=11 and the other indicates Req=10, then
    administrative action may be required.  These values should only
    be used in situations where the network equipment cannot function
    properly with a capability enabled or disabled.

    Absense of this TLV for a given capability indicates no change
    from prior value.  If an unknown capability is recieved, a TLV
    with E=0 and Req=10 SHOULD be returned.  Absense of a prior TLV
    for a given capability MUST be interpreted as E=0 and Req=10.

Is this a reasonable addition?  I hope we don't exceed 8K extensions!

Curtis

From lberger@labn.net  Mon Mar  8 08:49:11 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EED373A6A57 for <ccamp@core3.amsl.com>; Mon,  8 Mar 2010 08:49:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.158
X-Spam-Level: 
X-Spam-Status: No, score=-2.158 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gIaLtpv-6uMm for <ccamp@core3.amsl.com>; Mon,  8 Mar 2010 08:49:11 -0800 (PST)
Received: from outbound-mail-158.bluehost.com (outbound-mail-158.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id C17DC3A6A51 for <ccamp@ietf.org>; Mon,  8 Mar 2010 08:49:11 -0800 (PST)
Received: (qmail 18864 invoked by uid 0); 8 Mar 2010 16:42:36 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy2.bluehost.com with SMTP; 8 Mar 2010 16:42:36 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=DRmkUXJb5k2L/iMqSaYpG/p8WHmrAumbIscB6/+OmOhoE4TH2OGAeQmvOg8+SAtE9F76MMS0YNnw+5tvdi5megiXJDYv/T+WXPtKizsRMP9/fEUwtfX/RdXmpg+3HUK7;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1Nog2O-00032f-JZ; Mon, 08 Mar 2010 09:42:36 -0700
Message-ID: <4B952900.5080506@labn.net>
Date: Mon, 08 Mar 2010 11:42:40 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20091214 Eudora/3.0b4
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <787be2781003061306u348722e7v47c52756adb92f03@mail.gmail.com>
In-Reply-To: <787be2781003061306u348722e7v47c52756adb92f03@mail.gmail.com>
X-Enigmail-Version: 0.96a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: Loa Andersson <loa.andersson@ericsson.com>, mpls@ietf.org, ccamp@ietf.org, nabil.n.bitar@verizon.com, mpls-tp@ietf.org, lufang@cisco.com
Subject: Re: [CCAMP] Question RE: draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 16:49:12 -0000

Greg,
	MS-PW and SS-PW are in scope for both TP and TP's control plane.  The
control plane framework document does mention MS-PW a few times, and I
don't expect any change of this.

MS-PWs aren't shown in Figures 1 and 2 for simplicity.  We can at least
change the text of Section 1 to make this explicit.  We'll also take a
look at the figure to see if we can add MS-PWs and still have a sensical
figure.

Thank you for the comment.

Lou

On 3/6/2010 4:06 PM, Greg Mirsky wrote:
> Dear Editors, Authors and All,
> I've a question about portraying PW sublayer and LDP control plane in
> Figures 1 and 2 of the document. Though Section 5 differentiates SS-PW
> from MS-PW, mentions differences between S-PE and T-PE, the graphical
> depictions of the MPLS-TP Control Plane portray PW and LDP sublayers as
> single segment, end-to-end entities. If MS-PW is not outside of the
> scope of the document, as I couldn't find that being stated in the text,
> would it be proper that the MPLS-TP Control Plane Reference Model
> reflect the fact that MS-PW being switched at S-PEs (even if PW Label
> remains the same)?
> 
> Regards,
> Greg

From mach@huawei.com  Mon Mar  8 09:24:38 2010
Return-Path: <mach@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F71E3A6AD4; Mon,  8 Mar 2010 09:24:38 -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 p55hF33at-ku; Mon,  8 Mar 2010 09:24:32 -0800 (PST)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id CBF1C3A6A53; Mon,  8 Mar 2010 09:23:59 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYZ008IW4BWM8@szxga02-in.huawei.com>; Tue, 09 Mar 2010 01:23:57 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYZ0090Q4BW7T@szxga02-in.huawei.com>; Tue, 09 Mar 2010 01:23:56 +0800 (CST)
Received: from LENOVOmach (93-63-164-158.ip28.fastwebnet.it [93.63.164.158]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KYZ006ND4BR1M@szxml01-in.huawei.com>; Tue, 09 Mar 2010 01:23:56 +0800 (CST)
Date: Tue, 09 Mar 2010 01:23:51 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <4B9290D1.2080902@pi.nu>
To: Loa Andersson <loa@pi.nu>, mpls-tp@ietf.org, mpls@ietf.org, CCAMP <ccamp@ietf.org>, pwe3@ietf.org
Message-id: <5233FB2334A447558DB31F2D3D54B977@LENOVOmach>
Organization: Huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8089.726
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <20100305191502.17B8F28C0F0@core3.amsl.com> <4B9290D1.2080902@pi.nu>
Subject: Re: [CCAMP] [PWE3] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Mach Chen <mach@huawei.com>
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 17:24:38 -0000

Hi authors,

I just read the draft, in section 2.4(ICC TLV):

 0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         AchTlvType = 3        |       Length = 16             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     ICC                                       |
   |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Based on the picture above, the Length should be 6, but not 16, am I right?

Best regards,
Mach

--------------------------------------------------
From: "Loa Andersson" <loa@pi.nu>
Sent: Sunday, March 07, 2010 1:28 AM
To: <mpls-tp@ietf.org>; <mpls@ietf.org>; "CCAMP" <ccamp@ietf.org>; 
<pwe3@ietf.org>
Subject: [PWE3] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt

> All,
>
> this is to start a three week MPLS working group last call on
>
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt
>
> Please review and send your comments only to the mpls-tp@ietf.org
> mailing list.
>
> The working group last call end March 28, 2010.
>
> Loa and George
>
>
> -- 
>
>
> Loa Andersson                         email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3 


From stbryant@cisco.com  Mon Mar  8 09:51:51 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C71F3A6A0D; Mon,  8 Mar 2010 09:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.688
X-Spam-Level: 
X-Spam-Status: No, score=-7.688 tagged_above=-999 required=5 tests=[AWL=2.911,  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 bejO1h+xDJwJ; Mon,  8 Mar 2010 09:51:48 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A500E3A68B2; Mon,  8 Mar 2010 09:51:47 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvAAANLHlEuQ/uCWe2dsb2JhbACbKhUBAQsLJAYcowCBOgoBllYChHYE
X-IronPort-AV: E=Sophos;i="4.49,603,1262563200"; d="scan'208";a="57822219"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 08 Mar 2010 17:51:50 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o28Hpo29001900; Mon, 8 Mar 2010 17:51:50 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-55.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o28HpnX27456; Mon, 8 Mar 2010 17:51:49 GMT
Message-ID: <4B953935.1030602@cisco.com>
Date: Mon, 08 Mar 2010 17:51:49 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Mach Chen <mach@huawei.com>
References: <20100305191502.17B8F28C0F0@core3.amsl.com>	<4B9290D1.2080902@pi.nu> <5233FB2334A447558DB31F2D3D54B977@LENOVOmach>
In-Reply-To: <5233FB2334A447558DB31F2D3D54B977@LENOVOmach>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [PWE3] WG Last Call on	draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 17:51:51 -0000

Mach

Yes - Its a typo that results from incorrectly editing a 13 to a 6.

Will fix in the next version.

Thanks

Stewart



Mach Chen wrote:
> Hi authors,
>
> I just read the draft, in section 2.4(ICC TLV):
>
> 0                   1                   2                   3
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |         AchTlvType = 3        |       Length = 16             |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                     ICC                                       |
>   |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                               |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Based on the picture above, the Length should be 6, but not 16, am I 
> right?
>
> Best regards,
> Mach
>
> --------------------------------------------------
> From: "Loa Andersson" <loa@pi.nu>
> Sent: Sunday, March 07, 2010 1:28 AM
> To: <mpls-tp@ietf.org>; <mpls@ietf.org>; "CCAMP" <ccamp@ietf.org>; 
> <pwe3@ietf.org>
> Subject: [PWE3] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
>
>> All,
>>
>> this is to start a three week MPLS working group last call on
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt
>>
>> Please review and send your comments only to the mpls-tp@ietf.org
>> mailing list.
>>
>> The working group last call end March 28, 2010.
>>
>> Loa and George
>>
>>
>> -- 
>>
>>
>> Loa Andersson                         email: loa.andersson@ericsson.com
>> Sr Strategy and Standards Manager            loa@pi.nu
>> Ericsson Inc                          phone: +46 10 717 52 13
>>                                              +46 767 72 92 13
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3 
>
> _______________________________________________
> 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  Mon Mar  8 09:59:43 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 858C93A6A53; Mon,  8 Mar 2010 09:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.953
X-Spam-Level: 
X-Spam-Status: No, score=-3.953 tagged_above=-999 required=5 tests=[AWL=-1.354, 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 ZmvR2ukxOZPM; Mon,  8 Mar 2010 09:59:42 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 223C43A68B2; Mon,  8 Mar 2010 09:59:40 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvAAAO/JlEuQ/uCWe2dsb2JhbACbKxUBAQsLJAYcoweBOgoBllUChHYE
X-IronPort-AV: E=Sophos;i="4.49,603,1262563200";  d="scan'208";a="4097706"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-2.cisco.com with ESMTP; 08 Mar 2010 17:26:40 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o28Hxh5M003297; Mon, 8 Mar 2010 17:59:43 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-55.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o28HxhX28002; Mon, 8 Mar 2010 17:59:43 GMT
Message-ID: <4B953B0F.8050800@cisco.com>
Date: Mon, 08 Mar 2010 17:59:43 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Mach Chen <mach@huawei.com>
References: <20100305191502.17B8F28C0F0@core3.amsl.com>	<4B9290D1.2080902@pi.nu>	<5233FB2334A447558DB31F2D3D54B977@LENOVOmach> <4B953935.1030602@cisco.com>
In-Reply-To: <4B953935.1030602@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [PWE3] WG Last Call	on	draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 17:59:43 -0000

Just to be clear, it should be

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|         AchTlvType = 3        |       Length = 6              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                     ICC                                       |
|                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                               |              
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Stewart

Stewart Bryant wrote:
> Mach
>
> Yes - Its a typo that results from incorrectly editing a 13 to a 6.
>
> Will fix in the next version.
>
> Thanks
>
> Stewart
>
>
>
> Mach Chen wrote:
>> Hi authors,
>>
>> I just read the draft, in section 2.4(ICC TLV):
>>
>> 0                   1                   2                   3
>>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>   |         AchTlvType = 3        |       Length = 16             |
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>   |                     ICC                                       |
>>   |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>   |                               |
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> Based on the picture above, the Length should be 6, but not 16, am I 
>> right?
>>
>> Best regards,
>> Mach
>>
>> --------------------------------------------------
>> From: "Loa Andersson" <loa@pi.nu>
>> Sent: Sunday, March 07, 2010 1:28 AM
>> To: <mpls-tp@ietf.org>; <mpls@ietf.org>; "CCAMP" <ccamp@ietf.org>; 
>> <pwe3@ietf.org>
>> Subject: [PWE3] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
>>
>>> All,
>>>
>>> this is to start a three week MPLS working group last call on
>>>
>>> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt
>>>
>>> Please review and send your comments only to the mpls-tp@ietf.org
>>> mailing list.
>>>
>>> The working group last call end March 28, 2010.
>>>
>>> Loa and George
>>>
>>>
>>> -- 
>>>
>>>
>>> Loa Andersson                         email: loa.andersson@ericsson.com
>>> Sr Strategy and Standards Manager            loa@pi.nu
>>> Ericsson Inc                          phone: +46 10 717 52 13
>>>                                              +46 767 72 92 13
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3 
>>
>> _______________________________________________
>> 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 Italo.Busi@alcatel-lucent.com  Mon Mar  8 10:06:48 2010
Return-Path: <Italo.Busi@alcatel-lucent.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2471D3A6A99; Mon,  8 Mar 2010 10:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 CXKARnEs7lCt; Mon,  8 Mar 2010 10:06:47 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 8C0CF3A6A34; Mon,  8 Mar 2010 10:06:46 -0800 (PST)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.dc-m.alcatel-lucent.com [155.132.6.75]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o28I6h3C022975;  Mon, 8 Mar 2010 19:06:43 +0100
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Mar 2010 19:06:43 +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_01CABEEA.1BBF8FE5"
Date: Mon, 8 Mar 2010 19:09:43 +0100
Message-ID: <6FD21B53861BF44AA90A288402036AB402FBC599@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <7CC717E2F49DAA4A827DA3FEA237111BEFC460@XMB-RCD-103.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Request for input onhttp://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs
Thread-Index: Acq6ftM/d56A9tz1TeOQwAS8hyVlUwEangwg
References: <7CC717E2F49DAA4A827DA3FEA237111BEFC460@XMB-RCD-103.cisco.com>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.com>
To: "Zafar Ali (zali)" <zali@cisco.com>, <mpls@ietf.org>, <ccamp@ietf.org>
X-OriginalArrivalTime: 08 Mar 2010 18:06:43.0972 (UTC) FILETIME=[1C4A0C40:01CABEEA]
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Cc: Adrian Farrel <Adrian.Farrel@huawei.com>, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] Request for input onhttp://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 18:06:48 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CABEEA.1BBF8FE5
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It would be interesting to understand the relationship between the =
decription in this draft and the description in =
draft-ietf-mpls-tp-framework-10.
=20
My understanding is that:
- edge-to-edge LSPs will be setup with the "Ignore PID" option (as per =
section 2.3 of Ali's draft);
- service LSPs carrying multiple clients will be setup with the "Ignore =
PID" option (as per section 2.3): the encaps label will provide PID =
information;
- service LSPs carrying only IPv4 client will be setup using the IPv4 =
option (as per section 2.1 of Ali's draft);=20
- service LSPs carrying only IPv6 client will be setup using the IPv6 =
option (as per section 2.2 of Ali's draft).
=20
Is my understanding correct?
=20
Assuming my understanding is correct, then I have the following =
additional questions: how are service LSPs carrying only MPLS clients =
setup?
=20
Do we need to add another section for the 0x8847 (MPLS payload) case?
=20
Thanks, Italo


P.S. Please note my new email address, Italo.Busi@alcatel-lucent.com, =
effective since 1 November 2009.


=20


________________________________

	From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
Zafar Ali (zali)
	Sent: mercoled=EC 3 marzo 2010 4.09
	To: mpls@ietf.org; ccamp@ietf.org
	Cc: Adrian Farrel
	Subject: [mpls] Request for input =
onhttp://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02S=
ignaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs
=09
=09

	Dear fellows-=20

	I am planning to update =
http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02 =
<http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02> =
 "Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs", =
before IETF flood gate closes. I would like to address any comments/ =
input you have on the draft.
=09
	Your comments will be greatly appreciated.=20

	Thanks=20

	Regards... Zafar=20


------_=_NextPart_001_01CABEEA.1BBF8FE5
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Request for input on =
http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02 =
Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16981" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>It would be interesting to understand the =
relationship=20
between the decription in this draft and the description in=20
draft-ietf-mpls-tp-framework-10.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>My understanding is that:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>- edge-to-edge LSPs will be setup with the =
"Ignore PID"=20
option (as per section 2.3 of Ali's draft);</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>- service LSPs carrying multiple clients will =
be setup=20
with the "Ignore PID" option (as per section 2.3): the encaps label will =
provide=20
PID information;</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>- service LSPs carrying only IPv4 client will =
be setup=20
using the IPv4 option (as per section 2.1 of Ali's draft);
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010><SPAN class=3D585530018-08032010>- service =
LSPs carrying=20
only IPv6 client will be setup using the IPv6 option (as per section 2.2 =
of=20
Ali's draft).</SPAN></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010><SPAN=20
class=3D585530018-08032010></SPAN></SPAN></FONT></SPAN></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN=20
class=3D585530018-08032010></SPAN></FONT>&nbsp;</DIV></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>Is my understanding =
correct?</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>Assuming my understanding is correct, then I =
have the=20
following additional questions:&nbsp;</SPAN></FONT><FONT face=3DArial=20
color=3D#0000ff size=3D2><SPAN class=3D585530018-08032010>how are =
service LSPs=20
carrying only MPLS clients setup?</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>Do we need to add another section for the =
0x8847 (MPLS=20
payload) case?</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D585530018-08032010>Thanks, Italo</SPAN></FONT><FONT face=3DArial =

color=3D#0000ff size=3D2></FONT></DIV><!-- Converted from text/plain =
format --><BR>
<P><FONT size=3D2>P.S. Please note my new email address,=20
Italo.Busi@alcatel-lucent.com, effective since 1 November =
2009.<BR></FONT></P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; 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>Zafar Ali=20
  (zali)<BR><B>Sent:</B> mercoled=EC 3 marzo 2010 4.09<BR><B>To:</B>=20
  mpls@ietf.org; ccamp@ietf.org<BR><B>Cc:</B> Adrian =
Farrel<BR><B>Subject:</B>=20
  [mpls] Request for input=20
  =
onhttp://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-case-02S=
ignaled=20
  PID When Multiplexing Multiple PIDs over RSVP-TE =
LSPs<BR></FONT><BR></DIV>
  <DIV></DIV><!-- Converted from text/rtf format -->
  <P><FONT face=3D"Times New Roman" color=3D#000080>Dear fellows-</FONT> =
</P>
  <P><FONT face=3D"Times New Roman" color=3D#000080>I am planning to =
update=20
  </FONT><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multiplexing-ca=
se-02"><U></U><U><FONT=20
  face=3D"Times New Roman"=20
  =
color=3D#0000ff>http://tools.ietf.org/html/draft-ali-mpls-sig-pid-multipl=
exing-case-02</FONT></U></A><U></U><U><FONT=20
  face=3D"Times New Roman" color=3D#000080> "</FONT></U><FONT =
face=3D"Times New Roman"=20
  color=3D#000080>Signaled PID When Multiplexing Multiple PIDs over =
RSVP-TE LSPs",=20
  before IETF flood gate closes. I would like to address any comments/ =
input you=20
  have on the draft.<B><BR></B></FONT><BR><FONT face=3D"Times New Roman" =

  color=3D#000080>Your comments will be greatly appreciated. </FONT></P>
  <P><FONT face=3D"Times New Roman" color=3D#000080>Thanks</FONT> </P>
  <P><FONT face=3D"Times New Roman" color=3D#000080>Regards=85 Zafar=20
</FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CABEEA.1BBF8FE5--

From vishwas.ietf@gmail.com  Mon Mar  8 10:25:48 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 022E43A6A32 for <ccamp@core3.amsl.com>; Mon,  8 Mar 2010 10:25:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  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 VlHIxD8wr3H1 for <ccamp@core3.amsl.com>; Mon,  8 Mar 2010 10:25:47 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 8B5663A6A99 for <ccamp@ietf.org>; Mon,  8 Mar 2010 10:25:45 -0800 (PST)
Received: by gwb10 with SMTP id 10so3326937gwb.31 for <ccamp@ietf.org>; Mon, 08 Mar 2010 10:25:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=aQi6fhOi2yla7UpeRDDEP1m7+70fCK6P7amFSMZkl4g=; b=qqs/FwS3jslVprDU3l/mL2XpqnvwBMGG0662GVXLoIavUu+krqCWgJXso4lCFubc83 qt79+hVNzMQG95edbtu2fVknrkxHkIKij7JJBdqbiV38LspEGsCO/C/8thNDoGSIg1XF HSBjIQeqCcmyKlgoUKiDaK+NgOdgz/Jv8tdjE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=qsHooLK2qrRs/lGZzbzSor90SPIkp0rnmU5ORmEC0gkonsmkUiQ3mpt9fGiLb9TSkH CrtqSp/teOmcSKpH00/tk7HEU1Q5zrLnuId9zs2oQmKAEitCJFi0kWuWE41MAszhZGez 1n9b+kbtmkCJJ3XEIkzljUbAUdAg8//X0oCEc=
MIME-Version: 1.0
Received: by 10.150.119.37 with SMTP id r37mr3422405ybc.17.1268072746317; Mon,  08 Mar 2010 10:25:46 -0800 (PST)
Date: Mon, 8 Mar 2010 10:25:46 -0800
Message-ID: <77ead0ec1003081025y2b09a1e4laa13376d50b0921f@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: ccamp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [CCAMP] LMP Message ID
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 18:25:48 -0000

Hi LMP-authors,

I noticed that the Message-ID usage in LMP is very confusing and
unclear, have a look at section 7.

   For TE link specific messages, the Message_Id field is within the
scope of the LMP adjacency.

However in the same section for LinkSummary message the message-id is

   "less than the largest Message_Id value previously received from the
   sender for the TE Link, then the message SHOULD be treated as being
   out-of-order."

Here it seems to say the LinkSummary message Message-id is on a TE link basis.

For Channel Status Message

   "the most recently received Message_Id value
   associated with at least one of the data channels included in the
   message, the message MUST NOT be treated as out of order"

This means the message_id is also on a Datalink basis.

In my view the best way forward would be to not have special cases for
different message types and instead allow retransmits to use new
message id's.

Do let me know your views?

Thanks,
Vishwas

From vishwas.ietf@gmail.com  Mon Mar  8 10:32:47 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB2123A6AC9 for <ccamp@core3.amsl.com>; Mon,  8 Mar 2010 10:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M28Cf59ZblUg for <ccamp@core3.amsl.com>; Mon,  8 Mar 2010 10:32:44 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 709E83A6B00 for <ccamp@ietf.org>; Mon,  8 Mar 2010 10:32:43 -0800 (PST)
Received: by gwb10 with SMTP id 10so3329355gwb.31 for <ccamp@ietf.org>; Mon, 08 Mar 2010 10:32:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=JU5wt995aRi1yytg4jD/ydWWswVKmcO2o//2nv/DafI=; b=e8wb7/+Wj+WWlTi7aYlRKjLlTf3ouH2gIcoDdOdg4Sec39kDxIF5uBVz9HNXqMnKMV RXDaXhP87PLV07UmNvd8VwlC8dJaFhc5EDm9aXDFrQKQ1gpq2dTH+9ecvifTsD9Xpjsz Dsr0BTKLot4HBBXB6HcpQ/NNBCsP3iAXPJiKk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=FWKAqqC4h/SHltkP0Kj8UkpjesWcUTeCDW6b5Mq3z6Tz/4jrVBUN8ejJlbB4oNgAQR iHbfH+5vOVsI+uw3ZJjw85d1arLh1svbRp0TwjZwriXHFYXARNlA+hs8mQSdKcgiNMR1 WnlHIdZMZGTM5v9+UpJ80GguIRJWKFKya/q0w=
MIME-Version: 1.0
Received: by 10.151.86.17 with SMTP id o17mr4468603ybl.117.1268073164019; Mon,  08 Mar 2010 10:32:44 -0800 (PST)
Date: Mon, 8 Mar 2010 10:32:43 -0800
Message-ID: <77ead0ec1003081032p2b37f76er38cde7d050f29b79@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: ccamp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [CCAMP] LMP IPv6 issues
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 18:32:48 -0000

Hi LMP authors,

LMP is used to verify the Local and Remote Link identifiers of a TE
link. The identifiers are always 32 bit and exchanged in OSPF/ IS-IS
TE information (RFC4203).

However in LMP for IPv6 the identifier is 128 bits long. This seems to
be a discripancy and is wrong. Do let me know what can be done to
correct the same?

Thanks,
Vishwas

From wwwrun@core3.amsl.com  Mon Mar  8 13:13:37 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 09D953A69BE; Mon,  8 Mar 2010 13:13:36 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20100308211337.09D953A69BE@core3.amsl.com>
Date: Mon,  8 Mar 2010 13:13:36 -0800 (PST)
Cc: ccamp mailing list <ccamp@ietf.org>, Internet Architecture Board <iab@iab.org>, ccamp chair <ccamp-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [CCAMP] Protocol Action: 'Generalized Multi-Protocol Label Switching (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)' to Proposed Standard
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 21:13:37 -0000

The IESG has approved the following document:

- 'Generalized Multi-Protocol Label Switching (GMPLS) Protocol Extensions 
   for Multi-Layer and Multi-Region Networks (MLN/MRN) '
   <draft-ietf-ccamp-gmpls-mln-extensions-12.txt> as a Proposed Standard


This document is the product of the Common Control and Measurement Plane Working Group. 

The IESG contact persons are Adrian Farrel and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-mln-extensions-12.txt

Technical Summary

   This document extends GMPLS routing and signaling to support the
   operation of GMPLS Multi-Layer/Multi-Region Networks. A network
   comprised of multiple switching types (e.g. PSC and TDM) controlled
   by a single GMPLS control plane instance is called a Multi-Region
   Network (MRN).  A network comprising transport nodes participating in
   different data plane switching layers controlled by a single GMPLS
   control plane instance is called a Multi-Layer Network (MLN). This
   document defines GMPLS RSVP, OSPF and IS-IS to cover GMPLS MLN/MRN
   requirements.

Working Group Summary

   This document received much attention and discussion in its early
   revisions.  The document has been largely stable for quite some time,
   mainly needing revisions as part of the publication process.

Document Quality

   There have been no public statements related to intent to implement, 
   but portions of the extensions are now being used as part of the GMPLS
   tool set and are (at least) expected to implemented in those contexts.

Personnel

   Lou Berger (lberger@labn.net) is the Document Shepherd.
   Adrian Farrel (adrian.farrel@huawei.com) is the Responsible AD

RFC Editor Note

   RFC Editor - we suggest that you treat this I-D as part of a cluster
   including the following five documents.

   draft-ietf-ccamp-ethernet-traffic-parameters
   draft-ietf-ccamp-gmpls-dcsc-channel-ext
   draft-ietf-ccamp-gmpls-ether-svcs
   draft-ietf-ccamp-gmpls-mef-uni
   draft-ietf-ccamp-gmpls-mln-extensions
---
Section 1
s/TDM switching (TDM)/Time-Division Multiplexing Switching (TDM)/
---
Section 5.1 final paragraph
s/CALL ATTRIBUTES/CALL_ATTRIBUTES/
---
Section 5.1.5 paragraph 1
s/the Attributes Flags/the Call Attributes Flags/
---

IANA Note

   IANA - Please note that this I-D creates a registry which is
   also used by draft-ietf-ccamp-gmpls-ether-svcs which is also
   in the pipeline


From gregimirsky@gmail.com  Mon Mar  8 14:44:58 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F29D3A6A06; Mon,  8 Mar 2010 14:44:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.029,  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 LVUwDXwRMSFC; Mon,  8 Mar 2010 14:44:57 -0800 (PST)
Received: from mail-bw0-f211.google.com (mail-bw0-f211.google.com [209.85.218.211]) by core3.amsl.com (Postfix) with ESMTP id 671AD3A63D3; Mon,  8 Mar 2010 14:44:56 -0800 (PST)
Received: by bwz3 with SMTP id 3so297265bwz.29 for <multiple recipients>; Mon, 08 Mar 2010 14:44:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=9KjTJOmbhKZeSr1aU5d7DwfCxwgKFOlggH6cmR6GBwY=; b=TpmYcZQr6RxU2YtrKGB8h+kZo5nuIz7VmIjP7GrkShv/3qKzGjfryiHuP/VtMaz5fy cQDytXtNJ8ye5U18h5kRYxcrkqelInXCT3nuDG5TI7imWL2RDlaqLuv9B7VFzMwK0c5D TSGcjXiDsZm8qnw7KPF2hcMbTvOwTa1Sv+raI=
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=g6TjB1UwYOK2dh7PixHNJ5KoZzzTmwMqrtk/NKhPtoGc3U/KYypYESeSgm78KUtT/o FwxYqF57+607GvDRRAgEQgi42d/K/ZHGHkdPaQUQRN19uHe/dtdZs2gCg4GaxdwPLz/n mwJAagpdKSvjRRDOUWT5UqQFGoODdRCEseeTo=
MIME-Version: 1.0
Received: by 10.204.34.212 with SMTP id m20mr6064979bkd.79.1268088295945; Mon,  08 Mar 2010 14:44:55 -0800 (PST)
In-Reply-To: <C7A22C2A.CAE4%nitinb@juniper.net>
References: <787be2781002171259x1c9a3536k7dafabed3ab99f66@mail.gmail.com> <C7A22C2A.CAE4%nitinb@juniper.net>
Date: Mon, 8 Mar 2010 14:44:55 -0800
Message-ID: <787be2781003081444v16bbca86sde371895d21d74e2@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Nitin Bahadur <nitinb@juniper.net>
Content-Type: multipart/alternative; boundary=00032555b4ce6c75ad048151d04c
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, David Ward <dward@juniper.net>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, pwe3 <pwe3@ietf.org>
Subject: Re: [CCAMP] Comments on draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-02
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 22:44:58 -0000

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

Dear Nitin,
I think that you'll kind consider two more comments to the figures in the
document:

   - Figure 2 displays LSP-Ping ACH encapsulation over MPLS-TP LSP. The
   current caption suggests more generic interpretation of the figure.
   - Figure 2 and Figure 3 display GAL as part of a LSP-Ping and BFD control
   packet G-ACh encapsulation. The GAL is a label in the MPLS Label Stack which
   is constructed by Label Stack Elements. Perhaps GAL LSE might be clearer
   caption.

Regards,
Greg

On Wed, Feb 17, 2010 at 11:28 PM, Nitin Bahadur <nitinb@juniper.net> wrote:

> Hi Greg,
>
>   Thanks for reading the draft in detail. See inline below for responses to
> your comments.
>
> On 2/17/10 12:59 PM, "Greg Mirsky" <gregimirsky@gmail.com> wrote:
>
> Dear Authors and All,
> below are my comments to the document:
>
>  *   Abstract - "widely deployed" to replace "widely deployment"
>
> NB> Will fix that.
>
>
>  *   Section 2.1, Figure 2 - Section 3 RFC 5586 states that if ACH TLVs
> might be present then ACH TLV Header must be present. The Length of ACH TLV
> Header may set to zero in no ACH TLVs are actually present in the given
> packet. Said that I turn to figure 2 that presents LSP Ping packet with ACH
> format. The ACH TLV Header is not presented in the format even though
> presence of ACH TLVs is indicated. I think that proper LSP Ping with ACH
> format will look as:
>
>      0                           1                            2
>                3
>
>       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |                                    MPLS Label stack
>                |
>       |
>                            |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |                                              GAL
>                         |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |0 0 0 1|Version|   Reserved    |     LSP-Ping Channel Type     |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |                                   ACH TLV Header
>                |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |                                          ACH TLVs
>                    |
>
>       |
>                            |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |                                    LSP-Ping payload
>               |
>       |
>                            |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> NB> You are right. I will fix that.
>
>
>  *   Section 2.3 discusses optional use of Source Address TLV but the
> sentence "Only 1 source address TLV MUST be present in a LSP-Ping packet."
> may be interpreted as the Source Address TLV is mandatory. I propose to
> change "MUST" to "MAY" in the sentence
>
> NB> Sure...will rephrase to avoid confusion.
>
>
>  *   Figure 3 - same comments regarding ACH TLV Header in the format as for
> Figure 2
>
>
> NB> Will fix.
>
> Thanks for your useful comments Greg.
>
> Nitin
>
>

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

Dear Nitin,<br>I think that you&#39;ll kind consider two more comments to t=
he figures in the document:<br><ul><li>Figure 2 displays LSP-Ping ACH encap=
sulation over MPLS-TP LSP. The current caption suggests more generic interp=
retation of the figure.<br>
</li><li>Figure 2 and Figure 3 display GAL as part of a LSP-Ping and BFD co=
ntrol packet G-ACh encapsulation. The GAL is a label in the MPLS Label Stac=
k which is constructed by Label Stack Elements. Perhaps GAL LSE might be cl=
earer caption.</li>
</ul>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Wed, Feb 17, 201=
0 at 11:28 PM, Nitin Bahadur <span dir=3D"ltr">&lt;<a href=3D"mailto:nitinb=
@juniper.net">nitinb@juniper.net</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin=
: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Greg,<br>
<br>
 =A0 Thanks for reading the draft in detail. See inline below for responses=
 to your comments.<br>
<div class=3D"im"><br>
On 2/17/10 12:59 PM, &quot;Greg Mirsky&quot; &lt;<a href=3D"mailto:gregimir=
sky@gmail.com">gregimirsky@gmail.com</a>&gt; wrote:<br>
<br>
Dear Authors and All,<br>
below are my comments to the document:<br>
<br>
=A0* =A0 Abstract - &quot;widely deployed&quot; to replace &quot;widely dep=
loyment&quot;<br>
<br>
</div>NB&gt; Will fix that.<br>
<br>
<br>
=A0* =A0 Section 2.1, Figure 2 - Section 3 RFC 5586 states that if ACH TLVs=
 might be present then ACH TLV Header must be present. The Length of ACH TL=
V Header may set to zero in no ACH TLVs are actually present in the given p=
acket. Said that I turn to figure 2 that presents LSP Ping packet with ACH =
format. The ACH TLV Header is not presented in the format even though prese=
nce of ACH TLVs is indicated. I think that proper LSP Ping with ACH format =
will look as:<br>

<div class=3D"im"><br>
 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A03<br>
<br>
 =A0 =A0 =A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 =
1 2<br>
 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
<br>
 =A0 =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0MPLS Label stack =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0|<br>
 =A0 =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|<br>
<br>
 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
 =A0 =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0GAL =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
<br>
 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
 =A0 =A0 =A0 |0 0 0 1|Version| =A0 Reserved =A0 =A0| =A0 =A0 LSP-Ping Chann=
el Type =A0 =A0 |<br>
<br>
 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
 =A0 =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 ACH TLV Header =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0|<br>
<br>
 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
 =A0 =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0ACH TLVs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|<br>
<br>
 =A0 =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|<br>
 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
<br>
 =A0 =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0LSP-Ping payload =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 |<br>
 =A0 =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|<br>
<br>
 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
<br>
</div>NB&gt; You are right. I will fix that.<br>
<br>
<br>
=A0* =A0 Section 2.3 discusses optional use of Source Address TLV but the s=
entence &quot;Only 1 source address TLV MUST be present in a LSP-Ping packe=
t.&quot; may be interpreted as the Source Address TLV is mandatory. I propo=
se to change &quot;MUST&quot; to &quot;MAY&quot; in the sentence<br>

<br>
NB&gt; Sure...will rephrase to avoid confusion.<br>
<br>
<br>
=A0* =A0 Figure 3 - same comments regarding ACH TLV Header in the format as=
 for Figure 2<br>
<br>
<br>
NB&gt; Will fix.<br>
<br>
Thanks for your useful comments Greg.<br>
<font color=3D"#888888"><br>
Nitin<br>
<br>
</font></blockquote></div><br>

--00032555b4ce6c75ad048151d04c--

From ylee@huawei.com  Wed Mar 10 08:35:54 2010
Return-Path: <ylee@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 977963A694A for <ccamp@core3.amsl.com>; Wed, 10 Mar 2010 08:35:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 eWTDXlhDtGXx for <ccamp@core3.amsl.com>; Wed, 10 Mar 2010 08:35:47 -0800 (PST)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id AC8E53A6781 for <ccamp@ietf.org>; Wed, 10 Mar 2010 08:35:47 -0800 (PST)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ2006CDRFR5U@usaga04-in.huawei.com> for ccamp@ietf.org; Wed, 10 Mar 2010 10:35:52 -0600 (CST)
Received: from L73682 ([10.124.12.56]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KZ2006OXRFNGG@usaga04-in.huawei.com> for ccamp@ietf.org; Wed, 10 Mar 2010 10:35:51 -0600 (CST)
Date: Wed, 10 Mar 2010 10:35:47 -0600
From: Young Lee <ylee@huawei.com>
In-reply-to: <4B87DE23.8080004@cisco.com>
To: 'Giovanni Martinelli' <giomarti@cisco.com>, ccamp@ietf.org
Message-id: <002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_5E58IbTcf00kF2N5dk5m0g)"
Thread-index: Acq28iFFiJn7X0Z7QhWgCNePEj9A2AJfB3hg
References: <4B87DE23.8080004@cisco.com>
Subject: Re: [CCAMP] Comments on draft-ietf-ccamp-rwa-wson-framework-05
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 16:35:54 -0000

This is a multi-part message in MIME format.

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

Hi Giovanni,

 

Please see in-line for the comments.  

 

Regards,

Greg & Young

 

  _____  

From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of
Giovanni Martinelli
Sent: Friday, February 26, 2010 8:44 AM
To: ccamp@ietf.org
Subject: [CCAMP] Comments on draft-ietf-ccamp-rwa-wson-framework-05

 

Hi Greg/Young/Authors,

regarding the rwa framework I appreciate last updates, they goes in the
right direction. I still have few comment on the draft:


1) Sec. 3.5.1 Regenerators 
According to ITU inputs (Q6 mtg last october) the regeneration
classification was:
1R: amplifier
2R: does not exist
3R: the regenerator (indeed).

I can understand the framework list all the three types (for sake of
completess) but at the end we can consider only 3R as regeneration. This
should also simplify the related encoding: we need only to know if regen is
available and not the specific type (1, 2 or 3).



Young>> We are referencing these terminology from ITU-T G.872 (Annex A) so
these are legitimate regeneration classification. 
1R regenerators may work over a limited range of wavelength/frequencies so
this needs to be known to the control plane path computation process.
2R regenerators are usually dependent on modulation format and are limited
to a range of bit rates, so this needs to be known as well. 

 


2) Sec. 4.1.1
PCE is one of the architectural options but reading the first bullet looks
like there is a need of a *stateful* PCE to support RWA. 
If that the case probably worth a reference to RFC4655 section 6.8.

Young>> We didn't assume that we need a stateful PCE to support RWA. We
assume that the up-to-date RWA usage information will be updated by OSPF
routing enhancement. 


3) Sec. 4.1.3
The statement "this approach may generate higher blocking probability.." is
there any reference that demonstrate this? 



Young>> Please see the following references:


[1]

K. Lu, G. Xiao, and I. Chlamtac, "Analysis of blocking probability for
distributed lightpath establishment in WDM optical networks," IEEE/ACM
Trans. Netw., vol. 13, 2005, pp. 187-197.  


[2]

A. Giorgetti, N. Sambo, L. Valcarenghi, and P. Castoldi, "Reservation
Collision Avoidance in GMPLS Wavelength-routed Optical Networks," Photonics
in Switching, 2006. PS '06. International Conference on, 2006, pp. 1-3.


[3]

A. Giorgetti, F. Paolucci, F. Cugini, L. Valcarenghi, P. Castoldi, and G.
Bernstein, "Routing and Wavelength Assignment in PCE-based Wavelength
Switched Optical Networks," Optical Communication, 2008. ECOC 2008. 34th
European Conference on, 2008, pp. 1-2.


4) Section 4.3
Is not really clear to me the scope of this section, why do we need to state
anything about temporal characteristics?

Young>> The idea was to explain that different timeliness requirements for
lightpath setup influence or restrict the amount of "optimization" that can
be done with the computation of a path.


Another comment that I did some time ago was about defining
dynamic/pseudo-static/static with no reference: the draft just mention short
or moderately-long and long duration.

Young>> Do you have any suggestion as to how to change this section? 

5) Sec. 5.5.4
I understand you need to clarify some typical optical terminology like:
transparent / translucent etc. but how about having all terminology grouped
in section 3? 
And basically this WSON framework support either transparent (in different
flavors) and translucent.



Young>> Good idea! We will update that. Do you have some suggested
definition? 

 



Cheers
G





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

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo1;
	font-size:16.0pt;
	font-family:Arial;
	color:black;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
tt
	{font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;
	color:black;}
p.Style1, li.Style1, div.Style1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@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:1792360828;
	mso-list-template-ids:1288485006;}
@list l0:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	font-family:"Times New Roman";}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	font-family:"Times New Roman";}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	font-family:"Times New Roman";}
@list l0:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1027" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi =
Giovanni,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Please see in-line for the =
comments. &nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regards,<o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Greg &amp; =
Young<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:windowtext'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

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

<p class=3DMsoNormal><b><font size=3D2 color=3Dblack face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight=
:bold'>From:</span></font></b><font
size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:windowtext'> ccamp-bounces@ietf.org =
[mailto:ccamp-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Giovanni =
Martinelli<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, February =
26, 2010
8:44 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> ccamp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [CCAMP] Comments =
on
draft-ietf-ccamp-rwa-wson-framework-05</span></font><font =
color=3Dblack><span
style=3D'color:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><!--[if gte vml 1]><v:shapetype =
id=3D"_x0000_t74"=20
 coordsize=3D"21600,21600" o:spt=3D"74" =
path=3D"m10860,2187c10451,1746,9529,1018,9015,730,7865,152,6685,,5415,,41=
75,152,2995,575,1967,1305,1150,2187,575,3222,242,4220,,5410,242,6560,575,=
7597l10860,21600,20995,7597v485,-1037,605,-2187,485,-3377c21115,3222,2042=
0,2187,19632,1305,18575,575,17425,152,16275,,15005,,13735,152,12705,730v-=
529,288,-1451,1016,-1845,1457xe">
 <v:stroke joinstyle=3D"miter" />
 <v:path gradientshapeok=3D"t" o:connecttype=3D"custom" =
o:connectlocs=3D"10860,2187;2928,10800;10860,21600;18672,10800"=20
  o:connectangles=3D"270,180,90,0" textboxrect=3D"5037,2277,16557,13677" =
/>
</v:shapetype><v:shape id=3D"DtsShapeName" o:spid=3D"_x0000_s1026" =
type=3D"#_x0000_t74"=20
 =
alt=3D"47E529CG097D5920@5BB2C5D2BED5405097@8h8=3D@@dM62793!!!!!!BIHO@]M62=
793!!!11111111110BCGBD3519Onsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!80L8Z8;D8_M62793!!!!!!BIHO@]m62793!!!11111111110BCGBD351=
9110BCGBD3519!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!86G;&lt;=
8=3D?8`M62793!!!!!!BIHO@]M62793!!!11111111110B322C71D4110B322C71D4!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8;?;A8;?@@M62793!!!!!!BIHO@]=
m62793!!!1@6B1B5B110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!1"=20
 =
style=3D'position:absolute;margin-left:0;margin-top:0;width:.05pt;height:=
.05pt;
 z-index:1;visibility:hidden'>
 <w:anchorlock/>
</v:shape><![endif]--></span></font><tt><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Hi =
Greg/Young/Authors,</span></font></tt><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<br>
<tt><font face=3D"Courier New">regarding the rwa framework I appreciate =
last
updates, they goes in the right direction. I still have few comment on =
the
draft:</font></tt><br>
<br>
<br>
<tt><font face=3D"Courier New">1) Sec. 3.5.1 Regenerators =
</font></tt><br>
<tt><font face=3D"Courier New">According to ITU inputs (Q6 mtg last =
october) the
regeneration classification was:</font></tt><br>
<tt><font face=3D"Courier New">1R: amplifier</font></tt><br>
<tt><font face=3D"Courier New">2R: does not exist</font></tt><br>
<tt><font face=3D"Courier New">3R: the regenerator =
(indeed).</font></tt><br>
<br>
<tt><font face=3D"Courier New">I can understand the framework list all =
the three
types (for sake of completess) but at the end we can consider only 3R as
regeneration. This should also simplify the related encoding: we need =
only to
know if regen is available and not the specific type (1, 2 or =
3).</font></tt><br>
<br>
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p></o:p></span></font></p>

<pre style=3D'page-break-before:always'><font size=3D2 color=3D"#3366ff" =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>Young&gt;&gt; =
We are referencing these terminology from ITU-T G.872 (Annex A) so these =
are legitimate regeneration classification. =
<o:p></o:p></span></font></pre><pre
style=3D'page-break-before:always'><font size=3D2 color=3D"#3366ff" =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>1R =
regenerators may work over a limited range of wavelength/frequencies so =
this needs to be known to the control plane path computation =
process.<o:p></o:p></span></font></pre><pre
style=3D'page-break-before:always'><font size=3D2 color=3D"#3366ff" =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>2R =
regenerators are usually dependent on modulation format and are limited =
to a range of bit rates, so this needs to be known as well. =
</span></font><font
color=3D"#3366ff"><span =
style=3D'color:#3366FF'><O:P></O:P><o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><O:P><o:p>&nbsp;</o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'><br>
<tt><font face=3D"Courier New">2) Sec. 4.1.1</font></tt><br>
<tt><font face=3D"Courier New">PCE is one of the architectural options =
but
reading the first bullet looks like there is a need of a *stateful* PCE =
to support
RWA. </font></tt><br>
<tt><font face=3D"Courier New">If that the case probably worth a =
reference to
RFC4655 section 6.8.</font></tt><br>
<br>
</span></font><font size=3D2 color=3D"#3366ff" face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:#3366FF'>Young&gt;&gt;</span></font><font
size=3D2 color=3D"#3366ff" face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:#3366FF'> </span></font><font size=3D2
color=3D"#3366ff" face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:#3366FF'>We didn&#8217;t assume that we need a stateful PCE to =
support
RWA. We assume that the up-to-date RWA usage information will be updated =
by
OSPF routing enhancement. <O:P></O:P></span></font><font =
color=3D"#3366ff"><span
style=3D'color:#3366FF'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'><br>
<tt><font face=3D"Courier New">3) Sec. 4.1.3</font></tt><br>
<tt><font face=3D"Courier New">The statement &quot;this approach may =
generate
higher blocking probability..&quot; is there any reference that =
demonstrate
this? </font></tt><br>
<br>
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3D"#3366ff" face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:#3366FF'>Young&gt;&gt; Please see the following =
references:<o:p></o:p></span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0
 style=3D'border-collapse:collapse'>
 <tr>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal style=3D'line-height:13.2pt'><font size=3D2 =
color=3D"#3366ff"
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>[1]<o:p></o:p>=
</span></font></p>
  </td>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt 4.0pt'>
  <p class=3DMsoNormal style=3D'line-height:13.2pt'><font size=3D2 =
color=3D"#3366ff"
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>K.
  Lu, G. Xiao, and I. Chlamtac, &#8220;Analysis of blocking probability =
for
  distributed lightpath establishment in WDM optical networks,&#8221; =
<i><span
  style=3D'font-style:italic'>IEEE/ACM Trans. Netw.</span></i>, vol. 13, =
2005,
  pp. 187-197. <span class=3Dz3988><span
  =
title=3D"url_ver=3DZ39.88-2004&amp;ctx_ver=3DZ39.88-2004&amp;rft_val_fmt=3D=
info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=3Darticle&amp;rft.at=
itle=3DAnalysis%20of%20blocking%20probability%20for%20distributed%20light=
path%20establishment%20in%20WDM%20optical%20networks&amp;rft.jtitle=3DIEE=
E%2FACM%20Trans.%20Netw.&amp;rft.volume=3D13&amp;rft.issue=3D1&amp;rft.au=
first=3DKejie&amp;rft.aulast=3DLu&amp;rft.au=3DKejie%20Lu&amp;rft.au=3DGa=
oxi%20Xiao&amp;rft.au=3DImrich%20Chlamtac&amp;rft.date=3D2005&amp;rft.pag=
es=3D187-197">&nbsp;</span></span><o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal style=3D'line-height:13.2pt'><font size=3D2 =
color=3D"#3366ff"
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>[2]<o:p></o:p>=
</span></font></p>
  </td>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt 4.0pt'>
  <p class=3DMsoNormal style=3D'line-height:13.2pt'><font size=3D2 =
color=3D"#3366ff"
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>A.
  Giorgetti, <st1:place w:st=3D"on">N. Sambo</st1:place>, L. =
Valcarenghi, and P.
  Castoldi, &#8220;Reservation Collision Avoidance in GMPLS =
Wavelength-routed
  Optical Networks,&#8221; <i><span =
style=3D'font-style:italic'>Photonics in
  Switching, 2006. PS '06. International Conference on</span></i>, 2006, =
pp.
  1-3.<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal style=3D'line-height:13.2pt'><font size=3D2 =
color=3D"#3366ff"
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>[3]<o:p></o:p>=
</span></font></p>
  </td>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt 4.0pt'>
  <p class=3DMsoNormal style=3D'line-height:13.2pt'><font size=3D2 =
color=3D"#3366ff"
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:#3366FF'>A.
  Giorgetti, F. Paolucci, F. Cugini, L. Valcarenghi, P. Castoldi, and G.
  Bernstein, &#8220;Routing and Wavelength Assignment in PCE-based =
Wavelength
  Switched Optical Networks,&#8221; <i><span =
style=3D'font-style:italic'>Optical
  Communication, 2008. ECOC 2008. 34th European Conference =
on</span></i>, 2008,
  pp. 1-2.<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'><br>
<tt><font face=3D"Courier New">4) Section 4.3</font></tt><br>
<tt><font face=3D"Courier New">Is not really clear to me the scope of =
this
section, why do we need to state anything about temporal =
characteristics?</font></tt></span></font><tt><font
size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;color:navy'><o:p></o:p></span></font></tt></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3D"#3366ff" face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:#3366FF'>Young&gt;&gt; The idea was to explain that =
different
timeliness requirements for lightpath setup influence or restrict the =
amount of
&quot;optimization&quot; that can be done with the computation of a =
path.</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'><br>
<tt><font face=3D"Courier New">Another comment that I did some time ago =
was about
defining dynamic/pseudo-static/static with no reference: the draft just =
mention
short or moderately-long and long duration.</font></tt><br>
<br>
</span></font><font size=3D2 color=3D"#3366ff" face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:#3366FF'>Young&gt;&gt; Do you have any
suggestion as to how to change this section? =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><tt><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>5) Sec.
5.5.4</span></font></tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;font-family:"Courier New"'><br>
<tt><font face=3D"Courier New">I understand you need to clarify some =
typical
optical terminology like: transparent / translucent etc. but how about =
having
all terminology grouped in section 3? </font></tt><br>
<tt><font face=3D"Courier New">And basically this WSON framework support =
either
transparent (in different flavors) and translucent.</font></tt><br>
<br>
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3D"#3366ff" face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:#3366FF'>Young&gt;&gt; Good idea! We will update that. =
<O:P></O:P>Do
you have some suggested definition? </span></font><font =
color=3D"#3366ff"><span
style=3D'color:#3366FF'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'><br>
<br>
<tt><font face=3D"Courier New">Cheers</font></tt><br>
<tt><font face=3D"Courier New">G</font></tt><br>
<br>
<br>
</span></font><o:p></o:p></p>

<!--EndFragment--></div>

</body>

</html>

--Boundary_(ID_5E58IbTcf00kF2N5dk5m0g)--

From vishwas.ietf@gmail.com  Wed Mar 10 12:35:56 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A23963A69CE for <ccamp@core3.amsl.com>; Wed, 10 Mar 2010 12:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  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 fwD8oUC4yyPs for <ccamp@core3.amsl.com>; Wed, 10 Mar 2010 12:35:56 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id DABF73A690C for <ccamp@ietf.org>; Wed, 10 Mar 2010 12:35:55 -0800 (PST)
Received: by gyg10 with SMTP id 10so2257783gyg.31 for <ccamp@ietf.org>; Wed, 10 Mar 2010 12:35:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=4eLh4fxr3Z+QlSoZ4KbN3JLgKeLWrOMuzcSoggC0Smc=; b=EV6VuTlju0yNm5MjIzInG7lYdzhJ0RfmrjznRf291v9qGAM6/Njr1GDViqSbrIzJgm YVE5iaRZqbVVLRhhtuzpDnMAWTBdcVEZtOLKwgXfC/gGZtbrWruQ93LmO+zQ5vqY91t/ v1RAMhq/OkTVX057haY3vc0jgTvvYNamtDcvM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=DoSY+KSRMbeqf1Iy6spt0AnFJ4SOY00fcvrg59QG1SmIe+fFc7BfW0N+wvLkTDmHjt w4jcvWyJPxp3FnI8mrorgicd0kP6eGWgPhBdFBYP8uF33Svn23aCE5CM1FaqbWiKv9v0 kbA0gtIEREbEc0Ajtiv7Zv4fWopuiYoFTX8Es=
MIME-Version: 1.0
Received: by 10.150.55.32 with SMTP id d32mr2510570yba.261.1268253354642; Wed,  10 Mar 2010 12:35:54 -0800 (PST)
Date: Wed, 10 Mar 2010 12:35:54 -0800
Message-ID: <77ead0ec1003101235o7fcd155dobb25adb94c07d2a7@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Deborah Brungard <dbrungard@att.com>, Lou Berger <lberger@labn.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ccamp@ietf.org
Subject: [CCAMP] LMP Issues
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 20:35:56 -0000

Hi CCAMP-chairs,

I have sent multiple mails regarding LMP but have not heard back from
any of the authors. I have found some basic issues in the specs.

I was wondering if LMP is still actively used anywhere? If it is I was
wondering fi I should try and update the RFC to take care of al
lissues.

Thanks,
Vishwas

From swallow@cisco.com  Wed Mar 10 13:36:55 2010
Return-Path: <swallow@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A83CC3A69AC; Wed, 10 Mar 2010 13:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.202
X-Spam-Level: 
X-Spam-Status: No, score=-9.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdGx8bTFp078; Wed, 10 Mar 2010 13:36:45 -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 6CC463A68EE; Wed, 10 Mar 2010 13:36:45 -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: AgUFAEOgl0urRN+K/2dsb2JhbACBRJg3WnOjDphOAoR3BIMX
X-IronPort-AV: E=Sophos;i="4.49,616,1262563200"; d="scan'208,217";a="98422903"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 10 Mar 2010 21:36:38 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o2ALabLe015707; Wed, 10 Mar 2010 21:36:38 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 10 Mar 2010 15:36:37 -0600
Received: from 10.98.32.163 ([10.98.32.163]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ;  Wed, 10 Mar 2010 21:36:37 +0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Wed, 10 Mar 2010 16:36:34 -0500
From: George Swallow <swallow@cisco.com>
To: Maarten Vissers <maarten.vissers@huawei.com>, Loa Andersson <loa@pi.nu>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <ccamp@ietf.org>, <pwe3@ietf.org>
Message-ID: <C7BD7B12.22654%swallow@cisco.com>
Thread-Topic: [mpls] Comment onhttp://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt
Thread-Index: AcrAmcFbMuT2SnfRzkqAlkCKUylOdA==
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3351083795_98145618"
X-OriginalArrivalTime: 10 Mar 2010 21:36:37.0625 (UTC) FILETIME=[C3847E90:01CAC099]
Subject: Re: [CCAMP] [mpls] Comment onhttp://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 21:36:55 -0000

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

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

Maarten -

See inline:


On 12/17/09 2:45 AM, "Maarten Vissers" <maarten.vissers@huawei.com> wrote:

>=20
>=20
> Some comments on the content of this draft:
>=20
> In section 2.1 it is stated:
> "  <..>
>    For example an AIS message may be sent during a protection switching
>    event and would cease being sent if the protection switch was
>    successful in restoring the link.
>=20
>    Its primary purpose is to suppress alarms in the MPLS-TP layer
>    network above the level at which the defect occurs.  The AIS message
>    MAY be used to trigger recovery mechanisms.  It should be noted that
>    such use would be subject to false positives, e.g. unnecessary
>    protection switching events in the client layer."
>=20
> It is not correct to state that AIS sending is stopped if the protection
> switch was succesful. The reason is that the AIS insertion is done by a M=
EP
> Sink function that is upstream of the protection switch selector process,
> and this MEP Sink function is as such unaware of the presence of a
> protection switch process and of the state of the protection switch proce=
ss.
>=20
GS:  For better or worse, there is a significant difference in how the ITU
and IETF write specifications.  While the ITU defines detailed equipment
specifications, the IETF almost always speaks only about the behavior of th=
e
=B3node=B2 and what is seen =B3on the wire=B2.  So from a IETF perspective, if a ME=
P
generates AIS and then a selector process causes that AIS to be dropped,
then the node has stopped sending AIS and is fully compliant with the text
above.
>=20
> AIS in packet transport networks must **not** used to trigger recovery
> mechanisms. Reason is that AIS OAM messages in packet transport network a=
re
> to be generated within 1 second after the detection of the signal fail ty=
pe
> defect detection and be generated with a periodicity of 1 second. These
> times are much too long to trigger any recovery mechanism.
>=20
GS:  For a pure transport application, I totally agree.  If the CC function
is function is running fast enough to detect the failure in << 1 second the=
n
AIS nor LDI should be used to do protection switching.
>=20
> The 1 second time requirement to generate the first AIS message is derive=
d
> from the 2.5 +/- 0.5 second fault cause to failure integration timer as
> specified in G.7710. Generation of the first AIS message within a period =
of
> 1 second will leave enough time to reach the downstream MEP Sink function
> and suppress the fault cause that report the interruption of the connecti=
on.
>=20
> Protection switching in packet transport networks is triggered by e.g. lo=
ss
> of continuity and misconnection defects.
>=20
> In section 2.2 it is stated:
> "  The LDI message is generated in response to detecting a fatal failure
>    in the server layer.  The LDI message MUST NOT be sent until the
>    defect has been determined to be fatal.  For example during a
>    protection switching event LDI messages are not sent.  However if the
>    protection switch was unsuccessful in restoring the link within the
>    expected repair time, an LDI message MUST be sent."
> and in section 2.1 it is stated:
> "  The MPLS-TP Alarm Indication Signal (AIS) message is generated in
>    response to detecting defects in the server layer.  The AIS message
>    SHOULD be sent as soon is the condition is detected, that is before
>    any determination has been made as to whether the condition is fatal."
>=20
> This draft suggest that it is possible for a MEP Sink function to determi=
ne
> if the fault is *fatal* or *not fatal*. This is not possible for a MEP Si=
nk
> function. The reason is that a MEP Sink function has no knowledge of the
> presence or state of a protection switch process associated with the
> connection. E.g. the protection switch process may be in a downstream nod=
e.
>=20
GS: The assumption is that something in the box is capable of knowing if th=
e
facility is unprotected or if protection is currently unavailable.
>=20
> It is also not necessary to make AIS generation conditional on e.g.
> protection switch actions. Reason is that a protection switch process wil=
l
> select traffic from either a working connection input port, or a protecti=
on
> connection input port. Any traffic present on the not selected input port
> will drop at this input port and not be forwarded to the protection switc=
h
> process output port. At the output port AIS messages will be present as l=
ong
> as the protection switch process selects its traffic from the failed
> connection; once the protection switch process selects its traffic from t=
he
> non-failed connection AIS messages will not longer be forwarded to the
> output port.
>=20
GS:  Consider the following:

A client signal is cross-connected over a server layer connection at NodeA.
The server layer connection has 1:1 protection.

The server layer protection LSP fails, MEP-P starts sending AIS towards the
client MEP.  These are dropped as the selector is forwarding traffic from
the server layer working LSP.  Now working fails.

The desired behavior is that "something" causes LDI to be inserted in the
client signal at NodeA.

This could be implemented in any number of ways, e.g.:

1. When the server layer protection LSP fails, the =B3control function=B2
proactively instructs (programs) MEP-W to change its OP-CODE from AIS to
LDI.  Thus if the server layer working LSP fails, LDI is sent.
2. If the box is built such that the selector will switch to protection eve=
n
if protection has already failed, then the =B3control function=B2 proactively
instructs (programs) MEP-W to change its OP-CODE from AIS to LDI.  The when
the selector moves to protection, LDI will begin to be sent.
3. The =B3control function=B2 on determining that both the server layer working
and protection have failed, de-select both and send LDI itself.
4. The =B3control function=B2 on determining that both the server layer working
and protection have failed, reactively instructs the MEP of the currently
selected server layer LSP to change its OP-CODE from AIS to LDI.
5. (My favorite) Given that a modern box should be able to effect a
switch-over in a few milliseconds, implement in every MEP a hold-off timer
equal to the fail-over budget.  Then send LDI (AIS is never produced).

...George
>=20
> This draft should as such not become a WG document.
>=20
> Regards,
> Maarten
>=20
> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behal=
f
> Of Loa Andersson
> Sent: donderdag 17 december 2009 5:36
> To: mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org
> Subject: [mpls-tp] Poll om making
> http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt a working group
> document
>=20
> All,
>=20
> this is to start a two week poll on making
>=20
> http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt
>=20
> an MPLS working group document.
>=20
> Send a mail to the mpls-tp@ietf.org mailing list, indicating "yes/support=
"
> or "no/do not support".
>=20
> Comments on the content of the draft should be sent to the same mailing l=
ist
> with a different subject line.
>=20
> The poll ends Friday 15 Jan, 2010.
>=20
> /Loa
> --
>=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
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20



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

<HTML>
<HEAD>
<TITLE>Re: [mpls] Comment onhttp://www.ietf.org/id/draft-sfv-mpls-tp-fault-=
01.txt</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:14pt'>Maarten=
 -<BR>
<BR>
See inline:<BR>
<BR>
<BR>
On 12/17/09 2:45 AM, &quot;Maarten Vissers&quot; &lt;<a href=3D"maarten.visse=
rs@huawei.com">maarten.vissers@huawei.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
<BR>
Some comments on the content of this draft:<BR>
<BR>
In section 2.1 it is stated:<BR>
&quot; &nbsp;&lt;..&gt;<BR>
&nbsp;&nbsp;&nbsp;For example an AIS message may be sent during a protectio=
n switching<BR>
&nbsp;&nbsp;&nbsp;event and would cease being sent if the protection switch=
 was<BR>
&nbsp;&nbsp;&nbsp;successful in restoring the link.<BR>
<BR>
&nbsp;&nbsp;&nbsp;Its primary purpose is to suppress alarms in the MPLS-TP =
layer<BR>
&nbsp;&nbsp;&nbsp;network above the level at which the defect occurs. &nbsp=
;The AIS message<BR>
&nbsp;&nbsp;&nbsp;MAY be used to trigger recovery mechanisms. &nbsp;It shou=
ld be noted that<BR>
&nbsp;&nbsp;&nbsp;such use would be subject to false positives, e.g. unnece=
ssary<BR>
&nbsp;&nbsp;&nbsp;protection switching events in the client layer.&quot;<BR=
>
<BR>
It is not correct to state that AIS sending is stopped if the protection<BR=
>
switch was succesful. The reason is that the AIS insertion is done by a MEP=
<BR>
Sink function that is upstream of the protection switch selector process,<B=
R>
and this MEP Sink function is as such unaware of the presence of a<BR>
protection switch process and of the state of the protection switch process=
.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'>GS: &nbsp;For better or worse, there is a significant di=
fference in how the ITU and IETF write specifications. &nbsp;While the ITU d=
efines detailed equipment specifications, the IETF almost always speaks only=
 about the behavior of the &#8220;node&#8221; and what is seen &#8220;on the=
 wire&#8221;. &nbsp;So from a IETF perspective, if a MEP generates AIS and t=
hen a selector process causes that AIS to be dropped, then the node has stop=
ped sending AIS and is fully compliant with the text above.<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
AIS in packet transport networks must **not** used to trigger recovery<BR>
mechanisms. Reason is that AIS OAM messages in packet transport network are=
<BR>
to be generated within 1 second after the detection of the signal fail type=
<BR>
defect detection and be generated with a periodicity of 1 second. These<BR>
times are much too long to trigger any recovery mechanism.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'>GS: &nbsp;For a pure transport application, I totally ag=
ree. &nbsp;If the CC function is function is running fast enough to detect t=
he failure in &lt;&lt; 1 second then AIS nor LDI should be used to do protec=
tion switching.<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
The 1 second time requirement to generate the first AIS message is derived<=
BR>
from the 2.5 +/- 0.5 second fault cause to failure integration timer as<BR>
specified in G.7710. Generation of the first AIS message within a period of=
<BR>
1 second will leave enough time to reach the downstream MEP Sink function<B=
R>
and suppress the fault cause that report the interruption of the connection=
.<BR>
<BR>
Protection switching in packet transport networks is triggered by e.g. loss=
<BR>
of continuity and misconnection defects.<BR>
<BR>
In section 2.2 it is stated:<BR>
&quot; &nbsp;The LDI message is generated in response to detecting a fatal =
failure<BR>
&nbsp;&nbsp;&nbsp;in the server layer. &nbsp;The LDI message MUST NOT be se=
nt until the<BR>
&nbsp;&nbsp;&nbsp;defect has been determined to be fatal. &nbsp;For example=
 during a<BR>
&nbsp;&nbsp;&nbsp;protection switching event LDI messages are not sent. &nb=
sp;However if the<BR>
&nbsp;&nbsp;&nbsp;protection switch was unsuccessful in restoring the link =
within the<BR>
&nbsp;&nbsp;&nbsp;expected repair time, an LDI message MUST be sent.&quot;<=
BR>
and in section 2.1 it is stated:<BR>
&quot; &nbsp;The MPLS-TP Alarm Indication Signal (AIS) message is generated=
 in<BR>
&nbsp;&nbsp;&nbsp;response to detecting defects in the server layer. &nbsp;=
The AIS message<BR>
&nbsp;&nbsp;&nbsp;SHOULD be sent as soon is the condition is detected, that=
 is before<BR>
&nbsp;&nbsp;&nbsp;any determination has been made as to whether the conditi=
on is fatal.&quot;<BR>
<BR>
This draft suggest that it is possible for a MEP Sink function to determine=
<BR>
if the fault is *fatal* or *not fatal*. This is not possible for a MEP Sink=
<BR>
function. The reason is that a MEP Sink function has no knowledge of the<BR=
>
presence or state of a protection switch process associated with the<BR>
connection. E.g. the protection switch process may be in a downstream node.=
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'>GS: The assumption is that something in the box is capab=
le of knowing if the facility is unprotected or if protection is currently u=
navailable. &nbsp;<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
It is also not necessary to make AIS generation conditional on e.g.<BR>
protection switch actions. Reason is that a protection switch process will<=
BR>
select traffic from either a working connection input port, or a protection=
<BR>
connection input port. Any traffic present on the not selected input port<B=
R>
will drop at this input port and not be forwarded to the protection switch<=
BR>
process output port. At the output port AIS messages will be present as lon=
g<BR>
as the protection switch process selects its traffic from the failed<BR>
connection; once the protection switch process selects its traffic from the=
<BR>
non-failed connection AIS messages will not longer be forwarded to the<BR>
output port.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'>GS: &nbsp;Consider the following:<BR>
<BR>
A client signal is cross-connected over a server layer connection at NodeA.=
 &nbsp;The server layer connection has 1:1 protection.<BR>
<BR>
The server layer protection LSP fails, MEP-P starts sending AIS towards the=
<BR>
client MEP. &nbsp;These are dropped as the selector is forwarding traffic f=
rom<BR>
the server layer working LSP. &nbsp;Now working fails.<BR>
<BR>
The desired behavior is that &quot;something&quot; causes LDI to be inserte=
d in the client signal at NodeA.<BR>
<BR>
This could be implemented in any number of ways, e.g.:<BR>
<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'f=
ont-size:14pt'>When the server layer protection LSP fails, the &#8220;contro=
l function&#8221; proactively instructs (programs) MEP-W to change its OP-CO=
DE from AIS to LDI. &nbsp;Thus if the server layer working LSP fails, LDI is=
 sent.
</SPAN></FONT><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-=
size:14pt'>If the box is built such that the selector will switch to protect=
ion even if protection has already failed, then the &#8220;control function&=
#8221; proactively instructs (programs) MEP-W to change its OP-CODE from AIS=
 to LDI. &nbsp;The when the selector moves to protection, LDI will begin to =
be sent.
</SPAN></FONT><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-=
size:14pt'>The &#8220;control function&#8221; on determining that both the s=
erver layer working and protection have failed, de-select both and send LDI =
itself.
</SPAN></FONT><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-=
size:14pt'>The &#8220;control function&#8221; on determining that both the s=
erver layer working and protection have failed, reactively instructs the MEP=
 of the currently selected server layer LSP to change its OP-CODE from AIS t=
o LDI.
</SPAN></FONT><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-=
size:14pt'>(My favorite) Given that a modern box should be able to effect a =
switch-over in a few milliseconds, implement in every MEP a hold-off timer e=
qual to the fail-over budget. &nbsp;Then send LDI (AIS is never produced).<B=
R>
</SPAN></FONT></OL><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font=
-size:14pt'><BR>
...George<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
This draft should as such not become a WG document.<BR>
<BR>
Regards,<BR>
Maarten<BR>
<BR>
-----Original Message-----<BR>
From: <a href=3D"mpls-tp-bounces@ietf.org">mpls-tp-bounces@ietf.org</a> [<a h=
ref=3D"mailto:mpls-tp-bounces@ietf.org">mailto:mpls-tp-bounces@ietf.org</a>] O=
n Behalf<BR>
Of Loa Andersson<BR>
Sent: donderdag 17 december 2009 5:36<BR>
To: <a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a>; <a href=3D"mpls@ietf.org=
">mpls@ietf.org</a>; <a href=3D"ccamp@ietf.org">ccamp@ietf.org</a>; <a href=3D"p=
we3@ietf.org">pwe3@ietf.org</a><BR>
Subject: [mpls-tp] Poll om making<BR>
<a href=3D"http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt">http://www.=
ietf.org/id/draft-sfv-mpls-tp-fault-01.txt</a> a working group<BR>
document<BR>
<BR>
All,<BR>
<BR>
this is to start a two week poll on making<BR>
<BR>
<a href=3D"http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt">http://www.=
ietf.org/id/draft-sfv-mpls-tp-fault-01.txt</a><BR>
<BR>
an MPLS working group document.<BR>
<BR>
Send a mail to the <a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a> mailing =
list, indicating &quot;yes/support&quot;<BR>
or &quot;no/do not support&quot;.<BR>
<BR>
Comments on the content of the draft should be sent to the same mailing lis=
t<BR>
with a different subject line.<BR>
<BR>
The poll ends Friday 15 Jan, 2010.<BR>
<BR>
/Loa<BR>
--<BR>
<BR>
<BR>
Loa Andersson &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;email: <a href=3D"loa.andersson@ericsson.com">loa.andersson@ericsson.co=
m</a><BR>
Sr Strategy and Standards Manager &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"loa@pi.nu">loa@pi.nu</a><BR>
Ericsson Inc &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;phone: +46 10 717 52 13<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+46 767 72 92 13<BR>
_______________________________________________<BR>
mpls-tp mailing list<BR>
<a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a><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>
<a href=3D"mpls@ietf.org">mpls@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/m=
ailman/listinfo/mpls</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'><BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3351083795_98145618--


From loa@pi.nu  Wed Mar 10 21:44:19 2010
Return-Path: <loa@pi.nu>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB4F63A6841; Wed, 10 Mar 2010 21:44:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3jeOukztBjI; Wed, 10 Mar 2010 21:44:19 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id D27C33A681A; Wed, 10 Mar 2010 21:44:17 -0800 (PST)
Received: from pi.nu (localhost [127.0.0.1]) by mail.pi.nu (Postfix) with ESMTP id 1F64FD4055; Thu, 11 Mar 2010 06:44:20 +0100 (CET)
Received: from 59.154.63.92 (SquirrelMail authenticated user loa@pi.nu) by pi.nu with HTTP; Thu, 11 Mar 2010 06:44:21 +0100
Message-ID: <1dc47c8aa8fdf1d95b6f62696b414cfc.squirrel@pi.nu>
Date: Thu, 11 Mar 2010 06:44:21 +0100
From: "Loa Andersson" <loa@pi.nu>
To: mpls@ietf.org, mpls-tp@ietf.org, ccamp@ietf.org, pwe3@ietf.org
User-Agent: SquirrelMail/1.4.19
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: [CCAMP] wg last call on draft-ietf-mpls-tp-survive-fwk-04.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 05:44:20 -0000

All,

this is to start an MPLS  working group last call on
draft-ietf-mpls-tp-survive-fwk-04.txt.

Please send your comments to the mpls-tp@ietf.org mailing
list.

The working group last call ends eob April 2nd, 2010.

/Loa

--

Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///
   phone:  +46 10 717 52 13
           +46 767 72 92 13

   email:  loa.andersson@ericsson.com
           loa@pi.nu


From swallow@cisco.com  Thu Mar 11 06:29:26 2010
Return-Path: <swallow@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E86633A68FB; Thu, 11 Mar 2010 06:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.202
X-Spam-Level: 
X-Spam-Status: No, score=-9.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ryF+yw1bS7aQ; Thu, 11 Mar 2010 06:29:19 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 0547F3A69FF; Thu, 11 Mar 2010 06:28:22 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmQFAIOMmEutJV2Y/2dsb2JhbACBRJhCWnOkF4sHCI1lAoJhCIIQBIMX
X-IronPort-AV: E=Sophos;i="4.49,620,1262563200";  d="scan'208,217";a="216857594"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by sj-iport-3.cisco.com with ESMTP; 11 Mar 2010 14:28:26 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id o2BESQvi017139;  Thu, 11 Mar 2010 14:28:26 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 11 Mar 2010 08:28:26 -0600
Received: from 10.98.32.163 ([10.98.32.163]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 11 Mar 2010 14:28:26 +0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Thu, 11 Mar 2010 09:28:23 -0500
From: George Swallow <swallow@cisco.com>
To: Maarten Vissers <maarten.vissers@huawei.com>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <ccamp@ietf.org>, <pwe3@ietf.org>
Message-ID: <C7BE6837.226C4%swallow@cisco.com>
Thread-Topic: [mpls-tp] Comment onhttp://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt
Thread-Index: Acp+0nx4dPl6Lc1rTuiovDVmelzglwAFWAQgADmfjCAQVjABUg==
In-Reply-To: <001a01ca7fd5$6ac557c0$a070ca0a@china.huawei.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3351144504_101768198"
X-OriginalArrivalTime: 11 Mar 2010 14:28:26.0448 (UTC) FILETIME=[1CCBBD00:01CAC127]
Subject: Re: [CCAMP] [mpls-tp] Comment onhttp://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 14:29:27 -0000

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

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

Maarten -

See Inline -


On 12/18/09 6:29 AM, "Maarten Vissers" <maarten.vissers@huawei.com> wrote:

> I would like to raise three additional issues in this draft.
>=20
> 1) in section 3 it is stated "The FM Channel uses ACH TLVs and MUST inclu=
de
> the ACH TLV header." and "The ACH TLVs may include (but are not limited t=
o)
> IF-ID, Global-ID, and ICC." AIS and LCK OAM messages should not carry any
> identifiers, as such identifiers are not read by the receiving MEP. Those
> identifiers are not providing any useful information to network managemen=
t
> or detector circuits. Addition of such identifiers to the AIS and LCK fra=
mes
> adds unnecessary complexities to the designs.
>=20
GS: Hummm...  I got the idea for Global-ID / ICC from Y.1711.  Sounded
pretty useful in the inter-domain case  where the NMS would not be able to
correlate alarms across domain boundaries.
>=20
> 2) In section 4 it is stated "R-flag   The R-flag is normally set to zero=
.
> A setting of one indicates the removal of a previously sent FM condition.=
"
> This R-flag is not a helpful feature in AIS and LCK messages. Addition of
> such flag only increases complexity of the solution and designs. It is a
> classical item, discussed in previous OAM developments as well. The idea =
is
> that the receiver can be explicitly informed about the end of the AIS or =
LCK
> condition. Unfortunately it is necessary to take into account that a pack=
et
> may be dropped due to congestion or bit errors. As such, the AIS and LCK
> detector circuits in the MEP Sink fucntions must be able to clear the AIS
> and LCK defects also when such packet with R-flag was lost (which is
> foreseen in the specification in section 5.3). It is therefore less compl=
ex
> to have the absence of three AIS or LCK packets being used as clearing
> condition for the AIS and LCK defects.
>=20
GS:  If you don=B9t want to complicate you logic, you can just ignore packets
that have the R-bit set.
>=20
> 3) In section 4 it is stated "Refresh Timer   The maximum time between
> successive FM messages specified in seconds.  The range is 1 to 65535.  T=
he
> value 0 is not permitted. The default value is 60." The default AIS and L=
CK
> repetition period is generically 1-second, not 60-seconds. There is no ne=
ed
>=20
GS:  Changed the default, when not using the optional clearing, to 1 second=
.
>=20
> for a range of AIS and LCK repetition periods. The first AIS packet for e=
ach
> LSP/PW impacted by the fault has to be generated within 1 second after a
> signal fail type defect is detected and the next one has to be generated
> 1-second later. This 1 second period is necessary in order to prevent tha=
t
>=20
GS: Why does Y.1731 allow for 1 second or 1 minute?

...George
>=20
> downstream the alarms are raised (which happens after 2.5 +/- 0.5 seconds=
).
> If the first AIS packet was lost (due to congestion or bit errors) then
> there is a second AIS packet that will be received by the MEP Sink fucnti=
on
> before the 2.5 +/- 0.5 second fault cause to failure filter will expire.
> Either the first or second AIS packet will clear the fault cause and prev=
ent
> the alarm from being raised.
>=20
>=20
>=20
> MPLS-TP AIS and LCK OAM packets should be very simple OAM packets includi=
ng
> only a Version number and OAM Type (MsgType or OpCode). AIS and LCK OAM
> packets should be inserted within 1 second after the condition to generat=
e
> those packets became active and these OAM packets must be send with a 1
> second repetition rate.
>=20
> Regards,
> Maarten
>=20
>=20
>=20
>  =20
>=20
> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behal=
f
> Of Maarten Vissers
> Sent: donderdag 17 december 2009 8:45
> To: 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org;
> pwe3@ietf.org
> Subject: [mpls-tp] Comment
> onhttp://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt
>=20
>=20
> Some comments on the content of this draft:
>=20
> In section 2.1 it is stated:
> "  <..>
>    For example an AIS message may be sent during a protection switching
>    event and would cease being sent if the protection switch was
>    successful in restoring the link.
>=20
>    Its primary purpose is to suppress alarms in the MPLS-TP layer
>    network above the level at which the defect occurs.  The AIS message
>    MAY be used to trigger recovery mechanisms.  It should be noted that
>    such use would be subject to false positives, e.g. unnecessary
>    protection switching events in the client layer."
>=20
> It is not correct to state that AIS sending is stopped if the protection
> switch was succesful. The reason is that the AIS insertion is done by a M=
EP
> Sink function that is upstream of the protection switch selector process,
> and this MEP Sink function is as such unaware of the presence of a
> protection switch process and of the state of the protection switch proce=
ss.
>=20
> AIS in packet transport networks must **not** used to trigger recovery
> mechanisms. Reason is that AIS OAM messages in packet transport network a=
re
> to be generated within 1 second after the detection of the signal fail ty=
pe
> defect detection and be generated with a periodicity of 1 second. These
> times are much too long to trigger any recovery mechanism.
>=20
> The 1 second time requirement to generate the first AIS message is derive=
d
> from the 2.5 +/- 0.5 second fault cause to failure integration timer as
> specified in G.7710. Generation of the first AIS message within a period =
of
> 1 second will leave enough time to reach the downstream MEP Sink function
> and suppress the fault cause that report the interruption of the connecti=
on.
>=20
> Protection switching in packet transport networks is triggered by e.g. lo=
ss
> of continuity and misconnection defects.
>=20
> In section 2.2 it is stated:
> "  The LDI message is generated in response to detecting a fatal failure
>    in the server layer.  The LDI message MUST NOT be sent until the
>    defect has been determined to be fatal.  For example during a
>    protection switching event LDI messages are not sent.  However if the
>    protection switch was unsuccessful in restoring the link within the
>    expected repair time, an LDI message MUST be sent."
> and in section 2.1 it is stated:
> "  The MPLS-TP Alarm Indication Signal (AIS) message is generated in
>    response to detecting defects in the server layer.  The AIS message
>    SHOULD be sent as soon is the condition is detected, that is before
>    any determination has been made as to whether the condition is fatal."
>=20
> This draft suggest that it is possible for a MEP Sink function to determi=
ne
> if the fault is *fatal* or *not fatal*. This is not possible for a MEP Si=
nk
> function. The reason is that a MEP Sink function has no knowledge of the
> presence or state of a protection switch process associated with the
> connection. E.g. the protection switch process may be in a downstream nod=
e.
>=20
> It is also not necessary to make AIS generation conditional on e.g.
> protection switch actions. Reason is that a protection switch process wil=
l
> select traffic from either a working connection input port, or a protecti=
on
> connection input port. Any traffic present on the not selected input port
> will drop at this input port and not be forwarded to the protection switc=
h
> process output port. At the output port AIS messages will be present as l=
ong
> as the protection switch process selects its traffic from the failed
> connection; once the protection switch process selects its traffic from t=
he
> non-failed connection AIS messages will not longer be forwarded to the
> output port.
>=20
> This draft should as such not become a WG document.
>=20
> Regards,
> Maarten
>=20
> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behal=
f
> Of Loa Andersson
> Sent: donderdag 17 december 2009 5:36
> To: mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org
> Subject: [mpls-tp] Poll om making
> http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt a working group
> document
>=20
> All,
>=20
> this is to start a two week poll on making
>=20
> http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt
>=20
> an MPLS working group document.
>=20
> Send a mail to the mpls-tp@ietf.org mailing list, indicating "yes/support=
"
> or "no/do not support".
>=20
> Comments on the content of the draft should be sent to the same mailing l=
ist
> with a different subject line.
>=20
> The poll ends Friday 15 Jan, 2010.
>=20
> /Loa
> --
>=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
>=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
>=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
>=20


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

<HTML>
<HEAD>
<TITLE>Re: [mpls-tp] Comment onhttp://www.ietf.org/id/draft-sfv-mpls-tp-fau=
lt-01.txt</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:14pt'>Maarten=
 -<BR>
<BR>
See Inline -<BR>
<BR>
<BR>
On 12/18/09 6:29 AM, &quot;Maarten Vissers&quot; &lt;<a href=3D"maarten.visse=
rs@huawei.com">maarten.vissers@huawei.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'>I would like to raise three additional issues in this dra=
ft.<BR>
<BR>
1) in section 3 it is stated &quot;The FM Channel uses ACH TLVs and MUST in=
clude<BR>
the ACH TLV header.&quot; and &quot;The ACH TLVs may include (but are not l=
imited to)<BR>
IF-ID, Global-ID, and ICC.&quot; AIS and LCK OAM messages should not carry =
any<BR>
identifiers, as such identifiers are not read by the receiving MEP. Those<B=
R>
identifiers are not providing any useful information to network management<=
BR>
or detector circuits. Addition of such identifiers to the AIS and LCK frame=
s<BR>
adds unnecessary complexities to the designs.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'>GS: Hummm... &nbsp;I got the idea for Global-ID / ICC fr=
om Y.1711. &nbsp;Sounded pretty useful in the inter-domain case &nbsp;where =
the NMS would not be able to correlate alarms across domain boundaries.<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
2) In section 4 it is stated &quot;R-flag &nbsp;&nbsp;The R-flag is normall=
y set to zero.<BR>
A setting of one indicates the removal of a previously sent FM condition.&q=
uot;<BR>
This R-flag is not a helpful feature in AIS and LCK messages. Addition of<B=
R>
such flag only increases complexity of the solution and designs. It is a<BR=
>
classical item, discussed in previous OAM developments as well. The idea is=
<BR>
that the receiver can be explicitly informed about the end of the AIS or LC=
K<BR>
condition. Unfortunately it is necessary to take into account that a packet=
<BR>
may be dropped due to congestion or bit errors. As such, the AIS and LCK<BR=
>
detector circuits in the MEP Sink fucntions must be able to clear the AIS<B=
R>
and LCK defects also when such packet with R-flag was lost (which is<BR>
foreseen in the specification in section 5.3). It is therefore less complex=
<BR>
to have the absence of three AIS or LCK packets being used as clearing<BR>
condition for the AIS and LCK defects.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'>GS: &nbsp;If you don&#8217;t want to complicate you logi=
c, you can just ignore packets that have the R-bit set. <BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
3) In section 4 it is stated &quot;Refresh Timer &nbsp;&nbsp;The maximum ti=
me between<BR>
successive FM messages specified in seconds. &nbsp;The range is 1 to 65535.=
 &nbsp;The<BR>
value 0 is not permitted. The default value is 60.&quot; The default AIS an=
d LCK<BR>
repetition period is generically 1-second, not 60-seconds. There is no need=
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'>GS: &nbsp;Changed the default, when not using the option=
al clearing, to 1 second. &nbsp;<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
for a range of AIS and LCK repetition periods. The first AIS packet for eac=
h<BR>
LSP/PW impacted by the fault has to be generated within 1 second after a<BR=
>
signal fail type defect is detected and the next one has to be generated<BR=
>
1-second later. This 1 second period is necessary in order to prevent that<=
BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'>GS: Why does Y.1731 allow for 1 second or 1 minute?<BR>
<BR>
...George<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
downstream the alarms are raised (which happens after 2.5 +/- 0.5 seconds).=
<BR>
If the first AIS packet was lost (due to congestion or bit errors) then<BR>
there is a second AIS packet that will be received by the MEP Sink fucntion=
<BR>
before the 2.5 +/- 0.5 second fault cause to failure filter will expire.<BR=
>
Either the first or second AIS packet will clear the fault cause and preven=
t<BR>
the alarm from being raised.<BR>
<BR>
<BR>
<BR>
MPLS-TP AIS and LCK OAM packets should be very simple OAM packets including=
<BR>
only a Version number and OAM Type (MsgType or OpCode). AIS and LCK OAM<BR>
packets should be inserted within 1 second after the condition to generate<=
BR>
those packets became active and these OAM packets must be send with a 1<BR>
second repetition rate.<BR>
<BR>
Regards,<BR>
Maarten<BR>
<BR>
<BR>
<BR>
&nbsp;&nbsp;<BR>
<BR>
-----Original Message-----<BR>
From: <a href=3D"mpls-tp-bounces@ietf.org">mpls-tp-bounces@ietf.org</a> [<a h=
ref=3D"mailto:mpls-tp-bounces@ietf.org">mailto:mpls-tp-bounces@ietf.org</a>] O=
n Behalf<BR>
Of Maarten Vissers<BR>
Sent: donderdag 17 december 2009 8:45<BR>
To: 'Loa Andersson'; <a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a>; <a hr=
ef=3D"mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"ccamp@ietf.org">ccamp@ietf.or=
g</a>;<BR>
<a href=3D"pwe3@ietf.org">pwe3@ietf.org</a><BR>
Subject: [mpls-tp] Comment<BR>
onhttp://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt<BR>
<BR>
<BR>
Some comments on the content of this draft:<BR>
<BR>
In section 2.1 it is stated:<BR>
&quot; &nbsp;&lt;..&gt;<BR>
&nbsp;&nbsp;&nbsp;For example an AIS message may be sent during a protectio=
n switching<BR>
&nbsp;&nbsp;&nbsp;event and would cease being sent if the protection switch=
 was<BR>
&nbsp;&nbsp;&nbsp;successful in restoring the link.<BR>
<BR>
&nbsp;&nbsp;&nbsp;Its primary purpose is to suppress alarms in the MPLS-TP =
layer<BR>
&nbsp;&nbsp;&nbsp;network above the level at which the defect occurs. &nbsp=
;The AIS message<BR>
&nbsp;&nbsp;&nbsp;MAY be used to trigger recovery mechanisms. &nbsp;It shou=
ld be noted that<BR>
&nbsp;&nbsp;&nbsp;such use would be subject to false positives, e.g. unnece=
ssary<BR>
&nbsp;&nbsp;&nbsp;protection switching events in the client layer.&quot;<BR=
>
<BR>
It is not correct to state that AIS sending is stopped if the protection<BR=
>
switch was succesful. The reason is that the AIS insertion is done by a MEP=
<BR>
Sink function that is upstream of the protection switch selector process,<B=
R>
and this MEP Sink function is as such unaware of the presence of a<BR>
protection switch process and of the state of the protection switch process=
.<BR>
<BR>
AIS in packet transport networks must **not** used to trigger recovery<BR>
mechanisms. Reason is that AIS OAM messages in packet transport network are=
<BR>
to be generated within 1 second after the detection of the signal fail type=
<BR>
defect detection and be generated with a periodicity of 1 second. These<BR>
times are much too long to trigger any recovery mechanism.<BR>
<BR>
The 1 second time requirement to generate the first AIS message is derived<=
BR>
from the 2.5 +/- 0.5 second fault cause to failure integration timer as<BR>
specified in G.7710. Generation of the first AIS message within a period of=
<BR>
1 second will leave enough time to reach the downstream MEP Sink function<B=
R>
and suppress the fault cause that report the interruption of the connection=
.<BR>
<BR>
Protection switching in packet transport networks is triggered by e.g. loss=
<BR>
of continuity and misconnection defects.<BR>
<BR>
In section 2.2 it is stated:<BR>
&quot; &nbsp;The LDI message is generated in response to detecting a fatal =
failure<BR>
&nbsp;&nbsp;&nbsp;in the server layer. &nbsp;The LDI message MUST NOT be se=
nt until the<BR>
&nbsp;&nbsp;&nbsp;defect has been determined to be fatal. &nbsp;For example=
 during a<BR>
&nbsp;&nbsp;&nbsp;protection switching event LDI messages are not sent. &nb=
sp;However if the<BR>
&nbsp;&nbsp;&nbsp;protection switch was unsuccessful in restoring the link =
within the<BR>
&nbsp;&nbsp;&nbsp;expected repair time, an LDI message MUST be sent.&quot;<=
BR>
and in section 2.1 it is stated:<BR>
&quot; &nbsp;The MPLS-TP Alarm Indication Signal (AIS) message is generated=
 in<BR>
&nbsp;&nbsp;&nbsp;response to detecting defects in the server layer. &nbsp;=
The AIS message<BR>
&nbsp;&nbsp;&nbsp;SHOULD be sent as soon is the condition is detected, that=
 is before<BR>
&nbsp;&nbsp;&nbsp;any determination has been made as to whether the conditi=
on is fatal.&quot;<BR>
<BR>
This draft suggest that it is possible for a MEP Sink function to determine=
<BR>
if the fault is *fatal* or *not fatal*. This is not possible for a MEP Sink=
<BR>
function. The reason is that a MEP Sink function has no knowledge of the<BR=
>
presence or state of a protection switch process associated with the<BR>
connection. E.g. the protection switch process may be in a downstream node.=
<BR>
<BR>
It is also not necessary to make AIS generation conditional on e.g.<BR>
protection switch actions. Reason is that a protection switch process will<=
BR>
select traffic from either a working connection input port, or a protection=
<BR>
connection input port. Any traffic present on the not selected input port<B=
R>
will drop at this input port and not be forwarded to the protection switch<=
BR>
process output port. At the output port AIS messages will be present as lon=
g<BR>
as the protection switch process selects its traffic from the failed<BR>
connection; once the protection switch process selects its traffic from the=
<BR>
non-failed connection AIS messages will not longer be forwarded to the<BR>
output port.<BR>
<BR>
This draft should as such not become a WG document.<BR>
<BR>
Regards,<BR>
Maarten<BR>
<BR>
-----Original Message-----<BR>
From: <a href=3D"mpls-tp-bounces@ietf.org">mpls-tp-bounces@ietf.org</a> [<a h=
ref=3D"mailto:mpls-tp-bounces@ietf.org">mailto:mpls-tp-bounces@ietf.org</a>] O=
n Behalf<BR>
Of Loa Andersson<BR>
Sent: donderdag 17 december 2009 5:36<BR>
To: <a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a>; <a href=3D"mpls@ietf.org=
">mpls@ietf.org</a>; <a href=3D"ccamp@ietf.org">ccamp@ietf.org</a>; <a href=3D"p=
we3@ietf.org">pwe3@ietf.org</a><BR>
Subject: [mpls-tp] Poll om making<BR>
<a href=3D"http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt">http://www.=
ietf.org/id/draft-sfv-mpls-tp-fault-01.txt</a> a working group<BR>
document<BR>
<BR>
All,<BR>
<BR>
this is to start a two week poll on making<BR>
<BR>
<a href=3D"http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt">http://www.=
ietf.org/id/draft-sfv-mpls-tp-fault-01.txt</a><BR>
<BR>
an MPLS working group document.<BR>
<BR>
Send a mail to the <a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a> mailing =
list, indicating &quot;yes/support&quot;<BR>
or &quot;no/do not support&quot;.<BR>
<BR>
Comments on the content of the draft should be sent to the same mailing lis=
t<BR>
with a different subject line.<BR>
<BR>
The poll ends Friday 15 Jan, 2010.<BR>
<BR>
/Loa<BR>
--<BR>
<BR>
<BR>
Loa Andersson &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;email: <a href=3D"loa.andersson@ericsson.com">loa.andersson@ericsson.co=
m</a><BR>
Sr Strategy and Standards Manager &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"loa@pi.nu">loa@pi.nu</a><BR>
Ericsson Inc &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;phone: +46 10 717 52 13<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+46 767 72 92 13<BR>
_______________________________________________<BR>
mpls-tp mailing list<BR>
<a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a><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-tp mailing list<BR>
<a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a><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-tp mailing list<BR>
<a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ietf.or=
g/mailman/listinfo/mpls-tp</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3351144504_101768198--


From daniel@olddog.co.uk  Thu Mar 11 07:06:12 2010
Return-Path: <daniel@olddog.co.uk>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42F9F3A6BC4 for <ccamp@core3.amsl.com>; Thu, 11 Mar 2010 07:06:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_52=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 G5xV+wksJ8yk for <ccamp@core3.amsl.com>; Thu, 11 Mar 2010 07:06:11 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.193.159]) by core3.amsl.com (Postfix) with ESMTP id DC9F53A67E5 for <ccamp@ietf.org>; Thu, 11 Mar 2010 07:04:30 -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 o2BF4Lwa007424;  Thu, 11 Mar 2010 15:04:22 GMT
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id o2BF4K66007393;  Thu, 11 Mar 2010 15:04:21 GMT
From: "Daniel King" <daniel@olddog.co.uk>
To: <ccamp@ietf.org>
References: <003601cab0e7$b5474040$1fd5c0c0$@co.uk> <027c01cab991$ef543470$cdfc9d50$@co.uk>
In-Reply-To: <027c01cab991$ef543470$cdfc9d50$@co.uk>
Date: Thu, 11 Mar 2010 15:04:22 -0000
Message-ID: <008201cac12c$22b43e40$681cbac0$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acqw57TEOgs0P+/hQGW/9xkKgEy11QIqZatgAeaPqTA=
Content-Language: en-gb
Cc: "'Brungard, Deborah A, ALABS'" <dbrungard@att.com>
Subject: Re: [CCAMP] Agenda Requests for IETF 77
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 15:06:12 -0000

Hi all, 

The draft ccamp agenda for IETF 77 is now online:

http://tools.ietf.org/wg/ccamp/agenda?item=agenda77.html

If anyone has any questions please let us know. If your presenting slides,
please send me your slides (CC co-chairs) no later than Friday March 19. 

Br, Dan.

-----Original Message-----
From: Daniel King [mailto:daniel@olddog.co.uk] 
Sent: 18 February 2010 22:14
To: ccamp@ietf.org
Cc: 'Brungard, Deborah A, ALABS'; 'Lou Berger'; daniel@olddog.co.uk
Subject: Agenda Requests for IETF 77

Hello CCAMP'rs,

Please let us know if you have an agenda request for our CCAMP sessions at
IETF 77.  Reply to this email (please also CC the co-chairs) with the
desired duration, topic/draft title, and presenter for each slot that you
request. Please let us have your requests by Friday, March 12th. 

Key dates are at: http://www.ietf.org/meeting/cutoff-dates-2010.html#IETF77

2010-02-26 (Friday): Final agenda to be published.
2010-03-01 (Monday): Internet Draft Cut-off for initial document (-00)
submission by 17:00 PST (01:00 Tuesday, March 2 UTC), upload using IETF ID
Submission Tool.
2010-03-08 (Monday): Internet Draft final submission cut-off by 17:00 PST
(01:00 Tuesday, March 9 UTC), upload using IETF ID Submission Tool.

The preliminary agenda is at: https://datatracker.ietf.org/meeting/agenda/

Thanks,
Dan


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


From loa@pi.nu  Thu Mar 11 15:32:54 2010
Return-Path: <loa@pi.nu>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C79043A68C6; Thu, 11 Mar 2010 15:32:54 -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 3X6YOU76o1m5; Thu, 11 Mar 2010 15:32:54 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 713693A68B2; Thu, 11 Mar 2010 15:32:41 -0800 (PST)
Received: from pi.nu (localhost [127.0.0.1]) by mail.pi.nu (Postfix) with ESMTP id 4F957D4055; Fri, 12 Mar 2010 00:32:45 +0100 (CET)
Received: from 59.154.63.92 (SquirrelMail authenticated user loa@pi.nu) by pi.nu with HTTP; Fri, 12 Mar 2010 00:32:45 +0100
Message-ID: <97ea8a23065211ee6df8f08ea5e4ba67.squirrel@pi.nu>
Date: Fri, 12 Mar 2010 00:32:45 +0100
From: "Loa Andersson" <loa@pi.nu>
To: mpls@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org, ccamp@ietf.org
User-Agent: SquirrelMail/1.4.19
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: [CCAMP] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 23:32:54 -0000

All,

this is to start an MPLS working group last call on
draft-ietf-mpls-tp-identifiers-01

There is a discussion on the OAM model for MS-PWs where we haven't been
able to come to conclusion. Once we reach agreement the document will
be updated. Comments in this area are welcome during the working group
last call.


Please send your comments to the mpls-tp@ietf.org mailing list.

The working group last ends eob April 2nd.

/Loa

--

Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///
   phone:  +46 10 717 52 13
           +46 767 72 92 13

   email:  loa.andersson@ericsson.com
           loa@pi.nu





From davari@broadcom.com  Thu Mar 11 16:27:42 2010
Return-Path: <davari@broadcom.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 586243A6849; Thu, 11 Mar 2010 16:27:42 -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 RMs6xgPDZkTN; Thu, 11 Mar 2010 16:27:40 -0800 (PST)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 4F8C33A6822; Thu, 11 Mar 2010 16:27:40 -0800 (PST)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 11 Mar 2010 16:27:34 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Thu, 11 Mar 2010 16:27:34 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Loa Andersson" <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Date: Thu, 11 Mar 2010 16:27:32 -0800
Thread-Topic: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
Thread-Index: AcrBczT1LsEVDiSwTX2v9QSMrvpjyAAA7NaQ
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD68171AE5BF5@SJEXCHCCR02.corp.ad.broadcom.com>
References: <97ea8a23065211ee6df8f08ea5e4ba67.squirrel@pi.nu>
In-Reply-To: <97ea8a23065211ee6df8f08ea5e4ba67.squirrel@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 678755FC31G56992480-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 11 Mar 2010 17:49:14 -0800
Subject: Re: [CCAMP] [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 00:27:42 -0000

Hi,

Couple of comments:

1) Why the Interface_ID is 32-bit while the Tunnel_ID is 16-bit? Do we need=
 to support more interfaces than tunnels?=20
2) The draft defines the Global_Tunnel_ID as:
      Src-Global_ID::Src-Node_ID::Src-Tunnel_Num:: Dst-Global_ID::Dst-Node_=
ID::Dst-Tunnel_Num

This seems to define a bidirectional tunnel. Is that the intent? If so plea=
se clarify. If not then why Dst-Global_ID::Dst-Node_ID::Dst-Tunnel_Num is n=
eeded?

3) Is section 5.2 talking about unidirectional LSP or bidirectional LSP?
4) Section 7.1.2.1 says:
	Since a MEG pertains to a single MPLS-TP Tunnel, IP compatible MEG_IDs for=
 MPLS-TP Tunnels are simply the corresponding Tunnel_IDs

Assuming the Tunnel_ID is a unidirectional ID, then this statement implies =
that for the reverse direction a different MEG_ID is required. Is that the =
intent? If so why?

5) Why are drafts part of the normative references?

6) Will section 8 (open issues) be removed before publishing? This section =
implies that the MEP and MIP definition is not yet aligned with framework?

Regards,
Shahram



-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa=
 Andersson
Sent: Thursday, March 11, 2010 3:33 PM
To: mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ietf.org
Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01

All,

this is to start an MPLS working group last call on
draft-ietf-mpls-tp-identifiers-01

There is a discussion on the OAM model for MS-PWs where we haven't been
able to come to conclusion. Once we reach agreement the document will
be updated. Comments in this area are welcome during the working group
last call.


Please send your comments to the mpls-tp@ietf.org mailing list.

The working group last ends eob April 2nd.

/Loa

--

Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///
   phone:  +46 10 717 52 13
           +46 767 72 92 13

   email:  loa.andersson@ericsson.com
           loa@pi.nu




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



From Manuel.Paul@telekom.de  Fri Mar 12 00:21:30 2010
Return-Path: <Manuel.Paul@telekom.de>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDC303A6B48 for <ccamp@core3.amsl.com>; Fri, 12 Mar 2010 00:21:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ujWEmpX8RTpt for <ccamp@core3.amsl.com>; Fri, 12 Mar 2010 00:21:24 -0800 (PST)
Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id 0225F3A692A for <ccamp@ietf.org>; Fri, 12 Mar 2010 00:15:38 -0800 (PST)
Received: from s4de9jsaanm.mgb.telekom.de (HELO S4DE9JSAANM.ost.t-com.de) ([10.125.177.122]) by tcmail81.telekom.de with ESMTP; 12 Mar 2010 09:15:29 +0100
Received: from S4DE9JSAANI.ost.t-com.de ([10.125.177.223]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 12 Mar 2010 09:15:29 +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: Fri, 12 Mar 2010 09:14:43 +0100
Message-ID: <40FB0FFB97588246A1BEFB05759DC8A0040D9EED@S4DE9JSAANI.ost.t-com.de>
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
Thread-Index: Acq3LhTmuSG/kxGCTt+1iMNqBtXcygKiX3cA
References: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
From: <Manuel.Paul@telekom.de>
To: <ccamp@ietf.org>
X-OriginalArrivalTime: 12 Mar 2010 08:15:29.0093 (UTC) FILETIME=[2D441750:01CAC1BC]
Subject: Re: [CCAMP] [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 08:21:30 -0000

Yes/support.


Best regards
Manuel

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On=20
> Behalf Of BRUNGARD, DEBORAH A (ATTLABS)
> Sent: Friday, February 26, 2010 10:53 PM
> To: CCAMP
> Cc: mpls@ietf.org; pwe3@ietf.org; mpls-tp@ietf.org
> Subject: [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
>=20
> All,
>=20
> This is to start a two week working group poll on making
> draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working
> group document. This poll is being initiated at this time as this
> document is part of the MPLS-TP work and it is needed to progress the
> work.
>=20
> Send your response to the ccamp@ietf.org mailing list (only),=20
> indicating
> "yes/support" or "no/do not support".
>=20
> This poll ends March 12th.
>=20
> Deborah
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>=20

From loa@pi.nu  Fri Mar 12 18:15:46 2010
Return-Path: <loa@pi.nu>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A8153A68CE; Fri, 12 Mar 2010 18:15:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQ+HwADwrYXP; Fri, 12 Mar 2010 18:15:45 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 75C1F3A67B6; Fri, 12 Mar 2010 18:15:38 -0800 (PST)
Received: from [10.100.0.174] (unknown [203.47.135.90]) (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 5C15AD4055; Sat, 13 Mar 2010 03:15:39 +0100 (CET)
Message-ID: <4B9AF56D.1050203@pi.nu>
Date: Sat, 13 Mar 2010 13:16:13 +1100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>,  mpls-chairs@tools.ietf.org, mpls@ietf.org, pwe3@ietf.org,  CCAMP <ccamp@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [CCAMP] MPLS working group last call on draft-ietf-mpls-tp-data-plane-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 02:15:46 -0000

All,

this is to start an MPLS working group last call on

http://pi.nu/~loa/draft-ietf-mpls-tp-data-plane-01.txt

As you can see it is not yet available on the IETF home page (we
missed the cut-off date with a few days), we try to place it in
the IETF repository as quickly as possible.

In the mean time it is available from the web page above.

Please send your comments to the mpls-tp@ietf.org mailing
list.

The working group last call ends on April 2nd.

/Loa
-- 


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 dongjie_dj@huawei.com  Sun Mar 14 20:16:05 2010
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF39E3A686C; Sun, 14 Mar 2010 20:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.085
X-Spam-Level: 
X-Spam-Status: No, score=-0.085 tagged_above=-999 required=5 tests=[AWL=-0.190, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_56=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBqEyGTcIoSf; Sun, 14 Mar 2010 20:16:03 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 9EE6D3A6809; Sun, 14 Mar 2010 20:16:03 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZA004UTZQNU0@szxga02-in.huawei.com>; Mon, 15 Mar 2010 11:15:59 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZA0030SZQNVP@szxga02-in.huawei.com>; Mon, 15 Mar 2010 11:15:59 +0800 (CST)
Received: from d65110 ([10.111.12.191]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KZA0061GZQNHG@szxml04-in.huawei.com>; Mon, 15 Mar 2010 11:15:59 +0800 (CST)
Date: Mon, 15 Mar 2010 11:15:58 +0800
From: Jie Dong <dongjie_dj@huawei.com>
To: 'JP Vasseur' <jvasseur@cisco.com>
Message-id: <01c301cac3ed$d5c196e0$bf0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcrD7dVbDOdzw3SzSamAxLH0e4JNHw==
Cc: mpls@ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] New Draft Notification: draft-dong-ccamp-rsvp-te-plr-designation-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2010 03:16:06 -0000

Sorry for any duplication. I just found this mail didn't appear in the
mailing lists.

> > [Jie] This can be a solution for controlling backup LSPs,
> but it may
> > not work in all scenarios. One example is even when there is enough 
> > bandwidth, operators may do not want to reserve such bandwidth for 
> > backup LSPs.
> > 	
> 
> That seems a bit awkward to me. Usually if you provision backup 
> capacity and you can accommodate a primary TE LSP, why would you want 
> not to do it ?
SP can choose to protect some specific nodes based on network topology,
resource, policy, etc. 
Sometimes more protection LSPs do not mean higher availability.
There can be a case like this: 
The SP has the knowledge that some nodes on the path are using some other
mechanisms to insure survivability, thus a local repair for such nodes is
unneeded. Thus explicitly inform this can save resources of establishing and
maintaining unneeded backup LSPs. 
In this case, the key point here is not whether there is enough bandwidth,
but to determine whether backup paths are needed. If such backup LSPs are
unnecessary, there is no need to waste bandwidth on them.

Besides, based on RFC 4090, all the nodes(except the egress) along the LSP
will be candidate PLRs and will spend resources on establishment and
maintenance of backup paths. 
With this draft, non-PLR nodes do not need to participate in fast reroute
processing.

> Then if you cannot accommodate
> them all, there many existing techniques.
Do you mean RFC 4873 ? 

> Last but not least such mechanism requires to know the path 
> in advance to be effective. What do you do when you reroute ?
I don't get your point here. Could you please give more clarification?


Best regards,
Jie


> 
> >
> > Best regards,
> > Jie
> >
> >
> > 	On Mar 3, 2010, at 9:29 AM, Jie Dong wrote:
> >
> >
> >
> > 		Dear all,
> > 		
> > 		There is a new internet draft:
> > draft-dong-ccamp-rsvp-te-plr-designation-00:
> > 	
> > 
> http://tools.ietf.org/html/draft-dong-ccamp-rsvp-te-plr-designation-00
> > 		
> > 		The abstract is as follows:
> > 		
> > 		This document defines RSVP-TE extensions which 
> enable the ingress 
> > node to
> > 		designate particular LSRs along the path as 
> Points of Local Repair 
> > (PLRs) of
> > 		the protected LSP, and further indicate the 
> protection type of each 
> > PLR.
> > 		These mechanisms could enhance the control over 
> the establishment of 
> > backup
> > 		LSPs, and also could save the resources needed 
> for establishing and
> > 		maintaining unnecessary backup LSPs.
> > 		
> > 		Comments are appreciated.
> > 		
> > 		
> > 		
> > 		Best regards,
> > 		Jie
> > 		
> > 		
> > 		_______________________________________________
> > 		CCAMP mailing list
> > 		CCAMP@ietf.org
> > 		https://www.ietf.org/mailman/listinfo/ccamp
> > 		
> >
> >
> >
> 



From vishwas.ietf@gmail.com  Mon Mar 15 21:11:05 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 455483A6A29 for <ccamp@core3.amsl.com>; Mon, 15 Mar 2010 21:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level: 
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[AWL=0.707,  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 PZn8MNBt6Ywc for <ccamp@core3.amsl.com>; Mon, 15 Mar 2010 21:11:04 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by core3.amsl.com (Postfix) with ESMTP id 2B59E3A6A74 for <ccamp@ietf.org>; Mon, 15 Mar 2010 21:11:04 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 9so1008024qwb.31 for <ccamp@ietf.org>; Mon, 15 Mar 2010 21:11:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=rAxwotmEkHPM9cSCQv6+q4h2k4pJYDdNbDP4GacZWd4=; b=DqeV7q9TlAEKPxDjD0GXrAQqhiLzttQjRfun/fb/F0mDF+Z4pCnpClyBNJqtf9HtpF 6ijmeBZR0P+allYVdBpwmMAeaABax3ytekbnoBPCy0iezu0vaWzJh6ityGf6QWEqz3os KV1I6y9aaGsuyjtSjc6Y+KU2dAaPfeW3+6wTc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iwv1EKCold5O4KKDQJDMu1IpeDKSTIJK2ZbEqWwig/uhg7h5NBHjoVLxRQ6BJKvZE6 CyTJ9KjUSYD+5bP+tttelNFD+AnJ8Dvd+SwMKgRwdufPcfgo3wmdWjA2kmI3IY/7hPU0 OEdTGd/pQxl+JqMtw6/UIJTsjtudCvuJ0vJ7s=
MIME-Version: 1.0
Received: by 10.224.55.65 with SMTP id t1mr3011285qag.313.1268712669318; Mon,  15 Mar 2010 21:11:09 -0700 (PDT)
Date: Mon, 15 Mar 2010 21:11:09 -0700
Message-ID: <77ead0ec1003152111r5fcad393t6f2719f86243bd24@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: ccamp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [CCAMP] LMP-bis RFC
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2010 04:11:05 -0000

Hi folks,

Based on feedback from the list and chairs I am planning to respin the
RFC4204. Here are the main isues identified:

1. Config Retransmit algorithm is broken and causes LMP Control
Channel to never come up in some cases.
2. Hello Negotiation needs to be clarified.
3. Multiple issues with IPv6 both for TE_LINK as well as DATA_LINK.
4. Message_ID usage clarity.
5. More clarity about Test messages in case of packet networks but
seperate data and control plane.

Do let me know of other issues you may have?

Thanks,
Vishwas

From lberger@labn.net  Tue Mar 16 04:19:27 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EA073A6823 for <ccamp@core3.amsl.com>; Tue, 16 Mar 2010 04:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.189
X-Spam-Level: 
X-Spam-Status: No, score=-2.189 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PkM0Kqk7PmJl for <ccamp@core3.amsl.com>; Tue, 16 Mar 2010 04:19:26 -0700 (PDT)
Received: from outbound-mail-313.bluehost.com (outbound-mail-313.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id A3CD63A6980 for <ccamp@ietf.org>; Tue, 16 Mar 2010 04:19:26 -0700 (PDT)
Received: (qmail 19979 invoked by uid 0); 16 Mar 2010 11:19:35 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 16 Mar 2010 11:19:35 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=sYBrvYF+1L50HfODpuj9ApLeQh+yzzyo7nY64+Bej/5X+GA2FEdcxk9eA+dTh3oKFlKvUA5+EAdoZKmLhQYCgAf0AJlv/VKmDE7bdNLpPDUGSzbJ1I+Vpbo/RMnOMjJy;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1NrUoA-0005LZ-Sv; Tue, 16 Mar 2010 05:19:35 -0600
Message-ID: <4B9F6947.5030407@labn.net>
Date: Tue, 16 Mar 2010 07:19:35 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20091214 Eudora/3.0b4
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec1003152111r5fcad393t6f2719f86243bd24@mail.gmail.com>
In-Reply-To: <77ead0ec1003152111r5fcad393t6f2719f86243bd24@mail.gmail.com>
X-Enigmail-Version: 0.96a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] LMP-bis RFC
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2010 11:19:27 -0000

Vishwas,
	A question for the WG will be is whether to do a 4204-bis or to just
document just the issues and changes.  I think it would be helpful to
start with the latter so there is a clear understanding of the changes
being proposed.  Based on the scope of those changes, the WG then can
decide if we should have a bis or an update.

Much thanks,
Lou

On 3/16/2010 12:11 AM, Vishwas Manral wrote:
> Hi folks,
> 
> Based on feedback from the list and chairs I am planning to respin the
> RFC4204. Here are the main isues identified:
> 
> 1. Config Retransmit algorithm is broken and causes LMP Control
> Channel to never come up in some cases.
> 2. Hello Negotiation needs to be clarified.
> 3. Multiple issues with IPv6 both for TE_LINK as well as DATA_LINK.
> 4. Message_ID usage clarity.
> 5. More clarity about Test messages in case of packet networks but
> seperate data and control plane.
> 
> Do let me know of other issues you may have?
> 
> Thanks,
> Vishwas
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
> 
> 
> 

From rfgraveman@gmail.com  Tue Mar 16 04:36:40 2010
Return-Path: <rfgraveman@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0A8A3A696A for <ccamp@core3.amsl.com>; Tue, 16 Mar 2010 04:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O9h79QTSPmKG for <ccamp@core3.amsl.com>; Tue, 16 Mar 2010 04:36:39 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id B12A73A682F for <ccamp@ietf.org>; Tue, 16 Mar 2010 04:36:39 -0700 (PDT)
Received: by gwj18 with SMTP id 18so1822736gwj.31 for <ccamp@ietf.org>; Tue, 16 Mar 2010 04:36:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=wWmse0t7dQR/GFxer+BdrknLryBNngcafT9dZkEwvFw=; b=YNcrf3yVtPIYDfoTTSBhIeQ0CzCUVJVBM4JUcmYhKxv2rVG95xixQsglvYh/Y1UhX3 1hzbWtWfFXsBd7HQ6lEs2QBeN/7VozEfxyASckcJyAPSohpdTf+6cKbAlH/pPY9mskDi cEU03jGfMpuInOiQsYkUW5HuGKb0qQ09F/Aag=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=OWqOuIAwLfXFtHFgQn+YyXib/ix2orymcWXv8PE4w3IRTSYLRZrQ2rSqsZQuxdNcF8 P4nLnR/IXpwp1o6fTQpwMNky1AleD6JuYQXBmh1LJuwgh6XQQM8FT5ASNj2jYnvXIrwa SQd+uZnN+5AOSPscBEoWtu5G7ZDv9LTJwJxNs=
MIME-Version: 1.0
Received: by 10.100.235.26 with SMTP id i26mr329933anh.163.1268739405166; Tue,  16 Mar 2010 04:36:45 -0700 (PDT)
In-Reply-To: <4B9F6947.5030407@labn.net>
References: <77ead0ec1003152111r5fcad393t6f2719f86243bd24@mail.gmail.com> <4B9F6947.5030407@labn.net>
Date: Tue, 16 Mar 2010 07:36:44 -0400
Message-ID: <45c8c21a1003160436t7b1160bbi1dc37f90618b1c8f@mail.gmail.com>
From: Richard Graveman <rfgraveman@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 16 Mar 2010 04:57:31 -0700
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] LMP-bis RFC
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2010 11:36:40 -0000

On Tue, Mar 16, 2010 at 12:11 AM, Vishwas Manral <vishwas.ietf@gmail.com> w=
rote:
> Hi folks,
>
> Based on feedback from the list and chairs I am planning to respin the
> RFC4204. Here are the main isues identified:
>
> 1. Config Retransmit algorithm is broken and causes LMP Control
> Channel to never come up in some cases.
> 2. Hello Negotiation needs to be clarified.
> 3. Multiple issues with IPv6 both for TE_LINK as well as DATA_LINK.
> 4. Message_ID usage clarity.
> 5. More clarity about Test messages in case of packet networks but
> seperate data and control plane.
>
> Do let me know of other issues you may have?

I completely agree with the approach to security, but I have two comments:

1. The references are out of date. Most of the security references
have been updated or replaced, and improved methods are now available
and recommended. These updates actually simplify what need to be said.

2. The statement "confidentiality is not needed" seems to me an
over-reach. In my view, that is a question for the environment in
which the protocol is deployed, not for the protocol designer. It may
be true in many cases, but with the security mechanisms defined,
confidentiality is not a big deal--it comes along with little extra
design.

I would be glad to contribute text for this section at the appropriate time=
.

Richard Graveman


> Thanks,
> Vishwas
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>


On Tue, Mar 16, 2010 at 7:19 AM, Lou Berger <lberger@labn.net> wrote:
>
> Vishwas,
> =A0 =A0 =A0 =A0A question for the WG will be is whether to do a 4204-bis =
or to just
> document just the issues and changes. =A0I think it would be helpful to
> start with the latter so there is a clear understanding of the changes
> being proposed. =A0Based on the scope of those changes, the WG then can
> decide if we should have a bis or an update.
>
> Much thanks,
> Lou
>
> On 3/16/2010 12:11 AM, Vishwas Manral wrote:
>> Hi folks,
>>
>> Based on feedback from the list and chairs I am planning to respin the
>> RFC4204. Here are the main isues identified:
>>
>> 1. Config Retransmit algorithm is broken and causes LMP Control
>> Channel to never come up in some cases.
>> 2. Hello Negotiation needs to be clarified.
>> 3. Multiple issues with IPv6 both for TE_LINK as well as DATA_LINK.
>> 4. Message_ID usage clarity.
>> 5. More clarity about Test messages in case of packet networks but
>> seperate data and control plane.
>>
>> Do let me know of other issues you may have?
>>
>> Thanks,
>> Vishwas
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
>>
>>
>>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>

From vishwas.ietf@gmail.com  Tue Mar 16 07:43:03 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43B033A681B for <ccamp@core3.amsl.com>; Tue, 16 Mar 2010 07:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.218
X-Spam-Level: 
X-Spam-Status: No, score=-2.218 tagged_above=-999 required=5 tests=[AWL=0.381,  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 3TpmQd+tKOb2 for <ccamp@core3.amsl.com>; Tue, 16 Mar 2010 07:43:02 -0700 (PDT)
Received: from mail-pz0-f178.google.com (mail-pz0-f178.google.com [209.85.222.178]) by core3.amsl.com (Postfix) with ESMTP id CEDB53A6B29 for <ccamp@ietf.org>; Tue, 16 Mar 2010 07:40:52 -0700 (PDT)
Received: by pzk8 with SMTP id 8so3388439pzk.29 for <ccamp@ietf.org>; Tue, 16 Mar 2010 07:40:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nLRdoEXNuNF0C3PfUQkztoBG1htGUqAovdg4GiwJhbQ=; b=x9EMau4uIsPEfsFeSijV7mLVnOJsGpWA1QJiVpIfIpGJ2PnvZ4f1M0stFmsmt+FIDD gllEEiCKey1GNXejYYc53d4eNFwIYXZMuN+d3KUGsAOAdDVee7vc4kdoMVWOndnYfh5R +y8Dz109cy/YqEXFUq8HRHNl1PlGH1BOrMlHE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=w0/9WtwTRYbkV3Vlw2GaQKtfNBJiF8ADiUtgjYi7iB/32Jfd+DhzTPfMClpzQfdGN+ C0fDnFtMubnqaNfHuVnVo4u2kTTsrlYtnF7CX/52oFc87g9M6jfIAsimyyDXFv/w0+ZI dxK1/X/WF5X1G0qISzJeukcI6nepaxtyeA7SU=
MIME-Version: 1.0
Received: by 10.141.90.2 with SMTP id s2mr73162rvl.273.1268750457107; Tue, 16  Mar 2010 07:40:57 -0700 (PDT)
In-Reply-To: <4B9F6947.5030407@labn.net>
References: <77ead0ec1003152111r5fcad393t6f2719f86243bd24@mail.gmail.com> <4B9F6947.5030407@labn.net>
Date: Tue, 16 Mar 2010 07:40:56 -0700
Message-ID: <77ead0ec1003160740r60ec913cm97f197f8a8c8f359@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] LMP-bis RFC
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2010 14:43:03 -0000

Hi Lou,

Thanks for your inputs. It sounds like a reasonable approach and will
make the draft accordingly.

The only reason I was going in for a bis version was because I thought
there were some grave errors I found which may require that the base
RFC itself be updated.

Thanks,
Vishwas

On Tue, Mar 16, 2010 at 4:19 AM, Lou Berger <lberger@labn.net> wrote:
>
> Vishwas,
> =A0 =A0 =A0 =A0A question for the WG will be is whether to do a 4204-bis =
or to just
> document just the issues and changes. =A0I think it would be helpful to
> start with the latter so there is a clear understanding of the changes
> being proposed. =A0Based on the scope of those changes, the WG then can
> decide if we should have a bis or an update.
>
> Much thanks,
> Lou
>
> On 3/16/2010 12:11 AM, Vishwas Manral wrote:
>> Hi folks,
>>
>> Based on feedback from the list and chairs I am planning to respin the
>> RFC4204. Here are the main isues identified:
>>
>> 1. Config Retransmit algorithm is broken and causes LMP Control
>> Channel to never come up in some cases.
>> 2. Hello Negotiation needs to be clarified.
>> 3. Multiple issues with IPv6 both for TE_LINK as well as DATA_LINK.
>> 4. Message_ID usage clarity.
>> 5. More clarity about Test messages in case of packet networks but
>> seperate data and control plane.
>>
>> Do let me know of other issues you may have?
>>
>> Thanks,
>> Vishwas
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
>>
>>
>>
>

From vishwas.ietf@gmail.com  Tue Mar 16 07:45:25 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DACF33A680A for <ccamp@core3.amsl.com>; Tue, 16 Mar 2010 07:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.245
X-Spam-Level: 
X-Spam-Status: No, score=-2.245 tagged_above=-999 required=5 tests=[AWL=0.354,  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 TS5Ca1bc2gBl for <ccamp@core3.amsl.com>; Tue, 16 Mar 2010 07:45:25 -0700 (PDT)
Received: from mail-pz0-f178.google.com (mail-pz0-f178.google.com [209.85.222.178]) by core3.amsl.com (Postfix) with ESMTP id 8EE513A69D4 for <ccamp@ietf.org>; Tue, 16 Mar 2010 07:45:00 -0700 (PDT)
Received: by pzk8 with SMTP id 8so3393167pzk.29 for <ccamp@ietf.org>; Tue, 16 Mar 2010 07:45:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XfYU26NTRnn0dTU4NKgwI7joty7FEqiSNNbHZv/8SRE=; b=IGSNa94VM7MHyNNLzhppgTZyWa9++It1jQiQxBlmd+xzueusY7ynIdn3Hug1YKZd7v sPVD8WfvBIpp8LkfSAV5Xj6RZDTnWmAKHR5UrXwVYrmpNj7+JAhg4BQRi7/EwNjTumvu Crx2A0QAHt6R/QeL8CawvJ9N+hRbGW4I/vqRI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=CHR0Vyljz4NOFPZFKrGQWR98WGYOQIk46LjUMx5VjK8ozAZgF5jcL14eAV1ij3YFIb NFFcnrozb6ZvVVnPvti3nC1BXCbOlHFRj3scy3+Tf3Ed1sIrQu03rk7Ll6IakK4sI0fW BPhp/y6ak5wQEzqSwEpY71/Uy3yi0WjMI923o=
MIME-Version: 1.0
Received: by 10.114.51.18 with SMTP id y18mr5048way.106.1268750635500; Tue, 16  Mar 2010 07:43:55 -0700 (PDT)
In-Reply-To: <45c8c21a1003160436t7b1160bbi1dc37f90618b1c8f@mail.gmail.com>
References: <77ead0ec1003152111r5fcad393t6f2719f86243bd24@mail.gmail.com> <4B9F6947.5030407@labn.net> <45c8c21a1003160436t7b1160bbi1dc37f90618b1c8f@mail.gmail.com>
Date: Tue, 16 Mar 2010 07:43:55 -0700
Message-ID: <77ead0ec1003160743t2be5728eu1575e80035662bb9@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Richard Graveman <rfgraveman@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] LMP-bis RFC
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2010 14:45:25 -0000

Hi Richard,

I will certainly take your help when I get there!!! I agree the
references are now out of date (RFC2401 instead of 4301 etc).

We can still discuss the confidentiality part and why it may be
required for LMP.

Thanks,
Vishwas

On Tue, Mar 16, 2010 at 4:36 AM, Richard Graveman <rfgraveman@gmail.com> wr=
ote:
> On Tue, Mar 16, 2010 at 12:11 AM, Vishwas Manral <vishwas.ietf@gmail.com>=
 wrote:
>> Hi folks,
>>
>> Based on feedback from the list and chairs I am planning to respin the
>> RFC4204. Here are the main isues identified:
>>
>> 1. Config Retransmit algorithm is broken and causes LMP Control
>> Channel to never come up in some cases.
>> 2. Hello Negotiation needs to be clarified.
>> 3. Multiple issues with IPv6 both for TE_LINK as well as DATA_LINK.
>> 4. Message_ID usage clarity.
>> 5. More clarity about Test messages in case of packet networks but
>> seperate data and control plane.
>>
>> Do let me know of other issues you may have?
>
> I completely agree with the approach to security, but I have two comments=
:
>
> 1. The references are out of date. Most of the security references
> have been updated or replaced, and improved methods are now available
> and recommended. These updates actually simplify what need to be said.
>
> 2. The statement "confidentiality is not needed" seems to me an
> over-reach. In my view, that is a question for the environment in
> which the protocol is deployed, not for the protocol designer. It may
> be true in many cases, but with the security mechanisms defined,
> confidentiality is not a big deal--it comes along with little extra
> design.
>
> I would be glad to contribute text for this section at the appropriate ti=
me.
>
> Richard Graveman
>
>
>> Thanks,
>> Vishwas
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
>>
>
>
> On Tue, Mar 16, 2010 at 7:19 AM, Lou Berger <lberger@labn.net> wrote:
>>
>> Vishwas,
>> =A0 =A0 =A0 =A0A question for the WG will be is whether to do a 4204-bis=
 or to just
>> document just the issues and changes. =A0I think it would be helpful to
>> start with the latter so there is a clear understanding of the changes
>> being proposed. =A0Based on the scope of those changes, the WG then can
>> decide if we should have a bis or an update.
>>
>> Much thanks,
>> Lou
>>
>> On 3/16/2010 12:11 AM, Vishwas Manral wrote:
>>> Hi folks,
>>>
>>> Based on feedback from the list and chairs I am planning to respin the
>>> RFC4204. Here are the main isues identified:
>>>
>>> 1. Config Retransmit algorithm is broken and causes LMP Control
>>> Channel to never come up in some cases.
>>> 2. Hello Negotiation needs to be clarified.
>>> 3. Multiple issues with IPv6 both for TE_LINK as well as DATA_LINK.
>>> 4. Message_ID usage clarity.
>>> 5. More clarity about Test messages in case of packet networks but
>>> seperate data and control plane.
>>>
>>> Do let me know of other issues you may have?
>>>
>>> Thanks,
>>> Vishwas
>>> _______________________________________________
>>> CCAMP mailing list
>>> CCAMP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>
>>>
>>>
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
>>
>

From db3546@att.com  Tue Mar 16 07:48:50 2010
Return-Path: <db3546@att.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EFC43A69D4; Tue, 16 Mar 2010 07:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3SyX00dJ86Y8; Tue, 16 Mar 2010 07:48:49 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id E95703A69B3; Tue, 16 Mar 2010 07:48:48 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: db3546@att.com
X-Msg-Ref: server-8.tower-129.messagelabs.com!1268750936!39438450!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 24908 invoked from network); 16 Mar 2010 14:48:56 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-8.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Mar 2010 14:48:56 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o2GEmiAM002582; Tue, 16 Mar 2010 10:48:45 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o2GEme52002541; Tue, 16 Mar 2010 10:48:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Mar 2010 10:48:50 -0400
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA05FC3B82@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Closed - RE: [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
Thread-Index: Acq3LhTmuSG/kxGCTt+1iMNqBtXcygN5/7/g
References: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
To: "CCAMP" <ccamp@ietf.org>
Cc: mpls@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, pwe3@ietf.org, mpls-tp@ietf.org
Subject: [CCAMP] Closed - RE: [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2010 14:48:50 -0000

All,

This poll has closed.

We have accepted the draft as a ccamp working group document.

Would the authors please re-publish the draft with no other changes than
file-name and version as:
draft-ietf-ccamp-mpls-tp-control-plane-framework

While a few concerns have been raised, this document is identified as
part of the ITU-IETF mpls-tp work program. We encourage those with
interest to participate in progressing the document in a timely manner
as it will now have status as a wg document.

Thanks,
Deborah

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
BRUNGARD, DEBORAH A (ATTLABS)
Sent: Friday, February 26, 2010 4:53 PM
To: CCAMP
Cc: mpls@ietf.org; pwe3@ietf.org; mpls-tp@ietf.org
Subject: [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework

All,

This is to start a two week working group poll on making
draft-abfb-mpls-tp-control-plane-framework-02.txt as a ccamp working
group document. This poll is being initiated at this time as this
document is part of the MPLS-TP work and it is needed to progress the
work.

Send your response to the ccamp@ietf.org mailing list (only), indicating
"yes/support" or "no/do not support".

This poll ends March 12th.

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

From loa@pi.nu  Tue Mar 16 12:24:35 2010
Return-Path: <loa@pi.nu>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A8973A6886; Tue, 16 Mar 2010 12:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gLHX9NVAwtZQ; Tue, 16 Mar 2010 12:24:34 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 2E02B3A67B2; Tue, 16 Mar 2010 12:24:34 -0700 (PDT)
Received: from pi.nu (localhost [127.0.0.1]) by mail.pi.nu (Postfix) with ESMTP id E1B73D4055; Tue, 16 Mar 2010 20:24:38 +0100 (CET)
Received: from 129.192.170.250 (SquirrelMail authenticated user loa@pi.nu) by pi.nu with HTTP; Tue, 16 Mar 2010 20:24:39 +0100
Message-ID: <78ef165f68500e69e7d4dbf7c33d8acf.squirrel@pi.nu>
In-Reply-To: <4B9149A8.8020503@pi.nu>
References: <4B9149A8.8020503@pi.nu>
Date: Tue, 16 Mar 2010 20:24:39 +0100
From: "Loa Andersson" <loa@pi.nu>
To: "Loa Andersson" <loa@pi.nu>
User-Agent: SquirrelMail/1.4.19
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: mpls@ietf.org, mpls-chairs@tools.ietf.org, pwe3@ietf.org, CCAMP <ccamp@ietf.org>, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] working group last call on draft-ietf-mpls-tp-oam-framework-05.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2010 19:24:35 -0000

All,

it has been pointed out that I made the when starting the mpls
working group call on draft-ietf-mpls-tp-oam-framework-05.txt
in not copying the mpls-tp list.

Sorry if it caused any confusion.

This working group last call is therefore extended to April 1st, 2001.

/Loa

> All,
>
>
> this is to start a two week mpls  working group last call on
> draft-ietf-mpls-tp-oam-framework-05.txt.
>
> Please review and send your comments to the mpls-tp@ietf.org mailing list.
> Please do not copy the other mailing lists this working group last call
> is announced on.
>
> The working group last call ends March 19th.
>
> Loa and George
>
> --
>
> 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
>




Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///
   phone:  +46 10 717 52 13
           +46 767 72 92 13

   email:  loa.andersson@ericsson.com
           loa@pi.nu


From Attila.Takacs@ericsson.com  Wed Mar 17 08:28:19 2010
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C1AC3A69B0 for <ccamp@core3.amsl.com>; Wed, 17 Mar 2010 08:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odg8rmSktNI6 for <ccamp@core3.amsl.com>; Wed, 17 Mar 2010 08:28:18 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 83D963A6C50 for <ccamp@ietf.org>; Wed, 17 Mar 2010 08:26:50 -0700 (PDT)
X-AuditID: c1b4fb39-b7b85ae000005cbc-13-4ba0f4c3d214
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 44.DA.23740.3C4F0AB4; Wed, 17 Mar 2010 16:26:59 +0100 (CET)
Received: from ESESSCMS0355.eemea.ericsson.se ([169.254.2.93]) by esessmw0184.eemea.ericsson.se ([153.88.115.81]) with mapi; Wed, 17 Mar 2010 16:26:59 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: CCAMP <ccamp@ietf.org>
Date: Wed, 17 Mar 2010 16:26:58 +0100
Thread-Topic: Protection Object extensions in draft-takacs-ccamp-revertive-ps
Thread-Index: AcrF5kiIk0i1sETMRzytFfn1MbPR6w==
Message-ID: <79F41BA1E9BF3C489375521EF8DDE23C12B19CCEFD@ESESSCMS0355.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [CCAMP] Protection Object extensions in draft-takacs-ccamp-revertive-ps
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Mar 2010 15:28:19 -0000

Hi all,

We have a document out that suggest to extend the Protection Object to carr=
y sub-TLVs: ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-takacs-=
ccamp-revertive-ps-04.txt

This would allow to configure protection timers and revertive operation for=
 protection mechanisms that run independently from the control plane.

We would like to ask for CCAMP WG adoption in Anaheim. Please check the doc=
, your comments are welcome!

Thanks,
Attila

From root@core3.amsl.com  Wed Mar 17 15:30:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 16B4E3A69DA; Wed, 17 Mar 2010 15:30:01 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100317223002.16B4E3A69DA@core3.amsl.com>
Date: Wed, 17 Mar 2010 15:30:02 -0700 (PDT)
Cc: ccamp@ietf.org
Subject: [CCAMP] WG Action: RECHARTER: Common Control and Measurement Plane (ccamp)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Mar 2010 22:30:02 -0000

The Common Control and Measurement Plane (ccamp) working group in the
Routing Area of the IETF has been rechartered.  For additional
information, please contact the Area Directors or the working group
Chairs.

Common Control and Measurement Plane (ccamp)
--------------------------------------------------
Current Status: Active Working Group

Last Modified: 2010-03-09

Chair(s):
 -  Deborah Brungard <db3546@att.com>
 -  Lou Berger <lberger@labn.net>

Routing Area Director(s):
 -  Ross Callon <rcallon@juniper.net>
 -  Adrian Farrel <adrian.farrel@huawei.com>

Routing Area Advisor:
 -  Adrian Farrel <adrian.farrel@huawei.com>

Secretary(ies):
 -  Daniel King <daniel@olddog.co.uk>

Mailing Lists:

General Discussion: ccamp@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/ccamp
Archive: http://www.ietf.org/mail-archive/web/ccamp/current/maillist.html

Description of Working Group:

Organizational Overview

The CCAMP working group coordinates the work within the IETF defining a
common control plane and a separate common measurement plane for
physical path and core tunneling technologies of Internet and telecom
service providers (ISPs and SPs), e.g. O-O and O-E-O optical switches,
TDM Switches, Ethernet Switches, ATM and Frame Relay switches, IP
encapsulation tunneling technologies, and MPLS in cooperation with the
MPLS WG.

In this context, measurement refers to the acquisition and distribution
of attributes relevant to the setting up of tunnels and paths.

CCAMP WG work scope includes:

- Definition of protocol-independent metrics and parameters (measurement
  attributes) for describing links and paths that are required for
  routing and signaling. These will be developed in conjunction with
  requests and requirements from other WGs to ensure overall usefulness.

- Definition of and extensions to protocols for link and path attribute
  measurement. This includes the Link Management Protocol (LMP).

- Functional specification of extensions for GMPLS-related routing
  (OSPF, ISIS) and signaling (RSVP-TE) protocols required for path
  establishment and maintenance. Protocol formats and procedures that
  embody these extensions will be done jointly with the WGs supervising
  those protocols.

- Definition of the mechanisms required to determine the route and
  properties of an established path (tunnel tracing).

- Definition of management objects (e.g., as part of MIB modules) and
  control of OAM techniques relevant to the protocols and extensions
  specified within the WG.

- Work on traffic-engineering GMPLS mechanisms and protocol extensions
  to support source-controlled and explicitly-routed data paths for data
  planes that are already approved by a Standards Development
  Organization (SDO). Note that the specification or modification of
  data planes is out of scope of this working group. Example data planes
  include Wavelength Switched Optical Networks (WSON), Optical Transport
  Networks (OTN), Ethernet, and the MPLS data plane.

- Work on GMPLS mechanisms and protocol extensions to support the
  transport profile of MPLS (MPLS-TP) in cooperation with the MPLS,
  L2VPN, and PWE3 Working Group and in coordination with the
  requirements expressed jointly by the IETF and ITU-T.

CCAMP WG currently works on the following tasks:

- Define how the properties of network resources gathered by a
  measurement protocol (or by other means e.g. configured) can be
  distributed in existing routing protocols, such as OSPF and
  IS-IS. CCAMP will work with the WGs that supervise these
  protocols. The specifics of distribution within IS-IS are being
  addressed in the ISIS WG. Current work activities are focused in the
  areas of WSON and OTN.

- Define signaling and routing mechanisms and extensions to allow path
  and tunnel setup and maintenance across multiple domains, where a
  domain may be an IGP area, an Autonomous System, or any other region
  of topological visibility. To this end, work cooperatively with the
  PCE and MPLS WGs.

- Define abstract link and path properties needed for link and path
  protection. Specify signaling mechanisms for path protection, diverse
  routing and fast path restoration. Ensure that multi-layer path
  protection and restoration functions are achievable using the defined
  signaling, routing, and measurement protocols, either separately or in
  combination.

- Identify signaling and routing requirements for supporting protocol
  extensions in support of data plane technologies (e.g., WSON, OTN,
  MPLS-TP, and Ethernet) and network architectures (e.g. ITU-T's
  Automatically Switched Optical Network (ASON)) not currently met by
  protocols defined in CCAMP; based on these, define mechanisms to
  address these requirements. This activity will build on documents
  produced by the WG, including Informational, Standards Track and
  Experimental documents.

- Produce extensions to the CCAMP WG protocols and RFCs necessary to
  create an MPLS Transport Profile (MPLS TP). The work on the MPLS TP
  will be coordinated between the MPLS, L2VPN, PWE3, and CCAMP working
  groups that are jointly chartered to do MPLS TP work.

In doing this work, the WG will work closely with at least the following
other WGs: MPLS, L2VPN, PWE3, ISIS, OSPF, IDR, and PCE. The WG will also
cooperate with the ITU-T and the IEEE 802.1.

Goals and Milestones:

Done    Post strawman WG goals and charter
Done    Identify and document a limited set of candidate solutions for 
        signalling and for measurement. Among candidate control 
        solutions to be considered are the existing GMPLS drafts.
Done    Build appropriate design teams
Done    Submit WG document defining path setup portions of common 
        control plane protocol
Done    Submit WG document defining common measurement plane protocol
Done    Submit LMP MIB to IESG
Done    Submit protection & restoration documents to IESG
Done    Submit ASON signaling requirements doc to IESG
Done    Submit GMPLS MIBs to IESG
Done    Produce CCAMP WG document for generic tunnel tracing protocol
Done    Produce CCAMP WG document for multi-area/AS signaling and 
        routing
Done    Submit ASON routing requirements doc to IESG
Done    Submit revised charter and milestones to IESG for IESG 
        consideration of more detailed deliverables and determination of 
        usefulness of continuation of WG
Done    First version WG I-D for Advertising TE Node Capabilities in 
        ISIS and OSPF
Done    First version WG I-D for Automatic discovery of MPLS-TE mesh 
        membership
Done    Submit ASON Routing evaluation I-D for IESG review
Done    Cross-WG review of I-D for Advertising TE Node Capabilities in 
        ISIS and OSPF
Done    First version WG I-D MPLS to GMPLS migration strategies
Done    First version WG I-D Requirements for Multi-Layer and Multi-
        Region Networks
Done    First version WG I-D for Evaluation of existing protocols for 
        MLN/MRN
Done    First version of WG I-D for ASON Routing solutions
Done    Submit RSVP-TE extensions for inter-domain signaling I-D for 
        IESG review
Done    Submit Per-domain path computation signaling I-D for IESG review
Done    First version of WG I-D for OSPF-TE/GMPLS MIB module
Done    Submit GMPLS signaling in support of Call Management I-D for 
        IESG review
Done    First version WG Informational I-D for Analysis of inter-domain 
        issues for disjoint and protected paths
Done    Submit I-D for Advertising TE Node Capabilities in ISIS and OSPF 
        for IESG review
Done    First version WG I-D for Protocol solutions for MLN/MRN
Done    Submit GMPLS/ASON lexicography I-D for IESG review
Done    First version WG I-D MPLS-GMPLS interworking requirements and 
        solutions
Done    Submit LSP Stitching I-D for IESG review
Done    Submit I-D for Automatic discovery of MPLS-TE mesh membership 
        for IESG review
Done    First version WG I-D GMPLS OAM Requirements
Done    Submit GMPLS routing and signaling interoperability advice I-D 
        for IESG review
Done    Submit MPLS to GMPLS migration strategies I-D for IESG review
Done    Submit Requirements for Multi-Layer and Multi-Region Networks 
        I-D for IESG review
Done    Submit MPLS-GMPLS interworking requirements and solutions I-D 
        for IESG review
Done    Submit Evaluation of existing protocols for MLN/MRN for IESG 
        review
Done    First version WG I-Ds for GMPLS source-controlled and 
        explicitly-routed Ethernet networks
Done    Submit Informational I-D for Analysis of inter-domain issues for 
        disjoint and protected paths for IESG review
Done    Submit Protocol solutions for MLN/MRN I-D for IESG review
Done    Submit Ethernet related drafts for IESG review
Done    Submit hierarchy bis for IESG review
Done    First version of WSON routing related Working Group drafts
Apr 2010    Submit TE MIB module IESG review
Apr 2010    Submit VCAT/LCAS with GMPLS for IESG review
Apr 2010    First versions of impairments related solutions Working
            Group drafts
Apr 2010    First version of G.709 enhancements framework Working Group
            drafts
Apr 2010    First version of Working Group draft providing Control
            Plane Framework for MPLS-TP
Apr 2010    First version of LMP Negotiation Working Group draft
May 2010    Submit Lambda labels draft for IESG review
May 2010    Submit WSON framework draft for IESG review
May 2010    Submit WSON impairment framework draft for IESG review
May 2010    Submit OAM configuration framework for IESG review
May 2010    First version of OAM configuration solutions Working
            Group drafts
Aug 2010    First version of G.709 enhancements solutions Working
            Group drafts
Aug 2010    First version of LMP for  G.709 enhancements Working
            Group drafts
Sep 2010    First version of Working Group draft defining RSVP-TE
            extensions for MPLS-TP
Dec 2010    Submit WSON routing related for IESG review
Dec 2010    Submit impairments related solutions for IESG review
Dec 2010    Submit G.709 enhancements framework for IESG review
Dec 2010    Submit Control Plane Framework for MPLS-TP for IESG review
Mar 2011    Submit RSVP-TE extensions for MPLS-TP for IESG review
Apr 2011    Submit G.709 enhancements solutions for IESG review
Apr 2011    Submit LMP Negotiation for IESG review
Apr 2011    Submit last OAM configuration solutions for IESG review
Aug 2011    Submit LMP for G.709 enhancements for IESG review
Nov 2011    Recharter or close Working Group

From fu.xihua@zte.com.cn  Wed Mar 17 18:54:57 2010
Return-Path: <fu.xihua@zte.com.cn>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8B243A69ED; Wed, 17 Mar 2010 18:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.708
X-Spam-Level: 
X-Spam-Status: No, score=-100.708 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G2gP8K6s3Det; Wed, 17 Mar 2010 18:54:57 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 491533A689A; Wed, 17 Mar 2010 18:54:55 -0700 (PDT)
Received: from [10.30.17.99] by mx6.zte.com.cn with surfront esmtp id 128641914610606; Thu, 18 Mar 2010 09:54:06 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.15] with StormMail ESMTP id 64572.1914610606; Thu, 18 Mar 2010 09:55:01 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse1.zte.com.cn with ESMTP id o2I1swa3069338; Thu, 18 Mar 2010 09:54:58 +0800 (CST) (envelope-from fu.xihua@zte.com.cn)
To: ccamp@ietf.org, pce@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF483EA1F0.DECBCB8A-ON482576EA.000795EE-482576EA.000A8456@zte.com.cn>
From: fu.xihua@zte.com.cn
Date: Thu, 18 Mar 2010 09:56:57 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-03-18 09:54:56, Serialize complete at 2010-03-18 09:54:56
Content-Type: multipart/alternative; boundary="=_alternative 000A8451482576EA_="
X-MAIL: mse1.zte.com.cn o2I1swa3069338
Subject: [CCAMP] [PCE] and discussion on Explicit Control of Region Boundary
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Mar 2010 01:54:57 -0000

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

Hi All,

The topic of Explicit Control of Region Boundary has been discussed in the 
76th meeting. Following is the presentation in CCAMP and PCE.
http://www.ietf.org/proceedings/76/slides/ccamp-28/ccamp-28.htm
http://www.ietf.org/proceedings/76/slides/pce-10/pce-10.htm

For the upcoming 77th meeting, the original draft has been split into the 
following three drafts.
1. A framework for Explicit Control of Region Boundary in PCE: 
http://tools.ietf.org/html/draft-fuxh-pce-boundary-explicit-control-framework-01

2. PCEP extension for Explicit Control of Region Boundary in PCE: 
http://tools.ietf.org/html/draft-fuxh-pce-boundary-explicit-control-pcep-ext-00
3. RSVP-TE extension for Explicit Control of Region Boundary in CCAMP: 
http://tools.ietf.org/html/draft-fuxh-ccamp-boundary-explicit-control-ext-00
If you have any comments, please don't hesitate to tell us.

Xihua Fu
ZTE Corporation
--=_alternative 000A8451482576EA_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3 face="sans-serif">Hi All,</font>
<br>
<br><font size=3 face="sans-serif">The topic of Explicit Control of Region
Boundary has been discussed in the 76th meeting. Following is the presentation
in CCAMP and PCE.</font>
<br><font size=3 color=blue face="sans-serif"><u>http://www.ietf.org/proceedings/76/slides/ccamp-28/ccamp-28.htm</u></font>
<br><font size=3 color=blue face="sans-serif"><u>http://www.ietf.org/proceedings/76/slides/pce-10/pce-10.htm</u></font>
<br>
<br><font size=3 face="sans-serif">For the upcoming 77th meeting, the original
draft has been split into the following three drafts.</font>
<br><font size=3 face="sans-serif">1. A framework for Explicit Control
of Region Boundary in PCE: </font><font size=3 color=blue face="sans-serif"><u>http://tools.ietf.org/html/draft-fuxh-pce-boundary-explicit-control-framework-01</u></font><font size=3 face="sans-serif"><br>
2. PCEP extension for Explicit Control of Region Boundary in PCE: </font><font size=3 color=blue face="sans-serif"><u>http://tools.ietf.org/html/draft-fuxh-pce-boundary-explicit-control-pcep-ext-00</u></font>
<br><font size=3 face="sans-serif">3. RSVP-TE extension for Explicit Control
of Region Boundary in CCAMP: </font><font size=3 color=blue face="sans-serif"><u>http://tools.ietf.org/html/draft-fuxh-ccamp-boundary-explicit-control-ext-00</u></font>
<br><font size=3 face="sans-serif">If you have any comments, please don't
hesitate to tell us.</font>
<br>
<br><font size=3 face="sans-serif">Xihua Fu</font>
<br><font size=3 face="sans-serif">ZTE Corporation</font>
--=_alternative 000A8451482576EA_=--


From Lyong@Ciena.com  Thu Mar 18 09:48:02 2010
Return-Path: <Lyong@Ciena.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B02733A6909 for <ccamp@core3.amsl.com>; Thu, 18 Mar 2010 09:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 EKu5L2vhhH0b for <ccamp@core3.amsl.com>; Thu, 18 Mar 2010 09:47:56 -0700 (PDT)
Received: from ripley.ciena.com (ripley.ciena.com [63.118.34.24]) by core3.amsl.com (Postfix) with ESMTP id D4C3F3A6911 for <ccamp@ietf.org>; Thu, 18 Mar 2010 09:47:54 -0700 (PDT)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 Mar 2010 12:48:00 -0400
Content-Type: multipart/related; boundary="----=_NextPart_000_4303_01CAC699.3FE775F0"
Message-ID: <0AFD1B67B949784DA087CDA9F0DD4AD901720EA9@mdmxm03.ciena.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OIF draft on ason routing
thread-index: AcrGusQl3TjJiBdTRLiKE9Pb3II7JA==
From: "Ong, Lyndon" <Lyong@Ciena.com>
Importance: normal
Priority: normal
To: <ccamp@ietf.org>
Cc: Thomas Walsh <twalsh@juniper.net>, Acee Lindem <acee.lindem@ericsson.com>, Ross Callon <rcallon@juniper.net>, "Malis, Andrew G. \(Andy\)" <andrew.g.malis@verizon.com>
Subject: [CCAMP] OIF draft on ason routing
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Mar 2010 16:48:02 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_4303_01CAC699.3FE775F0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CAC6BA.C6AF6004"


------_=_NextPart_001_01CAC6BA.C6AF6004
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Folks,
=20
I wanted to give people a quick introductory email on the OIF-sponsored
draft on ason routing (draft-ong -gmpls-ason-routing-exper-01.txt) with
some background:
=20
1.      The OIF recognizes that the IETF is the owner of standards for
GMPLS protocols, including especially OSPF.  It is not in OIF's scope to
define standards.  In fact, OIF is currently on a track to adopt a
subset of the OSPF routing extensions defined by IETF CCAMP in the
forthcoming Experimental RFC 5787 (aka
draft-ietf-ccamp-gmpls-ason-routing-ospf-09.txt, as the RFC has not yet
been published).
=20
2.      That being said, we think there is a great opportunity for
synergy here if the IETF would consider adopting the formats defined in
the OIF draft as a testing-based update to the work in
draft-ietf-ccamp-gmpls-ason-routing-ospf-09.txt, as that draft suffers
from lack of implementation and testing (thus the Experimental status),
while the formats defined in the OIF draft have at least 8
implementations and the benefit of about 7 years of Interop testing.  We
believe this would accelerate the adoption and deployment of standards
for ASON routing using OSPF, and also save a good deal of effort and
resources on the part of OIF members to re-implement and re-test ASON
routing extensions. Also, given the long experience with running code,
it would be justified to move this work from Experimental status to
Standards Track.

3.      As explained in draft-ong -gmpls-ason-routing-exper-01.txt, we
think that the format modifications involved are quite small in the case
of the Local/Remote TE Router_IDs and the advertisement of local Address
Prefixes, basically in the one case the use of 2 vs. 1 combined sub-TLVs
and in the other case the use of address length rather than network mask
for the prefixing.  The issue of the ISCD for SONET/SDH is trickier, as
an alternative method is already defined in RFCs 4202 and 4203, however
the draft identifies concerns with the amount of overhead required using
RFCs 4202/3 and advertising multiple ISCDs for a fairly typical
SONET/SDH link of OC192 rate (which requires 5 ISCD sub-TLVs to be
advertised) and requests consideration of a supplementary sub-TLV that
would avoid needing to advertise multiple ISCDs.

4.      It has been suggested that OIF deliberately deviated from the
IETF work on ASON routing.  This is not the case.  Work on formats used
in OIF experimentation on ASON routing dates back to 11/2002, prior to
IETF CCAMP activities on ASON routing extensions, which were initially
submitted in June 2006.   =20

5.      One might ask why OIF did not submit input previously on this
issue.  I accept some of the fault for this, as I believed it was
implied to me that OIF input on formats was not especially welcome, and
that the fastest way to get standard OSPF extensions defined was to
leave the process entirely within IETF.   It should be noted that OIF
participants contributed to the work on ASON Routing requirements and
evaluation in RFCs 4258 and 4652 that preceded the work on OSPF
extensions.

We would welcome any comments on the draft, now or during its
presentation on Tuesday at CCAMP and are hopeful that this will be
received as constructive input.

Thanks,
Lyndon

=20





------_=_NextPart_001_01CAC6BA.C6AF6004
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word"><head><META =
content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type">
<meta content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<meta content=3D"Microsoft Word 12 (filtered medium)" name=3DGenerator>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:701856832;
	mso-list-type:hybrid;
	mso-list-template-ids:-1598227828 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head><BODY>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi
Folks,<br>
&nbsp;<br>
I wanted to give people a quick introductory email on the OIF-sponsored =
draft
on ason routing (draft-ong -gmpls-ason-routing-exper-01.txt) with some =
background:<br>
&nbsp;<br>
1. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The OIF recognizes that the IETF is the =
owner
of standards for GMPLS protocols, including especially OSPF. &nbsp;It is =
not in
OIF&#8217;s scope to define standards. &nbsp;In fact, OIF is currently =
on a
track to adopt a subset of the OSPF routing extensions defined by IETF =
CCAMP in
the forthcoming Experimental RFC 5787 (aka</span><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>
draft-ietf-ccamp-gmpls-ason-routing-ospf-09.txt, as the RFC has not yet =
been
published)</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<br>
&nbsp;<br>
2. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;That being said, we think there is a =
great
opportunity for synergy here if the IETF would consider adopting the =
formats
defined in the OIF draft as a testing-based update to the work in =
</span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>draft-ietf-c=
camp-gmpls-ason-routing-ospf-09.txt</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>, as that =
draft
suffers from lack of implementation and testing (thus the Experimental =
status),
while the formats defined in the OIF draft have at least 8 =
implementations and
the benefit of about 7 years of Interop testing. &nbsp;We believe this =
would
accelerate the adoption and deployment of standards for ASON routing =
using
OSPF, and also save a good deal of effort and resources on the part of =
OIF
members to re-implement and re-test ASON routing extensions. Also, given =
the
long experience with running code, it would be justified to move this =
work from
Experimental status to Standards Track.<br>
<br>
3. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;As explained in draft-ong
-gmpls-ason-routing-exper-01.txt, we think that the format modifications
involved are quite small in the case of the Local/Remote TE Router_IDs =
and the
advertisement of local Address Prefixes, basically in the one case the =
use of 2
vs. 1 combined sub-TLVs and in the other case the use of address length =
rather
than network mask for the prefixing. &nbsp;The issue of the ISCD for =
SONET/SDH
is trickier, as an alternative method is already defined in RFCs 4202 =
and 4203,
however the draft identifies concerns with the amount of overhead =
required
using RFCs 4202/3 and advertising multiple ISCDs for a fairly typical =
SONET/SDH
link of OC192 rate (which requires 5 ISCD sub-TLVs to be advertised) and
requests consideration of a supplementary sub-TLV that would avoid =
needing to
advertise multiple ISCDs.<br>
</span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>4.
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;It has been suggested that OIF =
deliberately
deviated from the IETF work on ASON routing. &nbsp;This is not the case.
&nbsp;Work on formats used in OIF experimentation on ASON routing dates =
back to
11/2002, prior to IETF CCAMP activities on ASON routing extensions, =
which were
initially submitted in June 2006. &nbsp;&nbsp;&nbsp;<br>
</span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>5.
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;One might ask why OIF did not submit input =
previously
on this issue. &nbsp;I accept some of the fault for this, as I believed =
it was
implied to me that OIF input on formats was not especially welcome, and =
that
the fastest way to get standard OSPF extensions defined was to leave the
process entirely within IETF. &nbsp; It should be noted that OIF =
participants contributed
to the work on ASON Routing requirements and evaluation in RFCs 4258 and =
4652
that preceded the work on OSPF extensions.<br>
</span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>We
would welcome any comments on the draft, now or during its presentation =
on
Tuesday at CCAMP and are hopeful that this will be received as =
constructive
input.<br>
<br>
Thanks,<br>
Lyndon</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p>

</div>

<BR><IMG ALIGN=3D"baseline" ALT BORDER=3D"0" HSPACE=3D"0" =
SRC=3D"cid:imageb69a0b.gif@91de8fa8.a4a44783"><BR><BR></BODY></HTML>

------_=_NextPart_001_01CAC6BA.C6AF6004--

------=_NextPart_000_4303_01CAC699.3FE775F0
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-ID: <imageb69a0b.gif@91de8fa8.a4a44783>

R0lGODlh3AAeAPcAANINQfb29uiCnuqVq9AALPXb4vLBzCopFcsAGbOyq+dmc8nJxeJig8gAB/3/
//TS2/r2+Pr5+eydsuZ8mauqo++0w2JiVBgXAuVyke6qvGtqXdMSRru6s/z///np7dEIPtrZ1vG9
y4yLgfru8dXU0kxKOtEANfz5+kNCMdMQRNLRzuFVeu2htFpaTPfh6NAAMdw6ZfLE0fjl6umNps8A
LeTk4tQUSVNSQzw7Kfr19u6luc4AKfTO2fC1xPGqspyblIWEeuHh3s0AJdoyWc7OytosWd5BbPLx
8ZaVjHZ1aXt6bvn39+FZfunq6dglU6alnuHh4MXGwds0YYKBdvz8/NIFPDUzIc8AMPGzus0AIOh+
mtAAA9IKQAMCAMLCvfTK1d5JcuFSdNUEF9orVeno5umFoPTM1pSUitgeUOqKpPry9u7u7L6+uPnx
8vXW36KhmXJxZSMiDn18cd7d2ubm5N9SedUNQt/f3Od5l/fe5Pfi5uNmiMTEvuNqidEAOO+jqvz+
/JKRiNUbR+JdgdMRRe3s65iXjtIUNaCfl9IEOueAnOVWZeRpivff5dcbTdckTdjX0/PI0+VvjdMO
Q7e1sNYYTNIAOJGQhtrb2I+OhdQKQGZlWOzr6nh3a9YSQuqKo9ECOmBfUKWjneRpjP39/szMxjk5
J9ICOPT08/Dw7/Xz9eRwj4mJfz8+LcDAutMSRdMQRjIxH9MQQW5tX4iGe9DPy2loW0JAMP36/OBO
dOqPp6ion6Sim/PM18jHwt09Z5mZj15dTtMUR9ICO9ACOVhXSNMEPEdFNh4dCcwAHy8uGzc2JcTD
vvz19//9/4B/dNzb2ZSTidIBO/f39rCvqdYYQ1BPP++xwPv7/NQANueMo8/RzdfY1Ofo5Orn50lI
OdEDO+yYr/C4xlBOP7i3sfz9/FdZSFpXR/Cuwf78/dAEMdIHNhAOAOLk4P7//uPj4NggUfDv7tkn
V+qRqO6dpfv7+pOUi8jIxOZ3lN9IbqOjm+6uv8vKxudwhKmooP///yH5BAAAAAAALAAAAADcAB4A
AAj/AP8JHEiw4MAObUgZXMiwocOHECNKnEixosWLGDO6YSRlRYyMIEOKHEmypEmLjdAkI5CsiriT
MGPKnEkzpDtFLTcQQpDPQc2fQIMKJemuDoFXr2zsKAJhqNOnUKP+u4mgig1YCHL5lMq1q9eRMuQh
GAvg49ezaNM+dIEnzJ5IauPKjeqg7taK7to84MHDxV2I7upCtOvA3dzDQiOEmMGI0Z49M67JmCpj
RLMRMk4sjMHEBpdJmiaBMUDQRYwvZr4Y8PDPATp8DBjNK1DQHSAZPebh2zOKkRYWehALj+lAghQT
O2hcoUFjBwJJ/x7Iq1QEnqMKBTvgeyHkhZ/vJrqH/xs4IZudFKcIXHO3gkByAkI0jReYLlw+eC+S
X1nunhCepsMFGBI2gwixAzgATDJJCilMggAT//QCH3JCsECQA0xkYcIkGwhDyAYbyJKFHW4IhAEB
JoDywgur1CGEHwpOAkByGQjkQiUImPBBggvKyAUNCPyihoBEWtQBEzl+COIkXHCRQjJ9RGeHHxt8
YEmNArmDRxangEgIOMpxUaUQihimhSWEpLmBDcN8kIIwOoEohDxDuiCPCQBwUUUibU4C5wbEIDBK
kYRKJEEWoAjzygaTmHDFii80sIKUVFqJ5T8GmPDCoim8oMkKYFQxCSHJ1GEmmmoCoOkVfnxIiDCg
mP8Qwj8u2JAMcx94AksiL4j5KgGy0FbosAudMIQQHm7wIzwT6KDDDGNA9wAAlV6ZJRNCpKATDWjM
+g8DeJZ6apqEpGCCI3sw4sgLrnJxhS7/5FHEL5/sE8MDDxgArpgbVPGChcQGPFAMO8Dy4SQvMMHa
QJf9w8OUVVqyj0AyVPMCiCac8pJA87C6QxnjEvKKH5WQ9k8kaJiQ5iQ0aPFPOY0wNAgNIAJAgACG
CRzwADt4SMgVUkTAkBkQc2ECwNeYAA6jNICx1QnH0eCJsGeKDAANqxA0wQ5isqzIQA7EUAYDKzDw
SS8CvMDhjDjrHPAeJix69QQNEU3lJASUIVAaBHD/IQwAV2Q9FSMvIKe3QFUrS8AABM3DNdNf/xMD
DCvusIOB0mzA4AY2t+32sODK/QK8Q0/5yiRXHC7ADgCcvsOk/2BQuBAr3JU4FwTMkPM/aQjRNQ0C
/POFMS8m+AIN8F2RbOe7w9T85yetcvHpNEBXuh+np87xFb6+4IQ4DBDwQhYwAIg4morrPlDvXef+
jxFZaEuIJVIoopsUxmjLPEYj/IFFOQypxSZqwRV+2OIeJinFEwJQEF50ggxe4MBEJICsD5nABl8o
3SnStAPrheAUidBJCmDxgUfRIBdtKMjtcrc79nGOBhIYgSbiRgg/yGNh/9DBDtZ2s+dJpB6L2MIW
/+hBkHiIoBT/oEYXKCESciDBhxHxRxcQYZJNsIMEBQnGBXzxjVYohCBP8MdCeNA3nRDiBfDYh2am
wpd/mEETrdqACYqQg38AoghXUFMKuGAMG2iDIF8AmQDQhzv17c13jLoCC3phDGmU6wV7IMge8si5
Hl4kD2LYQgMWcRdqsCMJ/2ADMngBgiYIZAnMIGARydAEftBBIJxgwxz+sYRxIKMUR4AGLv4BhRr8
IwCYEEgp+CC0I9BhDZj4ATIS8A9MQAMbA1lCFBaQDlV0owlReMdAVOCFIwxkAQtI4hSgyQ9XLOEf
cDjAO/xhiKkwgx//IMMylgEJZxSkHDDIApweaf+CX/ShDwxQx6T0YAOVpckEdQjBPqSAPTPWEAYe
6IAHQqAFddDgBGkgJAvXh0jUseABxhjGK+ZXBBe0RgJ+WFolPVcRB/RjC2LwwUDucIw4KMMebDhA
Kw5wA1TEwwKtwEE7ByKKW5TgANaYBhGsgYJvsEEfB4hDKEQQCwr8owQl+McZSgCCKcQBGcFYQwJu
cYxxKOEWXkhAHH6QsxrYYhlW4AMFjvGNOJhiG/9AwjFuYQFUOGMWF0DGG5CggWkYogStCAUqgKCM
d0QDCAFIZwmoAYSoctUgGcgCDWwQpw/QIAvJEEIDGPCPDsBgBx96BQAKlz/NyY9BhBCEEx6RiCv/
NOAQvDuF3Da6N64Jg2USyIEmXuAhczmBEXX4zgZ2GzyMUCESZiDINAJxAA2AwAsXSIISLiAKVrBD
CSjogisGcokuaCAJyDDEJuLAijgcwBehiEUCIHGAYnDgqxz4hgUygYwpKFMOP+jCDdiAiFaYIxab
WMNAdtEFFDxjGmfIrj6kSok4FGMWXWDFJdgxBWDUwhZxwIYontEJdlCDFVaYQwvGkQB2WEEENSDC
LW5BgVQYxB0TQMAO3iSMHtvABpUQAmn/EY4ssKvHwvhAFT6Qnx184FV/MwENXnAFEzRgCA4oAyF3
YMh/fMLJL0zDP+qAgA/0+IzweZHmKqm3POgA/4cgaccy/8GHC2jTFEAIxQFYkQQckGMg9rhADZqA
Alsc4xhIaMEN/kGLWwgECQfAgQVacAtTEGEWyxBIKMYRjVjMkhmxCCw0CNKNJBSjGFFAAg4K8Y9O
WEEDB7AFEIoBBMQORAmtuAMQkiCCZeiDFqaAwixCEYBnWOMcEmzBJhriDgGoYyVKA0UiTmHlMBjG
AYMI7aM0RQMhVCEXv8iCEFhVhSr4gTvrGMQD/iGJZOwAPg1orkAm0IBkXEG0GPiHHpygYxNUARQ7
yII88vlu0eLhH/gwAekmEgH//UUF7DgGCJR4D1RcgBW0YIcInpEJBgpEDl24QxDikIT1vqETT//4
hwa6YIgIkAEZXUhAILqgjH8Ygh1AQAIy5CACdnDjH0/gcAmUgUWBHOEHnehCC0SgDCVQIA4WuG8o
gPEMMoigC0D4gQosYApDdCEJwGAHEpSADBLcwNG8wHAr/nEDZOiDEw2JxCAEkQ0/WMISeBrDpTow
DynIQhMAEMQvJhADdzRDF373gwnMU4RVwEUg4ZCCEYwAgyLoYHc6kMcvjPCLIkjARgwQBLUtUQ0m
NCIE86K85XNohI1J5AQKEOIfdneETXTBFuRQxj28YQUKTCMUprBCIAgSCGVAAwQoeMIdvoGDW0hw
F4Hlwz82cQBO0LcT/4iABpBxgWAEwB/KwCv/NYjuiu8OpBTHwMEBKPEDK7QCGcpQgc1NkdhzWoAd
7EDEFG6ggmJ8QwPLsAuZcAvcAAebQALWEAuxQEU3Fwfyx2y44Sw6cA1uoAbPowYF8AV9YT4C0Qxu
UAEskAEPMAIFcQJtAAFLkAMjsEsDcQIjkAMQAAEjsEatIQMGwAIVkAeG4Q4jgIIqqBmAMAJQ1BCY
JEScRBCqsAAgQArtoBBBMA2/NE02NhBHEARTUQNQyAleoAJC4w4g4Auo8A/GJBA14HHlUAv8AIXT
AAVU8A/TYIX/cAd38EXTQAJeMEuBEAscAA1w+A8kwAe+9A9UsABEMA2o0A1ieA930AT1oAqvL7QG
hUAF3OAKsySIKsAPQgM9J+EAsRdTOkMLB0AEmjgsJ4AFITCERAIJlGBKThEQADs=

------=_NextPart_000_4303_01CAC699.3FE775F0--

From wwwrun@rfc-editor.org  Thu Mar 18 19:19:46 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA9743A6CD7; Thu, 18 Mar 2010 19:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.364
X-Spam-Level: 
X-Spam-Status: No, score=-1.364 tagged_above=-999 required=5 tests=[AWL=-0.494, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Puq+0YzyhCl; Thu, 18 Mar 2010 19:19:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id AB8CB3A6CC2; Thu, 18 Mar 2010 19:19:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5305CE0783; Thu, 18 Mar 2010 19:19:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100319021914.5305CE0783@rfc-editor.org>
Date: Thu, 18 Mar 2010 19:19:14 -0700 (PDT)
Cc: ccamp@ietf.org, rfc-editor@rfc-editor.org
Subject: [CCAMP] RFC 5814 on Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS Networks
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2010 02:19:47 -0000

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

        
        RFC 5814

        Title:      Label Switched Path (LSP) Dynamic 
                    Provisioning Performance Metrics in Generalized MPLS 
                    Networks 
        Author:     W. Sun, Ed.,
                    G. Zhang, Ed.
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    sunwq@mit.edu, 
                    zhangguoying@mail.ritt.com.cn
        Pages:      44
        Characters: 93386
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-lsp-dppm-11.txt

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

Generalized Multi-Protocol Label Switching (GMPLS) is one of the most
promising candidate technologies for a future data transmission
network.  GMPLS has been developed to control and operate different
kinds of network elements, such as conventional routers, switches,
Dense Wavelength Division Multiplexing (DWDM) systems, Add-Drop
Multiplexers (ADMs), photonic cross-connects (PXCs), optical cross-
connects (OXCs), etc.  These physically diverse devices differ
drastically from one another in dynamic provisioning ability.  At the
same time, the need for dynamically provisioned connections is
increasing because optical networks are being deployed in metro
areas.  As different applications have varied requirements in the
provisioning performance of optical networks, it is imperative to
define standardized metrics and procedures such that the performance
of networks and application needs can be mapped to each other.

This document provides a series of performance metrics to evaluate
the dynamic Label Switched Path (LSP) provisioning performance in
GMPLS networks, specifically the dynamic LSP setup/release
performance.  These metrics can be used to characterize the features
of GMPLS networks in LSP dynamic provisioning.  [STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

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

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

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


The RFC Editor Team
Association Management Solutions, LLC



From Lyong@Ciena.com  Thu Mar 18 19:24:50 2010
Return-Path: <Lyong@Ciena.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 082303A6CC9 for <ccamp@core3.amsl.com>; Thu, 18 Mar 2010 19:24:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.039
X-Spam-Level: *
X-Spam-Status: No, score=1.039 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, 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 oM9m7wRSuP+C for <ccamp@core3.amsl.com>; Thu, 18 Mar 2010 19:24:49 -0700 (PDT)
Received: from ripley.ciena.com (ripley.ciena.com [63.118.34.24]) by core3.amsl.com (Postfix) with ESMTP id C6ED23A6C95 for <ccamp@ietf.org>; Thu, 18 Mar 2010 19:24:48 -0700 (PDT)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 Mar 2010 22:24:59 -0400
Content-Type: multipart/related; boundary="----=_NextPart_000_811D_01CAC6E9.D9B9C2F0"
Message-ID: <0AFD1B67B949784DA087CDA9F0DD4AD901720FE1@mdmxm03.ciena.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OIF draft on lsp hierarchy and control plane adjacency
thread-index: AcrHC1+lIWW/s10WR1m4MxFBPb+uPw==
Importance: normal
From: "Ong, Lyndon" <Lyong@Ciena.com>
Priority: normal
To: <ccamp@ietf.org>
Subject: [CCAMP] OIF draft on lsp hierarchy and control plane adjacency
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2010 02:24:50 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_811D_01CAC6E9.D9B9C2F0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CAC70B.6086422F"


------_=_NextPart_001_01CAC70B.6086422F
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Folks,

=20

This is a quick email on the OIF-sponsored draft on lsp hierarchy and =
control plane adjacency configuration =
(draft-roch-ccamp-reqts-auto-adj-00.txt):

=20

This is submitted in the form of a problem statement, as suggested in =
the GMPLS change procedures of RFC 4929.  It identifies some additional =
issues with establishment of control plane adjacencies in the use of LSP =
hierarchy with ASON networks that we believe may require protocol =
extensions.

=20

The issues basically are:

=20

-          Identification of the client layer in LSP hierarchy, if =
flexible adaptation to multiple client layers is supported

-          Handling of separate control plane instances at different =
layers

o   Automatic configuration of control plane adjacency in the client =
layer, with separation between

=C2=A7   the identification of the resource in the client layer,=20

=C2=A7  the signaling controller in the client layer, and the SCN =
address to reach that controller

=C2=A7  the routing controller in the client layer, and the SCN address =
to reach that controller

=20

We believe this is not currently supported in the LSP hierarchy work, =
but that protocol extensions to support this could be done using =
mechanisms defined on the LSP hierarchy-bis draft =
(draft-ietf-ccamp-lsp-hierarchy-bis-08.txt).

=20

We would welcome comments on the draft and look forward to a =
determination by CCAMP as to whether this is in scope or not and whether =
protocol extensions are considered necessary.

=20

Evelyne Roch

Lyndon Ong

=20





------_=_NextPart_001_01CAC70B.6086422F
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word"><head><META =
content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type">
<meta content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<meta content=3D"Microsoft Word 12 (filtered medium)" name=3DGenerator>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1783261765;
	mso-list-type:hybrid;
	mso-list-template-ids:-2029230616 745944258 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head><BODY>

<div class=3DSection1>

<p class=3DMsoNormal>Hi Folks,<o:p></o:p></p>

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

<p class=3DMsoNormal>This is a quick email on the OIF-sponsored draft on =
lsp
hierarchy and control plane adjacency configuration
(draft-roch-ccamp-reqts-auto-adj-00.txt):<o:p></o:p></p>

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

<p class=3DMsoNormal>This is submitted in the form of a problem =
statement, as
suggested in the GMPLS change procedures of RFC 4929.&nbsp; It =
identifies some
additional issues with establishment of control plane adjacencies in the =
use of
LSP hierarchy with ASON networks that we believe may require protocol
extensions.<o:p></o:p></p>

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

<p class=3DMsoNormal>The issues basically are:<o:p></o:p></p>

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

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'>-<span =
style=3D'font-size:
7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Identification of the client layer in LSP hierarchy, if flexible
adaptation to multiple client layers is supported<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in'>-<span =
style=3D'font-size:
7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Handling of separate control plane instances at different =
layers<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in'><span =
style=3D'font-family:"Courier New"'>o</span><span =
style=3D'font-size:7.0pt;
font-family:"Times New Roman","serif"'>&nbsp;&nbsp; </span>Automatic
configuration of control plane adjacency in the client layer, with =
separation
between<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in'><span =
style=3D'font-family:Wingdings'>=C2=A7</span><span =
style=3D'font-size:7.0pt;font-family:
"Times New Roman","serif"'>&nbsp; </span>&nbsp;the identification of the
resource in the client layer, <o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in'><span =
style=3D'font-family:Wingdings'>=C2=A7</span><span =
style=3D'font-size:7.0pt;font-family:
"Times New Roman","serif"'>&nbsp; </span>the signaling controller in the =
client
layer, and the SCN address to reach that controller<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in'><span =
style=3D'font-family:Wingdings'>=C2=A7</span><span =
style=3D'font-size:7.0pt;font-family:
"Times New Roman","serif"'>&nbsp; </span>the routing controller in the =
client
layer, and the SCN address to reach that controller<o:p></o:p></p>

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

<p class=3DMsoNormal>We believe this is not currently supported in the =
LSP
hierarchy work, but that protocol extensions to support this could be =
done using
mechanisms defined on the LSP hierarchy-bis draft =
(draft-ietf-ccamp-lsp-hierarchy-bis-08.txt).<o:p></o:p></p>

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

<p class=3DMsoNormal>We would welcome comments on the draft and look =
forward to a
determination by CCAMP as to whether this is in scope or not and whether
protocol extensions are considered necessary.<o:p></o:p></p>

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

<p class=3DMsoNormal>Evelyne Roch<o:p></o:p></p>

<p class=3DMsoNormal>Lyndon Ong<o:p></o:p></p>

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

</div>

<BR><IMG ALIGN=3D"baseline" ALT BORDER=3D"0" HSPACE=3D"0" =
SRC=3D"cid:imageb08ba2.gif@c3e18d53.8455415b"><BR><BR></BODY></HTML>

------_=_NextPart_001_01CAC70B.6086422F--

------=_NextPart_000_811D_01CAC6E9.D9B9C2F0
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-ID: <imageb08ba2.gif@c3e18d53.8455415b>

R0lGODlh3AAeAPcAANINQfb29uiCnuqVq9AALPXb4vLBzCopFcsAGbOyq+dmc8nJxeJig8gAB/3/
//TS2/r2+Pr5+eydsuZ8mauqo++0w2JiVBgXAuVyke6qvGtqXdMSRru6s/z///np7dEIPtrZ1vG9
y4yLgfru8dXU0kxKOtEANfz5+kNCMdMQRNLRzuFVeu2htFpaTPfh6NAAMdw6ZfLE0fjl6umNps8A
LeTk4tQUSVNSQzw7Kfr19u6luc4AKfTO2fC1xPGqspyblIWEeuHh3s0AJdoyWc7OytosWd5BbPLx
8ZaVjHZ1aXt6bvn39+FZfunq6dglU6alnuHh4MXGwds0YYKBdvz8/NIFPDUzIc8AMPGzus0AIOh+
mtAAA9IKQAMCAMLCvfTK1d5JcuFSdNUEF9orVeno5umFoPTM1pSUitgeUOqKpPry9u7u7L6+uPnx
8vXW36KhmXJxZSMiDn18cd7d2ubm5N9SedUNQt/f3Od5l/fe5Pfi5uNmiMTEvuNqidEAOO+jqvz+
/JKRiNUbR+JdgdMRRe3s65iXjtIUNaCfl9IEOueAnOVWZeRpivff5dcbTdckTdjX0/PI0+VvjdMO
Q7e1sNYYTNIAOJGQhtrb2I+OhdQKQGZlWOzr6nh3a9YSQuqKo9ECOmBfUKWjneRpjP39/szMxjk5
J9ICOPT08/Dw7/Xz9eRwj4mJfz8+LcDAutMSRdMQRjIxH9MQQW5tX4iGe9DPy2loW0JAMP36/OBO
dOqPp6ion6Sim/PM18jHwt09Z5mZj15dTtMUR9ICO9ACOVhXSNMEPEdFNh4dCcwAHy8uGzc2JcTD
vvz19//9/4B/dNzb2ZSTidIBO/f39rCvqdYYQ1BPP++xwPv7/NQANueMo8/RzdfY1Ofo5Orn50lI
OdEDO+yYr/C4xlBOP7i3sfz9/FdZSFpXR/Cuwf78/dAEMdIHNhAOAOLk4P7//uPj4NggUfDv7tkn
V+qRqO6dpfv7+pOUi8jIxOZ3lN9IbqOjm+6uv8vKxudwhKmooP///yH5BAAAAAAALAAAAADcAB4A
AAj/AP8JHEiw4MAObUgZXMiwocOHECNKnEixosWLGDO6YSRlRYyMIEOKHEmypEmLjdAkI5CsiriT
MGPKnEkzpDtFLTcQQpDPQc2fQIMKJemuDoFXr2zsKAJhqNOnUKP+u4mgig1YCHL5lMq1q9eRMuQh
GAvg49ezaNM+dIEnzJ5IauPKjeqg7taK7to84MHDxV2I7upCtOvA3dzDQiOEmMGI0Z49M67JmCpj
RLMRMk4sjMHEBpdJmiaBMUDQRYwvZr4Y8PDPATp8DBjNK1DQHSAZPebh2zOKkRYWehALj+lAghQT
O2hcoUFjBwJJ/x7Iq1QEnqMKBTvgeyHkhZ/vJrqH/xs4IZudFKcIXHO3gkByAkI0jReYLlw+eC+S
X1nunhCepsMFGBI2gwixAzgATDJJCilMggAT//QCH3JCsECQA0xkYcIkGwhDyAYbyJKFHW4IhAEB
JoDywgur1CGEHwpOAkByGQjkQiUImPBBggvKyAUNCPyihoBEWtQBEzl+COIkXHCRQjJ9RGeHHxt8
YEmNArmDRxangEgIOMpxUaUQihimhSWEpLmBDcN8kIIwOoEohDxDuiCPCQBwUUUibU4C5wbEIDBK
kYRKJEEWoAjzygaTmHDFii80sIKUVFqJ5T8GmPDCoim8oMkKYFQxCSHJ1GEmmmoCoOkVfnxIiDCg
mP8Qwj8u2JAMcx94AksiL4j5KgGy0FbosAudMIQQHm7wIzwT6KDDDGNA9wAAlV6ZJRNCpKATDWjM
+g8DeJZ6apqEpGCCI3sw4sgLrnJxhS7/5FHEL5/sE8MDDxgArpgbVPGChcQGPFAMO8Dy4SQvMMHa
QJf9w8OUVVqyj0AyVPMCiCac8pJA87C6QxnjEvKKH5WQ9k8kaJiQ5iQ0aPFPOY0wNAgNIAJAgACG
CRzwADt4SMgVUkTAkBkQc2ECwNeYAA6jNICx1QnH0eCJsGeKDAANqxA0wQ5isqzIQA7EUAYDKzDw
SS8CvMDhjDjrHPAeJix69QQNEU3lJASUIVAaBHD/IQwAV2Q9FSMvIKe3QFUrS8AABM3DNdNf/xMD
DCvusIOB0mzA4AY2t+32sODK/QK8Q0/5yiRXHC7ADgCcvsOk/2BQuBAr3JU4FwTMkPM/aQjRNQ0C
/POFMS8m+AIN8F2RbOe7w9T85yetcvHpNEBXuh+np87xFb6+4IQ4DBDwQhYwAIg4morrPlDvXef+
jxFZaEuIJVIoopsUxmjLPEYj/IFFOQypxSZqwRV+2OIeJinFEwJQEF50ggxe4MBEJICsD5nABl8o
3SnStAPrheAUidBJCmDxgUfRIBdtKMjtcrc79nGOBhIYgSbiRgg/yGNh/9DBDtZ2s+dJpB6L2MIW
/+hBkHiIoBT/oEYXKCESciDBhxHxRxcQYZJNsIMEBQnGBXzxjVYohCBP8MdCeNA3nRDiBfDYh2am
wpd/mEETrdqACYqQg38AoghXUFMKuGAMG2iDIF8AmQDQhzv17c13jLoCC3phDGmU6wV7IMge8si5
Hl4kD2LYQgMWcRdqsCMJ/2ADMngBgiYIZAnMIGARydAEftBBIJxgwxz+sYRxIKMUR4AGLv4BhRr8
IwCYEEgp+CC0I9BhDZj4ATIS8A9MQAMbA1lCFBaQDlV0owlReMdAVOCFIwxkAQtI4hSgyQ9XLOEf
cDjAO/xhiKkwgx//IMMylgEJZxSkHDDIApweaf+CX/ShDwxQx6T0YAOVpckEdQjBPqSAPTPWEAYe
6IAHQqAFddDgBGkgJAvXh0jUseABxhjGK+ZXBBe0RgJ+WFolPVcRB/RjC2LwwUDucIw4KMMebDhA
Kw5wA1TEwwKtwEE7ByKKW5TgANaYBhGsgYJvsEEfB4hDKEQQCwr8owQl+McZSgCCKcQBGcFYQwJu
cYxxKOEWXkhAHH6QsxrYYhlW4AMFjvGNOJhiG/9AwjFuYQFUOGMWF0DGG5CggWkYogStCAUqgKCM
d0QDCAFIZwmoAYSoctUgGcgCDWwQpw/QIAvJEEIDGPCPDsBgBx96BQAKlz/NyY9BhBCEEx6RiCv/
NOAQvDuF3Da6N64Jg2USyIEmXuAhczmBEXX4zgZ2GzyMUCESZiDINAJxAA2AwAsXSIISLiAKVrBD
CSjogisGcokuaCAJyDDEJuLAijgcwBehiEUCIHGAYnDgqxz4hgUygYwpKFMOP+jCDdiAiFaYIxab
WMNAdtEFFDxjGmfIrj6kSok4FGMWXWDFJdgxBWDUwhZxwIYontEJdlCDFVaYQwvGkQB2WEEENSDC
LW5BgVQYxB0TQMAO3iSMHtvABpUQAmn/EY4ssKvHwvhAFT6Qnx184FV/MwENXnAFEzRgCA4oAyF3
YMh/fMLJL0zDP+qAgA/0+IzweZHmKqm3POgA/4cgaccy/8GHC2jTFEAIxQFYkQQckGMg9rhADZqA
Alsc4xhIaMEN/kGLWwgECQfAgQVacAtTEGEWyxBIKMYRjVjMkhmxCCw0CNKNJBSjGFFAAg4K8Y9O
WEEDB7AFEIoBBMQORAmtuAMQkiCCZeiDFqaAwixCEYBnWOMcEmzBJhriDgGoYyVKA0UiTmHlMBjG
AYMI7aM0RQMhVCEXv8iCEFhVhSr4gTvrGMQD/iGJZOwAPg1orkAm0IBkXEG0GPiHHpygYxNUARQ7
yII88vlu0eLhH/gwAekmEgH//UUF7DgGCJR4D1RcgBW0YIcInpEJBgpEDl24QxDikIT1vqETT//4
hwa6YIgIkAEZXUhAILqgjH8Ygh1AQAIy5CACdnDjH0/gcAmUgUWBHOEHnehCC0SgDCVQIA4WuG8o
gPEMMoigC0D4gQosYApDdCEJwGAHEpSADBLcwNG8wHAr/nEDZOiDEw2JxCAEkQ0/WMISeBrDpTow
DynIQhMAEMQvJhADdzRDF373gwnMU4RVwEUg4ZCCEYwAgyLoYHc6kMcvjPCLIkjARgwQBLUtUQ0m
NCIE86K85XNohI1J5AQKEOIfdneETXTBFuRQxj28YQUKTCMUprBCIAgSCGVAAwQoeMIdvoGDW0hw
F4Hlwz82cQBO0LcT/4iABpBxgWAEwB/KwCv/NYjuiu8OpBTHwMEBKPEDK7QCGcpQgc1NkdhzWoAd
7EDEFG6ggmJ8QwPLsAuZcAvcAAebQALWEAuxQEU3Fwfyx2y44Sw6cA1uoAbPowYF8AV9YT4C0Qxu
UAEskAEPMAIFcQJtAAFLkAMjsEsDcQIjkAMQAAEjsEatIQMGwAIVkAeG4Q4jgIIqqBmAMAJQ1BCY
JEScRBCqsAAgQArtoBBBMA2/NE02NhBHEARTUQNQyAleoAJC4w4g4Auo8A/GJBA14HHlUAv8AIXT
AAVU8A/TYIX/cAd38EXTQAJeMEuBEAscAA1w+A8kwAe+9A9UsABEMA2o0A1ieA930AT1oAqvL7QG
hUAF3OAKsySIKsAPQgM9J+EAsRdTOkMLB0AEmjgsJ4AFITCERAIJlGBKThEQADs=

------=_NextPart_000_811D_01CAC6E9.D9B9C2F0--

From db3546@att.com  Fri Mar 19 12:47:11 2010
Return-Path: <db3546@att.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 022173A6837 for <ccamp@core3.amsl.com>; Fri, 19 Mar 2010 12:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.034
X-Spam-Level: 
X-Spam-Status: No, score=-106.034 tagged_above=-999 required=5 tests=[AWL=-0.565, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 PAgt81O5YBMu for <ccamp@core3.amsl.com>; Fri, 19 Mar 2010 12:47:10 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id 162F83A63EB for <ccamp@ietf.org>; Fri, 19 Mar 2010 12:47:09 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: db3546@att.com
X-Msg-Ref: server-12.tower-129.messagelabs.com!1269028041!8548517!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 21973 invoked from network); 19 Mar 2010 19:47:22 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-12.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Mar 2010 19:47:22 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o2JJlAoh031230 for <ccamp@ietf.org>; Fri, 19 Mar 2010 15:47:10 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o2JJl9PV031221 for <ccamp@ietf.org>; Fri, 19 Mar 2010 15:47:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Mar 2010 15:47:19 -0400
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA060585B6@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Two new OIF Communications
Thread-Index: AcrHnPwmu99EIR3OSdWaSW6dX3OTng==
From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
To: "CCAMP" <ccamp@ietf.org>
Subject: [CCAMP] Two new OIF Communications
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2010 19:47:11 -0000

CCAMP,

We have two new OIF Communications:

http://trac.tools.ietf.org/wg/ccamp/trac/ticket/25

http://trac.tools.ietf.org/wg/ccamp/trac/ticket/26


From lberger@labn.net  Fri Mar 19 13:17:02 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CB243A67D2 for <ccamp@core3.amsl.com>; Fri, 19 Mar 2010 13:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level: 
X-Spam-Status: No, score=-0.333 tagged_above=-999 required=5 tests=[AWL=-1.798, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HS5oNm9pZKLR for <ccamp@core3.amsl.com>; Fri, 19 Mar 2010 13:17:00 -0700 (PDT)
Received: from outbound-mail-01.bluehost.com (outbound-mail-01.bluehost.com [69.89.21.11]) by core3.amsl.com (Postfix) with SMTP id E68273A677D for <ccamp@ietf.org>; Fri, 19 Mar 2010 13:16:59 -0700 (PDT)
Received: (qmail 14370 invoked by uid 0); 19 Mar 2010 20:17:13 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy1.bluehost.com with SMTP; 19 Mar 2010 20:17:13 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=z346dL4/qCXGrSAc7WATnMtp5sj58ZdQ7jZzBonBx2qaLUVfpiRQmJixX0MnICSoUIr6AjDapVxH6Sb2qPLwS3oAn8jiHKj5P/8JkBJ56P/j6ul0E0flRxXEML0cQj1j;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1Nsid7-00077o-2t for ccamp@ietf.org; Fri, 19 Mar 2010 14:17:13 -0600
Message-ID: <4BA3DBD2.1090202@labn.net>
Date: Fri, 19 Mar 2010 16:17:22 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20091214 Eudora/3.0b4
MIME-Version: 1.0
To: ccamp@ietf.org
References: <003601cab0e7$b5474040$1fd5c0c0$@co.uk> <027c01cab991$ef543470$cdfc9d50$@co.uk> <008201cac12c$22b43e40$681cbac0$@co.uk>
In-Reply-To: <008201cac12c$22b43e40$681cbac0$@co.uk>
X-Enigmail-Version: 0.96a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Subject: [CCAMP] Reminder: Slides for IETF 77
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2010 20:17:04 -0000

All,
	Just a reminder that we need slides ASAP.  Given how tight our agenda
is we really won't have time for swapping laptops and files during the
session.

Much thanks,
Lou

On 3/11/2010 10:04 AM, Daniel King wrote:
> Hi all, 
> 
> The draft ccamp agenda for IETF 77 is now online:
> 
> http://tools.ietf.org/wg/ccamp/agenda?item=agenda77.html
> 
> If anyone has any questions please let us know. If your presenting slides,
> please send me your slides (CC co-chairs) no later than Friday March 19. 
> 
> Br, Dan.
> 

From stbryant@cisco.com  Sat Mar 20 18:36:49 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D30B23A65A6; Sat, 20 Mar 2010 18:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.185
X-Spam-Level: 
X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[AWL=-2.716, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9DW1HYPcZ7R; Sat, 20 Mar 2010 18:36:48 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id EC6523A67EC; Sat, 20 Mar 2010 18:36:47 -0700 (PDT)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjUBABsVpUuQ/uCWe2dsb2JhbACbPxUBAQsLJAYcomWBQgoBll8ChHsE
X-IronPort-AV: E=Sophos;i="4.51,281,1267401600";  d="scan'208";a="4595787"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-2.cisco.com with ESMTP; 21 Mar 2010 01:03:02 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o2L1b1tu025022; Sun, 21 Mar 2010 01:37:01 GMT
Received: from host152.pickyourflick.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o2L1axX15237; Sun, 21 Mar 2010 01:36:59 GMT
Message-ID: <4BA5783A.9070307@cisco.com>
Date: Sun, 21 Mar 2010 01:36:58 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <20100305191502.17B8F28C0F0@core3.amsl.com>	<4B9290D1.2080902@pi.nu> <787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com>
In-Reply-To: <787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, pwe3@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] WG Last Call on	draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 01:36:50 -0000

We could allocate a small number - say 4 or 8 for experimental purposes.

What do others think?

-Stewart


Greg Mirsky wrote:
> Dear Authors and All,
> my question on how the Type range control been organized. Is the whole 
> range from 0x0000 through 0xffff controlled by IANA? Would we like to 
> leave some smaller range out for experimental use?
>
> Regards,
> Greg
>
> On Sat, Mar 6, 2010 at 9:28 AM, Loa Andersson <loa@pi.nu 
> <mailto:loa@pi.nu>> wrote:
>
>     All,
>
>     this is to start a three week MPLS working group last call on
>
>     http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt
>
>     Please review and send your comments only to the mpls-tp@ietf.org
>     <mailto:mpls-tp@ietf.org>
>     mailing list.
>
>     The working group last call end March 28, 2010.
>
>     Loa and George
>
>
>     -- 
>
>
>     Loa Andersson                         email:
>     loa.andersson@ericsson.com <mailto:loa.andersson@ericsson.com>
>     Sr Strategy and Standards Manager            loa@pi.nu
>     <mailto:loa@pi.nu>
>     Ericsson Inc                          phone: +46 10 717 52 13
>                                                 +46 767 72 92 13
>     _______________________________________________
>     mpls mailing list
>     mpls@ietf.org <mailto:mpls@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mpls
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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 vishwas.ietf@gmail.com  Sat Mar 20 19:33:16 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2BC23A688F; Sat, 20 Mar 2010 19:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.545
X-Spam-Level: 
X-Spam-Status: No, score=-1.545 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OR88MVhUGieV; Sat, 20 Mar 2010 19:33:15 -0700 (PDT)
Received: from mail-yw0-f200.google.com (mail-yw0-f200.google.com [209.85.211.200]) by core3.amsl.com (Postfix) with ESMTP id 74B543A6872; Sat, 20 Mar 2010 19:33:12 -0700 (PDT)
Received: by ywh38 with SMTP id 38so2279288ywh.29 for <multiple recipients>; Sat, 20 Mar 2010 19:33:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=lXE2b/pIS3dtatcHZ+TtGRvaDHouCj12twKGaloGqp8=; b=CyMTfdKj+6HEwebkC309Gn9Pqt72mxMWB/H341EFKjs5eAnqfD45/CS6Fmi4ypcAob jF5sOC0TixjfJZoTRGA5iwb+COuglJJhRNmKgULnnT8nSjVHeNihSvMLZTdIsePuPabF t8fPk29ywsLmP0P6T1atWTqPmkP0Q6R55g81c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hzOYL3DZIK++bU4qoEXwhGPgQPDeG4upeQUV2R8evdwuv3NQANOqfvo/S4Y5C9E0w9 7fDEaOtw7MsdwXijDLngnoH4GXb8jMHE0gQm/m+oWwWQQjGFz4cHGZQjUwRWv0ApY8o3 z75MYz5i+Q/Z46L0a4Koh0VEhJUDkOCzVbawc=
MIME-Version: 1.0
Received: by 10.150.128.10 with SMTP id a10mr341891ybd.273.1269138803961; Sat,  20 Mar 2010 19:33:23 -0700 (PDT)
In-Reply-To: <4BA5783A.9070307@cisco.com>
References: <20100305191502.17B8F28C0F0@core3.amsl.com> <4B9290D1.2080902@pi.nu> <787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com> <4BA5783A.9070307@cisco.com>
Date: Sat, 20 Mar 2010 19:33:23 -0700
Message-ID: <77ead0ec1003201933m8c5733s9fc0ec509d505009@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: stbryant@cisco.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: CCAMP <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, pwe3@ietf.org, mpls@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 02:33:16 -0000

Hi Stewart,

I agree we could allocate 8 numbers.

Thanks,
Vishwas

On Sat, Mar 20, 2010 at 6:36 PM, Stewart Bryant <stbryant@cisco.com> wrote:
> We could allocate a small number - say 4 or 8 for experimental purposes.
>
> What do others think?
>
> -Stewart
>
>
> Greg Mirsky wrote:
>>
>> Dear Authors and All,
>> my question on how the Type range control been organized. Is the whole
>> range from 0x0000 through 0xffff controlled by IANA? Would we like to le=
ave
>> some smaller range out for experimental use?
>>
>> Regards,
>> Greg
>>
>> On Sat, Mar 6, 2010 at 9:28 AM, Loa Andersson <loa@pi.nu
>> <mailto:loa@pi.nu>> wrote:
>>
>> =A0 =A0All,
>>
>> =A0 =A0this is to start a three week MPLS working group last call on
>>
>> =A0 =A0http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02=
.txt
>>
>> =A0 =A0Please review and send your comments only to the mpls-tp@ietf.org
>> =A0 =A0<mailto:mpls-tp@ietf.org>
>> =A0 =A0mailing list.
>>
>> =A0 =A0The working group last call end March 28, 2010.
>>
>> =A0 =A0Loa and George
>>
>>
>> =A0 =A0--
>>
>> =A0 =A0Loa Andersson =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ema=
il:
>> =A0 =A0loa.andersson@ericsson.com <mailto:loa.andersson@ericsson.com>
>> =A0 =A0Sr Strategy and Standards Manager =A0 =A0 =A0 =A0 =A0 =A0loa@pi.n=
u
>> =A0 =A0<mailto:loa@pi.nu>
>> =A0 =A0Ericsson Inc =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0p=
hone: +46 10 717 52 13
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0+46 767 72 92 13
>> =A0 =A0_______________________________________________
>> =A0 =A0mpls mailing list
>> =A0 =A0mpls@ietf.org <mailto:mpls@ietf.org>
>> =A0 =A0https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>
>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>

From hhelvoort@chello.nl  Sun Mar 21 10:31:15 2010
Return-Path: <hhelvoort@chello.nl>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC3263A6A2F; Sun, 21 Mar 2010 10:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.481
X-Spam-Level: **
X-Spam-Status: No, score=2.481 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vFYLt2AqNk73; Sun, 21 Mar 2010 10:31:14 -0700 (PDT)
Received: from viefep19-int.chello.at (viefep19-int.chello.at [62.179.121.39]) by core3.amsl.com (Postfix) with ESMTP id A95EB3A6863; Sun, 21 Mar 2010 10:31:13 -0700 (PDT)
Received: from edge01.upcmail.net ([192.168.13.236]) by viefep19-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100321173128.FKSN5582.viefep19-int.chello.at@edge01.upcmail.net>;  Sun, 21 Mar 2010 18:31:28 +0100
Received: from McAsterix.local ([76.79.230.2]) by edge01.upcmail.net with edge id vtXQ1d05l03lDLC01tXSRq; Sun, 21 Mar 2010 18:31:28 +0100
X-SourceIP: 76.79.230.2
Message-ID: <4BA657EB.9060709@chello.nl>
Date: Sun, 21 Mar 2010 18:31:23 +0100
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
References: <20100305191502.17B8F28C0F0@core3.amsl.com>	<4B9290D1.2080902@pi.nu>	<787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com> <4BA5783A.9070307@cisco.com>
In-Reply-To: <4BA5783A.9070307@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Cloudmark-Analysis: v=1.1 cv=EFR1pENkxzhdjTnRVAuI+iHrp5zsYr2ENPL4njVhkqM= c=1 sm=0 a=KfCxD1MNmM0A:10 a=8nJEP1OIZ-IA:10 a=48vgC7mUAAAA:8 a=0FD05c-RAAAA:8 a=OLZQc8AWAAAA:8 a=AZjmcI9-NlhnwyRoIA4A:9 a=aiABKlHFUuvqCPuc8NoA:7 a=XXKD-Vz57WzxrHDU7ugGInt6zn8A:4 a=wPNLvfGTeEIA:10 a=zSNQObAR6s4A:10 a=lZB815dzVvQA:10 a=f7GxY0FH8QIA:10 a=8Nja_CwlgzH-Ox0-:21 a=9wjsl6YkA8Ux2fxO:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, pwe3@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls-tp] [mpls] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 17:31:15 -0000

Ho Stewart,

You suggested:

> We could allocate a small number - say 4 or 8 for experimental purposes.
> 
> What do others think?

I agree, and for consistency use the same number (and numbers)
as allocated for experimental Channel types in RFC5586.

Regards, Huub.


> Greg Mirsky wrote:
>> Dear Authors and All,
>> my question on how the Type range control been organized. Is the whole 
>> range from 0x0000 through 0xffff controlled by IANA? Would we like to 
>> leave some smaller range out for experimental use?
>>
>> Regards,
>> Greg
>>
>> On Sat, Mar 6, 2010 at 9:28 AM, Loa Andersson <loa@pi.nu 
>> <mailto:loa@pi.nu>> wrote:
>>
>>     All,
>>
>>     this is to start a three week MPLS working group last call on
>>
>>     http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02.txt
>>
>>     Please review and send your comments only to the mpls-tp@ietf.org
>>     <mailto:mpls-tp@ietf.org>
>>     mailing list.
>>
>>     The working group last call end March 28, 2010.
>>
>>     Loa and George
>>
>>
>>     --
>>
>>     Loa Andersson                         email:
>>     loa.andersson@ericsson.com <mailto:loa.andersson@ericsson.com>
>>     Sr Strategy and Standards Manager            loa@pi.nu
>>     <mailto:loa@pi.nu>
>>     Ericsson Inc                          phone: +46 10 717 52 13
>>                                                 +46 767 72 92 13
>>     _______________________________________________
>>     mpls mailing list
>>     mpls@ietf.org <mailto:mpls@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>   
> 
> 

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

From zhang.fei3@zte.com.cn  Sun Mar 21 15:12:53 2010
Return-Path: <zhang.fei3@zte.com.cn>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC2B63A693B for <ccamp@core3.amsl.com>; Sun, 21 Mar 2010 15:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -93.905
X-Spam-Level: 
X-Spam-Status: No, score=-93.905 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 tNh61LoGT9S3 for <ccamp@core3.amsl.com>; Sun, 21 Mar 2010 15:12:53 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id E35DB3A6927 for <ccamp@ietf.org>; Sun, 21 Mar 2010 15:12:51 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 31490473195744; Mon, 22 Mar 2010 06:12:23 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.15] with StormMail ESMTP id 64572.2187257994; Mon, 22 Mar 2010 06:13:03 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o2LMD3ZE078874; Mon, 22 Mar 2010 06:13:03 +0800 (CST) (envelope-from zhang.fei3@zte.com.cn)
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA05C918EA@gaalpa1msgusr7e.ugd.att.com>
To: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF5EAF743F.413004E3-ON482576ED.0079F25D-882576ED.007A4F67@zte.com.cn>
From: zhang.fei3@zte.com.cn
Date: Sun, 21 Mar 2010 14:13:04 -0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-03-22 06:13:02, Serialize complete at 2010-03-22 06:13:02
Content-Type: multipart/alternative; boundary="=_alternative 007A4F66882576ED_="
X-MAIL: mse2.zte.com.cn o2LMD3ZE078874
Cc: CCAMP <ccamp@ietf.org>
Subject: Re: [CCAMP] [PWE3] poll on draft-abfb-mpls-tp-control-plane-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Mar 2010 22:12:53 -0000

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

eWVzL3N1cHBvcnQNCg0KDQoNCg0KIkJSVU5HQVJELCBERUJPUkFIIEEgKEFUVExBQlMpIiA8ZGIz
NTQ2QGF0dC5jb20+IA0Kt6K8/sjLOiAgcHdlMy1ib3VuY2VzQGlldGYub3JnDQoyMDEwLTAyLTI2
IDEzOjUzDQoNCsrVvP7Iyw0KIkNDQU1QIiA8Y2NhbXBAaWV0Zi5vcmc+DQqzrcvNDQptcGxzQGll
dGYub3JnLCBwd2UzQGlldGYub3JnLCBtcGxzLXRwQGlldGYub3JnDQrW98ziDQpbUFdFM10gcG9s
bCBvbiBkcmFmdC1hYmZiLW1wbHMtdHAtY29udHJvbC1wbGFuZS1mcmFtZXdvcmsNCg0KDQoNCg0K
DQoNCkFsbCwNCg0KVGhpcyBpcyB0byBzdGFydCBhIHR3byB3ZWVrIHdvcmtpbmcgZ3JvdXAgcG9s
bCBvbiBtYWtpbmcNCmRyYWZ0LWFiZmItbXBscy10cC1jb250cm9sLXBsYW5lLWZyYW1ld29yay0w
Mi50eHQgYXMgYSBjY2FtcCB3b3JraW5nDQpncm91cCBkb2N1bWVudC4gVGhpcyBwb2xsIGlzIGJl
aW5nIGluaXRpYXRlZCBhdCB0aGlzIHRpbWUgYXMgdGhpcw0KZG9jdW1lbnQgaXMgcGFydCBvZiB0
aGUgTVBMUy1UUCB3b3JrIGFuZCBpdCBpcyBuZWVkZWQgdG8gcHJvZ3Jlc3MgdGhlDQp3b3JrLg0K
DQpTZW5kIHlvdXIgcmVzcG9uc2UgdG8gdGhlIGNjYW1wQGlldGYub3JnIG1haWxpbmcgbGlzdCAo
b25seSksIGluZGljYXRpbmcNCiJ5ZXMvc3VwcG9ydCIgb3IgIm5vL2RvIG5vdCBzdXBwb3J0Ii4N
Cg0KVGhpcyBwb2xsIGVuZHMgTWFyY2ggMTJ0aC4NCg0KRGVib3JhaA0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnB3ZTMgbWFpbGluZyBsaXN0DQpwd2Uz
QGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3B3ZTMNCg0K
DQoNCg==
--=_alternative 007A4F66882576ED_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yPjx0dD55ZXMvc3VwcG9ydDwvdHQ+PC9mb250Pg0KPGJyPg0KPGJy
Pg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3
aWR0aD0zNCU+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjxiPiZxdW90O0JSVU5HQVJE
LCBERUJPUkFIDQpBIChBVFRMQUJTKSZxdW90OyAmbHQ7ZGIzNTQ2QGF0dC5jb20mZ3Q7PC9iPiA8
L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPreivP7IyzogJm5ic3A7
cHdlMy1ib3VuY2VzQGlldGYub3JnPC9mb250Pg0KPHA+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt
c2VyaWYiPjIwMTAtMDItMjYgMTM6NTM8L2ZvbnQ+DQo8dGQgd2lkdGg9NjUlPg0KPHRhYmxlIHdp
ZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQg
c2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPsrVvP7IyzwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBz
aXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+JnF1b3Q7Q0NBTVAmcXVvdDsgJmx0O2NjYW1wQGlldGYu
b3JnJmd0OzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48
Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+s63LzTwvZm9udD48L2Rpdj4NCjx0ZD48Zm9u
dCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+bXBsc0BpZXRmLm9yZywgcHdlM0BpZXRmLm9yZywg
bXBscy10cEBpZXRmLm9yZzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGln
bj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+1vfM4jwvZm9udD48L2Rpdj4N
Cjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+W1BXRTNdIHBvbGwgb24gZHJhZnQt
YWJmYi1tcGxzLXRwLWNvbnRyb2wtcGxhbmUtZnJhbWV3b3JrPC9mb250PjwvdGFibGU+DQo8YnI+
DQo8dGFibGU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwvdGFi
bGU+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yPjx0dD5BbGwsPGJyPg0KPGJyPg0KVGhp
cyBpcyB0byBzdGFydCBhIHR3byB3ZWVrIHdvcmtpbmcgZ3JvdXAgcG9sbCBvbiBtYWtpbmc8YnI+
DQpkcmFmdC1hYmZiLW1wbHMtdHAtY29udHJvbC1wbGFuZS1mcmFtZXdvcmstMDIudHh0IGFzIGEg
Y2NhbXAgd29ya2luZzxicj4NCmdyb3VwIGRvY3VtZW50LiBUaGlzIHBvbGwgaXMgYmVpbmcgaW5p
dGlhdGVkIGF0IHRoaXMgdGltZSBhcyB0aGlzPGJyPg0KZG9jdW1lbnQgaXMgcGFydCBvZiB0aGUg
TVBMUy1UUCB3b3JrIGFuZCBpdCBpcyBuZWVkZWQgdG8gcHJvZ3Jlc3MgdGhlPGJyPg0Kd29yay48
YnI+DQo8YnI+DQpTZW5kIHlvdXIgcmVzcG9uc2UgdG8gdGhlIGNjYW1wQGlldGYub3JnIG1haWxp
bmcgbGlzdCAob25seSksIGluZGljYXRpbmc8YnI+DQomcXVvdDt5ZXMvc3VwcG9ydCZxdW90OyBv
ciAmcXVvdDtuby9kbyBub3Qgc3VwcG9ydCZxdW90Oy48YnI+DQo8YnI+DQpUaGlzIHBvbGwgZW5k
cyBNYXJjaCAxMnRoLjxicj4NCjxicj4NCkRlYm9yYWg8YnI+DQpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCnB3ZTMgbWFpbGluZyBsaXN0PGJyPg0K
cHdlM0BpZXRmLm9yZzxicj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
cHdlMzxicj4NCjxicj4NCjwvdHQ+PC9mb250Pg0KPGJyPg0K
--=_alternative 007A4F66882576ED_=--


From giomarti@cisco.com  Mon Mar 22 08:17:00 2010
Return-Path: <giomarti@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B4F93A6800 for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 08:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.868
X-Spam-Level: 
X-Spam-Status: No, score=-6.868 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3IsC-LwhjyQt for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 08:16:50 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 376F028C0FA for <ccamp@ietf.org>; Mon, 22 Mar 2010 08:16:41 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmUBAAcnp0uQ/uCWe2dsb2JhbACBQpliFQEBCwskBhyieYsNCIx6gmMIghIE
X-IronPort-AV: E=Sophos;i="4.51,287,1267401600"; d="scan'208,217";a="58387213"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 22 Mar 2010 15:16:56 +0000
Received: from [10.61.83.36] (ams3-vpn-dhcp4901.cisco.com [10.61.83.36]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o2MFGtZv009415; Mon, 22 Mar 2010 15:16:55 GMT
Message-ID: <4BA78A3F.5010207@cisco.com>
Date: Mon, 22 Mar 2010 16:18:23 +0100
From: Giovanni Martinelli <giomarti@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100305 Lightning/1.0b2pre Thunderbird/3.0.3
MIME-Version: 1.0
To: Young Lee <ylee@huawei.com>
References: <4B87DE23.8080004@cisco.com> <002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com>
In-Reply-To: <002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com>
Content-Type: multipart/alternative; boundary="------------060006050702070005060004"
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] Comments on draft-ietf-ccamp-rwa-wson-framework-05
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 15:17:00 -0000

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

Hi,

On 03/10/2010 05:35 PM, Young Lee wrote:
>
> Hi Giovanni,
>
> Please see in-line for the comments.
>
> Regards,
>
> Greg & Young
>
> ------------------------------------------------------------------------
>
> *From:* ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] *On 
> Behalf Of *Giovanni Martinelli
> *Sent:* Friday, February 26, 2010 8:44 AM
> *To:* ccamp@ietf.org
> *Subject:* [CCAMP] Comments on draft-ietf-ccamp-rwa-wson-framework-05
>
> Hi Greg/Young/Authors,
>
> regarding the rwa framework I appreciate last updates, they goes in 
> the right direction. I still have few comment on the draft:
>
>
> 1) Sec. 3.5.1 Regenerators
> According to ITU inputs (Q6 mtg last october) the regeneration 
> classification was:
> 1R: amplifier
> 2R: does not exist
> 3R: the regenerator (indeed).
>
> I can understand the framework list all the three types (for sake of 
> completess) but at the end we can consider only 3R as regeneration. 
> This should also simplify the related encoding: we need only to know 
> if regen is available and not the specific type (1, 2 or 3).
>
> Young>>  We are referencing these terminology from ITU-T G.872 (Annex A) so these are legitimate regeneration classification.
> 1R regenerators may work over a limited range of wavelength/frequencies so this needs to be known to the control plane path computation process.
> 2R regenerators are usually dependent on modulation format and are limited to a range of bit rates, so this needs to be known as well.

I'm fine with the reference I was wandering about defining details which 
are not so useful: if 1R are equivalent to amplifier how does this 
impact with RWA (impairment free ;-)) case?

In term of info model I guess will be much more simpler to consider 
regens (so only 3R) without diving into 1-2-3R ... on this not sure 
there was a communication coming back from Q6 after last october meeting 
but we could probably ask better on this.


>
> 2) Sec. 4.1.1
> PCE is one of the architectural options but reading the first bullet 
> looks like there is a need of a *stateful* PCE to support RWA.
> If that the case probably worth a reference to RFC4655 section 6.8.
>
> Young>> We didn't assume that we need a stateful PCE to support RWA. 
> We assume that the up-to-date RWA usage information will be updated by 
> OSPF routing enhancement.
>
>
ok

> 3) Sec. 4.1.3
> The statement "this approach may generate higher blocking 
> probability.." is there any reference that demonstrate this?
>
> Young>> Please see the following references:
>
> [1]
>
> 	
>
> K. Lu, G. Xiao, and I. Chlamtac, "Analysis of blocking probability for 
> distributed lightpath establishment in WDM optical networks," 
> /IEEE/ACM Trans. Netw./, vol. 13, 2005, pp. 187-197.
>
> [2]
>
> 	
>
> A. Giorgetti, N. Sambo, L. Valcarenghi, and P. Castoldi, "Reservation 
> Collision Avoidance in GMPLS Wavelength-routed Optical Networks," 
> /Photonics in Switching, 2006. PS '06. International Conference on/, 
> 2006, pp. 1-3.
>
> [3]
>
> 	
>
> A. Giorgetti, F. Paolucci, F. Cugini, L. Valcarenghi, P. Castoldi, and 
> G. Bernstein, "Routing and Wavelength Assignment in PCE-based 
> Wavelength Switched Optical Networks," /Optical Communication, 2008. 
> ECOC 2008. 34th European Conference on/, 2008, pp. 1-2.
>
>

well only the first try to build an analytical model and even blocking 
probability depends on several boundary conditions (network loads, 
burstiness etc.)

Not sure if this framework is the right place to make those kind of 
considerations...


> 4) Section 4.3
> Is not really clear to me the scope of this section, why do we need to 
> state anything about temporal characteristics?
>
> Young>> The idea was to explain that different timeliness requirements 
> for lightpath setup influence or restrict the amount of "optimization" 
> that can be done with the computation of a path.
>
>
> Another comment that I did some time ago was about defining 
> dynamic/pseudo-static/static with no reference: the draft just mention 
> short or moderately-long and long duration.
>
> Young>> Do you have any suggestion as to how to change this section?
>

(Let me put the above two comments together)
So if I understand correctly, a potential network re-optimization will 
take into account only what you call static/pseduo-static LSPs, right?

Probably, thinking in term of framework I would add just some 
consideration about adding some lightpath liveness and how this  
information could be used. This could be done without defining different 
level of liveness as it is now



> 5) Sec. 5.5.4
> I understand you need to clarify some typical optical terminology 
> like: transparent / translucent etc. but how about having all 
> terminology grouped in section 3?
> And basically this WSON framework support either transparent (in 
> different flavors) and translucent.
>
> Young>> Good idea! We will update that. Do you have some suggested 
> definition?
>

Probably a section 3.x  that sounds like "Types of WSON networks" where 
the terms are defined: transparent/transparent-island, mostly 
transparent, opaque etc.

And for sure a statement that they are in  the scope of this framework


Cheers
G


>
>
> Cheers
> G
>
>

--------------060006050702070005060004
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<font face="Helvetica, Arial, sans-serif">Hi,<br>
</font><br>
On 03/10/2010 05:35 PM, Young Lee wrote:
<blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite">
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
  <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo1;
	font-size:16.0pt;
	font-family:Arial;
	color:black;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
tt
	{font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;
	color:black;}
p.Style1, li.Style1, div.Style1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@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:1792360828;
	mso-list-template-ids:1288485006;}
@list l0:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	font-family:"Times New Roman";}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	font-family:"Times New Roman";}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	font-family:"Times New Roman";}
@list l0:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
  </style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1027" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
  <div class="Section1">
  <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;">Hi Giovanni,<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;">Please see
in-line for the comments. &nbsp;<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;">Regards,<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;">Greg &amp;
Young<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>&nbsp;</o:p></span></font></p>
  <div class="MsoNormal" style="text-align: center;" align="center"><font
 size="3" color="black" face="Times New Roman"><span
 style="font-size: 12pt; color: windowtext;">
  <hr tabindex="-1" size="2" width="100%" align="center"></span></font></div>
  <p class="MsoNormal"><b><font size="2" color="black" face="Tahoma"><span
 style="font-size: 10pt; font-family: Tahoma; color: windowtext; font-weight: bold;">From:</span></font></b><font
 size="2" color="black" face="Tahoma"><span
 style="font-size: 10pt; font-family: Tahoma; color: windowtext;">
<a class="moz-txt-link-abbreviated" href="mailto:ccamp-bounces@ietf.org">ccamp-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:ccamp-bounces@ietf.org">mailto:ccamp-bounces@ietf.org</a>] <b><span
 style="font-weight: bold;">On Behalf Of </span></b>Giovanni Martinelli<br>
  <b><span style="font-weight: bold;">Sent:</span></b> Friday, February
26, 2010
8:44 AM<br>
  <b><span style="font-weight: bold;">To:</span></b> <a class="moz-txt-link-abbreviated" href="mailto:ccamp@ietf.org">ccamp@ietf.org</a><br>
  <b><span style="font-weight: bold;">Subject:</span></b> [CCAMP]
Comments on
draft-ietf-ccamp-rwa-wson-framework-05</span></font><font color="black"><span
 style="color: windowtext;"><o:p></o:p></span></font></p>
  <p class="MsoNormal"><font size="3" color="black"
 face="Times New Roman"><span style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoNormal"><font size="3" color="black"
 face="Times New Roman"><span style="font-size: 12pt;"><!--[if gte vml 1]><v:shapetype id="_x0000_t74" 
 coordsize="21600,21600" o:spt="74" path="m10860,2187c10451,1746,9529,1018,9015,730,7865,152,6685,,5415,,4175,152,2995,575,1967,1305,1150,2187,575,3222,242,4220,,5410,242,6560,575,7597l10860,21600,20995,7597v485,-1037,605,-2187,485,-3377c21115,3222,20420,2187,19632,1305,18575,575,17425,152,16275,,15005,,13735,152,12705,730v-529,288,-1451,1016,-1845,1457xe">
 <v:stroke joinstyle="miter" />
 <v:path gradientshapeok="t" o:connecttype="custom" o:connectlocs="10860,2187;2928,10800;10860,21600;18672,10800" 
  o:connectangles="270,180,90,0" textboxrect="5037,2277,16557,13677" />
</v:shapetype><v:shape id="DtsShapeName" o:spid="_x0000_s1026" type="#_x0000_t74" 
 alt="47E529CG097D5920@5BB2C5D2BED5405097@8h8=@@dM62793!!!!!!BIHO@]M62793!!!11111111110BCGBD3519Onsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!80L8Z8;D8_M62793!!!!!!BIHO@]m62793!!!11111111110BCGBD3519110BCGBD3519!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!86G;&lt;8=?8`M62793!!!!!!BIHO@]M62793!!!11111111110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8;?;A8;?@@M62793!!!!!!BIHO@]m62793!!!1@6B1B5B110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!1" 
 style='position:absolute;margin-left:0;margin-top:0;width:.05pt;height:.05pt;
 z-index:1;visibility:hidden'>
 <w:anchorlock/>
</v:shape><![endif]--></span></font><tt><font
 size="2" face="Courier New"><span style="font-size: 10pt;">Hi
Greg/Young/Authors,</span></font></tt><font size="2" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
  <br>
  <tt><font face="Courier New">regarding the rwa framework I appreciate
last
updates, they goes in the right direction. I still have few comment on
the
draft:</font></tt><br>
  <br>
  <br>
  <tt><font face="Courier New">1) Sec. 3.5.1 Regenerators </font></tt><br>
  <tt><font face="Courier New">According to ITU inputs (Q6 mtg last
october) the
regeneration classification was:</font></tt><br>
  <tt><font face="Courier New">1R: amplifier</font></tt><br>
  <tt><font face="Courier New">2R: does not exist</font></tt><br>
  <tt><font face="Courier New">3R: the regenerator (indeed).</font></tt><br>
  <br>
  <tt><font face="Courier New">I can understand the framework list all
the three
types (for sake of completess) but at the end we can consider only 3R
as
regeneration. This should also simplify the related encoding: we need
only to
know if regen is available and not the specific type (1, 2 or 3).</font></tt><br>
  <br>
  </span></font><font size="2" color="navy" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: navy;"><o:p></o:p></span></font></p>
  <pre style="page-break-before: always;"><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt; We are referencing these terminology from ITU-T G.872 (Annex A) so these are legitimate regeneration classification. <o:p></o:p></span></font></pre>
  <pre style="page-break-before: always;"><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">1R regenerators may work over a limited range of wavelength/frequencies so this needs to be known to the control plane path computation process.<o:p></o:p></span></font></pre>
  <pre style="page-break-before: always;"><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">2R regenerators are usually dependent on modulation format and are limited to a range of bit rates, so this needs to be known as well. </span></font><font
 color="#3366ff"><span style="color: rgb(51, 102, 255);"><o:p></o:p><o:p></o:p></span></font></pre>
  </div>
  </o:smarttagtype></blockquote>
<br>
I'm fine with the reference I was wandering about defining details
which are not so useful: if 1R are equivalent to amplifier how does
this impact with RWA (impairment free ;-)) case?<br>
<br>
In term of info model I guess will be much more simpler to consider
regens (so only 3R) without diving into 1-2-3R ... on this not sure
there was a communication coming back from Q6 after last october
meeting but we could probably ask better on this. <br>
<br>
<br>
<blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
  <div class="Section1">
  <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p><o:p>&nbsp;</o:p></o:p></span></font></p>
  <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
  <tt><font face="Courier New">2) Sec. 4.1.1</font></tt><br>
  <tt><font face="Courier New">PCE is one of the architectural options
but
reading the first bullet looks like there is a need of a *stateful* PCE
to support
RWA. </font></tt><br>
  <tt><font face="Courier New">If that the case probably worth a
reference to
RFC4655 section 6.8.</font></tt><br>
  <br>
  </span></font><font size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;</span></font><font
 size="2" color="#3366ff" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(51, 102, 255);">
  </span></font><font size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">We
didn&#8217;t assume that we need a stateful PCE to support
RWA. We assume that the up-to-date RWA usage information will be
updated by
OSPF routing enhancement. <o:p></o:p></span></font><font
 color="#3366ff"><span style="color: rgb(51, 102, 255);"><o:p></o:p></span></font></p>
  <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
  </span></font></p>
  </div>
  </o:smarttagtype></blockquote>
ok<br>
<br>
<blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
  <div class="Section1">
  <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><tt><font
 face="Courier New">3) Sec. 4.1.3</font></tt><br>
  <tt><font face="Courier New">The statement "this approach may
generate
higher blocking probability.." is there any reference that demonstrate
this? </font></tt><br>
  <br>
  </span></font><font size="2" color="navy" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: navy;"><o:p></o:p></span></font></p>
  <p class="MsoNormal" style=""><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;
Please see the following references:<o:p></o:p></span></font></p>
  <table class="MsoNormalTable" style="border-collapse: collapse;"
 cellpadding="0" cellspacing="0" border="0">
    <tbody>
      <tr>
        <td style="padding: 0.75pt;" valign="top">
        <p class="MsoNormal" style="line-height: 13.2pt;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">[1]<o:p></o:p></span></font></p>
        </td>
        <td style="padding: 0.75pt 0.75pt 0.75pt 4pt;" valign="top">
        <p class="MsoNormal" style="line-height: 13.2pt;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">K.

Lu, G. Xiao, and I. Chlamtac, &#8220;Analysis of blocking probability for
distributed lightpath establishment in WDM optical networks,&#8221; <i><span
 style="font-style: italic;">IEEE/ACM Trans. Netw.</span></i>, vol. 13,
2005, pp. 187-197. <span class="z3988"><span
 title="url_ver=Z39.88-2004&amp;ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.atitle=Analysis%20of%20blocking%20probability%20for%20distributed%20lightpath%20establishment%20in%20WDM%20optical%20networks&amp;rft.jtitle=IEEE%2FACM%20Trans.%20Netw.&amp;rft.volume=13&amp;rft.issue=1&amp;rft.aufirst=Kejie&amp;rft.aulast=Lu&amp;rft.au=Kejie%20Lu&amp;rft.au=Gaoxi%20Xiao&amp;rft.au=Imrich%20Chlamtac&amp;rft.date=2005&amp;rft.pages=187-197">&nbsp;</span></span><o:p></o:p></span></font></p>
        </td>
      </tr>
      <tr>
        <td style="padding: 0.75pt;" valign="top">
        <p class="MsoNormal" style="line-height: 13.2pt;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">[2]<o:p></o:p></span></font></p>
        </td>
        <td style="padding: 0.75pt 0.75pt 0.75pt 4pt;" valign="top">
        <p class="MsoNormal" style="line-height: 13.2pt;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">A.

Giorgetti, <st1:place w:st="on">N. Sambo</st1:place>, L. Valcarenghi,
and P. Castoldi, &#8220;Reservation Collision Avoidance in GMPLS
Wavelength-routed Optical Networks,&#8221; <i><span
 style="font-style: italic;">Photonics in Switching, 2006. PS '06.
International Conference on</span></i>, 2006, pp. 1-3.<o:p></o:p></span></font></p>
        </td>
      </tr>
      <tr>
        <td style="padding: 0.75pt;" valign="top">
        <p class="MsoNormal" style="line-height: 13.2pt;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">[3]<o:p></o:p></span></font></p>
        </td>
        <td style="padding: 0.75pt 0.75pt 0.75pt 4pt;" valign="top">
        <p class="MsoNormal" style="line-height: 13.2pt;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">A.

Giorgetti, F. Paolucci, F. Cugini, L. Valcarenghi, P. Castoldi, and G.
Bernstein, &#8220;Routing and Wavelength Assignment in PCE-based Wavelength
Switched Optical Networks,&#8221; <i><span style="font-style: italic;">Optical

Communication, 2008. ECOC 2008. 34th European Conference on</span></i>,
2008, pp. 1-2.<o:p></o:p></span></font></p>
        </td>
      </tr>
    </tbody>
  </table>
  <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
  </span></font></p>
  </div>
  </o:smarttagtype></blockquote>
<br>
well only the first try to build an analytical model and even blocking
probability depends on several boundary conditions (network loads,
burstiness etc.)<br>
<br>
Not sure if this framework is the right place to make those kind of
considerations... <br>
&nbsp;<br>
<br>
<blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
  <div class="Section1">
  <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><tt><font
 face="Courier New">4) Section 4.3</font></tt><br>
  <tt><font face="Courier New">Is not really clear to me the scope of
this
section, why do we need to state anything about temporal
characteristics?</font></tt></span></font><tt><font size="2"
 color="navy" face="Courier New"><span
 style="font-size: 10pt; color: navy;"><o:p></o:p></span></font></tt></p>
  <p class="MsoNormal" style=""><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;
The idea was to explain that different
timeliness requirements for lightpath setup influence or restrict the
amount of
"optimization" that can be done with the computation of a path.</span></font><font
 size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p></o:p></span></font></p>
  <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
  <tt><font face="Courier New">Another comment that I did some time ago
was about
defining dynamic/pseudo-static/static with no reference: the draft just
mention
short or moderately-long and long duration.</font></tt><br>
  <br>
  </span></font><font size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;
Do you have any
suggestion as to how to change this section? </span></font></p>
  </div>
  </o:smarttagtype></blockquote>
<br>
(Let me put the above two comments together)<br>
So if I understand correctly, a potential network re-optimization will
take into account only what you call static/pseduo-static LSPs, right?<br>
<br>
Probably, thinking in term of framework I would add just some
consideration about adding some lightpath liveness and how this&nbsp;
information could be used. This could be done without defining
different level of liveness as it is now <br>
<br>
<br>
<br>
<blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
  <div class="Section1">
  <p class="MsoNormal" style=""><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);"><o:p></o:p></span></font></p>
  <p class="MsoNormal" style=""><tt><font size="2" color="black"
 face="Courier New"><span style="font-size: 10pt;">5) Sec.
5.5.4</span></font></tt><font size="2" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
  <tt><font face="Courier New">I understand you need to clarify some
typical
optical terminology like: transparent / translucent etc. but how about
having
all terminology grouped in section 3? </font></tt><br>
  <tt><font face="Courier New">And basically this WSON framework
support either
transparent (in different flavors) and translucent.</font></tt><br>
  <br>
  </span></font><font size="2" color="navy" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: navy;"><o:p></o:p></span></font></p>
  <p class="MsoNormal" style=""><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;
Good idea! We will update that. <o:p></o:p>Do
you have some suggested definition? </span></font><font color="#3366ff"><span
 style="color: rgb(51, 102, 255);"><o:p></o:p></span></font></p>
  <p class="MsoNormal" style=""><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>&nbsp;</o:p></span></font></p>
  </div>
  </o:smarttagtype></blockquote>
<br>
Probably a section 3.x&nbsp; that sounds like "Types of WSON networks" where
the terms are defined: transparent/transparent-island, mostly
transparent, opaque etc.<br>
<br>
And for sure a statement that they are in&nbsp; the scope of this framework<br>
<br>
<br>
Cheers<br>
G <br>
<br>
<br>
<blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
  <div class="Section1">
  <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
  <br>
  <tt><font face="Courier New">Cheers</font></tt><br>
  <tt><font face="Courier New">G</font></tt><br>
  <br>
  <br>
  </span></font><o:p></o:p></p>
<!--EndFragment--></div>
  </o:smarttagtype></blockquote>
</body>
</html>

--------------060006050702070005060004--

From zhang.fei3@zte.com.cn  Mon Mar 22 10:23:25 2010
Return-Path: <zhang.fei3@zte.com.cn>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C5B128C0ED; Mon, 22 Mar 2010 10:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.108
X-Spam-Level: 
X-Spam-Status: No, score=-98.108 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kFosQit7Fkau; Mon, 22 Mar 2010 10:23:24 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 0384A3A696E; Mon, 22 Mar 2010 10:22:56 -0700 (PDT)
Received: from [10.30.17.99] by mx6.zte.com.cn with surfront esmtp id 128641237205243; Tue, 23 Mar 2010 01:22:16 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.15] with StormMail ESMTP id 64572.1237205243; Tue, 23 Mar 2010 01:23:08 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o2MHNMso047125; Tue, 23 Mar 2010 01:23:24 +0800 (CST) (envelope-from zhang.fei3@zte.com.cn)
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, CCAMP <ccamp@ietf.org>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFF373361F.B0C0DBCD-ON482576EE.005E9615-882576EE.005FC0CE@zte.com.cn>
From: zhang.fei3@zte.com.cn
Date: Mon, 22 Mar 2010 09:23:00 -0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-03-23 01:23:00, Serialize complete at 2010-03-23 01:23:00
Content-Type: multipart/alternative; boundary="=_alternative 005FC0CC882576EE_="
X-MAIL: mse2.zte.com.cn o2MHNMso047125
Subject: [CCAMP] extending rsvp-te to setup associated bidirectional LSP
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 17:23:25 -0000

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

Hi MPLS-TPers, CCAMPers

a new draft related to associated bidirectional LSP will be presented in 
CCAMP on Tuesday morning session (California C).

For more details, please see: 
http://tools.ietf.org/html/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-00, 
and online slides.

Any comments are welcome

B.R.

Fei
--=_alternative 005FC0CC882576EE_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Hi MPLS-TPers, CCAMPers</tt></font>
<br>
<br><font size=2><tt>a new draft related to associated bidirectional LSP
will be presented in CCAMP on Tuesday morning session (California C).<br>
<br>
For more details, please see: http://tools.ietf.org/html/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-00,
and online slides.</tt></font>
<br>
<br><font size=2><tt>Any comments are welcome</tt></font>
<br>
<br><font size=2><tt>B.R.</tt></font>
<br>
<br><font size=2><tt>Fei</tt></font>
--=_alternative 005FC0CC882576EE_=--


From root@core3.amsl.com  Mon Mar 22 10:30:03 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 733A73A6970; Mon, 22 Mar 2010 10:30:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100322173003.733A73A6970@core3.amsl.com>
Date: Mon, 22 Mar 2010 10:30:02 -0700 (PDT)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-gmpls-g-694-lambda-labels-06.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 17:30:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : Generalized Labels for Lambda-Switching Capable Label Switching Routers
	Author(s)       : T. Otani, et al.
	Filename        : draft-ietf-ccamp-gmpls-g-694-lambda-labels-06.txt
	Pages           : 14
	Date            : 2010-03-22

Technology in the optical domain is constantly evolving and as a 
consequence new equipment providing lambda switching capability has 
been developed and is currently being deployed. However, [RFC3471] 
has defined that a wavelength label (section 3.2.1.1) "only has 
significance between two neighbors" and global wavelength continuity 
is not considered. In order to achieve interoperability in a network 
composed of next generation lambda switch-capable equipment, this 
document defines a standard lambda label format, being compliant 
with either [G.694.1](DWDM-grid) or [G.694.2](CWDM-grid). Moreover 
some consideration on how to ensure lambda continuity with RSVP-TE 
is provided. This document is a companion to the Generalized Multi-
Protocol Label Switching (GMPLS) signaling. It defines the label 
format when Lambda Switching is requested in an all optical network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-g-694-lambda-labels-06.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-gmpls-g-694-lambda-labels-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From danli@huawei.com  Mon Mar 22 10:38:20 2010
Return-Path: <danli@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 429773A6A1F for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 10:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kXT5GFnYLs4 for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 10:38:19 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id 5248E3A6A11 for <ccamp@ietf.org>; Mon, 22 Mar 2010 10:38:19 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZP007XL2CC8L@usaga03-in.huawei.com> for ccamp@ietf.org; Mon, 22 Mar 2010 12:38:36 -0500 (CDT)
Received: from dhcp-wireless-open-a-40-178.meeting.ietf.org (dhcp-wireless-open-a-40-178.meeting.ietf.org [130.129.40.178]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPSA id <0KZP003ZW2CBRO@usaga03-in.huawei.com> for ccamp@ietf.org; Mon, 22 Mar 2010 12:38:36 -0500 (CDT)
Date: Tue, 23 Mar 2010 01:38:00 +0800
From: Dan Li <danli@huawei.com>
To: ccamp@ietf.org
Message-id: <76F3A963-4DDE-4A3D-8D57-AD615CA27D9B@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
Subject: [CCAMP] New Version Notification for draft-ietf-ccamp-gmpls-g-694-lambda-labels-06
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 17:38:20 -0000

Dear CCAMPers and co-chairs,

As we have discussed the issues raised on the CCAMP WG mailing list  
with respect to the tunable lasers case, we finally resolved this  
issue by updating the CWDM/DWDM label format.

The main changes have been made in this (06) version, a new  
"identifier" field has been added in the label format.

The label format of DWDM/CWDM is as following:

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |Grid | C.S   |    Identifier   |              n                |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  (3) Identifier: 9 bits

  The identifier field is a per-node assigned and scoped value. This
  field MAY change on a per-hop basis. In all cases but one, a node MAY
  select any value, including zero (0), for this field. Once selected,
  the value MUST NOT change until the LSP is torn down and the value
  MUST be used in all LSP related messages, e.g., in Resv messages and
  label RRO subobjects. The sole special case occurs when this label
  format is used in a label ERO subobject. In this case, the special
  value of zero (0) means that the referenced node MAY assign any
  Identifier field value, including zero (0), when establishing the
  corresponding LSP.


Please let us know if you have any comment.


-----------
A new version of I-D, draft-ietf-ccamp-gmpls-g-694-lambda- 
labels-06.txt has been successfully submitted by Dan Li and posted to  
the IETF repository.

Filename:	 draft-ietf-ccamp-gmpls-g-694-lambda-labels
Revision:	 06
Title:		 Generalized Labels for Lambda-Switching Capable Label  
Switching Routers
Creation_date:	 2010-03-19
WG ID:		 ccamp
Number_of_pages: 14

Abstract:
Technology in the optical domain is constantly evolving and as a
consequence new equipment providing lambda switching capability has
been developed and is currently being deployed. However, [RFC3471]
has defined that a wavelength label (section 3.2.1.1) "only has
significance between two neighbors" and global wavelength continuity
is not considered. In order to achieve interoperability in a network
composed of next generation lambda switch-capable equipment, this
document defines a standard lambda label format, being compliant
with either [G.694.1](DWDM-grid) or [G.694.2](CWDM-grid). Moreover
some consideration on how to ensure lambda continuity with RSVP-TE
is provided. This document is a companion to the Generalized Multi-
Protocol Label Switching (GMPLS) signaling. It defines the label
format when Lambda Switching is requested in an all optical network.
-----------


Thanks,

Authors of label draft



From danli@huawei.com  Mon Mar 22 10:38:21 2010
Return-Path: <danli@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FB2E3A6A1F for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 10:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5c35ukoDOUkU for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 10:38:21 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id 099463A6A11 for <ccamp@ietf.org>; Mon, 22 Mar 2010 10:38:21 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZP007XX2CE8L@usaga03-in.huawei.com> for ccamp@ietf.org; Mon, 22 Mar 2010 12:38:38 -0500 (CDT)
Received: from dhcp-wireless-open-a-40-178.meeting.ietf.org (dhcp-wireless-open-a-40-178.meeting.ietf.org [130.129.40.178]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPSA id <0KZP003082CERO@usaga03-in.huawei.com> for ccamp@ietf.org; Mon, 22 Mar 2010 12:38:38 -0500 (CDT)
Date: Tue, 23 Mar 2010 01:38:37 +0800
From: Dan Li <danli@huawei.com>
To: ccamp@ietf.org
Message-id: <A2735F57-5CE0-437B-99DC-683F581127D6@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
Subject: [CCAMP] New Version Notification for draft-ietf-ccamp-gmpls-g-694-lambda-labels-06
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 17:38:21 -0000

Dear CCAMPers and co-chairs,

As we have discussed the issues raised on the CCAMP WG mailing list  
with respect to the tunable lasers case, we finally resolved this  
issue by updating the CWDM/DWDM label format.

The main changes have been made in this (06) version, a new  
"identifier" field has been added in the label format.

The label format of DWDM/CWDM is as following:

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |Grid | C.S   |    Identifier   |              n                |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  (3) Identifier: 9 bits

  The identifier field is a per-node assigned and scoped value. This
  field MAY change on a per-hop basis. In all cases but one, a node MAY
  select any value, including zero (0), for this field. Once selected,
  the value MUST NOT change until the LSP is torn down and the value
  MUST be used in all LSP related messages, e.g., in Resv messages and
  label RRO subobjects. The sole special case occurs when this label
  format is used in a label ERO subobject. In this case, the special
  value of zero (0) means that the referenced node MAY assign any
  Identifier field value, including zero (0), when establishing the
  corresponding LSP.


Please let us know if you have any comment.


-----------
A new version of I-D, draft-ietf-ccamp-gmpls-g-694-lambda- 
labels-06.txt has been successfully submitted by Dan Li and posted to  
the IETF repository.

Filename:	 draft-ietf-ccamp-gmpls-g-694-lambda-labels
Revision:	 06
Title:		 Generalized Labels for Lambda-Switching Capable Label  
Switching Routers
Creation_date:	 2010-03-19
WG ID:		 ccamp
Number_of_pages: 14

Abstract:
Technology in the optical domain is constantly evolving and as a
consequence new equipment providing lambda switching capability has
been developed and is currently being deployed. However, [RFC3471]
has defined that a wavelength label (section 3.2.1.1) "only has
significance between two neighbors" and global wavelength continuity
is not considered. In order to achieve interoperability in a network
composed of next generation lambda switch-capable equipment, this
document defines a standard lambda label format, being compliant
with either [G.694.1](DWDM-grid) or [G.694.2](CWDM-grid). Moreover
some consideration on how to ensure lambda continuity with RSVP-TE
is provided. This document is a companion to the Generalized Multi-
Protocol Label Switching (GMPLS) signaling. It defines the label
format when Lambda Switching is requested in an all optical network.
-----------


Thanks,

Authors of label draft



From root@core3.amsl.com  Mon Mar 22 11:30:06 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 4E4C23A6A26; Mon, 22 Mar 2010 11:30:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100322183005.4E4C23A6A26@core3.amsl.com>
Date: Mon, 22 Mar 2010 11:30:03 -0700 (PDT)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-mpls-tp-cp-framework-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 18:30:06 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : MPLS-TP Control Plane Framework
	Author(s)       : L. Andersson, et al.
	Filename        : draft-ietf-ccamp-mpls-tp-cp-framework-00.txt
	Pages           : 43
	Date            : 2010-03-22

The MPLS Transport Profile (MPLS-TP) supports static provisioning
of transport paths via a Network Management System (NMS), and
dynamic provisioning of transport paths via a control plane. This
document provides the framework for MPLS-TP dynamic provisioning,
and covers control plane addressing, routing, path computation,
signaling, traffic engineering,, and path recovery.  MPLS-TP uses
GMPLS as the control plane for MPLS-TP LSPs and provides for
compatibility with MPLS.  The control plane for Pseudowires (PWs)
is also covered by this document.  Management plane functions such
as manual configuration and the initiation of LSP setup are out of
scope of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-mpls-tp-cp-framework-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-mpls-tp-cp-framework-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From root@core3.amsl.com  Mon Mar 22 11:45:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 93E513A699F; Mon, 22 Mar 2010 11:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100322184501.93E513A699F@core3.amsl.com>
Date: Mon, 22 Mar 2010 11:45:01 -0700 (PDT)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-mpls-tp-cp-framework-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 18:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : MPLS-TP Control Plane Framework
	Author(s)       : L. Andersson, et al.
	Filename        : draft-ietf-ccamp-mpls-tp-cp-framework-01.txt
	Pages           : 47
	Date            : 2010-03-22

The MPLS Transport Profile (MPLS-TP) supports static provisioning
of transport paths via a Network Management System (NMS), and
dynamic provisioning of transport paths via a control plane. This
document provides the framework for MPLS-TP dynamic provisioning,
and covers control plane addressing, routing, path computation,
signaling, traffic engineering,, and path recovery.  MPLS-TP uses
GMPLS as the control plane for MPLS-TP LSPs and provides for
compatibility with MPLS.  The control plane for Pseudowires (PWs)
is also covered by this document.  Management plane functions such
as manual configuration and the initiation of LSP setup are out of
scope of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-mpls-tp-cp-framework-01.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-mpls-tp-cp-framework-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From curtis@occnc.com  Mon Mar 22 14:18:08 2010
Return-Path: <curtis@occnc.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E12683A6BB2 for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 14:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.332
X-Spam-Level: 
X-Spam-Status: No, score=-0.332 tagged_above=-999 required=5 tests=[AWL=-1.463, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x5vOAGAjRnG8 for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 14:18:08 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id E7C1E28C1FB for <ccamp@ietf.org>; Mon, 22 Mar 2010 14:15:09 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o2MLFQqW044792; Mon, 22 Mar 2010 17:15:26 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201003222115.o2MLFQqW044792@harbor.orleans.occnc.com>
To: ccamp@ietf.org
From: Curtis Villamizar <curtis@occnc.com>
Date: Mon, 22 Mar 2010 17:15:26 -0400
Sender: curtis@occnc.com
Subject: [CCAMP] draft-ietf-ccamp-oam-configuration-fwk-03
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 21:18:09 -0000

I have a few comments on draft-ietf-ccamp-oam-configuration-fwk-03

Most of my comments are general.

  1. The method suggested to change OAM parameters should be
     non-disruptive, and if possible including no loss of protection
     status.  The proposed mechanism seems to temporarily break the
     responsiveness of CC/CV during the transition period if a minor
     OAM parameter is changed.  Perhaps identifying OAM packets such
     as CC/CV according to an OAM configuration identifier would allow
     for the transition in a way that is similar to the transition of
     crypto keys where for an interim period two are recognized before
     the old is withdrawn.  For example, CC/CV at one rate with proper
     identification may allow working path to stay up.  CC/CV with a
     second rate make take over at any time, also identified and
     therefore at a known rate.  If either are being received the
     working path is assumed to be working.  The older of the OAM
     parameters can then be withdrawn leaving only the new parameters
     in place.  Management plane changes in particular take an
     eternity to perform compared to the restoration time
     requirements.

     This is either a missed OAM requirement, or not important (not
     missed, not a requirement), or accommodated by an alternate
     mechanism.

     Another way to accomplish the same thing would be creating a new
     LSP on the same path using make-before-break semantics.  If this
     is preferable, maybe it should be mentioned here.  OTOH -
     resignaling the LSP and in doing so coming up with a different
     LSP-id and set of labels is a lot of overhead for a parameter
     change.

     Another question - should a parameter change which is rejected
     take down the LSP?  As currently specified it does.

  2. Note: There does not seem to be any possibility of OAM leaking
     outside.  OAM is always received, evn if received and discarded
     and never forwarded.  Perhaps the paragraph describing this could
     be deleted or edited to reflect this.

  3. A requirement and framework document does not generally define
     the protocol mechanisms at the same time.  Either this document
     has to be edited to not claim to be a requirement and framework
     document, or the mechanism needs to be split off into another
     document.  If the WG goes with the former, then this document
     should be held to a higher standard as required by the IETF
     routing area (working code, interoperability).  The reason for
     this is a lot of problems are found in taking the step to working
     and interoperable code.  As it exists this is a base protocol
     specification, not a equirement and framework document.

  4. If a MIP is only desired at select points along the LSP, it would
     be better to extend the ERO.  If so, then this discussion of
     attribute flags bits goes away.  The ingress can elect to not use
     an LSP if the egress and appropriate set of midpoint LSR have
     filled in the RRO indicating that the OAM functionality is
     enabled.  The ERO would also have to be modified by MIP to
     indicate to the egress that they have been set up.

     The ERO/RRO might also be a better place to put this simple
     because SESSION_ATTRIBUTE bits and ADMIN_STATUS bits are in short
     supply and have limited potential semantics.

  5. A "reject object" containing a reason and the TLV being rejected
     would be preferable to a PathErr.  This is particularly true if
     resignaling a parameter.

  6. It might be better to put "lock" and "loopback" functionality in
     the control plane for PW and LSP or management plane rather than
     putting it in the data plane in the OAM packets.  We just had a
     brief discussion on setting loopback in the data plane using TTL
     to identify the node and having the TTL and data path change due
     to a segment protection status change (FRR being an example).

Minor:

@@ -760,6 +810,10 @@
              2                   Performance Monitoring/Loss (PM/Loss)
              3                   Performance Monitoring/Delay (PM/Delay)

+* The length is not specified.  As drawn this is a arbitrary length
+  integer containing one of the values 0..3.  A bitmap would be
+  preferable and that may be what was intended.

Last is a nit - there is a spelling error.

-   In general, two types of Maintenance Poits (MPs) can be
+   In general, two types of Maintenance Points (MPs) can be

Curtis

From curtis@occnc.com  Mon Mar 22 14:28:49 2010
Return-Path: <curtis@occnc.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26D643A67E1 for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 14:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.274
X-Spam-Level: 
X-Spam-Status: No, score=-0.274 tagged_above=-999 required=5 tests=[AWL=-1.405, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MXpyGaRB+JkA for <ccamp@core3.amsl.com>; Mon, 22 Mar 2010 14:28:48 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 44D413A68B6 for <ccamp@ietf.org>; Mon, 22 Mar 2010 14:28:44 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o2MLT1s0044905; Mon, 22 Mar 2010 17:29:01 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201003222129.o2MLT1s0044905@harbor.orleans.occnc.com>
To: ccamp@ietf.org
From: Curtis Villamizar <curtis@occnc.com>
Date: Mon, 22 Mar 2010 17:29:01 -0400
Sender: curtis@occnc.com
Subject: [CCAMP] draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-01, draft-ietf-ccamp-rsvp-te-eth-oam-ext-02, draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext-02
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 21:28:49 -0000

These all seem to be cases built on the *base protocol spec*
raft-ietf-ccamp-oam-configuration-fwk-03

As is this is not a unified OAM framework for the following reasons.

  1.  The concept of MD level is applied only to Ethernet.

  2.  If the IEEE/MEF concept of MD level is extended, the 8K ID space
      and simple 8 levels may not map directly.  It might be better to
      have a TP-MD that identifies a layer and then within an Ethernet
      sublayer idenfifies a 3-bit MD level and 13 bit MD ID.

      Ethernet in PW in Ethernet in PW in ... presents an interesting
      case.

  3.  Some of the requirements (PM, LM, DM, lock, loopback) are not
      covered by some of these three drafts.  Each draft should at the
      front indicate which of these requirements are addressed and
      which are omitted.

      This also allows a later draft to address the remaining
      requirements (such as a better way of doing loopback for LSP
      than TTL addressing).

Curtis


From wwwrun@rfc-editor.org  Mon Mar 22 23:16:24 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FB863A6896; Mon, 22 Mar 2010 23:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.43
X-Spam-Level: **
X-Spam-Status: No, score=2.43 tagged_above=-999 required=5 tests=[DNS_FROM_OPENWHOIS=2.431, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qExdjvjo5sg6; Mon, 22 Mar 2010 23:16:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 3657F3A67E7; Mon, 22 Mar 2010 23:16:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 16130E075E; Mon, 22 Mar 2010 23:16:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100323061642.16130E075E@rfc-editor.org>
Date: Mon, 22 Mar 2010 23:16:42 -0700 (PDT)
Cc: ccamp@ietf.org, rfc-editor@rfc-editor.org
Subject: [CCAMP] RFC 5787 on OSPFv2 Routing Protocols Extensions for Automatically Switched Optical Network (ASON) Routing
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 06:16:24 -0000

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

        
        RFC 5787

        Title:      OSPFv2 Routing Protocols Extensions for 
                    Automatically Switched Optical Network (ASON) Routing 
        Author:     D. Papadimitriou
        Status:     Experimental
        Date:       March 2010
        Mailbox:    dimitri.papadimitriou@alcatel-lucent.be
        Pages:      29
        Characters: 67247
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-gmpls-ason-routing-ospf-09.txt

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

The ITU-T has defined an architecture and requirements for operating
an Automatically Switched Optical Network (ASON).

The Generalized Multiprotocol Label Switching (GMPLS) protocol suite
is designed to provide a control plane for a range of network
technologies including optical networks such as time division
multiplexing (TDM) networks including SONET/SDH and Optical Transport
Networks (OTNs), and lambda switching optical networks.

The requirements for GMPLS routing to satisfy the requirements of
ASON routing, and an evaluation of existing GMPLS routing protocols
are provided in other documents.  This document defines extensions to
the OSPFv2 Link State Routing Protocol to meet the requirements for
routing in an ASON.

Note that this work is scoped to the requirements and evaluation
expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations
current when those documents were written.  Future extensions of
revisions of this work may be necessary if the ITU-T Recommendations
are revised or if new requirements are introduced into a revision of
RFC 4258.  This document defines an Experimental Protocol for the 
Internet community.

This document is a product of the Common Control and Measurement Plane Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

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

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

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


The RFC Editor Team
Association Management Solutions, LLC



From root@core3.amsl.com  Tue Mar 23 06:45:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id C8D2B3A6B5A; Tue, 23 Mar 2010 06:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100323134501.C8D2B3A6B5A@core3.amsl.com>
Date: Tue, 23 Mar 2010 06:45:01 -0700 (PDT)
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 13:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.


	Title           : GMPLS RSVP-TE Extensions for SONET/SDH and OTN OAM Configuration
	Author(s)       : A. Kern, A. Takacs
	Filename        : draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext-00.txt
	Pages           : 21
	Date            : 2010-03-23

GMPLS has been extended to support connection establishment in both
SONET/SDH [RFC4606] and OTN [RFC4328] networks.  However support for
the configuration of the supervision functions is not specified.
Both SONET/SDH and OTN implement supervision functions to qualify the
transported signals.  This document defines extensions to RSVP-TE for
SONET/SDH and OTN OAM configuration based on the OAM Configuration
Framework defined in [GMPLS-OAM-FWK].Requirements Language

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

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From Attila.Takacs@ericsson.com  Tue Mar 23 10:29:42 2010
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C3AB3A6CB3 for <ccamp@core3.amsl.com>; Tue, 23 Mar 2010 10:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.869
X-Spam-Level: 
X-Spam-Status: No, score=-2.869 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 VIR1--pz4v3r for <ccamp@core3.amsl.com>; Tue, 23 Mar 2010 10:29:41 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 967493A6BA6 for <ccamp@ietf.org>; Tue, 23 Mar 2010 10:29:39 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-8c-4ba8fa956040
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id FC.C3.23532.59AF8AB4; Tue, 23 Mar 2010 18:29:58 +0100 (CET)
Received: from ESESSCMS0355.eemea.ericsson.se ([169.254.2.93]) by esessmw0184.eemea.ericsson.se ([153.88.115.81]) with mapi; Tue, 23 Mar 2010 18:29:53 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: "curtis@occnc.com" <curtis@occnc.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Date: Tue, 23 Mar 2010 18:29:52 +0100
Thread-Topic: [CCAMP] draft-ietf-ccamp-oam-configuration-fwk-03
Thread-Index: AcrKBTksaDRO/f0ZSpu2HWQ9EaZOCgAoDzQg
Message-ID: <79F41BA1E9BF3C489375521EF8DDE23C12B1A66700@ESESSCMS0355.eemea.ericsson.se>
References: <201003222115.o2MLFQqW044792@harbor.orleans.occnc.com>
In-Reply-To: <201003222115.o2MLFQqW044792@harbor.orleans.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [CCAMP] draft-ietf-ccamp-oam-configuration-fwk-03
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 17:29:42 -0000

Hi Curtis,=20

Thank you for the comments!

>=20
> I have a few comments on draft-ietf-ccamp-oam-configuration-fwk-03
>=20
> Most of my comments are general.
>=20
>   1. The method suggested to change OAM parameters should be
>      non-disruptive, and if possible including no loss of protection
>      status.  The proposed mechanism seems to temporarily break the
>      responsiveness of CC/CV during the transition period if a minor
>      OAM parameter is changed.  Perhaps identifying OAM packets such
>      as CC/CV according to an OAM configuration identifier would allow
>      for the transition in a way that is similar to the transition of
>      crypto keys where for an interim period two are recognized before
>      the old is withdrawn.  For example, CC/CV at one rate with proper
>      identification may allow working path to stay up.  CC/CV with a
>      second rate make take over at any time, also identified and
>      therefore at a known rate.  If either are being received the
>      working path is assumed to be working.  The older of the OAM
>      parameters can then be withdrawn leaving only the new parameters
>      in place.  Management plane changes in particular take an
>      eternity to perform compared to the restoration time
>      requirements.
>

To allow two parameters to be recognised during reconfiguration is, I think=
, OAM technology and implementation dependant. If this is indeed supported =
by the underlying OAM technology then, re-signaling with the changed parame=
ters without clearing the OAM Alarms Enabled flag would actually result in =
the desired operation you described above.

=20
>      This is either a missed OAM requirement, or not important (not
>      missed, not a requirement), or accommodated by an alternate
>      mechanism.

If this is a requirement, it must be addressed by the specific OAM technolo=
gy and not in this document that deals with GMPLS CP aspects only.

>=20
>      Another way to accomplish the same thing would be creating a new
>      LSP on the same path using make-before-break semantics.  If this
>      is preferable, maybe it should be mentioned here.  OTOH -
>      resignaling the LSP and in doing so coming up with a different
>      LSP-id and set of labels is a lot of overhead for a parameter
>      change.
>=20
>      Another question - should a parameter change which is rejected
>      take down the LSP?  As currently specified it does.
>

My intention was to say the following...I will need to elaborate on this in=
 the text further, I admit.

Let us take as example the CC rate, now it is running at say 100ms. There a=
re two cases:

1) the initiator wants to change to a higher rate say 3.3ms.
In this case the remote-end may chose not to accept the value and suggest 1=
0ms instead. What should not be allowed trough is to suggest a lower rate t=
han the 100ms that is used currently. So say suggesting 1s should result in=
 an error and tear down.

2) the initiator wants to reduce the reate say to 1 sec. In this case I ass=
ume that the remote-end will have no problem to accept the new rate.

Do you agree with this?
=20
>   2. Note: There does not seem to be any possibility of OAM leaking
>      outside.  OAM is always received, evn if received and discarded
>      and never forwarded.  Perhaps the paragraph describing this could
>      be deleted or edited to reflect this.
>=20

Hmm, I would say that this may be technology specific too. In any case, cal=
ling out the setup of the sink function should not be an issue. In the case=
 the "sink" function in implicit for a technology there is no harm calling =
that explicitly out.


>   3. A requirement and framework document does not generally define
>      the protocol mechanisms at the same time.  Either this document
>      has to be edited to not claim to be a requirement and framework
>      document, or the mechanism needs to be split off into another
>      document.  If the WG goes with the former, then this document
>      should be held to a higher standard as required by the IETF
>      routing area (working code, interoperability).  The reason for
>      this is a lot of problems are found in taking the step to working
>      and interoperable code.  As it exists this is a base protocol
>      specification, not a equirement and framework document.

Point taken, will discuss with the chairs.

>=20
>   4. If a MIP is only desired at select points along the LSP, it would
>      be better to extend the ERO.  If so, then this discussion of
>      attribute flags bits goes away.  The ingress can elect to not use
>      an LSP if the egress and appropriate set of midpoint LSR have
>      filled in the RRO indicating that the OAM functionality is
>      enabled.  The ERO would also have to be modified by MIP to
>      indicate to the egress that they have been set up.
>=20
>      The ERO/RRO might also be a better place to put this simple
>      because SESSION_ATTRIBUTE bits and ADMIN_STATUS bits are in short
>      supply and have limited potential semantics.
>=20

Discussion is going in the context of:
http://tools.ietf.org/html/draft-kern-ccamp-rsvpte-hop-attributes-00
http://tools.ietf.org/html/draft-kern-ccamp-intermediate-node-config-00
=20


>   5. A "reject object" containing a reason and the TLV being rejected
>      would be preferable to a PathErr.  This is particularly true if
>      resignaling a parameter.

Ok, will consider.


>=20
>   6. It might be better to put "lock" and "loopback" functionality in
>      the control plane for PW and LSP or management plane rather than
>      putting it in the data plane in the OAM packets.  We just had a
>      brief discussion on setting loopback in the data plane using TTL
>      to identify the node and having the TTL and data path change due
>      to a segment protection status change (FRR being an example).
>=20

Admin Status bits in the context of recovery signalling are defined in othe=
r documents for Lockout, Testing and Administratively Down that can be used=
 here as well.=20


> Minor:
>=20
> @@ -760,6 +810,10 @@
>               2                   Performance Monitoring/Loss=20
> (PM/Loss)
>               3                   Performance=20
> Monitoring/Delay (PM/Delay)
>=20
> +* The length is not specified.  As drawn this is a arbitrary length
> +  integer containing one of the values 0..3.  A bitmap would be
> +  preferable and that may be what was intended.
>=20

Intension is to have a bitmap. Will clarify.

> Last is a nit - there is a spelling error.
>=20
> -   In general, two types of Maintenance Poits (MPs) can be
> +   In general, two types of Maintenance Points (MPs) can be
>=20
> Curtis

Thanks,
Attila

> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
> =

From Attila.Takacs@ericsson.com  Tue Mar 23 10:57:08 2010
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AC103A6C87 for <ccamp@core3.amsl.com>; Tue, 23 Mar 2010 10:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.169
X-Spam-Level: 
X-Spam-Status: No, score=-4.169 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 t8SeO4HMQfiy for <ccamp@core3.amsl.com>; Tue, 23 Mar 2010 10:57:07 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 5B7203A6979 for <ccamp@ietf.org>; Tue, 23 Mar 2010 10:57:07 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-39-4ba901054ec3
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id B6.F5.23532.50109AB4; Tue, 23 Mar 2010 18:57:25 +0100 (CET)
Received: from ESESSCMS0355.eemea.ericsson.se ([169.254.2.93]) by esessmw0184.eemea.ericsson.se ([153.88.115.81]) with mapi; Tue, 23 Mar 2010 18:57:05 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: "curtis@occnc.com" <curtis@occnc.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Date: Tue, 23 Mar 2010 18:57:04 +0100
Thread-Topic: [CCAMP] draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-01, draft-ietf-ccamp-rsvp-te-eth-oam-ext-02, draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext-02
Thread-Index: AcrKBsCtqn/wjRXyRrmfKGQ7nMtI5wAp81rg
Message-ID: <79F41BA1E9BF3C489375521EF8DDE23C12B1A66720@ESESSCMS0355.eemea.ericsson.se>
References: <201003222129.o2MLT1s0044905@harbor.orleans.occnc.com>
In-Reply-To: <201003222129.o2MLT1s0044905@harbor.orleans.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [CCAMP] draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-01, draft-ietf-ccamp-rsvp-te-eth-oam-ext-02, draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext-02
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 17:57:08 -0000

Hi Curtis,=20

> These all seem to be cases built on the *base protocol spec*
> raft-ietf-ccamp-oam-configuration-fwk-03
>=20
> As is this is not a unified OAM framework for the following reasons.


It is a unified OAM *configuration* framework. It provides the procedures a=
nd placeholders for OAM entity/function configuration via RSVP-TE.=20

>=20
>   1.  The concept of MD level is applied only to Ethernet.
>=20
>   2.  If the IEEE/MEF concept of MD level is extended, the 8K ID space
>       and simple 8 levels may not map directly.  It might be better to
>       have a TP-MD that identifies a layer and then within an Ethernet
>       sublayer idenfifies a 3-bit MD level and 13 bit MD ID.
>=20
>       Ethernet in PW in Ethernet in PW in ... presents an interesting
>       case.

Actual details are kept technology specific, since OAM solutions evolve ind=
ependently for each of the technologies.=20

>=20
>   3.  Some of the requirements (PM, LM, DM, lock, loopback) are not
>       covered by some of these three drafts.  Each draft should at the
>       front indicate which of these requirements are addressed and
>       which are omitted.
>=20
>       This also allows a later draft to address the remaining
>       requirements (such as a better way of doing loopback for LSP
>       than TTL addressing).

Ok, agreed.

>=20
> Curtis
>=20

Thanks,
Attila


> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
> =

From Attila.Takacs@ericsson.com  Tue Mar 23 11:02:07 2010
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CC593A69C6; Tue, 23 Mar 2010 11:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.819
X-Spam-Level: 
X-Spam-Status: No, score=-2.819 tagged_above=-999 required=5 tests=[AWL=-1.350, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JIMksA1Myu+M; Tue, 23 Mar 2010 11:02:06 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 3B2093A690F; Tue, 23 Mar 2010 11:01:00 -0700 (PDT)
X-AuditID: c1b4fb39-b7b85ae000005cbc-ec-4ba901eed9bd
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 5C.B3.23740.EE109AB4; Tue, 23 Mar 2010 19:01:18 +0100 (CET)
Received: from ESESSCMS0355.eemea.ericsson.se ([169.254.2.93]) by esessmw0184.eemea.ericsson.se ([153.88.115.81]) with mapi; Tue, 23 Mar 2010 19:01:17 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Tue, 23 Mar 2010 19:01:16 +0100
Thread-Topic: Protection Object extension in draft-takacs-ccamp-revertive-ps
Thread-Index: AcrKstVTDYoCwdTdQtiZftTXpuOB4A==
Message-ID: <79F41BA1E9BF3C489375521EF8DDE23C12B1A66721@ESESSCMS0355.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: [CCAMP] Protection Object extension in draft-takacs-ccamp-revertive-ps
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 18:02:07 -0000

Hi all,

We have a document in CCAMP that suggest to extend the Protection Object to=
 carry sub-TLVs: ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ta=
kacs-ccamp-revertive-ps-04.txt

This would allow to configure protection timers and revertive operation for=
 protection mechanisms that run independently from the control plane. This =
has been identified in MPLS-TP Control Plane Framework as needed extension =
to fulfill TP requirements.

Please check, your comments are welcome!
Thanks,
Attila=

From hejia@huawei.com  Tue Mar 23 11:36:37 2010
Return-Path: <hejia@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E7543A6D0D; Tue, 23 Mar 2010 11:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.236
X-Spam-Level: ***
X-Spam-Status: No, score=3.236 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEhGSolrhGQ5; Tue, 23 Mar 2010 11:36:36 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 673D63A6CBA; Tue, 23 Mar 2010 11:36:36 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZQ00I7CZP9WR@szxga03-in.huawei.com>; Wed, 24 Mar 2010 02:36:45 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZQ00M9JZP9C8@szxga03-in.huawei.com>; Wed, 24 Mar 2010 02:36:45 +0800 (CST)
Received: from hejia (dhcp-wireless-open-abg-25-97.meeting.ietf.org [130.129.25.97]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KZQ008JJZOWOU@szxml01-in.huawei.com>; Wed, 24 Mar 2010 02:36:45 +0800 (CST)
Date: Wed, 24 Mar 2010 02:36:33 +0800
From: hejia <hejia@huawei.com>
To: Attila Takacs <Attila.Takacs@ericsson.com>, mpls@ietf.org, mpls-tp@ietf.org
Message-id: <7803FDA0040642F891804AC40662AD02@hejia>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <79F41BA1E9BF3C489375521EF8DDE23C12B1A66721@ESESSCMS0355.eemea.ericsson.se>
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] Protection Object extension indraft-takacs-ccamp-revertive-ps
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 18:36:37 -0000

Hi Attila,

Is the draft specific for MPLS-TP or a generalized configuration framework 
for ps just like what we do for OAM configuration currently?

B.R.
Jia


----- Original Message ----- 
From: "Attila Takacs" <Attila.Takacs@ericsson.com>
To: <mpls@ietf.org>; <mpls-tp@ietf.org>
Cc: <ccamp@ietf.org>
Sent: Wednesday, March 24, 2010 2:01 AM
Subject: [mpls-tp] Protection Object extension 
indraft-takacs-ccamp-revertive-ps


> Hi all,
>
> We have a document in CCAMP that suggest to extend the Protection Object 
> to carry sub-TLVs: 
> ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-takacs-ccamp-revertive-ps-04.txt
>
> This would allow to configure protection timers and revertive operation 
> for protection mechanisms that run independently from the control plane. 
> This has been identified in MPLS-TP Control Plane Framework as needed 
> extension to fulfill TP requirements.
>
> Please check, your comments are welcome!
> Thanks,
> Attila
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> 



From Attila.Takacs@ericsson.com  Tue Mar 23 12:04:51 2010
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B4B93A68B4; Tue, 23 Mar 2010 12:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[AWL=-0.900, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P2rGQT0F1DTY; Tue, 23 Mar 2010 12:04:50 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id CDE103A6841; Tue, 23 Mar 2010 12:04:49 -0700 (PDT)
X-AuditID: c1b4fb39-b7b85ae000005cbc-6b-4ba910e3c9fb
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id DC.E6.23740.3E019AB4; Tue, 23 Mar 2010 20:05:07 +0100 (CET)
Received: from ESESSCMS0355.eemea.ericsson.se ([169.254.2.93]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Tue, 23 Mar 2010 20:04:49 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: hejia <hejia@huawei.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Tue, 23 Mar 2010 20:04:47 +0100
Thread-Topic: [CCAMP] [mpls-tp] Protection Object extension indraft-takacs-ccamp-revertive-ps
Thread-Index: AcrKt9L/l19rM38mTYKYU+0In3YNGgAA7taA
Message-ID: <79F41BA1E9BF3C489375521EF8DDE23C12B1A66754@ESESSCMS0355.eemea.ericsson.se>
References: <79F41BA1E9BF3C489375521EF8DDE23C12B1A66721@ESESSCMS0355.eemea.ericsson.se> <7803FDA0040642F891804AC40662AD02@hejia>
In-Reply-To: <7803FDA0040642F891804AC40662AD02@hejia>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [CCAMP] [mpls-tp] Protection Object extension indraft-takacs-ccamp-revertive-ps
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 19:04:51 -0000

Hi Jia,
It is a general extension of the Protection Object which will be useful to =
meet TP requirements too.
Attila=20

> -----Original Message-----
> From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org]=20
> On Behalf Of hejia
> Sent: Tuesday, March 23, 2010 7:37 PM
> To: Attila Takacs; mpls@ietf.org; mpls-tp@ietf.org
> Cc: ccamp@ietf.org
> Subject: Re: [CCAMP] [mpls-tp] Protection Object extension=20
> indraft-takacs-ccamp-revertive-ps
>=20
> Hi Attila,
>=20
> Is the draft specific for MPLS-TP or a generalized=20
> configuration framework for ps just like what we do for OAM=20
> configuration currently?
>=20
> B.R.
> Jia
>=20
>=20
> ----- Original Message -----
> From: "Attila Takacs" <Attila.Takacs@ericsson.com>
> To: <mpls@ietf.org>; <mpls-tp@ietf.org>
> Cc: <ccamp@ietf.org>
> Sent: Wednesday, March 24, 2010 2:01 AM
> Subject: [mpls-tp] Protection Object extension=20
> indraft-takacs-ccamp-revertive-ps
>=20
>=20
> > Hi all,
> >
> > We have a document in CCAMP that suggest to extend the Protection=20
> > Object to carry sub-TLVs:
> >=20
> ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-takacs-ccamp-r
> > evertive-ps-04.txt
> >
> > This would allow to configure protection timers and revertive=20
> > operation for protection mechanisms that run independently=20
> from the control plane.
> > This has been identified in MPLS-TP Control Plane Framework=20
> as needed=20
> > extension to fulfill TP requirements.
> >
> > Please check, your comments are welcome!
> > Thanks,
> > Attila
> > _______________________________________________
> > mpls-tp mailing list
> > mpls-tp@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls-tp
> >=20
>=20
>=20
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
> =

From elisa.bellagamba@ericsson.com  Tue Mar 23 13:59:58 2010
Return-Path: <elisa.bellagamba@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 066793A69A6; Tue, 23 Mar 2010 13:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8CnaxHT-m3z; Tue, 23 Mar 2010 13:59:57 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 3D42C3A6937; Tue, 23 Mar 2010 13:59:54 -0700 (PDT)
X-AuditID: c1b4fb39-b7b85ae000005cbc-49-4ba92bdced2a
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 41.2B.23740.CDB29AB4; Tue, 23 Mar 2010 22:00:12 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.2.100]) by esessmw0184.eemea.ericsson.se ([153.88.115.81]) with mapi; Tue, 23 Mar 2010 22:00:11 +0100
From: Elisa Bellagamba <elisa.bellagamba@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Tue, 23 Mar 2010 21:59:19 +0100
Thread-Topic: [mpls-tp] [CCAMP] [mpls] WG Last Call on draft-ietf-mpls-tp-ach-tlv-02.txt
Thread-Index: AcrInvvarJW0ZWp4QdG73A0E3lRH9gCLGfBQ
Message-ID: <55EA962132DCC84286EB4429B9CA773A1CF86F56A8@ESESSCMS0356.eemea.ericsson.se>
References: <20100305191502.17B8F28C0F0@core3.amsl.com> <4B9290D1.2080902@pi.nu> <787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com> <4BA5783A.9070307@cisco.com> <77ead0ec1003201933m8c5733s9fc0ec509d505009@mail.gmail.com>
In-Reply-To: <77ead0ec1003201933m8c5733s9fc0ec509d505009@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, CCAMP <ccamp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls-tp] [mpls] WG Last Call on	draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 20:59:58 -0000

Hello,

>From draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-02:

2.4.  MEP and MIP Identifier
   When sending LSP-Ping packets using ACH, there MAY be a need to
   identify the maintenance end point (MEP) and/or the maintenance
   intermediate point (MIP) being monitored.  The MEP/MIP identifiers
   defined in [I-D.swallow-mpls-tp-identifiers] can be carried in the
   ACH TLVs [I-D.ietf-mpls-tp-ach-tlv] for identification.

But in draft-ietf-mpls-tp-ach-tlv-01 there are no sections specifying the M=
EP-ID.

I've noticed the problem because I was checking the configuration parameter=
s needed for MPLS OAM configuration via LSP-ping for draft-ietf-ccamp-rsvp-=
te-mpls-tp-oam-ext-01 and, since I didn't find anything for MEP-ID, I defin=
ed a new TLV to be put in the LSP ping message. But I think the best place =
would be the Ach TLV.

If you agree, we could move section "3.7. MPLS OAM SOURCE MEP-ID TLV for LS=
P Ping" of draft draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-01 to draft-ietf-=
mpls-tp-ach-tlv-01.=20

Thanks,
Elisa




-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf =
Of Vishwas Manral
Sent: den 20 mars 2010 19:33
To: stbryant@cisco.com
Cc: CCAMP; mpls-tp@ietf.org; pwe3@ietf.org; mpls@ietf.org
Subject: Re: [mpls-tp] [CCAMP] [mpls] WG Last Call on draft-ietf-mpls-tp-ac=
h-tlv-02.txt

Hi Stewart,

I agree we could allocate 8 numbers.

Thanks,
Vishwas

On Sat, Mar 20, 2010 at 6:36 PM, Stewart Bryant <stbryant@cisco.com> wrote:
> We could allocate a small number - say 4 or 8 for experimental purposes.
>
> What do others think?
>
> -Stewart
>
>
> Greg Mirsky wrote:
>>
>> Dear Authors and All,
>> my question on how the Type range control been organized. Is the whole
>> range from 0x0000 through 0xffff controlled by IANA? Would we like to le=
ave
>> some smaller range out for experimental use?
>>
>> Regards,
>> Greg
>>
>> On Sat, Mar 6, 2010 at 9:28 AM, Loa Andersson <loa@pi.nu
>> <mailto:loa@pi.nu>> wrote:
>>
>> =A0 =A0All,
>>
>> =A0 =A0this is to start a three week MPLS working group last call on
>>
>> =A0 =A0http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-ach-tlv-02=
.txt
>>
>> =A0 =A0Please review and send your comments only to the mpls-tp@ietf.org
>> =A0 =A0<mailto:mpls-tp@ietf.org>
>> =A0 =A0mailing list.
>>
>> =A0 =A0The working group last call end March 28, 2010.
>>
>> =A0 =A0Loa and George
>>
>>
>> =A0 =A0--
>>
>> =A0 =A0Loa Andersson =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ema=
il:
>> =A0 =A0loa.andersson@ericsson.com <mailto:loa.andersson@ericsson.com>
>> =A0 =A0Sr Strategy and Standards Manager =A0 =A0 =A0 =A0 =A0 =A0loa@pi.n=
u
>> =A0 =A0<mailto:loa@pi.nu>
>> =A0 =A0Ericsson Inc =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0p=
hone: +46 10 717 52 13
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0+46 767 72 92 13
>> =A0 =A0_______________________________________________
>> =A0 =A0mpls mailing list
>> =A0 =A0mpls@ietf.org <mailto:mpls@ietf.org>
>> =A0 =A0https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>
>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp

From dongjie_dj@huawei.com  Tue Mar 23 19:02:51 2010
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC8473A63D3; Tue, 23 Mar 2010 19:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.235
X-Spam-Level: ***
X-Spam-Status: No, score=3.235 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 Rx+2VJbBIdL0; Tue, 23 Mar 2010 19:02:51 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id DE1643A67F0; Tue, 23 Mar 2010 19:02:50 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZR00HQOKD0CF@szxga01-in.huawei.com>; Wed, 24 Mar 2010 10:03:00 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZR00DXCKD0OB@szxga01-in.huawei.com>; Wed, 24 Mar 2010 10:03:00 +0800 (CST)
Received: from JYS5040913q (dhcp-wireless-open-abg-25-122.meeting.ietf.org [130.129.25.122]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KZR00LMHKCXVM@szxml01-in.huawei.com>; Wed, 24 Mar 2010 10:03:00 +0800 (CST)
Date: Wed, 24 Mar 2010 10:02:50 +0800
From: Jie Dong <dongjie_dj@huawei.com>
To: mpls@ietf.org, ccamp@ietf.org
Message-id: <FA657688102F45F0AE8E3C4AFF6824FE@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Subject: [CCAMP] Discussion on PLR designation in TE FRR
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 02:02:51 -0000

Dear all,

During presentation in ccamp session this morning, we've received valuable comments, and we'd like to have more discussion in the mailing list. 

Since GMPLS segment recovery allows operators explicitly specify the start node and end node of protection paths, we think it would be beneficial to provide similar function in TE FRR.

We solicit feedbacks on this requirement, and we can also discuss in which way we should extend the signaling.

A good comment we got is maybe we can use some way to collect information about node/link reliability, and based on this information, operators can decide which nodes should perform as PLRs and whether node protection or link protection is needed. We will consider this in future work.

More comments are welcome.


Best Regards,
Jie

From wwwrun@rfc-editor.org  Tue Mar 23 19:55:05 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E2693A699D; Tue, 23 Mar 2010 19:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.726
X-Spam-Level: 
X-Spam-Status: No, score=-0.726 tagged_above=-999 required=5 tests=[AWL=0.744,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39BAFcYMNkPE; Tue, 23 Mar 2010 19:55:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 1E86E3A69A8; Tue, 23 Mar 2010 19:55:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 398F8E0777; Tue, 23 Mar 2010 19:55:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100324025524.398F8E0777@rfc-editor.org>
Date: Tue, 23 Mar 2010 19:55:24 -0700 (PDT)
Cc: ccamp@ietf.org, rfc-editor@rfc-editor.org
Subject: [CCAMP] RFC 5828 on Generalized Multiprotocol Label Switching (GMPLS) Ethernet Label Switching Architecture and Framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 02:55:05 -0000

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

        
        RFC 5828

        Title:      Generalized Multiprotocol Label Switching (GMPLS) 
                    Ethernet Label Switching Architecture and Framework 
        Author:     D. Fedyk, L. Berger,
                    L. Andersson
        Status:     Informational
        Date:       March 2010
        Mailbox:    donald.fedyk@alcatel-lucent.com, 
                    lberger@labn.net, 
                    loa.andersson@ericsson.com
        Pages:      20
        Characters: 46396
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-gmpls-ethernet-arch-09.txt

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

There has been significant recent work in increasing the
capabilities of Ethernet switches and Ethernet forwarding
models.  As a consequence, the role of Ethernet is rapidly expanding
into "transport networks" that previously were the domain of other
technologies such as Synchronous Optical Network (SONET) / Synchronous 
Digital Hierarchy (SDH), Time-Division Multiplexing (TDM), and 
Asynchronous Transfer Mode (ATM).  This document defines an architecture 
and framework for a Generalized-MPLS-based control plane for Ethernet in 
this "transport network" capacity.  GMPLS has already been specified for 
similar technologies.  Some additional extensions to the GMPLS control 
plane are needed, and this document provides a framework for these 
extensions.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

This document is a product of the Common Control and Measurement Plane Working Group of the IETF.


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC



From vivien.sterling@gmail.com  Wed Mar 24 01:20:39 2010
Return-Path: <vivien.sterling@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE3343A686D; Wed, 24 Mar 2010 01:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 4k9eh2JfEm8C; Wed, 24 Mar 2010 01:20:37 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 8A13F3A67F7; Wed, 24 Mar 2010 01:20:18 -0700 (PDT)
Received: by pvh1 with SMTP id 1so3764438pvh.31 for <multiple recipients>; Wed, 24 Mar 2010 01:20:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=QqlOvj2ZGxG0BArIS37ZwQBaldEs5f1/W4Uj/2yHuWw=; b=UT71WgaK/OMrc5/AGAKJoV1wIfJH59YHsB34pxMm7Y+rTaqJZO6RFwkNci+iLVFIn8 K7THs2Ipx0iTJldz3GP4rPtocRurXHJihIwUeNyGDH4lIt5JiR71JgmElfzXkbnVGw0/ IJOvejj2EjTVxsGXCWk05DxdVs/JUSu5563rI=
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=wuv4p1uLkt0N4hHIqwt5icxqcBWgvcLmFU+K1gR7cgggPRedYEVdWZV8hMVYPQiD5t Yg7EvPBUoaCWbRaob2HzhQOF/twwZHaDWEnKG7+8dGbSilrW4rknwZBxEMuazGBefhRF 06obfdieismukTwD2PPNIteOmx28K4Q7eulBg=
MIME-Version: 1.0
Received: by 10.115.66.33 with SMTP id t33mr1805549wak.199.1269418835819; Wed,  24 Mar 2010 01:20:35 -0700 (PDT)
In-Reply-To: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com>
Date: Wed, 24 Mar 2010 16:20:35 +0800
Message-ID: <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>
From: Vivien Sterling <vivien.sterling@gmail.com>
To: CCAMP@ietf.org, mpls@ietf.org, mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=0016e64ce5e8c7bbc20482879a97
Subject: [CCAMP] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 08:20:39 -0000

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

Dear Experts,

I'm surprised to find the term "PSC" used in this draft. I suppose the
authors are talking about data plane not control plane, right? Isn't PSC in
GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(

-- 
Cheers,
Vivien

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

<div>Dear Experts,</div>
<div>=A0</div>
<div>I&#39;m surprised to find the term &quot;PSC&quot; used in this draft.=
 I=A0suppose the authors are talking about data plane=A0not control plane, =
right? Isn&#39;t PSC=A0in GMPLS=A0elaborated as &quot;Packet Switch Capable=
&quot;=A0?=A0It&#39;s confusing :-(</div>

<div><br>-- <br>Cheers,<br>Vivien<br></div>

--0016e64ce5e8c7bbc20482879a97--

From Alexander.Vainshtein@ecitele.com  Wed Mar 24 01:30:10 2010
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E09F93A676A; Wed, 24 Mar 2010 01:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 rCw54SvpBfBM; Wed, 24 Mar 2010 01:30:06 -0700 (PDT)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 43D473A67F7; Wed, 24 Mar 2010 01:30:04 -0700 (PDT)
X-AuditID: 93eaf2e7-b7b62ae000003814-f5-4ba9cb734c39
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id F2.90.14356.37BC9AB4; Wed, 24 Mar 2010 10:21:07 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 24 Mar 2010 10:30:23 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Vivien Sterling <vivien.sterling@gmail.com>
Date: Wed, 24 Mar 2010 10:30:22 +0200
Thread-Topic: [mpls] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrLKvolOu7lBQSqT1ut2i2ehMfvzAAADAyQ
Message-ID: <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com> <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>
In-Reply-To: <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A3C5DF08D38B6049839A6F553B331C76C1078FB66EILPTMAIL02eci_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "CCAMP@ietf.org" <CCAMP@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 08:30:11 -0000

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

Vivien and all,
AFAIK, PSC stands for "Protection State Coordination" in the MPLS-TP parlan=
ce (see MPLS-TP Survivability Framework<http://datatracker.ietf.org/doc/dra=
ft-ietf-mpls-tp-survive-fwk/>) - a new fancy name for what has been known a=
s "APS Protocol" in SONET/SDH.

As you've noted, it has a completely different meaning in GMPLS.

Since GMPLS is going to be used with MPLS-TP, double usage of this acronym =
looks highly problematic.

Regards,
     Sasha

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Viv=
ien Sterling
Sent: Wednesday, March 24, 2010 10:21 AM
To: CCAMP@ietf.org; mpls@ietf.org; mpls-tp@ietf.org
Subject: [mpls] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01

Dear Experts,

I'm surprised to find the term "PSC" used in this draft. I suppose the auth=
ors are talking about data plane not control plane, right? Isn't PSC in GMP=
LS elaborated as "Packet Switch Capable" ? It's confusing :-(

--
Cheers,
Vivien

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Vivien and all,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>AFAIK, PSC stands for &#8220;Protection State Coordination&#=
8221;
in the MPLS-TP parlance (see <a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-survive-fwk/">MP=
LS-TP Survivability
Framework</a>) &#8211; a new fancy name for what has been known as &#8220;A=
PS
Protocol&#8221; in SONET/SDH.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>As you&#8217;ve noted, it has a completely different meaning=
 in
GMPLS.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Since GMPLS is going to be used with MPLS-TP, double usage o=
f
this acronym looks highly problematic.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

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

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b>On Behalf Of </b>Vi=
vien
Sterling<br>
<b>Sent:</b> Wednesday, March 24, 2010 10:21 AM<br>
<b>To:</b> CCAMP@ietf.org; mpls@ietf.org; mpls-tp@ietf.org<br>
<b>Subject:</b> [mpls] Term &quot;PSC&quot; in
draft-ietf-mpls-tp-linear-protection-01<o:p></o:p></span></p>

</div>

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

<div>

<p class=3DMsoNormal>Dear Experts,<o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>I'm surprised to find the term &quot;PSC&quot; used in=
 this
draft. I&nbsp;suppose the authors are talking about data plane&nbsp;not con=
trol
plane, right? Isn't PSC&nbsp;in GMPLS&nbsp;elaborated as &quot;Packet Switc=
h
Capable&quot;&nbsp;?&nbsp;It's confusing :-(<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><br>
-- <br>
Cheers,<br>
Vivien<o:p></o:p></p>

</div>

</div>

</body>

</html>

--_000_A3C5DF08D38B6049839A6F553B331C76C1078FB66EILPTMAIL02eci_--

From vivien.sterling@gmail.com  Wed Mar 24 02:26:57 2010
Return-Path: <vivien.sterling@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A65B3A69C6; Wed, 24 Mar 2010 02:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.387
X-Spam-Level: 
X-Spam-Status: No, score=0.387 tagged_above=-999 required=5 tests=[AWL=1.855,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 YzvMljOEMvEI; Wed, 24 Mar 2010 02:26:56 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 9CDCF3A6A6B; Wed, 24 Mar 2010 02:26:49 -0700 (PDT)
Received: by pwi10 with SMTP id 10so3877105pwi.31 for <multiple recipients>; Wed, 24 Mar 2010 02:27:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=PY2zqZuzzd53oNpdRv93vOM/8aoudGTkd7e6F5AOciI=; b=NReRxkVtIEfXHv08VqvkxkpIemQc1BGh4Efqfez9xh6F0EOySehr5n378IcW7JS9Fs veZ2oOqPYVMfjb7HtMTAqpcqCPjpt2EYjUmQS1Z6jUQ3SdmBqbqWDFDLRdP/2rGZstQE g3/HLY94Axg7CmZaPCjv6X4Al/O0WRGoMoqBA=
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=TgoFp55gI5H41YLPMcgyu7zb0+iKSaoDclraTJX7QJCqjE8Aae9lgnz5J9jTgRcxJa p4C9BUXWls4Uq1+kJdDChynEX03TDDsTcoTCiIMaKGUq1Nl6WYYLb4vjCx5BAkrdChHS lMmL0C6kChlJ2bQLN1hfA4Ja97gg17vquvzBc=
MIME-Version: 1.0
Received: by 10.115.64.6 with SMTP id r6mr4066275wak.226.1269422826165; Wed,  24 Mar 2010 02:27:06 -0700 (PDT)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com> <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com>
Date: Wed, 24 Mar 2010 17:27:06 +0800
Message-ID: <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com>
From: Vivien Sterling <vivien.sterling@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: multipart/alternative; boundary=0016e64ca4609f9599048288887d
Cc: "mpls@ietf.org" <mpls@ietf.org>, "CCAMP@ietf.org" <CCAMP@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 09:26:57 -0000

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

Sasha,

Right. It causes more confusion when GMPLS is used with MPLS-TP.
Could you share more information about the relationship between "PSC" and
"APS protocol" ? Are they exactly the same with only the different naming?
If so, I don't see any good of giving "a new fancy name". Anyway, I might b=
e
out of fashion ;-)

Cheers,
Vivien

2010/3/24 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>

>  Vivien and all,
>
> AFAIK, PSC stands for =93Protection State Coordination=94 in the MPLS-TP
> parlance (see MPLS-TP Survivability Framework<http://datatracker.ietf.org=
/doc/draft-ietf-mpls-tp-survive-fwk/>)
> =96 a new fancy name for what has been known as =93APS Protocol=94 in SON=
ET/SDH.
>
>
>
> As you=92ve noted, it has a completely different meaning in GMPLS.
>
>
>
> Since GMPLS is going to be used with MPLS-TP, double usage of this acrony=
m
> looks highly problematic.
>
>
>
> Regards,
>
>      Sasha
>
>
>
> *From:* mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On Behalf O=
f
> *Vivien Sterling
> *Sent:* Wednesday, March 24, 2010 10:21 AM
> *To:* CCAMP@ietf.org; mpls@ietf.org; mpls-tp@ietf.org
> *Subject:* [mpls] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01
>
>
>
> Dear Experts,
>
>
>
> I'm surprised to find the term "PSC" used in this draft. I suppose the
> authors are talking about data plane not control plane, right? Isn't PSC =
in
> GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(
>
>
> --
> Cheers,
> Vivien
>



--=20
Cheers,
Vivien

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

<div>Sasha,</div>
<div>=A0</div>
<div>Right. It causes more confusion when GMPLS is used=A0with MPLS-TP.=A0<=
/div>
<div>Could you share more information about the relationship between &quot;=
PSC&quot; and &quot;APS protocol&quot; ? Are they exactly the same with onl=
y the different naming? If so, I don&#39;t see any=A0good of giving=A0&quot=
;a=A0new fancy=A0name&quot;. Anyway, I might be out of=A0fashion=A0;-)</div=
>

<div>=A0</div>
<div>Cheers,</div>
<div>Vivien<br><br></div>
<div class=3D"gmail_quote">2010/3/24 Alexander Vainshtein <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshte=
in@ecitele.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">Vivi=
en and all,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">AFAI=
K, PSC stands for =93Protection State Coordination=94 in the MPLS-TP parlan=
ce (see <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-survi=
ve-fwk/" target=3D"_blank">MPLS-TP Survivability Framework</a>) =96 a new f=
ancy name for what has been known as =93APS Protocol=94 in SONET/SDH.</span=
></p>

<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">=A0<=
/span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">As y=
ou=92ve noted, it has a completely different meaning in GMPLS.</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">=A0<=
/span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">Sinc=
e GMPLS is going to be used with MPLS-TP, double usage of this acronym look=
s highly problematic.</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">=A0<=
/span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">Rega=
rds,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">=A0=
=A0=A0=A0 Sasha</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">=A0<=
/span></p>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b=
5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: mediu=
m none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class=3D"MsoNormal"><b><span style=3D"FONT-SIZE: 10pt">From:</span></b><=
span style=3D"FONT-SIZE: 10pt"> <a href=3D"mailto:mpls-bounces@ietf.org" ta=
rget=3D"_blank">mpls-bounces@ietf.org</a> [mailto:<a href=3D"mailto:mpls-bo=
unces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</a>] <b>On Behalf O=
f </b>Vivien Sterling<br>
<b>Sent:</b> Wednesday, March 24, 2010 10:21 AM<br><b>To:</b> <a href=3D"ma=
ilto:CCAMP@ietf.org" target=3D"_blank">CCAMP@ietf.org</a>; <a href=3D"mailt=
o:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>; <a href=3D"mailto:mpl=
s-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.org</a><br>
<b>Subject:</b> [mpls] Term &quot;PSC&quot; in draft-ietf-mpls-tp-linear-pr=
otection-01</span></p></div>
<div>
<div></div>
<div class=3D"h5">
<p class=3D"MsoNormal">=A0</p>
<div>
<p class=3D"MsoNormal">Dear Experts,</p></div>
<div>
<p class=3D"MsoNormal">=A0</p></div>
<div>
<p class=3D"MsoNormal">I&#39;m surprised to find the term &quot;PSC&quot; u=
sed in this draft. I=A0suppose the authors are talking about data plane=A0n=
ot control plane, right? Isn&#39;t PSC=A0in GMPLS=A0elaborated as &quot;Pac=
ket Switch Capable&quot;=A0?=A0It&#39;s confusing :-(</p>
</div>
<div>
<p class=3D"MsoNormal"><br>-- <br>Cheers,<br>Vivien</p></div></div></div></=
div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Cheers,<br>Vi=
vien<br>

--0016e64ca4609f9599048288887d--

From Cecil.Byles@interoute.com  Wed Mar 24 02:49:14 2010
Return-Path: <Cecil.Byles@interoute.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60A7B3A6A41; Wed, 24 Mar 2010 02:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.132
X-Spam-Level: 
X-Spam-Status: No, score=0.132 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, EXTRA_MPART_TYPE=1, GB_I_LETTER=-2, 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 Djf-ZWh2hofV; Wed, 24 Mar 2010 02:49:10 -0700 (PDT)
Received: from mail1.interoute.com (mail1.interoute.com [89.202.186.60]) by core3.amsl.com (Postfix) with ESMTP id 10AF43A6925; Wed, 24 Mar 2010 02:49:08 -0700 (PDT)
Received: from ukex01.interoute.com ([172.31.149.70]) by mail1.interoute.com with Microsoft SMTPSVC(7.0.6001.18000);  Wed, 24 Mar 2010 10:49:28 +0100
Received: from PREX22.interoute.com ([172.31.149.20]) by ukex01.interoute.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 24 Mar 2010 10:49:24 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01CACB37.491CE006"
Date: Wed, 24 Mar 2010 10:49:21 +0100
Message-ID: <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>
In-Reply-To: <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrLNG31FjIVEjC5TGK4ZVr9JRR1IAAAAzJw
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com><8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com><A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com>
From: "Cecil Byles" <Cecil.Byles@interoute.com>
To: "Vivien Sterling" <vivien.sterling@gmail.com>, "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 24 Mar 2010 09:49:24.0533 (UTC) FILETIME=[4934FE50:01CACB37]
X-Mailman-Approved-At: Wed, 24 Mar 2010 08:13:30 -0700
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 09:49:14 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CACB37.491CE006
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01CACB37.491CE006"


------_=_NextPart_002_01CACB37.491CE006
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
Can I therefore also asked how PSC "Protection State Coordination" in
the MPLS-TP parlance align with ITU-T 808.1 recommendation that "defines
the generic functional models, characteristics and processes associated
with various linear protection schemes for connection-oriented layer
networks; e.g., Optical Transport Networks (OTN), Synchronous Digital
Hierarchy (SDH) networks and Asynchronous Transfer Mode (ATM) networks"
and the sections covering  Terms and Definitions as well as
Abbreviations.  IMO all transport engineers and the general telecom
community understand that 1+1 or 1:1 are either SNCP or APS. Hence why
introduce a new TLA (three letter abbreviation) cover the same function
and feature for MPLS-TP.  I can only agree that this will only cause
confusion.
=20
Cecil Byles  =20


Senior Architect=20

Transmission Services=20

Interoute Communications Limited
Walbrook Building, 195 Marsh Wall, London E14 9SG, UK

  <http://www.interoute.com/networks/index.html>=20
=20
direct line: +44 (0)2070259599
fax: +44 (0)2070259864
mobile +44(0)7866447466
email: cecil.byles@interoute.com <mailto:x@interoute.com>=20
web: www.interoute.com <http://www.interoute.com/>=20

=20
=20
________________________________

From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
Behalf Of Vivien Sterling
Sent: 24 March 2010 09:27
To: Alexander Vainshtein
Cc: mpls@ietf.org; CCAMP@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] Term "PSC"
indraft-ietf-mpls-tp-linear-protection-01


Sasha,
=20
Right. It causes more confusion when GMPLS is used with MPLS-TP.=20
Could you share more information about the relationship between "PSC"
and "APS protocol" ? Are they exactly the same with only the different
naming? If so, I don't see any good of giving "a new fancy name".
Anyway, I might be out of fashion ;-)
=20
Cheers,
Vivien


2010/3/24 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>


	Vivien and all,

	AFAIK, PSC stands for "Protection State Coordination" in the
MPLS-TP parlance (see MPLS-TP Survivability Framework
<http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-survive-fwk/> ) - a
new fancy name for what has been known as "APS Protocol" in SONET/SDH.

	=20

	As you've noted, it has a completely different meaning in GMPLS.

	=20

	Since GMPLS is going to be used with MPLS-TP, double usage of
this acronym looks highly problematic.

	=20

	Regards,

	     Sasha

	=20

	From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
Behalf Of Vivien Sterling
	Sent: Wednesday, March 24, 2010 10:21 AM
	To: CCAMP@ietf.org; mpls@ietf.org; mpls-tp@ietf.org
	Subject: [mpls] Term "PSC" in
draft-ietf-mpls-tp-linear-protection-01

	=20

	Dear Experts,

	=20

	I'm surprised to find the term "PSC" used in this draft. I
suppose the authors are talking about data plane not control plane,
right? Isn't PSC in GMPLS elaborated as "Packet Switch Capable" ? It's
confusing :-(

=09
	--=20
	Cheers,
	Vivien




--=20
Cheers,
Vivien


------_=_NextPart_002_01CACB37.491CE006
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16981" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D215192909-24032010>Hi,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D215192909-24032010><FONT color=3D#0000ff>Can&nbsp;I therefore =
also asked=20
how&nbsp;PSC &#8220;Protection State Coordination&#8221; in the MPLS-TP =
parlance align with=20
ITU-T 808.1 recommendation that&nbsp;"defines <SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-bidi-font-size: 10.0pt; mso-fareast-font-family: 'Times New Roman'; =
mso-ansi-language: EN-GB; mso-fareast-language: EN-US; =
mso-bidi-language: AR-SA"><FONT=20
face=3DArial size=3D2>the generic functional models, characteristics and =
processes=20
associated with various linear protection schemes for =
connection-oriented layer=20
networks; e.g., Optical Transport Networks (OTN), Synchronous Digital =
Hierarchy=20
(SDH) networks and Asynchronous Transfer Mode (ATM) networks" and the=20
sections&nbsp;covering&nbsp;&nbsp;Terms and Definitions as well as=20
Abbreviations.&nbsp; IMO all transport&nbsp;engineers and the general =
telecom=20
community understand that 1+1 or 1:1 are either SNCP or APS. Hence why =
introduce=20
a&nbsp;new TLA (three letter abbreviation) cover the same function and =
feature=20
for MPLS-TP.&nbsp;&nbsp;I can only agree that&nbsp;this will only cause=20
confusion</FONT>.</SPAN></FONT></SPAN></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D215192909-24032010><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-bidi-font-size: 10.0pt; mso-fareast-font-family: 'Times New Roman'; =
mso-ansi-language: EN-GB; mso-fareast-language: EN-US; =
mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D215192909-24032010><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-bidi-font-size: 10.0pt; mso-fareast-font-family: 'Times New Roman'; =
mso-ansi-language: EN-GB; mso-fareast-language: EN-US; =
mso-bidi-language: AR-SA">
<P class=3DSection1 style=3D"MARGIN: 0cm 0cm 0pt" align=3Dleft><A=20
name=3D_MailAutoSig><STRONG><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">Cecil=20
Byles&nbsp;&nbsp;&nbsp;</SPAN></STRONG></A><SPAN=20
style=3D"mso-bookmark: _MailAutoSig"></SPAN><B=20
style=3D"mso-bidi-font-weight: normal"><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><BR></P></SPAN></B>
<P class=3DSection1 style=3D"MARGIN: 0cm 0cm 0pt"><SPAN =
class=3Dmain-heading><B=20
style=3D"mso-bidi-font-weight: normal"><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">Senior Architect=20
</SPAN></B></SPAN></P>
<P class=3DSection1 style=3D"MARGIN: 0cm 0cm 0pt"><SPAN =
class=3Dmain-heading><B=20
style=3D"mso-bidi-font-weight: normal"><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><SPAN =
class=3Dmain-heading><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><SPAN=20
style=3D"FONT-SIZE: 8pt; mso-hansi-font-family: =
Arial"><STRONG>Transmission=20
Services </STRONG></SPAN></SPAN></SPAN></SPAN></B></SPAN></P>
<P class=3DSection1 style=3D"MARGIN: 0cm 0cm 0pt">
<P class=3DSection1 style=3D"MARGIN: 0cm 0cm 0pt"><SPAN =
class=3Dmain-heading><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><SPAN=20
style=3D"FONT-SIZE: 8pt; mso-hansi-font-family: Arial"></P>
<DIV class=3DSection1></SPAN></SPAN></SPAN><SPAN class=3Dmain-heading><B =

style=3D"mso-bidi-font-weight: normal"><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: =
Tahoma"></SPAN></B></SPAN><STRONG><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma">Interoute Communications=20
Limited</SPAN></STRONG><B><SPAN=20
style=3D"FONT-SIZE: 8pt; FONT-FAMILY: Tahoma"><BR><STRONG><SPAN=20
style=3D"FONT-FAMILY: Tahoma">Walbrook Building, 195 Marsh Wall, London =
E14 9SG,=20
UK</SPAN></STRONG><BR></SPAN></B><SPAN lang=3DEN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: Tahoma; mso-ansi-language: =
EN"><BR><STRONG><SPAN=20
style=3D"FONT-FAMILY: Tahoma">&nbsp;</SPAN></STRONG><A=20
href=3D"http://www.interoute.com/networks/index.html"><B><SPAN=20
style=3D"COLOR: black; TEXT-DECORATION: none; text-underline: none"><IMG =

id=3D_x0000_i1025 height=3D101=20
src=3D"http://mmdownload.interoutemediaservices.com/%7b1f6bf083-a2a8-4f16=
-86a8-3f7df58cf0c5%7d/%7b61625953-b384-4613-84a8-bb6ec43d107d%7d/spade.jp=
g"=20
width=3D280 border=3D0></SPAN></B></A><BR><STRONG><SPAN=20
style=3D"FONT-FAMILY: =
Tahoma">&nbsp;</SPAN></STRONG><B><BR></B></SPAN><STRONG><SPAN=20
style=3D"FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: Tahoma">direct =
line: +44=20
(0)2070259599</SPAN></STRONG><B><SPAN=20
style=3D"FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: =
Tahoma"><BR><STRONG><SPAN=20
style=3D"FONT-FAMILY: Tahoma">fax: +44=20
(0)2070259864</SPAN></STRONG></SPAN></B></DIV>
<DIV class=3DSection1><B><SPAN=20
style=3D"FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: =
Tahoma"><STRONG><SPAN=20
style=3D"FONT-FAMILY: Tahoma">mobile=20
+44(0)7866447466</SPAN></STRONG><BR><STRONG><SPAN=20
style=3D"FONT-FAMILY: Tahoma">email: cecil.byles<A=20
href=3D"mailto:x@interoute.com"><SPAN=20
style=3D"COLOR: =
black">@interoute.com</SPAN></A></SPAN></STRONG></SPAN></B><B><SPAN=20
style=3D"FONT-SIZE: 10pt"><BR></SPAN></B><STRONG><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: Tahoma">web:&nbsp;<SPAN=20
style=3D"COLOR: black"><A=20
href=3D"http://www.interoute.com/">www.interoute.com</A></SPAN></SPAN></S=
TRONG><BR><STRONG><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: =
Tahoma"><ST1:PLACE></SPAN></STRONG></DIV></ST1:PLACE></SPAN></SPAN></FONT=
></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D215192909-24032010><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-bidi-font-size: 10.0pt; mso-fareast-font-family: 'Times New Roman'; =
mso-ansi-language: EN-GB; mso-fareast-language: EN-US; =
mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D215192909-24032010><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-bidi-font-size: 10.0pt; mso-fareast-font-family: 'Times New Roman'; =
mso-ansi-language: EN-GB; mso-fareast-language: EN-US; =
mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:</B>=20
mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] <B>On Behalf =
Of=20
</B>Vivien Sterling<BR><B>Sent:</B> 24 March 2010 09:27<BR><B>To:</B> =
Alexander=20
Vainshtein<BR><B>Cc:</B> mpls@ietf.org; CCAMP@ietf.org;=20
mpls-tp@ietf.org<BR><B>Subject:</B> Re: [mpls-tp] [mpls] Term "PSC"=20
indraft-ietf-mpls-tp-linear-protection-01<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Sasha,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Right. It causes more confusion when GMPLS is used&nbsp;with=20
MPLS-TP.&nbsp;</DIV>
<DIV>Could you share more information about the relationship between =
"PSC" and=20
"APS protocol" ? Are they exactly the same with only the different =
naming? If=20
so, I don't see any&nbsp;good of giving&nbsp;"a&nbsp;new =
fancy&nbsp;name".=20
Anyway, I might be out of&nbsp;fashion&nbsp;;-)</DIV>
<DIV>&nbsp;</DIV>
<DIV>Cheers,</DIV>
<DIV>Vivien<BR><BR></DIV>
<DIV class=3Dgmail_quote>2010/3/24 Alexander Vainshtein <SPAN =
dir=3Dltr>&lt;<A=20
href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein@eci=
tele.com</A>&gt;</SPAN><BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
  <DIV lang=3DEN-US link=3D"blue" vlink=3D"purple">
  <DIV>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 11pt; COLOR: =
#1f497d">Vivien and=20
  all,</SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 11pt; COLOR: =
#1f497d">AFAIK, PSC=20
  stands for &#8220;Protection State Coordination&#8221; in the MPLS-TP =
parlance (see <A=20
  =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-survive-fwk/" =

  target=3D_blank>MPLS-TP Survivability Framework</A>) &#8211; a new =
fancy name for what=20
  has been known as &#8220;APS Protocol&#8221; in SONET/SDH.</SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d"></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 11pt; COLOR: =
#1f497d">As you&#8217;ve=20
  noted, it has a completely different meaning in GMPLS.</SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d"></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 11pt; COLOR: =
#1f497d">Since GMPLS=20
  is going to be used with MPLS-TP, double usage of this acronym looks =
highly=20
  problematic.</SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d"></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">Regards,</SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">&nbsp;&nbsp;&nbsp;&nbsp;=20
  Sasha</SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d"></SPAN>&nbsp;</P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: =
#b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: =
medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal><B><SPAN style=3D"FONT-SIZE: =
10pt">From:</SPAN></B><SPAN=20
  style=3D"FONT-SIZE: 10pt"> <A href=3D"mailto:mpls-bounces@ietf.org"=20
  target=3D_blank>mpls-bounces@ietf.org</A> [mailto:<A=20
  href=3D"mailto:mpls-bounces@ietf.org" =
target=3D_blank>mpls-bounces@ietf.org</A>]=20
  <B>On Behalf Of </B>Vivien Sterling<BR><B>Sent:</B> Wednesday, March =
24, 2010=20
  10:21 AM<BR><B>To:</B> <A href=3D"mailto:CCAMP@ietf.org"=20
  target=3D_blank>CCAMP@ietf.org</A>; <A href=3D"mailto:mpls@ietf.org"=20
  target=3D_blank>mpls@ietf.org</A>; <A href=3D"mailto:mpls-tp@ietf.org" =

  target=3D_blank>mpls-tp@ietf.org</A><BR><B>Subject:</B> [mpls] Term =
"PSC" in=20
  draft-ietf-mpls-tp-linear-protection-01</SPAN></P></DIV>
  <DIV>
  <DIV></DIV>
  <DIV class=3Dh5>
  <P class=3DMsoNormal>&nbsp;</P>
  <DIV>
  <P class=3DMsoNormal>Dear Experts,</P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal>I'm surprised to find the term "PSC" used in this =
draft.=20
  I&nbsp;suppose the authors are talking about data plane&nbsp;not =
control=20
  plane, right? Isn't PSC&nbsp;in GMPLS&nbsp;elaborated as "Packet =
Switch=20
  Capable"&nbsp;?&nbsp;It's confusing :-(</P></DIV>
  <DIV>
  <P class=3DMsoNormal><BR>--=20
  =
<BR>Cheers,<BR>Vivien</P></DIV></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV=
><BR><BR=20
clear=3Dall><BR>-- <BR>Cheers,<BR>Vivien<BR></BODY></HTML>

------_=_NextPart_002_01CACB37.491CE006--

------_=_NextPart_001_01CACB37.491CE006
Content-Type: image/jpeg;
	name="spade.jpg"
Content-Transfer-Encoding: base64
Content-Description: spade.jpg
Content-Location: http://mmdownload.interoutemediaservices.com/%7B1f6bf083-a2a8-4f16-86a8-3f7df58cf0c5%7D/%7B61625953-b384-4613-84a8-bb6ec43d107d%7D/spade.jpg

/9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAZAAA/+4ADkFkb2JlAGTAAAAAAf/b
AIQAAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQICAgICAgICAgIC
AwMDAwMDAwMDAwEBAQEBAQECAQECAgIBAgIDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMD
AwMDAwMDAwMDAwMDAwMDAwMD/8AAEQgAZQEYAwERAAIRAQMRAf/EAKIAAQABBAMBAQAAAAAAAAAA
AAAGAwQFBwIICQEKAQEAAgMBAAAAAAAAAAAAAAAAAQYCAwUHEAABBAEDAgIGCAQFAQYHAQADAQIE
BQYAEQcSEyEIMVEiU5MUQZHRsjNz0xVxMhYJYYGxIxckwUJiQyYYofFSg7M0VBkRAQACAgAFAwME
AwAAAAAAAAABAhEDIRIEBQYxExRBUQdhcTIVgSIj/9oADAMBAAIRAxEAPwD9aeSZJcZBcT7Gxnyj
vPKM4Y3GJ2o4u47tR44uroEETNmojUT0evddBge+f3xfiP8At0Dvn98X4j/t0Dvn98X4j/t0Dvn9
8X4j/t0Dvn98X4j/ALdA75/fF+I/7dA75/fF+I/7dA75/fF+I/7dA75/fF+I/wC3QO+f3xfiP+3Q
O+f3xfiP+3QO+f3xfiP+3QO+f3xfiP8At0Dvn98X4j/t0Dvn98X4j/t0Dvn98X4j/t0Dvn98X4j/
ALdA75/fF+I/7dA75/fF+I/7dA75/fF+I/7dA75/fF+I/wC3QO+f3xfiP+3QO+f3xfiP+3QO+f3x
fiP+3QO+f3xfiP8At0Dvn98X4j/t0Dvn98X4j/t0Dvn98X4j/t0Dvn98X4j/ALdA75/fF+I/7dA7
5/fF+I/7dA75/fF+I/7dA75/fF+I/wC3QZ7G8kuMfuIFjXT5QHglBcQbTE7UgXcb3Y8gXV0FCVm7
VRyL6fXsugwJ/wAc35pPvroOpvOEYtHl9DfNynkSLXTcf5Dvrmhoc7vaKukNwTDWW8GPXxYchItc
6UWMvec1ioR71c5FVV3CdYlyhfzafPz5RU07LXBqCqyVUoZE39vsIN3iz8liRESwYskEuMgXhI/d
zH+Dmo3xboNHROb+Qqy7tvm41VOt8oDhMyqrmOye2x+njyOObTLjxq6qgR5Fwk21eEQHqNrhtMqm
eqsRUQPjuW8ySdNugRrUk4mQ293X4xY2tlEi1o6/y/Q8wJjc+tB23So7J6vX5Z3QjZn+5shN10Ge
tfMrkj5kv+mcXrbGvRLWZVK8N9Pm28Wio8PnzoEcVLHlqGfKsMlIIcgjGxQfL9JOpyqqBs2jz3N8
rx/liySrp6KFjEnNaDFpvzEwtnJs8bmXcZ0y0gbIyEMIAxU6WEV6naV3gxWtaGrMY5r5Jh4tFPPq
MduYmN43xEa5vJE+yFaWZuSP6ZDAX5ZUM0s8MWzKWWZXtG86J0N2VU0GYs/MNkocin0dZisOc6lv
clizI8ePfWU+2q6PPkw8Y61lZGOGusVgsLLIWUvyyuYg02VyLoMxytyBluC59ZWdKsWfS0PFA8kt
aSzmzxQjMFmg4Mo9fGioof3ssMnbGYmzGNTZyORdtBQn88ZOyKVanEoVnP7HJRQxBGmlI5MIz2px
WOZoAsceUiVU8so4RIpTEEjA9KuRNBGw83ZLIvKCbBi0s6dkdPg9XEZHyK0NhplyXk/JcUbbDrxj
eaDNJFrRvepGOlxupwCscounQXdR5h8utLHHoAsTr5hiEr4+RRqyPfzJByTc/wAjwg8ikKEBoNbF
gCoEmOWwI3uIRRtcisVyhbJ5h87/AKen2x8XxeCeuvIdXcOlS7lR4k+VXWsr5DKatgUtYfXNhx44
7RESue2V3v5BvTQbSyPmWPFgQ67Ho4JGbTLnC6AkKyhX39N1k7L7GugNkf1AKujV1/BhOnbo6Cd6
lREcmyb6DVzuW8+p7fMJdlHpo1p8lxnBbQyrWZe0tXYToXIh7F2PQcfWZOuZt2ajAiAjK4g2uRxn
dMd6oGRh+YHM7KZXNg4VUOZb4KLKaWqkWsqPZ5BJXDTZDLbRTSgbXTh11wNsE0NE+f7T0ko3t+Gg
ltfy9kUvh3J+R21dDPssbkyHOhVsid8rIrqwlaa5WZBlqK1pLavhnlMfFk7PaQDSLuIjdBDLPzEZ
OORlkmpx7H5VFiS5LePlyZliw99iOP5PBxLepcFhAitZVgyaRCkRQIxg29Cqrn6C7xvlXMT2rqLH
6eFbIG5zC6u3ZJkkhZjqdnLEjDhQaKdPJHhwf22GrzsEZzh9AmgCxXK1NBMeG+XL3kos8llQBg1p
KKvyConwol0CKJk2wtIRKKwm20YESdaRhQRGU0NXR3sKqJsrF0EBqvMJl1rLZUxqTFS2c/IMHrK2
WKRe/sbI2YHyGKZqzSRmOuVqJNH0pNhdUOWqvQeyN6lDC2PNmbZZWY4yBGrqAbJPGNhkkyvn2YJ5
JV1yjKx0kKp6Ucx9NJBj72yBHcjiCkqxXOa1zSBO+XeQcqh5MPFaBY9dWVNhxPY3NqObOi3R1yfk
Fte2BBSM1YxK0kWrcKUMqt7w5Dm7q1FYQIBfc455ehm09QlDTz4uQcfT4lrWPuTwSVlrnxcckUz5
xWRwXovnoYmSZkFywzhWQBvttVUDb/G3LNxmGbXmJ2lfTMFCqJlxCn0hLM0ZnyGRHx+TXEnTQMg3
RUVjCukQnLHE9XAVXEY/YNaN8xWaKIsM+NY5AvS5JFo215X5BOlUJC1mTWpYd1SV8UtzYFJHowLF
mQ2fJSmSlexdgvRQyYueM+OG7u3YVT1+N4qzjkuStsZVkO/jf1tXYZPnx41d22N3pR3U16lKo0cN
olViK0iODGs5uyM1tb3MasB3plPSwMUhHt7L+nXguuYshwSsuLOsGrmulLFgNkEOHoIYew29LFaq
Bm2845+HJoONS8JqzWEM+OwMjgVEiyt3mkZFc31UGzrbiuHMoqerhCqQyDNsCoVjZDmb9YCJoJXg
XLOQ5NhWb5Jb1WOwrLFIsk6VrbSRV/Jzo9QSfKpclFcDbKpC1koXafLeny0kS94SdCLoNe1vLmc5
jd8fghlqapI/K0nG7x0WLfxIORVRcEJkMUo4Nq2JZBjLDlHcxpmqhDjjHb7HhoJDmvO17iuYZFQB
qKKdCrKrMTQ1EW1PKBPxjjuVncYlxOCFtOFLR0Mkf5BhEmhG1DPVGPYjg2Nxfnd7mB8rr8ir6mDP
x2TjjmOpTTDRCw8mxWqyaMJ7pzGGfJhtsVER6NY16pujG/SG3wfjh/NH99NAP+Ob80n310ERyHC8
cyqTAk30D591dCv64AnnOOO+Dk9atRdRpAREYw45kBVH7W6t33bsvjoMRjXGeK4tV3dVCDYTg5GA
UO6kXdpNuJ8+BHrUp4deWZNKQyQYNYnZCNqojGqv0qqqERD5fuPgRuyL+pmSmugdq3blNyl1HFX0
szHARI9iknvBhOoJ5Ibwt2G4GybIrWqgZ+t4ewGolwpcCpKFa6WSXDAs6YWKHu4YDAXxuyUr0JFX
HI6D6XdS9aq/ffbYMG3y/cbDoKfGwwbaLW0wbyIL5O+tIcqdW5JJBKu6m2lxZAjWNbOfFE1wyKvS
waI1U9rcNh1GHUFHWXFNXw3Mrr6zvbazjPOZ7TSsjkGk2qMd1o8ASvO5GsYrUG3ZG7aDX7uIuN8f
xW4oZsmdCpb0eJVcudaZJJDJY/G5cYGHAh2ck43RJEGW2OGK1iornNGNEXwaocncC8ducNyxbvdZ
c+TYKuSXT3XrLK7DkUmHfFfMca2huuQNP0lcruvfdy9Ttwz2YcU4fnNilpfgs3ynVQaKQkK4sK+N
OpRWbbd9VYRYpxx50GTNY1xGEa7qRqbbKiLoMEbgfjyRJspRYt04lk+4L0f1FbpHrT3d9W5PJkU0
dJXZqjBv6ocoTgtbsRV6upEajQuofCPH0E9bKBXTllVZaWSCSa3sDnNMososMxizppDHe6ZLkZBa
HMdz9+4j+jZGoiIFL/gvjpJUCQyusRjhHbIJAHd2ja20eHJbPL4TbqCkns2o67ILc5wIZHdKORi9
TGtagWDfL3xsOGSGOLejc9QhbOZkt0lkCpjVM+gj49Hm/N94VCKktJEVI6L4iKu6q7ZyBN8gxbEb
yprMEnEZCHHFBsqCDX2jq65gMxSTXOhWdM8Rmzx/ssl8ZqmZ1NYpGNevtoihr+Lw5xA+RGq60xB2
UNleUYavLpwLlGYl+9UskziQrBli3cmWSo9g9FariyUR6tf06C9Z5feMWoIRamwkxBU7Kf8Ab5F3
aOryIPHlxNlmWIySwTrluOr8q2Smz2MRHN2eiOQJRjOFYXExa+x6oK67p8imX4clmSbk11Lt7KUx
1DfNsrJTlIs4LIXyhWIrFCoehWtc1dBHHcCccOqqClSvsh19BXGpmgBc2EZLimkW7b6TU5D8uYSW
9fIuEWQ4ZE263O22Ryoocm8M8a2pK61jBkyQgsbKx64N7MfAt1m5b/WJIVo2PIdHs62Fk4UOILt2
jeNEXfx3CQYlxbiGFGnmpIs/edXipmjsLWfZArqMEmZMDR1QZZysr6oUqwMRBMT+Z/iqoiIgRvHO
FeNa79ssqVLGeOvk4/JrJJclsrcAVxGVbOpARiHlyBth1zrQwuyxUF0tRFb1I5zgq/8ABHHjT1Jg
wrWM2mZVsBHjXtoGLK/ZskkZVWus47JCMsnxLWadWKbr6RlVqbK0asDJZPxxgmT5bXWtyaSzIvla
uQCviX0muS1iYheguIMuXUR5Am2oqmxntY4j2PaNslGqqOUStDDR+AOOokORBjx74YixKuDHIuS3
JT1kSjvyZJTAqDGlEdXCq7QiuE0Wzdv5kc5XOUMzjHGuC8d2QrWsLMhSpcY2NwUuMhmzANjWVs+7
ZTVceylEEHqsVI8Qgoj3K5+/UqqutG/qum6bk+Tspr9y8UpzWivNe38aVzMc1rYnFYzM44QwtspT
HPMRmcRmcZmfSI+8z9mFFwBxzHAooke9iSByYR66yjZJcitKQFbHtIcGrpZqSu7X1MeJdyxoBvsO
aZerqVrFbvZpDD4jwWBQ5LjUSqIGmyysrai3ifOy39UKooIeN1zI5SleWOWPWwR/7iL1uKnccquX
fQWJeFcBLWirPkJwgx8Yx7FIpwWkwEyJX4tcGv6WVFkiI0gbWNcHcdZCe2R3g7dqq1QwTuGuIqix
xqDJc+HKllCGtpJmUzANzGzx8lxk4pU2rLOY7JrepJPnTnORr3sa4j3p0NTpCR1vE+CY9jOUUCAm
Ppskq212QSLe6nSpDqWBVLUwof7jLkKWFBpqlnbB0ub2mN6lVXbu0EUoMQ4YL+0mocujWkpcox7L
qyyj8gfu9jPvJ+LOjUpGTf3OSafGyLFoRSjAiuHKioR4k7TfZCtb8d8O2mT3/wC4XAUyCdNkjt6N
uaED8pZ8h4lPxMirj/7h24VnlWPiIgHKFDG+W6grsxyaDaNBiNFjUq3m1EYgJF4tQti8kk50KlFT
QqCtaxhiPYJAVsAbV6URXu3c7dV0ErB+OH80f300A/45vzSffXQdJM/zzN6vlfLo1VlCwEpZcKFR
4+exMYdnAlcVWN/IZExCLUTCWMj+oB91tkUwwAeDsPXZyJoIUbPrAdTURgcyZMerLjGR5BPtSTIs
QkLOIHGmJX1XjDMsKhhXQZFraSpDoDUH0EX5ZWO7S7hd2PIPJUdbDJBZNfpcisp1eLH1aJ1QOT/7
fP6s7SUSxVVZLclAwrRLu1hEXpYjnvVwcIeZ5TPtYuN1PJOT2WOHGaW2+i3ESbYFsF4VuMstKxl6
KI9qiiXsMT1A324qkVGqNenpDFv5Lz7EoQMtk5nkdvWRcT42vLaFYnFKG615I4zziR1iEyOAQYUf
JqyEoA+A2EVqrvu5VDemfWV5jdLwnS32cW+OrYQLeDmOQDtBVkybY1/Hk+W10qwlje0RZN+FqNVd
no96dKo/pcgadpMmzu/qJGQ3eX3Zx11z5eq8dBIFCdVnLlUHjW1tbWUGRFIUkmUYalGjVYNj5BXt
RO6ugH5CyR0YT28lXj7i8zJ9fmOOGnCpoGLVouScopYTw5V2ZH9CpNra+NHUHY63MXvbruiaDdVL
l1tlfl+yB9Fm8e3z3HsVsCS7mkkGfOHYwRyrGqUjpMGBIdJtK2IxqmUDGnc9z2+yu+g0PYcqZhcR
LvLCZzdY7T21NyJmHHYY0uPWxrK5xi3xXGKPHgslhO23iEeCaZa9qq4ymVz2q5N9Btzj3kPIbnki
jx6fkRJBW5Tz3Hu6NxxKaJBqLigTFQTYfjJihhCJIbE69lVnUiKqIug1lmOeZ/SFySyrsxyFXzMg
54pmwzzAur6mrxPNcVg1ZK0Toj0gFrK+1kf9S7uPEzbZUYxGoGONyJnYbJsAXIoWwac1nIopz8rn
zIkqQLPKiD+0zbAeLrL5KPFgyHQ+1GEo+2ZCITqY5UDZPGtzKu+bY0m0yGZa3IQ82wptNKlgK3Go
1fnNJXVEKNBaNsqrjmrYY1QZHOR6sV6e056uDRx3TMfyPli1x/K7+Bd4zX802bCRrdppQzV/LeMi
iBnsMM5GxrJj0PIb7CynoiuVWK5rg7E8SZhlNzypewrbKElhKXksUvGJFsecevTHs1hVlIcFGCpG
DFBwoBVBtIlK+c0ncRrnIqoGip2aZBisGxZiGY2LZU7IuVxZJSBs4zYuNwh8uYtFiWjRMjFfQHkw
buY5Z5keqNeqtXpGiIEohZ5lH9QYbXyuTbGbWkyIlEyLQW5J9h8pM5FtKeDLPYWNRUx+RgOhR1rJ
J4TlLCYNk0bSdS6CYYjKmVnBPGsSiyW3hyLblfH8ftJsOyYawgR7bPi19hXCeVkhkTrhua9QvYrV
cRXOaqPVFCA0uf55MtsVrpmeT4jY8qmr4a2V9IiyL4ErmPNMSnNJWQqifYZZPkUlYCKpWOF8k4aG
VzVV7tBFsfzfMMEoMYrcdyS3m19nCTJ5ER0pZ7KSLx9k+b3mdQUTZywgzqOFDWQLwcb5jpc1UVNw
m9FyDnJptPPtM4uhW0ux4xtsSxtZUcUbJKHkfPMkfdhJUlipKvgVmNLFCxzNvkmjRW9H0BEJOQZ3
WVPFeZyMsyO5m5Jg+QS8pyB7ohbTD8PPkOCVF1NxwKCZ1yoVfFR6kf3Cd4xJKqiorkDvlk15nNeS
A3DMKqswgHiIU0+bmw8ecEnV/tMGJ1BcJNGYOz0KhG7qu230qGHyvjSl5WrcPkZ9Uur7PHpwL1lb
XzoVkGJYq0SyKyRYSalEtqgjhNQwVEMEroapBu6WdNI8z/H3jvnnwv7+l7fA6mN+rl5ONuGaX56X
59VsR7mqf+ezFfcrblrjl9z7R0fdva+XEz7N+auMev2nMTms4419J4ZicQ8xanmbM5d+XGrznbLm
4/e8tYXX5jmldc11dTV2D3lnyyQNhFt5sGHa8J3JbLGYFPOpJIQI1sdpwGIyWjtXd1G68h5k5Lxz
yjcJ84ycmtiT6DK66Tmk4kcCPyzDZ8nLMLqpFsBsYIJzJhJ9TO7qNaM72oZEVzmOQOuEfmLnmfFq
qvJuRshxsWKZPj3CGezJ2VJgwSZjjdVzbeWtnPzSVTWbKeXYArqMjjjGclkxjAud4q1A7Ccl5Ea5
w/yTZNmvI5MfmWlHl1hcck0s4mLGLYTeBr5R2kKfkFZBPVmyKaVg+t8UBFdKXtNG5Rq0NO0PmK5P
l0lJX3HIkxuUWWTcJmWmlHgssp+KXvlJs8jyKctScSmkU1tmSR5kgqDWOs4iK3p6kboMBjDA2+U8
QXl3ezqfvZr5ICWE2DZsoIayLbyxZjOJKMkdI8MEgk6K0IlajEYOUUTERCqmg3dzkd1tzhexbrIJ
1LS455ivKkEEuFYioW10S4wvKpE2TJswsARXAkp1hIcjvl3Ed0dPWqKHqHoKoPxw/mj++mgH/HN+
aT766CwWFDdLbPdEjLOYJwGTVAJZbAOXqcFshWd5onO8Vai7Kugt0pKf5dkNKmt+UHI+cZFSBF+X
ZLRVVJTAILtNkIqqvWidW6+nQXiRI6EUqRQoVx/mnFQLEI6T8skL5lX9PUp/k2oHr36u0nTv0+Gg
oAqq6KwY4tbCjDCUpxMBDAFgjHY4ZzDaMbWsKYb3Ne5Nlciqi+C6CJ5px/VZvVwqSeQ8GqBbUdjP
iV8aualvFoJaT4NNKLJgyTRq75wbHO+WcE3Q1WNejXvRQv77DarI7fF7izaYpcUlW8qHEVoCQJn7
1RzqCYCxjnAVTg+Unuc1GuZ7aJvum6aCQpXw0arEhRkY4kYzmpGEjXFhKFYZVb0bKSIscfad6R9t
vTt0psFF1PVvbNa+rgPbZOa6xa6FHc2e5n8jpqKJUlOZ9Cv6ttBjS4xBZHyBtUj6awyGK2PJtYog
S5AHAr0ra98eNaCnVyBrgIiijKFYqOVyqNVe9XBZYtg1DieMY7ikGG2XXYxHAKtLYhjyZSSA9T32
Ln9hgxz5ByPI942MRHvXpRE8NBJB10IR3yhQYopRXkISSOMJhyEKwTCveZrEI95WRxo5VXdyMai+
hNg+/IQ9np8lG2IklHp8sLZ6TXI+Yj06PaSW9EUu/wCIqbu30FFtPVsZCGyrgNHWvV9cxsGO1kB6
rur4TUEiRXqv0s6V0FQVdBBIJLDAihlGUriyRRQjkFdI+X76kMxiEepvlBde6r1dpm+/SmwcUqq5
CyDJWwkNMaRssqQwIWU0qCaVsgnb6jtI0LEcjlXdGN39CaCqKDEAc8oMOOGVK6PmpIo4xnk9tNh9
8zGIQ3QngnUq7aCj+01vWYn7bC7kgRgHf8mDrOCQd8mQEzu31EEeSVxHtdujnuVy7qqroPo6quEs
NRVsIa1zHjr1HDAxYLCN6CMhq0afKsexNlRnSip4LoObK+ENijHBisG6Us5zGRhNYs1SodZitRiN
WUp06+5/P1+O++g+LWQFKA618RTxXGfGMsQKljvkOc+Q4BFH1hcd7lV6tVFcqqq76DglTWt3VtbB
arlmOcqQwJ1LYK1Z6rsPxWcrU73vdk6t9Bz/AGyB3Ihv2+J3q8bgwC/KB7kITmINwoj+31RhuG1G
q1itRUTb0aAtbBUbQrAiKJkU8FglihUbIUntfMw2s7fS2LI7DOsaJ0P6G7ouyaC7RqoiIjVRE8ER
E2RET0IiaD7svqX6l0GHfjlCWPZRCUVQSLcSFl28Z9XDfHtZTnMc6TZBcBRzpDnCaqvKjnKrU8fB
NBemroUiJ+3yIMU8DoEP5I0URYnbArHBH8s9jg9AXDarU6dmq1NvQmgtJFBSSwTI0ukqpUawktmT
48itiHBOmMaJrJUwRAuHJktaFiI96OciMb4+CaCvMqKyxA2LYVkGdGaMgWx5kKPJA0RgOjGE0Jxv
GgyxnuG5u2zmKrV8F20FD9gpO+2UtLVfMsHHC2R+2xO+0MMMiPEE03Z7jRxQSysG3fZjCPRuyOXc
PjqGjcNoXU1S4LXQHtE6uhqNr6pGpVvaNQ9KOrUY35ddtw7J0bbaCrJqKmakhsyrrpbZZIhZbZMK
MdJRYD2EglkIUT0MSEQbXCc7dRuRFbsqaDI6CqD8cP5o/vpoB/xzfmk++ugpaDmz0/5f9qaCroGg
aBoGgaBoGgaBoGgaBoGgaBoGgaC2myxwIU2eZpXhgQ5U4zAM7h3BhgJJK0I1c1CFUYl6W7pu7ZN9
B08tfPlwBTr0y5WYK5FRFaLGwufuv0dK2rV9C6CJyv7jvl7jsc8cLkOSiKqJ28fq2br/APdv27b/
AOOgjxf7m/BbfAOI8nyHbr4JW44JdvX7eRL4aCh//pzworuluFckq707PBjg08fR4pdE9KaBI/ua
8PBViNwPkQnUxHbouOojd/XtZOVdBTb/AHNeKHoqs475BTZN/wDdPQC/y3SWVP8A56CoP+5XxoRU
6eOM2Rq7Ijls6L0rtsnSi7+hdB244N50xDnvF7DJMVDNry0twSkvKO0cB1lVTOyOXEeZ0ZzgljWM
MqEC9q7Ls9q+0xdBudfQv8F/00FDQNA0FUH44fzR/fTQD/jm/NJ99dBrLlnMrfj7BLrM6mupbT+n
RtsbKFd28qlCaqCq/Njgy4lXbvfbGcrBxxOF0kI/bdXdLHUb8jeUdy8L8R6rynt2jpeo+FWNu2m/
dfRW2mv8413pq3TO63Cuuk0xa04zM4rbl9567d2zt2zr9Ndd/ajmtF7TSJrHriYrb/aeEVjHGZ/x
OtvK3n3IXIGIyE5BrY0G0xmSHFrAsuVKZlknIYSKe1JkdE+jqYtKhYMyGSO0bzOex6q5fFNUH8B+
ZeaeYeL7J800a9PcO33jpdk3veOst1OuJttnqennRppozrvptritrzaLTNp4w5HiXcu59x6Gf7Ok
V3aZjXbMz7k3jjbnpyVivCazXEznPF4v+aDz7+azjTkHJo3HWfGkRZvLtvgWHYtLocWNAU0nKT4/
j1cKbJpDyOx3VCx7iK9Ua5XKqr6fd1rek0dn90Tj2o/cr13lh5zlwo/cscUoP6ixa9IcbUWRFqbK
XXYlW2BRvRWMVxGKT0tG5dmqGd4Y/uBcYZ5mDeIuXaS28uXODJ7aZMG5GL8tSXtyrFIldi2Wyo1a
AtmYSIQcCxBAlkG5qgSQ1yPUO/DmuY5zHtcx7VVrmuRWuaqeCo5q7Kioug46BoGgaBoGgaBoGgaB
oGgaBoKMmOyZGlQyORg5kaRDI9fQwcoL473r4p7LGkVV/wAE0HgHz35SOdeKmyrrIsLm2WJDMYkL
MqKRHyLHJkJxXfKzG2NeSQsYJxbKiHQe2+3p0HTZ7FG1zXj6HOVUcP0qxU9O6b7pui7aDGPTd3gi
9SbJt6PBPT/lt69B9ajnOVWNRq9O67pt0/R1brtvttoMh07dLnK571T2V9ldvTv4p9H16C8j+yxU
Jsu6rs1UTff0dP0/QvhoMkj2Mb0qioi9Ks8U2Tbx36k32VOldB3s/t5chxse55lYQQpmA5Twy3Cx
HPd8sXIcJ/8AUFc7p/ldKJSfuLGuXZ3T4eKaD3CX0L/Bf9NBQ0DQNBVB+OH80f300A/45vzSffXQ
UHMa9qse1r2OTZzXIjmqnqVqoqKmotWt6zW8RNZ+k8YRMRMYn0XMJjGyhqjWtUhxOIqIiK9yKNnU
9U2VzkYxE3Xx2RE+jSK1rMzWIiZnM/rOIjM/fhER+0RBiI9Pq/Ipy5J/evMVwNCONrh2fnDxEhVJ
v0HU3MtO96EcqeKNRVRf46lL9ecpd5MhfWcq/WR2g8lf7uXEOH5RwHF5QmUkB+V4hkFRSEuGhGOw
nY7aBsyRq+VKRGvkNqLmOE0TrVVAhTtYqNK5FDprw/5wvNHxVSXNPjmVVHKWDcbYjW39zA5ke2bY
4/RyLaBjlfEq8wBZ1eTz2/PzQiFGe+a4THIqIjfDQe3nlBzDlrzH8VO5Ry3HMDwuNNyC0paCtx+f
e3D5saj7Mexs5sieQTY6GsSPGETEcqMErnLu5EQOxs3EcljP6REqjKi7Knbkou+2/wD/AE7on0ej
06C0ZjWU+HeHWi/m3XYzkREXZrlRJXUiO9Po0F43EshXwUlWq7Kq9LZf0br4IrvHwT6F9Ogug4Xk
Bk6t4LWqngvSb0/+JO6m2/q9OgunYDkXh0Hq0RyJt3Uko5F23d1Na9d09W2/hoKrePMjXdPm6hV2
RU6GTFTx+hVVzfV/loDeOsmc3q+Yq09tW9KjmI7ZFXdVTuKiIrU3T06DoP5hPMNzBwrypMwPGuB8
P5JxyBR0lifKp3mW4c4rtCWVmEkiZWgxDOLcVq2LXjcJrZJu2yQ57lYnS1HKGtReeHkQTWEtPKdP
EFXdDyVPmw8pdsrHo1Fc1RG5JrH9Xj4b7b6CXwfOfMOPuTvLdylC22VWQOUvKvkD1RdvaYyu55Y9
6Lv4eHjoJBE84lBIe4Z+Euf4pGNRz2jo+L7fZF226f2LlqyUniu3sou6r4aCbxPMhj0piEdxpzZD
T2d2z8JpYjmo9EVrlQmYbObsviqbomy77bLoJvN5gwarolyG1tAQYQxgNKiMuMSubqCKQrWtfNpM
bya7shOErv8AcG0bzM2VVZsiroIZjHmi4Bz3Ja/A8P5axKVmt3IWDV0k9bSrmuN0kIcvy9lXRHFW
LGCQiDaquKrEY1FVdBtWwp8wpGWLsNt6G0oZTCfumJTosODAtxmaoZA3VMxDYvZMlDX/AHBFDCO/
/uyRroPDHzQ+XHPsYy3IM7hYBS0uC5BZlk1qYQKwDT0SPd41lrTzpdlIoZgFRW7tOSIf+YRHbroO
obcUunuVzYEjbZ3oa5dlRfR6F6k0GVi4DkBl6kr5LURGoq7PT0+lNneGy6DO/wDGuQ9LUbDIqez6
WORd9t1TqVvp3+nQZEPFORmRiJGVnW5E3cN7lT07/T609Wgzv/C9+VjGke4aOXbwY7xRfT49Kqnh
4f8Ax0G3+FMMl4PznwjbMC4Jq7k3F45jqqopIl6Q2MyxMaqJ7Jot09HeO2yroPfd3oX+C6ChoGga
CqD8cP5o/vpoB/xzfmk++ugpaC5h/wD7IfzR/wD5G6D8f/I5GC8yXBYSv3/b/Nvgju05V3Tucw1C
OVfH2UVzF8fDQfsHkNc6UdjUc5yyCojURVcq9xybIieKqug8If7yHm64+oeP8Z8t2KXLct5VzPP6
6KTEMZCS8tzWcGFKFAxmBDr0PItMidIs+8WHGYUoO2NpEa96N0GvOF/7c/m+5KxCQvLGU415dsbz
Ouq2ZNhZY/8AWufXlbDmRbqBV5PTU8mDRUTIlpGGdYhLYpxnZ/uDa5OlA9ffLVw5zD5Z+Oz8ZUHO
NRl2PDvrK9pjX/F7INhUuukCW1gONX5iUc2IWaFTC3axwnEcntIqbBtixjc5TSKUXKOMxiOVFcrc
KnuY70f+WuTbb/56CkAfP4goEvJmESdvDrdhFsNXIm3Qr2/1IVOr17eHq0Hx/wD7hd/Y5E4/d4Ki
9eI3bd2/QmyXD9tv89BSR3mObt0cg8cbJ6Gri983bw8F9mauyp6vRoOHzXmcRepM/wCM3qiIiddD
kjdkRfFE2euyL/mugvQXHmWAxWvyPieU5d/bfCy2P0LtsqsYMT2p1/SnjtoLd915m0YMY7jiN6CV
FY9SZoEnp3cr1bXFR/gu38NBpTMcT812RXcqZEo/I7ZRJYhqSw5I44zPNMkU/T2yCJLZWQRnhia1
vZRz+piKrfQiaCMxeDfMNLcr7ln9v+Im6KwdX5RLC3Qfo/lWzzSrYqoielW+P+Ggn9fwln7GNbY3
PlZC5NlVaDyUYFFdun0sLaZvZuaqfQvTv69BPqni+zrmo015xu/wb1/tnlp4SqFcqKi+yQlFaFZ6
PDdXbaCTJx5jEsbg5Hj2B5WF7kV4bjiXidol/wDCjYWFx3I3df8A6tBRdxBw04CRk4U4VGFPQwXE
XHY/pVfFW43uq7qq+vfx0FnXcHcIw7evtE4f41JIgywSIv8A6MoAshkY9uxYQ4sCOyOUfpbsmyKi
fRoOwNpgnGmRObWVvDlBn1g5UA+NR4nVSokcvirR2l6X5XH6r20XqWRKa9q+PQ70KGkebvL65ayo
h3GL4rQsjOWZFwzAKeFU49Uq6M8QRXOQhhwbjPrtwiuUjnii1kdz1aIDnp3tB0nj+WeSB6q6qYm7
3vX2Fdv1vVyIv0K5v0/4JoJhXeWx73sRa8adxyNa3tu/mVP+6m3Vvsmg2DB8qMtzU64Dl6lTb/YR
NvUiL06CXQ/Ki4bep9eruhFd+H6V9O3g1Pp/x0FU/loI5GtbWbKxF6lUS9W/0fRvv46DT+T8KJjG
a8ZzCwlGZOSsQAH0om8a3BcFVERVTccOrI5fBNmpoO5rvQv8F0FDQNA0FUH44fzR/fTQD/jm/NJ9
9dBS0FeO5GGG9fQx7HLt6mvaq/6aDww5F/tfcx5jll5lVJlmA0F6Pk2NnmEZGS6tTLjqVWTzMlqp
T6pmLmU9uOS6OvQpFjsUa7oTfbQdxbHy0ecjk+uPT8yedmRQ0k2IsWzrOC+N6fEbCyaRqNkOk5Cd
K6SxZLVd1N7RQqq+I1b7Khs/y8+Rby0eWa2Nl/H2CfvHKE2KkOy5i5DmrmvJ0mN1lK+JXX1gEcPE
qxxTvd8pSRa2OvWvU126qodvNA0DQNA0DQNA0DQNA0DQNA0DQR/LSnDimUFjK5JLMdvFjq1/bekh
ayUgFYT/AMt6FVNnfQvjoO7FRn5KylrKWsrotVErK6JBEMTO44TQAYFrfZYMDXqrd3bM9K6DXOTT
H2ZiyZPelOftu8ntdPrVqOcr09PrTQQJwI4mjY2K92799t2p0qvo6kRF9P0broM/UNaI2/ye69Xs
tViPcvV47oi+CbaDasEz+lrnARGtY3x6Gp4rsieGyeKInj4aDIlKzsuYrU6nLv4Jt4J6l+nwT/DQ
RyVN9tGdpBovoI9ERFRE+jdE39Ho0HUHkU7Ml5nw6pYjvlsDo7zO7FiDRRMtMgEfDMWGQiojmmLE
NbyGN8V/6dF8NvEJMvoX+C/6aChoGgaCqD8cP5o/vpoB/wAc35pPvroKWg5s9P8Al/2poKugaBoG
gaBoGgaBoGgaBoGgaBoGgaBoKEmOOVHLGK1rxGb0EY9quY9u6KrHtRzVcx22zk3TdF9KaCUyMuyI
5in79eNSqq9psE6hYrlVfBqz+4uyr4e1oKwswt+2jJUaolbNRvV8rLEq7ehV/wCvJv46C3PlNq/d
oYlKNionU0sacZXKieO7ksB7Iqp/loMhW5pOhOR8isrZT0RNnMfLjI3b0o1vdN4fxXQSIvKti9rW
soqpjW7KiLJmuRyp4Kr+lGKqLoKH/KFo5P8AcpKlXfQrJVgzp2226UXr8P4+OgoP5GmKvW2kr1fs
72TTpbxKqp4bsaBqo1P8F0Grhw0W5yLIZA4zbbJ58aXYPitKgBRq2EKtp62OpnOKsWvhiVU6v5jG
K/ZOvQXi+hf4L/poKGgaBoKoPxw/mj++mgH/ABzfmk++ugpaBvt6NB93X1r9a6BuvrX610DdfWv1
roG6+tfrXQN19a/Wugbr61+tdA3X1r9a6BuvrX610DdfWv1roG6+tfrXQN19a/Wugbr61+tdA3X1
r9a6BuvrX610DdfWv1roG6+tfrXQN19a/Wugbr61+tdA3X1r9a6BuvrX610DdfWv1roG6+tfrXQN
19a/Wugbr61+tdA3X1r9a6BuvrX610DdfWv1roG6+tfr0HzQNA0FUH44fzR/fTQSPKmY8l9aLQyb
J8B0+UomTIUcSiTvv3YIgrAynAi/hucwb1Zt1NRd9BHNge8L8Fn6+gbA94X4LP19A2B7wvwWfr6B
sD3hfgs/X0DYHvC/BZ+voGwPeF+Cz9fQNge8L8Fn6+gbA94X4LP19A2B7wvwWfr6BsD3hfgs/X0D
YHvC/BZ+voGwPeF+Cz9fQNge8L8Fn6+gbA94X4LP19A2B7wvwWfr6BsD3hfgs/X0DYHvC/BZ+voG
wPeF+Cz9fQNge8L8Fn6+gbA94X4LP19A2B7wvwWfr6BsD3hfgs/X0DYHvC/BZ+voGwPeF+Cz9fQN
ge8L8Fn6+gbA94X4LP19A2B7wvwWfr6BsD3hfgs/X0DYHvC/BZ+voGwPeF+Cz9fQNge8L8Fn6+gb
A94X4LP19A2B7wvwWfr6CR4qzHlvqtb6TZMgNnxVKyHCjlUqd9mzCkLYBUAFX8RzWEejN+lqrtoP
/9k=

------_=_NextPart_001_01CACB37.491CE006
Content-Type: image/jpeg;
	name="spade.jpg"
Content-Transfer-Encoding: base64
Content-Description: spade.jpg
Content-Location: http://mmdownload.interoutemediaservices.com/%7B1f6bf083-a2a8-4f16-86a8-3f7df58cf0c5%7D/%7B61625953-b384-4613-84a8-bb6ec43d107d%7D/spade.jpg

/9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAZAAA/+4ADkFkb2JlAGTAAAAAAf/b
AIQAAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQICAgICAgICAgIC
AwMDAwMDAwMDAwEBAQEBAQECAQECAgIBAgIDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMD
AwMDAwMDAwMDAwMDAwMDAwMD/8AAEQgAZQEYAwERAAIRAQMRAf/EAKIAAQABBAMBAQAAAAAAAAAA
AAAGAwQFBwIICQEKAQEAAgMBAAAAAAAAAAAAAAAAAQYCAwUHEAABBAEDAgIGCAQFAQYHAQADAQIE
BQYAEQcSEyEIMVEiU5MUQZHRsjNz0xVxMhYJYYGxIxckwUJiQyYYofFSg7M0VBkRAQACAgAFAwME
AwAAAAAAAAABAhEDIRIEBQYxExRBUQdhcTIVgSIj/9oADAMBAAIRAxEAPwD9aeSZJcZBcT7Gxnyj
vPKM4Y3GJ2o4u47tR44uroEETNmojUT0evddBge+f3xfiP8At0Dvn98X4j/t0Dvn98X4j/t0Dvn9
8X4j/t0Dvn98X4j/ALdA75/fF+I/7dA75/fF+I/7dA75/fF+I/7dA75/fF+I/wC3QO+f3xfiP+3Q
O+f3xfiP+3QO+f3xfiP+3QO+f3xfiP8At0Dvn98X4j/t0Dvn98X4j/t0Dvn98X4j/t0Dvn98X4j/
ALdA75/fF+I/7dA75/fF+I/7dA75/fF+I/7dA75/fF+I/wC3QO+f3xfiP+3QO+f3xfiP+3QO+f3x
fiP+3QO+f3xfiP8At0Dvn98X4j/t0Dvn98X4j/t0Dvn98X4j/t0Dvn98X4j/ALdA75/fF+I/7dA7
5/fF+I/7dA75/fF+I/7dA75/fF+I/wC3QZ7G8kuMfuIFjXT5QHglBcQbTE7UgXcb3Y8gXV0FCVm7
VRyL6fXsugwJ/wAc35pPvroOpvOEYtHl9DfNynkSLXTcf5Dvrmhoc7vaKukNwTDWW8GPXxYchItc
6UWMvec1ioR71c5FVV3CdYlyhfzafPz5RU07LXBqCqyVUoZE39vsIN3iz8liRESwYskEuMgXhI/d
zH+Dmo3xboNHROb+Qqy7tvm41VOt8oDhMyqrmOye2x+njyOObTLjxq6qgR5Fwk21eEQHqNrhtMqm
eqsRUQPjuW8ySdNugRrUk4mQ293X4xY2tlEi1o6/y/Q8wJjc+tB23So7J6vX5Z3QjZn+5shN10Ge
tfMrkj5kv+mcXrbGvRLWZVK8N9Pm28Wio8PnzoEcVLHlqGfKsMlIIcgjGxQfL9JOpyqqBs2jz3N8
rx/liySrp6KFjEnNaDFpvzEwtnJs8bmXcZ0y0gbIyEMIAxU6WEV6naV3gxWtaGrMY5r5Jh4tFPPq
MduYmN43xEa5vJE+yFaWZuSP6ZDAX5ZUM0s8MWzKWWZXtG86J0N2VU0GYs/MNkocin0dZisOc6lv
clizI8ePfWU+2q6PPkw8Y61lZGOGusVgsLLIWUvyyuYg02VyLoMxytyBluC59ZWdKsWfS0PFA8kt
aSzmzxQjMFmg4Mo9fGioof3ssMnbGYmzGNTZyORdtBQn88ZOyKVanEoVnP7HJRQxBGmlI5MIz2px
WOZoAsceUiVU8so4RIpTEEjA9KuRNBGw83ZLIvKCbBi0s6dkdPg9XEZHyK0NhplyXk/JcUbbDrxj
eaDNJFrRvepGOlxupwCscounQXdR5h8utLHHoAsTr5hiEr4+RRqyPfzJByTc/wAjwg8ikKEBoNbF
gCoEmOWwI3uIRRtcisVyhbJ5h87/AKen2x8XxeCeuvIdXcOlS7lR4k+VXWsr5DKatgUtYfXNhx44
7RESue2V3v5BvTQbSyPmWPFgQ67Ho4JGbTLnC6AkKyhX39N1k7L7GugNkf1AKujV1/BhOnbo6Cd6
lREcmyb6DVzuW8+p7fMJdlHpo1p8lxnBbQyrWZe0tXYToXIh7F2PQcfWZOuZt2ajAiAjK4g2uRxn
dMd6oGRh+YHM7KZXNg4VUOZb4KLKaWqkWsqPZ5BJXDTZDLbRTSgbXTh11wNsE0NE+f7T0ko3t+Gg
ltfy9kUvh3J+R21dDPssbkyHOhVsid8rIrqwlaa5WZBlqK1pLavhnlMfFk7PaQDSLuIjdBDLPzEZ
OORlkmpx7H5VFiS5LePlyZliw99iOP5PBxLepcFhAitZVgyaRCkRQIxg29Cqrn6C7xvlXMT2rqLH
6eFbIG5zC6u3ZJkkhZjqdnLEjDhQaKdPJHhwf22GrzsEZzh9AmgCxXK1NBMeG+XL3kos8llQBg1p
KKvyConwol0CKJk2wtIRKKwm20YESdaRhQRGU0NXR3sKqJsrF0EBqvMJl1rLZUxqTFS2c/IMHrK2
WKRe/sbI2YHyGKZqzSRmOuVqJNH0pNhdUOWqvQeyN6lDC2PNmbZZWY4yBGrqAbJPGNhkkyvn2YJ5
JV1yjKx0kKp6Ucx9NJBj72yBHcjiCkqxXOa1zSBO+XeQcqh5MPFaBY9dWVNhxPY3NqObOi3R1yfk
Fte2BBSM1YxK0kWrcKUMqt7w5Dm7q1FYQIBfc455ehm09QlDTz4uQcfT4lrWPuTwSVlrnxcckUz5
xWRwXovnoYmSZkFywzhWQBvttVUDb/G3LNxmGbXmJ2lfTMFCqJlxCn0hLM0ZnyGRHx+TXEnTQMg3
RUVjCukQnLHE9XAVXEY/YNaN8xWaKIsM+NY5AvS5JFo215X5BOlUJC1mTWpYd1SV8UtzYFJHowLF
mQ2fJSmSlexdgvRQyYueM+OG7u3YVT1+N4qzjkuStsZVkO/jf1tXYZPnx41d22N3pR3U16lKo0cN
olViK0iODGs5uyM1tb3MasB3plPSwMUhHt7L+nXguuYshwSsuLOsGrmulLFgNkEOHoIYew29LFaq
Bm2845+HJoONS8JqzWEM+OwMjgVEiyt3mkZFc31UGzrbiuHMoqerhCqQyDNsCoVjZDmb9YCJoJXg
XLOQ5NhWb5Jb1WOwrLFIsk6VrbSRV/Jzo9QSfKpclFcDbKpC1koXafLeny0kS94SdCLoNe1vLmc5
jd8fghlqapI/K0nG7x0WLfxIORVRcEJkMUo4Nq2JZBjLDlHcxpmqhDjjHb7HhoJDmvO17iuYZFQB
qKKdCrKrMTQ1EW1PKBPxjjuVncYlxOCFtOFLR0Mkf5BhEmhG1DPVGPYjg2Nxfnd7mB8rr8ir6mDP
x2TjjmOpTTDRCw8mxWqyaMJ7pzGGfJhtsVER6NY16pujG/SG3wfjh/NH99NAP+Ob80n310ERyHC8
cyqTAk30D591dCv64AnnOOO+Dk9atRdRpAREYw45kBVH7W6t33bsvjoMRjXGeK4tV3dVCDYTg5GA
UO6kXdpNuJ8+BHrUp4deWZNKQyQYNYnZCNqojGqv0qqqERD5fuPgRuyL+pmSmugdq3blNyl1HFX0
szHARI9iknvBhOoJ5Ibwt2G4GybIrWqgZ+t4ewGolwpcCpKFa6WSXDAs6YWKHu4YDAXxuyUr0JFX
HI6D6XdS9aq/ffbYMG3y/cbDoKfGwwbaLW0wbyIL5O+tIcqdW5JJBKu6m2lxZAjWNbOfFE1wyKvS
waI1U9rcNh1GHUFHWXFNXw3Mrr6zvbazjPOZ7TSsjkGk2qMd1o8ASvO5GsYrUG3ZG7aDX7uIuN8f
xW4oZsmdCpb0eJVcudaZJJDJY/G5cYGHAh2ck43RJEGW2OGK1iornNGNEXwaocncC8ducNyxbvdZ
c+TYKuSXT3XrLK7DkUmHfFfMca2huuQNP0lcruvfdy9Ttwz2YcU4fnNilpfgs3ynVQaKQkK4sK+N
OpRWbbd9VYRYpxx50GTNY1xGEa7qRqbbKiLoMEbgfjyRJspRYt04lk+4L0f1FbpHrT3d9W5PJkU0
dJXZqjBv6ocoTgtbsRV6upEajQuofCPH0E9bKBXTllVZaWSCSa3sDnNMososMxizppDHe6ZLkZBa
HMdz9+4j+jZGoiIFL/gvjpJUCQyusRjhHbIJAHd2ja20eHJbPL4TbqCkns2o67ILc5wIZHdKORi9
TGtagWDfL3xsOGSGOLejc9QhbOZkt0lkCpjVM+gj49Hm/N94VCKktJEVI6L4iKu6q7ZyBN8gxbEb
yprMEnEZCHHFBsqCDX2jq65gMxSTXOhWdM8Rmzx/ssl8ZqmZ1NYpGNevtoihr+Lw5xA+RGq60xB2
UNleUYavLpwLlGYl+9UskziQrBli3cmWSo9g9FariyUR6tf06C9Z5feMWoIRamwkxBU7Kf8Ab5F3
aOryIPHlxNlmWIySwTrluOr8q2Smz2MRHN2eiOQJRjOFYXExa+x6oK67p8imX4clmSbk11Lt7KUx
1DfNsrJTlIs4LIXyhWIrFCoehWtc1dBHHcCccOqqClSvsh19BXGpmgBc2EZLimkW7b6TU5D8uYSW
9fIuEWQ4ZE263O22Ryoocm8M8a2pK61jBkyQgsbKx64N7MfAt1m5b/WJIVo2PIdHs62Fk4UOILt2
jeNEXfx3CQYlxbiGFGnmpIs/edXipmjsLWfZArqMEmZMDR1QZZysr6oUqwMRBMT+Z/iqoiIgRvHO
FeNa79ssqVLGeOvk4/JrJJclsrcAVxGVbOpARiHlyBth1zrQwuyxUF0tRFb1I5zgq/8ABHHjT1Jg
wrWM2mZVsBHjXtoGLK/ZskkZVWus47JCMsnxLWadWKbr6RlVqbK0asDJZPxxgmT5bXWtyaSzIvla
uQCviX0muS1iYheguIMuXUR5Am2oqmxntY4j2PaNslGqqOUStDDR+AOOokORBjx74YixKuDHIuS3
JT1kSjvyZJTAqDGlEdXCq7QiuE0Wzdv5kc5XOUMzjHGuC8d2QrWsLMhSpcY2NwUuMhmzANjWVs+7
ZTVceylEEHqsVI8Qgoj3K5+/UqqutG/qum6bk+Tspr9y8UpzWivNe38aVzMc1rYnFYzM44QwtspT
HPMRmcRmcZmfSI+8z9mFFwBxzHAooke9iSByYR66yjZJcitKQFbHtIcGrpZqSu7X1MeJdyxoBvsO
aZerqVrFbvZpDD4jwWBQ5LjUSqIGmyysrai3ifOy39UKooIeN1zI5SleWOWPWwR/7iL1uKnccquX
fQWJeFcBLWirPkJwgx8Yx7FIpwWkwEyJX4tcGv6WVFkiI0gbWNcHcdZCe2R3g7dqq1QwTuGuIqix
xqDJc+HKllCGtpJmUzANzGzx8lxk4pU2rLOY7JrepJPnTnORr3sa4j3p0NTpCR1vE+CY9jOUUCAm
Ppskq212QSLe6nSpDqWBVLUwof7jLkKWFBpqlnbB0ub2mN6lVXbu0EUoMQ4YL+0mocujWkpcox7L
qyyj8gfu9jPvJ+LOjUpGTf3OSafGyLFoRSjAiuHKioR4k7TfZCtb8d8O2mT3/wC4XAUyCdNkjt6N
uaED8pZ8h4lPxMirj/7h24VnlWPiIgHKFDG+W6grsxyaDaNBiNFjUq3m1EYgJF4tQti8kk50KlFT
QqCtaxhiPYJAVsAbV6URXu3c7dV0ErB+OH80f300A/45vzSffXQdJM/zzN6vlfLo1VlCwEpZcKFR
4+exMYdnAlcVWN/IZExCLUTCWMj+oB91tkUwwAeDsPXZyJoIUbPrAdTURgcyZMerLjGR5BPtSTIs
QkLOIHGmJX1XjDMsKhhXQZFraSpDoDUH0EX5ZWO7S7hd2PIPJUdbDJBZNfpcisp1eLH1aJ1QOT/7
fP6s7SUSxVVZLclAwrRLu1hEXpYjnvVwcIeZ5TPtYuN1PJOT2WOHGaW2+i3ESbYFsF4VuMstKxl6
KI9qiiXsMT1A324qkVGqNenpDFv5Lz7EoQMtk5nkdvWRcT42vLaFYnFKG615I4zziR1iEyOAQYUf
JqyEoA+A2EVqrvu5VDemfWV5jdLwnS32cW+OrYQLeDmOQDtBVkybY1/Hk+W10qwlje0RZN+FqNVd
no96dKo/pcgadpMmzu/qJGQ3eX3Zx11z5eq8dBIFCdVnLlUHjW1tbWUGRFIUkmUYalGjVYNj5BXt
RO6ugH5CyR0YT28lXj7i8zJ9fmOOGnCpoGLVouScopYTw5V2ZH9CpNra+NHUHY63MXvbruiaDdVL
l1tlfl+yB9Fm8e3z3HsVsCS7mkkGfOHYwRyrGqUjpMGBIdJtK2IxqmUDGnc9z2+yu+g0PYcqZhcR
LvLCZzdY7T21NyJmHHYY0uPWxrK5xi3xXGKPHgslhO23iEeCaZa9qq4ymVz2q5N9Btzj3kPIbnki
jx6fkRJBW5Tz3Hu6NxxKaJBqLigTFQTYfjJihhCJIbE69lVnUiKqIug1lmOeZ/SFySyrsxyFXzMg
54pmwzzAur6mrxPNcVg1ZK0Toj0gFrK+1kf9S7uPEzbZUYxGoGONyJnYbJsAXIoWwac1nIopz8rn
zIkqQLPKiD+0zbAeLrL5KPFgyHQ+1GEo+2ZCITqY5UDZPGtzKu+bY0m0yGZa3IQ82wptNKlgK3Go
1fnNJXVEKNBaNsqrjmrYY1QZHOR6sV6e056uDRx3TMfyPli1x/K7+Bd4zX802bCRrdppQzV/LeMi
iBnsMM5GxrJj0PIb7CynoiuVWK5rg7E8SZhlNzypewrbKElhKXksUvGJFsecevTHs1hVlIcFGCpG
DFBwoBVBtIlK+c0ncRrnIqoGip2aZBisGxZiGY2LZU7IuVxZJSBs4zYuNwh8uYtFiWjRMjFfQHkw
buY5Z5keqNeqtXpGiIEohZ5lH9QYbXyuTbGbWkyIlEyLQW5J9h8pM5FtKeDLPYWNRUx+RgOhR1rJ
J4TlLCYNk0bSdS6CYYjKmVnBPGsSiyW3hyLblfH8ftJsOyYawgR7bPi19hXCeVkhkTrhua9QvYrV
cRXOaqPVFCA0uf55MtsVrpmeT4jY8qmr4a2V9IiyL4ErmPNMSnNJWQqifYZZPkUlYCKpWOF8k4aG
VzVV7tBFsfzfMMEoMYrcdyS3m19nCTJ5ER0pZ7KSLx9k+b3mdQUTZywgzqOFDWQLwcb5jpc1UVNw
m9FyDnJptPPtM4uhW0ux4xtsSxtZUcUbJKHkfPMkfdhJUlipKvgVmNLFCxzNvkmjRW9H0BEJOQZ3
WVPFeZyMsyO5m5Jg+QS8pyB7ohbTD8PPkOCVF1NxwKCZ1yoVfFR6kf3Cd4xJKqiorkDvlk15nNeS
A3DMKqswgHiIU0+bmw8ecEnV/tMGJ1BcJNGYOz0KhG7qu230qGHyvjSl5WrcPkZ9Uur7PHpwL1lb
XzoVkGJYq0SyKyRYSalEtqgjhNQwVEMEroapBu6WdNI8z/H3jvnnwv7+l7fA6mN+rl5ONuGaX56X
59VsR7mqf+ezFfcrblrjl9z7R0fdva+XEz7N+auMev2nMTms4419J4ZicQ8xanmbM5d+XGrznbLm
4/e8tYXX5jmldc11dTV2D3lnyyQNhFt5sGHa8J3JbLGYFPOpJIQI1sdpwGIyWjtXd1G68h5k5Lxz
yjcJ84ycmtiT6DK66Tmk4kcCPyzDZ8nLMLqpFsBsYIJzJhJ9TO7qNaM72oZEVzmOQOuEfmLnmfFq
qvJuRshxsWKZPj3CGezJ2VJgwSZjjdVzbeWtnPzSVTWbKeXYArqMjjjGclkxjAud4q1A7Ccl5Ea5
w/yTZNmvI5MfmWlHl1hcck0s4mLGLYTeBr5R2kKfkFZBPVmyKaVg+t8UBFdKXtNG5Rq0NO0PmK5P
l0lJX3HIkxuUWWTcJmWmlHgssp+KXvlJs8jyKctScSmkU1tmSR5kgqDWOs4iK3p6kboMBjDA2+U8
QXl3ezqfvZr5ICWE2DZsoIayLbyxZjOJKMkdI8MEgk6K0IlajEYOUUTERCqmg3dzkd1tzhexbrIJ
1LS455ivKkEEuFYioW10S4wvKpE2TJswsARXAkp1hIcjvl3Ed0dPWqKHqHoKoPxw/mj++mgH/HN+
aT766CwWFDdLbPdEjLOYJwGTVAJZbAOXqcFshWd5onO8Vai7Kugt0pKf5dkNKmt+UHI+cZFSBF+X
ZLRVVJTAILtNkIqqvWidW6+nQXiRI6EUqRQoVx/mnFQLEI6T8skL5lX9PUp/k2oHr36u0nTv0+Gg
oAqq6KwY4tbCjDCUpxMBDAFgjHY4ZzDaMbWsKYb3Ne5Nlciqi+C6CJ5px/VZvVwqSeQ8GqBbUdjP
iV8aualvFoJaT4NNKLJgyTRq75wbHO+WcE3Q1WNejXvRQv77DarI7fF7izaYpcUlW8qHEVoCQJn7
1RzqCYCxjnAVTg+Unuc1GuZ7aJvum6aCQpXw0arEhRkY4kYzmpGEjXFhKFYZVb0bKSIscfad6R9t
vTt0psFF1PVvbNa+rgPbZOa6xa6FHc2e5n8jpqKJUlOZ9Cv6ttBjS4xBZHyBtUj6awyGK2PJtYog
S5AHAr0ra98eNaCnVyBrgIiijKFYqOVyqNVe9XBZYtg1DieMY7ikGG2XXYxHAKtLYhjyZSSA9T32
Ln9hgxz5ByPI942MRHvXpRE8NBJB10IR3yhQYopRXkISSOMJhyEKwTCveZrEI95WRxo5VXdyMai+
hNg+/IQ9np8lG2IklHp8sLZ6TXI+Yj06PaSW9EUu/wCIqbu30FFtPVsZCGyrgNHWvV9cxsGO1kB6
rur4TUEiRXqv0s6V0FQVdBBIJLDAihlGUriyRRQjkFdI+X76kMxiEepvlBde6r1dpm+/SmwcUqq5
CyDJWwkNMaRssqQwIWU0qCaVsgnb6jtI0LEcjlXdGN39CaCqKDEAc8oMOOGVK6PmpIo4xnk9tNh9
8zGIQ3QngnUq7aCj+01vWYn7bC7kgRgHf8mDrOCQd8mQEzu31EEeSVxHtdujnuVy7qqroPo6quEs
NRVsIa1zHjr1HDAxYLCN6CMhq0afKsexNlRnSip4LoObK+ENijHBisG6Us5zGRhNYs1SodZitRiN
WUp06+5/P1+O++g+LWQFKA618RTxXGfGMsQKljvkOc+Q4BFH1hcd7lV6tVFcqqq76DglTWt3VtbB
arlmOcqQwJ1LYK1Z6rsPxWcrU73vdk6t9Bz/AGyB3Ihv2+J3q8bgwC/KB7kITmINwoj+31RhuG1G
q1itRUTb0aAtbBUbQrAiKJkU8FglihUbIUntfMw2s7fS2LI7DOsaJ0P6G7ouyaC7RqoiIjVRE8ER
E2RET0IiaD7svqX6l0GHfjlCWPZRCUVQSLcSFl28Z9XDfHtZTnMc6TZBcBRzpDnCaqvKjnKrU8fB
NBemroUiJ+3yIMU8DoEP5I0URYnbArHBH8s9jg9AXDarU6dmq1NvQmgtJFBSSwTI0ukqpUawktmT
48itiHBOmMaJrJUwRAuHJktaFiI96OciMb4+CaCvMqKyxA2LYVkGdGaMgWx5kKPJA0RgOjGE0Jxv
GgyxnuG5u2zmKrV8F20FD9gpO+2UtLVfMsHHC2R+2xO+0MMMiPEE03Z7jRxQSysG3fZjCPRuyOXc
PjqGjcNoXU1S4LXQHtE6uhqNr6pGpVvaNQ9KOrUY35ddtw7J0bbaCrJqKmakhsyrrpbZZIhZbZMK
MdJRYD2EglkIUT0MSEQbXCc7dRuRFbsqaDI6CqD8cP5o/vpoB/xzfmk++ugpaDmz0/5f9qaCroGg
aBoGgaBoGgaBoGgaBoGgaBoGgaC2myxwIU2eZpXhgQ5U4zAM7h3BhgJJK0I1c1CFUYl6W7pu7ZN9
B08tfPlwBTr0y5WYK5FRFaLGwufuv0dK2rV9C6CJyv7jvl7jsc8cLkOSiKqJ28fq2br/APdv27b/
AOOgjxf7m/BbfAOI8nyHbr4JW44JdvX7eRL4aCh//pzworuluFckq707PBjg08fR4pdE9KaBI/ua
8PBViNwPkQnUxHbouOojd/XtZOVdBTb/AHNeKHoqs475BTZN/wDdPQC/y3SWVP8A56CoP+5XxoRU
6eOM2Rq7Ijls6L0rtsnSi7+hdB244N50xDnvF7DJMVDNry0twSkvKO0cB1lVTOyOXEeZ0ZzgljWM
MqEC9q7Ls9q+0xdBudfQv8F/00FDQNA0FUH44fzR/fTQD/jm/NJ99dBrLlnMrfj7BLrM6mupbT+n
RtsbKFd28qlCaqCq/Njgy4lXbvfbGcrBxxOF0kI/bdXdLHUb8jeUdy8L8R6rynt2jpeo+FWNu2m/
dfRW2mv8413pq3TO63Cuuk0xa04zM4rbl9567d2zt2zr9Ndd/ajmtF7TSJrHriYrb/aeEVjHGZ/x
OtvK3n3IXIGIyE5BrY0G0xmSHFrAsuVKZlknIYSKe1JkdE+jqYtKhYMyGSO0bzOex6q5fFNUH8B+
ZeaeYeL7J800a9PcO33jpdk3veOst1OuJttnqennRppozrvptritrzaLTNp4w5HiXcu59x6Gf7Ok
V3aZjXbMz7k3jjbnpyVivCazXEznPF4v+aDz7+azjTkHJo3HWfGkRZvLtvgWHYtLocWNAU0nKT4/
j1cKbJpDyOx3VCx7iK9Ua5XKqr6fd1rek0dn90Tj2o/cr13lh5zlwo/cscUoP6ixa9IcbUWRFqbK
XXYlW2BRvRWMVxGKT0tG5dmqGd4Y/uBcYZ5mDeIuXaS28uXODJ7aZMG5GL8tSXtyrFIldi2Wyo1a
AtmYSIQcCxBAlkG5qgSQ1yPUO/DmuY5zHtcx7VVrmuRWuaqeCo5q7Kioug46BoGgaBoGgaBoGgaB
oGgaBoKMmOyZGlQyORg5kaRDI9fQwcoL473r4p7LGkVV/wAE0HgHz35SOdeKmyrrIsLm2WJDMYkL
MqKRHyLHJkJxXfKzG2NeSQsYJxbKiHQe2+3p0HTZ7FG1zXj6HOVUcP0qxU9O6b7pui7aDGPTd3gi
9SbJt6PBPT/lt69B9ajnOVWNRq9O67pt0/R1brtvttoMh07dLnK571T2V9ldvTv4p9H16C8j+yxU
Jsu6rs1UTff0dP0/QvhoMkj2Mb0qioi9Ks8U2Tbx36k32VOldB3s/t5chxse55lYQQpmA5Twy3Cx
HPd8sXIcJ/8AUFc7p/ldKJSfuLGuXZ3T4eKaD3CX0L/Bf9NBQ0DQNBVB+OH80f300A/45vzSffXQ
UHMa9qse1r2OTZzXIjmqnqVqoqKmotWt6zW8RNZ+k8YRMRMYn0XMJjGyhqjWtUhxOIqIiK9yKNnU
9U2VzkYxE3Xx2RE+jSK1rMzWIiZnM/rOIjM/fhER+0RBiI9Pq/Ipy5J/evMVwNCONrh2fnDxEhVJ
v0HU3MtO96EcqeKNRVRf46lL9ecpd5MhfWcq/WR2g8lf7uXEOH5RwHF5QmUkB+V4hkFRSEuGhGOw
nY7aBsyRq+VKRGvkNqLmOE0TrVVAhTtYqNK5FDprw/5wvNHxVSXNPjmVVHKWDcbYjW39zA5ke2bY
4/RyLaBjlfEq8wBZ1eTz2/PzQiFGe+a4THIqIjfDQe3nlBzDlrzH8VO5Ry3HMDwuNNyC0paCtx+f
e3D5saj7Mexs5sieQTY6GsSPGETEcqMErnLu5EQOxs3EcljP6REqjKi7Knbkou+2/wD/AE7on0ej
06C0ZjWU+HeHWi/m3XYzkREXZrlRJXUiO9Po0F43EshXwUlWq7Kq9LZf0br4IrvHwT6F9Ogug4Xk
Bk6t4LWqngvSb0/+JO6m2/q9OgunYDkXh0Hq0RyJt3Uko5F23d1Na9d09W2/hoKrePMjXdPm6hV2
RU6GTFTx+hVVzfV/loDeOsmc3q+Yq09tW9KjmI7ZFXdVTuKiIrU3T06DoP5hPMNzBwrypMwPGuB8
P5JxyBR0lifKp3mW4c4rtCWVmEkiZWgxDOLcVq2LXjcJrZJu2yQ57lYnS1HKGtReeHkQTWEtPKdP
EFXdDyVPmw8pdsrHo1Fc1RG5JrH9Xj4b7b6CXwfOfMOPuTvLdylC22VWQOUvKvkD1RdvaYyu55Y9
6Lv4eHjoJBE84lBIe4Z+Euf4pGNRz2jo+L7fZF226f2LlqyUniu3sou6r4aCbxPMhj0piEdxpzZD
T2d2z8JpYjmo9EVrlQmYbObsviqbomy77bLoJvN5gwarolyG1tAQYQxgNKiMuMSubqCKQrWtfNpM
bya7shOErv8AcG0bzM2VVZsiroIZjHmi4Bz3Ja/A8P5axKVmt3IWDV0k9bSrmuN0kIcvy9lXRHFW
LGCQiDaquKrEY1FVdBtWwp8wpGWLsNt6G0oZTCfumJTosODAtxmaoZA3VMxDYvZMlDX/AHBFDCO/
/uyRroPDHzQ+XHPsYy3IM7hYBS0uC5BZlk1qYQKwDT0SPd41lrTzpdlIoZgFRW7tOSIf+YRHbroO
obcUunuVzYEjbZ3oa5dlRfR6F6k0GVi4DkBl6kr5LURGoq7PT0+lNneGy6DO/wDGuQ9LUbDIqez6
WORd9t1TqVvp3+nQZEPFORmRiJGVnW5E3cN7lT07/T609Wgzv/C9+VjGke4aOXbwY7xRfT49Kqnh
4f8Ax0G3+FMMl4PznwjbMC4Jq7k3F45jqqopIl6Q2MyxMaqJ7Jot09HeO2yroPfd3oX+C6ChoGga
CqD8cP5o/vpoB/xzfmk++ugpaC5h/wD7IfzR/wD5G6D8f/I5GC8yXBYSv3/b/Nvgju05V3Tucw1C
OVfH2UVzF8fDQfsHkNc6UdjUc5yyCojURVcq9xybIieKqug8If7yHm64+oeP8Z8t2KXLct5VzPP6
6KTEMZCS8tzWcGFKFAxmBDr0PItMidIs+8WHGYUoO2NpEa96N0GvOF/7c/m+5KxCQvLGU415dsbz
Ouq2ZNhZY/8AWufXlbDmRbqBV5PTU8mDRUTIlpGGdYhLYpxnZ/uDa5OlA9ffLVw5zD5Z+Oz8ZUHO
NRl2PDvrK9pjX/F7INhUuukCW1gONX5iUc2IWaFTC3axwnEcntIqbBtixjc5TSKUXKOMxiOVFcrc
KnuY70f+WuTbb/56CkAfP4goEvJmESdvDrdhFsNXIm3Qr2/1IVOr17eHq0Hx/wD7hd/Y5E4/d4Ki
9eI3bd2/QmyXD9tv89BSR3mObt0cg8cbJ6Gri983bw8F9mauyp6vRoOHzXmcRepM/wCM3qiIiddD
kjdkRfFE2euyL/mugvQXHmWAxWvyPieU5d/bfCy2P0LtsqsYMT2p1/SnjtoLd915m0YMY7jiN6CV
FY9SZoEnp3cr1bXFR/gu38NBpTMcT812RXcqZEo/I7ZRJYhqSw5I44zPNMkU/T2yCJLZWQRnhia1
vZRz+piKrfQiaCMxeDfMNLcr7ln9v+Im6KwdX5RLC3Qfo/lWzzSrYqoielW+P+Ggn9fwln7GNbY3
PlZC5NlVaDyUYFFdun0sLaZvZuaqfQvTv69BPqni+zrmo015xu/wb1/tnlp4SqFcqKi+yQlFaFZ6
PDdXbaCTJx5jEsbg5Hj2B5WF7kV4bjiXidol/wDCjYWFx3I3df8A6tBRdxBw04CRk4U4VGFPQwXE
XHY/pVfFW43uq7qq+vfx0FnXcHcIw7evtE4f41JIgywSIv8A6MoAshkY9uxYQ4sCOyOUfpbsmyKi
fRoOwNpgnGmRObWVvDlBn1g5UA+NR4nVSokcvirR2l6X5XH6r20XqWRKa9q+PQ70KGkebvL65ayo
h3GL4rQsjOWZFwzAKeFU49Uq6M8QRXOQhhwbjPrtwiuUjnii1kdz1aIDnp3tB0nj+WeSB6q6qYm7
3vX2Fdv1vVyIv0K5v0/4JoJhXeWx73sRa8adxyNa3tu/mVP+6m3Vvsmg2DB8qMtzU64Dl6lTb/YR
NvUiL06CXQ/Ki4bep9eruhFd+H6V9O3g1Pp/x0FU/loI5GtbWbKxF6lUS9W/0fRvv46DT+T8KJjG
a8ZzCwlGZOSsQAH0om8a3BcFVERVTccOrI5fBNmpoO5rvQv8F0FDQNA0FUH44fzR/fTQD/jm/NJ9
9dBS0FeO5GGG9fQx7HLt6mvaq/6aDww5F/tfcx5jll5lVJlmA0F6Pk2NnmEZGS6tTLjqVWTzMlqp
T6pmLmU9uOS6OvQpFjsUa7oTfbQdxbHy0ecjk+uPT8yedmRQ0k2IsWzrOC+N6fEbCyaRqNkOk5Cd
K6SxZLVd1N7RQqq+I1b7Khs/y8+Rby0eWa2Nl/H2CfvHKE2KkOy5i5DmrmvJ0mN1lK+JXX1gEcPE
qxxTvd8pSRa2OvWvU126qodvNA0DQNA0DQNA0DQNA0DQNA0DQR/LSnDimUFjK5JLMdvFjq1/bekh
ayUgFYT/AMt6FVNnfQvjoO7FRn5KylrKWsrotVErK6JBEMTO44TQAYFrfZYMDXqrd3bM9K6DXOTT
H2ZiyZPelOftu8ntdPrVqOcr09PrTQQJwI4mjY2K92799t2p0qvo6kRF9P0broM/UNaI2/ye69Xs
tViPcvV47oi+CbaDasEz+lrnARGtY3x6Gp4rsieGyeKInj4aDIlKzsuYrU6nLv4Jt4J6l+nwT/DQ
RyVN9tGdpBovoI9ERFRE+jdE39Ho0HUHkU7Ml5nw6pYjvlsDo7zO7FiDRRMtMgEfDMWGQiojmmLE
NbyGN8V/6dF8NvEJMvoX+C/6aChoGgaCqD8cP5o/vpoB/wAc35pPvroKWg5s9P8Al/2poKugaBoG
gaBoGgaBoGgaBoGgaBoGgaBoKEmOOVHLGK1rxGb0EY9quY9u6KrHtRzVcx22zk3TdF9KaCUyMuyI
5in79eNSqq9psE6hYrlVfBqz+4uyr4e1oKwswt+2jJUaolbNRvV8rLEq7ehV/wCvJv46C3PlNq/d
oYlKNionU0sacZXKieO7ksB7Iqp/loMhW5pOhOR8isrZT0RNnMfLjI3b0o1vdN4fxXQSIvKti9rW
soqpjW7KiLJmuRyp4Kr+lGKqLoKH/KFo5P8AcpKlXfQrJVgzp2226UXr8P4+OgoP5GmKvW2kr1fs
72TTpbxKqp4bsaBqo1P8F0Grhw0W5yLIZA4zbbJ58aXYPitKgBRq2EKtp62OpnOKsWvhiVU6v5jG
K/ZOvQXi+hf4L/poKGgaBoKoPxw/mj++mgH/ABzfmk++ugpaBvt6NB93X1r9a6BuvrX610DdfWv1
roG6+tfrXQN19a/Wugbr61+tdA3X1r9a6BuvrX610DdfWv1roG6+tfrXQN19a/Wugbr61+tdA3X1
r9a6BuvrX610DdfWv1roG6+tfrXQN19a/Wugbr61+tdA3X1r9a6BuvrX610DdfWv1roG6+tfrXQN
19a/Wugbr61+tdA3X1r9a6BuvrX610DdfWv1roG6+tfr0HzQNA0FUH44fzR/fTQSPKmY8l9aLQyb
J8B0+UomTIUcSiTvv3YIgrAynAi/hucwb1Zt1NRd9BHNge8L8Fn6+gbA94X4LP19A2B7wvwWfr6B
sD3hfgs/X0DYHvC/BZ+voGwPeF+Cz9fQNge8L8Fn6+gbA94X4LP19A2B7wvwWfr6BsD3hfgs/X0D
YHvC/BZ+voGwPeF+Cz9fQNge8L8Fn6+gbA94X4LP19A2B7wvwWfr6BsD3hfgs/X0DYHvC/BZ+voG
wPeF+Cz9fQNge8L8Fn6+gbA94X4LP19A2B7wvwWfr6BsD3hfgs/X0DYHvC/BZ+voGwPeF+Cz9fQN
ge8L8Fn6+gbA94X4LP19A2B7wvwWfr6BsD3hfgs/X0DYHvC/BZ+voGwPeF+Cz9fQNge8L8Fn6+gb
A94X4LP19A2B7wvwWfr6CR4qzHlvqtb6TZMgNnxVKyHCjlUqd9mzCkLYBUAFX8RzWEejN+lqrtoP
/9k=

------_=_NextPart_001_01CACB37.491CE006--

From blu@infinera.com  Wed Mar 24 08:57:44 2010
Return-Path: <blu@infinera.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36E423A6BC1 for <ccamp@core3.amsl.com>; Wed, 24 Mar 2010 08:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mU4EKs9JzG21 for <ccamp@core3.amsl.com>; Wed, 24 Mar 2010 08:57:43 -0700 (PDT)
Received: from outgoing1.infinera.com (outgoing1.infinera.com [8.4.225.36]) by core3.amsl.com (Postfix) with ESMTP id 90A473A6BC5 for <ccamp@ietf.org>; Wed, 24 Mar 2010 08:53:06 -0700 (PDT)
Received: from SV-EXDB1.infinera.com ([10.100.97.30]) by sv-exhub1.infinera.com ([10.100.97.36]) with mapi; Wed, 24 Mar 2010 08:53:26 -0700
From: Biao Lu <blu@infinera.com>
To: "ccamp@ietf.org" <ccamp@ietf.org>
Date: Wed, 24 Mar 2010 08:51:43 -0700
Thread-Topic: draft-ceccarelli-ccamp-gmpls-ospf-g709-01 - new proposal
Thread-Index: AcrLaeagLXCayM83TLyat720L/bGXg==
Message-ID: <89F90D43540BB04BB165F3932DA603BA01D7C1B052@SV-EXDB1.infinera.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [CCAMP] draft-ceccarelli-ccamp-gmpls-ospf-g709-01 - new proposal
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 15:57:44 -0000

Folks:

After reading through this draft, I have a different proposal:

1. ODU and ODUflex are really different encoding instead of different switc=
hing cap.
2. ODUflex really needs the service bandwidth instead of TS numbers.

So here is the proposal:

a. There is no need to define a new top level ISCD as in Section 5 defines =
a new ISCD. We should reuse ISCD defined in RFC4203 with Switching Cap as T=
DM. But we will need to define two new encoding types:
          ODU
          ODUflex

b. For encoding type ODU, I suggest to change the Max LSP Bandwidth to enco=
de as TS numbers instead of IEEE floating point format bandwidth. This has =
to be agreed by folks. We can't use IEEE encoding because the TS is differe=
nt rate in different HO ODU.
=20
For this encoding type, we should have a 'Switching Capability-specific inf=
ormation' to list the supported LO ODU. It can be same as the 'signal flags=
' defined in the current draft.

c. For ODUflex encoding type, I suggest to keep the IEEE floating point for=
mat.

Also, for this encoding type, we might need a 'Switching Capability-specifi=
c information' to list the supported ODUflex if certain equipment doesn't s=
upport all possible ODUflex rate.

d. suggest to have a dedicated section on link bundling.

Thoughts?

Biao

From davari@broadcom.com  Wed Mar 24 09:20:36 2010
Return-Path: <davari@broadcom.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A86A63A68C4; Wed, 24 Mar 2010 09:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level: 
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GVSDpjP1KEQM; Wed, 24 Mar 2010 09:20:35 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id EE5463A6847; Wed, 24 Mar 2010 09:20:33 -0700 (PDT)
Received: from [10.16.192.232] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 24 Mar 2010 09:20:46 -0700
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Wed, 24 Mar 2010 09:20:46 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Loa Andersson" <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Date: Wed, 24 Mar 2010 09:20:44 -0700
Thread-Topic: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
Thread-Index: AcrBczT1LsEVDiSwTX2v9QSMrvpjyAAA7NaQAn1wnhA=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD68171AE66FD@SJEXCHCCR02.corp.ad.broadcom.com>
References: <97ea8a23065211ee6df8f08ea5e4ba67.squirrel@pi.nu> <2C2F1EBA8050E74EA81502D5740B4BD68171AE5BF5@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD68171AE5BF5@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67B4E45720S68308113-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [CCAMP] [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 16:20:36 -0000

Hi

In addition to the previous comments that I have raised I like to also rais=
e the following comments:

7) I think it is too early for this draft (just with 1 version) to become R=
FC. This draft affects many IETF WGs and drafts and is really putting stake=
s on the ground before the requirements are finalized for other drafts.=20

8) I am concerned about not having a commonly agreed identifier for objects=
 in this draft and in most cases defining an IETF identifier and an ITU ide=
ntifier. That would make the interoperability a nightmare.

Thanks,
Shahram

 =20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Sha=
hram Davari
Sent: Thursday, March 11, 2010 4:28 PM
To: Loa Andersson; mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ie=
tf.org
Subject: Re: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01

Hi,

Couple of comments:

1) Why the Interface_ID is 32-bit while the Tunnel_ID is 16-bit? Do we need=
 to support more interfaces than tunnels?=20
2) The draft defines the Global_Tunnel_ID as:
      Src-Global_ID::Src-Node_ID::Src-Tunnel_Num:: Dst-Global_ID::Dst-Node_=
ID::Dst-Tunnel_Num

This seems to define a bidirectional tunnel. Is that the intent? If so plea=
se clarify. If not then why Dst-Global_ID::Dst-Node_ID::Dst-Tunnel_Num is n=
eeded?

3) Is section 5.2 talking about unidirectional LSP or bidirectional LSP?
4) Section 7.1.2.1 says:
	Since a MEG pertains to a single MPLS-TP Tunnel, IP compatible MEG_IDs for=
 MPLS-TP Tunnels are simply the corresponding Tunnel_IDs

Assuming the Tunnel_ID is a unidirectional ID, then this statement implies =
that for the reverse direction a different MEG_ID is required. Is that the =
intent? If so why?

5) Why are drafts part of the normative references?

6) Will section 8 (open issues) be removed before publishing? This section =
implies that the MEP and MIP definition is not yet aligned with framework?

Regards,
Shahram



-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa=
 Andersson
Sent: Thursday, March 11, 2010 3:33 PM
To: mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ietf.org
Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01

All,

this is to start an MPLS working group last call on
draft-ietf-mpls-tp-identifiers-01

There is a discussion on the OAM model for MS-PWs where we haven't been
able to come to conclusion. Once we reach agreement the document will
be updated. Comments in this area are welcome during the working group
last call.


Please send your comments to the mpls-tp@ietf.org mailing list.

The working group last ends eob April 2nd.

/Loa

--

Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///
   phone:  +46 10 717 52 13
           +46 767 72 92 13

   email:  loa.andersson@ericsson.com
           loa@pi.nu




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


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



From Alexander.Vainshtein@ecitele.com  Wed Mar 24 09:57:09 2010
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D597A3A6C9E for <ccamp@core3.amsl.com>; Wed, 24 Mar 2010 09:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.169
X-Spam-Level: 
X-Spam-Status: No, score=-0.169 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Un1dPnWqqIPQ for <ccamp@core3.amsl.com>; Wed, 24 Mar 2010 09:57:08 -0700 (PDT)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id EB0263A6C97 for <ccamp@ietf.org>; Wed, 24 Mar 2010 09:57:07 -0700 (PDT)
X-AuditID: 93eaf2e7-b7b62ae000003814-81-4baa424a19fd
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id CA.62.14356.A424AAB4; Wed, 24 Mar 2010 18:48:10 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 24 Mar 2010 18:57:27 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Shahram Davari <davari@broadcom.com>
Date: Wed, 24 Mar 2010 18:57:22 +0200
Thread-Topic: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
Thread-Index: AcrBczT1LsEVDiSwTX2v9QSMrvpjyAAA7NaQAn1wnhAAATxgMA==
Message-ID: <A3C5DF08D38B6049839A6F553B331C76C1078FB8EF@ILPTMAIL02.ecitele.com>
References: <97ea8a23065211ee6df8f08ea5e4ba67.squirrel@pi.nu> <2C2F1EBA8050E74EA81502D5740B4BD68171AE5BF5@SJEXCHCCR02.corp.ad.broadcom.com> <2C2F1EBA8050E74EA81502D5740B4BD68171AE66FD@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD68171AE66FD@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [CCAMP] [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 16:57:10 -0000

Shahram,
I fully agree with you that defining two incompatible identifiers without d=
efining the mandatory default results in a clear breach of interoperability=
.=20

Aside =3D=3D> Could somebody remind me when did the IESG revoke its once-in=
-force requirement to explicitly define
          mandatory default every time multiple incompatible modes are spec=
ified in a protocol?

On the other hand, neither of the two looks like a good candidate for the m=
andatory default:

- IETF identifiers effectively assume usage of IP addressing which cannot b=
e presumed in MPLS-TP.=20
  The notes stating that IP addresses, AS numbers etc. used in these identi=
fiers do not necessarily have
  to behave as "real" IP addresses/AS numbers do not really help IMO.

- AFAIK, ITU identifiers have hardly ever been used before for any meaningf=
ul purpose.
  Hence mandating them would be at best premature.

I must admit that I do not see any clear way out of this situation.

Regards,
     Sasha


-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Sha=
hram Davari
Sent: Wednesday, March 24, 2010 6:21 PM
To: Loa Andersson; mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ie=
tf.org
Subject: Re: [PWE3] [mpls] mpls wg last call on draft-ietf-mpls-tp-identifi=
ers-01

Hi

In addition to the previous comments that I have raised I like to also rais=
e the following comments:

7) I think it is too early for this draft (just with 1 version) to become R=
FC. This draft affects many IETF WGs and drafts and is really putting stake=
s on the ground before the requirements are finalized for other drafts.=20

8) I am concerned about not having a commonly agreed identifier for objects=
 in this draft and in most cases defining an IETF identifier and an ITU ide=
ntifier. That would make the interoperability a nightmare.

Thanks,
Shahram

 =20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Sha=
hram Davari
Sent: Thursday, March 11, 2010 4:28 PM
To: Loa Andersson; mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ie=
tf.org
Subject: Re: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01

Hi,

Couple of comments:

1) Why the Interface_ID is 32-bit while the Tunnel_ID is 16-bit? Do we need=
 to support more interfaces than tunnels?=20
2) The draft defines the Global_Tunnel_ID as:
      Src-Global_ID::Src-Node_ID::Src-Tunnel_Num:: Dst-Global_ID::Dst-Node_=
ID::Dst-Tunnel_Num

This seems to define a bidirectional tunnel. Is that the intent? If so plea=
se clarify. If not then why Dst-Global_ID::Dst-Node_ID::Dst-Tunnel_Num is n=
eeded?

3) Is section 5.2 talking about unidirectional LSP or bidirectional LSP?
4) Section 7.1.2.1 says:
	Since a MEG pertains to a single MPLS-TP Tunnel, IP compatible MEG_IDs for=
 MPLS-TP Tunnels are simply the corresponding Tunnel_IDs

Assuming the Tunnel_ID is a unidirectional ID, then this statement implies =
that for the reverse direction a different MEG_ID is required. Is that the =
intent? If so why?

5) Why are drafts part of the normative references?

6) Will section 8 (open issues) be removed before publishing? This section =
implies that the MEP and MIP definition is not yet aligned with framework?

Regards,
Shahram



-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa=
 Andersson
Sent: Thursday, March 11, 2010 3:33 PM
To: mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ietf.org
Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01

All,

this is to start an MPLS working group last call on
draft-ietf-mpls-tp-identifiers-01

There is a discussion on the OAM model for MS-PWs where we haven't been
able to come to conclusion. Once we reach agreement the document will
be updated. Comments in this area are welcome during the working group
last call.


Please send your comments to the mpls-tp@ietf.org mailing list.

The working group last ends eob April 2nd.

/Loa

--

Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///
   phone:  +46 10 717 52 13
           +46 767 72 92 13

   email:  loa.andersson@ericsson.com
           loa@pi.nu




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


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


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

From hhelvoort@chello.nl  Wed Mar 24 10:14:27 2010
Return-Path: <hhelvoort@chello.nl>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9B113A6BCF; Wed, 24 Mar 2010 10:14:27 -0700 (PDT)
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=1.283,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OO6+ioU8F7vh; Wed, 24 Mar 2010 10:14:27 -0700 (PDT)
Received: from viefep15-int.chello.at (viefep15-int.chello.at [62.179.121.35]) by core3.amsl.com (Postfix) with ESMTP id 0A9643A69B0; Wed, 24 Mar 2010 10:14:15 -0700 (PDT)
Received: from edge01.upcmail.net ([192.168.13.236]) by viefep15-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100324171434.VRHP22993.viefep15-int.chello.at@edge01.upcmail.net>; Wed, 24 Mar 2010 18:14:34 +0100
Received: from dhcp-wireless-open-abg-28-148.meeting.ietf.org ([130.129.28.148]) by edge01.upcmail.net with edge id x5EW1d03G3Bk8vW015EYax; Wed, 24 Mar 2010 18:14:34 +0100
X-SourceIP: 130.129.28.148
Message-ID: <4BAA4873.3020706@chello.nl>
Date: Wed, 24 Mar 2010 18:14:27 +0100
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Cecil Byles <Cecil.Byles@interoute.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com><8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com><A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com>	<8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com> <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>
In-Reply-To: <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Cloudmark-Analysis: v=1.1 cv=O+FWVpunvrlG1gSnSO6WiIQ7o0MJ4laHqrEcUJ8XjIg= c=1 sm=0 a=-8P26MX4vjUA:10 a=N659UExz7-8A:10 a=48vgC7mUAAAA:8 a=sJFSPIpMiw1UhE6mH2EA:9 a=Zn4JgWg84MMT2vQau4RiCr1H52oA:4 a=pILNOxqGKmIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term "PSC"	indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 17:14:27 -0000

Hello Cecil,

You wrote:

> Can I therefore also asked how PSC “Protection State Coordination” in 
> the MPLS-TP parlance align with ITU-T 808.1 recommendation that "defines 
> the generic functional models, characteristics and processes associated 
> with various linear protection schemes for connection-oriented layer 
> networks; e.g., Optical Transport Networks (OTN), Synchronous Digital 
> Hierarchy (SDH) networks and Asynchronous Transfer Mode (ATM) networks" 
> and the sections covering  Terms and Definitions as well as 
> Abbreviations.  IMO all transport engineers and the general telecom 
> community understand that 1+1 or 1:1 are either SNCP or APS. Hence why 
> introduce a new TLA (three letter abbreviation) cover the same function 
> and feature for MPLS-TP.  I can only agree that this will only cause 
> confusion.

I agree with you.

In addition to that:
The ITU-T experts that reviewed the survivability draft had the same 
concerns, and expressed that in their reply liaison for the review of
this draft: https://datatracker.ietf.org/liaison/618/ that was
sent in november last year.
This concern has not been addressed yet.

Regards, Huub.


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

From stbryant@cisco.com  Wed Mar 24 10:23:43 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 954E53A6BB4; Wed, 24 Mar 2010 10:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.469
X-Spam-Level: 
X-Spam-Status: No, score=-9.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 1n5PohlMrzCu; Wed, 24 Mar 2010 10:23:42 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 3A4FB3A6D3E; Wed, 24 Mar 2010 10:21:44 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEABfnqUtAZnwM/2dsb2JhbACbG3OnC4FCCgGXOIR+BA
X-IronPort-AV: E=Sophos;i="4.51,301,1267401600"; d="scan'208";a="95841184"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 24 Mar 2010 17:22:04 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o2OHM3Fe005187; Wed, 24 Mar 2010 17:22:03 GMT
Received: from dhcp-wireless-open-abg-25-131.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o2OHM1X00396; Wed, 24 Mar 2010 17:22:01 GMT
Message-ID: <4BAA4A38.5030107@cisco.com>
Date: Wed, 24 Mar 2010 17:22:00 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: hhelvoort@chello.nl
References: <20100305191502.17B8F28C0F0@core3.amsl.com>	<4B9290D1.2080902@pi.nu>	<787be2781003061226t58ad6659x52a097d3b828d0c2@mail.gmail.com>	<4BA5783A.9070307@cisco.com> <4BA657EB.9060709@chello.nl>
In-Reply-To: <4BA657EB.9060709@chello.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, CCAMP <ccamp@ietf.org>, pwe3@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls-tp] [mpls] WG Last Call on	draft-ietf-mpls-tp-ach-tlv-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 17:23:43 -0000

Huub van Helvoort wrote:
> Ho Stewart,
>
> You suggested:
>
>> We could allocate a small number - say 4 or 8 for experimental purposes.
>>
>> What do others think?
>
> I agree, and for consistency use the same number (and numbers)
> as allocated for experimental Channel types in RFC5586.
>
> Regards, Huub.
I see no reason why they need to be the particular numbers used for ACH types, and if you look at the mail that I posted earlier today, you will see that there is an alternative method of doing padding that would conflict with that alignment.

- Stewart


From curtis@occnc.com  Wed Mar 24 11:01:26 2010
Return-Path: <curtis@occnc.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB7463A6993 for <ccamp@core3.amsl.com>; Wed, 24 Mar 2010 11:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.038
X-Spam-Level: *
X-Spam-Status: No, score=1.038 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qASwWkJJqXB4 for <ccamp@core3.amsl.com>; Wed, 24 Mar 2010 11:01:25 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id B55513A6D6E for <ccamp@ietf.org>; Wed, 24 Mar 2010 11:01:16 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o2OI1YKg033705; Wed, 24 Mar 2010 14:01:34 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201003241801.o2OI1YKg033705@harbor.orleans.occnc.com>
To: Attila Takacs <Attila.Takacs@ericsson.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Tue, 23 Mar 2010 18:29:52 BST." <79F41BA1E9BF3C489375521EF8DDE23C12B1A66700@ESESSCMS0355.eemea.ericsson.se>
Date: Wed, 24 Mar 2010 14:01:34 -0400
Sender: curtis@occnc.com
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [CCAMP] draft-ietf-ccamp-oam-configuration-fwk-03
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 18:01:26 -0000

In message <79F41BA1E9BF3C489375521EF8DDE23C12B1A66700@ESESSCMS0355.eemea.ericsson.se>
Attila Takacs writes:
>  
> Hi Curtis, 
>  
> Thank you for the comments!
>  
> > 
> > I have a few comments on draft-ietf-ccamp-oam-configuration-fwk-03
> > 
> > Most of my comments are general.
> > 
> >   1. The method suggested to change OAM parameters should be
> >      non-disruptive, and if possible including no loss of protection
> >      status.  The proposed mechanism seems to temporarily break the
> >      responsiveness of CC/CV during the transition period if a minor
> >      OAM parameter is changed.  Perhaps identifying OAM packets such
> >      as CC/CV according to an OAM configuration identifier would allow
> >      for the transition in a way that is similar to the transition of
> >      crypto keys where for an interim period two are recognized before
> >      the old is withdrawn.  For example, CC/CV at one rate with proper
> >      identification may allow working path to stay up.  CC/CV with a
> >      second rate make take over at any time, also identified and
> >      therefore at a known rate.  If either are being received the
> >      working path is assumed to be working.  The older of the OAM
> >      parameters can then be withdrawn leaving only the new parameters
> >      in place.  Management plane changes in particular take an
> >      eternity to perform compared to the restoration time
> >      requirements.
> >
>  
> To allow two parameters to be recognised during reconfiguration is, I
> think, OAM technology and implementation dependant. If this is indeed
> supported by the underlying OAM technology then, re-signaling with the
> changed parameters without clearing the OAM Alarms Enabled flag would
> actually result in the desired operation you described above.


If the underlying OAM is related to PW or LPS, then the capability is
what we define it to be.  Otherwise it is what IETF or ITU has defined
it to be for Etherent, SONET/SDH, OTN, etc.


> >      This is either a missed OAM requirement, or not important (not
> >      missed, not a requirement), or accommodated by an alternate
> >      mechanism.
>  
> If this is a requirement, it must be addressed by the specific OAM technology and not in this document that deals with GMPLS CP aspects only.


That is a good point.  My comments are misdirected.


> >      Another way to accomplish the same thing would be creating a new
> >      LSP on the same path using make-before-break semantics.  If this
> >      is preferable, maybe it should be mentioned here.  OTOH -
> >      resignaling the LSP and in doing so coming up with a different
> >      LSP-id and set of labels is a lot of overhead for a parameter
> >      change.
> > 
> >      Another question - should a parameter change which is rejected
> >      take down the LSP?  As currently specified it does.
> >
>  
> My intention was to say the following...I will need to elaborate on this in the text further, I admit.
>  
> Let us take as example the CC rate, now it is running at say 100ms. There are two cases:
>  
> 1) the initiator wants to change to a higher rate say 3.3ms.
> In this case the remote-end may chose not to accept the value and suggest 10ms instead. What should not be allowed trough is to suggest a lower rate than the 100ms that is used currently. So say suggesting 1s should result in an error and tear down.


A tear down is an unacceptable outcome.  That is why a suggested
make-before-break as a possibility.


> 2) the initiator wants to reduce the reate say to 1 sec. In this case I assume that the remote-end will have no problem to accept the new rate.
>  
> Do you agree with this?


That is true.  This could be done without make-before-break but the
more general case would be make-before-break.  Either that or the idea
of two rates, where accepting one of the two is adequate to keep the
LSP from being rejected.

Having a window where protection is disabled is undesirable but the WG
may end up agreeing that this is acceptable.  If so, it should be
documented.


> >   2. Note: There does not seem to be any possibility of OAM leaking
> >      outside.  OAM is always received, evn if received and discarded
> >      and never forwarded.  Perhaps the paragraph describing this could
> >      be deleted or edited to reflect this.
> > 
>  
> Hmm, I would say that this may be technology specific too. In any case, calling out the setup of the sink function should not be an issue. In the case the "sink" function in implicit for a technology there is no harm calling that explicitly out.


Please explain how signaling in PATH and RESV messages could be
related to anything other than PW or LSP.  Or are you considering the
GELs case?


> >   3. A requirement and framework document does not generally define
> >      the protocol mechanisms at the same time.  Either this document
> >      has to be edited to not claim to be a requirement and framework
> >      document, or the mechanism needs to be split off into another
> >      document.  If the WG goes with the former, then this document
> >      should be held to a higher standard as required by the IETF
> >      routing area (working code, interoperability).  The reason for
> >      this is a lot of problems are found in taking the step to working
> >      and interoperable code.  As it exists this is a base protocol
> >      specification, not a equirement and framework document.
>  
> Point taken, will discuss with the chairs.

Thanks.

> >   4. If a MIP is only desired at select points along the LSP, it would
> >      be better to extend the ERO.  If so, then this discussion of
> >      attribute flags bits goes away.  The ingress can elect to not use
> >      an LSP if the egress and appropriate set of midpoint LSR have
> >      filled in the RRO indicating that the OAM functionality is
> >      enabled.  The ERO would also have to be modified by MIP to
> >      indicate to the egress that they have been set up.
> > 
> >      The ERO/RRO might also be a better place to put this simple
> >      because SESSION_ATTRIBUTE bits and ADMIN_STATUS bits are in short
> >      supply and have limited potential semantics.
> > 
>  
> Discussion is going in the context of:
> http://tools.ietf.org/html/draft-kern-ccamp-rsvpte-hop-attributes-00
> http://tools.ietf.org/html/draft-kern-ccamp-intermediate-node-config-00


Thanks.  These referneces help.


> >   5. A "reject object" containing a reason and the TLV being rejected
> >      would be preferable to a PathErr.  This is particularly true if
> >      resignaling a parameter.
>  
> Ok, will consider.

Thanks.

> >   6. It might be better to put "lock" and "loopback" functionality in
> >      the control plane for PW and LSP or management plane rather than
> >      putting it in the data plane in the OAM packets.  We just had a
> >      brief discussion on setting loopback in the data plane using TTL
> >      to identify the node and having the TTL and data path change due
> >      to a segment protection status change (FRR being an example).
> > 
>  
> Admin Status bits in the context of recovery signalling are defined in other documents for Lockout, Testing and Administratively Down that can be used here as well. 


I'm missing something.  Which I-D is this?

draft-kern-ccamp-intermediate-node-config-00 has:

  2.2.  OAM Configuration of Non-Intrusive Monitoring Entities

but lock and loopback are not non-intrusive and this section is not
very specific.  Good work though.


> > Minor:
> > 
> > @@ -760,6 +810,10 @@
> >               2                   Performance Monitoring/Loss 
> > (PM/Loss)
> >               3                   Performance 
> > Monitoring/Delay (PM/Delay)
> > 
> > +* The length is not specified.  As drawn this is a arbitrary length
> > +  integer containing one of the values 0..3.  A bitmap would be
> > +  preferable and that may be what was intended.
> > 
>  
> Intension is to have a bitmap. Will clarify.
>  
> > Last is a nit - there is a spelling error.
> > 
> > -   In general, two types of Maintenance Poits (MPs) can be
> > +   In general, two types of Maintenance Points (MPs) can be
> > 
> > Curtis
>  
> Thanks,
> Attila
>  
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
> > 
>  

From giomarti@cisco.com  Wed Mar 24 18:37:44 2010
Return-Path: <giomarti@cisco.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 92C053A6B89 for <ccamp@core3.amsl.com>; Wed, 24 Mar 2010 18:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.868
X-Spam-Level: 
X-Spam-Status: No, score=-6.868 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Qixd4C045vc for <ccamp@core3.amsl.com>; Wed, 24 Mar 2010 18:37:36 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id D96BA3A6B2E for <ccamp@ietf.org>; Wed, 24 Mar 2010 18:37:35 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am8FABpbqktAZnwN/2dsb2JhbACBRJlXc6ZxixEIjXeCZAiCEgQ
X-IronPort-AV: E=Sophos;i="4.51,304,1267401600"; d="scan'208,217";a="95845542"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 25 Mar 2010 01:37:55 +0000
Received: from [10.61.84.20] (ams3-vpn-dhcp5141.cisco.com [10.61.84.20]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o2P1bsgD025056; Thu, 25 Mar 2010 01:37:54 GMT
Message-ID: <4BAABECC.30801@cisco.com>
Date: Thu, 25 Mar 2010 02:39:24 +0100
From: Giovanni Martinelli <giomarti@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100305 Lightning/1.0b2pre Thunderbird/3.0.3
MIME-Version: 1.0
To: Young Lee <ylee@huawei.com>
References: <4B87DE23.8080004@cisco.com>	<002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com> <4BA78A3F.5010207@cisco.com>
In-Reply-To: <4BA78A3F.5010207@cisco.com>
Content-Type: multipart/alternative; boundary="------------060801040701020409000506"
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] Comments on draft-ietf-ccamp-rwa-wson-framework-05
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 01:37:44 -0000

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

Hi Young,


On 03/22/2010 04:18 PM, Giovanni Martinelli wrote:
> Hi,
>
> On 03/10/2010 05:35 PM, Young Lee wrote:
>>
>> Hi Giovanni,
>>
>> Please see in-line for the comments.
>>
>> Regards,
>>
>> Greg & Young
>>
>> ------------------------------------------------------------------------
>>
>> *From:* ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] *On 
>> Behalf Of *Giovanni Martinelli
>> *Sent:* Friday, February 26, 2010 8:44 AM
>> *To:* ccamp@ietf.org
>> *Subject:* [CCAMP] Comments on draft-ietf-ccamp-rwa-wson-framework-05
>>
>> Hi Greg/Young/Authors,
>>
>> regarding the rwa framework I appreciate last updates, they goes in 
>> the right direction. I still have few comment on the draft:
>>
>>
>> 1) Sec. 3.5.1 Regenerators
>> According to ITU inputs (Q6 mtg last october) the regeneration 
>> classification was:
>> 1R: amplifier
>> 2R: does not exist
>> 3R: the regenerator (indeed).
>>
>> I can understand the framework list all the three types (for sake of 
>> completess) but at the end we can consider only 3R as regeneration. 
>> This should also simplify the related encoding: we need only to know 
>> if regen is available and not the specific type (1, 2 or 3).
>>
>> Young>>  We are referencing these terminology from ITU-T G.872 (Annex A) so these are legitimate regeneration classification.
>> 1R regenerators may work over a limited range of wavelength/frequencies so this needs to be known to the control plane path computation process.
>> 2R regenerators are usually dependent on modulation format and are limited to a range of bit rates, so this needs to be known as well.
>
> I'm fine with the reference I was wandering about defining details 
> which are not so useful: if 1R are equivalent to amplifier how does 
> this impact with RWA (impairment free ;-)) case?
>
> In term of info model I guess will be much more simpler to consider 
> regens (so only 3R) without diving into 1-2-3R ... on this not sure 
> there was a communication coming back from Q6 after last october 
> meeting but we could probably ask better on this.
>
>

finally I got it

https://datatracker.ietf.org/liaison/602/

at page 2 they explain about different types of regenerators

cheers
G







>>
>> 2) Sec. 4.1.1
>> PCE is one of the architectural options but reading the first bullet 
>> looks like there is a need of a *stateful* PCE to support RWA.
>> If that the case probably worth a reference to RFC4655 section 6.8.
>>
>> Young>> We didn't assume that we need a stateful PCE to support RWA. 
>> We assume that the up-to-date RWA usage information will be updated 
>> by OSPF routing enhancement.
>>
>>
> ok
>
>> 3) Sec. 4.1.3
>> The statement "this approach may generate higher blocking 
>> probability.." is there any reference that demonstrate this?
>>
>> Young>> Please see the following references:
>>
>> [1]
>>
>> 	
>>
>> K. Lu, G. Xiao, and I. Chlamtac, "Analysis of blocking probability 
>> for distributed lightpath establishment in WDM optical networks," 
>> /IEEE/ACM Trans. Netw./, vol. 13, 2005, pp. 187-197.
>>
>> [2]
>>
>> 	
>>
>> A. Giorgetti, N. Sambo, L. Valcarenghi, and P. Castoldi, "Reservation 
>> Collision Avoidance in GMPLS Wavelength-routed Optical Networks," 
>> /Photonics in Switching, 2006. PS '06. International Conference on/, 
>> 2006, pp. 1-3.
>>
>> [3]
>>
>> 	
>>
>> A. Giorgetti, F. Paolucci, F. Cugini, L. Valcarenghi, P. Castoldi, 
>> and G. Bernstein, "Routing and Wavelength Assignment in PCE-based 
>> Wavelength Switched Optical Networks," /Optical Communication, 2008. 
>> ECOC 2008. 34th European Conference on/, 2008, pp. 1-2.
>>
>>
>
> well only the first try to build an analytical model and even blocking 
> probability depends on several boundary conditions (network loads, 
> burstiness etc.)
>
> Not sure if this framework is the right place to make those kind of 
> considerations...
>
>
>> 4) Section 4.3
>> Is not really clear to me the scope of this section, why do we need 
>> to state anything about temporal characteristics?
>>
>> Young>> The idea was to explain that different timeliness 
>> requirements for lightpath setup influence or restrict the amount of 
>> "optimization" that can be done with the computation of a path.
>>
>>
>> Another comment that I did some time ago was about defining 
>> dynamic/pseudo-static/static with no reference: the draft just 
>> mention short or moderately-long and long duration.
>>
>> Young>> Do you have any suggestion as to how to change this section?
>>
>
> (Let me put the above two comments together)
> So if I understand correctly, a potential network re-optimization will 
> take into account only what you call static/pseduo-static LSPs, right?
>
> Probably, thinking in term of framework I would add just some 
> consideration about adding some lightpath liveness and how this  
> information could be used. This could be done without defining 
> different level of liveness as it is now
>
>
>
>> 5) Sec. 5.5.4
>> I understand you need to clarify some typical optical terminology 
>> like: transparent / translucent etc. but how about having all 
>> terminology grouped in section 3?
>> And basically this WSON framework support either transparent (in 
>> different flavors) and translucent.
>>
>> Young>> Good idea! We will update that. Do you have some suggested 
>> definition?
>>
>
> Probably a section 3.x  that sounds like "Types of WSON networks" 
> where the terms are defined: transparent/transparent-island, mostly 
> transparent, opaque etc.
>
> And for sure a statement that they are in  the scope of this framework
>
>
> Cheers
> G
>
>
>>
>>
>> Cheers
>> G
>>
>>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>    

--------------060801040701020409000506
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<font face="Helvetica, Arial, sans-serif">Hi Young,<br>
<br>
</font><br>
On 03/22/2010 04:18 PM, Giovanni Martinelli wrote:
<blockquote cite="mid:4BA78A3F.5010207@cisco.com" type="cite">
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
  <title></title>
  <font face="Helvetica, Arial, sans-serif">Hi,<br>
  </font><br>
On 03/10/2010 05:35 PM, Young Lee wrote:
  <blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite">
    <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
    <meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
    <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo1;
	font-size:16.0pt;
	font-family:Arial;
	color:black;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
tt
	{font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;
	color:black;}
p.Style1, li.Style1, div.Style1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@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:1792360828;
	mso-list-template-ids:1288485006;}
@list l0:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	font-family:"Times New Roman";}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	font-family:"Times New Roman";}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	font-family:"Times New Roman";}
@list l0:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
  </style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1027" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
    <div class="Section1">
    <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;">Hi Giovanni,<o:p></o:p></span></font></p>
    <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>&nbsp;</o:p></span></font></p>
    <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;">Please see
in-line for the comments. &nbsp;<o:p></o:p></span></font></p>
    <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>&nbsp;</o:p></span></font></p>
    <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;">Regards,<o:p></o:p></span></font></p>
    <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;">Greg &amp;
Young<o:p></o:p></span></font></p>
    <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>&nbsp;</o:p></span></font></p>
    <div class="MsoNormal" style="text-align: center;" align="center"><font
 size="3" color="black" face="Times New Roman"><span
 style="font-size: 12pt; color: windowtext;">
    <hr tabindex="-1" size="2" width="100%" align="center"></span></font></div>
    <p class="MsoNormal"><b><font size="2" color="black" face="Tahoma"><span
 style="font-size: 10pt; font-family: Tahoma; color: windowtext; font-weight: bold;">From:</span></font></b><font
 size="2" color="black" face="Tahoma"><span
 style="font-size: 10pt; font-family: Tahoma; color: windowtext;">
    <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
 href="mailto:ccamp-bounces@ietf.org">ccamp-bounces@ietf.org</a> [<a
 moz-do-not-send="true" class="moz-txt-link-freetext"
 href="mailto:ccamp-bounces@ietf.org">mailto:ccamp-bounces@ietf.org</a>]
    <b><span style="font-weight: bold;">On Behalf Of </span></b>Giovanni
Martinelli<br>
    <b><span style="font-weight: bold;">Sent:</span></b> Friday,
February
26, 2010
8:44 AM<br>
    <b><span style="font-weight: bold;">To:</span></b> <a
 moz-do-not-send="true" class="moz-txt-link-abbreviated"
 href="mailto:ccamp@ietf.org">ccamp@ietf.org</a><br>
    <b><span style="font-weight: bold;">Subject:</span></b> [CCAMP]
Comments on
draft-ietf-ccamp-rwa-wson-framework-05</span></font><font color="black"><span
 style="color: windowtext;"><o:p></o:p></span></font></p>
    <p class="MsoNormal"><font size="3" color="black"
 face="Times New Roman"><span style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
    <p class="MsoNormal"><font size="3" color="black"
 face="Times New Roman"><span style="font-size: 12pt;"><!--[if gte vml 1]><v:shapetype id="_x0000_t74" 
 coordsize="21600,21600" o:spt="74" path="m10860,2187c10451,1746,9529,1018,9015,730,7865,152,6685,,5415,,4175,152,2995,575,1967,1305,1150,2187,575,3222,242,4220,,5410,242,6560,575,7597l10860,21600,20995,7597v485,-1037,605,-2187,485,-3377c21115,3222,20420,2187,19632,1305,18575,575,17425,152,16275,,15005,,13735,152,12705,730v-529,288,-1451,1016,-1845,1457xe">
 <v:stroke joinstyle="miter" />
 <v:path gradientshapeok="t" o:connecttype="custom" o:connectlocs="10860,2187;2928,10800;10860,21600;18672,10800" 
  o:connectangles="270,180,90,0" textboxrect="5037,2277,16557,13677" />
</v:shapetype><v:shape id="DtsShapeName" o:spid="_x0000_s1026" type="#_x0000_t74" 
 alt="47E529CG097D5920@5BB2C5D2BED5405097@8h8=@@dM62793!!!!!!BIHO@]M62793!!!11111111110BCGBD3519Onsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!80L8Z8;D8_M62793!!!!!!BIHO@]m62793!!!11111111110BCGBD3519110BCGBD3519!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!86G;&lt;8=?8`M62793!!!!!!BIHO@]M62793!!!11111111110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8;?;A8;?@@M62793!!!!!!BIHO@]m62793!!!1@6B1B5B110B322C71D4110B322C71D4!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!1" 
 style='position:absolute;margin-left:0;margin-top:0;width:.05pt;height:.05pt;
 z-index:1;visibility:hidden'>
 <w:anchorlock/>
</v:shape><![endif]--></span></font><tt><font
 size="2" face="Courier New"><span style="font-size: 10pt;">Hi
Greg/Young/Authors,</span></font></tt><font size="2" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
    <br>
    <tt><font face="Courier New">regarding the rwa framework I
appreciate
last
updates, they goes in the right direction. I still have few comment on
the
draft:</font></tt><br>
    <br>
    <br>
    <tt><font face="Courier New">1) Sec. 3.5.1 Regenerators </font></tt><br>
    <tt><font face="Courier New">According to ITU inputs (Q6 mtg last
october) the
regeneration classification was:</font></tt><br>
    <tt><font face="Courier New">1R: amplifier</font></tt><br>
    <tt><font face="Courier New">2R: does not exist</font></tt><br>
    <tt><font face="Courier New">3R: the regenerator (indeed).</font></tt><br>
    <br>
    <tt><font face="Courier New">I can understand the framework list
all
the three
types (for sake of completess) but at the end we can consider only 3R
as
regeneration. This should also simplify the related encoding: we need
only to
know if regen is available and not the specific type (1, 2 or 3).</font></tt><br>
    <br>
    </span></font><font size="2" color="navy" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: navy;"><o:p></o:p></span></font></p>
    <pre style="page-break-before: always;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt; We are referencing these terminology from ITU-T G.872 (Annex A) so these are legitimate regeneration classification. <o:p></o:p></span></font></pre>
    <pre style="page-break-before: always;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">1R regenerators may work over a limited range of wavelength/frequencies so this needs to be known to the control plane path computation process.<o:p></o:p></span></font></pre>
    <pre style="page-break-before: always;"><font size="2"
 color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">2R regenerators are usually dependent on modulation format and are limited to a range of bit rates, so this needs to be known as well. </span></font><font
 color="#3366ff"><span style="color: rgb(51, 102, 255);"><o:p></o:p><o:p></o:p></span></font></pre>
    </div>
    </o:smarttagtype></blockquote>
  <br>
I'm fine with the reference I was wandering about defining details
which are not so useful: if 1R are equivalent to amplifier how does
this impact with RWA (impairment free ;-)) case?<br>
  <br>
In term of info model I guess will be much more simpler to consider
regens (so only 3R) without diving into 1-2-3R ... on this not sure
there was a communication coming back from Q6 after last october
meeting but we could probably ask better on this. <br>
  <br>
  <br>
</blockquote>
<br>
finally I got it<br>
<br>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/liaison/602/">https://datatracker.ietf.org/liaison/602/</a><br>
<br>
at page 2 they explain about different types of regenerators<br>
<br>
cheers<br>
G<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote cite="mid:4BA78A3F.5010207@cisco.com" type="cite">
  <blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
    <div class="Section1">
    <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p><o:p>&nbsp;</o:p></o:p></span></font></p>
    <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
    <tt><font face="Courier New">2) Sec. 4.1.1</font></tt><br>
    <tt><font face="Courier New">PCE is one of the architectural
options
but
reading the first bullet looks like there is a need of a *stateful* PCE
to support
RWA. </font></tt><br>
    <tt><font face="Courier New">If that the case probably worth a
reference to
RFC4655 section 6.8.</font></tt><br>
    <br>
    </span></font><font size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;</span></font><font
 size="2" color="#3366ff" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(51, 102, 255);">
    </span></font><font size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">We
didn&#8217;t
assume that we need a stateful PCE to support
RWA. We assume that the up-to-date RWA usage information will be
updated by
OSPF routing enhancement. <o:p></o:p></span></font><font
 color="#3366ff"><span style="color: rgb(51, 102, 255);"><o:p></o:p></span></font></p>
    <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
    </span></font></p>
    </div>
    </o:smarttagtype></blockquote>
ok<br>
  <br>
  <blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
    <div class="Section1">
    <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><tt><font
 face="Courier New">3) Sec. 4.1.3</font></tt><br>
    <tt><font face="Courier New">The statement "this approach may
generate
higher blocking probability.." is there any reference that demonstrate
this? </font></tt><br>
    <br>
    </span></font><font size="2" color="navy" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: navy;"><o:p></o:p></span></font></p>
    <p class="MsoNormal" style=""><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;
Please
see the following references:<o:p></o:p></span></font></p>
    <table class="MsoNormalTable" style="border-collapse: collapse;"
 cellpadding="0" cellspacing="0" border="0">
      <tbody>
        <tr>
          <td style="padding: 0.75pt;" valign="top">
          <p class="MsoNormal" style="line-height: 13.2pt;"><font
 size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">[1]<o:p></o:p></span></font></p>
          </td>
          <td style="padding: 0.75pt 0.75pt 0.75pt 4pt;" valign="top">
          <p class="MsoNormal" style="line-height: 13.2pt;"><font
 size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">K.

Lu,
G. Xiao, and I. Chlamtac, &#8220;Analysis of blocking probability for
distributed lightpath establishment in WDM optical networks,&#8221; <i><span
 style="font-style: italic;">IEEE/ACM Trans. Netw.</span></i>, vol. 13,
2005, pp. 187-197. <span class="z3988"><span
 title="url_ver=Z39.88-2004&amp;ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.atitle=Analysis%20of%20blocking%20probability%20for%20distributed%20lightpath%20establishment%20in%20WDM%20optical%20networks&amp;rft.jtitle=IEEE%2FACM%20Trans.%20Netw.&amp;rft.volume=13&amp;rft.issue=1&amp;rft.aufirst=Kejie&amp;rft.aulast=Lu&amp;rft.au=Kejie%20Lu&amp;rft.au=Gaoxi%20Xiao&amp;rft.au=Imrich%20Chlamtac&amp;rft.date=2005&amp;rft.pages=187-197">&nbsp;</span></span><o:p></o:p></span></font></p>
          </td>
        </tr>
        <tr>
          <td style="padding: 0.75pt;" valign="top">
          <p class="MsoNormal" style="line-height: 13.2pt;"><font
 size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">[2]<o:p></o:p></span></font></p>
          </td>
          <td style="padding: 0.75pt 0.75pt 0.75pt 4pt;" valign="top">
          <p class="MsoNormal" style="line-height: 13.2pt;"><font
 size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">A.

Giorgetti,
          <st1:place w:st="on">N. Sambo</st1:place>, L. Valcarenghi,
and P. Castoldi, &#8220;Reservation Collision Avoidance in GMPLS
Wavelength-routed Optical Networks,&#8221; <i><span
 style="font-style: italic;">Photonics in Switching, 2006. PS '06.
International Conference on</span></i>, 2006, pp. 1-3.<o:p></o:p></span></font></p>
          </td>
        </tr>
        <tr>
          <td style="padding: 0.75pt;" valign="top">
          <p class="MsoNormal" style="line-height: 13.2pt;"><font
 size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">[3]<o:p></o:p></span></font></p>
          </td>
          <td style="padding: 0.75pt 0.75pt 0.75pt 4pt;" valign="top">
          <p class="MsoNormal" style="line-height: 13.2pt;"><font
 size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">A.

Giorgetti,
F. Paolucci, F. Cugini, L. Valcarenghi, P. Castoldi, and G.
Bernstein, &#8220;Routing and Wavelength Assignment in PCE-based Wavelength
Switched Optical Networks,&#8221; <i><span style="font-style: italic;">Optical

Communication,
2008. ECOC 2008. 34th European Conference on</span></i>,
2008, pp. 1-2.<o:p></o:p></span></font></p>
          </td>
        </tr>
      </tbody>
    </table>
    <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
    </span></font></p>
    </div>
    </o:smarttagtype></blockquote>
  <br>
well only the first try to build an analytical model and even blocking
probability depends on several boundary conditions (network loads,
burstiness etc.)<br>
  <br>
Not sure if this framework is the right place to make those kind of
considerations... <br>
&nbsp;<br>
  <br>
  <blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
    <div class="Section1">
    <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><tt><font
 face="Courier New">4) Section 4.3</font></tt><br>
    <tt><font face="Courier New">Is not really clear to me the scope of
this
section, why do we need to state anything about temporal
characteristics?</font></tt></span></font><tt><font size="2"
 color="navy" face="Courier New"><span
 style="font-size: 10pt; color: navy;"><o:p></o:p></span></font></tt></p>
    <p class="MsoNormal" style=""><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;
The
idea was to explain that different
timeliness requirements for lightpath setup influence or restrict the
amount of
"optimization" that can be done with the computation of a path.</span></font><font
 size="2" color="navy" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p></o:p></span></font></p>
    <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
    <tt><font face="Courier New">Another comment that I did some time
ago
was about
defining dynamic/pseudo-static/static with no reference: the draft just
mention
short or moderately-long and long duration.</font></tt><br>
    <br>
    </span></font><font size="2" color="#3366ff" face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;
Do
you have any
suggestion as to how to change this section? </span></font></p>
    </div>
    </o:smarttagtype></blockquote>
  <br>
(Let me put the above two comments together)<br>
So if I understand correctly, a potential network re-optimization will
take into account only what you call static/pseduo-static LSPs, right?<br>
  <br>
Probably, thinking in term of framework I would add just some
consideration about adding some lightpath liveness and how this&nbsp;
information could be used. This could be done without defining
different level of liveness as it is now <br>
  <br>
  <br>
  <br>
  <blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
    <div class="Section1">
    <p class="MsoNormal" style=""><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);"><o:p></o:p></span></font></p>
    <p class="MsoNormal" style=""><tt><font size="2" color="black"
 face="Courier New"><span style="font-size: 10pt;">5) Sec.
5.5.4</span></font></tt><font size="2" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
    <tt><font face="Courier New">I understand you need to clarify some
typical
optical terminology like: transparent / translucent etc. but how about
having
all terminology grouped in section 3? </font></tt><br>
    <tt><font face="Courier New">And basically this WSON framework
support either
transparent (in different flavors) and translucent.</font></tt><br>
    <br>
    </span></font><font size="2" color="navy" face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: navy;"><o:p></o:p></span></font></p>
    <p class="MsoNormal" style=""><font size="2" color="#3366ff"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: rgb(51, 102, 255);">Young&gt;&gt;
Good
idea! We will update that. <o:p></o:p>Do
you have some suggested definition? </span></font><font color="#3366ff"><span
 style="color: rgb(51, 102, 255);"><o:p></o:p></span></font></p>
    <p class="MsoNormal" style=""><font size="2" color="navy"
 face="Arial"><span
 style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>&nbsp;</o:p></span></font></p>
    </div>
    </o:smarttagtype></blockquote>
  <br>
Probably a section 3.x&nbsp; that sounds like "Types of WSON networks" where
the terms are defined: transparent/transparent-island, mostly
transparent, opaque etc.<br>
  <br>
And for sure a statement that they are in&nbsp; the scope of this framework<br>
  <br>
  <br>
Cheers<br>
G <br>
  <br>
  <br>
  <blockquote cite="mid:002b01cac06f$bd1b0d50$380c7c0a@china.huawei.com"
 type="cite"><o:smarttagtype
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
    <div class="Section1">
    <p class="MsoNormal" style=""><font size="2" color="black"
 face="Courier New"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><br>
    <br>
    <tt><font face="Courier New">Cheers</font></tt><br>
    <tt><font face="Courier New">G</font></tt><br>
    <br>
    <br>
    </span></font><o:p></o:p></p>
<!--EndFragment--></div>
    </o:smarttagtype></blockquote>
  <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
CCAMP mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CCAMP@ietf.org">CCAMP@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ccamp">https://www.ietf.org/mailman/listinfo/ccamp</a>
  </pre>
</blockquote>
</body>
</html>

--------------060801040701020409000506--

From curtis@occnc.com  Wed Mar 24 22:59:11 2010
Return-Path: <curtis@occnc.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4B733A6927; Wed, 24 Mar 2010 22:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.216
X-Spam-Level: 
X-Spam-Status: No, score=-0.216 tagged_above=-999 required=5 tests=[AWL=1.254,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KvovJ8IrSq6s; Wed, 24 Mar 2010 22:59:11 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id CF7373A67D9; Wed, 24 Mar 2010 22:59:10 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o2P5xTAd062305; Thu, 25 Mar 2010 01:59:29 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201003250559.o2P5xTAd062305@harbor.orleans.occnc.com>
To: Vivien Sterling <vivien.sterling@gmail.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 24 Mar 2010 16:20:35 +0800." <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> 
Date: Thu, 25 Mar 2010 01:59:29 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 05:59:12 -0000

In message <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>
Vivien Sterling writes:
>  
>  
> Dear Experts,
>  
> I'm surprised to find the term "PSC" used in this draft. I suppose the
> authors are talking about data plane not control plane, right? Isn't PSC in
> GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(
>  
> -- 
> Cheers,
> Vivien


I fully agree.  This is an IETF document within MPLS and the PSC
acronym conflicts with a prior MPLS acronym.  The prior usage should
take precedence.  This acronym really should be changed.

A change as simple as recovery service coordination (RSC) would avoid
the clash.  Or a substitute for the word coordination could be used.

Curtis

From curtis@occnc.com  Wed Mar 24 23:09:13 2010
Return-Path: <curtis@occnc.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 410883A6841; Wed, 24 Mar 2010 23:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.633
X-Spam-Level: 
X-Spam-Status: No, score=-1.633 tagged_above=-999 required=5 tests=[AWL=1.836,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khzh6szSFaC7; Wed, 24 Mar 2010 23:09:12 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 5143F3A6856; Wed, 24 Mar 2010 23:09:12 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o2P69T7l062460; Thu, 25 Mar 2010 02:09:29 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201003250609.o2P69T7l062460@harbor.orleans.occnc.com>
To: "Cecil Byles" <Cecil.Byles@interoute.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 24 Mar 2010 10:49:21 BST." <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> 
Date: Thu, 25 Mar 2010 02:09:29 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 06:09:13 -0000

In message <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>
"Cecil Byles" writes:
>  
>  
> Hi,
> Can I therefore also asked how PSC "Protection State Coordination" in
> the MPLS-TP parlance align with ITU-T 808.1 recommendation that "defines
> the generic functional models, characteristics and processes associated
> with various linear protection schemes for connection-oriented layer
> networks; e.g., Optical Transport Networks (OTN), Synchronous Digital
> Hierarchy (SDH) networks and Asynchronous Transfer Mode (ATM) networks"
> and the sections covering  Terms and Definitions as well as
> Abbreviations.  IMO all transport engineers and the general telecom
> community understand that 1+1 or 1:1 are either SNCP or APS. Hence why
> introduce a new TLA (three letter abbreviation) cover the same function
> and feature for MPLS-TP.  I can only agree that this will only cause
> confusion.
>  
> Cecil Byles


Though this is joint work, this is the IETF not the ITU.  We should
use ITU terms where appropriate but where there is a conflict such as
this we need to pick another term and another TLA.  If the ITU wants
to update 808.1 at some later date that is up to the ITU.  In the mean
time we can use another term and point out the mapping.

Curtis

From hhelvoort@chello.nl  Wed Mar 24 23:17:56 2010
Return-Path: <hhelvoort@chello.nl>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B5F73A6BF4; Wed, 24 Mar 2010 23:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=2.300, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YT4d9GwF-t+z; Wed, 24 Mar 2010 23:17:55 -0700 (PDT)
Received: from viefep18-int.chello.at (viefep18-int.chello.at [62.179.121.38]) by core3.amsl.com (Postfix) with ESMTP id 0E4ED3A6A89; Wed, 24 Mar 2010 23:17:52 -0700 (PDT)
Received: from edge01.upcmail.net ([192.168.13.236]) by viefep18-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100325061812.JBMW4252.viefep18-int.chello.at@edge01.upcmail.net>;  Thu, 25 Mar 2010 07:18:12 +0100
Received: from McAsterix.local ([76.79.230.2]) by edge01.upcmail.net with edge id xJJ81d03c03lDLC01JJAwB; Thu, 25 Mar 2010 07:18:12 +0100
X-SourceIP: 76.79.230.2
Message-ID: <4BAB0020.2040804@chello.nl>
Date: Thu, 25 Mar 2010 07:18:08 +0100
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: curtis@occnc.com
References: <201003250559.o2P5xTAd062305@harbor.orleans.occnc.com>
In-Reply-To: <201003250559.o2P5xTAd062305@harbor.orleans.occnc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Cloudmark-Analysis: v=1.1 cv=SLkC287PFWo6d7eSEiSBB9255DBOWQ3bwOwHXJiyZoo= c=1 sm=0 a=kHRpFeiL9R0A:10 a=8nJEP1OIZ-IA:10 a=pGLkceISAAAA:8 a=OLZQc8AWAAAA:8 a=_N0uTqiu9kuOFVvHKysA:9 a=7bzKPX64qUrYIpxfD7C3LzbfgUAA:4 a=wPNLvfGTeEIA:10 a=BRk5Yph32-Vx15z7:21 a=D7yODpqP0mUoMfq4:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] Term "PSC" in	draft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 06:17:56 -0000

Hi Curtis,

You wrote:

> In message <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>
> Vivien Sterling writes:
>>  
>> Dear Experts,
>>  
>> I'm surprised to find the term "PSC" used in this draft. I suppose the
>> authors are talking about data plane not control plane, right? Isn't PSC in
>> GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(
>>  
>> -- 
>> Cheers,
>> Vivien
> 
> I fully agree.  This is an IETF document within MPLS and the PSC
> acronym conflicts with a prior MPLS acronym.  The prior usage should
> take precedence.  This acronym really should be changed.
> 
> A change as simple as recovery service coordination (RSC) would avoid
> the clash.  Or a substitute for the word coordination could be used.

What is wrong with the acronym APS?
MPLS-TP will be used by transport network operators that are
familiar with the term APS and where it is used for.
Why confuse them with another TLW (three letter word)?

Regards, Huub.

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

From hhelvoort@chello.nl  Wed Mar 24 23:18:43 2010
Return-Path: <hhelvoort@chello.nl>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19B173A6A89; Wed, 24 Mar 2010 23:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=2.300, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-Tq8TI5D85T; Wed, 24 Mar 2010 23:18:43 -0700 (PDT)
Received: from viefep11-int.chello.at (viefep11-int.chello.at [62.179.121.31]) by core3.amsl.com (Postfix) with ESMTP id A856A3A6C67; Wed, 24 Mar 2010 23:18:16 -0700 (PDT)
Received: from edge01.upcmail.net ([192.168.13.236]) by viefep11-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100325061832.CEET4620.viefep11-int.chello.at@edge01.upcmail.net>;  Thu, 25 Mar 2010 07:18:32 +0100
Received: from McAsterix.local ([76.79.230.2]) by edge01.upcmail.net with edge id xJJV1d03h03lDLC01JJXgY; Thu, 25 Mar 2010 07:18:32 +0100
X-SourceIP: 76.79.230.2
Message-ID: <4BAB0035.6010208@chello.nl>
Date: Thu, 25 Mar 2010 07:18:29 +0100
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: curtis@occnc.com
References: <201003250559.o2P5xTAd062305@harbor.orleans.occnc.com>
In-Reply-To: <201003250559.o2P5xTAd062305@harbor.orleans.occnc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Cloudmark-Analysis: v=1.1 cv=ZDt3ILgE3VX9xkJc7+9REBIC4hFTL6V7NAq0V56QRNQ= c=1 sm=0 a=kHRpFeiL9R0A:10 a=8nJEP1OIZ-IA:10 a=pGLkceISAAAA:8 a=OLZQc8AWAAAA:8 a=_N0uTqiu9kuOFVvHKysA:9 a=7bzKPX64qUrYIpxfD7C3LzbfgUAA:4 a=wPNLvfGTeEIA:10 a=BRk5Yph32-Vx15z7:21 a=D7yODpqP0mUoMfq4:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] Term "PSC" in	draft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 06:18:43 -0000

Hi Curtis,

You wrote:

> In message <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>
> Vivien Sterling writes:
>>  
>> Dear Experts,
>>  
>> I'm surprised to find the term "PSC" used in this draft. I suppose the
>> authors are talking about data plane not control plane, right? Isn't PSC in
>> GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(
>>  
>> -- 
>> Cheers,
>> Vivien
> 
> I fully agree.  This is an IETF document within MPLS and the PSC
> acronym conflicts with a prior MPLS acronym.  The prior usage should
> take precedence.  This acronym really should be changed.
> 
> A change as simple as recovery service coordination (RSC) would avoid
> the clash.  Or a substitute for the word coordination could be used.

What is wrong with the acronym APS?
MPLS-TP will be used by transport network operators that are
familiar with the term APS and where it is used for.
Why confuse them with another TLW (three letter word)?

Regards, Huub.

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

From curtis@occnc.com  Thu Mar 25 00:18:07 2010
Return-Path: <curtis@occnc.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAB5D3A6C9B; Thu, 25 Mar 2010 00:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.168
X-Spam-Level: 
X-Spam-Status: No, score=-2.168 tagged_above=-999 required=5 tests=[AWL=1.301,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xhqf4HBFXqBu; Thu, 25 Mar 2010 00:18:06 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id CE8483A6C81; Thu, 25 Mar 2010 00:18:00 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o2P7IHi3066558; Thu, 25 Mar 2010 03:18:17 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201003250718.o2P7IHi3066558@harbor.orleans.occnc.com>
To: hhelvoort@chello.nl
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 25 Mar 2010 07:18:08 BST." <4BAB0020.2040804@chello.nl> 
Date: Thu, 25 Mar 2010 03:18:17 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 07:18:08 -0000

In message <4BAB0020.2040804@chello.nl>
Huub van Helvoort writes:
>  
> Hi Curtis,
>  
> You wrote:
>  
> > In message <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>
> > Vivien Sterling writes:
> >>  
> >> Dear Experts,
> >>  
> >> I'm surprised to find the term "PSC" used in this draft. I suppose the
> >> authors are talking about data plane not control plane, right? Isn't PSC in
> >> GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(
> >>  
> >> -- 
> >> Cheers,
> >> Vivien
> > 
> > I fully agree.  This is an IETF document within MPLS and the PSC
> > acronym conflicts with a prior MPLS acronym.  The prior usage should
> > take precedence.  This acronym really should be changed.
> > 
> > A change as simple as recovery service coordination (RSC) would avoid
> > the clash.  Or a substitute for the word coordination could be used.
>  
> What is wrong with the acronym APS?
> MPLS-TP will be used by transport network operators that are
> familiar with the term APS and where it is used for.
> Why confuse them with another TLW (three letter word)?
>  
> Regards, Huub.


APS is specific to SONET and serves a similar function but is
different.

Curtis

From alan.mcguire@bt.com  Thu Mar 25 00:22:23 2010
Return-Path: <alan.mcguire@bt.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D815B3A69A6; Thu, 25 Mar 2010 00:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.469
X-Spam-Level: 
X-Spam-Status: No, score=-4.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, 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 D6R3ldGwOuAw; Thu, 25 Mar 2010 00:22:22 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id 481AD3A68AF; Thu, 25 Mar 2010 00:21:40 -0700 (PDT)
Received: from E03MVB1-UKBR.domain1.systemhost.net ([193.113.197.110]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 25 Mar 2010 07:22:00 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Mar 2010 07:21:23 -0000
Message-ID: <346DD76A8C47FD4A87FA57FD1DEBCC9C06DCDE91@E03MVB1-UKBR.domain1.systemhost.net>
In-Reply-To: <201003250718.o2P7IHi3066558@harbor.orleans.occnc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [CCAMP] [mpls-tp] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrL62IjmfYKCjbQQ4qXofBETD5cxQAAEAhA
From: <alan.mcguire@bt.com>
To: <curtis@occnc.com>, <hhelvoort@chello.nl>
X-OriginalArrivalTime: 25 Mar 2010 07:22:00.0550 (UTC) FILETIME=[DC320860:01CACBEB]
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 07:22:24 -0000

APS is not specific to SONET. Try again=20

-----Original Message-----
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf
Of Curtis Villamizar
Sent: 25 March 2010 07:18
To: hhelvoort@chello.nl
Cc: mpls@ietf.org; CCAMP@ietf.org; mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] Term "PSC"
indraft-ietf-mpls-tp-linear-protection-01


In message <4BAB0020.2040804@chello.nl>
Huub van Helvoort writes:
> =20
> Hi Curtis,
> =20
> You wrote:
> =20
> > In message=20
> > <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>
> > Vivien Sterling writes:
> >> =20
> >> Dear Experts,
> >> =20
> >> I'm surprised to find the term "PSC" used in this draft. I suppose=20
> >> the authors are talking about data plane not control plane, right?=20
> >> Isn't PSC in GMPLS elaborated as "Packet Switch Capable" ? It's=20
> >> confusing :-(
> >> =20
> >> --
> >> Cheers,
> >> Vivien
> >=20
> > I fully agree.  This is an IETF document within MPLS and the PSC=20
> > acronym conflicts with a prior MPLS acronym.  The prior usage should

> > take precedence.  This acronym really should be changed.
> >=20
> > A change as simple as recovery service coordination (RSC) would=20
> > avoid the clash.  Or a substitute for the word coordination could be
used.
> =20
> What is wrong with the acronym APS?
> MPLS-TP will be used by transport network operators that are familiar=20
> with the term APS and where it is used for.
> Why confuse them with another TLW (three letter word)?
> =20
> Regards, Huub.


APS is specific to SONET and serves a similar function but is different.

Curtis
_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp

From adrian@olddog.co.uk  Thu Mar 25 01:00:36 2010
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CDFD3A69C8; Thu, 25 Mar 2010 01:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.168
X-Spam-Level: 
X-Spam-Status: No, score=-0.168 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0tMDb-Hqu2N; Thu, 25 Mar 2010 01:00:35 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id 6BCAC3A6973; Thu, 25 Mar 2010 01:00:35 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id o2P80b7r001544;  Thu, 25 Mar 2010 08:00:42 GMT
Received: from your029b8cecfe (dhcp-wireless-open-abg-25-211.meeting.ietf.org [130.129.25.211]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id o2P80YDe001514;  Thu, 25 Mar 2010 08:00:36 GMT
Message-ID: <239F5ECAA0574FB4A0003E9EC88F5D30@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>, "Vivien Sterling" <vivien.sterling@gmail.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com><8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com>
Date: Thu, 25 Mar 2010 07:55:42 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 08:00:36 -0000

For issues related to clashes of acronyms please see RFC 5513.


----- Original Message ----- 
From: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
To: "Vivien Sterling" <vivien.sterling@gmail.com>
Cc: <mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
Sent: Wednesday, March 24, 2010 8:30 AM
Subject: Re: [CCAMP] [mpls] Term "PSC" 
indraft-ietf-mpls-tp-linear-protection-01


Vivien and all,
AFAIK, PSC stands for "Protection State Coordination" in the MPLS-TP 
parlance (see MPLS-TP Survivability 
Framework<http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-survive-fwk/>)  
- a new fancy name for what has been known as "APS Protocol" in SONET/SDH.

As you've noted, it has a completely different meaning in GMPLS.

Since GMPLS is going to be used with MPLS-TP, double usage of this acronym 
looks highly problematic.

Regards,
     Sasha

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of 
Vivien Sterling
Sent: Wednesday, March 24, 2010 10:21 AM
To: CCAMP@ietf.org; mpls@ietf.org; mpls-tp@ietf.org
Subject: [mpls] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01

Dear Experts,

I'm surprised to find the term "PSC" used in this draft. I suppose the 
authors are talking about data plane not control plane, right? Isn't PSC in 
GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(

--
Cheers,
Vivien



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


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


From Adrian.Farrel@huawei.com  Thu Mar 25 01:32:49 2010
Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BF6B3A69DC; Thu, 25 Mar 2010 01:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.338
X-Spam-Level: 
X-Spam-Status: No, score=0.338 tagged_above=-999 required=5 tests=[AWL=1.207,  BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DxFKkAvJOXG; Thu, 25 Mar 2010 01:32:48 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 2F8523A6974; Thu, 25 Mar 2010 01:32:48 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZT002RXX39XT@usaga01-in.huawei.com>; Thu, 25 Mar 2010 01:33:09 -0700 (PDT)
Received: from your029b8cecfe (dhcp-wireless-open-abg-25-211.meeting.ietf.org [130.129.25.211]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KZT00J3YX38LT@usaga01-in.huawei.com>; Thu, 25 Mar 2010 01:33:09 -0700 (PDT)
Date: Thu, 25 Mar 2010 08:32:48 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: hhelvoort@chello.nl, Cecil Byles <Cecil.Byles@interoute.com>
Message-id: <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; format=flowed; charset=Windows-1252; reply-type=response
Content-transfer-encoding: 8BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com> <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com> <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <4BAA4873.3020706@chello.nl>
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"	indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <Adrian.Farrel@huawei.com>
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 08:32:49 -0000

Huub,

You will note that the comment in the liaison you reference said:

"The acronyms PSC and APS are used, in ITU-T APS is a generic term used in 
different methodologies and does not provide a solution."

This was neither a question nor a request for any change. And it is not 
really clear that it is a "concern".

APS is an abstract protocol (G.808.1) with specific characteristics and 
behaviors.

The Survivability Framework deliberately does not prejudge the abstract 
protocol or solution protocol that is required. Instead, it picked another 
acronym to avoid any assumptions. This frees the people working in the 
solution space to choose the necessary abstract model for the problems they 
need to solve, and to develop a protocol realisation that meets the model. 
This neither precludes nor forces the use of APS.

If you like, PSC is simply a generalisation that allows freedom of 
interpretation. Viz.

   In some protection switching schemes (such as bidirectional
   protection switching), it is necessary to coordinate the protection
   state between the edges of the recovery domain.  An MPLS-TP
   Protection State Coordination (PSC) protocol may be used as an in-
   band (i.e., data plane-based) control protocol to align both ends of
   the protected domain.  Control plane-based mechanism can also be used
   to coordinate the protection states between the edges of the
   protection domain.

In the view of the authors, the term "APS" has become synonymous with 
specific protocol realisations. For example, in the working copy of G.8131 I 
have infront of me, section 10 describes the "APS Protocol" setting out byte 
formats and defining messages to go on the wire. While we can interpret "APS 
Protocol" as the technology-specific realisation of "APS", there are 
sufficient overtones that if the Survivability Framework used the term "APS" 
it might be construed as support for a specific protocol realisation. Y.1731 
defines APS PDUs for Ethernet which gives us another competing 
interpretation of the term. (It is notable that the term "APS Protocol" is 
used in G.870 to mean the abstract protocol, which is subtly different from 
its use in G.8131 and Y.1731.)

Surely the working group would prefer to derive the correct protocol 
solution without being constrained except at a functional level?

Adrian


----- Original Message ----- 
From: "Huub van Helvoort" <hhelvoort@chello.nl>
To: "Cecil Byles" <Cecil.Byles@interoute.com>
Cc: <mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
Sent: Wednesday, March 24, 2010 5:14 PM
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC" 
indraft-ietf-mpls-tp-linear-protection-01


Hello Cecil,

You wrote:

> Can I therefore also asked how PSC “Protection State Coordination” in the 
> MPLS-TP parlance align with ITU-T 808.1 recommendation that "defines the 
> generic functional models, characteristics and processes associated with 
> various linear protection schemes for connection-oriented layer networks; 
> e.g., Optical Transport Networks (OTN), Synchronous Digital Hierarchy 
> (SDH) networks and Asynchronous Transfer Mode (ATM) networks" and the 
> sections covering  Terms and Definitions as well as Abbreviations.  IMO 
> all transport engineers and the general telecom community understand that 
> 1+1 or 1:1 are either SNCP or APS. Hence why introduce a new TLA (three 
> letter abbreviation) cover the same function and feature for MPLS-TP.  I 
> can only agree that this will only cause confusion.

I agree with you.

In addition to that:
The ITU-T experts that reviewed the survivability draft had the same
concerns, and expressed that in their reply liaison for the review of
this draft: https://datatracker.ietf.org/liaison/618/ that was
sent in november last year.
This concern has not been addressed yet.

Regards, Huub.


-- 
================================================================
Always remember that you are unique...just like everyone else...
_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp 


From tochio@jp.fujitsu.com  Thu Mar 25 01:43:00 2010
Return-Path: <tochio@jp.fujitsu.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2D6B3A6CF1; Thu, 25 Mar 2010 01:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.546
X-Spam-Level: 
X-Spam-Status: No, score=-96.546 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, 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 T6lScAgpENFz; Thu, 25 Mar 2010 01:43:00 -0700 (PDT)
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by core3.amsl.com (Postfix) with ESMTP id BFCFF3A6CA1; Thu, 25 Mar 2010 01:42:59 -0700 (PDT)
Received: from m1.gw.fujitsu.co.jp ([10.0.50.71]) by fgwmail7.fujitsu.co.jp (Fujitsu Gateway) with ESMTP id o2P8h7xK027482 (envelope-from tochio@jp.fujitsu.com); Thu, 25 Mar 2010 17:43:07 +0900
Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id CC0E245DE59; Thu, 25 Mar 2010 17:43:04 +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 8B87A45DE50; Thu, 25 Mar 2010 17:43:01 +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 0C754E3800C; Thu, 25 Mar 2010 17:42:59 +0900 (JST)
Received: from sw13.gw.fujitsu.co.jp (sw13.gw.fujitsu.co.jp [10.0.76.53]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id ED79FE78014; Thu, 25 Mar 2010 17:42:51 +0900 (JST)
Received: from [127.0.0.1] ([172.31.149.120]) by sw13.gw.fujitsu.co.jp with ESMTP id o2P8geeJ041379; Thu, 25 Mar 2010 17:42:48 +0900 (JST)
X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v0.15.3
Received: from Tochio_FMVS8360[172.31.149.120] by Tochio_FMVS8360 (FujitsuOutboundMailChecker v0.15.3/9992[172.31.149.120]); Thu, 25 Mar 2010 01:42:44 GMT
Message-ID: <4BAB21F5.3020706@jp.fujitsu.com>
Date: Thu, 25 Mar 2010 01:42:29 -0700
From: Yuji Tochio <tochio@jp.fujitsu.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Adrian Farrel <Adrian.Farrel@huawei.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com>	<8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>	<A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com>	<8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com>	<4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>	<4BAA4873.3020706@chello.nl> <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe>
In-Reply-To: <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: Cecil Byles <Cecil.Byles@interoute.com>, mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] [mpls-tp]	Term"PSC"	indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tochio@labs.fujitsu.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 08:43:00 -0000

Hi Adrian,

Very minnor comment, but need to address for clear understanding:

Adrian Farrel wrote:
> Y.1731 defines APS PDUs for Ethernet which gives us another competing
> interpretation of the term. (It is notable that the term "APS
> Protocol" is used in G.870 to mean the abstract protocol, which is
> subtly different from its use in G.8131 and Y.1731.)
>

Y.1731 does not fully define APS PDU, only defines the opcode and common
OAM PDU. APS PDU is defined in G.8031 and G.8032 (ERP)
Please read 9.10.1 in Y.1731

Regards,
Yuji


From Alexander.Vainshtein@ecitele.com  Thu Mar 25 01:52:10 2010
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25EF23A6AF2; Thu, 25 Mar 2010 01:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.819
X-Spam-Level: 
X-Spam-Status: No, score=-0.819 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d5n3GnBcPCjs; Thu, 25 Mar 2010 01:52:09 -0700 (PDT)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id AD9B83A6909; Thu, 25 Mar 2010 01:52:06 -0700 (PDT)
X-AuditID: 93eaf2e7-b7b62ae000003814-d3-4bab221a08dc
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id D8.32.14356.A122BAB4; Thu, 25 Mar 2010 10:43:07 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 25 Mar 2010 10:52:26 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Date: Thu, 25 Mar 2010 10:52:25 +0200
Thread-Topic: [CCAMP] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrL8UXTy/5QKB/HSvmNL816886NAAABtBiA
Message-ID: <A3C5DF08D38B6049839A6F553B331C76C10809F659@ILPTMAIL02.ecitele.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com><8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <239F5ECAA0574FB4A0003E9EC88F5D30@your029b8cecfe>
In-Reply-To: <239F5ECAA0574FB4A0003E9EC88F5D30@your029b8cecfe>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "CCAMP@ietf.org" <CCAMP@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 08:52:10 -0000

Adrian,
Lots of thanks for pointing to 5513, I've missed its publication.
IMHO and FWIW (which are not covered by 5513) it is extremely relevant for =
the MPLS-TP project.
Do you consider 5513bis to cover MPLS-TP?

Regards,
     Sasha

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20
Sent: Thursday, March 25, 2010 9:56 AM
To: Alexander Vainshtein; Vivien Sterling
Cc: mpls@ietf.org; CCAMP@ietf.org; mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protecti=
on-01

For issues related to clashes of acronyms please see RFC 5513.


----- Original Message -----=20
From: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
To: "Vivien Sterling" <vivien.sterling@gmail.com>
Cc: <mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
Sent: Wednesday, March 24, 2010 8:30 AM
Subject: Re: [CCAMP] [mpls] Term "PSC"=20
indraft-ietf-mpls-tp-linear-protection-01


Vivien and all,
AFAIK, PSC stands for "Protection State Coordination" in the MPLS-TP=20
parlance (see MPLS-TP Survivability=20
Framework<http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-survive-fwk/>)=
 =20
- a new fancy name for what has been known as "APS Protocol" in SONET/SDH.

As you've noted, it has a completely different meaning in GMPLS.

Since GMPLS is going to be used with MPLS-TP, double usage of this acronym=
=20
looks highly problematic.

Regards,
     Sasha

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of=20
Vivien Sterling
Sent: Wednesday, March 24, 2010 10:21 AM
To: CCAMP@ietf.org; mpls@ietf.org; mpls-tp@ietf.org
Subject: [mpls] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01

Dear Experts,

I'm surprised to find the term "PSC" used in this draft. I suppose the=20
authors are talking about data plane not control plane, right? Isn't PSC in=
=20
GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(

--
Cheers,
Vivien



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


> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>=20


From zhiwlin@gmail.com  Thu Mar 25 07:37:51 2010
Return-Path: <zhiwlin@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86CBB3A6968; Thu, 25 Mar 2010 07:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.433
X-Spam-Level: 
X-Spam-Status: No, score=-0.433 tagged_above=-999 required=5 tests=[AWL=1.546,  BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, 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 5G6NJ7hxeoLH; Thu, 25 Mar 2010 07:37:50 -0700 (PDT)
Received: from mail-qy0-f196.google.com (mail-qy0-f196.google.com [209.85.221.196]) by core3.amsl.com (Postfix) with ESMTP id 357023A6943; Thu, 25 Mar 2010 07:37:50 -0700 (PDT)
Received: by qyk34 with SMTP id 34so2704244qyk.22 for <multiple recipients>; Thu, 25 Mar 2010 07:38:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=8EwM90nGioOd9PEiCsGgflLt2kq7GhccZzClXB5Wfng=; b=K0dbg/tOffE+tUHHgTXJXmq4qyToUpnP4ZWJqa6suSv7pvAB+2vcxA/3r0Lwkden3a 9fZVeoMelCciCzxgGvAybHFuI+FqjQJXqJ/t+fNXAXxXh2pD4D0Um7qDZ+qdJ0QeAcpj hkMBWf01xDaW8aqQ/fRLiG142rbKp94tZnwPs=
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=VnFKcV2rluHtRCfX1P7MQ5CyIGsYqSoIu1twSm0MbksVC61QocxxgwW/WaOkTubv0Q CRFAOte1Pb6v9JhJ0wy+nO9D0TmBhaqU8yRMEC1BzRv5vyDKCNHq+g0T24EIzIsWbz3R yWQ74nXDw4t8CnzqV0ljwHZdS21DXGeRsueDA=
MIME-Version: 1.0
Received: by 10.229.131.39 with SMTP id v39mr76152qcs.66.1269527889226; Thu,  25 Mar 2010 07:38:09 -0700 (PDT)
In-Reply-To: <201003250609.o2P69T7l062460@harbor.orleans.occnc.com>
References: <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <201003250609.o2P69T7l062460@harbor.orleans.occnc.com>
Date: Thu, 25 Mar 2010 10:38:06 -0400
Message-ID: <67ec4be61003250738v272809bcwd339d5771566f390@mail.gmail.com>
From: Zhi-Wei Lin <zhiwlin@gmail.com>
To: curtis@occnc.com
Content-Type: multipart/alternative; boundary=001517576e80deaeb50482a0fe45
Cc: Cecil Byles <Cecil.Byles@interoute.com>, mpls@ietf.org, CCAMP@ietf.org, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] [mpls-tp] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 14:37:51 -0000

--001517576e80deaeb50482a0fe45
Content-Type: text/plain; charset=UTF-8

Hi,

I like to give my perspective. As a small network company (but one of the
largest transit agencies), we have a small operating staff split into two
groups: one that handles traditional data network (Ethernet, IP), and one
that handles transport network (SONET, WDM).

We are targeting the transport network operating staff to maintain and
operate the MPLS-TP network. As such, anything that will help to reduce the
learning curve (less training), simplify operating, and make the MOP as
consistent as possible between SONET and MPLS-TP would be hugely beneficial.

Obviously there will be some differences since MPLS-TP is a packet-based
transport network, but the standards groups (I don't really care for
politics of IETF and ITU) should strive to make these differences easy to
learn.

Thanks
Zhi


On Thu, Mar 25, 2010 at 2:09 AM, Curtis Villamizar <curtis@occnc.com> wrote:

>
> In message <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>
> "Cecil Byles" writes:
> >
> >
> > Hi,
> > Can I therefore also asked how PSC "Protection State Coordination" in
> > the MPLS-TP parlance align with ITU-T 808.1 recommendation that "defines
> > the generic functional models, characteristics and processes associated
> > with various linear protection schemes for connection-oriented layer
> > networks; e.g., Optical Transport Networks (OTN), Synchronous Digital
> > Hierarchy (SDH) networks and Asynchronous Transfer Mode (ATM) networks"
> > and the sections covering  Terms and Definitions as well as
> > Abbreviations.  IMO all transport engineers and the general telecom
> > community understand that 1+1 or 1:1 are either SNCP or APS. Hence why
> > introduce a new TLA (three letter abbreviation) cover the same function
> > and feature for MPLS-TP.  I can only agree that this will only cause
> > confusion.
> >
> > Cecil Byles
>
>
> Though this is joint work, this is the IETF not the ITU.  We should
> use ITU terms where appropriate but where there is a conflict such as
> this we need to pick another term and another TLA.  If the ITU wants
> to update 808.1 at some later date that is up to the ITU.  In the mean
> time we can use another term and point out the mapping.
>
> Curtis
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

--001517576e80deaeb50482a0fe45
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>I like to give my perspective. As a small network company (but o=
ne of the largest transit agencies), we have a small operating staff split =
into two groups: one that handles traditional data network (Ethernet, IP), =
and one that handles transport network (SONET, WDM).<br>
<br>We are targeting the transport network operating staff to maintain and =
operate the MPLS-TP network. As such, anything that will help to reduce the=
 learning curve (less training), simplify operating, and make the MOP as co=
nsistent as possible between SONET and MPLS-TP would be hugely beneficial.<=
br>
<br>Obviously there will be some differences since MPLS-TP is a packet-base=
d transport network, but the standards groups (I don&#39;t really care for =
politics of IETF and ITU) should strive to make these differences easy to l=
earn.<br>
<br>Thanks<br>Zhi<br><br><br><div class=3D"gmail_quote">On Thu, Mar 25, 201=
0 at 2:09 AM, Curtis Villamizar <span dir=3D"ltr">&lt;<a href=3D"mailto:cur=
tis@occnc.com">curtis@occnc.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid=
 rgb(204, 204, 204); padding-left: 1ex;">
<br>
In message &lt;<a href=3D"mailto:4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@P=
REX22.interoute.com">4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.intero=
ute.com</a>&gt;<br>
<div class=3D"im">&quot;Cecil Byles&quot; writes:<br>
&gt;<br>
&gt;<br>
&gt; Hi,<br>
&gt; Can I therefore also asked how PSC &quot;Protection State Coordination=
&quot; in<br>
&gt; the MPLS-TP parlance align with ITU-T 808.1 recommendation that &quot;=
defines<br>
&gt; the generic functional models, characteristics and processes associate=
d<br>
&gt; with various linear protection schemes for connection-oriented layer<b=
r>
&gt; networks; e.g., Optical Transport Networks (OTN), Synchronous Digital<=
br>
&gt; Hierarchy (SDH) networks and Asynchronous Transfer Mode (ATM) networks=
&quot;<br>
&gt; and the sections covering =C2=A0Terms and Definitions as well as<br>
&gt; Abbreviations. =C2=A0IMO all transport engineers and the general telec=
om<br>
&gt; community understand that 1+1 or 1:1 are either SNCP or APS. Hence why=
<br>
&gt; introduce a new TLA (three letter abbreviation) cover the same functio=
n<br>
&gt; and feature for MPLS-TP. =C2=A0I can only agree that this will only ca=
use<br>
&gt; confusion.<br>
&gt;<br>
&gt; Cecil Byles<br>
<br>
<br>
</div>Though this is joint work, this is the IETF not the ITU. =C2=A0We sho=
uld<br>
use ITU terms where appropriate but where there is a conflict such as<br>
this we need to pick another term and another TLA. =C2=A0If the ITU wants<b=
r>
to update 808.1 at some later date that is up to the ITU. =C2=A0In the mean=
<br>
time we can use another term and point out the mapping.<br>
<br>
Curtis<br>
_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<div><div></div><div class=3D"h5"><a href=3D"https://www.ietf.org/mailman/l=
istinfo/mpls" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls<=
/a><br>
</div></div></blockquote></div><br>

--001517576e80deaeb50482a0fe45--

From lberger@labn.net  Thu Mar 25 08:30:49 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 967A03A684C for <ccamp@core3.amsl.com>; Thu, 25 Mar 2010 08:30:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.485
X-Spam-Level: 
X-Spam-Status: No, score=-1.485 tagged_above=-999 required=5 tests=[AWL=1.650,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K0RE1vTtz15Q for <ccamp@core3.amsl.com>; Thu, 25 Mar 2010 08:30:49 -0700 (PDT)
Received: from outbound-mail-158.bluehost.com (outbound-mail-158.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id 658A73A6B4F for <CCAMP@ietf.org>; Thu, 25 Mar 2010 08:30:36 -0700 (PDT)
Received: (qmail 29284 invoked by uid 0); 25 Mar 2010 15:30:58 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy2.bluehost.com with SMTP; 25 Mar 2010 15:30:58 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=WcmqbtmDheG+pY0RbDATRnd4ULsWaf6YU/40aY8QoMz2BOHStlvEheqx7AuC9mo9K2ue0jcvgBhQqF6KxroFjpapXnZKZrUdQ5ZbhPl0uj6qa/2A8B9yiR3mq+i8AzUp;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1Nup1O-0007Xy-5s; Thu, 25 Mar 2010 09:30:58 -0600
Message-ID: <4BAB81B9.3030004@labn.net>
Date: Thu, 25 Mar 2010 08:31:05 -0700
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20091214 Eudora/3.0b4
MIME-Version: 1.0
To: Adrian Farrel <Adrian.Farrel@huawei.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com>	<8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com>	<A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com>	<8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com>	<4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>	<4BAA4873.3020706@chello.nl> <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe>
In-Reply-To: <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe>
X-Enigmail-Version: 0.96a
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: Cecil Byles <Cecil.Byles@interoute.com>, mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls]	Term"PSC"	indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 15:30:49 -0000

Adrian,
	I fully support the high-level point you are making, i.e., the
continued use of a term other than APS in the context of TP.  That said,
I'm open to renaming PSC to something that doesn't conflict with
existing MPLS/GMPLS terms.  Curtis' proposal of RSC is an example.

Lou

On 3/25/2010 1:32 AM, Adrian Farrel wrote:
> Huub,
> 
> You will note that the comment in the liaison you reference said:
> 
> "The acronyms PSC and APS are used, in ITU-T APS is a generic term used in 
> different methodologies and does not provide a solution."
> 
> This was neither a question nor a request for any change. And it is not 
> really clear that it is a "concern".
> 
> APS is an abstract protocol (G.808.1) with specific characteristics and 
> behaviors.
> 
> The Survivability Framework deliberately does not prejudge the abstract 
> protocol or solution protocol that is required. Instead, it picked another 
> acronym to avoid any assumptions. This frees the people working in the 
> solution space to choose the necessary abstract model for the problems they 
> need to solve, and to develop a protocol realisation that meets the model. 
> This neither precludes nor forces the use of APS.
> 
> If you like, PSC is simply a generalisation that allows freedom of 
> interpretation. Viz.
> 
>    In some protection switching schemes (such as bidirectional
>    protection switching), it is necessary to coordinate the protection
>    state between the edges of the recovery domain.  An MPLS-TP
>    Protection State Coordination (PSC) protocol may be used as an in-
>    band (i.e., data plane-based) control protocol to align both ends of
>    the protected domain.  Control plane-based mechanism can also be used
>    to coordinate the protection states between the edges of the
>    protection domain.
> 
> In the view of the authors, the term "APS" has become synonymous with 
> specific protocol realisations. For example, in the working copy of G.8131 I 
> have infront of me, section 10 describes the "APS Protocol" setting out byte 
> formats and defining messages to go on the wire. While we can interpret "APS 
> Protocol" as the technology-specific realisation of "APS", there are 
> sufficient overtones that if the Survivability Framework used the term "APS" 
> it might be construed as support for a specific protocol realisation. Y.1731 
> defines APS PDUs for Ethernet which gives us another competing 
> interpretation of the term. (It is notable that the term "APS Protocol" is 
> used in G.870 to mean the abstract protocol, which is subtly different from 
> its use in G.8131 and Y.1731.)
> 
> Surely the working group would prefer to derive the correct protocol 
> solution without being constrained except at a functional level?
> 
> Adrian
> 
> 
> ----- Original Message ----- 
> From: "Huub van Helvoort" <hhelvoort@chello.nl>
> To: "Cecil Byles" <Cecil.Byles@interoute.com>
> Cc: <mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
> Sent: Wednesday, March 24, 2010 5:14 PM
> Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC" 
> indraft-ietf-mpls-tp-linear-protection-01
> 
> 
> Hello Cecil,
> 
> You wrote:
> 
>> Can I therefore also asked how PSC “Protection State Coordination” in the 
>> MPLS-TP parlance align with ITU-T 808.1 recommendation that "defines the 
>> generic functional models, characteristics and processes associated with 
>> various linear protection schemes for connection-oriented layer networks; 
>> e.g., Optical Transport Networks (OTN), Synchronous Digital Hierarchy 
>> (SDH) networks and Asynchronous Transfer Mode (ATM) networks" and the 
>> sections covering  Terms and Definitions as well as Abbreviations.  IMO 
>> all transport engineers and the general telecom community understand that 
>> 1+1 or 1:1 are either SNCP or APS. Hence why introduce a new TLA (three 
>> letter abbreviation) cover the same function and feature for MPLS-TP.  I 
>> can only agree that this will only cause confusion.
> 
> I agree with you.
> 
> In addition to that:
> The ITU-T experts that reviewed the survivability draft had the same
> concerns, and expressed that in their reply liaison for the review of
> this draft: https://datatracker.ietf.org/liaison/618/ that was
> sent in november last year.
> This concern has not been addressed yet.
> 
> Regards, Huub.
> 
> 

From ryoo@etri.re.kr  Thu Mar 25 00:40:22 2010
Return-Path: <ryoo@etri.re.kr>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 213823A6808 for <ccamp@core3.amsl.com>; Thu, 25 Mar 2010 00:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.882
X-Spam-Level: 
X-Spam-Status: No, score=-92.882 tagged_above=-999 required=5 tests=[AWL=-1.905, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, HELO_MISMATCH_INFO=1.448, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, MIME_HTML_MOSTLY=0.001, MPART_ALT_DIFF=0.739, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1UE3gaiecBA for <ccamp@core3.amsl.com>; Thu, 25 Mar 2010 00:40:21 -0700 (PDT)
Received: from email1.etri.info (email1.etri.re.kr [129.254.16.131]) by core3.amsl.com (Postfix) with ESMTP id 735713A6890 for <CCAMP@ietf.org>; Thu, 25 Mar 2010 00:40:17 -0700 (PDT)
Received: from mail pickup service by email1.etri.info with Microsoft SMTPSVC; Thu, 25 Mar 2010 16:40:33 +0900
Priority: normal
X-ReadCheckName: CCAMP%40ietf.org
Thread-Topic: Re: [mpls] [mpls-tp] [CCAMP] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
Content-Transfer-Encoding: 7bit
X-ReadCheckMessageID: <d0359862-fe9e-43ee-8a16-7e6a0c38ef0b@etri.re.kr>
thread-index: AcrL7m4yq5LPeUEzQ1ubMWfGqlGU8g==
From: =?ks_c_5601-1987?B?t/nBpLW/?= <ryoo@etri.re.kr>
To: "Curtis Villamizar" <curtis@occnc.com>, <hhelvoort@chello.nl>
Date: Thu, 25 Mar 2010 16:40:33 +0900
Comment: =?ks_c_5601-1987?B?x9GxucD8wNrF673Fv6yxuL/4LCCxpLPXxq6/9sWpv6yxuA==?= =?ks_c_5601-1987?B?xsAsILTjtOc=?=
Message-ID: <8F015281791343DF86D18F32634F1622@etri.info>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_9D01_01CACC39.E1C581A0"
X-Mailer: Microsoft CDO for Exchange 2000
Content-Class: urn:content-classes:message
Importance: normal
x-mimeole: Produced By Microsoft MimeOLE V6.00.3790.4133
X-OriginalArrivalTime: 25 Mar 2010 07:40:33.0947 (UTC) FILETIME=[73D4EEB0:01CACBEE]
X-Mailman-Approved-At: Thu, 25 Mar 2010 08:31:17 -0700
Cc: mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] [mpls-tp] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: =?ks_c_5601-1987?B?t/nBpLW/?= <ryoo@etri.re.kr>
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 07:40:22 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_9D01_01CACC39.E1C581A0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64


------=_NextPart_000_9D01_01CACC39.E1C581A0
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PERJViBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTogsby4siI+DQo8RElWPkl0
IGlzIG15IHVuZGVyc3RhbmRpbmcgdGhhdCBvdGhlciBwYWNrZXQgdHJhbnNwb3J0IHRlY2hub2xv
Z2llcyAoRXRoZXJuZXQgbGluZWFyIHByb3RlY3Rpb24sIEV0aGVybmV0IHJpbmcgcHJvdGVjdGlv
bikgYWxzbyB1c2UgQVBTLiA8L0RJVj4NCjxESVY+PEJSPiZuYnNwOzwvRElWPg0KPERJViBzdHls
ZT0iV09SRC1CUkVBSzogYnJlYWstYWxsOyBGT05ULUZBTUlMWTogIj4NCjxESVY+DQo8RElWIHN0
eWxlPSJGT05ULUZBTUlMWTogIj4NCjxESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogIj4N
CjxESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogIj4NCjxESVY+PEZPTlQgZmFjZT1Bcmlh
bCBzaXplPTI+PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PTxC
Uj5KZW9uZy1kb25nIFJ5b28sIFBoLkQuPEJSPlByaW5jaXBhbCBNZW1iZXIgb2YgUmVzZWFyY2gg
U3RhZmY8QlI+TmV0d29yayBSZXNlYXJjaCBEZXBhcnRtZW50PEJSPkVsZWN0cm9uaWNzIGFuZCBU
ZWxlY29tbXVuaWNhdGlvbnMgUmVzZWFyY2ggSW5zdGl0dXRlIChFVFJJKSA8QlI+UGhvbmU6ICs4
Mi00Mi04NjAtNTM4NCwgRmF4OiArODItNDItODYwLTYzNDI8L0ZPTlQ+PEZPTlQgZmFjZT1Bcmlh
bCBzaXplPTI+PEJSPkVtYWlsOiA8L0ZPTlQ+PEEgaHJlZj0ibWFpbHRvOnJ5b29AZXRyaS5yZS5r
ciIgdGFyZ2V0PV9ibGFuaz48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj5yeW9vQGV0cmkucmUua3I8
L0ZPTlQ+PC9BPjxCUj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj49PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PC9GT05UPjwvRElWPjwvRElWPjwvRElWPjwvRElW
PjwvRElWPjwvRElWPjwvRElWPjwvRElWPg0KPERJVj48QlI+LS0tLS2/+Lq7ILjevcPB9i0tLS0t
PEJSPjxCPkZyb206PC9CPiAiQ3VydGlzIFZpbGxhbWl6YXIiICZsdDtjdXJ0aXNAb2NjbmMuY29t
Jmd0OzxCUj48Qj5Gcm9tIERhdGU6PC9CPiAyMDEwLTAzLTI1IL/AyMQgNDoxODoxNzxCUj48Qj5U
bzo8L0I+ICJoaGVsdm9vcnRAY2hlbGxvLm5sIiAmbHQ7aGhlbHZvb3J0QGNoZWxsby5ubCZndDs8
QlI+PEI+Q2M6PC9CPiAibXBsc0BpZXRmLm9yZyIgJmx0O21wbHNAaWV0Zi5vcmcmZ3Q7LCAiQ0NB
TVBAaWV0Zi5vcmciICZsdDtDQ0FNUEBpZXRmLm9yZyZndDssICJtcGxzLXRwQGlldGYub3JnIiAm
bHQ7bXBscy10cEBpZXRmLm9yZyZndDssICJjdXJ0aXNAb2NjbmMuY29tIiAmbHQ7Y3VydGlzQG9j
Y25jLmNvbSZndDs8QlI+PEI+U3ViamVjdDo8L0I+IFJlOiBbbXBsc10gW21wbHMtdHBdIFtDQ0FN
UF0gVGVybSAiUFNDIiBpbmRyYWZ0LWlldGYtbXBscy10cC1saW5lYXItcHJvdGVjdGlvbi0wMTxC
Uj48QlI+PC9ESVY+DQo8RElWPjwhLS0gQ29udmVydGVkIGZyb20gdGV4dC9wbGFpbiBmb3JtYXQg
LS0+PEJSPjxCUj4NCjxQPjxGT05UIHNpemU9Mj5JbiBtZXNzYWdlICZsdDs0QkFCMDAyMC4yMDQw
ODA0QGNoZWxsby5ubCZndDs8QlI+SHV1YiB2YW4gSGVsdm9vcnQgd3JpdGVzOjxCUj4mZ3Q7Jm5i
c3A7PEJSPiZndDsgSGkgQ3VydGlzLDxCUj4mZ3Q7Jm5ic3A7PEJSPiZndDsgWW91IHdyb3RlOjxC
Uj4mZ3Q7Jm5ic3A7PEJSPiZndDsgJmd0OyBJbiBtZXNzYWdlICZsdDs4YmYzOTM0MTAwMzI0MDEy
MHI1NTRiNzJqM2Y2YjkyNDQ3NWExMWQzY0BtYWlsLmdtYWlsLmNvbSZndDs8QlI+Jmd0OyAmZ3Q7
IFZpdmllbiBTdGVybGluZyB3cml0ZXM6PEJSPiZndDsgJmd0OyZndDsmbmJzcDs8QlI+Jmd0OyAm
Z3Q7Jmd0OyBEZWFyIEV4cGVydHMsPEJSPiZndDsgJmd0OyZndDsmbmJzcDs8QlI+Jmd0OyAmZ3Q7
Jmd0OyBJJ20gc3VycHJpc2VkIHRvIGZpbmQgdGhlIHRlcm0gIlBTQyIgdXNlZCBpbiB0aGlzIGRy
YWZ0LiBJIHN1cHBvc2UgdGhlPEJSPiZndDsgJmd0OyZndDsgYXV0aG9ycyBhcmUgdGFsa2luZyBh
Ym91dCBkYXRhIHBsYW5lIG5vdCBjb250cm9sIHBsYW5lLCByaWdodD8gSXNuJ3QgUFNDIGluPEJS
PiZndDsgJmd0OyZndDsgR01QTFMgZWxhYm9yYXRlZCBhcyAiUGFja2V0IFN3aXRjaCBDYXBhYmxl
IiA/IEl0J3MgY29uZnVzaW5nIDotKDxCUj4mZ3Q7ICZndDsmZ3Q7Jm5ic3A7PEJSPiZndDsgJmd0
OyZndDsgLS08QlI+Jmd0OyAmZ3Q7Jmd0OyBDaGVlcnMsPEJSPiZndDsgJmd0OyZndDsgVml2aWVu
PEJSPiZndDsgJmd0OzxCUj4mZ3Q7ICZndDsgSSBmdWxseSBhZ3JlZS4mbmJzcDsgVGhpcyBpcyBh
biBJRVRGIGRvY3VtZW50IHdpdGhpbiBNUExTIGFuZCB0aGUgUFNDPEJSPiZndDsgJmd0OyBhY3Jv
bnltIGNvbmZsaWN0cyB3aXRoIGEgcHJpb3IgTVBMUyBhY3JvbnltLiZuYnNwOyBUaGUgcHJpb3Ig
dXNhZ2Ugc2hvdWxkPEJSPiZndDsgJmd0OyB0YWtlIHByZWNlZGVuY2UuJm5ic3A7IFRoaXMgYWNy
b255bSByZWFsbHkgc2hvdWxkIGJlIGNoYW5nZWQuPEJSPiZndDsgJmd0OzxCUj4mZ3Q7ICZndDsg
QSBjaGFuZ2UgYXMgc2ltcGxlIGFzIHJlY292ZXJ5IHNlcnZpY2UgY29vcmRpbmF0aW9uIChSU0Mp
IHdvdWxkIGF2b2lkPEJSPiZndDsgJmd0OyB0aGUgY2xhc2guJm5ic3A7IE9yIGEgc3Vic3RpdHV0
ZSBmb3IgdGhlIHdvcmQgY29vcmRpbmF0aW9uIGNvdWxkIGJlIHVzZWQuPEJSPiZndDsmbmJzcDs8
QlI+Jmd0OyBXaGF0IGlzIHdyb25nIHdpdGggdGhlIGFjcm9ueW0gQVBTPzxCUj4mZ3Q7IE1QTFMt
VFAgd2lsbCBiZSB1c2VkIGJ5IHRyYW5zcG9ydCBuZXR3b3JrIG9wZXJhdG9ycyB0aGF0IGFyZTxC
Uj4mZ3Q7IGZhbWlsaWFyIHdpdGggdGhlIHRlcm0gQVBTIGFuZCB3aGVyZSBpdCBpcyB1c2VkIGZv
ci48QlI+Jmd0OyBXaHkgY29uZnVzZSB0aGVtIHdpdGggYW5vdGhlciBUTFcgKHRocmVlIGxldHRl
ciB3b3JkKT88QlI+Jmd0OyZuYnNwOzxCUj4mZ3Q7IFJlZ2FyZHMsIEh1dWIuPEJSPjxCUj48QlI+
QVBTIGlzIHNwZWNpZmljIHRvIFNPTkVUIGFuZCBzZXJ2ZXMgYSBzaW1pbGFyIGZ1bmN0aW9uIGJ1
dCBpczxCUj5kaWZmZXJlbnQuPEJSPjxCUj5DdXJ0aXM8QlI+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX188QlI+bXBscyBtYWlsaW5nIGxpc3Q8QlI+bXBsc0Bp
ZXRmLm9yZzxCUj48QSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L21wbHMiIHRhcmdldD1fYmxhbms+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9tcGxzPC9BPjxCUj48L0ZPTlQ+PC9QPjwvRElWPjwvRElWPjxpbWcgc3R5bGU9ImRpc3BsYXk6
bm9uZSIgd2lkdGg9MCBoZWlnaHQ9MCBzcmM9Imh0dHA6Ly91bWFpbC5ldHJpLnJlLmtyL0V4dGVy
bmFsX1JlYWRDaGVjay5hc3B4P2VtYWlsPUNDQU1QQGlldGYub3JnJm5hbWU9Q0NBTVAlNDBpZXRm
Lm9yZyZmcm9tZW1haWw9cnlvb0BldHJpLnJlLmtyJm1lc3NhZ2VpZD0lM0NkMDM1OTg2Mi1mZTll
LTQzZWUtOGExNi03ZTZhMGMzOGVmMGJAZXRyaS5yZS5rciUzRSI+

------=_NextPart_000_9D01_01CACC39.E1C581A0--

From davari@broadcom.com  Thu Mar 25 08:35:29 2010
Return-Path: <davari@broadcom.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 407893A67AC; Thu, 25 Mar 2010 08:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.54
X-Spam-Level: 
X-Spam-Status: No, score=-1.54 tagged_above=-999 required=5 tests=[AWL=1.929,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJHMtUvlM3ap; Thu, 25 Mar 2010 08:35:28 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id E7C4F3A6870; Thu, 25 Mar 2010 08:35:26 -0700 (PDT)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 25 Mar 2010 08:35:36 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Thu, 25 Mar 2010 08:35:35 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Date: Thu, 25 Mar 2010 08:35:34 -0700
Thread-Topic: [mpls] [CCAMP] [mpls-tp] Term"PSC" indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrMMFcBt6PYcPOQT3etNQyg4TTtkwAAD7gg
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD68171BEA1DA@SJEXCHCCR02.corp.ad.broadcom.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com> <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com> <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <4BAA4873.3020706@chello.nl> <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe> <4BAB81B9.3030004@labn.net>
In-Reply-To: <4BAB81B9.3030004@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67B55D4D31G70609919-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "CCAMP@ietf.org" <CCAMP@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls] [mpls-tp] Term"PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 15:35:29 -0000

Hi,

By the way PSC is also used in RFC3270 as acronym for "Per-hop Scheduling C=
lass"

Thanks,
Shahram=20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Lou=
 Berger
Sent: Thursday, March 25, 2010 8:31 AM
To: Adrian Farrel
Cc: Cecil Byles; mpls@ietf.org; CCAMP@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls] [CCAMP] [mpls-tp] Term"PSC" indraft-ietf-mpls-tp-linear=
-protection-01

Adrian,
	I fully support the high-level point you are making, i.e., the
continued use of a term other than APS in the context of TP.  That said,
I'm open to renaming PSC to something that doesn't conflict with
existing MPLS/GMPLS terms.  Curtis' proposal of RSC is an example.

Lou

On 3/25/2010 1:32 AM, Adrian Farrel wrote:
> Huub,
>=20
> You will note that the comment in the liaison you reference said:
>=20
> "The acronyms PSC and APS are used, in ITU-T APS is a generic term used i=
n=20
> different methodologies and does not provide a solution."
>=20
> This was neither a question nor a request for any change. And it is not=20
> really clear that it is a "concern".
>=20
> APS is an abstract protocol (G.808.1) with specific characteristics and=20
> behaviors.
>=20
> The Survivability Framework deliberately does not prejudge the abstract=20
> protocol or solution protocol that is required. Instead, it picked anothe=
r=20
> acronym to avoid any assumptions. This frees the people working in the=20
> solution space to choose the necessary abstract model for the problems th=
ey=20
> need to solve, and to develop a protocol realisation that meets the model=
.=20
> This neither precludes nor forces the use of APS.
>=20
> If you like, PSC is simply a generalisation that allows freedom of=20
> interpretation. Viz.
>=20
>    In some protection switching schemes (such as bidirectional
>    protection switching), it is necessary to coordinate the protection
>    state between the edges of the recovery domain.  An MPLS-TP
>    Protection State Coordination (PSC) protocol may be used as an in-
>    band (i.e., data plane-based) control protocol to align both ends of
>    the protected domain.  Control plane-based mechanism can also be used
>    to coordinate the protection states between the edges of the
>    protection domain.
>=20
> In the view of the authors, the term "APS" has become synonymous with=20
> specific protocol realisations. For example, in the working copy of G.813=
1 I=20
> have infront of me, section 10 describes the "APS Protocol" setting out b=
yte=20
> formats and defining messages to go on the wire. While we can interpret "=
APS=20
> Protocol" as the technology-specific realisation of "APS", there are=20
> sufficient overtones that if the Survivability Framework used the term "A=
PS"=20
> it might be construed as support for a specific protocol realisation. Y.1=
731=20
> defines APS PDUs for Ethernet which gives us another competing=20
> interpretation of the term. (It is notable that the term "APS Protocol" i=
s=20
> used in G.870 to mean the abstract protocol, which is subtly different fr=
om=20
> its use in G.8131 and Y.1731.)
>=20
> Surely the working group would prefer to derive the correct protocol=20
> solution without being constrained except at a functional level?
>=20
> Adrian
>=20
>=20
> ----- Original Message -----=20
> From: "Huub van Helvoort" <hhelvoort@chello.nl>
> To: "Cecil Byles" <Cecil.Byles@interoute.com>
> Cc: <mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
> Sent: Wednesday, March 24, 2010 5:14 PM
> Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"=20
> indraft-ietf-mpls-tp-linear-protection-01
>=20
>=20
> Hello Cecil,
>=20
> You wrote:
>=20
>> Can I therefore also asked how PSC "Protection State Coordination" in th=
e=20
>> MPLS-TP parlance align with ITU-T 808.1 recommendation that "defines the=
=20
>> generic functional models, characteristics and processes associated with=
=20
>> various linear protection schemes for connection-oriented layer networks=
;=20
>> e.g., Optical Transport Networks (OTN), Synchronous Digital Hierarchy=20
>> (SDH) networks and Asynchronous Transfer Mode (ATM) networks" and the=20
>> sections covering  Terms and Definitions as well as Abbreviations.  IMO=
=20
>> all transport engineers and the general telecom community understand tha=
t=20
>> 1+1 or 1:1 are either SNCP or APS. Hence why introduce a new TLA (three=
=20
>> letter abbreviation) cover the same function and feature for MPLS-TP.  I=
=20
>> can only agree that this will only cause confusion.
>=20
> I agree with you.
>=20
> In addition to that:
> The ITU-T experts that reviewed the survivability draft had the same
> concerns, and expressed that in their reply liaison for the review of
> this draft: https://datatracker.ietf.org/liaison/618/ that was
> sent in november last year.
> This concern has not been addressed yet.
>=20
> Regards, Huub.
>=20
>=20
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls



From zhiwlin@gmail.com  Thu Mar 25 08:42:47 2010
Return-Path: <zhiwlin@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CE633A6A03; Thu, 25 Mar 2010 08:42:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level: 
X-Spam-Status: No, score=-1.318 tagged_above=-999 required=5 tests=[AWL=2.150,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, 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 u3HSAlgL2e+N; Thu, 25 Mar 2010 08:42:42 -0700 (PDT)
Received: from mail-qy0-f196.google.com (mail-qy0-f196.google.com [209.85.221.196]) by core3.amsl.com (Postfix) with ESMTP id DFD5D3A6B7D; Thu, 25 Mar 2010 08:41:49 -0700 (PDT)
Received: by qyk34 with SMTP id 34so2767644qyk.22 for <multiple recipients>; Thu, 25 Mar 2010 08:42:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=i1hIdvDLuF48mkWi+8brvUXAUZRrGRgCWckpI0X2BAY=; b=YO/aUCAz3i52IEe5hGrs+Jisnp/LAj3dsQEyuZPyzN9+8Jt04ODOIIP6YMbOj8qSGx 76lhEcO1pjhVhNYv5gDPhDuLaiF/3df+iRNPGzwDMEJBER/NMUt2bD8AlyYYD0mjdDru 3qRKsZW5wBFwKvIYozMsyOtxpVyryOj54MU0o=
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=Xvlz4FwlSR6im6JdLTEvCLJOQPK+Cz/Zo2MfoFnxiBNWJq1yAi+KIfa9QVSaUrWviV 8kvtPTqewB3Z7Mp+JClW66nQenIryK6MuX/ki1RnLV2FE7Tk/+KV/Um21AS4yBsGpot8 vfe4ZGKvbxUEhb5PiludNS69l4Lk7SQHbZ1CA=
MIME-Version: 1.0
Received: by 10.229.88.193 with SMTP id b1mr769029qcm.27.1269531728081; Thu,  25 Mar 2010 08:42:08 -0700 (PDT)
In-Reply-To: <4BAB81B9.3030004@labn.net>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com> <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com> <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <4BAA4873.3020706@chello.nl> <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe> <4BAB81B9.3030004@labn.net>
Date: Thu, 25 Mar 2010 11:42:08 -0400
Message-ID: <67ec4be61003250842r7927acaes1a39905d92a3a7dc@mail.gmail.com>
From: Zhi-Wei Lin <zhiwlin@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=0016363b797aaef5980482a1e35a
Cc: Cecil Byles <Cecil.Byles@interoute.com>, mpls@ietf.org, CCAMP@ietf.org, Adrian Farrel <Adrian.Farrel@huawei.com>, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 15:42:47 -0000

--0016363b797aaef5980482a1e35a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

We have PSC, RSC, APS...how about MPS for MPLS-TP Protection Switching...? =
I
think the acronym (whatever it is) should have "protection switching" in it
just so that transport folks know it is similar to what they have used (but
different because it's not TDM based).

Thanks
Zhi

On Thu, Mar 25, 2010 at 11:31 AM, Lou Berger <lberger@labn.net> wrote:

> Adrian,
>        I fully support the high-level point you are making, i.e., the
> continued use of a term other than APS in the context of TP.  That said,
> I'm open to renaming PSC to something that doesn't conflict with
> existing MPLS/GMPLS terms.  Curtis' proposal of RSC is an example.
>
> Lou
>
> On 3/25/2010 1:32 AM, Adrian Farrel wrote:
> > Huub,
> >
> > You will note that the comment in the liaison you reference said:
> >
> > "The acronyms PSC and APS are used, in ITU-T APS is a generic term used
> in
> > different methodologies and does not provide a solution."
> >
> > This was neither a question nor a request for any change. And it is not
> > really clear that it is a "concern".
> >
> > APS is an abstract protocol (G.808.1) with specific characteristics and
> > behaviors.
> >
> > The Survivability Framework deliberately does not prejudge the abstract
> > protocol or solution protocol that is required. Instead, it picked
> another
> > acronym to avoid any assumptions. This frees the people working in the
> > solution space to choose the necessary abstract model for the problems
> they
> > need to solve, and to develop a protocol realisation that meets the
> model.
> > This neither precludes nor forces the use of APS.
> >
> > If you like, PSC is simply a generalisation that allows freedom of
> > interpretation. Viz.
> >
> >    In some protection switching schemes (such as bidirectional
> >    protection switching), it is necessary to coordinate the protection
> >    state between the edges of the recovery domain.  An MPLS-TP
> >    Protection State Coordination (PSC) protocol may be used as an in-
> >    band (i.e., data plane-based) control protocol to align both ends of
> >    the protected domain.  Control plane-based mechanism can also be use=
d
> >    to coordinate the protection states between the edges of the
> >    protection domain.
> >
> > In the view of the authors, the term "APS" has become synonymous with
> > specific protocol realisations. For example, in the working copy of
> G.8131 I
> > have infront of me, section 10 describes the "APS Protocol" setting out
> byte
> > formats and defining messages to go on the wire. While we can interpret
> "APS
> > Protocol" as the technology-specific realisation of "APS", there are
> > sufficient overtones that if the Survivability Framework used the term
> "APS"
> > it might be construed as support for a specific protocol realisation.
> Y.1731
> > defines APS PDUs for Ethernet which gives us another competing
> > interpretation of the term. (It is notable that the term "APS Protocol"
> is
> > used in G.870 to mean the abstract protocol, which is subtly different
> from
> > its use in G.8131 and Y.1731.)
> >
> > Surely the working group would prefer to derive the correct protocol
> > solution without being constrained except at a functional level?
> >
> > Adrian
> >
> >
> > ----- Original Message -----
> > From: "Huub van Helvoort" <hhelvoort@chello.nl>
> > To: "Cecil Byles" <Cecil.Byles@interoute.com>
> > Cc: <mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
> > Sent: Wednesday, March 24, 2010 5:14 PM
> > Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"
> > indraft-ietf-mpls-tp-linear-protection-01
> >
> >
> > Hello Cecil,
> >
> > You wrote:
> >
> >> Can I therefore also asked how PSC =E2=80=9CProtection State Coordinat=
ion=E2=80=9D in
> the
> >> MPLS-TP parlance align with ITU-T 808.1 recommendation that "defines t=
he
> >> generic functional models, characteristics and processes associated wi=
th
> >> various linear protection schemes for connection-oriented layer
> networks;
> >> e.g., Optical Transport Networks (OTN), Synchronous Digital Hierarchy
> >> (SDH) networks and Asynchronous Transfer Mode (ATM) networks" and the
> >> sections covering  Terms and Definitions as well as Abbreviations.  IM=
O
> >> all transport engineers and the general telecom community understand
> that
> >> 1+1 or 1:1 are either SNCP or APS. Hence why introduce a new TLA (thre=
e
> >> letter abbreviation) cover the same function and feature for MPLS-TP. =
 I
> >> can only agree that this will only cause confusion.
> >
> > I agree with you.
> >
> > In addition to that:
> > The ITU-T experts that reviewed the survivability draft had the same
> > concerns, and expressed that in their reply liaison for the review of
> > this draft: https://datatracker.ietf.org/liaison/618/ that was
> > sent in november last year.
> > This concern has not been addressed yet.
> >
> > Regards, Huub.
> >
> >
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>

--0016363b797aaef5980482a1e35a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>We have PSC, RSC, APS...how about MPS for MPLS-TP Protection Swi=
tching...? I think the acronym (whatever it is) should have &quot;protectio=
n switching&quot; in it just so that transport folks know it is similar to =
what they have used (but different because it&#39;s not TDM based).<br>
<br>Thanks<br>Zhi<br><br><div class=3D"gmail_quote">On Thu, Mar 25, 2010 at=
 11:31 AM, Lou Berger <span dir=3D"ltr">&lt;<a href=3D"mailto:lberger@labn.=
net">lberger@labn.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 2=
04, 204); padding-left: 1ex;">
Adrian,<br>
 =C2=A0 =C2=A0 =C2=A0 =C2=A0I fully support the high-level point you are ma=
king, i.e., the<br>
continued use of a term other than APS in the context of TP. =C2=A0That sai=
d,<br>
I&#39;m open to renaming PSC to something that doesn&#39;t conflict with<br=
>
existing MPLS/GMPLS terms. =C2=A0Curtis&#39; proposal of RSC is an example.=
<br>
<br>
Lou<br>
<br>
On 3/25/2010 1:32 AM, Adrian Farrel wrote:<br>
&gt; Huub,<br>
&gt;<br>
&gt; You will note that the comment in the liaison you reference said:<br>
&gt;<br>
&gt; &quot;The acronyms PSC and APS are used, in ITU-T APS is a generic ter=
m used in<br>
&gt; different methodologies and does not provide a solution.&quot;<br>
&gt;<br>
&gt; This was neither a question nor a request for any change. And it is no=
t<br>
&gt; really clear that it is a &quot;concern&quot;.<br>
&gt;<br>
&gt; APS is an abstract protocol (G.808.1) with specific characteristics an=
d<br>
&gt; behaviors.<br>
&gt;<br>
&gt; The Survivability Framework deliberately does not prejudge the abstrac=
t<br>
&gt; protocol or solution protocol that is required. Instead, it picked ano=
ther<br>
&gt; acronym to avoid any assumptions. This frees the people working in the=
<br>
&gt; solution space to choose the necessary abstract model for the problems=
 they<br>
&gt; need to solve, and to develop a protocol realisation that meets the mo=
del.<br>
&gt; This neither precludes nor forces the use of APS.<br>
&gt;<br>
&gt; If you like, PSC is simply a generalisation that allows freedom of<br>
&gt; interpretation. Viz.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0In some protection switching schemes (such as bidirection=
al<br>
&gt; =C2=A0 =C2=A0protection switching), it is necessary to coordinate the =
protection<br>
&gt; =C2=A0 =C2=A0state between the edges of the recovery domain. =C2=A0An =
MPLS-TP<br>
&gt; =C2=A0 =C2=A0Protection State Coordination (PSC) protocol may be used =
as an in-<br>
&gt; =C2=A0 =C2=A0band (i.e., data plane-based) control protocol to align b=
oth ends of<br>
&gt; =C2=A0 =C2=A0the protected domain. =C2=A0Control plane-based mechanism=
 can also be used<br>
&gt; =C2=A0 =C2=A0to coordinate the protection states between the edges of =
the<br>
&gt; =C2=A0 =C2=A0protection domain.<br>
&gt;<br>
&gt; In the view of the authors, the term &quot;APS&quot; has become synony=
mous with<br>
&gt; specific protocol realisations. For example, in the working copy of G.=
8131 I<br>
&gt; have infront of me, section 10 describes the &quot;APS Protocol&quot; =
setting out byte<br>
&gt; formats and defining messages to go on the wire. While we can interpre=
t &quot;APS<br>
&gt; Protocol&quot; as the technology-specific realisation of &quot;APS&quo=
t;, there are<br>
&gt; sufficient overtones that if the Survivability Framework used the term=
 &quot;APS&quot;<br>
&gt; it might be construed as support for a specific protocol realisation. =
Y.1731<br>
<div class=3D"im">&gt; defines APS PDUs for Ethernet which gives us another=
 competing<br>
&gt; interpretation of the term. (It is notable that the term &quot;APS Pro=
tocol&quot; is<br>
&gt; used in G.870 to mean the abstract protocol, which is subtly different=
 from<br>
&gt; its use in G.8131 and Y.1731.)<br>
&gt;<br>
</div>&gt; Surely the working group would prefer to derive the correct prot=
ocol<br>
&gt; solution without being constrained except at a functional level?<br>
&gt;<br>
&gt; Adrian<br>
<div class=3D"im">&gt;<br>
&gt;<br>
&gt; ----- Original Message -----<br>
&gt; From: &quot;Huub van Helvoort&quot; &lt;<a href=3D"mailto:hhelvoort@ch=
ello.nl">hhelvoort@chello.nl</a>&gt;<br>
&gt; To: &quot;Cecil Byles&quot; &lt;<a href=3D"mailto:Cecil.Byles@interout=
e.com">Cecil.Byles@interoute.com</a>&gt;<br>
&gt; Cc: &lt;<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;; &lt;<a=
 href=3D"mailto:CCAMP@ietf.org">CCAMP@ietf.org</a>&gt;; &lt;<a href=3D"mail=
to:mpls-tp@ietf.org">mpls-tp@ietf.org</a>&gt;<br>
</div><div class=3D"im">&gt; Sent: Wednesday, March 24, 2010 5:14 PM<br>
&gt; Subject: Re: [CCAMP] [mpls-tp] [mpls] Term&quot;PSC&quot;<br>
&gt; indraft-ietf-mpls-tp-linear-protection-01<br>
&gt;<br>
&gt;<br>
</div><div><div></div><div class=3D"h5">&gt; Hello Cecil,<br>
&gt;<br>
&gt; You wrote:<br>
&gt;<br>
&gt;&gt; Can I therefore also asked how PSC =E2=80=9CProtection State Coord=
ination=E2=80=9D in the<br>
&gt;&gt; MPLS-TP parlance align with ITU-T 808.1 recommendation that &quot;=
defines the<br>
&gt;&gt; generic functional models, characteristics and processes associate=
d with<br>
&gt;&gt; various linear protection schemes for connection-oriented layer ne=
tworks;<br>
&gt;&gt; e.g., Optical Transport Networks (OTN), Synchronous Digital Hierar=
chy<br>
&gt;&gt; (SDH) networks and Asynchronous Transfer Mode (ATM) networks&quot;=
 and the<br>
&gt;&gt; sections covering =C2=A0Terms and Definitions as well as Abbreviat=
ions. =C2=A0IMO<br>
&gt;&gt; all transport engineers and the general telecom community understa=
nd that<br>
&gt;&gt; 1+1 or 1:1 are either SNCP or APS. Hence why introduce a new TLA (=
three<br>
&gt;&gt; letter abbreviation) cover the same function and feature for MPLS-=
TP. =C2=A0I<br>
&gt;&gt; can only agree that this will only cause confusion.<br>
&gt;<br>
&gt; I agree with you.<br>
&gt;<br>
&gt; In addition to that:<br>
&gt; The ITU-T experts that reviewed the survivability draft had the same<b=
r>
&gt; concerns, and expressed that in their reply liaison for the review of<=
br>
&gt; this draft: <a href=3D"https://datatracker.ietf.org/liaison/618/" targ=
et=3D"_blank">https://datatracker.ietf.org/liaison/618/</a> that was<br>
&gt; sent in november last year.<br>
&gt; This concern has not been addressed yet.<br>
&gt;<br>
&gt; Regards, Huub.<br>
&gt;<br>
&gt;<br>
</div></div>_______________________________________________<br>
CCAMP mailing list<br>
<a href=3D"mailto:CCAMP@ietf.org">CCAMP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ccamp" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/ccamp</a><br>
</blockquote></div><br>

--0016363b797aaef5980482a1e35a--

From neil.2.harrison@bt.com  Thu Mar 25 08:56:50 2010
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0551A3A6B58; Thu, 25 Mar 2010 08:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level: 
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rIO9bedExfwl; Thu, 25 Mar 2010 08:56:37 -0700 (PDT)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138]) by core3.amsl.com (Postfix) with ESMTP id 1FE2C3A6B00; Thu, 25 Mar 2010 08:56:34 -0700 (PDT)
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.111]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 25 Mar 2010 15:56:55 +0000
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CACC33.BB3A34AD"
Date: Thu, 25 Mar 2010 15:56:27 -0000
Message-ID: <2ECAA42C79676B42AEBAC11229CA7D0C05C105AC@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <67ec4be61003250842r7927acaes1a39905d92a3a7dc@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [CCAMP] [mpls-tp] [mpls] Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrMMeUjKErPQOPpTa6mLkJaqy6dNQAAGgcA
From: <neil.2.harrison@bt.com>
To: <zhiwlin@gmail.com>, <lberger@labn.net>
X-OriginalArrivalTime: 25 Mar 2010 15:56:55.0326 (UTC) FILETIME=[CAEABBE0:01CACC33]
Cc: Cecil.Byles@interoute.com, mpls@ietf.org, CCAMP@ietf.org, Adrian.Farrel@huawei.com, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 15:56:50 -0000

This is a multi-part message in MIME format.

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

There are only so many ways to provide DP/MP/CP components of each of
the 3 networking modes (addressing, signalling, routing, OAM,
etc)....and there will be a best-of-breed solution for a given component
at any given time, whatever name we give it.  I sometimes sense that
judgement of technical merit might get compromised by a stronger NIH
(Not Invented Here) behaviour....esp if the component in question comes
from another SDO.=20
=20
Speaking as an operator we have a (well publicised internally) desire to
have as much sensible re-use of components as possible.
=20
regards, Neil


________________________________

	From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On
Behalf Of Zhi-Wei Lin
	Sent: 25 March 2010 15:42
	To: Lou Berger
	Cc: Cecil Byles; mpls@ietf.org; CCAMP@ietf.org; Adrian Farrel;
mpls-tp@ietf.org
	Subject: Re: [CCAMP] [mpls-tp] [mpls]
Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
=09
=09
	Hi,
=09
	We have PSC, RSC, APS...how about MPS for MPLS-TP Protection
Switching...? I think the acronym (whatever it is) should have
"protection switching" in it just so that transport folks know it is
similar to what they have used (but different because it's not TDM
based).
=09
	Thanks
	Zhi
=09
=09
	On Thu, Mar 25, 2010 at 11:31 AM, Lou Berger <lberger@labn.net>
wrote:
=09

		Adrian,
		       I fully support the high-level point you are
making, i.e., the
		continued use of a term other than APS in the context of
TP.  That said,
		I'm open to renaming PSC to something that doesn't
conflict with
		existing MPLS/GMPLS terms.  Curtis' proposal of RSC is
an example.
	=09
		Lou
	=09
		On 3/25/2010 1:32 AM, Adrian Farrel wrote:
		> Huub,
		>
		> You will note that the comment in the liaison you
reference said:
		>
		> "The acronyms PSC and APS are used, in ITU-T APS is a
generic term used in
		> different methodologies and does not provide a
solution."
		>
		> This was neither a question nor a request for any
change. And it is not
		> really clear that it is a "concern".
		>
		> APS is an abstract protocol (G.808.1) with specific
characteristics and
		> behaviors.
		>
		> The Survivability Framework deliberately does not
prejudge the abstract
		> protocol or solution protocol that is required.
Instead, it picked another
		> acronym to avoid any assumptions. This frees the
people working in the
		> solution space to choose the necessary abstract model
for the problems they
		> need to solve, and to develop a protocol realisation
that meets the model.
		> This neither precludes nor forces the use of APS.
		>
		> If you like, PSC is simply a generalisation that
allows freedom of
		> interpretation. Viz.
		>
		>    In some protection switching schemes (such as
bidirectional
		>    protection switching), it is necessary to
coordinate the protection
		>    state between the edges of the recovery domain.  An
MPLS-TP
		>    Protection State Coordination (PSC) protocol may be
used as an in-
		>    band (i.e., data plane-based) control protocol to
align both ends of
		>    the protected domain.  Control plane-based
mechanism can also be used
		>    to coordinate the protection states between the
edges of the
		>    protection domain.
		>
		> In the view of the authors, the term "APS" has become
synonymous with
		> specific protocol realisations. For example, in the
working copy of G.8131 I
		> have infront of me, section 10 describes the "APS
Protocol" setting out byte
		> formats and defining messages to go on the wire. While
we can interpret "APS
		> Protocol" as the technology-specific realisation of
"APS", there are
		> sufficient overtones that if the Survivability
Framework used the term "APS"
		> it might be construed as support for a specific
protocol realisation. Y.1731
	=09
		> defines APS PDUs for Ethernet which gives us another
competing
		> interpretation of the term. (It is notable that the
term "APS Protocol" is
		> used in G.870 to mean the abstract protocol, which is
subtly different from
		> its use in G.8131 and Y.1731.)
		>
	=09
		> Surely the working group would prefer to derive the
correct protocol
		> solution without being constrained except at a
functional level?
		>
		> Adrian
	=09
		>
		>
		> ----- Original Message -----
		> From: "Huub van Helvoort" <hhelvoort@chello.nl>
		> To: "Cecil Byles" <Cecil.Byles@interoute.com>
		> Cc: <mpls@ietf.org>; <CCAMP@ietf.org>;
<mpls-tp@ietf.org>
	=09
		> Sent: Wednesday, March 24, 2010 5:14 PM
		> Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"
		> indraft-ietf-mpls-tp-linear-protection-01
		>
		>
	=09
		> Hello Cecil,
		>
		> You wrote:
		>
		>> Can I therefore also asked how PSC "Protection State
Coordination" in the
		>> MPLS-TP parlance align with ITU-T 808.1
recommendation that "defines the
		>> generic functional models, characteristics and
processes associated with
		>> various linear protection schemes for
connection-oriented layer networks;
		>> e.g., Optical Transport Networks (OTN), Synchronous
Digital Hierarchy
		>> (SDH) networks and Asynchronous Transfer Mode (ATM)
networks" and the
		>> sections covering  Terms and Definitions as well as
Abbreviations.  IMO
		>> all transport engineers and the general telecom
community understand that
		>> 1+1 or 1:1 are either SNCP or APS. Hence why
introduce a new TLA (three
		>> letter abbreviation) cover the same function and
feature for MPLS-TP.  I
		>> can only agree that this will only cause confusion.
		>
		> I agree with you.
		>
		> In addition to that:
		> The ITU-T experts that reviewed the survivability
draft had the same
		> concerns, and expressed that in their reply liaison
for the review of
		> this draft: https://datatracker.ietf.org/liaison/618/
that was
		> sent in november last year.
		> This concern has not been addressed yet.
		>
		> Regards, Huub.
		>
		>
	=09
		_______________________________________________
		CCAMP mailing list
		CCAMP@ietf.org
		https://www.ietf.org/mailman/listinfo/ccamp
	=09



------_=_NextPart_001_01CACC33.BB3A34AD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000>There are only so many ways to =
provide=20
DP/MP/CP components of each of the 3 networking modes (addressing, =
signalling,=20
routing, OAM, etc)....and there will be a best-of-breed solution for a =
given=20
component at any given time, whatever name we give it.&nbsp; I sometimes =
sense=20
that judgement of technical merit might get compromised by a stronger =
NIH (Not=20
Invented Here) behaviour....esp if the component in question comes from =
another=20
SDO.&nbsp;</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000>Speaking as an operator we have a =
(well=20
publicised internally) desire to have as much sensible re-use of =
components as=20
possible.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000>regards, =
Neil</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; 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> ccamp-bounces@ietf.org=20
  [mailto:ccamp-bounces@ietf.org] <B>On Behalf Of </B>Zhi-Wei=20
  Lin<BR><B>Sent:</B> 25 March 2010 15:42<BR><B>To:</B> Lou =
Berger<BR><B>Cc:</B>=20
  Cecil Byles; mpls@ietf.org; CCAMP@ietf.org; Adrian Farrel;=20
  mpls-tp@ietf.org<BR><B>Subject:</B> Re: [CCAMP] [mpls-tp] [mpls]=20
  =
Term"PSC"indraft-ietf-mpls-tp-linear-protection-01<BR></FONT><BR></DIV>
  <DIV></DIV>Hi,<BR><BR>We have PSC, RSC, APS...how about MPS for =
MPLS-TP=20
  Protection Switching...? I think the acronym (whatever it is) should =
have=20
  "protection switching" in it just so that transport folks know it is =
similar=20
  to what they have used (but different because it's not TDM=20
  based).<BR><BR>Thanks<BR>Zhi<BR><BR>
  <DIV class=3Dgmail_quote>On Thu, Mar 25, 2010 at 11:31 AM, Lou Berger =
<SPAN=20
  dir=3Dltr>&lt;<A =
href=3D"mailto:lberger@labn.net">lberger@labn.net</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Adrian,<BR>&nbsp;=20
    &nbsp; &nbsp; &nbsp;I fully support the high-level point you are =
making,=20
    i.e., the<BR>continued use of a term other than APS in the context =
of TP.=20
    &nbsp;That said,<BR>I'm open to renaming PSC to something that =
doesn't=20
    conflict with<BR>existing MPLS/GMPLS terms. &nbsp;Curtis' proposal =
of RSC is=20
    an example.<BR><BR>Lou<BR><BR>On 3/25/2010 1:32 AM, Adrian Farrel=20
    wrote:<BR>&gt; Huub,<BR>&gt;<BR>&gt; You will note that the comment =
in the=20
    liaison you reference said:<BR>&gt;<BR>&gt; "The acronyms PSC and =
APS are=20
    used, in ITU-T APS is a generic term used in<BR>&gt; different =
methodologies=20
    and does not provide a solution."<BR>&gt;<BR>&gt; This was neither a =

    question nor a request for any change. And it is not<BR>&gt; really =
clear=20
    that it is a "concern".<BR>&gt;<BR>&gt; APS is an abstract protocol=20
    (G.808.1) with specific characteristics and<BR>&gt;=20
    behaviors.<BR>&gt;<BR>&gt; The Survivability Framework deliberately =
does not=20
    prejudge the abstract<BR>&gt; protocol or solution protocol that is=20
    required. Instead, it picked another<BR>&gt; acronym to avoid any=20
    assumptions. This frees the people working in the<BR>&gt; solution =
space to=20
    choose the necessary abstract model for the problems they<BR>&gt; =
need to=20
    solve, and to develop a protocol realisation that meets the =
model.<BR>&gt;=20
    This neither precludes nor forces the use of APS.<BR>&gt;<BR>&gt; If =
you=20
    like, PSC is simply a generalisation that allows freedom of<BR>&gt;=20
    interpretation. Viz.<BR>&gt;<BR>&gt; &nbsp; &nbsp;In some protection =

    switching schemes (such as bidirectional<BR>&gt; &nbsp; =
&nbsp;protection=20
    switching), it is necessary to coordinate the protection<BR>&gt; =
&nbsp;=20
    &nbsp;state between the edges of the recovery domain. &nbsp;An=20
    MPLS-TP<BR>&gt; &nbsp; &nbsp;Protection State Coordination (PSC) =
protocol=20
    may be used as an in-<BR>&gt; &nbsp; &nbsp;band (i.e., data =
plane-based)=20
    control protocol to align both ends of<BR>&gt; &nbsp; &nbsp;the =
protected=20
    domain. &nbsp;Control plane-based mechanism can also be used<BR>&gt; =
&nbsp;=20
    &nbsp;to coordinate the protection states between the edges of =
the<BR>&gt;=20
    &nbsp; &nbsp;protection domain.<BR>&gt;<BR>&gt; In the view of the =
authors,=20
    the term "APS" has become synonymous with<BR>&gt; specific protocol=20
    realisations. For example, in the working copy of G.8131 I<BR>&gt; =
have=20
    infront of me, section 10 describes the "APS Protocol" setting out=20
    byte<BR>&gt; formats and defining messages to go on the wire. While =
we can=20
    interpret "APS<BR>&gt; Protocol" as the technology-specific =
realisation of=20
    "APS", there are<BR>&gt; sufficient overtones that if the =
Survivability=20
    Framework used the term "APS"<BR>&gt; it might be construed as =
support for a=20
    specific protocol realisation. Y.1731<BR>
    <DIV class=3Dim>&gt; defines APS PDUs for Ethernet which gives us =
another=20
    competing<BR>&gt; interpretation of the term. (It is notable that =
the term=20
    "APS Protocol" is<BR>&gt; used in G.870 to mean the abstract =
protocol, which=20
    is subtly different from<BR>&gt; its use in G.8131 and=20
    Y.1731.)<BR>&gt;<BR></DIV>&gt; Surely the working group would prefer =
to=20
    derive the correct protocol<BR>&gt; solution without being =
constrained=20
    except at a functional level?<BR>&gt;<BR>&gt; Adrian<BR>
    <DIV class=3Dim>&gt;<BR>&gt;<BR>&gt; ----- Original Message =
-----<BR>&gt;=20
    From: "Huub van Helvoort" &lt;<A=20
    =
href=3D"mailto:hhelvoort@chello.nl">hhelvoort@chello.nl</A>&gt;<BR>&gt; =
To:=20
    "Cecil Byles" &lt;<A=20
    =
href=3D"mailto:Cecil.Byles@interoute.com">Cecil.Byles@interoute.com</A>&g=
t;<BR>&gt;=20
    Cc: &lt;<A href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A>&gt;; =
&lt;<A=20
    href=3D"mailto:CCAMP@ietf.org">CCAMP@ietf.org</A>&gt;; &lt;<A=20
    href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</A>&gt;<BR></DIV>
    <DIV class=3Dim>&gt; Sent: Wednesday, March 24, 2010 5:14 PM<BR>&gt; =
Subject:=20
    Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"<BR>&gt;=20
    indraft-ietf-mpls-tp-linear-protection-01<BR>&gt;<BR>&gt;<BR></DIV>
    <DIV>
    <DIV></DIV>
    <DIV class=3Dh5>&gt; Hello Cecil,<BR>&gt;<BR>&gt; You=20
    wrote:<BR>&gt;<BR>&gt;&gt; Can I therefore also asked how PSC =
&#8220;Protection=20
    State Coordination&#8221; in the<BR>&gt;&gt; MPLS-TP parlance align =
with ITU-T=20
    808.1 recommendation that "defines the<BR>&gt;&gt; generic =
functional=20
    models, characteristics and processes associated with<BR>&gt;&gt; =
various=20
    linear protection schemes for connection-oriented layer=20
    networks;<BR>&gt;&gt; e.g., Optical Transport Networks (OTN), =
Synchronous=20
    Digital Hierarchy<BR>&gt;&gt; (SDH) networks and Asynchronous =
Transfer Mode=20
    (ATM) networks" and the<BR>&gt;&gt; sections covering &nbsp;Terms =
and=20
    Definitions as well as Abbreviations. &nbsp;IMO<BR>&gt;&gt; all =
transport=20
    engineers and the general telecom community understand =
that<BR>&gt;&gt; 1+1=20
    or 1:1 are either SNCP or APS. Hence why introduce a new TLA=20
    (three<BR>&gt;&gt; letter abbreviation) cover the same function and =
feature=20
    for MPLS-TP. &nbsp;I<BR>&gt;&gt; can only agree that this will only =
cause=20
    confusion.<BR>&gt;<BR>&gt; I agree with you.<BR>&gt;<BR>&gt; In =
addition to=20
    that:<BR>&gt; The ITU-T experts that reviewed the survivability =
draft had=20
    the same<BR>&gt; concerns, and expressed that in their reply liaison =
for the=20
    review of<BR>&gt; this draft: <A=20
    href=3D"https://datatracker.ietf.org/liaison/618/"=20
    target=3D_blank>https://datatracker.ietf.org/liaison/618/</A> that =
was<BR>&gt;=20
    sent in november last year.<BR>&gt; This concern has not been =
addressed=20
    yet.<BR>&gt;<BR>&gt; Regards,=20
    =
Huub.<BR>&gt;<BR>&gt;<BR></DIV></DIV>____________________________________=
___________<BR>CCAMP=20
    mailing list<BR><A =
href=3D"mailto:CCAMP@ietf.org">CCAMP@ietf.org</A><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/ccamp"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/ccamp</A><BR></BLOC=
KQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CACC33.BB3A34AD--

From jdrake@juniper.net  Thu Mar 25 09:38:01 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11ACD3A6A40; Thu, 25 Mar 2010 09:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.469
X-Spam-Level: 
X-Spam-Status: No, score=-6.469 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, 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 XxkdC2z7n0IH; Thu, 25 Mar 2010 09:37:59 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id 7D0993A69C3; Thu, 25 Mar 2010 09:37:59 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKS6uRfbulZJC0k3qRDguN/pFwhxDEPLi3@postini.com; Thu, 25 Mar 2010 09:38:22 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Thu, 25 Mar 2010 09:29:52 -0700
From: John E Drake <jdrake@juniper.net>
To: Shahram Davari <davari@broadcom.com>
Date: Thu, 25 Mar 2010 09:29:38 -0700
Thread-Topic: [mpls] [CCAMP] [mpls-tp] Term"PSC" indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrMOGTqsq2r57iPRQCW9BrZBWModg==
Message-ID: <1A727523-3374-4D6C-A16B-6F45673AC3E9@juniper.net>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com> <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com> <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <4BAA4873.3020706@chello.nl> <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe> <4BAB81B9.3030004@labn.net> <2C2F1EBA8050E74EA81502D5740B4BD68171BEA1DA@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD68171BEA1DA@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "CCAMP@ietf.org" <CCAMP@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [CCAMP] [mpls] [mpls-tp] Term"PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 16:38:01 -0000

Doesn't it also stand for 'packet switch capable'?

Sent from my iPhone

On Mar 25, 2010, at 8:36 AM, "Shahram Davari" <davari@broadcom.com> =20
wrote:

> Hi,
>
> By the way PSC is also used in RFC3270 as acronym for "Per-hop =20
> Scheduling Class"
>
> Thanks,
> Shahram
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =20
> Of Lou Berger
> Sent: Thursday, March 25, 2010 8:31 AM
> To: Adrian Farrel
> Cc: Cecil Byles; mpls@ietf.org; CCAMP@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [CCAMP] [mpls-tp] Term"PSC" indraft-ietf-mpls-tp-=20
> linear-protection-01
>
> Adrian,
>    I fully support the high-level point you are making, i.e., the
> continued use of a term other than APS in the context of TP.  That =20
> said,
> I'm open to renaming PSC to something that doesn't conflict with
> existing MPLS/GMPLS terms.  Curtis' proposal of RSC is an example.
>
> Lou
>
> On 3/25/2010 1:32 AM, Adrian Farrel wrote:
>> Huub,
>>
>> You will note that the comment in the liaison you reference said:
>>
>> "The acronyms PSC and APS are used, in ITU-T APS is a generic term =20
>> used in
>> different methodologies and does not provide a solution."
>>
>> This was neither a question nor a request for any change. And it is =20
>> not
>> really clear that it is a "concern".
>>
>> APS is an abstract protocol (G.808.1) with specific characteristics =20
>> and
>> behaviors.
>>
>> The Survivability Framework deliberately does not prejudge the =20
>> abstract
>> protocol or solution protocol that is required. Instead, it picked =20
>> another
>> acronym to avoid any assumptions. This frees the people working in =20
>> the
>> solution space to choose the necessary abstract model for the =20
>> problems they
>> need to solve, and to develop a protocol realisation that meets the =20
>> model.
>> This neither precludes nor forces the use of APS.
>>
>> If you like, PSC is simply a generalisation that allows freedom of
>> interpretation. Viz.
>>
>>   In some protection switching schemes (such as bidirectional
>>   protection switching), it is necessary to coordinate the protection
>>   state between the edges of the recovery domain.  An MPLS-TP
>>   Protection State Coordination (PSC) protocol may be used as an in-
>>   band (i.e., data plane-based) control protocol to align both ends =20
>> of
>>   the protected domain.  Control plane-based mechanism can also be =20
>> used
>>   to coordinate the protection states between the edges of the
>>   protection domain.
>>
>> In the view of the authors, the term "APS" has become synonymous with
>> specific protocol realisations. For example, in the working copy of =20
>> G.8131 I
>> have infront of me, section 10 describes the "APS Protocol" setting =20
>> out byte
>> formats and defining messages to go on the wire. While we can =20
>> interpret "APS
>> Protocol" as the technology-specific realisation of "APS", there are
>> sufficient overtones that if the Survivability Framework used the =20
>> term "APS"
>> it might be construed as support for a specific protocol =20
>> realisation. Y.1731
>> defines APS PDUs for Ethernet which gives us another competing
>> interpretation of the term. (It is notable that the term "APS =20
>> Protocol" is
>> used in G.870 to mean the abstract protocol, which is subtly =20
>> different from
>> its use in G.8131 and Y.1731.)
>>
>> Surely the working group would prefer to derive the correct protocol
>> solution without being constrained except at a functional level?
>>
>> Adrian
>>
>>
>> ----- Original Message -----
>> From: "Huub van Helvoort" <hhelvoort@chello.nl>
>> To: "Cecil Byles" <Cecil.Byles@interoute.com>
>> Cc: <mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
>> Sent: Wednesday, March 24, 2010 5:14 PM
>> Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"
>> indraft-ietf-mpls-tp-linear-protection-01
>>
>>
>> Hello Cecil,
>>
>> You wrote:
>>
>>> Can I therefore also asked how PSC "Protection State Coordination" =20
>>> in the
>>> MPLS-TP parlance align with ITU-T 808.1 recommendation that =20
>>> "defines the
>>> generic functional models, characteristics and processes =20
>>> associated with
>>> various linear protection schemes for connection-oriented layer =20
>>> networks;
>>> e.g., Optical Transport Networks (OTN), Synchronous Digital =20
>>> Hierarchy
>>> (SDH) networks and Asynchronous Transfer Mode (ATM) networks" and =20
>>> the
>>> sections covering  Terms and Definitions as well as =20
>>> Abbreviations.  IMO
>>> all transport engineers and the general telecom community =20
>>> understand that
>>> 1+1 or 1:1 are either SNCP or APS. Hence why introduce a new TLA =20
>>> (three
>>> letter abbreviation) cover the same function and feature for MPLS-=20
>>> TP.  I
>>> can only agree that this will only cause confusion.
>>
>> I agree with you.
>>
>> In addition to that:
>> The ITU-T experts that reviewed the survivability draft had the same
>> concerns, and expressed that in their reply liaison for the review of
>> this draft: https://datatracker.ietf.org/liaison/618/ that was
>> sent in november last year.
>> This concern has not been addressed yet.
>>
>> Regards, Huub.
>>
>>
> _______________________________________________
> 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 Adrian.Farrel@huawei.com  Thu Mar 25 09:56:25 2010
Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8922D3A6B6B; Thu, 25 Mar 2010 09:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.858
X-Spam-Level: 
X-Spam-Status: No, score=0.858 tagged_above=-999 required=5 tests=[AWL=0.467,  BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDfkM1iR4Grv; Thu, 25 Mar 2010 09:56:24 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id 4E2893A63C9; Thu, 25 Mar 2010 09:56:12 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZU008AAKEA8N@usaga03-in.huawei.com>; Thu, 25 Mar 2010 11:56:34 -0500 (CDT)
Received: from your029b8cecfe (dhcp-wireless-open-abg-25-211.meeting.ietf.org [130.129.25.211]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KZU008Q1KE9X5@usaga03-in.huawei.com>; Thu, 25 Mar 2010 11:56:34 -0500 (CDT)
Date: Thu, 25 Mar 2010 16:55:24 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: tochio@labs.fujitsu.com
Message-id: <6AB422D13EF0456FB691F7681E5F7FAA@your029b8cecfe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; format=flowed; charset=ISO-2022-JP; reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com> <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com> <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <4BAA4873.3020706@chello.nl> <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe> <4BAB21F5.3020706@jp.fujitsu.com>
Cc: Cecil Byles <Cecil.Byles@interoute.com>, mpls@ietf.org, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] [mpls-tp]	Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <Adrian.Farrel@huawei.com>
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 16:56:25 -0000

Oh, but I thought someone said APS was an abstract protocol.

Is it the case that there are multiple documents that define PDUs and data 
fields for APS?

Thanks,
Adrian
----- Original Message ----- 
From: "Yuji Tochio" <tochio@jp.fujitsu.com>
To: "Adrian Farrel" <Adrian.Farrel@huawei.com>
Cc: <hhelvoort@chello.nl>; "Cecil Byles" <Cecil.Byles@interoute.com>; 
<mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
Sent: Thursday, March 25, 2010 8:42 AM
Subject: Re: [mpls] [CCAMP] [mpls-tp] 
Term"PSC"indraft-ietf-mpls-tp-linear-protection-01


> Hi Adrian,
>
> Very minnor comment, but need to address for clear understanding:
>
> Adrian Farrel wrote:
>> Y.1731 defines APS PDUs for Ethernet which gives us another competing
>> interpretation of the term. (It is notable that the term "APS
>> Protocol" is used in G.870 to mean the abstract protocol, which is
>> subtly different from its use in G.8131 and Y.1731.)
>>
>
> Y.1731 does not fully define APS PDU, only defines the opcode and common
> OAM PDU. APS PDU is defined in G.8031 and G.8032 (ERP)
> Please read 9.10.1 in Y.1731
>
> Regards,
> Yuji
>
> 


From adrian@olddog.co.uk  Thu Mar 25 09:59:46 2010
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1AD53A6914; Thu, 25 Mar 2010 09:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.818
X-Spam-Level: 
X-Spam-Status: No, score=-1.818 tagged_above=-999 required=5 tests=[AWL=1.650,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e6kNWWoZSUgz; Thu, 25 Mar 2010 09:59:45 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id 0BC423A68D7; Thu, 25 Mar 2010 09:59:44 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id o2PGxiKo029635;  Thu, 25 Mar 2010 16:59:50 GMT
Received: from your029b8cecfe (dhcp-wireless-open-abg-25-211.meeting.ietf.org [130.129.25.211]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id o2PGxfGh029613;  Thu, 25 Mar 2010 16:59:42 GMT
Message-ID: <D4435E85CD7A4B18A87A78B88BCF0B3B@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Zhi-Wei Lin" <zhiwlin@gmail.com>, <curtis@occnc.com>
References: <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com><201003250609.o2P69T7l062460@harbor.orleans.occnc.com> <67ec4be61003250738v272809bcwd339d5771566f390@mail.gmail.com>
Date: Thu, 25 Mar 2010 16:56:54 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: Cecil Byles <Cecil.Byles@interoute.com>, mpls@ietf.org, CCAMP@ietf.org, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] [mpls-tp] Term "PSC"indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 16:59:46 -0000

Hi,

Welcome your input on this as an operator.

Need to understand whether "MOP" covers the PDU formats or refers to the 
actions that an operator must take, and the states that are reported by the 
network?

Thanks,
Adrian
----- Original Message ----- 
From: "Zhi-Wei Lin" <zhiwlin@gmail.com>
To: <curtis@occnc.com>
Cc: "Cecil Byles" <Cecil.Byles@interoute.com>; <mpls@ietf.org>; 
<CCAMP@ietf.org>; "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>; 
<mpls-tp@ietf.org>
Sent: Thursday, March 25, 2010 2:38 PM
Subject: Re: [mpls] [CCAMP] [mpls-tp] Term 
"PSC"indraft-ietf-mpls-tp-linear-protection-01


> Hi,
>
> I like to give my perspective. As a small network company (but one of the
> largest transit agencies), we have a small operating staff split into two
> groups: one that handles traditional data network (Ethernet, IP), and one
> that handles transport network (SONET, WDM).
>
> We are targeting the transport network operating staff to maintain and
> operate the MPLS-TP network. As such, anything that will help to reduce 
> the
> learning curve (less training), simplify operating, and make the MOP as
> consistent as possible between SONET and MPLS-TP would be hugely 
> beneficial.
>
> Obviously there will be some differences since MPLS-TP is a packet-based
> transport network, but the standards groups (I don't really care for
> politics of IETF and ITU) should strive to make these differences easy to
> learn.
>
> Thanks
> Zhi
>
>
> On Thu, Mar 25, 2010 at 2:09 AM, Curtis Villamizar <curtis@occnc.com> 
> wrote:
>
>>
>> In message 
>> <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>
>> "Cecil Byles" writes:
>> >
>> >
>> > Hi,
>> > Can I therefore also asked how PSC "Protection State Coordination" in
>> > the MPLS-TP parlance align with ITU-T 808.1 recommendation that 
>> > "defines
>> > the generic functional models, characteristics and processes associated
>> > with various linear protection schemes for connection-oriented layer
>> > networks; e.g., Optical Transport Networks (OTN), Synchronous Digital
>> > Hierarchy (SDH) networks and Asynchronous Transfer Mode (ATM) networks"
>> > and the sections covering  Terms and Definitions as well as
>> > Abbreviations.  IMO all transport engineers and the general telecom
>> > community understand that 1+1 or 1:1 are either SNCP or APS. Hence why
>> > introduce a new TLA (three letter abbreviation) cover the same function
>> > and feature for MPLS-TP.  I can only agree that this will only cause
>> > confusion.
>> >
>> > Cecil Byles
>>
>>
>> Though this is joint work, this is the IETF not the ITU.  We should
>> use ITU terms where appropriate but where there is a conflict such as
>> this we need to pick another term and another TLA.  If the ITU wants
>> to update 808.1 at some later date that is up to the ITU.  In the mean
>> time we can use another term and point out the mapping.
>>
>> Curtis
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>


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


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


From zhiwlin@gmail.com  Thu Mar 25 10:14:15 2010
Return-Path: <zhiwlin@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC4C53A6BF0; Thu, 25 Mar 2010 10:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.572
X-Spam-Level: 
X-Spam-Status: No, score=-0.572 tagged_above=-999 required=5 tests=[AWL=0.896,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 hwqrK8HWXyw1; Thu, 25 Mar 2010 10:14:14 -0700 (PDT)
Received: from mail-qy0-f196.google.com (mail-qy0-f196.google.com [209.85.221.196]) by core3.amsl.com (Postfix) with ESMTP id 472B53A6E15; Thu, 25 Mar 2010 10:12:14 -0700 (PDT)
Received: by qyk34 with SMTP id 34so2849185qyk.22 for <multiple recipients>; Thu, 25 Mar 2010 10:12:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=ERpPWH57TLeijUxeyxeORNzzEQcvxJDAVsJRP3rWQuk=; b=BsCYBvg/y/vjHUBPeEa4/qFIGuUyDWbhOTN9u0+DuzVbpDf3NLojtBCm6SSGB9cNw8 IG6mDlg+vAiCVPpkRgeqMULrot5XhX3DTV4Ho2cMQBW2HlU9vF/AnzlMwP7+P3+zgSGD PgsyMAGQS9JwPP4Y7BYqKd3OPfEFIRaxVK6Ds=
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=K6VQLPiQPArjCfxQJwUFn/ZKW5mO9RzwhiNeFJds/JCPUGSxhR6QUHUlW14KjnxOfm TGbo1/NNhQApHO0r0LiTAJvaLtRODRdx+Drm6FRpnv6dMO/ripkzN7Lodf0yJCqG2I3e RHWOr1GQgqo0ljDB7n4g28gzS6h8uum1eHsOU=
MIME-Version: 1.0
Received: by 10.229.222.76 with SMTP id if12mr2382824qcb.17.1269537150932;  Thu, 25 Mar 2010 10:12:30 -0700 (PDT)
In-Reply-To: <6AB422D13EF0456FB691F7681E5F7FAA@your029b8cecfe>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com> <8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <8bf39341003240227i7fe1e00en9edbe2269b3953cf@mail.gmail.com> <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <4BAA4873.3020706@chello.nl> <B9565B7FB5D940D2AE9104617758C6ED@your029b8cecfe> <4BAB21F5.3020706@jp.fujitsu.com> <6AB422D13EF0456FB691F7681E5F7FAA@your029b8cecfe>
Date: Thu, 25 Mar 2010 13:12:30 -0400
Message-ID: <67ec4be61003251012kd3816dfl28c51ea28ee0f1a5@mail.gmail.com>
From: Zhi-Wei Lin <zhiwlin@gmail.com>
To: Adrian Farrel <Adrian.Farrel@huawei.com>
Content-Type: multipart/alternative; boundary=0016361e7f34e9454c0482a3263d
Cc: Cecil Byles <Cecil.Byles@interoute.com>, mpls@ietf.org, CCAMP@ietf.org, tochio@labs.fujitsu.com, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] [mpls-tp] Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 17:14:15 -0000

--0016361e7f34e9454c0482a3263d
Content-Type: text/plain; charset=UTF-8

Hi,

I found the following documents to contain APS:

ITU: G.841, G.870, G.8031
Also used obviously in U.S. SONET standards and Telcordia GRs.

As mentioned before, from operating staff point of view, using the term APS
would have a warm and fuzzy feeling of familiarity (at least in our company,
MPLS-TP will be maintained by the transport group, not the data group). APS
protocol definition and operation obviously will be little bit different for
MPLS-TP, but that's the case in general for the TDM world as well. You also
have modifiers for APS, such as 1:1 linear APS, ring APS, Ethernet APS.

So here we have MPLS-TP APS...

Thanks
Zhi


On Thu, Mar 25, 2010 at 12:55 PM, Adrian Farrel <Adrian.Farrel@huawei.com>wrote:

> Oh, but I thought someone said APS was an abstract protocol.
>
> Is it the case that there are multiple documents that define PDUs and data
> fields for APS?
>
> Thanks,
> Adrian
> ----- Original Message ----- From: "Yuji Tochio" <tochio@jp.fujitsu.com>
> To: "Adrian Farrel" <Adrian.Farrel@huawei.com>
> Cc: <hhelvoort@chello.nl>; "Cecil Byles" <Cecil.Byles@interoute.com>; <
> mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
> Sent: Thursday, March 25, 2010 8:42 AM
> Subject: Re: [mpls] [CCAMP] [mpls-tp]
> Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
>
>
>
>  Hi Adrian,
>>
>> Very minnor comment, but need to address for clear understanding:
>>
>> Adrian Farrel wrote:
>>
>>> Y.1731 defines APS PDUs for Ethernet which gives us another competing
>>> interpretation of the term. (It is notable that the term "APS
>>> Protocol" is used in G.870 to mean the abstract protocol, which is
>>> subtly different from its use in G.8131 and Y.1731.)
>>>
>>>
>> Y.1731 does not fully define APS PDU, only defines the opcode and common
>> OAM PDU. APS PDU is defined in G.8031 and G.8032 (ERP)
>> Please read 9.10.1 in Y.1731
>>
>> Regards,
>> Yuji
>>
>>
>>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>

--0016361e7f34e9454c0482a3263d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>I found the following documents to contain APS:<br><br>ITU: G.84=
1, G.870, G.8031<br>Also used obviously in U.S. SONET standards and Telcord=
ia GRs.<br><br>As mentioned before, from operating staff point of view, usi=
ng the term APS would have a warm and fuzzy feeling of familiarity (at leas=
t in our company, MPLS-TP will be maintained by the transport group, not th=
e data group). APS protocol definition and operation obviously will be litt=
le bit different for MPLS-TP, but that&#39;s the case in general for the TD=
M world as well. You also have modifiers for APS, such as 1:1 linear APS, r=
ing APS, Ethernet APS.<br>
<br>So here we have MPLS-TP APS...<br><br>Thanks<br>Zhi<br><br><br><div cla=
ss=3D"gmail_quote">On Thu, Mar 25, 2010 at 12:55 PM, Adrian Farrel <span di=
r=3D"ltr">&lt;<a href=3D"mailto:Adrian.Farrel@huawei.com">Adrian.Farrel@hua=
wei.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;">Oh, but I thought=
 someone said APS was an abstract protocol.<br>
<br>
Is it the case that there are multiple documents that define PDUs and data =
fields for APS?<br>
<br>
Thanks,<br>
Adrian<br>
----- Original Message ----- From: &quot;Yuji Tochio&quot; &lt;<a href=3D"m=
ailto:tochio@jp.fujitsu.com" target=3D"_blank">tochio@jp.fujitsu.com</a>&gt=
;<br>
To: &quot;Adrian Farrel&quot; &lt;<a href=3D"mailto:Adrian.Farrel@huawei.co=
m" target=3D"_blank">Adrian.Farrel@huawei.com</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:hhelvoort@chello.nl" target=3D"_blank">hhelvoort@=
chello.nl</a>&gt;; &quot;Cecil Byles&quot; &lt;<a href=3D"mailto:Cecil.Byle=
s@interoute.com" target=3D"_blank">Cecil.Byles@interoute.com</a>&gt;; &lt;<=
a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>&gt;; &l=
t;<a href=3D"mailto:CCAMP@ietf.org" target=3D"_blank">CCAMP@ietf.org</a>&gt=
;; &lt;<a href=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.o=
rg</a>&gt;<br>

Sent: Thursday, March 25, 2010 8:42 AM<br>
Subject: Re: [mpls] [CCAMP] [mpls-tp] Term&quot;PSC&quot;indraft-ietf-mpls-=
tp-linear-protection-01<div><div></div><div class=3D"h5"><br>
<br>
<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;">
Hi Adrian,<br>
<br>
Very minnor comment, but need to address for clear understanding:<br>
<br>
Adrian Farrel 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;">
Y.1731 defines APS PDUs for Ethernet which gives us another competing<br>
interpretation of the term. (It is notable that the term &quot;APS<br>
Protocol&quot; is used in G.870 to mean the abstract protocol, which is<br>
subtly different from its use in G.8131 and Y.1731.)<br>
<br>
</blockquote>
<br>
Y.1731 does not fully define APS PDU, only defines the opcode and common<br=
>
OAM PDU. APS PDU is defined in G.8031 and G.8032 (ERP)<br>
Please read 9.10.1 in Y.1731<br>
<br>
Regards,<br>
Yuji<br>
<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
CCAMP mailing list<br>
<a href=3D"mailto:CCAMP@ietf.org" target=3D"_blank">CCAMP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ccamp" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/ccamp</a><br>
</div></div></blockquote></div><br>

--0016361e7f34e9454c0482a3263d--

From zhiwlin@gmail.com  Thu Mar 25 10:22:10 2010
Return-Path: <zhiwlin@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A5C03A6EA4; Thu, 25 Mar 2010 10:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.005
X-Spam-Level: 
X-Spam-Status: No, score=-1.005 tagged_above=-999 required=5 tests=[AWL=2.463,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, 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 VHNWjCMGfkoO; Thu, 25 Mar 2010 10:22:08 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by core3.amsl.com (Postfix) with ESMTP id E2D3F3A6E63; Thu, 25 Mar 2010 10:15:25 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 5so1501852qwi.31 for <multiple recipients>; Thu, 25 Mar 2010 10:15:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=G0OurzPIjmSc9ef+gSEu7//4cYp14QEf3B11B+IZ8gQ=; b=ZhLFP3Id6FdlC5o4xsN5QhYNoPMqdQFeRbl6gw2tdnLO25Sg44lSf2yr/kMOSKLimX kdIeltRa+LBJvPsqdh5Qkp5EODwJ9wZSu+pmVyfkSfG+k9va/O9CesvZQGt4QPz9zNUT RO1KPkGy+km7XBKRgJnVJCvLu5gscBE1NgACY=
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=GyTMfyZ/QCf+GJ2tZJ9bDeEC4zS8ny7apGPzExZw+OEeQOaryWw3M87KWF6BYnxd7K Pl6LKrLJqgJ09XHzsJRJlOytNDw9Cyx1MA2MNxVUImtgvJhFW8EUNpUAkKZR7lepA6rG AqDsqcgsFhUbn5/0OiirF363iHTcyoGQkEeG8=
MIME-Version: 1.0
Received: by 10.229.97.147 with SMTP id l19mr944356qcn.24.1269537344319; Thu,  25 Mar 2010 10:15:44 -0700 (PDT)
In-Reply-To: <D4435E85CD7A4B18A87A78B88BCF0B3B@your029b8cecfe>
References: <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <201003250609.o2P69T7l062460@harbor.orleans.occnc.com> <67ec4be61003250738v272809bcwd339d5771566f390@mail.gmail.com> <D4435E85CD7A4B18A87A78B88BCF0B3B@your029b8cecfe>
Date: Thu, 25 Mar 2010 13:15:44 -0400
Message-ID: <67ec4be61003251015m68923d32g7c44da02aea6002a@mail.gmail.com>
From: Zhi-Wei Lin <zhiwlin@gmail.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=0016364ef3266ff3e80482a332fb
Cc: mpls@ietf.org, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, Cecil Byles <Cecil.Byles@interoute.com>, CCAMP@ietf.org, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] [mpls-tp] Term "PSC"indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 17:22:10 -0000

--0016364ef3266ff3e80482a332fb
Content-Type: text/plain; charset=UTF-8

Hi Adrian,

Sorry. MOP in our company refers to method of procedure, basically the
operating model and process for operation and maintenance of the network.

We do realize our MOP would need to be modified to handle MPLS-TP, but
anything that can be done to reduce the effort would be greatly appreciated.

Thanks
Zhi


On Thu, Mar 25, 2010 at 12:56 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi,
>
> Welcome your input on this as an operator.
>
> Need to understand whether "MOP" covers the PDU formats or refers to the
> actions that an operator must take, and the states that are reported by the
> network?
>
> Thanks,
> Adrian
> ----- Original Message ----- From: "Zhi-Wei Lin" <zhiwlin@gmail.com>
> To: <curtis@occnc.com>
> Cc: "Cecil Byles" <Cecil.Byles@interoute.com>; <mpls@ietf.org>; <
> CCAMP@ietf.org>; "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>;
> <mpls-tp@ietf.org>
> Sent: Thursday, March 25, 2010 2:38 PM
> Subject: Re: [mpls] [CCAMP] [mpls-tp] Term
> "PSC"indraft-ietf-mpls-tp-linear-protection-01
>
>
>
>  Hi,
>>
>> I like to give my perspective. As a small network company (but one of the
>> largest transit agencies), we have a small operating staff split into two
>> groups: one that handles traditional data network (Ethernet, IP), and one
>> that handles transport network (SONET, WDM).
>>
>> We are targeting the transport network operating staff to maintain and
>> operate the MPLS-TP network. As such, anything that will help to reduce
>> the
>> learning curve (less training), simplify operating, and make the MOP as
>> consistent as possible between SONET and MPLS-TP would be hugely
>> beneficial.
>>
>> Obviously there will be some differences since MPLS-TP is a packet-based
>> transport network, but the standards groups (I don't really care for
>> politics of IETF and ITU) should strive to make these differences easy to
>> learn.
>>
>> Thanks
>> Zhi
>>
>>
>> On Thu, Mar 25, 2010 at 2:09 AM, Curtis Villamizar <curtis@occnc.com>
>> wrote:
>>
>>
>>> In message <
>>> 4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>
>>> "Cecil Byles" writes:
>>> >
>>> >
>>> > Hi,
>>> > Can I therefore also asked how PSC "Protection State Coordination" in
>>> > the MPLS-TP parlance align with ITU-T 808.1 recommendation that >
>>> "defines
>>> > the generic functional models, characteristics and processes associated
>>> > with various linear protection schemes for connection-oriented layer
>>> > networks; e.g., Optical Transport Networks (OTN), Synchronous Digital
>>> > Hierarchy (SDH) networks and Asynchronous Transfer Mode (ATM) networks"
>>> > and the sections covering  Terms and Definitions as well as
>>> > Abbreviations.  IMO all transport engineers and the general telecom
>>> > community understand that 1+1 or 1:1 are either SNCP or APS. Hence why
>>> > introduce a new TLA (three letter abbreviation) cover the same function
>>> > and feature for MPLS-TP.  I can only agree that this will only cause
>>> > confusion.
>>> >
>>> > Cecil Byles
>>>
>>>
>>> Though this is joint work, this is the IETF not the ITU.  We should
>>> use ITU terms where appropriate but where there is a conflict such as
>>> this we need to pick another term and another TLA.  If the ITU wants
>>> to update 808.1 at some later date that is up to the ITU.  In the mean
>>> time we can use another term and point out the mapping.
>>>
>>> Curtis
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>>
>>>
>>
>
>
> --------------------------------------------------------------------------------
>
>
>
>  _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>

--0016364ef3266ff3e80482a332fb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Adrian,<br><br>Sorry. MOP in our company refers to method of procedure, =
basically the operating model and process for operation and maintenance of =
the network.<br><br>We do realize our MOP would need to be modified to hand=
le MPLS-TP, but anything that can be done to reduce the effort would be gre=
atly appreciated.<br>
<br>Thanks<br>Zhi<br><br><br><div class=3D"gmail_quote">On Thu, Mar 25, 201=
0 at 12:56 PM, Adrian Farrel <span dir=3D"ltr">&lt;<a href=3D"mailto:adrian=
@olddog.co.uk">adrian@olddog.co.uk</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px sol=
id rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<br>
Welcome your input on this as an operator.<br>
<br>
Need to understand whether &quot;MOP&quot; covers the PDU formats or refers=
 to the actions that an operator must take, and the states that are reporte=
d by the network?<br>
<br>
Thanks,<br>
Adrian<br>
----- Original Message ----- From: &quot;Zhi-Wei Lin&quot; &lt;<a href=3D"m=
ailto:zhiwlin@gmail.com" target=3D"_blank">zhiwlin@gmail.com</a>&gt;<br>
To: &lt;<a href=3D"mailto:curtis@occnc.com" target=3D"_blank">curtis@occnc.=
com</a>&gt;<br>
Cc: &quot;Cecil Byles&quot; &lt;<a href=3D"mailto:Cecil.Byles@interoute.com=
" target=3D"_blank">Cecil.Byles@interoute.com</a>&gt;; &lt;<a href=3D"mailt=
o:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>&gt;; &lt;<a href=3D"ma=
ilto:CCAMP@ietf.org" target=3D"_blank">CCAMP@ietf.org</a>&gt;; &quot;Alexan=
der Vainshtein&quot; &lt;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com=
" target=3D"_blank">Alexander.Vainshtein@ecitele.com</a>&gt;; &lt;<a href=
=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.org</a>&gt;<br>

Sent: Thursday, March 25, 2010 2:38 PM<br>
Subject: Re: [mpls] [CCAMP] [mpls-tp] Term &quot;PSC&quot;indraft-ietf-mpls=
-tp-linear-protection-01<div><div></div><div class=3D"h5"><br>
<br>
<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;">
Hi,<br>
<br>
I like to give my perspective. As a small network company (but one of the<b=
r>
largest transit agencies), we have a small operating staff split into two<b=
r>
groups: one that handles traditional data network (Ethernet, IP), and one<b=
r>
that handles transport network (SONET, WDM).<br>
<br>
We are targeting the transport network operating staff to maintain and<br>
operate the MPLS-TP network. As such, anything that will help to reduce the=
<br>
learning curve (less training), simplify operating, and make the MOP as<br>
consistent as possible between SONET and MPLS-TP would be hugely beneficial=
.<br>
<br>
Obviously there will be some differences since MPLS-TP is a packet-based<br=
>
transport network, but the standards groups (I don&#39;t really care for<br=
>
politics of IETF and ITU) should strive to make these differences easy to<b=
r>
learn.<br>
<br>
Thanks<br>
Zhi<br>
<br>
<br>
On Thu, Mar 25, 2010 at 2:09 AM, Curtis Villamizar &lt;<a href=3D"mailto:cu=
rtis@occnc.com" target=3D"_blank">curtis@occnc.com</a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
In message &lt;<a href=3D"mailto:4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@P=
REX22.interoute.com" target=3D"_blank">4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2=
FE59@PREX22.interoute.com</a>&gt;<br>
&quot;Cecil Byles&quot; writes:<br>
&gt;<br>
&gt;<br>
&gt; Hi,<br>
&gt; Can I therefore also asked how PSC &quot;Protection State Coordination=
&quot; in<br>
&gt; the MPLS-TP parlance align with ITU-T 808.1 recommendation that &gt; &=
quot;defines<br>
&gt; the generic functional models, characteristics and processes associate=
d<br>
&gt; with various linear protection schemes for connection-oriented layer<b=
r>
&gt; networks; e.g., Optical Transport Networks (OTN), Synchronous Digital<=
br>
&gt; Hierarchy (SDH) networks and Asynchronous Transfer Mode (ATM) networks=
&quot;<br>
&gt; and the sections covering =C2=A0Terms and Definitions as well as<br>
&gt; Abbreviations. =C2=A0IMO all transport engineers and the general telec=
om<br>
&gt; community understand that 1+1 or 1:1 are either SNCP or APS. Hence why=
<br>
&gt; introduce a new TLA (three letter abbreviation) cover the same functio=
n<br>
&gt; and feature for MPLS-TP. =C2=A0I can only agree that this will only ca=
use<br>
&gt; confusion.<br>
&gt;<br>
&gt; Cecil Byles<br>
<br>
<br>
Though this is joint work, this is the IETF not the ITU. =C2=A0We should<br=
>
use ITU terms where appropriate but where there is a conflict such as<br>
this we need to pick another term and another TLA. =C2=A0If the ITU wants<b=
r>
to update 808.1 at some later date that is up to the ITU. =C2=A0In the mean=
<br>
time we can use another term and point out the mapping.<br>
<br>
Curtis<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>
</blockquote>
<br>
</blockquote>
<br>
<br></div></div>
---------------------------------------------------------------------------=
-----<div><div></div><div class=3D"h5"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
_______________________________________________<br>
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>
</blockquote>
<br>
</div></div></blockquote></div><br>

--0016364ef3266ff3e80482a332fb--

From Cecil.Byles@interoute.com  Thu Mar 25 11:01:46 2010
Return-Path: <Cecil.Byles@interoute.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBE393A6C82; Thu, 25 Mar 2010 11:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.668
X-Spam-Level: 
X-Spam-Status: No, score=-1.668 tagged_above=-999 required=5 tests=[AWL=1.800,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, 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 N5Utm9lUfuCF; Thu, 25 Mar 2010 11:01:45 -0700 (PDT)
Received: from mail1.interoute.com (mail1.interoute.com [89.202.186.60]) by core3.amsl.com (Postfix) with ESMTP id 75BA73A694D; Thu, 25 Mar 2010 11:01:24 -0700 (PDT)
Received: from ukex01.interoute.com ([172.31.149.70]) by mail1.interoute.com with Microsoft SMTPSVC(7.0.6001.18000);  Thu, 25 Mar 2010 19:01:46 +0100
Received: from PREX22.interoute.com ([172.31.149.20]) by ukex01.interoute.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 25 Mar 2010 19:01:42 +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_01CACC45.3952A22A"
Date: Thu, 25 Mar 2010 19:01:40 +0100
Message-ID: <4B2E9510FA2E7E4EB223A7F2F9EE3A9503AB0595@PREX22.interoute.com>
In-Reply-To: <67ec4be61003251015m68923d32g7c44da02aea6002a@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [CCAMP] [mpls-tp] Term "PSC"indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrMPtDbuxGzbG96SfaiIz4iG3bAkAAAFEIA
References: <4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com> <201003250609.o2P69T7l062460@harbor.orleans.occnc.com> <67ec4be61003250738v272809bcwd339d5771566f390@mail.gmail.com> <D4435E85CD7A4B18A87A78B88BCF0B3B@your029b8cecfe> <67ec4be61003251015m68923d32g7c44da02aea6002a@mail.gmail.com>
From: "Cecil Byles" <Cecil.Byles@interoute.com>
To: "Zhi-Wei Lin" <zhiwlin@gmail.com>, "Adrian Farrel" <adrian@olddog.co.uk>
X-OriginalArrivalTime: 25 Mar 2010 18:01:42.0131 (UTC) FILETIME=[39668430:01CACC45]
Cc: mpls@ietf.org, CCAMP@ietf.org, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] [mpls-tp] Term "PSC"indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 18:01:46 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CACC45.3952A22A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Adrian,
=20
As stated in all the various e-mails associated with this issue, the
acronym APS (also in our company) relates to all manner of automated
protections switching (no manual interaction) schemes applied to either
SDH, OTN or Ethernet and in the future MPLS-TP ( which is also aim at a
transport team doing the O&M). However the semantics of how APS is
applied and implemented in SDH, OTN, Ethernet and MPLS-TP can all be
different or similar, but the basic principle is that there is a work
and protect path that can function as either Uni-directional or
bi-directional protection switch . Thus I believe that the PSC protocol
is just one of the methodology for implementing MPLS-TP APS (automatic
protection switching) be that linear or ring protection.=20
=20
MOP also means "Method of Procedure in our company as well with the same
understand as stated by Zhi below.=20
=20
regards
Cecil

________________________________

From: Zhi-Wei Lin [mailto:zhiwlin@gmail.com]=20
Sent: 25 March 2010 17:16
To: Adrian Farrel
Cc: curtis@occnc.com; Cecil Byles; mpls@ietf.org; CCAMP@ietf.org;
Alexander Vainshtein; mpls-tp@ietf.org
Subject: Re: [mpls] [CCAMP] [mpls-tp] Term
"PSC"indraft-ietf-mpls-tp-linear-protection-01


Hi Adrian,

Sorry. MOP in our company refers to method of procedure, basically the
operating model and process for operation and maintenance of the
network.

We do realize our MOP would need to be modified to handle MPLS-TP, but
anything that can be done to reduce the effort would be greatly
appreciated.

Thanks
Zhi



On Thu, Mar 25, 2010 at 12:56 PM, Adrian Farrel <adrian@olddog.co.uk>
wrote:


	Hi,
=09
	Welcome your input on this as an operator.
=09
	Need to understand whether "MOP" covers the PDU formats or
refers to the actions that an operator must take, and the states that
are reported by the network?
=09
	Thanks,
	Adrian
	----- Original Message ----- From: "Zhi-Wei Lin"
<zhiwlin@gmail.com>
	To: <curtis@occnc.com>
	Cc: "Cecil Byles" <Cecil.Byles@interoute.com>; <mpls@ietf.org>;
<CCAMP@ietf.org>; "Alexander Vainshtein"
<Alexander.Vainshtein@ecitele.com>; <mpls-tp@ietf.org>
	Sent: Thursday, March 25, 2010 2:38 PM
	Subject: Re: [mpls] [CCAMP] [mpls-tp] Term
"PSC"indraft-ietf-mpls-tp-linear-protection-01=20




		Hi,
	=09
		I like to give my perspective. As a small network
company (but one of the
		largest transit agencies), we have a small operating
staff split into two
		groups: one that handles traditional data network
(Ethernet, IP), and one
		that handles transport network (SONET, WDM).
	=09
		We are targeting the transport network operating staff
to maintain and
		operate the MPLS-TP network. As such, anything that will
help to reduce the
		learning curve (less training), simplify operating, and
make the MOP as
		consistent as possible between SONET and MPLS-TP would
be hugely beneficial.
	=09
		Obviously there will be some differences since MPLS-TP
is a packet-based
		transport network, but the standards groups (I don't
really care for
		politics of IETF and ITU) should strive to make these
differences easy to
		learn.
	=09
		Thanks
		Zhi
	=09
	=09
		On Thu, Mar 25, 2010 at 2:09 AM, Curtis Villamizar
<curtis@occnc.com> wrote:
	=09
	=09


			In message
<4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.com>
			"Cecil Byles" writes:
			>
			>
			> Hi,
			> Can I therefore also asked how PSC "Protection
State Coordination" in
			> the MPLS-TP parlance align with ITU-T 808.1
recommendation that > "defines
			> the generic functional models, characteristics
and processes associated
			> with various linear protection schemes for
connection-oriented layer
			> networks; e.g., Optical Transport Networks
(OTN), Synchronous Digital
			> Hierarchy (SDH) networks and Asynchronous
Transfer Mode (ATM) networks"
			> and the sections covering  Terms and
Definitions as well as
			> Abbreviations.  IMO all transport engineers
and the general telecom
			> community understand that 1+1 or 1:1 are
either SNCP or APS. Hence why
			> introduce a new TLA (three letter
abbreviation) cover the same function
			> and feature for MPLS-TP.  I can only agree
that this will only cause
			> confusion.
			>
			> Cecil Byles
		=09
		=09
			Though this is joint work, this is the IETF not
the ITU.  We should
			use ITU terms where appropriate but where there
is a conflict such as
			this we need to pick another term and another
TLA.  If the ITU wants
			to update 808.1 at some later date that is up to
the ITU.  In the mean
			time we can use another term and point out the
mapping.
		=09
			Curtis
			_______________________________________________
			mpls mailing list
			mpls@ietf.org
			https://www.ietf.org/mailman/listinfo/mpls
		=09
		=09




=09
------------------------------------------------------------------------
--------=20




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




------_=_NextPart_001_01CACC45.3952A22A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16981" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D719051817-25032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Adrian,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D719051817-25032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D719051817-25032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>As stated in all the various =
e-mails&nbsp;associated with=20
this issue,&nbsp;the&nbsp;acronym APS&nbsp;(also in our =
company)&nbsp;relates to=20
all manner of automated protections switching (no manual interaction) =
schemes=20
applied to&nbsp;either SDH, OTN or Ethernet and in the future MPLS-TP ( =
which is=20
also aim at a transport team doing the O&amp;M).&nbsp;However the =
semantics of=20
how APS is applied and implemented in SDH, OTN, Ethernet and MPLS-TP can =
all be=20
different or similar, but the basic principle is that there is a work =
and=20
protect path that can function as either Uni-directional or =
bi-directional=20
protection switch .&nbsp;Thus&nbsp;I believe that&nbsp;the =
PSC&nbsp;protocol is=20
just one of the methodology for implementing MPLS-TP&nbsp;APS (automatic =

protection switching)&nbsp;be that linear or ring protection.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D719051817-25032010></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D719051817-25032010></SPAN><SPAN=20
class=3D719051817-25032010><FONT face=3DArial color=3D#0000ff =
size=3D2>MOP also=20
means&nbsp;"Method of Procedure in our company as well&nbsp;with the =
same=20
understand as stated by Zhi below.</FONT>&nbsp;</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D719051817-25032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D719051817-25032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D719051817-25032010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Cecil</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Zhi-Wei Lin =
[mailto:zhiwlin@gmail.com]=20
<BR><B>Sent:</B> 25 March 2010 17:16<BR><B>To:</B> Adrian =
Farrel<BR><B>Cc:</B>=20
curtis@occnc.com; Cecil Byles; mpls@ietf.org; CCAMP@ietf.org; Alexander=20
Vainshtein; mpls-tp@ietf.org<BR><B>Subject:</B> Re: [mpls] [CCAMP] =
[mpls-tp]=20
Term "PSC"indraft-ietf-mpls-tp-linear-protection-01<BR></FONT><BR></DIV>
<DIV></DIV>Hi Adrian,<BR><BR>Sorry. MOP in our company refers to method =
of=20
procedure, basically the operating model and process for operation and=20
maintenance of the network.<BR><BR>We do realize our MOP would need to =
be=20
modified to handle MPLS-TP, but anything that can be done to reduce the =
effort=20
would be greatly appreciated.<BR><BR>Thanks<BR>Zhi<BR><BR><BR>
<DIV class=3Dgmail_quote>On Thu, Mar 25, 2010 at 12:56 PM, Adrian Farrel =
<SPAN=20
dir=3Dltr>&lt;<A=20
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</A>&gt;</SPAN> =
wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Hi,<BR><BR>Welcome=20
  your input on this as an operator.<BR><BR>Need to understand whether =
"MOP"=20
  covers the PDU formats or refers to the actions that an operator must =
take,=20
  and the states that are reported by the=20
  network?<BR><BR>Thanks,<BR>Adrian<BR>----- Original Message ----- =
From:=20
  "Zhi-Wei Lin" &lt;<A href=3D"mailto:zhiwlin@gmail.com"=20
  target=3D_blank>zhiwlin@gmail.com</A>&gt;<BR>To: &lt;<A=20
  href=3D"mailto:curtis@occnc.com" =
target=3D_blank>curtis@occnc.com</A>&gt;<BR>Cc:=20
  "Cecil Byles" &lt;<A href=3D"mailto:Cecil.Byles@interoute.com"=20
  target=3D_blank>Cecil.Byles@interoute.com</A>&gt;; &lt;<A=20
  href=3D"mailto:mpls@ietf.org" target=3D_blank>mpls@ietf.org</A>&gt;; =
&lt;<A=20
  href=3D"mailto:CCAMP@ietf.org" target=3D_blank>CCAMP@ietf.org</A>&gt;; =
"Alexander=20
  Vainshtein" &lt;<A href=3D"mailto:Alexander.Vainshtein@ecitele.com"=20
  target=3D_blank>Alexander.Vainshtein@ecitele.com</A>&gt;; &lt;<A=20
  href=3D"mailto:mpls-tp@ietf.org" =
target=3D_blank>mpls-tp@ietf.org</A>&gt;<BR>Sent:=20
  Thursday, March 25, 2010 2:38 PM<BR>Subject: Re: [mpls] [CCAMP] =
[mpls-tp] Term=20
  "PSC"indraft-ietf-mpls-tp-linear-protection-01
  <DIV>
  <DIV></DIV>
  <DIV class=3Dh5><BR><BR><BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Hi,<BR><BR>I=20
    like to give my perspective. As a small network company (but one of=20
    the<BR>largest transit agencies), we have a small operating staff =
split into=20
    two<BR>groups: one that handles traditional data network (Ethernet, =
IP), and=20
    one<BR>that handles transport network (SONET, WDM).<BR><BR>We are =
targeting=20
    the transport network operating staff to maintain and<BR>operate the =
MPLS-TP=20
    network. As such, anything that will help to reduce the<BR>learning =
curve=20
    (less training), simplify operating, and make the MOP =
as<BR>consistent as=20
    possible between SONET and MPLS-TP would be hugely=20
    beneficial.<BR><BR>Obviously there will be some differences since =
MPLS-TP is=20
    a packet-based<BR>transport network, but the standards groups (I =
don't=20
    really care for<BR>politics of IETF and ITU) should strive to make =
these=20
    differences easy to<BR>learn.<BR><BR>Thanks<BR>Zhi<BR><BR><BR>On =
Thu, Mar=20
    25, 2010 at 2:09 AM, Curtis Villamizar &lt;<A =
href=3D"mailto:curtis@occnc.com"=20
    target=3D_blank>curtis@occnc.com</A>&gt; wrote:<BR><BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid"><BR>In=20
      message &lt;<A=20
      =
href=3D"mailto:4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute.=
com"=20
      =
target=3D_blank>4B2E9510FA2E7E4EB223A7F2F9EE3A9503A2FE59@PREX22.interoute=
.com</A>&gt;<BR>"Cecil=20
      Byles" writes:<BR>&gt;<BR>&gt;<BR>&gt; Hi,<BR>&gt; Can I therefore =
also=20
      asked how PSC "Protection State Coordination" in<BR>&gt; the =
MPLS-TP=20
      parlance align with ITU-T 808.1 recommendation that &gt; =
"defines<BR>&gt;=20
      the generic functional models, characteristics and processes=20
      associated<BR>&gt; with various linear protection schemes for=20
      connection-oriented layer<BR>&gt; networks; e.g., Optical =
Transport=20
      Networks (OTN), Synchronous Digital<BR>&gt; Hierarchy (SDH) =
networks and=20
      Asynchronous Transfer Mode (ATM) networks"<BR>&gt; and the =
sections=20
      covering &nbsp;Terms and Definitions as well as<BR>&gt; =
Abbreviations.=20
      &nbsp;IMO all transport engineers and the general telecom<BR>&gt;=20
      community understand that 1+1 or 1:1 are either SNCP or APS. Hence =

      why<BR>&gt; introduce a new TLA (three letter abbreviation) cover =
the same=20
      function<BR>&gt; and feature for MPLS-TP. &nbsp;I can only agree =
that this=20
      will only cause<BR>&gt; confusion.<BR>&gt;<BR>&gt; Cecil=20
      Byles<BR><BR><BR>Though this is joint work, this is the IETF not =
the ITU.=20
      &nbsp;We should<BR>use ITU terms where appropriate but where there =
is a=20
      conflict such as<BR>this we need to pick another term and another =
TLA.=20
      &nbsp;If the ITU wants<BR>to update 808.1 at some later date that =
is up to=20
      the ITU. &nbsp;In the mean<BR>time we can use another term and =
point out=20
      the=20
      =
mapping.<BR><BR>Curtis<BR>_______________________________________________=
<BR>mpls=20
      mailing list<BR><A href=3D"mailto:mpls@ietf.org"=20
      target=3D_blank>mpls@ietf.org</A><BR><A=20
      href=3D"https://www.ietf.org/mailman/listinfo/mpls"=20
      =
target=3D_blank>https://www.ietf.org/mailman/listinfo/mpls</A><BR><BR></B=
LOCKQUOTE><BR></BLOCKQUOTE><BR><BR></DIV></DIV>--------------------------=
------------------------------------------------------
  <DIV>
  <DIV></DIV>
  <DIV class=3Dh5><BR><BR><BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px =
solid">_______________________________________________<BR>mpls=20
    mailing list<BR><A href=3D"mailto:mpls@ietf.org"=20
    target=3D_blank>mpls@ietf.org</A><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/mpls"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/mpls</A><BR><BR></B=
LOCKQUOTE><BR></DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>

------_=_NextPart_001_01CACC45.3952A22A--

From Cecil.Byles@interoute.com  Thu Mar 25 11:51:22 2010
Return-Path: <Cecil.Byles@interoute.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FCBD3A6D96; Thu, 25 Mar 2010 11:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.900,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, GB_I_LETTER=-2, 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 u9FQ3ktmy1Y6; Thu, 25 Mar 2010 11:51:12 -0700 (PDT)
Received: from mail1.interoute.com (mail1.interoute.com [89.202.186.60]) by core3.amsl.com (Postfix) with ESMTP id 56FDD3A6CC1; Thu, 25 Mar 2010 11:51:04 -0700 (PDT)
Received: from ukex01.interoute.com ([172.31.149.70]) by mail1.interoute.com with Microsoft SMTPSVC(7.0.6001.18000);  Thu, 25 Mar 2010 19:51:27 +0100
Received: from PREX22.interoute.com ([172.31.149.20]) by ukex01.interoute.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 25 Mar 2010 19:51:22 +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_01CACC4C.2A1E1718"
Date: Thu, 25 Mar 2010 19:51:21 +0100
Message-ID: <4B2E9510FA2E7E4EB223A7F2F9EE3A9503AB05A0@PREX22.interoute.com>
In-Reply-To: <2ECAA42C79676B42AEBAC11229CA7D0C05C105AC@E03MVB2-UKBR.domain1.systemhost.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [CCAMP] [mpls-tp] [mpls] Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrMMeUjKErPQOPpTa6mLkJaqy6dNQAAGgcAAATAFkA=
References: <67ec4be61003250842r7927acaes1a39905d92a3a7dc@mail.gmail.com> <2ECAA42C79676B42AEBAC11229CA7D0C05C105AC@E03MVB2-UKBR.domain1.systemhost.net>
From: "Cecil Byles" <Cecil.Byles@interoute.com>
To: <Adrian.Farrel@huawei.com>
X-OriginalArrivalTime: 25 Mar 2010 18:51:22.0949 (UTC) FILETIME=[2A1B3F50:01CACC4C]
Cc: Maarten Vissers <maarten.vissers@huawei.com>, mpls@ietf.org, CCAMP@ietf.org, Ibrahim Djafer <Ibrahim.Djafer@interoute.com>, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 18:51:22 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CACC4C.2A1E1718
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Adrian,
=20
Please can you or colleagues explain to me, what do you mean by the
following statement "
" If you like, PSC is simply a generalisation that allows freedom of
interpretation. "
=20
>From a transport view point, us and all other operators' can
inter-operate various protection schemes (SDH/OTN) base on
characteristics and behaviours of G. 808.1 and G.841/G.873.1 without
having the same manufactures equipment. Thus are you advocating
operators must now all purchase the same equipment type if they want to
inter-operate MPLS-TP protection schemes based various equipment vendors
freedom of interpretation of the PSC protocol that do not comply with
Y.1731 sections 7.8 and 9.10 to 9.10.2. Also are you by inference
stating as an SDO can not run nested protection schemes for example
G.8131 over a G.8031/G.8032 or G.8132. or a combination of any of these
protection schemes as a hierarchal network similar to other ITU
standards based transports networks.?
=20
Regards
=20
Cecil

=20
________________________________

From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]=20
Sent: 25 March 2010 15:56
To: zhiwlin@gmail.com; lberger@labn.net
Cc: Cecil Byles; mpls@ietf.org; CCAMP@ietf.org;
Adrian.Farrel@huawei.com; mpls-tp@ietf.org
Subject: RE: [CCAMP] [mpls-tp] [mpls]
Term"PSC"indraft-ietf-mpls-tp-linear-protection-01


There are only so many ways to provide DP/MP/CP components of each of
the 3 networking modes (addressing, signalling, routing, OAM,
etc)....and there will be a best-of-breed solution for a given component
at any given time, whatever name we give it.  I sometimes sense that
judgement of technical merit might get compromised by a stronger NIH
(Not Invented Here) behaviour....esp if the component in question comes
from another SDO.=20
=20
Speaking as an operator we have a (well publicised internally) desire to
have as much sensible re-use of components as possible.
=20
regards, Neil


________________________________

	From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On
Behalf Of Zhi-Wei Lin
	Sent: 25 March 2010 15:42
	To: Lou Berger
	Cc: Cecil Byles; mpls@ietf.org; CCAMP@ietf.org; Adrian Farrel;
mpls-tp@ietf.org
	Subject: Re: [CCAMP] [mpls-tp] [mpls]
Term"PSC"indraft-ietf-mpls-tp-linear-protection-01
=09
=09
	Hi,
=09
	We have PSC, RSC, APS...how about MPS for MPLS-TP Protection
Switching...? I think the acronym (whatever it is) should have
"protection switching" in it just so that transport folks know it is
similar to what they have used (but different because it's not TDM
based).
=09
	Thanks
	Zhi
=09
=09
	On Thu, Mar 25, 2010 at 11:31 AM, Lou Berger <lberger@labn.net>
wrote:
=09

		Adrian,
		       I fully support the high-level point you are
making, i.e., the
		continued use of a term other than APS in the context of
TP.  That said,
		I'm open to renaming PSC to something that doesn't
conflict with
		existing MPLS/GMPLS terms.  Curtis' proposal of RSC is
an example.
	=09
		Lou
	=09
		On 3/25/2010 1:32 AM, Adrian Farrel wrote:
		> Huub,
		>
		> You will note that the comment in the liaison you
reference said:
		>
		> "The acronyms PSC and APS are used, in ITU-T APS is a
generic term used in
		> different methodologies and does not provide a
solution."
		>
		> This was neither a question nor a request for any
change. And it is not
		> really clear that it is a "concern".
		>
		> APS is an abstract protocol (G.808.1) with specific
characteristics and
		> behaviors.
		>
		> The Survivability Framework deliberately does not
prejudge the abstract
		> protocol or solution protocol that is required.
Instead, it picked another
		> acronym to avoid any assumptions. This frees the
people working in the
		> solution space to choose the necessary abstract model
for the problems they
		> need to solve, and to develop a protocol realisation
that meets the model.
		> This neither precludes nor forces the use of APS.
		>
		> If you like, PSC is simply a generalisation that
allows freedom of
		> interpretation. Viz.
		>
		>    In some protection switching schemes (such as
bidirectional
		>    protection switching), it is necessary to
coordinate the protection
		>    state between the edges of the recovery domain.  An
MPLS-TP
		>    Protection State Coordination (PSC) protocol may be
used as an in-
		>    band (i.e., data plane-based) control protocol to
align both ends of
		>    the protected domain.  Control plane-based
mechanism can also be used
		>    to coordinate the protection states between the
edges of the
		>    protection domain.
		>
		> In the view of the authors, the term "APS" has become
synonymous with
		> specific protocol realisations. For example, in the
working copy of G.8131 I
		> have infront of me, section 10 describes the "APS
Protocol" setting out byte
		> formats and defining messages to go on the wire. While
we can interpret "APS
		> Protocol" as the technology-specific realisation of
"APS", there are
		> sufficient overtones that if the Survivability
Framework used the term "APS"
		> it might be construed as support for a specific
protocol realisation. Y.1731
	=09
		> defines APS PDUs for Ethernet which gives us another
competing
		> interpretation of the term. (It is notable that the
term "APS Protocol" is
		> used in G.870 to mean the abstract protocol, which is
subtly different from
		> its use in G.8131 and Y.1731.)
		>
	=09
		> Surely the working group would prefer to derive the
correct protocol
		> solution without being constrained except at a
functional level?
		>
		> Adrian
	=09
		>
		>
		> ----- Original Message -----
		> From: "Huub van Helvoort" <hhelvoort@chello.nl>
		> To: "Cecil Byles" <Cecil.Byles@interoute.com>
		> Cc: <mpls@ietf.org>; <CCAMP@ietf.org>;
<mpls-tp@ietf.org>
	=09
		> Sent: Wednesday, March 24, 2010 5:14 PM
		> Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"
		> indraft-ietf-mpls-tp-linear-protection-01
		>
		>
	=09
		> Hello Cecil,
		>
		> You wrote:
		>
		>> Can I therefore also asked how PSC "Protection State
Coordination" in the
		>> MPLS-TP parlance align with ITU-T 808.1
recommendation that "defines the
		>> generic functional models, characteristics and
processes associated with
		>> various linear protection schemes for
connection-oriented layer networks;
		>> e.g., Optical Transport Networks (OTN), Synchronous
Digital Hierarchy
		>> (SDH) networks and Asynchronous Transfer Mode (ATM)
networks" and the
		>> sections covering  Terms and Definitions as well as
Abbreviations.  IMO
		>> all transport engineers and the general telecom
community understand that
		>> 1+1 or 1:1 are either SNCP or APS. Hence why
introduce a new TLA (three
		>> letter abbreviation) cover the same function and
feature for MPLS-TP.  I
		>> can only agree that this will only cause confusion.
		>
		> I agree with you.
		>
		> In addition to that:
		> The ITU-T experts that reviewed the survivability
draft had the same
		> concerns, and expressed that in their reply liaison
for the review of
		> this draft: https://datatracker.ietf.org/liaison/618/
that was
		> sent in november last year.
		> This concern has not been addressed yet.
		>
		> Regards, Huub.
		>
		>
	=09
		_______________________________________________
		CCAMP mailing list
		CCAMP@ietf.org
		https://www.ietf.org/mailman/listinfo/ccamp
	=09



------_=_NextPart_001_01CACC4C.2A1E1718
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16981" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D005160218-25032010>Hi Adrian,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D005160218-25032010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D005160218-25032010>Please can you or colleagues explain to me, =
what do you=20
mean&nbsp;by the following statement "</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D005160218-25032010><FONT face=3D"Times New Roman" =
color=3D#000000=20
size=3D3>"&nbsp;If you like, PSC is simply a generalisation that allows =
freedom=20
of&nbsp; interpretation. "</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D005160218-25032010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT color=3D#0000ff><FONT=20
face=3DArial>From&nbsp;a&nbsp;transport&nbsp;view&nbsp;point<SPAN=20
class=3D005160218-25032010>,=20
</SPAN>us&nbsp;and&nbsp;all&nbsp;other&nbsp;operators'&nbsp;can&nbsp;<SPA=
N=20
class=3D005160218-25032010>inter-operate&nbsp;</SPAN>various&nbsp;protect=
ion&nbsp;schemes&nbsp;<SPAN=20
class=3D005160218-25032010>(SDH/OTN) =
</SPAN>base&nbsp;on&nbsp;characteristics=20
and&nbsp;behaviours&nbsp;of&nbsp;<SPAN class=3D005160218-25032010>G.=20
</SPAN>808.1&nbsp;and&nbsp;G.841<SPAN=20
class=3D005160218-25032010>/G.873.1</SPAN>&nbsp;without&nbsp;having&nbsp;=
the&nbsp;same<SPAN=20
class=3D005160218-25032010> manufactures</SPAN>&nbsp;equipment.<SPAN=20
class=3D005160218-25032010> Thus are you advocating operators must=20
now&nbsp;all&nbsp;purchase the same equipment type if they want to =
inter-operate=20
MPLS-TP protection schemes based various equipment=20
vendors&nbsp;</SPAN></FONT><SPAN class=3D005160218-25032010><FONT=20
face=3DArial>freedom of&nbsp;interpretation of the PSC protocol that do =
not comply=20
with Y.1731 sections 7.8 and 9.10 to 9.10.2. =
</FONT></SPAN></FONT></FONT><FONT=20
size=3D2><FONT face=3DArial color=3D#0000ff><SPAN =
class=3D005160218-25032010>Also are=20
you by inference stating as an SDO can not run nested protection schemes =
for=20
example G.8131 over a G.8031/G.8032 or G.8132. or a combination of any =
of these=20
protection schemes as a hierarchal network similar to other ITU =
standards based=20
transports networks.?</SPAN></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D005160218-25032010></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D005160218-25032010>Regards</SPAN></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D005160218-25032010></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D005160218-25032010>Cecil</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff size=3D2><FONT=20
face=3D"Times New Roman"><SPAN =
class=3D005160218-25032010></SPAN></FONT><FONT=20
face=3D"Times New Roman"></FONT><FONT face=3D"Times New =
Roman"></FONT><FONT=20
face=3D"Times New Roman"></FONT><BR>&nbsp;</DIV></FONT></FONT>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> neil.2.harrison@bt.com=20
[mailto:neil.2.harrison@bt.com] <BR><B>Sent:</B> 25 March 2010=20
15:56<BR><B>To:</B> zhiwlin@gmail.com; lberger@labn.net<BR><B>Cc:</B> =
Cecil=20
Byles; mpls@ietf.org; CCAMP@ietf.org; Adrian.Farrel@huawei.com;=20
mpls-tp@ietf.org<BR><B>Subject:</B> RE: [CCAMP] [mpls-tp] [mpls]=20
Term"PSC"indraft-ietf-mpls-tp-linear-protection-01<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000>There are only so many ways to =
provide=20
DP/MP/CP components of each of the 3 networking modes (addressing, =
signalling,=20
routing, OAM, etc)....and there will be a best-of-breed solution for a =
given=20
component at any given time, whatever name we give it.&nbsp; I sometimes =
sense=20
that judgement of technical merit might get compromised by a stronger =
NIH (Not=20
Invented Here) behaviour....esp if the component in question comes from =
another=20
SDO.&nbsp;</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000>Speaking as an operator we have a =
(well=20
publicised internally) desire to have as much sensible re-use of =
components as=20
possible.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D019154615-25032010><FONT=20
face=3D"Comic Sans MS" color=3D#800000>regards, =
Neil</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; 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> ccamp-bounces@ietf.org=20
  [mailto:ccamp-bounces@ietf.org] <B>On Behalf Of </B>Zhi-Wei=20
  Lin<BR><B>Sent:</B> 25 March 2010 15:42<BR><B>To:</B> Lou =
Berger<BR><B>Cc:</B>=20
  Cecil Byles; mpls@ietf.org; CCAMP@ietf.org; Adrian Farrel;=20
  mpls-tp@ietf.org<BR><B>Subject:</B> Re: [CCAMP] [mpls-tp] [mpls]=20
  =
Term"PSC"indraft-ietf-mpls-tp-linear-protection-01<BR></FONT><BR></DIV>
  <DIV></DIV>Hi,<BR><BR>We have PSC, RSC, APS...how about MPS for =
MPLS-TP=20
  Protection Switching...? I think the acronym (whatever it is) should =
have=20
  "protection switching" in it just so that transport folks know it is =
similar=20
  to what they have used (but different because it's not TDM=20
  based).<BR><BR>Thanks<BR>Zhi<BR><BR>
  <DIV class=3Dgmail_quote>On Thu, Mar 25, 2010 at 11:31 AM, Lou Berger =
<SPAN=20
  dir=3Dltr>&lt;<A =
href=3D"mailto:lberger@labn.net">lberger@labn.net</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Adrian,<BR>&nbsp;=20
    &nbsp; &nbsp; &nbsp;I fully support the high-level point you are =
making,=20
    i.e., the<BR>continued use of a term other than APS in the context =
of TP.=20
    &nbsp;That said,<BR>I'm open to renaming PSC to something that =
doesn't=20
    conflict with<BR>existing MPLS/GMPLS terms. &nbsp;Curtis' proposal =
of RSC is=20
    an example.<BR><BR>Lou<BR><BR>On 3/25/2010 1:32 AM, Adrian Farrel=20
    wrote:<BR>&gt; Huub,<BR>&gt;<BR>&gt; You will note that the comment =
in the=20
    liaison you reference said:<BR>&gt;<BR>&gt; "The acronyms PSC and =
APS are=20
    used, in ITU-T APS is a generic term used in<BR>&gt; different =
methodologies=20
    and does not provide a solution."<BR>&gt;<BR>&gt; This was neither a =

    question nor a request for any change. And it is not<BR>&gt; really =
clear=20
    that it is a "concern".<BR>&gt;<BR>&gt; APS is an abstract protocol=20
    (G.808.1) with specific characteristics and<BR>&gt;=20
    behaviors.<BR>&gt;<BR>&gt; The Survivability Framework deliberately =
does not=20
    prejudge the abstract<BR>&gt; protocol or solution protocol that is=20
    required. Instead, it picked another<BR>&gt; acronym to avoid any=20
    assumptions. This frees the people working in the<BR>&gt; solution =
space to=20
    choose the necessary abstract model for the problems they<BR>&gt; =
need to=20
    solve, and to develop a protocol realisation that meets the =
model.<BR>&gt;=20
    This neither precludes nor forces the use of APS.<BR>&gt;<BR>&gt; If =
you=20
    like, PSC is simply a generalisation that allows freedom of<BR>&gt;=20
    interpretation. Viz.<BR>&gt;<BR>&gt; &nbsp; &nbsp;In some protection =

    switching schemes (such as bidirectional<BR>&gt; &nbsp; =
&nbsp;protection=20
    switching), it is necessary to coordinate the protection<BR>&gt; =
&nbsp;=20
    &nbsp;state between the edges of the recovery domain. &nbsp;An=20
    MPLS-TP<BR>&gt; &nbsp; &nbsp;Protection State Coordination (PSC) =
protocol=20
    may be used as an in-<BR>&gt; &nbsp; &nbsp;band (i.e., data =
plane-based)=20
    control protocol to align both ends of<BR>&gt; &nbsp; &nbsp;the =
protected=20
    domain. &nbsp;Control plane-based mechanism can also be used<BR>&gt; =
&nbsp;=20
    &nbsp;to coordinate the protection states between the edges of =
the<BR>&gt;=20
    &nbsp; &nbsp;protection domain.<BR>&gt;<BR>&gt; In the view of the =
authors,=20
    the term "APS" has become synonymous with<BR>&gt; specific protocol=20
    realisations. For example, in the working copy of G.8131 I<BR>&gt; =
have=20
    infront of me, section 10 describes the "APS Protocol" setting out=20
    byte<BR>&gt; formats and defining messages to go on the wire. While =
we can=20
    interpret "APS<BR>&gt; Protocol" as the technology-specific =
realisation of=20
    "APS", there are<BR>&gt; sufficient overtones that if the =
Survivability=20
    Framework used the term "APS"<BR>&gt; it might be construed as =
support for a=20
    specific protocol realisation. Y.1731<BR>
    <DIV class=3Dim>&gt; defines APS PDUs for Ethernet which gives us =
another=20
    competing<BR>&gt; interpretation of the term. (It is notable that =
the term=20
    "APS Protocol" is<BR>&gt; used in G.870 to mean the abstract =
protocol, which=20
    is subtly different from<BR>&gt; its use in G.8131 and=20
    Y.1731.)<BR>&gt;<BR></DIV>&gt; Surely the working group would prefer =
to=20
    derive the correct protocol<BR>&gt; solution without being =
constrained=20
    except at a functional level?<BR>&gt;<BR>&gt; Adrian<BR>
    <DIV class=3Dim>&gt;<BR>&gt;<BR>&gt; ----- Original Message =
-----<BR>&gt;=20
    From: "Huub van Helvoort" &lt;<A=20
    =
href=3D"mailto:hhelvoort@chello.nl">hhelvoort@chello.nl</A>&gt;<BR>&gt; =
To:=20
    "Cecil Byles" &lt;<A=20
    =
href=3D"mailto:Cecil.Byles@interoute.com">Cecil.Byles@interoute.com</A>&g=
t;<BR>&gt;=20
    Cc: &lt;<A href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A>&gt;; =
&lt;<A=20
    href=3D"mailto:CCAMP@ietf.org">CCAMP@ietf.org</A>&gt;; &lt;<A=20
    href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</A>&gt;<BR></DIV>
    <DIV class=3Dim>&gt; Sent: Wednesday, March 24, 2010 5:14 PM<BR>&gt; =
Subject:=20
    Re: [CCAMP] [mpls-tp] [mpls] Term"PSC"<BR>&gt;=20
    indraft-ietf-mpls-tp-linear-protection-01<BR>&gt;<BR>&gt;<BR></DIV>
    <DIV>
    <DIV></DIV>
    <DIV class=3Dh5>&gt; Hello Cecil,<BR>&gt;<BR>&gt; You=20
    wrote:<BR>&gt;<BR>&gt;&gt; Can I therefore also asked how PSC =
&#8220;Protection=20
    State Coordination&#8221; in the<BR>&gt;&gt; MPLS-TP parlance align =
with ITU-T=20
    808.1 recommendation that "defines the<BR>&gt;&gt; generic =
functional=20
    models, characteristics and processes associated with<BR>&gt;&gt; =
various=20
    linear protection schemes for connection-oriented layer=20
    networks;<BR>&gt;&gt; e.g., Optical Transport Networks (OTN), =
Synchronous=20
    Digital Hierarchy<BR>&gt;&gt; (SDH) networks and Asynchronous =
Transfer Mode=20
    (ATM) networks" and the<BR>&gt;&gt; sections covering &nbsp;Terms =
and=20
    Definitions as well as Abbreviations. &nbsp;IMO<BR>&gt;&gt; all =
transport=20
    engineers and the general telecom community understand =
that<BR>&gt;&gt; 1+1=20
    or 1:1 are either SNCP or APS. Hence why introduce a new TLA=20
    (three<BR>&gt;&gt; letter abbreviation) cover the same function and =
feature=20
    for MPLS-TP. &nbsp;I<BR>&gt;&gt; can only agree that this will only =
cause=20
    confusion.<BR>&gt;<BR>&gt; I agree with you.<BR>&gt;<BR>&gt; In =
addition to=20
    that:<BR>&gt; The ITU-T experts that reviewed the survivability =
draft had=20
    the same<BR>&gt; concerns, and expressed that in their reply liaison =
for the=20
    review of<BR>&gt; this draft: <A=20
    href=3D"https://datatracker.ietf.org/liaison/618/"=20
    target=3D_blank>https://datatracker.ietf.org/liaison/618/</A> that =
was<BR>&gt;=20
    sent in november last year.<BR>&gt; This concern has not been =
addressed=20
    yet.<BR>&gt;<BR>&gt; Regards,=20
    =
Huub.<BR>&gt;<BR>&gt;<BR></DIV></DIV>____________________________________=
___________<BR>CCAMP=20
    mailing list<BR><A =
href=3D"mailto:CCAMP@ietf.org">CCAMP@ietf.org</A><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/ccamp"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/ccamp</A><BR></BLOC=
KQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CACC4C.2A1E1718--

From curtis@occnc.com  Sat Mar 27 19:53:41 2010
Return-Path: <curtis@occnc.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B616B3A68D1 for <ccamp@core3.amsl.com>; Sat, 27 Mar 2010 19:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.766
X-Spam-Level: 
X-Spam-Status: No, score=-0.766 tagged_above=-999 required=5 tests=[AWL=0.703,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhq7LO+L4mJ8 for <ccamp@core3.amsl.com>; Sat, 27 Mar 2010 19:53:41 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id D43C33A68C7 for <CCAMP@ietf.org>; Sat, 27 Mar 2010 19:53:40 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o2S2s4Tu099819; Sat, 27 Mar 2010 22:54:04 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201003280254.o2S2s4Tu099819@harbor.orleans.occnc.com>
To: Zhi-Wei Lin <zhiwlin@gmail.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 25 Mar 2010 11:42:08 EDT." <67ec4be61003250842r7927acaes1a39905d92a3a7dc@mail.gmail.com> 
Date: Sat, 27 Mar 2010 22:54:04 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, Cecil Byles <Cecil.Byles@interoute.com>, CCAMP@ietf.org, mpls-tp@ietf.org, Adrian Farrel <Adrian.Farrel@huawei.com>
Subject: Re: [CCAMP] [mpls-tp] [mpls] Term"PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Mar 2010 02:53:41 -0000

In message <67ec4be61003250842r7927acaes1a39905d92a3a7dc@mail.gmail.com>
Zhi-Wei Lin writes:
>  
>  
> Hi,
>  
> We have PSC, RSC, APS...how about MPS for MPLS-TP Protection
> Switching...?  I think the acronym (whatever it is) should have
> "protection switching" in it just so that transport folks know it is
> similar to what they have used (but different because it's not TDM
> based).
>  
> Thanks
> Zhi
>  
> On Thu, Mar 25, 2010 at 11:31 AM, Lou Berger <lberger@labn.net> wrote:
>  
> > Adrian,
> >        I fully support the high-level point you are making, i.e., the
> > continued use of a term other than APS in the context of TP.  That said,
> > I'm open to renaming PSC to something that doesn't conflict with
> > existing MPLS/GMPLS terms.  Curtis' proposal of RSC is an example.
> >
> > Lou


I'm in favor of R for recovery rather than P for protection. in the
future we won't get into a semantic argument over whether that is a
protection or a restoration scheme if it is fast but has some
signaling (or OAM) on failure.  For example we define a capability
that sets aside some shared bandwidth but commits it to a particular
use depending on the SRLG that failed we could get into such an
argument if we use P rather than R.

Curtis

From loa@pi.nu  Fri Mar 26 18:12:12 2010
Return-Path: <loa@pi.nu>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 822983A6A4A; Fri, 26 Mar 2010 18:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.76
X-Spam-Level: 
X-Spam-Status: No, score=0.76 tagged_above=-999 required=5 tests=[AWL=-0.185,  BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixHK4o2eF0K4; Fri, 26 Mar 2010 18:12:11 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id C583D3A6882; Fri, 26 Mar 2010 18:12:07 -0700 (PDT)
Received: from [130.129.25.89] (dhcp-wireless-open-abg-25-89.meeting.ietf.org [130.129.25.89]) (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 D571ED404F; Sat, 27 Mar 2010 02:12:27 +0100 (CET)
Message-ID: <4BAD5B78.5000808@pi.nu>
Date: Fri, 26 Mar 2010 18:12:24 -0700
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; 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>
Content-Type: multipart/mixed; boundary="------------060800030206020104050907"
X-Mailman-Approved-At: Sun, 28 Mar 2010 09:41:39 -0700
Subject: [CCAMP] changes to the mpls working group klast calls on mpls-tp documents
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2010 01:12:12 -0000

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

Working Group(s), Ad Hoc Team

Offline the mpls-tp working group chairs, ADs and for part of the
time the ITU-T SG15 Rapporteurs attending the meeting in Anaheim
have spent time during the IETF week on the issue how to get a
high-quality standard out of the joint mpls-tp project. The
IETF leadership still see great value in keeping to the schedule
we've been working on for the last 9 months and is quite optimistic
about getting a high-quality work done on time.

The working group chairs have agreed to extend the working group
last call schedule.

We have made the following extensions/changes for the mpls-tp
project drafts that is currently in (or soon will be) in mpls
wg last call:


OAM Acronyms draft-ietf-opsawg-mpls-tp-oam-def
The OPSAWG wg last call will start on March 29 and end on April 18


MPLS-TP Framework draft-ietf-mpls-tp-framework
The MPLS wg last call will start on April 5 and end on April 18


MPLS-TP OAM Framework draft-ietf-mpls-tp-oam-framework
The ongoing MPLS wg last call will end on April 1

MPLS-TP Survivability Framework draft-ietf-mpls-tp-survive-fwk
The ongoing MPLS working group last call will end on April 11


MPLS-TP Data plane draft-ietf-mpls-tp-data-plane
The ongoing MPLS working group last call will end on April 11


ACH-TLV structure draft-ietf-mpls-tp-ach-tlv
The ongoing MPLS wg last call will end on April 12


MPLS-TP Identifiers draft-ietf-mpls-tp-identifiers-00
The ongoing MPLS wg last call will end on April 11

The latest version of a excel schedule that has been discussed
is included in this mail. I'd lake to poll for working group(s)
for comments on the schedule. As usual send these comments to
the mpls-tp mailing list only.

/Loa
-- 


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

--------------060800030206020104050907
Content-Type: application/vnd.ms-excel;
 name="schedule-B.xls"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="schedule-B.xls"

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAAQAAAAAA
AAAAEAAAUQAAAAEAAAD+////AAAAAAAAAAD/////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
///////////////////////////////////9////UwAAAAMAAAAEAAAABQAAAAYAAAAHAAAA
CAAAAAkAAAAKAAAACwAAAAwAAAANAAAADgAAAA8AAAAQAAAAEQAAABIAAAATAAAAFAAAABUA
AAAWAAAAFwAAABgAAAAZAAAAGgAAABsAAAAcAAAAHQAAAB4AAAAfAAAAIAAAACEAAAAiAAAA
IwAAACQAAAAlAAAAJgAAACcAAAAoAAAAKQAAACoAAAArAAAALAAAAC0AAAAuAAAALwAAADAA
AAAxAAAAMgAAADMAAAA0AAAANQAAADYAAAA3AAAAOAAAADkAAAA6AAAAOwAAADwAAAA9AAAA
PgAAAD8AAABAAAAAQQAAAEIAAABDAAAARAAAAEUAAABGAAAARwAAAEgAAABJAAAASgAAAEsA
AABMAAAATQAAAE4AAABPAAAAUAAAAP7////+////VAAAAP7////+////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////1IA
bwBvAHQAIABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAWAAUA//////////8CAAAAIAgCAAAAAADAAAAAAAAARgAAAABRaDaNNs3KAfB4
RXJKzcoBUgAAAIACAAAAAAAAVwBvAHIAawBiAG8AbwBrAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAgEEAAAA//////////8AAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAASZwAAAAAAAAFAFMAdQBtAG0AYQByAHkA
SQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKAACAQEA
AAADAAAA/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADQAAAA
AAAAAAUARABvAGMAdQBtAGUAbgB0AFMAdQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkA
bwBuAAAAAAAAAAAAAAA4AAIB////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAABAAAAOAAAAAAAAAACQgQAAAGBQCqH80HyQABAAYEAADhAAIAsATBAAIA
AADiAAAAXABwAAcAAGVsb2FhbmQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICBCAAIAsARhAQIAAADAAQAAPQECAAQAnAACABAAGQACAAAAEgACAAAA
EwACAAAArwECAAAAvAECAAAAPQASAHgAeABTYSsvOAAAAAAAAQBYAkAAAgAAAI0AAgAAACIA
AgAAAA4AAgABALcBAgAAANoAAgAAADEAHgDcAAAACACQAQAAAAIAcgcBQwBhAGwAaQBiAHIA
aQAxAB4A3AAAAAgAkAEAAAACAHIHAUMAYQBsAGkAYgByAGkAMQAeANwAAAAIAJABAAAAAgBy
BwFDAGEAbABpAGIAcgBpADEAHgDcAAAACACQAQAAAAIAcgcBQwBhAGwAaQBiAHIAaQAxAB4A
3AAAAAgAkAEAAAACAHIHAUMAYQBsAGkAYgByAGkAMQAeANwAAAAJAJABAAAAAgByBwFDAGEA
bABpAGIAcgBpADEAHgDcAAAAFACQAQAAAAIAcgcBQwBhAGwAaQBiAHIAaQAxAB4A3AABADQA
vAIAAAACAHIHAUMAYQBsAGkAYgByAGkAMQAeANwAAQAJALwCAAAAAgByBwFDAGEAbABpAGIA
cgBpADEAHgDcAAIAFwCQAQAAAAIAcgcBQwBhAGwAaQBiAHIAaQAxAB4A3AAAABEAkAEAAAAC
AHIHAUMAYQBsAGkAYgByAGkAMQAeACwBAQA4ALwCAAAAAgByBwFDAGEAbABpAGIAcgBpADEA
HgAEAQEAOAC8AgAAAAIAcgcBQwBhAGwAaQBiAHIAaQAxAB4A3AABADgAvAIAAAACAHIHAUMA
YQBsAGkAYgByAGkAMQAeANwAAAA+AJABAAAAAgByBwFDAGEAbABpAGIAcgBpADEAHgDcAAAA
NACQAQAAAAIAcgcBQwBhAGwAaQBiAHIAaQAxAB4A3AAAADwAkAEAAAACAHIHAUMAYQBsAGkA
YgByAGkAMQAeANwAAQA/ALwCAAAAAgByBwFDAGEAbABpAGIAcgBpADEAHgBoAQEAOAC8AgAA
AAIAcgcBQwBhAG0AYgByAGkAYQAxAB4A3AABAAgAvAIAAAACAHIHAUMAYQBsAGkAYgByAGkA
MQAeANwAAAAKAJABAAAAAgByBwFDAGEAbABpAGIAcgBpADEAHgAYAQEACAC8AgAAAAIAcgcB
QwBhAGwAaQBiAHIAaQAxAB4A8AABAAgAvAIAAAACAHIHAUMAYQBsAGkAYgByAGkAHgQeAAUA
GQAAIywjIzBcICJrciI7XC0jLCMjMFwgImtyIh4EIwAGAB4AACMsIyMwXCAia3IiO1tSZWRd
XC0jLCMjMFwgImtyIh4EJAAHAB8AACMsIyMwLjAwXCAia3IiO1wtIywjIzAuMDBcICJrciIe
BCkACAAkAAAjLCMjMC4wMFwgImtyIjtbUmVkXVwtIywjIzAuMDBcICJrciIeBD4AKgA5AABf
LSogIywjIzBcICJrciJfLTtcLSogIywjIzBcICJrciJfLTtfLSogIi0iXCAia3IiXy07Xy1A
Xy0eBD4AKQA5AABfLSogIywjIzBcIF9rX3JfLTtcLSogIywjIzBcIF9rX3JfLTtfLSogIi0i
XCBfa19yXy07Xy1AXy0eBEYALABBAABfLSogIywjIzAuMDBcICJrciJfLTtcLSogIywjIzAu
MDBcICJrciJfLTtfLSogIi0iPz9cICJrciJfLTtfLUBfLR4ERgArAEEAAF8tKiAjLCMjMC4w
MFwgX2tfcl8tO1wtKiAjLCMjMC4wMFwgX2tfcl8tO18tKiAiLSI/P1wgX2tfcl8tO18tQF8t
4AAUAAAAAAD1/yAAAAAAAAAAAAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUA
AAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUAAAD1/yAA
APQAAAAAAAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAA
AAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg
4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUA
AAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAUAAAD1/yAA
APQAAAAAAAAAAMAg4AAUAAUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAABACAAAAAAAAAA
AAAAAsAg4AAUAAUAAAD1/yAAALQAAAAAAAAABJ8g4AAUAAUAAAD1/yAAALQAAAAAAAAABK0g
4AAUAAUAAAD1/yAAALQAAAAAAAAABKog4AAUAAUAAAD1/yAAALQAAAAAAAAABK4g4AAUAAUA
AAD1/yAAALQAAAAAAAAABJsg4AAUAAUAAAD1/yAAALQAAAAAAAAABK8g4AAUAAUAAAD1/yAA
ALQAAAAAAAAABKwg4AAUAAUAAAD1/yAAALQAAAAAAAAABJ0g4AAUAAUAAAD1/yAAALQAAAAA
AAAABIsg4AAUAAUAAAD1/yAAALQAAAAAAAAABK4g4AAUAAUAAAD1/yAAALQAAAAAAAAABKwg
4AAUAAUAAAD1/yAAALQAAAAAAAAABLMg4AAUAAYAAAD1/yAAALQAAAAAAAAABJ4g4AAUAAYA
AAD1/yAAALQAAAAAAAAABJ0g4AAUAAYAAAD1/yAAALQAAAAAAAAABIsg4AAUAAYAAAD1/yAA
ALQAAAAAAAAABKQg4AAUAAYAAAD1/yAAALQAAAAAAAAABLEg4AAUAAYAAAD1/yAAALQAAAAA
AAAABLQg4AAUAAYAAAD1/yAAALQAAAAAAAAABL4g4AAUAAYAAAD1/yAAALQAAAAAAAAABIog
4AAUAAYAAAD1/yAAALQAAAAAAAAABLkg4AAUAAYAAAD1/yAAALQAAAAAAAAABKQg4AAUAAYA
AAD1/yAAALQAAAAAAAAABLEg4AAUAAYAAAD1/yAAALQAAAAAAAAABLUg4AAUAAcAAAD1/yAA
ALQAAAAAAAAABK0g4AAUAAgAAAD1/yAAAJQREZcLlwsABJYg4AAUAAkAAAD1/yAAAJRmZr8f
vx8ABLcg4AAUAAUAKwD1/yAAAPgAAAAAAAAAAMAg4AAUAAUAKQD1/yAAAPgAAAAAAAAAAMAg
4AAUAAUALAD1/yAAAPgAAAAAAAAAAMAg4AAUAAUAKgD1/yAAAPgAAAAAAAAAAMAg4AAUAAoA
AAD1/yAAAPQAAAAAAAAAAMAg4AAUAAsAAAD1/yAAALQAAAAAAAAABKog4AAUAAwAAAD1/yAA
ANQAUAAAAB8AAMAg4AAUAA0AAAD1/yAAANQAUAAAAAsAAMAg4AAUAA4AAAD1/yAAANQAIAAA
AA8AAMAg4AAUAA4AAAD1/yAAAPQAAAAAAAAAAMAg4AAUAA8AAAD1/yAAAJQREZcLlwsABK8g
4AAUABAAAAD1/yAAANQAYAAAABoAAMAg4AAUABEAAAD1/yAAALQAAAAAAAAABKsg4AAUAAUA
AAD1/yAAAJwRERYLFgsABJog4AAUABIAAAD1/yAAAJQREb8fvx8ABJYg4AAUAAUACQD1/yAA
APgAAAAAAAAAAMAg4AAUABMAAAD1/yAAAPQAAAAAAAAAAMAg4AAUABQAAAD1/yAAANQAYQAA
Ph8AAMAg4AAUABUAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAABACAAACASEkAgQCAAAsAg
4AAUAAAAAAABACAAACASEUAgQCAAAsAg4AAUAAAAAAABACAAACAAAAAAAAAAAsAg4AAUAAAA
AAABACAAACACAEAAAAAAAsAg4AAUAAAAAAABACgAADAAAAAAAAAAAsAg4AAUAAAAAAABACAA
AGACAEAAAAAABg0g4AAUAAAAAAABACAAAGACAEAAAAAABigg4AAUAAAAAAABACAAACAAIAAA
ACAAAsAg4AAUAAAAAAABACgAADABAkAAQAAAAsAg4AAUAAAAAAABACgAADABAEAAAAAAAsAg
4AAUAAAAAAABACgAADACAkAAQAAAAsAg4AAUAAAAAAABACgAADAhAkAgQAAAAsAg4AAUAAAA
AAABACgAADACAEAAAAAAAsAg4AAUAAAAAAABACgAADAhAEAgAAAAAsAg4AAUABQAAAABACgA
ADgBAkAAQAAAAsAg4AAUABQAAAABACgAADgBAEAAAAAAAsAg4AAUABQAAAABACgAADgCAkAA
QAAAAsAg4AAUABQAAAABACgAADghAkAgQAAAAsAg4AAUABQAAAABACgAADgCAEAAAAAAAsAg
4AAUABQAAAABACgAADghAEAgAAAAAsAg4AAUAAAAAAABACgAAHAiIkAgQCAABigg4AAUAAAA
AAABACgAADAiIkAgQCAAAsAg4AAUAAAAAAABACgAAHAiIkAgQCAABg0g4AAUABQAAAABACgA
AHgiIkAgQCAABg0g4AAUAAAAAAABACgAAHAiIkAgQCAABiQg4AAUABQAAAABACgAAHgiIkAg
QCAABiQg4AAUAAAAAAABACgAAHAiIkAgQCAABgkg4AAUABQAAAABACAAAAgAAAAAAAAAAsAg
4AAUABQAAAABACAAACgCAkAAQAAAAsAg4AAUABYAAAABABgAADgAIgAAQCAAAsAg4AAUAAAA
AAABACAAACAgAAAgAAAAAsAg4AAUAAAAAAABACAAACAgIAAgACAAAsAg4AAUAAAAAAABACgA
AHAiIkAgQCAABjIg4AAUAAAAAAABACgAAHACIkAAQCAABg0g4AAUAAAAAAABACAAAGACIEAA
ACAABjIg4AAUAAAAAAABACgAAHAiIkAgQCAAAsAg4AAUAAAAAAABACgAAHAiIkAgQCAABh8g
4AAUAAAAAAABACgAAHAgIgAgQCAABgkg4AAUAAAAAAABACgAAHAiIkAgQCAABhsg4AAUABQA
AAABACgAAHgiIkAgQCAABgkg4AAUAAAAAAABACAAAGASEUAgQCAABgkg4AAUAAAAAAABACgA
AHABAEAAAAAABgkg4AAUAAAAAAABACgAAHAAAAAAAAAABgkg4AAUAAAAAAABACAAAEAAAAAA
AAAABgkg4AAUAAAAAAABACgAAHAiIkAgQCAABjUg4AAUABQAAAABACgAAHgiIkAgQCAABjUg
4AAUAAAAAAABACgAAHAAAAAAAAAABjUg4AAUAAAAAAABACgAAHACIkAAQCAABjUg4AAUAAAA
AAABACgAAHACIkAAQCAABgkg4AAUAAAAAAABACgAAHAgIgAgQCAABjUg4AAUAAAAAAABACgA
ADACIkAAQCAAAsAg4AAUAAAAAAABACgAADAiAkAgQAAAAsAg4AAUAAYAAAABACgAAHgiAkAg
QAAABigg4AAUAAAAAAABACgAAHAiAkAgQAAABigg4AAUAAAAAAABACgAAHAiAkAgQAAABiQg
4AAUAAAAAAABACgAAHAiAkAgQAAABhsg4AAUABQAAAABACgAAHgiAkAgQAAABiQg4AAUAAAA
AAABACgAAHAiAkAgQAAABgkg4AAUAAAAAAABACgAAHACAkAAQAAABgkg4AAUAAYAAAABACgA
AHgiIkAgQCAABgkg4AAUAAYAAAABACgAAHgiIkAgQCAABjUg4AAUAAAAAAABACAAAGAAAAAA
AAAABgkg4AAUAAAAAAABACgAAHACAEAAAAAABgkg4AAUAAAAAAABACgAADABIEAAACAAAsAg
4AAUABQAAAABACAAAGgCAEAAAAAABgkg4AAUAAAAAAABACAAAGACAEAAAAAABgkg4AAUABQA
AAABACgAADgBEkAAQCAAAsAg4AAUABQAAAABACgAADgBEUAAQCAAAsAg4AAUABcAAAABACgA
ADgBEUAAQCAAAsAg4AAUABcAAAABACgAAHgBEUAAQCAABjUg4AAUABcAAAABACgAADgREUAg
QCAAAsAg4AAUABYAAAABABoAADgCIkAAQCAAAsAg4AAUABYAAAABABoAADgAIgAAQCAAAsAg
4AAUABYAAAABABoAADggIgAgQCAAAsAg4AAUABYAAAABABoAADgCIEAAACAAAsAg4AAUABYA
AAABABoAADgAIAAAACAAAsAg4AAUABYAAAABABoAAHgCIkAAQCAABgog4AAUABYAAAABABoA
AHgAIgAAQCAABgog4AAUABYAAAABABoAAHggIgAgQCAABgog4AAUAAAAAAABACAAAGACAEAA
AAAABhsg4AAUAAAAAAABACAAAGAAAAAAAAAAAsAg4AAUAAAAAAABACAAAGACAEAAAAAABiQg
fAgUAHwIAAAAAAAAAAAAAAAAkAA0n75WfQgtAH0IAAAAAAAAAAAAAAAAAAAAAAIADQAUAAMA
AAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAAEAAAACAA0AFAADAAAAAQAA
ACMjMC4wMFwgDgAFAAJ9CC0AfQgAAAAAAAAAAAAAAAACAAAAAgANABQAAwAAAAEAAAAjIzAu
MDBcIA4ABQACfQgtAH0IAAAAAAAAAAAAAAAAAwAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAO
AAUAAn0ILQB9CAAAAAAAAAAAAAAAAAQAAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9
CC0AfQgAAAAAAAAAAAAAAAAFAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQgtAH0I
AAAAAAAAAAAAAAAABgAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAA
AAAAAAAAAAcAAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CC0AfQgAAAAAAAAAAAAA
AAAIAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAAAAAACQAA
AAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAAoAAAACAA0A
FAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CC0AfQgAAAAAAAAAAAAAAAALAAAAAgANABQAAwAA
AAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAAAAAADAAAAAIADQAUAAMAAAABAAAA
IyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAA0AAAACAA0AFAADAAAAAQAAACMjMC4w
MFwgDgAFAAJ9CC0AfQgAAAAAAAAAAAAAAAAOAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4A
BQACfQgtAH0IAAAAAAAAAAAAAAAADwAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0I
QQB9CAAAAAAAAAAAAAAAABAAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwBl
ZgQAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAABEAAAADAA0AFAADAAAAAQAAACMjMC4w
MFwgDgAFAAIEABQAAwBlZgUAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAABIAAAADAA0A
FAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwBlZgYAAAAgX2tfcl8tO30IQQB9CAAAAAAA
AAAAAAAAABMAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwBlZgcAAAAgX2tf
cl8tO30IQQB9CAAAAAAAAAAAAAAAABQAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIE
ABQAAwBlZggAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAABUAAAADAA0AFAADAAAAAQAA
ACMjMC4wMFwgDgAFAAIEABQAAwBlZgkAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAABYA
AAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwDMTAQAAAAgX2tfcl8tO30IQQB9
CAAAAAAAAAAAAAAAABcAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwDMTAUA
AAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAABgAAAADAA0AFAADAAAAAQAAACMjMC4wMFwg
DgAFAAIEABQAAwDMTAYAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAABkAAAADAA0AFAAD
AAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwDMTAcAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAA
AAAAABoAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwDMTAgAAAAgX2tfcl8t
O30IQQB9CAAAAAAAAAAAAAAAABsAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQA
AwDMTAkAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAABwAAAADAA0AFAADAAAAAAAAACMj
MC4wMFwgDgAFAAIEABQAAwAyMwQAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAB0AAAAD
AA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAwAyMwUAAAAgX2tfcl8tO30IQQB9CAAA
AAAAAAAAAAAAAB4AAAADAA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAwAyMwYAAAAg
X2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAB8AAAADAA0AFAADAAAAAAAAACMjMC4wMFwgDgAF
AAIEABQAAwAyMwcAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAACAAAAADAA0AFAADAAAA
AAAAACMjMC4wMFwgDgAFAAIEABQAAwAyMwgAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAA
ACEAAAADAA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAwAyMwkAAAAgX2tfcl8tO30I
QQB9CAAAAAAAAAAAAAAAACIAAAADAA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAwAA
AAQAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAACMAAAADAA0AFAADAAAAAAAAACMjMC4w
MFwgDgAFAAIEABQAAwAAAAUAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAACQAAAADAA0A
FAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAwAAAAYAAAAgX2tfcl8tO30IQQB9CAAAAAAA
AAAAAAAAACUAAAADAA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAwAAAAcAAAAgX2tf
cl8tO30IQQB9CAAAAAAAAAAAAAAAACYAAAADAA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIE
ABQAAwAAAAgAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAACcAAAADAA0AFAADAAAAAAAA
ACMjMC4wMFwgDgAFAAIEABQAAwAAAAkAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAACgA
AAADAA0AFAACAAAAnAAG/yMjMC4wMFwgDgAFAAIEABQAAgAAAP/Hzv8gX2tfcl8tO30IkQB9
CAAAAAAAAAAAAAAAACkAAAAHAA0AFAACAAAA+n0A/yMjMC4wMFwgDgAFAAIEABQAAgAAAPLy
8v8gX2tfcl8tOwcAFAACAAAAf39//yAgICAgICAgCAAUAAIAAAB/f3//ICAgICAgICAJABQA
AgAAAH9/f/8AAAAAAAAAAAoAFAACAAAAf39//wAAAAAAAAAAfQiRAH0IAAAAAAAAAAAAAAAA
KgAAAAcADQAUAAMAAAAAAAAAIyMwLjAwXCAOAAUAAgQAFAACAAAApaWl/yBfa19yXy07BwAU
AAIAAAA/Pz//ICAgICAgICAIABQAAgAAAD8/P/8gICAgICAgIAkAFAACAAAAPz8//wAAAAAA
AAAACgAUAAIAAAA/Pz//AAAAAAAAAAB9CC0AfQgAAAAAAAAAAAAAAAArAAAAAgANABQAAwAA
AAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAAAAAALAAAAAIADQAUAAMAAAABAAAA
IyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAC0AAAACAA0AFAADAAAAAQAAACMjMC4w
MFwgDgAFAAJ9CC0AfQgAAAAAAAAAAAAAAAAuAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4A
BQACfQgtAH0IAAAAAAAAAAAAAAAALwAAAAIADQAUAAIAAAB/f3//IyMwLjAwXCAOAAUAAn0I
QQB9CAAAAAAAAAAAAAAAADAAAAADAA0AFAACAAAAAGEA/yMjMC4wMFwgDgAFAAIEABQAAgAA
AMbvzv8gX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAADEAAAADAA0AFAADAAAAAwAAACMjMC4w
MFwgDgAFAAIIABQAAwAAAAQAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAADIAAAADAA0A
FAADAAAAAwAAACMjMC4wMFwgDgAFAAIIABQAAwD/PwQAAAAgX2tfcl8tO30IQQB9CAAAAAAA
AAAAAAAAADMAAAADAA0AFAADAAAAAwAAACMjMC4wMFwgDgAFAAIIABQAAwAyMwQAAAAgX2tf
cl8tO30ILQB9CAAAAAAAAAAAAAAAADQAAAACAA0AFAADAAAAAwAAACMjMC4wMFwgDgAFAAJ9
CJEAfQgAAAAAAAAAAAAAAAA1AAAABwANABQAAgAAAD8/dv8jIzAuMDBcIA4ABQACBAAUAAIA
AAD/zJn/IF9rX3JfLTsHABQAAgAAAH9/f/8gICAgICAgIAgAFAACAAAAf39//yAgICAgICAg
CQAUAAIAAAB/f3//AAAAAAAAAAAKABQAAgAAAH9/f/8AAAAAAAAAAH0IQQB9CAAAAAAAAAAA
AAAAADYAAAADAA0AFAACAAAA+n0A/yMjMC4wMFwgDgAFAAIIABQAAgAAAP+AAf8gX2tfcl8t
O30IQQB9CAAAAAAAAAAAAAAAADcAAAADAA0AFAACAAAAnGUA/yMjMC4wMFwgDgAFAAIEABQA
AgAAAP/rnP8gX2tfcl8tO30IkQB9CAAAAAAAAAAAAAAAADgAAAAHAA0AFAADAAAAAQAAACMj
MC4wMFwgDgAFAAIEABQAAgAAAP//zP8gX2tfcl8tOwcAFAACAAAAsrKy/yAgICAgICAgCAAU
AAIAAACysrL/ICAgICAgICAJABQAAgAAALKysv8AAAAAAAAAAAoAFAACAAAAsrKy/wAAAAAA
AAAAfQiRAH0IAAAAAAAAAAAAAAAAOQAAAAcADQAUAAIAAAA/Pz//IyMwLjAwXCAOAAUAAgQA
FAACAAAA8vLy/yBfa19yXy07BwAUAAIAAAA/Pz//ICAgICAgICAIABQAAgAAAD8/P/8gICAg
ICAgIAkAFAACAAAAPz8//wAAAAAAAAAACgAUAAIAAAA/Pz//AAAAAAAAAAB9CC0AfQgAAAAA
AAAAAAAAAAA6AAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAA
AAAAOwAAAAIADQAUAAMAAAADAAAAIyMwLjAwXCAOAAUAAX0IVQB9CAAAAAAAAAAAAAAAADwA
AAAEAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIHABQAAwAAAAQAAAAgX2tfcl8tOwgAFAAD
AAAABAAAACAgICAgICAgfQgtAH0IAAAAAAAAAAAAAAAAPQAAAAIADQAUAAIAAAD/AAD/IyMw
LjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAD4AAAACAA0AFAADAAAAAQAAACMjMC4wMFwg
DgAFAAJ9CC0AfQgAAAAAAAAAAAAAAAA/AAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQAC
fQgtAH0IAAAAAAAAAAAAAAAAQAAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9
CAAAAAAAAAAAAAAAAEEAAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CC0AfQgAAAAA
AAAAAAAAAABCAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQhBAH0IAAAAAAAAAAAA
AAAAQwAAAAMADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAgQAFAACAAAA//8A/yBfa19yXy07
fQhBAH0IAAAAAAAAAAAAAAAARAAAAAMADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAgQAFAAC
AAAAALDw/yBfa19yXy07fQgtAH0IAAAAAAAAAAAAAAAARQAAAAIADQAUAAMAAAABAAAAIyMw
LjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAEYAAAACAA0AFAADAAAAAQAAACMjMC4wMFwg
DgAFAAJ9CC0AfQgAAAAAAAAAAAAAAABHAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQAC
fQgtAH0IAAAAAAAAAAAAAAAASAAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9
CAAAAAAAAAAAAAAAAEkAAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CC0AfQgAAAAA
AAAAAAAAAABKAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAA
AAAASwAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAEwA
AAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CC0AfQgAAAAAAAAAAAAAAABNAAAAAgAN
ABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAAAAAATgAAAAIADQAUAAMA
AAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAE8AAAACAA0AFAADAAAAAQAA
ACMjMC4wMFwgDgAFAAJ9CC0AfQgAAAAAAAAAAAAAAABQAAAAAgANABQAAwAAAAEAAAAjIzAu
MDBcIA4ABQACfQgtAH0IAAAAAAAAAAAAAAAAUQAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAO
AAUAAn0IQQB9CAAAAAAAAAAAAAAAAFIAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIE
ABQAAgAAAACw8P8gX2tfcl8tO30ILQB9CAAAAAAAAAAAAAAAAFMAAAACAA0AFAADAAAAAQAA
ACMjMC4wMFwgDgAFAAJ9CEEAfQgAAAAAAAAAAAAAAABUAAAAAwANABQAAwAAAAEAAAAjIzAu
MDBcIA4ABQACBAAUAAIAAAD//wD/IF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABVAAAAAwAN
ABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAIAAAD//wD/IF9rX3JfLTt9CEEAfQgAAAAA
AAAAAAAAAABWAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAMjMHAAAAIF9r
X3JfLTt9CEEAfQgAAAAAAAAAAAAAAABXAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQAC
BAAUAAMAMjMHAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABYAAAAAwANABQAAwAAAAEA
AAAjIzAuMDBcIA4ABQACBAAUAAMAAAAAAAAAIF9rX3JfLTt9CC0AfQgAAAAAAAAAAAAAAABZ
AAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAAAAAAWgAAAAIA
DQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAAAFsAAAACAA0AFAAD
AAAAAQAAACMjMC4wMFwgDgAFAAJ9CC0AfQgAAAAAAAAAAAAAAABcAAAAAgANABQAAwAAAAEA
AAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAAAAAAXQAAAAIADQAUAAMAAAABAAAAIyMw
LjAwXCAOAAUAAn0IQQB9CAAAAAAAAAAAAAAAAF4AAAADAA0AFAADAAAAAQAAACMjMC4wMFwg
DgAFAAIEABQAAgAAAJLQUP8gX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAF8AAAADAA0AFAAD
AAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAgAAAP//AP8gX2tfcl8tO30IQQB9CAAAAAAAAAAA
AAAAAGAAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAgAAAJLQUP8gX2tfcl8t
O30ILQB9CAAAAAAAAAAAAAAAAGEAAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CEEA
fQgAAAAAAAAAAAAAAABiAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAZWYE
AAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABjAAAAAwANABQAAwAAAAEAAAAjIzAuMDBc
IA4ABQACBAAUAAMAAAAAAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABkAAAAAwANABQA
AwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAZWYIAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAA
AAAAAABlAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAAAAAAIF9rX3Jf
LTt9CEEAfQgAAAAAAAAAAAAAAABmAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAU
AAMAAAAAAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABnAAAAAwANABQAAwAAAAEAAAAj
IzAuMDBcIA4ABQACBAAUAAMAAAAAAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABoAAAA
AwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAAAAAAIF9rX3JfLTt9CEEAfQgA
AAAAAAAAAAAAAABpAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAAAAAA
IF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABqAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4A
BQACBAAUAAMAAAAJAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABrAAAAAwANABQAAwAA
AAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAJAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAA
AABsAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAJAAAAIF9rX3JfLTt9
CEEAfQgAAAAAAAAAAAAAAABtAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMA
AAAJAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABuAAAAAwANABQAAwAAAAEAAAAjIzAu
MDBcIA4ABQACBAAUAAMAAAAAAAAAIF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAABvAAAAAwAN
ABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAJAAAAIF9rX3JfLTt9CC0AfQgAAAAA
AAAAAAAAAABwAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAAAAAA
AAAAcQAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0IQQB9CAAAAAAAAAAAAAAAAHIA
AAADAA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAgAAAACw8P8gX2tfcl8tO30IQQB9
CAAAAAAAAAAAAAAAAHMAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAgAAAACw
8P8gX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAHQAAAADAA0AFAADAAAAAQAAACMjMC4wMFwg
DgAFAAIEABQAAwAyMwcAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAHUAAAADAA0AFAAD
AAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwBlZggAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAA
AAAAAHYAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQAAwAyMwcAAAAgX2tfcl8t
O30IQQB9CAAAAAAAAAAAAAAAAHcAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAIEABQA
AwAAAAAAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAHgAAAADAA0AFAADAAAAAQAAACMj
MC4wMFwgDgAFAAIEABQAAwAAAAAAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAHkAAAAD
AA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAwAAAAAAAAAgX2tfcl8tO30IQQB9CAAA
AAAAAAAAAAAAAHoAAAADAA0AFAADAAAAAAAAACMjMC4wMFwgDgAFAAIEABQAAwAAAAkAAAAg
X2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAHsAAAADAA0AFAADAAAAAQAAACMjMC4wMFwgDgAF
AAIEABQAAwAAAAAAAAAgX2tfcl8tO30IQQB9CAAAAAAAAAAAAAAAAHwAAAADAA0AFAADAAAA
AQAAACMjMC4wMFwgDgAFAAIEABQAAwAAAAAAAAAgX2tfcl8tO30ILQB9CAAAAAAAAAAAAAAA
AH0AAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CEEAfQgAAAAAAAAAAAAAAAB+AAAA
AwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAAAAAAIF9rX3JfLTt9CEEAfQgA
AAAAAAAAAAAAAAB/AAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAAAAAA
IF9rX3JfLTt9CC0AfQgAAAAAAAAAAAAAAACAAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4A
BQACfQgtAH0IAAAAAAAAAAAAAAAAgQAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0I
LQB9CAAAAAAAAAAAAAAAAIIAAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CEEAfQgA
AAAAAAAAAAAAAACDAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAAAAJAAAA
IF9rX3JfLTt9CC0AfQgAAAAAAAAAAAAAAACEAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4A
BQACfQgtAH0IAAAAAAAAAAAAAAAAhQAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0I
LQB9CAAAAAAAAAAAAAAAAIYAAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CC0AfQgA
AAAAAAAAAAAAAACHAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQgtAH0IAAAAAAAA
AAAAAAAAiAAAAAIADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAn0ILQB9CAAAAAAAAAAAAAAA
AIkAAAACAA0AFAADAAAAAQAAACMjMC4wMFwgDgAFAAJ9CEEAfQgAAAAAAAAAAAAAAACKAAAA
AwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAIAAAD/AAD/IF9rX3JfLTt9CEEAfQgA
AAAAAAAAAAAAAACLAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACBAAUAAIAAAD/AAD/
IF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAACMAAAAAwANABQAAwAAAAEAAAAjIzAuMDBcIA4A
BQACBAAUAAIAAAD/AAD/IF9rX3JfLTt9CEEAfQgAAAAAAAAAAAAAAACNAAAAAwANABQAAwAA
AAEAAAAjIzAuMDBcIA4ABQACBAAUAAMAZWYIAAAAIF9rX3JfLTt9CC0AfQgAAAAAAAAAAAAA
AACOAAAAAgANABQAAwAAAAEAAAAjIzAuMDBcIA4ABQACfQhBAH0IAAAAAAAAAAAAAAAAjwAA
AAMADQAUAAMAAAABAAAAIyMwLjAwXCAOAAUAAgQAFAADADIzBwAAACBfa19yXy07kwISABAA
DQAAMjAlIC0gQWNjZW50MZIITQCSCAAAAAAAAAAAAAABBB7/DQAyADAAJQAgAC0AIABBAGMA
YwBlAG4AdAAxAAAAAwABAAwABwRlZtvl8f8FAAwABwEAAAAAAP8lAAUAApMCEgARAA0AADIw
JSAtIEFjY2VudDKSCE0AkggAAAAAAAAAAAAAAQQi/w0AMgAwACUAIAAtACAAQQBjAGMAZQBu
AHQAMgAAAAMAAQAMAAcFZWby3dz/BQAMAAcBAAAAAAD/JQAFAAKTAhIAEgANAAAyMCUgLSBB
Y2NlbnQzkghNAJIIAAAAAAAAAAAAAAEEJv8NADIAMAAlACAALQAgAEEAYwBjAGUAbgB0ADMA
AAADAAEADAAHBmVm6vHd/wUADAAHAQAAAAAA/yUABQACkwISABMADQAAMjAlIC0gQWNjZW50
NJIITQCSCAAAAAAAAAAAAAABBCr/DQAyADAAJQAgAC0AIABBAGMAYwBlAG4AdAA0AAAAAwAB
AAwABwdlZuXg7P8FAAwABwEAAAAAAP8lAAUAApMCEgAUAA0AADIwJSAtIEFjY2VudDWSCE0A
kggAAAAAAAAAAAAAAQQu/w0AMgAwACUAIAAtACAAQQBjAGMAZQBuAHQANQAAAAMAAQAMAAcI
ZWbb7vP/BQAMAAcBAAAAAAD/JQAFAAKTAhIAFQANAAAyMCUgLSBBY2NlbnQ2kghNAJIIAAAA
AAAAAAAAAAEEMv8NADIAMAAlACAALQAgAEEAYwBjAGUAbgB0ADYAAAADAAEADAAHCWVm/enZ
/wUADAAHAQAAAAAA/yUABQACkwISABYADQAANDAlIC0gQWNjZW50MZIITQCSCAAAAAAAAAAA
AAABBB//DQA0ADAAJQAgAC0AIABBAGMAYwBlAG4AdAAxAAAAAwABAAwABwTMTLjM5P8FAAwA
BwEAAAAAAP8lAAUAApMCEgAXAA0AADQwJSAtIEFjY2VudDKSCE0AkggAAAAAAAAAAAAAAQQj
/w0ANAAwACUAIAAtACAAQQBjAGMAZQBuAHQAMgAAAAMAAQAMAAcFzEzmubj/BQAMAAcBAAAA
AAD/JQAFAAKTAhIAGAANAAA0MCUgLSBBY2NlbnQzkghNAJIIAAAAAAAAAAAAAAEEJ/8NADQA
MAAlACAALQAgAEEAYwBjAGUAbgB0ADMAAAADAAEADAAHBsxM1+S8/wUADAAHAQAAAAAA/yUA
BQACkwISABkADQAANDAlIC0gQWNjZW50NJIITQCSCAAAAAAAAAAAAAABBCv/DQA0ADAAJQAg
AC0AIABBAGMAYwBlAG4AdAA0AAAAAwABAAwABwfMTMzA2v8FAAwABwEAAAAAAP8lAAUAApMC
EgAaAA0AADQwJSAtIEFjY2VudDWSCE0AkggAAAAAAAAAAAAAAQQv/w0ANAAwACUAIAAtACAA
QQBjAGMAZQBuAHQANQAAAAMAAQAMAAcIzEy23ej/BQAMAAcBAAAAAAD/JQAFAAKTAhIAGwAN
AAA0MCUgLSBBY2NlbnQ2kghNAJIIAAAAAAAAAAAAAAEEM/8NADQAMAAlACAALQAgAEEAYwBj
AGUAbgB0ADYAAAADAAEADAAHCcxM/NW0/wUADAAHAQAAAAAA/yUABQACkwISABwADQAANjAl
IC0gQWNjZW50MZIITQCSCAAAAAAAAAAAAAABBCD/DQA2ADAAJQAgAC0AIABBAGMAYwBlAG4A
dAAxAAAAAwABAAwABwQyM5Wz1/8FAAwABwAAAP////8lAAUAApMCEgAdAA0AADYwJSAtIEFj
Y2VudDKSCE0AkggAAAAAAAAAAAAAAQQk/w0ANgAwACUAIAAtACAAQQBjAGMAZQBuAHQAMgAA
AAMAAQAMAAcFMjPZl5X/BQAMAAcAAAD/////JQAFAAKTAhIAHgANAAA2MCUgLSBBY2NlbnQz
kghNAJIIAAAAAAAAAAAAAAEEKP8NADYAMAAlACAALQAgAEEAYwBjAGUAbgB0ADMAAAADAAEA
DAAHBjIzwtaa/wUADAAHAAAA/////yUABQACkwISAB8ADQAANjAlIC0gQWNjZW50NJIITQCS
CAAAAAAAAAAAAAABBCz/DQA2ADAAJQAgAC0AIABBAGMAYwBlAG4AdAA0AAAAAwABAAwABwcy
M7Khx/8FAAwABwAAAP////8lAAUAApMCEgAgAA0AADYwJSAtIEFjY2VudDWSCE0AkggAAAAA
AAAAAAAAAQQw/w0ANgAwACUAIAAtACAAQQBjAGMAZQBuAHQANQAAAAMAAQAMAAcIMjOTzd3/
BQAMAAcAAAD/////JQAFAAKTAhIAIQANAAA2MCUgLSBBY2NlbnQ2kghNAJIIAAAAAAAAAAAA
AAEENP8NADYAMAAlACAALQAgAEEAYwBjAGUAbgB0ADYAAAADAAEADAAHCTIz+sCQ/wUADAAH
AAAA/////yUABQACkwIMACIABwAAQWNjZW50MZIIQQCSCAAAAAAAAAAAAAABBB3/BwBBAGMA
YwBlAG4AdAAxAAAAAwABAAwABwQAAE+Bvf8FAAwABwAAAP////8lAAUAApMCDAAjAAcAAEFj
Y2VudDKSCEEAkggAAAAAAAAAAAAAAQQh/wcAQQBjAGMAZQBuAHQAMgAAAAMAAQAMAAcFAADA
UE3/BQAMAAcAAAD/////JQAFAAKTAgwAJAAHAABBY2NlbnQzkghBAJIIAAAAAAAAAAAAAAEE
Jf8HAEEAYwBjAGUAbgB0ADMAAAADAAEADAAHBgAAm7tZ/wUADAAHAAAA/////yUABQACkwIM
ACUABwAAQWNjZW50NJIIQQCSCAAAAAAAAAAAAAABBCn/BwBBAGMAYwBlAG4AdAA0AAAAAwAB
AAwABwcAAIBkov8FAAwABwAAAP////8lAAUAApMCDAAmAAcAAEFjY2VudDWSCEEAkggAAAAA
AAAAAAAAAQQt/wcAQQBjAGMAZQBuAHQANQAAAAMAAQAMAAcIAABLrMb/BQAMAAcAAAD/////
JQAFAAKTAgwAJwAHAABBY2NlbnQ2kghBAJIIAAAAAAAAAAAAAAEEMf8HAEEAYwBjAGUAbgB0
ADYAAAADAAEADAAHCQAA95ZG/wUADAAHAAAA/////yUABQACkwIIACgAAwAAQmFkkgg5AJII
AAAAAAAAAAAAAAEBG/8DAEIAYQBkAAAAAwABAAwABf8AAP/Hzv8FAAwABf8AAJwABv8lAAUA
ApMCEAApAAsAAENhbGN1bGF0aW9ukgiBAJIIAAAAAAAAAAAAAAECFv8LAEMAYQBsAGMAdQBs
AGEAdABpAG8AbgAAAAcAAQAMAAX/AADy8vL/BQAMAAX/AAD6fQD/JQAFAAIGAA4ABf8AAH9/
f/8BAAcADgAF/wAAf39//wEACAAOAAX/AAB/f3//AQAJAA4ABf8AAH9/f/8BAJMCDwAqAAoA
AENoZWNrIENlbGySCH8AkggAAAAAAAAAAAAAAQIX/woAQwBoAGUAYwBrACAAQwBlAGwAbAAA
AAcAAQAMAAX/AAClpaX/BQAMAAcAAAD/////JQAFAAIGAA4ABf8AAD8/P/8GAAcADgAF/wAA
Pz8//wYACAAOAAX/AAA/Pz//BgAJAA4ABf8AAD8/P/8GAJMCBAArgAP/kgggAJIIAAAAAAAA
AAAAAAEFA/8FAEMAbwBtAG0AYQAAAAAAkwIEACyABv+SCCgAkggAAAAAAAAAAAAAAQUG/wkA
QwBvAG0AbQBhACAAWwAwAF0AAAAAAJMCBAAtgAT/kggmAJIIAAAAAAAAAAAAAAEFBP8IAEMA
dQByAHIAZQBuAGMAeQAAAAAAkwIEAC6AB/+SCC4AkggAAAAAAAAAAAAAAQUH/wwAQwB1AHIA
cgBlAG4AYwB5ACAAWwAwAF0AAAAAAJMCFQAvABAAAEV4cGxhbmF0b3J5IFRleHSSCEcAkggA
AAAAAAAAAAAAAQI1/xAARQB4AHAAbABhAG4AYQB0AG8AcgB5ACAAVABlAHgAdAAAAAIABQAM
AAX/AAB/f3//JQAFAAKTAgkAMAAEAABHb29kkgg7AJIIAAAAAAAAAAAAAAEBGv8EAEcAbwBv
AGQAAAADAAEADAAF/wAAxu/O/wUADAAF/wAAAGEA/yUABQACkwIOADEACQAASGVhZGluZyAx
kghHAJIIAAAAAAAAAAAAAAEDEP8JAEgAZQBhAGQAaQBuAGcAIAAxAAAAAwAFAAwABwMAAB9J
ff8lAAUAAgcADgAHBAAAT4G9/wUAkwIOADIACQAASGVhZGluZyAykghHAJIIAAAAAAAAAAAA
AAEDEf8JAEgAZQBhAGQAaQBuAGcAIAAyAAAAAwAFAAwABwMAAB9Jff8lAAUAAgcADgAHBP8/
qMDe/wUAkwIOADMACQAASGVhZGluZyAzkghHAJIIAAAAAAAAAAAAAAEDEv8JAEgAZQBhAGQA
aQBuAGcAIAAzAAAAAwAFAAwABwMAAB9Jff8lAAUAAgcADgAHBDIzlbPX/wIAkwIOADQACQAA
SGVhZGluZyA0kgg5AJIIAAAAAAAAAAAAAAEDE/8JAEgAZQBhAGQAaQBuAGcAIAA0AAAAAgAF
AAwABwMAAB9Jff8lAAUAApMCCgA1AAUAAElucHV0kgh1AJIIAAAAAAAAAAAAAAECFP8FAEkA
bgBwAHUAdAAAAAcAAQAMAAX/AAD/zJn/BQAMAAX/AAA/P3b/JQAFAAIGAA4ABf8AAH9/f/8B
AAcADgAF/wAAf39//wEACAAOAAX/AAB/f3//AQAJAA4ABf8AAH9/f/8BAJMCEAA2AAsAAExp
bmtlZCBDZWxskghLAJIIAAAAAAAAAAAAAAECGP8LAEwAaQBuAGsAZQBkACAAQwBlAGwAbAAA
AAMABQAMAAX/AAD6fQD/JQAFAAIHAA4ABf8AAP+AAf8GAJMCDAA3AAcAAE5ldXRyYWySCEEA
kggAAAAAAAAAAAAAAQEc/wcATgBlAHUAdAByAGEAbAAAAAMAAQAMAAX/AAD/65z/BQAMAAX/
AACcZQD/JQAFAAKTAgQAAIAA/5IIMwCSCAAAAAAAAAAAAAABAQD/BgBOAG8AcgBtAGEAbAAA
AAIABQAMAAcBAAAAAAD/JQAFAAKTAgkAOAAEAABOb3RlkghiAJIIAAAAAAAAAAAAAAECCv8E
AE4AbwB0AGUAAAAFAAEADAAF/wAA///M/wYADgAF/wAAsrKy/wEABwAOAAX/AACysrL/AQAI
AA4ABf8AALKysv8BAAkADgAF/wAAsrKy/wEAkwILADkABgAAT3V0cHV0kgh3AJIIAAAAAAAA
AAAAAAECFf8GAE8AdQB0AHAAdQB0AAAABwABAAwABf8AAPLy8v8FAAwABf8AAD8/P/8lAAUA
AgYADgAF/wAAPz8//wEABwAOAAX/AAA/Pz//AQAIAA4ABf8AAD8/P/8BAAkADgAF/wAAPz8/
/wEAkwIEADqABf+SCCQAkggAAAAAAAAAAAAAAQUF/wcAUABlAHIAYwBlAG4AdAAAAAAAkwIK
ADsABQAAVGl0bGWSCDEAkggAAAAAAAAAAAAAAQMP/wUAVABpAHQAbABlAAAAAgAFAAwABwMA
AB9Jff8lAAUAAZMCCgA8AAUAAFRvdGFskghNAJIIAAAAAAAAAAAAAAEDGf8FAFQAbwB0AGEA
bAAAAAQABQAMAAcBAAAAAAD/JQAFAAIGAA4ABwQAAE+Bvf8BAAcADgAHBAAAT4G9/wYAkwIR
AD0ADAAAV2FybmluZyBUZXh0kgg/AJIIAAAAAAAAAAAAAAECC/8MAFcAYQByAG4AaQBuAGcA
IABUAGUAeAB0AAAAAgAFAAwABf8AAP8AAP8lAAUAAo4IWACOCAAAAAAAAAAAAACQAAAAEQAR
AFQAYQBiAGwAZQBTAHQAeQBsAGUATQBlAGQAaQB1AG0AOQBQAGkAdgBvAHQAUwB0AHkAbABl
AEwAaQBnAGgAdAAxADYAYAECAAAAhQAOAF1NAAAAAAYAU2hlZXQ0mggYAJoIAAAAAAAAAAAA
AAEAAAAAAAAAAgAAAKMIEACjCAAAAAAAAAAAAAAAAAAAjAAEAAEALgDBAQgAwQEAAB3rAQD8
AO4DIwAAACMAAAAuAABPQU0gQWNyb255bXMgZHJhZnQtaWV0Zi1vcHNhd2ctbXBscy10cC1v
YW0tZGVmLgAATVBMUy1UUCBGcmFtZXdvcmsgZHJhZnQtaWV0Zi1tcGxzLXRwLWZyYW1ld29y
az4AAE1QTFMtVFAgU3Vydml2YWJpbGl0eSBGcmFtZXdvcmsgZHJhZnQtaWV0Zi1tcGxzLXRw
LXN1cnZpdmUtZndrNQAATVBMUy1UUCBJZGVudGlmaWVycyBkcmFmdC1pZXRmLW1wbHMtdHAt
aWRlbnRpZmllcnMtMDA2AABNUExTLVRQIE9BTSBGcmFtZXdvcmsgZHJhZnQtaWV0Zi1tcGxz
LXRwLW9hbS1mcmFtZXdvcmsGAABMZWdlbmQLAABJRVNHIHJldmlldxYAAGRyYWZ0IHdpdGgg
dGhlIGF1dGhvcnMMAAB3ZyBsYXN0IGNhbGwJAABWZXN0aW9uIDQsAABBQ0gtVExWIHN0cnVj
dHVyZSBkcmFmdC1pZXRmLW1wbHMtdHAtYWNoLXRsdggAAE1hciA4LTE0CQAATWFyIDE1LTIx
CQAATWFyIDIyLTI4DgAATWFyIDI5IC0gQXByIDQKAABBcHIgNSAtIDExCwAAQXByIDE5IC0g
MjULAABBcHIgMTIgLSAxOA4AAEFwciAyNiAtIE1heSAyCQAATWF5IDMgLSA5CwAATWF5IDEw
IC0gMTYLAABNYXkgMTcgLSAyMwsAAE1heSAyNCAtIDMwDgAATWF5IDMxIC0gSnVuIDYKAABK
dW4gNyAtIDEzEQAAc2hlcGhlcmQgd3JpdGUgdXAwAABNUExTLVRQIERhdGEgcGxhbmUgZHJh
ZnQtaWV0Zi1tcGxzLXRwLWRhdGEtcGxhbmUmAABJRVNHICAtIFByb2Nlc3Npbmcgb2YgdGhl
IE9QU0FXRyBEcmFmdCYAAElFU0cgLSBQcm9jZXNzaW5nIG9mIE1QTFMtVFAgRnJhbWV3b3Jr
KAAASUVTRyBQcm9jZXNzaW5nIG9mIE1QTFMtVFAgT0FNIEZyYW1ld29yazMAAElFU0cgUHJv
Y2Vzc2luZyBvZiBNUExTLVRQIFN1cnZpdmVhYmlsaXR5IEZyYW1ld29yaycAAElFU0cgUHJv
Y2Vzc2luZyBvZiBNUExTLVRQIEFyY2hpdGVjdHVyZSQAAElFU0cgUHJvY2Vzc2luZyBvZiBB
Q0gtVExWIHN0cnVjdHVyZSYAAElFU0cgUHJvY2Vzc2luZyBvZiBNUExTLVRQIElkZW50aWZp
ZXJzHwAAImZpbmFsIiB3b3JraW5nIGdyb3VwIGxhc3QgY2FsbP8AKgAIAO9IAAAMAAAAM0oA
AFABAAC+SgAA2wEAADJLAABPAgAAY0wAAIADAABjCBYAYwgAAAAAAAAAAAAAFgAAAAAAAAAC
AJYIEACWCAAAAAAAAAAAAABC5QEAmwgQAJsIAAAAAAAAAAAAAAEAAACMCBAAjAgAAAAAAAAA
AAAAAAAAAAoAAAAJCBAAAAYQAKofzQfJAAEABgQAAAsCGAAAAAAAAAAAACMAAACldwAAAZkA
AGmbAAANAAIAAQAMAAIAZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIAAQAqAAIAAAAr
AAIAAACCAAIAAQCAAAgAAAAAAAAAAAAlAgQAAAAsAYEAAgDBBBQAAAAVAAAAgwACAAAAhAAC
AAAAJgAIAGZmZmZmZuY/JwAIAGZmZmZmZuY/KAAIAAAAAAAAAOg/KQAIAAAAAAAAAOg/TQAg
IAAAXABcAGUAcwBlAGEAbABtAHcANQA4ADQAXABrAGkAOAA0ADAAOQAyADAAMwBhAGMAbwAA
AAAAAAAAAAAAAAAAAAEEAAbcAEgoU/+AAwEACQCaCzQIZAABAOkEWAICAAIAWAIDAAEAQQA0
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAABAAAAAgAAAAEBAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAFBSSVbiMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAAAAAAAQJxAnECcA
ABAnAAAAAAAAAABoCTwMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwAAAAAAAAAMHBAAXEsD
AGhDBAAAAAAAAAAAAAEAAQAAAAAAAAAAAAAAAAAAAAAA/VWo8EUAAAAAAAAAAQAFAP8A/wAA
AAEAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABQADAAQAAwAEAAQABAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQABAAEAAQABAAEAAQAB
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABoCQAAU01USgAAAAAQAFgJSABQACAAQwBv
AGwAbwByACAATABhAHMAZQByAEoAZQB0ACAANAA3ADAAMAAgAFAAUwAAAEhQT3JpZW50YXRp
b24ASFBPcmllbnRhdGlvblBvcnRyYWl0AEhQT3JpZW50Um90YXRlMTgwAEZhbHNlAER1cGxl
eABEdXBsZXhOb1R1bWJsZQBQYWdlU2l6ZQBBNABQYWdlUmVnaW9uAABMZWFkaW5nRWRnZQAA
SW5wdXRTbG90ACpVc2VGb3JtVHJheVRhYmxlAE1lZGlhVHlwZQBQTEFJTgBDb2xsYXRlAFRy
dWUAT3V0cHV0QmluAFN0YXBsZXIAU3RhcGxlTG9jYXRpb24ATm9uZQBUZXh0QXNCbGFjawBG
YWxzZQBIUENvbG9yQXNHcmF5AEZhbHNlAEFsdGVybmF0ZUxldHRlckhlYWQARmFsc2UASFBQ
YXBlclNpemVBTE1Db25zdHJhaW50cwBFTlZfMTAASkNMUmVzb2x1dGlvbgA2MDBkcGkASkNM
SFBQcmludEluR3JheVNjYWxlAEZhbHNlAEpDTEhQUHJpbnRPbkJvdGhTaWRlc01hbnVhbGx5
AEZhbHNlAFByaW50UXVhbGl0eUdyb3VwAFBRR3JvdXBfMQBIUENvbG9yU21hcnQAQXV0b21h
dGljAEhQQ29sb3JTbWFydF9Db2xvck9wdGlvbnNfRWRnZUNvbnRyb2wATm9ybWFsAEhQQ29s
b3JTbWFydF9UZXh0X05ldXRyYWxHcmF5cwBCbGFja09ubHkASFBDb2xvclNtYXJ0X1RleHRf
SGFsZnRvbmUARGV0YWlsAEhQQ29sb3JTbWFydF9HcmFwaGljc19OZXV0cmFsR3JheXMAQmxh
Y2tPbmx5AEhQQ29sb3JTbWFydF9HcmFwaGljc19IYWxmdG9uZQBEZXRhaWwASFBDb2xvclNt
YXJ0X1Bob3RvX05ldXRyYWxHcmF5cwA0LUNvbG9yAEhQQ29sb3JTbWFydF9QaG90b19IYWxm
dG9uZQBEZXRhaWwASFBDb2xvck1vZGUAQ09MT1JfTU9ERQBIUFBKTEVuY29kaW5nAFVURjgA
SFBKb2JBY2NvdW50aW5nAEhQSk9CQUNDVF9KT0JBQ05UX0NPTE9SQVVUSABIUEJvcm5PbkRh
dGUASFBCT0QASFBKb2JCeUpvYk92ZXJyaWRlAEpCSk8ASFBYTUxGaWxlVXNlZABocGM0NzAw
cy54bWwASFBTbWFydER1cGxleFNpbmdsZVBhZ2VKb2IAVHJ1ZQBIUFNtYXJ0RHVwbGV4T2Rk
UGFnZUpvYgBUcnVlAEhQTWFudWFsRHVwbGV4RGlhbG9nSXRlbXMASW5zdHJ1Y3Rpb25JRF8w
MV9GQUNFRE9XTi1OT1JPVEFURQBIUE1hbnVhbEZlZWRPcmllbnRhdGlvbgBGQUNFVVAASFBP
dXRwdXRCaW5PcmllbnRhdGlvbgBGQUNFRE9XTgBIUE1hbnVhbER1cGxleERpYWxvZ01vZGVs
AE1vZGVsZXNzAEhQTWFwTWFudWFsRmVlZFRvVHJheTEAVHJ1ZQBIUE1hbnVhbER1cGxleFBh
Z2VSb3RhdGUARHJpdmVyUm90YXRlAEpSQ29uc3RyYWludHMASlJDSERQYXJ0aWFsAEpSSERJ
bnN0YWxsZWQASlJIRE9mZgBKUkhETm90SW5zdGFsbGVkAEpSSERPZmYASFBOVXNlRGlmZkZp
cnN0UGFnZUNob2ljZQBUcnVlAEhQUGFnZUV4Y2VwdGlvbnNGaWxlAEhQWlBFNWluAEhQUGFn
ZUV4Y2VwdGlvbnNJbnRlcmZhY2UAU2hvd1BhZ2VFeGNlcHRpb25zAEhQUGFnZUV4Y2VwdGlv
bnNMb3dFbmQASFBQYWdlRXhjZXB0aW9uc0xvd0VuZFZlcgBIUFBhZ2VFeGNlcHRpb25zAENv
dmVySW5zZXJ0aW9uAEhQUGFwZXJTaXplRHVwbGV4Q29uc3RyYWludHMAQTUASFBNZWRpYVR5
cGVEdXBsZXhDb25zdHJhaW50cwBFWFRSQV9IRUFWWQBIUER1cGxpY2F0ZUpvYk5hbWVPdmVy
cmlkZQBTV0ZXAFBTQWxpZ25tZW50RmlsZQBIUFpMUzVpbgBQU1NlcnZpY2VzX0RldmljZWFu
ZFN1cHBsaWVzU3RhdHVzAFRSVUUAUFNTZXJ2aWNlc19QcmludGNvbG9ydXNhZ2Vqb2Jsb2cA
VFJVRQBIUFNtYXJ0SHViX09ubGluZWRpYWdub3N0aWN0b29scwBUUlVFAEhQU21hcnRIdWJf
U3VwcG9ydGFuZHRyb3VibGVzaG9vdGluZwBUUlVFAEhQU21hcnRIdWJfUHJvZHVjdG1hbnVh
bHMAVFJVRQBIUFNtYXJ0SHViX0NoZWNrZm9yZHJpdmVydXBkYXRlcwBUUlVFAEhQU21hcnRI
dWJfQ29sb3JwcmludGluZ2FjY2Vzc3VzYWdlAFRSVUUASFBTbWFydEh1Yl9PcmRlcnN1cHBs
aWVzAFRSVUUAUFNTZXJ2aWNlc09wdGlvbgBQcm5TdGF0X1NJRF8yNDJfQklEXzI3MF9ISURf
MTU1MjEASFBTbWFydEh1YgBJbmV0X1NJRF8yNjNfQklEXzI3Nl9ISURfMjY1AFBvc3RTY3Jp
cHRDdXN0b21QYWdlU2l6ZQBGYWxzZQBIUENvbnN1bWVyQ3VzdG9tUGFwZXIAVHJ1ZQBIUEVu
YWJsZVJBV1Nwb29saW5nAFRydWUASFBEb2NQcm9wUmVzb3VyY2VEYXRhAEhQQ2FiRmlsZU5h
bWUAUkdCQ29sb3IARGVmYXVsdC1zUkdCAENNWUtJbmtzAERlZmF1bHRDTVlLKwAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAwcAABJVVBIEwABAHic7ZnPaxNREMe/m4BYW2mhRz3kYmkPBpQc1Iqy7r7+oNWu
acGA9RBMKoGaSBKxx/ZQSv+FXrzbP6GXHPsHeBVvKv4F4kW/s9mF3U23QSiNTecTJm/em3m7
gbfvzcxm7CbgGm9hEhaEDCVL6fa6ZCO6RY8Kvy2OZgI/aW0U0I8RHIwWrgJ/Isj8K31n9sdK
tGnk8BJ1NChVvDqD+yoXC13/y42NJmooY3PQP0QZCBKlvEAPY0Wn04m1UUYCv0qPZfvxafdJ
xqEMB7JWPE4lfQyWscIn1MYzuKddXBlSHnLt36PN+PSWZ1SbJ9VrPBr0j1LOGStFkrbknJhu
9dpPmiv6eMRfdCvQJT8P/UKfqD2keHQdkteLKEpIGPMURVEEOQ4c5jitIMvJMRuXiqzOfg6r
rMrbft5Txxv6KMPIv4SESuD/1M+Fm3xmWpQN/2lZYbvhj1fZM9jyNa3sFWXYWMMH7vvb3P01
nglVSg7TcBlJ3nHHV7n3Z2KxpBtBzhcplvLj6fZvlGtj6fbvlN+j6Xb5n+XjBGBKjlnOm5IJ
xtPqxbOUsO6L1oHRNkqsPtzmJ8DBA6z7a9Tg2jRR9uP/HNdKVrBFW79Tfj3Wu4O7HDEo8cry
7izv6wbK/43E6AZXv8w92vteVRl2DGzudIfZvnJ50RdDSpdFz3bc4gt3dd5ec2xv8cbs4dxe
4YfZ+fz13uTz2aWeCbWDL7tTv8z+rZ/3P01sHXvekwXbFL0TLq0oiqIoiqIoiqJcEP4C7Ud2
9gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAA8AAYJAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAoQAiAAkAZAABAAEAAQACAFgCWAIzMzMzMzPTPzMzMzMzM9M/AQCcCCYAnAgA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADwzAAAAAAAAAABVAAIACAB9AAwAAQABAJIkDwAC
AAAAfQAMAAIAAgAkBQ8AAgAAAH0ADAADAGIAtgMPAAIAAAB9AAwAYwBjAJIDDwACAAAAfQAM
AGQAZAC2Aw8AAwAAAH0ADABlAGUAJAQPAAIAAAAAAg4AAAAAACMAAAAAAHAAAAAIAhAAAAAA
AHAAhgEAAAAAwAFZIAgCEAABAAAAcAAsAQAAAAAAAQ8ACAIQAAIAAABwADsBAAAAAAABDyAI
AhAAAwAAAHAAhQIAAAAAAAEPIAgCEAAEAAAAcACFAgAAAAAAAQ8gCAIQAAUAAABwAEoBAAAA
AIABaSAIAhAABgAAAHAAhQIAAAAAAAEPIAgCEAAHAAAAcACFAgAAAAAAAQ8gCAIQAAgAAABw
AEoBAAAAAAABDyAIAhAACQAAAHAAhQIAAAAAAAEPIAgCEAAKAAAAcACFAgAAAAAAAQ8gCAIQ
AAsAAABwAEoBAAAAAAABDyAIAhAADAAAAHAAhQIAAAAAAAEPIAgCEAANAAAAcACFAgAAAAAA
AQ8gCAIQAA4AAABwAEoBAAAAAIABaSAIAhAADwAAAHAAhQIAAAAAAAEPIAgCEAAQAAAAbwCF
AgAAAAAAAQ8gCAIQABEAAABvAEoBAAAAAAABDyAIAhAAEgAAAG8AhQIAAAAAAAEPIAgCEAAT
AAAAbwCFAgAAAAAAAQ8gCAIQABQAAABvAEoBAAAAAAABDyAIAhAAFQAAAG8AhQIAAAAAAAEP
IAgCEAAWAAAAbwCFAgAAAAAAAQ8gCAIQABcAAABvAEoBAAAAAAABDyAIAhAAGAAAAG8ALAEA
AAAAAAEPAAgCEAAZAAAAbwAsAQAAAAAAAQ8ACAIQABoAAABvACwBAAAAAAABDwAIAhAAGwAA
AG8ALAEAAAAAAAEPAAgCEAAcAAAAbwAsAQAAAAAAAQ8ACAIQAB0AAABvACwBAAAAAAABDwAI
AhAAHgAAAG8ALAEAAAAAAAEPAAgCEAAfAAAAbwAsAQAAAAAAAQ8AAQIGAAAAAABaAP0ACgAA
AAEAWwAJAAAAAQIGAAAAAgBbAP0ACgAAAAMAhQALAAAAvgASAAAABACGAIYAhgCGAIYAhwAJ
AP0ACgAAAAoAhQAMAAAAvgASAAAACwCGAIYAhgCGAIYAhwAQAP0ACgAAABEAigANAAAAvgAS
AAAAEgCLAIsAiwCLAIsAjAAXAP0ACgAAABgAhQAOAAAAvgASAAAAGQCGAIYAhgCGAIYAhwAe
AP0ACgAAAB8AhQAPAAAAvgASAAAAIACGAIYAhgCGAIYAhwAlAP0ACgAAACYAhQARAAAAvgAS
AAAAJwCGAIYAhgCGAIYAhwAsAP0ACgAAAC0AhQAQAAAAvgASAAAALgCGAIYAhgCGAIYAhwAz
AP0ACgAAADQAhQASAAAAvgASAAAANQCGAIYAhgCGAIYAhwA6AP0ACgAAADsAhQATAAAAvgAS
AAAAPACGAIYAhgCGAIYAhwBBAP0ACgAAAEIAhQAUAAAAvgASAAAAQwCGAIYAhgCGAIYAhwBI
AP0ACgAAAEkAhQAVAAAAvgASAAAASgCGAIYAhgCGAIYAhwBPAP0ACgAAAFAAhQAWAAAAvgAS
AAAAUQCGAIYAhgCGAIYAhwBWAP0ACgAAAFcAhQAXAAAAvgASAAAAWACGAIYAhgCGAIYAhwBd
AP0ACgAAAF4AiAAYAAAAvgAWAAAAXwCJAIkAiQCJAIkAiQCJAH4AZgC+ANQAAQAAAD4AgABG
AEgARgBGAEYARgBGAEkASABGAEYARgBGAEYASQBIAEYARgBGAEYARgBJAEgARgBGAEYARgBG
AEkASABGAEYARgBGAEYASQBIAEYARgBGAEYARgBJAEgARgBGAEYARgBGAEkASABGAEYARgBG
AEYASQBOAEwATABMAEwATABPAEgARgBGAEYARgBGAEkASABGAEYARgBGAEYASQBIAEYARgBG
AEYARgBJAEgARgBGAEYARgBGAEkASABGAEYARgBGAEYARgBGAH8AZgC+ANQAAgAAAD8AgQBH
AEoARwBHAEcARwBHAEsASgBHAEcARwBHAEcASwBKAEcARwBHAEcARwBLAEoARwBHAEcARwBH
AEsASgBHAEcARwBHAEcASwBKAEcARwBHAEcARwBLAEoARwBHAEcARwBHAEsASgBHAEcARwBH
AEcASwBQAE0ATQBNAE0ATQBRAEoARwBHAEcARwBHAEsASgBHAEcARwBHAEcASwBKAEcARwBH
AEcARwBLAEoARwBHAEcARwBHAEsASgBHAEcARwBHAEcARwB9AH8AZgABAgYAAwAAAD8A/QAK
AAMAAQCCAAAAAAC+ANAAAwACAEcAUwBTAFMAUwBTAFMAUwBTAFMAUwBTAFMAUwBTAFMAUwBT
AFMAUwBTAFMAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAVgBW
AFYAVgBWAFYAVgBYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAGUAZQBlAGUAZQBl
AGUAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFMAUwBTAFMAUwBTAFMAUwBTAFMAUwBC
AHAAfwBmAAECBgAEAAAAPwD9AAoABAABAIIAGwAAAL4A0AAEAAIARwBTAFMAUwBTAFMAUwBT
AFMAUwBTAFMAUwBTAFMAUwBTAFMAUwBTAFMAUwBYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABeAF4AVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFUAVQBV
AFUAVQBVAFUAVABUAFQAVABUAFQAVABUAFQAVABUAFQAWABYAFgAWABYAFgAWABYAFgAUwBT
AFMAUwBTAFMAUwBTAFMAUwBTAEIAcAB/AGYAvgDUAAUAAABmAIMAZwBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAawBrAGsAawBrAGsAawBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGwAbQB/AGYAAQIGAAYAAAA/AP0ACgAGAAEAggABAAAAvgDQ
AAYAAgBHAFYAVgBWAFYAVgBWAFYAVgBWAFYAVgBWAFYAVgBWAFYAVgBWAFYAVgBWAFYAVgBW
AFYAVgBWAFYAZABkAGQAZABkAGQAZABkAGQAZABkAGQAZABkAFYAVgBWAFYAVgBWAFYAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABlAGUAZQBlAGUAZQBlAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFMAUwBTAFMAQgBwAH8AZgABAgYABwAA
AD8A/QAKAAcAAQCCABwAAAC+ANAABwACAEcAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABeAF4AVABUAFQAVABUAFQAVABUAFQAVABU
AFQAVABUAFUAVQBVAFUAVQBVAFUAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAGUAZQBl
AGUAZQBlAGUAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAUwBT
AFMAUwBCAHAAfwBmAL4A1AAIAAAAPwCDAEcAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGsAawBr
AGsAawBrAGsAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBsAG0AfwBmAAECBgAJAAAAPwD9AAoACQABAIIABAAAAL4A0AAJAAIARwBSAFIAUgBS
AFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFYAVgBWAFYAVgBW
AFYAVgBWAFYAYgBiAGIAYgBiAGIAYgBiAGIAYgBiAGIAYgBiAFYAVgBWAFcAVwBXAFcAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAGUAZQBlAGUAZQBl
AGUAWABYAFgAWABYAFgAWABYAFgAWABhAEIAcAB/AGYAAQIGAAoAAAA/AP0ACgAKAAEAggAd
AAAAvgDgAAoAAgBHAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABeAF4AVABUAFQAVABUAFQAVABUAFQAVABU
AFQAVABUAFQAVABUAFQAVABUAFQAVQBVAFUAVQBVAFUAVQBUAFQAVABUAFQAWABYAFgAWABY
AFgAWABYAFgAZQBlAGUAZQBlAGUAZQBYAFgAWABYAFgAWABYAGEAYQBhAGEAQgBwAH8AQABA
AEAAQABAAEAAQABAAG4AvgDkAAsAAAA/AIMARwBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGsAawBrAGsAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGsAawBrAGsAawBrAGsAagBqAGoAagBqAGoAagBq
AGoAagBqAGwAbQB/AEAAQABAAEAAQABAAEAAQABuAAECBgAMAAAAPwD9AAoADAABAIIAAgAA
AL4A4gAMAAIARwBTAFMAUwBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBS
AFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAVgBWAFYAVgBWAFYAVgBWAFYAVgBWAFYAVgBW
AGQAZABkAGQAZABkAGQAZABkAGQAZABkAGQAZABXAFcAVwBXAFcAVwBXAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAbgB8AGgAaABo
AGgAaABoAGgAaABpAG8AAQIGAA0AAAA/AP0ACgANAAEAggAeAAAAvgDgAA0AAgBHAFMAUwBT
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAXgBeAFQAVABUAFQAVABU
AFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABfAFQAVABUAFQAVABU
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABuAHwAaABoAGgAaABoAGgAaABoAG4AvgDk
AA4AAABmAIMAZwBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBrAGsAawBrAGsAawBrAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAbQB8AGgAaABo
AGgAaABoAGgAaABuAAECBgAPAAAAPwD9AAoADwABAIIAGgAAAL4A4AAPAAIARwBYAFgAWABY
AFgAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBS
AFIAUgBSAFIAVgBWAFYAVgBWAFYAVgBWAFYAVgBWAFYAVgBWAFYAVgBkAGQAZABkAGQAZABk
AGQAZABkAGQAZABkAGQAVwBXAFcAVwBXAFcAVwBXAGUAZQBlAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAbgB8AGgAewBAAEAAQABAAEAAQABuAAECBgAQ
AAAAPwD9AAoAEAABAIIAHwAAAL4A4AAQAAIARwBYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAF4AXgBUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABU
AFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABYAFgAWABYAFgAWABYAG4AWABj
AFgAWABYAGgAbgB8AGgAQABAAEAAQABAAEAAQABuAL4A5AARAAAAPwCDAEcAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGsAawBr
AGsAawBrAGsAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBtAGoAbwBqAGoAagBsAG0AfABoAEAAQABAAEAAQABAAEAAbgABAgYAEgAA
AD8A/QAKABIAAQCCAAoAAAC+AOAAEgACAEcAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBS
AFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAUgBSAFIAVgBWAFYAVgBW
AFYAVgBWAFYAVgBWAFYAVgBWAGQAZABkAGQAZABkAGQAZABkAGQAZABkAGQAZABXAFcAVwBX
AFcAVwBXAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABuAFgAYwBT
AFMAUwBCAHAAfwBAAEAAQABAAEAAQABAAEAAbgABAgYAEwAAAD8A/QAKABMAAQCCACAAAAC+
AOAAEwACAEcAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AF4AXgBUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABU
AFQAVABUAFQAVABUAFQAWABuAFgAYwBYAFgAWABuAFgAYwBTAFMAUwBCAHAAfwBAAEAAQABA
AEAAQABAAEAAbgC+AOQAFAAAAD8AgwBHAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAawBrAGsAawBrAGsAawBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAbQBqAG8AagBq
AGoAbABtAH8AQABAAEAAQABAAEAAQABAAG4AAQIGABUAAAA/AP0ACgAVAAEAggADAAAAvgDg
ABUAAgBHAHEAcQBxAHEAcgBzAHMAcwBzAHMAcwBzAHMAcwBzAHMAcwBzAHMAcwBzAHMAcwBz
AHMAcwBzAHMAcwBzAHMAcwBzAHMAcwB0AHQAdAB0AHQAdAB0AHQAdAB0AHQAdAB0AHQAdQB1
AHUAdQB1AHUAdQB1AHUAdQB1AHUAdQB1AHYAdgB2AHYAdgB2AHYAdwB3AHcAdwB3AHcAdwB3
AHcAdwB3AHcAdwB3AHcAdwB3AHcAdwB3AHcAdwB3AHcAdwB3AHcAdwB4AHwAaABAAEAAQABA
AEAAQABAAG4AAQIGABYAAABBAP0ACgAWAAEAhAAhAAAAvgDSABYAAgBCAFMAUwBTAFMAeQBY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAWABYAFgAXgBeAFQAVABUAFQAVABUAFQAVABU
AFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFQAVABUAFgAWABY
AFgAWABYAFgAWABYAFgAWABYAFgAWABuAHwAaABnAL4A1gAXAAAAQQCEAEIAagBqAGoAagB6
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGsAawBr
AGsAawBrAGsAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBqAGoAagBq
AGoAagBqAGoAagBqAGoAagBqAGoAagBqAG0AfABoAGcAvgDSABgAAABBAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAXABlAL4A0gAZAAAAQQBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAFwAZQC+ANIAGgAAAEEAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBcAGUAvgDSABsAAABBAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBCAEIAQgBC
AEIAQgBCAEIAQgBCAEIAQgBCAEIAXABlAAECBgAcAAAAQQD9AAoAHAABAEAABQAAAL4AzgAc
AAIAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAXABlAAECBgAdAAAAQwD9
AAoAHQABAEAABgAAAL4AzgAdAAIAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAXABlAAECBgAeAAAAjwD9AAoAHgABAEAABwAAAL4AzgAeAAIAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAXABlAAECBgAfAAAARAD9AAoAHwABAEAACAAAAL4AzgAf
AAIAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAXABlANcARADkIAAAbAIe
AtgA2ADsAOwA2ADsAOwA2ADsAPwA6AD+APwA6AD8APwA6AD8APwA6AD8AO4A2gDWANYA1gDW
AOoA6gDqAAgCEAAgAAAAZgAsAQAAAAAAAQ8ACAIQACEAAABmADsBAAAAAAABDyAIAhAAIgAA
AGYALAEAAAAAAAEPAAECBgAgAAAAjQD9AAoAIAABAI4AIgAAAL4AzgAgAAIAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQABA
AEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAXABlAAECBgAhAAAAYAD9AAoAIQABAEUAGQAA
AL4AzgAhAAIARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBF
AEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBF
AEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBF
AEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUARQBFAEUAXQBlAL4ADAAi
AGMAQABAAEAAZQDXAAoAIAIAACgA6gDqAD4CEgC2Bg0AAABAAAAAAABkAGUAAACLCBAAiwgA
AAAAAAAAAAAAAABiAB0ADwADGwAEAAAAAQAbABsABATlAHIADgAAAAAAUABWAAAAAABXAF0A
AAAAACYALAAAAAAALQAzAAAAAAA0ADoAAAAAADsAQQAAAAAAQgBIAAAAAABJAE8AAAAAAF4A
ZQAAAAAAAwAJAAAAAAAKABAAAAAAABEAFwAAAAAAGAAeAAAAAAAfACUAZwgXAGcIAAAAAAAA
AAAAAAIAAf////8DRAAACgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAgAAAAMAAAD+////BQAAAAYAAAAHAAAA
/v///wkAAAD+////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////7/
AAAGAQIAAAAAAAAAAAAAAAAAAAAAAAEAAADghZ/y+U9oEKuRCAArJ7PZMAAAAKAAAAAHAAAA
AQAAAEAAAAAEAAAASAAAAAgAAABYAAAAEgAAAGgAAAAMAAAAgAAAAA0AAACMAAAAEwAAAJgA
AAACAAAA5AQAAB4AAAAIAAAAZWxvYWFuZAAeAAAACAAAAGVsb2FhbmQAHgAAABAAAABNaWNy
b3NvZnQgRXhjZWwAQAAAAADCssb/tsoBQAAAAABUKHJKzcoBAwAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAABgECAAAAAAAAAAAA
AAAAAAAAAAABAAAAAtXN1ZwuGxCTlwgAKyz5rjAAAACwAAAACAAAAAEAAABIAAAAFwAAAFAA
AAALAAAAWAAAABAAAABgAAAAEwAAAGgAAAAWAAAAcAAAAA0AAAB4AAAADAAAAIsAAAACAAAA
5AQAAAMAAAAAAAwACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAAeEAAAAQAAAAcA
AABTaGVldDQADBAAAAIAAAAeAAAACwAAAFdvcmtzaGVldHMAAwAAAAEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQBDAG8AbQBwAE8AYgBqAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAgD///////////////8AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAcgAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA////////////////AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD/////////////
//8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAP7/
AwoAAP////8gCAIAAAAAAMAAAAAAAABGJgAAAE1pY3Jvc29mdCBPZmZpY2UgRXhjZWwgMjAw
MyBXb3Jrc2hlZXQABgAAAEJpZmY4AA4AAABFeGNlbC5TaGVldC44APQ5snEAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
--------------060800030206020104050907--
