Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment

Andrew Sullivan <ajs@shinkuro.com> Fri, 18 February 2011 23:08 UTC

Return-Path: <ajs@shinkuro.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 374063A6DA8 for <dnsext@core3.amsl.com>; Fri, 18 Feb 2011 15:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level:
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, 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 3puxoNqwuVk7 for <dnsext@core3.amsl.com>; Fri, 18 Feb 2011 15:08:33 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 76AF83A6D3E for <dnsext@ietf.org>; Fri, 18 Feb 2011 15:08:33 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id AAC741ECB420 for <dnsext@ietf.org>; Fri, 18 Feb 2011 23:09:07 +0000 (UTC)
Date: Fri, 18 Feb 2011 18:09:06 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsext@ietf.org
Message-ID: <20110218230905.GN74065@shinkuro.com>
References: <20110216073338.7251.qmail@joyce.lan> <F21692535B1A478F95D9E3AA048E8037@ics.forth.gr> <20110216165921.GW96213@shinkuro.com> <3B90ED2E-980D-4B01-889F-447D66D0B58D@insensate.co.uk> <20110216174011.GZ96213@shinkuro.com> <20110218143653.GC84482@bikeshed.isc.org> <20110218151209.GF66684@shinkuro.com> <4D5EEE09.4080405@dougbarton.us> <20110218222950.GL74065@shinkuro.com> <4D5EF74C.9080603@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4D5EF74C.9080603@dougbarton.us>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 23:08:34 -0000

On Fri, Feb 18, 2011 at 02:48:44PM -0800, Doug Barton wrote:

> Sure, that's possible. But I think it's very, very unlikely. As I said  
> in my previous post registries today are giving registrants the option  
> of whether to delegate the variants, I don't see this changing if we  
> give them a new tool to use.

I've asked before, and I'll ask again now: what do you mean by
"registries"?  Remember that we are _not_ talking only about the top
level.

It is certainly true that the commercial environment today
concentrates most of the commercial relationships and delegations at
the top level, and it is also true that most delegations below the top
level are friendly and co-operative.

But I'm simply not willing to say, glibly, "The future will resemble
the past," in this area.  For instance, we are today in a commercial
environment where the scope for expansion of the top level is very
large, and there is little reason to believe that all of those new
operators are going to do exactly the same thing as everyone else
already has been doing.  We need to design this protocol change for
cases we can plausibly imagine, not just what we happen to have seen.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.