Ted Lemon <mel...@fugue.com> writes: >> Depending on the type of performance problem. If the performance problem >> is general, yes. If it is specific to DNS, there's no reason to not use >> the connection for other things; and the "send queries to all upstreams" >> solution will automatically converge to use the best-performing upstream. > > I think we are wandering off into nonsense territory here. Have you > observed this sort of problem in the field? If so, can you describe > what happened? If not, why would we optimize for it?
If you consider flaky ISP DNS servers to be "nonsense" you are clearly more fortunate with your ISPs than me. And that's before even going into the DNS censorship issue; in my part of the world ISP DNS servers are broken *by design*. >> Right, so if this is the case, how about we specify that routers MAY (or >> maybe even SHOULD) support MPvD-specific resolver addresses, and >> advertise the fact over HNCP. And that if a router receives such an >> announcement from another router it MUST announce the MPvD-specific >> resolver addresses over DHCP/RA. This way we ensure that *if* a router >> on the network implements MPvD it is going to work for the whole >> network; but routers can still opt to not implement the functionality >> itself if the implementer doesn't want to pay the implementation cost. > > Can you describe for us what this implementation cost is that you want > to avoid? Can you describe for us how multiplying the number of resolvers by N (or MxN if we follow your suggestion of running a full set of resolvers on every router) is *not* going to incur a significant implementation and debugability cost? -Toke _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
