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

 Charter
 Last Modified: 2011-02-23

 Current Status: Active Working Group

 Chair(s):
     David Ward  <dward@juniper.net>
     Gonzalo Camarillo  <gonzalo.camarillo@ericsson.com>

 Internet Area Director(s):
     Ralph Droms  <rdroms.ietf@gmail.com>
     Jari Arkko  <jari.arkko@piuha.net>

 Internet Area Advisor:
     Ralph Droms  <rdroms.ietf@gmail.com>

 Mailing Lists: 
     General Discussion:hipsec@ietf.org
     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         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 


 Internet-Drafts:

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

Oct 2008 Jan 2011   <draft-ietf-hip-cert-09.txt>
                Host Identity Protocol Certificates 

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

Apr 2010 Jan 2011   <draft-ietf-hip-over-hip-05.txt>
                Host Identity Protocol Signaling Message Transport Modes 

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

Aug 2010 Oct 2010   <draft-ietf-hip-rfc5206-bis-01.txt>
                Host Mobility with the Host Identity Protocol 

Aug 2010 Jan 2011   <draft-ietf-hip-rfc5201-bis-04.txt>
                Host Identity Protocol 

Sep 2010 Jan 2011   <draft-ietf-hip-native-nat-traversal-01.txt>
                Native NAT Traversal Mode for the Host Identity Protocol 

Sep 2010 Sep 2010   <draft-ietf-hip-rfc5202-bis-00.txt>
                Using the Encapsulating Security Payload (ESP) Transport Format 
                with the Host Identity Protocol (HIP) 

Oct 2010 Oct 2010   <draft-ietf-hip-multihoming-00.txt>
                Host Multihoming with the Host Identity Protocol 

 Request For Comments:

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

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

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

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

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

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

RFC5201 E    Apr 2008    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 

RFC6028 E    Oct 2010    Host Identity Protocol (HIP) Multi-hop Routing Extension 

RFC6078 E    Jan 2011    Host Identity Protocol (HIP) Immediate Carriage and 
                       Conveyance of Upper-Layer Protocol Signaling (HICCUPS) 

RFC6079 E    Jan 2011    HIP BONE: Host Identity Protocol (HIP) Based Overlay 
                       Networking Environment (BONE)