HNCP is going to solve a lot of problems with border discovery, propagating ipv6 prefixes and other problems like that. It looks like it will break the logjam we've had for 2+ years in homenet with the incendiary "embed config info in routing protocol" vs "embed config in a separate protocol" debate.
Some code already exists for openwrt. I haven't had time to read the draft or code fully, but with the latent integration into opewrt's ubus system it seems probable we can replace AHCP in the long run. I love that HNCP uses the trickle protocol underlying. My only glancing comments were that the crypto architecture needs work, and it wasn't clear if /128s could be distributed and there is probably more configuration information that needs to be propagated across a homenet. Also I'd still like to see some ipv4 concerns (like local nat discovery) also addressed. Please make your comments on the homenet mailing list, not here. This is not slated for the upcoming cero stable release. See below for links. ---------- Forwarded message ---------- From: Markus Stenberg <[email protected]> Date: Wed, Feb 5, 2014 at 9:52 AM Subject: [homenet] Two new drafts (and third one 'soon') To: "[email protected] Group" <[email protected]> Cc: Markus Stenberg <[email protected]> Drafts: http://tools.ietf.org/html/draft-stenberg-homenet-hncp-00 http://tools.ietf.org/html/draft-stenberg-homenet-dnssd-hybrid-proxy-zeroconf-00 (Generic PA one in the works, but submitted also 'soon') Experimental partial implementation: https://github.com/sbyx/hnetd/ Discuss. Cheers, -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet -- Dave Täht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html _______________________________________________ Cerowrt-devel mailing list [email protected] https://lists.bufferbloat.net/listinfo/cerowrt-devel
