Host Identity Protocol (hip)

Host Identity Protocol (hip)
----------------------------

Charter
Last Modified: 2010-07-23

Current Status: Active Working Group

Chair(s):
David Ward <[email protected]>
Gonzalo Camarillo <[email protected]>

Internet Area Director(s):
Ralph Droms <[email protected]>
Jari Arkko <[email protected]>

Internet Area Advisor:
Ralph Droms <[email protected]>

Mailing Lists:
General Discussion:[email protected]
To Subscribe: http://www.ietf.org/mailman/listinfo/hipsec
Archive: http://www.ietf.org/mail-archive/web/hipsec/current/maillist.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, from which
end-point identifiers are taken. The public keys are typically, but
not necessarily, self generated. HIP uses existing IP addressing and
forwarding for locators and packet delivery.

The architecture and protocol details for these mechanisms are
currently specified in the following Experimental RFCs:

o HIP Architecture (RFC 4423)
o Host Identity Protocol (RFC 5201)

There are several publicly known interoperating implementations, some
of which are open source.

The HIP WG was chartered to publish protocol specifications in
documents whose quality and security properties would meet the
requirements for publication as standards track documents. These
specifications have been published as Experimental RFCs, because the
effects of the protocol on applications and on the Internet as a whole
were unknown.

The Experimental RFCs produced by the HIP WG allowed the community to
experiment with HIP technologies and learn from these experiments.
The HIP WG will now produce standards track versions of the main HIP
RFCs taking as a base the existing Experimental RFCs. The WG will also
specify certificate handling in HIP in a standards track RFC.

Additionally, the WG will finish the WG items it was working on before
starting the standards track work. These WG items relate to how to
build HIP-based overlays and will result in Experimental RFCs.

The following are charter items for the working group:

o Revise RFCs 4423, 4843, 5201, 5202, 5203, 5204, 5205, 5206, and 5770
as standards track RFCs.

o Specify in a standards track RFC how to carry certificates in the
base exchange. This was removed from the base HIP spec so that the
mechanism is specified in a stand-alone spec.

o Specify in an Experimental RFC how to build a HIP-based overlay
using RELOAD.

o Specify in an Experimental RFC how to transport HIP messages over
encrypted connections that were established using HIP.

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.

Done WGLC Legacy Application Interworking specification

Done Submit the Legacy Application Interworking specification to the
IESG

Done WGLC Legacy NAT traversal specification

Done WGLC Native API specification

Done Submit the Legacy NAT traversal specification to the IESG

Done Submit Native API specification to the IESG

Done Submit Framework for HIP overlays specification to the IESG

Done Submit Multi-hop routing mechanism for HIP

Done Submit Upper-layer data transport in HIP to the IESG

Sep 2010 WGLC RFC4423bis

Sep 2010 WGLC Certs in HIP base exchange specification

Sep 2010 WGLC RFC4843bis

Sep 2010 WGLC RFC5201bis

Sep 2010 WGLC RFC5202bis

Oct 2010 Submit RFC5201bis to the IESG

Oct 2010 Submit RFC4843bis to the IESG

Oct 2010 Submit RFC4423bis to the IESG

Oct 2010 Submit RFC5202bis to the IESG

Dec 2010 WGLC RFC5203bis

Dec 2010 WGLC RFC5204bis

Dec 2010 WGLC RFC5205bis

Dec 2010 WGLC the mobility portion of RFC5206bis

Jan 2011 Submit RFC5203bis to the IESG

Jan 2011 Submit RFC5204bis to the IESG

Jan 2011 Submit RFC5205bis to the IESG

Jan 2011 Submit the mobility portion of RFC5206bis to the IESG

Feb 2011 WGLC RFC5770bis

Feb 2011 WGLC the multihoming portion of RFC5206bis

Mar 2011 Submit RFC5770bis to the IESG

Mar 2011 Submit the multihoming portion of RFC5206bis to the IESG

Apr 2011 Recharter or close the WG

Internet-Drafts:

Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Aug 2010 <draft-ietf-hip-rfc5203-bis-00.txt>
Host Identity Protocol (HIP) Registration Extension

Nov 2006 Jan 2010 <draft-ietf-hip-native-api-12.txt>
Basic Socket Interface Extensions for Host Identity Protocol
(HIP)

Oct 2008 Apr 2010 <draft-ietf-hip-cert-03.txt>
HIP Certificates

Oct 2008 Jun 2010 <draft-ietf-hip-bone-07.txt>
HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking
Environment

Oct 2009 Jul 2010 <draft-ietf-hip-hiccups-05.txt>
HIP (Host Identity Protocol) Immediate Carriage and Conveyance
of Upper- layer Protocol Signaling (HICCUPS)

Oct 2009 Jun 2010 <draft-ietf-hip-via-03.txt>
Host Identity Protocol (HIP) Multi-hop Routing Extension

Jan 2010 Jul 2010 <draft-ietf-hip-reload-instance-02.txt>
Host Identity Protocol-Based Overlay Networking Environment
(HIP BONE) Instance Specification for REsource LOcation And
Discovery (RELOAD)

Apr 2010 Jul 2010 <draft-ietf-hip-over-hip-01.txt>
Host Identity Protocol Signaling Message Transport Modes

Aug 2010 Aug 2010 <draft-ietf-hip-rfc5205-bis-00.txt>
Host Identity Protocol (HIP) Domain Name System (DNS) Extension

Aug 2010 Aug 2010 <draft-ietf-hip-rfc5204-bis-00.txt>
Host Identity Protocol (HIP) Rendezvous Extension

Aug 2010 Aug 2010 <draft-ietf-hip-rfc4843-bis-00.txt>
An IPv6 Prefix for Overlay Routable Cryptographic Hash
Identifiers (ORCHID)

Aug 2010 Aug 2010 <draft-ietf-hip-rfc4423-bis-01.txt>
Host Identity Protocol Architecture

Aug 2010 Sep 2010 <draft-ietf-hip-rfc5201-bis-01.txt>
Host Identity Protocol

Aug 2010 Aug 2010 <draft-ietf-hip-rfc5206-bis-00.txt>
End-Host Mobility and Multihoming with the Host Identity
Protocol

Request For Comments:

RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC4423 I May 2006 Host Identity Protocol (HIP) Architecture

RFC5201 E Apr 2008 Host Identity Protocol

RFC5205 E Apr 2008 Host Identity Protocol (HIP) Domain Name System (DNS)
Extensions

RFC5203 E Apr 2008 Host Identity Protocol (HIP) Registration Extension

RFC5202 E Apr 2008 Using the Encapsulating Security Payload (ESP) Transport
Format with the Host Identity Protocol (HIP)

RFC5204 E Apr 2008 Host Identity Protocol (HIP) Rendezvous Extension

RFC5206 E Apr 2008 End-Host Mobility and Multihoming with the Host Identity
Protocol

RFC5338 E Sep 2008 Using the Host Identity Protocol with Legacy
Applications

RFC5770 E Apr 2010 Basic Host Identity Protocol (HIP) Extensions for
Traversal of Network Address Translators