Host Identity Protocol Architecture
draft-ietf-hip-rfc4423-bis-20
Document | Type | Active Internet-Draft (hip WG) | ||
---|---|---|---|---|
Authors | Robert Moskowitz , Miika Komu | |||
Last updated | 2019-07-08 (latest revision 2019-02-14) | |||
Stream | IETF | |||
Intended RFC status | Informational | |||
Formats | plain text xml pdf htmlized (tools) htmlized bibtex | |||
Reviews | ||||
Stream | WG state | Submitted to IESG for Publication | ||
Document shepherd | Gonzalo Camarillo | |||
Shepherd write-up | Show (last changed 2018-02-08) | |||
IESG | IESG state | RFC Ed Queue | ||
Action Holders |
(None)
|
|||
Consensus Boilerplate | Yes | |||
Telechat date | ||||
Responsible AD | Éric Vyncke | |||
Send notices to | Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> | |||
IANA | IANA review state | IANA OK - No Actions Needed | ||
IANA action state | No IANA Actions | |||
RFC Editor | RFC Editor state | MISSREF | ||
Details |
Network Working Group R. Moskowitz, Ed. Internet-Draft HTT Consulting Obsoletes: 4423 (if approved) M. Komu Intended status: Informational Ericsson Expires: August 18, 2019 February 14, 2019 Host Identity Protocol Architecture draft-ietf-hip-rfc4423-bis-20 Abstract This memo describes the Host Identity (HI) namespace, that provides a cryptographic namespace to applications, and the associated protocol layer, the Host Identity Protocol, located between the internetworking and transport layers, that supports end-host mobility, multihoming and NAT traversal. Herein are presented the basics of the current namespaces, their strengths and weaknesses, and how a HI namespace will add completeness to them. The roles of the HI namespace in the protocols are defined. This document obsoletes RFC 4423 and addresses the concerns raised by the IESG, particularly that of crypto agility. The section on security considerations describe also measures against flooding attacks, usage of identities in access control lists, weaker types of identifiers and trust on first use. This document incorporates lessons learned from the implementations of RFC 5201 and goes further to explain how HIP works as a secure signaling channel. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on August 18, 2019. Moskowitz & Komu Expires August 18, 2019 [Page 1] Internet-Draft Host Identity Protocol Architecture February 2019 Copyright Notice Copyright (c) 2019 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. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Terms common to other documents . . . . . . . . . . . . . . 4 2.2. Terms specific to this and other HIP documents . . . . . . 5 3. Background . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.1. A desire for a namespace for computing platforms . . . . . 8 4. Host Identity namespace . . . . . . . . . . . . . . . . . . . 9 4.1. Host Identifiers . . . . . . . . . . . . . . . . . . . . . 10 4.2. Host Identity Hash (HIH) . . . . . . . . . . . . . . . . . 11 4.3. Host Identity Tag (HIT) . . . . . . . . . . . . . . . . . . 11 4.4. Local Scope Identifier (LSI) . . . . . . . . . . . . . . . 12 4.5. Storing Host Identifiers in directories . . . . . . . . . . 13 5. New stack architecture . . . . . . . . . . . . . . . . . . . 14 5.1. On the multiplicity of identities . . . . . . . . . . . . . 15 6. Control plane . . . . . . . . . . . . . . . . . . . . . . . . 16 6.1. Base exchange . . . . . . . . . . . . . . . . . . . . . . . 16 6.2. End-host mobility and multi-homing . . . . . . . . . . . . 17Show full document text