Dear all,
At the last RIPE Meeting, I presented at the RIPE Community Plenary on
Mastodon, asking if the RIPE NCC should run a server that would be
open to community members. The presentation is at:
https://ripe87.ripe.net/archives/video/1251/
The feedback we got was that this was not something we should do, or
at least not right away. The main concerns were about the work
involved and the difficulties in moderating a public server. Given
this feedback, and considering the costs and maintenance required from
our technical staff, we will not provide a server this year.
However, there were also suggestions that we should dip our toe in the
water. So we have started a RIPE NCC account on Mastodon that
community members can follow. We hope to connect with people and also
learn more about the Mastodon ecosystem. We can then revisit this
question at a later date once we are familiar with the platform and we
can better assess whether there is appetite for us to provide a server
for the community.
If you’re already on Mastodon, you can follow us at:
https://mastodon.social/@ripencc.
See you there!
Best regards,
Ulka Athale
RIPE NCC
Dear colleagues,
I am happy to inform you that the RIPE DNS Resolver Best Common Practice
Task Force [1] finished its work and published a set of recommendations
and best current practices for operators of DNS resolvers - now
available as RIPE Document 823:
https://www.ripe.net/publications/docs/ripe-823/
I would like to take this opportunity to thank all task force members
for their contributions to this document and especially Shane Kerr who
chaired the group and ensured that progress was made and that all
feedback was heard and considered by the task force.
Kind regards,
Mirjam Kühne
RIPE Chair
[1] The RIPE DNS Resolver Best Common Practice Task Force
https://www.ripe.net/community/tf/dns-resolver-best-common-practice-task-fo…
