Host Identity Protocol (hip)
----------------------------
Charter
Last Modified: 2006-11-03
Current Status: Active Working Group
Chair(s):
David Ward <
[email protected]>
Gonzalo Camarillo <
[email protected]>
Internet Area Director(s):
Jari Arkko <
[email protected]>
Mark Townsley <
[email protected]>
Internet Area Advisor:
Mark Townsley <
[email protected]>
Mailing Lists:
General Discussion:
[email protected]
To Subscribe:
http://www1.ietf.org/mailman/listinfo/hipsec
Archive:
http://www.ietf.org/mail-archive/web/hipsec/index.html
Description of Working Group:
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.
There are five publicly known interoperating HIP implementations, some
of which are open source.
Currently, the HIP base protocol works well with any pair of
co-operating end-hosts. However, to be more useful and more widely
deployable, HIP needs some support from the existing infrastructure,
including the DNS, and a new piece of infrastructure, called the HIP
rendezvous server. Additionally, in order to facilitate experimenting
with HIP, there is a need to study the interactions of HIP with legacy
NATS and legacy applications, and to describe an API for HIP.
+----------------------------------------------------------+
| The purpose of this Working Group is to define the |
| minimal elements that are needed for HIP experimentation |
| on a wide scale. |
+----------------------------------------------------------+
In particular, the objective of this working group is to complete the
base protocol specification, define one or more DNS resource records
for storing HIP related data, complete the existing work on basic
mobility and multi-homing, complete the work on NATs and on APIs, and
produce Experimental RFCs for these.
Note that even though the specifications are chartered for
Experimental, 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.
There is a roughly parallel, though perhaps considerably broader, IRTF
Research Group that includes efforts both on developing the more
forward looking aspects of the HIP architecture and on exploring the
effects that HIP may have on applications and the Internet.
Goals and Milestones:
Done First version of the HIP basic mobility and multi-homing
mechanism specification.
Done First version of the HIP DNS resource record(s) specification.
Done First version of the HIP basic rendezvous mechanism
specification.
Done WGLC on the HIP architecture specification
Done Submit the HIP architecture specification to the IESG
Done WG LC on the base protocol specification
Done WG LC on the ESP usage specification
Done WGLC the HIP registration extensions specification
Done WGLC the HIP DNS resource record(s) specification
Done WG LC on the basic HIP rendezvous mechanism specification.
Done Submit the ESP usage specification to the IESG for Experimental
Done Submit the base protocol specification to the IESG for
Experimental
Done WG LC on the HIP basic mobility and multi-homing specification.
Done Submit the HIP registration extensions specification for
Experimental
Done Submit the HIP DNS resource record(s) specification to the IESG
for Experimental.
Done Submit the HIP basic mobility and multihoming specification to
the IESG for Experimental.
Done Submit the basic HIP rendezvous mechanism specification to the
IESG for Experimental.
Jan 2007 WGLC Legacy NAT traversal specification
Jan 2007 WGLC Legacy Application Interworking specification
Jan 2007 WGLC Native API specification
Mar 2007 Submit the Legacy NAT traversal specification to the IESG
Mar 2007 Submit the Legacy Application Interworking specification to the
IESG
Mar 2007 Submit Native API specification to the IESG
Apr 2007 Recharter or close the WG
Internet-Drafts:
Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Jun 2004 Jun 2006 <draft-ietf-hip-base-06.txt>
Host Identity Protocol
Oct 2004 Jun 2006 <draft-ietf-hip-mm-04.txt>
End-Host Mobility and Multihoming with the Host Identity
Protocol
Oct 2004 Oct 2006 <draft-ietf-hip-dns-08.txt>
Host Identity Protocol (HIP) Domain Name System (DNS)
Extensions
Oct 2004 Jun 2006 <draft-ietf-hip-rvs-05.txt>
Host Identity Protocol (HIP) Rendezvous Extension
Jul 2005 Oct 2006 <draft-ietf-hip-esp-04.txt>
Using ESP transport format with HIP
Sep 2005 Jun 2006 <draft-ietf-hip-registration-02.txt>
Host Identity Protocol (HIP) Registration Extension
Nov 2006 Nov 2006 <draft-ietf-hip-nat-traversal-00.txt>
HIP Extensions for the Traversal of Network Address Translators
Nov 2006 Nov 2006 <draft-ietf-hip-native-api-00.txt>
Native Application Programming Interfaces for SHIM Layer
Prococols
Nov 2006 Nov 2006 <draft-ietf-hip-applications-00.txt>
Using HIP with Legacy Applications
Request For Comments:
RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC4423 I May 2006 Host Identity Protocol (HIP) Architecture
