Browse Prior Art Database

Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) (RFC5202)

IP.com Disclosure Number: IPCOM000169509D
Original Publication Date: 2008-Apr-01
Included in the Prior Art Database: 2008-Apr-19
Document File: 31 page(s) / 68K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Jokela: AUTHOR [+3]

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group                                          P. Jokela Request for Comments: 5202                  Ericsson Research NomadicLab Category: Experimental                                      R. Moskowitz                                                                 ICSAlabs                                                              P. Nikander                                             Ericsson Research NomadicLab                                                               April 2008

 Using the Encapsulating Security Payload (ESP) Transport Format with the                       Host Identity Protocol (HIP)

Status of This Memo

   This memo defines an Experimental Protocol for the Internet    community.  It does not specify an Internet standard of any kind.    Discussion and suggestions for improvement are requested.    Distribution of this memo is unlimited.

IESG Note

   The following issues describe IESG concerns about this document.  The    IESG expects that these issues will be addressed when future versions    of HIP are designed.

   In case of complex Security Policy Databases (SPDs) and the co-    existence of HIP and security-related protocols such as IKE,    implementors may encounter conditions that are unspecified in these    documents.  For example, when the SPD defines an IP address subnet to    be protected and a HIP host is residing in that IP address area,    there is a possibility that the communication is encrypted multiple    times.  Readers are advised to pay special attention when running HIP    with complex SPD settings.  Future specifications should clearly    define when multiple encryption is intended, and when it should be    avoided.

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

 Jokela, et al.                Experimental                      [Page 1]
 RFC 5202        Using the ESP Transport Format with HIP       April 2008

 Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

   2.  Conventions Used in This Document  . . . . . . . . . . . . . .  3

   3.  Using ESP with HIP . . . . . . . . . . . . . . . . . . . . . .  4

     3.1.  ESP Packet Format  . . . . . . . . . . . . . . . . . . . .  4

     3.2.  Conceptual ESP Packet Processing . . . . . . . . . . . . .  4

       3.2.1.  Semantics of t...