[Hipsec] HIP-based anycast

Miika Komu <mkomu@cs.hut.fi> Tue, 27 November 2012 09:38 UTC

Message-ID: <50B48A1A.1080609@cs.hut.fi>
Date: Tue, 27 Nov 2012 11:38:34 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: hip WG <hipsec@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] HIP-based anycast
Precedence: list

Hi,

opportunistic mode with the help of a rendezvous server could be used 
for implementing HIP-based anycast. The current RVS specification does 
not allow this:

http://tools.ietf.org/html/draft-ietf-hip-rfc5204-bis-02

4.3.1. Processing Outgoing I1 Packets

    An initiator SHOULD NOT send an opportunistic I1 with a NULL
    destination HIT to an IP address that is known to be a rendezvous
    server address, unless it wants to establish a HIP association with
    the rendezvous server itself and does not know its HIT.

I think we could specify either a flag in the base exchange or 
alternatively a special HIT encoding for the "NULL" destination HIT in 
the I1. What do you think?

[Hipsec] HIP-based anycast Miika Komu
Re: [Hipsec] HIP-based anycast Julien Laganier
Re: [Hipsec] HIP-based anycast Miika Komu
Re: [Hipsec] HIP-based anycast Julien Laganier
Re: [Hipsec] HIP-based anycast Miika Komu