Re: [mif] [DNSOP] [dnsext] 2nd Last Call for MIF DNS server selection document

Alex Bligh <alex@alex.org.uk> Mon, 24 October 2011 11:19 UTC

Return-Path: <alex@alex.org.uk>
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 4D65C21F8CFB; Mon, 24 Oct 2011 04:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 92+JBbx-W4Dz; Mon, 24 Oct 2011 04:19:25 -0700 (PDT)
Received: from mail.avalus.com (mail.avalus.com [IPv6:2001:41c8:10:1dd::10]) by ietfa.amsl.com (Postfix) with ESMTP id AE59D21F8CFA; Mon, 24 Oct 2011 04:19:25 -0700 (PDT)
Received: from [192.168.100.15] (87-194-71-186.bethere.co.uk [87.194.71.186]) by mail.avalus.com (Postfix) with ESMTPSA id B71E6C56100; Mon, 24 Oct 2011 12:19:21 +0100 (BST)
Date: Mon, 24 Oct 2011 12:19:21 +0100
From: Alex Bligh <alex@alex.org.uk>
To: Keith Moore <moore@network-heretics.com>, sthaug@nethelp.no
Message-ID: <E68B291B136EE9E8CFBF68F0@Ximines.local>
In-Reply-To: <59274CC1-611A-445B-A1CF-A0F49329DC1F@network-heretics.com>
References: <F2045A70-6314-41CF-AC3C-01F1F1ECF84C@network-heretics.com> <96472FB7-8425-4928-8F55-2ABF2CB59A93@conundrum.com> <628C128E-BDA8-46C3-BF07-364A482FE199@network-heretics.com> <20111024.080822.74700976.sthaug@nethelp.no> <59274CC1-611A-445B-A1CF-A0F49329DC1F@network-heretics.com>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Mon, 24 Oct 2011 04:49:17 -0700
Cc: mif@ietf.org, matt@conundrum.com, dnsop@ietf.org, dnsext@ietf.org, pk@isoc.de, Alex Bligh <alex@alex.org.uk>, dhcwg@ietf.org, denghui02@hotmail.com
Subject: Re: [mif] [DNSOP] [dnsext] 2nd Last Call for MIF DNS server selection document
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Alex Bligh <alex@alex.org.uk>
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: Mon, 24 Oct 2011 11:19:26 -0000

--On 24 October 2011 06:53:05 -0400 Keith Moore 
<moore@network-heretics.com> wrote:

> I'm just pointing out that for the vast majority of the contexts in which
> domain names are used, the expectation is that a domain name that
> contains a "." is fully-qualified.

This is sampling bias.

In the vast majority of contexts where domain names (term used
loosely) are used, those domain names contain at least one dot.

In the vast majority of contexts where domain names (term used
loosely) are used, those domain names are fully qualified.

It is therefore statistically unsurprising that in the vast
majority of contexts where domain with a dot in them, are used
they are fully qualified.

The question here should be "where search lists are used, are
they frequently used in combination with domain names that
are not fully qualified". I would suggest the answer to this
question is "yes". If so, then to the extent that search lists
are supported, you need to make them interwork names with
dots in them. Moreover, with a search list of "example.com",
having "mail" work, but not "mail.dev" is going to be a
pretty surprising outcome.

I think the two options are either deprecating search lists
(or not supporting them), or supporting them properly, in
which case they must be used whatever domain name is
specified, and the way to avoid using a search list
is the same old hack as before (i.e. putting a dot on the
end).

-- 
Alex Bligh