Jump to content

Host Identity Protocol

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Wrs1864 (talk | contribs) at 05:14, 7 December 2008 (External links: add more RFCs). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The Host Identity Protocol (HIP) provides a method of separating the end-point identifier and locator roles of IP addresses. It introduces a new Host Identity (HI) name space, based on public keys. The public keys are typically, but not necessarily, self-generated.

HIP is being specified in the IETF's HIP working group. An IRTF HIP research group looks at the broader impacts of HIP.

The working group is chartered to produce RFCs on the "Experimental" track, but it is understood that their quality and security properties should match the standards track requirements. The main purpose for producing Experimental documents instead of standards track ones are the unknown effects that the mechanisms may have on applications and on the Internet in the large.

  • IETF working group
  • IRTF research group
  • How HIP works - from InfraHIP site
  • RFC 4423 - Host Identity Protocol (HIP) Architecture (early "informational" snapshot)
  • RFC 5201 - Host Identity Protocol base
  • RFC 5202 - Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)
  • RFC 5203 - Host Identity Protocol (HIP) Registration Extension
  • RFC 5204 - Host Identity Protocol (HIP) Rendezvous Extension
  • RFC 5205 - Host Identity Protocol (HIP) Domain Name System (DNS) Extension
  • RFC 5206 - End-Host Mobility and Multihoming with the Host Identity Protocol
  • RFC 5207 - NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) Communication