<<<
Chronological Index
>>> <<<
Thread Index
>>>
[ga] More on localized tlds
- To: ga@xxxxxxxxxxxxxx
- Subject: [ga] More on localized tlds
- From: Danny Younger <dannyyounger@xxxxxxxxx>
- Date: Mon, 26 Dec 2005 14:17:41 -0800 (PST)
- Cc: stahura@xxxxxxxx
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=wYP/mVdMpjkOguadGtFA4XaN/QTRq6Q46o7LBR9nI/GHmck3IAZhCjEDZ1Z57WbC+mPvh/A2xlrVa8g++3kS4CzDKipInmEZGaPcY26QdQEnWf0Q27d0WpG6rzhNIg99yHFh2AtzQIxfXN2+WusqrU4VHOILO9j21oYwiBNruSI= ;
- Sender: owner-ga@xxxxxxxxxxxxxx
On the topic of localized TLDs, Paul Stahura wrote to
me with the following observation after reading my
post on area code tlds (reprinted with permission):
Danny,
numerical TLDs are not allowed (its in rfc 1035
http://www.ietf.org/rfc/rfc1035.txt?number=1035 )
because programs can confuse the resulting name with
IP addresses, for example 2.34.32.212
"2.3.1. Preferred name syntax
The DNS specifications attempt to be as general as
possible in the rules for constructing domain names.
....
They must start with a letter, end with a letter or
digit, and have as interior characters only letters,
digits, and hyphen."
__________________________________
Yahoo! for Good - Make a difference this year.
http://brand.yahoo.com/cybergivingweek2005/
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|