HIP%20BONE%20draft-camarillo-hip-bone-01.txt

1
HIP BONEdraft-camarillo-hip-bone-01.txt

• Gonzalo.Camarillo_at_ericsson.com

2
HIP BONEs Goal

• Specify how to build generic HIP-based overlays
  (i.e., not only to run SIP on top of them)
• Use HIP for
• Connection management
• Use the peer protocol developed by the P2PSIP WG
  for
• Data storage and retrieval
• Overlay maintenance

3
HIPs Basic Idea

• ID/Locator split
• A new Name Space of Host Identifiers (HI)
• Presented as hash values, Host Identity Tags
  (HIT)
• Sockets bound to HIs, not to IP addresses
• Makes mobility and multihoming easier

Host ID
lt , portgt
IP addr
IP address
4
Way Forward for HIP BONE Requirement on the
P2PSIP WG

• The peer protocol standardized by the P2PSIP WG
  is kept functionally and specification wise
  reasonably modular so that the HIP community can
  use the peer protocol minus the connection
  management and NAT traversal modules to
  experiment with HIP-based overlays

5
Way Forward for P2PSIP

• HIP is not used in P2PSIP
• The requirement in the previous slide is still
  met
• HIP is mandatory in P2PSIP
• The HIP WG would prioritize the work on HIP BONE
  and its related specs to meet the P2PSIP WGs
  timeframe
• HIP is optional in P2PSIP
• At the overlay level
• Non-HIP P2PSIP nodes would be unable to join a
  HIP P2PSIP overlay
• At the node level
• A mechanism to negotiate HIP between nodes would
  be needed.
• The complexity of such a mechanism (on HIP and on
  non-HIP nodes) would need to be studied

6
A Possible Outcome

• Explore if 3.2 can be designed so that the
  overhead on non-HIP nodes is minimal
• If this is not possible, do 1