1 / 24

IPv6 이동성기술 표준화 동향 - 네트워크 기반 이동성 관리 기술 중심 -

IPv6 이동성기술 표준화 동향 - 네트워크 기반 이동성 관리 기술 중심 -. Youn-Hee Han yhhan@kut.ac.kr Korea University of Technology and Education Laboratory of Intelligent Networks http://link.kut.ac.kr 2010.08.31. IETF Core Standards for IP Mobility Management. [ 관련 WG: MEXT, MIPSHOP, NETEXT - 2010 년 8 월 현재 ].

keenan
Download Presentation

IPv6 이동성기술 표준화 동향 - 네트워크 기반 이동성 관리 기술 중심 -

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. IPv6 이동성기술 표준화 동향- 네트워크 기반 이동성 관리 기술 중심- Youn-Hee Han yhhan@kut.ac.kr Korea University of Technology and EducationLaboratory of Intelligent Networks http://link.kut.ac.kr 2010.08.31

  2. IETF Core Standards for IP Mobility Management [관련 WG: MEXT, MIPSHOP, NETEXT- 2010년 8월 현재] Host-based IP Mobility Network-basedIP Mobility Mobility Support in IPv6 [RFC 3775, June 2004] Hierarchical Mobile IPv6 [RFC 4140, Aug. 2005] Mobile IPv6 Support for Dual Stack Hosts and Routers [RFC 5555, June 2009] Fast Handovers for Mobile IPv6 [RFC 4068, July 2005] Multiple Care-of Addresses Registration [RFC 5648, Oct. 2009] Flow Bindings in Mobile IPv6 and NEMO Basic Support [draft-ietf-mext-flow-binding-14] Traffic Selectors for Flow Binding [draft-ietf-mext-binary-ts-04] Proxy Mobile IPv6 [RFC 5213, Aug. 2008] IPv4 Support for Proxy Mobile IPv6 [RFC 5844, May 2010] Fast Handovers for Proxy Mobile IPv6 [draft-ietf-mipshop-pfmipv6-14] Logical Interface Support for multi-mode IP Hosts [draft-melia-netext-logical-interface-support-01] Multiple Care-of Addresses Registration & Flow Bindings in Proxy Mobile IPv6 [draft-bernardos-netext-pmipv6-flowmob-00] Horizontal Handover A handover is initiated when mobile device exits the boundaries of an administrative domain. Single interface is used. Vertical Handover A mobile device does need to move in order to initiate a handover. Multiple interfaces are required, but use one interface at a time. Complexity Level Multiple Interface Management Simultaneous use of multiple interfaces and access networks. Association of an application with an interface Multiple Flow Management Ability to split individual flows between links with respect to the requirements of the flows and the user preferences

  3. MIPv6/DSMIPv6 Deployment • Host-based IP Mobility (MIPv4/MIPv6/DSMIPv6) has not been widely deployed due to several factors • Implementation issues • IPsec and IKEv1 • Too heavy specification to be implemented at a small terminal • RFC 3344 (MIPv4): 99 pages, RFC 3775 (MIPv6): 165 pages • Deployment issues • Negligible deployment of IPv6 • No stable MIPv4/v6 stack executed in Microsoft Windows OS • Operational issues • Battery problem • Layer 3 signalling via radio link  waste of air resource • Layer 8 issues (Financial/Human/Political/FUD/…) • Many operators elected to create their own protocols (eg. GTP), or They picked other IETF mobility protocols (Proxy MIP etc.) • Money!

  4. Recent IETF Activity of Host-based IP Mobility • Criticism about Mobile IPv6 • Create “Simplified Mobile IPv6” (?) “Several SDOs have considered MIP6 and DSMIP6 as a solution for interworking and mobility between different access technologies and only 3GPP has adopted it in a very limited manner for Rel 8 (for use on the S2c interface) with the likelihood of it being actually deployed quite low (IMO).” - IETF MEXT WG chair (2010.03.04) “My opinion as a result of implementation experience is that MIP6/DSMIP6 can be significantly simplified, especially the security architecture.” - IETF MEXT WG chair (2010.03.04)

  5. Proxy Mobile IPv6 (PMIPv6) • Proxy Mobile IPv6 [IETF RFC 5213, August 2008] LMA: Localized Mobility AgentMAG: Mobile Access Gateway IP Tunnel IP-in-IP tunnel between LMA and MAG LMA Home Network MN’s Home Network (Topological Anchor Point) MAG LMA Address (LMAA) That will be the tunnel entry-point LMM (Localized Mobility Management)Domain MAG movement Proxy Binding Update/Ack. (PBU/PBA) Control messages exchanged by MAG to LMA to establish a binding between MN-HoA and Proxy-CoA MN’s Home Network Prefix (MN-HNP) CAFE:2:/64 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

  6. PMIPv6 Operation Flow PBU: Proxy Binding UpdatePBA: Proxy Binding Ack. • RA*: MN의 Prefix를 Policy Store에서 수신한 경우의 Router Advertisement • RA**: MN의 Prefix를 LMA에서 수신한 경우의 Router Advertisement MN MAG AAA&Policy Store LMA CN MN Attachment AAA Query with MN-ID AAA Reply with Profile RA* PBU with MN-ID, Home Network Prefix option, Timestamp option PBA with MN-ID, Home Network Prefix option RA** Tunnel Setup Optional DHCP Server DHCP Request DHCP Request DHCP Response DHCP Response [MN-HoA:CN](data) [Proxy-CoA:LMAA][MN-HoA:CN](data) [MN-HoA:CN](data)

  7. PMIPv6 Features • Home in Any Place • MAG sends the RA (Router Advertisement) messages advertising MN’s home network prefix and other parameters • MAG will emulate the home link on its access link. • RA Unicast • RA should be UNICASTed to an MN • It will contain MN’s Home Network Prefix • Per-MN Prefix • Any MN is just a IPv6 host • Any MN is just a IPv6 host with its protocol operation consistent with the base IPv6 specification. • M:1 Tunnel • LMA-MAG tunnel is a shared tunnel among many MNs. • One tunnel is associated to multiple MNs’ Binding Caches.

  8. PMIPv6 in 3GPP LTE/EPC Proxy Mobile IPv6 over LTE AAA/Policy Server Ref.] I. Guardini et al., “Mobile IPv6 deployment opportunities in next generation 3GPP networks,” 16th IST Mobile&Wireless Communication Summit, Budapest, Hungary 1-5, July 2007 GTP-U Tunnel IP-in-IP Tunnel UE eNodeB S-GW/(MAG) P-GW/LMA P-GW: access gateway towards Packet Data Networks (similar to the GGSN) Optional! - PMIPv6 will be mainly used for inter-system handovers (i.e. handovers between 3GPP and non-3GPP accesses)

  9. PMIPv6 in 3GPP LTE/EPC • Proxy Mobile IPv6 over LTE • Vertical handover scenario LMA LMA

  10. WiBro IP Network Cellular IP network Dual Stack Support in PMIPv6 • Dual-Stack Support in Proxy MIPv6 • IPv4 Support for Proxy Mobile IPv6 [RFC 5844, May 2010] • PMIPv6 기반 IPv6/IPv4 Transport 지원 + IPv6/IPv4 Home Address Mobility 지원 • DS-MIPv6와 같은 설계 목표와 원칙 • DS(Dual Stack)-PMIPv6가 고려하는 시나리오 IPv4 Application(VoD, IP-Phone…) RAS DS-PMIPv6LMA MN IPv4 DS-PMIPv6MAG IPv4 LTE BS IPv6 DS-PMIPv6MAG WLANIP Network IPv6 NAT Private IPv4 AAA WLAN AP DS-PMIPv6MAG IPv6 Application(VoD, IP-Phone…)

  11. Operation of DS-PMIPv6 • PMIPv6’s Dual-Stack Support [Mobility Binding] HoAv4 and HoAv6 PBU (HoAv6, Proxy CoAv6, HoAv4) Proxy CoAv6 Dual Stack MNor IPv4 MN IPv4 traffic CNv4  HoAv4 IPv6 Tunnel (LMAAv6Proxy CoAv6) IPv6 traffic CNv6->HoAv6 Dual Stack MAG Only-IPv6 enabled (Proxy CoAv6) Dual Stack LMA Only-IPv6 enabled (LMMAv6) <MN in IPv6 domain> [Mobility Binding] HoAv4 and HoAv6 PBU (HoAv6, Proxy CoAv4, HoAv4) Dual Stack MNor IPv4 MN Proxy CoAv4 IPv4 traffic CNv4  HoAv4 IPv4 Tunnel (LMAAv4Proxy CoAv4) IPv6 traffic CNv6->HoAv6 Dual Stack MAG Only-IPv4 enabled (Proxy CoAv4) Dual Stack LMA Only-IPv4 enabled (LMAAv4) <MN in IPv4 domain>

  12. DS-PMIPv6 테스트베드-1 v4/v6 VoD Server CN eth1) 192.168.2.1 3ffe:2::1/64 ETRI (2007,2008) LMA V4/V6 network MN has Dual Stack and both addresses are always enabled eth0) 192.168.2.2 3ffe:2::2/64 LMA가 MN에게 할당할 Prefix Pool 3ffe:1:3:1::/64 ~ 3ffe:1:3:ffff::/64 eth0) 192.168.1.1 3ffe:1::1/64 NAT 192.168.1.3 Private V4 network V6 network eth0) 10.0.0.1 MAG3 V4 network eth0) 3ffe:1::2/64 MAG1 eth0) 192.168.1.2 MAG2 ra0) 10.0.1.1 3ffe:1:3::1/64 fe80::1 ra0) 192.168.101.1 3ffe:1:1::1/64 fe80::1 ra0) 192.168.102.1 3ffe:1:2::1/64 fe80::1 SSID: PMIP3 SSID: PMIP1 SSID: PMIP2 초기 실행: v4 VoD Client 초기 실행: v6 VoD Client

  13. Subnet 4 VoD (PC4) 192.168.4.1 192.168.4.2 LMA (PC0) 192.168.3.1 192.168.1.1 192.168.3.2 192.168.1.2 802.11g 802.11a NAT2 NAT1 10.0.1.1 10.0.2.1 10.0.1.1 10.0.1.2 10.0.2.2 10.0.1.2 Subnet 1 Subnet 2 Subnet 3 MAG1 (PC1) MAG2 (PC2) MAG3 (PC3) 10.0.101.1 10.0.102.1 10.0.101.1 192.168.5.1 192.168.5.2 192.168.5.1 192.168.5.1 Notebook1 Notebook1 Notebook2 Notebook1 DS-PMIPv6 테스트베드-2 KT (2007): DS-PMIPv6 with Only Private IPv4 Network and IPv4 Application

  14. Test: MIPv6 vs. PMIPv6 • Test Results with Heavy Traffic (presented at MobiWorld 2008 conference) • Encoding Rate: 2Mbps UDP Throughput of MIPv6 UDP Throughput of PMIPv6

  15. PMIPv6 Handover Optimization • 네트워크 기반의 IP Handover 기술 및 최적화 • Basic Standard • ProxyMobile IPv6 (PMIPv6) – RFC 5213 • Base Protocol • IETF의 네트워크 기반 핸드오버 최적화 기술 • Fast Handovers for Proxy Mobile IPv6 (F-PMIPv6) • draft-ietf-mipshop-pfmipv6-14.txt (May 2010) • 핸드오버시 라우터간 터널링 기술 • Transient Binding for Proxy Mobile IPv6 (TB-PMIPv6) • draft-ietf-mipshop-transient-bce-pmipv6-05.txt (Jan 2010) • Make-before-break 핸드오버시 두 개의 인터페이스를 동시에 사용할 수 있는 기술 MD (필요없음), DAD (생략가능), Network-based BU L2 handover [PMIPv6] time Layer 2+3 Latency

  16. Fast Handover for PMIPv6 • F-PMIPv6 Procedure Access technology specific(out of scope) Tunnel Setup NMAG requests PMAG to forward or buffer the packets& Tunnel Setup (When?  out of scope) Forwarding (OptionallyBuffering at NMAG) Access technology specific(out of scope)

  17. Fast Handover for PMIPv6 • PMIPv6 vs. F-PMIPv6 LMA LMA PMIPv6 Old MAG Old MAG PBU PBAck HAck HI PBU PBAck New MAG New MAG Buffering Link-specific Handover Link-specific Handover MN MN HO-COMPLETE(Link-UP) HO-INITIATE F-PMIPv6 Total Handover Latency Total Handover Latency HO-COMPLETE(Link-UP) HO-INITIATE

  18. Multihoming Scenario • Works in Host-based MIPv6 • “draft-ietf-mext-flow-binding-14” • It allows a mobile node (MN)/mobile router (MR) to bind a particular flow to a particular CoA with HA and CN. • “draft-ietf-mext-binary-ts-04” • It defines the formats for IPv4 and IPv6 Traffic Selector sub-options defined in “draft-ietf-mext-flow-binding-06.txt”.

  19. Scenarios for Network-based Flow Mobility • Supported Scenario • Scenario 1: Setting up Mobility Sessions on Demand • Create additional mobility sessions via a new interface on demand • A new mobility session with a new prefix is created LMA LMA Mobile IPTVflow PBU(HI=1) Mobile IPTVflow PBU(HI=1) 다른 인터페이스의 스위치를 올려서 단순하게 접속만 시도했군 !세션이동성은 없고… MAG MAG MAG MAG VoIPflow VoIPflow WiBro 3G WiBro 3G HTTPflow WiBro 3G WiBro 3G MN MN

  20. Scenarios for Network-based Flow Mobility • Supported Scenario • Scenario 2: Move some of flows to a new interface • If another access is enabled on the MN, some of the existing flows could be moved over, to achieve, e.g., load balancing and better user experience LMA LMA Mobile IPTVflow PBU(HI=2) Mobile IPTVflow PBU(HI=1) 새로운 인터페이스로 세션을 이동하고 있네?Vertical 핸드오버군 ! MAG MAG MAG MAG VoIPflow VoIPflow WiBro 3G WiBro 3G WiBro 3G WiBro 3G MN MN

  21. Logical Interface • Logical Interface over Multiple Physical Interfaces • draft-melia-netext-logical-interface-support-01 • Virtual Interface: term in implementation perspective • Features • It provide a single interface view to the layers above IP. • Therefore, it also allow hiding access technology changes or movement from host IP layer. • Resolve the problem that each physical interface should be assigned different IP addresses. • That is, only logical interface is assigned all addresses Application Layer Transport Layer (TCP, UDP…) Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Virtual Interface Layer Logical Interface Layer Data Link Layer PI1 [IEEE 802.11] PI2 [3GPP] PI3 [IEEE 802.16] … Virtual Interface Flow Interface Manager

  22. Current flow mobility Proposal of NetExt WG • Document • draft-bernardos-netext-pmipv6-flowmob-00, July 2010 • Proposed procedure • [New Messages] • - FMI (Flow Mobility Initiation) • - FMA (Flow Mobility Ack.)

  23. Current flow mobility Proposal of NetExt WG • Binding and Flow Binding States • After flow mobility…

  24. Summary & Conclusions • IETF Standards of Network-based Mobility Management • Open Issues • Not Yet Complete - Flow Mobility Design • Implement and Validate It! • Proposals • Implementation and Validation Tool: NS3 (http://www.nsnam.org/) 1) Proxy Mobile IPv6 [RFC 5213, Aug. 2008] 2) IPv4 Support for Proxy Mobile IPv6 [RFC 5844, May 2010] 3) Fast Handovers for Proxy Mobile IPv6 [draft-ietf-mipshop-pfmipv6-14] 4) Logical Interface Support for multi-mode IP Hosts [draft-melia-netext-logical-interface-support-01] 5) Proxy Mobile IPv6 Extensions to Support Flow Mobility [draft-bernardos-netext-pmipv6-flowmob-00]

More Related