On Wed, Apr 28, 2021 at 15:55, Stephane Bortzmeyer <bortzmeyer(a)nic.fr> wrote
> Note that despite its name, it is not an "european policy", it is just an individual work developed in Europe. (Hey, I will rebrand my blog as "the European Blog".)
My apologies if I wasn't clear on the call but this statement is incorrect: the policy document is indeed the result of collaboration across the tech and telecoms sectors, with input from a wide range of people. It is intended to provide a policy suited for European resolver operators, noting that anyone is welcome to apply it in other geographies should they feel that it is suitable.
> Indeed, and the so-called "European Resolver Policy" does not have any advantage over RFC 8932 (a good document, I suggest all resolver operators should read it).
The documents address different requirements and you will note that the European Resolver Policy recommends that resolver operators adopt the practices documented in Section 5 of RFC 8932.
> And some negative, too, for instance when it asks resolvers to be lying resolvers by default. Otherwise, it brings very little new content.
This may be a reference to the recommendation that resolver operators take care "in offering DNS resolution without malicious content protection or the blocking of child sexual abuse material as a default option to non-expert end-users such as consumers unless it is unlawful to provide such protections"? It is unclear to me why anyone would wish to offer non-expert users a service that recklessly increases their exposure to harmful or illegal content, although I note that some in the tech sector disagree.
> No. Instead, the DNS WG should raise awareness about RFC 7626 and RFC 8932.
In addition to reading RFC 8932 itself, anyone wanting more information may be interested to know that one of the co-authors of the document joined my weekly call on encrypted DNS a few weeks ago; you can hear her talk about the document in the second half of the call at https://419.consulting/encrypted-dns/f/mozilla-trr-consultation-dns-privacy.
Andrew
Those of you who were on the WG Call last week will of seen Andrew Campling from 419 Consulting give a presentation on the newly developed European Resolver policy.
https://www.ripe.net/participate/ripe/wg/active-wg/dns/remote-sessions/remo…
This is an attempt to get resolver operators to operate in a standard way safeguarding the privacy of their users, some of the content is based around:
RFC 8932 Recommendations for DNS Privacy Service Operators
This policy document has already received some positive feedback and some organisations have already come out in support.
My view is this kind of policy would be more likely to get traction if it had the rubber stamp of a well known organisation behind it, and so I had two ideas to try and make this happen.
1. DNS WG Members review the policy, provide feedback to the authors for potential updates/changes and then when we are happy it is rubber stamped as approved by the RIPE DNS WG
2. Andrew (and other volunteers), turn this into a RIPE Document format which the WG then discuss and modify as needed and then that goes through the process to ratify it as an official RIPE Document.
I’d be very happy to hear other members views on whether either of the above are a good/bad idea or If there is another approach we should take or indeed if the WG should not take this on as a work item at all for any reason.
Thanks
Brett
--
Brett Carr
Manager DNS Engineering
Nominet UK
Dear colleagues,
The European Resolver Policy is intended to provide reassurance to end-users and other stakeholders that personal data gained in the operation of DNS resolution services will not be misused. In this guest post on RIPE Labs, Andrew Campling talks about the aims and benefits of the policy:
https://labs.ripe.net/author/andrew_campling/understanding-the-european-res…
Kind regards,
Alun Davies
RIPE Labs Editor
RIPE NCC
ROW#10: Register now & submit your proposal
June 8th, 2021 | 13:00 - 16:00 UTC | Zoom Video Conference
ROW#10<https://regiops.net> will be held via remote participation on June 8th, 2021, 13:00 - 16:00 UTC. Check additional time zones here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=ROW#10&iso=202106…>.
Registration is NOW available at: https://regiops.net/events/row10registration/
ROW's Program Committee has also opened the call for presentation and panel proposals and is interested in:
1. Topic related presentation proposals.
2. Topic suggestions for focused panel discussions.
3. Suggestions for additional topics.
In the past, workshops have included discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more. Below is a non-exhaustive list of possible topics for this session.
• RDAP implementation experience
• DNS abuse
• DNS privacy and encryption
• Differentiated access
• Authentication and authorization
• Credential Security/Credential Management
• DNSSEC operationalization (CSYNC, managing transfers of secured domains)
• Registration support functions (data escrow/business continuity)
• Automation
• Other innovative uses for registration and resolution technologies
Please email a short abstract describing your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca>
We also encourage discussions/suggestions for additional topics on ROW’s mailing list regiops(a)googlegroups.com<mailto:regiops@googlegroups.com>.
Important dates:
• Deadline to submit proposals: May 14th, 2021
• Program Committee to notify selected authors by May 21st, 2021
• Speaker agreements and materials required from selected presenters by May 31st, 2021
We hope that you can join us and request that you disseminate this Call to other lists where it might be of interest.
ROW Program Committee
Stay tuned for further updates! Follow @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie?ref_src=twsrc%5Etfw>
ROW website: http://regiops.net<http://regiops.net/>
Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca>
ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com>
ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://www.icann.org/>, organized by Viagenie<http://viagenie.ca/>
(cross-posting to multiple lists - sorry for any duplicates)
Hi all,
We have our last remote session prior to RIPE 82 coming up on Wednesday, April 21st, and our session at RIPE 82 on Wednesday, May 21st.
We're currently seeking contributions for both of those. Presentations and suggestions for discussion topics are always welcome, recent operational experiences and observations are particularly encouraged.
Please send your ideas to the DNS WG Chairs at <dns-wg-chair(a)ripe.net>
You can find an archive of our previous sessions at https://www.ripe.net/participate/ripe/wg/active-wg/dns/remote-sessions
Thanks and kind regards,
dave
for the dns wg chairs
