Re: ENUM (e164.arpa): background, scope, and coordination steps
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
participants (1)
-
Hisham Ibrahim