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

"John Levine" <johnl@taugh.com> Tue, 14 July 2015 21:37 UTC

Return-Path: <johnl@taugh.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 095CB1B2DCC for <ietf@ietfa.amsl.com>; Tue, 14 Jul 2015 14:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.862
X-Spam-Level:
X-Spam-Status: No, score=0.862 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 QVBEPLP2MXbW for <ietf@ietfa.amsl.com>; Tue, 14 Jul 2015 14:37:42 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D109B1B2DCE for <ietf@ietf.org>; Tue, 14 Jul 2015 14:37:41 -0700 (PDT)
Received: (qmail 52822 invoked from network); 14 Jul 2015 21:37:55 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 14 Jul 2015 21:37:55 -0000
Date: Tue, 14 Jul 2015 21:37:17 -0000
Message-ID: <20150714213717.25168.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard
In-Reply-To: <CA+9kkMAz1ogcpWAdKaKTRm9f8sV4RO+TKu6aYB717D7+eM0bmw@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HIrOEtgAs9ucSX-QJ7wOsvVobnI>
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 21:37:43 -0000

>​I believe that .onion is, essentially, a way for structuring protocol
>addresses so that they appear to be DNS names.  It does not conform to the
>delegation model of the DNS, and it requires special knowledge on the part
>of the handler to understand it. ...

Right, that's why it's a special use name.  As others have noted, one
reason to regisiter it as special use is to deter hijacking if the
names leak into the real DNS.  The other is for bureaucratic reasons
related to SSL CAs.  Those seem reasonably compelling to me.

We had a long discussion about the perverse incentives that this might
create for other people to invent other names.  Yes, they might, but
this is engineering rather than art, and we need to deal with things
as they are, not as we might prefer they should have been.

R's,
John