From mailman-bounces@ietf.org Wed Dec 1 06:11:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13925 for ; Wed, 1 Dec 2004 06:11:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZSTO-0005cw-TQ for pce-archive@ietf.org; Wed, 01 Dec 2004 06:16:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZRnA-0001RT-CP for pce-archive@ietf.org; Wed, 01 Dec 2004 05:33:00 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: lists.ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: pce-archive@ietf.org X-No-Archive: yes Message-ID: Date: Wed, 01 Dec 2004 05:25:14 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your lists.ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@lists.ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@lists.ietf.org. Thanks! Passwords for pce-archive@ietf.org: List Password // URL ---- -------- pce@lists.ietf.org geebfe https://www1.ietf.org/mailman/options/pce/pce-archive%40ietf.org From pce-bounces@ietf.org Sun Dec 19 18:04:01 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17814; Sun, 19 Dec 2004 18:04:01 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgAF0-0005gK-AZ; Sun, 19 Dec 2004 18:13:31 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgA4j-0008Ku-NN; Sun, 19 Dec 2004 18:02:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgA3E-0006vZ-7G for pce@megatron.ietf.org; Sun, 19 Dec 2004 18:01:20 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17676 for ; Sun, 19 Dec 2004 18:01:17 -0500 (EST) Received: from galaxy.systems.pipex.net ([62.241.162.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgACJ-0005bh-Uj for pce@ietf.org; Sun, 19 Dec 2004 18:10:47 -0500 Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by galaxy.systems.pipex.net (Postfix) with ESMTP id 40DB2E00013F for ; Sun, 19 Dec 2004 23:00:40 +0000 (GMT) Received: from Puppy ([217.158.132.209] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 19 Dec 2004 22:57:07 +0000 Message-ID: <01b601c4e61e$324a1620$4a849ed9@Puppy> From: "Adrian Farrel" To: Date: Sun, 19 Dec 2004 19:53:50 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-OriginalArrivalTime: 19 Dec 2004 22:57:08.0051 (UTC) FILETIME=[10EBC230:01C4E61E] X-Spam-Score: 0.7 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Subject: [Pce] PCE BOF/WG Update 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: , Sender: pce-bounces@ietf.org Errors-To: pce-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit Hi, Since some of you have been asking, I thought you might all appreciate an update on the status. JP and I have been working with Alex and Bill to tidy up the proposed charter and this is now looking pretty good. We have had initial feed-back from various members of the IESG and this has led to some more fine-tuning. The revised charter will be taken to the next IESG telechat for (dis)approval and we can expect to know a decision shortly after that. Adrian _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@ietf.org Tue Dec 21 15:19:47 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15825; Tue, 21 Dec 2004 15:19:47 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgqdY-0006Lt-4c; Tue, 21 Dec 2004 15:29:40 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgqSv-000252-IG; Tue, 21 Dec 2004 15:18:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgqCb-0007py-Of for pce@megatron.ietf.org; Tue, 21 Dec 2004 15:01:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13620 for ; Tue, 21 Dec 2004 15:01:48 -0500 (EST) Received: from web53204.mail.yahoo.com ([206.190.39.220]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CgqM7-0005tb-Dt for pce@ietf.org; Tue, 21 Dec 2004 15:11:40 -0500 Received: (qmail 80286 invoked by uid 60001); 21 Dec 2004 20:01:17 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=p7+bHcjhrA99DDf/nEvWapvlACJSXpsTUlGPkM60/bytu2u20y7owdgeSZ3y1xnWbGIPe/lq9gwy+BlSa7AIeRJeZ6lBM1Jo7ZMpb+CRFYEztttmVCsvF66vMfZ7PU+pNXb6yDWo5H5g9NXVkgsLiaLZSf7iAsHaVUquN1bHNAM= ; Message-ID: <20041221200117.80284.qmail@web53204.mail.yahoo.com> Received: from [206.54.51.125] by web53204.mail.yahoo.com via HTTP; Tue, 21 Dec 2004 12:01:17 PST Date: Tue, 21 Dec 2004 12:01:17 -0800 (PST) From: Rajeev Manur Subject: Re: [Pce] PCE BOF/WG Update To: pce@ietf.org In-Reply-To: <01b601c4e61e$324a1620$4a849ed9@Puppy> MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 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="===============2085469367==" Sender: pce-bounces@ietf.org Errors-To: pce-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 --===============2085469367== Content-Type: multipart/alternative; boundary="0-215944445-1103659277=:76121" --0-215944445-1103659277=:76121 Content-Type: text/plain; charset=us-ascii All: Can someone clarify if this PCE work group scope involves GMPLS only OR this is also relevant and applies to regular psn based MPLSTE? Thanks with regards, Rajeev Adrian Farrel wrote: Hi, Since some of you have been asking, I thought you might all appreciate an update on the status. JP and I have been working with Alex and Bill to tidy up the proposed charter and this is now looking pretty good. We have had initial feed-back from various members of the IESG and this has led to some more fine-tuning. The revised charter will be taken to the next IESG telechat for (dis)approval and we can expect to know a decision shortly after that. Adrian _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce --------------------------------- Do you Yahoo!? Send holiday email and support a worthy cause. Do good. --0-215944445-1103659277=:76121 Content-Type: text/html; charset=us-ascii
All:
 
