dns-wg

Download

dns-wg@ripe.net

April 2026

2 participants
2 discussions

Agenda DNS-WG at Ripe92
by Ulrich Wisser 25 Apr '26

25 Apr '26

Dear working group, The preliminary agenda for our meeting at Ripe92 in Edinburgh is ready. 1. Welcome and announcement of the new co-chair 2. DNS, Transitive Trust and How Many is Many, Ondřej Surý 3. Black Holes and Prisoners: Understanding AS112 Deployment Characteristics, Elizabeth Boswell 4. DNS TAPIR POP – Managing Multiple RPZ Inputs, Lars-Johan Liman 5. Overdoing NSEC3 Hurts, Petr Špaček 6. RIPE NCC DNS Update, Florian Obser 7. (Time Permitting) Measuring Resilience of Recursive Resolvers, Maynard Koch A friendly reminder: We are still collecting expressions of support (or opposition) for the new working group co-chair from the mailing list until Monday, 18th May 2026. See you all in Edinburgh or online! Your chairs (Yevheniya, Moritz and Ulrich)

1 0

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 5

Results per page: