Return to New TLD Agreements Forum - Message Thread - FAQ

Username: InternetAdvocate
Date/Time: Sat, April 21, 2001 at 9:59 PM GMT
Browser: Microsoft Internet Explorer V5.5 using Windows NT 4.0
Subject: Reform cc-TLD's.

Message:
 

 

Two letters are insufficient for future LOGICAL expansion of country codes.  (For example, it makes no sense for .gq to be Equatorial Guninea's CC-TLD which should be .gueq instead.)
       
All two-letter CC-TLD's should be changed to three or four letters.
Then .sm, .tm, .am, .fm, .tv should be opened for G-TLD use (service marks, trademarks, AM radio, FM radio, television).
       
For a transition period, all links to current CC-TLD's would be automatically forwarded to new CC-TLD's.

Just like with changes in telephone country code or area codes.

Great Britain just completed a huge revision in its telephone number system.  Several U.S. territories in the Pacific changed their country codes to 1 (the North American country code).  The Carribean islands changed their area codes (from 809).

A phase-in would reduce the expense and confusion of such change.  Both codes would be equally valid for a time period so that new paperwork and signs would state the new codes and old paperwork would not be obsoleted.

If all CC-TLD's were changed to more than two letters, then contacts could learn of such wholesale changes from their own ISP company.

After the phase-in period ends, then a standard error message would direct users to replace the old code with the new code (for example, replace ".co.uk" with ".com.brit").

Likewise, I think the North American area codes should be changed so that numerically sequential codes are geographically near each.  (For example, area codes 320 through 329 could be Los Angeles County, California.)  After all, that's how telephone country codes are.  European codes start with digits 30 through 49 as first two digits.  South American codes start with 50 through 59 as first two digits.

http://www.nanpa.com [for area codes]

 

Link: CC-TLD's


Message Thread:


Privacy Policy | Terms of Service | Cookies Policy