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)


     
    This discussion has been archived. No new comments can be posted.
    Commerce to Re-Award IANA to ICANN Without Considering Alternatives | Log in/Create an Account | Top | 4 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.
    From the IETF...
    by Anonymous on Tuesday March 18 2003, @10:25PM (#11340)
    Dateline: San Francisco

    At the IETF meeting here in San Francisco not a soul can be found who believes that ICANN is competent to perform any of the technical functions of IANA.

    There is a universal consensus here at the IETF meeting that the IANA functions should be stripped from ICANN as the result of repeatedly demonstrated incompetence.

    I wonder what claims of competence were included in ICANN's bid to NTIA, or rather NOAA? Are there any reporters out there willing to pursue a FOIA request to take a look at what ICANN submitted?

    And come to think of it - NOAA?!! Pushing the IANA contract through the National Oceanic and Atmospheric Administration does have a strong and foul stench of laundering.
    [ Reply to This | Parent ]
      Re:From the IETF...
      by phoffman@proper.com on Wednesday March 19 2003, @12:55PM (#11342)
      User #2063 Info
      Sorry, but this is utter garbage. "Anonymous" is speaking about something that never happened. I am posting from IETF meeting (and I'm putting my name on this post...).

      - The IANA discussion is going to happen about 18 hours after I post this... Saying that there was "universal consensus" when the discussion is in the future is an interesting trick.

      - In off-line talks, I know lots of active IETF folks who think ICANN is competent to perform IANA. Many of us would rather that ICANN wasn't doing it (for many reasons), but that is radically different than saying that they are not competent.

      - Fully agree about the NOAA stench. But that is unrelated to the preceding lies about the views on competence.
      [ Reply to This | Parent ]
      How much would it cost?
      by KarlAuerbach on Wednesday March 19 2003, @04:22PM (#11346)
      User #3243 Info | http://www.cavebear.com/
      "the IANA function" has several components. One part is the IP address allocation part, another is figuring out who gets TLD slots (with the particularly troublesome question of who gets to run ccTLDs.) The part that I suspect is most interesting to the IETF is the part of handling the assignment of various protocol numbers.

      I have not been able to get a clear feel about how much this costs ICANN to handle. The raw number of hours of labor might be interesting to know, particularly if the IETF were to consider having somebody other than ICANN do the work.

      From the IETF point of view I don't see that there has been any problem in assigning the various numbers - we can look at ICANN's status report to NTIA to get a listing of what was done. I have not heard anybody complaining about number clashes.

      The more interesting question for the IETF is whether it could get better number services from some other body or perhaps the IETF's own secretariat. However, the IETF is getting a good deal from ICANN - whatever the cost to ICANN, the cost to the IETF for protocol number assignments is zero. And given the IETF's prospective financial distress, ICANN certainly represents a bargain.

      As for the NOAA part - I'm sure that there must be some strange bureaucratic reason why it was issued by NOAA rather than NTIA. I wish somebody would explain why a zero-dollar purchase couldn't be handled by NTIA the same way it buys magazine subscriptions.
      [ Reply to This | Parent ]
        Re:How much would it cost?
        by Anonymous on Thursday March 20 2003, @10:39AM (#11352)
        The policy aspect (for instance the creation of new gTLDs, and "determining who gets to run CCTLDs" as you put it) is different from the operational requirement of running what is in essence a simple database. IE the question of who has the ability to modify the delegees database is different from who runs it, publishes it (i.e. constructs the root zone file), and processes policy-free changes (such as changing name-servers on ccTLDs). Plenty of people could do the latter efficiently. To date, ICANN has failed to do this cost effectively, as it has a lot of other expensive policy baggage which is not cost-ringfenced, and has confused the IANA function (operating of the database) with policy decisions (for instance by suggesting ccTLDs should have to allow ICANN to zone transfer in order to change a nameserver entry). ICANN has also failed to do the former (the policy side) essentially because it does not have widespread community support. It doesn't have (universal) industry support not least because of the former, and because the policy making process has hardly been effective to-date, and it doesn't have community support due to (a) lack of participation of an at-large community, and/or (b) lack of participation of governments. I write "and/or" as the debate as to whether governments are indeed the representatives of at-large internet users, or whether they require separate representation is interesting, but not germaine to the point I make. Lastly, ICANN's mechanisms for funding have always discouraged participation, and encouraged machiavellian politics - and not only on VRSNs part. ICANN appears to have finally realised this (at least to some extent) in respect of the ccTLDs (see latest budget published). The ccTLDs offered (see CENTR proposal) a long while ago to pay their share of funding an IANA database operation, and root-server operators costs, provided they were ringfenced, didn't come with strings attached about redelegation and binding policy (remember many ccTLDs have far more transparent policy forming procedures than ICANN), and some level of service was described. ICANN refused this offer. In consequence, they provided the service anyway (albeit badly), and didn't get any funding. This should surprise noone.
        [ 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