Re-, As the situation is now much more clearer for the static/deterministic mapping, let us focus on the dynamic allocation case.
What would prevent a dhcpv6 server to manipulate IPv4 addresses + port range as IPv4-mapped IPv6 prefixes for instance? Cheers, Med >-----Message d'origine----- >De : Ted Lemon [mailto:[email protected]] >Envoyé : lundi 15 avril 2013 16:52 >À : BOUCADAIR Mohamed OLNC/OLN >Cc : Qi Sun; [email protected]; Softwires ([email protected]) >Objet : Re: [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6 > >On Apr 15, 2013, at 10:47 AM, [email protected] wrote: >> Does the same conclusion applies also for lw-4over6? (I'm naively >assuming, given the approach defined in draft-ietf-softwire-unified-cpe, >the same dhcpv6 to configure MAP will also be used lw-4over6) > >I think if you're using a purely deterministic mapping, you can do lw4over6 >with just the DHCPv6 option. For deployments where dynamic allocation is >desired, then you need DHCPv4-over-DHCPv6. _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
