From pce-bounces@lists.ietf.org Thu Dec 01 18:50:08 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EhyBk-0003nk-9O; Thu, 01 Dec 2005 18:50:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EhyBf-0003kw-0Q; Thu, 01 Dec 2005 18:50:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03045;
	Thu, 1 Dec 2005 18:49:15 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EhyWE-0003iK-IK; Thu, 01 Dec 2005 19:11:18 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EhyBd-00048a-Tu; Thu, 01 Dec 2005 18:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EhyBd-00048a-Tu@newodin.ietf.org>
Date: Thu, 01 Dec 2005 18:50:01 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-reqs-00.txt 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.

	Title		: PCE Communication Protocol (PCECP) specific
                          requirements for Inter-Area (G)MPLS Traffic 
                          Engineering 
	Author(s)	: J. Le Roux
	Filename	: draft-ietf-pce-pcecp-interarea-reqs-00.txt
	Pages		: 19
	Date		: 2005-12-1
	
   For scalability purposes a network may comprise multiple IGP areas. 
   An inter-area TE-LSP is an LSP that transits through at least two IGP 
   areas. In a multi-area network, topology visibility remains local to 
   a given area, and a head-end LSR cannot compute alone an inter-area 
   shortest constrained path. One key application of the Path 
   Computation Element (PCE) architecture is the computation of inter-
   area TE-LSP paths. In this context, this document lists a detailed 
   set of PCE Communication Protocol (PCECP) specific requirements for 
   support of inter-area TE-LSP path computation. It complements generic 
   requirements for a PCE Communication Protocol. 

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcecp-interarea-reqs-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pce-pcecp-interarea-reqs-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pce-pcecp-interarea-reqs-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-12-1154910.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pce-pcecp-interarea-reqs-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pce-pcecp-interarea-reqs-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-12-1154910.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--NextPart--




From pce-bounces@lists.ietf.org Wed Dec 07 17:36:58 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ek7uE-0005z9-GI; Wed, 07 Dec 2005 17:36:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ek7uD-0005xd-Ju
	for pce@megatron.ietf.org; Wed, 07 Dec 2005 17:36:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11207
	for <pce@ietf.org>; Wed, 7 Dec 2005 17:36:04 -0500 (EST)
