[v4v6interim] Single namespace

Fred Baker <fred@cisco.com> Wed, 01 October 2008 17:42 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 7D9663A6909; Wed, 1 Oct 2008 10:42:38 -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 54F3E3A6909 for <v4v6interim@core3.amsl.com>; Wed, 1 Oct 2008 10:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level:
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 WPBBgaqNCiiu for <v4v6interim@core3.amsl.com>; Wed, 1 Oct 2008 10:42:36 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 5ED873A67B3 for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 10:42:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="166765400"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 01 Oct 2008 17:42:14 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m91HgEo9023319; Wed, 1 Oct 2008 10:42:14 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91HgEnt001798; Wed, 1 Oct 2008 17:42:14 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 1 Oct 2008 10:42:14 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 1 Oct 2008 10:42:13 -0700
Message-Id: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Bill Manning <bmanning@karoshi.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 01 Oct 2008 13:42:11 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 17:42:13.0726 (UTC) FILETIME=[09E90FE0:01C923ED]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1335; t=1222882934; x=1223746934; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Single=20namespace |Sender:=20; bh=YBx2S3HvPWtrcPXZI6cneKf6wlH8OFc9FRPgV69hU3A=; b=tYp9wubyp20daBOnjAhpi6ec7Lyy8ly16s+a2VN+gTGeJ7RurhzG0vL+JL cWB9SIV3UK4lzaOGc6QhITRJ0fxX6I+w+F9t35Ftmdz/GMZ14qz8ELh7M4Sa SXXjO1psZW;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Cc: v4v6interim@ietf.org
Subject: [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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

picking up from the discussion in the chat room, and passing along a  
question that jabber wasn't able to deliver in the chat room.

Not sure we're disagreeing on whether there should be a single name  
space. The real question is what you say about a name when you're  
asked to translate it into a name.

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.

The difference in the domains in DNS64 is between an IPv4 (IPv4-only  
or IPv4+IPv6) domain and an IPv6-only domain and referencing a name  
that has an A record but not an AAAA record.

So now I will repeat my question. You said that you didn't care for  
DNS64. I'm asking what, specifically, you would prefer to use.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim