Re: [v4v6interim] Single namespace

Andrew Sullivan <ajs@commandprompt.com> Thu, 02 October 2008 13:22 UTC

Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AED833A6C14; Thu, 2 Oct 2008 06:22:59 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D8AF3A697D for <v4v6interim@core3.amsl.com>; Thu, 2 Oct 2008 06:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level:
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id laQ3ehHh65Wa for <v4v6interim@core3.amsl.com>; Thu, 2 Oct 2008 06:22:58 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by core3.amsl.com (Postfix) with ESMTP id 2EBE43A6887 for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 06:22:58 -0700 (PDT)
Received: from commandprompt.com (traingw.ericsson.ca [192.75.88.176]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m92DQbRF022175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 06:26:40 -0700
Date: Thu, 02 Oct 2008 09:22:52 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: v4v6interim@ietf.org
Message-ID: <20081002132252.GC38182@commandprompt.com>
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com> <090C6392-9082-4660-AE68-FA384B788C03@apple.com> <20081002045221.GA36568@commandprompt.com> <AC9D9C70-5E07-4909-871D-A17E3D7F456D@apnic.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <AC9D9C70-5E07-4909-871D-A17E3D7F456D@apnic.net>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 02 Oct 2008 06:26:41 -0700 (PDT)
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Thu, Oct 02, 2008 at 04:35:47PM +1000, Geoff Huston wrote:
> But we all knew this Andrew, didn't we? So I for one am not sure what point 
> you are making here that wasn't part and parcel of any of these hybrid 
> translation approaches. Am I missing something here in your post that 
> advances something that was not well understood already?

I don't think I'm advancing something that was not understood, but I
am arguing that it is not plain the benefits are worth the cost.  I am
pretty sure there are going to be DNS protocol enthusiasts who think
it's _not_ worth the cost.  Certainly we're going to have to have a
better argument than "We know we're introducing this breakage, so it's
ok."

I can imagine someone arguing, for instance, that if you're an
IPv4-only operator and you want people on v6 networks to be able to
use your services, put a AAAA record for a v4-compatible (or some new,
improved v4-compatible) address in the DNS.  If the response is, "But
v4-only operators might not do that, and v6 users will suffer," then
we're begging the question, because what we're debating is whether
altering DNS answers for some users is ok given the benefit thereby
achieved.  Such a person might also argue that supporting v4 users'
use of v6-only systems is just not a practical goal given the costs,
and if they want to use those services, that will give them an
excellent incentive to add IPv6 support; so for practical reasons, we
shouldn't try to solve that scenario.

Note that there's an important disanalogy between the current
proposals and the corporate network, split-brain case.  If I run a
split-brain DNS installation, I am taking the risk of leaks &c.  It's
my network, and if I want to do funky things inside it, that's
arguably my privilege.  But unless I'm missing something important,
most of the current proposals will change the DNS answers without the
operator of the source DNS answer needing to know anything about it.
The potential for increases in support costs and surprising results is
real, and that will cause people to object.

A

-- 
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim