Re: [v4v6interim] Single namespace

james woodyatt <jhw@apple.com> Wed, 01 October 2008 18:35 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 319413A69DF; Wed, 1 Oct 2008 11:35:07 -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 393773A69DF for <v4v6interim@core3.amsl.com>; Wed, 1 Oct 2008 11:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 lfjJtSz35xNU for <v4v6interim@core3.amsl.com>; Wed, 1 Oct 2008 11:35:05 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 78E563A67A7 for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:35:05 -0700 (PDT)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id 0015B3FAC5BA for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:34:30 -0700 (PDT)
Received: from relay13.apple.com (unknown [127.0.0.1]) by relay13.apple.com (Symantec Mail Security) with ESMTP id DB7792808C for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:34:30 -0700 (PDT)
X-AuditID: 1180711d-ac911bb000000ede-ce-48e3c2b6afcb
Received: from il0602f-dhcp175.apple.com (il0602f-dhcp175.apple.com [17.206.50.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay13.apple.com (Apple SCV relay) with ESMTP id B7B722807D for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:34:30 -0700 (PDT)
Message-Id: <090C6392-9082-4660-AE68-FA384B788C03@apple.com>
From: james woodyatt <jhw@apple.com>
To: v4v6interim@ietf.org
In-Reply-To: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 01 Oct 2008 11:34:30 -0700
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
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-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

On Oct 1, 2008, at 10:42, Fred Baker wrote:
>
> 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.

The reason I've been having a hard time following this discussion is  
that you're using the word "domain" where I've always seen the word  
"horizon" in order to distinguish the concept from the meaning of the  
word "domain" in Domain Name System.

> 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 "gross indecency" here is, apparently, admitting in public that we  
cannot escape the need to amend the DNS standards to recognize, for  
the first time, that we need more than one public horizon, i.e. the  
V4V6COEX public horizon and the IPv6 public horizon.

I do not see how we can escape that problem except by deprecating IPv4- 
only operation.  You want to talk to IPv6 nodes?  Then get yourself an  
IPv6 stack and a default route. Otherwise, have a coke and a smile,  
and shut the frell up.  I'm assuming that rough consensus is still  
leaning away from that, so can we please face up to the reality that  
multiple public DNS horizons are the way out of this?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim