Re: [Inip-discuss] Domain Names

Andrew Sullivan <ajs@anvilwalrusden.com> Sun, 10 January 2016 23:25 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: inip-discuss@ietfa.amsl.com
Delivered-To: inip-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8A541A1A91 for <inip-discuss@ietfa.amsl.com>; Sun, 10 Jan 2016 15:25:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] 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 378S2rVIqzYN for <inip-discuss@ietfa.amsl.com>; Sun, 10 Jan 2016 15:25:00 -0800 (PST)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 4259F1A1A8A for <inip-discuss@iab.org>; Sun, 10 Jan 2016 15:25:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id DD29910832 for <inip-discuss@iab.org>; Sun, 10 Jan 2016 23:24:59 +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 R2VAQmAG2U9n for <inip-discuss@iab.org>; Sun, 10 Jan 2016 23:24:59 +0000 (UTC)
Received: from mx2.yitter.info (c-73-142-157-135.hsd1.nh.comcast.net [73.142.157.135]) by mx2.yitter.info (Postfix) with ESMTPSA id E641E10823 for <inip-discuss@iab.org>; Sun, 10 Jan 2016 23:24:58 +0000 (UTC)
Date: Sun, 10 Jan 2016 18:24:57 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: inip-discuss@iab.org
Message-ID: <20160110232457.GH29518@mx2.yitter.info>
References: <D285CCDC.11B63%edward.lewis@icann.org> <A3306B3F-2C01-4236-8A5F-119C1669425B@isoc.org> <D2A15E6C.124B4%edward.lewis@icann.org> <7047EC59-873A-4A76-80EF-3F2899A9052A@interisle.net> <CAHw9_iL1f7pgaFHdqWJTpW5mxbfRYsquOO3J-5cVNLv103LSig@mail.gmail.com> <5692C267.9050907@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5692C267.9050907@acm.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/inip-discuss/YPbCN9AEr0bjdWmnB3UNkKjQKGY>
Subject: Re: [Inip-discuss] Domain Names
X-BeenThere: inip-discuss@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IAB Internet Names and Identifiers Discussion List <inip-discuss.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/inip-discuss>, <mailto:inip-discuss-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/inip-discuss/>
List-Post: <mailto:inip-discuss@iab.org>
List-Help: <mailto:inip-discuss-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/inip-discuss>, <mailto:inip-discuss-request@iab.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jan 2016 23:25:01 -0000

On Sun, Jan 10, 2016 at 03:43:19PM -0500, Avri Doria wrote:
> 
> Is this a definition specific to the IN class domain name space?

That's an excellent question.  Sitting parked on my wet-drive (the thing
in between my ears before it comes out my fingers) is an I-D entitled,
"DNS CLASS Considered Useless"

If you read carefully the way CLASS is described, it turns out to
assume that the name tree is parallel.  If that is true, then some
things follow:

    1.  All names must subsist in all classes.
    2.  No name with a cross-class type can result in different
    resolution across classes.

If those are both true, then classes simply don't work, because of
[CD]NAME.  And if you think about the way the DNS is defined, this is
not surprising.

DNS is defined as a name space subordinate to which is the type and
class.  If classes worked, then the namespace would need to be
subordinate to class: you'd look up a name under a class with a
specific type.  But that's not how it is defined.

If you look at the very earliest namedroppers archives, actually, it
seems that this was very much the concern some commenters on DNS were
asking, though they didn't put it quite this starkly.  I think that
may be because they didn't yet have the experience with DNS that we
now do.  But I think those earliest questions were right on, and I
think that the complete failure of classes to take off is a pretty
good indication they were right.

I swore I'd submit that I-D before the end of 2015, but it's not even
been typed out yet.  I am still keen to make it happen.  I think we
should close the CLASS registry and admit that it's the appendix of
the DNS.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com