Re: [v4v6interim] Single namespace

Andrew Sullivan <ajs@commandprompt.com> Wed, 01 October 2008 17:58 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 C21413A6856; Wed, 1 Oct 2008 10:58:00 -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 7203F3A6856 for <v4v6interim@core3.amsl.com>; Wed, 1 Oct 2008 10:57: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 omUadDStfCUc for <v4v6interim@core3.amsl.com>; Wed, 1 Oct 2008 10:57:58 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by core3.amsl.com (Postfix) with ESMTP id 5FEC43A6405 for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 10:57: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 m91I1A11002570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:01:13 -0700
Date: Wed, 01 Oct 2008 13:57:26 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: v4v6interim@ietf.org
Message-ID: <20081001175725.GI33079@commandprompt.com>
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
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]); Wed, 01 Oct 2008 11:01:13 -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 Wed, Oct 01, 2008 at 01:42:11PM -0400, Fred Baker wrote:

> Let's imagine that the name oatwillie.example.com has two A records, 
> pointing respectively to 1.2.3.4 and 192.168.0.1. The question is not 
> whether the name is different in different namespaces; the question is 
> whether the translation is different in different domains.
>
> The way we usually implement this kind of thing is to have multiple name 
> servers, one of which is accessible from outside and the other is 
> accessible from inside. That gives us one name space, but different 
> responses to that translation request depending on the source of the 
> request. DNS64 does largely the same thing, but commits the gross and 
> indecent act of saying out loud that it does so.

I think that in the scenario with one RFC1918 address and one public
address, one of the answers comes with a local context and the other
comes with a global context.  The local context is determinable by the
querying host on the basis of the host's own IP address, because you
know that if you have an RFC1918 address, you're in a local-only
context.  In the case of DNS64, however, the whole point is that the
host doesn't need to know that it's living in a special place.  So
there's nothing about the state of the host that tells you what the
context is.  Instead, you need to know what the state of its relation
to other hosts on the Internet is in order to know what the "right"
context is.  Something about that makes me uneasy, but I can't yet put
my finger on what.

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