On 5 Aug 2025, at 12:00, Edward Shryane wrote: > The DB team will proceed with implementing the e164.arpa zone in RDAP and we > will document in an RFC.
Thanks, Ed. I would like the WG to be aware that this will likely need some "pre-preparation", before an ID appears, so that stakeholders, who may not be aware of this WG, can be engaged appropriately. These include the IAB, SG2 of the ITU-T (who are parties to a formal liaison about this zone), and the operators of the registries for the daughter zones delegated from e164.arpa. Early engagement may help avoid either unwelcome surprises to, or unexpected consequences for, any of these organizations, as well as (potentially significant) diplomatic work needed to address any misunderstandings which may otherwise arise. I encourage any of these stakeholders who are actually present on this list to engage as soon as they can, which may be on their return from vacation. Following the multi-stakeholder model properly can be hard. Thanks for taking note of these concerns. Best regards, Niall O'Reilly RIPE Vice-Chair ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
