1 / 7

Requirements/Background

Reflector Extension for Route Optimization Agent <draft-cui-netext-route-optimization-agent-ext-01.txt> November 11, 2009 IETF 76, Hiroshima Xiangsong Cui. Requirements/Background.

boyce
Download Presentation

Requirements/Background

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. Reflector Extension for Route Optimization Agent<draft-cui-netext-route-optimization-agent-ext-01.txt>November 11, 2009 IETF 76, HiroshimaXiangsong Cui

  2. Requirements/Background [3GPP2-X.S0011-002-D] specifies, "The Home Agent shall support Return Routability (RR) for Route Optimization as specified in [RFC3775]." [3GPP2-X.S0047-0] specifies, "The MS may support the return routability procedure, binding update procedure..." The protocol reference model for MIP6 Route Optimization mode is illustrated in [3GPP2-X.S0011-001-D] .

  3. Existing Issues Route Optimization can’t be used if CN can’t support that

  4. Extension Overview Route Optimization Agent intercepts HoTI, CoTI and BU message, and manages binding for the attached MN Route Optimization Agent rewrites the source/destination address of the traffic packets, adds/removes Extension Header…

  5. Handover Consideration MN1 HA LMA pMAG nMAG MN2 nMAG supports ROA pMAG acts Route Optimization Agent Return routability & binding update through pMAG * If the security parameters (Keys, Token, etc.) are not transferred to nMAG, the nMAG should send a Binding Refresh Requests message to the home address of MN1 to trigger the update PFMIP applied during handover Agent Binding Cache entry is transferred to nMAG as context* Binding Refresh Requests nMAG acts Route Optimization Agent New return routability & binding update through nMAG

  6. Handover, contd. MN1 HA LMA pMAG nMAG MN2 pMAG acts Route Optimization Agent return routability & binding update through pMAG If nMAG can not support Route Optimization Agent function or the configuration is disable, pMAG must revoke the Route Optimization binding PFMIP applied during handover Agent Binding Cache entry is not transferred because nMAG can not support Agent function RO Binding Revocation Fallback to bidirectional tunneling mode

  7. Discussion • A manner of *Reactive* & *Network-based* mobility management, for seamless mobility • Any questions or comments on this item? Thank you!

More Related