Host Identity Protocol Version 2 (HIPv2)
draft-ietf-hip-rfc5201-bis-11

Network Working Group                                  R. Moskowitz, Ed.
Internet-Draft                                                   Verizon
Obsoletes: 5201 (if approved)                                    T. Heer
Intended status: Standards Track               Hirschmann Automation and
Expires: August 29, 2013                                         Control
                                                               P. Jokela
                                            Ericsson Research NomadicLab
                                                            T. Henderson
                                                      The Boeing Company
                                                       February 25, 2013

                Host Identity Protocol Version 2 (HIPv2)
                     draft-ietf-hip-rfc5201-bis-11

Abstract

   This document specifies the details of the Host Identity Protocol
   (HIP).  HIP allows consenting hosts to securely establish and
   maintain shared IP-layer state, allowing separation of the identifier
   and locator roles of IP addresses, thereby enabling continuity of
   communications across IP address changes.  HIP is based on a SIGMA-
   compliant Diffie-Hellman key exchange, using public key identifiers
   from a new Host Identity namespace for mutual peer authentication.
   The protocol is designed to be resistant to denial-of-service (DoS)
   and man-in-the-middle (MitM) attacks.  When used together with
   another suitable security protocol, such as the Encapsulated Security
   Payload (ESP), it provides integrity protection and optional
   encryption for upper-layer protocols, such as TCP and UDP.

   This document obsoletes RFC 5201 and addresses the concerns raised by
   the IESG, particularly that of crypto agility.  It also incorporates
   lessons learned from the implementations of RFC 5201.

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

Moskowitz, et al.        Expires August 29, 2013                [Page 1]
Internet-Draft                    HIPv2                    February 2013

   This Internet-Draft will expire on August 29, 2013.

Copyright Notice

   Copyright (c) 2013 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  . . . . . . . . . . . . . . . . . . . . . . . .   6
     1.1.   A New Namespace and Identifiers  . . . . . . . . . . . .   7
     1.2.   The HIP Base Exchange (BEX)  . . . . . . . . . . . . . .   7
     1.3.   Memo Structure . . . . . . . . . . . . . . . . . . . . .   8
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   8
     2.1.   Requirements Terminology . . . . . . . . . . . . . . . .   8
     2.2.   Notation . . . . . . . . . . . . . . . . . . . . . . . .   8
     2.3.   Definitions  . . . . . . . . . . . . . . . . . . . . . .   9
   3.  Host Identity (HI) and its Structure  . . . . . . . . . . . .  10
     3.1.   Host Identity Tag (HIT)  . . . . . . . . . . . . . . . .  11