[Hipsec-rg] About simultaneous mobility to HIP

[gurtov at cs.helsinki.fi (Andrei Gurtov)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi all,

I've commented to John in private that the use of DHT or Hi3 (or even
fast enough DynDNS) could help in simultaneous mobility.

If I recall right, earlier revisions of rvs or mm drafts used to have
extensive flow charts for various mobility scenarios but were removed
later for simplicity/lack of interest. Might be useful to check history
at http://tools.ietf.org/html/draft-ietf-hip-mm-00

Andrei

John.zhao wrote:
| Hi,Andrew
|
| 	See my comments inline.
|
| 	Best Rgds,
| Thanks
|
| John.zhao
| ======= 2008-07-31 21:46:00 You have said:=======
|
|> This is what the concept of a Rendezvous Server is intended to solve.
|> The (perhaps undocumented) idea is that a host should maintain
|> connectivity to one such that is unlikely to move, and to advertise
|> its locator as a potential rendezvous point.
| [John.zhao] Agree from my opinion. But is it ok? And how about the
detail chart flow? Is it should be and can be standarded as a doc at
now? After all , without a document, something is uncertain.
|> Andrew
|>
|> On 31/07/2008, at 9:32 PM, 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiRnAgACgkQP7jp0uceFkSAIgCeNh5js5G6JXtuTKamWQlFqjOo
9J0AoJoZJJfnndafU9K890pmtrPiiPO0
=VnUk
-----END PGP SIGNATURE-----