Re: the names that aren't DNS names problem, was Last Call: <draft-ietf-dnsop-onion-tld-00.txt>

Andrew Sullivan <ajs@anvilwalrusden.com> Sun, 26 July 2015 07:29 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60B8B1ACE15 for <ietf@ietfa.amsl.com>; Sun, 26 Jul 2015 00:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zlb8gqOW4gXo for <ietf@ietfa.amsl.com>; Sun, 26 Jul 2015 00:29:42 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 094A91ACE0B for <ietf@ietf.org>; Sun, 26 Jul 2015 00:29:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id A049D10590 for <ietf@ietf.org>; Sun, 26 Jul 2015 07:29:41 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F22My1VbiR_e for <ietf@ietf.org>; Sun, 26 Jul 2015 07:29:40 +0000 (UTC)
Received: from mx2.yitter.info (unknown [193.86.243.7]) by mx2.yitter.info (Postfix) with ESMTPSA id 5FE1210012 for <ietf@ietf.org>; Sun, 26 Jul 2015 07:29:40 +0000 (UTC)
Date: Sun, 26 Jul 2015 09:29:37 +0200
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: the names that aren't DNS names problem, was Last Call: <draft-ietf-dnsop-onion-tld-00.txt>
Message-ID: <20150726072936.GB5857@mx2.yitter.info>
References: <20150725165829.76805.qmail@ary.lan> <413CD2A31E4AFF293091DD05@JcK-HP5.jck.com> <DM2PR0301MB065582F1A4F6854EF86D4C8AA8800@DM2PR0301MB0655.namprd03.prod.outlook.com> <A005522A947794D54E141DEC@JcK-HP5.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A005522A947794D54E141DEC@JcK-HP5.jck.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KhkjfDA9TM-oDXyIDJpV8kN1Px0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jul 2015 07:29:43 -0000

On Sat, Jul 25, 2015 at 04:12:01PM -0400, John C Klensin wrote:
> Christian, as I have told others, there was, between
> approximately when the DNS came into use and when ICANN decided
> to ignore it, a firm rule about such names.  The rule was that
> there would never been names (labels with delegation records) in
> the DNS root longer than four characters, so one was free to
> improvise with ".local", ".localhost", etc.  No special rules
> (or additional special rules) needed.

Given what I know of operations at the time (and bearing in mind that
I was not directly involved in TLD operations until the time ICANN was
changing the rule), I believe the above to have been true. But it
hasn't been true since 2001, and it seems to me that is long enough
for us to say that the policy clearly changed.

Anyway, it's not clear to me that this rule was ever actually written
down, so it's hard to see how firm it was.  RFC 1123 has some rules
about the top level, but thost rules do not include the 4-character
limit.  RFC 1123 _does_ note that the DNS ought to work in a network
not connected to the Internet, and talks about "local names", so it is
clear there was an expectation that there would be some.  RFC 1591
outlines the top-level domains, and it is silent on the 4-character
rule.  Anyway, it's quite clear that ICANN's new delegation decisions
circa 2001 rendered 1591 obsolete (though why ICANN never published
updates to 1591 is a mystery to me).  

Best regards,

A (speaking as ever as an individual)

-- 
Andrew Sullivan
ajs@anvilwalrusden.com