I am opposed to a "cache only" specification of LocalRoot. Caches are subject to eviction and expiration, so a simple cache-only LocalRoot implementation would not naturally offer strong guarantees about leakage to the root. I support documenting such a "mostly local" root serving behavior, but I would also like to see the specification include the "parallel authoritative" and "hyperlocal root" behaviors documented in draft-wkumari-dnsop-localroot-bcp Section 3.3, as these may be necessary to achieve certain privacy properties, reliable functioning on air-gapped networks, etc.
(Specifying a "reliably cached" LocalRoot behavior would be a contradiction in terms, in my view.) --Ben On Sun, Nov 8, 2026 at 11:50 AM Jamal Leblanc <[email protected]> wrote: > > Hello, Thank you everyone for giving equal time for my comments and > supporting them. I agree with Paul as an author suggesting another's work. > His faith in the process is another reason worth supporting that direction. > Thank you. Best regard, > > Hello, > > Thank you everyone for giving equal time for my comments and supporting them. > I agree with Paul as an author suggesting another's work. His faith in the > process is another reason worth supporting that direction. > > Thank you. > > Best regard, > Jamal > > Jamal Peter Le Blanc > 7927 Otter Cove Ct > Gaithersburg, MD 20879 > (240) 715-5037 > [email protected] > https://ATempleJar.Substack.com > > On Sun, Nov 8, 2026, 11:44 Peter Thomassen <[email protected]> > wrote: >> >> All speaking for myself, of course. >> Peter >> >> On 11/8/26 11:54, Peter Thomassen wrote: >> > I think there should be implementation flexibility (pre-filling cache, >> > local auth, ...), but I do think that Paul's points about re-using the >> > normal cache are pretty compelling. >> > >> > I therefore think that either the rootcache document should be relaxed, to >> > describe its current method and recommend it, but allow others, or >> > alternatively the localroot document should spell out clearly that cache >> > prefill has some safety belts you'd otherwise have to think of when using >> > a different approach, and therefore recommend it. Both cases would lead to >> > the same document. If I was the editor, I would start from Paul's coz >> > succinctness. >> > >> > I don't have a preference which is adopted (if any), so this really >> > doesn't really answer the call and is more like a comment. >> > >> > Best, >> > Peter >> > >> > >> > On 11/6/26 16:41, Benno Overeinder wrote: >> >> Dear WG, >> >> >> >> This message starts a DNSOP WG Call for Adoption of: >> >> - draft-wkumari-dnsop-localroot-bcp >> >> *OR* >> >> - draft-hoffman-rootcache >> >> >> >> This joint call for adoption, in which only one of the proposed drafts >> >> can be adopted, is the result of discussions in the DNSOP WG during IETF >> >> 125 and 126. >> >> >> >> This Working Group Call for Adoption ends on 2026-11-20. >> >> >> >> Wes Hardaker presented "RSS Communication / LocalRoot / RootCache" at the >> >> DNSOP WG session during IETF 126. This presentation followed up on the >> >> DNSOP meeting at IETF 125, where the WG had requested a problem statement >> >> document. >> >> >> >> In fact, three questions were raised regarding possible calls for >> >> adoption. With this email, we are initiating the first of these calls. >> >> >> >> Please reply to this message and indicate whether or not you support >> >> adoption of (pick one): >> >> - draft-wkumari-dnsop-localroot-bcp (with a rename to drop the -bcp) >> >> - draft-hoffman-rootcache >> >> >> >> Or don't do anything at all. >> >> >> >> Comments to explain your preference are greatly appreciated. Please >> >> reply to all recipients of this message and include this message in your >> >> response. >> >> >> >> The adoption of either draft would result in the replacement of RFC 8807, >> >> which could then be marked as Historic. >> >> >> >> Best regards, >> >> >> >> -- Benno >> >> for the DNSOP co-chairs >> >> >> >> >> >> _______________________________________________ >> >> DNSOP mailing list -- [email protected] >> >> To unsubscribe send an email to [email protected] >> > >> >> -- >> Like our community service? 💛 >> Please consider donating at >> >> https://desec.io/ >> >> deSEC e.V. >> Möckernstraße 74 >> 10965 Berlin >> Germany >> >> Vorstandsvorsitz: Nils Wisiol >> Registergericht: AG Berlin (Charlottenburg) VR 37525 >> >> _______________________________________________ >> DNSOP mailing list -- [email protected] >> To unsubscribe send an email to [email protected] > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
