Using the Host Identity Protocol with Legacy Applications
RFC 5338, “Using the Host Identity Protocol with Legacy Applications”, is an Experimental document published in September 2008 by T. Henderson, P. Nikander, M. Komu. The canonical text is published by the RFC Editor.
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 memo provides information for the Internet community.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 5338 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5337 Internationalized Delivery Status and Disposition Notifications
- RFC 5339 Evaluation of Existing GMPLS Protocols against Multi-Layer and Multi-Region Networks
- RFC 5336 SMTP Extension for Internationalized Email Addresses
- RFC 5340 OSPF for IPv6
- RFC 5335 Internationalized Email Headers
- RFC 5341 The Internet Assigned Number Authority tel Uniform Resource Identifier Parameter Registry
- RFC 5334 Ogg Media Types
- RFC 5342 IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters