On Sat, Nov 07, 2026 at 11:04 AM, Joe Abley < [email protected]> wrote:
> On 7 Nov 2026, at 08:47, Wes Hardaker <[email protected]> wrote: > > Benno Overeinder <[email protected]> writes: > > - draft-wkumari-dnsop-localroot-bcp > > It should not be a surprise that I believe this document should be adopted > and renamed (and not as a BCP candidate, as stated at the last IETF). > > I think there is value in making recommendations around this practice so > that its implementation becomes more robust and consistent. Providing the > kind of guidance that implementers can use to help with that is a good > idea. > > I think this document can help. I support adoption. > > I am more comfortable with this document simply providing operational > guidance than I am with it being labelled a BCP. > Yup. The document name is draft-wkumari-dnsop-localroot-bcp because the initial version proposed it as a BCP, but we changed the Intended Status to Standards Track after discussion with the WG. If adopted, when we upload it well drop the -bcp part. We didn't want to rename it before this, because it arguably would have led to more confusion[0]. Thank you, W [0]: Of course, it might have led to less confusion - we've had a number of people say "I don't like this because it's a BCP" and we've had to mention that it isn't anymore. As an important note to self: Never include the intended track in a draft name - it leads to confusion. Mainly this is because I think the root server system is a better bet for > stability for many people than maintaining a local dependency. But if > people are going to do it, they may as well do it well. > > Joe >
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
