Hi Robert (I'm answering as WG chair.)
Sorry for the slow reply. I would expect the progress of draft-ietf-pce-pceps through to RFC to be reasonably fast, so I'm not sure early code point allocation should be needed. The main risk would be a conflict with the stateful PCE drafts, should the new message in the PCEPS draft be allocated a clashing code point with the values that the stateful drafts have "recommended" for their messages. I think it is possible that PCEPS will leap-frog stateful PCE on the way to RFC, so I think the best way to proceed is to obtain an early allocation for draft-ietf-pce-stateful-pce and draft-ietf-pce-pce-initiated-lsp. To do this we would only require help from the stateful draft authors (e.g. you) to answer any questions that IANA has about your text (which would happen sooner or later anyway :-). Would you like us to start an early allocation for these drafts? Best regards Jon From: Pce [mailto:[email protected]] On Behalf Of Robert Varga Sent: 21 January 2016 21:48 To: DIEGO LOPEZ GARCIA <[email protected]>; [email protected] Subject: Re: [Pce] draft-ietf-pce-pceps-07 available On 2016-01-21 15:07, DIEGO LOPEZ GARCIA wrote: Hi, We have just uploaded a new version of draft-ietf-pce-pceps (https://datatracker.ietf.org/doc/draft-ietf-pce-pceps/) We believe this new version addresses all the comments received from the SECDIR review after the last call period, and other pending ones provided by Tom while that SECDIR review was taking place. As far as the authors can say, the document is ready to progress. Hello, would it make sense to request an early codepoint allocation for use in implementations? Thanks, Robert
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
