RFC 3761 defines ENUM — a system for mapping plain old telephone numbers into the DNS, so that dialing +1-202-555-0100 could resolve to a SIP address, an email, a fax gateway, or any other URI. It's one of the most ambitious — and politically fraught — bridges ever built between two namespaces that grew up in completely different worlds: the ITU-T's E.164 numbering plan and the IETF's DNS.

The problem. By the early 2000s, VoIP was real. SIP could route calls over IP, but how do you find a user's SIP URI when all you have is their phone number printed on a business card? Operators had proprietary databases. Federation between carriers was nonexistent. The IETF's answer: stuff phone numbers into the DNS and let everyone query the world's largest distributed database.

The mechanism. Take a fully-qualified E.164 number like +442079460148. Strip the +, reverse the digits, separate with dots, and append .e164.arpa:

• 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa

Why reversed? So the DNS hierarchy matches the phone-number hierarchy: country code closest to the root, subscriber digits deepest. Now query that name for NAPTR records — the Naming Authority Pointer record type from the DDDS framework (RFC 3403). NAPTRs return a regular expression that rewrites the input into a URI, plus a service tag like E2U+sip or E2U+mailto, plus a priority. A single number can advertise multiple endpoints: try SIP first, fall back to PSTN, fall back to email.

Why DDDS? Faltstrom and Mealling didn't invent NAPTRs for ENUM — they reused the Dynamic Delegation Discovery System, a generalized rewriting framework. ENUM is technically just one DDDS application; the URN resolution system is another. This is classic IETF layering: don't bake telephony assumptions into the record type itself.

The politics. This is where ENUM gets interesting. Who controls e164.arpa? The ITU-T, which represents national governments, wanted authority over country-code delegations. The IETF runs .arpa. The compromise: each country code delegated only with consent of the relevant national regulator. Result — uneven, glacial deployment. Austria, the Netherlands, and a handful of others ran public ENUM tiers. The US essentially never did. By 2010 the dream of a universal public ENUM tree was effectively dead.

What survived. ENUM didn't die — it went private. Infrastructure ENUM and carrier ENUM (RFCs 5067, 6116) use the exact same NAPTR mechanism inside carrier networks and interconnect federations. Every time a SIP trunk provider routes a call, there's a good chance an internal ENUM-style lookup is happening. The technology won; the public namespace lost.

Modern relevance. If you've ever debugged a SIP routing problem and stared at a NAPTR record, you've touched ENUM. Microsoft Teams, Zoom Phone, Twilio, and basically every CPaaS routes calls through private ENUM-like databases. The pattern — reverse the identifier, encode as DNS labels, return rewrite rules — also shows up in reverse DNS for IP addresses (in-addr.arpa) and was the inspiration for several later directory schemes.

ENUM is also a cautionary tale about cross-SDO protocols: the technology was elegant, the governance question was unsolvable, and the deployment reflected the governance, not the engineering.