(as an individual) On Fri, Nov 7, 2025 at 11:57 AM Hollenbeck, Scott <shollenbeck= [email protected]> wrote:
> I'm having a lot of difficulty understanding people's positions on the > issues associated with registering Internet-Drafts and non-IETF > specifications in the EPP extension registry. I'm going to ask some basic > questions that I'd like people to answer to help me understand where we > agree and disagree. These questions have simple "yes" or "no" answers. As > given information, we know that RFC 3688 prohibits registration of XML > schema and namespace URIs where the associated specification isn't an RFC. > > Should we allow registration of an active Internet-Draft on a provisional > basis with the registered entity expected to be updated when the draft > proceeds to RFC status? > No? This is a common problem in http and media types... if you have string code points that are registered provisionally, and people implement them... you can't really "take them back"... in HTTP headers, this led to the decision to stop x- prefixing... https://datatracker.ietf.org/doc/html/rfc6648 We frequently grandfather deprecated x- prefixed media types into the standards tree, for media types that have widespread use, see also: https://www.ietf.org/rfc/rfc6838.html#appendix-A I'm not sure what you are asking here, but if you are suggesting something like x- for EPP, please don't do that : ) > > Should we allow registration of an inactive or abandoned Internet-Draft > knowing that the draft might not proceed to RFC status? > Yes > > Should we require non-IETF EPP extensions to register their URIs using > non-IETF namespaces? > Yes, (this is consistent with what XML registry attempts, but as noted, does not prevent conflicts) > > There will be other things to consider once we have agreement on the > answers to these questions. > > Scott > _______________________________________________ > regext mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
