Re: [MEXT] DSMIPv6 deregistration

[Hesham Soliman <hesham at elevatemobile.com>]

Sri,


> 
> I was referring to the IPv4 Home Address Option. Its is there in the
> BU. Specific question, if the mobile needs to include IPv4 HoA option
> for each of the currently assigned IPv4 home addresses or prefixes ?

=> Yes. 

  Also, I'm not sure if the
> format for re-registration messages is the same as the initial message,
> few lines will help. Or if it is there, if you can point me.

=> I don't think there is anything in the spec about that. The BU, as
defined in 3775 is always the same format, there is no distinction between
the format for initial and refresh AFAIK. We don't need to talk about that
because you only talk about something when you've deviated from the
well-known norm. Otherwise, we would have to repeat major sections of 3775.

Hesham

> 
> 
> 5.4: MN Operation:
> 
>     When sending a binding update from a visited network that supports
>     IPv6, the mobile node MUST follow the rules specified in [RFC3775].
>     In addition, if the mobile node has an IPv4 home address or needs
>     one, it MUST include the IPv4 home address option in the mobility
>     header.  If the mobile node already has a static IPv4 home address,
>     this address MUST be included in the IPv4 home address option.
>     Otherwise, if the mobile node needs a dynamic IPv4 address, it MUST
>     include the IPv4 0.0.0.0 address in the IPv4 home address option.
> 
> 
> Thanks
> Sri
> 
> 


_______________________________________________
MEXT mailing list
MEXT at ietf.org
https://www.ietf.org/mailman/listinfo/mext