Storing Host Locators in HIP Resource Record
draft-ponomarev-hip-dns-locators-00

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on January 7, 2010.

Copyright Notice

Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.

Abstract

There 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.

Table of Contents

1.  Introduction
2.  IANA Considerations
3.  Security Considerations
4.  Normative References
§  Author's Address

1.  Introduction

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 [RFC5205] (Nikander, P. and J. Laganier, “Host Identity Protocol (HIP) Domain Name System (DNS) Extensions,” April 2008.). The host may have a set of IP address(es) in A [RFC1035] (Mockapetris, P., “Domain names - implementation and specification,” November 1987.) and AAAA [RFC3596] (Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, “DNS Extensions to Support IP Version 6,” October 2003.) RR sets (RRSets [RFC2181] (Elz, R. and R. Bush, “Clarifications to the DNS Specification,” July 1997.)).

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)[RFC5204] (Laganier, J. and L. Eggert, “Host Identity Protocol (HIP) Rendezvous Extension,” April 2008.). 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 [I‑D.ietf‑hip‑nat‑traversal] (Komu, M., Henderson, T., Tschofenig, H., Melen, J., and A. Keraenen, “Basic HIP Extensions for Traversal of Network Address Translators,” June 2009.) 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[RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

2.  IANA Considerations

This section will be added later on.

3.  Security Considerations

This section will be added later on.

4. Normative References

Author's Address