Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material

Ted Lemon <Ted.Lemon@nominum.com> Thu, 14 May 2015 14:19 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 9B0BF1B2AEC for <dnsop@ietfa.amsl.com>; Thu, 14 May 2015 07:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 De7ozEkVW3XZ for <dnsop@ietfa.amsl.com>; Thu, 14 May 2015 07:19:45 -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 8E7151B2AEB for <dnsop@ietf.org>; Thu, 14 May 2015 07:19:33 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (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 155F1DA0085; Thu, 14 May 2015 14:19:33 +0000 (UTC)
Received: from [10.0.1.29] (8.20.190.66) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 14 May 2015 07:19:32 -0700
References: <20150513205135.14395.qmail@ary.lan> <7AD02DF7-45A5-42CE-AAE2-50CCAE3B6A4F@virtualized.org> <0EC766DD-E56D-4E6F-80D7-8B26BC87A528@INTERISLE.NET> <5E25D193-A5A4-46FC-A724-A4125585CAD8@virtualized.org> <CAKr6gn2cC275w1O3vSMBc0k6ZDZvbofx47GqPXc4wXJwdwY_4w@mail.gmail.com> <7D84AC1B-2782-4CC1-81D8-279F45125FEC@nominum.com> <CAKr6gn0rbvWXfjrgwocFb73jVutNyRQfG8dSfo7o6Q04cYOvNw@mail.gmail.com>
In-Reply-To: <CAKr6gn0rbvWXfjrgwocFb73jVutNyRQfG8dSfo7o6Q04cYOvNw@mail.gmail.com>
MIME-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
Message-ID: <22BEFF07-F54F-4BC5-9396-44A1DB1BF480@nominum.com>
X-Mailer: iPad Mail (12F69)
From: Ted Lemon <Ted.Lemon@nominum.com>
Date: Thu, 14 May 2015 10:19:31 -0400
To: George Michaelson <ggm@algebras.org>
X-Originating-IP: [8.20.190.66]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/3HsXVwn1ImISECzy9OKjK1Q3aIk>
Cc: Lyman Chapin <lyman@interisle.net>, dnsop WG <dnsop@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material
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, 14 May 2015 14:19:46 -0000

George, I didn't get into your game theory because I think it's irrelevant.  The IETF process is not a fast process. If parasitical organizations decide to try to get the calories they need from us rather than from ICANN, I am pretty sure they will quickly learn that this is futile. It might briefly suck for us while they learn that it won't work, but I don't think so.   We already know how to deal with useless proposals.

So with that in mind, I think we really are free to do the technically right thing without concern that it will encourage badness in the future.

As to the topic of fairness, that is inherently political, and we should steer well clear of it. There is no way we can reach consensus on it, and whether you want to admit it or not, by advancing the argument you are advancing, that is what you are asking us to do.

What you are saying is a really good argument against us reserving names simply because they have been squatted on.  I agree we should not use that as a reason to reserve a special use name.  ICANN already has a process for that    If we want to reserve a special use name, we should have a technical argument in favor of doing so.

But in the case of .onion, .corp and .home, we _do_ have such a reason. So there is no need to resort to the argument that these names should be documented in the special use registry because they were squatted on.

If .onion were being proposed today, and had no previous implementation, its proponents would rightly be arguing for .onion, not for .onion.alt, because how names read _matters_, and it makes sense for .onion to be a special use TLD, as it does for .corp and .home.

DNS has had a long run as the only name database that is taken seriously on the Internet, and so we no longer think of names as being something that has an existence independent of the DNS hierarchy, but that is not an inherent truth of domain names. It is just the status quo. I would not want to have to use a different name hierarchy designator in order to use mDNS, and that being the case, I don't think you can make the argument that .onion is qualitatively different from .local.