[DNSOP] Paul Wouters' Yes on draft-ietf-dnsop-rfc8109bis-06: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Tue, 20 August 2024 14:29 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from [10.244.2.52] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id EF3D3C151096; Tue, 20 Aug 2024 07:29:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.22.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172416419764.2051711.7085421659943352715@dt-datatracker-6df4c9dcf5-t2x2k>
Date: Tue, 20 Aug 2024 07:29:57 -0700
Message-ID-Hash: 7N3YD56OZ4H2LDNTGAYSAICMOAEN6TLY
X-Message-ID-Hash: 7N3YD56OZ4H2LDNTGAYSAICMOAEN6TLY
X-MailFrom: noreply@ietf.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
CC: draft-ietf-dnsop-rfc8109bis@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Paul Wouters <paul.wouters@aiven.io>
Subject: [DNSOP] Paul Wouters' Yes on draft-ietf-dnsop-rfc8109bis-06: (with COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/y7UmJYT1f6QWLA-oGqW5UnR5hAA>
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>

Paul Wouters has entered the following ballot position for
draft-ietf-dnsop-rfc8109bis-06: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc8109bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

small update to my ballot. I saw and actually do agree with Mark Andrews that
the text about source port randomization should mention DNS COOKIES as well:

     I know this is late in the process but why is DNS COOKIE not suggested
     as it is much better than source port randomisation for eliminating spoofed
     responses?  It even works when NATs that de-randomise source ports are in
     the path.