HIP working group 1 HIP-WG meeting, IETF61 HIP-mm update November 8, 2004 Tom Henderson

HIP working group 2 HIP mm goals session persistence across multiple locators –simultaneously (multihoming) –sequentially (mobility) –address families (IPv4/IPv6 transition) address verification –with reachability check locator change with or without rekeying declaring a “preferred” address announcing additional locators in base handshake middlebox-friendliness

HIP working group 3 HIP mm non-goals rendezvous or proxy services location privacy multihoming with legacy hosts transport layer issues –MTU discovery –congestion control –QoS adjustment

HIP working group 4 draft history nikander-hip-mm-00, -01, -02 –draft receives WG status in July 2004 draft-ietf-hip-mm-00 (October 17, 2004) –REA parameter type value now “3” –inbound/outbound SAs are paired to avoid ambiguity when rekeying –multihoming restricted to failover, for now –clarification on use of non-global addresses –some additional clarifications mainly due to Mika Kousa

HIP working group 5 Open issues (i) needed: implementation experience!! –Implementations: HIPL, Boeing, NomadicLab –however, protocol not significantly exercised yet (corner cases?), especially in multihoming context Missing sections in draft: policy considerations (Section 8) security analysis and considerations (Section 9) –note, these are not trivial sections

HIP working group 6 Open issues (ii) Technical issues in existing draft: parameter ordering for middlebox friendliness –some duplication in presence of SPI values (in SPI, REA, NES) are we doing enough for NAT traversal? –protocol needs analysis in this light multihoming design is probably not clean or understood enough –currently restricted to “paired” SAs and failover (not load balancing) only

HIP working group 7 Next steps Informal middlebox design team/reviewers needed –resolve how middleboxes and mobility interact experimentation with real multihoming –are any PlanetLab nodes multihomed? Security and policy issues sections need written