RE: [Pce] draft-leroux-pce-of-00.txt
"ASH, GERALD R, ATTLABS" <gash@att.com> Thu, 15 March 2007 21:55 UTC
Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRxvE-0004hV-SD; Thu, 15 Mar 2007 17:55:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRxvD-0004gm-AS for pce@ietf.org; Thu, 15 Mar 2007 17:55:43 -0400
Received: from mail146.messagelabs.com ([216.82.245.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HRxv0-0007cm-9w for pce@ietf.org; Thu, 15 Mar 2007 17:55:43 -0400
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-12.tower-146.messagelabs.com!1173995729!3284366!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 14671 invoked from network); 15 Mar 2007 21:55:29 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-12.tower-146.messagelabs.com with SMTP; 15 Mar 2007 21:55:29 -0000
Received: from attrh.att.com (localhost [127.0.0.1]) by attrh3i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2FLtSbV019905; Thu, 15 Mar 2007 17:55:28 -0400 (EDT)
Received: from kcclust06evs1.ugd.att.com ([135.38.164.88]) by attrh3i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2FLtEa3019828; Thu, 15 Mar 2007 17:55:25 -0400 (EDT)
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] draft-leroux-pce-of-00.txt
Date: Thu, 15 Mar 2007 16:55:03 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC8308@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <D109C8C97C15294495117745780657AE0736D435@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Pce] draft-leroux-pce-of-00.txt
Thread-Index: AcdbVwERm/G70y43SzGrppgaWl9PcQBztA2QAMiArrAAbnR58AEJVQNAABJeg4AABX8JsAAw+otw
References: <9473683187ADC049A855ED2DA739ABCA0DDC82FE@KCCLUST06EVS1.ugd.att.com> <D109C8C97C15294495117745780657AE0736D435@ftrdmel1.rd.francetelecom.fr>
From: "ASH, GERALD R, ATTLABS" <gash@att.com>
To: LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@orange-ftgroup.com>, pce@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc:
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org
Hi JL, > > IMO an important missing PCECP requirement is identified in > > http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-07.txt > > Appendix A (Compliance with the PCECP Requirement Document): > > > > " Here is the list of currently unsatisfied requirements: > > > > o Allow to select/prefer from advertised list of standard > > objective > > functions/options > > > > o Allow to customize objective function/options > > > > o Support "unsynchronized" & "synchronized" objective functions" > > > > They all deal with the missing 6 objective functions required > > in RFC 4657, and are an important omission in PCEP, so far. > > > In montreal we indicated that objective functions would not > be covered in the base PCEP spec. > There was no objection. This was recalled in San Diego, again > no objection... Well that doesn't cast it in concrete, I'll register my objection. Without objective functions, PCE would not be able to do much to optimize path computation. I think it's important for PCEP to include the objective functions required in the PCECP generic requirements in the base PCEP spec. > > You say that PCEP is 'stable' so you don't want to add them > > there? > > What I say is that this would create dependency between PCEP > and OF drafts which is not good. The base PCEP draft should > not have any dependency with other drafts. > > > Does that mean no further changes to PCEP before > > WGLC? > > Definitely no! > > But, again, note that it was agreed that objective functions > would not be covered in the base spec. See above comments. > > I don't think other new drafts (e.g., > > draft-lee-pce-global-concurrent-optimization-02.txt) that > > specify perhaps *new* PCEP requirements, should be satisfying > > the original RFC 4657 PCECP requirements on PCEP. > > Why? > > Draft-lee specifies two objective functions listed in 4657, > where is the problem? Several. No rationale to put generic PCECP requirements in some other draft besides the base PCEP draft. The draft isn't a WG draft. There isn't any compelling reason to not specify the objective functions in the base PCEP draft. > > You also > > say 'We can add other synchronized objective functions in the > > next revision of the gco draft.' I don't think that's the > > right place to satisfy the PCECP requirements. > > Why? See above comments. Thanks, Regards, Jerry _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce
- [Pce] draft-leroux-pce-of-00.txt LE ROUX Jean-Louis RD-CORE-LAN
- RE: [Pce] draft-leroux-pce-of-00.txt ASH, GERALD R, ATTLABS
- RE: [Pce] draft-leroux-pce-of-00.txt LE ROUX Jean-Louis RD-CORE-LAN
- Re: [Pce] draft-leroux-pce-of-00.txt Wenhu Lu
- RE: [Pce] draft-leroux-pce-of-00.txt LE ROUX Jean-Louis RD-CORE-LAN
- Re: [Pce] draft-leroux-pce-of-00.txt JP Vasseur
- Re: [Pce] draft-leroux-pce-of-00.txt Wenhu Lu
- Re: [Pce] draft-leroux-pce-of-00.txt JP Vasseur
- RE: [Pce] draft-leroux-pce-of-00.txt ASH, GERALD R, ATTLABS
- RE: [Pce] draft-leroux-pce-of-00.txt LE ROUX Jean-Louis RD-CORE-LAN
- RE: [Pce] draft-leroux-pce-of-00.txt ASH, GERALD R, ATTLABS
- RE: [Pce] draft-leroux-pce-of-00.txt LE ROUX Jean-Louis RD-CORE-LAN
- RE: [Pce] draft-leroux-pce-of-00.txt ASH, GERALD R, ATTLABS
- Re: [Pce] draft-leroux-pce-of-00.txt JP Vasseur