From pce-bounces@lists.ietf.org Mon Jun 04 08:43:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvBu4-0002B3-JV; Mon, 04 Jun 2007 08:43:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvBu3-0002Ax-Cm for pce@lists.ietf.org; Mon, 04 Jun 2007 08:43:19 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HvBu1-0004lY-Us for pce@lists.ietf.org; Mon, 04 Jun 2007 08:43:19 -0400 Received: (qmail 25165 invoked by uid 0); 4 Jun 2007 12:43:15 -0000 Received: from 192.35.17.11 by www129.gmx.net with HTTP; Mon, 04 Jun 2007 14:43:14 +0200 (CEST) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Jun 2007 14:43:14 +0200 From: _den@gmx.de In-Reply-To: Message-ID: <20070604124314.194340@gmx.net> MIME-Version: 1.0 References: To: pce@lists.ietf.org X-Authenticated: #19887475 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1+e/IxBqWeeOPux6dmwSHRmop/8PX+sURF2NP5WAq tZT1b+WbOF+RfQVCmtaikMiNtsMgJECTmwrw== X-GMX-UID: 0D5Rd58jbUk7LkVGHWknWs5sZ2hlN4qT X-Spam-Score: 0.2 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [Pce] Contradiction in Idle state 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 In the description of the Idle state you can find: " - Initiates of a TCP connection with the PCEP peer, - Increments the TCPRetry variable " 1)This seems to be in contradiction with the definition of the TCPRetry variable. 2)This variable can be only incremented in TCPPending state, because only in that state it is possible to determine if connection was established or not. -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Mon Jun 04 10:43:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvDm6-00089s-GY; Mon, 04 Jun 2007 10:43:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvDm4-00086S-Lw for pce@lists.ietf.org; Mon, 04 Jun 2007 10:43:13 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HvDm2-0007C4-5L for pce@lists.ietf.org; Mon, 04 Jun 2007 10:43:12 -0400 Received: (qmail 6954 invoked by uid 0); 4 Jun 2007 14:43:09 -0000 Received: from 192.35.17.15 by www086.gmx.net with HTTP; Mon, 04 Jun 2007 16:43:09 +0200 (CEST) Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 04 Jun 2007 16:43:09 +0200 From: _den@gmx.de In-Reply-To: Message-ID: <20070604144309.152130@gmx.net> MIME-Version: 1.0 References: To: pce@lists.ietf.org X-Authenticated: #19887475 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1+FJn1JwBqFhguT7CoeavjJg2wYv12Y1puM4b9157 WXWZ78rFV4b03/B6OIFweG+dqg3Zq2DvYOCA== X-GMX-UID: yhJXcg9zTXsucQARTmU5rupCRzdyMgNw X-Spam-Score: 0.2 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Subject: [Pce] Comment on KeepWait state 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 The reception of an malformed message will be mentioned in OpenWait and UP state, but not in KeepWait state. Why? -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Mon Jun 04 11:30:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvEVO-0007dD-8y; Mon, 04 Jun 2007 11:30:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvEVN-0007aI-BF for pce@lists.ietf.org; Mon, 04 Jun 2007 11:30:01 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HvEVL-000528-Qi for pce@lists.ietf.org; Mon, 04 Jun 2007 11:30:01 -0400 Received: (qmail 32122 invoked by uid 0); 4 Jun 2007 15:29:59 -0000 Received: from 192.35.17.30 by www112.gmx.net with HTTP; Mon, 04 Jun 2007 17:29:58 +0200 (CEST) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Jun 2007 17:29:59 +0200 From: _den@gmx.de In-Reply-To: Message-ID: <20070604152959.279500@gmx.net> MIME-Version: 1.0 References: To: pce@lists.ietf.org X-Authenticated: #19887475 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX18w5pVYzbgwakGxbuMoDbSSki+2iN8oasjlJf7rck UTDf67fe+56MSNF7Cw7hUW1nlGjiB46ald4A== X-GMX-UID: kUsMCxUMbHIhcgFNFjU0r9AiJihyapCn X-Spam-Score: 0.2 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: [Pce] Additional comment on KeepWait state 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 In the description of this state: " 2. If the proposed values are acceptable, the system adjusts its PCEP session characteristics according to the proposed values received in the PCErr message restarts the KeepWait timer and sends a new Open message. If RemoteOK=1, the system stays in the KeepWait state. If RemoteOK=0, the system moves to the OpenWait state. " If moving to OpenWait state OpenWait timer should be started and not Keepwait timer. In the OpenWait state it will not be waited for the expiration of the Keepwait timer. -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Mon Jun 04 13:36:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvGU7-00052t-H1; Mon, 04 Jun 2007 13:36:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvGU6-00052l-19 for pce@lists.ietf.org; Mon, 04 Jun 2007 13:36:50 -0400 Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvGU4-0007tM-Lk for pce@lists.ietf.org; Mon, 04 Jun 2007 13:36:50 -0400 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Jun 2007 19:36:35 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Pce] Additional comment on KeepWait state Date: Mon, 4 Jun 2007 19:36:40 +0200 Message-ID: In-Reply-To: <20070604152959.279500@gmx.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Pce] Additional comment on KeepWait state Thread-Index: AcemvUSYQNxB/fbyQbyk26BVZ/RnXQAAJrIw References: <20070604152959.279500@gmx.net> From: "LE ROUX Jean-Louis RD-CORE-LAN" To: <_den@gmx.de>, X-OriginalArrivalTime: 04 Jun 2007 17:36:35.0865 (UTC) FILETIME=[E62ED090:01C7A6CE] X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da 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 Den, Thanks for these useful comments on the PCEP FSM. I'm bundling the answers: Comment 1: > In the description of the Idle state you can find: >=20 > " - Initiates of a TCP connection with the PCEP peer, > - Increments the TCPRetry variable > " >=20 > 1)This seems to be in contradiction with the definition of=20 > the TCPRetry variable. >=20 > 2)This variable can be only incremented in TCPPending state,=20 > because only in that state it is possible to determine if=20 > connection was established or not.=20 You are right, the processing is not consistent with the definition. This will be updated in next revision. Comment 2: >The reception of an malformed message will be mentioned in OpenWait=20 >and UP state, but not in KeepWait state. Why? This is an omission that will be rectified. Of course this applies to this state as well. Comment 3: > In the description of this state: > " > 2. If the proposed values are acceptable, the system adjusts its > PCEP session characteristics according to the proposed values > received in the PCErr message restarts the KeepWait timer and > sends a new Open message. If RemoteOK=3D1, the system=20 > stays in the > KeepWait state. If RemoteOK=3D0, the system moves to=20 > the OpenWait > state. > " >=20 > If moving to OpenWait state OpenWait timer should be started=20 > and not Keepwait timer. In the OpenWait state it will not be=20 > waited for the expiration of the Keepwait timer. Actually the OpenWait timer has been started earlier. Here you send an Open, so you start a Keepwait timer.=20 But I agree there is something missing. We need to process Keepwait/OpenWait timer expiration events both in Keepwait and OpenWait states.=20 By the way that would actually be simpler to define a single timer to control session setup, as in BGP. Note that the FSM will be consolidated in rev 08, and this will account for your comments. Kind Regards, J-L _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Tue Jun 05 08:28:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvY9R-0001HE-VY; Tue, 05 Jun 2007 08:28:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvY9Q-0001H0-JA for pce@ietf.org; Tue, 05 Jun 2007 08:28:40 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvY9P-0003DS-BB for pce@ietf.org; Tue, 05 Jun 2007 08:28:40 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 05 Jun 2007 08:28:39 -0400 X-IronPort-AV: i="4.16,385,1175486400"; d="scan'208"; a="122807133:sNHT38392310" Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l55CSdZk028251 for ; Tue, 5 Jun 2007 08:28:39 -0400 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 l55CSB65010697 for ; Tue, 5 Jun 2007 12:28:39 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Jun 2007 08:28:29 -0400 Received: from [10.86.104.179] ([10.86.104.179]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Jun 2007 08:28:28 -0400 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: pce@ietf.org From: JP Vasseur Date: Tue, 5 Jun 2007 08:28:10 -0400 X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 05 Jun 2007 12:28:28.0925 (UTC) FILETIME=[058562D0:01C7A76D] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=147; t=1181046519; x=1181910519; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20 |Subject:=20Adopting=20draft-lee-pce-global-concurrent-optimization-04.tx t=20as=20a=20WG=20document=20? |Sender:=20 |To:=20pce@ietf.org; bh=+ZyveDEaebd1j6FAlZ9SLN9WlJu+5JPU7a/vOfm0+MQ=; b=OoeUhtqdI8czKmbmmR5Fj604otuJ0ITnu1hkKTI1pJ1OoCqC49YBW3GtSmGqVq8kjFBRzA5R Bwo0Zm2Rbx20I0r2iBuHhsQC9G6zddA93Mz37V4fKvZhLKOg74XGWQq6; Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Cc: Subject: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? 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, Do you support the adoption of draft-lee-pce-global-concurrent- optimization-04.txt as a Working Group document ? Thanks. JP. _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Wed Jun 06 13:54:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvzhm-0005R8-PM; Wed, 06 Jun 2007 13:53:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvzhm-0005R0-2C for pce@ietf.org; Wed, 06 Jun 2007 13:53:58 -0400 Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvzhk-0004sQ-JP for pce@ietf.org; Wed, 06 Jun 2007 13:53:58 -0400 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JJ800L9W70NH9@szxga03-in.huawei.com> for pce@ietf.org; Thu, 07 Jun 2007 01:53:11 +0800 (CST) Received: from dan (47-251.3-85.cust.bluewin.ch [85.3.251.47]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JJ800JZB6Y8VV@szxga03-in.huawei.com> for pce@ietf.org; Thu, 07 Jun 2007 01:53:11 +0800 (CST) Date: Wed, 06 Jun 2007 19:50:46 +0200 From: Dan Li Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? To: JP Vasseur , pce@ietf.org Message-id: <001b01c7a863$8b177ef0$3401a8c0@dan> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Mailer: Microsoft Outlook Express 6.00.2900.3028 Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 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 I support this draft to be a WG doc. Thanks, Dan ----- Original Message ----- From: "JP Vasseur" To: Sent: Tuesday, June 05, 2007 2:28 PM Subject: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? > Dear WG, > > Do you support the adoption of draft-lee-pce-global-concurrent- > optimization-04.txt as a Working Group document ? > > Thanks. > > JP. > > _______________________________________________ > 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 Wed Jun 06 17:23:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw2yO-0004pg-Fh; Wed, 06 Jun 2007 17:23:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw2yN-0004pb-D6 for pce@ietf.org; Wed, 06 Jun 2007 17:23:19 -0400 Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hw2yL-0007yb-4X for pce@ietf.org; Wed, 06 Jun 2007 17:23:19 -0400 Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JJ80027BGLG48@usaga01-in.huawei.com> for pce@ietf.org; Wed, 06 Jun 2007 14:20:04 -0700 (PDT) Received: from Yong73674 (185.81.203.62.cust.bluewin.ch [62.203.81.185]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JJ8004DOGL8OK@usaga01-in.huawei.com> for pce@ietf.org; Wed, 06 Jun 2007 14:20:04 -0700 (PDT) Date: Wed, 06 Jun 2007 16:19:58 -0500 From: Lucy Yong Subject: RE: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? In-reply-to: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> To: 'JP Vasseur' , pce@ietf.org Message-id: <011101c7a880$735af6d0$9001a8c0@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Thread-index: AcenbRgLNXTEVJw4TayVSfZh5CjDwgBExg+g X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 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 I support this draft as a WG document. Lucy -----Original Message----- From: JP Vasseur [mailto:jvasseur@cisco.com] Sent: Tuesday, June 05, 2007 7:28 AM To: pce@ietf.org Subject: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? Dear WG, Do you support the adoption of draft-lee-pce-global-concurrent- optimization-04.txt as a Working Group document ? Thanks. JP. _______________________________________________ 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 Wed Jun 06 19:33:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw503-0003HF-0O; Wed, 06 Jun 2007 19:33:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw502-0003HA-07 for pce@ietf.org; Wed, 06 Jun 2007 19:33:10 -0400 Received: from tama55.ecl.ntt.co.jp ([129.60.39.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hw500-0008K5-4C for pce@ietf.org; Wed, 06 Jun 2007 19:33:09 -0400 Received: from sfs2.rdh.ecl.ntt.co.jp (IDENT:mirapoint@sfs2.rdh.ecl.ntt.co.jp [129.60.39.117]) by tama55.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l56NWP1o016754; Thu, 7 Jun 2007 08:33:05 +0900 (JST) Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp [129.60.39.114]) by sfs2.rdh.ecl.ntt.co.jp (MOS 3.8.3-GA) with ESMTP id ANN02118; Thu, 7 Jun 2007 08:33:05 +0900 (JST) Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 0183120AE29; Thu, 7 Jun 2007 08:33:04 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100]) by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id B559720AE2E; Thu, 7 Jun 2007 08:33:04 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l56NX4L4029032; Thu, 7 Jun 2007 08:33:04 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l56NX3u2003726; Thu, 7 Jun 2007 08:33:04 +0900 (JST) Received: from imc.m.ecl.ntt.co.jp (imc0.m.ecl.ntt.co.jp [129.60.5.141]) by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l56NX3nR003723; Thu, 7 Jun 2007 08:33:03 +0900 (JST) Received: from [127.0.0.1] ([129.60.80.148]) by imc.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l56NX1l9011832; Thu, 7 Jun 2007 08:33:03 +0900 (JST) Message-ID: <4667442C.8020200@lab.ntt.co.jp> Date: Thu, 07 Jun 2007 08:33:00 +0900 From: Kohei Shiomoto User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: JP Vasseur Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> In-Reply-To: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: pce@ietf.org 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 Yes, I support it. JP Vasseur wrote: > Dear WG, > > Do you support the adoption of > draft-lee-pce-global-concurrent-optimization-04.txt as a Working Group > document ? > > Thanks. > > JP. > > _______________________________________________ > Pce mailing list > Pce@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/pce > > -- Kohei Shiomoto NTT Network Service Systems Laboratories 3-9-11 Midori, Musashino, Tokyo 180-8585, Japan Phone +81 422 59 4402 Fax +81 422 59 3787 _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Wed Jun 06 21:10:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw6Vn-0004fj-Er; Wed, 06 Jun 2007 21:10:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw6Vl-0004fe-Nb for pce@ietf.org; Wed, 06 Jun 2007 21:10:01 -0400 Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hw6Vj-0008Cm-SG for pce@ietf.org; Wed, 06 Jun 2007 21:10:01 -0400 Received: from sfs2.rdh.ecl.ntt.co.jp (IDENT:mirapoint@sfs2.rdh.ecl.ntt.co.jp [129.60.39.117]) by tama5.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l5719m8m028926; Thu, 7 Jun 2007 10:09:48 +0900 (JST) Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp [129.60.39.114]) by sfs2.rdh.ecl.ntt.co.jp (MOS 3.8.3-GA) with ESMTP id ANN28726; Thu, 7 Jun 2007 10:09:48 +0900 (JST) Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 11D5F20AE2E; Thu, 7 Jun 2007 10:09:48 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100]) by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 8104320AE3A; Thu, 7 Jun 2007 10:09:47 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l5719l10013379; Thu, 7 Jun 2007 10:09:47 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l5719kNI025721; Thu, 7 Jun 2007 10:09:46 +0900 (JST) Received: from imf.m.ecl.ntt.co.jp (imf0.m.ecl.ntt.co.jp [129.60.5.144]) by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l5719kBU025717; Thu, 7 Jun 2007 10:09:46 +0900 (JST) Received: from Panasonic.lab.ntt.co.jp ([129.60.80.90]) by imf.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l5719geT008379; Thu, 7 Jun 2007 10:09:46 +0900 (JST) Message-Id: <6.0.0.20.2.20070607100717.077cb750@imf.m.ecl.ntt.co.jp> X-Sender: tt043@imf.m.ecl.ntt.co.jp X-Mailer: QUALCOMM Windows Eudora Version 6J-Jr3 Date: Thu, 07 Jun 2007 10:09:12 +0900 To: JP Vasseur , pce@ietf.org From: Tomonori TAKEDA Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txtas a WG document ? In-Reply-To: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 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 Yes. Tomonori At 21:28 07/06/05, JP Vasseur wrote: >Dear WG, > >Do you support the adoption of draft-lee-pce-global-concurrent- optimization-04.txt as a Working Group document ? > >Thanks. > >JP. > >_______________________________________________ >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 Wed Jun 06 21: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 1Hw6jA-0005v3-Ug; Wed, 06 Jun 2007 21:23:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw6j9-0005pl-F7 for pce@ietf.org; Wed, 06 Jun 2007 21:23:51 -0400 Received: from szxga04-in.huawei.com ([61.144.161.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hw6j7-0002d7-Nl for pce@ietf.org; Wed, 06 Jun 2007 21:23:51 -0400 Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JJ800K1GRUHFI@szxga04-in.huawei.com> for pce@ietf.org; Thu, 07 Jun 2007 09:23:05 +0800 (CST) Received: from M55527 ([10.111.12.154]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JJ800925RUG5C@szxga04-in.huawei.com> for pce@ietf.org; Thu, 07 Jun 2007 09:23:05 +0800 (CST) Date: Thu, 07 Jun 2007 09:23:23 +0800 From: Mach Chen Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? To: JP Vasseur Message-id: <002501c7a8a2$730a1f40$9a0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: pce@ietf.org 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 Yes, I support this draft to be WG document. Best regards, Mach ----- Original Message ----- From: "JP Vasseur" To: Sent: Tuesday, June 05, 2007 8:28 PM Subject: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? > Dear WG, > > Do you support the adoption of draft-lee-pce-global-concurrent- > optimization-04.txt as a Working Group document ? > > Thanks. > > JP. > > _______________________________________________ > 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 Wed Jun 06 21:40:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw6yt-0007dW-NQ; Wed, 06 Jun 2007 21:40:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw6yr-0007d8-VK for pce@ietf.org; Wed, 06 Jun 2007 21:40:06 -0400 Received: from tama55.ecl.ntt.co.jp ([129.60.39.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hw6yr-0004Vd-39 for pce@ietf.org; Wed, 06 Jun 2007 21:40:05 -0400 Received: from sfs2.rdh.ecl.ntt.co.jp (IDENT:mirapoint@sfs2.rdh.ecl.ntt.co.jp [129.60.39.117]) by tama55.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l571auNp003760; Thu, 7 Jun 2007 10:39:59 +0900 (JST) Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp [129.60.39.114]) by sfs2.rdh.ecl.ntt.co.jp (MOS 3.8.3-GA) with ESMTP id ANN38291; Thu, 7 Jun 2007 10:39:58 +0900 (JST) Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 9DB1C20AE39; Thu, 7 Jun 2007 10:39:58 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100]) by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 6F86920AE31; Thu, 7 Jun 2007 10:39:58 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l571dwhH000016; Thu, 7 Jun 2007 10:39:58 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l571dv8E014159; Thu, 7 Jun 2007 10:39:57 +0900 (JST) Received: from imb.m.ecl.ntt.co.jp (imb0.m.ecl.ntt.co.jp [129.60.5.140]) by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l571dvQh014155; Thu, 7 Jun 2007 10:39:57 +0900 (JST) Received: from YOUR-D26E4720EE.lab.ntt.co.jp ([129.60.80.208]) by imb.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l571dsqD001477; Thu, 7 Jun 2007 10:39:57 +0900 (JST) Message-Id: <5.0.2.5.2.20070607103444.01facec0@imb.m.ecl.ntt.co.jp> X-Sender: ii004@imb.m.ecl.ntt.co.jp X-Mailer: QUALCOMM Windows Eudora Version 5.0.2-J Date: Thu, 07 Jun 2007 10:35:38 +0900 To: pce@ietf.org, JP Vasseur From: "inoue.ichiro@lab.ntt.co.jp" Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txtas a WG document ? In-Reply-To: <002501c7a8a2$730a1f40$9a0c6f0a@china.huawei.com> References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 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, I do support it. Thanks. Ichiro From: "JP Vasseur" >To: >Sent: Tuesday, June 05, 2007 8:28 PM >Subject: [Pce] Adopting >draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? > > > > Dear WG, > > > > Do you support the adoption of draft-lee-pce-global-concurrent- > > optimization-04.txt as a Working Group document ? > > > > Thanks. > > > > JP. > > > > _______________________________________________ > > 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 _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Thu Jun 07 01:49:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwAs3-0003mF-C0; Thu, 07 Jun 2007 01:49:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwAs1-0003m4-Dz for pce@ietf.org; Thu, 07 Jun 2007 01:49:17 -0400 Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwAs0-0006iM-5E for pce@ietf.org; Thu, 07 Jun 2007 01:49:17 -0400 Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JJ9000HC463OY@usaga01-in.huawei.com> for pce@ietf.org; Wed, 06 Jun 2007 22:49:15 -0700 (PDT) Received: from huawei.com ([172.17.1.36]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JJ900HVI4616N@usaga01-in.huawei.com> for pce@ietf.org; Wed, 06 Jun 2007 22:49:15 -0700 (PDT) Received: from [172.24.1.3] (Forwarded-For: [221.191.104.173]) by szxmc04-in.huawei.com (mshttpd); Thu, 07 Jun 2007 13:49:12 +0800 Date: Thu, 07 Jun 2007 13:49:12 +0800 From: xuhuiying 19371 Subject: =?gb2312?B?u9i4tA==?=:[Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? To: JP Vasseur Message-id: <5ab13bb5ab1629.5ab16295ab13bb@huawei.com> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar 3 2004) Content-type: text/plain; charset=gb2312 Content-language: zh-CN Content-transfer-encoding: quoted-printable Content-disposition: inline X-Accept-Language: zh-CN Priority: normal X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: pce@ietf.org 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 Yes=2C I support this draft to a WG document=2E Thanks=2C = Huiying Xu ----- =D4=AD=D3=CA=BC=FE ----- =B7=A2=BC=FE=C8=CB=3A JP Vasseur =3Cjvasseur=40cisco=2Ecom=3E =C8=D5=C6=DA=3A =D0=C7=C6=DA=B6=FE=2C =C1=F9=D4=C2 5=C8=D5=2C 2007 =CF=C2= =CE=E78=3A28 =D6=F7=CC=E2=3A =5BPce=5D Adopting draft-lee-pce-global-concurrent-optimi= zation-04=2Etxt as a WG document =3F =3E Dear WG=2C =3E = =3E Do you support the adoption of draft-lee-pce-global-concurrent- = =3E optimization-04=2Etxt as a Working Group document =3F =3E = =3E Thanks=2E =3E = =3E JP=2E =3E = =3E =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F =3E Pce mailing list =3E Pce=40lists=2Eietf=2Eorg =3E https=3A//www1=2Eietf=2Eorg/mailman/listinfo/pce =3E _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Thu Jun 07 03:21: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 1HwCJa-0006PY-GD; Thu, 07 Jun 2007 03:21:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwCJZ-0006PQ-VN for pce@ietf.org; Thu, 07 Jun 2007 03:21:49 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwCJY-0007ju-KZ for pce@ietf.org; Thu, 07 Jun 2007 03:21:49 -0400 Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 07 Jun 2007 00:21:48 -0700 X-IronPort-AV: i="4.16,393,1175497200"; d="scan'208"; a="160280448:sNHT60107193" Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l577LmXb025457 for ; Thu, 7 Jun 2007 00:21:48 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l577LltV014825 for ; Thu, 7 Jun 2007 07:21:47 GMT Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Jun 2007 00:21:47 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txtas a WG document ? Date: Thu, 7 Jun 2007 00:21:55 -0700 Message-ID: <70BC84B185C3EE448EDB7AB8956D3B0E03AD579B@xmb-sjc-234.amer.cisco.com> In-Reply-To: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txtas a WG document ? Thread-Index: AcenbRbx4WhCFFcTSeKO+8ctgNFIugBZ2Mzg References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> From: "Dean Cheng \(dcheng\)" To: "Jean Philippe Vasseur \(jvasseur\)" , X-OriginalArrivalTime: 07 Jun 2007 07:21:47.0745 (UTC) FILETIME=[8263A510:01C7A8D4] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=583; t=1181200908; x=1182064908; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dcheng@cisco.com; z=From:=20=22Dean=20Cheng=20\(dcheng\)=22=20 |Subject:=20RE=3A=20[Pce]=20Adopting=20draft-lee-pce-global-concurrent-op timization-04.txtas=20a=20WG=20document=20? |Sender:=20; bh=7m4CobKe8RLAoyZjE3mHpnK/TUhc77GEZ/u/hX1Fcmk=; b=vMYqmJq6mjm/U7eavmfDZMjhvfoDeRdbe4JceRxnpNxcMOzYHwauQGEugfPHuX9254LAjTPd K0zY3rxcwx+JMOreNNx6InfkCyJX9peuE9GboxADu1F2afXdHpmTgZDRZY2Jtl0dVRRRMu7BEY BDFbfrGIcbRrVWjFLNU6Vv/pE=; Authentication-Results: sj-dkim-1; header.From=dcheng@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 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 yes.=20 > -----Original Message----- > From: Jean Philippe Vasseur (jvasseur)=20 > Sent: Tuesday, June 05, 2007 5:28 AM > To: pce@ietf.org > Subject: [Pce] Adopting=20 > draft-lee-pce-global-concurrent-optimization-04.txtas a WG document ? >=20 > Dear WG, >=20 > Do you support the adoption of=20 > draft-lee-pce-global-concurrent- optimization-04.txt as a=20 > Working Group document ? >=20 > Thanks. >=20 > JP. >=20 > _______________________________________________ > Pce mailing list > Pce@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/pce >=20 _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Fri Jun 08 22:39: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 1Hwqr6-0003ER-Ge; Fri, 08 Jun 2007 22:39:08 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwqr4-0003EB-Mg for pce@ietf.org; Fri, 08 Jun 2007 22:39:06 -0400 Received: from pro.abac.com ([66.226.64.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwqr3-00080b-9M for pce@ietf.org; Fri, 08 Jun 2007 22:39:06 -0400 Received: from [192.168.1.2] (adsl-75-36-145-116.dsl.pltn13.sbcglobal.net [75.36.145.116]) (authenticated bits=0) by pro.abac.com (8.13.8/8.13.8) with ESMTP id l592cwcn065145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 8 Jun 2007 19:39:02 -0700 (PDT) (envelope-from gregb@grotto-networking.com) Message-ID: <466A12C2.70103@grotto-networking.com> Date: Fri, 08 Jun 2007 19:38:58 -0700 From: Greg Bernstein User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: pce@ietf.org Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> In-Reply-To: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 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 Yes. Greg B. JP Vasseur wrote: > Dear WG, > > Do you support the adoption of > draft-lee-pce-global-concurrent-optimization-04.txt as a Working Group > document ? > > Thanks. > > JP. > > _______________________________________________ > Pce mailing list > Pce@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/pce > -- =================================================== Dr Greg Bernstein, Grotto Networking (510) 573-2237 _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Mon Jun 11 10:54:45 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HxlGf-0000E9-G8; Mon, 11 Jun 2007 10:53:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HxlGd-0000Af-L5 for pce@ietf.org; Mon, 11 Jun 2007 10:53:15 -0400 Received: from smtp.polymtl.ca ([132.207.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxlD2-0001Zc-Br for pce@ietf.org; Mon, 11 Jun 2007 10:49:33 -0400 Received: from localhost (imp-4-3.polymtl.ca [132.207.4.78]) by smtp.polymtl.ca (8.13.6/8.13.6) with ESMTP id l5BEnUbK003739; Mon, 11 Jun 2007 10:49:30 -0400 Received: from chaplin.larim.polymtl.ca (chaplin.larim.polymtl.ca [132.207.67.80]) by www.imp.polymtl.ca (IMP) with HTTP for ; Mon, 11 Jun 2007 10:49:29 -0400 Message-ID: <1181573369.466d60f9583ab@www.imp.polymtl.ca> Date: Mon, 11 Jun 2007 10:49:29 -0400 From: Meral Shirazipour To: JP Vasseur Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> In-Reply-To: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.3 X-Originating-IP: 132.207.67.80 X-Poly-FromMTA: (imp-4-3.polymtl.ca [132.207.4.78]) at Mon, 11 Jun 2007 14:49:30 +0000 X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: "pce@ietf.org" 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, I would support this draft based on its content, but I only see one problem: it does not consider or even refer to draft-ietf-pce-brpc-04.txt (or maybe I missed it?). I would rather see a single draft covering all possible optimization scenarios/solutions based on the PCE architecture. Having several IDs for optimization applications is ok as long as they refer to each other and maybe provide an section between the different methods. Cordially, Meral Selon JP Vasseur : > Dear WG, > > Do you support the adoption of draft-lee-pce-global-concurrent- > optimization-04.txt as a Working Group document ? > > Thanks. > > JP. > > _______________________________________________ > 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 Tue Jun 12 09:57:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy6rv-0003bR-4L; Tue, 12 Jun 2007 09:57:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy6ru-0003Uo-3R for pce@ietf.org; Tue, 12 Jun 2007 09:57:10 -0400 Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy6rs-0008Jj-LS for pce@ietf.org; Tue, 12 Jun 2007 09:57:10 -0400 Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 15:57:04 +0200 Received: from [10.193.75.118] ([10.193.75.118]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 15:57:03 +0200 Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txtas a WG document ? From: Thomas Morin To: JP Vasseur In-Reply-To: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> Content-Type: text/plain Organization: France Telecom R&D - Orange Date: Tue, 12 Jun 2007 15:57:04 +0200 Message-Id: <1181656624.10335.14.camel@wintermute> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Jun 2007 13:57:03.0782 (UTC) FILETIME=[8E507460:01C7ACF9] X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: pce@ietf.org 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 Support. -Thomas JP Vasseur : > Dear WG, > > Do you support the adoption of draft-lee-pce-global-concurrent- > optimization-04.txt as a Working Group document ? > > Thanks. > > JP. > > _______________________________________________ > 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 Tue Jun 12 16:16: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 1HyCnA-0004ac-0L; Tue, 12 Jun 2007 16:16:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCn8-0004Zx-5H for pce@ietf.org; Tue, 12 Jun 2007 16:16:38 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCn6-0001FF-SG for pce@ietf.org; Tue, 12 Jun 2007 16:16:38 -0400 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 12 Jun 2007 16:16:36 -0400 X-IronPort-AV: i="4.16,412,1175486400"; d="scan'208"; a="123422029:sNHT47737702" 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 l5CKGa9c010528; Tue, 12 Jun 2007 16:16:36 -0400 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 l5CKGaBk016118; Tue, 12 Jun 2007 20:16:36 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 16:16:20 -0400 Received: from [10.86.104.179] ([10.86.104.179]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 16:16:19 -0400 In-Reply-To: <1181573369.466d60f9583ab@www.imp.polymtl.ca> References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> <1181573369.466d60f9583ab@www.imp.polymtl.ca> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <18233BB2-3F21-4F59-98C3-A99124E3103A@cisco.com> Content-Transfer-Encoding: 7bit From: JP Vasseur Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? Date: Tue, 12 Jun 2007 16:15:56 -0400 To: Meral Shirazipour X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 12 Jun 2007 20:16:19.0955 (UTC) FILETIME=[8A0CE430:01C7AD2E] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1402; t=1181679396; x=1182543396; 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:=20Re=3A=20[Pce]=20Adopting=20draft-lee-pce-global-concurrent-op timization-04.txt=09as=20a=20WG=20document=20? |Sender:=20 |To:=20Meral=20Shirazipour=20; bh=Tsk0Nm9jpz5Qf8B5y8vvlJ+F9GanMKmez+a6A11zkns=; b=XlOYmMPAlDHOvQi+191L1zCV6G3qksraYX3iSLUYNKVUZP3t8rIaPvqqmsQqFs1Vin3bWgXE Nb90mY1442n5WBRZO0Qeeafd+9i2GZ/sKBxN0y6dYqOqeItpf9aCmn1z; 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: f4c2cf0bccc868e4cc88dace71fb3f44 Cc: "pce@ietf.org" 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 Meral, On Jun 11, 2007, at 10:49 AM, Meral Shirazipour wrote: > Hi, > I would support this draft based on its content, but I only see one > problem: it > does not consider or even refer to draft-ietf-pce-brpc-04.txt (or > maybe I > missed it?). > I would rather see a single draft covering all possible optimization > scenarios/solutions based on the PCE architecture. > BRPC is a multi-PCE path computation technique used to compute a shortest constrained inter-domain path wheres this ID specifies a (preferably) NMS based technique where a set of path computation requests are bundled and send to a PCE with the objective of "optimizing" the set of computed paths. > Having several IDs for optimization applications is ok as long as > they refer to > each other and maybe provide an section between the > different > methods. There is no real reason for referring to each other since there is no dependency. Thanks. JP. > > Cordially, > Meral > > > > Selon JP Vasseur : > >> Dear WG, >> >> Do you support the adoption of draft-lee-pce-global-concurrent- >> optimization-04.txt as a Working Group document ? >> >> Thanks. >> >> JP. >> >> _______________________________________________ >> 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 Tue Jun 12 17:55: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 1HyEKv-0004Zc-KL; Tue, 12 Jun 2007 17:55:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyEKu-0004ZX-R8 for pce@ietf.org; Tue, 12 Jun 2007 17:55:36 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyEKt-00064p-JQ for pce@ietf.org; Tue, 12 Jun 2007 17:55:36 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 12 Jun 2007 17:55:36 -0400 X-IronPort-AV: i="4.16,413,1175486400"; d="scan'208,217"; a="123430615:sNHT67222936" Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5CLtZF0001195 for ; Tue, 12 Jun 2007 17:55:35 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5CLtU63010272 for ; Tue, 12 Jun 2007 21:55:35 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 17:55:23 -0400 Received: from [10.86.104.179] ([10.86.104.179]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 17:55:23 -0400 Mime-Version: 1.0 (Apple Message framework v752.2) To: pce@ietf.org Message-Id: From: JP Vasseur Date: Tue, 12 Jun 2007 17:55:00 -0400 X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 12 Jun 2007 21:55:23.0214 (UTC) FILETIME=[60823EE0:01C7AD3C] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1234; t=1181685335; x=1182549335; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20 |Subject:=20draft-lee-pce-global-concurrent-optimization-04.txt=20adopted =20as=20a=20WG=20document |Sender:=20 |To:=20pce@ietf.org; bh=yP6MwslzuqqsV6vk0UQ1p5Bsh7KOvNexXx+NZqVAxQU=; b=r7sVmVlDfL7k/sKN11C1shdS7Sz0AyXYgYrhb9vz64d6Sql5sz2KQ0bWgOEdWJIDxkSPL2ZG KNAH4WLWy87mMxfDt6NH/wKkg1s5NC32YKEcHQ7+n+e3Xc7MXPTDfv07; Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); X-Spam-Score: 0.6 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: Subject: [Pce] draft-lee-pce-global-concurrent-optimization-04.txt adopted as a WG document 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="===============2033545696==" Errors-To: pce-bounces@lists.ietf.org --===============2033545696== Content-Type: multipart/alternative; boundary=Apple-Mail-22--632845791 --Apple-Mail-22--632845791 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hi, Considering the fair support of draft-lee-pce-global-concurrent- optimization-04.txt, the document is approved to become a PCE WG ID. Authors, please resubmit as draft-ietf-pce- global-concurrent-optimization-00.txt (with no content change). Thanks. JP. --Apple-Mail-22--632845791 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 Hi,

