Re: [homenet] Dynamically computed metrics in IS-IS are difficult

to solve, that's great. If not, it's better if we have a plan B already in progress. Can we take the first steps toward standardization even if homenet *hasn't* declared a preference yet? -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc

Re: [homenet] Babel specification quality [was: Dynamically computed metrics...]

, but I hate to see running code lose a fight to political inertia. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] draft-cheshire-homenet-dot-home-01

On Thu, Nov 13, 2014 at 09:05:16AM -0800, Michael Thomas wrote: Let's be clear that we aren't designing homenet for 7 year old cpe. Or even 0 year old cpe. That way lies madness. I think the point is if a 7-year-old CPE can do it, it's likely to be feasible on newer gear too. -- Evan Hunt

Re: [homenet] RFC: dhcpv4 to slaac DNS naming scheme

an educated guess at a usable v6 address for a host, confirm it, and act on it, either by sending a suitable DNS update or (for something like dnsmasq, which acts as both DHCP and DNS server) updating its own internal state. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc

Re: [homenet] Unicast DNS within the Homenet?

in lieu of anything better. Another +1. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] Unicast DNS within the Homenet?

it). But if we're going to be supplying DNS data from multiple sources -- DHCP, mDNS, maybe others -- then it might be a good idea to manage time limits on the demand side. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list

Re: [homenet] Unicast DNS within the Homenet?

resurrecting it. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] LQDN (was tunnels as way to disambiguate .local)

previously proposed for LQDN. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] tunnels as way to disambiguate .local

. In that context, we would like reachable devices to have names, and we would like devices that are reachable remotely to have names that are resolvable remotely. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet

Re: [homenet] tunnels as way to disambiguate .local

previous router. If I absolutely refuse to give my router a network name, then it could choose one for me, and in that event a ULA-style name seems like a good choice. But I would expect it to be a rare one. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc

Re: [homenet] tunnels as way to disambiguate .local

owning the fact that you have state, and you have to go to the trouble to get it right. Explain what you mean by state here please? I'm not sure I'm following you. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list

Re: [homenet] tunnels as way to disambiguate .local

), then in addition to the locally reachable name described in (1), the device MUST also answer to devicename.FQDN. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https://www.ietf.org

Re: [homenet] tunnels as way to disambiguate .local

-memorable, and ideally human-selected names. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] tunnels as way to disambiguate .local

. ...but I did not hear a clear consensus on this one. (For the record, though I'm open to being convinced otherwise, my current preference is for a reserved generic namespace such as .local and/or .sitelocal, and *not* for ULA-style domains.) -- Evan Hunt -- e...@isc.org Internet Systems Consortium

Re: [homenet] tunnels as way to disambiguate .local

to come up with a solution for geeks, why not come up with a _real_ solution, instead of the .local hack? I'd love to hear the plan. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https

Re: [homenet] Reverse DNS

and the secondary servers are authoritative for the externally visible view of the network; the router is solely authoritative for the internally visible view. I don't know of any reason this approach couldn't scale. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc

Re: [homenet] tunnels as way to disambiguate .local

not sure it came across.) -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] Name service design principles: a proposal

for everything else, and it would only bother with validation on the recursive answers. (That's how BIND 9 works, anyway; I'm not particularly knowledgable about other DNS software.) -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing

Re: [homenet] Name service design principles: a proposal

A local trust anchor is needed for the isolated network with more than one router. Agreed there. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet