1 / 10

DMM Framework and Analysis based on Functional Elements draft- liebsch - dmm -framework-analysis

This draft proposes Functional Elements for DMM use cases, decoupled from mobility protocols. It includes analysis, extensions, and design constraints for a flexible DMM solution.

padron
Download Presentation

DMM Framework and Analysis based on Functional Elements draft- liebsch - dmm -framework-analysis

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. DMM Framework and Analysis based on Functional Elementsdraft-liebsch-dmm-framework-analysis M. Liebsch IETF85, Atlanta DMM WG08th November 2012

  2. First Notes • This draft is NAFGAD(Not Another Framework and Gap Analysis Draft) • Draft is based on discussion from Vancouver IETF84 • Draft proposes Functional Entities to enable DMM use cases • Can apply to solutions that are solely based on existing IP mobility protocols • Can apply to solutions which get support from non-mobility protocols

  3. Methodology • Define a set of Functional Entities that enable DMM use cases and IP address continuity • Enable level of indirection and associated control • Enable establishment of MN’s mobility context at MN’s new anchor • Keep these functions decoupled from IP mobility management protocols, but complementary • Apply DMM Functional Entities to architecture components of existing architectures & associated protocols • Mobility protocols, Routing plane in transport network, .. • Analyze, if a DMM function can be accomplished by existing protocol • Identify gap and protocol component to extend

  4. Existing vs. DMM Functional Entities Proxy Mobile IPv6 data FE_R FE_I FE_IEC FE_R FE_E FE_MCTX Local MobilityAnchor FE_MA_C FE_MA_U FE_I: Ingress for DMM indirection FE_E: DMM Egress Function FE_IEC: Control to establish states for DMM indirection FE_MCTX: Function to establish existing MN context in new mobility anchor Interface between FEs BU BA MobileAccess Gateway FE_MU_C FE_MU_U Mobile Node

  5. Existing vs. DMM Functional Entities Mobile IPv6 data FE_R FE_I FE_IEC FE_R FE_E FE_MCTX Home Agent FE_MA_C FE_MA_U FE_I: Ingress for DMM indirection FE_E: DMM Egress Function FE_IEC: Control to establish states for DMM indirection FE_MCTX: Function to establish existing MN context in new mobility anchor Interface between FEs BU BA Mobile Node FE_MU_C FE_MU_U

  6. DMM design constraints • Given Fact:Design constraints have impact to the DMM solution • Transparency of DMM to MN • Simultaneous handling of multiple IP addresses at MN • Multiple vs. Single Mobility Anchor at a time • Consequence:Not all identified DMM Functional Entities may be required • So far two approaches exists for indirection • Forwarding/tunneling from previous anchor through new anchor • Indirection above anchor level

  7. Anchor Centric Model – Mobile IPv6 Home Agent interactionto set up DMM indirection FE_R Example FE_R FE_R FE_I FE_E Current Home Agent Previous Home Agent FE_MCTX FE_MCTX FE_IEC FE_IEC FE_MA_C FE_MA_C FE_MA_U FE_MA_U BU BA FE_MU_C FE_MU_U Mobile Node

  8. MN Centric Model – Mobile IPv6 Mobile Node coordinatesindirection FE_R Example FE_R FE_I FE_R FE_E Current Home Agent Previous Home Agent FE_IEC FE_IEC FE_MA_C FE_MA_C FE_MA_U FE_MA_U BA BU BA BU FE_MCTX Mobile Node FE_MU_C FE_MU_U

  9. Distributed Model – Mobile IPv6 U/C-Plane Split Extended Home AgentControl Function enablesDMM indirection Router in transport network FE_R FE_I Example Home AgentControl Function FE_IEC FE_R FE_MA_C previous Home AgentUser Function current Home AgentUser Function FE_E FE_MCTX FE_E FE_MCTX FE_MA_U FE_MA_U BU BA FE_MU_C FE_MU_U Mobile Node

  10. Concluding & Next • DMM analysis and specification of extensions should be done on a functional level • Enables gap analysis and specification beyond mobility protocol level • Applicable to current analysis drafts and their methodology • top-down / bottom-up • If DMM WG concludes to focus solely on IP Mobility based solutions, consider hooks for external support according to these DMM Functional Entities and reference points • Keep DMM solution extensible • Keep DMM solution deployable

More Related