On 03/13/2013 11:20 AM, Tim Chown wrote:
More speculation about dnydns without any motivation for why it's interesting
and/or significant.
There seems to be no mention of the relationship between local/home resolvers
if the local resolver isn't the authoritative resolver. In particular, it's not
an
unusual situation to have a "cloud" (read: high bandwidth, well connected...)
authoritative dns be a slave to a local master. Or if you don't like that, some
other way to achieve similar goals of not wanting my home network have to
know how to deal with ddos's on nameservers, as one for-instance.
I think that's not precluded. The key bit is the homenet must be able to
operate if disconnected.
[i'm not a namedropper, so pardon me if I screw up nomenclature]
I don't think we should be adopting requirements unless they are really
"hard" requirements. Disconnected use within a homenet seems more
aspirational than hard -- there are just so many things that will puke if
the net is down, that I don't think we should worry about it.
That said, there seems to be an assumption that the CER would be the
logical place to house a repository. I don't recall seeing any discussion
about whether it would be what the root resolvers points to. If it is,
we definitely have to think about bandwidth, DoS, etc, etc. If it's not
the preferred means (which i don't really think it is because if nothing
else, you need failover resolvers), I think we need to flesh this out a bit
more to say that, so that we can take inventory of whether the CER could
reasonably master for a cloud-based slave. Or something else... I'm not
wedded to a solution, just want to see more clarity about the problem
space.
Mike
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
