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> Tue, 14 July 2015 20:53 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 6F4511B2CFA for <ietf@ietfa.amsl.com>; Tue, 14 Jul 2015 13:53:10 -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 G33l8PmJ8PPA for <ietf@ietfa.amsl.com>; Tue, 14 Jul 2015 13:53:08 -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 82C301B2CE2 for <ietf@ietf.org>; Tue, 14 Jul 2015 13:53:04 -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 63803DA006F; Tue, 14 Jul 2015 20:53:04 +0000 (UTC)
Received: from [10.19.125.164] (50.242.119.237) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 14 Jul 2015 13:53:04 -0700
Message-ID: <55A576AF.9080800@nominum.com>
Date: Tue, 14 Jul 2015 13:53:03 -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: Ted Hardie <ted.ietf@gmail.com>
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> <55A56C59.2090700@nominum.com> <CA+9kkMA__9t2NLRZ07ypxd3+vCFd3133N1c5a94U1=NhFskFRA@mail.gmail.com>
In-Reply-To: <CA+9kkMA__9t2NLRZ07ypxd3+vCFd3133N1c5a94U1=NhFskFRA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [50.242.119.237]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Fq6RjIdyE2W20DiaV2gOau1w2d8>
Cc: IETF <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: Tue, 14 Jul 2015 20:53:10 -0000

On 07/14/2015 01:28 PM, Ted Hardie wrote:
> ​Given that the point of IETF Last Call is to determine if there is 
> IETF consensus on the working group's analysis and proposal, I find 
> "inappropriate" an odd choice of words here.  The IETF as a whole may 
> have a different sense of the trade-offs here.​
It's certainly appropriate for people who aren't DNSOP participants to 
weigh in here, and for DNSOP participants to raise new issues that the 
working group missed.   But it seems bogus to me for DNSOP participants 
to raise the same issue here that they raised in DNSOP and that didn't 
get consensus.   I  believe you are a DNSOP participant, but perhaps I 
am mistaken.   I think you and at least one other person read my comment 
as saying that once the working group has consensus, that's the end of 
it, but that wasn't my point.   My point is simply that it would be 
useless and harmful to the IETF for DNSOP participants to waste the 
collective attention of the IETF re-arguing points that already got 
consensus in DNSOP. This is a perennial problem in the IETF.   Of 
course, now we will have a long argument about the appropriateness of my 
interjection here instead, but I'm not convinced that that's worse.

> ​I have a great deal of respect for the folks in DNSOP, and a similar 
> amount for those who created and TOR.  But I believe that this 
> approach to segmenting the namespace for protocol resolution does not 
> scale well.  I would far prefer a notation that onion addresses can 
> appear in the authority section of URIs without them being DNS names, 
> something that RFC 3986 allows with the registered name syntax.
I don't see how that helps: if they can appear in URIs, then we still 
need to mark that special-use TLD as in use.