Return-Path: 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 1CCB0D4E533A for ; Wed, 1 Apr 2026 08:47:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775058468; bh=D14/bAExHTphFPdx5FJ2dBjugBmpeQJZV9k85lSSktY=; h=Date:From:To:Subject:In-Reply-To:References; b=Sva5j4h45ck7dTmv0xpe9okiwMhM/b52//EVC2eOumSfJPrAKMRdIZRlUNNxcl3RU UdPNMKBay4OO/Ieg0f9joZA+VOlbNnT4JuJbMI96qALUftrLGPjlkr0pArFY+xKM3Y umvcAO9nS98NZ1JHn4jj0J0yHlPqdCmU2LmPPDSw= X-Virus-Scanned: amavisd-new at ietf.org 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 t_mnkjG7n9gy for ; Wed, 1 Apr 2026 08:47:47 -0700 (PDT) Received: from mxg.dd.org (rb-sip2-11.greenmountainaccess.net [69.54.28.11]) (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 A9126D4E5332 for ; Wed, 1 Apr 2026 08:47:47 -0700 (PDT) Received: by mxg.dd.org (Postfix, from userid 102) id 655A329D9A8; Wed, 01 Apr 2026 11:47:41 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <27085.15901.387333.288862@gro.dd.org> Date: Wed, 1 Apr 2026 11:47:41 -0400 From: Dave Lawrence To: dnsop@ietf.org In-Reply-To: References: <177364466468.250409.3258111596991249669@dt-datatracker-5477d56788-5pkt5> Message-ID-Hash: ZNOPZBZUBNUM6YH5TZAKYEDDDDA7CKLY X-Message-ID-Hash: ZNOPZBZUBNUM6YH5TZAKYEDDDDA7CKLY X-MailFrom: tale@dd.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: =?utf-8?q?=5BDNSOP=5D_Re=3A_Fwd=3A_New_Version_Notification_for_draft-sury-d?= =?utf-8?q?nsop-parent-centric-resolver-01=2Etxt?= List-Id: IETF DNSOP WG mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Shane Kerr writes: > One thing that I really like about the draft is that it documents > refreshing TTL values for NS on any lookup at the parent. This is > probably something resolver implementers already do, but writing it > down seems useful. It would seem to obviate 11 versions and over 6 years of work on https://datatracker.ietf.org/doc/draft-ietf-dnsop-ns-revalidation/ Or maybe not. I haven't tried to reconcile them.