Just for clarification draft-ietf-regext-rdap-extensions is not being held up based on draft-ietf-regext-rdap-versioning but based on an attempt to tackle the versioning problem in scope for draft-ietf-regext-rdap-versioning. If we have overlapping, incompatible, and in cases competing approaches being defined in active working group drafts, we need to reconcile those ahead of one of the drafts moving to WGLC. I have communicated the compatibility issues across the three working group documents (draft-ietf-regext-rdap-x-media-type, draft-ietf-regext-rdap-versioning, and draft-ietf-regext-rdap-extensions) numerous times.
I posted the "Extensions Versioning Location Information and What Changes the Version Options (https://mailarchive.ietf.org/arch/msg/regext/XHyPXtm0fCFlnHeHEU_kr63cg7s/) message to the mailing list in the hope of discussing the options and preferences moving forward, but I have not received any responses yet. Please review this message and respond to it with any additional options, your preference(s), and the reasons for your preference(s) so we can find a path forward. Thanks, -- JG James Gould Fellow Engineer [email protected] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 6/18/26, 1:45 PM, "Pawel Kowalik" <[email protected] <mailto:[email protected]>> wrote: On 18.06.26 14:44, Andy Newton wrote: > Finally, it very unfair to the author team and the working group for you to > hold up this document based on your versioning draft. Since adoption, the > versioning draft has radically changed, moving from semantic versioning to > maturity versioning to point versioning and now a new theory called embedded > versioning. It is a meandering, moving target with a lot of complexity. So > that this does not spiral further, it would be best if the chairs stepped in > now. +1 Pawel _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
