Inside ICANNWatch  
Submit Story
Lost Password
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)

    ENUM & VOIP ENUM: The Collision Of Telephony And DNS Policy
    posted by michael on Tuesday January 15 2002, @02:57PM

    Anonymous writes "Robert Cannon, of the Washington Internet Project, has written a very useful paper on ENUM, available at ssrn.com, noting that "ENUM creates multiple policy problems." Here's the abstract:"

    ENUM marks either the convergence or collision of the public telephone network with the Internet. ENUM is an innovation in the domain name system (DNS). It starts with numerical domain names that are used to query DNS name servers. The servers respond with address information found in DNS records. This can be telephone numbers, email addresses, fax numbers, SIP addresses, or other information. The concept is to use a single number in order to obtain a plethora of contact information. By convention, the Internet Engineering Task Force (IETF) ENUM Working Group determined that an ENUM number would be the same numerical string as a telephone number. In addition, the assignee of an ENUM number would be the assignee of that telephone number. But ENUM could work with any numerical string or, in fact, any domain name. The IETF is already working on using E.212 numbers with ENUM.

    ENUM creates multiple policy problems. What impact does ENUM have upon the public telephone network and the telephone numbering resource? For example, does this create a solution or a problem for number portability? If ENUM truly is a DNS innovation, how does it square with the classic difficulties experienced with DNS and ICANN? Is ENUM, while presenting a convergence solution, also encumbered with the policy problems of both the DNS and telephony worlds?

    IETF ENUM proponents suggest that ENUM needs a single unified database administered through national and international government sanctioned monopolies. The IETF took the unusual step of requesting that the International Telecommunications Union (ITU) regulate an aspect of the Internet, that is, participate and have authority over the international ENUM service provider. But this notion of establishing a new communications monopoly collides with the deregulatory efforts of the Telecommunications Act of 1996, the attempts to privatize DNS through ICANN, and US policy that the Internet should be left unregulated. ENUM is an unproven innovation with no evidence of commercial viability. It faces a strongly competitive market of other directory assistance innovations and services. Proponents are asking governments to sanction one competitor over others.

    ENUM offers two lessons. First, involving the government in a standards process is fraught with problems and delays. It starts with the cliche of having too many cooks in the kitchen, producing a mediocre cake at best. And it ends with a cumbersome bureaucratic process resulting in fatal delay and ultimately collapsing in upon itself. Similar efforts in the past rose to grandiose levels and failed. These include X.500 and OSI.

    Second, a number by any other name remains a number. A significant portion of the DNS wars has been focused on resolving who has the right to a name. Is it first come, first serve, a trademark holder, someone using the domain name pursuant to free speech rights, or perhaps some other right? With ENUM, the question presented is who has the right to a numerical string. ENUM attempts to resolve this question by convention, concluding that the assignee of a telephone number has rights to an ENUM number. But an ENUM number is not a telephone number. A telephone number is an address used on a telephone network to reach a telephone. An ENUM number is a token used to access a database. Transferring a numerical string from one context to another does not likewise transfer the rules and regulations of the original context. Rules and regulations created for telephone numbers assume a particular purpose in a particular context; they do not apply to numerical strings in a foreign context with a different purpose. It is illogical and dangerous to transfer the policy concerning one type of number to a different type of number. This means, among other things, that the regulatory authority over telephone numbers has no more jurisdiction over ENUM numbers then when telephone numbers are used to rent videos or access savings clubs at the grocery store.

    US policy has been to keep information technology unregulated to permit it to innovate at the speed of the market and not at the pace of bureaucracy. Yet ENUM proponents beg for government entanglement. It would be unprecedented for the government to sanction a monopoly for something as unproven as ENUM where the appropriateness of a government monopoly has not been demonstrated. Were such government involvement in fact approved, the delay experienced would likely be fatal to the innovation.

    There are those who are strong advocates of an ENUM unified database. An ENUM unified database can likely be achieved by private industry through some level of a joint venture devoid of government entanglement. This is the best hope for ENUM achieving the goal of a swift implementation.

      ICANNWatch Login  


    [ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]

      Related Links  
  • ssrn.com
    This discussion has been archived. No new comments can be posted.
    ENUM: The Collision Of Telephony And DNS Policy | Log in/Create an Account | Top | 1 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • 1 reply beneath your current threshold.

  • Search ICANNWatch.org:

    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com