Scope%20and%20Charter%20for%20MOBIKE

1
Scope and Charter for MOBIKE

• Chairs

2
Scope of MOBIKE -- Goals

• Movement and multi-homing of VPN road-warriors
  without re-establishing security associations
• Specific components useful for other WGs
• Ability to change SCTP endpoints without
  re-negotiation
• The use of IKEv2 in protecting Mobile IP
  signaling without re-negotiation

3
Scope of MOBIKE -- Non-Goals

• MOBIKE is NOT a fully fledged mobility protocol
• MOBIKE does NOT
• Hide mobility from transport protocols (beyond
  what tunnel mode already provides)
• Handle IP address changes from third parties such
  as NATs (e.g. IKEv2 NAT traversal)
• Provide opportunistic authentication (e.g. HIP)
• Provide any optimization of routing paths (e.g.
  MIPv6 RO)
• Provide load balancing mechanisms
• Allow the use of IKEv1

4
Scope of MOBIKE -- Question Marks

• Possible other in-scope items
• PFKEY extensions? (as Informational)
• BEET mode?
• (Suggestion include both)

5
Deliverables

• Jan 04 First drafts about address update support
• Mar 04 First drafts about reduced overhead (BEET)
• May 04 Submit address update support for Std RFC
• May 04 First drafts about PFKEY extensions
• Sep 04 Reduced overhead (BEET) for Inform. RFC
• Dec 04 PFKEY extension for Inform. RFC

6
Relation to Other Work at IETF

• Chairs

7
Relationship to SCTP, MIP, and HIP

• SCTP
• MOBIKE provides smoother changes to SCTP
  endpoints
• MIP
• MOBIKE can be useful for MIPv6
• Avoid re-running IKE after movements
• Unlike Mobile IP, MOBIKE does not provide
• New ways to hide mobility from upper layers
• Finer mobility functions such as MIPv6 RO
• HIP
• HIP is a fully-fledged solution, MOBIKE is a VPN
  extension
• Opportunistic authentication vs. configured
  security
• On/off vs. high granularity
• MOBIKE could provide PFKEY and BEET, useful for
  HIP