April 2026 - ncc-services-wg - mailman.ripe.net

ENUM (e164.arpa): background, scope, and coordination steps
by Hisham Ibrahim 08 Apr '26

08 Apr '26

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

3 4

Re: ENUM (e164.arpa): background, scope, and coordination steps
by Hisham Ibrahim 07 Apr '26

07 Apr '26

Hi Sergey, Thank you, that is a fair point. To provide some additional context now, the assessment I referred to was based on query data shared internally for 16 February 2026 from three RIPE NCC authoritative DNS servers for the e164.arpa zone, located in Amsterdam, Paris and Mangalore. On that day, the number of queries for e164.arpa seen on those servers was as follows: - Amsterdam: 61,981 queries out of 873,948,265 total queries (0.007%) - Paris: 15,584 queries out of 161,779,569 total queries (0.009%) - Mangalore: 953 queries out of 62,438,947 total queries (0.002%) It is also important to note that these figures include traffic generated by RIPE Atlas anchors for DNSMON monitoring, and in the case of Amsterdam also include a certain amount of clearly non-meaningful or “junk” traffic. In other words, the level of genuine query traffic appears to be lower still. That said, as I noted in my previous message, visible query volume to the public e164.arpa tree does not by itself provide a complete picture of possible reliance on ENUM-related mechanisms more broadly. This is one of the reasons we are trying to gather broader input before drawing conclusions. I will make sure that this context is also reflected in the RIPE 92 presentation. Best regards, Hisham

1 0

Extending API Keys
by Fallon Albrecht 01 Apr '26

01 Apr '26

Dear colleagues, We are extending the API key model introduced for the RIPE Database to the remaining API Keys in the LIR Portal, providing a more secure and flexible way to manage access across services. API keys for My resources and IP Analyser can now be created directly within the services where they are used, while centrally visible and manageable via RIPE NCC Access. You can read more about these changes and what they mean for you here: https://labs.ripe.net/author/fallon-albrecht/extending-api-keys-beyond-the-… Kind regards, Fallon Albrecht Manager Business Applications

1 0