On Wed, Apr 28, 2021 at 15:55, Stephane Bortzmeyer <bortzmeyer@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