I think simplifying this to always send to regext is a good idea. We aren't saving that many bits otherwise.
Tracking here: https://github.com/anewton1998/draft-regext-rdap-extensions/issues/88 -andy, doc co-author On Fri, Jul 17, 2026 at 2:40 PM Amanda Baber via RT <[email protected]> wrote: > > Dear Authors (cc: regext), > > Before the IETF meeting, we check working group agendas for documents with > IANA-related issues. Notes about this document: > > https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-extensions-14 > > Just double-checking logistics: Section 7.2 says, “IANA is requested to send > a copy of any request not originating from the IETF to [email protected] or its > successor.” Are you sure you don’t want the experts to forward the request > from IANA as needed, or for IANA to just copy [email protected] on all requests > we send to the experts? Should requests originating in AD-sponsored documents > or other WG documents be sent to the list? > > If you have any questions, just let us know. If you'd like to talk in person, > you can find us at the IANA table from Monday through Thursday. You can also > request another review at any time by contacting us at [email protected]. > > For more information about IANA Considerations section requirements, please > see > > https://www.iana.org/help/protocol-registration > > Best regards, > > Amanda Baber > IANA _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
