[DNSOP] DNAMEs in the root zone? [was: Re: draft-grothoff-iesg-special-use-p2p-names-00.txt]

Chris Thompson <cet1@cam.ac.uk> Mon, 09 December 2013 14:41 UTC

Return-Path: <cet1@hermes.cam.ac.uk>
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 76CC71AE2E2 for <dnsop@ietfa.amsl.com>; Mon, 9 Dec 2013 06:41:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level:
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.001] 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 BXV9JOCz7w7D for <dnsop@ietfa.amsl.com>; Mon, 9 Dec 2013 06:41:11 -0800 (PST)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id 03DE41ADF8B for <dnsop@ietf.org>; Mon, 9 Dec 2013 06:41:10 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:45687) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:cet1) id 1Vq21A-0005f5-9G (Exim 4.82_3-c0e5623) (return-path <cet1@hermes.cam.ac.uk>); Mon, 09 Dec 2013 14:41:04 +0000
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:cet1) id 1Vq21A-0000Am-Pu (Exim 4.72) (return-path <cet1@hermes.cam.ac.uk>); Mon, 09 Dec 2013 14:41:04 +0000
Received: from [131.111.56.28] by old-webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 09 Dec 2013 14:41:04 +0000
Date: 09 Dec 2013 14:41:04 +0000
From: Chris Thompson <cet1@cam.ac.uk>
To: Joe Abley <jabley@hopcount.ca>
Message-ID: <Prayer.1.3.5.1312091441040.15674@hermes-2.csi.cam.ac.uk>
In-Reply-To: <0AE0E07B-2509-440D-81CF-4A75A7F95F45@hopcount.ca>
References: <BF87877A-8989-4AA4-9ED1-52C82E1BC538@nominum.com> <alpine.LFD.2.10.1312011206480.12923@bofh.nohats.ca> <20131202151651.GD16808@mx1.yitter.info> <A12FD3E0-58F6-4490-877F-A9C59405F717@vpnc.org> <6DBBC8339C394DBDAE4FE1F764E02A8D@hopcount.ca> <20131203170825.GA17211@nic.fr> <21D03162-81D1-494A-89A9-41BE89D28A0E@nominum.com> <BB7627E9-8D50-48E5-B809-64AE4D574271@virtualized.org> <20131203221006.GB5689@sources.org> <D3E446D0-F9ED-4671-A1C2-29A15D3DE010@virtualized.org> <20131204094449.GA5492@nic.fr> <9650BF6D-727B-4EF3-B357-7E4E2FDDE0AF@virtualized.org> <2614C613-1399-429D-856B-5E2C18DCA7A6@kumari.net> <1DA98CD6C61144088EA480D71E51AF3D@hopcount.ca> <Prayer.1.3.5.1312051215460.21609@hermes-2.csi.cam.ac.uk> <0AE0E07B-2509-440D-81CF-4A75A7F95F45@hopcount.ca>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Chris Thompson <cet1@hermes.cam.ac.uk>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: [DNSOP] DNAMEs in the root zone? [was: Re: draft-grothoff-iesg-special-use-p2p-names-00.txt]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: cet1@cam.ac.uk
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: <http://www.ietf.org/mail-archive/web/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: Mon, 09 Dec 2013 14:41:13 -0000

On Dec 7 2013, Joe Abley wrote:

>On 2013-12-05, at 07:15, Chris Thompson <cet1@cam.ac.uk> wrote:
[...]
>> How would such DNAMEs interact with use of BIND's "root-delegation-only"
>> (or equivalents, if any, in other software)? Do we have any idea how
>> widespread use of that option is?
>
>I don't recall there ever being a time when the default behaviour of BIND9
>was to insist on delegation-only behaviour from the *root* zone. As I
>remember those fun and exciting, lawyer-infested times the delegation-only
>behaviour was applied to all TLD zones, except those that were specified
>as needing to be otherwise.

Well the BIND9 ARM says

| root-delegation-only
|
|  Turn on enforcement of delegation-only in TLDs (top level domains)
|  and root zones with an optional exclude list.

so I presume it *is* meant to apply to the root zone. In the absence
of an offending RR in the real root zone, I suppose I would have to
set up a configuration with a fake root to confirm that. 

root-delegation-only has never been a distribution BIND default, and
the words about it in the ARM should be enough to put anyone reading
them off the idea, Could it be in packaged configurations, though?
Or just in private configurations dating from the 10-years-ago
"*.com" wildcard era and not modified since?

-- 
Chris Thompson               University of Cambridge Computing Service,
Email: cet1@ucs.cam.ac.uk    Roger Needham Building, 7 JJ Thomson Avenue,
Phone: +44 1223 334715       Cambridge CB3 0RB, United Kingdom.