Slashdot Mirror


ICANN Responds To gTLD Plan Comments

angry tapir writes "ICANN has delayed its plans to sell new generic top-level domains while responding to public comments about the controversial proposal. The organization has released a 154-page document detailing and analyzing the hundreds of comments (PDF) it has received about its gTLD plan. In response to several concerns brought up by the public and companies in the Internet industry, ICANN has moved out the projected timeline for taking applications for new gTLDs from September to December."

119 comments

  1. Don't click the link! by smooth+wombat · · Score: 3, Funny

    a 154-page document detailing and analyzing the hundreds of comments (PDF)

    It's a trap!

    --
    We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
    1. Re:Don't click the link! by MrPayne · · Score: 3, Informative

      Just open it in something other than Adobe Reader.

    2. Re:Don't click the link! by sexconker · · Score: 2, Informative

      Just open it in something other than Adobe Reader 9.

    3. Re:Don't click the link! by contra_mundi · · Score: 4, Funny

      Just do it.

    4. Re:Don't click the link! by Anonymous Coward · · Score: 0

      I could tell by the file extension, and having seen many traps in my day.

    5. Re:Don't click the link! by smooth+wombat · · Score: 1

      Just open it in something other than Adobe Reader 9.

      Not quite. From the InfoWorld article:

      The flaw affects version 9 of Reader and Acrobat as well as earlier versions, according to Adobe's advisory.

      --
      We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
    6. Re:Don't click the link! by Anonymous Coward · · Score: 4, Funny

      This is Slashdot. What are the chances anyone would click the link to a story?

    7. Re:Don't click the link! by Aqualung812 · · Score: 1

      There are many other programs that read PDFs that are not made by Adobe...

      --
      Grammer Nazis - I mod you "troll" unless you actually add something on-topic. Yes, I know I have mispellings in my sig.
    8. Re:Don't click the link! by tonyreadsnews · · Score: 1

      I'm sure most are safe, given the number of people that RTFA (which at worst is 10 pages with 1 paragraph each).

    9. Re:Don't click the link! by oasisbob · · Score: 1

      Just open it in something other than Adobe Reader 9.

      ... or 8. Or 7.

    10. Re:Don't click the link! by iamhigh · · Score: 1

      Yeah, good thing I still have Reader 5.0 installed. Surely all the script kiddies aren't still attacking that dino!

      --
      No comprende? Let me type that a little slower for you...
  2. This "plan" only benefits registrars by winkydink · · Score: 4, Insightful

    Further balkanization of gTLD's does nothing for the end user. It will be a great stream of new revenue for registrars though.

    ICANN has become nothing more than a pawn of domain registrars. Read the meeting minutes and see for yourself.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    1. Re:This "plan" only benefits registrars by contra_mundi · · Score: 1

      Sure looks like it.
      .cola? Are they kidding?

    2. Re:This "plan" only benefits registrars by sexconker · · Score: 1

      .cola domain names would be an invaluable tool to reach our core target audience who make cola soft drinks a defining part of their unique life experiences!

      In addition, .diet-cola, .citrus, .diet-citrus, .max, .diet-max, .one, .diet-cola, .caffeine-free, .diet-caffeine-free, .wildcherry, .diet-wildcherry, .vanilla, .diet-vanilla-caffeine-free-wildcherry and other domain names will help grow our brand net out from just our core audience.

    3. Re:This "plan" only benefits registrars by meadowsoft · · Score: 1

      Obviously to document anything related to Cost of Living Adjustments? Important in today's economy, no?

      Or are you aware of a different type of cola?

    4. Re:This "plan" only benefits registrars by Workaphobia · · Score: 1

      It is a disgusting thing to do to the Internet, to remove the last semblance of hierarchy and structure in the naming system. It's crap like this that makes me wonder how long it will be before entire contenents are on separate competing DNS roots, fracturing the net as we know it.

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    5. Re:This "plan" only benefits registrars by Ihmhi · · Score: 1

      Jokes aside, wouldn't this kinda make the Internet go more the way of Usenet?

      Instead of alt.cherrycoke you'd have www.cherry.coke

      I don't see how it's that bad of a thing. Any company that worries about their brand is going to buy every related brand under the sun. So long as the approval process is very rigorous I don't have such a big problem with it.

      This opens up the possibility for a new industry, even - gTLD agents:

      1) Collect a set of people with the same gTLD in mind - for example, let's say the domain is .arcade. Examples:

      www.penny.arcade
      www.play.arcade
      www.buy.arcade
      www.w.arcade

      2) Give the equivalent of "pre-registration" for the domains. After info is collected on a certain amount, the agent goes to ICANN with the proposal as well as info on the prospective clients.

      3a) If the gTLD is approved, the agent registers the domains for the parties involved (after the gTLD is created) and collects their fees and commissions.

      3b) If the gTLD is not approved, most of the money is refunded to the clients. (Gotta pay the agent for making the effort, at least.

      I predict that .dot will be popular.

    6. Re:This "plan" only benefits registrars by Estanislao+Mart�nez · · Score: 1

      It is a disgusting thing to do to the Internet, to remove the last semblance of hierarchy and structure in the naming system.

      This claim makes no sense. DNS is just as hierarchical under the traditional and the gTLD model.

      The hierarchy of domain names is really about delegation of authority for assigning IP addresses for symbolic names. The folks who manage the .edu domain have the authority to assign symbolic hostnames that end in .edu, and additionally, to delegate assignments in subdomains thereof to other parties, like the folks who manage the mit.edu and stanford.edu domains. And these latter folks have the same authority within those subdomains, and so on.

      So, the TLDs are a relic of the early days of the Internet, where it was a network connecting computers at US military installations and universities, so very few top-level authorities were needed. Today, when the Internet is so large and pervasive, there is really no good argument for limiting the number of TLDs.

    7. Re:This "plan" only benefits registrars by Sloppy · · Score: 1

      Further balkanization of gTLD's does nothing for the end user.

      Ok, but does it harm the end user?

      I don't think it does. I put this in the "useless but also harmless" category.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    8. Re:This "plan" only benefits registrars by Workaphobia · · Score: 1

      What would be so horrible about registering entities under a path to the root that indicated something meaningful about that site's purpose and charter?

      - Companies registering domain names based on their existing trademarked names in the jurisdictions where they're represented. Think .co.uk, but with an actual restriction on who can register what.
      - Reserving a name (again under the appropriate jurisdiction) for non-profit organizations, instead of allowing any Tom, Dick, and Harry to have a .org.
      - Giving banks a suffix of their own, to help protect their customers from phishing, and without extorting ridiculous sums from them to do so. Just create a damned .bank.us.
      - Not polluting a global namespace with registrations that are irrelevant to most of the world. Why the hell should .gov be under the control of the United States? Are we the only nation with a government that has an internet presence?

      What common interest is served by flattening the hierarchy and allowing registrars to cash in on a virtual land grab? I know it's not realistic to expect any better, but I'm speaking idealistically: why couldn't we have imposed better, more sensible standards for naming?

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    9. Re:This "plan" only benefits registrars by 1u3hr · · Score: 1
      I don't see how it's that bad of a thing. Any company that worries about their brand is going to buy every related brand under the sun. So long as the approval process is very rigorous I don't have such a big problem with it.

      If you had a brand name you wanted to protect and had to spend tens of thousands of dollars to register all these extra domain names you don't want and will never use, just to prevent squatters or spammers or phishers taking them, you might.

      What GOOD does it do anyone, aside from the assholes selling them?

      None of your examples require new TLDs. They can all easily, and virtually freely, be done within the current system, without any hassle or registration. Just create as many second, third, fourth... level names as you want on your .com (or .co.uk, etc, etc.). No cost. No profit to the registrars, sadly.

    10. Re:This "plan" only benefits registrars by Anonymous Coward · · Score: 0

      www.slash.dot

  3. blarg i am anonymous by Anonymous Coward · · Score: 0

    waste of money. our company won't dish out that much for a domain name. .com, .net, and .org works perfectly fine for us. Sorry Microsoft but .ms already is an anti-trusted domain name =P

    1. Re:blarg i am anonymous by mcgrew · · Score: 1

      Companies aren't the only "people" who have web sites. Try registering [yourname].anything

    2. Re:blarg i am anonymous by PPH · · Score: 1

      True. But do you really think the folks in Redmond are really going to let Bob Microsoft register microsoft.person?

      --
      Have gnu, will travel.
    3. Re:blarg i am anonymous by nine-times · · Score: 3, Insightful

      But how much of that is squatters, anyway? I know I've had many times where I've gone to register an domain name and it's been taken, but when I go to the sites under that domain, I find placeholder pages with ads.

    4. Re:blarg i am anonymous by fuzzyfuzzyfungus · · Score: 2, Funny

      Don't worry sir, I'm sure that your company will be willing to pay our very reasonable fees for all possible variations of its name, and any distinctive trademarks. It would be such a pity for them to fall into the hands of spammers, link farmers, or others who would reflect poorly on them...

    5. Re:blarg i am anonymous by Chyeld · · Score: 1

      True. But do you really think the folks in Redmond are really going to let Bob Microsoft register microsoft.person?

      Given Microsoft Bob's relation to Melinda Gates, I'd say... yes.

    6. Re:blarg i am anonymous by Metasquares · · Score: 3, Insightful

      The .name TLD is still pretty unused (unless you have a very common name), and was created for exactly that purpose.

    7. Re:blarg i am anonymous by Propaganda13 · · Score: 1

      I followed your advice, but got bored before I checked all of them. There's at least 25 domains available including .com, .net., .org.

    8. Re:blarg i am anonymous by Sloppy · · Score: 1

      our company won't dish out that much for a domain name. .com, .net, and .org works perfectly fine for us.

      [Emphasis mine.]

      If you bought all 3, perhaps you're already drinking the koolaid.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  4. I'm for it! by Anonymous Coward · · Score: 2, Insightful

    I, for one, am for it. At the very least it will derail the slimy domain squatters that just sit on every-damn-word-in-the-dictionary-and-combination-thereof.com|net|org

    And I don't want to hear the shit about companies protecting their brand name. It is just about impossible to give your company a name that has not already been used *somewhere* and/or registered as a domain name.

    - Sick of it all

    1. Re:I'm for it! by smoker2 · · Score: 1

      How ?
      It does nothing more than allow every fucker with some money to buy them all up AGAIN ! Why don't we expand the TLD space again, (when they need some more money). Fucking consumer !

  5. Sigh by oahazmatt · · Score: 5, Funny

    And I was so looking forward to registering ".1" so I could realize my dream of having an external URL at 127.0.0.1.

    --
    Those who believe the Internet is private,
    find their privates are on the Internet.
    1. Re:Sigh by david.emery · · Score: 4, Funny

      All that traffic directed to 127.0.0.1 would serve you right! :-)

      dave

    2. Re:Sigh by Anonymous Coward · · Score: 4, Funny

      Looks like someone already beat you to it. I went to http://127.0.0.1/ . I have to say I like that site a lot. But then again it looks very similar to mine, so I am biased.

    3. Re:Sigh by Anonymous Coward · · Score: 1, Funny

      Already slashdotted!

    4. Re:Sigh by Anonymous Coward · · Score: 0

      Turn in your card.

    5. Re:Sigh by Anonymous Coward · · Score: 0

      I do believe i spot a troll thar.
      Get back to the bridge where you belong Troll!

  6. The problem with this in relation to the article is the price:

    ICANN has proposed an application cost of US$185,000, not including yearly upkeep fees.

    Now I don't know about you, but most "people" don't have that kind of money to throw at a domain name. The real thing to think about: How will this affect online shopping? Those big companies with money to blow will get their fancy gTLDs whereas small businesses and freshly started ones who don't have that kind of money will be stuck with what may eventually become the 'less appealing' .com/.org/etc that we already have. Will these small companies be pushed aside because they lack the appeal of having a fancy gTLD? Will people be more suspicious of them because it is easier for malicious people to set up a spoofed site with a .com than a .insert-big-corp-here?

  7. I've run out of happy. by Anonymous Coward · · Score: 0

    Guess it means the .hascheezburguer domain will not be released.

    In other words, ICANN not .hazcheezburguer. :(

  8. ICANN Responds by Anonymous Coward · · Score: 0

    I wonder if it's a canned response.

  9. Just a Money Grab by basementman · · Score: 1

    This is just a blatant money grab by ICANN. It does nothing for the end user, and nothing for domain owners. Will your life be made better with a .penis extension? It just adds another level of confusion and makes names more difficult to remember. We already have enough dumb TLDs, why do we need infinity more?

    1. Re:Just a Money Grab by Anonymous Coward · · Score: 0

      I don't know about you, but I could always use a .penis extension.

    2. Re:Just a Money Grab by oskard · · Score: 1

      I don't know about you, but I could always use a .penis extension.

      Ah, so you're the guy who's always emailing me.

      --
      Sigs are for Terrorists.
    3. Re:Just a Money Grab by digitalchinky · · Score: 1

      I stopped remembering phone numbers in about 1992 when I bought my first cellular, I quite literally do not know my own phone number, and I don't even need to when I can bluetooth it around or send via text, so what makes you think we might need to remember domain names? We have bookmarks and a myriad of search engines for that.

      Money grab? Like ICANN is not all that right now? As of today there are roughly 200 million registered domain names, that's a lot of money changing hands no matter how you swing it. Some very rich people living off bits in a database. The entire system costs just a small fraction of the total figure to implement world wide. Greed, if you're not with it, you're just a normal well rounded human being :-)

  10. Existing non-Internet Registrars by surmak · · Score: 3, Interesting
    We already have too many gTLDs. What is the difference between foo.com and foo.net? Most likely foo.com got there first, and then foo.net was the second comer. The only reason I can see for allowing new top-level domains is to provide a reference to organizations that already exist within another globally unique registry of some sort.

    The best example of such a registry I can think of is the callsign of a radio station. These are globally unique (the first letter or two identified the country, and the rest is assigned by the radio regulatory authority of that country (in the US, the FCC). Thus, I could see adding a TLD .radio, which would be limited to callsigns as the second level domain. (e.g. wkrp.radio)

    Other such global registries could include UPC or ISBN prefixes. PCI, USB or ethernet manufacturer IDs, or the like are also globally unique ID's and may be worth putting into DNS.

    1. Re:Existing non-Internet Registrars by nine-times · · Score: 1

      We already have too many gTLDs. What is the difference between foo.com and foo.net? Most likely foo.com got there first, and then foo.net was the second comer.

      I'm not sure that's a sign that we have too many, but perhaps rather that the attempt at organizing these things has been a failure so far. Personally, I'd like to see the whole thing reevaluated, figuring out what the goals of the organization are, and then figuring out what organization is likely to achieve those goals based on the reality of the Internet today (i.e. spammers, phishing, fraud, domain squatting).

    2. Re:Existing non-Internet Registrars by Anonymous Coward · · Score: 0

      .net is for network providers (like the backbone and ISPs), but some luser at Verisign decided there's more money in letting it be abused by squatters.

    3. Re:Existing non-Internet Registrars by Keen+Anthony · · Score: 1

      I wouldn't mind more gTLDs, but perhaps it's for the wrong reason that I want them. A ".radio" would be very useful, but just having more gTLDs out there would allow me and others in the same boat a chance to register the domains we want now that the big three (.com, .net, .org) are so crowded. Of course, squatters and competition-adverse companies alike will rush to sweep up domains on new gTLDs, but hey at least I might get a day or two.

    4. Re:Existing non-Internet Registrars by hackstraw · · Score: 1

      We already have too many gTLDs. What is the difference between foo.com and foo.net? Most likely foo.com got there first, and then foo.net was the second comer.

      Better yet, what is the difference between slashdot.org and slashdot.com? What about wikipedia.org and wikipedia.com?

      Where I work, we are under a .org TLD. And another person I work with in IT types in wikipedia.com and never notices that the site is wikipedia.org. What about whitehouse.com vs whitehouse.gov? For those that didn't know,whitehouse.com was a porn site or something. What about usps.com or army.com? The government and military have their own TLDs, yet they opt out of using them for the more user friendly (sic) .com.

      The point is that 1 gTLD is too many. When the web was young, I guess TLDs made sense on paper, but since its gotten popular, practically 100% of the people ask for your email or something and they already append .com at the end of it.

      I used to argue that TLDs made sense for countries. But .fm and .tv has sold their countries' domains away, and very few people use those domains. I think there are domains now that are so long that most people probably can't spell. .museum comes to mind.

      With junk like .mobi, which is designed for mobile devices, why can't a prefix on a domain work like it has for everything else before cellphones? we have ftp.example.com, www.example.com, mail.example,com (which has cool hooks in DNS and I wish there were more...), what about mobi.example.com? I mean, the introduction of .mobi implies that .com is broken, right? /rant

    5. Re:Existing non-Internet Registrars by gad_zuki! · · Score: 1

      No, these tlds are helpful. If anything ends with .biz its a scam or not worth visiting. I expect the new influx of vanity tlds will be the same, with someone eventually writing an IE and Firefox extension that blacklists all domains that dont end with .com, .net, org, mil, and the established country/state codes.

  11. ICANN has .LOLdomain? by w0mprat · · Score: 1

    Obviously they have canned this idea - pardon the pun - most likely due to being inundanted by requests for domains like .cheezburger

    --
    After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
  12. Damn the feedback, full speed ahead! by damn_registrars · · Score: 2, Insightful

    So they took feedback, and then did what with it? They compiled (parts of) it into a PDF. Wow, I'm impressed. Now in response they have moved out the date by a few months; great.

    I can't wait until some shady group in another country buys the .viagra and .software TLDs and self-administers the registrations within them as permitted by the ICANN plans. Once that happens we'll get spam from dirtcheap.viagra and superubercheap.software, which will be for domains that have no readable whois data and ICANN will just shrug their shoulders and say "talk to the registrar" (who themselves won't speak to us).

    Thanks ICANN. I guess the assumption was right, you don't give a damn about feedback after all. As long as you can make a few more bucks on new registrar accreditations (whatever that will mean when you start selling new gTLDs) you're happy, right? And thats really all that matters on the internet.

    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
    1. Re:Damn the feedback, full speed ahead! by Anonymous Coward · · Score: 0

      The US-puritan-controlled ICANN wouldn't approve .sex, but they'll approve .viagra?

      Can I have some of what you're smoking please?

    2. Re:Damn the feedback, full speed ahead! by damn_registrars · · Score: 1

      ICANN wouldn't approve .sex, but they'll approve .viagra?

      Correct. They are going to allow the sale of gTLDs, which will likely at some point include .viagra and perhaps .sex or .xxx (which they had previously declined). The difference is that they did not want to manage the sale of domains within domains like .xxx. Now instead they will pass the buck entirely and sell the gTLD of .xxx to some other registrar who will be solely responsible for who can buy domains within it.

      However even worse is that they will sell the right to sell gTLDs to other registrars. So eventually it is all but guaranteed that we will see TLDs of .viagra, .sex, and .xxx. But as ICANN won't have anything to do with those registrars directly, there will likely be unlegible gobbledygook behind the domains under those new TLDs (particularly the gTLDs that are good targets for scammers and spammers like .viagra, .software, .money, .purses, ...). And then to make it even better there will be nobody to talk to about who owns the domains under those gTLDs that are selling illegal wares.

      Can I have some of what you're smoking please?

      There is no smoking involved. The problem lies in ICANN passing the buck again. Soon the things that they reportedly stood for will be torn down by the vendors that are first in line with the requisite amount of money.

      --
      Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
  13. Gated Community TLDs by RevWaldo · · Score: 4, Interesting

    Just a thought experiment. Suppose you set up a TLD - .bob for instance. Users can set up domains for web sites, e-mail, FTP etc. within .bob just like any other domain, but the rules of using it are different from the rest of the web. Such as -

    Web -
    - Only other .bob account holders can access .bob sites. No one else can get in, not even google.
    - .bob sites cannot be accessed anonymously, but .bob sites must guarantee privacy - your usage can't be shared with anyone else.

    E-mail and IM -
    - No anonymous addresses or accounts. .bob e-mail addresses or chat names must be linked to an actual person.
    - .bob users can only send/receive e-mails or IM to other .bob addresses. Nothing outside .bob is allowed in.
    - Spam is not allowed. At all. You spam, you lose your .bob access

    Content -
    - Your .bob account comes with a license with nearly all known media companies. (www.timewarner.bob, for instance.) For a monthly fee you can access any media they have digitized - books, news, film, music, games, software, etc. It's DRMed out the wazoo, of course. All usage is tracked. Violate the terms of use and you lose your .bob access.

    In other words, a fully privatized portion of the internet. A nightmare to some, but to others - "Access to all media? No spam? $39.95 a month? Where do I sign?"

    Other TLDs could set up other ecologies. .ftw might only allow services that are fully encrypted and anonymous, for example.

    Is there anything that would prevent TLD owners from doing this?

    1. Re:Gated Community TLDs by Anonymous Coward · · Score: 0

      That it doesn't work? Three letters: AOL

    2. Re:Gated Community TLDs by vishbar · · Score: 1

      What's preventing then from doing it with an existing subdomain? (bob.com, e.g. www.timewarner.bob.com)

      --
      Ride the skies
    3. Re:Gated Community TLDs by Anonymous Coward · · Score: 0

      If they do it that way, ICANN doesn't get $25000 per year.

    4. Re:Gated Community TLDs by Nethead · · Score: 1

      Because a lot of that depends on reverse DNS. And you can put anything you want for a reverse.

      --
      -- I have a private email server in my basement.
    5. Re:Gated Community TLDs by Anonymous Coward · · Score: 0

      TLDs are about mapping domain names to IP addresses. A server doesn't know whether a client got the server's address from the .bob nameservers or a note taped to the monitor. A walled garden has to actually do the work to authenticate users, and I don't see how having your own TLD even helps.

    6. Re:Gated Community TLDs by rednip · · Score: 1

      Suppose you set up a TLD ...but the rules of using it are different from the rest of the web

      So instead of simply using the DNS to resolve to an IP address, how would you route '.bob'?

      --
      The force that blew the Big Bang continues to accelerate.
    7. Re:Gated Community TLDs by Piranhaa · · Score: 1

      You've clearly been hanging around Him too long sir

    8. Re:Gated Community TLDs by RevWaldo · · Score: 1

      Rewinding the scenario I spelled out a bit, this wouldn't involve any rewiring of DNS. Basically, if I owned a TLD, could I place contractual obligations on anyone that wanted to create domain names under it?

      We already have TLDs with usage restrictions. .edu, .gov, and .int domains cannot be used for any old web site. Many national domains can only be owned by residents/organizations residing in those countries.

      But these are more of a benign nature. I'm talking about setting up TLDs that work on their own set of principles:

      - The owners of the .anon TLD require domain name owners to adhere to strict rules regarding privacy an anonymity
      - The owners of the .vegas TLD require domain name owners to cut them in on the action
      - The owners of the .commons TLD require domain name owners to have creative commons licensing for all content.
      - The owners of the .christ TLD require domain name owners to keep it clean
      - and so on and so on.

      Going back to the .bob scenario the TLD owners place restrictions on domain name owners regarding user authentication, revenue sharing, e-mail use, etc. The obligations placed on the domain name owners would effectively wall off the .bob domain, if not completely in reality.

      Why this might sell is that visitors of domains under these TLDs would know what to expect. If I go to an .anon site I'm virtually guaranteed my boss or significant other won't find out what I do there (at least from the site owners.) If I'm a Christian I know a .christ site won't contain anything that will shake my faith. Users know that there is a third party overseeing the use of the domain they are visiting. If the site owners didn't follow the dictates of the TLD owners, they wouldn't have the domain name in the first place.

    9. Re:Gated Community TLDs by Sloppy · · Score: 1

      Is there anything that would prevent TLD owners from doing this?

      There's nothing preventing people from doing that right now, without the need of new TLDs. Run whatever protocols and policies that you wish.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    10. Re:Gated Community TLDs by Nethead · · Score: 1

      All of which you could do with a regular page of links that you have 'reviewed.' Sure, if you have your own TLD then you could do all that but you would still have to monitor (robot) those sites to insure that they conform to your AUP. If you did have to pull a domain for an AUP violation then you may have to lawyer-up, even if you are in the right.

      --
      -- I have a private email server in my basement.
    11. Re:Gated Community TLDs by Anonymous Coward · · Score: 0
  14. trademark by Lord+Ender · · Score: 3, Interesting

    Even US trademark law does not scale well to the Internet. I can't imagine the disaster GTLDs would be for international trademark disputes. The IP lawyers must be licking their lips at the thought of GTLDs.

    --
    A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    1. Re:trademark by Anonymous Coward · · Score: 0

      It scales just fine, but they did it wrong. Trademarks should have never been applied to the domain names themselves. If someone misused a trademark on their web pages, then normal trademark rules could be used.

  15. Report, p35 by French31 · · Score: 1

    A number of commenters urged ICANN not to move forward with the new gTLD program because of threats to DNS stability and security, and warned that the new program will create a new wave of malicious activity, including spam and phishing.

    Phishing Hell if they don't do things right, for sure.

    What's the point of this program anyway? Being able to register fancy urls? By paying $185,000 + yearly fees?

    --
    They who would give up an essential liberty for temporary security, deserve neither liberty or security. --Ben Franklin
  16. Where is my comment... by pongo000 · · Score: 1

    ...about how to best handle "colliding" gTLDs previously established by alternate roots? I don't see it anywhere in the linked PDF.

    Oh, silly me...Vint Cerf has already waxed majestic about how alternate roots would be "disastrous" to the architecture of the Internet. So I suppose this means ICANN can (pun intended) conveniently ignore the entire issue of alternate roots, even though China has already established an alternate root, with no sign of the meltdown predicted by Dr. Cerf.

  17. Re: by Captain+Splendid · · Score: 1

    what may eventually become the 'less appealing' .com/.org/etc

    I don't see that happening for a long time. For most, the "web" is .com

    Speaking of which, custom TLDs just sounds like a way to make squatters spend a whole lot more money. Sounds good to me.

    --
    Linux, you magnificent bastard, I read the fucking manual!
  18. It will be a great stream of new revenue for registrars though.

    Will it, really? I mean, if any organization can register a TLD and sell subdomains within it, that would drastically increase the supply of domain names. The prices of domains should go down, in that case, since if you can't get joe-blow.tld1 you could get joe-blow.tld2.

    Of course, this is assuming that the domain registrars don't form a cartel. But the point is that generic TLDs aren't a big deal; a cartel of domain registrars is.

    1. Re:How? by ion.simon.c · · Score: 1

      Will it, really? I mean, if any organization can register a TLD and sell subdomains within it, that would drastically increase the supply of domain names.

      But, um... what happens when we run out of IPv4 addresses? Chaos, I tell you!

    2. Re:How? by Aluvus · · Score: 1

      Because major multinational Joe-Blow, Inc., is not comfortable buying joe-blow.tld1 and letting whoever wants to buy joe-blow.tld2, which they could use in a way that damages Joe-Blow's reputation. There is some legal recourse to that, depending on the specifics, but that takes time and is anything but guaranteed. Why risk it? So most large companies (and indeed, many smaller companies) just buy a bunch of permutations of their domain name, including different TLDs and common misspellings. They will generally ignore ccTLDs (of which there are over 250) except maybe the one for their own country, but will often buy several or all of the no-restrictions gTLDs (.com, .net, .org, and if they feel like it .biz, .info, and maybe the others). ICANN is moving toward creating more gTLDs.

      So in effect, increasing the supply of gTLDs stands to artificially increase the demand as well, thus offsetting any price pressure.

      --
      Never mistake "can" for "should".
    3. Re:How? by Estanislao+Mart�nez · · Score: 1

      Because major multinational Joe-Blow, Inc., is not comfortable buying joe-blow.tld1 and letting whoever wants to buy joe-blow.tld2, which they could use in a way that damages Joe-Blow's reputation. There is some legal recourse to that, depending on the specifics, but that takes time and is anything but guaranteed. Why risk it? So most large companies (and indeed, many smaller companies) just buy a bunch of permutations of their domain name, including different TLDs and common misspellings.

      But I'd argue that this approach is only feasible given a limited number of TLDs in the first place. If gTLDs mean they can't corner the market on registrations of names related to their company name, why would they try?

      As you point out yourself, they already can't do it, given all the ccTLDs in existence. Doesn't that just go to show that how many domains Joe-Blow Inc. registers isn't determined by how many TLDs there are?

  19. The question you're failing to ask... by Estanislao+Mart�nez · · Score: 1

    You're failing to ask a crucial question here: why do we insist in continuing to use domain names as an end-user content addressing mechanism? Why not use web directories, search engines, bookmarks and portals instead?

    There are technical reasons for DNS as part of the low-level plumbing of the internet, certainly, but are there really any good reasons for a non-technical user to be aware of it?

    1. Re:The question you're failing to ask... by thePowerOfGrayskull · · Score: 1

      There are technical reasons for DNS as part of the low-level plumbing of the internet, certainly, but are there really any good reasons for a non-technical user to be aware of it?

      Of course there are. It gives you a specific and presumably permanent location that Person or Company X may always be found at.

      Saying that search or directories can somehow replace this is like saying we could business addresses with the yellow pages.

    2. Re:The question you're failing to ask... by 1u3hr · · Score: 1
      Of course there are. It gives you a specific and presumably permanent location that Person or Company X may always be found at.

      We have an effectively infinite number of "specific and presumably permanent locations" NOW. Adding an indefinite number of TLDs to that does not give you any advantage over the current "limited" number of TLDs. But I can think of a lot of confusion and malicious use that could be made of confusingly similar TLDs.

  20. The point of DNS isn't to organize content. by Estanislao+Mart�nez · · Score: 1

    I'm not sure that's a sign that we have too many, but perhaps rather that the attempt at organizing these things has been a failure so far. Personally, I'd like to see the whole thing reevaluated, figuring out what the goals of the organization are, and then figuring out what organization is likely to achieve those goals based on the reality of the Internet today (i.e. spammers, phishing, fraud, domain squatting).

    But the point of DNS isn't to "organize" the content of the net. The point of DNS is to delegate and distribute authority for maintaining the records of a database of domain names to IP addresses, and answering queries about the records. If I have example.com, that means I can assign mappings within example.com, or delegate authority to assign mappings within a subdomain to some other party. That's all it is.

    If we want to organize the content of the internet, we have better tools for doing so, like search engines or directories.

    1. Re:The point of DNS isn't to organize content. by nine-times · · Score: 1

      I think you're misunderstanding what I'm getting at. The reason we have different TLDs certainly is about organization as well as delegation of authority. If it was only about authority, why bother having .net, .org, .com, .info, and .biz addresses?

      Schools are supposed to have EDU addresses, government organizations are supposed to have GOV. I believe that ORG addresses were supposed to be non-profits, COM were supposed to be for commercial entities, and NET addresses were supposed to be mainly for ISPs and companies providing network services. And then countries were supposed to have their own addresses for sites specific to their country. The idea was partially so that you'd know the type of organization you were connecting to by its name.

      But look what's happened-- there's no real distrinction between how ORG, COM, and NET addresses are used. Nobody really uses INFO or BIZ. On top of that, country-specific TLDs are being used for various purposes, depending on whether their abbreviation is somehow catchy. People are using WS as though it's an abbreviation for "web site", and they're using ME to be the word "me" and therefore using it for personal sites. The whole thing is kind of a mess.

      So I'm just thinking they should go back to the drawing board and come up with a TLD structure that makes sense. Or maybe even reevaluate the whole DNS idea, because the TLD issue isn't the only, or even the biggest, problem with DNS.

    2. Re:The point of DNS isn't to organize content. by Estanislao+Mart�nez · · Score: 1

      I think you're misunderstanding what I'm getting at. The reason we have different TLDs certainly is about organization as well as delegation of authority. If it was only about authority, why bother having .net, .org, .com, .info, and .biz addresses?

      But my larger point is that that use of TLDs is wrong. You will not solve the organization problems with DNS, simply because there is no one universal scheme of classification that you can apply to all sites in al contexts. Different users of the net will need different classification schemes, and there is no technical reason why DNS should impose one.

      The reason we have those TLDs is because of an attempt to make DNS serve the function I'm arguing it should not serve.

      Schools are supposed to have EDU addresses, government organizations are supposed to have GOV. I believe that ORG addresses were supposed to be non-profits, COM were supposed to be for commercial entities, and NET addresses were supposed to be mainly for ISPs and companies providing network services. And then countries were supposed to have their own addresses for sites specific to their country. The idea was partially so that you'd know the type of organization you were connecting to by its name.

      True, but again: why should DNS encode that as part of the domain name? If you want to know what kind of organization you're connecting to, why not just search the web for information about them? Or, why not consult some sort of trusted, non-DNS database that catalogues organizations of that kind?

      Examples of tools we already have that do this sort of job better than DNS: (a) Google, (b) the Better Business Bureau online database, (c) SSL certificate authorities.

      So I'm just thinking they should go back to the drawing board and come up with a TLD structure that makes sense. Or maybe even reevaluate the whole DNS idea, because the TLD issue isn't the only, or even the biggest, problem with DNS.

      I don't think the TLD structure needs to make any particular amount of sense. Organizing the net with DNS is just using the wrong tool to solve the problems.

    3. Re:The point of DNS isn't to organize content. by nine-times · · Score: 1

      But my larger point is that that use of TLDs is wrong.

      According to who? If it's just according to you, then I wouldn't say it's "wrong". You don't like it, and you don't think it's best. That's fine. But I'm not really "wrong".

      True, but again: why should DNS encode that as part of the domain name? If you want to know what kind of organization you're connecting to, why not just search the web for information about them? Or, why not consult some sort of trusted, non-DNS database that catalogues organizations of that kind?

      If you're not going to use DNS to find and identify anything and instead are only going to use Google, then why bother at all? Why not just stick to IPs? Or if you need a dynamic way of identifying things independently of IPs, why not just issue some other serial number?

      DNS is a naming system. It was built to be treated as hierarchical organizational scheme. If you want it to be a complete free-for-all with no particular organizational structure, I think that's an interesting idea, and would constitute the sort of reevaluation I'm suggesting. It would not be the same as how things stand now.

    4. Re:The point of DNS isn't to organize content. by Estanislao+Mart�nez · · Score: 1

      If you're not going to use DNS to find and identify anything and instead are only going to use Google, then why bother at all? Why not just stick to IPs? Or if you need a dynamic way of identifying things independently of IPs, why not just issue some other serial number?

      I'm not questioning the value of DNS as a layer of abstraction between high-level protocols like HTTP from low-level protocols like IP and TCP. The ability to change what IP address a request to a symbolic hostname gets sent to is of certainly valuable, because a host's IP address is determined by details about routing that are not relevant to a protocol like HTTP. Using symbolic hostnames allows you to make hosting or routing changes that invalidate a host's IP address without breaking existing references to that host.

      I still don't think DNS is a good content addressing scheme for non-technical end users.

    5. Re:The point of DNS isn't to organize content. by nine-times · · Score: 1

      The ability to change what IP address a request to a symbolic hostname gets sent to is of certainly valuable, because a host's IP address is determined by details about routing that are not relevant to a protocol like HTTP

      Right, so then why not just issue a separate serial number that identifies the host and link based on that? Why bother allocating names in a hierarchical system if not in order to organize?

    6. Re:The point of DNS isn't to organize content. by Estanislao+Mart�nez · · Score: 1

      Right, so then why not just issue a separate serial number that identifies the host and link based on that? Why bother allocating names in a hierarchical system if not in order to organize?

      Because the serial numbers scheme would require a centralized authority to issue the numbers. If you wanted a new hostname, you'd have to submit a request to this centralized authority, and wait until it was processed. Under DNS, if you are the holder of the example.com domain, you have the authority to assign names within example.com, and to delegate the authority to assign names within subdomains thereof. When you want to add a new hostname within example.com, you don't need to submit a request to some overworked office that takes a week to process it; you do it yourself at your DNS servers. When the folks you've given a subdomain to need to add a hostname within that subdomain, they also do it at their DNS servers, they don't need to bug you.

      And then there's the issue of who answers queries for the mapping of the serial numbers to IP addresses. If we wanted to have a distributed system for answering queries about which IP each serial number points to, we'd need a system largely equivalent to DNS anyway, except more complicated, because you wouldn't be able to tell anything about a serial number's assignee without examining a database that contains all of the serial numbers. Compare this to DNS, where the hierarchical nature of FQDNs means that each domain server only needs to store a subset of the assignments. Each prefix of an FQDN determines set of DNS servers that can answer questions about the rest of the name. This is what allows the system to get away with no server in the system needing to store anything like the full table of assignments.

      This just goes to demonstrate the point I started this thread with: the point of the hierarchy of domain names is to delegate the authority to assign stable hostnames and respond to queries about assignments. A stable host identifiers system that used purely numeric, meaningless identifiers would have a exact same technical reasons for giving the same sort of hierarchical structure to its numeric host identifiers, so that a stable host ID would be a sequence of numbers, each associated with an authority in the context of the preceding ones.

    7. Re:The point of DNS isn't to organize content. by nine-times · · Score: 1

      Under DNS, if you are the holder of the example.com domain, you have the authority to assign names within example.com, and to delegate the authority to assign names within subdomains thereof.

      I'm talking about domains, not subdomains. I'm saying if the point were not to organize, we wouldn't need to bother having TLDs and domains. We could just issue serial numbers. It'd be simple, and you wouldn't have to deal with domain squatting and such.

      This just goes to demonstrate the point I started this thread with: the point of the hierarchy of domain names is to delegate the authority to assign stable hostnames and respond to queries about assignments.

      No, your point is that's what you want domain names to be about, and think domain names should be about. The truth is that it's not why domain names exist and it's not how they're used. One of the benefits of being hierarchical is that it allows greater organizational units to delegate authority for smaller organizational units to someone else-- that much is true-- but people do create smaller organizational units without delegating authority, too. The intention of making them "names" in the dictionary sense is so that the organization would be capable of meaning things other than just delegation of authority. Domain names are also memorable and identifiable labels, and the hierarchy is also used in such a way as to be descriptive of organization.

  21. Shorter Names, Spreading Power by bill_mcgonigle · · Score: 1

    Further balkanization of gTLD's does nothing for the end user.

    It has the potential to make domain names shorter, that's a good thing.

    Every new motion picture has the domain now, SomeSillySobStoryTHEMOVIE.COM. This is silly.

    SomeSillySobStory.movie would be much more sensible. How does that harm me? I rather like that what's left of Network Solutions will have less of a monopoly power.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    1. Re:Shorter Names, Spreading Power by smoker2 · · Score: 1

      I'm sorry but those (max)4 characters are not enough to make me want to ditch the current working system. All this is, is dilution of the namespace, in order to make more money (as a registrar). the prices won't go down but there will be more work for DNS, which you may note is already under strain.

    2. Re:Shorter Names, Spreading Power by ion.simon.c · · Score: 1

      the prices won't go down...

      Um.
      The prices *should* be next to nothing. I manage my own little corner of the Internet. It's *VERY* easy to add subdomains. Hell, it's even scriptable for fully hands-off management!

    3. Re:Shorter Names, Spreading Power by Mozk · · Score: 1

      Why not just SomeSillySobStory? You don't necessarily need a TLD suffix.

      --
      No existe.
    4. Re:Shorter Names, Spreading Power by bill_mcgonigle · · Score: 1

      Why not just SomeSillySobStory? You don't necessarily need a TLD suffix.

      I heard on the radio today one of the movies up for an award is called 'Milk'.

      Interestingly, Google's algorithms understand this. DNS can't.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    5. Re:Shorter Names, Spreading Power by Mozk · · Score: 1

      How would it be different than it is now? For example, with Nissan.com, which is owned by a company that sells computers rather than the Nissan Motor Company. If you use a general name like Milk or one that is used by other people, of course there will be conflicts. Say there are two movies titled Milk. Where would milk.movies go? A hierarchical system like that doesn't help here, unless you have a more complex system with something like milk.2008.movies and milk.otheryear.movies. In any case, you don't just open a browser and type a domain name like milk.movies expecting it to go where you want unless you see it in an ad.

      So instead of something like having Nissan.cars and Nissan.computers, why not just have NissanCars and NissanComputers, cutting out the TLD "middleman"? The World Wide Web as it is today doesn't really need a hierarchical system like Usenet has.

      --
      No existe.
    6. Re:Shorter Names, Spreading Power by bill_mcgonigle · · Score: 1

      Ah, I understand now. Thanks for clarifying.

      This is pretty much the same as the old 'Mozilla domain guessing' scheme, right? (type in MilkMovie and it goes to 'www.milkmovie.com' automatically (if milkmovie.local fails).

      They basically achieved that user experience using 'www' and '.com' as technical implementation details. I think they gave it up because search engines wound up giving the users an experience they liked better.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    7. Re:Shorter Names, Spreading Power by Mozk · · Score: 1

      No, I'm saying do it at the DNS level. You can have a website on a TLD itself. A Slashdot user here has a page about it, though it's outdated. My point is that you can have a TLD without an SLD. I'm not talking about browsers guessing where you want to go.

      --
      No existe.
    8. Re:Shorter Names, Spreading Power by bill_mcgonigle · · Score: 1

      My point is that you can have a TLD without an SLD. I'm not talking about browsers guessing where you want to go.

      I understand, I was just pointing out that the user experience would be the same.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    9. Re:Shorter Names, Spreading Power by MikeBabcock · · Score: 1

      The new gTLDs wouldn't make any difference unless they're well-managed and regulated. None of the current gTLDs are, so why believe these would be?

      --
      - Michael T. Babcock (Yes, I blog)
    10. Re:Shorter Names, Spreading Power by bill_mcgonigle · · Score: 1

      The new gTLDs wouldn't make any difference unless they're well-managed and regulated. None of the current gTLDs are, so why believe these would be?

      Oh, I make no pretentions that they would be, but what we currently have is poor management, practically no regulation, and artificial scarcity, so prices remain high while quality is low.

      We can't expect, no matter how hard we'd wish it, to get get good management and good regulation (ICANN is worse than useless but they get the contracts and the revenue anyway). So, the best we can do is attempt to defuse the scarcity and open up the field to competition.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  22. More Structure by bill_mcgonigle · · Score: 1

    It is a disgusting thing to do to the Internet, to remove the last semblance of hierarchy and structure in the naming system

    What? This is adding more structure, if done right. Which imparts more structure, to group all animals in a flat bucket called 'animals' (.com) or to pull them out into 'sponges', 'worms', 'molluscs', 'insects', 'chordates', etc (new TLD's)?

    Granted, it's not a multi-level hierarchy, but then again, when was the last time you used the old Yahoo! directory? Ontological organization has been voted off the Internet, for better or worse.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    1. Re:More Structure by Estanislao+Mart�nez · · Score: 1

      What? This is adding more structure, if done right. Which imparts more structure, to group all animals in a flat bucket called 'animals' (.com) or to pull them out into 'sponges', 'worms', 'molluscs', 'insects', 'chordates', etc (new TLD's)?

      But what if I wanted to classify animals by color, instead of taxon?

      The big problem with centralized hierarchical organizational schemas is that the same domain of things can be classified orthogonally according to different criteria, and different classifications are appropriate for different tasks. So you will never be able to choose a "correct" one true classification.

      Granted, it's not a multi-level hierarchy, but then again, when was the last time you used the old Yahoo! directory? Ontological organization has been voted off the Internet, for better or worse.

      Yup. For better, I'd insist.

    2. Re:More Structure by bill_mcgonigle · · Score: 1

      So you will never be able to choose a "correct" one true classification.

      Sure, and nothing prevents registering Slashdot.blue and Slashdot.black. If the TLD's are wide, it can be more of tagging than classification.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    3. Re:More Structure by Workaphobia · · Score: 1

      Huh? I don't understand your argument at all. How is flattening a hierarchy adding more structure, compared with separating out its contents into categories based on their nature? Doesn't your example actually serve as an exact counterexample? How is it more structured to have "sponges", "worms", "trees", "grass", etc., as single-level names, as opposed to "sponges.animals", "worms.animals", "trees.plants", "grass.plants"?

      Ontological organization has been voted off the Internet, for better or worse./blockquote>
      That may be so, but I wish people didn't go ahead and help it on its way, just to artificially create virtual real estate.

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    4. Re:More Structure by Workaphobia · · Score: 1

      Whoops, as you can see, I screwed up the blockquote. Lot of good that preview function does; it just conditioned me to be even less attentive.

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    5. Re:More Structure by Workaphobia · · Score: 1

      Why is no organization better than one organization? Especially when that one organization is authoritative for some legitimate purpose? It's like (bad analogy time!) saying that because you can create different views over a table depending on your needs, you might as well just eliminate the primary key on the actual table. (Indexing and all that crap notwithstanding, the point is why prefer anarchy to order.)

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    6. Re:More Structure by Workaphobia · · Score: 1

      Ug! That's exactly what we DON'T want in DNS! I thought DNS was supposed to convey some notion of authority about its records.

      Much more importantly, why the hell would we willingly step into a situation where we're promoting the metaphor of tagging as a means to organize names, when we don't actually have the freedom (libre) to apply tags in a free (gratis) and easy manner? I'm referring to the fact that registrants would be hemorrhaging money to registrars on a per-tag basis, and for the top level, that would be quite a steep and ludicrous fee.

      It'd be like GMail or your web2.0 application of choice charging you micropayments based on the number of labels you use or even the number of messages you apply them to. You're mixing metaphors in a way that conveys a false sense of liquidity.

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    7. Re:More Structure by bill_mcgonigle · · Score: 1

      Huh? I don't understand your argument at all. How is flattening a hierarchy adding more structure, compared with separating out its contents into categories based on their nature? Doesn't your example actually serve as an exact counterexample? How is it more structured to have "sponges", "worms", "trees", "grass", etc., as single-level names, as opposed to "sponges.animals", "worms.animals", "trees.plants", "grass.plants"?

      We might be agreeing and not communicating, I'm not sure. To whit: you can't have sponges.animals if you don't have .animals.

      Sponges.com and grasses.com is less structured than sponges.animals and grasses.plants.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    8. Re:More Structure by bill_mcgonigle · · Score: 1

      I'm referring to the fact that registrants would be hemorrhaging money to registrars on a per-tag basis, and for the top level, that would be quite a steep and ludicrous fee.

      Sure, if it's limited. If it's unlimited then it gets reasonable, nobody can afford to register 'everything' then.

      The point of broad TLD's is only to serve as disambiguation, the way we have, say trademark categories. So, if I run McGonigle's Furniture Repair, I might want mcgonigle.furniture and perhaps mcgonigle.antiques. I have no use for mcgonigle.birds and mcgonigle.candy or any of tens of thousands of other TLD's.

      I can't imagine DNS would ever supplant semantic or even text search.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    9. Re:More Structure by MikeBabcock · · Score: 1

      And what's stopping someone from adding "trees." and "grass." as top levels as well as "trees.plants." and "trees.plants.greenstuff." ?

      Additional top-level domains will both allow intelligent domain operators to organize their data better and make life more confusing and less predictable for users.

      --
      - Michael T. Babcock (Yes, I blog)
    10. Re:More Structure by bill_mcgonigle · · Score: 1

      Additional top-level domains will both allow intelligent domain operators to organize their data better and make life more confusing and less predictable for users.

      True, and since DNS was never intended to be used by users, this might be OK. Most people I know effectively use Google, via start page or searchbar for their navigation. Some even type DNS-based locations directly into the Google search box and click the link. That one I don't get - maybe because the Google search box grabs cursor focus (but that just delays the click...).

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    11. Re:More Structure by Workaphobia · · Score: 1

      Yes, I agree that .com's meaning has been changed and diluted by the 90s, to the point that it no longer represents what it originally was supposed to, contributing to end user confusion and unnecessary defensive name grabbing. But I don't see how giving everyone their own TLD is a step up.

      The closer to the root a name is, the more compelling the taxonomical justification for its existence should be. At the closest level is the root itself, then the "top" level of country jurisdictions, then categories specifying a purpose such as commerce or public forum, etc.

      Keeping with our organism taxonomy analogy, I'd rather see sponges.animals.org.us and grasses.plants.org.us.

      I realize this is entirely unrealistic at this point, but I'm trying to be idealistic about what an ideal naming system would look like. There might also have to be some kind of local automatic suffix system to shorten lengthy names, so that a user in the United States might be able to omit the trailing .us for brevity. Those kinds of details I feel are secondary to the more important goals of clarity and authority that are conveyed by a domain name.

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    12. Re:More Structure by Workaphobia · · Score: 1

      Allowing anyone to register TLDs in a fairly non-restricted manner is rubbish because it undermines hierarchy and permits exactly that kind of pointless redundancy. If on the other hand no one but sovereign nations had control of a TLD, there might be a bit more order in the namespace. I'm not suggesting there wouldn't still be significant hurdles, I'm just saying it would be less of an embarrassment. I'm sick of gimicks in place of sound structure.

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    13. Re:More Structure by Workaphobia · · Score: 1

      Ah, but who controls the hypothetical and absurdly generic TLD name "furniture"? How on Earth is it fair to allow some middleman to usurp a piece of the TLD space, so that they have influence or even monopoly control over who in the industry is allowed to play?

      Wireless telecommunications companies have created the disgustingly artificial space of commercial texting numbers so that they could grow and culture an industry of crap on your cellphone, and reap a sizable share of the profits. It's a closed network in stark opposition to the Internet's openness. Why would we want to emulate that? Why would we want to give private entities control over what has basically been community property? It's a betrayal of the purpose of the Internet and the credibility that the network has earned.

      These TLDs should be in the control of neutral or governing parties, not private third parties.

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    14. Re:More Structure by MikeBabcock · · Score: 1

      I told a user to visit a website, say "ford.com" and watched them type "Google" into their MSN homepage, then type "ford.com" into the Google search, then click the first result.

      --
      - Michael T. Babcock (Yes, I blog)
  23. Walled gardens exist today. Vanity TLD or not. by jbn-o · · Score: 1

    I fail to see how setting up a set of services with strictly enforced rules is any different from what we already have. What does the arrangement you describe have to do with new top-level domain names? There might be plenty of valid reasons to object to new TLDs but yours doesn't strike me as a reason to object to any new TLD.

  24. It's unused because it's retarded. by Anonymous Coward · · Score: 0

    Names should either be intuitive or short. "dot name" is neither, especially when it's "Selma Beefendorfer dot name". The brits were smart enough to use .co instead of .com in JANET.

    "xxx" is an awesome TLD. Everyone would remember it.

    1. Re:It's unused because it's retarded. by MikeBabcock · · Score: 1

      "slash" would be a fun TLD. "x" alone would be too. One of the fun domain names I never forget is cr.yp.to made possible by the "to" ccTLD.

      I can see major companies buying their own names as TLDs to create domains like "ftp.dev.intel" or "update.office.ms"

      --
      - Michael T. Babcock (Yes, I blog)
  25. Other way around by Jay+L · · Score: 1

    With only a few gTLDs, you're right - there's no obvious difference between .com and .net. So everyone with a trademark wants to register their trademark in every gTLD, which only reinforces the lack of distinction between them. And so consumers don't really understand what a gTLD is; they think ".com" is part of the "noise" of the URL, like "http://www.". Which, again, becomes a self-fulfilling proposition.

    I don't know if the right number of gTLDs is hundreds or thousands, but the right number is "more than most trademark holders are willing to pay for". In trademark law itself, there are categories of trademarks, and most don't rise to the level of what IIRC are called "famous marks" - trademarks that are protected no matter how they're used. (You could maybe sell a stuffed toy and call it the Caterpillar, but you couldn't call it the Google.)

    We need to get gTLDs to that point, where most second-level domains (cisco.com) are unique only within the gTLD (.com), or a group of gTLDs (.com, .network, .wifi) and nobody cares about other gTLDs - because consumers wouldn't expect to see the trademark in that context (cisco.rap-music? No, you must be looking for sisqo.rap-music). It's self-reinforcing in both directions.

    Think back to phone numbers, before 10-digit dialing. Companies tried to pick memorable phone numbers. Some companies that operated in multiple area codes reserved the same number in each area code - so you could always call 736-5000 and get a tow truck anywhere in New York, or whatever. Some brands were so strongly associated with their phone number that they were set up in EVERY area code - 936-3636 for dial-a-santa.

    With ~200 area codes, and only a handful serving any one region, this was feasible. Once you went to a thousand area codes, with overlays and cell-phones confusing the mix, and ten-digit dialing, it became pointless. Now, the only "area-code-free" numbers are the x11 numbers.

    gTLDs are like area codes.

  26. Re: by rfunches · · Score: 1

    For some, the web isn't even ".com," it's whatever name they type in the address bar sans TLD. I had a user complain that she couldn't access Google. She edited the URL already in the address bar to read "http://www.google" and didn't know why she was getting the 404. (I guess there's a browser which will append a ".com" without using a specific keystroke?)

    With other users getting to Google from their Yahoo home page by searching for "google" and clicking on the first link, I wouldn't bet on gTLDs going too far with the user base. It will probably only be a cash cow for ICANN and the major search engines.