>> I think this is a mischaracterization of the debate, which actually >> started because of a third position that you don't mention: Mozilla's >> public statement that in the future they will force (or, at least, make as >> a default - clarification requests haven't solved the doubt yet) Firefox >> users to use a remote resolver chosen within a shortlist that they will >> manage. >> > > I'm not sure where you have attempted to clarify this point (I think we've > been clear on this point at > https://hacks.mozilla.org/2018/05/a-cartoon-intro-to-dns-over-https/)
Unfortunately this is not clear at all. The web page at the link above says: "We'd like to turn this on as the default for all of our users.". Combined with the remaining text on the web page, the only conclusions I can draw is that - Mozilla would like to turn on DoH by default, invisible to the user (the user gets this configuration without making a choice). - When DoH is turned on, by default Cloudflare will be used as the DoH provider. If these conclusions are correct they are precisely why some of us find the Mozilla/Firefox stance completely unacceptable. If these are *not* the conclusions we should draw about Firefox and Mozilla's plans, you badly need to update the web page on the link above. You could also at the same time clarify whether Firefox will use DoH resolvers that are on the same IP addresses as other non-DoH content. Steinar Haug, AS2116 _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
