Storing Host Locators in HIP
Resource RecordHelsinki Institute for Information TechnologyHIIT, PO Box 9800TKKFIN-02015Finlandoleg.ponomarev@hiit.fi
Host Identity Protocol
Host Identity ProtocolThere is a resource record (RR) in the Domain Name System
(DNS) used for the Host Identity Protocol (HIP). This document proposes
to store the host locators in the HIP resource records as well.The HIP RR allows a node to store its Host Identity (HI, the public
component of the node public-private key pair), Host Identity Tag (HIT,
a truncated hash of its public key), and the Domain Names of its
rendezvous servers (RVSs) in the DNS . The host
may have a set of IP address(es) in A and AAAA
RR sets (RRSets ).However there is no mechanism to specify custom UDP port for incoming
UDP-encapsulated HIP control packets without using a third party as a
rendezvous server (RVS). Furthermore separate
queries for the set of IP address cause extra delays and additional load
to the nameservers. The situation can be changed by listing locators in
HIP RR. The format of extended LOCATOR parameter may be used.The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.Let us reuse the existing format , but allow locators as well.The HIT length, PK algorithm, PK length, HIT, and Public Key fields are the same as in RFC5205, but the Public Key
is OPTIONAL. This change may reduce the length of the record and thus the memory required for a huge (e.g. billions) number of HIP
records. Also it would allow greater number of HIP RRs in a single 512-byte UDP packet.Various locators MAY be listed in the field using LOCATOR parameter format as in Section 5.7. of
draft-ietf-hip-nat-traversal-08 in addition to wire-encoded domain names of
rendezvous server(s).This section will be added later on.This section will be added later on.