Re: [dns-wg] Candidates for the open co-chair position at the DNS WG

[Peter Hessler]

On 2023 Nov 15 (Wed) at 12:03:19 +0100 (+0100), Joao Luis Silva Damas wrote:
:
:Doris Houser, nominated by Willem Toroop:
:-
:> I would like to propose Doris Hauser as a candidate for the new DNS Working 
group co-chair.
:> 
:> Doris (aka Dodo) is an amazing young lady working at nic.at 
. Doris and I (Willem) were team-mates in the Port 53 Hackathon 
during the last RIPE 87 in Rotterdam, which was a constructive and inspiring 
experience.  It would be a joy for me and Moritz, and I am sure also for the 
working group as a whole, to have Doris as the new DNS Working group co-chair.
:

With Doris being nominated by someone else, I'd like to ask Doris what
her opinion is of running for DNS-WG co-chair.  While I'm sure she would
be terrific in that role, I would like to hear her comments before I
decide where my support should go.

-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/dns-wg

Re: [dns-wg] Candidates for the open co-chair position at the DNS WG

[Peter Hessler]

I think all three would do a great job, but I would like to support Doris
for WG Co-Chair.


-- 
Brain, n.:
The apparatus with which we think that we think.
-- Ambrose Bierce, "The Devil's Dictionary"

-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/dns-wg

Re: [dns-wg] Draft of RIPE DNS Resolver Best Common Practices

[Peter Hessler]

True, but many smaller networks don't particularly care about DNS, and
are only willing to put in a token effort due to lack of personnel and
lack of understanding.

What problem are we trying to solve?  If its "small networks have good dns",
then unfortunately we do need to keep that in mind.

-peter


On 2023 Nov 27 (Mon) at 17:52:33 + (+), Michele Neylon - Blacknight via 
dns-wg wrote:
:Running critical infrastructure isn’t “easy” so if a relatively short document 
scares people off then that’s probably not the worst thing.
:
:I don’t mean to be dismissive of your comments, but providing a DNS resolver 
to users while not super complicated in many respects is a serious undertaking.
:
:Regards
:
:Michele
:
:
:--
:Mr Michele Neylon
:Blacknight Solutions
:Hosting, Colocation & Domains
:https://www.blacknight.com/
:https://blacknight.blog/
:Intl. +353 (0) 59  9183072
:Direct Dial: +353 (0)59 9183090
:Personal blog: https://michele.blog/
:Some thoughts: https://ceo.hosting/
:---
:Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty 
Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845
:
:I have sent this email at a time that is convenient for me. I do not expect 
you to respond to it outside of your usual working hours.
:
:
:From: dns-wg  on behalf of Moritz Müller via dns-wg 

:Date: Monday, 27 November 2023 at 17:47
:To: Shane Kerr 
:Cc: dns-wg@ripe.net 
:Subject: Re: [dns-wg] Draft of RIPE DNS Resolver Best Common Practices
:[EXTERNAL EMAIL] Please use caution when opening attachments from unrecognised 
sources.
:
:If I recall correctly, someone just mentioned at the mic during the BCOP BOF 
session that such a long list of recommendations might actually scare people 
off from running their own resolver.
:Maybe adding a short paragraph in the introduction like the one below might 
address this:
:
:"Operators interested in running their own resolver might find the number of 
recommendations overwhelming. These operators could prioritise the 
recommendations in this document depending on their own requirements and start 
by implementing recommendations based on their priority. “
:
:-
:Moritz
:
:
:> On 26 Nov 2023, at 18:01, Shane Kerr  wrote:
:>
:> Colleagues,
:>
:> Here is a draft of the RIPE DNS Resolver Best Common Practices document
:> that the task force of that name has been working on.
:>
:> The intention is to collect feedback during the RIPE 87 meeting and
:> afterwards, and either publish a RIPE document or another draft based on
:> that.
:>
:> Cheers,
:>
:> --
:> Shane Kerr
:> Chair, RIPE DNS Resolver BCP Task Force
:>
:>
:> # DNS Resolver Recommendations
:>
:> About the DNS Resolver Best Common Practice Task Force
:>  
https://www.ripe.net/participate/ripe/tf/dns-resolver-best-common-practice-task-force
:>
:> ## Terminology
:>
:> * Open Resolver: A DNS resolver that accepts queries from any client.
:>  Often the result of misconfiguration.
:>
:> * Public Resolver: A resolver intentionally configured to be an open
:>  resolver.
:>
:> ## Introduction
:>
:> ### What Is This Document? Who Is It For?
:>
:> This document presents recommendations and best current practices for
:> operating DNS resolvers, both public and non-public ones. It covers
:> technical aspects of operations and provides best practice
:> recommendations for data management, with a particular focus on user
:> privacy, security, and resilience.
:>
:> The document serves as guidance for the wider Internet community,
:> offering input to:
:>
:> * Those running public DNS resolver services, and
:> * Those who want to make informed choices between such services.
:>
:> Its purpose is to provide clear guidance and promote effective
:> practices in DNS resolver operation.
:>
:> The intended audience is not the entire DNS community. Advice here is
:> probably not useful for operators of authoritative servers, domain
:> registrars, and so on. It is also not meant to be an introductory or
:> educational document. There are many documents which cover the basics
:> of DNS and the roles of organizations in it; a good overview is:
:>
:> Addressing the challenges of modern DNS - a comprehensive tutorial
:> by van der Toorn et al.
:>  https://ris.utwente.nl/ws/files/282427879/1_s2.0_S1574013722000132_main.pdf
:>
:> The document does not consider how to measure adherence to these
:> recommendations. So it is not intended to be used for certification,
:> although certification created based on the principles here is
:> possible.
:>
:> ### How Is This Document Organized?
:>
:> This document has a number of sections, and specific recommendations
:> in each section. The intent is for each recommendations to have clear
:> guidance at the top, and then background and discussion related to the
:> recommendation afterwards. Each recommendation indicates whether it is
:> mostly for operators of public resolvers or for operators of any
:> resolver.
:>
:> ## System and Network Hardening
:>