Received: from relay1.mail.uk.clara.net ([80.168.70.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ek8Fz-0003sS-GY
	for pce@ietf.org; Wed, 07 Dec 2005 17:59:28 -0500
Received: from du-069-0207.access.clara.net ([217.158.132.207] helo=Puppy)
	by relay1.mail.uk.clara.net with esmtp (Exim 4.46)
	id 1Ek7uA-000JaK-HA for pce@ietf.org; Wed, 07 Dec 2005 22:36:55 +0000
Message-ID: <01c501c5fb7f$3431bb60$9d849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Wed, 7 Dec 2005 22:40:14 -0000
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.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Pce] Liaison statement from ITU-T SG15
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

Hi,

There was a liaison to us from the recent meeting of Questions 12 and 14
of Study Group 15 of the ITU-T.

It was in response to our communication about the formation of the PCE
working group and the work we are doing. No further response from us is
required, but we will obviously keep the ITU-T in the loop as we go
forward.

You can see the liaison at the IETF's liaison tracker
https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=152

Thanks,
Adrian


_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Fri Dec 09 18:50:40 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eks0e-0004CY-Aj; Fri, 09 Dec 2005 18:50:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eks06-0003ml-9R; Fri, 09 Dec 2005 18:50:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29311;
	Fri, 9 Dec 2005 18:49:10 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Eks0K-0003uH-Of; Fri, 09 Dec 2005 18:50:21 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1Eks02-00086r-7p; Fri, 09 Dec 2005 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Eks02-00086r-7p@newodin.ietf.org>
Date: Fri, 09 Dec 2005 18:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-architecture-03.txt 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.

	Title		: Path Computation Element (PCE) Architecture
	Author(s)	: A. Farrel, et al.
	Filename	: draft-ietf-pce-architecture-03.txt
	Pages		: 37
	Date		: 2005-12-9
	
Constraint-based path computation is a fundamental building block for
   traffic engineering systems such as Multiprotocol Label Switching
   (MPLS) and Generalized Multiprotocol Label Switching (GMPLS)
   networks. Path computation in large, multi-domain, multi-region or
   multi-layer networks is complex and may require special
   computational components and cooperation between the different
   network domains.

   This document specifies the architecture for a Path Computation
   Element (PCE)-based model to address this problem space. This
   document does not attempt to provide a detailed description of all
   the architectural components, but rather it describes a set of
   building blocks for the PCE architecture from which solutions may be
   constructed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-architecture-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pce-architecture-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pce-architecture-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-12-9165208.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pce-architecture-03.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pce-architecture-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-12-9165208.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--NextPart--




From pce-bounces@lists.ietf.org Mon Dec 19 18:32:07 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EoUUB-0002uM-Aw; Mon, 19 Dec 2005 18:32:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EoUUA-0002u5-EP
	for pce@megatron.ietf.org; Mon, 19 Dec 2005 18:32:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06120
	for <pce@ietf.org>; Mon, 19 Dec 2005 18:31:03 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EoUWS-0003X0-AW for pce@ietf.org; Mon, 19 Dec 2005 18:34:29 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-2.cisco.com with ESMTP; 19 Dec 2005 15:31:56 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id jBJNVtQg015741
	for <pce@ietf.org>; Mon, 19 Dec 2005 15:31:55 -0800 (PST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Mon, 19 Dec 2005 18:31:34 -0500
Received: from [192.168.1.101] ([10.86.242.107]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 19 Dec 2005 18:31:34 -0500
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Transfer-Encoding: 7bit
Message-Id: <2DD8AA26-799C-43D4-ABA7-615D5396EB11@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: pce@ietf.org
From: JP Vasseur <jvasseur@cisco.com>
Date: Mon, 19 Dec 2005 18:31:00 -0500
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 19 Dec 2005 23:31:34.0617 (UTC)
	FILETIME=[59777490:01C604F4]
X-Spam-Score: 2.2 (++)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Pce] Working Group Last call on draft-ietf-pce-architecture-03.txt
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

Hi,

A new revision of draft-ietf-pce-architecture has been edited  
addressing several comments related to the Policy aspects, which  
requires a new Working Group Last Call.

This email initiates a working group last call on draft-ietf-pce- 
architecture-03.txt.

The last call will end on January 3 at noon EST.

Please send your comments to the mailing list and copy the chairs.

Thanks.

JP.


_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Wed Dec 28 03:05:59 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ErWJr-0005FS-43; Wed, 28 Dec 2005 03:05:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ErWFb-0004Mj-1D
	for pce@megatron.ietf.org; Wed, 28 Dec 2005 03:01:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03492
	for <pce@ietf.org>; Wed, 28 Dec 2005 03:00:22 -0500 (EST)
Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ErW4s-0003Tt-8C
	for pce@ietf.org; Wed, 28 Dec 2005 02:50:31 -0500
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IS7000JV76UJ8@szxga03-in.huawei.com> for
	pce@ietf.org; Wed, 28 Dec 2005 15:52:06 +0800 (CST)
Received: from szxml02-in ([172.24.1.6])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IS7001IF76TL1@szxga03-in.huawei.com> for
	pce@ietf.org; Wed, 28 Dec 2005 15:52:06 +0800 (CST)
Received: from z18605 ([10.111.12.87])
	by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IS700IYR7EUCE@szxml02-in.huawei.com>; Wed,
	28 Dec 2005 15:56:54 +0800 (CST)
Date: Wed, 28 Dec 2005 15:03:36 +0800
From: Zhang Renhai <zhangrenhai@huawei.com>
To: LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@francetelecom.com>
Message-id: <000001c60b7f$14a2bf00$570c6f0a@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: pce@ietf.org
Subject: [Pce] Comment on draft-ietf-pce-pcecp-interarea-reqs-00.txt
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1026787875=="
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============1026787875==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_V7ijof//P7NiPAOtkYRZ0A)"

This is a multi-part message in MIME format.

--Boundary_(ID_V7ijof//P7NiPAOtkYRZ0A)
Content-type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7BIT

Hi, Jean-Louis

 I have some comment on the draft draft-ietf-pce-pcecp-interarea-reqs-00.txt

 In section 7.11.1, In case of network failure, jittering will be used to avoid
simultaneous requests sent to one PCE. Could more consideration be given here to
the preemptment, becouse the jittering timeout is stochastic, some lower request
may be served before a higher request and the path may be calculated differently.
which may increase the probability of a preemptment.

 I have always been thinking a question: if a PCC will not perform the CSPF 
computation, why does it still maintain the TEDB any longer? which may consume 
a lot of memory and CPU of a LSR.This question dost not aid at this draft.

 In inter-area environment,sometimes, a PCC may wish to get as many paths as possible,
for all kinds of purpose,so could the PCC send the request to more than one PCEs? 

Regards,
Zhang 

--Boundary_(ID_V7ijof//P7NiPAOtkYRZ0A)
Content-type: text/html; charset=gb2312
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 5.50.4807.2300" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Hi, Jean-Louis</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>&nbsp;I have some comment on the draft 
draft-ietf-pce-pcecp-interarea-reqs-00.txt</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>&nbsp;In section 7.11.1, In case of network failure, jittering 
will be used to avoid</FONT></DIV>
<DIV><FONT size=2>simultaneous requests sent to one PCE.&nbsp;Could more 
consideration be given here to</FONT></DIV>
<DIV><FONT size=2>the preemptment, becouse the jittering timeout is stochastic, 
some lower request</FONT></DIV>
<DIV><FONT size=2>may be served before a higher request and the path may be 
calculated differently.</FONT></DIV>
<DIV><FONT size=2>which may increase the probability&nbsp;of a 
preemptment.</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>&nbsp;I have always been thinking a question: if a PCC will 
not perform the CSPF&nbsp;</FONT></DIV>
<DIV><FONT size=2>computation, why does it still maintain the TEDB any longer? 
which may consume </FONT></DIV>
<DIV><FONT size=2>a lot of </FONT><FONT size=2>memory and CPU of a LSR.This 
question dost not aid&nbsp;at this draft.</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>&nbsp;In inter-area environment,s</FONT><FONT size=2>ometimes, 
a PCC may wish to get as many paths as possible,</FONT></DIV>
<DIV><FONT size=2>for all kinds of purpose,so could the PCC </FONT><FONT 
size=2>send the request to more than one PCEs? </FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>Regards,</FONT></DIV>
<DIV><FONT size=2>Zhang </FONT></DIV></BODY></HTML>

--Boundary_(ID_V7ijof//P7NiPAOtkYRZ0A)--


--===============1026787875==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--===============1026787875==--




From pce-bounces@lists.ietf.org Wed Dec 28 10:50:26 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ErdZK-0002p8-Dn; Wed, 28 Dec 2005 10:50:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ErdYy-0002i5-Dq; Wed, 28 Dec 2005 10:50:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20298;
	Wed, 28 Dec 2005 10:48:54 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Erdd1-0003an-2H; Wed, 28 Dec 2005 10:54:16 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ErdYv-0004Ji-Q6; Wed, 28 Dec 2005 10:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ErdYv-0004Ji-Q6@newodin.ietf.org>
Date: Wed, 28 Dec 2005 10:50:01 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-comm-protocol-gen-reqs-03.txt 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.

	Title		: PCE Communication Protocol Generic Requirements
	Author(s)	: J. Le Roux, J. Ash
	Filename	: draft-ietf-pce-comm-protocol-gen-reqs-03.txt
	Pages		: 22
	Date		: 2005-12-28
	
The PCE model is described in the "PCE Architecture" document and
   facilitates path computation requests from Path Computation Clients
   (PCCs) to Path Computation Elements (PCEs).  This document specifies
   generic requirements for a communication protocol between PCCs and
   PCEs, and also between PCEs where cooperation between PCEs is
   desirable.  Subsequent documents will specify application-specific
   requirements for the PCE communication protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-comm-protocol-gen-reqs-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pce-comm-protocol-gen-reqs-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pce-comm-protocol-gen-reqs-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-12-28094245.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pce-comm-protocol-gen-reqs-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pce-comm-protocol-gen-reqs-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-12-28094245.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--NextPart--





From pce-bounces@lists.ietf.org Wed Dec 28 12:19:02 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Erex4-0008Tt-8c; Wed, 28 Dec 2005 12:19:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Erex2-0008Tj-Ak
	for pce@megatron.ietf.org; Wed, 28 Dec 2005 12:19:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12732
	for <pce@ietf.org>; Wed, 28 Dec 2005 12:17:49 -0500 (EST)
Received: from mail126.messagelabs.com ([216.82.254.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Erf13-0002d6-EB
	for pce@ietf.org; Wed, 28 Dec 2005 12:23:13 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-6.tower-126.messagelabs.com!1135790309!10888752!5
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 20490 invoked from network); 28 Dec 2005 17:18:45 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-6.tower-126.messagelabs.com with SMTP;
	28 Dec 2005 17:18:45 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by
	attrh3i.attrh.att.com (7.2.052)
	id 43AED14A000382C3 for pce@ietf.org; Wed, 28 Dec 2005 12:18:45 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 28 Dec 2005 11:18:45 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9842@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ietf-pce-comm-protocol-gen-reqs-03.txt 
Thread-Index: AcYLyg7r9fYT60FcSF65LhClU/gvggAB5yJg
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <pce@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Pce] RE: I-D ACTION:draft-ietf-pce-comm-protocol-gen-reqs-03.txt 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

Hi All,

Please review and comment on the updated version of the PCE
communications protocol (PCECP) generic requirements I-D
http://www.ietf.org/internet-drafts/draft-ietf-pce-comm-protocol-gen-req
s-03.txt.

Per our agreements at IETF-64 (see JL's slide at
http://www3.ietf.org/proceedings/05nov/slides/pce-11/sld7.htm), the
referenced requirements in the inter-area PCECP requirements draft have
been moved into the generic PCECP requirements draft.  In particular,

- Section 6.1.17 'Objective Functions Supported' was added
- Section 6.3.4 'LSP Rerouting & Reoptimization' was updated

Our objective is to start a WG last call soon.  We look forward to your
review and comments.

Thanks,
Regards,
Jerry

-----Original Message-----
From: i-d-announce-bounces@ietf.org
[mailto:i-d-announce-bounces@ietf.org] On Behalf Of
Internet-Drafts@ietf.org
Sent: Wednesday, December 28, 2005 10:50 AM
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: I-D ACTION:draft-ietf-pce-comm-protocol-gen-reqs-03.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Path Computation Element Working Group
of the IETF.

	Title		: PCE Communication Protocol Generic
Requirements
	Author(s)	: J. Le Roux, J. Ash
	Filename	: draft-ietf-pce-comm-protocol-gen-reqs-03.txt
	Pages		: 22
	Date		: 2005-12-28
=09
The PCE model is described in the "PCE Architecture" document and
   facilitates path computation requests from Path Computation Clients
   (PCCs) to Path Computation Elements (PCEs).  This document specifies
   generic requirements for a communication protocol between PCCs and
   PCEs, and also between PCEs where cooperation between PCEs is
   desirable.  Subsequent documents will specify application-specific
   requirements for the PCE communication protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-comm-protocol-gen-req
s-03.txt

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



