IETF Logo Mail Archive

[DNSOP] Re: New Version Notification for draft-bortzmeyer-dnsop-poisonlicious-05.txt

Bill Woodcock <woody@pch.net> Tue, 04 August 2026 19:30 UTC

Return-Path: <woody@pch.net>
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 3A259123A2238 for <dnsop@mail2.ietf.org>; Tue, 4 Aug 2026 12:30:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785871815; bh=S9d2XppS8hIbds2WEIEvRTXaJ2MqFUkxhJ0splmQOuI=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=s+xtKGuTV1jsRgUCyivZxpRKdKgVOvqGBp0LeE1r5UzJ4VVXPjNrytrtZDYGNaW9w b1GvJJsf/LQlLmfn3U2SdJMhmPwis0VCf3GZKtO2/kLOhY7kdR+4l9Y9Pj50Sup+8T VUif7Jk+4QGzLPPRAkiAZBCuMzTxDWXQ34WD0hBY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_HELO_NONE=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=pch.net
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 J78GskFeNjBG for <dnsop@mail2.ietf.org>; Tue, 4 Aug 2026 12:30:14 -0700 (PDT)
Received: from secmail.pch.net (secmail.pch.net [206.220.231.87]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id BD3DC123A222D for <dnsop@ietf.org>; Tue, 4 Aug 2026 12:30:14 -0700 (PDT)
Received: from secmail.pch.net (localhost [127.0.0.1]) by secmail.pch.net (Postfix) with ESMTP id 4hF3Xk1Xdmz4yQQc for <dnsop@ietf.org>; Tue, 4 Aug 2026 12:30:14 -0700 (PDT)
Authentication-Results: secmail.pch.net (amavisd-new); dkim=pass (2048-bit key) reason="pass (just generated, assumed good)" header.d=pch.net
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pch.net; h= x-mailer:to:references:message-id:date:in-reply-to:from:subject :mime-version:content-type; s=secmail_dkim; t=1785871813; x= 1788463814; bh=S9d2XppS8hIbds2WEIEvRTXaJ2MqFUkxhJ0splmQOuI=; b=q 3HwnOG5jlOm3C2VvgyQSWQfUCwuua643l/ZW2aR3wVJPaceBFEF+u9Zwm0wUVYI+ iBIQVmMXvLdWdDL4QpWwVjivbyPscsktgH43RA1Y5MQ4fgniU73xLd05DFDpwc6c gZ5H5NPDM3PEOmYmEP9cjLu2rCP7zdNyQyKEtMm5N2KIx6CLqDvUdyzBzmgKp5Ym R4O+6NzyAj+8IssXvIndtCBTHWQJ7QCIJgwrnKXI0eLIBAtEGhMJKR2a1Olrktog tVcNiiVzRcJG+RxtPi/JD2B2bgKpryCJteaguWhEn5evzypEfGTIDF9W6uYRUufq zb9hAwmH2nQSBcRPvtlOA==
X-Virus-Scanned: amavisd-new at secmail.pch.net
Received: from secmail.pch.net ([127.0.0.1]) by secmail.pch.net (secmail.pch.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9BFIOSWTt8VU for <dnsop@ietf.org>; Tue, 4 Aug 2026 12:30:13 -0700 (PDT)
Received: from smtpclient.apple (unknown [66.185.123.190]) by secmail.pch.net (Postfix) with ESMTPSA id 4hF3Xj1VlKz4yQQQ; Tue, 4 Aug 2026 12:30:13 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_C16EE159-41A0-40A5-8B01-F3319DD42F2D"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.1\))
From: Bill Woodcock <woody@pch.net>
In-Reply-To: <m2zez1em7l.fsf@farrokhi.net>
Date: Tue, 04 Aug 2026 21:30:10 +0200
Message-Id: <E66439A7-EB1D-43DF-91E9-42B49051AD77@pch.net>
References: <178586655868.1998675.29436192776087871@dt-datatracker-d4d6ff9d9-ql5mb> <m2zez1em7l.fsf@farrokhi.net>
To: Babak Farrokhi <babak=40farrokhi.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3864.700.51.1.1)
Message-ID-Hash: TBBU5VX4SE6ICK3NRBMWCDMX76SDYMDJ
X-Message-ID-Hash: TBBU5VX4SE6ICK3NRBMWCDMX76SDYMDJ
X-MailFrom: woody@pch.net
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: IETF DNSOP WG <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: New Version Notification for draft-bortzmeyer-dnsop-poisonlicious-05.txt
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mwcbnDnsc40HDcGs9tz3t7SS9PA>
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 Aug 4, 2026, at 21:10, Babak Farrokhi <babak=40farrokhi.net@dmarc.ietf.org> wrote:
> 1- Paul Wouters asked for a mode allowing mutually untrusted nodes to
>   share only DNSSEC-validated data, like pool.ntp.org does. We have not
>   done that, since we think it is a different trust model from what
>   draft describes. 

It is indeed a different trust model, but in many cases (national “internet shutdown” for instance) it may be a more broadly-useful one.  I advocate in favor of including it, in the manner Paul suggests.

                                -Bill

v2.46.0 | Report a Bug | By Email | System Status