> Oh, my. > > In that case, please clarify whether prefixes assigned from non-zero > policy prefixes should be treated specially, by HNCP, by the routing > protocol, or by RA/DHCP. (E.g. do I just serve such a prefix normally > over DHCPv4? Do I tag it somehow in the routing protocol? Do I serve the > associated DHCP options normally, say DNS servers?) > > Steven, I'd really be grateful for a usage scenario. There is the section "Special Purpose Prefixes" (now renamed to "Prefix Policy") which specifies extra behavior. In general (unless noted there) you do not treat them differently than other prefixes.
Just serve them via RA/DHCPv6 as usual if they are assigned. Also HNCP does not specify routing protocol behavior so that's out of scope. At some point when mif-wg has finalized their work on special RA or DHCPv6 options, clients will be able to identify and interpret them based on the TBD options that HNCP just passes through, until then its basic SAS. IPv4 / DHCPv4 only allows a single prefix, so it doesn't really apply there anyway. Example usecases for Prefix Policy (autonomous and manual): 1. You have a (company?) VPN router and only want to be able to reach the VPN from a certain link, e.g. only in your home office. 2. You are an IOT-device manufacturer and want to form a single prefix / "IOT-network" if a user has multiple of your IOT-gateways (and with that even discover there is a second one already). 3. You are an ISP and have a special purpose uplink or vlan (e.g. for IPTV) and only want to assign prefixes from these to your HNCP-Enabled STPs that can really use them, but you want the user to be able to place these boxes anywhere in the network. Maybe it would be worth adding 1 or 2 of them to the draft as well. Cheers, Steven _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
