Dear Desiree,

on this, speaking from a personal perspective and not EURALO, which I'll leave to Sébastien Bachollet, I should add that I agree with the points the Statement makes, with the added point that the inherent robustness of the Internet has always been due to its diversity: diverse technologies with nameservers and resolvers that were running on a variety of technologies. Putting together a uniform set of DNS resolvers, all of which run on the same technology, will actually weaken the European Internet infrastructure rather than enhance it, as it will reduce that diversity of technologies that mitigates attacks using specific security flaws and buggy updates.
Kindest regards,

Olivier

On 03/02/2022 22:16, Desiree Miloshevic wrote:
Dear members, dear all

Further to the RIPE NCC’s summary of the DNS4EU Open House discussion and further to your witnessing of our earlier 'transparent wordsmithing consultation' with other RIPE - WG Chairs,
I’d like to propose the following high level statement draft for your consideration. 

Julf and myself, as Co-Chairs are in agreement with this draft statement and Achilleas had excused himself due to his affiliation with the EC.

We’d like to know if there is some support from members for having a RIPE community response on this proposal?

We would really appreciate your feedback or any comments you’d wish to make or if you'd like us to work further on this.

Many thanks for your consideration and the feedback,

Desiree
--
Coop WG Co-Chair

Proposed DNS4EU RIPE community statement comments


  1. RIPE community believes that governance of the DNS resolution chain, which is such an important element of everybody's Internet connectivity, should involve all stakeholders and can not solely rely on legislation and regulatory oversight.
  1. RIPE Community believes that the responsibility of well-functioning Internet access including the DNS resolution is with the access providers. We believe it should stay that way.
  2. We understand that to be able to minimise some risks when the end user selects a random DNS resolver, a possible and feasible solution is to have the access provider run their local DNS resolvers and/or an additional DNS resolver as a back-up.
  3. On 2 Feb 2022, at 15:26, Chris Buckridge <chrisb@ripe.net> wrote:
    Dear colleagues,  Thank you to all who joined for the RIPE NCC Open House discussion of DNS4EU on Monday, 31 January. We have posted a summary of some key points and links to the video archive here:  https://labs.ripe.net/author/chrisb/dns4eu-ripe-ncc-open-house-discussion/ Cheers Chris --  To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https:


-- 
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html