<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.irtf-hiprg-proxies" target="https://datatracker.ietf.org/doc/html/draft-irtf-hiprg-proxies-05">
   <front>
      <title>Overview of HIP Proxy Scenarios and Solutions</title>
      <author initials="D." surname="Zhang" fullname="Dacheng Zhang">
         <organization>Huawei Technologies Co.,Ltd</organization>
      </author>
      <author initials="X." surname="Xu" fullname="Xiaohu Xu">
         <organization>Huawei Technologies Co.,Ltd</organization>
      </author>
      <author initials="J." surname="Yao" fullname="Jiankang Yao">
         <organization>CNNIC</organization>
      </author>
      <author initials="Z." surname="Cao" fullname="Zehn Cao">
         <organization>China Mobile</organization>
      </author>
      <date month="March" day="8" year="2012" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-irtf-hiprg-proxies-05" />
   
</reference>
