Hi Hisham! Thanks for sharing. Being one of the old dogs in this particular corner of the DNS cube*, I've seen e164.arpa come, rise, and fall. Netnod still operates secondary service for the Swedish national prefix 6.4.e164.arpa, but it seems(!) like there have been no changes to the zone for the past 5 years. Precious little underneath actually works - if anything ... I don't have a strong opinion about whether or how this service should be operated, but FWIW I do have one strong opinion about process: if the ultimate decision is to dismantle the operation of e164.arpa entirely (and I can live with that), then please make sure you don't close it down in such a way that it's impossible to put service back in the future, if someone finds new and brilliant use for it. You don't have to keep and maintain the infrastructure, but don't put in anything that _prevents_ re-building new infrastructure for it in the future. One such bad example could be to re-use e164.arpa for some other purpose. Just say "it's time", take down the scaffolding, and leave the stage. Cheers, /Liman * Some might argue that I'm an old dog in _any_ of the corners of the DNS cube. They wouldn't be wrong ... ;-) #---------------------------------------------------------------------- # Lars-Johan Liman, M.Sc. ! E-mail: liman@netnod.se # Senior Systems Specialist ! Tel: +46 8 - 562 860 12 # Netnod AB, Stockholm ! https://www.netnod.se/ #---------------------------------------------------------------------- HMI@ripe.net 2026-02-17 18:12 [+0400]:

Dear colleagues,

This message summarises recent discussion regarding ENUM (e164.arpa) and clarifies the scope and next steps.

The RIPE NCC has operated the e164.arpa registry for many years under instructions and coordination arrangements established with the ITU-T and IAB. These arrangements, and the operational context for how the registry is run, are described here: https://www.ripe.net/manage-ips-and-asns/dns/enum/iab-instructions/

Recently, a request was raised in the RIPE Database Working Group to support ENUM (e164.arpa) in RDAP for querying the RIPE Database. We noted that RDAP support for ENUM is not currently implemented, but could be added if there is clear interest. We also checked current query patterns and found a few hundred ENUM-related queries per day in DNS and in Database; so low usage, but not zero.

Following discussion on the Database WG mailing list, including replies in support, we proposed implementing RDAP support for ENUM. While this is a limited operational change, it was recognised that anything touching E.164 and e164.arpa can raise political questions that go beyond the purely technical.

As e164.arpa is directly linked to the ITU E.164 numbering system, the relevant points of contact are typically national administrations and the entities they designate. This led us to consult ITU-T Study Group 2 to clarify the status of ENUM and its usage and needs for ongoing support. ITU-T will ask member states for their feedback and share this with us.

ITU-T provides an established and coordinated channel to reach those administrations, and importantly confirm whether any delegating authorities still rely on the service, so our technical decisions are informed by real-world use and help us avoid unnecessary operational risk, confusion, or compliance headaches (including in the context of regulatory frameworks such as NIS2).

We are also reaching out to the IAB regarding these operations, which the RIPE NCC performs under its instruction on behalf of the global DNS and Internet community.

I am sharing this message with the DNS, Database, Cooperation and RIPE NCC Services Working Group mailing lists to ensure all relevant working groups are informed. If you wish to share thoughts in response, please reply to the thread on the RIPE NCC Services WG mailing list.

Best regards, Hisham Ibrahim Chief Community Officer, RIPE NCC