Considering the fair = support of=A0draft-lee-pce-global-concurrent-optimization-04.txt, the document = is approved
to become a PCE WG ID. Authors, please = resubmit = as=A0draft-ietf-pce-global-concurrent-optimization-00.txt
(with no content change).

Thanks.

JP.
= --Apple-Mail-22--632845791-- --===============2033545696== 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 --===============2033545696==-- From pce-bounces@lists.ietf.org Wed Jun 13 14:47:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyXsg-0005Ev-OG; Wed, 13 Jun 2007 14:47:46 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyXsd-0005E1-7i; Wed, 13 Jun 2007 14:47:43 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HyXsb-0000gk-D5; Wed, 13 Jun 2007 14:47:42 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 4F6DC175CD; Wed, 13 Jun 2007 18:47:11 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HyXs7-0003Mq-2s; Wed, 13 Jun 2007 14:47:11 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Wed, 13 Jun 2007 14:47:11 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Cc: pce@ietf.org Subject: [Pce] Last Call: draft-ietf-pce-disco-proto-isis (IS-IS protocol extensions for Path Computation Element (PCE) Discovery) to Proposed Standard X-BeenThere: pce@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: Path Computation Element List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: pce-bounces@lists.ietf.org The IESG has received a request from the Path Computation Element WG (pce) to consider the following document: - 'IS-IS protocol extensions for Path Computation Element (PCE) Discovery' as a Proposed Standard This last call is being repeated to clarify downrefs. This document has a normative reference to an informational RFC, RFC 3567. RFC 3567 is part of a group of informational RFCs that was published as informational instead of standards-track for historical reasons, and there is current work in progress to advance it to standards track. However, to avoid unnecessary delay for this document, the IESG proposes using a combination of the RFC 3967 rule (this Last Call) and the annotation described in section 4 of draft-klensin-norm-ref (currently in Last Call). The annotation will read: As of this writing, there is ongoing work to republish RFC 3567 on the IETF Standards Track. Please consult the RFC Index to see if this has occurred, and see the updated reference if so. This document has a normative reference to an informational RFC, RFC 3784. RFC 3784 is part of a group of informational RFCs that was published as informational instead of standards-track for historical reasons, and there is current work in progress to advance it to standards track. However, to avoid unnecessary delay for this document, the IESG proposes using a combination of the RFC 3967 rule (this Last Call) and the annotation described in section 4 of draft-klensin-norm-ref (currently in Last Call). The annotation will read: As of this writing, there is ongoing work to republish RFC 3784 on the IETF Standards Track. Please consult the RFC Index to see if this has occurred, and see the updated reference if so. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-06-27. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-pce-disco-proto-isis-05.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=15172&rfc_flag=0 _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Wed Jun 13 15:20:48 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyYOb-0000Z1-T5; Wed, 13 Jun 2007 15:20:45 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyYOa-0000Yt-R3 for pce@ietf.org; Wed, 13 Jun 2007 15:20:44 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HyYON-0004W4-JJ for pce@ietf.org; Wed, 13 Jun 2007 15:20:44 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 13 Jun 2007 15:20:31 -0400 X-IronPort-AV: i="4.16,417,1175486400"; d="scan'208,217"; a="62675359:sNHT103478178" Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5DJKVdD008603 for ; Wed, 13 Jun 2007 15:20:31 -0400 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 l5DJJ25r013512 for ; Wed, 13 Jun 2007 19:20:31 GMT Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 13 Jun 2007 15:20:16 -0400 Received: from [10.86.104.179] ([10.86.104.179]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 13 Jun 2007 15:20:15 -0400 Mime-Version: 1.0 (Apple Message framework v752.2) To: pce@ietf.org Message-Id: References: <200706131732.l5DHWtV2010669@nit.isi.edu> From: JP Vasseur Date: Wed, 13 Jun 2007 15:19:51 -0400 X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 13 Jun 2007 19:20:15.0374 (UTC) FILETIME=[DF0452E0:01C7ADEF] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=20024; t=1181762431; x=1182626431; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20 |Subject:=20Fwd=3A=20BCP0097=20RFC=204897=20on=20Handling=20Normative=20R eferences=20to=20Standards-Track=20Documents |Sender:=20 |To:=20pce@ietf.org; bh=Hz73TfowOfB5gX70Suodx9fQ0j9Tn6YYFJIRqhB+41E=; b=bFitDODVi9p4OjcTmn1htsNN+EwOcOvulk4apwMuAqLtIgf6yU2rMaL476FB42OoZ1oEqQnI hMPunB72HMtLkxkmFWewiMMc5xCsl5htP5UwwNVyBI3QJjZ3JQKhq03/; Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); X-Spam-Score: 0.2 (/) X-Scan-Signature: c119f9923e40f08a1d7f390ce651ea92 Cc: Subject: [Pce] Fwd: BCP0097 RFC 4897 on Handling Normative References to Standards-Track Documents 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="===============0467344069==" Errors-To: pce-bounces@lists.ietf.org --===============0467344069== Content-Type: multipart/alternative; boundary=Apple-Mail-50--555754655 --Apple-Mail-50--555754655 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Begin forwarded message: > From: rfc-editor@rfc-editor.org > Date: June 13, 2007 1:32:55 PM EDT > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: rfc-editor@rfc-editor.org > Subject: BCP0097 RFC 4897 on Handling Normative References to > Standards-Track Documents > > > A new Request for Comments is now available in online RFC libraries. > > BCP 97 > RFC 4897 > > Title: Handling Normative References to Standards-Track > Documents > Author: J. Klensin, S. Hartman > Status: Best Current Practice > Date: June 2007 > Mailbox: john-ietf@jck.com, > hartmans-ietf@mit.edu > Pages: 6 > Characters: 13023 > > > I-D Tag: draft-klensin-norm-ref-04.txt > > URL: http://www.rfc-editor.org/rfc/rfc4897.txt > > The Internet Engineering Task Force (IETF) and Request for Comments > (RFC) Editor have a long-standing rule that a document at a given > maturity level cannot be published until all of the documents that it > references as normative are at that maturity level or higher. This > rule has sometimes resulted in very long publication delays for > documents and some claims that it was a major obstruction to > advancing documents in maturity level. The IETF agreed on a way to > bypass this rule with RFC 3967. This document describes a simpler > procedure for downward references to Standards-Track and Best Current > Practice (BCP) documents, namely "note and move on". The procedure > in RFC 3967 still applies for downward references to other classes of > documents. In both cases, annotations should be added to such > References. This document specifies an Internet Best Current > Practices > for the Internet Community, and requests discussion and suggestions > for > improvements. > > This document specifies an Internet Best Current Practices for the > Internet Community, and requests discussion and suggestions for > improvements. Distribution of this memo is unlimited. > > This announcement is sent to the IETF list and the RFC-DIST list. > Requests to be added to or deleted from the IETF distribution list > should be sent to IETF-REQUEST@IETF.ORG. Requests to be > added to or deleted from the RFC-DIST distribution list should > be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. > > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body > > help: ways_to_get_rfcs. For example: > > To: rfc-info@RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. > Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > Submissions for Requests for Comments should be sent to > RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions > to RFC > Authors, for further information. > > > The RFC Editor Team > USC/Information Sciences Institute > > ... > > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce --Apple-Mail-50--555754655 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1