Re: [dns-wg] Candidates for the open co-chair position at the RIPE DNS working group

[Peter Hessler]

I support Moritz for another term as co-chair.


On 2024 Apr 23 (Tue) at 20:52:35 +0200 (+0200), Willem Toorop wrote:
:Dear all,
:
:The deadline for volunteers/nominations has passed and I am very pleased to
:announce that we received a single self-nomination: Moritz Müller applying
:for a second term as co-chair.
:
:We will now collect expressions of support (or opposition) from the
:mailing-list, until Monday 20 May 2024, and will announce the results on
:Wednesday 22 May 2024 during the DNS working group session at the RIPE 88.
:
:Find below Moritz' motivation to apply for a second term:
:
:###
:
:I'd like to volunteer for a second term as RIPE DNS-WG co-chair. In my last
:term, I've helped organizing (hopefully) interesting and diverse
:working-group meetings and I'd like to continue doing this for another 3
:years.
:
:For the next term, I'd like to go on organizing meetings that are relevant
:not only for DNS experts but also for the broader RIPE community with
:interest in the DNS.
:
:###
:
:
:   Timeline
:
: * Monday, 20 May 2024
:   Deadline for showing support for candidates/volunteers on the mail list
:
: * Wednesday, 22 May 2024
:   DNS WG session at RIPE 88
:
:
:   References
:
:The RIPE working group chair job description is included in ripe-692:
:https://www.ripe.net/publications/docs/ripe-692
:
:The DNS working group chair selection process is documented here:
:https://www.ripe.net/participate/ripe/wg/dns/dns-wg-chair-selection-process
:We have 3 co-chairs so the term is 3 years.
:
:The current approach was announced on this mailing list on 2018-07-17:
:https://www.ripe.net/ripe/mail/archives/dns-wg/2018-July/003566.html
:
:As always, please feel free to reach out to any of the chairs directly, to us
:as a group at dns-wg-chairs AT ripe.net, or discuss this or any other any
:relevant topic on this mailing list.
:


-- 
The average income of the modern teenager is about 2 a.m.

-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/dns-wg

Re: [dns-wg] Retiring ns.ripe.net

[Peter Hessler]

On 2024 May 02 (Thu) at 17:28:32 +0100 (+0100), Nick Hilliard wrote:
:Paul de Weerd wrote on 02/05/2024 16:49:
:> We are proposing to retire the secondary DNS service by the end of
:> 2024 and we're asking for your input and feedback on this proposal.
:> Please share any feedback on the DNS Working Group mailing list by 16
:> May 2024.
:
:definitely a good move to retire this.
:

Agreed.


:Could you consider having a different the end-of-service date so that it
:doesn't fall into industry holiday / change freeze periods? There will be a
:lot of change freezes in effect thoughout december and early january, and
:this might affect peoples' ability to fix any problems caused by the service
:disappearing.
:

Doubly agreed.

Semi-related, and apology for the micro-managing, do you think it
would make sense to lower the TTL on those zones from 1 day to something
shorter during the change?



-- 
When all other means of communication fail, try words.

-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/dns-wg