Host Identity Protocol (hip)

WG Name Host Identity Protocol
Acronym hip
Area Internet Area (int)
State Active
Charter charter-ietf-hip-07 Approved
Personnel Chair Gonzalo Camarillo
Area Director Terry Manderson
Mailing list Addresshipsec@ietf.org
To subscribehttp://www.ietf.org/mailman/listinfo/hipsec
Archivehttp://www.ietf.org/mail-archive/web/hipsec/
Jabber chat Room address xmpp://hip@jabber.ietf.org
Logs https://jabber.ietf.org/logs/hip/

Charter for 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.

Milestones

Date Milestone
Jan 2012 Recharter or close the WG
Dec 2011 Submit Certs in HIP base exchange (referencing RFC5201bis) to the IESG as PS
Nov 2011 WGLC Certs in HIP base exchange specification (referencing RFC5201bis)
Oct 2011 Submit the multihoming portion of RFC5206bis to the IESG
Oct 2011 Submit RFC5770bis to the IESG
Sep 2011 WGLC the multihoming portion of RFC5206bis
Sep 2011 WGLC RFC5770bis
Aug 2011 Submit the mobility portion of RFC5206bis to the IESG
Aug 2011 Submit RFC5205bis to the IESG
Aug 2011 Submit RFC5204bis to the IESG
Aug 2011 Submit RFC5203bis to the IESG
Jul 2011 WGLC the mobility portion of RFC5206bis
Jul 2011 WGLC RFC5205bis
Jul 2011 WGLC RFC5204bis
Jul 2011 WGLC RFC5203bis
Jun 2011 Submit RFC5202bis to the IESG
Jun 2011 Submit RFC4423bis to the IESG
Jun 2011 Submit RFC4843bis to the IESG
Jun 2011 Submit RFC5201bis to the IESG
May 2011 WGLC RFC5202bis
May 2011 WGLC RFC5201bis
May 2011 WGLC RFC4843bis
May 2011 WGLC RFC4423bis
Apr 2011 Submit the specification on how to build HIP-based overlays using RELOAD to the IESG
Mar 2011 WGLC the specification on how to build HIP-based overlays using RELOAD
Done Submit the HIP over HIP specification to the IESG
Done Submit Certs in HIP base exchange to the IESG as Experimental
Done WGLC the HIP over HIP specification
Done WGLC Certs in HIP base exchange specification
Done Submit Upper-layer data transport in HIP to the IESG
Done Submit Multi-hop routing mechanism for HIP
Done Submit Framework for HIP overlays specification to the IESG
Done Submit Native API specification to the IESG