What's in a gTLD?
economist.com
What's in a gTLD?
1–10 of 11 posts
Re: What's in a gTLD?
#2Trademarks in which country / how do they plan to cope with conflicting trademarks?
Geographic protections, .norfolk - does that refer to the county in the UK or to one of the places in the US, or else where?
Re: What's in a gTLD?
#3I'd like to hear more about the trademark and geographic protections. Trademarks in which country / how do they plan to cope with conflicting trademarks? Geographic protections, .norfolk - does that refer to the county in the UK or to one of the places in the US, or else where?
Trademark protections come in three parts. At the top level a trademark holder can object to you applying for a TLD that is an exact match for a trademark they hold in any jurisdiction. There are provision for trademark front running as well here. At the second level registries are required to provide protection for trademark holders both at registry start up (sunrise and landrush) as well as for ongoing operations. The protections during sunrise and landrush are stronger than during ongoing operations.
During sunrise and landrush registries are required to restrict registrations that are an exact match to marks in the trademark clearing house. They are also required to implement the Uniform Rapid Suspension (URS) during sunrise and landrush and the first 60 days of general availability. There is also a requirement for the UDRP for ongoing operations but this is almost exactly the same for other existing gTLDs (ccTLDs are a different matter).
Obviously there are corner cases to the above and there are a large number of details involved. If you want more information a good starting point is the Applicant Guidebook which you can get from this link:
http://newgtlds.icann.org/en/applicants/agb
EDIT: added information about UDRP.
Re: What's in a gTLD?
#4Not true, and you can see it yourself:
Nothing technically prevents a TLD from having an A record, it's just uncommon. So there could very well be http://microsoft/ or http://apple/, which would appear as "microsoft" and "apple" in FF and Chrome, at least.
Re: What's in a gTLD?
#5Right now you can guess that a company's web address is probably companyname.com, but .companyname alone can't be a web address. Not true, and you can see it yourself: http://ac/ http://ai/ http://tm/ Nothing technically prevents a TLD from having an A record, it's just uncommon. So there could very well be http://microsoft/ or http://apple/ , which would appear as "microsoft" and "apple" in FF and Chrome, at least.
nslookup tm
Non-existent domain
Browsers are able to reach them by forwarding to ac.com, ai.com or tm.comRe: What's in a gTLD?
#6Right now you can guess that a company's web address is probably companyname.com, but .companyname alone can't be a web address. Not true, and you can see it yourself: http://ac/ http://ai/ http://tm/ Nothing technically prevents a TLD from having an A record, it's just uncommon. So there could very well be http://microsoft/ or http://apple/ , which would appear as "microsoft" and "apple" in FF and Chrome, at least.
You should also note that email addresses that doesn't have a '.' in the host part are technically invalid, i.e. me@mytld is not a valid fully qualified email address.
Re: What's in a gTLD?
#7Right now you can guess that a company's web address is probably companyname.com, but .companyname alone can't be a web address. Not true, and you can see it yourself: http://ac/ http://ai/ http://tm/ Nothing technically prevents a TLD from having an A record, it's just uncommon. So there could very well be http://microsoft/ or http://apple/ , which would appear as "microsoft" and "apple" in FF and Chrome, at least.
Are you sure about that? ac, ai and tm do not resolve: nslookup tm Non-existent domain Browsers are able to reach them by forwarding to ac.com, ai.com or tm.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: tm
Address: 193.223.78.213
Seems to be working for me.Re: What's in a gTLD?
#8Right now you can guess that a company's web address is probably companyname.com, but .companyname alone can't be a web address. Not true, and you can see it yourself: http://ac/ http://ai/ http://tm/ Nothing technically prevents a TLD from having an A record, it's just uncommon. So there could very well be http://microsoft/ or http://apple/ , which would appear as "microsoft" and "apple" in FF and Chrome, at least.
Are you sure about that? ac, ai and tm do not resolve: nslookup tm Non-existent domain Browsers are able to reach them by forwarding to ac.com, ai.com or tm.com
% dig a tm
; > DiG 9.7.3 > a tm.
;; global options: +cmd
;; Got answer:
;; ->>HEADER
And also an open http server: % nmap tm.
Starting Nmap 5.00 ( http://nmap.org ) at 2012-01-12 10:24 BRST
Interesting ports on serv213.icb.co.uk (193.223.78.213):
Not shown: 997 filtered ports
PORT STATE SERVICE
80/tcp open http
113/tcp closed auth
443/tcp open httpsRe: What's in a gTLD?
#9Right now you can guess that a company's web address is probably companyname.com, but .companyname alone can't be a web address. Not true, and you can see it yourself: http://ac/ http://ai/ http://tm/ Nothing technically prevents a TLD from having an A record, it's just uncommon. So there could very well be http://microsoft/ or http://apple/ , which would appear as "microsoft" and "apple" in FF and Chrome, at least.
Are you sure about that? ac, ai and tm do not resolve: nslookup tm Non-existent domain Browsers are able to reach them by forwarding to ac.com, ai.com or tm.com
And yes, browsers redirect to .com if you jut put "tm", but at least Firefox loads the correct website if you put the whole URL, with http://
Re: What's in a gTLD?
#10Right now you can guess that a company's web address is probably companyname.com, but .companyname alone can't be a web address. Not true, and you can see it yourself: http://ac/ http://ai/ http://tm/ Nothing technically prevents a TLD from having an A record, it's just uncommon. So there could very well be http://microsoft/ or http://apple/ , which would appear as "microsoft" and "apple" in FF and Chrome, at least.
I think you'll find that IANA (currently ICANN) refuses to put general purpose A, and AAAA records in the root. As far as I am aware only NS, "glue" A (and AAAA), and DNSSEC records are allowed in the root (aside from the records necessary for the root itself, i.e. SOA etc). You should also note that email addresses that doesn't have a '.' in the host part are technically invalid, i.e. me@mytld is not a valid fully q…
You should also note that email addresses that doesn't have a '.' in the host part are technically invalid, i.e. me@mytld is not a valid fully qualified email address.
Hmm, has RFC 2822 been superseded? Because it clearly says the domain part can be a dot-atom, which is defined in the same RFC in ABNF form as:
dot-atom = [CFWS] dot-atom-text [CFWS]
dot-atom-text = 1*atext *("." 1*atext)
As you can see, the dot (".") is enclosed in a section of variable repetition (*) with no minimum number of times, so it can not appear at all.