Summary

  • A RIPE NCC draft circulated on 17 August says the registry supports continued Public ENUM under e164.arpa and is not proposing closure. It clarifies and supersedes the relevant parts of its February submission, SG2-C-0196.
  • The registry's review found 23 of 46 delegations without a top-level DNS issue, 17 apparently non-operational and six with partial issues. The new draft treats the latter 23 as maintenance and data-accuracy cases, not a vote on the whole system.
  • RIPE NCC asks ITU-T Study Group 2 to confirm revised interim procedures in September. The draft remains open for comment until 25 August; neither the procedures nor any individual removal reported here has taken effect.

One technical inventory had been asked to answer two different questions

Public ENUM is a bridge between telephone numbering and DNS. ITU's description says it places E.164 country codes into the Domain Name System. RFC 6116 specifies how an E.164 number is converted into a DNS name and how records may return communication identifiers.

The bridge has several stewards. The IAB has responsibility for the arpa infrastructure and designated RIPE NCC to operate e164.arpa; ITU-T coordinates the E.164 country-code side; national authorities and their operators maintain delegations. RFC 3245 records the cooperative design. No one observation automatically carries all of those roles.

RIPE NCC's February contribution did not keep the questions sufficiently apart. It grew out of a practical issue—whether ENUM domain objects should be available through RDAP—but also raised the future status of ENUM and e164.arpa. The 17 August draft says those broader questions did not accurately reflect the established division of responsibility. It therefore clarifies and supersedes the relevant parts of SG2-C-0196.

The corrected sentence is direct: RIPE NCC supports continued Public ENUM and is not proposing its closure. The registry is no longer asking SG2 to determine ENUM's technical or architectural future. It is asking SG2 to give individual delegation problems a usable procedure.

Twenty-three problem records do not make one system verdict

The numerical finding remains serious. RIPE NCC reviewed 46 current delegations. Twenty-three showed no DNS issue at the top delegation level. Seventeen appeared non-operational. Six showed partial DNS issues. Half of the inventory therefore had some observed fault at that layer.

But a DNS check answers a bounded question: did the delegation respond as expected at the observation time? It does not, by itself, reveal why. An operator may have abandoned service, misconfigured authoritative servers, entered a migration, lost contact with a national authority or retained a deliberate but little-used delegation. A top-level check also does not count users, failed calls, dependent applications or demand for restoration.

The draft uses that limit correctly. It calls the findings a registry-maintenance and data-accuracy issue and says they are insufficient for a system-wide conclusion. Each troubled delegation becomes a candidate case. The functioning half is not made collateral evidence for closure.

This is the central news. RIPE NCC did not make the faults disappear. It changed the unit of decision from one architecture to one delegation at a time.

September is about putting a procedure into force

The February SG2 meeting record says revised ENUM interim procedures in TD423 Rev.1/PLEN were approved to come into force at the next meeting, scheduled for 9–18 September, pending conclusions drawn from responses to TSB Circular 123.

Circular 123 asked Member States about possible closure of E.164 country-code delegations in e164.arpa. The related incoming liaison recorded a 15 August response deadline. RIPE NCC's new draft says those answers can inform the status and intentions of individual national delegations, but should not be aggregated into an architectural verdict.

Its request to SG2 has two parts. First, confirm that the revised procedures take effect at the September meeting and cover individual non-operational or expired temporary delegations. Second, keep broader technical or long-term questions in coordination with the IAB, RIPE NCC, relevant IETF processes and affected parties.

If confirmed, RIPE NCC says it will refresh its technical assessment, engage delegation operators where possible and send substantiated cases to the Telecommunication Standardization Bureau. The sequence matters: observe again, seek an explanation or repair, then present a case. A stale snapshot should not become an automatic deletion instruction.

The IAB response supplied the missing boundary

The IAB's June liaison did not deny that Member State feedback could provide useful operational information. It said that such a consultation could not, by itself, determine the disposition of e164.arpa or the status of ENUM. Any move to make RFC 6116 Historic belongs in the IETF's open standards process; retirement of the namespace would require coordination among the relevant technical and operational bodies.

That is more than an institutional objection. It is a test of evidence. A country can say whether it still wants a delegation. A DNS operator can show whether nameservers answer. RIPE NCC can maintain the zone and document technical results. SG2 and TSB can administer E.164 coordination. The IETF can decide a standards-track protocol's status. One body's evidence may inform the others without substituting for their decisions.

The 17 August draft now follows that map. It preserves SG2's role in case procedures while declining to ask SG2 alone for an Internet-architecture judgment. It preserves RIPE NCC's operating role without treating operation as ownership of the namespace.

An independent RIPE NCC explainer includes ENUM coordination among the registry's services. Lu Heng's Policy Mirror supplies the sharper principle: a registry gains trust by keeping a bounded ledger accurate, not by enlarging a maintenance observation into authority over the surrounding system. ENUM makes that boundary visible because telephone numbering, DNS operation and Internet standards meet in one tree.

RDAP is no longer being used as a proxy for survival

The draft also separates RDAP support from continued Public ENUM operation. That is an important housekeeping choice. Whether a modern registration-data protocol should expose ENUM objects is an implementation and community-priority question. Whether e164.arpa should exist is an architectural and operational question. Low query volume or a missing RDAP feature may inform investment, but neither proves that a namespace should close.

The same discipline should apply to the 46-delegation inventory. An accurate registry should not preserve obviously broken state indefinitely. Nor should a cleanup tool be made to carry a conclusion it cannot prove. The answer is a transparent case record: observation time, tested servers, failure reason, contact attempt, operator or national-authority response, proposed action and restoration route.

Temporary or withdrawn delegations need a reversible path because national intent and technical service can change. Functioning delegations need protection from a batch conclusion. Users need enough published reasoning to distinguish maintenance from policy.

The correction is real, but it is still a draft

Comments are requested by 25 August. SG2 has not yet confirmed the procedures, RIPE NCC has not yet submitted the final liaison statement described by the draft, and this article reports no completed delegation removal. The count is an assessment, not a sentence.

Those limits do not make the change cosmetic. The previous framing allowed one weak-service inventory to carry a question about the whole namespace. The new framing says that 23 troubled delegations deserve 23 substantiated decisions, while ENUM's future requires a separate record and wider agreement.

September can now produce something practical: a method for repairing, withdrawing and restoring individual delegations. If a system-wide proposal returns later, it should arrive under its own name, with evidence about use, dependency, transition and protocol status. A registry check can start that conversation. It cannot finish it.

Sources