Thanks, this is the first time ive seen this RFC being mentioned. Thank you.
I was about to say +1 for adding this feature but to also to allow for custom dnscrypt installs (i.e support custom provider-key, provider-name and providor address) as a lot of us don't use OpenDNS or any other open public server(s). Some of us run our own dns inferstructure which we also have dnscrypt support.
However now that I know they are working on something, I will start investigating when bind/unbound etc will get this support (out of the box). Hopefully soon, meanwhile I would say that dnscrypt support would really help many of us to add to your existing products as a lot of customers use this and with the new laws recently announced, more and more will be jumping onto the boat to use encryption everywhere.
is the source(s) you need.
This is all you need (client wise), so if mikrotik had this support as in binary/package, it would solve our issues or we are forced to run additional hardware to support this in our networks i.e. rpi, nas etc assuming soho user here.
Thanks for the heads up btw.