From pce-bounces@lists.ietf.org Thu Nov 01 17:42:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InhmI-0005js-Rx; Thu, 01 Nov 2007 17:40:38 -0400 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1InhmH-0005hm-Rx for pce-confirm+ok@megatron.ietf.org; Thu, 01 Nov 2007 17:40:37 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InhmH-0005hC-Fh; Thu, 01 Nov 2007 17:40:37 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InhmH-0007yo-2i; Thu, 01 Nov 2007 17:40:37 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 215DA2ADA1; Thu, 1 Nov 2007 21:40:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Inhli-0002Ua-C8; Thu, 01 Nov 2007 17:40:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 01 Nov 2007 17:40:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: pce@ietf.org Subject: [Pce] I-D Action:draft-ietf-pce-policy-enabled-path-comp-03.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 : Policy-Enabled Path Computation Framework Author(s) : I. Bryskin, et al. Filename : draft-ietf-pce-policy-enabled-path-comp-03.txt Pages : 34 Date : 2007-11-01 The Path Computation Element (PCE) Architecture introduces the concept of policy in the context of path computation. This document provides additional details on policy within the PCE Architecture and also provides context for the support of PCE Policy. This document introduces the use of the Policy Core Information Model (PCIM) as a framework for supporting path computation policy. This document also provides representative scenarios for the support of PCE Policy.Contents A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-policy-enabled-path-comp-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-policy-enabled-path-comp-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-policy-enabled-path-comp-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: <2007-11-01173201.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-policy-enabled-path-comp-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-policy-enabled-path-comp-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-01173201.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 Thu Nov 01 17:49:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InhuL-0002pl-NR; Thu, 01 Nov 2007 17:48:57 -0400 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1InhuL-0002pd-1w for pce-confirm+ok@megatron.ietf.org; Thu, 01 Nov 2007 17:48:57 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InhuK-0002p9-Lb for pce@ietf.org; Thu, 01 Nov 2007 17:48:56 -0400 Received: from esc91.midphase.com ([216.104.33.66]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InhuK-0008GJ-3f for pce@ietf.org; Thu, 01 Nov 2007 17:48:56 -0400 Received: from esc91.midphase.com ([216.104.33.66] helo=LC1.labn.net) by esc91.midphase.com with esmtpa (Exim 4.68) (envelope-from ) id 1Inhu7-0008Cs-FS; Thu, 01 Nov 2007 17:48:44 -0400 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Thu, 01 Nov 2007 17:48:45 -0400 To: pce@ietf.org From: Lou Berger Subject: Re: [Pce] I-D Action:draft-ietf-pce-policy-enabled-path-comp-03.txt In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - esc91.midphase.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - labn.net X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Message-Id: Cc: X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Changes from the previous version address the 'pre-last-call' comments received. Only editorial changes were made. The authors believe the document is ready for WG last call (per discussion with chairs on list.) Lou (and co-authors) At 05:40 PM 11/1/2007, Internet-Drafts@ietf.org wrote: >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 : Policy-Enabled Path Computation Framework > Author(s) : I. Bryskin, et al. > Filename : draft-ietf-pce-policy-enabled-path-comp-03.txt > Pages : 34 > Date : 2007-11-01 > >The Path Computation Element (PCE) Architecture introduces the >concept of policy in the context of path computation. This document >provides additional details on policy within the PCE Architecture and >also provides context for the support of PCE Policy. This document >introduces the use of the Policy Core Information Model (PCIM) as a >framework for supporting path computation policy. This document also >provides representative scenarios for the support of PCE Policy.Contents > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-pce-policy-enabled-path-comp-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-policy-enabled-path-comp-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-policy-enabled-path-comp-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. > >Content-ID: <2007-11-01173201.I-D@ietf.org> >Content-Type: text/plain; x-avg-checked=avg-ok-4FB74AEF > >ENCODING mime >FILE /internet-drafts/draft-ietf-pce-policy-enabled-path-comp-03.txt > > > >_______________________________________________ >Pce mailing list >Pce@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/pce _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Sat Nov 03 09:56:17 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IoJST-0000Jy-Hq; Sat, 03 Nov 2007 09:54:41 -0400 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IoJSR-0000JZ-0t for pce-confirm+ok@megatron.ietf.org; Sat, 03 Nov 2007 09:54:39 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IoJSQ-00005E-Mx for pce@ietf.org; Sat, 03 Nov 2007 09:54:38 -0400 Received: from heisenberg.zen.co.uk ([212.23.3.141]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IoJRz-0001qS-MW for pce@ietf.org; Sat, 03 Nov 2007 09:54:11 -0400 Received: from [88.96.235.142] (helo=aria-networks.com) by heisenberg.zen.co.uk with esmtp (Exim 4.50) id 1IoJRw-00021B-AZ for pce@ietf.org; Sat, 03 Nov 2007 13:54:08 +0000 Received: from your029b8cecfe ([81.140.15.32]) by aria-networks.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 3 Nov 2007 13:54:06 +0000 Message-ID: <069101c81e20$feafcce0$5aa92f40@your029b8cecfe> From: "Adrian Farrel" To: Date: Sat, 3 Nov 2007 13:53:50 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-OriginalArrivalTime: 03 Nov 2007 13:54:07.0154 (UTC) FILETIME=[00852920:01C81E21] X-Originating-Heisenberg-IP: [88.96.235.142] X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: Subject: [Pce] Vancouver Schedule X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Hi, The *preliminary* schedule is at https://datatracker.ietf.org/meeting/70/agenda.html It shows PCE at: 1pm Tuesday 4th December Adrian _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Mon Nov 05 10:23:53 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip3ns-0007Qv-M0; Mon, 05 Nov 2007 10:23:52 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1Ip3nr-0007Q7-Sb for pce-confirm+ok@megatron.ietf.org; Mon, 05 Nov 2007 10:23:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip3nr-0007Pw-I5 for pce@ietf.org; Mon, 05 Nov 2007 10:23:51 -0500 Received: from usaga04-in.huawei.com ([206.16.17.180] helo=usaga01-in.huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ip3np-00016F-Tc for pce@ietf.org; Mon, 05 Nov 2007 10:23:51 -0500 Received: from huawei.com (usaga04-in [172.18.9.16]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JR100FPPHFOH0@usaga04-in.huawei.com> for pce@ietf.org; Mon, 05 Nov 2007 09:23:48 -0600 (CST) Received: from Lee736821 ([10.124.12.76]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JR100L4BHFLCQ@usaga04-in.huawei.com> for pce@ietf.org; Mon, 05 Nov 2007 09:23:48 -0600 (CST) Date: Mon, 05 Nov 2007 09:23:45 -0600 From: Young Lee To: pce@ietf.org Message-id: <001e01c81fbf$db0b13d0$4c0c7c0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Mailer: Microsoft Office Outlook 11 Thread-index: Acgfv9qvsP4keEP8QP2BafW7c1jKXA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 Cc: Subject: [Pce] a new draft on PCE WSON routing and wavelength X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0059007602==" Errors-To: pce-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============0059007602== Content-type: multipart/alternative; boundary="Boundary_(ID_J+LALA01z1sIPqANsDwgzw)" This is a multi-part message in MIME format. --Boundary_(ID_J+LALA01z1sIPqANsDwgzw) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi all, There was a slight mistake associated with the title of PCE WSON RWA draft. The corrected version has been updated as follows: http://www.ietf.org/internet-drafts/draft-lee-pce-wson-routing-wavelength-00 .txt Best regards, Young --Boundary_(ID_J+LALA01z1sIPqANsDwgzw) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT

Hi all,

 

There was a slight mistake associated with the title of PCE WSON RWA draft.  The corrected version has been updated as follows: http://www.ietf.org/internet-drafts/draft-lee-pce-wson-routing-wavelength-00.txt

 

Best regards,

 

Young

--Boundary_(ID_J+LALA01z1sIPqANsDwgzw)-- --===============0059007602== 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 --===============0059007602==-- From pce-bounces@lists.ietf.org Wed Nov 07 10:52:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpnCc-0003hp-Qa; Wed, 07 Nov 2007 10:52:26 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IpnCb-0003hV-S3 for pce-confirm+ok@megatron.ietf.org; Wed, 07 Nov 2007 10:52:25 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpnCb-0003gV-Cy for pce@ietf.org; Wed, 07 Nov 2007 10:52:25 -0500 Received: from heisenberg.zen.co.uk ([212.23.3.141]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpnCX-0005q7-TK for pce@ietf.org; Wed, 07 Nov 2007 10:52:25 -0500 Received: from [88.96.235.142] (helo=aria-networks.com) by heisenberg.zen.co.uk with esmtp (Exim 4.50) id 1IpnCX-0001Ny-DG for pce@ietf.org; Wed, 07 Nov 2007 15:52:21 +0000 Received: from your029b8cecfe ([81.140.15.32]) by aria-networks.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 7 Nov 2007 15:52:20 +0000 Message-ID: <0e4301c82156$2ccdd490$5aa92f40@your029b8cecfe> From: "Adrian Farrel" To: Date: Wed, 7 Nov 2007 15:52:10 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-OriginalArrivalTime: 07 Nov 2007 15:52:21.0034 (UTC) FILETIME=[2E7458A0:01C82156] X-Originating-Heisenberg-IP: [88.96.235.142] X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: Subject: [Pce] Working Group Last Call on draft-ietf-pce-policy-enabled-path-comp-03.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Hi, This I-D has been stable for some time. It has just been updated after comments received from IPSphere participants. This email begins a two week working group last call. The call will end at 5pm GMT on Wednesday 21st November. Please send you comments to the list. Thanks, Adrian _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Thu Nov 08 18:15:10 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqGab-0001By-PX; Thu, 08 Nov 2007 18:15:09 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IqGaW-00011W-O0 for pce-confirm+ok@megatron.ietf.org; Thu, 08 Nov 2007 18:15:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqGaW-00010M-Bz; Thu, 08 Nov 2007 18:15:04 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IqGaU-0008Fq-VZ; Thu, 08 Nov 2007 18:15:04 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id CBFD826E65; Thu, 8 Nov 2007 23:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IqGaU-0000ly-Nf; Thu, 08 Nov 2007 18:15: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: Date: Thu, 08 Nov 2007 18:15:02 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: pce@ietf.org Subject: [Pce] I-D ACTION:draft-ietf-pce-global-concurrent-optimization-01.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 Communication Protocol (PCECP) Requirements and Protocol Extensions In Support of Global Concurrent Optimization Author(s) : Y. Lee, et al. Filename : draft-ietf-pce-global-concurrent-optimization-01.txt Pages : 31 Date : 2007-11-8 The Path Computation Element (PCE) is a network component, application, or node that is capable of performing path computations at the request of Path Computation Clients (PCCs). The PCE is applied in Multiprotocol Label Switching Traffic Engineering (MPLS-TE) networks and in Generalized MPLS (GMPLS) networks to determine the routes of Label Switched Paths (LSPs) through the network. The Path Computation Element Communication Protocol (PCEP) is specified for communications between PCCs and PCEs, and between cooperating PCEs. When computing or re-optimizing the routes of a set of LSPs through a network it may be advantageous to perform bulk path computations in order to avoid blocking problems and to achieve more optimal network- wide solutions. Such bulk optimization is termed Global Concurrent Optimization (GCO). A Global Concurrent Optimization is able to simultaneously consider the entire topology of the network and the complete set of existing LSPs, and their respective constraints, and look to optimize or re-optimize the entire network to satisfy all constraints for all LSPs. The Global Concurrent Optimization (GCO) application is primarily an NMS based solution. This document provides application-specific requirements and the PCEP extensions in support of a global concurrent optimization (GCO) application. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-global-concurrent-optimization-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-global-concurrent-optimization-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-global-concurrent-optimization-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. --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: <2007-11-8165915.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-global-concurrent-optimization-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-global-concurrent-optimization-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-8165915.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 Fri Nov 09 17:32:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqcPH-0008J9-SD; Fri, 09 Nov 2007 17:32:56 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IqcPG-0008J4-NM for pce-confirm+ok@megatron.ietf.org; Fri, 09 Nov 2007 17:32:54 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqcPG-0008Iv-Cc for pce@ietf.org; Fri, 09 Nov 2007 17:32:54 -0500 Received: from pythagoras.zen.co.uk ([212.23.3.140]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IqcPF-00088Q-Pq for pce@ietf.org; Fri, 09 Nov 2007 17:32:54 -0500 Received: from [88.96.235.142] (helo=aria-networks.com) by pythagoras.zen.co.uk with esmtp (Exim 4.50) id 1IqcPC-00068f-Eo; Fri, 09 Nov 2007 22:32:50 +0000 Received: from your029b8cecfe ([81.140.15.32]) by aria-networks.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 9 Nov 2007 22:31:48 +0000 Message-ID: <10ea01c82320$71970f30$5aa92f40@your029b8cecfe> From: "Adrian Farrel" To: Date: Fri, 9 Nov 2007 22:32:09 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-OriginalArrivalTime: 09 Nov 2007 22:31:48.0965 (UTC) FILETIME=[5147E150:01C82320] X-Originating-Pythagoras-IP: [88.96.235.142] X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Cc: Ross Callon , Scott Bradner Subject: [Pce] Fw: Time for a liaison to the ITU X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Hi working group, In recent months there has been a resurgence of interest in the inter-layer characteristics of the ASON architecture defined in the ITU-T. This has included discussions in Study Group 15 Questions 12 and 14 about how to provide routing in a layered network. As you may recall, Study Group 15 recently recognized PCE as an option for handling their multi-level routing requirements , and published G.7715.2 describing how a separate path computation component could be used. So we think that draft-ietf-pce-inter-layer-frwk-05.txt and draft-ietf-pce-inter-layer-req-05.txt may be of interest to them and propose to send the short liaison below. Your comments are welcomed. Regards, Adrian and JP === To: ITU-T Q12/15 and Q14/15 Cc: Stephen Trowbridge, Kam Lam, Malcolm Betts, Ross Callon, Dave Ward, Scott Bradner Subject: Application of PCE to Inter-Layer Networks For: Information The Path Computation Element (PCE) working group of the IETF is aware that your Questions have recently been discussing the inter-layer aspects of the ASON architecture and particularly how to select routes across a multi-layer network, and how to represent within a higher layer network the potential or real connectivity across a lower layer network. In the light of G.7715.2 we believe that you may be interested in some work being discussed in the PCE working group. "Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering" may be found at http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-frwk-05.txt. This document should be read in the context of the general PCE architecture described in "A Path Computation Element (PCE)-Based Architecture" http://www.ietf.org/rfc/rfc4655.txt Although not specifically targeted at the ASON architecture, we would welcome any comments that you have on draft-ietf-pce-inter-layer-frwk-05.txt, and invite interested parties to contribute either through the liaison process or via the PCE working group mailing list details of which can be found at the PCE working group charter page http://www.ietf.org/html.charters/pce-charter.html We are also looking at the requirements driven by inter-layer routing for extensions to the PCE Protocol (PCEP) used for communication between Path Computation Clients (PCCs) and PCEs. These can be found in "PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic Engineering " http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-req-05.txt Best regards, JP Vasseur and Adrian Farrel IETF PCE working group co-chairs _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Sat Nov 10 08:45:22 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqqeH-0000o3-DN; Sat, 10 Nov 2007 08:45:21 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IqqeF-0000jT-0r for pce-confirm+ok@megatron.ietf.org; Sat, 10 Nov 2007 08:45:19 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqqeE-0000jJ-MO for pce@ietf.org; Sat, 10 Nov 2007 08:45:18 -0500 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IqqeE-0000eZ-Em for pce@ietf.org; Sat, 10 Nov 2007 08:45:18 -0500 X-IronPort-AV: E=Sophos;i="4.21,398,1188792000"; d="scan'208";a="75697436" Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 10 Nov 2007 08:45:17 -0500 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lAADjHMP002368 for ; Sat, 10 Nov 2007 08:45:18 -0500 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lAADj1dS002929 for ; Sat, 10 Nov 2007 13:45:18 GMT Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 10 Nov 2007 08:45:04 -0500 Received: from 10.86.104.180 ([10.86.104.180]) by xmb-rtp-213.amer.cisco.com ([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; Sat, 10 Nov 2007 13:45:04 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Sat, 10 Nov 2007 08:45:03 -0500 From: JP Vasseur To: Message-ID: Thread-Topic: Preliminary Agenda for Vancouver Thread-Index: Acgjn+USI1asno+TEdyHogANk8WjQA== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 10 Nov 2007 13:45:04.0559 (UTC) FILETIME=[E5FFFBF0:01C8239F] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15536.002 X-TM-AS-Result: No--2.919300-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=155; t=1194702318; x=1195566318; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20 |Subject:=20Preliminary=20Agenda=20for=20Vancouver |Sender:=20 |To:=20; bh=O4k1snSgEWDIbjynYAF1rK6ezDcd1yQG7qF2e5j2NM0=; b=OMzI0Ch6y46Da1dOAXMAylc6F/PCHOljg7WJYX6/6vUQmIWfRcqujhoBAhqWyLbhKvBFMQh8 NVgGrCUo30myI+LimyVuM1Xf68BJN7Uxgh/4o0zF5NFGOwhoM/lFTyKu; Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Cc: Subject: [Pce] Preliminary Agenda for Vancouver X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Dear WG, Here is the preliminary agenda: http://www3.ietf.org/proceedings/07dec/agenda/pce.txt Let us know if you have comments. Thanks. JP. _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Tue Nov 13 11:15:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IryQ9-0000oY-7B; Tue, 13 Nov 2007 11:15:25 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IryPp-0000Eb-AK for pce-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 11:15:05 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IryPo-0000EP-Nh; Tue, 13 Nov 2007 11:15:04 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IryPn-0000fo-89; Tue, 13 Nov 2007 11:15:04 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 1837826E85; Tue, 13 Nov 2007 16:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IryPl-0005A8-TL; Tue, 13 Nov 2007 11:15: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: Date: Tue, 13 Nov 2007 11:15:01 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: pce@ietf.org Subject: [Pce] I-D ACTION:draft-ietf-pce-inter-layer-req-06.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 : PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic Engineering Author(s) : E. Oki Filename : draft-ietf-pce-inter-layer-req-06.txt Pages : 13 Date : 2007-11-13 The Path Computation Element (PCE) provides functions of path computation in support of traffic engineering in Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. MPLS and GMPLS networks may be constructed from layered client/server networks. It is advantageous for overall network efficiency to provide end-to-end traffic engineering across multiple network layers. PCE is a candidate solution for such requirements. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-req-06.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-inter-layer-req-06.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-inter-layer-req-06.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: <2007-11-13104134.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-inter-layer-req-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-inter-layer-req-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-13104134.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 Tue Nov 13 20:00:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is6cc-0001gG-If; Tue, 13 Nov 2007 20:00:50 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1Is6cb-0001gB-Hk for pce-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 20:00:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is6cb-0001fx-7S for pce@ietf.org; Tue, 13 Nov 2007 20:00:49 -0500 Received: from [2001:200:601:12:230:48ff:fe22:3a84] (helo=mandala.kddilabs.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Is6ca-0000cC-4d for pce@ietf.org; Tue, 13 Nov 2007 20:00:49 -0500 Received: from localhost (localhost [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id BE868ECC01 for ; Wed, 14 Nov 2007 09:38:17 +0900 (JST) Received: from mail.cn.kddilabs.jp (yellow.lan.kddilabs.jp [172.19.98.10]) by mandala.kddilabs.jp (Postfix) with ESMTP id A097DECC10 for ; Wed, 14 Nov 2007 09:38:16 +0900 (JST) Received: from [IPv6:::1] (unknown [172.19.66.65]) by mail.cn.kddilabs.jp (Postfix) with ESMTP id 939851E0002 for ; Wed, 14 Nov 2007 09:38:16 +0900 (JST) Message-ID: <473A4378.30303@kddilabs.jp> Date: Wed, 14 Nov 2007 09:38:16 +0900 From: Kenji Kumaki User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: pce@ietf.org Content-Type: multipart/mixed; boundary="------------060806020504030608050405" X-Virus-Scanned: by amavisd-new X-Spam-Score: -1.4 (-) X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c Cc: Subject: [Pce] [Fwd: I-D ACTION:draft-kumaki-pce-bgp-disco-attribute-00.txt] X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org This is a multi-part message in MIME format. --------------060806020504030608050405 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Hi, I submitted the following draft. BGP protocol extensions using attribute for Path Computation Element (PCE) Discovery http://www.ietf.org/internet-drafts/draft-kumaki-pce-bgp-disco-attribute-00.txt The point here is as follows: 1. Actually, static configuration is fine. But, PCCs/PCEs are required to discover a set of PCEs automatically from service provider perspective. 2. PCEs are discovered by BGP. In this case, BGP defines a new PCE Discovery Attribute and does not require PCE capability. Could you tell me comments and feedback? Thanks, Kenji --------------060806020504030608050405 Content-Type: message/rfc822; name="I-D ACTION:draft-kumaki-pce-bgp-disco-attribute-00.txt.eml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename*0="I-D ACTION:draft-kumaki-pce-bgp-disco-attribute-00.txt.eml" Return-Path: X-Original-To: ke-kumaki@mail.cn.kddilabs.jp Delivered-To: ke-kumaki@mail.cn.kddilabs.jp Received: from mandala.kddilabs.jp (mandala.kddilabs.jp [172.19.66.6]) by mail.cn.kddilabs.jp (Postfix) with ESMTP id 4FAD51E0002 for ; Wed, 14 Nov 2007 02:16:07 +0900 (JST) Received: by mandala.kddilabs.jp (Postfix) id 4A986ECAD5; Wed, 14 Nov 2007 02:16:07 +0900 (JST) Delivered-To: ke-kumaki@kddilabs.jp Received: from localhost (localhost [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id 2A6E3ECA61 for ; Wed, 14 Nov 2007 02:16:07 +0900 (JST) Received: from UTMC1124.kddi.com (unknown [10.5.16.54]) by mandala.kddilabs.jp (Postfix) with ESMTP id 24888EC9FB for ; Wed, 14 Nov 2007 02:16:05 +0900 (JST) Received: from UTMC1114.kddi.com (unknown [10.5.16.17]) by UTMC1124.kddi.com (Postfix) with ESMTP id 103171BD3 for ; Wed, 14 Nov 2007 02:16:05 +0900 (JST) Received: by UTMC1114.kddi.com; Wed, 14 Nov 2007 02:16:05 +0900 Resent-From: Resent-Date: Wed, 14 Nov 2007 02:16:05 +0900 Received: from usjk1037 (usjk1037.kddi.com [10.5.16.67]) by post-ims.kddi.com; Wed, 14 Nov 2007 02:16:05 +0900 Received: from UTMC1120.kddi.com ([10.5.16.42]) by LTMC1002 with ESMTP; Wed, 14 Nov 2007 02:16:00 +0900 (JST) Received: from UTMC1120.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 1CBD31BDA; Wed, 14 Nov 2007 02:16:00 +0900 (JST) Received: from UTMC1103.kddi.com (unknown [210.141.112.39]) by UTMC1120.kddi.com (Postfix) with ESMTP id E8B6F1B70; Wed, 14 Nov 2007 02:15:59 +0900 (JST) Received: from megatron.ietf.org (www1.ietf.ORG [156.154.16.145]) by UTMC1103.kddi.com (Postfix) with ESMTP id 6F24D1E1D; Wed, 14 Nov 2007 02:15:59 +0900 (JST) Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrzLt-0005Wh-L2; Tue, 13 Nov 2007 12:15:05 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrzLr-0005Vv-6Y for i-d-announce@ietf.org; Tue, 13 Nov 2007 12:15:03 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrzLq-00076x-QR for i-d-announce@ietf.org; Tue, 13 Nov 2007 12:15:03 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 76119175DD for ; Tue, 13 Nov 2007 17:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IrzLq-00083C-0m for i-d-announce@ietf.org; Tue, 13 Nov 2007 12:15:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 13 Nov 2007 12:15:02 -0500 X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Subject: I-D ACTION:draft-kumaki-pce-bgp-disco-attribute-00.txt X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: internet-drafts@ietf.org List-Id: i-d-announce.ietf.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: i-d-announce-bounces@ietf.org X-matriXscan-Auth: Authenticated X-matriXscan: Uncategorized X-matriXscan-RefId: str=0001.0A090202.4739DA4A.016C,ss=1,fgs=0 X-matriXscan-Action: Approve X-WAuditID: 0711140216000000028005 Resent-Message-Id: <20071113171605.103171BD3@UTMC1124.kddi.com> X-Virus-Scanned: by amavisd-new --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : BGP protocol extensions using attribute for Path Computation Element (PCE) Discovery Author(s) : K. Kumaki, T. Murai Filename : draft-kumaki-pce-bgp-disco-attribute-00.txt Pages : 8 Date : 2007-11-13 It is highly desirable for Path Computation Clients (PCCs) to be able to dynamically discover a set of Path Computation Elements (PCEs) when PCCs/PCEs request a path computation to PCEs across ASes. In such a scenario, it is advantageous to use BGP to distribute PCE information. This document defines a new attribute and describes how PCE information can be carried using BGP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-kumaki-pce-bgp-disco-attribute-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-kumaki-pce-bgp-disco-attribute-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-kumaki-pce-bgp-disco-attribute-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: <2007-11-13110035.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-kumaki-pce-bgp-disco-attribute-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-kumaki-pce-bgp-disco-attribute-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-13110035.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart-- --------------060806020504030608050405 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 --------------060806020504030608050405-- From pce-bounces@lists.ietf.org Wed Nov 14 02:03:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsCHC-0006NJ-GN; Wed, 14 Nov 2007 02:03:06 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IsCHB-0006ND-4g for pce-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 02:03:05 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsCHA-0006Mv-NZ for pce@ietf.org; Wed, 14 Nov 2007 02:03:04 -0500 Received: from ns1.nict.go.jp ([133.243.3.1]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsCHA-0005g1-2Y for pce@ietf.org; Wed, 14 Nov 2007 02:03:04 -0500 Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp with ESMTP id lAE731Ga018320 for ; Wed, 14 Nov 2007 16:03:01 +0900 (JST) Received: from gw1.nict.go.jp (localhost [127.0.0.1]) by gw1.nict.go.jp with ESMTP id lAE731tO016066 for ; Wed, 14 Nov 2007 16:03:01 +0900 (JST) Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp with ESMTP id lAE730UG016063 for ; Wed, 14 Nov 2007 16:03:00 +0900 (JST) Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by localhost.nict.go.jp (Postfix) with ESMTP id BC4346E4E for ; Wed, 14 Nov 2007 16:03:00 +0900 (JST) Received: from Platini (5gou2f-dhcp24.nict.go.jp [133.243.146.184]) by mail2.nict.go.jp (Postfix) with ESMTP id 9EAF56E3B for ; Wed, 14 Nov 2007 16:03:00 +0900 (JST) Message-ID: <019d01c8268c$62a1ffc0$b892f385@Platini> From: "Filippo Cugini" To: Date: Wed, 14 Nov 2007 08:02:57 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: Subject: [Pce] Liveness in draft-ietf-pce-monitoring-00.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1714896646==" Errors-To: pce-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============1714896646== Content-Type: multipart/alternative; boundary="----=_NextPart_000_019A_01C82694.C458AC20" This is a multi-part message in MIME format. ------=_NextPart_000_019A_01C82694.C458AC20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, just a consideration on the Liveness information in the pce-monitoring = draft. In case of specific monitoring request: if one PCE involved in the path computation chain is not alive the = computation should fail and, rather than a monitoring object, maybe a = specific error could be more appropriate. In case of general monitoring requests, maybe the discovery mechanism = could be more appropriate for such information. but maybe I missed something. Could you please comment on that? Thank you Filippo ------=_NextPart_000_019A_01C82694.C458AC20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
just a consideration on the = Liveness=20 information in the pce-monitoring draft.
 
In case of specific monitoring request:
if one PCE involved in = the path=20 computation chain is not alive the computation should fail and, = rather than=20 a monitoring object, maybe a specific error could be more=20 appropriate.
 
In case of general monitoring = requests, maybe=20 the discovery mechanism could be more = appropriate=20 for such information.
 
but maybe I missed something. Could you = please=20 comment on that?
 
Thank you
  =  Filippo
------=_NextPart_000_019A_01C82694.C458AC20-- --===============1714896646== 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 --===============1714896646==-- From pce-bounces@lists.ietf.org Wed Nov 14 17:15:10 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsQVp-0008R3-HB; Wed, 14 Nov 2007 17:15:09 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IsQVo-0008Py-Pa for pce-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 17:15:08 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsQVo-0008Pf-DX for pce@ietf.org; Wed, 14 Nov 2007 17:15:08 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsQVn-0005SJ-VO for pce@ietf.org; Wed, 14 Nov 2007 17:15:08 -0500 Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 14 Nov 2007 14:15:07 -0800 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lAEMF7fH014329; Wed, 14 Nov 2007 14:15:07 -0800 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lAEMF5CZ021233; Wed, 14 Nov 2007 22:15:06 GMT Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Nov 2007 17:15:05 -0500 Received: from 10.86.104.180 ([10.86.104.180]) by xmb-rtp-213.amer.cisco.com ([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; Wed, 14 Nov 2007 22:15:05 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Wed, 14 Nov 2007 17:15:02 -0500 Subject: Re: [Pce] Liveness in draft-ietf-pce-monitoring-00.txt From: JP Vasseur To: Filippo Cugini , Message-ID: Thread-Topic: [Pce] Liveness in draft-ietf-pce-monitoring-00.txt Thread-Index: AcgnC80lC7UZ/5L/EdyAEAANk8WjQA== In-Reply-To: <019d01c8268c$62a1ffc0$b892f385@Platini> Mime-version: 1.0 X-OriginalArrivalTime: 14 Nov 2007 22:15:05.0568 (UTC) FILETIME=[CF466600:01C8270B] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15544.002 X-TM-AS-Result: No--19.527200-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5462; t=1195078507; x=1195942507; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20 |Subject:=20Re=3A=20[Pce]=20Liveness=20in=20draft-ietf-pce-monitoring-00. txt |Sender:=20; bh=VnVEmQUw8a+ITLVYVWadvEHpp0c++duUwr0hMtv6SSQ=; b=upidauHGWDwQHdbo9RWQNUNQaC6V301Circ/TaUjc8QsHo01jugSvjoQ5uwDhSkr7MIYBa4L pWjSsfgLwarMphSgoV5iOCqG1mLAi8LS6qBvGv+wi3+15byG6ek4TB5m; Authentication-Results: sj-dkim-2; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Cc: X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1167507318==" Errors-To: pce-bounces@lists.ietf.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============1167507318== Content-type: multipart/alternative; boundary="B_3277905303_3549822" > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3277905303_3549822 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Hi, From: Filippo Cugini Date: Wed, 14 Nov 2007 08:02:57 +0100 To: Subject: [Pce] Liveness in draft-ietf-pce-monitoring-00.txt Hi, =20 just a consideration on the Liveness information in the pce-monitoring draft. =20 In case of specific monitoring request: if one PCE involved in the path computation chain is not alive the computation should fail and, rather than a monitoring object, maybe a specific error could be more appropriate. =20 In case of general monitoring requests, maybe the discovery mechanism could be more appropriate for such information. =20 but maybe I missed something. Could you please comment on that? JP> Let=B9s consider the case of PCC1 ---- PCE1 ---- PCE2 Few comments: 1. PCC1 may of course use a timer upon sending a request after the expiration of which it will resend its request if no reply has been receive= d (which covers the case where PCE1 or PCE2 fail). This ID is not aimed at being used for that purpose. 2. If PCE1 dies, indeed PCC1 may discover PCE=B9s failure thanks to the IGP i= f dynamic PCE discovery is in use (which may not be always the case). Furthermore PCEP could be used to detect a PCE failure. But again the aim o= f this ID is not to solve that specific issue. The aim of this ID is to be used by the network operator or an NMS to =B3monitor=B2 a PCE chain. For example, the user may want to check the liveness of the PCE chain at any point in time, which can be used with PCMonReq message, without having to send an actual path computation request. Thanks. JP. =20 Thank you Filippo _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce --B_3277905303_3549822 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Re: [Pce] Liveness in draft-ietf-pce-monitoring-00.txt Hi,


From: Filippo Cugini <filip= po.cugini@cnit.it>
Date: Wed, 14 Nov 2007 08:02:57 +0100
To: <pce@ietf.org>
Subject: [Pce] Liveness in draft-ietf-pce-monitoring-00.txt

Hi,
just a consideration on the Liveness information = in the pce-monitoring draft.
In case of specific monitoring request:
if one PCE involved in the path computation chain is not alive the computat= ion should fail and, rather than a monitoring object, maybe a specific error= could be more appropriate.
In case of general monitoring requests, maybe the= discovery mechanism could be more appropriate for such information.
but maybe I missed something. Could you please co= mment on that?

JP> Let’s consider the case of PCC1 ---- PCE1 ---- PCE2

Few comments:

  1. PCC1 may of course use a timer upon sending a request after= the expiration of which it will resend its request if no reply has been rec= eived (which covers the case where PCE1 or PCE2 fail). This ID is not aimed = at being used for that purpose.
  2. If PCE1 dies, indeed PCC1 may discover PCE’s failure than= ks to the IGP if dynamic PCE discovery is in use (which may not be always th= e case). Furthermore PCEP could be used to detect a PCE failure. But again t= he aim of this ID is not to solve that specific issue.  

The aim of this ID is to be used by the network operator or an NMS to ̶= 0;monitor” a PCE chain. For example, the user may want to check the li= veness of the PCE chain at any point in time, which can be used with PCMonRe= q message, without having to send an actual path computation request.

Thanks.

JP.
Thank you
   Filippo

____________________= ___________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce
 --B_3277905303_3549822-- --===============1167507318== 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 --===============1167507318==-- From pce-bounces@lists.ietf.org Wed Nov 14 17:23:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsQe7-0005N4-W5; Wed, 14 Nov 2007 17:23:44 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IsQe6-0005JV-Uf for pce-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 17:23:42 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsQe6-0005I8-Iu for pce@ietf.org; Wed, 14 Nov 2007 17:23:42 -0500 Received: from asmtp2.iomartmail.com ([62.128.201.249]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsQe5-0005iA-TO for pce@ietf.org; Wed, 14 Nov 2007 17:23:42 -0500 Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id lAEMNdAF011359 for ; Wed, 14 Nov 2007 22:23:39 GMT Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id lAEMNbIk011349 for ; Wed, 14 Nov 2007 22:23:39 GMT Message-ID: <066701c8270c$fe2f1b50$0200a8c0@your029b8cecfe> From: "Adrian Farrel" To: Date: Wed, 14 Nov 2007 22:23:31 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: Subject: [Pce] Fw: I-D Action:draft-yasukawa-pce-p2mp-req-04.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org For your information. Only a small change. Section 2.1.6 re-written. Adrian ----- Original Message ----- From: To: Sent: Wednesday, November 14, 2007 8:50 PM Subject: I-D Action:draft-yasukawa-pce-p2mp-req-04.txt >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > > Title : PCC-PCE Communication Requirements for Point to > Multipoint Multiprotocol Label Switching Traffic Engineering (MPLS-TE) > Author(s) : S. Yasukawa, A. Farrel > Filename : draft-yasukawa-pce-p2mp-req-04.txt > Pages : 10 > Date : 2007-11-14 > > The Path Computation Element (PCE) provides path computation > functions in support of traffic engineering in Multi-Protocol Label > Switching (MPLS) and Generalized MPLS (GMPLS) networks. > > Extensions to the MPLS and GMPLS signaling and routing protocols have > been made in support of point-to-multipoint (P2MP) Traffic Engineered > (TE) Label Switched Paths (LSPs). Since P2MP TE LSP routes are > sometimes complex to compute, and given the use of PCE in MPLS > networks it is likely that PCE will be used in P2MP MPLS-TE networks. > > Generic requirements for a communication protocol between Path > Computation Clients (PCCs) and PCEs are presented in "Path > Computation Element (PCE) Communication Protocol Generic > Requirements". This document complements the generic requirements and > presents a detailed set of PCC-PCE communication protocol > requirements for point-to-multipoint MPLS traffic engineering. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-yasukawa-pce-p2mp-req-04.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-yasukawa-pce-p2mp-req-04.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-yasukawa-pce-p2mp-req-04.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. > -------------------------------------------------------------------------------- > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce > _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Fri Nov 16 08:22:34 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1It19W-0006jH-4A; Fri, 16 Nov 2007 08:22:34 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1It19V-0006iv-GD for pce-confirm+ok@megatron.ietf.org; Fri, 16 Nov 2007 08:22:33 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1It19V-0006iN-6G for pce@ietf.org; Fri, 16 Nov 2007 08:22:33 -0500 Received: from tyo202.gate.nec.co.jp ([202.32.8.206]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1It19S-0001q3-GU for pce@ietf.org; Fri, 16 Nov 2007 08:22:33 -0500 Received: from mailgate3.nec.co.jp (mailgate53.nec.co.jp [10.7.69.192]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id lAGDMTi1003464 for ; Fri, 16 Nov 2007 22:22:29 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id lAGDMT716115 for pce@ietf.org; Fri, 16 Nov 2007 22:22:29 +0900 (JST) Received: from yonosuke.jp.nec.com (yonosuke.jp.nec.com [10.26.220.15]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id lAGDMSG04096 for ; Fri, 16 Nov 2007 22:22:28 +0900 (JST) Received: from NISHIOKAPC2 ([10.56.135.192] [10.56.135.192]) by mail.jp.nec.com with ESMTP; Fri, 16 Nov 2007 22:22:28 +0900 From: "Itaru Nishioka" To: Date: Fri, 16 Nov 2007 22:31:12 +0900 Organization: nec Message-Id: <008b01c82854$f476cf10$c087380a@NISHIOKAPC2> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: AcgoVPRQ4n8cUyIuTeqzm5+T30pGrg== X-Spam-Score: -0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: Subject: [Pce] draft-nishioka-pce-svec-list-01.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: i-nishioka@cb.jp.nec.com List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Hi GCO draft Editors and All We have submitted the update version of the following draft. The proposal discussed in this draft is one of the GCO applications. Please find the draft for your perusal. We would appreciate feedback/suggestions on the topics proposed. "The use of SVEC (Synchronization VECtor) list for Synchronized dependent path computations" http://www.ietf.org/internet-drafts/draft-nishioka-pce-svec-list-01.txt Our intention in the draft is to discuss Synchronization VECtors for dependent/diverse path computations concurrently. When a PCE performs multiple dependent/diverse path computations, like a disjoint path for a working and protected LSPs, the PCE would need to synchronize the computations in order to increase the probability of meeting the working and protected path disjoint objective and efficient network resource utilization. The document look to define the association among SVECs and the required processing rules. Best Regards, Itaru & Dan _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Fri Nov 16 16:50:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1It94e-0005Ya-Li; Fri, 16 Nov 2007 16:50:04 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1It94d-0005YE-Qb for pce-confirm+ok@megatron.ietf.org; Fri, 16 Nov 2007 16:50:03 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1It94d-0005Xz-Fc; Fri, 16 Nov 2007 16:50:03 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1It94d-0002tM-2q; Fri, 16 Nov 2007 16:50:03 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id B330A175E4; Fri, 16 Nov 2007 21:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1It94c-0005FX-8l; Fri, 16 Nov 2007 16: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: Date: Fri, 16 Nov 2007 16:50:02 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: pce@ietf.org Subject: [Pce] I-D Action:draft-ietf-pce-pcep-09.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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) communication Protocol (PCEP) Author(s) : A. Ayyangar, et al. Filename : draft-ietf-pce-pcep-09.txt Pages : 73 Date : 2007-11-16 This document specifies the Path Computation Element communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. Such interactions include path computation requests and path computation replies as well as notifications of specific states related to the use of a PCE in the context of Multiprotocol Label Switching (MPLS) and Generalized (GMPLS) Traffic Engineering. The PCEP protocol is designed to be flexible and extensible so as to easily allow for the addition of further messages and objects, should further requirements be expressed in the future. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-09.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-pcep-09.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-pcep-09.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: <2007-11-16164622.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-pcep-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-pcep-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-16164622.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 Fri Nov 16 16:57:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1It9Bw-0002EM-HW; Fri, 16 Nov 2007 16:57:36 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1It9Bv-0002EH-Hd for pce-confirm+ok@megatron.ietf.org; Fri, 16 Nov 2007 16:57:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1It9Bv-0002E5-7T for pce@ietf.org; Fri, 16 Nov 2007 16:57:35 -0500 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1It9Bp-0003Qe-P3 for pce@ietf.org; Fri, 16 Nov 2007 16:57:35 -0500 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 16 Nov 2007 16:57:29 -0500 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lAGLvTju024934 for ; Fri, 16 Nov 2007 16:57:29 -0500 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lAGLvTwl001021 for ; Fri, 16 Nov 2007 21:57:29 GMT Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Nov 2007 16:57:29 -0500 Received: from 161.44.71.191 ([161.44.71.191]) by xmb-rtp-213.amer.cisco.com ([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; Fri, 16 Nov 2007 21:57:29 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Fri, 16 Nov 2007 16:57:26 -0500 Subject: FW: [Pce] I-D Action:draft-ietf-pce-pcep-09.txt From: JP Vasseur To: Message-ID: Thread-Topic: [Pce] I-D Action:draft-ietf-pce-pcep-09.txt Thread-Index: Acgom6yM6xHExJSOEdyN6QANk8WjQA== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable X-OriginalArrivalTime: 16 Nov 2007 21:57:29.0372 (UTC) FILETIME=[AE8F2DC0:01C8289B] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15548.002 X-TM-AS-Result: No--20.181700-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8633; t=1195250249; x=1196114249; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20 |Subject:=20FW=3A=20[Pce]=20I-D=20Action=3Adraft-ietf-pce-pcep-09.txt=20 |Sender:=20 |To:=20; bh=dospKy33qu/XJd8efRhG62LabTZtJlC+EWOUH9RhXg0=; b=QZw+3ytQOdDNAAJqVl/50p+8sgIU+vnEUYKGH4Wux0m2ErkMipPkUj4WOVaLi8R79cJNq+SL tICI1hzGwRLgIQ9Th4AhM++35V/yZVQyT00P3gQovndx2LMIEWYNqskp; Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); X-Spam-Score: 0.4 (/) X-Scan-Signature: d008c19e97860b8641c1851f84665a75 Cc: X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Dear WG, Please find below the changes in revision -09 of PCEP: 1) New text: "The P flag of the END-POINT object MUST be set in PCReq message." =20 2) A New PCErr type and value has been defined. =20 10 Reception of a malformed object Error-value=3D1: reception of an object with P flag not set although the P-flag must be set according to this specification= . =20 3) Text added for both the RP and END-POINT objects: =20 "The P flag of the RP object MUST be set in PCReq and PCReq messages and MUST be cleared in PCNtf and PCErr messages. If the RP objet is received with the P flag set incorrectely according to the rules states above, the receiving peer MUST send a PCErr message with Error-type=3D10 and Error-value=3D1. The corresponding path computation request MUST be cancelled by the PCE without further notification." =20 4) Clarification on receiving two METRIC object in a PCReq message with B=3D0= . =20 "If a PCReq message is received that contains two METRIC object with the B flag set, the receiving peer MUST send a PCErr message with Error-type=3D10 and Error-value=3D2." 5) Clarification in 7.1 "If the PCE does not understand an object with the P flag set or understand= s the object but decides to ignore the object, the entire PCEP message MUST b= e rejected and the PCE MUST send a PCErr message with Error-Type=3D=B3Unknown Object=B2 or =B3Not supported Object=B2 along with the corresponding RP object. Note that if a PCReq includes multiple requests, only requests for which an object with the P flag set is unknown/unrecognized MUST be rejected." 6) Common PCEP Object We used to have different TLV format. We have now defined a single TLV format for all PCEP object. "A PCEP object may include a set of one or more optional TLV(s). All PCEP TLV have a common format: Type: 2 bytes Lenght: 2 bytes Value =20 A PCEP object TLV is comprised of 2 bytes for the type, 2 bytes specifying the TLV length, and a value field. The Length field defines the length of the value portion in bytes. The TLV is padded to 4-bytes alignment; padding is not included in the Length field (so a three bytes value would have a length of three, but the total size of the TLV would be eight bytes). Unrecognized TLVs MUST be ignored." IANA is requested to managed the PCEP Object TLV. A new registry has been requested. 7) New format for the NO-PATH-VECTOR TLV "The NO-PATH-VECTOR TLV is compliant with the PCEP TLV format defined in section 7.1 and is comprised of 2 bytes for the type, 2 bytes specifying th= e TLV length (length of the value portion in bytes) followed by a fix length value field of 32-bits flags field used to report the reason(s) that led to unsuccessful path computation. TYPE: To be assigned by IANA (suggested value=3D1) LENGTH: 1 VALUE: 32-bits flags field" 8) New format for the OVERLOAD-DURATION TLV "The OVERLOADED-DURATION TLV is compliant with the PCEP TLV format defined in section 7.1 and is comprised of 2 bytes for the type, 2 bytes specifying the TLV length (length of the value portion in bytes) followed by a fix length value field of 32-bits flags field. TYPE: To be assigned by IANA (Suggested Value=3D2) LENGTH: 4 VALUE: 32-bits flags field indicates the estimated PCE congestion duration in seconds." 9) New format for the REQ-MISSING TLV "The REQ-MISSING TLV is compliant with the PCEP TLV format defined in section 7.1 and is comprised of 2 bytes for the type, 2 bytes specifying th= e TLV length (length of the value portion in bytes) followed by a fix length value field of 4 bytes. TYPE: To be assigned by IANA (suggested value=3D3) LENGTH: 4 VALUE: 4 bytes that indicates the request-id-number that corresponds to the missing request."=20 10) Clarification on the SVEC Handling "When a PCE receives a path computation request that cannot be satisfied (for example because the PCReq message contains an object with the P bit se= t that is not supported), the PCE sends a PCErr message for this request (see section 7.2) the PCE MUST cancel the whole set of related path computation requests and MUST send a PCErr message with Error-Type=3D"Synchronized path computation request missing". 11) Change in the FSM with regards to the Collision resolution procedure: "If the system receives an Open message from the PCEP peer before the expiration of the OpenWait timer, the system first examines all of its sessions that are in the OpenWait or KeepWait state. If another session wit= h the same PCEP peer already exists (same IP address), then the system performs the following collision resolution procedure: * If the system has initiated the current session and has a lower IP addres= s than the PCEP Peer, the system closes the TCP connection, releases the PCEP resources for the pending session and moves back to the Idle state. * If the session was initiated by the PCEP peer and the system has a higher IP address that the PCEP Peer, the system closes the TCP connection, releases the PCEP resources for the pending session, and moves back to the Idle state.=20 * Otherwise, the system checks the PCEP session attributes (Keepalive frequency, DeadTimer, ...)." 12) Clarification in the IANA section. Thanks. JP. ------ Forwarded Message > From: > Date: Fri, 16 Nov 2007 16:50:02 -0500 > To: > Cc: > Subject: [Pce] I-D Action:draft-ietf-pce-pcep-09.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 o= f the > IETF. >=20 >=20 > Title : Path Computation Element (PCE) communication Protocol (= PCEP) > Author(s) : A. Ayyangar, et al. > Filename : draft-ietf-pce-pcep-09.txt > Pages : 73 > Date : 2007-11-16 >=20 > This document specifies the Path Computation Element communication > Protocol (PCEP) for communications between a Path Computation Client > (PCC) and a Path Computation Element (PCE), or between two PCEs. > Such interactions include path computation requests and path > computation replies as well as notifications of specific states > related to the use of a PCE in the context of Multiprotocol Label > Switching (MPLS) and Generalized (GMPLS) Traffic Engineering. The > PCEP protocol is designed to be flexible and extensible so as to > easily allow for the addition of further messages and objects, should > further requirements be expressed in the future. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-09.txt >=20 > 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. >=20 > 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-pcep-09.txt". >=20 > 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 >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-pce-pcep-09.txt". >=20 > 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. >=20 > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > Content-Type: text/plain > Content-ID: <2007-11-16164622.I-D\@ietf.org> >=20 > _______________________________________________ > Pce mailing list > Pce@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/pce ------ End of Forwarded Message _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Mon Nov 19 12:15:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuADr-0005kK-Nt; Mon, 19 Nov 2007 12:15:47 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IuADe-0004vb-IO for pce-confirm+ok@megatron.ietf.org; Mon, 19 Nov 2007 12:15:34 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuADd-0004t1-Kr; Mon, 19 Nov 2007 12:15:33 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuADd-0001It-6y; Mon, 19 Nov 2007 12:15:33 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id CFEB2175C0; Mon, 19 Nov 2007 17:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IuAD8-0002oo-BG; Mon, 19 Nov 2007 12:15: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: Date: Mon, 19 Nov 2007 12:15:02 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Cc: pce@ietf.org Subject: [Pce] I-D ACTION:draft-ietf-pce-of-01.txt X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 : Encoding of Objective Functions in Path Computation Element communication Protocol (PCEP) Author(s) : J. Le Roux, et al. Filename : draft-ietf-pce-of-01.txt Pages : 17 Date : 2007-11-19 The computation of one or a series of Traffic Engineering Label Switched Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks, is subject to a set of one or more specific optimization criteria(s), referred to as an objective function (e.g. minimum cost path, widest path, etc.). A Path Computation Element (PCE) may support one or multiple objective functions, and it is desired for a Path Computation Client (PCC) to automatically discover the set of objective functions supported by a PCE. Furthermore, it may be useful for a PCC to specify in a path computation request the required objective function to be used by the PCE to compute a TE LSP or a set of TE LSPs. Thus the aim of this document is to define extensions to the PCE communication Protocol (PCEP) in order to allow a PCC to discover the set of objective functions supported by a PCE as well as to allow a PCC to indicate in a path computation request the required objective function and a PCE to indicate in a path computation reply the objective function that was used for path computation. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-of-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-of-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-of-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. --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: <2007-11-19114406.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-of-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-of-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-19114406.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 Tue Nov 20 11:33:40 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuW2c-0007dl-On; Tue, 20 Nov 2007 11:33:38 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IuW2a-0007cb-VB for pce-confirm+ok@megatron.ietf.org; Tue, 20 Nov 2007 11:33:36 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuW2a-0007cQ-I5; Tue, 20 Nov 2007 11:33:36 -0500 Received: from [202.99.23.227] (helo=people.com.cn) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IuW2Z-0008GF-Hj; Tue, 20 Nov 2007 11:33:36 -0500 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm42474337ea; Wed, 21 Nov 2007 00:46:33 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm217473e6aee; Sat, 17 Nov 2007 06:45:29 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Sat, 17 Nov 2007 06:45:29 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1It94g-0005Yf-2j; Fri, 16 Nov 2007 16:50:06 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1It94d-0005Xz-Fc; Fri, 16 Nov 2007 16:50:03 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1It94d-0002tM-2q; Fri, 16 Nov 2007 16:50:03 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id B330A175E4; Fri, 16 Nov 2007 21:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1It94c-0005FX-8l; Fri, 16 Nov 2007 16: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: Date: Fri, 16 Nov 2007 16:50:02 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-AIMC-AUTH: (null) X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: Internet-Drafts@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 Cc: pce@ietf.org Subject: [Pce] I-D Action:draft-ietf-pce-pcep-09.txt X-BeenThere: pce@lists.ietf.org Reply-To: internet-drafts@ietf.org List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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) communication Protocol (PCEP) Author(s) : A. Ayyangar, et al. Filename : draft-ietf-pce-pcep-09.txt Pages : 73 Date : 2007-11-16 This document specifies the Path Computation Element communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. Such interactions include path computation requests and path computation replies as well as notifications of specific states related to the use of a PCE in the context of Multiprotocol Label Switching (MPLS) and Generalized (GMPLS) Traffic Engineering. The PCEP protocol is designed to be flexible and extensible so as to easily allow for the addition of further messages and objects, should further requirements be expressed in the future. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-09.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-pcep-09.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-pcep-09.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: <2007-11-16164622.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-pcep-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-pcep-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-16164622.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --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 Tue Nov 20 14:29:58 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuYnG-0004z3-HQ; Tue, 20 Nov 2007 14:29:58 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IuYlb-0004Kd-Op for pce-confirm+ok@megatron.ietf.org; Tue, 20 Nov 2007 14:28:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuYlb-0004KV-Es; Tue, 20 Nov 2007 14:28:15 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuYlY-00066A-Mh; Tue, 20 Nov 2007 14:28:15 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns0.neustar.com (Postfix) with ESMTP id 76AD132896; Tue, 20 Nov 2007 19:28:12 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1IuYlY-0004gw-B9; Tue, 20 Nov 2007 14:28:12 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: Greg Jones From: Adrian Farrel (IETF PCE WG) Message-Id: Date: Tue, 20 Nov 2007 14:28:12 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 X-Mailman-Approved-At: Tue, 20 Nov 2007 14:29:57 -0500 Cc: Scott Bradner , Stephen Trowbridge , PCE Working Group , Dave Ward , Ross Callon , Malcolm Betts , Kam Lam Subject: [Pce] New Liaison Statement, "Application of PCE to Inter-Layer Networks" X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Title: Application of PCE to Inter-Layer Networks Submission Date: 2007-11-20 URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=384 From: Adrian Farrel(IETF PCE WG) To: ITU-T Q12/15 and Q14/15(Greg Jones ) Cc: Stephen Trowbridge Kam Lam Malcolm Betts Ross Callon Dave Ward Scott Bradner PCE Working Group Reponse Contact: Adrian Farrel JP Vasseur Technical Contact: Adrian Farrel JP Vasseur Purpose: For information Body: The Path Computation Element (PCE) working group of the IETF is aware that your Questions have recently been discussing the inter-layer aspects of the ASON architecture and particularly how to select routes across a multi-layer network, and how to represent within a higher layer network the potential or real connectivity across a lower layer network. In the light of G.7715.2 we believe that you may be interested in some work being discussed in the PCE working group. "Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering" may be found at http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-frwk-05.txt. This document should be read in the context of the general PCE architecture described in "A Path Computation Element (PCE)-Based Architecture" http://www.ietf.org/rfc/rfc4655.txt Although not specifically targeted at the ASON architecture, we would welcome any comments that you have on draft-ietf-pce-inter-layer-frwk-05.txt, and invite interested parties to contribute either through the liaison process or via the PCE working group mailing list details of which can be found at the PCE working group charter page http://www.ietf.org/html.charters/pce-charter.html We are also looking at the requirements driven by inter-layer routing for extensions to the PCE Protocol (PCEP) used for communication between Path Computation Clients (PCCs) and PCEs. These can be found in "PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic Engineering " http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-req-05.txt Best regards, JP Vasseur and Adrian Farrel IETF PCE working group co-chairs Attachment(s): No document has been attached _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Sat Nov 24 06:18:34 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ivt1g-000598-Qh; Sat, 24 Nov 2007 06:18:20 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1Ivt1e-00058h-RK for pce-confirm+ok@megatron.ietf.org; Sat, 24 Nov 2007 06:18:18 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ivt1Z-00056h-3p; Sat, 24 Nov 2007 06:18:13 -0500 Received: from [202.99.23.227] (helo=people.com.cn) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1Ivt1Y-0000Vf-19; Sat, 24 Nov 2007 06:18:13 -0500 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm654748320e; Sat, 24 Nov 2007 19:31:09 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm1c474207bc; Tue, 20 Nov 2007 01:33:09 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Tue, 20 Nov 2007 01:33:09 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuADr-0005ZN-0l; Mon, 19 Nov 2007 12:15:47 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuADd-0004t1-Kr; Mon, 19 Nov 2007 12:15:33 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuADd-0001It-6y; Mon, 19 Nov 2007 12:15:33 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id CFEB2175C0; Mon, 19 Nov 2007 17:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IuAD8-0002oo-BG; Mon, 19 Nov 2007 12:15: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: Date: Mon, 19 Nov 2007 12:15:02 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-AIMC-AUTH: (null) X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: Internet-Drafts@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: pce@ietf.org Subject: [Pce] I-D ACTION:draft-ietf-pce-of-01.txt X-BeenThere: pce@lists.ietf.org Reply-To: internet-drafts@ietf.org List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 : Encoding of Objective Functions in Path Computation Element communication Protocol (PCEP) Author(s) : J. Le Roux, et al. Filename : draft-ietf-pce-of-01.txt Pages : 17 Date : 2007-11-19 The computation of one or a series of Traffic Engineering Label Switched Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks, is subject to a set of one or more specific optimization criteria(s), referred to as an objective function (e.g. minimum cost path, widest path, etc.). A Path Computation Element (PCE) may support one or multiple objective functions, and it is desired for a Path Computation Client (PCC) to automatically discover the set of objective functions supported by a PCE. Furthermore, it may be useful for a PCC to specify in a path computation request the required objective function to be used by the PCE to compute a TE LSP or a set of TE LSPs. Thus the aim of this document is to define extensions to the PCE communication Protocol (PCEP) in order to allow a PCC to discover the set of objective functions supported by a PCE as well as to allow a PCC to indicate in a path computation request the required objective function and a PCE to indicate in a path computation reply the objective function that was used for path computation. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-of-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-of-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-of-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. --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: <2007-11-19114406.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-of-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-of-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-19114406.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --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 Nov 26 14:59:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iwk7Q-0008HE-56; Mon, 26 Nov 2007 14:59:48 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1Iwk7P-0008H4-I5 for pce-confirm+ok@megatron.ietf.org; Mon, 26 Nov 2007 14:59:47 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iwk7P-0008Gw-8W for pce@ietf.org; Mon, 26 Nov 2007 14:59:47 -0500 Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iwk7L-0001mr-8t for pce@ietf.org; Mon, 26 Nov 2007 14:59:47 -0500 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Nov 2007 20:59:41 +0100 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-of-01.txt Date: Mon, 26 Nov 2007 20:59:40 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Pce] I-D ACTION:draft-ietf-pce-of-01.txt Thread-Index: Acgqz/FcErK1ioyoRtSVy8vHXet0WgFlEvkw References: From: "LE ROUX Jean-Louis RD-CORE-LAN" To: X-OriginalArrivalTime: 26 Nov 2007 19:59:41.0775 (UTC) FILETIME=[E212F5F0:01C83066] X-Spam-Score: 0.0 (/) X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7 Cc: X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Hi all, Here are the changes in this new revision: -The discovery of the Objective Functions (OF) supported by a PCE used = to rely on the PCED TLV carried in ISIS/OSPF. Actually for scalability = reasons, the OSPF/ISIS PCED TLV has been closed, and no new sub-TLVs can = be added, so we can no longer rely on the PCED TLV for OF discovery.=20 Following the requirements set forth in RFC 4657 & 4674, and as OF can = be considered as a detailed capability, its discovery could rely on = PCEP.=20 For that purpose we moved OF discovery from ISIS/OSPF to PCEP. A new = PCEP TLV has been defined, the OF-List TLV, to be carried within the = Open object. This allows discovering the OF supported by a PCE during = session setup phase. -We factorized the transport of the OF in a PCRep for a synchronized = computation: "When the PCE wants to indicate to the PCC the objective function that = was used for the synchronized computation of a set of paths, the PCRep = message MUST include the corresponding SVEC object directly followed by = the OF object, which MUST NOT be repeated for each elementary request." -Also we made some rewording for the sake of clarity. Of course your feedback/comments are welcome. Regards, J-L, J-P, Young > -----Message d'origine----- > De : Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 > Envoy=E9 : lundi 19 novembre 2007 18:15 > =C0 : i-d-announce@ietf.org > Cc : pce@ietf.org > Objet : [Pce] I-D ACTION:draft-ietf-pce-of-01.txt=20 >=20 > A New Internet-Draft is available from the on-line=20 > Internet-Drafts directories. > This draft is a work item of the Path Computation Element=20 > Working Group of the IETF. >=20 > Title : Encoding of Objective Functions in=20 > Path Computation Element communication Protocol (PCEP) > Author(s) : J. Le Roux, et al. > Filename : draft-ietf-pce-of-01.txt > Pages : 17 > Date : 2007-11-19 > =09 > The computation of one or a series of Traffic Engineering Label=20 > Switched Paths (TE LSPs) in MultiProtocol Label Switching=20 > (MPLS) and=20 > Generalized MPLS (GMPLS) networks, is subject to a set of=20 > one or more=20 > specific optimization criteria(s), referred to as an objective=20 > function (e.g. minimum cost path, widest path, etc.). A Path=20 > Computation Element (PCE) may support one or multiple objective=20 > functions, and it is desired for a Path Computation Client=20 > (PCC) to=20 > automatically discover the set of objective functions=20 > supported by a=20 > PCE. Furthermore, it may be useful for a PCC to specify in a path=20 > computation request the required objective function to be=20 > used by the=20 > PCE to compute a TE LSP or a set of TE LSPs. Thus the aim of this=20 > document is to define extensions to the PCE communication Protocol=20 > (PCEP) in order to allow a PCC to discover the set of objective=20 > functions supported by a PCE as well as to allow a PCC to=20 > indicate in=20 > a path computation request the required objective function=20 > and a PCE=20 > to indicate in a path computation reply the objective=20 > function that=20 > was used for path computation. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-pce-of-01.txt >=20 > To remove yourself from the I-D Announcement list, send a=20 > message to i-d-announce-request@ietf.org with the word=20 > unsubscribe in the body of the message.=20 > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. >=20 > Internet-Drafts are also available by anonymous FTP. Login=20 > with the username "anonymous" and a password of your e-mail=20 > address. After logging in, type "cd internet-drafts" and then=20 > "get draft-ietf-pce-of-01.txt". >=20 > A list of Internet-Drafts directories can be found in=20 > http://www.ietf.org/shadow.html or=20 > ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-pce-of-01.txt". > =09 > 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=20 > 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. >=20 > Below is the data which will enable a MIME compliant mail=20 > reader implementation to automatically retrieve the ASCII=20 > version of the Internet-Draft. >=20 _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Thu Nov 29 16:03:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxqXb-0005ol-Or; Thu, 29 Nov 2007 16:03:23 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IxqXa-0005oX-BG for pce-confirm+ok@megatron.ietf.org; Thu, 29 Nov 2007 16:03:22 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxqXa-0005oM-0f for pce@ietf.org; Thu, 29 Nov 2007 16:03:22 -0500 Received: from asmtp1.iomartmail.com ([62.128.201.248]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IxqXZ-0007yh-HK for pce@ietf.org; Thu, 29 Nov 2007 16:03:21 -0500 Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id lATL3KHB007109 for ; Thu, 29 Nov 2007 21:03:20 GMT Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id lATL3HIZ007079 for ; Thu, 29 Nov 2007 21:03:20 GMT Message-ID: <0c4c01c832cb$42a81240$0200a8c0@your029b8cecfe> From: "Adrian Farrel" To: Date: Thu, 29 Nov 2007 21:02:31 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: Subject: [Pce] Discussion of distribution of TE information from outside the AS X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org Hi, Various recent drafts have been floated at CCAMP that propose different mechanisms for distributing TE information from outside the AS within the AS. We plan a chunk of our time at our Vancouver meeting (Tuesday, 9.00-11.30) to discuss this topic and look at the I-Ds. The objective is to clarify what is in scope and what is out of scope before moving further forward with anything. Please see our agenda at http://www3.ietf.org/proceedings/07dec/agenda/ccamp.htm to see a full list of the relevant I-Ds. And have a look at a set of overview slides I have written and placed at http://www3.ietf.org/proceedings/07dec/slides/ccamp-2.ppt You are all very welcome to attend CCAMP to throw peanuts (or speak at the mic). And, of course, contributions on the CCAMP mailing list before, during, or after, will be valued. Thanks, Adrian _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Fri Nov 30 16:38:32 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyDZ9-00042L-BS; Fri, 30 Nov 2007 16:38:31 -0500 Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IyDZ8-00041z-Cf for pce-confirm+ok@megatron.ietf.org; Fri, 30 Nov 2007 16:38:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyDZ8-00041p-2G for pce@ietf.org; Fri, 30 Nov 2007 16:38:30 -0500 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IyDZ7-000209-Or for pce@ietf.org; Fri, 30 Nov 2007 16:38:30 -0500 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 30 Nov 2007 16:38:30 -0500 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lAULcT2E027162 for ; Fri, 30 Nov 2007 16:38:29 -0500 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lAULcS0m015615 for ; Fri, 30 Nov 2007 21:38:29 GMT Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Nov 2007 16:38:09 -0500 Received: from 10.86.104.180 ([10.86.104.180]) by xmb-rtp-213.amer.cisco.com ([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; Fri, 30 Nov 2007 21:38:09 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Fri, 30 Nov 2007 16:38:07 -0500 From: JP Vasseur To: Message-ID: Thread-Topic: Thanks to send your slides if you have a discussion slot in Vancouver. Thread-Index: AcgzmUuDifv045+MEdyp5QANk8WjQA== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 30 Nov 2007 21:38:09.0816 (UTC) FILETIME=[4D317980:01C83399] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2; t=1196458709; x=1197322709; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20 |Subject:=20Thanks=20to=20send=20your=20slides=20if=20you=20have=20a=20di scussion=20slot=20in=0A=20Vancouver. |Sender:=20 |To:=20; bh=frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY=; b=eb3XI/XdvFSIu1orgfwc/cYzY1fk/NO9YMkMq0y8kVbRc0pVMJFkqlIAQl5GKBxDogp0m5Fm n3wJP8eChW4jcbWhKUVE4OPufY8bmDq7S/d+17fl14So2tBoQkaJvera; Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); X-Spam-Score: -4.0 (----) X-Scan-Signature: bb8eae9af85e4fcfe76f325e38493bf4 Cc: Subject: [Pce] Thanks to send your slides if you have a discussion slot in Vancouver. X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce