Re: [Hipsec] [Hipsec-rg] About simultaneous mobility to HIP

[Varjonen Samu <samu.varjonen at helsinki.fi>]

Hi,

If both peers move at the same time, the update mechanism does not work
because both peers changed addresses at the same time and there is no
address that has been successfully connectivity tested. One way to solve
this is to use rendezvous server as a "home server".

http://infrahip.hiit.fi/hipl/manual/ch14s03.html

When both peers are mobile and the connectivity tests fail, peers should
try to find other peers RVS server and contact it through it. You could
also look RFC 5204 .

Cut-and-paste from RFC 5206 mobility and multihoming where this is
mentioned also

   There are a number of situations where the simple end-to-end
   readdressing functionality is not sufficient.  These include the
   initial reachability of a mobile host, location privacy, simultaneous
   mobility of both hosts, and some modes of NAT traversal.  In these
   situations, there is a need for some helper functionality in the
   network, such as a HIP rendezvous server [RFC5204].

BR
Samu Varjonen

John.zhao wrote:
> Hi,folks
> 
> 	After take a look about current docs located in hip wg and hip rg. I didn't find the document to describe how to resolve the simultaneous mobility problem aimed to hip. If anyone have some clues , hope can be shared. 
> 	If not,is it ok to start it?
> 	
> 
> 	Best Rgds,
> Thanks,
>  				
> 
> 	　　　　　　　　 John.zhao
> 　　	　	　　　　　john.zhao at huawei.com
> 　　　	　	　　　　　　2008-07-31
> _______________________________________________
> Hipsec-rg mailing list
> Hipsec-rg at listserv.cybertrust.com
> https://listserv.cybertrust.com/mailman/listinfo/hipsec-rg

_______________________________________________
Hipsec mailing list
Hipsec at ietf.org
https://www.ietf.org/mailman/listinfo/hipsec