Hi Gavin, On 07.11.25 04:29, Gavin Brown wrote:
A standards-track I-D can use any URI, and then switch to an IETF URN at the point when it is published as an RFC. But I think draft-ietf-regext-ext-registry-epp may want to say so, with reference to the above.
Similar to the discussion on draft-carney-regext-rfc3915bis-00, a "switch to an IETF URN", if there are already live deployments base in the wild is a very complex and costly process - both for the registries and registrars. I don't see any business case that would support that. The framework shall be defined the way, that such things won't happen just out of procedural requirements.
Kind Regards, Pawel
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
