RIPE DNS Resolver BCP Task Force - Reviewing Charter
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. Kind regards, Mirjam
Hi Mirjam. Thanks for pushing this along. I am away on holidays this week but will start contributing next week Thanks again Joao
On 23 Jan 2023, at 10:39, Mirjam Kuehne <mir@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.
Kind regards, Mirjam
-- dns-resolver-tf mailing list dns-resolver-tf@ripe.net https://ripe.net/mailman/listinfo/dns-resolver-tf
Mirjam Thanks for this. On Mon, Jan 23, 2023 at 4:39 AM Mirjam Kuehne <mir@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
participants (3)
-
João Damas -
Mirjam Kuehne -
Tim Wicinski