Eric, Richard and all, Given recent events, I find it difficult to see how any RFC is relevant to making determinations as to what is a "Valid" TLD and what is not with respect to Confusion. RFC 1035 I believe is the RFC you were searching for Eric. At any rate, in that the ICANN BoD has "RULED" on trailing "-" (Dashes) as not being valid, where there is no known restriction in any RFC presently, and that a private company has purchased the rights to .CC (Dot CC) it is difficult to justify that two letter TLD's as ONLY Country Code TLD's or ccTLD's. A TLD is a TLD, IMHO at this juncture, given the known facts and events. First ICANN says it will follow the standards of the RFC's, than it turns around and does a 180% and doesn't do that. Go figure. Either ICANN follows the RFC standards or it doesn't. Can't have it both ways, boys and girls! Now if you wan to change those RFC standards, that is fine and dandy. But it stands to reason that until those RFC standards are changed, and proper announcement is made publicly, inane rulings such as the Trailing Dash ruling/edict, should NEVER occur. More evidence of the stinking refuse heap of cluelessness from the ICANN baud. Sheeesh! Richard J. Sexton (At work) wrote: > Path: ns3.vrx.net!news2.best.com!newshub.northeast.verio.net!verio!news.maxwell.syr.edu!newsfeed.online.be!tank.news.pipex.net!pipex!server1.netnews.ja.net!newsfeed.ed.ac.uk!wormhole.ucs.ed.ac.uk!user > From: [EMAIL PROTECTED] (Sam Wilson) > Newsgroups: comp.protocols.tcp-ip.domains > Subject: Re: Naming > Date: Fri, 04 Feb 2000 10:13:38 +0000 > Organization: Network_Services_Division > Lines: 23 > Distribution: inet > Message-ID: <[EMAIL PROTECTED]> > References: <879135$8mi$[EMAIL PROTECTED]> <879k9r$d4r$[EMAIL PROTECTED]> <87c8dv$p5o$[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <87cndq$3oj$[EMAIL PROTECTED]> <[EMAIL PROTECTED]> > NNTP-Posting-Host: wormhole.ucs.ed.ac.uk > X-Trace: scotsman.ed.ac.uk 949659218 11994 129.215.200.202 (4 Feb 2000 10:13:38 GMT) > X-Complaints-To: [EMAIL PROTECTED] > NNTP-Posting-Date: 4 Feb 2000 10:13:38 GMT > Xref: ns3.vrx.net comp.protocols.tcp-ip.domains:10394 > > In article <[EMAIL PROTECTED]>, "Eric A. Hall" <[EMAIL PROTECTED]> > wrote: > > >All two-letter TLDs are reserved by IANA for use with ccTLDs, although > >there aren't any entries for AA or ZZ in the root file. I can't find the > >specific RFC right now, but I read it in one of the DNS-related RFCs. > > Are you thinking of this from RFC 1032? > > Countries that wish to be registered as top-level domains are > required to name themselves after the two-letter country code listed > in the international standard ISO-3166. In some cases, however, the > two-letter ISO country code is identical to a state code used by the > U.S. Postal Service. Requests made by countries to use the three- > letter form of country code specified in the ISO-3166 standard will > be considered in such cases so as to prevent possible conflicts and > confusion. > > -- > Sam Wilson > Network Services Division, Computing Services > The University of Edinburgh > Edinburgh, Scotland, UK Regards, -- Jeffrey A. Williams Spokesman INEGroup (Over 95k members strong!) CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail [EMAIL PROTECTED] Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
