[dns-privacy] [Errata Verified] RFC9250 (7883)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 23 April 2024 13:14 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 522A5C14F61B; Tue, 23 Apr 2024 06:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.649
X-Spam-Level:
X-Spam-Status: No, score=-6.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 U6cK_piAfbvf; Tue, 23 Apr 2024 06:14:46 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6D67C14F702; Tue, 23 Apr 2024 06:14:46 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 8AD4D11FDEC; Tue, 23 Apr 2024 06:14:46 -0700 (PDT)
To: lyra@omg.lol, huitema@huitema.net, sara@sinodun.com, allison.mankin@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: evyncke@cisco.com, iesg@ietf.org, dns-privacy@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240423131446.8AD4D11FDEC@rfcpa.amsl.com>
Date: Tue, 23 Apr 2024 06:14:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/bvtqcuChghQo4wZzkvlwyUOPu0g>
Subject: [dns-privacy] [Errata Verified] RFC9250 (7883)
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Addition of privacy to the DNS protocol <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2024 13:14:51 -0000

The following errata report has been verified for RFC9250,
"DNS over Dedicated QUIC Connections". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7883

--------------------------------------
Status: Verified
Type: Technical

Reported by: Lyra Naeseth <lyra@omg.lol>
Date Reported: 2024-04-05
Verified by: Eric Vyncke (IESG)

Section: 7.5

Original Text
-------------
Implementations SHOULD use the mechanisms defined in Section 5.4 to
mitigate this attack.

Corrected Text
--------------
Implementations MUST use the padding mechanisms defined in Section 5.4
to mitigate this attack.

Notes
-----
Section 5.4 states that "[i]mplementations MUST protect against the traffic analysis attacks described in Section 7.5", but Section 7.5 describes that obligation as a "SHOULD". "MUST" is correct, and the inconsistent "SHOULD" in Section 7.5 is an error.

-- Verifier (Eric Vyncke) note --

The short discussion on the DPRIVE WG list has indicated that 2 authors are in favour of verifying this errata.

--------------------------------------
RFC9250 (draft-ietf-dprive-dnsoquic-12)
--------------------------------------
Title               : DNS over Dedicated QUIC Connections
Publication Date    : May 2022
Author(s)           : C. Huitema, S. Dickinson, A. Mankin
Category            : PROPOSED STANDARD
Source              : DNS PRIVate Exchange
Stream              : IETF
Verifying Party     : IESG