On 9/18/19 3:12 PM, Ted Lemon wrote:
On Sep 18, 2019, at 6:07 PM, Michael Thomas <m...@mtcc.com
<mailto:m...@mtcc.com>> wrote:
So I'm a little unclear about the specifics of Firefox using DNS over
HTTP, but wouldn't this affect homenet naming, or any split horizon
kind of naming?
In order for DoH to not break lots of things, it has to be implemented
in such a way that special-use names are not resolved using a global
resolver, and that VPN-supported names are looked up using the VPN
resolver. It would also be nice if there were a way for the homenet
to signal that a public domain belonging to it is resolved locally, so
that split-horizon naming on the homenet works correctly. Similar
functionality will be required for corporate networks that do
split-horizon naming.
Yeah, that's pretty much what it seemed to me too. How vetted was this?
I mean, did it make the rounds in standards-ville, or is this roll your
own by Mozilla?
I also don't get what the motivation is, and/or problem it's trying to
solve. Seems pretty scary to have a single point of failure (Cloudflare)
introduced.
Mike
_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
