HIP WG's Charter

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

Originally, the HIP WG was chartered to produce Experimental
RFCs. However, even though the WG produced Experimental RFCs, it was
understood that their quality and security properties had to match the
standards track requirements. The main reason for producing
Experimental documents instead of standards track ones was the unknown
effects that the mechanisms may have had on applications and on the
Internet at large.

The Experimental RFCs produced by the HIP WG allowed the community to
experiment with HIP technologies and learn from these experiments. At
this point, HIP is considered to be mature enough to be specified in
standards track RFCs. This WG will 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.

In parallel to this working group, there is an IRTF Research Group
with a broader scope 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 the applications and the Internet.

The following are charter items for the working group:

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.

o Revise RFCs 4423, 4843, 5201, 5202, 5203, 5204, 5205, and 5206 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.


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 	WGLC Framework for HIP overlays specification
Done 	WGLC Multi-hop routing mechanism for HIP
Done 	WGLC Upper-layer data transport in HIP
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 Certs in HIP base exchange specification
Sep 2010	WGLC RFC4423bis
Sep 2010	WGLC RFC4843bis
Sep 2010	WGLC RFC5201bis
Sep 2010	WGLC RFC5202bis
Oct 2010 	Submit Certs in HIP base exchange specification to the
    		IESG
Oct 2010 	Submit RFC4423bis to the IESG
Oct 2010 	Submit RFC4843bis to the IESG
Oct 2010 	Submit RFC5201bis 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 2010 	Submit RFC5203bis to the IESG
Jan 2010 	Submit RFC5204bis to the IESG
Jan 2010 	Submit RFC5205bis to the IESG
Jan 2010 	Submit the mobility portion of RFC5206bis to the IESG
Feb 2010	WGLC RFCxxxxbis (NAT traversal)
Feb 2010	WGLC the multihoming portion of RFC5206bis
Mar 2010 	Submit RFCxxxxbis (NAT traversal) to the IESG
Mar 2010 	Submit the multihoming portion of RFC5206bis to the IESG
Apr 2010 	Recharter or close the WG