On Wed, May 24, 2023 at 10:01:49AM -0400, Tim Wicinski wrote:
> All
>
> The authors for RFC8109 have made some updates to their document
> "Initializing a DNS Resolver with Priming Queries", and are looking to have
> the
> work adopted by DNSOP.
>
> You can see the changes made since RFC8109 here:
>
> https://author-tools.ietf.org/iddiff?url1=rfc8109&url2=draft-klh-dnsop-rfc8109bis-06&difftype=--html
>
> This starts a Call for Adoption for draft-klh-dnsop-rfc8109bis
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-klh-dnsop-rfc8109bis/
>
>
> Please review this draft to see if you think it is suitable for adoption
> by DNSOP, and send any comments to the list, clearly stating your view.
>
> Please also indicate if you are willing to contribute text, review, etc.
>
> This call for adoption ends: 7 June 2023
>
> Thanks,
> tim wicinski
> For DNSOP co-chairs
Hello,
Section 3.1 mentions:
(Note that a recursive resolver MAY pre-fetch the NS RRset before it
expires.) Followed by a [[ need to discuss ]]
I think this part could be elaborated upon: especially if some of the
addresses in the hints are outdated it is good to use data previously
obtained to re-prime the root, i.e. repeat the priming using cached
data *before expiry*.
That way the potentially outdated hint data is only used once during
the lifetime of the resolver at startup. Subsequent refresh queries
are done using up-to-date data and will pick up future changes as well
without trying to contact no-longer existing root addresses.
-Otto
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
