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!

281 comments

  1. Re:Hmm.... by Alex+Gurney · · Score: 1

    Tim Berners-Lee, when asked what he would do differently if he had his time again, said: "I would make http://www.whatever.com into http:/com/whatever."

    The second version is certainly quicker to type and to pronounce, as well as resembling to the good 'ol Unix directory syntax (despite the differences behind the scenes).

  2. Free for all tlds? by NiceBacon · · Score: 1

    For those of you who'd like to see free for all tld's (e.g. .microsoft or .nicebacon)...
    How many .com domain name registrants do you think will register their .com name as a tld? About all of them? Probably.
    And how many seconds will that take? Probably around 10.
    So where would we stand after that? Right where we are now with the .com name space.
    So what's the point? Every bloody marketing moron will register every tld he can think of and the remaining will be taken by people running dodgy xxx sites or cybersquatters.
    Hell, even upthearse.com is taken nowadays!

  3. The ONLY good solution is unlimited domain names. by Anonymous Coward · · Score: 1
    ICANN should allow anything to be used as a TLD, subject to the following 3 requirements.

    Law 1: Any combination of letters and numbers and the dash (-) may be used as a TLD. (dash may not be the first or last character).

    Law 2: Only second level domains may be registered. i.e., ***ALL*** domain registrations must still consist of two parts. Domain + TLD are both required to constitute a single registration action.

    Law 3: The TLD itself is registered to no one and remains free for anyone to use. (like is currently done with .com, .net, .org, etc.)

    This would accomplish the follwing:

    (1) An end to domain hogging. e.g., not even Microsoft, could "buy up all of microsoft.*" since there is for all practical purposes, infinite combinations of microsoft.* to say nothing of m1crosoft.*, m1cr0soft.*, m1cr0s0ft.*, etc.

    (2) An end to squatting/domain-brokering. Anyone wanting a FOO domain name need not worry if FOO.{com|net|org} is already taken. Even the domain auctioneers/resellers can't "get 'em all" so there will always be something available.

    (3) Allows sharing of domains among same named companies and individuals. e.g., Apple Computer Inc. can have apple.computers or apple.inc or apple.comp while Apple Records can have apple.records or apple.music and a farmer can have apple.farms or apple.growers and John Q. Apple can have john.apple or apple.family. The possibilities are endless and there is room for everyone.

    Of course the root DNS servers will need some adjusting to handle this, but could distribute the load based of the first few letters of the TLD. And *only* the root servers need their DNS software rewritten. Ordinary users needn't upgrade anything unless they have software that expects domains to come from some hardcoded list or be exactly 2 or 3 characters long.

    However, limited domain names make them porfitable and prevents corps from "fully protecting our trademark" so this sensible idea will probably not be implemented since it ruffles too many political feathers and doesn't make as much money for domain registrars and resellers.

  4. Proposing ... Proposing ... Proposing by SuperDuG · · Score: 2
    Okay this is wonderful ... everyone proposes these wonderful ideas about TLD's ... let's see ... .gov ... ohh yeah that's the american government ... .gov.uk wait how come .gov isn't .gov.us ?? hmm

    Another thing ... even if the creation of .xxx or .sex came about ... I see no reason why a commercial sex site would do that ... automatically gets into blockers and such ...

    Then there's the wonderful idea of regulating the domains ... ahh yes ... .org is for non-profit orginizations only ... right? Whoa hold on there what's slashdot.org ... ohhh yeah ... commercial news site.

    So here's my proposal ... I say GOODBYE ICANN ... and hello FREECANN ... I have no idea how to get something like this off the ground, but imagine a distributed database that linked domains for ... let's hear it ... FREE ... and anyone could add them ... we'll call it First Come ... First Serve ... and screw 3 letter limit I say we make .news .stuff .linux ... it will be like USENET And IRC And FREENET combined into one ...

    Lost ya? okay IRC ... There's regulation services that hold channels for you ... but it's still first come first serve ... if they decide to not use the channel the service is ended ... then theres USENET ... a bunch of alt.whatever.sex and everyone knows by the name what the newsgroup has. Then theres FREENET the unregulatory shared filesystem that anyone can join and view ...

    I say we make it happen ... FREE THE NET!

    --
    Ignore the "p2p is theft" trolls, they're just uninformed
  5. Yeah, that .three33 stuff is strange since they have it again in Chinese (Japanese too?) as .sansansan. I wonder if three has any significance, as do, say four (death) and eight (luck/fortune, though that seems to be more the case in guangdonghua, aka Cantonese).

    1. Re:333 by Ted+Nitz · · Score: 1

      since they have it again in Chinese (Japanese too?) as .sansansan.

      Yep, quite a long time ago the Japanese people realized that their counting system sucked, so they adopted the Chinese system. It would be sansansan in Japanese as well.
      -Ted

  6. What makes a _TOP_ level domain? by 10sball · · Score: 1

    Why are some of the proposals simply just references to protocols? I'm speaking of things like *.wap, & *.web. Why can't a company live with ftp.companyname.shoes, www.companyname.shoes & wap.companyname.shoes?

    It also seems to me that 95% of the tlds on this list are purely for vanity & not for organization purposes. Like RegistryPro, Ltd proposing the *.pro TLD & Dubai Technology proposing *.dubai. Shouldn't we be discussing the merits of *.apparel vs. *.shirts and not sillyness like *.i, *.pro & *.cool

    --
    [place .sig here]
  7. Re:.wap would be bad by BlowCat · · Score: 1
    This would mean:

    1. More companies using more than one domain
    2. More conflicts
    3. What company has more rights on cvs.wap: cvs.com, cvs.org or cvs.net? I don't know the answer.

  8. Re:Gotta love ICM Registry, Inc. by mayonaise · · Score: 1

    I haven't had time to research this more, so I may be incorrect, but what part do the companies proposing these TLDs have if their TLDs are selected? Do they get to be the root servers for those particular TLDs, or do they just get credit for coming up with the name?

    If they do happen to get to be root servers for their TLDs, do they get control over what's registered under their TLDs? If so, wouldn't they be regulating it?

    I realize there are a lot more questions than comments in this post, so please feel free to fill me in on what i don't know (which is a lot)!

  9. Stating the obvious for those who don't get it by mttlg · · Score: 2
    First, it makes a lot of sense for the same company to suggest a .sex type TLD and a .kids TLD at the same time. Having both would allow for different levels of parental censorship. Parents who can't be bothered to raise their kids can either block all nasty porn sites (.sex) or limit their kids to sites that are so dull and boring that they can't possibly offend anyone (.kids). This tactic also gives a greater chance of success at making "family-friendly" browsing possible - if both aren't accepted, maybe one will be.

    As for enforcing the use of these TLDs, someone will probably have to figure out what would and wouldn't be allowed in a .kids kind of TLD, and all of this will take time and money, but those costs could just be passed on to people who keep complaining that the web isn't perfectly sterile and empty of thought - in other words, let them deal with it. An occasional check-up to make sure a .kids site hasn't turned into kiddie porn is all it would take to enforce this (and there are probably lots of people who would do this for free). If things get too restrictive, people might just realize how silly this nonsense really is.

    There is no need to force any adult site to move to a special TLD. Many would probably do so voluntarily, just like many take precautions to keep people from "accidentally" viewing porn. It's good PR to look like you care about protecting underage people from nakedness, just like how beer and cigarette companies pretend to discourage children from using their products (although they are probably under pressure to do that). I'm sure a .sex TLD would be quite popular with adult sites anyway - everyone would want a domain with their favorite type of sex. The added bonus is that people could finally use the internet as it was intended by blocking all but the .sex sites.

    1. Re:Stating the obvious for those who don't get it by mikpos · · Score: 2
      You could do it at the libresolv level (or whatever the equivalents would be on other systems). There would be a system-wide configuration file, maybe. libresolv consults that before doing any name lookups and automatically returns an error if user jimmy is looking a domain matching .*\.religion.

      Mind you there's nothing that says that jimmy can't download or write his own libresolv in order to read Christian propaganda, but he probably wouldn't go to the trouble (especially if he didn't have superuser permissions).

    2. Re:Stating the obvious for those who don't get it by LiNT_ · · Score: 1
      Now correct me if I'm wrong. Wouldn't it be possible to just do an nslookup on the hostname and use the ip instead? Sure I realize that no system will be fool proof. And yes, I realize that web browsers could be forced to do reverse lookups and check the hostname.

      All in all, I think it's a great idea. It makes it hard for kids to view porn and easy for adults to find it. I just don't think changing the .tld's will allow much better url filtering than we have now.

      LiNT

  10. but .dot is listed by twingo_gtx · · Score: 1

    .dot .info .site .spot .surf .web JVTeam, LLC 1120 Vermont Avenue., NW Washington, DC 20005 USA +1 202 533-2600 Ken.hansen@neustar.com

  11. 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).
    --

  12. Two comments by David+H · · Score: 1

    First, I'm glad to see only a few entries that may be subject to trademark status. I would prefer that none of the tld's be trademarks.

    Second, no one took .comp, .rec, .sci, .alt, etc. Those seem like naturals to me.

  13. SOS by lsommerer · · Score: 1

    URL to the slashdot help files:

    http://dotdot.stashslashslashdot.dot

  14. Re:.SEX, .XXX, .KIDS TLDs Restrict Freedom of Spee by chakmol · · Score: 1

    Bottom line is that TLDs should be for categorizing content, not restricting content which is what the proposed .SEX, .XXX, and .KIDS TLDs would do.

    Well said. Most commercial adult sites ALREADY require some type of adult verification (AVS). Those sites which do not are not likely to abide by the new TLD's .sex, or .xxx. There will always be flash-in-the-pan Geocities-type adult content. Then the big censorship monster rears its head as to who decides what is adult content when we try to fit all those grey areas into the new TLD's. At this point we are back to the political and capricious decisions of "what is" and "what isn't" as is evidenced by current filtering software.

  15. .SEX, .XXX, .KIDS TLDs Restrict Freedom of Speech by Ron+Bennett · · Score: 1

    First the problems with the proposed .SEX & .XXX TLDs:

    The proposed TLDs .SEX and .XXX seem well intentioned as a way of partitioning off adult oriented materials from minors, etc.

    Seems sensible, but how does one exactly define adult oriented materials? -especially considering the internet is an international medium. What is considered adult oriented here in the United States isn't elsewhere and vice-versa.

    And what happens when ICANN or whoever decides to go the next step and restricts adult oriented materials to only certain TLDs - for example .SEX and .XXX only.

    And how would such content restrictions be enforced?

    In the end TLDs such as .SEX and .XXX will probably result in ICANN dictating content too.

    In regards to problems with the proposed .KIDS TLD:

    Many of the same points above apply to .KIDS too...

    How does one exactly define kid oriented materials? -especially considering the internet is an international medium. What is considered adult oriented here in the United States isn't elsewhere and vice-versa. For example, nudity in many parts of the world such as parts of Europe and Japan is not considered harmful to children. On the other hand, violence aimed at children is widely tolerated in the United States, but not content containing nudity.

    And how would such content restrictions be enforced?

    And as I said above, in the end TLDs such as .KIDS will probably result in ICANN dictating content too.

    TLDs should be used to better categorize content, but not to restrict it. While .SEX, .XXX, and .KIDS TLDs are well intentioned, all three of these TLDs are all primarily intended to restrict content as opposed to merely categorizing it. It's very important to keep this distinction in mind when considering new .TLDs.

    Bottom line is that TLDs should be for categorizing content, not restricting content which is what the proposed .SEX, .XXX, and .KIDS TLDs would do.

  16. Worthwile TLDs by Yottabyte84 · · Score: 1

    Personaly I think TLDs sould be limited to 3 chacters. Anyways here's a list of TLDs that I think should be implemented and why.
    .per for personal sites like this. (no it's not mine)
    .sex for p0rn
    .xxx for p0rn
    .shp for online stores.
    .crp corprate information.
    .ent entertainment.
    .web whatever
    .inc alternative to .com
    .uni university sites
    .k12 sites for K-12 schools

    anything more is too much and will confuse the crap out of newbies

  17. Re:Wow ICANN is an awesome organism by |guillaume| · · Score: 1
    d'oh...

    my mistake, don't know where I saw that we were the 2nd...

    gotta put my head in the ground and try to be forgotten now...

    --

    give me all your garmonbozia

  18. 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
    1. Re:Trademarks go here by taniwha · · Score: 1

      yeah but that's a country code - and not available as a TLD (which is why you can already get a .tm domain)

    2. Re:Trademarks go here by big+balls · · Score: 1
      Then let's nuke that country so the domain becomes available again!

      --

      --

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

    3. Re:Trademarks go here by Yamao · · Score: 1

      or it would have to include its full address (company.road.zipcode.country.tm)

      Probably not. What if you relocate? What if you have multiple sites? Also, the idea that you're accessible from anywhere also goes down the toilet.

      Personally, I like the idea of having infinite TLD's with no ownership. That's way cool, and I wish I had thought of it.

      --
      Be nice to your friends. If it weren't for them, you'd be a complete stranger.
    4. Re:Trademarks go here by excesspwr · · Score: 1

      I'm amazed there is no .riaa or .mpaa and the like.

    5. Re:Trademarks go here by kirwin · · Score: 1

      I think .inc, .ltd, .llc, and .sm are needed also.

    6. Re:Trademarks go here by fatphil · · Score: 1

      .reg then?

      Who has registered in .tm, by the way?
      What country is it - Turkmenistan?
      How many of the registrants are based (really _base_d) in that country.
      How many are simply making a DNS pun on their trademarks?
      It appears that you don't need a local company to register, or even a local presence. And the payments are to be made in US dollars...
      Ah yes, that Turkmenistan, the one that uses dollars as its currency...

      FatPhil

      --
      Also FatPhil on SoylentNews, id 863
  19. Re:A Couple of Observations by Alex+Gurney · · Score: 1

    The list is not complete as one of the submitters list says "other portions of application claimed confidential"

    That company also asked for .sex and .xxx, so perhaps the TLDs are "rude words" that ICANN didn't want to publish.

  20. Stupid .1 by Mr.+Competence · · Score: 1

    Haven't they heard of IP addresses?

    Guess I will get .314159

    --
    Those who open their minds too far often let their brains fall out.
    1. Re:Stupid .1 by John+Napkintosh · · Score: 1

      Those would be about as useless as .net.

      :)

      --

      Long signatures suck.
    2. Re:Stupid .1 by QuMa · · Score: 1

      Actually, iirc there's some rfc that states no part of a domain (not toplevel, not second level, not 3rd level etc) may start with a number. Not that anybody sticks to it ofcourse...

    3. Re:Stupid .1 by kvbeek · · Score: 1

      By the way, if they do allow the TLD .1 to be a new TLD, I will be in line to register 0.1, and the first host in my zone file will be 127.0.0.1. I'll have a very popular website.

      As far as I can discern, TLDs CANNOT be purely numeric. That'd break a hell of a lot of software. How do you know if it's a DNS name to look up or an IP number?!?!?

    4. Re:Stupid .1 by Yogger · · Score: 1

      Actually, I think it could be a number as long as its not 0 to 255. so you could have like 333.333.333.333 as a domain name but just mapped to an ip addy the same way the current names are.

    5. Re:Stupid .1 by mikpos · · Score: 2
      Presumably they would still disallow hostnames that started with a number. e.g. you could register zero.1, but not 0.1.

      Not to say that it makes it any less stupid.

    6. Re:Stupid .1 by gle · · Score: 1

      Of course there are!
      2600.org comes to mind immediatly.

      Join KWSN - The coolest SETI team!

      --
      Ni!
    7. Re:Stupid .1 by clgoh · · Score: 1

      Imagine if we get .1 and .one

  21. Re:can't do it and follow protocol by Anonymous Coward · · Score: 1

    You can configure BIND to think it has authority for a TLD, just like you would for a regular domain. This would effectively block out any TLD you don't want to service.

  22. How about .gnu? by jlittle · · Score: 1

    I just scanned some comments and didn't see this yet, but how about a .gnu TLD? This way, most open source projects can get their own domain easily, and companies are less likely to squat on it.

    I know.. I know.. .gnu may be limiting to GPL, etc.. .oss? Just a few thoughts that sprang to mind

  23. 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.
    1. Re:just in time by xtermz · · Score: 1

      awesome, ill ad it to my new domain: havelotsofsexwithalarge.group

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

      --


      I lost my concept of community when my community lost all concept of me.
  24. Lots of TLDs by Devil_Dog · · Score: 1

    Glad to see that lots of TLDs were included in the list, although it's enough that it makes you think about whether we should just open up .whatever and have any TLD that's possible? Just an idea, I know it's been thought of before and has it's downsides, but it does have it's benefits also.

    Someday I'll make devildog.org into something.

    --

    Someday I'll make

    1. Re:Lots of TLDs by billybob2001 · · Score: 1
      Ok, I'll start with .earth (better have .world and .globe).

      Next .mars, .venus and how about .planet?

      I guess .moon would be quite a good one, but I obviously wouldn't want .sun!

    2. Re:Lots of TLDs by Moghedien · · Score: 1
      >but I obviously wouldn't want .sun!

      though no doubt Sun Microsystems would like one of those... :)

      --
      I've come to... anesthetize you!
  25. Re:Don't see .dot? by SenshiNeko · · Score: 1

    I don't see ".dot"! C'mon!

    He is using "see" in the common vernacular sense of substituting for 'don't understand'... as in saying 'I don't understand why someone proposed 'dot-dot'!

    It does sound like it could lead to more than a bit of confusion, as people end the 'dot-dot' addresses with "www.slashdot.." for example.

  26. Re:.DOT by Delphis · · Score: 1

    it's just going to be a mad scramble for dot.dot as a domain name.. that's all anyone is interested in.. you can then have .dot or whatever you want then

    --

    --
    Delphis
  27. 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.

    1. Re:Don't see .dot? by Ggggeo · · Score: 1

      It does say at the top of the page that there was a correction made today (Oct 3) which includes 2 applications which were previously omitted. It is possible that one of JVTeam's was one of the applications omitted. Or not. I dunno.

      --
      In God we trust...all others please have two forms of ID
    2. Re:Don't see .dot? by victim · · Score: 1

      I guess we can't expect the posters to read the articles they post. They don't even read the slashdot headlines!

      JVTeam has requested ".dot".

  28. why not allow all three letter TLDs? by fantail · · Score: 1

    Expand the current system which allows .com .org and .net to allow any 3 letter top level domain (except a few reserved for special use e.g. .edu .mil .gov).

    Of course this might cost amazon.com a bit of money if it has to register amazon.*** for around 17000 different TLDs :)

  29. Re:.wap? by dav · · Score: 1

    you halfway get it, genius.

  30. There is a .dot by keepper · · Score: 1

    READ before you post Mr Taco :P

    .dot .info .site .spot .surf .web
    By:
    JVTeam, LLC 1120 Vermont Avenue., NW Washington, DC 20005 USA +1 202 533-2600 Ken.hansen@neustar.com

    1. Re:There is a .dot by mach-5 · · Score: 2

      Whoa! Cool! h-t-t-p-colon-slash-slash-slashdot-dot-dot. Say that 3 times fast!

  31. Re:A Couple of Observations by skoda · · Score: 2

    The list is not complete as one of the submitters list says "other portions of application claimed confidential"

    I was wondering about that. If their business plan revolves around secret tlds--well, that's even more stupid that the cuecat nonsense.

    Or perhaps it's .eviloverlord, .takeovertheworld, & .resistanceisfutile, and they don't want to spoil their "surprise" for us just yet. But they could have saved everyone the hassle and just used .microsoft :)
    -----
    D. Fischer

  32. .wap? by Alanzilla · · Score: 1

    Is that for Italians?

    1. Re:.wap? by extar-bags · · Score: 1
      first, B, and three, eh? well you sound just super-intelligent.

      ----------

      --

      ----------
      "Rock over London... Rock on Chicago..." -Wesley Willis

    2. Re:.wap? by B-B · · Score: 1

      Wop stands for _With _Out _Papers, as in arriving at Ellis Island without identification of any kind.

      Cheers,
      Tom

      --
      Reality does not happen until you analyze the dots. -Don DeLillo (Underworld)
    3. Re:.wap? by t0qer · · Score: 1

      no that would be .wop you dumb bastard. --Toq

    4. Re:.wap? by dav · · Score: 1

      first off, bozo, the deragatory word for italians is wop. and B) .wap is for Wireless Application Protocol and three: shut up you fuck.

  33. enforcement? by geekoid · · Score: 1

    I am a big believer in the need for the .xxx or .sex TLD. I think that could allow parents to easily control what there kids view(like it or not that is the parents responsibility), without needing undue 'censorware'. It would be trivial to block everything of a specific domain.
    If they don't force adult entertainment sites to use those TLD, it will be useless.
    Same goes for .kids. Are they going to monitor that TLD to be sure it only has content for kids?
    I think that the people submitting these ideas have the right idea, but they really need to find away to impliment these ideas thats fair for all parties involved.
    as for the .xxx domain, they will need to put on paper exactly what constitutes a adult entertainment site. Using words like inappropriet, immoral, risqu(sp)etc... needs to be avoided, they must explicitly name the acts that would be involved. I would also like to see the adult entertainment industry push for a specific domain for there sites. It would be great marketing, and fantastic PR opportunity. As long as there is a place where adults can easily get to there sites, I would find it difficult to call this censorship.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  34. Re:Why limit tld's? by jonathanclark · · Score: 2

    I just use google's "I'm feeling lucky" for everything... Then you don't have to remember a TLD and you don't end up going to a pron site when you meant to go to the real white house. I think there were unlimited TLDs then people would be forced to use a search engine for everything and names would have less value. Still there is so much marketing and demand out there for ".com" that it will likely always remain a tight space.

  35. .Nom? by quinto2000 · · Score: 1
    The one I REALLY don't understand is .nom

    What does that mean? Any ideas?

    --
    Ceci n'est pas un post
    1. Re:.Nom? by /dev/trash · · Score: 1

      nom is French for name.

  36. Re:Because FORCING 2nd level regist'ns devalues na by Grahf666 · · Score: 1

    These new TLD's are a bad idea, imo. As if it isn't hard enough to remember any given url, this will now make it a good bit harder, given the essentially unlimited number of new TLD's. Perhaps a few new ones, like say .xxx to easily denote porn sites, might be nice to increase the name space, but really, most of the proposed tld's are way too long to easily remember, and the rest are obviously centered on one company's web site. Oh yeah, and I DID see .dot.

  37. OT: Karma rest to 50 today. Coincidence? by Cy+Guy · · Score: 1

    Interesting Coincidence that today is the day Taco chose to finally reset the karma of everyone over 50 back down to 50.

    Maybe he is finally removing the cap, and is just making it fair by giving anyone previously held to the 50 cap a level playing field with those that had previously gotten past 50. Regardless of the reason, there is finally a point to clicking the 'No Score +1 Bonus box again.'

  38. ICANN is not the last word by chuck · · Score: 2

    I'm surprised to see very little mention of the fact that you can choose your registry. With projects like OPENNIC available to us, we have much more choice than we think. Of course the great challenge is getting an "alternative" domain name system accepted, but this can be done on a server-by-server basis. Alternative DNS systems can co-exist with the mainstream and gain influence until we can overturn the current, corrupt, and f**ked up system.

  39. Re:Why limit tld's? by RedWizzard · · Score: 1
    The problem with this is consumer conscience. While I agree that there should be more TLDs, most internet users are doing good to remember a 2nd level domain with .com (possibly .org or .net). Yep. One of things I like is that if I'm looking for company I can be fairly confident that the address is www.companyname.com. (I was actually asked this in a survey one: "How would you find Sony on the Web? I'd go to www.sony.com. Duh.) It's going to be bad enough having to guess between www.companyname.com, and www.companyname.biz, without throwing www.companyname into the mix. Oh well, there's always google.
  40. Re:Why limit tld's? by Glarvat+the+Hepcat · · Score: 1
    The problem with this is consumer conscience. While I agree that there should be more TLDs, most internet users are doing good to remember a 2nd level domain with .com (possibly .org or .net).

    But when you add many more TLDs, it becomes much more difficult to get people to remember both a TLD and a 2nd level domain. How are they supposed to know whether to go to mybiz.com, mybiz.biz, mybiz.ebiz, etc.?

    Unfortunately, I aside from a select few new TLDs, I don't see many new ones that will actually enter the consumer conscience and become well known.

    That's just my opinion, I could be wrong...

  41. Try saying this by GenetixSW · · Score: 1

    three times fast:

    slashdot.dot

    Doesn't that get annoying at one point or another? "Slash-dot-dot-dot"... Honestly I'm surprised that .dot was released as a TLD, since it's going to get it many tongues' way...

  42. Why don't we... by Mr.+Piccolo · · Score: 1

    steal the Usenet ones?

    linux.comp
    fermilab.sci
    slashdot.misc
    trolls.rec

    etc...

    --
    Glückwünsche, haben Sie Slashdot ermordet, indem Sie zum korporativen Druck beugten und Subskriptionen einlei
  43. Re:Hmm.... by RedWizzard · · Score: 1
    Just exactly how is it easier to pronounce and type given that most of the time the www. part is optional and people generally exclude the http://?

    You're really comparing whatever.com to com/whatever. I don't see the benefits.

  44. .soup anyone? by otomo_1001 · · Score: 1

    Am I the only one seeing this? We have a whole tld allocated for a foodtype? chunky.soup, creamy.soup, crappy.soup?!?!?!?!? It just doesn't fit to me. But .sucks is perfect, I just wonder what'll happen to suck.com.

  45. .global, no .int by KjetilK · · Score: 2

    ".global" -- makes sense for multinats orgs/corps.

    I think that they should ease up on .int instead. Int is for international organizations formed by a treaty, that's OK, but then, what is meant by an internation organization is then defined to mean only inter-governmental organizations. I'll claim however, that it was never the intention of those who wrote the international law on treatises to come up with a general definition for "international organization". Now, the reason why I'm whining is that YMCA and ESA are not inter-governmental organizations, but yet they've got .int domains. Ain't fair. :-)

    --
    Employee of Inrupt, Project Release Manager and Community Manager for Solid
    1. Re:.global, no .int by Billy+Donahue · · Score: 2


      Name.Space's point is that there is room for both. Why not? Why limit ourselves?

      --
      -- The Funk, The Whole Funk, And Nothing But The Funk
  46. Re:.dot and .god? by _xeno_ · · Score: 1
    I prefer the former, then you can register dot.slashdot.dot and slash.slashdot.dot.

    Just so you know, all he'd register is the slashdot.dot domain. Once he has that, he can tack whatever the hell he wants on the beginning. A lookup would first ask the .dot server for who knows about slashdot.dot and then that server, which would be run by the slashteam, could have slash.slashdot.dot, beta.slashdot.dot, goatsex.slashdot.dot, or whatever. You only register the second level name. Microsoft owns all server names that end it microsoft.com. My college can have whatever names they want within wpi.edu.

    --
    You are in a maze of twisty little relative jumps, all alike.
  47. Re:"one company" - "one tld" will fail by Wellspring · · Score: 2

    Why should a company only get one TLD? It doesn't need to be three letters long... Let's just open it up and register it the way the domain registrars are set up.

  48. Re:A very simple proposal to end domain abuse by /dev/kev · · Score: 1

    While I like this idea (a lot), I'm concerned that it wouldn't necessarily end abuse, just reshape it.

    For example, it provides more opportunity for typosquatting, white.house has additional typos of whit.ehouse and whiteh.ouse.

    In some sense, you've made the "whitehouse" domain even more scarce, since now it's just "white.house", not "whitehouse.{com,org,net,gov}"... You say they'd be "worthless except as a functional identifier of your enterprise", but this may be the whole problem - now there's essentially only one domain which represents you as "acme.ebusiness". If "acme.e.business" is also gone, and your company's name is "ACME eBusiness", then you're pretty fucked.

    Hmmm and you could have wierd things like "w.h.i.t.e.h.o.u.s.e"... Definately needs quite a bit more thought, I think.

    I do however love the idea of a .alt domain, where anything goes, just like on usenet.

    --
    Quidquid latine dictum sit, altum viditur.
  49. .tim by TwP · · Score: 1
    Personally, and speaking for all "Tims" everywhere, I am deeply offended that .tim was nowhere proposed or recommended. It is in the interest of "Tims" everywhere to have a .tim TLD to act as convienent and easy to find collection point for all things relating to "Tim". The conventional three letter TLD names works very well for our purposes. In fact, I fail to see how the web will continue to function in a coherent manner with the .tim TLD.

    On a more humorus note, I am surprised that no one recommended .tld for a TLD.


    -----------------

  50. Re:Hmm.... by RedWizzard · · Score: 1
    com.microsoft.www makes a lot more sense. I really don't see why. Maybe it makes more sense to programmers and other people used to dealing with hierarchical namespaces in that order, but when most people go looking for MS I bet they think "I'm look for Microsoft, which is a company" (i.e. microsoft.com) and not "I'm looking for a company which is called Microsoft" (i.e. com.microsoft).

    While the hierarchy for domain names may look like a file system to us most people don't make that connection. As for fitting with Java's name space, who gives a rat's arse?

  51. The simple solution. by mindstrm · · Score: 2

    1) Leave the domain structure as it is; it's heirarchial; anyone is free to expan beneath their current domain as much as they want.

    2) Come up with a NEW lookup service for the WWW. DNS was *NOT* invented for the WWW. IT was not designed with this kind of use in mind.

  52. Re:A Couple of Observations by RedWizzard · · Score: 1

    You forgot .beer.

  53. Why use TLD's at all? by Frizzle+Fry · · Score: 1

    Allowing an of wide variety of names to be used as tld's makes them no longer than useful for figuring out what kind of site you're going to, so why not eliminate them all together? People who are intimidated by the internet would find an address like microsoft much more friendly than microsoft.com.

    Care about freedom?

    --
    I'd rather be lucky than good.
  54. Personal homepages by harmonica · · Score: 2

    .home (ianbicking.home -- only registration by individuals of their own name or variation on their name... maybe a different TLD, though... .person)

    What about all those John Smiths? Peter Muellers? You'd have to append a number as 4th level domain, which will look ugly:

    344.john.smith.home

    Yuck! Lots of people want homepages with their nicks in the name:

    1.cmdrtaco.home

    Those names make a fine hierarchy, but they look butt-ugly... (IMHO) And if you want to visit a person's homepage, you would again have something that you cannot memorize: a number (given that you have no problems with the name itself).

  55. How about .likeItUsedToBe? by yellowstone · · Score: 1

    It's a winner.

    Who wouldn't surf over to www.slashdot.likeItUsedToBe, www.kuro5hin.likeItUsedToBe, www.deja-news.likeItUsedToBe, or even www.theWholeDamnWeb.likeItUsedToBe?
    --
    150 Opening BINARY mode data connection for slashdot.sig (129323052 bytes).
  56. Re:.wap - bad idea! by RedWizzard · · Score: 1
    They do: wap.domain.tld. wap belongs at the front, just like ftp and www. Google, for example, does this (wap.google.com).

    What you seem to want is better WAP support from sites. That's a different issue and making wap a TLD won't help that issue as no one will force companies to register *.wap or to use it even if they do register it.

  57. Bring some Order in this Chaos. by senfman · · Score: 2

    I think the ICANN would do well bringing some order in the current 'Domain Chaos' before adding new Domains. I'll give you some samples. In Germany every Domain has the ending '.de'. In England or Israel you have endings like '.co.uk' or '.co.il' for companies and other endings for other Institutions, which is actually the best Solution and should be used in every country. The U.S. don't even have an own Domain (okay, there is '.us', but there is hardly somebody using it), so they use '.gov' for Government and '.edu' for educational Instituions, which is unfair as compared to other countries. '.gov' should be available for the UNO, NATO and other similar institutions. The ICANN must invent a fair system for Domains toface the Future.

  58. 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.
    1. Re:A very simple proposal to end domain abuse by paulds · · Score: 2

      This is not a new suggestion. I, for one, was proposing this to everyone who'd listen within the ICANN formation process since the very beginning, but I was met with nothing but stony silence in response.

      Everyone agrees that there are no technical reasons this wouldn't work. The root servers are easily capable of handling referrals for an unlimited number of TLDs, which is obvious when you realize they're currently handling referrals for all the .com second-level domains *directly*.

      The frank answer to why this isn't on the table for discussion is a political one; it's simply not in the best interests of the corporatists who run the DNSO (and the ICANN board, for that matter). The corporations running the registries and registrars are afraid of their cozy profit model being shaken up by any such change. Likewise, the corporations everywhere who are abusing intellectual property law in regards to the domain name system would fight tooth and nail against opening the floodgates to potentially thousands of new TLDs, since they'd be functionally unable to continually steal all possible domains vaguely related to their names and trademarks.

      Thus, while this is clearly the fairest and healthiest long-term solution for the good of normal non-abusive users of the Net, I am sadly forced to conceed that it is unlikely ever to be implemented.

    2. Re:A very simple proposal to end domain abuse by nizo · · Score: 1

      Umm, so if microsoft picks windows.microsoft, then I can register yousuck.microsoft? :-) I do kinda like your idea however, since it would tend to keep the really good domains from being sucked up, and would make the domains alot more identifiable.

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

      Umm, so if microsoft picks windows.microsoft, then I can register yousuck.microsoft? :-)

      I'd actually thoguht of this. Absolutely. As long as your use of this domain fell within the normal fair use standards for trademarks. If you were Corel^H^H^H^H^H Red Hat and registered "yousuck.microsoft" you might be liable under trademark dilution (IANAL), but if you were an advocacy group, sure go ahead.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    4. Re:A very simple proposal to end domain abuse by hey! · · Score: 2

      In some sense, you've made the "whitehouse" domain even more scarce, since now it's just "white.house", not "whitehouse.{com,org,net,gov}"...

      No, because you could still register "whitehouse.gov" (etc.), as well as "presidency.whitehouse" and "whitehouse.presidency" and "burn.down.the.whitehouse".

      You say they'd be "worthless except as a functional identifier of your enterprise", but this may be the whole problem - now there's essentially only one domain which represents you as "acme.ebusiness". If "acme.e.business" is also gone, and your company's name is "ACME eBusiness", then you're pretty fucked.

      You'd be considerably less fucked than you are now just .com, .net, .org. You'd still have "ebusiness.acme", "ebusiness.acmecorp", "acme.e", "acme.ebusiness.corp", "acme.ebusiness.com", "acme.ebusiness.services" etc. You'd still have recourse to trademark infringement.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  59. Re:Why .nom? by Cy+Guy · · Score: 1

    Nom is French for name, so you could have johnsmith.nom and 5551212.tel as your personal domains. Of course, there would be a lot of other John Smith's who want the johnsmith.nom domain, so I think the .tel is a better idea.

    On a related note, the US post office is creating a email address for every mail recipient in the US. it will consist of your 9-digit zip, followed by the last two digits of your street address or apartment number, and your first and last initial. So Bill Clinton's is bc20502000100@usps.gov


  60. Re:.wap would be bad by RedWizzard · · Score: 1

    WTF is wrong with wap.slashdot.org? WAP is a protocol - it belongs at the front.

  61. If this isn't a reflection of greedy interests... by cswiii · · Score: 2

    ...I dunno what it is. It certainly isn't unbiased.

    .dubai, as recommended by "Dubai Technologies"? .kids, suggested by both "DotKids, Inc." and ".KIDS Domains, Inc.", among others? .africa?

    This is just the same old tired crowd of cybersquatters, speculators and egotists waiting for ICANN to fire its gun into the air.

  62. Re:Borrow naming scheme from usenet? by KjetilK · · Score: 1
    Yep, .rec was something I really missed on the list. It was the only really nice TLD from Generic Top Level Domain Memorandum of Understanding, which is the stuff from the other time this was up.

    And, I would really like to get my hands on such a domain....

    --
    Employee of Inrupt, Project Release Manager and Community Manager for Solid
  63. .dubai rant by SaiyajinTrunks · · Score: 1

    Proposed by none other than Dubai Technology, Electronic Commerce and Media Free Zone Authority, whatever the hell that is supposed to be. Where is the .conceited? I want .russleonard! Even the best suggestions on the list are questionable (I kinda liked .home for a few seconds). Hardly any are reasonable suggestions for TOP LEVEL domains. I just can't get over it: .dubai! Do they propose to host a massive amount of different sites that require special "Dubai" distinction? I have never even heard of Dubai Technology and [blah blah blah] company! Gee why not .netcom or .aol or .earthlink? /rant

    --


    "You point your finger at the moon, the fool stares at your finger."
  64. Re:er... by Zarniwoop · · Score: 1

    Solely so Malda could have a URL of slash dot dot dot.


    What do I do, when it seems I relate to Judas more than You?

    --
    Still not dead.
  65. Didn't RMS suggest .gnu by Yohahn · · Score: 1

    And if he did, why isn't it on this list?

  66. .inc and more by lord+kiwano · · Score: 1

    .inc gave me the idea that they should add corp, gmbh, ltd, tm, etc. and restrict those domains to corporations whose name contains the relevant tld, then kick all the trademark lawyers out of the rest of the domains (like com, org, net)
    That and have some sort of mechanism to prevent registration of both foo.inc and foo.sucks by the same company (or wholly owned subsidiaries)

  67. What about Families .net and .org by WillSeattle · · Score: 1

    Seriously, we already have a bunch of people in my fairly small extended family with affleck.com, affleck.org, and affleck.net, which is not fair, if you think about it. Adding .per just gives us one more to squabble over.

    And don't get me started on .home - I know two John Affleck's in my immeadiate family, are they supposed to be john.affleck.home and john2.affleck.home and even then it's not fair.

    if we're going to implement .per, it has to be a workable string, like john.affleck.wa2.per and john.affleck.fla.per, but with the domain resolvable only at the discrete level, so noone owns affleck.per or john.affleck.per, since they are multiples.

    Luckily for me I've got a hyphen in my name, so I can discretely own my last name as a domain, even if the rest of my relatives are SOL.

    --
    --- Will in Seattle - What are you doing to fight the War?
  68. Hrm... by cbwsdot · · Score: 1

    "h t t p : forward slash forward slash slashdot dot dot"

    --

  69. Re:huh? by Sloppy · · Score: 1

    You go to your favorite sex site (foo.sex) and type "group" into their search page.


    ---
    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  70. .sex is lame by AintTooProudToBeg · · Score: 1

    .sex is lame. .adult would be way more "professional".

    I saw Jim at the sex bookstore!
    I saw Jim at the adult bookstore!

  71. Re:.dot and .god? by Captain+Derivative · · Score: 1

    Er... you forgot "slash." Who says a TLD can't be 0x00?


    --

    --

    --
    The real Captain Derivative has a Slashdot ID.

  72. Re:Hmm.... by kubalaa · · Score: 1
    I never did understand why URLs are so mixed up. See what I mean (numbered from highest level in the hierarchy to lowest):

    1. protocol
    4. subdomain (...)
    3. domain
    2. TLD
    5. root
    6. subdirectories
    etc.

    How more ass-backwards can you get? Somebody please tell me there was some reason for this other than crack?

    --

    "If you look 'round the table and can't tell who the sucker is, it's you." -- Quiz Show

  73. character limit's need to be set by zentex · · Score: 1

    i think a max of 3 characters should be set...i mean, c'mon! if not things will get out of control... i can see possibly 4, but really...3 makes more sense...

    i can see a .comonyawannalayme TLD some day if things dont get under wraps...

    ---
    remove SPORK.

    --
    Appended to the end of comments you post. 120 chars.
  74. 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
  75. Re:.dot and .god? by Chris+Pimlott · · Score: 2

    There's already a .at (Austria), go to town...

  76. where's .web? by fixe · · Score: 1

    where's .web?

    1. Re:where's .web? by JBReynolds · · Score: 1

      There are two different .web applicants: Image Online Design and Afilias, a consortium of 19 ICANN registrars.

  77. Re:new TLDs are useless by Billy+Donahue · · Score: 2

    With new TLDs, every company is going to register in any TLD they can. This will lead to exactly the same problem.

    This is exactly what will happen if TLDs are brought in 1, 2, or 3 at a time, with totally meaningless three-letter names. This is one of the strongest reasons why Name.Space has pushed to open up hundreds of new TLDs, with meaningful extensions. If you decide to make TLDs which are actually specific enough to do their job of segmenting the domain space, then you need lots of them.. The more specific, the more you need.. And there is no reason not to add hundreds of them. No reason at all... This is probably the only way will avert a landgrab and a goldrush in the new domain space.

    --
    -- The Funk, The Whole Funk, And Nothing But The Funk
  78. Because FORCING 2nd level regist'ns devalues names by Anonymous Coward · · Score: 1

    If you just drop the TLD, then whoever gets "FOO" has a value commodity that puts us all in the same mess we're in now. Worse even, since there would be only one FOO. And only the owner of .FOO could creste subdomains in foo. Unlimited TLDs, while still requiring registrations to consist of DOMAIN+TLD, keeps choices open by devaluing the inherent worth of any particular TLD.

  79. New Italian Domain? by rfg · · Score: 1

    is .wap the new domain for Italy? They must have run out of the .it names already.

  80. Useful TLDs by Ian+Bicking · · Score: 2
    As other's have mentioned, lots of TLDs won't necessarily help. But they could help. Here's some I think would be good:

    • .movie (since every movie wants its own domain name... cell.movie, excorcist.movie, etc. buy.movie would be dumb, though, and I'd hope they'd keep them out. Maybe .film, definately not both)
    • .museum (field.museum)
    • .law (kurneysmithjones.law or something)
    • .sex (obviously)
    • .game (starcraft.game, etc... only actual games, not sites about games)
    • .coop (wedge.coop)
    • .home (ianbicking.home -- only registration by individuals of their own name or variation on their name... maybe a different TLD, though... .person)
    • .alt (free for all! But it can't mirror any other TLD)
    Ones that might be good are: .art/.gallery, .hotel, .school (.edu might be too restrictive, .k12.xx.us, etc., aren't a great alternative).

    But .web, .dvd, .pro, .biz, .wap, etc., are simply dumb. They are totally ambiguous -- how do you know if something should be a .com, .biz, .ecom, etc? I would be rightfully concerned if I had mybusiness.com and someone else registered mybusiness.ecom. The other TLDs have to actually mean something, and be exclusive of the generic online-business/zine/community/whatever that is .com/.org/.net. If someone registered mybusiness.hotel, it wouldn't really matter to me.
    --

  81. Re:The heck with .dot... what about .FUD by cant_get_a_good_nick · · Score: 1

    Then the big corporations like microsoft.FUD and sun.FUD would have their own play space.

  82. Naming yourself on a bet by ResHippie · · Score: 1
    I noticed a few of the companies volunteering to host the TLDs were founded on that single purpose such as DotKids, Inc. who only wants to host .kids.

    Now that's an interesting bet.

    Does anyone know what power the company will have over their TLD?

    --

    Those who don't know me, probably shouldn't trust me. Those that do know me, DEFINITELY shouldn't trust me.

  83. Re:One feature which we need with these new TLDs. by plague3106 · · Score: 1

    Actually i'm kinda worried that might really happen. Could lead to nasty censorship. imagine if all adult sites had to be in .sex...i think shortly after we'd see some isps blocking that whole tld. .kids would be good, b/c i doubt an isp would block that, and parents could know for sure if the site was kid friendly.

  84. Re:This ain't gonna work by Mr+T · · Score: 2
    I agree. What it means to me is that we don't need TLDs anymore, just do away with them and register domain name like "microsoft" or "slashdot" The .org/.com/.net/.whatever doesn't matter anymore. IBM will still own IBM.* and Microsoft will still buy microsoft.* and sue anybody who was able to get a microsoft.anything as soon as it happened.

    They don't even mean anything anymore. .GOV and .EDU are the only correct TLDs anymore.

    --
    This is my signature. There are many signatures like it but this one is mine..
  85. Re:.xxx? Bravo! by vinci · · Score: 1

    Uhm, who would stop me from registering all kinds of .kids domains and starting porn sites on them?
    No-one, that's the whole problem with blocking TLDs, it only works when people play by the rules, wake up call: they don't ...

    Cheers,
    vinci

    --
    [ http://www.gizmozone.com/ | World's smallest screensaver in 2kB! ]
  86. Re:One feature which we need with these new TLDs. by Pentagram · · Score: 1

    I'd like a couple of "meta-tld's"; .biz and .free (say). All commercial URI's under the former and non-profit sites under the other. And have it enforced.


    ---

  87. 'non-routable' tld? by Dr.Dubious+DDQ · · Score: 1

    (Yes, I know the 'domain name' has nothing to do with the routing itself, but...)

    I was struck by a whacky idea yesterday - how about a '.lan', used to designate a 'local area network' domain (essentially the .tld counterpart to the 192.168.x.x, etc. non-routable IP addresses). In practice, software would be set up to treat any .lan names as 'if it's not in /etc/hosts or on a dns with a non-routable (i.e. on the lan) IP address, don't bother querying any further'.

    Potentially useful, or am I an idiot?
    (And, yes, perhaps that's not an 'or' question :-) )


    Joe Sixpack is dead!
  88. "one company" - "one tld" will fail by Speare · · Score: 2

    Companies who wanted to farm TLDs would just spin off many microcompanies. It's cheap to be a microcompany.

    What definition of a 'company' would you use? SEC "C-Corporation"? LLC? Aunt Gertrude's Bead Jewelry Enterprises? How about international definitions of companies?

    --
    [ .sig file not found ]
  89. For us by phwiffo · · Score: 1

    How about .gay? That way we can segregate ourselves into obilvion.

    --


    Trolls, it must be cool to be that bored.
  90. Re:www.slash.dot? by gfoyle · · Score: 1

    Wouldn't dot@atdot.org be more symetrical? especially if atdot@dotat.org isn't an option.

  91. There already is an equivalent to .alt on opennic by yerricde · · Score: 2

    OpenNIC, the Democratic Name System, has a .null TLD that is often compared to alt. of Usenet.
    <O
    ( \
    XPlay Tetris On Drugs!

    --
    Will I retire or break 10K?
  92. 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 bfree · · Score: 2

      I wanted this exact feature myself for .law

      While I'm at it, someone suggested .gnu or .oss but I think .src would be best (not in list and friendly to a lot more).

      --

      Never underestimate the dark side of the Source

    2. Re:One feature which we need with these new TLDs. by fatphil · · Score: 1

      I love you!
      I've just got rid of bloody ad.doubleclick.net
      Webmail is useful again!

      Phil

      --
      Also FatPhil on SoylentNews, id 863
    3. Re:One feature which we need with these new TLDs. by mikpos · · Score: 2

      This would be a feature best put into the underlying OS, or possibly the proxy server (if one is used).

    4. 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
    5. Re:One feature which we need with these new TLDs. by interiot · · Score: 2

      But then you'd have the same problem as porn blockers... not everyone has the same definition of "spam" or "porn". Granted, the S/N ratio would greatly improve if the ones that qualify under the lowest common denominator definition would be relegated to .ads, but that wouldn't be a complete solution.
      --

  93. How will USians type them? by yerricde · · Score: 2

    Every keyboard and OS in the world supports ASCII (positions U+0000 to U+007F of Unicode 3). Not every keyboard and OS supports Unihan (U+4C00 to U+A000 or something). One generally has to buy CJK input support for common consumer operating systems.
    <O
    ( \
    XPlay Tetris On Drugs!

    --
    Will I retire or break 10K?
  94. The seeds of confusion. by levik · · Score: 1
    I know that a small set of tld's is a completely artificial and contrived concept, but I think that many people have gotten used to the limited choices when it comes to finishing that URL:
    slashdot.org?
    slashdot.com?
    slashdot.net?
    Now with all these new proposals (if they are accepted anyway), it seems like there will be a substantial period of confusion in waiting for the dust to settle.

    Of course international users are more used to this with all the country code TLDs outthere...

    Just my two cents.

    --
    Ñ'
    1. Re:The seeds of confusion. by BradleyUffner · · Score: 1

      That sbring up another good point. Big Companies like Microsoft are going to scurry to get microsoft.??? in ever TLD they can. Soon it's not going to make much of a difference no matter how many TLDs tehre are because everything will lead to the same place.

  95. Re:.xxx? Bravo! by Sloppy · · Score: 2

    Well, if we let commercial sites use .org, then commercial porn sites should be allowed to use .com or .org too.

    Remember that the purpose of names is to make hosts easier to remember, instead of using numbers. It makes it easier to find things, not easier to block things. If I have a not-specifically-sex site, and I post a rant that contains the word "fuck" too many times, or a raytraced picture of a simulated woman with big bouncy hooters, am I going to have to worry about the government telling me to move my site to another domain? I better not.

    This TLD stuff is not a replacement for filters and ratings. It is not mneumonic purposes only!

    BTW, is it just me, or does .xxx seem stupid? .sex is much better, since it is descriptive. "Sex" refers to reproduction and the enjoyable sensations that mother nature gave us to trick us into reproducing. Whereas "XXX" just refers to an obsolete rating that the MPAA used to assign. My guess is that most people who are looking for porn, are completely uninterested in the MPAA.

    "Yeah, everything on this site is XXX. We ran every JPEG by the MPAA, and they said that none of them qualified for an R."


    ---
    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  96. Re:www.slash.dot? by /dev/kev · · Score: 1

    Heh, org.dot@atdot.org would be even better. :)
    Sadly, it's already taken, along with all the other good ones like dot, atdot, atat, etc.

    --
    Quidquid latine dictum sit, altum viditur.
  97. Gotta love ICM Registry, Inc. by wmoyes · · Score: 2

    ICM Registry, Inc. wants both .kids, and .xxx, and nothing else. I am sure congress is going to have a field day with this one.

    1. Re:Gotta love ICM Registry, Inc. by Grahf666 · · Score: 1

      The problem comes when goat.kids redirects to goat.sex. ;)

    2. 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.
    3. Re:Gotta love ICM Registry, Inc. by wmoyes · · Score: 2
      ObDisclaimer: I am not trying to start a flame war, just express my views on censorship. Read the whole post and think about it before you make a fool out of yourself ;)

      I would not mind requiring all explicit adult entertainment sites to register under a particular TLD. I hate accidentally visiting them, and it would be easier to block them if they were labeled before I click on the link (or worse yet, sent their by some JavaScript).

      I agree that censorware has too many problems, I am not a fan of censorship, but I would appreciate a warning before I have something I might object to displayed on my screen. If I really want to see it, so be it. But if I really don't, at least warn me first.

      Classic example: I am looking up information regarding a new security exploit, and some 31137 kiddie's web site pops open 200 windows of XXX porn. Not appreciated. I have ended up disabling JavaScript, Java, and automatic loading of pictures while visiting sites that might pull this stunt.

      But back to the point. I don't really want censorship, but I do want user selectable blocking. If _I_ don't want to see it, ask me for my permission. Censorship is when someone else tells me _I_ can't see it. When I tell them I don't want to see it, its just another preference menu.

    4. Re:Gotta love ICM Registry, Inc. by jvj24601 · · Score: 1

      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?

      Why not? If a family wants to make sure that their kids don't get to these domains, I'm sure that this could be a marketing idea for family-type ISP's.

      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.

      This is a valid concern. I mean, what's to stop some porn shop registering www.ilovewomenthatlooklike.kids or something like that. A .kids would only work if it were regulated (not that I support such regulation).

    5. Re:Gotta love ICM Registry, Inc. by John+Napkintosh · · Score: 1

      I think there should be some committee that decides what your TLD should be based on your content. I don't like having to worry about whether or not that site I'm trying to go to at work is porn or not, so that might help out.

      As for ISPs blocking sites based on TLD, think of the current situation. If any ISP was not offering unrestricted net access, how many customers do you really think they would be able to keep? There are those who have no shame and will happily call an ISP to claim that they ISP is the reason that they can't get their porn, so after word gets out that they don't offer unrestricted access, they won't be sittin' too pretty.

      --

      Long signatures suck.
    6. Re:Gotta love ICM Registry, Inc. by lizrd · · Score: 1
      Why not? If a family wants to make sure that their kids don't get to these domains, I'm sure that this could be a marketing idea for family-type ISP's.

      I have to agree that some of these new TLDs would be great for marketing, both by ISPs and by websites. It certianly would be handy to be able to accurately guess in advance that goat.kids is going to be really different from goat.sex. What concerns me most about ISPs deciding not to accept certian TLDs is that the ones that choose to provide full access will become the net equivalent of adult shops. This could quickly turn into a nasty bit of regulation (i.e. Such ISPs may not conduct business within 500 meters of any school, church or daycare center. Hours of operation will be limited to 7PM-midnight Monday thru Saturday...)

      I'm not saying that any of this will happen, just that it could if things aren't handled properly. And then internet being what it is there is always a slippery slope.
      ________________
      They're - They are
      Their - Belonging to them

      --
      I don't want free as in beer. I just want free beer.
  98. bad fingers! bad! by Sloppy · · Score: 1

    s/It is not mneumonic purposes only!/It is for mneumonic purposes only!/


    ---
    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  99. huh? by Coward+Anonymous · · Score: 1

    Ok, so there is .group and there is .sex but where do I look if I'm interested in group sex?

  100. Re:Name.Space by Nailer · · Score: 1

    > having both .sex and .xxx is a bit redundant

    But not completely redundant. There are some important differences which is why I wouldn't like to see .sex implemented. `Sex' is a larger category, and would classify things like sex education, which IMHO should be rated differently from from pornography [which would be the field of endeavor of the .xxx domain].

    There a difference between a sex education column for teenagers, and adult products site, a community for hedonists, and a porno site. Though, as with all other TLDs, that distinction is blurry. A fundamentalist christian would perhaps find the sex education column to be pornographic, other fiond the use of marital aids offensive, and sites like nerve.com bl;ur the lines between erotica and porn.

  101. Re:Wireless Application Protocol by ToiletDuk · · Score: 1
    Is it just me, or does everybody except you seem to understand that top level domains go at the END of the domain name, not the beginning. wap.slashdot.org != www.slashdot.wap
    • _____

    • ToiletDuk (58% Slashdot Pure)
  102. Reading... by Mancide · · Score: 1

    How about actually reading a story before writing a summary about it next time? But, if someone at /. did that, then it wouldn't be a /. post now would it?

    Kinda like that proofreading story a few days ago...

    --
    "This amp is special, see all the knobs go up to 11, that means it is one louder than other amps"
  103. Re:Name.Space by Nailer · · Score: 1

    Sorry, hit `submit' to early...

    The reason why I prefer .xxx is because that way the sites that believe they are pornography [ie, persiankitty type sites] can use their .xxx domain as an advertising tool, and those who'd prefer not to see these sites get the option to ban at least those who label themselves as porn, but not all sex related sites per se [and prevent access to what may be some valuable information]. For example, a high school could ban all .xxx access, but if .sex existed [and they decided to ban it], they would be throwing out info about contraceptives.

  104. Too many! by AdamHaun · · Score: 2

    .aids? .shoes?

    The whole point of the DNS is to create a hierarchial naming system. If the roots of the hierarchy are going to be this numerous, it defeats the point of having a TLD at all.

    What is needed is for the people buying domain names *cough*corporations*cough* to stick to the suitable hierarchy. Owning ford.org is perfectly legitimate if I happen to run the Betty Ford center. Try to fix the system before you destroy it altogether.

    --
    Visit the
  105. Re:Need special tld's for scriptkiddies and hax0rs by Nailer · · Score: 1

    m37hink5 j00 m34n .n37!!!!!@@@@!!111112222!!!@@!

  106. Are the good folks at www.TV ballot stuffing? by disc-chord · · Score: 1

    I was noticing odd applicant names like:
    The dotPRO Consortium
    The dotNOM Consortium

    so I started looking a little closer and this is what I found:
    .pro
    The dotPRO Consortium
    130 W. Union Street
    Pasadena, California 91103 USA
    +1 626 685-4904
    a@www.tv
    The .TV Corporation International
    130 W. Union Street
    Pasadena, California 91103 USA
    +1 626 685-4904
    a@www.tv

    .nom
    The dotNOM Consortium
    130 W. Union Street
    Pasadena, California 91103 USA
    +1 626 685-4904
    a@www.tv
    The .TV Corporation International
    130 W. Union Street
    Pasadena, California 91103 USA
    +1 626 685-4904
    a@www.tv

    Two identical Addresses from 2 different "organizations" both suggesting the same exact domains... but that's not all folks. Take a closer look and you'll notice that ALL the people that suggested .nom also suggested .pro ...
    Lycos, Inc, SK Telecom, XO Communications, Inc. (formerly Concentric Network, OnlineNIC, Inc., 7DC

    Wonder what's up with this? WTF is a .nom for anyhow? Why would Concentric, Lycos and some guys in Korea both all want it?

    disc-chord
    "Though we say, 'all information should be free', it is not. Information is power and currency in the digital world we inhabit."-Billy Idol(1994)

  107. Re:*blink* by Chris+Pimlott · · Score: 2

    Yes, but the entry requirements are rather high. You have to be an organization founded/recognized by international treaty.

    My dream is to have 31337.int.

    Would require a little more pull than I have right now though...

  108. Whoa, I found .dot!!! by AFCArchvile · · Score: 1
    Here's the applicant (get a pen, Taco):

    JVTeam, LLC

    1120 Vermont Avenue., NW Washington, DC 20005 USA +1 202 533-2600
    --
    "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
  109. Re:.xxx? Bravo! by Nailer · · Score: 1

    .XXX is actually a fairly good internation description of merdi of an adult nature, and is used over the world by many more organizations than the MPAA.

  110. .everythinginthedictionary by Vspirit · · Score: 1
    who are this to help?

    the common user who one see to help, would be more confused than ever.

    but ok, the searchengine business will flourish..

  111. Re:*blink* by Chris+Pimlott · · Score: 2

    (by the way if there are any major world leaders reading that would be willing to help me out, please email me)

  112. How about by WinDoze · · Score: 1

    .katz? Then we could filter him as easily as .sex!

  113. .reallylongtld's by cetan · · Score: 1

    How much of a good idea is creating really long TLD's?

    Maybe I'm lame (*probably*) but I think sticking with 3 characters is a Good Thing(tm). Just when the unwashed masses are getting the hang of .com v.s. .net v.s. .org v.s. .gov etc. do we really want to throw .heylookatthistld out there?

    --
    In Soviet Russia...michael would be rotting in Siberia!
    1. Re: .reallylongtld's by cetan · · Score: 2

      That's it!

      Why isn't there an .etc TLD?!

      --
      In Soviet Russia...michael would be rotting in Siberia!
  114. Re:Because FORCING 2nd level regist'ns devalues na by mikpos · · Score: 2
    His method seems to get around that by not having an incentive to make silly TLDs. e.g. you couldn't have http://applerecords because you need both a TLD and a domain-name. You could register applerecords.applerecords, but you probably wouldn't because you'd end up looking like a moron. So you'd probably opt for apple.records instead.

    This brings up the issue of typo TLD squatting. Maybe I don't like Apple Records so I register apple.recodrs with a bunch of FUD about them. However, there's no advantage to having apple.recodrs over, say, spple.records, so it's not any worse than the current system in terms of typo squatting (though it's not any better either). I haven't been bothered too much (or bothered at all for that matter) by typo squatting so far.

  115. Re:Hmm.... by titus-g · · Score: 1
    and combine that with an app (and an update to BIND) that will let you query DNS servers, say

    nslookup -list software.open.linux.browsers

    and get a listing of all the sites and subcategories under that, e.g.

    software.open.linux.browsers.galeon
    software.open.linux.browsers.mozilla
    ...

    Possibly adding a brief description (possibly keywords as well, although they tend to get abused) of the site to the DNS record.

    And you have a massive distributed directory of all websites (except IP address ones), not just the 30% (?) currently indexed by search engines and directories.

    --

    ~ppppppppö

  116. Cool, SCO can register SCO.xxx! by Nailer · · Score: 1

    Well, they put binaries in /etc, don't they :-)

  117. .go as a gTLD??? by ectoraige · · Score: 1
    Hang on a moment, were they even THINKING when they came up with this?

    There are a set of what are called "top-level domain names" (TLDs). These are the generic TLDs (EDU, COM, NET, ORG, GOV, MIL, and INT), and the two letter country codes from ISO-3166. ( RFC 1591)

    The .go gTLD should not be delegated for the following, simple reason:
    Assume, for arguments sake that the Golan Heights declare themselves an independent nation, are internationally accepted, and ISO assign them a ISO 3166-1-Alpha-2 code of GO. Since ICANN assign ccTLDs based on the ISO-3166 list, this would cause an obvious conflict. This is precisely the reason all the gTLDs are three letters long and ccTLDs two letters long. Obviously those people in Dubai didn't have their thinking caps on. Allowing .go would be a dangerous precedence and should not happen.

    Oh yeah, and before anyone mentions it, the very next line from RFC 1591 is "It is extremely unlikely that any other TLDs will be created.". Just goes to show...

    "A goldfish was his muse, eternally amused"

    --
    Vs lbh pna ernq guvf, ybt bss abj. Tb bhgfvqr. Syl n xvgr.
  118. 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.
    1. Re:Why limit tld's? by juliao · · Score: 1
      Just make it so one company can't own more than one tld.

      And where does that leave us? With .cars being owned by Ford, and .vehicles being owned by "The .Vehicles Consortium, a wholly owned subsidiary of Ford Motors", and .motorcars being owned by "The .motorcars Consortium, a wholly owned subsidiary of Ford Motors", and...
    2. Re:Why limit tld's? by Wellspring · · Score: 2
      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.

      Exactly, Burn all TLDs. Then you could have a cooperative system for having nameservers refer to one another. Are the TLD's on a given nameserver encroaching on an assigned TLD? (Conflicting name assignments is AFAIK the only argument against unlimited TLDs) Then the other referring nameservers would just give them the equivalent of the Usenet Death Penalty.

      This way, you could have .dot or .slashdot or whatever. You just register TLDs as if they were Domain Names, because that is effectively what they then become. And you would avoid much of the bureaucratic and authoritarian nonsense we're seeing from ICANN lately.

  119. 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 magic · · Score: 2
      This is actually how URL's work in England (and maybe all of Europe?). Software translates them back and forth between English and US style. I think URL's are always displayed US style in UI's these days, however.

      com.microsoft.www makes a lot more sense. Also, this fits nicely with schemes like Java's name space, where your piece of a namespace begins with your URL. For example, when sun releases new Java packages, they go in the package named com.sun.*.

      -m

    2. Re:Hmm.... by timftbf · · Score: 1

      Erm.. no. *{host|domain}names* on the UK *acadmic* network (JANET) used to be 'back-to-front', and ISTR it caused more confusion with email than anything else.

      It was running in parallel (uk.ac.ukc and ukc.ac.uk both worked) when I was at uni (about 8-9 years ago), and I believe JANET now fully believes in names in the same direction as everyone else.

      The commercial UK Internet has always been the 'right' way around.

      Regards,
      Tim.

    3. Re:Hmm.... by Peter+Millerchip · · Score: 1

      Actually, here in the UK domain names are written in exactly the same way as the rest of the world (i.e. I am posting to slashdot.org and not org.slashdot).

      What I believe you are referring to is the early days of JANET, the UK's Joint Academic Network, which links all of the universities together (the *.ac.uk domain). Early on, that used the "reverse style" domain names that you were talking about, but they changed over to the correct style sometime around 1991 (if I remember correctly).

      This is from memory - the only net access I had when it changed was from Uni, so it may well have been the whole UK (please correct me if I'm wrong!) But the whole point is that the UK has been using "correct" URLs and domain names for nearly yen years now!

    4. Re:Hmm.... by juliao · · Score: 1

      I personally don't see much of a difference between org.news and com.news, for that matter... TLDs as we know them have stopped making much sense a long time ago. How about starting to make them useful, for a change?

    5. 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
    6. Re:Hmm.... by spinfire · · Score: 1
      Part of the problem with this is as you propose it is that people are used to the TLD part at the end, unless they are usenet geeks. Personally, i am in favor of doing this in a similar way, a la:

      thematrix.movies.net vs. whatisthematrix.com
      or...
      dpn.random-moronic-personal-sites.com instead of dpn.com

      This is similar to the usenet system, and would still be intuitive to most internet users (IE, slashdot.news.org, nytimes.news.org). Many sites already do this, but it needs to be accepted by the business oriented folk to catch on.

  120. What will happen? by icezip · · Score: 1

    If you notice some tv ads don't include the http:// part. People assume if it ends in dot-com its a web site. When i see something that ends in more than three letters, I assume its a news group. At least keep it three letters, I mean can you imagine www.DrSmith.medicaldoctor? I do however like the idea of h-t-t-p-colon-slash-slash-slash-dot-dot-dot (http://slashdot.dot)

  121. What about 2LDs? by Twylite · · Score: 1

    Everyone knows that its .cool to have a .com . But whatever happened to 2LDs, and does anyone have an inkling of what this is going to do to them? Take my home country's .za domain for example. We have the usual .org.za and .co.za 2LDs for orgs and cos in South Africa. Simple. But not so simple, because some people didn't like the existing system, and got hold of .za.org and .za.com and started up a separate registry. Enter .web, .shop, .bank, .dot, .mother, .sister, .dog, and you have a .mess . The intent of the country domains was to have .com, .net and .org as US or international, and everything else in a country domain. This has already gone to all hell, why let it go further? More TLDs also screw the little guy - so you have an e-shop proferring your petty wares (no, not warez), and you have a limited budget. Do you get a .shop, .com, .eretailer, .biz, .ebiz, .ecom, or all of the above? First pay your registration fee times 6, then your hosting fee times 6, and if you don't then someone is going to use your name with a different TLD.

    --
    i-name =twylite [http://public.xdi.org/=twylite], see idcommons.net
  122. .patent ??? by MolGOLD · · Score: 1

    I hereby parent the .patent TLD Any patents that get any exposure on the web, or involve internet technology must hereby pay me a royalty ;)

    --
    "Life ain't interesting till you blow something up" --Anonymous
  123. strlen(TLD) != 3 ? by jeavis · · Score: 1

    This is probably a moot point by now, but in my opinion allowing new TLDs to vary in length is not a good idea. I'm reminded of when the FCC started expanding area codes, and some PBXes were unable to place calls to those numbers because the second digit of the area code was not a 1 or 0. I can't help but wonder just how much software out there depends on the TLD being exactly 3 letters (or 2 for ccTLDs) and will break with confronted with www.disney.kids or www.barnesandnoble.store.

  124. There has to be a country name (Re:Trademarks by Punto · · Score: 1
    .tm sounds like a TLD that would be assigned to a country.. Isn't it taken yet? "TroMelin island"? "TurkMenistan"?

    It'd be cool to create a new country on a little island with a name like that, just to start selling domains..

    --

    --

    --
    Stay tuned for some shock and awe coming right up after this messages!

  125. Re:www.slash.dot? by TheNottledimKid · · Score: 1

    Just to make it clear slahdot should change the wwww bit to slash: i.e. slash.slashdot.dot Dotty eh?

    --
    TheNottledimKid
  126. I don't see '.dot'! Com'on! by kenf · · Score: 1

    You did not look hard enough, its there.

  127. new tld by nut · · Score: 1

    How about .hack?
    :-)

    --
    Never trust a man in a blue trench coat, Never drive a car when you're dead
  128. .nyc? by TheKingAnt · · Score: 2

    As in New York City? What happened to .ny.us.whatever?

    1. Re:.nyc? by Evangelion · · Score: 1


      The ny.us etc domains are regulated by state and regional buearcracies. .nyc wouldn't be.

      There you go.

      I know I can't fucking spell, so don't bother.
      --

  129. Name.Space by sugarman · · Score: 2
    Do these guys even have a clue? Jeezus, I'm debating sending them my own copy of O'Reilly's "DNS & Bind" just to bring them up to speed.

    For the most part, the pther requests seem even and measured, thoguh I might urge some consolidation (eg, having both .sex and .xxx is a bit redundant; same goes for some of the other categories)

    But Name.Space looks like the largest group of domain-squatting vultures I've seen. I'm thinking they should be unilaterally rejected just to prove a point.

    --
    --sugarman--
  130. .xxx? Bravo! by Wog · · Score: 1

    It's about time this happened. If all pornographic sites would move to .xxx or .sex then blocking objectionable content would be simple. All it would take to keep kids away from the stuff is a switch in the browser: "Block .xxx domains."

    The question that will inevitably come up is, is it wrong to force adult sites to move to a new TLD?

    1. Re:.xxx? Bravo! by uksv29 · · Score: 1

      Its all very well having TLDs for sex etc. The problem is defining what goes in each and trying to enforce it.

      The problem is that the Internet is world wide and the different countries each have their own standards for what is acceptable. If ICANN or a registry try to apply a given standard for decency they would (rightly) be accused of trying to force the rest of the world into their standards of ethics, morals and decency. And in the case of ICANN charges of American Imperialism would me made. Imagine trying to come up with a definition of pornography which would be acceptable to Iran, China, France and the US.

      There would also be cases where a commercial organisation would wish to have a TLD which others would think inappropriate. Who defines what it right?

      I forsee lots of trouble ahead ...

    2. Re:.xxx? Bravo! by boboroshi · · Score: 1

      The idea of .xxx or .sex and the use of them points to two things in my mind:

      1.) a better way for the determining of content. Of course this would require legislation and therefore yet another agency reviewing usage of any given site applying for some domain. We've already got enough government. And honestly, is whitehouse.com going to give up that easily? Doubtful at best.

      2.) just another way for monitoring/censoring software to restrict content. boo hiss

      I agree we need some new ones, but some of these are completely ludicrous. Can i get .bobo? please?


      // john athayde
      # x@boboroshi.com
      # http://www.boboroshi.com/
      --
      // john athayde
      # x@boboroshi.com
      # http://www.boboroshi.com/
  131. Email address of the month. by l-ascorbic · · Score: 1

    Look at June 2000: someone's done it.

  132. Re:.dot and .god? by ptomblin · · Score: 1

    Yes, I know, but dot@dotat.at is already gone. So is atdotcom@dotcomat.com.

    --
    The next Cmdr Taco duplicate will be ready soon, but subscribers can beat the rush and see it early!
  133. lol by ctm · · Score: 1
    dubai
    .go

    Proposed by
    Dubai Technology, Electronic Commerce and
    Media Free Zone Authority
    Lars Olof Kanngard
    P.O. Box 73000
    Dubai, UAE
    +9714 3998888
    icann@dubaiinternetcity.com

    why not .amazon and .slashdot while we're at it

  134. Need special tld's for scriptkiddies and hax0rs by alhaz · · Score: 2

    .c0m and .n3t should do it :)

    --
    This is just like television, only you can see much further.
  135. Re:Dumb by Billy+Donahue · · Score: 2


    Why should they pay you anything?
    It's your silly broken software..
    The world changes.. Deal with it.
    No one owes you anything.

    --
    -- The Funk, The Whole Funk, And Nothing But The Funk
  136. My preffered (drum roll)... by f5426 · · Score: 1

    From Name.Space, Incorporated:

    .sucks

    From Rathbawn Computers Limited

    .sansansan

    Nice TLDs, indeed

    Cheers,

    --fred

    --

    1 reply beneath your current threshold.

  137. Oh, please. by Carme · · Score: 1

    .three33? .sansansan?

    I thought TLD's are supposed to be categorical, for general use applications. I'd like to know what the crackheads at Rathbawn Computers Limited are thinking of doing with these...

    Someone should tell them to go register a couple of SLD and quit wasting their $50k.

  138. .wap: NO by Trinition · · Score: 1
    .wap would not be a good TLD. WAP is usually a reformatting of rehular information. Such information can usually be optained in either WWW/HTML or WAP, and in the future, even further formats.

    Instead, let's use names like http://wap.slashdot.org.

  139. so, some company gets to classify web content? by heckler+spray · · Score: 1

    So let me get this straight- some company in New York or San Diego gets to decide how to classify content on the web? That's nuts! IFLA or the Library of Congress should be the ones deciding new categories of information, not "Name.Space, Incorporated". .shoes? C'mon!

  140. .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

    1. Re:.dot and .god? by Tet · · Score: 2
      I want atdotdot@dotdotat.dot

      It's already been done along similar lines. There's a guy in Austria with the email address dot#dot.at (obviously, replace the # with an @ to get the unspamproofed version -- then try saying it out loud).

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    2. Re:.dot and .god? by quasipunk+guy · · Score: 1
      Erm, not to spoil your fun, but there's already a "." domain. It's what com, net, org, and all the other tld's are under. Try http://www.kuro5hin.org./, it'll work.

      If .slash was registered, .slash. would exist, obviously.

      This is also good for defeating most internet filters...

      -tsunake

    3. Re:.dot and .god? by ptomblin · · Score: 1

      I want atdotdot@dotdotat.dot

      --
      The next Cmdr Taco duplicate will be ready soon, but subscribers can beat the rush and see it early!
    4. Re:.dot and .god? by TheTomcat · · Score: 2

      I've said it before, but Rob wants:
      http://slashdot.dot/
      (H-T-T-P-COLON-SLASH-SLASH-SLASH-DOT-DOT-DOT)

    5. Re:.dot and .god? by retinaburn · · Score: 1

      Too bad he cannot get
      http://slashdot.slash
      (H-T-T-P-COLON-SLASH-SLASH-SLASH-DOT-DOT-SLASH)
      If you changed the slash's to dashs what is that in morse code.
      "Useless post #1 of the day for me"
      --Me

    6. Re:.dot and .god? by kzinti · · Score: 2

      I've said it before, but Rob wants: http://slashdot.dot/ (H-T-T-P-COLON-SLASH-SLASH-SLASH-DOT-DOT-DOT)

      Oh, well, that's the Italian form; the Elizibethan goes H-T-T-P-COLON-SLASH-COLON-SLASH-DOT-DOT.

      --Jim

    7. Re:.dot and .god? by BlowCat · · Score: 1

      I'm the dot in .God

    8. Re:.dot and .god? by bmongar · · Score: 1

      how about elipsis.dod

      --
      As x approaches total apathy I couldn't care less.
    9. Re:.dot and .god? by mikpos · · Score: 2

      Well he could get slash.dot and then have a host in there called "slashdot.slash.dot" which would then come out as "aytch tee tee pee colon slash slash slash dot dot slash dot dot". You could really go nuts making subdomains if you wanted, though I don't think anyone would actually bother to put in a non-sensical string of dozens of "slash"s, "slashdots" and "dots" placed randomly and delimited by dots. http://slashdot.dot.slash.slash.dot.dot.dot.slashd ot.slashdot.slash.dot.dot.slashdot.slash .dot". Loads of fun.

    10. Re:.dot and .god? by JBReynolds · · Score: 1

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

      Presumably, he didn't feel like spending the $50K to apply.

  141. what about? by Mabonus · · Score: 1

    Perhaps .dotdot

    Just think! "I'll see you at evilspace..."

    mwuhuhahahaua

    See, a person is left hanging, waiting for the punch line, the ending threat, but on the sly, you find it's an actual website...

    1. Re:what about? by Wog · · Score: 1

      Just think:

      "Just go to double U double U double U dot Slash dot dot dot dot!"

  142. er... by Wakko+Warner · · Score: 1
    ...what the hell good would ".dot" be?

    --
    * CmdrTaco is an idiot.

    --
    "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
    1. Re:er... by null-und-eins · · Score: 1

      For SUN? They claim they are the DOT.

      --
      At the beginning was at.
  143. Dumb by voidptr · · Score: 2
    This is absurd. I think it's time for someone to seriously look at starting a 'pirate' DNS service again, just to wrest control away from ICANN. They've turned the entire DNS structure into a farce. Did anyone else pay attention to what you had to do to suggest a new domain? US$50,000, which doesn't even guarantee you anything. And if two companies suggest the same thing, which one gets control? Seems to me the one that looses their 50k is gonna be pissed.

    What we've aparently got now is ICANN creating a horde of mega-squatters who can afford it. And now that we've finally gotten control of the registry away from NSI, we're going to have a whole bunch of little registrar monopolies shooting up offering domains under their space. (Excepting those that just want it to have their own TLD just for them). You can bet that they aren't going to be as competitive as the ones offering .[net|org|com] are right now.

    The big companies will just buy company.*, which defeats the point. If you actually manage to buy Microsoft.sux before they do, they'll just sue you into oblivion anyway.

    Lastly, there's alot of software out there that validates hostnames by some pretty specific rules. 4+ character TLDs with dashes and numbers are going to break all that. Are the companies that just bought .my1st-tld going to pay me for the time it takes to fix those checks in my company's software?

    --
    This .sig for unofficial government use only. Official use subject to $500 fine.
  144. Re:This ain't gonna work by timftbf · · Score: 1

    Some of .uk is still something other than a cesspit. A given company gets exactly one .ltd.uk - the name of the limited company, as registered at Companies House. (Likewise for .plc/PLCs) .ltd.uk deserves more recognition as a nice, well-regulated part of the namespace.

    .se is similarly tightly controlled, and .it also to some degree.

    Regards,
    Tim.

  145. Is there a proposal to enforce the TLD's use? by SpookyGuru · · Score: 1

    Making .kids and .sex TLD's is a great idea, but is there any proposed way to enforce that a site like young.kids doesn't become an under aged porn site?

    1. Re:Is there a proposal to enforce the TLD's use? by Carbonite · · Score: 1

      Sure, there's a few ways that I see. - Bots could check the .kids domain for any "keywords" that may signal inappropriate content. These could then be checked out by real live people. - Parents (or anyone else) could report these to a .kids content commitee. They would be able to levy large fines if a .kids site has adult content. - Theses pr0n sites won't have any reason to invade .kids since kids won't provide any revenue (no credit cards) and parents will go ape. Plus, it's just wrong.

      --
      ich muß mehr Kuhglocke haben
    2. 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

  146. 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
    1. Re:www.slash.dot? by /dev/kev · · Score: 2

      Obviously, the same way you tell someone your email is atdot@atdot.org :)

      --
      Quidquid latine dictum sit, altum viditur.
    2. Re:www.slash.dot? by qux.net · · Score: 1

      I believe the classic one like that is dot@dotat.at...

  147. Erk. by slothdog · · Score: 1

    Does it frighten anyone else that a few applicants applied for *both* [.kids|.fam] and .xxx ?

  148. They're missing another important TLD by vaxzilla · · Score: 1

    What about .orama?

  149. *blink* by Stonehand · · Score: 2

    Some of these just seem silly. Actually, a lot do...

    ".three33" ?
    ".air" -- what, now industry-specific domains?
    ".cool" -- Um, right.
    ".museum" -- why, oh why, would they need an entire TLD ? What, .org isn't big enough for 'em?

    A lot just seemed aimed at grabbing a piece of the pie -- especially coming from those corps that appear to be registrars, and choose a TLD named after themselves. And the folks at Name.Space, well, my thoughts on them aren't exactly polite...

    But some are interesting.

    ".global" -- makes sense for multinats orgs/corps.
    ".mobile" -- Hrm. Perhaps.
    ".kids" -- Hm. If they have a decent TOS/AUP requirement to allow booting the obvious kiddie-porn domains...
    ".xxx" -- if there's an incentive for porn operators to use it, rather than just .com. I'm not sure what that would be, short of legislative action, however, and that'd have to be done through treaties or agreements between all registrars...

    --
    Only the dead have seen the end of war.
    1. Re:*blink* by don_carnage · · Score: 1
      Sounds like some companies are trying to get a jump-start on some new products / marketing schemes. yuk!

      .pretzelyummies
      .cooldraftbeer
      .hotmonkeylove
      ;

      This has the potential to get as ridiculous as newsgroups...

      --

  150. Ok, let's do it .. by hygelic · · Score: 1

    Let's stop talking about this, and let's get it done. This process is taking MUCH too long. We should have had new .tlds a LONG time ago. -cfm

  151. Why limit TLDs at all? by null-und-eins · · Score: 1

    Just wondering: why are TLDs limited? Why can't I buy a TLD like I can buy any other domain? Having your own TLD would no longer force you to buy domain names under TLDs in order to prevent abuse of your name and the like. Sure, giving away a new TLD from time to time is a nice revenue source.

    --
    At the beginning was at.
  152. The good, the bad and the ugly by ozbird · · Score: 1

    There's some very good suggestions in here, but some downright silly ones. I'm surprised that ".ego", ".l33t" and ".patented" didn't rate a mention.

    I'm amused by "other portions of application claimed confidential" - a confidential TLD kind of defeats the purpose, doesn't it? (And what the heck are ".sansansan" and ".three33" supposed to be?)

    Being able to filter out all ".ad" sites would be nice, but I doubt you'll ever keep the TLDs focused enough for that (just look at the .net and .org commercial sites.)

    ".nyc" is rather narrow focused, but was suggested a number of times. Perhaps ".(three letter airport code)" would be a more useful set of international TLDs.

  153. Ick... American Spelling by PurpleKarma · · Score: 1
    Didn't anybody else notice that at least two of the TLD's were spelled using American spelling?

    e.g. "Theater" and "Center".

    Sorry, but I can't help but wonder if the British spellings of these words aren't in more widespread use.

    --

    --

    --
    eek. eek. eeeeeek. eek-eek.
  154. Some Name Changes... by sconeu · · Score: 1

    Some of those companies will have to change their names if they don't get the TLDs... DotKids, Inc, and dotlaw come to mind.

    --
    General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
  155. .id by Tomcat666 · · Score: 1

    What about a new TLD .id for all id software games?
    There are TLDs for countries like Liechtenstein (.li) or Luxemburg (.lu)...
    countries that are so small that they have, like, 10 servers using the TLDs... (no offense :)
    But if we moved all sites about id software games to .id, ICANN would see we really needed it. =)

    --
    Two Worlds - One Sun [Spirit]
  156. .linux? by Jester998 · · Score: 1

    Where the hell is .linux? Or .hacker or something?? Us hackers (geeks???) should have our own TLD. What do YOU think?

  157. There is a .dot by mistah_monkey · · Score: 1

    The company 'NeuStar' requested the .dot TLD. Check it out, Taco...

    --
    -------------------------------------------------- -------
    I bent my wookie
  158. Re:Oh, come on! by AFCArchvile · · Score: 2

    At least give me credit for using the DIV tag to properly display the mailing address! All those other ninnies did was cut and paste!

    --
    "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
  159. new TLDs are useless by spinfire · · Score: 2
    Adding more TLDs will only compound an existing problem. Anyone who has ever registered a domain would note that most registrars encourage registering of domains in every possible TLD. Here is where the problem is. If people were forced to actually obey the 'rules', .com for companies, .net for networks, .org for non-profit, etc, then the domain situation would perhaps be better off.

    With new TLDs, every company is going to register in any TLD they can. This will lead to exactly the same problem.

    1. Re:new TLDs are useless by Billy+Donahue · · Score: 2

      I'm personally not a money hungry domain registrar. I'm an individual hacker, like the rest of us. I've had stories posted to Slashdot. I've got a lot to say about issues that affect you and me.

      Either add to the discussion or shut up.
      Why can't you reply to my point, instead of
      wishing that I'll go away? My point was that the TLD namespace needs RAPID expansion to avoid a landrush by trademark interests and domain hoarders. I'll be satisfied when I see that happen in a democratic and fair way. Trickling new TLDs in one at a time, each 'owned' by a different registry is not my idea of democracy or fairness.

      --
      -- The Funk, The Whole Funk, And Nothing But The Funk
  160. A Couple of Observations by Cy+Guy · · Score: 2
    1. Almost all the suggested TLDs that are words are English words.
    2. I guess there was no requirement that they be any specific length. I had thought they at least had to be 3 letters, but there is .i .go and .yp
    3. Shouldn't 2 character TLD's be reserved for Country Domains?
    4. There didn't seem to be a restriction on characters used (other than starting with a letter) as there is .three33 and .co-op
    5. The list is not complete as one of the submitters list says "other portions of application claimed confidential"
    6. Based on the number of times they were suggested, I guess .nom and .tel will make it in
    7. I thought .buy had been talked about frequently, but no one suggested it.


    I think the the .i is the most inventive, but you might as well have the whole alphabet.

    1. Re:A Couple of Observations by Cy+Guy · · Score: 2

      My own suggestions:

      .slash
      (in addition to /. could be used for fan-fiction)

      .tld

      .url

      .www (as well as .ftp .nntp .smtp etc.)

      .etc

      .ssl

      .phd, .cpa & .lld (there's already a .md, so it would only be fair. Wait, add .ianal while you're at it)

      .spam

      .oss

      .linux .bsd .os2

      Of those that were suggested, I call dibs on deer.xing and shark.fin

  161. Re:New TLDs aren't going to help anything! by eightball · · Score: 1

    I had to respond to at least one of these comments like this..
    It will not solve domain problems like penicillin used to solve many infections, but that doesn't mean it isn't going help.
    There are big differences in how things work now and how they could (and to some degree will without question) work with this system.
    Right now, with very few TLD's (except for the almost unusable country codes), a company could more easily make the argument that their organization on the net is also a commercial business.. : P
    With many more TLD, it would be much harder to make those arguments. So for example in your example, if Amazon contests a native held amazon.tribes, their argument would hold no water. In any case, the basis of ownership is exclusivity.. The basis of capitalism is invention.. Companies have shown lots of in recent years coming up with names that are catchy and easy to remember, even while the dictionary names disappeared.. Are you worried about amazon.sex, even though you were there and they had none.. Anyway, I could ramble about that for a while, but I don't see that squatting is going to happen nearly as much as today (relative amounts that is)
    Yes it would be great if companies and people who had nothing to do with commerce, networks or non-profits didn't buy them, but it is also much easier to do now with only 3 major TLDs to horde.
    Why don't we put together a blue ribbon panel.. no an Inquisition.. and we'll put you as the head and you will check each application to make sure that porn shops aren't trying to buy .art domains
    Good enough for government work........

  162. uh...hello? by MemeRot · · Score: 1

    Sectioning off of the web by content concerns you? You mean like with internet providers having sites that end in .net? And companies having sites that end in .com?

    I do see your point about censorware. But really, I am personally sick of being redirected to porn sites, having them pop up a billion ads etc. Also sick of sites that host doubleclick or whatever sneaking their cookies onto my machine. If the ad companies had to serve up ads from a .ads tld and the porn sites had to end with .xxx then I would be able to control my browser, which is something I should be able to do now, by blocking those extensions. What sucks more than what you're afraid of is the current system whereby you a) personally review every cookie, which is a pain in the ass and a job better done by a machine or b) let doubleclick track your movements across their affiliate sites. Cookies were only supposed to be accepted from the site you are at. Not from doubleclicks remote servers. This was not enforced or built into the system. Well here's a possible way to fix that. I don't mind looking at doubleclick's ads. But i don't want to be tracked by them, period. I'm in favor of anything that empowers the user to control their experience, and i think this does that.

  163. New TLDs aren't going to help anything! by atomly · · Score: 2

    Don't they realize that no matter how many TLDs they add, companies are still going to buy them. Amazon will buy amazon.stupidfuckingtld if they have to just so that nobody else has it.

    The real solution would be to limit the number of domains that people can have, but we know that won't happen, and if it did it would only hurt smaller people and the big companies would find a loophole in it.

    I wish we could make it so that companies couldn't have .ORGs and only ISPs could have .NETs, but that won't happen any time soon.

    --
    -- atomly :: atomly(at)atomly(dot)com :: http://www.atomly.com/
  164. Re:.dot by tolan's+my+name · · Score: 1

    while we're thinking about this, '. ' [ie dot, or dot space] seems to be a well formed TLD, so we could have slash.
    .....well it works for me

    On a more serious note the .sex, .xxx domains seem to be a good idea, and should avaoid all those 'accidental' visits to porn sites

  165. not censoring if I choose it by MemeRot · · Score: 1

    If I choose to not go to any site ending in .xxx or .sex, why shouldn't i be allowed to implement that decision? There will probably be some kids who find themselves censored. But personally i'm more concerned about the darned involuntary redirects and 200 extra opening windows that i really really don't ever want to experience again. As someone said earlier - if someone else tells me i can't see it, it's censorship. If I choose it, it's a preferences menu.

  166. Re:Guess what? by tbo · · Score: 1

    It's a hard job, but someone's got to do it... My karma's already at the 50 cap, so I think I'm qualified. I'm your man.

    Signal 11, we salute you!

    OK, just so this isn't totally OT, will anybody be enforcing the new TLDs better than the ones we have now? If not, it just means that Time Warner will take timewarner.tv, .kids, .sex, .dot, .biz, .dvd..., instead of just timewarner.com, .net, and .org. Kind of defeats the purpose. Should there be limits on how many domains any one company can own? That would also help do something about those Domain Whores out there.

    Maybe I should start a new nickname as the successor to Signal 11. How about Kill -9?

  167. Good for filtering by JimDabell · · Score: 1

    .ads

    Woohoo. Now I can firewall off an entire TLD!

    .books

    Are domains this specific any use? Amazon aren't going to make it their default, since they do more than books. Nobody is going to guess "do they sell product <foobar>" by guessing TLDs now, are they?

    .solutions

    Mmm... good, wholesome marketese. Or do they mean people who don't want to do homework should search here?

    .free

    As in sugar?

    .gay

    Bagsy "is" :)

    Seriously though. TLDs like these aren't useful. Being able to see what sites are in a category is useful. That's why the open directory works, it helps you find stuff. Being able to see what categories a site is in is of questionable value, seeing as you could just go to that site and find out.

  168. Nice. by Alanzilla · · Score: 1

    I like the "a", "2", and "d" from Home Alone, myself. Yours had class, though, I'll give it that.

  169. What the new TLD's really mean by wmoyes · · Score: 1
    If the DNS system was invented today, instead of by researchers 20-30 years ago, I am sure the TLDs would look a lot like the ones just proposed.

    Someone was concerned that this could create more confusion if a particular site is a .com, .org, or .net. It won't. Why? If enough new TLD's are created then the meaning of TLD will be destroyed. For example if things were setup right you could visit 'coke' instead of 'coca-cola.com'. If you look at the list you will see several TLDs for specific companies, not general categories (.dubai, .yp, etc). Of couse this might take some client hacking to make it work.

  170. The .dot domain debacle by Foz · · Score: 1

    Oh come on, you are all such a bunch of weenies (whoops, -1, flamebait, can't accuse me of being a karma whore).

    When he said "I don't see .dot" it's quite obvious he's saying "I don't get why someone would want to sponser a lame tld like .dot".

    Of course, all the weenies and whiners want to immediately jump up and prove how superior they are by pointing out "doh... it's right there" thus proving their own weenieness.

    Haven't you ever heard of giving people the benefit of the doubt? Sheesh, people, get a clue. They're on sale right now, a whole box of clues for a buck ninety-five, so you'd better stock up.

  171. 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

    1. Re:ADULT TLD by Anonymous Coward · · Score: 1

      Schoolgirls! The Dot in .edu!

  172. A new TLD by fjordboy · · Score: 1

    a TLD specifically for Sysadmins... .god would be awesome...

    It could be used for religous sites too...maybe.


  173. A new /. mirror? by Dracos · · Score: 1

    So, is CmdrTaco going to grab slashdot.dot? Or slash.dot?


    Dracos
    "Time flies when you're procrastinating."

  174. The heck with .dot... what about by ackthpt · · Score: 2

    .FUD


    --
    Chief Frog Inspector

    --

    A feeling of having made the same mistake before: Deja Foobar
  175. Re:.DOT by GungaDan · · Score: 1

    Which of the United States' 50 "big government bodies" known as the Dept. of Transportation would get the TLD? I think the Commandante is hoping for the "Domain of Tacos."

    --
    Eloi are stupid, throw morlocks at them!
  176. Re:what is wap? by markbark · · Score: 1

    It's a TLA.....

    Ok, lame joke...
    Most folks seem to think it stands for Wireless Application Protocol.

  177. .OSS? by kevlar · · Score: 2


    I think there should be a .oss -- Open Source Software... hell theres enough of it out there...

    1. Re:.OSS? by Foogle · · Score: 2
      Why? There isn't a CSS for closed-source software. I see no reason that software, of any kind, needs it's own TLD.

      -----------

      "You can't shake the Devil's hand and say you're only kidding."

  178. .i? by Ralph+Bearpark · · Score: 2

    Y?

  179. How will control be delegated? by Operandi · · Score: 1

    If administration of TLDs is delegated to 1 commercial entity for each of these new TLDs, as is the case with most country TLDs, we will be taking a step backwards. There should be 1 international group, ICANN, which manages TLDs. Extend upon that an 'open' method of domain registration for accredited registrars and we have ourselves a very nice open system not owned in any way by commercial organisations. Does anyone else have any insights on how this will be done/should be done?

    Regards

  180. Re:.dot by plumpy · · Score: 2

    then you have to worry about the pronounciation. slash dot dot (sounds like colon slash slash, yes?)

    That's the whole point. When slashdot was first around you couldn't go to www.slashdot.org (well... it redirected you to remove the www). The whole point of the name "slashdot" is the annoying pronounciation. Say the whole URL out loud:
    H T T P SLASH SLASH SLASH DOT DOT ORG

    If he had .dot, it would be http://slashdot.dot as in:
    H T T P COLON SLASH SLASH SLASH DOT DOT DOT

  181. Re:.wap - bad idea! by mach-5 · · Score: 1

    I think its a great idea! I think it would be great for everyone with a device that uses wap to have a place that they can definately go.

  182. 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-
  183. there is so a .dot! by sherpajohn · · Score: 1

    along with:
    .info (that's helpful!)
    .site (oh, and I thought it was a domain?)
    .spot (every dog has it's domain)
    .surf (what about the hydophobic?)
    .web (spiders are insects too!)
    Applied for by: JVTeam, LLC

    The funniest to me is the Canadian who wants there to be a .kids and .xxx (hmmmm, makes you wonder what kind of sites they want to put up).

    Going on means going far

    --

    Going on means going far
    Going far means returning
  184. Short-sightedness of these TLDs. by karzan · · Score: 1

    Has anyone else noticed that most of these TLDs are really short-sighted and are of far more limited use than the current ones? ie are things like .radio and .dvd really going to make sense in a few years? And how wide is their true range of use? It seems to me that only generic, widely usable TLDs should be allowed, otherwise the whole thing gets confusing (people have a hard enough time remember whether something is .com, .org, or .net now, imagine trying to work out whether it's .free, .radio, .dvd, .kids, or .men!) Plus so many people assume everything ends with ".com" now that they are going to misunderstand and think you mean "playground.kids.com" rather than "playground.kids" which by the way just sounds really weird.

  185. I love the organizations by ultra+laser · · Score: 1

    who suggest their own name as a tld.

    I've always wanted a .dubai domain!!

    (actually im holding out for insi.pid)

    --
    wisconsin does not exist.
  186. can't do it and follow protocol by operagost · · Score: 1

    DNS servers, well BIND at least, must forward all requests to a forwarding server or a root server regarding domains for which they do not have authority. To block whole TLDs would require a custom named.
    It's STD0013, section 5.3.3.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
  187. Why .nom? by Millennium · · Score: 1

    If I remember right, .nom is supposed to be for personal sites. Why was this chosen?

    Seems to me, .sum (Latin for "I am") would be a more appropriate choice; IANALS (I Am Not A Latin Student), but unless I'm mistaken, something like "millennium.sum" is even gramatically correct, the dot notwithstanding.

    Just a nit to pick...
    ----------

  188. I'm a little surprised... by Atreides_78723 · · Score: 1
    ...noone suggested ".grits" yet...

    --
    "...heroic hearts, made weak by time and fate, but strong in will, to strive, to seek, to find, and not to yield."
  189. Change the face of the internet. by mach-5 · · Score: 1

    This will be cool. It will change the face of the internet big time. Not everyone will want a .com anymore. Although it will make finding things more difficult. No more picking a random word dealing with the topic you're interested in and putting .com after it to get a site. I'll have to actually use search engines...Noooooo!

  190. .fan! by barbaBob · · Score: 1
    For fansites of course... No commercial exploitation allowed, for fan enjoyment only.

    But then again, we all know what happened to .org ;)

    --

    --

    --
    *sig*

  191. Wow ICANN is an awesome organism by |guillaume| · · Score: 1
    They are so fast end efficient, look at this note on their page:

    Note: On 3 October 2000, we revised this list to add two mistakenly omitted applications and to make minor corrections to some TLD and applicant data.

    Is the date now becoming another ICANN assigned number??

    ---
    Guillaume

    --

    give me all your garmonbozia

  192. .XXX and .kids!!!! by Zwack · · Score: 1

    What conclusions can be drawn from the fact that one registrar wanted both .kids and .xxx?

    I guess they want to clearly delineate websites for adults and those for children, but howlong before we see someone registering nude.kids?

    At least they didn't ask for .teens too...

    Z.

    --
    -- Under/Overrated is meta-moderation, and therefore is Redundant.
  193. .wap would be bad by BlowCat · · Score: 2
    How are you going to resolve a conflict between foo.org and foo.com when both try to get hold of .wap?

    I cannot imagine any company or organization using exclusively .wap

    1. Re:.wap would be bad by LiNT_ · · Score: 1
      I think it would be a great idea. Think about it. Websites that wish to provide content to mobile users could offer a slimmed down version of thier site available at .wap.

      You want to read the latest headlines on your Handspring? Head over to slashdot.wap. With the way that wireless computing is going. I can't think of a better tld.

      LiNT

  194. TLD's by Archangel+Michael · · Score: 1

    Here are some useful new domain names. dot.dot and dash.dot

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  195. Nation-based TLDs. by karzan · · Score: 1

    I've said it before and I'll say it again: domains should be regulated so the only entities capable of getting .com, .org, and .net should be global entities--90% of the current ones should be moved to .co.us, .org.us, .net.us, .mil.us, .gov.us, etc. There shouldn't even be the OPTION of having momscookiesofindiana.com. We should stop wasting the namespace and translate all the existing wastes of namespace into nation-based domains to save room for truly global things (ie, you would have ibm.com, but whitehouse.gov.us)

  196. Wireless Application Protocol by skip77 · · Score: 1

    No, I believe that .wap stands for Wireless Application Protocol. Which makes no sense, considering that alot of web pages that can be accessed by your cell phone or palm forgo the www. for .wap For example wap.slashdot.org, speaking of wap.slashdot...when will /. be available to WAP browsers Taco?(or is it already?)

    --
    --Chris
  197. Pi (OT) by nowan · · Score: 1

    That'd be 187.64.230.78

    Well, Pi * 10^9, anyway.

  198. There wouldn't be problem with TLD overcrowding... by atomice · · Score: 1

    ...if every Tom, Dick and Harry didn't want to have their own domain for their web pages. In the good old days only the major hosts had their own domains and everyone else just had a home page off it. (eg. http://www.ic.ac.uk/~abc99) Now companies like www.freenetname.co.uk give domains away for free (as in with catches) and everyone wants to jump on the bandwagon. I think that naming domains along the same lines as newsgroups is good. Yes - I know it's not compatible with the current DNS system - but you could easily implement an alternative mechanism.

  199. What about .mars and .moon? by BluesMoon · · Score: 1

    Shouldn't we be getting ready for an intergalactic network? After all, /usr/src/linux/net/ipv4/tcp_timer.c has this to say:
    * PAWS allows us longer timeouts and large windows, so once
    * implemented ftp to mars will work nicely. We will have to fix
    * the 120 second clamps though!

    Any comments?

    Philip

    --
    Do not underestimate the value of print statements for debugging.
  200. Unicode domain names? by Anonymous Coward · · Score: 1

    Seems a little dumb to stick with the Ascii charater set, why not expand DNS/Domain names to support unicode so that people/organisations in various countries can devise address schemes to suit them and their target audience?

  201. Borrow naming scheme from usenet? by E1ven · · Score: 1

    There allready exists a naming scheme for classification based on subject. We use it in Usenet.
    .comp for computer related
    .soc for societal
    .rec for recreation
    ect...
    The system could be modified, to make it more relavant, but why not start with something everyone knows?
    --

    This message brought to you by Colin Davis

    --
    Colin Davis