Hi, I forgot to reply earlier but I mostly just want us to try to aim for feature parity with WHOIS. So I agree with with your decision :)
-Cynthia On Tue, 5 Aug 2025, 13:00 Edward Shryane, <[email protected]> wrote: > Dear colleagues, > > > On 4 Aug 2025, at 11:01, Edward Shryane <[email protected]> wrote: > > > > ... > > > > Is our time better spent in supporting e164.arpa in RDAP, or deprecating > e164.arpa? > > > > Thanks for raising this and for your feedback. > > The DB team will proceed with implementing the e164.arpa zone in RDAP and > we will document in an RFC. This will be a small extension to the existing > protocol. > > I don't foresee e164.arpa being deprecated, at least in the short term, > and we are aiming for feature parity with Whois. > > Regards > Ed Shryane > RIPE NCC > > ----- > 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/ >
----- 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/
