[dns-resolver-tf] Final final draft of RIPE DNS Resolver Best Common Practices

hi Shane,

On Sun Mar 24, 2024 at 17:25 CET, Shane Kerr wrote:
> Thank you for your suggestions, edits, and discussion. I've updated 
> the final draft to give us a final, final draft. 😉
>
> I've included the last (?) version at the bottom of this e-mail, and 
> responded to your suggestions inline below.

Thanks, including for your perseverance when Spamhaus ate your homework 
;-) Only one comment; in regards to this change:

>    2. its framework on a Recursive operator Privacy Statement, by
>    publishing a privacy statement on their website covers all topics in
>    Section 6. (See for example
>    [Cloudflare's 
> statement](https://developers.cloudflare.com/1.1.1.1/privacy/public-dns-resolver)
>    or [Quad9's privacy page](https://www.quad9.net/service/privacy/).)

By citing examples in this context, a reader may infer that they meet 
this recommendation (ie.  cover all topics in Section 6), which may or 
may not be true now and in the future.

Checking now:
Quad9's current privacy policy explicitly states it intends to meet or 
exceed the RFC, which makes it a good example at present. Cloudflare's 
does not.

kind regards, Maarten