Investigation in HIP Proxies
draft-zhang-hip-investigation-proxy-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dacheng Zhang , Xiaohu Xu | ||
| Last updated | 2010-03-08 | ||
| 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
HIP proxies play an important role in the transition from the current Internet architecture to the HIP architecture. A core objective of a HIP proxy is to facilitate the communications between legacy (or Non-HIP) hosts and HIP hosts while not modifying their protocol stacks. In this document, the legacy hosts served by proxies are referred to as the Made-up Legacy (ML) hosts. Currently, various designing solutions of HIP proxies have been proposed. These solutions may be applicable in different working circumstances. In this document, we attempt to investigate these solutions in detail and compare their performances in different scenarios.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)