
New ICANN TLDs Are Live 174
BenBenBen writes "According to this story on the BBC, several of the new ICANN top level domains now have sites available. Examples are visa.info and afilias.info. " I'm still waiting to get my 'dot' TLD. The article doesn't say much new except it tells us a few biz and info sites that you can use if you just wanna see a new TLD working. I gotta say, it's pretty surreal.
New TLD's (Score:1)
Re:New TLD's (Score:1)
I already have slash.dot, or at least I had it
until Nielsen vanished from the earth and
apparently took
the slashdot.org censored articles
Leto
Re:New TLD's (Score:2, Insightful)
The only people I have seen bullying anyone have been the rogue TLDs.
There are plenty of name squatters who have bought up new.net swampland who would like their real estate to be connected up to the interstate. So they yammer on with squeals of complaint.
Re:New TLD's (Score:2)
You don't need an addon to windows or linux for this - it's built into the OS, even in Windows - windows has a perfectly normal hosts.txt file, since it's network stack is from BSD.
I'm just kinda surprised this doesn't happen more often - you could have people swapping personal lists of "cool" aliases - "but hyperlinks would stop working if the world didn't all use the same DNS root servers?" - well, maybe, but so what? The fragmentation impact would be much reduced since most web-pages have very domain-specific forests of links, so a short statement of "we use such-and-such's TLDs" on a site would usually be enough to sort things out, since most links would be to other pages within the same "family".
All this could be made very pointy-clicky for the drooling idiots of the world - in fact, it would keep them entertained for hours, making their computer think www.popularfootballteam.com or whatever was called wank.droolers.suck.suck.suck...
Re:New TLD's (Score:3, Funny)
> I think that icann should stop bullying people around and let some of the rouge TLD's in.
Yes, but if they allow rouge now they'll end up having to allow all kind of other crazy colors later, so they need to hold the line as long as they can.
Color me shocked. (Score:2, Insightful)
Re:Color me shocked. (Score:1)
The rest of us are reeling in shock from it.
Honest.
Re:Color me shocked. (Score:2)
The rest of us are reeling in shock from it.
Now, don't get too upset. If you need to talk it out with someone, online counselors are available at www.tld-trauma.info.Honest.
Or it that
Maybe it's
Ah, hell. Forget it. Just deal.
new TLD's never thought it would happen (Score:3, Insightful)
I don't know how to feel strangely, because we have known it will eventually happen, but it seems a little bit has been lost in the process of change.
I'm not against change, I just ponder where we are heading...
Commercial Internet (Score:1)
Ok, it won't make it easy, since most of the dictionary is probably sold already anyway, but it will help.
Don't buy .sex domains! It's not a real TLD! (Score:5, Informative)
When you buy a
But it won't work for all the rest of the world. You'll be charged $75 for a domain that nobody will see.
Take care, there are a lot of registrar registering ".sex" domains, saying that "they soon will be available as real TLDs". But that's untrue. Nobody knows whether it will even happen. But your credit card will be billed.
Why We Don't Need A .sex (Score:3, Insightful)
Re:Why We Don't Need A .sex (Score:3, Redundant)
Good point! [whitehouse.com]
(Seriously, I do agree with you and besides this venerable exception and the oft-mentioned difficulty of getting good clean musical fun after typing "Britney Spears" into a search engine (although lately even the official Britney material is becoming delightfully unclean), there really is no real possibility of confusing porn and non-porn sites. IMO while a
Duh... (Score:1)
I would hope the average Slashdot community member would know that. Then again, I've seen some wierd posts that could disprove that theory.
Don't buy
Re:Don't buy .sex domains! It's not a real TLD! (Score:1)
Re:Don't buy .sex domains! It's not a real TLD! (Score:1)
Besides,
Re:Don't buy .sex domains! It's not a real TLD! (Score:2)
But it won't work for all the rest of the world. You'll be charged $75 for a domain that nobody will see.
Now THAT'S what I call getting well screwed
Not real yet (Score:2)
Still won't clean up the rest of the net. Only a proven lack of demand will do that. Too bad there's a new one born every minute.
Re:Not real yet (Score:2)
dot info?? (Score:1)
There is one plus that I can think of. Maybe people will start to realize that not everything is a "dot com".
Re:dot info?? (Score:2, Flamebait)
So the only new tld's suck.
LIke '.biz'. Yeah.. that's useful..
Isn't everything on the net about information? (Score:3, Interesting)
I think they were created for two reasons:
1. To increase sales for registrars.
2. To help people find shorter names for their web sites.
Have you tried to search for a
Re: (Score:3, Insightful)
Re:Isn't everything on the net about information? (Score:1)
Why This Is A Bad Idea... (Score:5, Insightful)
These domains add confusion and too much generality. At the risk of a TLD being too long, why not create a ".store" for retail fronts, or ".gr(ou)p" for non-established organizations (that one would be great for OSS developers). How about extending the concept of the
I may just be blowing my horn here, but these things are just plain dumb. Some of my suggestions here may add some confusion, but won't adding to the mess also do that in a less constructive way?
Re:Why This Is A Bad Idea... (Score:2, Insightful)
Country codes are enough. How would you be meant to know where in the world that region truely is?
Re:Why This Is A Bad Idea... (Score:1)
Anyway, you can achieve that very easily using the
non-domain part of your URL:
www.somecompany.com/east (or west, or tanzania, or whatever)
Re:Why This Is A Bad Idea... (Score:1)
Also, most ORGanization sites might be informational, but most INFOrmational sites aren't necessarily organizations. I know I was looking to put up a specific product news site awhile back. I couldn't find a good
What astonishes me is how LONG it took to implement them. What the hell took so long?!
Re:Why This Is A Bad Idea... (Score:3, Insightful)
Why not hand out TLDs themselves? So Dell could have 'dell' and make www.dell and so on under there. That is the least insane way to do things given the current legal system.
(Of course the sane way would be to go for TLDs where the legal procedures are clearly defined:
Re:Why This Is A Bad Idea... (Score:3, Insightful)
Right know Foobar Computers and Foobar Foodstuff are fighting over the domain foobar.com. If you get rid of TLDs, they will fight for .foobar. What's the difference?
Using trademarks for domain names won't work either. Foobar Computers and Foobar Foodstuff may well both have a trademark on the word Foobar, but for different products.
For a fun real-world illustration, see this page [bell-labs.com]. It lists many products called "Unix", such as Unix® diapers and Unix eyeglass frames.
The only solution I see, is (a) getting rid of .com, .net, etc. and only keep the regional domains and maybe .int, and (b) force organisations to use their full name. Of course, you won't have short URLs with this scheme...
Re:Why This Is A Bad Idea... (Score:1)
Re:Why This Is A Bad Idea... (Score:3, Interesting)
.foobar should list all demains which involve foobar, kinda like how alteon.com [alteon.com] lets you see both the Alteon pharmacuticals group, and Alteon web systems.
This is how two entities with trademarks to the same name, but in different fields, can co-exist peacefully.
Re:Why This Is A Bad Idea... (Score:2)
Re:Why This Is A Bad Idea... (Score:1)
Re:Why This Is A Bad Idea... (Score:2)
Re:Why This Is A Bad Idea... (Score:2)
Below is a simplified description of how the caching works:
Most internet users use their ISPs DNS server as their nameserver.
That nameserver will cache the result of any query up to a specified amount of time (the maximum value you're supposed to cache an entry is provided to you in the response when you query a DNS server).
Now, if you request www.foo.bar, your machine will query your ISPs DNS server, and if www.foo.bar isn't cached, the DNS server will strip off the leftmost part, and check if information about which nameservers serve foo.bar is cached.
If it isn't, then it will strip off the next part, and so on. If it can't find the TLD in its cache, it will ask the root servers.
If foo.bar is found in the cache, however, your ISPs nameserver will request info on www.foo.bar from one of the nameservers responsible for foo.bar, and cache that data for future reference.
So if someone else using your ISP has accessed any domain on the top-level domain "bar" recently, the nameserver info for the TLD "bar" will likely be in the cache, and valid.
And if someone else using your ISP has accessed foo.bar, or any host under foo.bar, information about foo.bar is likely in your ISPs DNS cache.
And if they've looked up www.foo.bar in particular, even that may be in the cache.
So only a small percentage of all lookups of a domain will actually cause a hit on the root servers, quite few will avoid hitting the nameservers for the specific TLDs, and for quite a few domains much of the data will be cached at your ISP most of the time.
Allowing people to register directly under the root would mean that the number of lookups in the root servers would go through the roof, as there is one less level of caching, and the network of root servers would have to be able to cope with a load similar to all the current TLDs combined, as opposed to "only" when nameserver info for a TLD has expired from the cache somewhere - the traffic volume is high enough as it is.
Re:Why This Is A Bad Idea... (Score:2)
Re:Why This Is A Bad Idea... (Score:2)
That also doesn't take into accounts new TLDs like ".name", which has a very different market from the three above, and which gets significant interest. It also doesn't take into account that the seven new TLDs introduced now is only a "proof-of-consept" phase for ICANN, and that if things work out reasonably well, we can expect further new TLDs to be approved in the future.
(ObDisclaimer: I co-founded the company that operates .name)
Re:Why This Is A Bad Idea... (Score:2)
In addition there's less reason for trademark holders to object to a name that collides, as they can't themselves register the name anyway, and as such their only reason to go after you is if they believe you're infringing on their trademark - not to get control over the domain themselves.
Of course, if you get the domain e.toys.name and start selling toys on the website, then Etoys will likely come after you no matter what your name is, and they'd likely win, as there'd be a real chance of confusing people into believing they were actually shopping from Etoys.
Re:Why This Is A Bad Idea... (Score:2)
Too vague? It's the enforcement of domain use policy that's too vague.
Are you a COMpany? .com .net .org .edu .gov .mil
Are you running a NETwork?
Are you running an ORGanization?
Are you doing this for an EDUcational institution?
Is this for the GOVernment?
MILitary?
What's too vague about that? I agree that adding more TLDs will create confusion, but there's not confusion now.
Re:Why This Is A Bad Idea... (Score:1)
Is Slashdot the Government? No.
Is Slashdot the Military? No.
Is Slashdot a Network? It might qualify as "network of geeks"
Is Slashdot educational? Sometimes.
Is Slashdot a company? It's somehow part of the OSDnetwork which is a COMpany.
Is Slashdot an ORGanization? See "network".
So what is the TLD you think slashdot should have?
(other than CT's favorite slash.dot)
Re:yes, it is vague (Score:2)
The FBI is a government agency first and foremost, therefore, it belongs in .gov. St Timothy Christian Academy is a school, first and foremost, therefore .edu is fine, IMO.
Still waiting for a good example...
Re:Why This Is A Bad Idea... (Score:1)
.... I may just be blowing my horn here, but these things are just plain dumb
Ok, they may add confusion, and they may be dumb, but there is one thing they will do very well - adding to the profits of the registars.
Do you really believe that these decisions were made for the good of the people in general? The only reason these came into existance was to make the people in power more money.
Re:Why This Is A Bad Idea... (Score:1)
Hmmm... when we're at it, we could just reintroduce the good old ICBM addressing ;-)
hohoho (Score:3, Funny)
Re:hohoho (Score:5, Funny)
Re:hohoho (Score:1)
Aww too bad. A couple of more slashes and we might have had morse code for 'sos' (Ya, I know SOS in morse is '. . . / / / . .
Still funny just the same.
Re:hohoho (Score:1)
www.dot.dot
Re:hohoho (Score:2)
You could simplify that to "slash.dot".
I'm still waiting for (Score:1, Funny)
and of course (Score:2, Funny)
Re:and of course (Score:1)
Now they only need to set up the obvious hostname... http://info.info.info
.sex? (Score:3, Funny)
That's a good sign (Score:1)
Maybe it isn't the TLDs... (Score:1)
"I gotta say, it's pretty surreal." (Score:1)
[circumventing lameness filter]
So young, and already abused. (Score:4, Interesting)
Trademark Name: SEX
Trademark Date: 2000-01-04
Trademark Country: USA
Trademark Number: 2306348
As a search on The USPTO [uspto.gov] shows, a very specific rendering of "sex" is trademarked by a Jaime M Cerrato, to be used for "games, playthings and novelty items, namely, mechanical pull toys." This trademark was used by Hera Ventures and Investments, Ltd. to register sex.info. Somehow, I doubt the only thing that site is going to be doing is selling "mechinal pull toys". Dirty trick or outright fraud? I don't know, but it's obviously abuse.
Re:So young, and already abused. (Score:1)
So, what do we get instead? The website of some wanker who managed to send the paperwork into the USPTO.
I guess little Jimmy will technically get information at sex.info
the reason for "traditional TLDs" (Score:3, Insightful)
How many people are going to remember that my site is not www.thinkbrown.com but instead www.thinkbrown.info or www.thinkbrown.TLDoftheday?
Heck, why don't we go one step furhter, I want to define my own TLDs.
I don't buy into the arguement that traditional TLDs are all taken.... just stop the domain squatters and you'll be happy.
I wonder (Score:3, Insightful)
Is this the worlds biggest DNS server? Meta DNS? Seriously, though, how many companies who snatch up an
How do you think companies will react? (Score:3, Interesting)
finnair.fi [finnair.fi] already belongs to Finnair
finnair.com [finnair.com] as well, as they're doing business in many countries so they'll need an "international" commercial domain
finnair.aero just because they're dealing with aviation
finnair.biz because they're doing business
finnair.pro - well, they're professionals after all
finnair.info, timetables anyone?
Nice move, ICANN.
Re:How do you think companies will react? (Score:3, Informative)
Now, whether that's useful to anyone, I don't know. But no finnair.pro, I'm afraid.
Thanks,
Matt
Note: I work for a domain registrar, but I don't speak for one.
Konqueror can't handle the new TLD (Score:1)
[Actually, it's just crappy HTML code with frames. Too bad people still can't code.]
I wonder how long it will take for the 7 'forbidden' words to make it to TLD; now that would be news.
Re:Konqueror can't handle the new TLD (Score:1)
Of course, you know this is gonna lead... (Score:2)
Re:Of course, you know this is gonna lead... (Score:1, Informative)
Didn't get mine.... :-( (Score:5, Insightful)
Well, I was really going to rant about trademarks. TMs is usually the part of IP regime that I find the least problematic, but. There is something strange there.
Here's my story:
I have for several years maintained a site titled "How to use a compass" [folk.uio.no]. Since I've been orienteering for many years, and just because I could write this, just because the web allowed me to become a publisher, I did write it up.
It is time for the site to move on, I intend to open it up for many contributors. I intend to get a few excellent orienteers and expeditionists to join me in making this site even better, and I intend to release it under the GNU Free Documentation License (but with some modifications to allow people to print and distribute printouts more easily).
Obviously, I should have a domain for it. While I have other options, what can possibly be more fitting for this site than compass.info? It is the most used compass tutorial on the web, there are a few of them, but most are actually using my illustrations... The site is literally information about the centuries-old gadget called a compass.
However, it has been decided that trademarks owners should have a prior right to our language (eh, well, English is not my native tongue, I'm Norwegian). They should be allowed to grab first, and so, compass.info is gone. Like in some many cases, the compass has been used metaphorically. There is actually very little information about the gadget compass on the web, but there is extensive use of the term "compass" used metaphorically. In fact, this is a problem I've had when designing metadata for the site.
I'm quite confident (yep, I do have some self-confidence :-) ), that if
the delegation of domain names had been based on what merit a site has for
accurately describing what lies in a name, my site would have won... :-)
So, what is it with trademarks that makes them so valuable for mankind that it is more important that the domain name compass.info is used do point to a product that has nothing to do with what has for centuries been known as a compass, rather than an accurate description on how to use this gadget....?
I do not doubt that the American College Testing Program [act.org], who has been awarded compass.info has good intentions for it, but still, the question stands, why is it that trademarks should have that level of protection?
I feel there is something wrong about all this. Names are a scarce resource, and should be treated with caution. I feel the use of trademarks needs a review. This isn't what they are supposed to be: My parents went to China and bought "The North Face" jackets with a Gore-Tex membran for just about nothing. While they realize it certainly aren't real North Face jackets, I have yet to convince them it certainly has no Gore-Tex membran. They are going to get seriously wet one of these days... :-)
That's what trademarks are supposed to do for us: protect us from being
sold crap. They're not supposed to be used for grabbing bits and pieces
of living langauges...
New TLDs need to be reconsidered (Score:5, Insightful)
Let me just talk about .ws for a second. This is the most meaningless TLD of them all. The nodename part of a domainname should specify what the service is i.e. www, smtp, ns, nntp, etc... otherwise we need to create all these others as TLDs as well, which I'm sure everyone would agree is silly.
And to those who have posted that we need regional TLDs, we have those already. The are called country code TLDs. In fact I think we should get rid of .com, .net, .org, .edu, and .gov and stick them under .us. It seems to work for the UK and Australia. A company should have to register a .com.ccTLD for the countries they exist in. The Internet is not just the United States anymore.
In summary new TLDs only polute the DNS name space.
Artifical Limitation (Score:1)
Re:Artifical Limitation (Score:1)
The theory was the same name could exist on separate TLDs, owned by separate people, doing different things.
apple.net wasn't supposed to be apple.com wasn't supposed to be apple.org. So instead of .apple, you'd have at least three domain hierarchies under .apple.TLD.
That's not a limitation, that's compartmentalizing and therefore broadening the namespace.
Re:New TLDs need to be reconsidered (Score:2, Insightful)
ORG - This domain is intended as the miscellaneous TLD for organizations that didn't fit anywhere else. Some non-government organizations may fit here.
See - its miscellaneous. In addition,
As far as polluting the namespace - the DNS system is designed to support a large number of TLDs. The restraints that need to be placed are policy ones, not technical ones.
Thanks,
Matt
Note: Although I work for a domain registrar, I don't speak for one.
Re:New TLDs need to be reconsidered (Score:1, Interesting)
1) COM/ORG/NET were always international domains, however they've always been managed by the US governenment
2) COM is popular in the UK and Australia.
3) Country code domain policy is under local administration. There is no such thing as
4) GOV/MIL/EDU are historical accidents that show a bias towards the government that built the Internet. There's no feasible way to obsolete these domains, and until you think of one, forget trying. How many UKians are even aware of MIL anyway? Most USians aren't (goarmy.com).
5) The Domain system was never intended to be the greatest rational hierarchy or a means of locating information -- it was always intended to be layered with other directory systems (Yahoo, Switchboard, 'Internet keywords', whatever). Get that through your head.
6) Trying to reform the domain name system at this point is like trying switch over to metric time. Unless you have a time machine and can go back to 1988 and discuss it with Jon Postel, forget about it. Now.
7) Adding a couple new TLDs does seem like a pointless exercise, or even extorition by the registrars. However, keep in mind that these are just a test run for planned massive expansion of TLDs. Given enough of them, it will be virutally impossible for a company to buy all of them, or for squatters to eat up the namespace. I'm not going to make a judgement of whether this is a good idea, only that it's too early to tell. (see #5) One point is that it's culturally and techincally very difficult to contract the namespace, but it's easy to expand it.
Re:New TLDs need to be reconsidered (Score:1)
Re:New TLDs need to be reconsidered (Score:1)
Erm.... (Score:1)
slashdot.info
go get it.....
An idea... (Score:1)
Where is a good place is get one? (Score:1)
[OT][Urgent] Last day for RFC on patent-based WWW (Score:1, Offtopic)
"On 16 August 2001 the W3C made public a proposal to substantially change their patent policy framework. Amongst the changes is support for a new licensing model (called RAND) that legitimises the W3C's role in developing and promoting standards that could require the payment of royalties."
Today, September 30, is the last day for submitting a comment. You can read more about this at Linux Today [linuxtoday.com].
Act now, while you can still access the Web via free software.
TLD propaganda (Score:2, Insightful)
THOUSANDs of new open TLDs will not solve any problem - even if every one has 'Sunrise Period'
It will not solve 'consumer confusion', 'trademark conflict' or stop anybody 'passing off'.
Also, as an example on Sunrise, thousands of trademarks using word 'Apple' have no guarantee of being able to use name.
Apple computers will still protect and make claim to every Apple.[anything] - even though they share word with 727 others in the USA alone (plus all those in 200+ countries).
TRUE or FALSE?
No reply required - I know the TRUTH - The solution to trademark problem is at WIPO.org.uk [wipo.org.uk].
Say what? (Score:1)
To quote:
Woo hoo!
Sign me up!
[we're in the money.. c'mon my honey...]
t_t_b
anything.moreso (Score:1)
Personally, I beleive that TLDs should be taken care of just like domains are. Though, moving off track, subdomains are taken care of exclusively on the domain's server, without any interaction with the registrar. Not that I am saying this should be the same for TLDs, but te route of the subdomain works well for domains now.
TLDs on the other hand should be registered with the registrar, but as soon as it is created [.conesus perhaps] anyone can now register domains on that TLD. Or maybe just have every TLD as part of the domain. Instead of removing the TLDs completely [http://conesus], there could be a two part domain system, replacing the one part domain, and one part fixed TLD. [http://conesus.web-design] or [http://microsoft.software] or even [http://microsoft.porn]. That way, Microsoft wouldn't be concerned about registering microsoft.porn, because nobody would even go there if they were looking for a microsoft product.
If we [as humans, not just US citizens] can remember phone numbers for all the people/family/friends/businesses we call regularly, then why can't we remember two-part names that can be easily looked up [by Google, or by asking, or by looking at that piece of paper you got when you were wondering about a piece of software, and a representative gave you the web address]. This solves a lot of these .com problems, but what I am really wondering is, how many new problems are created when we remove the TLD system, and institute a two part domain system, so not every word is taken.
Re:anything.moreso (Score:1)
Speak for yourself...
t_t_b
TLD contacts... (Score:4, Informative)
There's always http://www.icann.org/tlds/
If you want to voice your concerns about a specific issue with the new domains. Direct contacts, that's evil, I wonder if they will read all their mail.
New TLDs aren't new. (Score:3, Informative)
limited subsets of the 'Net for some time.
Check out OpenNIC's site [opennic.net] for a host of information about an internet namespace that's administered democratically. (There are several such namespaces, many of which are coalescing into a large, collaborative space run by the people,
for the people. OpenNIC is particularly well
run.)
The new ICANN standards actually conflict with pre-existing namespaces (such as
All you have to do is point your DNS server into
the OpenNIC tree...
What is .int? (Score:2)
What is
Shaun
Re:What is .int? (Score:2, Informative)
This one's not new, but rather is one of the "special" TLDs, alongside .gov, .edu, and .mil. Its used for International Organizations, such as the United Nations [un.int].
Re:What is .int? (Score:3, Funny)
Not to be confused with the United Nations Special Interest Group for Networking Educational Districts [unsigned.int].
(You may now groan).
Re:What is .int? (Score:3, Informative)
Well, it is for "international organizations", but in this context, they have decided to follow the definition used by the International Law on Treaties, in which "international organization" is defined to be "intergovernmental organization", such as the UN, WHO, etc. What they say is that to get a .int, the organization would have to be formed by an international treaty between governments (there is another option: international databases).
However, it should be quite clear that the International Law of Treaties never intended to give a general definition of "international organization", so what has happened is that most organizations that are international has been excluded. I for one think that IAPS belongs in .int.
Now the really bad part of this is that certain organizations has been allowed to get .int though they have not been formed by international treaties, for example YMCA [ymca.int]. YMCA has a similar formation history as IAPS, and does certainly not fit the criteria used. I think they do belong in .int, but it kind of makes you wonder what they did to get that name.
.biz lottery (Score:1)
I wanted to get a certain
One critical loophole: the initial pre-registration period is also meant to allow those with trademark or "intellectual property" claims to a name to challenge your right to register it. While this sounds like a good way to protect legitimate rights, it just allowed people time to register all kinds of bogus claims with the USPTO [uspto.gov]. Last week I received a notice from Neuland (?) informing me that 15 or 20 people had "IP" claims to my domain. What should I do? Do I have any chance, as a non-corporate-lawyer-holding netizen of preserving my rights to the name even if I happen to be awarded it? I'd think that I should have just as much right to it as anybody else considering there's no "prior use" of the
afilias not new (Score:1)
Silly waste of money but hey, its their money (Score:2)
.www TLD (Score:2, Funny)
Just wanted to remind everyone... (Score:1)
.info is a mess! (Score:1)
pre-registration process (the "sunrise" period for
trademark holders) has resulted in a profound mess.
highlights include music.info pre-registered with a
corea trademark for "dumping", analsex.info with a
morocco trademark for "sandip singh sandhu", or
newyork.info obtained by the holder of the u.s.
trademark no. "e.g. 12345". dozens of domains were
given to the holder(s) of an albanian patent for
"unknown", issued on january 2, 2040.
during "sunrise", one individual from austria has
pre-registered no less than 4981
another guy has not only successfully filed
trademarks for lawyers.info and attorneys.info, but
also for blowjobs.info and teensex.info. other
domain names, like hawaii.info, have been taken over by registrars for "testing purposes".
if you want more info on
icann forum [icann.org]
the internet challenge [theinternetchallenge.com]
Re:.info is a mess! (Score:1)
Re:.info is a mess! (Score:1)
-cryptophiliac
.name oddness (Score:1)
Does anyone know? Will "bob.smith.name" actually be a different domain from "john.smith.name"?
Re:.name oddness (Score:2)
So presumably Rob would get away with commander.taco.name, for instance.
As for registrations on the third level, technically that is trivially easy. The reason that has been done is so that the second level can be shared for mail purposes. So while under .com only one of Bob Smith and John Smith would be able to get smith.com, and use bob@smith.com or john@smith.com, unless they could agree to share it (or Bob could decide to register bobsmith.com, and get a crappy mail address like bob@bobsmith.com, or similar), under .name they can get bob.smith.name/bob@smith.name and john.smith.name/john@smith.name respectively.
Some data I took out on that this weekend shows that in the US, for the 65000 most common lastnames, 22 million people would be able to get their firstname.lastname.name without doing anything special. If you take into account nicknames, use of initials, use of hyphens etc., that number increases to more than 100 million that can get a nice name-based e-mail address on the form firstname@lastname.name, as opposed to only 65000 if noone share the second level.
If you add in the people with less common lastnames, the number increase to about 170 million in the US alone, before you need to start doing stuff like adding numbers.
Of course, for more common last names, like Smith, using numbers will be necessary quite a lot earlier than for less common lastnames.
(Ob Disclaimer: I co-founded the company that operates .name, but I'm talking only for myself)
More chaos with TLDs (Score:1)
Since
Therefore, buy searching
Surely more TLD's are only going to move further away from the geographical reality of the world and further confuse a lot of information.
In fact, if I could start again, I'd trash
Re:WTC HAH!! (Score:2)
Oh, Please... We should be so lucky here at slashdot to be able to call up some special forces mo-fo's to clean you guys out with K-Bars and sniper rifles.
Unfortunately, we simply do not have the clout necessary. But, if it makes you feel better, the moderators we send over there will be knocking them down a little lower than -1.
krystal_blade