Begin = forwarded message:

Date: June 13, 2007 1:32:55 PM = EDT
Subject: BCP0097 RFC 4897 on Handling = Normative References to Standards-Track Documents


A new Request = for Comments is now available in online RFC libraries.

=A0 =A0 =A0 =A0 BCP 97 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 = RFC 4897

=A0 =A0 =A0 =A0 = Title:=A0 =A0 =A0 = Handling Normative References to Standards-Track=A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = Documents=A0
=A0 =A0 =A0 =A0 = Author: =A0 =A0 J. = Klensin, S. Hartman
=A0 =A0 =A0 =A0 Status: =A0 =A0 Best Current = Practice
=A0 =A0 =A0 =A0 Date: =A0 =A0 =A0 June 2007
=A0 =A0 =A0 =A0 = Mailbox:=A0 =A0 john-ietf@jck.com,=A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = hartmans-ietf@mit.edu
=A0 =A0 =A0 =A0 = Pages:=A0 =A0 =A0 = 6
=A0 =A0 =A0 =A0 Characters: = 13023


=A0 =A0 =A0 =A0 I-D Tag:=A0 =A0 = draft-klensin-norm-ref-04.txt

=A0 =A0 =A0 =A0 URL:=A0 =A0 =A0 =A0 http://www.rfc-editor.o= rg/rfc/rfc4897.txt
The Internet Engineering Task = Force (IETF) and Request for Comments
(RFC) = Editor have a long-standing rule that a document at a given
maturity level cannot be published until all of the = documents that it
references as normative are at = that maturity level or higher.=A0 = This
rule has sometimes resulted in = very long publication delays for
documents and = some claims that it was a major obstruction to
advancing documents in maturity level.=A0 The IETF agreed on a way = to
bypass this rule with RFC 3967.=A0 This document describes a = simpler
procedure for downward = references to Standards-Track and Best Current
Practice (BCP) documents, namely "note and move = on".=A0 The = procedure
in RFC 3967 still applies for = downward references to other classes of
=A0 In both = cases, annotations should be added to such
=A0 This = document specifies an Internet Best Current Practices=A0
for the = Internet Community, and requests discussion and suggestions = for
improvements.

