1 / 10

Mobility Support in NSIS <draft-fu-nsis-mobility-00.txt> 57th IETF Meeting, July 13-18, Vienna

Xiaoming Fu Henning Schulzrinne Hannes Tschofenig. Mobility Support in NSIS <draft-fu-nsis-mobility-00.txt> 57th IETF Meeting, July 13-18, Vienna. How NSIS can work with Mobility. Problem:

baruch
Download Presentation

Mobility Support in NSIS <draft-fu-nsis-mobility-00.txt> 57th IETF Meeting, July 13-18, Vienna

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Xiaoming Fu Henning Schulzrinne Hannes Tschofenig Mobility Support in NSIS<draft-fu-nsis-mobility-00.txt>57th IETF Meeting, July 13-18, Vienna

  2. How NSIS can work with Mobility Problem: • In WG charter: “The work produced in this Working Group should work with existing IETF mobility and AAA protocols, including (but not limited to)Mobile IP, SeaMoby Context Transfer and Diameter.” • But - there are various mobility protocols (IPv4+v6 mobility, FMIP, HMIP/LMM, CTP, …) Implications: • NSIS concerns with signaling along data path • Separating NSIS signaling from mobility signaling! • How about generalizing data path after completing various mobility protocols? • API for (mobility) route change notification & query

  3. MN as data sender: CN as data sender: CN CN HA HA MAP/GFA MAP/GFA pAR pAR nAR nAR • Possibilities: • Mobile IP (route-opt) • Mobile IP (no-route-opt) • Fast Handover • Hierarchical Mobile IP • Fast handover with HMIP • …… IP-in-IP tunnel MN MN Normal routing

  4. General issue: state management CN Problem: • Cross-Over Router (CR) splits the data path • State must be updated to reflect the flow • Must be ONE state per single session • Scope to refresh: locally or E2E? Implications: • Session ID independent of flow ID • E2E refresh to update flow ID CR R R pAR nAR MN

  5. Local repair issue CN Problem: • Between MN and CR: • New path  establish new states • Old path state expiration or explicit teardown • MN may loose connectivity •  impossible to send a teardown • Teardown should NOT release state in common path Implication: • Maybe a Branch_ID or Message_ID? • CR is best to initiate teardown? • Authentication/DoS? CR R pAR nAR MN

  6. Data source issue CN Problem: • MN or CN as data source • how to determine a CR? • MNCN: by detecting a session ID match • CNMN: network-triggered, or MN triggered? • When to initiate a teardown? • MNCN: after/simultaneous to refresh? • CNMN: after/simultaneous to refresh? Implication: • Unification of operations is necessary • Securing local repair? CR R pAR nAR MN

  7. Synchronization issue CN Problem: • Improper local repair can cause: • States removed improperly • States established improperly • Even run into race conditions Implication: • Incremental Branch_ID / Message_ID? • RSVP LIH-like object? • Wait timer CR 4 5 3 R AR2 pAR AR1 2 1 MN (MN moves)

  8. Tunneling issue Problem: • Tunnel endpoints should support NSIS • To signal into tunnels • Tunnels can be physically long, even for pARnAR Implication: • Tunnel signaling optional? • How about several levels of tunnels? • P2P addressing: discovery component? • E2E addressing: RFC2746-like NTLP-in-NTLP?

  9. Summary • NSIS independent of mobility protocols • General state management • Mobility-caused local repair • Synchronization • Who is data source • Mobility-caused tunnels • How to address NSIS messages • P2P or E2E? • How to secure NSIS mobility support

  10. Should these issues be considered in NSIS design? • Next step for “NSIS working with mobility”? • Make this a separate item, or • Incorporated with NSIS design

More Related