[Hipsec-rg] About simultaneous mobility to HIP
john.zhao at huawei.com (John.zhao) Thu, 31 July 2008 13:06 UTC
From: "john.zhao at huawei.com"
Date: Thu, 31 Jul 2008 14:06:29 +0100
Subject: [Hipsec-rg] About simultaneous mobility to HIP
Message-ID: <0K4V00640GEWP1@szxml01-in.huawei.com>
See my comments inline. ======= 2008-07-31 14:03:00 You have said:======= > >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. [John.zhao]Agree. Currently , there are some much mature technolgoy can be used to review the resolution of this problem. But whatever is used, I mean among RVS,DHT or Hi3 etc, it seems that a fixed or respective fixed entity is need and the key to this case. So , it is similiar from this perspective. If that can be considered some harmonized and output one guideline as detail as possible for deployment? > >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 [John.zhao]Just checked with those historic version. All version said the specific solution is out of scope.Although all of them mention about it and also mention about RVS solution to it. > >Andrei > >| ======= 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
- [Hipsec-rg] About simultaneous mobility to HIP Henderson, Thomas R
- [Hipsec-rg] 回复 :Re: About simultaneous mobility t… Fabrice HOBAYA
- [Hipsec-rg] 回复 :Re: About simultaneous mobility t… xuxiaohu 41208
- [Hipsec-rg] About simultaneous mobility to HIP John.zhao
- [Hipsec-rg] About simultaneous mobility to HIP Andrei Gurtov
- [Hipsec-rg] About simultaneous mobility to HIP xuxiaohu 41208
- [Hipsec-rg] About simultaneous mobility to HIP Andrei Gurtov
- [Hipsec-rg] About simultaneous mobility to HIP Robert Moskowitz
- [Hipsec-rg] About simultaneous mobility to HIP John.zhao
- [Hipsec-rg] About simultaneous mobility to HIP Varjonen Samu
- [Hipsec-rg] About simultaneous mobility to HIP Andrew McGregor
- [Hipsec-rg] About simultaneous mobility to HIP John.zhao