[DNSOP] Some proposals for draft-adpkja-dnsop-special-names-problem-02
"Paul Hoffman" <paul.hoffman@vpnc.org> Fri, 25 March 2016 01:10 UTC
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EED912D990 for <dnsop@ietfa.amsl.com>; Thu, 24 Mar 2016 18:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 TdxGbTphjkxO for <dnsop@ietfa.amsl.com>; Thu, 24 Mar 2016 18:10:00 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 89FC712D989 for <dnsop@ietf.org>; Thu, 24 Mar 2016 18:09:59 -0700 (PDT)
Received: from [10.32.60.140] (50-1-98-216.dsl.dynamic.fusionbroadband.com [50.1.98.216]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id u2P19wAh084119 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Thu, 24 Mar 2016 18:09:58 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-98-216.dsl.dynamic.fusionbroadband.com [50.1.98.216] claimed to be [10.32.60.140]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: dnsop WG <dnsop@ietf.org>
Date: Thu, 24 Mar 2016 18:09:56 -0700
Message-ID: <2C4FA5BF-9B6F-46C9-A5B2-43C7BF780576@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/2xyvqsadvqOaAdTOP_84FyUf_cU>
Subject: [DNSOP] Some proposals for draft-adpkja-dnsop-special-names-problem-02
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 25 Mar 2016 01:10:01 -0000
Greetings. The authors have done a great job of cleaning up the document since the -01, but there are still many open issues. It would be grand if we could use the mailing list to discuss this before the face-to-face meeting in under two weeks. Below are the issues I brought up on the -01 document that are still not addressed in the -02. Maybe these are not what the rest of the WG wants, but it would be good to find out. --Paul Hoffman ========== Differences in encoding Section 4 mentions that labels in .onion do not have the 63-octet limit that names in the DNS have. However, there are differences listed for names in .local. Labels in .local MUST be valid UTF-8 strings. Thus, even though labels in names (not hostnames) can contain any sequence of octets, labels in .local are more restricted. Proposal: mention this difference in Section 4. ========== Onion URI In section 4, it says: Application architects see using special name tags (a la .onion) as an easy way to get new features deployed. They consider the hurdles of deploying new URI schemes such as http:/onion/onion-name as too onerous and too slow to deploy for their needs. The example is malformed. Proposal: The example should be both http://onion/onion-name and onion:/onion-name. ========== Default action Near the end of Section 4, it says: In effect, it would associate TLDs with indications on how applications and resolvers should treat them. However, such an approach would leave open the question of not-yet-defined TLDs. No resolution mechanism could be associated with those. During the earlier discussion, many people pointed out that the default action is to assume that names are in the DNS unless they are in the registry. Proposal: Change the text to reflect the current default action: In effect, it would associate TLDs with indications on how applications and resolvers should treat them. However, such an approach would leave open the question of not-yet-defined TLDs. Systems would continue to assume that not-yet-defined TLDs are part of the DNS until they are listed in the registry. ========== The use of .alt There was a significant amount of interest in the WG's .alt proposal (draft-ietf-dnsop-alt-tld-03). However, that draft is never mentioned in the problem statement, and is only obliquely referred to once near the end of Section 4. During earlier discussions many people said that the .alt proposal solves many of the difficult problems listed in the problem statement. Proposal: Add greater discussion of the .alt proposal to Section 4 (architectural considerations), Section 5 (technical considerations, in this case about the lack of registry for .alt), and in a few places in Section 6.2.
- [DNSOP] Some proposals for draft-adpkja-dnsop-spe… Paul Hoffman
- Re: [DNSOP] Some proposals for draft-adpkja-dnsop… Stephane Bortzmeyer