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

Ted Lemon <ted.lemon@nominum.com> Wed, 15 July 2015 18:12 UTC

Return-Path: <Ted.Lemon@nominum.com>
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 4948B1B3355; Wed, 15 Jul 2015 11:12:19 -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 lvtp1oT-CmKu; Wed, 15 Jul 2015 11:12:18 -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 5BF081B3353; Wed, 15 Jul 2015 11:12:18 -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 2E649DA0077; Wed, 15 Jul 2015 18:12:18 +0000 (UTC)
Received: from [64.89.225.79] (64.89.225.79) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 15 Jul 2015 11:12:18 -0700
Message-ID: <55A6A281.5040706@nominum.com>
Date: Wed, 15 Jul 2015 11:12:17 -0700
From: Ted Lemon <ted.lemon@nominum.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Edward Lewis <edward.lewis@icann.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard
References: <20150714192438.1138.96059.idtracker@ietfa.amsl.com> <D1CBC489.D039%edward.lewis@icann.org> <55A69556.9020207@nominum.com> <D1CC11CA.D086%edward.lewis@icann.org>
In-Reply-To: <D1CC11CA.D086%edward.lewis@icann.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [64.89.225.79]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ISbr0gIGmax_lzGKp0AKeUk93fo>
Cc: "dnsop@ietf.org" <dnsop@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: Wed, 15 Jul 2015 18:12:19 -0000

On 07/15/2015 11:04 AM, Edward Lewis wrote:
> That "Ted".
Yup, Ted pointed that out to me privately--sorry.   :)
> Keep in mind - I'm saying the document, the internet-draft, doesn't
> contain all that it could or should to be a convincing use case.  Perhaps
> it ticked off all the check boxes of RFC 6761, but I think it lacks what
> it needs to be convincing as well as stand the test of time.
Argh.   I won't belabor the point, but the criteria established in 6761 
are criteria for the IETF to evaluate, not criteria that need to be 
documented in the specification.   The specification says what to do, 
and the working group considered that sufficient.   I do too.   Can you 
explain why it is beneficial for the document to try to make some 
statement about how widespread use of TOR is?   It's pretty easy for the 
working group to look at the situation and say "looks like enough."   
It's a lot harder to quantify it in a way that makes sense to put in an 
RFC, and I don't think it would be appropriate to do so.   I guess we 
could say "it is the consensus of the DNSOP working group that use of 
.onion is sufficiently widespread to justify publishing this document," 
but I think we are already saying that by requesting its publication.