IETF 80 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

Host Identity Protocol (hip) (WG)

Minutes  | Audio Archives  |  Jabber Logs  |  Mailing List Archives

Additional information is available at tools.ietf.org/wg/hip

Chair(s): David Ward Gonzalo Camarillo Internet Area Director(s): Ralph Droms Jari Arkko Internet Area Advisor: Ralph Droms

Meeting Slides

• Chair Slides
• RFC 4423 bis
• RFC 5201 bis
• RFC 5206 bis

Internet-Drafts:

• Host Identity Protocol (HIP) Registration Extension (28036 bytes)
• Basic Socket Interface Extensions for Host Identity Protocol (HIP) (45680 bytes)
• Host Identity Protocol Certificates (26293 bytes)
• Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD) (21860 bytes)
• Encrypted Signaling Transport Modes for the Host Identity Protocol (28400 bytes)
• Host Identity Protocol (HIP) Domain Name System (DNS) Extension (35885 bytes)
• Host Identity Protocol (HIP) Rendezvous Extension (30999 bytes)
• An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID) (32094 bytes)
• Host Identity Protocol Architecture (67319 bytes)
• Host Identity Protocol Version 2 (HIPv2) (295259 bytes)
• Host Mobility with the Host Identity Protocol (78697 bytes)
• Native NAT Traversal Mode for the Host Identity Protocol (32468 bytes)

Request for Comments:

• Host Identity Protocol (HIP) Architecture (RFC 4423) (60977 bytes)
• End-Host Mobility and Multihoming with the Host Identity Protocol (RFC 5206) (99430 bytes)
• Host Identity Protocol (HIP) Rendezvous Extension (RFC 5204) (30233 bytes)
• Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) (RFC 5202) (68195 bytes)
• Host Identity Protocol (HIP) Registration Extension (RFC 5203) (26620 bytes)
• Host Identity Protocol (HIP) Domain Name System (DNS) Extensions (RFC 5205) (34799 bytes)
• Host Identity Protocol (RFC 5201) (240492 bytes)
• Using the Host Identity Protocol with Legacy Applications (RFC 5338) (34882 bytes)
• Basic Host Identity Protocol (HIP) Extensions for Traversal of Network Address Translators (RFC 5770) (79767 bytes)
• Host Identity Protocol (HIP) Multi-hop Routing Extension (RFC 6028) (21571 bytes)
• Host Identity Protocol (HIP) Immediate Carriage and Conveyance of Upper-Layer Protocol Signaling (HICCUPS) (RFC 6078) (41482 bytes)
• HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking Environment (BONE) (RFC 6079) (51013 bytes)

Charter (as of 2011-02-23)

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		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
Done		WGLC Certs in HIP base exchange specification
Done		WGLC the HIP over HIP specification
Done		Submit Certs in HIP base exchange to the IESG as Experimental
Done		Submit the HIP over HIP specification to the IESG
Mar 2011		WGLC the specification on how to build HIP-based overlays using RELOAD
Apr 2011		Submit the specification on how to build HIP-based overlays using RELOAD to the IESG
May 2011		WGLC RFC4423bis
May 2011		WGLC RFC4843bis
May 2011		WGLC RFC5201bis
May 2011		WGLC RFC5202bis
Jun 2011		Submit RFC5201bis to the IESG
Jun 2011		Submit RFC4843bis to the IESG
Jun 2011		Submit RFC4423bis to the IESG
Jun 2011		Submit RFC5202bis to the IESG
Jul 2011		WGLC RFC5203bis
Jul 2011		WGLC RFC5204bis
Jul 2011		WGLC RFC5205bis
Jul 2011		WGLC the mobility portion of RFC5206bis
Aug 2011		Submit RFC5203bis to the IESG
Aug 2011		Submit RFC5204bis to the IESG
Aug 2011		Submit RFC5205bis to the IESG
Aug 2011		Submit the mobility portion of RFC5206bis to the IESG
Sep 2011		WGLC RFC5770bis
Sep 2011		WGLC the multihoming portion of RFC5206bis
Oct 2011		Submit RFC5770bis to the IESG
Oct 2011		Submit the multihoming portion of RFC5206bis to the IESG
Nov 2011		WGLC Certs in HIP base exchange specification (referencing RFC5201bis)
Dec 2011		Submit Certs in HIP base exchange (referencing RFC5201bis) to the IESG as PS
Jan 2012		Recharter or close the WG