Rajeev Koodli | 20 Jun 2006 03:12
Picon

Re: [Mobopts] Re: MIP and Upper Layer Protocol interaction


Hi,

the purpose here is to list the available options. Perhaps SHIM6 is
one option, but there are others to explore. I encourage you to
discuss them at the MobOpts meeting.

-Rajeev

ps: location privacy as such is being discussed in a problem statement
draft, and there is also a mobopts drfat on solutions. Please have a look
at them. Thanks.

Shinta Sugimoto wrote:

>Hi Rajeev,
>
>  
>
>If you need to maintain the sessions while changing the HoA
>from one to another, I think you need additional mechanism
>than plain MIPv6.  MIP (no matter IPv6 or IPv4) is designed
>to assure the reachability to a given HoA with the current
>location of the mobile node (CoA).  If the app wants
>to change HoAs for some reason (I assume that privacy is the
>main interest), there is a need to maintain the mapping of
>the identity and the locator of the mobile node.
>
>One option would be to run Shim6 over MIPv6.  Such usage has
>already been discussed in Shim6 WG.  By mobile node establishing
>Shim6 context with its HA/CN, it could utilize multiple HoAs
>without annoying upper layer protocols.  However, I am not sure
>if it fulfills your requirement especially in terms of privacy
>(hiding the identity, which is MN's HoA in this case).
>Would you see any problem with this approach ?  I see that
>signaling overhead may also be a concern (to run both Shim6
>and MIPv6).
>
>I have some additional questions:
>
>- If privacy is the main concern, would you think 
>http://www.ietf.org/internet-drafts/draft-dupont-mip6-privacyext-03.txt
>would help to solve your initial requirement ? If not, could
>you please tell me why ?
>- Do you assume that different HoAs that mobile node may
>request are derived from different home prefixes ? Or are you
>considering that the node generates HoAs from a single prefix
>with privacy extension ?
>
>
>Regards,
>Shinta
>  
>

Gmane