Hi Thomas, > On 18 Dec 2025, at 11:32, Thomas Corte (TANGO support) > <[email protected]> wrote: > > Hello Gavin, > > On 18.12.25 12:24, Gavin Brown wrote: > >> Hi Sabrina, >> These are OK to be registered, however, please change the “Document status” >> of these >> registrations to “Other”. This will help avoid confusion with Informational >> RFCs. > > Thanks for the review! > > Note that I saw this status being corrected for my previous submissions and > considered using "Other" for the new ones, but then I looked at > https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc7451.html__;!!PtGJab4!-28wDT895SwYLYAlnT2nR_RN73njQx5_4wzTIXyp0zwqft-AuyofhYO1WBLWjS4YcpBD-8Aak5cM5ofXJHjCrychm5_dDF9M$ > [rfc-editor[.]org] again which says: > > Document Status: The document status ("Informational", "Standards > Track", etc.) of the specification document. For documents that are > not RFCs, this will always be "Informational". > > So this is no longer correct?
This comment was added to harmonise my response with that of Scott, in his last review (of the Domain Name Variant Extension Mapping), which can be seen here: https://mailarchive.ietf.org/arch/msg/regext/yREHVLThpQVrGXoc2M2FwJ2oVmE/ Both comments attempt to "future-proof" the registrations with the guidance in draft-ietf-regext-ext-registry-epp. >> Please also suggest to the registrand that since multiple deployments (if >> not implementations) >> of these extensions exist, they should consider publishing new versions that >> use namespaces that >> can be shared between existing (and any future) implementations. This will >> make things much >> easier for client implementers. They may then submit a request to mark the >> old registrations as >> “inactive”. > > Indeed, we'll look into this, as it will make our lives easier, too. Good to hear! G. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
