Hip Status PagesHost Identity Protocol (Active WG) |
Int Area: Éric Vyncke, Erik Kline | 2004-Feb-05 —
Chairs: ![]() ![]() ![]() |
2020-03-26 charter
Host Identity Protocol (hip) ---------------------------- Charter Current Status: Active Chair: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> Internet Area Directors: Erik Kline <ek.ietf@gmail.com> Éric Vyncke <evyncke@cisco.com> Internet Area Advisor: Éric Vyncke <evyncke@cisco.com> Mailing Lists: General Discussion: hipsec@ietf.org To Subscribe: http://www.ietf.org/mailman/listinfo/hipsec Archive: https://mailarchive.ietf.org/arch/browse/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, 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: Apr 2016 - Submit RFC5770bis to the IESG Jun 2016 - Submit the mobility portion of RFC5206bis to the IESG Jun 2016 - Submit the multihoming portion of RFC5206bis to the IESG Oct 2016 - WGLC RFC4423bis Dec 2016 - Submit RFC4423bis to the IESG Jan 2017 - Recharter or close the WG 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 Done - WGLC the specification on how to build HIP-based overlays using RELOAD Done - Submit the specification on how to build HIP-based overlays using RELOAD to the IESG Done - WGLC RFC4843bis Done - WGLC RFC5201bis Done - WGLC RFC5202bis Done - Submit RFC5201bis to the IESG Done - Submit RFC4843bis to the IESG Done - Submit RFC5202bis to the IESG Done - WGLC RFC5203bis Done - WGLC RFC5204bis Done - WGLC RFC5205bis Done - Submit RFC5203bis to the IESG Done - Submit RFC5204bis to the IESG Done - Submit RFC5205bis to the IESG Done - WGLC RFC5770bis Done - WGLC Certs in HIP base exchange specification (referencing RFC5201bis) Done - Submit Certs in HIP base exchange (referencing RFC5201bis) to the IESG as PS Done - WGLC the mobility portion of RFC5206bis Done - WGLC the multihoming portion of RFC5206bis
All charter page changes, including changes to draft-list, rfc-list and milestones: