Cong, > I have some concerns about current map-dhcp-05 document. From my > understanding, this draft has been changed to "softwire-dhcp", to cover all > DHCPv6-related provisioning for softwire mechanisms. But I'm confused with > the descriptions about lw4o6 and the provisioning. > > In order to improve the document and push map, lw4o6 and softwire-dhcp > further, I think there should be some updates on it. Here are the > issues/suggestions: > > 0) MAP & lw4o6 are parallel solutions, rather than lw4o6 is a subset of MAP. > Softwire-dhcp should claim this, and remove "Lightweight 4over6 is a strict > subset of MAP-E". > 1) MAP uses DHCPv6 as the provisioning mechanism. DHCPv6 is optional for > lw4over6, used for stateless provisioning (static mode) > 2) Dynamic IPv4 address assignment uses DHCPv4-over-DHCPv6 (IMHO it's the > default case of lw4o6). DHCPv4-over-DHCPv6 enable & server address options > can be put into containers, to enable the function. > 3) use DHCPv4-over-DHCPv6 to provision additional configuration information > for both lw4o6 & MAP. > 4) Softwire-dhcp should make a normative reference to DHCPv4-over-DHCPv6. > > I have also submitted two tickets to the tracker : #27 for the "subset" > issue, and #28 for DHCPv4-over-DHCPv6 issues. > > I'd like to ask the WG whether these should be considered.
MAP is incompatible with dynamic IPv4 address assignment using DHCPv4. either you can consider MAP DHCP as the building block used by a separate document describing the DHCPv4 address assignment case. or we can split out LW46 provisioning from MAP DHCP altogether. cheers, Ole
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
