Re: [Softwires] [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6

[<[e-mail]>]

Hi Med,

It would still work for lw-4o6 and the unified CPE. All of the basic
params for configuring lw4o6/MAP1:1 can be provisioned through the
OPTION_MAP_BIND that is proposed in the unified CPE draft over DHCPv6.
Additional DHCPv4 only options would be done via the DHCPv4oDHCPv6 method
for both lw4o6 and MAP-E.

We still need to agree on which option will be used for provisioning the
address of the lwAFTR/MAP BR, however. There was some discussion on this
on the SW ML last week, but no conclusion reached.


Cheers,
Ian

On 15/04/2013 16:47, "[e-mail]"
<[e-mail]> wrote:

>Re-,
>
>Thanks for clarifying Ted. I must admit this is not what I understood
>when I read draft-scskf-*.
>
>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)
>
>Cheers,
>Med
>
>>-----Message d'origine-----
>>De : Ted Lemon [mailto:[e-mail]]
>>Envoyé : lundi 15 avril 2013 16:39
>>À : BOUCADAIR Mohamed OLNC/OLN
>>Cc : Qi Sun; [e-mail]; Softwires ([e-mail])
>>Objet : Re: [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6
>>
>>On Apr 15, 2013, at 10:27 AM, <[e-mail]> wrote:
>>> Are you saying MAP is not a concerned with this draft and dhcpv6 can be
>>used for MAP?
>>
>>For configuring the MAP-E prefix and port set, yes.   That was the
>>discussion we had in Softwires in Orlando: cover the easy stuff with
>>DHCPv6
>>(this is the existing DHCPv6 MAP option), and then if someone needs
>>legacy
>>IPv4 services or stateful address allocation, do it with DHCPv4-over-
>>DHCPv6.
>
>_______________________________________________
>Softwires mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/softwires