Host Identity Protocol BOF (hipbof)

Monday, November 10 at 0900-1130
================================
CHAIRS:  Pekka Nikander <[email protected]>
        David Ward <[email protected]>

AGENDA:

5 min  Intro and Agenda Bashing                 Chairs
25 min  Introduction to HIP                      Pekka Nikander
20 min  Demo of current implementations          Demo team
         - HIP base exchange
         - HIP mobility between IPv4 and IPv6
         - HIP based IPv4/IPv6 API bridging
10 min  Status of current work                   Chairs
50 min  Charter discussion                       All
10 min  Summary and next steps                   Chairs


DESCRIPTION:

Host Identity Protocol (HIP) proposes a solution for 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 HIP protocol permits IPv6 and IPv4 hosts to identify each other
based on the public keys, to establish a pair of host-to-host ESP
security associations using these public keys, and to run both IPv4 and
IPv6 applications side-by-side independent of the underlying type of
connectivity.  It also allows many IPv4 applications to communicate
directly with IPv6 applications, and vice versa.

Currently, the HIP base protocol works well with any pair of co-operating
end-hosts.  However, to be more useful and more widely deployable, HIP
needs some support from the existing infrastructure and a new piece of
infrastructure, called the HIP rendezvous server or the HIP proxy.

+--------------------------------------------------------+
| The purpose of the proposed Working Group is to define |
| the required infrastructure elements that are needed   |
| for HIP experimentation on a wide scale.               |
+--------------------------------------------------------+

In particular, the objective of the proposed working working group is to
complete the DNS, mobility, multi-homing, and NAT traversal work on HIP,
and produce Experimental RFCs for these.  If necessary, the WG can also
revise the base HIP protocol specification, but only if the changes do
not unnecessarily increase the complexity of the base protocol.

Additionally, the proposed working group aims to standardize, together
with the IPsec Working Group, a set of small additions to IPsec ESP.
The goal of these additions is to allow HIP to utilize existing ESP
implementations.  The same additions would also be potentially benefit
for other multi-addressing mechanisms, such as Mobile IP.


READING LIST:

draft-moskowitz-hip-arch-04.txt (soon -05.txt)
draft-moskowitz-hip-07.txt (soon -08.txt)
draft-nikander-hip-mm-00.txt
draft-nikander-esp-beet-mode-00.txt
http://www.tml.hut.fi/~pnr/HIP/hip_charter_proposal.txt


MAILING LIST:

General Discussion: [email protected]
Send mail to: [email protected]
With a subject line: subscribe
List archive: http://honor.trusecure.com/pipermail/hipsec/
Host Identity Protocol (HIP)


The following are charter items for the working group:

0) If the architecture and base protocol specifications have not been
  submitted to the IESG by the time the WG is formally created, complete
  the specifications and submit them to the IESG.

1) Complete the basic mobility and multi-homing support for HIP.

  This work will use draft-nikander-hip-mm-00.txt as a starting point.
  While this work partially overlaps the work in Mobile IP and Multi6
  Working Groups, it is very different in the sense that is based on the
  Experimental HIP specification, and cannot function without it.

2) Define DNS interactions, including how to store HIP Host Identifiers
  into the DNS.

3) Define NAT traversal for HIP.

  The NAT traversal must work with mobile and multi-homed HIP hosts.
  The mechanism MAY require changes to existing NAT boxes.

4) Define a HIP rendezvous and proxy mechanism.

  A HIP rendezvous mechanism is needed to provide initial connectivity
  with fast moving HIP hosts, and to allow simultaneously moving hosts
  to find each other after con-current movements.

  Additionally, HIP hosts are currently able to talk to non-HIP hosts
  using standard IPv6 or IPv4, including MIPv6 or MIPv4.  However, if
  they do so, the HIP hosts do not benefit from the mobility and
  multi-homing aspects of HIP.  A proxy would allow a HIP host to talk
  to a non-HIP host, but still use HIP mobility and multi-homing.

  It looks like these two functions would be fairly similar, and
  therefore they are currently grouped together.  If the perception of
  similarity appears to be wrong, the working group may decide to
  separate the functions.

5) Optionally, define a mechanism that allows any Host Identifier to be
  as a seach key to find a DNS name and/or an IP address.  Such a
  mechanism could be based on Distributed Hash Tables.

6) If needed to complete any of the items above, revise the base protocol
  specification.  If any such revisions are needed, care must be taken
  not to unnecessarily increase the complexity of the base protocol.

The Working Group bases all the work on the base HIP protocol specifications
(as defined above).


Specifically out of scope is comparison of HIP to existing or other proposed
IP based mobility, multi-homing, other multi-addressing, security, or NAT
traversal solutions.  This does *not* mean that such comparison should not
be made (indeed, such comparisons would be very valuable), but that they are
outside of the scope of the working group, and should not be discussed at
the working group mailing list.  Announcements of any completed works in
those areas are acceptable.

Goals and Milestones:

Nov 03    Complete the architecture and and base protocol specifications
         and submit them to the IESG to be considered as Experimental.

Nov 03    First version of the HIP basic mobility and multi-homing mechanism
         specification, using draft-nikander-hip-mm-00.txt as a starting
         point.

Nov 03    First version of the ESP additions specification, using
         draft-nikander-esp-beet-mode-00.txt as a starting point.

Dec 03    First version of the HIP DNS interactions specification.

Jan 04    First version of the HIP NAT traversal specification.

Jan 04    Combined HIP and IPsec WG LC on the ESP additions specification.

Feb 04    First version of HIP rendezvous and proxy mechanism specification.
Mar 04    Submit the ESP additions specification to the IESG for Standards
         Track.

Mar 04    WG LC on the HIP DNS interactions specification.

Apr 04    WG LC on the HIP basic mobility and multihoming specification
         together with the HIP NAT traversal specification.

May 04    Submit the HIP DNS interactions specification to the IESG for
         Experimental.

Jun 04    Submit the HIP basic mobility and multihoming specification
         together with the HIP NAT traversal specification to the IESG for
         Experimental.

Jul 04    WC LC on the HIP rendezvous and proxy mechanism specification.

Sep 04    Submit the HIP rendezvous and proxy mechanism specification to
         the IESG for Experimental.

Nov 04    Close or recharter the WG.

Current Internet-Drafts:

draft-moskowitz-hip-arch-04.txt (soon -05.txt)
draft-moskowitz-hip-07.txt (soon -08.txt)
draft-nikander-hip-mm-00.txt
draft-nikander-esp-beet-mode-00.txt

Proposed WG items:

draft-ietf-hip-mm-XX.txt         (HIP basic mobility and multihoming)
draft-ietf-hip-esp-beet-XX.txt   (ESP additions)
draft-ietf-hip-dns-XX.txt        (HIP DNS interactions)
draft-ietf-hip-nat-XX.txt        (HIP NAT traversal)
draft-ietf-hip-rendezvous-XX.txt (HIP rendezvous and proxy)

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.