IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Thu, 21 May 2015 17:48 UTC

Return-Path: <Ted.Lemon@nominum.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 64FEC1A0089 for <dnsop@ietfa.amsl.com>; Thu, 21 May 2015 10:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 x3Gi1CSmIesN for <dnsop@ietfa.amsl.com>; Thu, 21 May 2015 10:48:42 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88D8E1A000B for <dnsop@ietf.org>; Thu, 21 May 2015 10:48:42 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 7EC24DA00A8; Thu, 21 May 2015 17:48:42 +0000 (UTC)
Received: from [10.0.1.29] (8.20.190.66) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 21 May 2015 10:48:42 -0700
References: <555CC061.7040109@gmail.com> <5A8378EF-97B3-44AE-B6E7-4873D68B18F6@hopcount.ca> <CAHw9_i+xnC=fivaJrWs4DLLiHuy+VyOf_J7wxzfpdL3MYK153A@mail.gmail.com> <9FBE3C74-F7B8-4ADC-8917-6BCBBC36A303@uniregistry.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <9FBE3C74-F7B8-4ADC-8917-6BCBBC36A303@uniregistry.com>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Message-ID: <F8AE3317-BB44-44CD-9D5B-97AA50738174@nominum.com>
X-Mailer: iPad Mail (12F69)
From: Ted Lemon <Ted.Lemon@nominum.com>
Date: Thu, 21 May 2015 13:48:41 -0400
To: Francisco Obispo <fobispo@uniregistry.com>
X-Originating-IP: [8.20.190.66]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/RCXhB-oeGxSCuoHp_ZAdwFsEM-M>
Cc: dnsop <dnsop@ietf.org>
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, 21 May 2015 17:48:43 -0000

On May 21, 2015, at 1:35 PM, Francisco Obispo <fobispo@uniregistry.com> wrote:
> Is something that in reality won’t happen, and we will be back to square one. “foo.ALT” is going to be very popular and without a registry to control the namespace you’ll end up in a situation where more than one application will attempt to connect to the wrong server (names collision problem).

This is a really good point.   I think there does need to be a .ALT registry in order for .ALT to be able to address anything other than experimental uses.   And I think this would actually be a good thing.   Experimental uses could either come under .EXP (I will probably get flamed for that, but please don't take it too seriously) or .EXP.ALT.

Of course, if we had a registry for .ALT, I suppose there would be a land rush on it, but if we don't have one I think that will be even worse.

v2.23.0 | Report a Bug | By Email