[dns-privacy] [Editorial Errata Reported] RFC8467 (7874)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 28 March 2024 02:05 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 11B70C15152D for <dns-privacy@ietfa.amsl.com>; Wed, 27 Mar 2024 19:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 pBJ9V3fONzXc for <dns-privacy@ietfa.amsl.com>; Wed, 27 Mar 2024 19:05:13 -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 39678C14CEFE for <dns-privacy@ietf.org>; Wed, 27 Mar 2024 19:05:13 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 16EFA191A493; Wed, 27 Mar 2024 19:05:13 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: hello.world@example.com, alex.mayrhofer.ietf@gmail.com, dns-privacy@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240328020513.16EFA191A493@rfcpa.amsl.com>
Date: Wed, 27 Mar 2024 19:05:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/YCihY8LHhnFQ-u56hlYr-_Xdf8I>
Subject: [dns-privacy] [Editorial Errata Reported] RFC8467 (7874)
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: Thu, 28 Mar 2024 02:05:17 -0000
The following errata report has been submitted for RFC8467, "Padding Policies for Extension Mechanisms for DNS (EDNS(0))". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7874 -------------------------------------- Type: Editorial Reported by: hello world <hello.world@example.com> Section: 6 Original Text ------------- Note that even with encryption and padding, it might be trivial to identify that the observed traffic is DNS. Corrected Text -------------- Note that even with encryption and padding, it might be easy to identify that the observed traffic is DNS. Notes ----- easy to understand what that means. 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. -------------------------------------- RFC8467 (draft-ietf-dprive-padding-policy-06) -------------------------------------- Title : Padding Policies for Extension Mechanisms for DNS (EDNS(0)) Publication Date : October 2018 Author(s) : A. Mayrhofer Category : EXPERIMENTAL Source : DNS PRIVate Exchange Stream : IETF Verifying Party : IESG
- [dns-privacy] [Editorial Errata Reported] RFC8467… RFC Errata System