Dear *, I've read this document and think it provides a good method by using AAA-server and radius to store and provision v6-prefix in IPv6 multicast scenario. Some comments on this draft:
Section 1: * The name of new DHCPv6 option has turned into 'OPTION_V6_PREFIX64' in the latest [I-D.ietf-softwire-multicast-prefix-option]. Section 3: * What does it mean by 'based on the sending client'? * If mB4 using DHCPv6 Solicit just for lease query, instead of IP address, the access request will always be send to AAA-server? AAA-server receives any access request from NAS will always be send Multicast-Prefixes-64 attribute back to NAS? * In Lightweight 4over6 scenario, lwB4 ([I-D.ietf-softwire-lw4over6]) as the client of DHCPv6 and DCHPv4o6 to request it's IPv6 & IPv4 address respectively. How the AAA-server to mantain the binding relationships with these two DHCP servers which as the part of NAS. Section 4.1: * The priority of Multicast-Prefixes-64 in Access-Accept message is higher than pre-provisioned? Best Regards, Hao Wang Hao Wang，[email protected] 2014/9/24
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
