A new IETF working group has been formed in the Internet Area. For additional information, please contact the Area Directors or the WG Chairs. Host Identity Protocol (hip) ----------------------------- Current Status: Active Working Group Chair(s): David Ward <dward@cisco.com> Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> Internet Area Director(s): Thomas Narten <narten@us.ibm.com> Margaret Wasserman <margaret@thingmagic.com> Internet Area Advisor: Margaret Wasserman <margaret@thingmagic.com> Mailing Lists: General Discussion: hipsec@honor.trusecure.com To Subscribe: hipsec-request@honor.trusecure.com In Body: With a subject line: subscribe Archive: http://honor.trusecure.com/pipermail/hipsec/ 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. The specifications for the architecture and protocol details for these mechanisms consist of: draft-moskowitz-hip-arch-05.txt (at RFC editor) and draft-moskowitz-hip-08.txt (soon -09.txt) There are five publicly known, interoperating 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. +-------------------------------------------------------+ | The purpose of this Working Group is to define the | | minimal infrastructure 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, to complete the existing work on basic mobility and multi-homing, 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. It is expected that there will be a roughly parallel, though perhaps considerably broader, IRTF Research Group that will include efforts both on developing the more forward looking aspects of the HIP architecture and on exploring the effects that HIP may have on the applications and the Internet. The following are charter items for the working group: 1) Complete the HIP base protocol specification. Starting point: draft-moskowitz-hip-08.txt (or newer) 2) Complete the basic mobility and multi-homing support for HIP. Starting point: draft-nikander-hip-mm-01.txt (or newer) While this work partially overlaps the work in Mobile IP and Multi6 Working Groups, it is very different in the sense that is based on the Experimental HIP specification, and cannot function without it. 3) Define one or more new DNS Resource Records for storing HIP related data, such as Host Identifiers and Host Identity Tags (HITs). This task explicitly excludes the task of defining reverse DNS entries based on HITs. 4) Define a basic HIP rendezvous mechanism. A basic HIP rendezvous server allows mobile and non-mobile HIP hosts to register their current IP addresses at the server. Other hosts can then send the initial I1 packets to the rendezvous server, which forwards the packets to the HIP host's current address. This task explicitly excludes solving more general problems, such as the referral problem. Also excluded is the problem of finding the right rendezvous server. It is expected that the DNS records will be used for that. The Working Group bases all the work on the HIP achitecture specification (as defined above). Goals and Milestones: Mar 04 WG LC on the base protocol specification Mar 04 First version of the HIP basic mobility and multi-homing mechanism specification. Mar 04 First version of the HIP DNS resource record(s) specification. Apr 04 Complete the base protocol specification and submit it to the IESG for Experimental Apr 04 First version of the HIP basic rendezvous mechanism specification. Aug 04 WG LC on the HIP DNS resource record(s) specification. Sep 04 Submit the HIP DNS resource record(s) specification to the IESG for Experimental.Nov 04 WG LC on the HIP basic mobility and multi-homing specification. Nov 04 WG LC on the basic HIP rendezvous mechanism specification. Dec 04 Submit the HIP basic mobility and multihoming specification to the IESG for Experimental. Dec 04 Submit the basic HIP rendezvous mechanism specification to the IESG for Experimental. Jan 05 Recharter or close the WG.
