Juliusz, >>> Requires host changes. Out of scope. > >> This is *complete* bs. > > While I would have expressed it in somewhat milder terms, I tend to agree > with Michael. If HNCP gets massively deployed together with a naming > protocol that is easy to implement, the host implementations will come in > due time.
The homenet architecture and / or charter say that for this WG host changes are to be minimized and in some areas completely out of scope. Furthermore, as Markus noted, the IETF has MDNS and stateful DHCPv6 (or rather RFC 4704) in standards track and these protocols are widely supported by all kinds of clients already. Bottom line: I'm not sure what problem you and Michael are claiming needs to be solved here or could be addressed by HNCP, us or the working group in some way. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
