[DNSOP] Re: Fwd: New Version Notification for draft-yorgos-dnsop-dry-run-dnssec-02.txt

Philip Homburg <pch-dnsop-5@u-1.phicoh.com> Fri, 19 July 2024 17:34 UTC

Return-Path: <pch-b538D2F77@u-1.phicoh.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 3EEEDC14F71F for <dnsop@ietfa.amsl.com>; Fri, 19 Jul 2024 10:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tOV-S4NQYYID for <dnsop@ietfa.amsl.com>; Fri, 19 Jul 2024 10:34:49 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [IPv6:2a10:3781:2413:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF16EC14F6BB for <dnsop@ietf.org>; Fri, 19 Jul 2024 10:34:37 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #158) id m1sUrUy-0000MXC; Fri, 19 Jul 2024 19:34:28 +0200
Message-Id: <m1sUrUy-0000MXC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop-5@u-1.phicoh.com>
Sender: pch-b538D2F77@u-1.phicoh.com
References: <172046952695.458153.14393628216486074514@dt-datatracker-5f88556585-j5r2h> <659a0f2a-eb82-4769-ad80-63e4f3a24978@nlnetlabs.nl> <SA1PR15MB43700A14CBADA73B4F63D766B3A22@SA1PR15MB4370.namprd15.prod.outlook.com> <4d0cb8bc-4c18-42aa-bc7d-18cf6ad7c90c@nlnetlabs.nl> <6dbdacc0-51b1-4180-bbb6-e70c17695e8c@desec.io>
In-reply-to: Your message of "Fri, 19 Jul 2024 09:57:05 -0700 ." <6dbdacc0-51b1-4180-bbb6-e70c17695e8c@desec.io>
Date: Fri, 19 Jul 2024 19:34:28 +0200
Message-ID-Hash: 3DCXP7YCBFABQ7RDE56MNYTGXVERIH2F
X-Message-ID-Hash: 3DCXP7YCBFABQ7RDE56MNYTGXVERIH2F
X-MailFrom: pch-b538D2F77@u-1.phicoh.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Peter Thomassen <peter@desec.io>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: Fwd: New Version Notification for draft-yorgos-dnsop-dry-run-dnssec-02.txt
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3hg2d-S3GJjkcZYHT_x8OhxI7Ng>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

> To prevent this discrepancy between how dry-run and real validation
> is done, the resolver either needs to halve its work bounds (which
> is a disadvantage for real deployments), or commit to twice the
> work it is willing to do.

This would be a problem is the work a validator can reasonably do is
close to the amount of work that is needed in real world scenarios.

I don't think that's the case. So giving twice the resources to a DS RRset
that includes dry-run should not be a problem.

Even if it would be a problem for some particularly busy resolvers, the
world is full of validators that are 99% idle. So the internet as a whole
has enough resources for dry-run.