Folliwing the admonishments to pipe up if you haven't participated in the discussion as of yet (and having spent some time reading through the email thread and watching the meeting discussions).
Option A // Eric ________________________________ From: Pawel Kowalik <kowalik=40denic...@dmarc.ietf.org> Sent: 15 August 2025 18:00 To: Jasdip Singh <jasd...@arin.net>; James Galvin <gal...@elistx.com>; REGEXT Working Group <regext@ietf.org> Subject: [regext] Re: RESPONSE REQUESTED: status of draft-ietf-regext-rdap-extensions Option B. Yes, please voice up. Kind Regards, Pawel On 15.08.25 16:52, Jasdip Singh wrote: Hi, Option A. To help bring closure, it’d be good to hear from folks who might not have participated earlier in this discussion. Thanks, Jasdip From: James Galvin <gal...@elistx.com><mailto:gal...@elistx.com> Date: Wednesday, August 13, 2025 at 8:56 AM To: REGEXT Working Group <regext@ietf.org><mailto:regext@ietf.org> Subject: [regext] RESPONSE REQUESTED: status of draft-ietf-regext-rdap-extensions During our IETF123 meeting the status of “RDAP Extensions” <https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-extensions/> was discussed. Currently there is one technical issue that has been under discussion on the mailing list for some time. It was agreed during the meeting that the Chairs would seek to bring the discussion to a close by asking the open question on the mailing list. The Chairs need your response. We would most like to hear from folks who have not had much to say up to this point. The question is what should the status of bare identifiers be in the “RDAP Extensions” draft? Three possible answers have emerged. The Chairs are opening a poll by presenting the three choices and asking folks to indicate the option they would most prefer to support. Please note - this is not a discussion. If you have a clarifying question you may ask and the Chairs will respond. The Chairs are asking you to indicate which option you would most prefer to support. The three options are as follows. A. Always disallow them - Bare identifiers can cause confusion because they do not define a structured namespace. The bare identifiers that already exist in the RDAP Extensions Registry would be permitted to remain as specified; new bare identifiers would not be allowed. B. Always allow them - They already exist in the RDAP Extensions Registry and thus we know that they can work. The IANA processes ensure there are no duplicate identifiers. C. Only allow them if it is REQUIRED to solve the problem being considered - This option is a compromise that would require that guidance exist in order to evaluate whether or not the bare identifier is the only solution. Some additional background information you may find helpful as you consider which option you would most prefer to support can be found in the following IAB guidance: [1] https://datatracker.ietf.org/doc/html/rfc5218#autoid-15 [2] https://datatracker.ietf.org/doc/html/rfc1958#page-4 [3] https://datatracker.ietf.org/doc/html/rfc9413#name-protocol-decay Also note that given there are already some bare identifiers defined in the IANA RDAP Extension Registry, all existing extensions will remain as currently specified. The response selected here only applies to new extensions. This poll will close on Wednesday, 1200 UTC, 27 August 2025. Please select an option and indicate your choice on the list by replying to this message. Recall from the meeting that the Chairs proposed that option 1 was the best course of action. Thank you for your prompt attention, Jorge, Antoin, and Jim _______________________________________________ regext mailing list -- regext@ietf.org<mailto:regext@ietf.org> To unsubscribe send an email to regext-le...@ietf.org<mailto:regext-le...@ietf.org> _______________________________________________ regext mailing list -- regext@ietf.org<mailto:regext@ietf.org> To unsubscribe send an email to regext-le...@ietf.org<mailto:regext-le...@ietf.org>
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
