[Add] [Editorial Errata Reported] RFC9606 (8425)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 20 May 2025 07:41 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: add@ietf.org
Delivered-To: add@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 853772A90E08; Tue, 20 May 2025 00:41:49 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 2EB542361F4; Tue, 20 May 2025 00:41:49 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250520074149.2EB542361F4@rfcpa.rfc-editor.org>
Date: Tue, 20 May 2025 00:41:49 -0700
Message-ID-Hash: 3ZSSETMZUAYU42SBJNSTGS4ZRIDAK7BT
X-Message-ID-Hash: 3ZSSETMZUAYU42SBJNSTGS4ZRIDAK7BT
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mkoerber@akamai.com, kondtir@gmail.com, mohamed.boucadair@orange.com, add@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Add] [Editorial Errata Reported] RFC9606 (8425)
List-Id: Applications Doing DNS <add.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/tdUDCv_DhcLcyggKlGfhoD5MEoc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Owner: <mailto:add-owner@ietf.org>
List-Post: <mailto:add@ietf.org>
List-Subscribe: <mailto:add-join@ietf.org>
List-Unsubscribe: <mailto:add-leave@ietf.org>
The following errata report has been submitted for RFC9606, "DNS Resolver Information". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8425 -------------------------------------- Type: Editorial Reported by: Mathias Koerber <mkoerber@akamai.com> Section: 3, paragraph 2 Original Text ------------- A DNS client can retrieve the resolver information using the RESINFO RR type and the QNAME of the domain name that is used to authenticate the DNS resolver (referred to as the Authentication Domain Name (ADN) in DNR [RFC9463]). Corrected Text -------------- A DNS client can retrieve the resolver information using the RESINFO RR type and the QNAME of the domain name that is used to authenticate the DNS resolver (referred to as the Authentication Domain Name (ADN) in DNR [RFC9463]) Notes ----- The link to RFC9463 at the end of the paragraph has an Anchor of https://www.rfc-editor.org/rfc/rfc9606.html#RFC9463 which just pointspback to itself, instead of to the actual RFC946 document The correct link should IMHO be https://www.rfc-editor.org/rfc/rfc9463 (or maybe it should point to the relevant line in Section 9 References that has details of the RFCs)? 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. -------------------------------------- RFC9606 (draft-ietf-add-resolver-info-13) -------------------------------------- Title : DNS Resolver Information Publication Date : June 2024 Author(s) : T. Reddy.K, M. Boucadair Category : PROPOSED STANDARD Source : Adaptive DNS Discovery Stream : IETF Verifying Party : IESG
- [Add] [Editorial Errata Reported] RFC9606 (8425) RFC Errata System
- [Add] Re: [Editorial Errata Reported] RFC9606 (84… mohamed.boucadair