Re: A letter hierarchy based scheme for arbitrary TLDs
"Donald E. Eastlake 3rd" <dee3@torque.pothole.com> Thu, 31 May 2001 14:08 UTC
Received: from nic.cafax.se ([192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25725 for <dnsop-archive@odin.ietf.org>; Thu, 31 May 2001 10:08:50 -0400 (EDT)
Received: by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) id f4VDhVwj001317 for dnsop-outgoing; Thu, 31 May 2001 15:43:31 +0200 (MEST)
Received: from torque.pothole.com ([38.138.52.132]) by nic.cafax.se (8.12.0.Beta7/8.12.0.Beta5) with ESMTP id f4VDhSLt001312 for <dnsop@cafax.se>; Thu, 31 May 2001 15:43:29 +0200 (MEST)
Received: from localhost by torque.pothole.com (8.9.3/1.1.29.3/11Jan01-1206AM) id JAA0000031804; Thu, 31 May 2001 09:42:46 -0400 (EDT)
Message-Id: <200105311342.JAA0000031804@torque.pothole.com>
To: Anssi Porttikivi <anssi.porttikivi@teleware.fi>
cc: dnsop@cafax.se
Subject: Re: A letter hierarchy based scheme for arbitrary TLDs
In-reply-to: Your message of "Thu, 31 May 2001 14:02:17 +0300." <20E5886B5437D511A2AC005004992A7103573E@twnt0.teleware.fi>
Date: Thu, 31 May 2001 09:42:46 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
Sender: owner-dnsop@cafax.se
Precedence: bulk
Hi, The message below is outside the charter of this working group. It is a message entirely within the realm of ICANN/DNSO/USDOC/... NOT the IETF. Please do not post any further on this topic to this list. Thanks, Donald From: Anssi Porttikivi <anssi.porttikivi@teleware.fi> Message-ID: <20E5886B5437D511A2AC005004992A7103573E@twnt0.teleware.fi> To: dnsop@cafax.se Date: Thu, 31 May 2001 14:02:17 +0300 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-dnsop@cafax.se Precedence: bulk >How about this: > >Let's SET UP NEW TOP LEVEL DOMAINS FOR ALL SINGLE LETTERS a., b.,...z. So >the top domains will be the classical ones + these new one letter TLDs. > >Now I want to have a name "anssi.abc." for my machine. I rewrite it (first >in my head) to be "anssi.a.b.c." > >I go to the "c." TLD server administration. I ask them, if anyone has >registered a "b.c." first level name with them. If such domain exists, I go >to its administrator, and ask, if they have a domain "a.b.c." already. And >so on, up to the letter, that is not yet served by anyone. If the domain >"a.b.c." already does exist, I can't register a new one. First come first >served. > >In this case, let's say the domain "b.c." did exist, but the domain "a.b.c." >did not. Now I register my "a.b.c." with the domain "b.c." administration. >There should be a rule, that single letter domains allow registration for >any unregistered single letter subdomains! > >So now I can set up names like "anssi.a.b.c." in my own name server, serving >the domain "a.b.c.", registered at "b.c.". > >NOW I MODIFY MY RESOLVER and ask everybody to do the same, if they please! >The new versions of resolvers are standardized to TRANSLATE ALL UNRECOGNISED >many-letter TLDs into a sequence of one letter domains. So "anssi.abc." will >be resolved as "anssi.a.b.c." domain. > >Additionally, domains "c.o.m.", "o.r.g." etc. and corresponding country >domains like "f.i." and "u.k." can be set up as peered, synonymous domains >for "com.", "org.", "fi., "uk." and such. So that the new resolvers would >not even have to know any list of special "recognizable" classic TLD >domains. > >Now anybody is free to set up whatever TLDs they want to!!! > >Old resolvers will work with the old TLDs. > >Old resolvers will kind of work with the new names, but only if you >translate manually, using "anssi.a.b.c" instead of "anssi.abc". > >New resolvers will work with all names, old and new, whether written as >"anssi.a.b.c." or "anssi.abc." > >Anssi.Porttikivi@teleware.fi >Data communications trainer/consultant >Teleware, Helsinki
- Re: A letter hierarchy based scheme for arbitrary… Donald E. Eastlake 3rd