Preferred Alternatives for Tunnelling HIP (PATH)
draft-nikander-hip-path-01

Document Type Expired Internet-Draft (individual)
Author Pekka Nikander 
Last updated 2006-03-09
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-nikander-hip-path-01.txt

Abstract

With the extensions defined in this document Host Identity Protocol (HIP) can traverse legacy Network Address Translators (NATs) and certain firewalls. The extension will be useful as part of the base exchange and with the HIP Registration Extension. By using a rendezvous server an additional entity inside the network is utilized, which not only allows but also supports more restrictive NATs to be traversed.

Authors

Pekka Nikander (Pekka.Nikander@nomadiclab.com)

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