1 / 27

PMIPv6 에서의 확장 기술

PMIPv6 에서의 확장 기술. Internet Computing Laboratory @ KUT ( http://icl.kut.ac.kr ) Youn-Hee Han. Contents. Why Network-based Mobility Management? Proxy Mobile IPv6 Overview Extension Technologies IPv4 Support PMIPv6 – MIPv6 Interworking Route Optimization Fast Handover NeMo Support

cissy
Download Presentation

PMIPv6 에서의 확장 기술

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. PMIPv6에서의 확장 기술 Internet Computing Laboratory @ KUT (http://icl.kut.ac.kr) Youn-Hee Han

  2. Contents • Why Network-based Mobility Management? • Proxy Mobile IPv6 Overview • Extension Technologies • IPv4 Support • PMIPv6 – MIPv6 Interworking • Route Optimization • Fast Handover • NeMo Support • Mobile Sensor Network Support • Summary IPv6 기술워크샵

  3. Why Network-based? • Host-based Mobile IPv4/v6 (RFC 3344/3775) has not been yet deployed that much. • Why host-based MIP is not deployed yet? • Too heavy specification to be implemented at a small terminal • RFC 3344 (MIPv4): 99 pages • RFC 3775 (MIPv6): 165 pages • Battery problem • Waste of air resource • No Stable MIPv4/v6 stack executed in Microsoft Windows OS IPv6 기술워크샵

  4. Why Network-based? • WLAN switch device starts to provide link specific and proprietary solution for IP handover. • No change in MN protocol stack required! Layer 3 fast secure roaming The solution works by tunneling traffic from the access point to the WLSM through your Layer 3 core network. No changes to the client devices or the underlying infrastructure are required IPv6 기술워크샵

  5. Why Network-based? • IETF NetLMM WG started to standardize a network-based mobility management protocol. • 63th IETF (2005.7) • The first NetLMM BoF • 64th IETF (2005.11) • The second NetLMM BoF • 65th IETF (2006.03) • The first NetLMM WG • 66th,67th,68thIETF (2006.07, 2006.11, 2007.03) • The one of very active WGs in IETF meetings • Almost 150~200 persons usually participates in the NetLMM WG • Operator’s favoritism • Network-based XXX managed by operator itself. • However… the opinions are varying… IPv6 기술워크샵

  6. Why Network-based? • 3GPP, 3GPP2 and WiMAX operators are now showing their STRONG interests for network-based IP mobility solution • They are even now deploying their non-standardized network-based IP mobility solution (not Mobile IPv4/v6!). A message from the chair of netlmm WG “3gpp and 3gpp2 have official liaisons to the IETF. 3gpp2 communicated through an official liaison before our session in San Diego that they would like the IETF to produce a standard for proxy MIP. 3gpp maintains a list of what they would like to see from the IETF and they have also communicated their desire to see a standard for PMIP. The IETF does not have an official liaison relationship with the WiMAX forum. They nonetheless sent a message about what they would like to see and some questions. All this information has already been posted here, on the mailing list.” - Phil and Vidya (March 10, 2007) IPv6 기술워크샵

  7. Proxy MIPv6 Goal • IETF Draft History • S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-00, October 16, 2006. • S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-01, January 5, 2007. • S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), B. Patil (Nokia), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-02, March 5, 2007. • S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), B. Patil (Nokia), “Proxy Mobile IPv6,” draft-ietf-netlmm-proxymip6-00.txt, April 8, 2007. • GOAL • This protocol is for providing mobility support to any IPv6 host within a restricted and topologically localized portion of the network and without requiring the host to participate in any mobility related signaling. IPv6 기술워크샵

  8. Proxy MIPv6 Overview • Proxy Mobile IPv6 Overview LMA: Localized Mobility AgentMAG: Mobile Access Gateway IP Tunnel A IPinIP tunnel LMA and MAG. LMA Home NetworkMN’s Home Network (Topological Anchor Point) MN’s Home Network Prefix (MN-HNP) CAFE:1:/64 MAG1 Host A LMA Address (LMAA) That will be the tunnel entry-point. LMM (Localized Mobility Management)Domain MAG2 MN’s Home Network Prefix (MN-HNP) CAFE:2:/64 Proxy Binding Update (PBU) Control message sent out by MAG to LMA to register its correct location Host B MN Home Address (MN-HoA) MN continues to use it as long as it roams within a same domain Proxy Care of Address (Proxy-CoA) The address of MAG. That will be the tunnel end-point. IPv6 기술워크샵

  9. Proxy MIPv6 Overview • No host stack change for IP mobility • Avoiding tunneling overhead over the air • Re-use of Mobile IPv6 • PMIPv6 is based on Mobile IPv6 [RFC3775]. • Mobile IPv6 is a very mature mobility protocol for IPv6. • Reuse of Mobile IPv6’s home agent functionality and the messages/format used in mobility signaling. • Numerous Mobile IPv6 enhancement can be re-used. • PMIPv6 provides solution to a real deployment problem. • Only supports Per-MN-Prefix model • Unique home network prefix assigned for each MN. • The prefix follows the MN. IPv6 기술워크샵

  10. internet IPv4/IPv6 IPv4 Support • R. Wakikawa (Keio Univ.), S. Gundavelli (Cisco), “IPv4 Support for Proxy Mobile IPv6”, draft-ietf-netlmm-pmip6-ipv4-support-00.txt, May 2007 • PMIPv6 will support IPv4 Access Network may be IPv4, Private IPv4, IPv6, or Both IPv4 and IPv6 - Dual Stack entity - IPv4&IPv6 Enabled MAG LMA MN IPv4 only, IPv6 only, or Dual Stack - Dual Stack entity - IPv4&IPv6 Enabled Transport network can be IPv4 only, IPv6 only or DS • - A separated RFC will be published for extending IPv4 support to the Proxy Mobile IPv6 • It will includes • 1) IPv4 Home Address Mobility 2) IPv4 Transport Network Support • - The signaling protocol is based on Proxy Mobile IP6. IPv6 기술워크샵

  11. IPv4 Support • Leveraging the existing Dual Stack Mobile IPv6 (DSMIPv6) protocol • Hesham Soliman (Ed.), “Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)”, draft-ietf-mip6-nemo-v4traversal-04.txt, March, 2007 CN HA Tunneled to IPv6 CoA IPv4 Packet v4 Network • - Dual Stack MN (or Mobile Router) • It has only MIPv6 (not MIPv4) to manage mobility. • - Two mobility protocols are needless. • Extensions are defined for BU and BAck v6 Network Movement Tunneled to IPv4 CoA IPv6 Packet CN v4 Network v6 Network NAT Tunneled to private IPv4 CoA Private v4 Network Movement IPv6 기술워크샵

  12. IPv4 Support • PMIPv6’s IPv4 Support by using DSMIPv6 proposal • When MN moves to an IPv6 network IPv6 header (src=LMA_ADDR, dst=MAG_ADDR) Mobility header - Proxy BAck [P flag is set] Mobility Option - Home Network Prefix (MN IPv6 Home Address) - Timestamp Option - MN IPv4 Home Address Ack. Option - IPv4 Default Router Address Option IPv6 header (src=MAG_ADDR, dst=LMA_ADDR) Mobility header - Proxy BU [P flag is set] Mobility Option - Home Network Prefix (MN IPv6 Home Address) - Timestamp Option - MN IPv4 Home Address Option Proxy Binding Update IPv6 binding cache entry LMA MN MAG MN’s IPv6 HoA MAG_ADDR (IPv6) IPv4 binding cache entry MN’s IPv4 HoA MAG_ADDR (IPv6) IPv6 header (src=LMA_ADDR, dst=MAG_ADDR) IPv6 header (src=CN_ADDR, dst=MN_ADDR) Paylaod IPv6 header (src=MAG_ADDR, dst=LMA_ADDR) IPv6 header (src=MN_ADDR, dst=CN_ADDR) Payload IPv6 Data Traffic IPv6 header (src=LMA_ADDR, dst=MAG_ADDR) IPv4 header (src=CN_V4ADDR, dst=MN_V4ADDR) Paylaod IPv6 header (src=MAG_ADDR, dst=LMA_ADDR) IPv4 header (src=MN_V4ADDR, dst=CN_V4ADDR) Payload IPv4 Data Traffic IPv6 기술워크샵

  13. IPv4 Support • PMIPv6’s IPv4 Support by using DSMIPv6 proposal • When MN moves to a Public IPv4 network IPv4 header (src=MAG_V4ADDR, dst=LMA_V4ADDR) UDP header IPv6 header (src=LMA_ADDR, dst=MAG_ADDR) Mobility header - Proxy BAck [P flag is set] Mobility Option - Home Network Prefix (MN IPv6 Home Address) - Timestamp Option - MN IPv4 Home Address Ack. Option IPv4 header (src=MAG_V4ADDR, dst=LMA_V4ADDR) UDP header IPv6 header (src=MAG_ADDR, dst=LMA_ADDR) Mobility header - Proxy BU [P flag is set] Mobility Option - Home Network Prefix (MN IPv6 Home Address) - Timestamp Option - MN IPv4 Home Address Option Proxy Binding Update IPv6 binding cache entry LMA MN MAG MN’s IPv6 HoA MAG_V4ADDR IPv4 binding cache entry MN’s IPv4 HoA MAG_V4ADDR IPv4 header (src=LMA_V4ADDR, dst=MAG_V4ADDR) IPv6 header (src=CN_ADDR, dst=MN_ADDR) Payload IPv4 header (src=MAG_V4ADDR, dst=LMA_V4ADDR) IPv6 header (src=MN_ADDR, dst=CN_ADDR) Payload IPv6 Data Traffic IPv4 header (src=LMA_V4ADDR, dst=MAG_V4ADDR) IPv4 header (src=CN_V4ADDR, dst=MN_V4ADDR) Payload IPv4 header (src=MAG_V4ADDR, dst=LMA_V4ADDR) IPv4 header (src=MN_V4ADDR, dst=CN_V4ADDR) Payload IPv4 Data Traffic IPv6 기술워크샵

  14. IPv4 Support • PMIPv6’s IPv4 Support by using DSMIPv6 proposal • When MN moves to a Private IPv4 network IPv4 header (src=MAG_V4ADDR, dst=LMA_V4ADDR) UDP header IPv6 header (src=LMA_ADDR, dst=MAG_ADDR) Mobility header - Proxy BAck [P flag is set] Mobility Option - Home Network Prefix (MN IPv6 Home Address) - Timestamp Option - MN IPv4 Home Address Ack. Option - NAT Detection Option IPv4 header (src=MAG_V4ADDR, dst=LMA_V4ADDR) UDP header IPv6 header (src=MAG_ADDR, dst=LMA_ADDR) Mobility header - Proxy BU [P flag is set] Mobility Option - Home Network Prefix (MN IPv6 Home Address) - Timestamp Option - MN IPv4 Home Address Option Proxy Binding Update IPv6 binding cache entry IPv4 NAT LMA MN MAG MN’s IPv6 HoA MAG_V4ADDR IPv4 binding cache entry MN’s IPv4 HoA MAG_V4ADDR IPv4 header (src=LMA_V4ADDR, dst=MAG_V4ADDR) UDP header IPv6 header (src=CN_ADDR, dst=MN_ADDR) Payload IPv4 header (src=MAG_V4ADDR, dst=LMA_V4ADDR) UDP header IPv6 header (src=MN_ADDR, dst=CN_ADDR) Payload IPv6 Data Traffic IPv4 header (src=LMA_V4ADDR, dst=MAG_V4ADDR) UDP header IPv4 header (src=CN_V4ADDR, dst=MN_V4ADDR) Payload IPv4 header (src=MAG_V4ADDR, dst=LMA_V4ADDR) UDP header IPv4 header (src=MN_V4ADDR, dst=CN_V4ADDR) Payload IPv4 Data Traffic IPv6 기술워크샵

  15. IPv4 Support – Open Issues • IPv4 NAT’s location • Current spec. discusses the case that NAT resides between MAG and LMA. • More Consideration about NAT’s location • NAT and MAG Coexistence • NAT between MN and MAG IPv6 기술워크샵

  16. PMIPv6 and MIPv6 Interworking • V. Devarapalli (Azaire Network), S. Gundavelli (Cisco), K. Chowdhury (Starent Networks), A. Muhanna (Nortel), “Proxy Mobile IPv6 and Mobile IPv6 Interworking”, draft-devarapalli-netlmm-pmipv6-mipv6-00.txt, April 2007. • PMIPv6 is typically used for localized mobility management and MIPv6 is applied for global mobility management. • In case of intra-domain movement • the MN and MIPv6 HA are not aware of the movement. • In case of inter-domain movement • It acquires a new MN-HoA in the new domain • It treats the new MN-HoA as the CoA of MIPv6. • It treats the previous MN-HoA as the HoA of MIPv6. • MN sends MIPv6 binding update with the pair (New MN-HoA, Prev. MN-HoA). IPv6 기술워크샵

  17. Case #1. MN in a Home Domain PMIPv6 Domain #2 PMIPv6 Domain #3 MIPv6-Home Agent = LMA #1 Binding Cache MAG #1-1 MAG #1-2 HoA CoA Proxy Flag MN-HoA #1 MAG#1-1’s Addr. 1 Proxy BU In the interior of MN, MIPv6-CoA is not needed since all MAGs will emulate the home link. PMIPv6 Domain #1(Mobile IPv6 Home Domain) MIPv6-HoA = MN-HoA #1 IPv6 기술워크샵

  18. Case #2. Movement in a Home Domain PMIPv6 Domain #2 Non-PMIPv6 Domain MIPv6-Home Agent = LMA #1 Binding Cache MAG #1-1 MAG #1-2 HoA CoA Proxy Flag MN-HoA #1 MAG#1-2’s Addr. 1 Proxy BU In the interior of MN, MIPv6-CoA is still not needed since all MAGs will emulate the home link. PMIPv6 Domain #1(Mobile IPv6 Home Domain) PMIPv6 is operated! Still… MIPv6-HoA = MN-HoA #1 IPv6 기술워크샵

  19. Case #3. MN moves to a new domain • MN maintains two addresses • - MIPv6-HoA = MN-HoA #1 • MIPv6-CoA = MN-HoA #2 Both MIPv6 and PMIPv6 are operated! MN obtains MN-HoA #2 MAG #2-1 Binding Cache HoA CoA Proxy Flag Proxy BU MN-HoA #2 MAG#2-1’s Addr. 1 MIPv6 BU LMA #2 MAG #2-2 PMIPv6 Domain #2 Non-PMIPv6 Domain MIPv6-Home Agent = LMA #1 Binding Cache HoA CoA Proxy Flag MN-HoA #1 MN-HoA #2 0 PMIPv6 Domain #1(Mobile IPv6 Home Domain) IPv6 기술워크샵

  20. Case #4. Intra-domain Movement Just PMIPv6 is operated! • MN still maintains two addresses • - MIPv6-HoA = MN-HoA #1 • MIPv6-CoA = MN-HoA #2 MAG #2-1 Binding Cache HoA CoA Proxy Flag MN-HoA #2 MAG#2-2’s Addr. 1 LMA #2 Proxy BU MAG #2 PMIPv6 Domain #2 Non-PMIPv6 Domain MIPv6-Home Agent = LMA #1 Binding Cache HoA CoA Proxy Flag MN-HoA #1 MN-HoA #2 0 PMIPv6 Domain #1(Mobile IPv6 Home Domain) IPv6 기술워크샵

  21. Case #5. MN moves to a new domain without net-based mobility management • PMIPv6 is NOT operated! • Just MIPv6 is operated. • MN obtains a normal CoA, CoA #1 • MN maintains two addresses • - MIPv6-HoA = MN-HoA #1 • MIPv6-CoA = CoA #1 AR #1 MIPv6 BU A Normal Gateway AR #2 PMIPv6 Domain #2 Non-PMIPv6 Domain MIPv6-Home Agent = LMA #1 Binding Cache HoA CoA Proxy Flag MN-HoA #1 CoA #1 0 PMIPv6 Domain #1(Mobile IPv6 Home Domain) IPv6 기술워크샵

  22. Case #6. Intra-domain Movement in the domain • Just MIPv6 is operated. • MN again obtains a normal CoA, CoA #2 • MN maintains two addresses • - MIPv6-HoA = MN-HoA #1 • MIPv6-CoA = CoA #2 AR #1 A Normal Gateway AR #2 MIPv6 BU PMIPv6 Domain #2 Non-PMIPv6 Domain MIPv6-Home Agent = LMA #1 Binding Cache HoA CoA Proxy Flag MN-HoA #1 CoA #2 0 PMIPv6 Domain #1(Mobile IPv6 Home Domain) IPv6 기술워크샵

  23. Case #7. Returning to Home PMIPv6 Domain #2 Non-PMIPv6 Domain Both MIPv6 and PMIPv6 are operated. MN sends a de-registration MIPv6 BU. MAG sends PMIPv6 PBU. MIPv6-Home Agent = LMA #1 Binding Cache MAG #1-1 MAG #1-2 HoA CoA Proxy Flag MN-HoA #1 MAG#1-2’s Addr. 1 Proxy BU MIPv6 BU (lifetime=0) PMIPv6 Domain #1(Mobile IPv6 Home Domain) IPv6 기술워크샵

  24. PMIPv6 and MIPv6 Interworking - Issues • possible race condition between PMIP registration and MIP registration • this is because the PBU and the BU are sent by different entities (MAG and MN) • this is different from the HMIPv6/MIPv6 scenario since in the latter case the MN is responsible of sending both registration messages • MIPv6 terminals and PMIPv6 terminals in the same network • The issue seems to be solvable at system-level • HoA management and lookup key in BC • in MIPv6, the HoA is the lookup key in the BC • MN does not include any MN-ID in the BU based on standard rfc3775 • in PMIPv6, the HoA may not even be present (based on the per-MN prefix model) and either MN-ID or the network prefix is the lookup key IPv6 기술워크샵

  25. HA1(LMA) HA1(LMA1) HA2(LMA2) CN PMIP Network PMIP Network AR(MAG1) AR(MAG1) AR(MAG2) MN MN CN Scenario 2 CN behind MAG Scenario 1 MIP6 enabled CN Route Optimization in PMIPv6 • A. Qin (Huawei), A. Huang (Huawei), W. Wu (Huawei), B. Sarikaya (Huawei), “PMIPv6 Route Optimization Protocol”, draft-qin-mipshop-pmipro-00.txt, Feb. 2007. • PMIPv6 uses indirect routing via HA • Type 1 CNs • MIPv6 corresponding node functionality enabled, not behind PMIPv6 ‘MAG’ • Type 2 CNs • MNs behind PMIPv6 ‘MAG’ IPv6 기술워크샵

  26. Fast Handover in PMIPv6 • F. Xia (Huawei), B. Sarikaya (Huawei), ”Mobile Node Agnostic Fast Handovers for Proxy Mobile IPv6”, draft-xia-netlmm-fmip-mnagno-00.txt, Feb. 2007 Reactive Mode Predictive Mode IPv6 기술워크샵

  27. Summary • PMIPv6 is New Idea? • Absolutely No!, but new trend!. It’s a turn for the better! • PMIPv6 is a good example of compromise • 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! • More Studies Needed • Route Optimization in PMIPv6 • Fast Handover in PMIPv6 • PMIPv6 over IEEE 802.16/WiBro (Cross-layering Issues) • New Research Areas using PMIPv6 • Network-based Global Mobility • PMIPv6-based NeMo (MANEMO) • PMIPv6-based 6LowPAN Sensor Node Mobility IPv6 기술워크샵

More Related