[support] Re: [Dsmip] Implementation of UMIP and Dyanamic key estabilishment through IKEv2 in IPV4-only network

[Arnaud Ebalard]

Hi,

satya sahu <satya0675 at gmail.com> writes:

> *Solution B*
>
>           I was thinking of making the following code change in mip6d when
> MN move to FL(IPv4):
>
> 1.      Enhanced the behavior of KMADDRESS to support IPv4 address also. I
> have already verified that strongswan support KMADDRESS having IPv4 or IPv6
> addresses.
>
> 2.      Insert corresponding IPv4 xfrm policies and templates to the kernel.
> Which is missing currently. Current implementation push v6-mapped-v4 policy
> to the kernel when MN moves to FL(IPv4).
>
> Changes will be made when the new CoA address is v6-mapped-v4. The following
> functions may be affected to support the above requirement.
>
> Ø       _mn_trns_update
>
> Ø       _mn_tnl_update
>
> Ø       _mn_tnl_pol_mod
>
> Ø       xfrm_sendmigrate
>
> Ø       ...And some more to be identified...
>
> Kindly let me know if I am thinking on the right direction to fix the issue.
> I will appreciate if you can send me some more pointers which Solution I
> should go for.

Solution A looks like a workaround. Solution B is IMHO the way to
go. Regarding the list of function, it looks like a good start.

If you manage to implement and test your ideas, I'd be interested by some
feedback that could be integrated in:

http://tools.ietf.org/html/draft-ebalard-mext-pfkey-enhanced-migrate-00

Cheers,

a+

ps: you may find some material on http://natisbad.org/MIPv6/ and in the
    repo here: http://hg.natisbad.org/migrate2_patches_umip_nemo/