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

"Patrik Fältström " <paf@frobbit.se> Wed, 15 July 2015 06:58 UTC

Return-Path: <paf@frobbit.se>
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 B08881A8750; Tue, 14 Jul 2015 23:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.261
X-Spam-Level:
X-Spam-Status: No, score=-1.261 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, 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 uGpL_wLbh_HC; Tue, 14 Jul 2015 23:58:41 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A86F1A8748; Tue, 14 Jul 2015 23:58:41 -0700 (PDT)
Received: from [192.168.1.103] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 117D1205DE; Wed, 15 Jul 2015 08:58:39 +0200 (CEST)
From: Patrik Fältström <paf@frobbit.se>
To: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 15 Jul 2015 08:58:38 +0200
Message-ID: <2EB26DE7-6953-4FF0-BE2C-1E3DBE5AD13D@frobbit.se>
In-Reply-To: <CA+9kkMAz1ogcpWAdKaKTRm9f8sV4RO+TKu6aYB717D7+eM0bmw@mail.gmail.com>
References: <20150714192438.1138.96059.idtracker@ietfa.amsl.com> <CA+9kkMAz1ogcpWAdKaKTRm9f8sV4RO+TKu6aYB717D7+eM0bmw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_2DF9AC3D-A263-416B-B018-566BCF4354F2_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/E4Nn6XGUPMidyU-Zjq6HxpAJjTg>
Cc: dnsop@ietf.org, IETF <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Jul 2015 06:58:42 -0000

On 14 Jul 2015, at 22:16, Ted Hardie wrote:

> Further, I believe this stretches the "special handling" requirement of RFC 6761 to the breaking point.  This does not describe special handling _within the DNS_, but instead removes a portion of the global namespace from the DNS at all.  To me, at least, this does not seem to me to meet the analogy RFC 6761 provides to IP multicast ranges or local addresses.   Whether it is permitted or not by RFC 6761, it is a bad idea.

Speaking personally I think the intention of RFC6761 was to allow any kind of splitting of the namespace used by for example the global DNS so that there would not be any confusion and/or questions on how to resolve a specific string. See other similar specifications regarding .EXAMPLE, .LOCAL and such. And I think this is exactly the kind of need that exists for .ONION. The reference (normative or informative) is something I agree can be discussed whether it should not have been normative.

If the wording in RFC6761 is such that we do not agree that this is the process, but instead that RFC6761 is only for specifications that use the DNS for resolution, then I think RFC6761 should be made more clear, and not this document.

RFC6761 should be about namespace management, which I think is what we discuss here.

Because of this, I think this RFC should be published modulo resolution of the question about the reference.

> ​My opinion only,

Likewise ;-)

   Patrik