Search RFCs

RFC Editor

File formats:

Status:

EXPERIMENTAL

Authors:

T. Henderson
P. Nikander
M. Komu

Stream:

IETF

Source:

hip (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5338

Discuss this RFC: Send questions or comments to the mailing listhipsec@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5338

Abstract

This document is an informative overview of how legacy applicationscan be made to work with the Host Identity Protocol (HIP). HIPproposes to add a cryptographic name space for network stack names.From an application viewpoint, HIP-enabled systems support a newaddress family of host identifiers, but it may be a long time untilsuch HIP-aware applications are widely deployed even if host systemsare upgraded. This informational document discusses implementationand Application Programming Interface (API) issues relating to usingHIP in situations in which the system is HIP-aware but theapplications are not, and is intended to aid implementors and earlyadopters in thinking about and locally solving systems issuesregarding the incremental deployment of HIP. This memo provides information for the Internet community.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.