1 / 26

NETLMM 및 IETF 이동성기술 표준화 동향

NETLMM 및 IETF 이동성기술 표준화 동향. Internet Computing Laboratory @ KUT ( http://icl.kut.ac.kr ) Youn-Hee Han. Outline. Background 67 th IETF Activities PMIPv6 vs. NetLMM DT (Design Team) Solution NetLMM DT Solution PMIPv6 - Proxy Mobile IPv6 PMIPv6 Features PMIPv6 Procedures and Operations

koko
Download Presentation

NETLMM 및 IETF 이동성기술 표준화 동향

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. NETLMM 및 IETF 이동성기술 표준화 동향 Internet Computing Laboratory @ KUT (http://icl.kut.ac.kr) Youn-Hee Han

  2. Outline • Background • 67th IETF Activities • PMIPv6 vs. NetLMM DT (Design Team) Solution • NetLMM DT Solution • PMIPv6 - Proxy Mobile IPv6 • PMIPv6 Features • PMIPv6 Procedures and Operations • Conclusions NetLMM: Network-based Localized Mobility Management Network-based Mobility

  3. Background • Host-based Mobile IPv4/v6 (RFC 3344/3775) has not been yet deployed that much. • Why host-based MIP is not deployed yet? • Waste of air resource • Too heavy specification to be implemented at a small terminal • Battery problem • WLAN switch device starts to provide link specific and proprietary solution for IP handover. • 3GPP2 and WiMAX operators are now deploying their non-standardized network-based Mobile IPv4 (not Mobile IPv4!). • Operator’s favoritism • Network-based XXX managed by operator itself. • IETF NetLMM WG started to standardize a network-based mobility management protocol. Network-based Mobility

  4. Background • Host-based vs. Network-based Mobility HA HA Route Update Route Update AR AR Movement Movement Network-based Mobility Host-based Mobility Network-based Mobility

  5. 67th IETF Activities • Before 67th IETF Meeting (Nov. 5~10, 2006) • IETF MIPv6 WG • Proxy Mobile IPv6 • draft-sgundave-mipv6-proxymipv6 • draft-chowdhury-netmip6-01 • IETF NetLMM WG • DT (Design Team) Solution • draft-giaretta-netlmm-dt-protocol • draft-akiyoshi-netlmm-protocol • draft-giaretta-netlmm-protocol • draft-gundavelli-netlmm-mip6-proxy • draft-raman-netlmm-protocol • draft-templin-autoconf-netlmm-dhcp • draft-vidya-netlmm-netmob • draft-wanghui-netlmm-protocol • DHCP-based solution • draft-templin-autoconf-netlmm-dhcp • In MIPv6/NetLMM WG mailing list, so much mailing discussion!!! Network-based Mobility

  6. 67th IETF Activities • During 67th IETF Meeting • IETF NetLMM WG • Proxy Mobile IPv6 • draft-sgundave-mipv6-proxymipv6 (First Author – Cisco) [1] • draft-chowdhury-netmip6-01 (First Author – Starent Networks) [2] • DT (Design Team) Solution • draft-giaretta-netlmm-dt-protocol (First Author – Ericsson) [3] • DHCP-based solution • draft-templin-autoconf-netlmm-dhcp (First Author – Boeing) [4] • Before voting, there are already many input from other SDOs • 3GPP2 Correspondence to IETF on NetLMM WG • “3GPP2 has made a decision to use the Proxy Mobile IP concept as a network based mobility management solution.” • Voice of a person from WiMAX • “WiMAX adopted PMIP. PLEASE make it standardized in IETF.” Network-based Mobility

  7. 67th IETF Activities • Voting Results • Vote 1: NETLMM WG should adopt more than one draft. • Overwhelming support against  Just one solution! • Vote 2: Which one is our solution? • A Proxy MIPv6, [1] or [2]: 45 peoples  So, PMIP is selected! • DT Solution, [3]: 30 peoples • DHCP-based Solution, [4]: 10 peoples • Vote 3: Then, which PMIP is adopted as a starting point? • [1]: 18 peoples • [2]: 7 peoples • Abstain and wait: 28 peoples  Harmonize! Network-based Mobility

  8. PMIPv6 vs. NetLMM • PMIPv6 vs. NetLMM DT Solution • Global Mobility vs. Local Mobility • RFC 3775 MIPv6 Re-use vs. new design • Signaling messages • Mobility Header vs. UDP messages • IP Protocol dependency • PMIP • PMIPv4 • No standardized specification. But it is already deployed by CISCO • PMIPv6 • NetLMM makes its protocol general so that both IPv4 and IPv6 are supported • Other SDO’s favoritism • Advocate PMIP and be hostile to NetLMM DT Solution Network-based Mobility

  9. NetLMM DT Solution • Introduction • H. Levkowetz (Ericsson), G. Giaretta (Telecom Italia), K. Leung (Cisco), M. Liebsch (NEC), P. Roberts (Motorola), K. Nishida (NTT DoCoMo), H. Yokota (KDDI Labs), M. Parthasarathy (Nokia), "The NetLMM Protocol,", draft-giaretta-netlmm-dt-protocol-02, Oct. 2006. • It is not assumed that a MAG is associated with only a single LMA • MN has NetLMM address anchored at LMA, which advertises the NNP via routing protocol. • Routing for IP address is established between MAG and LMA. • MN can move between MAGs using the same NetLMM address for data communications Mobility Access Gateway (MAG) Local Mobility Anchor (LMA) NetLMM Network Prefix (NNP) Network-based Mobility

  10. NetLMM DT Solution • Two Group of New Messages • Group 1: Basic Mobility Support • Location Registration/Ack • Location Deregistration/Ack • Group 2: Support for maintaining and managing association and connectivity between LMAs and MAGs • Association Request/Ack • Disassociation Request/Ack • Heartbeat/Ack Network-based Mobility

  11. NetLMM DT Solution • Network Entry Support If MAG obtains the prefix for the MN first (e.g., via DHCP response), MAG transfer it. LMA creates forwarding state for packets based on the prefix MAG creates forwarding state for packets based on the prefix Network-based Mobility

  12. NetLMM DT Solution • Mobility Support The entry related to MN ID exists in Routing Cache, it means that a MAG to MAG handover has occurred Prefix options SHOULD be included in ACK. MAG deletes the entry related to the MN ID from its Routing Cache MAG deletes forwarding state for packets based on the prefix Network-based Mobility

  13. NetLMM DT Solution • MAG and LMA Association All possible methodse.g., IPv6-in-IPv6 Only one method MAG updates the forwarding method to the one indicated in the ACK LMA marks related MN entries in its Routing Cache as unroutable MAG marks related MN entries in its Routing Cache as unroutable Network-based Mobility

  14. NetLMM DT Solution • Data Transport MAG CN MN LMA MN sends a packet to CN TTL is decremented after the original packet is decapsulated MAG forwards to LMA TTL is decremented before the original packet is encapsulated LMA sends to CN CN sends packet to MN LMA forwards to MAG TTL is decremented before the original packet is encapsulated MAG sends to MN TTL is decremented after the original packet is decapsulated Network-based Mobility

  15. NetLMM DT Solution • Link-local Multicast Traffic MAG CN MN LMA MN sends link-local multicast packets Packets are processed by MAG. They are never forwarded to LMA Network-based Mobility

  16. Proxy MIPv6 • Introduction • S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-00, October 16, 2006 • GOAL • This protocol is for enabling any IPv6 host to achieve protocol mobility without requiring the host to participate in any mobility related signaling. • Advantages • No host stack change for IP mobility • Avoiding tunneling overhead over the air Network-based Mobility

  17. Proxy MIPv6 • Re-use of Mobile IPv6 • PMIPv6 is based on Mobile IPv6 [RFC3775]. • Mobile IPv6 is a very mature mobility protocol for IPv6. • Numerous Mobile IPv6 enhancement can be re-used. • PMIPv6 allows the same Home Agent to provide mobility to hosts that do not use any mobility management protocol as well as hosts that use Mobile IPv6. • PMIPv6 provides solution to a real deployment problem. Network-based Mobility

  18. Proxy MIPv6 • Home in Any Place • MN will always obtain its “home-address”, any where in the network. • The access router will emulate the home link on its access link. • It will ensure that MN believes it is at its home. • A new function, Proxy Mobile Agent, that runs on the access router is required for this scheme to work. Network-based Mobility

  19. Proxy MIPv6 • Proxy Mobile IPv6 Overview Mobile IP Tunnel A IPinIP tunnel HA and PMA. Home NetworkMN’s Home Network (Topological Anchor Point) Home Agent Prefix CAFÉ::/64 PMA2 Host D PMA1 LMM Network Access Router C Proxy Binding Update (PBU) Control message sent out by PMA to HA to register its correct location Host Prefix BABA::/64 Care of Address (CoA) The address of the Proxy Mobile Agent. That will be the tunnel end-point. Network-based Mobility

  20. Proxy MIPv6 • Network Entry Procedure • MN moves and attaches to an access router • After access authentication, access router (Proxy Mobile Agent, PMA) identifies MN • PMA obtains MN’s profile containing the Home Address ..etc • PMA sends the Proxy Binding Update on behalf of MN • PMA sends Router Advertisements containing MN’s home network prefix • Stateless Case • MN will still configure (or maintain) the same as its home address. • Stateful Case: • the network will ensure that it always gets its home address. Network-based Mobility

  21. Proxy MIPv6 • Home Agent Operation (1/2) • The home agent needs to understand the Proxy Registration. • It needs to accept Proxy registrations from certain trusted network entities. • It has to modify the typical 3775 trust model to support Proxy Model. Proxy Binding Update Proxy Binding Acknowledgement Network-based Mobility

  22. Proxy MIPv6 • Home Agent Operation (2/2) • HA-MN tunnel is a shared tunnel among many MNs. • 1:1 relation  m:1 relation • One tunnel is associated to multiple BCE. • Life-time of a tunnel should not be dependent on the life time of any single BCE. • Home Agent will add host/prefix routes to the mobile home address/prefix over the tunnel. Network-based Mobility

  23. Proxy MIPv6 • Proxy Mobile Agent Operation • It emulates the home link for eachMN. • After the access authentication, PMA will obtain MN’s profile which contains: • MN’s home address • home network prefix • home agent address ..etc. • PMA sends a Proxy Binding Update to MN’s home agent. • It establishes a IPv6/IPv6 tunnel with its home agent. • All the packets from MN are reverse tunneled to its home agent • All the packets from the tunnel are routed to MN. Network-based Mobility

  24. Proxy MIPv6 • Mobile Node Operation • Any MN is just a IPv6 host with its protocol operation consistent with the base IPv6 specification. • All aspects of Neighbor Discovery Protocol will not change. • When MN attaches to a new AR, it receives a Router Advertisement message from the AR with its home prefix. • Throughout the PMIP domain, MN using DHCP procedure or in stateless address configuration mode, will obtain the same home address. Network-based Mobility

  25. Proxy MIPv6 • Call Flow Network-based Mobility

  26. Conclusions • PMIP is New Idea? • Absolutely No! • Not new idea, but new trend!. It’s a turn for the better! • Until now, long confrontation • Telecommunication Operators  Internet Developers and Users • PMIP is a good example of compromise • It is still RFC 3775 MIP-based one. • But, it follows telco’s favoritism! Network-based Mobility

More Related