I support publication. The remainder feel like nits which would get resolved in editor queue.
I discussed the priming issue with Paul H privately and I think his response covered my concerns. Basically, if you run hyperlocal root, it subsumes the functionality of the cache priming activity, but it doesn't need to be explicit in this document, its a redundency, and adding language to address this is like patching 8806 as a side effect, which we don't need to do: in fact, it has risks. Better to leave it out. -G On Tue, Jan 9, 2024 at 11:55 AM Tim Wicinski <[email protected]> wrote: > > All > > > This starts a Working Group Last Call for draft-ietf-dnsop-rfc8109bis > "Initializing a DNS Resolver with Priming Queries" > > Current versions of the draft is available here: > https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc8109bis/ > > The Current Intended Status of this document is: Best Current Practice > > Please review the draft and offer relevant comments. > > For WGLC, we need *positive support and constructive comments*; lack of > objection is not enough. > So if you think this draft should be published as an RFC, please say so. > > If you feel the document is *not* ready for publication, please speak out > with your reasons. > > > This starts a two week Working Group Last Call process, and ends on: January > 22, 2024 > > thanks > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
