Re: [DNSOP] new draft: 'NSEC(3) TTLs and NSEC Aggressive Use' (New Version Notification for draft-vandijk-dnsop-nsec-ttl-00.txt)

Peter van Dijk <peter.van.dijk@powerdns.com> Wed, 06 January 2021 20:02 UTC

Return-Path: <peter.van.dijk@powerdns.com>
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 1AEB93A124C for <dnsop@ietfa.amsl.com>; Wed, 6 Jan 2021 12:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.009, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 9jub8YnWNdWA for <dnsop@ietfa.amsl.com>; Wed, 6 Jan 2021 12:02:32 -0800 (PST)
Received: from mx3.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 A62A33A1432 for <dnsop@ietf.org>; Wed, 6 Jan 2021 12:01:44 -0800 (PST)
Received: from imap.open-xchange.com (imap.open-xchange.com [84.81.54.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id AC02E6A22E; Wed, 6 Jan 2021 21:01:41 +0100 (CET)
Received: from plato ([84.81.54.175]) by imap.open-xchange.com with ESMTPSA id EfPTKCUX9l+QPQAA3c6Kzw (envelope-from <peter.van.dijk@powerdns.com>); Wed, 06 Jan 2021 21:01:41 +0100
Message-ID: <bbd6c5d2866abcff6617e09c9a4e3ab319cc096a.camel@powerdns.com>
From: Peter van Dijk <peter.van.dijk@powerdns.com>
To: dnsop@ietf.org
Date: Wed, 06 Jan 2021 21:01:41 +0100
In-Reply-To: <bf61d356-0e9b-6b42-3ee2-9420be0d1460@nic.cz>
References: <160616178406.24526.15858981444327414727@ietfa.amsl.com> <ca6217f45a8b3be86fb62f4967a342bb50b241a0.camel@powerdns.com> <bf61d356-0e9b-6b42-3ee2-9420be0d1460@nic.cz>
Organization: PowerDNS.COM B.V.
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5-1.1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0bsSz8dcWFiThawAgjwPcXyNq0M>
Subject: Re: [DNSOP] new draft: 'NSEC(3) TTLs and NSEC Aggressive Use' (New Version Notification for draft-vandijk-dnsop-nsec-ttl-00.txt)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Jan 2021 20:02:34 -0000

Hello Vladimir,

On Sat, 2020-12-12 at 11:46 +0100, Vladimír Čunát wrote:
>  From resolver point of view... this implies that signed *positive* 
> wildcard answers will now get cached with this shorter "negative TTL", 
> right?  These do need to deny existence of non-wildcard match, so they 
> need to contain NSEC*.

That depends on whether a resolver caches wildcards with the TTL of the
wildcard RRset, or of the NSECs proving that the wildcard expansion is
valid. My suspicion is that most resolvers today do the former, and
when they grow the 'aggressive NSEC for wildcards' feature, they'll
take MIN(former, latter).

> Maybe the final text would better explicitly note such implications, but 
> that certainly can wait way past WG adoption. Also it might be confusing 
> that just by singing a zone the effective TTL of these answers would get 
> lower - assuming I got your intention right (if not, perhaps the current 
> text wasn't clear enough anyway).

Whether signing a zone lowers the TTL on an expanded wildcard depends entirely on the implementation - basically my previous paragraph in this email. I'd say the right approach is the MIN(..) from the previous paragraph.

However, I'm unsure what text the document should have about this. As in my response to Matthijs, the problem flows from 8198 but the problem is not in 8198. That said, we can always put more explanations in this document - perhaps even a Background section, and then I can shorten the Introduction section to only explain the core of the problem.
 
Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/