Re: [Hipsec] HIP Registration problem

Miika Komu <mkomu@cs.hut.fi> Thu, 04 November 2010 10:47 UTC

Return-Path: <mkomu@cs.hut.fi>
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 CCA673A69D1 for <hipsec@core3.amsl.com>; Thu, 4 Nov 2010 03:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 WQGuZHvd6tPJ for <hipsec@core3.amsl.com>; Thu, 4 Nov 2010 03:47:32 -0700 (PDT)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id EEBE43A69B7 for <hipsec@ietf.org>; Thu, 4 Nov 2010 03:47:31 -0700 (PDT)
Received: from hutcs.cs.hut.fi ([130.233.192.10] helo=[127.0.0.1]) by mail.cs.hut.fi with esmtp (Exim 4.54) id 1PDxM3-0002IS-Uu for hipsec@ietf.org; Thu, 04 Nov 2010 12:47:40 +0200
Message-ID: <4CD28F4A.5070106@cs.hut.fi>
Date: Thu, 04 Nov 2010 12:47:38 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
To: hipsec@ietf.org
References: <201011041748233287181@163.com>
In-Reply-To: <201011041748233287181@163.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Subject: Re: [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 10:47:32 -0000

On 11/04/2010 11:48 AM, zfhu2001 wrote:
> 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

Hi,

there's no such thing as "home agent" or "home area" in HIP. This is one
of the differences to MIP. The same rendezvous server can be reused
independently of the current network using the UPDATE procedure.
Remember also that the rendezvous server forwards only the first I1 or
the first UPDATE packet, so it's still a light-weight operation even
though the latency be longer. The rendezvous server does not forward any
application payload.

Fault-tolerance for RVS may fall into the category of local policies
(?). Changing the "current" RVS requires also an update to the DNS
records. Another strategy could be just to publish multiple RVS servers
in the DNS and send packets to all of them (which ever happens to be alive).