Re: [DNSOP] Adoption and Working Group Last Call for draft-appelbaum-dnsop-onion-tld

"John Levine" <johnl@taugh.com> Thu, 04 June 2015 20:15 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B9671A90EC for <dnsop@ietfa.amsl.com>; Thu, 4 Jun 2015 13:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4oNrPY0Z-8QW for <dnsop@ietfa.amsl.com>; Thu, 4 Jun 2015 13:15:26 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D22A1A90F3 for <dnsop@ietf.org>; Thu, 4 Jun 2015 13:15:26 -0700 (PDT)
Received: (qmail 24954 invoked from network); 4 Jun 2015 20:15:33 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 4 Jun 2015 20:15:33 -0000
Date: Thu, 04 Jun 2015 20:15:03 -0000
Message-ID: <20150604201503.45504.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20150604200719.GO94969@mx2.yitter.info>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/BpTHSAqsbEyr_YqM_7UGHd0HJFQ>
Cc: ajs@anvilwalrusden.com
Subject: Re: [DNSOP] Adoption and Working Group Last Call for draft-appelbaum-dnsop-onion-tld
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2015 20:15:27 -0000

>I agree that if you had a registry that had no unique entry, there'd
>be no problem.  But if you have to be prepared for identifier
>collisions anyway, what use is the registry?

It tells you where to find out about foo.alt if you want to use that
particular un-DNS hack.  Other than that, not much.  

Given the experience with usenet alt.*, it appears that in the absence
of a daddy to declare a winner when names collide, name collision
problems go away because it is much easier to avoid them than to
argue.  People used to the ICANN environment may find this a
conceptual challenge, but that's their problem.

R's,
John