This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-resolver-tf] RIPE DNS Resolver BCP Task Force - Reviewing Charter
- Previous message (by thread): [dns-resolver-tf] RIPE DNS Resolver BCP Task Force - Reviewing Charter
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Wicinski
tjw.ietf at gmail.com
Tue Jan 24 11:26:52 CET 2023
Mirjam Thanks for this. On Mon, Jan 23, 2023 at 4:39 AM Mirjam Kuehne <mir at zu-hause.nl> wrote: > Hi all, > > As mentioned in my previous mail, the charter is currently marked as DRAFT: > > "The Task Force will gather best current practices for the operation of > DNS resolvers and work towards producing a recommendation of operational > practices that will be available to the RIPE community and the Internet > community at large." > > You might have seen that Lars-Johan Liman raised some concerns on the > RIPE Discussion List that this text might be too limiting. In the > meantime I worked with Liman on some alternative text: > > "The Task Force will gather best current practices for the operation of > DNS resolvers and look at various design alternatives. The aim is to > describe the consequences of the various choices and to work towards > producing recommendations of operational practices that will be > available to the RIPE community and the Internet community at large." > > The motivation behind this is to enable DNS resolver operators to make > conscious choices rather providing one BCP for everyone which might lead > to single points of failure. But I am sure Liman can explain better 😄 > > If there are no concerns or suggested changes, I will update the charter > on the website accordingly. > > I agree with Liman on this - I feel strongly that a good BCP should not just be one choice but provide different choices based on different situations. tim -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://ripe.net/ripe/mail/archives/dns-resolver-tf/attachments/20230124/88061058/attachment-0001.html>
- Previous message (by thread): [dns-resolver-tf] RIPE DNS Resolver BCP Task Force - Reviewing Charter
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]