RE: [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-reqs-01.txt
"LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@francetelecom.com> Thu, 23 February 2006 07:51 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCBGJ-0007u0-0p; Thu, 23 Feb 2006 02:51:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCBGH-0007ts-9K for pce@ietf.org; Thu, 23 Feb 2006 02:51:41 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCBGF-0004Hx-Rk for pce@ietf.org; Thu, 23 Feb 2006 02:51:41 -0500
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Feb 2006 08:51:38 +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-pcecp-interarea-reqs-01.txt
Date: Thu, 23 Feb 2006 08:52:14 +0100
Message-ID: <D109C8C97C15294495117745780657AE044EBB01@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-reqs-01.txt
thread-index: AcY38hNZxvJT378kT8SahBfqnOXdMAAWqNdw
From: LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@francetelecom.com>
To: pce@ietf.org
X-OriginalArrivalTime: 23 Feb 2006 07:51:38.0846 (UTC) FILETIME=[FA3B37E0:01C6384D]
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, 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 : Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Envoyé : mercredi 22 février 2006 21:50 > À : i-d-announce@ietf.org > Cc : pce@ietf.org > 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 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-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-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 Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce
- [Pce] I-D ACTION:draft-ietf-pce-pcecp-interarea-r… Internet-Drafts
- RE: [Pce] I-D ACTION:draft-ietf-pce-pcecp-interar… LE ROUX Jean-Louis RD-CORE-LAN