brian> But if the CE includes a little autonomic service agent (ASA) which brian> is in the ISP's security domain (not the SOHO domain), it can act for brian> HNCP to solicit address space from the ISP. That's the southern side brian> of the CASM model and the northern side of HNCP.
HNCP just doesn't care. HNCP has a notion of "External Connection", and an External Connection may provide one or more External Prefixes. HNCP will assign to each link in the HNCP one /64 from each External Prefix. HNCP doesn't care where these External Connection TLVs come from, but it is my understanding that there is WG consensus that DHCPv6-PD is the default mechanism. I don't think there's anything in any of our RFCs that would prevent an implementation from obtaining External Prefixes using a different protocol, e.g. manual configuration, a proprietary provisioning protocol or even algorithmically derived from an IPv4 address (as with 6rd). Both implementations of HNCP are easy to extend with a different mechanism for obtaining External Prefixes, should you wish to experiment. -- Juliusz _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
