RE: [Pce] I-D ACTION:draft-ietf-pce-disco-proto-igp-01.txt

"LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@francetelecom.com> Thu, 09 March 2006 13:02 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHKmu-0005lf-35; Thu, 09 Mar 2006 08:02:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHKms-0005la-FP for pce@ietf.org; Thu, 09 Mar 2006 08:02:38 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHKms-0000om-22 for pce@ietf.org; Thu, 09 Mar 2006 08:02:38 -0500
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 Mar 2006 14:02:36 +0100
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pce] I-D ACTION:draft-ietf-pce-disco-proto-igp-01.txt
Date: Thu, 09 Mar 2006 14:02:35 +0100
Message-ID: <D109C8C97C15294495117745780657AE04686249@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Pce] I-D ACTION:draft-ietf-pce-disco-proto-igp-01.txt
Thread-Index: AcZA/yy6Ei5YlicrSL+idAZJEamHpwCagFug
From: LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@francetelecom.com>
To: pce@ietf.org
X-OriginalArrivalTime: 09 Mar 2006 13:02:36.0473 (UTC) FILETIME=[BCD3AA90:01C64379]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc:
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>
Errors-To: pce-bounces@lists.ietf.org

Hi all,

Here are the major changes in this new revision of the IGP-based PCE discovery ID:

-Clarified the definition and applicability of PCE preferences
(in the PATH-SCOPE TLV).
-Added protocol elements and procedures for discovery of PCE Congestion Status. A new TLV is defined, the PCES (PCE Status) TLV to be carried within the ISIS Cap TLV and OSPF RI LSA. It allows advertising when a PCE enters or leaves a processing congestion state. Procedures to avoid any impact on the IGP scalability (dampening, hysterisis, congestion duration) are discussed.
-Some rewordings for the sake of clarity
-Added a new co-author

Your comments on this new revision are required.

Regards,

JL


> -----Message d'origine-----
> De : Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> Envoyé : lundi 6 mars 2006 08:50
> À : i-d-announce@ietf.org
> Cc : pce@ietf.org
> Objet : [Pce] I-D ACTION:draft-ietf-pce-disco-proto-igp-01.txt 
> 
> 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		: IGP protocol extensions for Path 
> Computation Element (PCE) Discovery
> 	Author(s)	: J. Le Roux, et al.
> 	Filename	: draft-ietf-pce-disco-proto-igp-01.txt
> 	Pages		: 32
> 	Date		: 2006-3-5
> 	
> There are various circumstances in which it is highly 
> desirable for a Path Computation Client (PCC) to be able to 
> dynamically and automatically discover a set of Path 
> Computation Element(s) (PCE), along with some of information 
> that can used for PCE selection. When the PCE is an LSR 
> participating to the IGP, or even a server participating 
> passively to the IGP, a simple and efficient way for PCE 
> discovery consists of relying on IGP flooding. For that 
> purpose this document defines OSPF and ISIS extensions for 
> the advertisement of PCE Discovery information within an IGP 
> area or the entire routing domain.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pce-disco-proto
> -igp-01.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-disco-proto-igp-01.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-disco-proto-igp-01.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.
> 

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