> - The architecture document > [draft-mglt-homenet-front-end-naming-delegation] in NOT CPE specific.
> - The DHCP Options document > [draft-mglt-homenet-naming-architecture-dhc-options] is currently CPE > specific. Ah, I see. That definitely needs to be clarified. > - a) Explicitly mention that the CPE is an example [...] > - b) Introduce a new designation like the Internet Homenet Authoritative > Server. [...] > Maybe b) is better. Definitely so. Replacing CPE with IHAS in the text will allow you to see more clearly where you've assumed that the CPE and IHAS are co-located. There's still something I don't understand. If I'm understanding Steve's and Markus' work correctly, HNCP performs prefix delegation to internal routers over HNCP, and the internal routers don't proxy stateful DHCPv6 to the CPE. How does your protocol work in the presence of multiple links? Or are you assuming that only nodes directly connected to the IHAS/CPE can be advertised over your protocol? Finally, what happens when there are multiple CPEs, which HNCP explicitly supports? Are you assuming that only one acts as IHAS? -- Juliusz _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
