RE: [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-reqs-02.txt

"LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@orange-ft.com> Mon, 03 July 2006 15:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FxQ2W-00056J-B3; Mon, 03 Jul 2006 11:08:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FxQ2V-00056E-0X for pce@ietf.org; Mon, 03 Jul 2006 11:08:43 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxQ2U-0004uq-JD for pce@ietf.org; Mon, 03 Jul 2006 11:08:42 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Mon, 3 Jul 2006 17:08:41 +0200
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
Subject: RE: [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-reqs-02.txt
Date: Mon, 03 Jul 2006 17:08:34 +0200
Message-ID: <D109C8C97C15294495117745780657AE0549122D@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-reqs-02.txt
Thread-Index: AcabFd7GLynwKcd9TrmYwm7Q/DnjIwDmqMQQ
From: LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@orange-ft.com>
To: pce@ietf.org
X-OriginalArrivalTime: 03 Jul 2006 15:08:41.0003 (UTC) FILETIME=[918E57B0:01C69EB2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
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,

There are no major changes in this new version.
As required in Dallas, authors of this draft and authors of the policy framework draft discussed together to see whether the inter-area path computation application had an impact on the policy framework and whether there were additional policy requirements for the PCECP. It resulted that no new element needs to be added in this requirement draft. But we reformulated the policy section (section 5.7) to clarify the requirements.

We are waiting for your comments on this new version.

Best Regards,

JL

> -----Message d'origine-----
> De : Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> Envoyé : jeudi 29 juin 2006 00:50
> À : i-d-announce@ietf.org
> Cc : pce@ietf.org
> Objet : [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-reqs-02.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-02.txt
> 	Pages		: 10
> 	Date		: 2006-6-28
> 	
> 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-02.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-02.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-02.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