Another like restriction that might be investigated is whether
http://microsoft/ or other similar corporate TLDs would work as intended with
deployed legacy browsers.
I suspect (but have not tried) that if you simply type 'Microsoft' into the
address bar of some browsers you might have the keyword immediately interpreted
as a search term, not an address to visit.
I also suspect that if we actually read the technical specs being proposed we
might find that some of these issues have already been anticipated in them and
addressed.
________________________________
From: ietf-bounces(_at_)ietf(_dot_)org on behalf of Dave Crocker
Sent: Tue 7/1/2008 12:44 PM
To: Tony Finch
Cc: IETF Discussion
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Tony Finch wrote:
Speaking technically, how would you distinguish the top-level domain
"127.0.0.1" from the IP address 127.0.0.1?
A word while passing here: is there a document (RFC, Posix standard,
whatever) which says which is the right result in such a case?
RFC 1123 section 2.1, especially the last sentence.
Interesting.
I hadn't noticed the implication of that, before, but it seems to be a pretty
clear technical specification that a top-level domain is not allowed to be a
decimal number. Ever.
That's a concrete constraint on what ICANN is permitted to authorize.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf