Re: [mif] Last Call for MIF DNS server selection document

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 09 September 2011 01:30 UTC

Return-Path: <brian.e.carpenter@gmail.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 5E8A521F8B46 for <mif@ietfa.amsl.com>; Thu, 8 Sep 2011 18:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.584
X-Spam-Level:
X-Spam-Status: No, score=-103.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ejAU9vX7YCSo for <mif@ietfa.amsl.com>; Thu, 8 Sep 2011 18:30:12 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9B71D21F8B3F for <mif@ietf.org>; Thu, 8 Sep 2011 18:30:12 -0700 (PDT)
Received: by fxe6 with SMTP id 6so2241562fxe.31 for <mif@ietf.org>; Thu, 08 Sep 2011 18:32:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DyYDABg8CXDqbcE6EM5CxzjIt0NGq8CVsVRsxdvnkqY=; b=qJnWwRALeuJiQKMp4Q78u2usDSLzQZhmiNFOFdfG75uYpZIWlJe6OD2eNjcLYUMfwH vYfOyf9CXFYVG6O3Z2nE3bUHYMaUi0TAGa+1arsUJZR6YcfOkPjqrmIN0Yqgy98wB+nD /UpO127h9xJNALJWawzj+kFEH6epKUxp6RJo0=
Received: by 10.223.15.145 with SMTP id k17mr1275689faa.132.1315531924440; Thu, 08 Sep 2011 18:32:04 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id f1sm2175534fah.9.2011.09.08.18.32.01 (version=SSLv3 cipher=OTHER); Thu, 08 Sep 2011 18:32:03 -0700 (PDT)
Message-ID: <4E696C8B.9010401@gmail.com>
Date: Fri, 09 Sep 2011 13:31:55 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
References: <COL118-W599D9E8760C3E370077FC3B1140@phx.gbl> <4E683F9B.7020905@gmail.com> <916CE6CF87173740BC8A2CE4430969620256F33F@008-AM1MPN1-032.mgdnok.nokia.com> <4E692D62.5080902@gmail.com> <BFFE3312-4DE3-432D-8DC7-20987AB3E34A@network-heretics.com> <20110909001101.GS38973@shinkuro.com>
In-Reply-To: <20110909001101.GS38973@shinkuro.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: mif@ietf.org
Subject: Re: [mif] 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: Fri, 09 Sep 2011 01:30:13 -0000

On 2011-09-09 12:11, Andrew Sullivan wrote:
> On Thu, Sep 08, 2011 at 06:22:17PM -0400, Keith Moore wrote:
>> I'm quite surprised that MIF was able to get this far with the document without the issue being raised.
> 
> Have I really been so polite that this qualifies as "not raised"?  I
> apologise to everyone, then.  But I've been uneasy about this since
> early in my work on the DNS64 drafts.  I'm getting perhaps too adept
> at nose-holding.

DNS64 doesn't damage the logical structure of the namespace itself.
As soon as you admit that not all DNS servers serve the exact same
namespace, and that a host may be able to see more than one
DNS server, the total namespace cannot be guaranteed unique.
There could be two totally unrelated entries for host.example.com.
Introducing ambiguity in the DNS namespace, having already
done so in the IPv4 address space, is a very serious step indeed.

If you want a citation, see clause 4.2 in RFC 1958.

This could be fixed by a BCP describing appropriate constraints
on names that only resolve within a limited scope, I think,
but it should not be just a by-product of the draft under review.

   Brian