[Hipsec] HIP Registration problem
"zfhu2001" <zfhu2001@163.com> Thu, 04 November 2010 09:48 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 6039F3A69D5 for <hipsec@core3.amsl.com>; Thu, 4 Nov 2010 02:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 nmntEkaUJUD6 for <hipsec@core3.amsl.com>; Thu, 4 Nov 2010 02:48:26 -0700 (PDT)
Received: from m50-132.163.com (m50-132.163.com [123.125.50.132]) by core3.amsl.com (Postfix) with ESMTP id C0EC43A692F for <hipsec@ietf.org>; Thu, 4 Nov 2010 02:48:25 -0700 (PDT)
Received: from ZFHU-BUTP (unknown [123.122.4.195]) by smtp2 (Coremail) with SMTP id DNGowKBr1IRwgdJMquXaAA--.191S2; Thu, 04 Nov 2010 17:48:34 +0800 (CST)
Date: Thu, 04 Nov 2010 17:48:25 +0800
From: zfhu2001 <zfhu2001@163.com>
To: hipsec <hipsec@ietf.org>
Message-ID: <201011041748233287181@163.com>
X-mailer: Foxmail 6, 15, 201, 23 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon215848251840_====="
X-CM-TRANSID: DNGowKBr1IRwgdJMquXaAA--.191S2
X-Coremail-Antispam: 1Uf129KBjvdXoWrXFyxXrWftFW7ZF1fKrWUtwb_yoWxXFc_u3 yvkryDta1kWr47Kr4xGF45WrWS9ayUKr1avw4Fqas3Cwn8Jr45Jry0qr9Ykw1Iy3WjgrZI yr1SvrZa9w13WjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7IU8j0PDUUUUU==
X-CM-SenderInfo: p2ik3jqqqrqiywtou0bp/1tbiOQJ-iUjh4v67rQAAsu
Cc: 胡博老师 <bj.hubo@gmail.com>, 杜文静 <lxadj@126.com>
Subject: [Hipsec] HIP Registration problem
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: Thu, 04 Nov 2010 09:48:29 -0000
Hi all,
As we know, a mobile node registers its HIP and IP address binding to a correponding RVS server, but now I'm wondering whether the MN will register to a new RVS if a mobile node moves to another network and simultaneously its previous RVS server does not work any more. Or does HIP provide a mechanisim as DAAP of MIP to detect the serving RVS server of its home area?
Thanks.
2010-11-04
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
- Re: [Hipsec] HIP Registration problem Andrew McGregor
- Re: [Hipsec] HIP Registration problem Miika Komu
- [Hipsec] HIP Registration problem zfhu2001
- Re: [Hipsec] HIP Registration problem Miika Komu
- Re: [Hipsec] HIP Registration problem Zhangfeng HU