Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
The Internet Technology Politics

ICANN Might Pre-Register gTLDs To Placate Critics 70

Posted by kdawson
from the i-think-i-can dept.
judgecorp writes "ICANN is to be congratulated for succeeding in expanding the Internet beyond the Latin alphabet. However, the organization is facing a harder task in extending the Internet's global top-level domains (gTLDs) — its proposal to open up the gTLD space has been plagued by controversy and delays. INCANN faces struggles with trademark owners and competing businesses — but even so it is being criticized for acting slowly (as seen in transcripts from the recent meeting in Seoul). It now seems likely the body will have a pre-registration scheme to gauge demand and placate critics by getting something moving on new gTLDs."
This discussion has been archived. No new comments can be posted.

ICANN Might Pre-Register gTLDs To Placate Critics

Comments Filter:
  • So (Score:2, Interesting)

    by sopssa (1498795) *

    When will Slashdot move under .slashdot?

    • Re:So (Score:5, Interesting)

      by sopssa (1498795) * <sopssa@email.com> on Saturday October 31, 2009 @04:01PM (#29937039) Journal

      For that matter, Slashdot isn't really an organization, so why is it under .org?

      • by Anonymous Coward

        It isn't a .com(pany) either. It has nothing to do with .net(work related services).

        Technically it should be slashdot.info but really, who cares? The gTLDs have lost their meaning and that is a good thing - it is impossible to moderate them well so it is better if people don't assume they should be given any attention.

        • Re: (Score:3, Interesting)

          That argument is pretty weak, is it better to remove all trafic lights so people don't assume it's safe to cross a junction?

          ICANN has fucked up gTLDs and everything they do seams to make it worse, now im not saying they should go around taking domains back, but if they made sure decent rules were in place then a domain name might actually mean something.

        • Re: (Score:3, Insightful)

          .com stands for commercial and Slashdot is in fact a commercial site.
        • Re: (Score:3, Insightful)

          by cenc (1310167)

          Traded on the stock exchange under LNUX ticker symbol. How is it not a company?

      • by rs79 (71822)

        " For that matter, Slashdot isn't really an organization, so why is it under .org?" .org isn't really for organizations. it's a catch-all. The way the rfc is worded, com is for commercial organisations, net is for network infrastructure org is for things that don't fit any of these. It's just shorter than ".other".

        • Re: (Score:3, Informative)

          by jonwil (467024)

          except that .net has been used for so many things totally unrelated to network infrastructure (I myself have a .net and its just a small personal site)

    • Re: (Score:1, Interesting)

      by Anonymous Coward

      Remember that a fully qualified domain name ends in another dot, so it would really be "slashdot.slashdot." or you could go with "slashdot.slash." or "slash.slash."

      • Re: (Score:2, Redundant)

        by Ihmhi (1206036)

        H T T P Colon Slash Slash Slash Dot Dot Slash Dot.

        Sounds like morse code. @_@

        • Re: (Score:3, Insightful)

          by Jeremy Erwin (2054)

          I'm just surprised that colon.slashdot.org isn't being used. "idle" could have used that name,

          • by Ihmhi (1206036)

            Well considering what comes out of one's colon, that would certainly be a more appropriate subdomain for idle.

    • The ./. tld? I think I like it.
    • Re:So (Score:4, Funny)

      by Looce (1062620) * on Saturday October 31, 2009 @04:09PM (#29937093) Journal

      Forget about .slashdot, .dot is where the real fun is!

      "Ok, so the address is slashdot.dot - I'll spell it out for you. (attempting to add emphasis) It's http colon slash slash slashdot dot dot.
      - Dot dot dot... So an ellipsis? How do I type those on a computer?
      - No, I mean slashdot, as in S-L-A-S-H-D-O-T, then a dot, then dot spelled out.
      - Oh! Ok, thanks!"

    • by rs79 (71822)

      " When will Slashdot move under .slashdot?"

      http://slash.dot/ [slash.dot] has worked for a decade for those in the know.

      Christian Neilson on the BOFH-net list suggested it and set it up.

  • by Hognoxious (631665) on Saturday October 31, 2009 @04:17PM (#29937129) Homepage Journal

    "ICANN is to be congratulated for succeeding in expanding the Internet beyond the Latin alphabet.

    No it isn't.

    If you think phishing and typosquatting are bad now, think of how bad it will be when people see a link that looks like logon.[pictogram of a cat sitting on a stool].bank and it redirects to logon.[pictogram of a cat sitting on a stool with its tail curled a little bit at the end].bank that's owned by Lavaturian gangsters.

    • Plato was Greek, you insensitive clod!
    • I see it this way:

      Plato: BeOS - Like, very deep, man. Thoughtful.

      Shakespeare: Mac OS X - He was fashionable . . . big collars and all. And he just wanted to write, and did not want to be bothered with technical details.

      Jesus: Let's see - The Emperor of Rome, Tiberius (Bill Gates) controlled the known world at that time. Some yokel from some hick province starts a movement that challenges the monopoly, by preaching an alternative. Tiberius hires a hatchet man, Pontius Pilate (Daryl McBride), to "take

    • by Miamicanes (730264) on Saturday October 31, 2009 @08:37PM (#29938543)

      > "ICANN is to be congratulated for succeeding in expanding the Internet beyond the Latin alphabet.

      The problem isn't that ICANN expanded "the Internet" beyond the Latin Alphabet (or at least the subset enshrined in ASCII's alphanumeric characters plus hyphen)... the problem is the collateral damage it caused, and continues to cause, because they did the equivalent of dumping a freeway interchange in the middle of an already-thriving residential neighborhood.

      ICANN (possibly with IETF) needs to do three things:

      1) Work with IETF to extend DNS so that TLD registrars can define a specific subset of UTF-8 that's valid for its subdomains. By definition, .com/.net/.org should be forever restricted to the historical [A-Za-z0-9\-] subset to put an end to homograph phishing. In other words, no TLD could indiscriminately include everything from legacy-ASCII to Klingon, Runes, and ancient Egyptian. They'd have to pick the characters used to write a single real language and stick with it.

      2) Require that TLD character-validity rules be fully normalized against characters between 0x30 and 0x7f. In other words, if there's a letter in the language's unicode codepage that looks just like ASCII 'i', they can allow ASCII 'i', or the language's own version of 'i' with its own UTF-8 value, but NOT both. The choice of which 'a-zA-Z' to use would largely depend upon which value gets generated from a keypress by a keyboard in the target country.

      3) Create new TLDs for writing systems used in more than one country, by at least 50 million people... preferably, short and understandable to anyone in a country that uses that writing system. So, Chinese might get .{zhong} or .{zhongwen} (but the PRC itself's country TLD might be .{zhongguo}), Cyrillic might sensibly get the characters that resemble .NHT (backwards 'N') which apparently is the abbreviation for "Int" in Russian, Ukranian, Serbian, and probably most other languages using Cyrillic, etc, and conveniently looks vaguely like ".NET" to everyone else (but the backwards-N would ensure only a complete idiot could think it really WAS .net). Ditto for Arabic. Languages almost synonymous with a single country (Hebrew, Greek, Japanese, Korean, etc) or spoken by fewer than 50 million real people in daily business wouldn't get their own TLDs... but their countries would get a new country TLD in the writing system (along with their old 2-letter TLD).

      The point is, the way internationalization has been rolled out so far has created a worldwide party for fraud and phishing via homograph attacks. An end needs to be put to it NOW. If someone has an existing IDNS name that would be invalidated by the new rules (say, {nurren}.com), they'd get first chance at it in the new .{zhong} TLD (nurren}.{zhong}). If there were two or more existing .com|.net|.org domains that clashed (say, {nurren}.com and {nurren}.net), they'd have to share the TLD and settle for distinct subdomains of it, like {something}.{nurren}.{zhong} and {somethingdifferent}.{nurren}.{zhong}.

  • Wow (Score:1, Funny)

    by Anonymous Coward

    How many translations of "goat.se" are there?

  • by karl.auerbach (157250) on Saturday October 31, 2009 @05:07PM (#29937391) Homepage

    There are 40 applicants who paid ICANN $50,000 each in year 2000 who ICANN has strung along all these years, neither granting nor denying. These include IOD's application for .web.

    ICANN needs to deal with this leftover business from 9 years ago.

    • by rs79 (71822)

      Thank you for bringing this up Karl; right now there's a certain Euphoria about IDN's and tons of people who didn't do any work on them are patting themselves on the back: it's newsworthy; people come up to me on the street and tell me the news.

      And per AVC's suggestion they think maybe they can get started on new "g"tld apps, another source of institutional euphoria. I suggested long ago to him to organize a tld-apps "union".

      I'm not sure anything short of a lawsuit would awaken the memory of the ICANN 2000

    • by rs79 (71822)

      RT @Techno_Cat http://is.gd/4JAAj [is.gd] "There are 40 applicants who paid
      #ICANN $50,000 each" Mike Roberts said there were applicants the U.S. Government denied.

    • by elronxenu (117773)

      Deny them all and problem solved!

      Who will rid me of this troublesome gTLD madness?

  • by MoralHazard (447833) on Saturday October 31, 2009 @05:29PM (#29937509)

    Any existing 2nd-level domain registrant automatically gets assigned a new TLD equivalent to the current 2nd-level name minus the TLD suffix. Collision priority scheme is .edu, then .com, then .org and .net, then .gov, and finally .mil. Ignores ccTLDs.

    First, take care of the .edu sites: Automatically register a new TLD for each registered .edu name, such the that new TLD is the 2nd-level part of the existing .edu name. For example, Harvard U. currently owns 'harvard.edu.', so they would automatically receive the new 'harvard.' TLD.

    Second, it seems reasonable to assume that the .com names have higher visibility than the .net/.org names, but not quite as over-riding as the grant to the existing .edu holders. Autoregister the new TLD and give it to the .com holder, but allow a weighted bidding process if the current .net or .org holder wants to try to buy the rights: During some designated 6-month period before open TLD registration starts, the .org/.net holder puts a bid of X dolllars in trust, and the .com holder has 60 days to match 20% of X (single-round bid, weighted at 0.2). That weighting is pretty arbitrary--it doesn't really matter what the actual weight is.

    Third, whatever's left in the TLD space gets assigned to .gov and .mil names, on the same basis as .edu.

    It's not perfect--it totally ignores ccTLDs, and the weighting is arbitrary, and who am I to say that a .com name is more of a claim on the new TLD than a .net/.org name?

    But do you think an unqualified, disorganized "land rush" would be somehow better? At least this way, you're limiting the number of trademark/squatting cases that have to be litigated.

    • by Rich0 (548339)

      I don't get the point of having a new gTLD if it just ends up being a perfect replica of existing TLDs. Why do we need harvard.cool when we already have harvard.edu?

      If anything there should be an outright ban on owning the same name in more than one TLD.

      It just seems like another way to get everybody with a domain name to fork over a chunk of change to get another one.

    • by rs79 (71822)

      "Any existing 2nd-level domain registrant automatically gets assigned a new TLD equivalent to the current 2nd-level name minus the TLD suffix. Collision priority scheme is .edu, then .com, then .org and .net, then .gov, and finally .mil. Ignores ccTLDs."

      The "move the dot to the left one" argument came up in 1997. I liked it. Course, I suggested it.

      Having to pick a "winner" from com/net/org/edu etc means win-lose. Much better I think would be for them to run it in a cooperative manner. Recall that original

    • And what if Harvard is a legally registered trademark in a foreign country, not owned by Harvard University? Shouldn't the TLD in that foreign language go to the trademark owner of the country that natively speaks the foreign language?
    • by zoloto (586738)
      Then why bother having different TLD's? If Harvard has the .edu and other FQDNs, why do we even bother having multiple? It's not like slashdot.edu matters because that school of thought is at the dot org already. How many white houses are there (ok, stop with teh porn site references right now...)? Or cia? or microsofts?

      Why don't we get rid of the TLD all together and just type in http://microsoft/ and be done with it?
  • by Killer Eye (3711) on Saturday October 31, 2009 @05:57PM (#29937677)

    Every time something new is created, the squatters make millions, and everyone else has headaches. Does that not sum up ICANN's contributions in the last decade?

    • by rs79 (71822)

      "Every time something new is created, the squatters make millions, and everyone else has headaches. Does that not sum up ICANN's contributions in the last decade?"

      That makes little or no sense. ICANN hasn't *done* *anything*. They've say on their hands for a decade when they were formed to, and told by the US government that formed them to make new tlds.

      Apart from some truly lame tlds burped up in 2000 (the enormously popular .museum and .coop and others, which haven't even broken even yet) there have be

      • by elronxenu (117773)
        • Lame TLDs (.museum, .coop, .jobs etc)
        • The domain tasting debacle
        • The UDRP
        • Allowing VeriSign to ride roughshod all over the DNS with their wildcard entry "Site Finder"
        • Lack of openness and insufficient public participation

        Some of these problems were the result of ICANN's actions; some were caused by ICANN doing nothing when it should have acted. The GF's point is valid; the DNS is only good for squatters and registrars and registries; what good will more gTLDs do?

  • What is the point? (Score:3, Insightful)

    by Gonoff (88518) on Saturday October 31, 2009 @06:14PM (#29937753)

    All new TLDs are immediately filled by the same old names.

    If they created a new TLD of .whateveryoulike then you can be sure that all the corporate big names would fill in their names - Microsoft, Sears, Exxon or whoever. After them would come all the domain grabbers who would sit on anything of interest and offer it for "only $499".

    It needs to be ensured that this does not just become another land-grab by multiple registrars, like last times...

    • by Duncan3 (10537)

      All this has EVER been is a way to extort more yearly fees from every corporation on the planet.

      That's what our economy is based on now. It is well known to be the best way to make money, since you don't have to do anything in return. http://en.wikipedia.org/wiki/Rent_seeking [wikipedia.org]

      Think of it as Mafia 2.0.

  • I can't wait for the next profitable action from ICANN that will improve spamming opportunities to take effect. Really, the current gTLDs are far too well regulated - we need something wide open so that domains are not traceable or accountable to anyone at all.

You're already carrying the sphere!

Working...