Can someone clarify if this PCE work group scope involves GMPLS only OR this is also relevant and applies to regular psn based MPLSTE? Thanks
 
with regards,
Rajeev
 
 

Adrian Farrel <adrian@olddog.co.uk> wrote:
Hi,

Since some of you have been asking, I thought you might all appreciate an
update on the status.

JP and I have been working with Alex and Bill to tidy up the proposed
charter and this is now looking pretty good. We have had initial feed-back
from various members of the IESG and this has led to some more
fine-tuning.

The revised charter will be taken to the next IESG telechat for
(dis)approval and we can expect to know a decision shortly after that.

Adrian


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

Do you Yahoo!?
Send holiday email and support a worthy cause. Do good. --0-215944445-1103659277=:76121-- --===============2085469367== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce --===============2085469367==-- From pce-bounces@ietf.org Tue Dec 21 17:26:20 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05800; Tue, 21 Dec 2004 17:26:20 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cgsc2-0004md-2p; Tue, 21 Dec 2004 17:36:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgs9x-0006P8-EJ; Tue, 21 Dec 2004 17:07:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgs37-00035X-4t for pce@megatron.ietf.org; Tue, 21 Dec 2004 17:00:09 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00902 for ; Tue, 21 Dec 2004 17:00:06 -0500 (EST) Received: from astro.systems.pipex.net ([62.241.163.6]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgsCe-0003Et-Ty for pce@ietf.org; Tue, 21 Dec 2004 17:10:01 -0500 Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by astro.systems.pipex.net (Postfix) with ESMTP id 3C8DFE0001B5; Tue, 21 Dec 2004 21:59:35 +0000 (GMT) Received: from Puppy ([217.158.145.220] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 21 Dec 2004 21:58:11 +0000 Message-ID: <03a201c4e7a8$4c3e4d90$4a849ed9@Puppy> From: "Adrian Farrel" To: "Rajeev Manur" , References: <20041221200117.80284.qmail@web53204.mail.yahoo.com> Subject: Re: [Pce] PCE BOF/WG Update Date: Tue, 21 Dec 2004 21:56:48 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-OriginalArrivalTime: 21 Dec 2004 21:58:12.0184 (UTC) FILETIME=[2A34C580:01C4E7A8] X-Spam-Score: 0.1 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit 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: , Sender: pce-bounces@ietf.org Errors-To: pce-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7bit Rajeev, > Can someone clarify if this PCE work group scope involves GMPLS only OR this is also relevant and applies to regular psn based MPLSTE? Thanks With pleasure. PCE applies to MPLS-TE and GMPLS controlled networks of PSN and non-PSN capabilities. The current proposed charter begins with the words: The PCE Working Group is chartered to specify a Path Computation Element (PCE) based architecture for the computation of paths for MPLS and GMPLS Traffic Engineering LSPs [In case there should be any lack of clarity: GMPLS is a control plane technology suitable for the control of PSN.] Cheers, Adrian _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@ietf.org Thu Dec 23 14:19:19 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10789; Thu, 23 Dec 2004 14:19:19 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChYeX-0004fj-KO; Thu, 23 Dec 2004 14:29:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ChYNd-0001wt-5x; Thu, 23 Dec 2004 14:12:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ChYIv-00010H-W0; Thu, 23 Dec 2004 14:07:18 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09150; Thu, 23 Dec 2004 14:07:16 -0500 (EST) Message-Id: <200412231907.OAA09150@ietf.org> From: The IESG To: IETF-Announce@ietf.org Date: Thu, 23 Dec 2004 14:07:15 -0500 Cc: pce@ietf.org Subject: [Pce] WG Review: Path Computation Element (pce) X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: pce-bounces@ietf.org Errors-To: pce-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 A new IETF working group has been proposed in the Routing Area. The IESG has not made any determination as yet. The following description was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by December 30th. +++ Path Computation Element (pce) ================================ Current Status: Proposed Working Group Description of Working Group: The PCE Working Group is chartered to specify a Path Computation Element (PCE) based architecture for the computation of paths for MPLS and GMPLS Traffic Engineering LSPs. In this architecture path computation does not occur on the head-end (ingress) LSR, but on some other path computation entity that may physically not be located on the head-end LSR. The PCE WG will work on application of this model within a single domain or within a small group of domains (where a domain is a layer, IGP area or Autonomous System with limited visibility from the head-end LSR). At this time, applying this model to large groups of domains such as the Internet is not thought to be possible, and the PCE WG will not spend energy on that topic. The WG will specify a protocol for communication between LSRs (termed Path Computation Clients - PCCs) and PCEs, and between cooperating PCEs. This protocol will be capable of representing requests for path computation including a full set of constraints, will be able to return multiple paths, and will include security mechanisms such as authentication and confidentiality. The WG will determine requirements for extensions to existing routing and signaling protocols in support of PCE discovery and signaling of inter-domain paths. Candidate protocols for extensions are RSVP-TE, OSPF-TE, ISIS-TE and BGP. Any necessary extensions will be produced in collaboration with the Working Groups responsible for the protocols. The Working Group will also work on the definition of metrics to evaluate path quality, scalability, responsiveness and robustness of path computation models. Work Items: - Functional specification of MPLS and GMPLS Traffic Engineered LSP path computation models involving Path Computation Element(s). This includes the case of computing the paths of intra and inter-domain TE LSPs. Such path computation includes the generation of primary, protection and recovery paths, as well as computations for (local/global) reoptimization and load balancing. The WG will address the inter-area (single IGP domain) scenario first. WG progress will be evaluated before inter-AS related work is started. - Specification of the PCE-based architecture. - Specification of requirements and protocol extensions related to the policy, and security aspects of PCE-based path computation involving PCEs of multiple administrative entities. - In cooperation with protocol specific Working Group (OSPF, ISIS, IDR, MPLS, CCAMP), development of routing (OSPF, ISIS, BGP) and LSP signaling (RSVP-TE) extensions required to support PCE-based path computation models. - Specification of techniques in support of PCE discovery within and across domains. Where such techniques result in the extensions of existing protocols (OSPF, ISIS and BGP), this work will be done in conjunction with the appropriate WGs. - Specification of a new communication protocol for use between a PCC and a PCE, and between PCEs. A single protocol will be selected from among candidates that include the existing protocols defined in other WGs. - Definition of objective metrics to evaluate various criteria such as the measurement of path quality, response time, robustness and scalability of path computation models. Review of the document "Requirements for path computation element in GMPLS inter-domain networks" produced by the CCAMP WG. _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce