RE: Last Call: draft-ietf-pce-pcep (Path Computation Element (PCE) Communication Protocol (PCEP)) to Proposed Standard

Olafur Gudmundsson <ogud@ogud.com> Thu, 01 May 2008 15:36 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2ABD93A6E29; Thu, 1 May 2008 08:36:04 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF7773A6E29; Thu, 1 May 2008 08:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-s+zf1EmCHz; Thu, 1 May 2008 08:36:01 -0700 (PDT)
Received: from ogud.com (hlid.ogud.com [66.92.146.160]) by core3.amsl.com (Postfix) with ESMTP id 2616928C3FB; Thu, 1 May 2008 08:33:42 -0700 (PDT)
Received: from Puki.ogud.com (ns.md.ogud.com [10.20.30.6]) by ogud.com (8.13.1/8.13.1) with ESMTP id m41FXcn2013012; Thu, 1 May 2008 11:33:38 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-Id: <200805011533.m41FXcn2013012@ogud.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 01 May 2008 11:33:36 -0400
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
From: Olafur Gudmundsson <ogud@ogud.com>
Subject: RE: Last Call: draft-ietf-pce-pcep (Path Computation Element (PCE) Communication Protocol (PCEP)) to Proposed Standard
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04B7B28E@307622ANEX5.global. avaya.com>
References: <20080416204850.8E0A43A6F68@core3.amsl.com> <EDC652A26FB23C4EB6384A4584434A04B7B28E@307622ANEX5.global.avaya.com>
Mime-Version: 1.0
X-Scanned-By: MIMEDefang 2.63 on 10.20.30.6
Cc: ops-dir@ietf.org, pce@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Yes this is well written document,
I find it scary how many flags fields the document defines in message types
with no flags defined and NO GUIDANCE on the scope of these flags.
Are they per "object Class +object type" or per message type.

Are these needed or just nice to have?
What is the harm to just define these fields as Reserved ?

         Olafur


At 05:56 30/04/2008, Romascanu, Dan (Dan) wrote:
>I would like to congratulate the editors for the inclusion and content
>of the Manageability Consideration section. It is well written, and
>includes detailed information that will be very useful for implementers
>as well as for operators who will deploy the protocol.
>
>One nit: in section 8.6 s/number of session/number of sessions/
>
>Dan
>
>
> > -----Original Message-----
> > From: ietf-announce-bounces@ietf.org
> > [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
> > Sent: Wednesday, April 16, 2008 11:49 PM
> > To: IETF-Announce
> > Cc: pce@ietf.org
> > Subject: Last Call: draft-ietf-pce-pcep (Path Computation
> > Element (PCE) Communication Protocol (PCEP)) to Proposed Standard
> >
> > The IESG has received a request from the Path Computation Element WG
> > (pce) to consider the following document:
> >
> > - 'Path Computation Element (PCE) Communication Protocol (PCEP) '
> >    <draft-ietf-pce-pcep-12.txt> as a Proposed Standard
> >
> > 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
> > 2008-04-30. 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-pcep-12.txt
> >
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/public/pidtracker.cgi?command=vie
> > w_id&dTag=14049&rfc_flag=0
> >
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-announce
> >
>_______________________________________________
>IETF mailing list
>IETF@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf