[DNSOP] Conflict between "Aggressive Use" and "Wildcards"
Edward Lewis <firstname.lastname@example.org> Mon, 05 March 2018 20:19 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD87D12D77D for <email@example.com>; Mon, 5 Mar 2018 12:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([18.104.22.168]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WHLVlOH2YWmP for <firstname.lastname@example.org>; Mon, 5 Mar 2018 12:19:16 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [22.214.171.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89BC3129515 for <email@example.com>; Mon, 5 Mar 2018 12:19:16 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (126.96.36.199) by PMBX112-W1-CA-1.pexch112.icann.org (188.8.131.52) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 5 Mar 2018 12:19:14 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([184.108.40.206]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([220.127.116.11]) with mapi id 15.00.1178.000; Mon, 5 Mar 2018 12:19:14 -0800
From: Edward Lewis <firstname.lastname@example.org>
To: "email@example.com" <firstname.lastname@example.org>
Thread-Topic: Conflict between "Aggressive Use" and "Wildcards"
Date: Mon, 5 Mar 2018 20:19:13 +0000
Content-Type: text/plain; charset="utf-8"
Subject: [DNSOP] Conflict between "Aggressive Use" and "Wildcards"
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 20:19:19 -0000
A few weeks ago, I came across a blog post describing a "security hole" in so-called "NSEC Aggressive Use" implementations. https://medium.com/nlnetlabs/the-peculiar-case-of-nsec-processing-using-expanded-wildcard-records-ae8285f236be After some exchanges of email with the blog author, I (probably not alone, but not wanting to speak for anyone else) came to a conclusion that there's a conflict between the documents "Aggressive Use of DNSSEC-Validated Cache"  and "The Role of Wildcards in the Domain Name System" . In the latter document, this text appears in " NSEC RRSet at a Wildcard Domain Name" (section 4.7): # "Synthesized NSEC RRs will not be harmful as they will never be used in # negative caching or to generate a negative response [RFC2308]." From this, the former document ought to list it as updating the latter document, and explain how. This seems (said without confirming) to be the origin of the implementation difficulties. I tried (once, a while ago) to contact the editors of the "Aggressive Use" document, but haven't gotten a response. Suggestions?  https://www.rfc-editor.org/rfc/rfc8198.txt  https://www.rfc-editor.org/rfc/rfc4592.txt
- [DNSOP] Conflict between "Aggressive Use" and "Wi… Edward Lewis