Preferred Alternatives for Tunnelling HIP (PATH)
draft-nikander-hip-path-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Pekka Nikander | ||
| Last updated | 2006-03-09 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)