Doh!  That is correct…

Thank you!
W


On Tue, Oct 31, 2023 at 8:59 AM, Joe Abley <[email protected]> wrote:

> Verified.
>
> On 31 Oct 2023, at 04:10, RFC Errata System <[email protected]>
> wrote:
>
> The following errata report has been submitted for RFC8806,
> "Running a Root Server Local to a Resolver".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7692
>
> --------------------------------------
> Type: Editorial
> Reported by: Deliang Chang <[email protected]>
>
> Section: 3
>
> Original Text
> -------------
> There is a risk that a system using a local authoritative server for the
> root zone cannot refresh the contents of the root zone before the expire
> time in the SOA. A system using a local authoritative server for the root
> zone MUST NOT serve stale data for the root zone. To mitigate the risk that
> stale data is served, the local root server MUST immediately switch to
> using non-local root servers when it detects that it would be serving state
> data.
>
> Corrected Text
> --------------
> There is a risk that a system using a local authoritative server for the
> root zone cannot refresh the contents of the root zone before the expire
> time in the SOA. A system using a local authoritative server for the root
> zone MUST NOT serve stale data for the root zone. To mitigate the risk that
> stale data is served, the local root server MUST immediately switch to
> using non-local root servers when it detects that it would be serving stale
> data.
>
> Notes
> -----
> Based on the context, it seems that in the last sentence the intended word
> is "stale" as in stale data, instead of "state". So, I believe there might
> be a typo in the text, and the correct interpretation would be to swith
> back to the non-local root when stale data is detected.
>
> 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.
>
> --------------------------------------
> RFC8806 (draft-ietf-dnsop-7706bis-12)
> --------------------------------------
> Title : Running a Root Server Local to a Resolver Publication Date : June
> 2020
> Author(s) : W. Kumari, P. Hoffman
> Category : INFORMATIONAL
> Source : Domain Name System Operations Area : Operations and Management
> Stream : IETF
> Verifying Party : IESG
>
> _______________________________________________
> DNSOP mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dnsop
>
> _______________________________________________
> DNSOP mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dnsop
>
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to