[Hipsec] Simultaneous end-host mobility & High availability for RVS servers(mechanism of backup RVS)
"HU Zhangfeng" <zfhu2001@163.com> Sun, 30 May 2010 09:06 UTC
Return-Path: <zfhu2001@163.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B590D3A67B5 for <hipsec@core3.amsl.com>; Sun, 30 May 2010 02:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.877
X-Spam-Level: ***
X-Spam-Status: No, score=3.877 tagged_above=-999 required=5 tests=[AWL=0.876, BAYES_95=3, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tLMAIq39KDfa for <hipsec@core3.amsl.com>; Sun, 30 May 2010 02:06:31 -0700 (PDT)
Received: from m50-134.163.com (m50-134.163.com [123.125.50.134]) by core3.amsl.com (Postfix) with ESMTP id DE4213A635F for <hipsec@ietf.org>; Sun, 30 May 2010 02:06:29 -0700 (PDT)
Received: from zfhu (unknown [123.119.252.69]) by smtp4 (Coremail) with SMTP id DtGowLALNpeEKgJMhBtLAA--.11781S2; Sun, 30 May 2010 17:06:13 +0800 (CST)
Date: Sun, 30 May 2010 17:06:11 +0800
From: HU Zhangfeng <zfhu2001@163.com>
To: hipsec <hipsec@ietf.org>
Message-ID: <201005301706108432645@163.com>
X-mailer: Foxmail 6, 15, 201, 22 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon006167416721_====="
X-CM-TRANSID: DtGowLALNpeEKgJMhBtLAA--.11781S2
X-Coremail-Antispam: 1Uf129KBjvdXoWrtF1rCw1UtFyxJry7Xw47Arb_yoWDGrb_u3 srGryjq3yxKw1Svr4xArWUZryxWay7Wr15X3y0v3W5Ga4ktw4DGrZ0gasxua4fJa1a9rZx Crn8Xw42vr13WjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7IUUCeHPUUUUU==
X-CM-SenderInfo: p2ik3jqqqrqiywtou0bp/1tbiJhjgiUCpiazT2QABsQ
Subject: [Hipsec] Simultaneous end-host mobility & High availability for RVS servers(mechanism of backup RVS)
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 May 2010 09:06:31 -0000
hi all, As you know, 1) the scenario of simultaneous end-host mobility maybe actually exist in real world, while it still has not been specified in HIP. 2) RVS servers in HIP functioning as HAs in MIP play very important roles for the management of mobile nodes. If a RVS server stops working, then all the mobile nodes managed by it should be lost in the network and cannot be re-managed any more before the mobile nodes re-register to a new RVS server. So a mechanism of backup RVS should be proposed to solve this problem. I'm considering doing some work on both or either of the two above-mentioned topics, and I'm wondering if some ones have completed some work or got some achievement on both of them. Thank you. 2010-05-30 Zhangfeng HU, phD candidate of Broadband Network Research Center, State Key Laboratory of Networking and Switching Technology, Beijing University of Posts and Telecommunications, Beijing, China Email:zfhu2001@gmail.com Tel:86+13811892137
- [Hipsec] Simultaneous end-host mobility & High av… HU Zhangfeng
- Re: [Hipsec] Simultaneous end-host mobility & Hig… Fabrice HOBAYA