Using the Host Identity Protocol with Legacy Applications

Metadata

Publisher: IETF
Doc Type: Experimental
Pages: 14
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.
Publication Date: 2008-09-01
Status Note: Experimental
DOI: 10.17487/RFC5338
Link: https://doi.org/10.17487/RFC5338
Author(s): Tom Henderson
Pekka Nikander
Miika Komu
Keyword(s): HIP, Cryptographic Namespace, Network Stack Names, API, Application Programming Interface

Latest version of IETF RFC 5338

Document Versions — IETF RFC 5338

▶ IETF RFC 5338 (2008-09-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

Nordmark, E., "Shim6 Application Referral Issues" , Work in Progress, July 2005. EXTERNAL
Salz, J., Balakrishnan, H., and A. Snoeren, "TESLA: A Transparent, Extensible Session-Layer Architecture for End-to-end Network Services", Proceedings of USENIX Symposium on Internet Technologies and Systems (USITS), pages 211-224, March 2003. EXTERNAL
IETF RFC 1958 [Active*]
IETF RFC 3493 [Active*]
IETF RFC 4033 [Active*]
IETF RFC 4843 [Superseded*]
IETF RFC 5201 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5338.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 5338, Using the Host Identity Protocol with Legacy Applications. Available at https://doi.org/10.17487/RFC5338

Snippet:

IETF RFC 5338, Using the Host Identity Protocol with Legacy Applications. Available at https://doi.org/10.17487/RFC5338

HTML (ISO 690 compliant)

Preview:

IETF RFC 5338, Using the Host Identity Protocol with Legacy Applications. Available at https://doi.org/10.17487/RFC5338

Snippet:

<span class="citation"><cite>IETF RFC 5338</cite>, Using the Host Identity Protocol with Legacy Applications. Available at <a href="https://doi.org/10.17487/RFC5338" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5338</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5338, Using the Host Identity Protocol with Legacy Applications
doi: 10.17487/RFC5338
url: https://doi.org/10.17487/RFC5338

Snippet:

<li>
<cite id="bib-rfc5338">IETF RFC 5338</cite>, Using the Host Identity Protocol with Legacy Applications
<span class="doi">10.17487/RFC5338</span>
</li>

Referenced By

IETF RFC 6079 [Active*]
IETF RFC 6317 [Active*]
IETF RFC 6538 [Active*]
IETF RFC 7401 [Active*]
IETF RFC 9063 [Active*]