Host Identity Protocol (HIP) Domain Name System (DNS) Extension
RFC 8005
| Document | Type |
RFC - Proposed Standard
(October 2016; No errata)
Obsoletes RFC 5205
|
|
|---|---|---|---|
| Author | Julien Laganier | ||
| Last updated | 2016-10-14 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Gonzalo Camarillo | ||
| Shepherd write-up | Show (last changed 2015-11-08) | ||
| IESG | IESG state | RFC 8005 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Terry Manderson | ||
| Send notices to | "Gonzalo Camarillo" <gonzalo.camarillo@ericsson.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) J. Laganier
Request for Comments: 8005 Luminate Wireless, Inc.
Obsoletes: 5205 October 2016
Category: Standards Track
ISSN: 2070-1721
Host Identity Protocol (HIP) Domain Name System (DNS) Extension
Abstract
This document specifies a resource record (RR) for the Domain Name
System (DNS) and how to use it with the Host Identity Protocol (HIP).
This RR allows a HIP node to store in the DNS its Host Identity (HI),
the public component of the node public-private key pair; its Host
Identity Tag (HIT), a truncated hash of its public key (PK); and the
domain names of its rendezvous servers (RVSs). This document
obsoletes RFC 5205.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8005.
Copyright Notice
Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Laganier Standards Track [Page 1]
RFC 8005 HIP DNS Extension October 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Usage Scenarios . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Simple Static Single-Homed End Host . . . . . . . . . . . 5
3.2. Mobile End Host . . . . . . . . . . . . . . . . . . . . . 6
4. Overview of Using the DNS with HIP . . . . . . . . . . . . . 7
4.1. Storing HI, HIT, and RVS in the DNS . . . . . . . . . . . 7
4.2. Initiating Connections Based on DNS Names . . . . . . . . 8
5. HIP RR Storage Format . . . . . . . . . . . . . . . . . . . . 9
5.1. HIT Length Format . . . . . . . . . . . . . . . . . . . . 9
5.2. PK Algorithm Format . . . . . . . . . . . . . . . . . . . 9
5.3. PK Length Format . . . . . . . . . . . . . . . . . . . . 10
5.4. HIT Format . . . . . . . . . . . . . . . . . . . . . . . 10
5.5. Public Key Format . . . . . . . . . . . . . . . . . . . . 10
5.6. Rendezvous Servers Format . . . . . . . . . . . . . . . . 10
6. HIP RR Presentation Format . . . . . . . . . . . . . . . . . 11
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8.1. Attacker Tampering with an Insecure HIP RR . . . . . . . 13
8.2. Hash and HITs Collisions . . . . . . . . . . . . . . . . 13
8.3. DNSSEC . . . . . . . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Changes from RFC 5205 . . . . . . . . . . . . . . . 17
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 17
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction
This document specifies a resource record (RR) for the Domain Name
System (DNS) [RFC1034] and how to use it with the Host Identity
Protocol (HIP) [RFC7401]. This RR allows a HIP node to store in the
DNS its Host Identity (HI), the public component of the node public-
private key pair; its Host Identity Tag (HIT), a truncated hash of
its HI; and the domain names of its rendezvous servers (RVSs)
[RFC8004].
Currently, most of the Internet applications that need to communicate
with a remote host first translate a domain name (often obtained via
user input) into one or more IP addresses. This step occurs prior to
Show full document text