Minutes HIP WG at IETF 66

Minutes edited by Gonzalo Camarillo
Based on notes by Jeffrey Ahrenholz
Meeting chaired by David Ward and Gonzalo Camarillo
Slides presented included in the proceedings

MONDAY, July 10, 2006, 1850-1950

Topic: Agenda Bash
Discussions led by: Chairs

The chairs presented the status of the HIP WG items. The base spec and
the ESP draft have already been sent to the IESG and the rest of them
are ready to be sent to the IESG. Mark, the AD for the HIP WG, said
that it is OK to send all those draft as a bundle shorly after the
meeting.

The chairs presented the milestones that will be added to the charter
based on the rechartering discussions. The new items are:

o how can hip traverse legacy NATs
o describe how HIP can interwork with legacy (no-HIP-aware applications)
o describe a native API for HIP (informational in nature) 

It seems that it will be possible to WG last call these new items in
December (if everything goes as planned).


Topic: NAT Traversal
Discussion led by: Miika Komu
Relevant documents:
	draft-schmitt-hip-nat-traversal-01.txt

Miika presented the draft. Five people in the room had read the draft.


Topic: Native API for SHIM Layer Protocols
Discussion led by: Miika Komu
Relevant documents:
        draft-komu-shim-native-api-00.txt

Miika presented the draft. Two people in the room had read the
draft. There was a question about socket options and Miika answered
that the new socket type defined in this draft will support the socket
options supported by IPv4 and IPv6 sockets.


Topic: API for Multihoming Shim
Discussion led by: Shinta Sugimoto
Relevant documents:
        draft-sugimoto-multihome-shim-api-00.txt

This draft was presented in the SHIM6 WG before the HIP session and
will be adopted as a WG item in that WG. The chairs encouraged HIP
folks to review this draft even if its home is SHIM6.

Shinta presented the draft.


Topic: Conclusions
Discussions led by: Chairs

It does not seem that further face-to-face will be needed in order to
finish the new WG items HIP will have after its rechartering. If no
special need arises, the WG may not meet in the next IETF in San
Diego.

After completing those milestones, the WG may go to sleep for a while
if there is no additional work at that point.


The HIP session ended.