Slashdot Mirror


US Government Withdraws IANA Contract From ICANN

mbone writes "The 'no cost' contract between the U.S. Department of Commerce and ICANN over hosting the Internet Assigned Names and Number Authority (IANA) was supposed to be re-let this March. Now, it has been withdrawn, and the National Telecommunications and Information Administration (NTIA) says that 'we are cancelling this RFP because we received no proposals that met the requirements requested by the global community.' This is a pretty stunning vote of no confidence in ICANN by the U.S. government, on the eve of the 43rd ICANN meeting in Costa Rica. Speculation is that this is related to the attempts of the ITU-T to take over Internet governance, but it also could be over the new global top level domains. I am sure we will be hearing a lot more about this in the weeks to come."

3 of 140 comments (clear)

  1. ICANN's corruption finally has consequences by Arrogant-Bastard · · Score: 5, Interesting

    ICANN has been rolling out TLDs in order to profit its core constituency: the registrars.

    Nobody needed .xxx -- except the registrar who pushed it and is now using extortion tactics to pressure people into buying domains in it, e.g. "get yours...before someone else does".

    Nobody needed .info -- what, domains in other TLDs don't contain "information"? (Well...alright...spammers needed it, and quickly overran it. It's been a best practice in anti-spam engineering to block *.info and whitelist what you need for many years.) But registrars stood to profit, especially from the spammers buying domains by the thousands, so it was created.

    Nobody needed .biz -- because we already had .com. But it was a chance to sell the same thing twice, always a great business opportunity for registrars, so ICANN made it happen.

    And nobody needs hundreds of additional TLDs, either. There is no clamor of voices among the billion people on the Internet for .pepsi or .google or .dell.

    It's not an exaggeration to say that the majority of domains in existence today are used for abusive purposes: spam, phishing, typosquatting, search engine manipulation, etc. Yet ICANN wants to do whatever it can to explode the number, to keep the cash registers ringing at the registrars.

    What ICANN could be doing -- but isn't -- is to reign in the epidemic abuses. There are registrars that are owned by known spammers, for example. Another thing it could be tackling are domain confiscations (by the USG) without due process: ICANN can and should push back hard against that. But none of this will happen: ICANN is corrupt to the bone, a textbook example of regulatory capture, therefore it will do whatever maximizes the profits of its masters.

  2. Re:Misleading Headline by game+kid · · Score: 4, Interesting

    provisions reflecting heightened respect for local country laws

    This is the scary part for me, at least to the extent that it takes the sort of country-specific blocking that Twitter and Blogger are doing, and the sort of The Pirate Bay blocking that countries are doing, and bakes them into the requirements of doing any sort of business with a domain name on the internet.

    Otherwise, yeah, seems reasonable.

    --
    You can hold down the "B" button for continuous firing.
  3. Re:How is US govt controlling IANA? by mbone · · Score: 4, Interesting

    So the thing that surprises me is - how does the US government get involved in IANA and various TLDs? The only TLD they should be bothered about is .us. I guess one could make an argument for .com, .org, .net and others, but there too, they are assigned to non-US organizations as well. While the US may have 'invented the internet', its management as a worldwide resource has to be free of any country's government, even if the bulk of that organization's activities happen within that country.

    Which is why it puzzles me that the government should be in any way involved in the relationship b/w ICANN and IANA.

    It has always been involved, and there has always been this connection. IANA was set up by Jon Postel under a US Government contract and transferred to ICANN under a US Government contract (the one with the canceled RFP, to be specific).