This = document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and = suggestions for
improvements.=A0 Distribution of this memo is = unlimited.

This announcement is sent to the IETF list and the = RFC-DIST list.
Requests to be added to or = deleted from the IETF distribution list
should = be sent to IETF-REQUEST@IETF.ORG.=A0 Requests to be
added to or deleted from the RFC-DIST distribution = list should

Details on obtaining RFCs via FTP or EMAIL may be = obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with = the message body=A0

help: = ways_to_get_rfcs. For example:

=A0 =A0 =A0 =A0 To: rfc-info@RFC-EDITOR.ORG
<= DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">=A0 =A0 =A0 =A0 = Subject: getting rfcs

=A0 =A0 =A0 =A0 help: = ways_to_get_rfcs

Requests for special distribution should be = addressed to either the
author of the = RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.= =A0 Unless
specifically noted otherwise on the RFC itself, all = RFCs are for
unlimited = distribution.

Submissions for Requests for Comments should be sent = to
RFC-EDITOR@RFC-EDITOR.ORG.=A0 Please consult RFC 2223, = Instructions to RFC
Authors, for further = information.


The RFC = Editor Team
USC/Information Sciences = Institute

...



IETF-Announce mailing list
https://www1= .ietf.org/mailman/listinfo/ietf-announce =
= --Apple-Mail-50--555754655-- --===============0467344069== 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 --===============0467344069==-- From pce-bounces@lists.ietf.org Fri Jun 15 11:54:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzE7Z-0005eh-4a; Fri, 15 Jun 2007 11:53:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzE7X-0005ec-UJ for pce@ietf.org; Fri, 15 Jun 2007 11:53:55 -0400 Received: from smtp.polymtl.ca ([132.207.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzE7X-0000WE-Ks for pce@ietf.org; Fri, 15 Jun 2007 11:53:55 -0400 Received: from localhost (imp-4-2.polymtl.ca [132.207.4.77]) by smtp.polymtl.ca (8.13.6/8.13.6) with ESMTP id l5FFrrU7004503; Fri, 15 Jun 2007 11:53:53 -0400 Received: from lmcprb.ericsson.ca (lmcprb.ericsson.ca [192.75.88.232]) by www.imp.polymtl.ca (IMP) with HTTP for ; Fri, 15 Jun 2007 11:53:55 -0400 Message-ID: <1181922835.4672b613b90d9@www.imp.polymtl.ca> Date: Fri, 15 Jun 2007 11:53:55 -0400 From: Meral Shirazipour To: JP Vasseur Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> <1181573369.466d60f9583ab@www.imp.polymtl.ca> <18233BB2-3F21-4F59-98C3-A99124E3103A@cisco.com> In-Reply-To: <18233BB2-3F21-4F59-98C3-A99124E3103A@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.3 X-Originating-IP: 192.75.88.232 X-Poly-FromMTA: (imp-4-2.polymtl.ca [132.207.4.77]) at Fri, 15 Jun 2007 15:54:10 +0000 X-Spam-Score: 0.0 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Cc: "pce@ietf.org" 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, Thank you for the answer. But I still think any optimization application draft should refer to the others, even if it is only one sentence to say that there are no dependencies. Also, since each optimization application draft will probably propose similar extensions to PCEP, it would be better, at least from an implementation point of view, to generalize these extensions instead of making them application specific. Cordially, Meral Selon JP Vasseur : > Hi Meral, > > On Jun 11, 2007, at 10:49 AM, Meral Shirazipour wrote: > > > Hi, > > I would support this draft based on its content, but I only see one > > problem: it > > does not consider or even refer to draft-ietf-pce-brpc-04.txt (or > > maybe I > > missed it?). > > I would rather see a single draft covering all possible optimization > > scenarios/solutions based on the PCE architecture. > > > > BRPC is a multi-PCE path computation technique used to compute a > shortest constrained > inter-domain path wheres this ID specifies a (preferably) NMS based > technique where a > set of path computation requests are bundled and send to a PCE with > the objective of > "optimizing" the set of computed paths. > > > Having several IDs for optimization applications is ok as long as > > they refer to > > each other and maybe provide an section between the > > different > > methods. > > There is no real reason for referring to each other since there is no > dependency. > > Thanks. > > JP. > > > > > Cordially, > > Meral > > > > > > > > Selon JP Vasseur : > > > >> Dear WG, > >> > >> Do you support the adoption of draft-lee-pce-global-concurrent- > >> optimization-04.txt as a Working Group document ? > >> > >> Thanks. > >> > >> JP. > >> > >> _______________________________________________ > >> 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 Jun 16 06:34:16 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzVbh-0000TQ-CS; Sat, 16 Jun 2007 06:34:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzVbg-0000TH-5o for pce@ietf.org; Sat, 16 Jun 2007 06:34:12 -0400 Received: from mta3.iomartmail.com ([62.128.193.153]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzVbf-0002Ri-OH for pce@ietf.org; Sat, 16 Jun 2007 06:34:12 -0400 Received: from mta3.iomartmail.com (localhost.localdomain [127.0.0.1]) by mta3.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id l5GAY9g1022431; Sat, 16 Jun 2007 11:34:09 +0100 Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by mta3.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id l5GAY7Re022375; Sat, 16 Jun 2007 11:34:08 +0100 Message-ID: <04c601c7b001$dd1909d0$5102010a@your029b8cecfe> From: "Adrian Farrel" To: "Meral Shirazipour" , "JP Vasseur" References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com><1181573369.466d60f9583ab@www.imp.polymtl.ca><18233BB2-3F21-4F59-98C3-A99124E3103A@cisco.com> <1181922835.4672b613b90d9@www.imp.polymtl.ca> Subject: Re: [Pce] Adoptingdraft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? Date: Sat, 16 Jun 2007 11:34:02 +0100 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.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8 Cc: pce@ietf.org 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 Meral, I'm not sure that you are applying the term "optimization" consistently. BRPC optimizes the placement of a single end-to-end LSP that crosses multiple domains. GCO optimizes a "network", that is a set of LSPs within a single domain. But, anyway, if you think some form of cross-reference would be valuable, can you please suggest some text to the GCO authors for inclusion in their I-D. Thanks, Adrian ----- Original Message ----- From: "Meral Shirazipour" To: "JP Vasseur" Cc: Sent: Friday, June 15, 2007 4:53 PM Subject: Re: [Pce] Adoptingdraft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? > Hi, > Thank you for the answer. But I still think any optimization application > draft > should refer to the others, even if it is only one sentence to say that > there > are no dependencies. Also, since each optimization application draft will > probably propose similar extensions to PCEP, it would be better, at least > from > an implementation point of view, to generalize these extensions instead of > making them application specific. > > Cordially, > Meral > > > > > > > Selon JP Vasseur : > >> Hi Meral, >> >> On Jun 11, 2007, at 10:49 AM, Meral Shirazipour wrote: >> >> > Hi, >> > I would support this draft based on its content, but I only see one >> > problem: it >> > does not consider or even refer to draft-ietf-pce-brpc-04.txt (or >> > maybe I >> > missed it?). >> > I would rather see a single draft covering all possible optimization >> > scenarios/solutions based on the PCE architecture. >> > >> >> BRPC is a multi-PCE path computation technique used to compute a >> shortest constrained >> inter-domain path wheres this ID specifies a (preferably) NMS based >> technique where a >> set of path computation requests are bundled and send to a PCE with >> the objective of >> "optimizing" the set of computed paths. >> >> > Having several IDs for optimization applications is ok as long as >> > they refer to >> > each other and maybe provide an section between the >> > different >> > methods. >> >> There is no real reason for referring to each other since there is no >> dependency. >> >> Thanks. >> >> JP. >> >> > >> > Cordially, >> > Meral >> > >> > >> > >> > Selon JP Vasseur : >> > >> >> Dear WG, >> >> >> >> Do you support the adoption of draft-lee-pce-global-concurrent- >> >> optimization-04.txt as a Working Group document ? >> >> >> >> Thanks. >> >> >> >> JP. >> >> >> >> _______________________________________________ >> >> 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 > _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Sat Jun 16 06:44: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 1HzVm1-0004Wo-Cw; Sat, 16 Jun 2007 06:44:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzVm0-0004Wj-J9 for pce@ietf.org; Sat, 16 Jun 2007 06:44:52 -0400 Received: from mta6.iomartmail.com ([62.128.193.156]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzVlz-0005xX-6l for pce@ietf.org; Sat, 16 Jun 2007 06:44:52 -0400 Received: from mta6.iomartmail.com (localhost.localdomain [127.0.0.1]) by mta6.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id l5GAiola005850 for ; Sat, 16 Jun 2007 11:44:50 +0100 Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by mta6.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id l5GAinlO005821 for ; Sat, 16 Jun 2007 11:44:50 +0100 Message-ID: <04d501c7b003$5b6318c0$5102010a@your029b8cecfe> From: "Adrian Farrel" To: Date: Sat, 16 Jun 2007 11:44:39 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: Subject: [Pce] Fw: 69th IETF - DRAFT Meeting Agenda 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 The draft agenda for Chicago shows PCE meeting on Monday from 15.20 to 17.20 > The DRAFT agenda for the 69th IETF Meeting can be found at: > http://www.ietf.org/meetings/69-IETF.html > > Please note that the agenda is in draft form and is subject to change > before the final agenda is published on Monday, July 2nd. Please let JP and me know if you would like to bring something to the show-and-tell, the nature table, or just to be on the agenda. Thanks, Adrian _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Mon Jun 18 10:07: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 1I0HtL-0002jp-Vx; Mon, 18 Jun 2007 10:07:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0HtK-0002jk-O8 for pce@ietf.org; Mon, 18 Jun 2007 10:07:38 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0HtJ-0000eT-DF for pce@ietf.org; Mon, 18 Jun 2007 10:07:38 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 18 Jun 2007 10:07:37 -0400 X-IronPort-AV: i="4.16,435,1175486400"; d="scan'208"; a="123898174:sNHT138984358" Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5IE7btU020588; Mon, 18 Jun 2007 10:07:37 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5IE7961005718; Mon, 18 Jun 2007 14:07:37 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Jun 2007 10:07:21 -0400 Received: from [10.86.104.180] ([10.86.104.180]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Jun 2007 10:07:20 -0400 In-Reply-To: <1181922835.4672b613b90d9@www.imp.polymtl.ca> References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> <1181573369.466d60f9583ab@www.imp.polymtl.ca> <18233BB2-3F21-4F59-98C3-A99124E3103A@cisco.com> <1181922835.4672b613b90d9@www.imp.polymtl.ca> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: JP Vasseur Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ? Date: Mon, 18 Jun 2007 10:06:58 -0400 To: Meral Shirazipour X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 18 Jun 2007 14:07:20.0777 (UTC) FILETIME=[FC8CEB90:01C7B1B1] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2225; t=1182175657; x=1183039657; c=relaxed/simple; s=rtpdkim1001; 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]=20Adopting=20draft-lee-pce-global-concurrent-op timization-04.txt=09as=20a=20WG=20document=20? |Sender:=20 |To:=20Meral=20Shirazipour=20; bh=XT/l+lcoBMq6Zd5i1axXkbPPx0sdR3z9HKZe/YLK1SQ=; b=IT/0EjME3wixeFQejDPWOhnpJ1tMzXMDYhXwbdwzR4+8wMY/u0tA0lH3QBLZxp+W7fmIQgMa CbB0qnPU02O6sY0ZqEmSPxlBRjUkTkv6dbY5NpLAskgNs69M8hbzBroJ; Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Cc: "pce@ietf.org" 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 Meral, On Jun 15, 2007, at 11:53 AM, Meral Shirazipour wrote: > Hi, > Thank you for the answer. But I still think any optimization > application draft > should refer to the others, even if it is only one sentence to say > that there > are no dependencies. Please suggest to the authors. > Also, since each optimization application draft will > probably propose similar extensions to PCEP, it would be better, at > least from > an implementation point of view, to generalize these extensions > instead of > making them application specific. > "generalize" ? Thanks. JP. > Cordially, > Meral > > > > > > > Selon JP Vasseur : > >> Hi Meral, >> >> On Jun 11, 2007, at 10:49 AM, Meral Shirazipour wrote: >> >>> Hi, >>> I would support this draft based on its content, but I only see one >>> problem: it >>> does not consider or even refer to draft-ietf-pce-brpc-04.txt (or >>> maybe I >>> missed it?). >>> I would rather see a single draft covering all possible optimization >>> scenarios/solutions based on the PCE architecture. >>> >> >> BRPC is a multi-PCE path computation technique used to compute a >> shortest constrained >> inter-domain path wheres this ID specifies a (preferably) NMS based >> technique where a >> set of path computation requests are bundled and send to a PCE with >> the objective of >> "optimizing" the set of computed paths. >> >>> Having several IDs for optimization applications is ok as long as >>> they refer to >>> each other and maybe provide an section between the >>> different >>> methods. >> >> There is no real reason for referring to each other since there is no >> dependency. >> >> Thanks. >> >> JP. >> >>> >>> Cordially, >>> Meral >>> >>> >>> >>> Selon JP Vasseur : >>> >>>> Dear WG, >>>> >>>> Do you support the adoption of draft-lee-pce-global-concurrent- >>>> optimization-04.txt as a Working Group document ? >>>> >>>> Thanks. >>>> >>>> JP. >>>> >>>> _______________________________________________ >>>> 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 Thu Jun 21 15:50:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1SfV-0003q1-Tx; Thu, 21 Jun 2007 15:50:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1SfL-0003ca-0R; Thu, 21 Jun 2007 15:50:03 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1SfK-0001a9-Hs; Thu, 21 Jun 2007 15:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 821FA3292D; Thu, 21 Jun 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I1SfK-0000t7-Cs; Thu, 21 Jun 2007 15:50: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, 21 Jun 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: pce@ietf.org Subject: [Pce] I-D ACTION:draft-ietf-pce-brpc-05.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 : A Backward Recursive PCE-based Computation (BRPC) procedure to compute shortest inter-domain Traffic Engineering Label Switched Paths Author(s) : J. Vasseur, et al. Filename : draft-ietf-pce-brpc-05.txt Pages : 18 Date : 2007-3-2 The ability to compute shortest constrained Traffic Engineering (TE) Label Switched Paths (LSPs) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks across multiple domains (where a domain is referred to as a collection of network elements within a common sphere of address management or path computational responsibility such as IGP areas and Autonomous Systems) has been identified as a key requirement . This document specifies a procedure relying on the use of multiple Path Computation Elements (PCEs) in order to compute such inter-domain shortest constrained paths along a determined sequence of domains, using a backward recursive path computation technique while preserving confidentiality across domains, which is sometimes required when domains are managed by different Service Providers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-brpc-05.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-brpc-05.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-brpc-05.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-6-21120935.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-brpc-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-brpc-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-6-21120935.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 Jun 21 15:59: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 1I1SoW-0007jC-2D; Thu, 21 Jun 2007 15:59:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1SoV-0007ip-84 for pce@ietf.org; Thu, 21 Jun 2007 15:59:31 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1SoO-000894-Sn for pce@ietf.org; Thu, 21 Jun 2007 15:59:31 -0400 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 21 Jun 2007 15:59:24 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CACd1ekZAZnmf/2dsb2JhbACCYQ X-IronPort-AV: i="4.16,448,1175486400"; d="scan'208,217"; a="63387100:sNHT65434380" 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 l5LJxOIG012805 for ; Thu, 21 Jun 2007 15:59:24 -0400 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 l5LJxIM7011265 for ; Thu, 21 Jun 2007 19:59:24 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Jun 2007 15:59:19 -0400 Received: from [10.86.104.181] ([10.86.104.181]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Jun 2007 15:59:18 -0400 Mime-Version: 1.0 (Apple Message framework v752.2) To: pce@ietf.org Message-Id: References: From: JP Vasseur Subject: Fwd: [Pce] I-D ACTION:draft-ietf-pce-brpc-05.txt Date: Thu, 21 Jun 2007 15:58:55 -0400 X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 21 Jun 2007 19:59:18.0948 (UTC) FILETIME=[A7335640:01C7B43E] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=20336; t=1182455964; x=1183319964; 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:=20Fwd=3A=20[Pce]=20I-D=20ACTION=3Adraft-ietf-pce-brpc-05.txt=20 |Sender:=20 |To:=20pce@ietf.org; bh=wQOMW0+jjFJa+mU3T/WasX1aQGuQQM4wbndBtX+K8AM=; b=ZFykdrCNnXhRMrw9jfyaC9JcaiORlxPxDfg/YIvr/82xOvnO3P7cCeN2PiNgQwBhNrGudD7a 1L2grNC/m7srn0m0OduAjQK1FDiI2mCAa2uIWU4FaDOUPC5B61wnh/GM; Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); X-Spam-Score: 0.2 (/) X-Scan-Signature: a630332fa112280ecc4c4186b5c9ea83 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="===============1620075290==" Errors-To: pce-bounces@lists.ietf.org --===============1620075290== Content-Type: multipart/alternative; boundary=Apple-Mail-71-137788872 --Apple-Mail-71-137788872 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed For information, just editorial changes (typos). No change in term of content. This ID has been very stable for a while and will likely be Last Called right after PCEP. Thanks. JP. Begin forwarded message: > From: Internet-Drafts@ietf.org > Date: June 21, 2007 3:50:02 PM EDT > To: i-d-announce@ietf.org > Cc: pce@ietf.org > Subject: [Pce] I-D ACTION:draft-ietf-pce-brpc-05.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Path Computation Element Working > Group of the IETF. > > Title : A Backward Recursive PCE-based Computation (BRPC) > procedure to compute shortest inter-domain Traffic Engineering > Label Switched Paths > Author(s) : J. Vasseur, et al. > Filename : draft-ietf-pce-brpc-05.txt > Pages : 18 > Date : 2007-3-2 > > The ability to compute shortest constrained Traffic Engineering (TE) > Label Switched Paths (LSPs) in Multiprotocol Label Switching (MPLS) > and Generalized MPLS (GMPLS) networks across multiple domains > (where > a domain is referred to as a collection of network elements > within a > common sphere of address management or path computational > responsibility such as IGP areas and Autonomous Systems) has been > identified as a key requirement . This document specifies a > procedure relying on the use of multiple Path Computation Elements > (PCEs) in order to compute such inter-domain shortest constrained > paths along a determined sequence of domains, using a backward > recursive path computation technique while preserving > confidentiality > across domains, which is sometimes required when domains are > managed > by different Service Providers. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-pce-brpc-05.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-brpc-05.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-brpc-05.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-Type: text/plain > Content-ID: <2007-6-21120935.I-D@ietf.org> > > _______________________________________________ > Pce mailing list > Pce@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/pce --Apple-Mail-71-137788872 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 For information, just editorial = changes (typos). No change in term of content.
This ID has been very = stable for a while and will likely be Last Called right after = PCEP.

Thanks.

JP.

Begin = forwarded message:

Date: June 21, 2007 3:50:02 PM = EDT
To: i-d-announce@ietf.org
Subject: = [Pce] I-D ACTION:draft-ietf-pce-brpc-05.txt=A0

A New = Internet-Draft is available from the on-line Internet-Drafts=A0
This draft is a work item of the = Path Computation Element Working Group of the IETF.

= Title = = : A Backward Recursive PCE-based Computation (BRPC) procedure to = compute shortest inter-domain Traffic Engineering Label Switched = Paths
Author(s) : J. = Vasseur, et al.
Filename : = draft-ietf-pce-brpc-05.txt
= Pages = = : 18
Date : 2007-3-2


The ability = to compute shortest constrained Traffic Engineering (TE)
=A0=A0 = Label Switched Paths (LSPs) in Multiprotocol Label Switching = (MPLS)
=A0=A0 and Generalized MPLS = (GMPLS) networks across multiple domains (where
=A0=A0 = a domain is referred to as a collection of network elements = within a
=A0=A0 common sphere of address = management or path computational
=A0=A0 responsibility such as IGP = areas and Autonomous Systems) has been
=A0=A0 identified as a key = requirement .=A0 This = document specifies a
=A0=A0 procedure relying on the = use of multiple Path Computation Elements
=A0=A0 (PCEs) in order to compute = such inter-domain shortest constrained
=A0=A0 paths along a determined = sequence of domains, using a backward
=A0=A0 recursive path computation = technique while preserving confidentiality
=A0=A0 across domains, which is = sometimes required when domains are managed
=A0=A0 by different Service = Providers.

A URL for this Internet-Draft is:

To = remove yourself from the I-D Announcement list, send a message to=A0
i-d-announce-request@ietf.or= g with the word unsubscribe in the body of=A0
the = message.=A0
to = change your subscription settings.

Internet-Drafts are also = available by anonymous FTP. Login with the=A0
username = "anonymous" and a password of your e-mail address. After=A0
logging = in, type "cd internet-drafts" and then=A0
"get = draft-ietf-pce-brpc-05.txt".

A list of Internet-Drafts = directories can be found in
Internet-Drafts can also be = obtained by e-mail.
Send a message to:
In the body type:
"FILE = /internet-drafts/draft-ietf-pce-brpc-05.txt".


NOTE: The mail = server at ietf.org can return the document in
MIME-encoded form by using the = "mpack" utility.=A0 To use = this
feature, insert the command = "ENCODING mime" before the "FILE"
= command.=A0 To = decode the response(s), you will need "munpack" or
a MIME-compliant mail = reader.=A0 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
Content-Type: = text/plain

=

= --Apple-Mail-71-137788872-- --===============1620075290== 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 --===============1620075290==-- From pce-bounces@lists.ietf.org Mon Jun 25 15:51: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 1I2ub0-0001bv-3B; Mon, 25 Jun 2007 15:51:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2uaT-0000c7-LY; Mon, 25 Jun 2007 15:51:01 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2uZW-0003vF-DE; Mon, 25 Jun 2007 15:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 5ED793289E; Mon, 25 Jun 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I2uZW-0000gF-6C; Mon, 25 Jun 2007 15:50: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: Mon, 25 Jun 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 Cc: pce@ietf.org Subject: [Pce] I-D ACTION:draft-ietf-pce-global-concurrent-optimization-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 --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-00.txt Pages : 31 Date : 2007-6-25 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-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-ietf-pce-global-concurrent-optimization-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-ietf-pce-global-concurrent-optimization-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-6-25131723.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-global-concurrent-optimization-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-global-concurrent-optimization-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-6-25131723.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 Jun 26 19:04: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 1I3K51-0006A3-NV; Tue, 26 Jun 2007 19:04:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3K4x-000647-Ly; Tue, 26 Jun 2007 19:04:11 -0400 Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3K4T-00080L-Ob; Tue, 26 Jun 2007 19:04:11 -0400 Received: by bosco.isi.edu (Postfix, from userid 70) id BC05ED8AAE; Tue, 26 Jun 2007 16:03:36 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20070626230336.BC05ED8AAE@bosco.isi.edu> Date: Tue, 26 Jun 2007 16:03:36 -0700 (PDT) X-Spam-Score: -14.8 (--------------) X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985 Cc: pce@ietf.org, rfc-editor@rfc-editor.org Subject: [Pce] RFC 4927 on Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering 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 A new Request for Comments is now available in online RFC libraries. RFC 4927 Title: Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering Author: J.-L. Le Roux, Ed. Status: Informational Date: June 2007 Mailbox: jeanlouis.leroux@orange-ftgroup.com Pages: 12 Characters: 25016 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pce-pcecp-interarea-reqs-05.txt URL: http://www.rfc-editor.org/rfc/rfc4927.txt For scalability purposes, a network may comprise multiple Interior Gateway Protocol (IGP) areas. An inter-area Traffic Engineered Label Switched Path (TE-LSP) is an LSP that transits through at least two IGP areas. In a multi-area network, topology visibility remains local to a given area, and a head-end Label Switching Router (LSR) cannot compute an inter-area shortest constrained path. One key application of the Path Computation Element (PCE)-based architecture is the computation of inter-area TE-LSP paths. The PCE Communication Protocol (PCECP) is used to communicate computation requests from Path Computation Clients (PCCs) to PCEs, and to return computed paths in responses. This document lists a detailed set of PCECP-specific requirements for support of inter-area TE-LSP path computation. It complements the generic requirements for a PCE Communication Protocol. This memo provides information for the Internet community. This document is a product of the Path Computation Element Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Wed Jun 27 13:40: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 1I3bV7-0003Fc-1Z; Wed, 27 Jun 2007 13:40:21 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3bV5-0003FV-I1 for pce@ietf.org; Wed, 27 Jun 2007 13:40:19 -0400 Received: from pro.abac.com ([66.226.64.2]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3bV5-0007hk-88 for pce@ietf.org; Wed, 27 Jun 2007 13:40:19 -0400 Received: from [192.168.0.131] (c-71-202-41-42.hsd1.ca.comcast.net [71.202.41.42]) (authenticated bits=0) by pro.abac.com (8.13.8/8.13.8) with ESMTP id l5RHdVuQ083636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jun 2007 10:39:38 -0700 (PDT) (envelope-from gregb@grotto-networking.com) Message-ID: <4682A0D1.4050904@grotto-networking.com> Date: Wed, 27 Jun 2007 10:39:29 -0700 From: Greg Bernstein User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: ccamp , pce@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: Young Lee Subject: [Pce] New draft on wavelength switched optical networks 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 CCAMPer's and PCEr's, we have just published a new draft on the "Applicability of GMPLS and PCE to Wavelength Switched Optical Networks" http://www.ietf.org/internet-drafts/draft-bernstein-ccamp-wavelength-switched-00.txt . This draft looks at optical networks that include tunable lasers and ROADM (reconfigurable optical add/drop multiplexers) with no or limited wavelength conversion capability (these components are defined in the draft). These limitations lead to the RWA (routing and wavelength assignment) problem which is a bit more demanding in terms of input information and computation than other constrained path computation problems. In the draft we look at the implications for GMPLS signaling, GMPLS routing, and PCE protocols and suggest some potential extensions to better accommodate this application. We'd appreciate feedback/collaboration on (a) overall interest in this application, (b) requirements discussions, and (c) solution/extension discussions. Cheers Greg B. -- =================================================== Dr Greg Bernstein, Grotto Networking (510) 573-2237 _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Wed Jun 27 21:11:57 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3iY9-0003vT-G2; Wed, 27 Jun 2007 21:11:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3iY8-0003vN-Nw for pce@ietf.org; Wed, 27 Jun 2007 21:11:56 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3iY4-00047q-5y for pce@ietf.org; Wed, 27 Jun 2007 21:11:56 -0400 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 27 Jun 2007 21:11:52 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAAungkZAZnmf/2dsb2JhbAA X-IronPort-AV: i="4.16,468,1175486400"; d="scan'208"; a="63857468:sNHT24892284" 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 l5S1BpHK003405; Wed, 27 Jun 2007 21:11:51 -0400 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 l5S1BlZF018506; Thu, 28 Jun 2007 01:11:51 GMT Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 27 Jun 2007 21:11:47 -0400 Received: from kkoushikwxp ([64.101.185.227]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 27 Jun 2007 21:11:47 -0400 Message-ID: <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> From: "A S Kiran Koushik" To: References: <4682A0D1.4050904@grotto-networking.com> Date: Wed, 27 Jun 2007 20:11:46 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response 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.3138 X-OriginalArrivalTime: 28 Jun 2007 01:11:47.0181 (UTC) FILETIME=[4C7F29D0:01C7B921] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=522; t=1182993111; x=1183857111; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kkoushik@cisco.com; z=From:=20=22A=20S=20Kiran=20Koushik=22=20 |Subject:=20draft-kkoushik-pce-pcep-mib-00.txt=20(PCE-PCEP-DRAFT-MIB) |Sender:=20 |To:=20; bh=PDphIqUSHf43AuKbl8AKMzdRhpEu0LXsxFSaKgKcpio=; b=Pp7XtfILt+UjllW6Q3nY5YS9p8BgawU31nj98XfLl1bUnTgAAwrq1YSSYCIcxd5qQ/LC/zrV LJiPXyjBzc4g3QdYWuEsM9LJ37/of9C5DwzRzq8s1KS2CgRa7xHnqYmj; Authentication-Results: rtp-dkim-2; header.From=kkoushik@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: jpv@cisco.com Subject: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB) 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 pce-team, We are working on updating the PCE-PCEP-DRAFT-MIB (PCE communication protocol MIB) with some editorial changes. http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt Can some of you kindly review the existing draft and let us know of any comments/suggestions. That way we can fix them by the deadline. Also we are planning to request this to be a working group document. If there are any objections to this, please let us know and we will work on fixing them. Thanks, Kiran and Emile. _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce From pce-bounces@lists.ietf.org Thu Jun 28 10:12:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3ujW-0005Y2-GM; Thu, 28 Jun 2007 10:12:30 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3ujU-0005Xg-Ne for pce@ietf.org; Thu, 28 Jun 2007 10:12:29 -0400 Received: from smtp.polymtl.ca ([132.207.4.11]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3ujU-00019J-Fw for pce@ietf.org; Thu, 28 Jun 2007 10:12:28 -0400 Received: from localhost (imp-4-2.polymtl.ca [132.207.4.77]) by smtp.polymtl.ca (8.13.6/8.13.6) with ESMTP id l5SEBr2r011596; Thu, 28 Jun 2007 10:11:54 -0400 Received: from chaplin.larim.polymtl.ca (chaplin.larim.polymtl.ca [132.207.67.80]) by www.imp.polymtl.ca (IMP) with HTTP for ; Thu, 28 Jun 2007 10:11:53 -0400 Message-ID: <1183039913.4683c1a9722c8@www.imp.polymtl.ca> Date: Thu, 28 Jun 2007 10:11:53 -0400 From: Meral Shirazipour To: A S Kiran Koushik Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB) References: <4682A0D1.4050904@grotto-networking.com> <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> In-Reply-To: <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.3 X-Originating-IP: 132.207.67.80 X-Poly-FromMTA: (imp-4-2.polymtl.ca [132.207.4.77]) at Thu, 28 Jun 2007 14:11:53 +0000 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Cc: "pce@ietf.org" , "jpv@cisco.com" 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, I have a question regarding page 3, section 4: "The PCEP MIB will contain the following information: a. PCEP client configuration and status." Does the "status" here also represent the previous/ongoing path computation requests? I am referring to Section 6.8. Stateful versus Stateless PCEs in RFC4655; would the information related to a stateful PCE be stored in the described MIB ? Best regards, Meral Selon A S Kiran Koushik : > Hi pce-team, > We are working on updating the PCE-PCEP-DRAFT-MIB > (PCE communication protocol MIB) with some editorial changes. > http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt > > Can some of you kindly review the existing draft and let us know of any > comments/suggestions. That way we can fix them by the deadline. > > Also we are planning to request this to be a working group document. > If there are any objections to this, please let us know and we will work > on fixing them. > > Thanks, > Kiran and Emile. > > _______________________________________________ > 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 Thu Jun 28 13:38: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 1I3xwT-0000Sr-6T; Thu, 28 Jun 2007 13:38:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3xwR-0000S2-Nq for pce@ietf.org; Thu, 28 Jun 2007 13:38:03 -0400 Received: from wa-out-1112.google.com ([209.85.146.182]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3xvb-0002q6-SL for pce@ietf.org; Thu, 28 Jun 2007 13:38:03 -0400 Received: by wa-out-1112.google.com with SMTP id k17so957103waf for ; Thu, 28 Jun 2007 10:37:11 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:content-type; b=hOgcWOftBVNuYBpjW+8PnTtqMj+/h/FjfEjf0dGcK4Htv5PmecXrNbTZfURj05G5NtQJiKB7YB0FxuZ+hUTI51aPvJ118rR95/ZNWKhnWxhbYS2A87j4H5ZStApAxu+fdOXy6kKb5mOXDH4WcNIwZmxL4aT8iosZ343jlfq6mi8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:content-type; b=UrwnkN1W13gld53uXSSob8M5hLPiCwl/z1k515ScT122RlJuDL7a6Wmh8PRX0HNbQpd5ldOiSzvT3bYO+GNruEdD3VMu9LLCgnTiMysPCBm9BqLZGNZ7KLWx14RtEaBTcOQ91NtORP75wOb952w8qwSJFUrZXVJ4vrMg6sUlO5E= Received: by 10.115.93.16 with SMTP id v16mr1727340wal.1183052231055; Thu, 28 Jun 2007 10:37:11 -0700 (PDT) Received: from ?192.168.1.2? ( [122.167.202.253]) by mx.google.com with ESMTP id n20sm19603465pof.2007.06.28.10.37.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 Jun 2007 10:37:09 -0700 (PDT) Message-ID: <4683F19F.5010708@gmail.com> Date: Thu, 28 Jun 2007 23:06:31 +0530 From: santanu User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: A S Kiran Koushik Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB) References: <4682A0D1.4050904@grotto-networking.com> <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> In-Reply-To: <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> X-Spam-Score: 0.1 (/) X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba Cc: pce@ietf.org, jpv@cisco.com 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="===============2054036217==" Errors-To: pce-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============2054036217== Content-Type: multipart/alternative; boundary="------------060203020608050908070708" This is a multi-part message in MIME format. --------------060203020608050908070708 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Dear Kiran and Emile, I have some more questions below:- Section 8.1 of draft-ietf-pce-pcep-07.txt says: A PCEP implementation SHOULD allow configuring the following PCEP session parameters on a PCEP peer: o The local keepalive and Deadtimer (i.e. parameters send by the PCEP speaker in an Open message), o The maximum acceptable remote keepalive and dead timers (i.e.parameters sent by a peer in an Open message), o Negotiation enabled or disabled, o If negotiation is allowed, the minimum acceptable Keepalive and Deadtimer timers sent by a PCEP peer, o The SyncTimer, o The maximum number of sessions that can be setup o Request timer: amount of time a PCC waits for a reply before resending its path computation requests (potentially to an alternate PCE). But, these parameters are not configurable in any of the tables mentioned in draft-kkoushik-pce-pcep-mib-00.txt Section 8.1 also says: A PCEP implementation SHOULD allow configuring a specific PCEP session with a given PCEP peer. This includes the configuration of the following parameters: o The IP address of the PCEP peer, o The PCEP speaker role: PCC, PCE or both, o Whether the PCEP speaker should initiate the PCEP session or wait for initiation by the peer, o The PCEP session parameters, as listed above, if they differ from the default parameters, o A set of PCEP policies including the type of operations allowed for the PCEP peer (e.g. diverse path computation, synchronization, etc.) A PCEP implementation MUST allow restricting the set of PCEP peers that can initiate a PCEP session with the PCEP speaker (e.g. list of authorized PCEP peers, all PCEP peers in the area, all PCEP peers in the AS). Do you have any plan to add these parameters in any new/existing table(s) ? Thanks, Santanu Mazumder A S Kiran Koushik wrote: > Hi pce-team, > We are working on updating the PCE-PCEP-DRAFT-MIB > (PCE communication protocol MIB) with some editorial changes. > http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt > > Can some of you kindly review the existing draft and let us know of any > comments/suggestions. That way we can fix them by the deadline. > > Also we are planning to request this to be a working group document. > If there are any objections to this, please let us know and we will > work on fixing them. > > Thanks, > Kiran and Emile. > > _______________________________________________ > Pce mailing list > Pce@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/pce > --------------060203020608050908070708 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Dear Kiran and Emile,

I have some more questions below:-

Section 8.1 of draft-ietf-pce-pcep-07.txt says:

 
A PCEP implementation SHOULD allow configuring the following PCEP
   session parameters on a PCEP peer:

   o  The local keepalive and Deadtimer (i.e. parameters send by the
      PCEP speaker in an Open message),

   o  The maximum acceptable remote keepalive and dead timers
      (i.e.parameters sent by a peer in an Open message),
    o Negotiation enabled or disabled,
   o  If negotiation is allowed, the minimum acceptable Keepalive and
      Deadtimer timers sent by a PCEP peer,

   o  The SyncTimer,

   o  The maximum number of sessions that can be setup

   o  Request timer: amount of time a PCC waits for a reply before
      resending its path computation requests (potentially to an
      alternate PCE).
But, these parameters are not configurable in any of the tables mentioned in draft-kkoushik-pce-pcep-mib-00.txt

Section 8.1 also says:

A PCEP implementation SHOULD allow configuring
   a specific PCEP session with a given PCEP peer.  This includes the
   configuration of the following parameters:

   o  The IP address of the PCEP peer,

   o  The PCEP speaker role: PCC, PCE or both,

   o  Whether the PCEP speaker should initiate the PCEP session or wait
      for initiation by the peer,

   o  The PCEP session parameters, as listed above, if they differ from
      the default parameters,

   o  A set of PCEP policies including the type of operations allowed
      for the PCEP peer (e.g. diverse path computation, synchronization,
      etc.)

   A PCEP implementation MUST allow restricting the set of PCEP peers
   that can initiate a PCEP session with the PCEP speaker (e.g. list of
   authorized PCEP peers, all PCEP peers in the area, all PCEP peers in
   the AS).


Do you have any plan to add these parameters in any new/existing table(s) ?

Thanks,
Santanu Mazumder


A S Kiran Koushik wrote:
Hi pce-team,
We are working on updating the PCE-PCEP-DRAFT-MIB
(PCE communication protocol MIB) with some editorial changes.
http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt

Can some of you kindly review the existing draft and let us know of any
comments/suggestions. That way we can fix them by the deadline.

Also we are planning to request this to be a working group document.
If there are any objections to this, please let us know and we will work on fixing them.

Thanks,
Kiran and Emile.

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


--------------060203020608050908070708-- --===============2054036217== 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 --===============2054036217==-- From pce-bounces@lists.ietf.org Thu Jun 28 13:48: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 1I3y6S-0000TV-Cv; Thu, 28 Jun 2007 13:48:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3y6R-0000TP-QN for Pce@lists.ietf.org; Thu, 28 Jun 2007 13:48:23 -0400 Received: from nz-out-0506.google.com ([64.233.162.235]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3y5x-0005nN-VS for Pce@lists.ietf.org; Thu, 28 Jun 2007 13:48:23 -0400 Received: by nz-out-0506.google.com with SMTP id i11so361835nzh for ; Thu, 28 Jun 2007 10:47:53 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:content-type; b=cuBfwP2Pd9cWWD6kItpUzp3f800UEtXfEGLreqU6K/bmDC8BMao0YpoF0CtE7BQ8oFsG/5PF04pse30q5SfRDIxznERfzHhfkDJ2ZQc7Er05iG+QzQeFSrLIbzEgqLaY64KLf0Kr6c9yHROyg7eCuesBAmzigVFtPaa+8/3lKeM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:content-type; b=Uv2kXhkdS/M/It3B6PwnTrekwa0VzBl314zYKOVOc8HgLfw4QDcyDjcRV3ub1E2G+EnFltriEAJJ0WYRoCNM+eYOWWFnO1ZmQ7HGVwUmqq3qy9+jlviIvHxYYhc9avkj6nDS68hlBaGoK519wGDNsjwmoIjMTWNrX3gC4pkeQpc= Received: by 10.114.107.19 with SMTP id f19mr1732057wac.1183052871751; Thu, 28 Jun 2007 10:47:51 -0700 (PDT) Received: from ?192.168.1.2? ( [122.167.202.253]) by mx.google.com with ESMTP id j21sm3876846wah.2007.06.28.10.47.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 Jun 2007 10:47:50 -0700 (PDT) Message-ID: <4683F420.6040405@gmail.com> Date: Thu, 28 Jun 2007 23:17:12 +0530 From: santanu User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pce@lists.ietf.org Subject: [Fwd: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB)] X-Spam-Score: 0.4 (/) X-Scan-Signature: 8068004c042dabd7f1301bcc80e039df 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="===============2091181251==" Errors-To: pce-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============2091181251== Content-Type: multipart/alternative; boundary="------------070402040703000004020904" This is a multi-part message in MIME format. --------------070402040703000004020904 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit -------- Original Message -------- Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB) Date: Thu, 28 Jun 2007 23:06:31 +0530 From: santanu To: A S Kiran Koushik CC: pce@ietf.org, jpv@cisco.com References: <4682A0D1.4050904@grotto-networking.com> <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> Dear Kiran and Emile, I have some more questions below:- Section 8.1 of draft-ietf-pce-pcep-07.txt says: A PCEP implementation SHOULD allow configuring the following PCEP session parameters on a PCEP peer: o The local keepalive and Deadtimer (i.e. parameters send by the PCEP speaker in an Open message), o The maximum acceptable remote keepalive and dead timers (i.e.parameters sent by a peer in an Open message), o Negotiation enabled or disabled, o If negotiation is allowed, the minimum acceptable Keepalive and Deadtimer timers sent by a PCEP peer, o The SyncTimer, o The maximum number of sessions that can be setup o Request timer: amount of time a PCC waits for a reply before resending its path computation requests (potentially to an alternate PCE). But, these parameters are not configurable in any of the tables mentioned in draft-kkoushik-pce-pcep-mib-00.txt Section 8.1 also says: A PCEP implementation SHOULD allow configuring a specific PCEP session with a given PCEP peer. This includes the configuration of the following parameters: o The IP address of the PCEP peer, o The PCEP speaker role: PCC, PCE or both, o Whether the PCEP speaker should initiate the PCEP session or wait for initiation by the peer, o The PCEP session parameters, as listed above, if they differ from the default parameters, o A set of PCEP policies including the type of operations allowed for the PCEP peer (e.g. diverse path computation, synchronization, etc.) A PCEP implementation MUST allow restricting the set of PCEP peers that can initiate a PCEP session with the PCEP speaker (e.g. list of authorized PCEP peers, all PCEP peers in the area, all PCEP peers in the AS). Do you have any plan to add these parameters in any new/existing table(s) ? Thanks, Santanu Mazumder A S Kiran Koushik wrote: > Hi pce-team, > We are working on updating the PCE-PCEP-DRAFT-MIB > (PCE communication protocol MIB) with some editorial changes. > http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt > > Can some of you kindly review the existing draft and let us know of any > comments/suggestions. That way we can fix them by the deadline. > > Also we are planning to request this to be a working group document. > If there are any objections to this, please let us know and we will > work on fixing them. > > Thanks, > Kiran and Emile. > > _______________________________________________ > Pce mailing list > Pce@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/pce > --------------070402040703000004020904 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

-------- Original Message --------
Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB)
Date: Thu, 28 Jun 2007 23:06:31 +0530
From: santanu <mazumder.santanu@gmail.com>
To: A S Kiran Koushik <kkoushik@cisco.com>
CC: pce@ietf.org, jpv@cisco.com
References: <4682A0D1.4050904@grotto-networking.com> <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com>


Dear Kiran and Emile,

I have some more questions below:-

Section 8.1 of draft-ietf-pce-pcep-07.txt says:

 
A PCEP implementation SHOULD allow configuring the following PCEP
   session parameters on a PCEP peer:

   o  The local keepalive and Deadtimer (i.e. parameters send by the
      PCEP speaker in an Open message),

   o  The maximum acceptable remote keepalive and dead timers
      (i.e.parameters sent by a peer in an Open message),
    o Negotiation enabled or disabled,
   o  If negotiation is allowed, the minimum acceptable Keepalive and
      Deadtimer timers sent by a PCEP peer,

   o  The SyncTimer,

   o  The maximum number of sessions that can be setup

   o  Request timer: amount of time a PCC waits for a reply before
      resending its path computation requests (potentially to an
      alternate PCE).
But, these parameters are not configurable in any of the tables mentioned in draft-kkoushik-pce-pcep-mib-00.txt

Section 8.1 also says:

A PCEP implementation SHOULD allow configuring
   a specific PCEP session with a given PCEP peer.  This includes the
   configuration of the following parameters:

   o  The IP address of the PCEP peer,

   o  The PCEP speaker role: PCC, PCE or both,

   o  Whether the PCEP speaker should initiate the PCEP session or wait
      for initiation by the peer,

   o  The PCEP session parameters, as listed above, if they differ from
      the default parameters,

   o  A set of PCEP policies including the type of operations allowed
      for the PCEP peer (e.g. diverse path computation, synchronization,
      etc.)

   A PCEP implementation MUST allow restricting the set of PCEP peers
   that can initiate a PCEP session with the PCEP speaker (e.g. list of
   authorized PCEP peers, all PCEP peers in the area, all PCEP peers in
   the AS).


Do you have any plan to add these parameters in any new/existing table(s) ?

Thanks,
Santanu Mazumder


A S Kiran Koushik wrote:
Hi pce-team,
We are working on updating the PCE-PCEP-DRAFT-MIB
(PCE communication protocol MIB) with some editorial changes.
http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt

Can some of you kindly review the existing draft and let us know of any
comments/suggestions. That way we can fix them by the deadline.

Also we are planning to request this to be a working group document.
If there are any objections to this, please let us know and we will work on fixing them.

Thanks,
Kiran and Emile.

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


--------------070402040703000004020904-- --===============2091181251== 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 --===============2091181251==-- From pce-bounces@lists.ietf.org Thu Jun 28 15:50:46 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I400l-00027l-8l; Thu, 28 Jun 2007 15:50:39 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I400f-00023g-1P; Thu, 28 Jun 2007 15:50:33 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I400e-00037G-QP; Thu, 28 Jun 2007 15:50:32 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id B1DBA2ACAD; Thu, 28 Jun 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I400A-0005Pd-F8; Thu, 28 Jun 2007 15:50: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, 28 Jun 2007 15:50:02 -0400 X-Spam-Score: 0.3 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: pce@ietf.org Subject: [Pce] I-D ACTION:draft-ietf-pce-disco-proto-ospf-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 : OSPF protocol extensions for Path Computation Element (PCE) Discovery Author(s) : J. Le Roux, et al. Filename : draft-ietf-pce-disco-proto-ospf-06.txt Pages : 21 Date : 2007-6-28 There are various circumstances where it is highly desirable for a Path Computation Client (PCC) to be able to dynamically and automatically discover a set of Path Computation Elements (PCE), along with some information that can be used for PCE selection. When the PCE is a Label Switching Router (LSR) participating in the Interior Gateway Protocol (IGP), or even a server participating passively in the IGP, a simple and efficient way to discover PCEs consists of using IGP flooding. For that purpose, this document defines extensions to the Open Shortest Path First (OSPF) routing protocol for the advertisement of PCE Discovery information within an OSPF area or within the entire OSPF routing domain. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-disco-proto-ospf-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-disco-proto-ospf-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-disco-proto-ospf-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-6-28133043.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-disco-proto-ospf-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-disco-proto-ospf-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-6-28133043.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 Jun 28 16:08: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 1I40He-0001BX-Ag; Thu, 28 Jun 2007 16:08:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I40HY-00016m-CS; Thu, 28 Jun 2007 16:08:00 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I40Gq-00017O-Gz; Thu, 28 Jun 2007 16:08:00 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 9220726ED6; Thu, 28 Jun 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I400A-0005PU-Cf; Thu, 28 Jun 2007 15:50: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, 28 Jun 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: pce@ietf.org Subject: [Pce] I-D ACTION:draft-ietf-pce-disco-proto-isis-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 : IS-IS protocol extensions for Path Computation Element (PCE) Discovery Author(s) : J. Le Roux, et al. Filename : draft-ietf-pce-disco-proto-isis-06.txt Pages : 19 Date : 2007-6-28 There are various circumstances where it is highly desirable for a Path Computation Client (PCC) to be able to dynamically and automatically discover a set of Path Computation Elements (PCE), along with some information that can be used for PCE selection. When the PCE is a Label Switching Router (LSR) participating in the Interior Gateway Protocol (IGP), or even a server participating passively in the IGP, a simple and efficient way to discover PCEs consists of using IGP flooding. For that purpose this document defines extensions to the Intermediate System to Intermediate System (IS-IS) routing protocol for the advertisement of PCE Discovery information within an IS-IS area or within the entire IS-IS routing domain. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-disco-proto-isis-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-disco-proto-isis-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-disco-proto-isis-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-6-28132435.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pce-disco-proto-isis-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pce-disco-proto-isis-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-6-28132435.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 Jun 28 18:16: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 1I42HZ-0002dY-Lu; Thu, 28 Jun 2007 18:16:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I42HZ-0002dS-1Z for pce@ietf.org; Thu, 28 Jun 2007 18:16:09 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I42HT-0002XK-Eb for pce@ietf.org; Thu, 28 Jun 2007 18:16:09 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 28 Jun 2007 18:16:03 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAP7Pg0ZAZnme/2dsb2JhbAA X-IronPort-AV: i="4.16,472,1175486400"; d="scan'208"; a="124828359:sNHT39708264" Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5SMG3K2020896; Thu, 28 Jun 2007 18:16:03 -0400 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 l5SMG3ZF008248; Thu, 28 Jun 2007 22:16:03 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 18:16:03 -0400 Received: from kkoushikwxp ([64.101.185.227]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 18:16:02 -0400 Message-ID: <05fc01c7b9d1$ea3c6b00$6b10590a@apac.cisco.com> From: "A S Kiran Koushik" To: "Meral Shirazipour" References: <4682A0D1.4050904@grotto-networking.com> <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> <1183039913.4683c1a9722c8@www.imp.polymtl.ca> Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB) Date: Thu, 28 Jun 2007 17:16:02 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; 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.3138 X-OriginalArrivalTime: 28 Jun 2007 22:16:02.0539 (UTC) FILETIME=[E9D03BB0:01C7B9D1] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2175; t=1183068963; x=1183932963; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kkoushik@cisco.com; z=From:=20=22A=20S=20Kiran=20Koushik=22=20 |Subject:=20Re=3A=20[Pce]=20draft-kkoushik-pce-pcep-mib-00.txt=20(PCE-PCE P-DRAFT-MIB) |Sender:=20 |To:=20=22Meral=20Shirazipour=22=20; bh=7Xv+3K57PG9Cy/R+ap1KJ22Wos103u4yOoFj6Fv4C4E=; b=Xts7Xy+DG35Gs3VMYNDWFPW6zDwqgITAOTx77IOHZTCzGTXf4rWtgBCyw3z3hgDRwhdLrGEL uLuysFKR1hxTUZ/Zpj4yJ7a597OIM3FJCW84Md+tXVmk5f8l6aeJxxdw; Authentication-Results: rtp-dkim-1; header.From=kkoushik@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: pce@ietf.org, jpv@cisco.com 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 Meral, We have divided the organization of PCE management MIBs as below: MIB module WG draft name ================================================ PCE-DISC-DRAFT-MIB draft-ietf-pce-disc-mib -- PCE discovery MIB. PCE-PCEP-DRAFT-MIB draft-ietf-pce-pcep-mib -- PCE communication protocol MIB PCE-PCC-DRAFT-MIB draft-ietf-pce-pcc-mib -- Path Computation Client MIB PCE-TC-DRAFT-MIB draft-ietf-pce-tc-mib -- PCE Textual conventions MIB. The information you are referring to below will be contained as a part of draft-ietf-pce-pcc-mib which is yet to be started. Regards, Kiran. ----- Original Message ----- From: "Meral Shirazipour" To: "A S Kiran Koushik" Cc: ; Sent: Thursday, June 28, 2007 9:11 AM Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB) > Hi, > I have a question regarding page 3, section 4: > "The PCEP MIB will contain the following information: > a. PCEP client configuration and status." > > Does the "status" here also represent the previous/ongoing path computation > requests? > I am referring to Section 6.8. Stateful versus Stateless PCEs in RFC4655; > would > the information related to a stateful PCE be stored in the described MIB ? > > Best regards, > Meral > > > Selon A S Kiran Koushik : > >> Hi pce-team, >> We are working on updating the PCE-PCEP-DRAFT-MIB >> (PCE communication protocol MIB) with some editorial changes. >> http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt >> >> Can some of you kindly review the existing draft and let us know of any >> comments/suggestions. That way we can fix them by the deadline. >> >> Also we are planning to request this to be a working group document. >> If there are any objections to this, please let us know and we will work >> on fixing them. >> >> Thanks, >> Kiran and Emile. >> >> _______________________________________________ >> 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 Thu Jun 28 18:37:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I42br-0001N9-73; Thu, 28 Jun 2007 18:37:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I42bp-000172-DT for pce@ietf.org; Thu, 28 Jun 2007 18:37:05 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I42bU-0005at-7S for pce@ietf.org; Thu, 28 Jun 2007 18:37:05 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-5.cisco.com with ESMTP; 28 Jun 2007 15:36:43 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAADbUg0arR7PDh2dsb2JhbACPKwIJDiw X-IronPort-AV: i="4.16,472,1175497200"; d="scan'208"; a="164762242:sNHT69924510" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5SMahlH032531; Thu, 28 Jun 2007 15:36:43 -0700 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 l5SMagXH020363; Thu, 28 Jun 2007 22:36:42 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 18:36:42 -0400 Received: from kkoushikwxp ([64.101.185.227]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 18:36:41 -0400 Message-ID: <063701c7b9d4$cd0a5440$6b10590a@apac.cisco.com> From: "A S Kiran Koushik" To: "santanu" References: <4682A0D1.4050904@grotto-networking.com> <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> <4683F19F.5010708@gmail.com> Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB) Date: Thu, 28 Jun 2007 17:36:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; 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.3138 X-OriginalArrivalTime: 28 Jun 2007 22:36:41.0999 (UTC) FILETIME=[CC96D1F0:01C7B9D4] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3313; t=1183070203; x=1183934203; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kkoushik@cisco.com; z=From:=20=22A=20S=20Kiran=20Koushik=22=20 |Subject:=20Re=3A=20[Pce]=20draft-kkoushik-pce-pcep-mib-00.txt=20(PCE-PCE P-DRAFT-MIB) |Sender:=20; bh=a5KiOf8GTv3vcZJ5zg3S9pD3YDNMlpfquQc82jR6olM=; b=fLaAzu1SKju0+9ejdj+HV0aHymnWyf8aGVSn2dL5Xi4zLbQ8QanQTUsgx2e+hid1Z3r3j9k6 WlznNtrNaTMoAPiomFY2jrMw36ENlQ73ES8nkJVjhsce3d1HkYsCxzt5; Authentication-Results: sj-dkim-3; header.From=kkoushik@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 Cc: pce@ietf.org, jpv@cisco.com 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 Santanu, Yes, we have plans to update the MIB with the below configurable parameters in its next version. Regards, Kiran. ----- Original Message ----- From: "santanu" To: "A S Kiran Koushik" Cc: ; Sent: Thursday, June 28, 2007 12:36 PM Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB) > Dear Kiran and Emile, > > I have some more questions below:- > > Section 8.1 of draft-ietf-pce-pcep-07.txt says: > > > A PCEP implementation SHOULD allow configuring the following PCEP > session parameters on a PCEP peer: > > o The local keepalive and Deadtimer (i.e. parameters send by the > PCEP speaker in an Open message), > > o The maximum acceptable remote keepalive and dead timers > (i.e.parameters sent by a peer in an Open message), > > o Negotiation enabled or disabled, > > o If negotiation is allowed, the minimum acceptable Keepalive and > Deadtimer timers sent by a PCEP peer, > > o The SyncTimer, > > o The maximum number of sessions that can be setup > > o Request timer: amount of time a PCC waits for a reply before > resending its path computation requests (potentially to an > alternate PCE). > > > But, these parameters are not configurable in any of the tables > mentioned in draft-kkoushik-pce-pcep-mib-00.txt > > Section 8.1 also says: > > A PCEP implementation SHOULD allow configuring > a specific PCEP session with a given PCEP peer. This includes the > configuration of the following parameters: > > o The IP address of the PCEP peer, > > o The PCEP speaker role: PCC, PCE or both, > > o Whether the PCEP speaker should initiate the PCEP session or wait > for initiation by the peer, > > o The PCEP session parameters, as listed above, if they differ from > the default parameters, > > o A set of PCEP policies including the type of operations allowed > for the PCEP peer (e.g. diverse path computation, synchronization, > etc.) > > A PCEP implementation MUST allow restricting the set of PCEP peers > that can initiate a PCEP session with the PCEP speaker (e.g. list of > authorized PCEP peers, all PCEP peers in the area, all PCEP peers in > the AS). > > > > Do you have any plan to add these parameters in any new/existing table(s) ? > > Thanks, > Santanu Mazumder > > > A S Kiran Koushik wrote: > >> Hi pce-team, >> We are working on updating the PCE-PCEP-DRAFT-MIB >> (PCE communication protocol MIB) with some editorial changes. >> http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt >> >> Can some of you kindly review the existing draft and let us know of any >> comments/suggestions. That way we can fix them by the deadline. >> >> Also we are planning to request this to be a working group document. >> If there are any objections to this, please let us know and we will >> work on fixing them. >> >> Thanks, >> Kiran and Emile. >> >> _______________________________________________ >> 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 Thu Jun 28 19:11:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I438o-00076n-Dw; Thu, 28 Jun 2007 19:11:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I438m-00072O-Kr for pce@ietf.org; Thu, 28 Jun 2007 19:11:08 -0400 Received: from mta5.iomartmail.com ([62.128.193.155]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I438i-00075D-8d for pce@ietf.org; Thu, 28 Jun 2007 19:11:08 -0400 Received: from mta5.iomartmail.com (localhost.localdomain [127.0.0.1]) by mta5.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id l5SNB3jW027938 for ; Fri, 29 Jun 2007 00:11:03 +0100 Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by mta5.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id l5SNAjRm027748 for ; Fri, 29 Jun 2007 00:11:02 +0100 Message-ID: <022d01c7b9d9$97dbba70$0a23fea9@your029b8cecfe> From: "Adrian Farrel" To: Date: Fri, 29 Jun 2007 00:09:47 +0100 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.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: Subject: [Pce] Considering draft-vasseur-pce-monitoring-03.txt for WG status 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, draft-vasseur-pce-monitoring-03.txt was updated last month to take into account issues raised in Prague and on the mailing list. The I-D specifies procedures and extensions to PCEP in order to gather information about the state of the chain of PCEs involved in a path computation chain for troubleshooting and performance monitoring purposes. Please state your opinion on whether this should become a working group draft. Thanks, Adrian _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce