1 / 9

Mobility Anchor Selection

Mobility Anchor Selection. H. Ali-Ahmad D. Moses H. Moustafa P. Seite. d raft- aliahmad - dmm -anchor-selection. Motivation. The current dmm intuition is that whenever a mobile node connects to the network, the mobility anchor serving it should be the closest to it.

tamas
Download Presentation

Mobility Anchor Selection

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. Mobility Anchor Selection H. Ali-Ahmad D. Moses H. Moustafa P. Seite draft-aliahmad-dmm-anchor-selection IETF-86, Orlando

  2. Motivation • The current dmm intuition is that whenever a mobile node connects to the network, the mobility anchor serving it should be the closest to it. • This is driven by the following assumptions: • Most flows are short • New flows are always anchored by the MA that is co-located with the current access router • After IP-handover, these flows are tunneled via their MA (until they end) Is this always the most efficient selection? IETF-86, Orlando

  3. Problematic Use-case (2) The MN typically attaches through AR2 Current MA (1) The MN has long flows (long-lived after undergoing an IP-handover) (3) But in this case, it is attached through AR1… IETF-86, Orlando

  4. After IP-handover A Long Flow !!! New traffic Handover traffic Current MA (4) So what is the situation after IP-handover? IETF-86, Orlando

  5. Problematic Use-case - Solution Knowing that – • the MN typically attaches through AR2 and – • the flows are long… What if we select AR2 as the Mobility Anchor in the first place IETF-86, Orlando

  6. Before IP-handover Yes, the traffic is tunneled, but for a short while, since the MN is typically connected through AR2 Current MA (1) Although the MN is attached through AR1, MA2 is selected as the MA IETF-86, Orlando

  7. After IP-handover Handover traffic New traffic Both new and IP-handover flows are handled without any tunnel  Current MA Current MA IETF-86, Orlando

  8. Summary • There may be use-cases where a more intelligent selection process can reduce overhead and improve performance (reduce end-to-end delay) • draft-aliahmad-dmm-anchor-selection proposes the following contexts for analyzing the different use-cases: • Mobile node context (how mobile is it? Does it connect through a typical location?) • Application context (what type of flows are generated by the application in the mobile node?) • Network context (what is the load situation on each MA?) • It describes various use-cases that require different selection methods to achieve minimum overhead IETF-86, Orlando

  9. Next Steps • Feedback from the WG is needed on the draft • Are there any additional use-case that come to mind? • What are the additional tools needed to enable a better mobility anchor selection? IETF-86, Orlando

More Related