Hi all,

This new revision accounts for points discussed in Vancouver and on the list. 
Here are the main changes:
-Removed all text related to the applicability of PCEs for inter-area path 
computation. This will be moved to an applicability statement draft to be 
posted soon.
-Requirements for reoptimization, load balancing, objective functions, metrics, 
cost recording and re-routing have been moved to the generic ID.
-Added a requirement for area recording in a reply (see section 5.2).
-Added one co-author.
-Some rewordings for the sake of clarity.

Any comment on this new version would be welcome.

Best Regards,

JL et al.



> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Envoyé : mercredi 22 février 2006 21:50
> À : [email protected]
> Cc : [EMAIL PROTECTED]
> Objet : [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-reqs-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           : 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-01.txt
>       Pages           : 10
>       Date            : 2006-2-22
>       
> 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) based 
> architecture is the computation of inter-area TE-LSP paths. 
> 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-inter
> area-reqs-01.txt
> 
> To remove yourself from the I-D Announcement list, send a 
> message to [EMAIL PROTECTED] 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-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:
>       [EMAIL PROTECTED]
> In the body type:
>       "FILE 
> /internet-drafts/draft-ietf-pce-pcecp-interarea-reqs-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
[email protected]
https://www1.ietf.org/mailman/listinfo/pce

Reply via email to