Hi Reading both of these and then the comments, I am in the "combine the two documents", but I feel the "how we get the root zone" portion will change more frequently than "what we do with it". Is having two shorter documents simpler ?
Either case a better explanation on updating 8806. tim On Fri, Nov 6, 2026 at 10:42 AM Benno Overeinder <[email protected]> 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] >
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
