[dns-privacy] [Technical Errata Reported] RFC9250 (7883)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 05 April 2024 01:39 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 A08F8C14F6E3 for <dns-privacy@ietfa.amsl.com>; Thu, 4 Apr 2024 18:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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 a4QYuudGhDLL for <dns-privacy@ietfa.amsl.com>; Thu, 4 Apr 2024 18:38:57 -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 B6494C14F738 for <dns-privacy@ietf.org>; Thu, 4 Apr 2024 18:38:57 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7736ACE3DB; Thu, 4 Apr 2024 18:38:57 -0700 (PDT)
To: huitema@huitema.net, sara@sinodun.com, allison.mankin@gmail.com, ek.ietf@gmail.com, evyncke@cisco.com, brian@innovationslab.net, tjw.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: lyra@omg.lol, dns-privacy@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240405013857.7736ACE3DB@rfcpa.amsl.com>
Date: Thu, 04 Apr 2024 18:38:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/mfkMtwNmRz6UPab8dnk3afietuM>
X-Mailman-Approved-At: Sat, 06 Apr 2024 11:37:29 -0700
Subject: [dns-privacy] [Technical Errata Reported] 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: Fri, 05 Apr 2024 01:39:02 -0000
The following errata report has been submitted for RFC9250, "DNS over Dedicated QUIC Connections". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7883 -------------------------------------- Type: Technical Reported by: Lyra Naeseth <lyra@omg.lol> 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. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- 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
- [dns-privacy] [Technical Errata Reported] RFC9250… RFC Errata System