Dear Hisham, dear colleagues,

Thank you for the continued transparency around this process, and for your 6 April update acknowledging that framing this discussion primarily in terms of closure is premature. We agree, and would like to contribute the perspective that has so far been missing from this thread: that of an active national delegating authority.

Internet Society Netherlands (ISOC NL) holds the delegation for 1.3.e164.arpa, covering the Dutch country code (+31), with SURF providing the technical infrastructure. The delegation is operationally sound, contact information is current, and DNSSEC is in place. We do not intend to request revocation.

More importantly, we are actively exploring forward-looking applications for the +31 delegation. The principle at the heart of ENUM, linking a regulated, government-authorised numbering resource to verifiable Internet identifiers through a standards-based, DNSSEC-signed framework, is gaining renewed relevance in the context of the IP interconnection transition, DNS-based identity verification, and European digital identity frameworks. We are engaged with national stakeholders, including the Dutch Ministry of Economic Affairs and Climate Policy (EZK), to assess how this infrastructure can meet these emerging needs.

We therefore support Marco Hogewoning's call for further study before any conclusions are reached and specifically echo his point that low query volume at the Tier-0 level is a poor proxy for actual reliance on the ENUM protocol and national delegations. The relevant signal is at the Tier-1 level and below, which is precisely where active national delegations like ours operate.

We look forward to the RIPE 92 session and would welcome the opportunity to contribute the Dutch delegating authority's perspective directly. We are also happy to coordinate with RIPE NCC and SURF on providing more granular usage data from 1.3.e164.arpa specifically, if that would support a more complete factual basis for this discussion.