Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)
draft-ietf-hip-rfc5202-bis-04

The information below is for an old version of the document
Document Type Active Internet-Draft (hip WG)
Last updated 2013-09-05
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          P. Jokela
Internet-Draft                              Ericsson Research NomadicLab
Obsoletes: 5202 (if approved)                               R. Moskowitz
Intended status: Standards Track                ICSAlabs, An Independent
Expires: March 8, 2014                      Division of Verizon Business
                                                                 Systems
                                                                J. Melen
                                            Ericsson Research NomadicLab
                                                       September 4, 2013

Using the Encapsulating Security Payload (ESP) Transport Format with the
                      Host Identity Protocol (HIP)
                     draft-ietf-hip-rfc5202-bis-04

Abstract

   This memo specifies an Encapsulated Security Payload (ESP) based
   mechanism for transmission of user data packets, to be used with the
   Host Identity Protocol (HIP).  This document obsoletes RFC 5202.

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 March 8, 2014.

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

Jokela, et al.            Expires March 8, 2014                 [Page 1]
Internet-Draft   Using the ESP Transport Format with HIP  September 2013

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Conventions Used in This Document  . . . . . . . . . . . . . .  4
   3.  Using ESP with HIP . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  ESP Packet Format  . . . . . . . . . . . . . . . . . . . .  5
     3.2.  Conceptual ESP Packet Processing . . . . . . . . . . . . .  5
       3.2.1.  Semantics of the Security Parameter Index (SPI)  . . .  6
     3.3.  Security Association Establishment and Maintenance . . . .  7
       3.3.1.  ESP Security Associations  . . . . . . . . . . . . . .  7
       3.3.2.  Rekeying . . . . . . . . . . . . . . . . . . . . . . .  7
       3.3.3.  Security Association Management  . . . . . . . . . . .  8
       3.3.4.  Security Parameter Index (SPI) . . . . . . . . . . . .  8
       3.3.5.  Supported Ciphers  . . . . . . . . . . . . . . . . . .  9
       3.3.6.  Sequence Number  . . . . . . . . . . . . . . . . . . .  9
       3.3.7.  Lifetimes and Timers . . . . . . . . . . . . . . . . .  9
     3.4.  IPsec and HIP ESP Implementation Considerations  . . . . .  9
       3.4.1.  Data Packet Processing Considerations  . . . . . . . . 10
       3.4.2.  HIP Signaling Packet Considerations  . . . . . . . . . 10
   4.  The Protocol . . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.1.  ESP in HIP . . . . . . . . . . . . . . . . . . . . . . . . 11
       4.1.1.  IPsec ESP Transport Format Type  . . . . . . . . . . . 11
       4.1.2.  Setting Up an ESP Security Association . . . . . . . . 11
       4.1.3.  Updating an Existing ESP SA  . . . . . . . . . . . . . 12
   5.  Parameter and Packet Formats . . . . . . . . . . . . . . . . . 13
     5.1.  New Parameters . . . . . . . . . . . . . . . . . . . . . . 13
       5.1.1.  ESP_INFO . . . . . . . . . . . . . . . . . . . . . . . 13
       5.1.2.  ESP_TRANSFORM  . . . . . . . . . . . . . . . . . . . . 15
       5.1.3.  NOTIFICATION Parameter . . . . . . . . . . . . . . . . 16
     5.2.  HIP ESP Security Association Setup . . . . . . . . . . . . 16
       5.2.1.  Setup During Base Exchange . . . . . . . . . . . . . . 16
     5.3.  HIP ESP Rekeying . . . . . . . . . . . . . . . . . . . . . 18
       5.3.1.  Initializing Rekeying  . . . . . . . . . . . . . . . . 18
       5.3.2.  Responding to the Rekeying Initialization  . . . . . . 19
     5.4.  ICMP Messages  . . . . . . . . . . . . . . . . . . . . . . 19
Show full document text