Re: [mif] bare names (was: [dnsext] 2nd Last Call for MIF DNS server selection document)

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 19 October 2011 14:27 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE2AB21F8BA7 for <mif@ietfa.amsl.com>; Wed, 19 Oct 2011 07:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.405
X-Spam-Level:
X-Spam-Status: No, score=-2.405 tagged_above=-999 required=5 tests=[AWL=0.194, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KvGsxTfkBELT for <mif@ietfa.amsl.com>; Wed, 19 Oct 2011 07:27:19 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 35FB521F8B84 for <mif@ietf.org>; Wed, 19 Oct 2011 07:27:19 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id D3FE71ECB428; Wed, 19 Oct 2011 14:26:18 +0000 (UTC)
Date: Wed, 19 Oct 2011 10:26:27 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: mif@ietf.org
Message-ID: <20111019142626.GC18523@shinkuro.com>
References: <COL118-W55403198A984BAAE44BA47B1F70@phx.gbl> <916CE6CF87173740BC8A2CE44309696203782D75@008-AM1MPN1-037.mgdnok.nokia.com> <121DABD1-65E8-4275-8471-9FA38D25C434@nominet.org.uk> <8EFC868A-8796-4013-BB07-F3D33F33C552@network-heretics.com> <20111019132633.GB18523@shinkuro.com> <79350865-2ED5-4B12-BA36-B53550CB01F7@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <79350865-2ED5-4B12-BA36-B53550CB01F7@network-heretics.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Keith Moore <moore@network-heretics.com>
Subject: Re: [mif] bare names (was: [dnsext] 2nd Last Call for MIF DNS server selection document)
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2011 14:27:19 -0000

On Wed, Oct 19, 2011 at 09:48:23AM -0400, Keith Moore wrote:

>  I agree that search paths are somewhat broken.  What's not broken
> is the idea of using single-label names as local names.

[. . .]

> 
> split-brain DNS is an abomination that should be eradicated from the planet.

By "local names", do you just mean "globally-accessible names that are
of special interest to me?"  (If not, then unless you are arguing that
everyone ought to be configuring /etc/hosts themselves, I don't see
how the above two claims are consistent.  The way you get single-label
names as local names (at least as deployed) is to use the seach path
mechanism and look things up in the "local" DNS.  By definition, that
means that split-brain DNS is in action: the DNS namespace is not, in
that case, global.)

In any case, we do not have the option of eradicating split-brain DNS
any more than we can un-know how to split atoms and make bombs.  Once
such an innovation exits, we have to figure out how to cope with it to
the extent it can be coped with.  I too think that split-brain DNS is
a mistake, and I think most of the things people are doing with it are
foolish and stupid, but they are doing it.  We can either make the
network work as well as it can in the presence of such systems, or
live with the inventions that such innovators come up with in an
attempt to bandage the foot they just shot. 

> and sometimes, single-label names are set up to work correctly on
> multiple networks - the salient point being that the meaning of the
> name might be inherently context-sensitive.

Right, but not by virtue of it being single-label.  You can look up
single labels in the DNS just fine.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com