I've just reread the current HNCP draft (version of 17 August, 10:51), and I have almost no nits. If anyone is interested, I've written up a few notes about shncpd's compliance on
http://www.pps.univ-paris-diderot.fr/~jch/software/homenet/shncpd.html This needs to be completed with DNCP and PA compliance, of course. Minor nits: Section 6.5: MUST NOT for ULA if global IPv6 available -- "in the absence of explicit user configuration"? Section 8: "HNCP routers providing name resolving services MUST resolve these names to their respective IP addresses as if there were corresponding A/AAAA records." This is not clear to me; what exactly should an HNCP node be doing? What "naming services" are being referred to? Does this apply to locally published names, or also to names discovered over HNCP? Section 11. "If the CE sends a size-hint as indicated in WPD-2, the hint MUST NOT be determined by the number of LAN-interfaces of the CE, but SHOULD instead be large enough to at least accommodate prefix assignments announced for existing delegated or ULA- prefixes, if such prefixes exist and unless explicitly configured otherwise." I have serious doubts about this recommendation, it feels like there's a feedback loop somewhere, I wouldn't swear it doesn't diverge really badly. What about simply looking at the number of links in the Homenet? _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
