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

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 13 May 2015 18:05 UTC

Return-Path: <ajs@anvilwalrusden.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 66B231A8AE1 for <dnsop@ietfa.amsl.com>; Wed, 13 May 2015 11:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 rbULCCzWmcGI for <dnsop@ietfa.amsl.com>; Wed, 13 May 2015 11:05:52 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id D9E211A1B73 for <dnsop@ietf.org>; Wed, 13 May 2015 11:05:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 8BBED106B1; Wed, 13 May 2015 18:05:50 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vr5gqvaU5pML; Wed, 13 May 2015 18:05:49 +0000 (UTC)
Received: from [IPv6:2601:18d:8600:22:54b1:3e69:8363:afe2] (unknown [IPv6:2601:18d:8600:22:54b1:3e69:8363:afe2]) by mx2.yitter.info (Postfix) with ESMTPSA id 6AF9E10636; Wed, 13 May 2015 18:05:49 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <F8108959-3BAD-4198-BF97-39B4C54F917C@nominum.com>
Date: Wed, 13 May 2015 14:05:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8EEA3B35-64CB-4960-A58A-7D6B62E11CCF@anvilwalrusden.com>
References: <20150508193400.55273.qmail@ary.lan> <FF464258-0C33-45CC-A684-BAB7BCE8A8FB@gmail.com> <alpine.OSX.2.11.1505082118060.31363@ary.lan> <0902600F-134B-4688-9CDD-1ACB23431DDE@vpnc.org> <20150512010624.GC74841@mx2.yitter.info> <62970575-A605-4B3E-9E98-D760B47E8532@isoc.org> <CAHw9_i+jpobNKtim=Gw3ZAjaU6ff3A-SHVrGHqn0AW7-WOwsNQ@mail.gmail.com> <A789E52D-9682-42C7-AF04-A25C8C43450F@nominum.com> <CAHw9_iL8CkQ8VwaCXza+vsYh990MJWsdF0crAdq2qLbJdhG6-Q@mail.gmail.com> <DA7987D3-BA53-4D88-9B83-E272D728A70E@nominum.com> <20150512163603.GP75349@mx2.yitter.info> <F8108959-3BAD-4198-BF97-39B4C54F917C@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/6N3GW0dnuu-Rh5TKVWaEkd4BEdw>
Cc: "<dnsop@ietf.org>" <dnsop@ietf.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: Wed, 13 May 2015 18:05:53 -0000

I think you're missing a distinction I was making, however, which is that we should not be poaching on turf already handed to someone else.  Managing top-level domains that are intended to be looked up in the DNS -- even if people expect them to be part of a "local root" or otherwise not actually part of the DNS -- is, I increasingly think, part of ICANN's remit.  Managing things that are domain names that are by definition _never_ to be looked up in the DNS is different, and we have a legitimate claim (I'm arguing.  I should note I'm not sure I completely buy the distinction I'm making, but I want to keep testing it).  

The distinction I'm making suggests why corp and onion seem different.  They are, in this fundamental resolution nature.  

A

-- 
Andrew Sullivan 
Please excuse my clumbsy thums. 

> On May 12, 2015, at 19:16, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> 
>> On May 12, 2015, at 12:36 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
>> This is a bizarre argument.  You don't get to kind-of delegate policy
>> authority this way.  Authority was delegated, and if we don't like the
>> outcome we can go pound sand.
> 
> I think the IETF can develop a position on whether we think what ICANN is doing with the authority we delegated to them makes sense. You are right that we may not be able to do anything about this position other than state it, but we could state it, if we chose. But that wasn't the argument I was making.
> 
> The argument I was making is that it's pretty clear that what ICANN has done is bad for the Internet, and that we should not decide whether or not to allocate special use names, or how many to allocate, based on an attitude of deferring to ICANN's greater wisdom on the topic.
> 
> If in fact we have any basis for claiming to be able to allocate special use names, then we should just do that, not without taking care to avoid creating unnecessary conflicts, but not with trepidation either.   If we don't, then we should figure that out, and figure out what to do about it, because this whole conversation appears to be based on the premise that we can in fact allocate special use names.