On Oct 29, 2013, at 10:32 AM, Cong Liu <[email protected]> wrote: > 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".
I think the correct thing to say here is that lw4over6 is much simpler than MAP-E—the client doesn't need to do any math, and just takes the configuration from the server. > 1) MAP uses DHCPv6 as the provisioning mechanism. DHCPv6 is optional for > lw4over6, used for stateless provisioning (static mode) How does the lw4over6 client know it's stateless without a DHCPv6 option that tells it? If you mean that the absence of a DHCPv6 option configuring a static IP address/port set is what does it, then that solution still requires DHCPv6—it just doesn't require that specific option to be sent. The difference here is not that lw4over6 doesn't require DHCPv6, but that it additionally requires DHCPv4 for dynamic allocation, if dynamic allocation is used. I am sure that I am just restating what you already know, but I want to be sure that we don't start arguing about a point on which we don't actually disagree. _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
