Slashdot Mirror


New TLDs Proposed To ICANN

MemeRot writes: "ICANN has a list here of the new TLDs that have been proposed, along with the companies that have proposed them. The applications haven't been checked to be complete, and ICANN still has to decide whether they're going to allow multiple proposals by a single applicant. Still, this is the list of all possible new TLDs and you will be happy to notice that many people are proposing common sense ideas whose time seems to have come - .sex, .xxx, .kids, and .wap. The current target date for completing any negotiations with registry sponsors and registrars is 31 December 2000." I don't see ".dot"! C'mon!

17 of 281 comments (clear)

  1. Re:Trademarks go here by interiot · · Score: 4

    Actually, someone suggests just that here. But trademarks conflict sometimes... the same name in different industries or different countries. So it'd either have to be hierachical (company.industry.country.tm) or it would have to include its full address (company.road.zipcode.country.tm).
    --

  2. Trademarks go here by fatphil · · Score: 4

    .tm

    You know it makes sense.

    All claims to other tlds should be thrown in the bin.

    FatPhil

    --
    Also FatPhil on SoylentNews, id 863
  3. just in time by xtermz · · Score: 3

    when the time comes that you cant even register bigfathairychickswholoveskinnydudes.com .... its a sign that more tld's are needed

    "sex on tv is bad, you might fall off..."

    --


    I lost my concept of community when my community lost all concept of me.
  4. Don't see .dot? by big+balls · · Score: 4
    How about opening your eyes?

    --

    --

    --
    It's my belief that my big balls should be held every night.

  5. A very simple proposal to end domain abuse by hey! · · Score: 3

    Make the number of TLDs unlimited.

    You could register under any TLD you wanted.

    The catch: you can't own the TLD and can't stop someone else from using it.

    So if I registered "FUJINON.BINOCULARS", somebody else could register "KOWA.BINOCULARS".

    The reason people register more domains than they need is that second level domains under ".COM" are a very limited resource and therefore much more valuable than the registration fee. Talk to any business consultant and you'll find strategic cybersquatting is standard business practice.

    If second level domains where many thousands of times more numerous then the value of any one is that much less. Thus while a domain like "ebusiness.com" is valuable under the current system, the name "acme.ebusiness" would be worthless except as functionally as an identifier for your enterprise.

    While the root servers may have to be rearchitected, this solution would be transparent to all domain clients.

    The biggest problem I could see is with TLDs that are synonymous with a company (e.g. ".IBM"). I'd say those folks could stay under "IBM.COM", or could register several second level domains under ".IBM", such as "computers.ibm" and "services.ibm".

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  6. Re:Name.Space by Billy+Donahue · · Score: 3

    While we'd appreciate the free book, I think you may be the one who needs to be brought up to speed if you think that there is a technical barrier to running several new TLDs. Name.Space has been operating a registry for 500+ new TLDs for 4 years now with no complaints from BIND. The FUD that we used to see from the likes of NSI about new TLDs breaking the internet is just that: FUD. There are thousands of domains operating in these new TLDs without a hiccup. You can see them for yourself by pointing your DNS servers to 209.48.2.11, 206.86.247.30, or one of Name.Space's 7 other globally diverse nameservers. Several ISPs have made the switch. Name.Space _IS_ the sort of alternative root system that people have been asking for on Slashdot everytime this pops up. If enough people express interest in a new domain which is generic and useful, then Name.Space will add it to the root. It's that simple.

    Name.Space does not assert exclusive 'ownership' of the new TLDs, only a right to publish under them. It may look like a land grab when placed on a list of land-grabbers on that ICANN site, but it most certainly is not.

    As for your point about domain-squatting vultures,
    Name.Space doesn't support domain squatting or registrations on famous names. Name.Space will not allow a domain to be resold. Which domains are Name.Space squatting on?

    --
    -- The Funk, The Whole Funk, And Nothing But The Funk
  7. One feature which we need with these new TLDs. by AFCArchvile · · Score: 3

    ...the new web browser feature to block out DNS entries with specific TLDs. I don't know about you, but I redirect all the damn ad pages to 127.0.0.1 in my /etc/hosts file (that is, E:\WINNT\System32\drivers\etc\hosts, hehe). Doubleclick should be forced to use the TLD of .ads. That way, we can block them out at will.

    --
    "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
    1. Re:One feature which we need with these new TLDs. by dboyles · · Score: 3

      Doubleclick should be forced to use the TLD of .ads. That way, we can block them out at will.

      I really don't think you want that to happen. As it is now, it's not too hard to set up a proxy like junkbuster to filter most of the stuff that you don't want to see. That is to say, it's not too hard for the typical /. reader to set up.

      Now fast forward to a time when *everybody* can easily block ads like that. One of two things would happen:

      1. Companies like DoubleClick would come up with new, sneaky ways of getting their ads to show up.
      2. A lot of good sites that depend on advertising for revenue (let's assume for the sake of argument that /. is considered "good") wouldn't be able to continue. While some people might consider this good -- you know, an anti-commercialism of the internet sort of thing -- I think it would be bad as a whole.

      --
      -- "Complacency is a far more dangerous attitude than outrage." -Naomi Littlebear
  8. Why limit tld's? by MikeFM · · Score: 3

    Why put any limit on the number of tld's? If a company or organization or whatever is willing to sponsor a tld and act as the database for looking up tld addresses etc then why not let them? Just make it so one company can't own more than one tld.

    --
    At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
  9. Hmm.... by wedg · · Score: 4
    If it ever comes to the point where the domain name system has to be re-vamped, maybe it should be done like newsgroups. All the new suggested TLDs I'm hearing sound like newsgroups to me. com.os.microsoft anyone? How about org.news.slashdot? Just a thought.

    - w

    --
    Jake
    Dating: while( 1 ){ call_girl(); get_rejected(); drink_40(); } return 0;
    1. Re:Hmm.... by ichimunki · · Score: 4

      Combine this idea with the previous post where it is suggested that anyone who is willing to sponsor and host a TLD should be able to, then you've got a really cool system going, imho. Of course, then you need a TLD registrar to keep all the zone lookups in order, right?

      By the way, I love this com.* org.* type construction a lot, for the simple fact that you can begin to build URL completion around them. Looking for a company, but aren't totally sure how to spell the name, or worried that it might be hyphenated or whatever. Typing: com.business*name or com.bus*name, gets a list of matches, until you've found your site. This doesn't work so well when the matching starts at the most specific part of the address and is mostly useful for filling in the last four digits/characters.

      --
      I do not have a signature
  10. .dot and .god? by kzinti · · Score: 3

    .dot is there -- it's under the section proposed by JVTeam, LLC. So if .dot becomes a TLD, how do you register slashdot? Is it slashdot.dot or slash.dot? I prefer the former, then you can register dot.slashdot.dot and slash.slashdot.dot. Too bad no one's proposed a .slash TLD; then you could have slashdot.slash and dot.slashdot.slash.

    BTW, I notice that Joe Baptista's .god domain hasn't made it into the proposed lists. Anybody know what gives there?

    --Jim

  11. www.slash.dot? by Lxy · · Score: 4

    how would you tell someone that your URL is dot.dot.dot without spelling it out?

    "You'll die up there son, just like I did!" - Abe Simpson

    --

    There is no reasonable defense against an idiot with an agenda
    :wq
  12. Re:Gotta love ICM Registry, Inc. by lizrd · · Score: 3

    This sectioning off of the web by content really concerns me. Are we going to get ISPs that refuse to carry .sex or .xxx on their DNS servers? Are we going to have some committee that decides when a site cannot register under the .com or .net TLDs and must register as .adult? I realize that it is still possible to get to sites without using DNS, but it's a lot harder. This raises the spectre of censorware becoming really effective, thereby we lose one of the best arguments against it. That would really suck.
    ________________
    They're - They are
    Their - Belonging to them

    --
    I don't want free as in beer. I just want free beer.
  13. ADULT TLD by grovertime · · Score: 3
    .xxx, .sex - seriously people, there is only one reasonable selection

    .cum



    1. S I T E
      1. U N S E E N

  14. This ain't gonna work by dwdyer · · Score: 3

    Will these companies have exclusive rights to those TLDs? If not, this seems kinda stupid. Not that having exclusive rights to a TLD makes much practical sense, either.

    Right now, people who are aggressive in their pursuit of domain namespace will grab .net, .com. and .org at the same time. If we add more TLDs, then these same people will buy up as many names as they can.

    If they don't you can bet that whoever grabs disney.sex or microsoft.sucks will get slapped with a suit.

    We'll see even more namespace squabbling, even more lawsuits, even more domain grabs, and the only ones to really benefit will be marketdroids pitching TLDs to clients.

    Bah!

    If we're going this far, why not just hand the whole thing over to RealNames and do away with TLDs altogether.

    Humbug!

    --
    -dwd-
  15. Re:Is there a proposal to enforce the TLD's use? by skoda · · Score: 3

    What I found disturbing was that ICM Registry, Inc. proposed the pair: .kids and .xxx .

    Uhmmm... What exactly does their business plan entail? (shudder) No, nevermind, I don't want to know.

    -----
    D. Fischer