Browse Prior Art Database

Using the Host Identity Protocol with Legacy Applications (RFC5338)

IP.com Disclosure Number: IPCOM000174721D
Original Publication Date: 2008-Sep-01
Included in the Prior Art Database: 2008-Sep-19
Document File: 15 page(s) / 35K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Henderson: AUTHOR [+3]

Abstract

This document is an informative overview of how legacy applications can be made to work with the Host Identity Protocol (HIP). HIP proposes to add a cryptographic name space for network stack names. From an application viewpoint, HIP-enabled systems support a new address family of host identifiers, but it may be a long time until such HIP-aware applications are widely deployed even if host systems are upgraded. This informational document discusses implementation and Application Programming Interface (API) issues relating to using HIP in situations in which the system is HIP-aware but the applications are not, and is intended to aid implementors and early adopters in thinking about and locally solving systems issues regarding the incremental deployment of HIP.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Network Working Group                                       T. Henderson Request for Comments: 5338                            The Boeing Company Category: Informational                                      P. Nikander                                             Ericsson Research NomadicLab                                                                  M. Komu                            Helsinki Institute for Information Technology                                                           September 2008

        Using the Host Identity Protocol with Legacy Applications

Status of This Memo

   This memo provides information for the Internet community.  It does    not specify an Internet standard of any kind.  Distribution of this    memo is unlimited.

Abstract

   This document is an informative overview of how legacy applications    can be made to work with the Host Identity Protocol (HIP).  HIP    proposes to add a cryptographic name space for network stack names.    From an application viewpoint, HIP-enabled systems support a new    address family of host identifiers, but it may be a long time until    such HIP-aware applications are widely deployed even if host systems    are upgraded.  This informational document discusses implementation    and Application Programming Interface (API) issues relating to using    HIP in situations in which the system is HIP-aware but the    applications are not, and is intended to aid implementors and early    adopters in thinking about and locally solving systems issues    regarding the incremental deployment of HIP.

 Henderson, et al.            Informational                      [Page 1]
 RFC 5338           Using HIP with Legacy Applications     September 2008

 Table of Contents

   1. Introduction ....................................................2

   2. Terminology .....................................................3

   3. Enabling HIP Transparently within the System ....................4

      3.1. Applying HIP to Cases in Which IP Addresses Are Used .......4

      3.2. Interposing a HIP-Aware Agent in the DNS Resolution ........6

      3.3. Discussion .................................................7

   4. Users Invoking HIP with a Legacy Application ....................8

      4.1. Connecting to a HIT or LSI .................................8

      4.2. Using a Modified DNS Name ..................................9

      4.3. Other Techniques ...........................................9

   5. Local Address Management ....