Overview of HIP Proxy Scenarios and Solutions
draft-irtf-hiprg-proxies-05

Document Type Expired Internet-Draft (hiprg RG)
Last updated 2012-09-09 (latest revision 2012-03-08)
Stream IRTF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream IRTF state (None)
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
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-irtf-hiprg-proxies-05.txt

Abstract

A Host Identity Protocol (HIP) proxy is a host that holds the keying material, and participates in HIP-based communications, on behalf of one or more hosts. 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 communication between legacy (or Non- HIP) hosts and HIP hosts while not modifying the host protocol stacks. In this document, the legacy hosts served by proxies are referred to as Legacy Hosts (LHs). Currently, various design solutions of HIP proxies have been proposed. These solutions may be applicable in different working circumstances. In this document, these solutions are investigated in detail to compare their effectiveness in different scenarios.

Authors

Dacheng Zhang (zhangdacheng@huawei.com)
Xiaohu Xu (xuxh@huawei.com)
Jiankang Yao (yaojk@cnnic.cn)
Zehn Cao (zehn.cao@gmail.com)

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