Using HIP with Legacy Applications
draft-henderson-hip-applications-03

Document Type Replaced Internet-Draft (individual)
Last updated 2008-03-03 (latest revision 2006-05-26)
Replaced by draft-ietf-hip-applications
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-hip-applications
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-henderson-hip-applications-03.txt

Abstract

The Host Identity Protocol and architecture (HIP) proposes to add a cryptographic name space for network stack names. From an application viewpoint, HIP-enabled systems support a new address family (e.g., AF_HOST), 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 API issues relating to using HIP in situations in which the system is HIP-aware but the applications are not.

Authors

Tom Henderson (thomas.r.henderson@boeing.com)
Pekka Nikander (Pekka.Nikander@nomadiclab.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)