Hi Adrian, Dhruv, I also see added value in doing it. Ideally we should really have some reserved range wherever possible to avoid using completely non-standard objects…
Thanks, Samuel From: Dhruv Dhody <[email protected]> Sent: Tuesday, July 23, 2024 4:03 AM To: [email protected] Cc: [email protected] Subject: [Pce] Re: Experimental Error-Types and Error-values Hi Adrian, As a WG participant... On Wed, Jul 3, 2024 at 3:45 AM Adrian Farrel <[email protected]<mailto:[email protected]>> wrote: Hi working group, I just refreshed draft-farrel-pce-experimental-errors and cleaned up a couple of nits. It tweaks the scope of the IANA registry to carve out a few Error-Types to be for Experimental Use. It also describes how to experiment with Error-Types and Error-values BIG QUESTION Does the working group want to pursue this? IMHO it might be worth doing this. Can those who have used experimental codepoints for messages, objects and TLV comment on the need for them for error-types? Could this have helped you in your experiments? If we go down in this direction, I also wonder if we should reserve some space for error-values for each of the error-types as it is common practice to assign new errors under the error-type! Thanks! Dhruv If so: chairs, can we consider adoption? If not: I can get a little peace by dropping the draft Cheers, Adrian -----Original Message----- From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Sent: 03 July 2024 11:34 To: Adrian Farrel <[email protected]<mailto:[email protected]>>; Haomian Zheng <[email protected]<mailto:[email protected]>> Subject: New Version Notification for draft-farrel-pce-experimental-errors-02.txt A new version of Internet-Draft draft-farrel-pce-experimental-errors-02.txt has been successfully submitted by Adrian Farrel and posted to the IETF repository. Name: draft-farrel-pce-experimental-errors Revision: 02 Title: Allowing Experimental Error Codes in the Path Computation Element Protocol Date: 2024-07-03 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/archive/id/draft-farrel-pce-experimental-errors-02.txt Status: https://datatracker.ietf.org/doc/draft-farrel-pce-experimental-errors/ HTMLized: https://datatracker.ietf.org/doc/html/draft-farrel-pce-experimental-errors Diff: https://author-tools.ietf.org/iddiff?url2=draft-farrel-pce-experimental-errors-02 Abstract: Experimental RFCs are often considered beneficial approaches to developing new protocol features. To that end, sub-ranges of code point registries are often designated as for experimental use. IANA assigns values to the Path Computation Element Communication Protocol (PCEP) parameters (messages, objects, TLVs). According to RFC 5440 as updated by RFC 8356, the allocation policies for the registries for PCEP messages, objects, and TLV types are IETF Review with some sub-ranges of these registries being assigned for Experimental Use. However, the registry of PCEP Error-Types and Error-values has only the IETF Review assignment policy meaning that experimentation is somewhat limited. This document updates RFC 5440 by designating a range of PCEP Error- Types for Experimental Use. _______________________________________________ Pce mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________ Pce mailing list -- [email protected] To unsubscribe send an email to [email protected]
