Greetings again. Based on the technical input I received, I ripped out the first-guess mechanism and replaced it with one that will work with validating stub resolvers but still work with the same use cases.
It's clear some people here don't have the use cases listed in the draft; that's fine, lots of protocols don't apply to everyone. I do still believe that the folks who spoke up saying that they want their browsers to use DoH servers that are matched with the DNS-over-53 resolvers they chose, and this would allow that. --Paul Hoffman The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-hoffman-resolver-associated-doh/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-hoffman-resolver-associated-doh-01 https://datatracker.ietf.org/doc/html/draft-hoffman-resolver-associated-doh-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-hoffman-resolver-associated-doh-01 _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
