[DNSOP] Re: A question regarding DNSSEC validation

John Kristoff <jtk@dataplane.org> Tue, 21 April 2026 20:05 UTC

Return-Path: <jtk@dataplane.org>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 639BDE052616 for <dnsop@mail2.ietf.org>; Tue, 21 Apr 2026 13:05:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776801903; bh=xeW88ZAXIX9lIG4TZVM7Pu0qDkaOYrgBd6pBcPOtIu4=; h=Date:From:To:Subject:In-Reply-To:References; b=hbtFN3Al/X1F5oVu3x7UzhHPBIhWm/6lGTEK+TJROFVXyn78MPCiAg067DgeL0Qu+ e7f01FauDgV1/0u5EWxV8Jg2j5S5kcozPj5+VE3y6PF3/yHdVm/Pw5iAb4NV4ufJb6 ifqvCJbcGw3w3oSQtqK0wW3oBwGt88FZsToUD44U=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=dataplane.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nuEWhh4ef-rk for <dnsop@mail2.ietf.org>; Tue, 21 Apr 2026 13:05:02 -0700 (PDT)
Received: from dataplane.org (dataplane.org [50.31.183.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6D09AE052611 for <dnsop@ietf.org>; Tue, 21 Apr 2026 13:05:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dataplane.org; s=2025121200a; t=1776801902; bh=xeW88ZAXIX9lIG4TZVM7Pu0qDkaOYrgBd6pBcPOtIu4=; h=Date:From:To:Subject:In-Reply-To:References:From; b=SgLm/1lKzWYT1toTPtDnereXY0e7t5cxmwqt35scHkgb8oQr7teY3Kj3OESjmhlC8 MtFpZhUkKhN4uXjk7YxYDP0MWzXinQHb85weT/ibDFIiKXGpyYOrsYBxYHdt3H6oMr QTZ0m6l1JSlVL7WJeL04BSr5X+uL+u+kUmx7EtxulNJX9rl3gOEb24QjZGzyjjJP5V iDGF218iThIrZsJb+CdA5WMzMmpfdrbYbQkBqKtA53obda3tAi7LDEI+ix2yAVl2/r u+swYMZd5qQvzppQGovCwVlpT0NEpt0RTQOEeINIVsPVF1p3T8ea0S+66Pstzlz6tp 9fpN3t7mG/6jw==
Received: from localhost (localhost [127.0.0.1]) by dataplane.org (Postfix) with ESMTP id 2C0174020F for <dnsop@ietf.org>; Tue, 21 Apr 2026 20:05:02 +0000 (UTC)
Date: Tue, 21 Apr 2026 15:05:02 -0500
From: John Kristoff <jtk@dataplane.org>
To: dnsop@ietf.org
Message-ID: <20260421150502.1cc26708@dataplane.org>
In-Reply-To: <CAHPuVdUjoYz7P1-eZBC+-wci5W_6fK5UaJ-trPxMe4Jv8w9xbA@mail.gmail.com>
References: <749d198c.101a.19d93e2675d.Coremail.scooct@163.com> <CAOdQrVMv+PhzCc1_=uAqb=qWeF53um5VwnkhPFsSgK40XSt=yw@mail.gmail.com> <907eeced-4878-4d55-b3cb-48ecd6b9a780@nic.cz> <CAHPuVdWog2kHVG_zYDfo_JJjoHaMbyLjf0_j_6iEZ=d5UvReFg@mail.gmail.com> <BEFAB35F-B622-4395-88CD-F3B616C62254@gmail.com> <CAHPuVdUjoYz7P1-eZBC+-wci5W_6fK5UaJ-trPxMe4Jv8w9xbA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: B4MCRN3RG3NRJSHJO5UEKKY6MKUM3A2A
X-Message-ID-Hash: B4MCRN3RG3NRJSHJO5UEKKY6MKUM3A2A
X-MailFrom: jtk@dataplane.org
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: A question regarding DNSSEC validation
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/aQPry5qbJrO3zQsH7PoCl5CUyuI>
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>

On Tue, 21 Apr 2026 15:41:04 -0400
Shumon Huque <shuque@gmail.com> wrote:

> Unless I've missed it, this does not seem to be clearly addressed
> today anywhere in the DNS specs.

In addition to the quoted bits IETF RFCs 1034 and 1035 I put in my last
message, IETF RFC 4035 has this:

  4.7 Caching BAD Data

    While many validation errors will be transient, some are likely to
    be more persistent, such as those caused by administrative error
    (failure to re-sign a zone, clock skew, and so forth).  Since
    requerying will not help in these cases, validating resolvers might
    generate a significant amount of unnecessary DNS traffic as a result
    of repeated queries for RRsets with persistent validation failures.

    To prevent such unnecessary DNS traffic, security-aware resolvers MAY
    cache data with invalid signatures, with some restrictions.

It is not clear to me from this if data should be considered bad after a
single response or if it is OK for a resolver to retry other name
servers to be sure. I could imagine someone interpreting it either way.

Hopefully these bits are useful leads as to what specifically may need
clarification in your proposal.

John