ENUM (continued)

In March 2011, RFC 6116: The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) obsoleted RFC361.

For details of Dial Sequences and Global Switched Telephone Network (GSTN) see RFC 3601. {Dial Sequences include pauses and other signaling in addition to the phone number}

Note that ENUM maintains the nation-state “ownership” of E.164 numbers. Note there are discussions about adding virtual E.164 numbers, see [Mészáros 2012].

Slide Notes

S. Bradner, L. Conroy, and K. Fujiwara, ‘The164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)’, Internet Request for Comments, RFC 6116 (Proposed Standard), Mar. 2011. Available: http://www.rfc-editor.org/rfc/rfc6116.txt Links to an external site.

C. Allocchio, “Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / 164 Addresses”, RFC 3601, September 2003.

Mihály Mészáros, NRENum.net (update): new developments and service update, RIPE65 - ENUM WG, Budapest, Hungary, 27 Sep 2012, https://ripe65.ripe.net/presentations/263-ripe65.pdf

Transcript

[slide219] Now, the first problem that occurs with ENUM is the fact that to get a phone number, what do you have to be? What's the first thing we said there? It's a country code. Right? So the ITU issued the initial numbers to countries. The blocks of addresses under that were issued by who? The authority in that country who handed out phone numbers. That means if you weren't a telephone operator, you couldn't have a phone number. And if you weren't associated with the country, there was no one to get an allocation from. So this was tied and worked well whenever you had the fixed telephony system typically run by national operators. It started to hit some problems.