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

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
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 DoC "opts in" to e164.arpa
    posted by tbyfield on Thursday February 13 2003, @09:57PM

    RFassett writes "In a letter from the NTIA to Ambassador David A. Gross, U.S. Coordinator for International Communications and Information Policy, Assistant Secretary of Commerce Nancy Victory has recommended for the United States to take initial steps toward "opting in" to e164.arpa.



    The DoC Feb 12 press release can be found here. The letter to Ambassador Gross can be found here.

    The short story to this is that Ms. Victory has formally expressed DoC's support for the ITU global efforts to coordinate the e164.arpa zone, one that is progressing consistent to RFC 2916. To quote, Ms. Victory "believes that the United States should seize this opportunity and take steps to participate in e164.arpa". Good news for the ITU.

    This press release comes on the heals of the recent announcement by DoC to extend IANA functions to ICANN (without competitive bid) for another 3 years because ICANN is the "only responsible entity that can continue to provide seamless performance of the IANA functions". Ok. But per RFC 3172, ICANN obtains its authority (via DoC) to administer the .arpa domain as an extension of its IANA functions.

    In the letter to Ambassador Gross, Ms. Victory states that "NTIA is committed to working diligently to resolve [ENUM] implementation issues with the FCC and the Department of State". Is this "commitment" merely a direct pass-off for the FCC and Department of State to go talk to the privatized ICANN? I mean, it's not like DoC can be confused for having a history of direct oversight or accountability of ICANN activities...more like pure delegation to the nth degree in the spirit of privatization for better or worse, including a "self-reform".

    Meanwhile, the ITU is on record as questioning the private status of ICANN given its beholding to a single goverment. But, given this "Victory" of achieving formal USG support for its RFC 2916 ENUM initiative and certainly one that is crucial, will the ITU question this extension of IANA functions (and .arpa administration) to ICANN by DoC? It seems difficult to reconcile this.

    We've seen this kind of language before from DoC such as "support competition", "promote innovation", "minimize regulation" and "preserve opportunity for alternative deployments" only to see these concepts delegated in totality to ICANN...ENUM is commonly referred to as the convergence of Telephony and Internet. For the US, it may well be titled "FCC meets ICANN". Should be interesting."

     
      ICANNWatch Login  
    Nickname:

    Password:

    [ 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  
  • IANA
  • ITU
  • IETF
  • ICANN
  • Nancy Victory
  • US Nat'l Telecom & Info Admin.
  • here
  • here
  • recent announcement
  • RFC 3172
  • confused
  • record
  • before
  • RFassett
  • More on ENUM
  • Also by tbyfield
  •  
    This discussion has been archived. No new comments can be posted.
    DoC "opts in" to e164.arpa | Log in/Create an Account | Top | 7 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    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.
    This story got it wrong
    by Mueller ({mueller} {at} {syr.edu}) on Friday February 14 2003, @12:29PM (#11157)
    User #2901 Info | http://istweb.syr.edu/~mueller/
    DoC is not in love with ITU. ITU would like a new TLD for ENUM. e164.arpa is controlled by RIPE-NCC and the IAB guys. ITU and the US-based telecom and internet interessts have been fighting about this for months. Victory is (surprise!) expressing support for the U.S.-based telecom industry-IAB/Internet community root for ENUM and dashing hopes for an ITU root, as well as, of course, dashing cold water on free market advocates for competing roots.
    [ Reply to This | Parent ]
    what "unregulated" internet?
    by joppenheimer on Wednesday February 19 2003, @12:23PM (#11194)
    User #5 Info | http://JudithOppenheimer.com
    I am an ENUM Forum founding member, and it is simply not as squeaky clean as the individual pieces, looked at separately, might appear.

    To begin with, I'm tired of these VoIP aka ENUM "we are the world" articles springing up everywhere claiming that they are saving entrepreneurs and consumers from PSTN regulatory stranglehold because "the internet isn't regulated."

    That's why this story is exactly where it belongs - here on ICANNWatch, because we know better.

    ENUM people have apoplexy every time the word ICANN comes up at a meeting because they have to keep up this premise of no regulatory body on the internet - they have to make these VoIP boys BELIEVE, or they won't help bring telecom over to the Promised Land.

    How long will it take for "ICANN [to] become an unaccountable regulatory body that controls prices, services, and business practices" [icbtollfree.com] over VoIP companies too?

    Whether ICANN or whomever DoC anoints and appoints, we know the internet is regulated, so if everything's on the up-and-up, why the face-to-face lies and PR subterfuge campaign?

    Splain me that, Lucy.

    [ Reply to This | Parent ]


    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