Re: [DNSOP] Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard

David Cake <dave@difference.com.au> Mon, 20 July 2015 03:02 UTC

Return-Path: <dave@difference.com.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB0D91B2F0E; Sun, 19 Jul 2015 20:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.087
X-Spam-Level: **
X-Spam-Status: No, score=2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MANGLED_TOOL=2.3, RELAY_IS_203=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UvK5DWmEW4y5; Sun, 19 Jul 2015 20:02:53 -0700 (PDT)
Received: from legba.difference.com.au (legba.difference.com.au [203.56.168.25]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8401B2F0D; Sun, 19 Jul 2015 20:02:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by legba.difference.com.au (Postfix-vscanned) with ESMTP id 20020A2216; Sun, 19 Jul 2015 18:06:50 +0800 (AWST)
Received: from legba.difference.com.au ([127.0.0.1]) by localhost (legba.difference.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F35FPZHhDuRt; Sun, 19 Jul 2015 18:06:48 +0800 (AWST)
Received: from [192.168.1.4] (58-7-57-40.dyn.iinet.net.au [58.7.57.40]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by legba.difference.com.au (Postfix-smtp) with ESMTPSA id B5E8FA20A2; Sun, 19 Jul 2015 18:06:47 +0800 (AWST)
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Content-Type: multipart/signed; boundary="Apple-Mail=_4D3EE88B-B3D1-4FA2-B9CB-A899C02A0E41"; protocol="application/pgp-signature"; micalg="pgp-sha256"
X-Pgp-Agent: GPGMail 2.5
From: David Cake <dave@difference.com.au>
In-Reply-To: <55A6BA55.3020403@nominum.com>
Date: Mon, 20 Jul 2015 11:02:41 +0800
Message-Id: <49A193AB-BA82-412E-B86A-E62823B3408F@difference.com.au>
References: <20150714192438.1138.96059.idtracker@ietfa.amsl.com> <D1CBC489.D039%edward.lewis@icann.org> <55A69556.9020207@nominum.com> <D1CC11CA.D086%edward.lewis@icann.org> <55A6A281.5040706@nominum.com> <D1CC1E37.D097%edward.lewis@icann.org> <55A6BA55.3020403@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/LRq4D6RpIpz1vEP9-BQQq9eLXi4>
X-Mailman-Approved-At: Sun, 19 Jul 2015 22:50:41 -0700
Cc: Edward Lewis <edward.lewis@icann.org>, "dnsop@ietf.org" <dnsop@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jul 2015 03:02:54 -0000

There are plausible, if unlikely, circumstances in which a fork, not just of the Tor project software itself, but of the entire project including the specific URL, might happen. While this argument is an attempt at a reductio ab absurdum, I do not think it is - the circumstance described is unlikely, but not absurd. In other words, I agree with Ted.
And as a much more active contributor to ICANN processes than IETF ones, I think Ted is right in characterisation of the appropriate interaction here.

	David

> On 16 Jul 2015, at 3:53 am, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> 
> On 07/15/2015 11:46 AM, Edward Lewis wrote:
>> What if I copied the onion draft, changed all of the uses of onion to
>> carrot, and then threw in some supporting documents to describe some other
>> system that used carrot as it's base identifier?  On the heels of onion's
>> admission to the Special Use Domain Names registry, could I expect to have
>> carrot admitted too?
> 1. Do you seriously think DNSOP would have had consensus to advance such a draft?
> 2. If DNSOP did have consensus to advance such a draft, what would your objection be?
> 
> I think that DNSOP would not advance such a draft unless a lot of reasonable people decided that they believed that .carrot was needed.   And if DNSOP did indeed advance such a draft, I think that it would be the right thing to do to go to ICANN and say "what do you guys think about this?"   I don't think we would be in a position to make demands, but we should be able to have the conversation.
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop