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

From: Olafur Gudmundsson <[email-masked]>
Date: Thu, 01 May 2008 11:33:36 -0400

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: [email-masked]
> > [mailto:[email-masked]] On Behalf Of The IESG
> > Sent: Wednesday, April 16, 2008 11:49 PM
> > To: IETF-Announce
> > Cc: [email-masked]
> > 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 [email-masked] mailing lists by
> > 2008-04-30. Exceptionally, comments may be sent to
> > [email-masked] 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
> > [email-masked]
> > https://www.ietf.org/mailman/listinfo/ietf-announce
> >
>_______________________________________________
>IETF mailing list
>[email-masked]
>https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
IETF mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/ietf