Microsoft PowerPoint - B2-1-한연희

Size: px

Start display at page:

Download "Microsoft PowerPoint - B2-1-한연희"

지수 용
6 years ago
Views:

1 IP Dual-Stack Mobility Youn-Hee Han Korea University of Technology and Education Internet Computing Laboratory

2 Outline Background DSMIPv6 (Dual-Stack Mobile IPv6) Operation DSMIPv6 in PMIPv6 (Proxy Mobile IPv6) Conclusions & Discussion 2/37

3 Background 3/37

4 Dual-Stack Mobile IPv6 (DSMIPv6) IETF Internet-Draft Hesham Soliman (Ed.), Mobile IPv6 Support for Dual Stack Hosts and Routers (DSMIPv6), draft-ietf-mip6-nemov4traversal-00.txt, October, 2005 참여업체 : Nokia, NTT Docomo, Ericsson, CISCO, Flarion, Keio Univ.. Hesham Soliman (Ed.), Mobile IPv6 Support for Dual Stack Hosts and Routers (DSMIPv6), draft-ietf-mip6-nemov4traversal-06.txt, November, Hesham Soliman (Ed.), Mobile IPv6 Support for Dual Stack Hosts and Routers (DSMIPv6), draft-ietf-mext-nemov4travesrsal-02.txt, April, 년하반기 RFC 예정 4/37

Recent Status of IPv4 Address Space http://www.potaroo.net/tools/ipv4/index.

5 Recent Status of IPv4 Address Space IANA (Internet Assigned Numbers Authority) - 인터넷할당번호관리기관 RIR (Regional Internet Registry) - 대륙별인터넷레지스트리 - APNIC: (Asia Pacific Network Information Center) 5/37

6 Recent Status of IPv4 Address Space 6/37

7 Terminology Mixed IPv4/IPv6 Devices/Networks IPv4 Capable & IPv6 Capable IPv4 Stack, IPv6 Stack 이구현이되어져있음 IPv4 Enabled & IPv6 Enabled 실제 Stack 이가동되어 IPv4 Address, IPv6 Address 가할당되고활용됨 현재와미래의단말기및장비의상황 현재의단말기및네트워크장비들 IPv4/IPv6 Capable & Most of them are only IPv4 Enabled 현재 & 향후의단말기및네트워크장비들 IPv4/IPv6 Capable & Some of them are only IPv4 Enabled Others are only IPv6 Enabled The others are IPv4/IPv6 Enabled 7/37

8 기대되는상황 Mixed IPv4/IPv6 Devices/Networks 사업자들에의해서비스되는 ( 이동 ) 단말기들 IPv4 Enabled, IPv6 Enabled, or IPv4/IPv6 Enabled ( 유무선통신 ) 네트워크사업자들이구축하는네트워크장비 IPv4 Enabled, IPv6 Enabled, or IPv4/IPv6 Enabled DSMIPv6 을사용하기위한가정상황 DSMIPv6 서비스가구축된이동단말기들 IPv4/IPv6 Enabled DSMIPv6 서비스가구축된 Home Agent IPv4/IPv6 Enabled 8/37

Expected Mobility Scenarios DSMIPv6 가고려하는이동성시나리오 IP Network Heterogeneity as well as Accee Network Hetrogeneity IPv6/IPv4/Private IPv4 Transport

9 Expected Mobility Scenarios DSMIPv6 가고려하는이동성시나리오 IP Network Heterogeneity as well as Accee Network Hetrogeneity IPv6/IPv4/Private IPv4 Transport Network Support DSMIPv6 MN RAS IPv4 WiBro IP Network DSMIPv6 HA LTE BS WLAN AP Cellular IP network IPv6 WLAN NAT IP Network Private IPv4 AAA 9/37

10 DSMIPv6 가고려하는응용레벨시나리오 (1/2) IPv6 Home Address Mobility Expected Mobility Scenarios DSMIPv6 MN RAS IPv4 WiBro IP Network DSMIPv6 HA LTE BS Cellular IP network IPv4 IPv6 WLAN AP WLAN NAT IP Network Private IPv4 AAA IPv6 IPv6 Application (VoD, IP-Phone ) 10/37

11 Expected Mobility Scenarios DSMIPv6 가고려하는응용레벨시나리오 (2/2) IPv4 Home Address Mobility IPv4 Application (VoD, IP-Phone ) DSMIPv6 MN RAS IPv4 WiBro IP Network DSMIPv6 HA LTE BS Cellular IP network IPv4 IPv6 WLAN AP WLAN NAT IP Network Private IPv4 AAA IPv6 IPv6 Application (VoD, IP-Phone ) 11/37

12 Existing Solution & Problems Except DSMIPv6 Bad Solutions: Two IP Mobilty Stacks MN Mobile IPv4 (RFC3344) & Mobile IPv6 (RFC3775) 을동시에구현 HA Mobile IPv4 & Mobile IPv6을하나의 HA에동시에구현 또는 Mobile IPv4 HA 및 Mobile IPv6 HA를각각따로운영 Problems IPv4 IPv6 (or IPv4 IPv6) 세션유지불가능 구현 (Implementation) 의어려움 두개의프로토콜을동시에구현 단말및장비의단가향상 운영 (Operation) 의어려움 비효율적인이동성관리 네트워크시그널메시지의오버헤드 Alterative Solution: Mobile IPv4/IPv6 Traversal with DSMIPv6 IPv4 IPv6 (or IPv4 IPv6) 세션유지 12/37

13 DSMIPv6 Operation 13/37

14 DSMIPv6 Goal & Design Principle 설계목표 IPv4 및 IPv6 이동성을위하여하나의통합된이동성관리프로토콜설계 Mobile IPv6를확장하여다음두가지를만족한다. IPv4 Transport Network Support IPv4 Home Address Mobility 가정 (Assumption) MN과 HA는 IPv4/IPv6 Enabled 이다. 단말은 IPv6 Home Address (IPv6 HoA) 와 IPv4 Home Address (IPv4 HoA) 를모두알고있어야한다. Dynamic Stateless or Stateful Static 14/37

15 DSMIPv6 Goal & Design Principle 설계원칙 MN은 IPv4 HoA/CoA 및 IPv6 HoA/CoA 에대한바인딩정보를함께 HA에등록을한다. MN은자신과 HA 사이의네트워크에 NAT가있는지를파악하여올바르게 traverse 할수있어야한다. 임의의 IPv4 or IPv6 or IPv4/v6 Dual 네트워크로이동하더라도 IPv4 및 IPv6 패킷을받을수있도록한다. 15/37

16 프로토콜에새로운 Options 정의 DSMIPv6 Operation MIPv6 Binding Update (BU) 메시지에추가되는 Option IPv4 Home Address option IPv4 Care-of Address option IPv6[MIPv6 BU with New Options] HA MN 에서 HA 로전달됨 MIPv6 Binding Acknowlegement (BAck) 메시지에추가되는 Option IPv4 Address Acknowledgement option NAT Detection option HA에서 MN으로전달됨 IPv6[MIPv6 BAck with New Options] HA Solution Sketching HA가각MN에대한IPv6/IPv4 Home Address (HoA) 바인딩정보를동시에관리 16/37

17 세가지경우로나누어서프로토콜이기술됨 Case I. Visited network supports IPv6 Case II. Visited network supports IPv4 DSMIPv6 Operation First of all, MN needs to detect whether a NAT is in its path to HA. This is done while exchanging BU and BAck Case II-1. Visited network supports Public IPv4 MN can only configure a globally unique IPv4 CoA in the visited network. Case II-2. Visited network supports Private IPv4 MN can only configure a private IPv4 address in the visited network. 17/37

18 Case I. Visited network supports IPv6 DSMIPv6 Operation 바인딩관리방법 IPv6[MIPv6 BU with IPv4 HoA option] IPv6[MIPv6 BAck with IPv4 Addr. Ack. option] HA IPv6 binding cache entry MN s s IPv6 HoA MN s s IPv6 CoA IPv4 binding cache entry MN s s IPv4 HoA MN s s IPv6 CoA 터널설정및 Data Traffic 전송 MN HA CN IPv6 Data Traffic (IPv6-in-IPv6) IPv6 header (src=ipv6 CoA, dst=ipv6 HA) IPv6 header (src=ipv6 HoA, dst=ipv6 CN) Payload IPv6 header (src=ipv6 HA, dst=ipv6 CoA) IPv6 header (src=ipv6 CN, dst=ipv6 HoA) Paylaod IPv4 Data Traffic (IPv4-in-IPv6) IPv6 header (src=ipv6 CoA, dst=ipv6 HA) IPv4 header (src=ipv4 HoA, dst=ipv4 CN) Payload IPv6 header (src=ipv6 HA, dst=ipv6 CoA) IPv4 header (src=ipv4 CN, dst=ipv4 HoA) Paylaod 18/37

19 Case II-1. Visited network supports Public IPv4 바인딩관리방법 IPv4[UDP[IPv6[MIPv6 BU with IPv4 HoA option, IPv4 CoA option]]] DSMIPv6 Operation HA IPv6 binding cache entry MN s s IPv6 HoA MN s s IPv4 CoA IPv4 binding cache entry MN s s IPv4 HoA MN s s IPv4 CoA IPv4[UDP[IPv6[MIPv6 BAck with IPv4 Addr. Ack. Option, NAT Detection option]]] (No Detection) IPv4 HoA Option IPv4 CoA Option Outer IPv4 Header UDP Inner IPv6 Header HoA Destination Option Binding Update Source Addr. Destination Addr. Source Addr. Destination Addr. IPv4 CoA HA s IPv4 Addr. IPv6 HoA HA s IPv6 Addr. IPv6 HoA IPv4 HoA IPv4 CoA = No NAT is Detected 19/37

20 Case II-1. Visited network supports Public IPv4 터널설정및 Data Traffic 전송 DSMIPv6 Operation MN HA CN IPv6 Data Traffic (IPv6-in-IPv4) IPv4 header (src=ipv4 CoA, dst=ipv4 HA) IPv6 header (src=ipv6 HoA, dst=ipv6 CN) Payload IPv4 header (src=ipv4 HA, dst=ipv4 CoA) IPv6 header (src=ipv6 CN, dst=ipv6 HoA) Paylaod IPv4 Data Traffic (IPv4-in-IPv4) IPv4 header (src=ipv4 CoA, dst=ipv4 HA) IPv4 header (src=ipv4 HoA, dst=ipv4 CN) Payload IPv4 header (src=ipv4 HA, dst=ipv4 CoA) IPv4 header (src=ipv4 CN, dst=ipv4 HoA) Paylaod 20/37

21 Case II-2. Visited network supports Private IPv4 바인딩관리방법 IPv4[UDP[IPv6[MIPv6 BU with IPv4 HoA option, IPv4 CoA option]]] NAT IPv4[UDP[IPv6[MIPv6 BAck with IPv4 Addr. Ack. Option, NAT Detection option]]] (NAT Detected) DSMIPv6 Operation HA IPv6 binding cache entry MN s s IPv6 HoA MN s s IPv4 CoA IPv4 binding cache entry MN s s IPv4 HoA MN s s IPv4 CoA IPv4 HoA Option IPv4 CoA Option Outer IPv4 Header UDP Inner IPv6 Header HoA Destination Option Binding Update Source Addr. Destination Addr. Source Addr. Destination Addr. IPv4 CoA HA s IPv4 Addr. IPv6 HoA HA s IPv6 Addr. IPv6 HoA IPv4 HoA IPv4 CoA 21/37 NAT is Detected

22 Case II-2. Visited network supports Private IPv4 터널설정및 Data Traffic 전송 DSMIPv6 Operation MN HA CN IPv6 Data Traffic (IPv6-in-UDP-in-IPv4) IPv4 header (src=ipv4 CoA, dst=ipv4 HA) UDP header IPv6 header (src=ipv6 HoA, dst=ipv6 CN) Payload IPv4 header (src=ipv4 HA, dst=ipv4 CoA) UDP header IPv6 header (src=ipv6 CN, dst=ipv6 HoA) Paylaod IPv4 Data Traffic (IPv4-in-UDP-in-IPv4) IPv4 header (src=ipv4 CoA, dst=ipv4 HA) UDP header IPv4 header (src=ipv4 HoA, dst=ipv4 CN) Payload IPv4 header (src=ipv4 HA, dst=ipv4 CoA) UDP header IPv4 header (src=ipv4 CN, dst=ipv4 HoA) Paylaod 22/37

23 NAT Detection Option & NAT Keepalive NAT Detection Option Message Format F It indicates to MN that UDP encapsulation is required. Refresh Time A suggested time (in seconds) for MN to refresh the NAT binding. all 1s means that keepalives are not needed (no NAT was detected). NAT binding Refreshment if MN is not active, it will need to periodically send a message to HA in order to refresh the NAT binding. The default time is NATKATIMEOUT (=110 sec.) If Refresh time is suggested from HA, MN should use it. 23/37

종합적인모습 MN 와 HA 사이의시그널링및터널설정 HA (IPv6 HoA & IPv4 HoA 적절한 IPv4 or IPv6 CoA ) IPv6- BU IPv6- BAck 6-in-6 Tunnel 4-in-6 Tunnel IPv4- UDP- IPv6- BU IPv4- UDP- IPv6- BAck 6-in-4 Tunnel

24 종합적인모습 MN 와 HA 사이의시그널링및터널설정 HA (IPv6 HoA & IPv4 HoA 적절한 IPv4 or IPv6 CoA ) IPv6- BU IPv6- BAck 6-in-6 Tunnel 4-in-6 Tunnel IPv4- UDP- IPv6- BU IPv4- UDP- IPv6- BAck 6-in-4 Tunnel 4-in-4 Tunnel IPv4- UDP- IPv6- BU IPv4- UDP- IPv6- BAck 6-inudp-in-4 Tunnel NAT 4-inudp-in-4 Tunnel MN MN MN MN 이 IPv6 네트워크로이동할때 MN 이 IPv4 네트워크로이동할때 MN 이 Private IPv4 네트워크로이동할때 24/37

25 DSMIPv6 Operation 25/37

26 Internet Drafts of PMIPv6 IETF PMIPv6 Drafts Official WG Item S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), B. Patil (Nokia), Proxy Mobile IPv6, draft-ietf-netlmmproxymip6-00.txt, April 8, S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), B. Patil (Nokia), Proxy Mobile IPv6, draft-ietf-netlmmproxymip6-01.txt, June 18, S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), B. Patil (Nokia), Proxy Mobile IPv6, draft-ietf-netlmmproxymip6-12.txt April 24, 년중반 RFC 예정 26/37

PMIPv6 Overview IP Tunnel IP-in-IP tunnel between LMA and MAG LMA: Localized Mobility Agent MAG: Mobile Access Gateway MAG LMA Home Network 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

27 PMIPv6 Overview IP Tunnel IP-in-IP tunnel between LMA and MAG LMA: Localized Mobility Agent MAG: Mobile Access Gateway MAG LMA Home Network MN s Home Network (Topological Anchor Point) movement MAG LMA Address (LMAA) LMM That will be the tunnel entry-point (Localized Mobility Management) Domain 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 Proxy Binding Update (PBU) Control message sent by MAG to LMA to establish a binding between MN-HoA and Proxy-CoA 27/37

28 New entities LMA (Local Mobility Anchor) PMIPv6 Overview Home Agent for the mobile node in the PMIPv6 domain Assigns MN's home prefix and manages the MN's reachability state MAG (Mobile Access Gateway) Manages the mobility related signaling for a mobile node Tracking the MN s attachment to the link and for signaling the MN's LMA LMA PBU PBAck 6-in-6 Tunnel 4-in-6 Tunnel PBU PBAck 6-in-4 Tunnel 4-in-4 Tunnel PBU PBAck 6-in-udpin-4 Tunnel 4-in-udpin-4 Tunnel NAT MAG MAG MAG 28/37 MN

29 PMIPv6 Operation Flow PBU: Proxy Binding Update PBA: Proxy Binding Ack. MN MAG AAA&Policy Store LMA CN MN Attachment AAA Query with MN-ID AAA Reply with Profile PBU with MN-ID, Home Network Prefix option, Timestamp option RA PBA with MN-ID, Home Network Prefix option Optional Tunnel Setup DHCP Request DHCP Response [MN-HoA:CN](data) DHCP Server DHCP Request DHCP Response [Proxy-CoA:LMAA][MN-HoA:CN](data) [MN-HoA:CN](data) RA (Router Advertisement) 29/37

30 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. MN always obtain its home network prefix, any where in the network. It will ensure that MN believes it is at its home. RA Unicast RA should be UNICASTed to an MN It will contain MN s Home Network Prefix Per-MN Prefix M:1 Tunnel LMA-MAG tunnel is a shared tunnel among many MNs. One tunnel is associated to multiple MNs Binding Caches. 30/37

IPv4 Support for PMIPv6 Two functions supported IPv4 Transport Network Support IPv4 Home Address Mobility The new WG draft for IPv4 support for PMIPv6

31 IPv4 Support for PMIPv6 Two functions supported IPv4 Transport Network Support IPv4 Home Address Mobility The new WG draft for IPv4 support for PMIPv6 R. Wakikawa (Keio Univ.), S. Gundavelli (Cisco), IPv4 Support for Proxy Mobile IPv6, draft-ietf-netlmm-pmip6-ipv4-support-02.txt, November 19, /37

IPv4 Support for PMIPv6 PMIPv6 s IPv4 Support Dual Stack MN or IPv4 MN PBU (HoAv6, Proxy CoAv6, HoAv4) IPv6 Tunnel (LMAAv6->Proxy CoAv6) [Mobility Binding] HoAv4 and HoAv6 Proxy CoAv6 IPv4 traffic

32 IPv4 Support for PMIPv6 PMIPv6 s IPv4 Support Dual Stack MN or IPv4 MN PBU (HoAv6, Proxy CoAv6, HoAv4) IPv6 Tunnel (LMAAv6->Proxy CoAv6) [Mobility Binding] HoAv4 and HoAv6 Proxy CoAv6 IPv4 traffic CNv4 HoAv4 Dual Stack MAG Only-IPv6 enabled (Proxy CoAv6) <MN in IPv6 domain> Dual Stack LMA Only-IPv6 enabled (LMMAv6) IPv6 traffic CNv6->HoAv6 [Mobility Binding] Dual Stack MN or IPv4 MN PBU (HoAv6, Proxy CoAv4, HoAv4) HoAv4 and HoAv6 Proxy CoAv4 IPv4 traffic CNv4 HoAv4 IPv4 Tunnel (LMAAv4->Proxy CoAv4) Dual Stack MAG Only-IPv4 enabled (Proxy CoAv4) <MN in IPv4 domain> Dual Stack LMA Only-IPv4 enabled (LMAAv4) IPv6 traffic CNv6->HoAv6 32/37

H/W 및 S/W 명세 MAG (MAG1, MAG2, MAG3) LMA CPU: Intel Pentium 4, 3.00GHz 802.11 NIC: Linksys Dual-Band Wireless A+G PCI Adapter WMP-55AG (Atheros Chipset) OS: Debian 3.1 sarge, kernel 2.6.

33 H/W 및 S/W 명세 MAG (MAG1, MAG2, MAG3) LMA CPU: Intel Pentium 4, 3.00GHz NIC: Linksys Dual-Band Wireless A+G PCI Adapter WMP-55AG (Atheros Chipset) OS: Debian 3.1 sarge, kernel CPU: Intel Pentium 4, 3.00GHz OS: Debian 3.1 sarge, kernel Free Radius S/W CN, MN CPU: Intel Pentium 4, 1.80GHz, 1.6 GHz OS: Windows XP, SP2 VoD Streaming Software CN: VLC media server MN: VLC media player 테스트베드구축 33/37

With ETRI, KT MN has Dual Stack and both addresses are

3ffe:1:3:ffff::/64 V6 network IPv6-IPv4 종합테스트베드 LMA eth0)

168.2.2 3ffe:2::2/64 NAT 192.168.1.3 Private V4 network eth0) 10.

168.101.1 3ffe:1:1::1/64 SSID: PMIP1 fe80::1 ra0) 192.168.102.

3ffe:1:3::1/64 fe80::1 SSID: PMIP3 34/37 초기실행 : v6 VoD

34 With ETRI, KT MN has Dual Stack and both addresses are always enabled LMA 가 MN 에게할당할 Prefix Pool 3ffe:1:3:1::/64 ~ 3ffe:1:3:ffff::/64 V6 network IPv6-IPv4 종합테스트베드 LMA eth0) ffe:1::1/64 V4 network eth1) ffe:2::1/64 V4/V6 network eth0) ffe:2::2/64 NAT Private V4 network eth0) CN MAG3 MAG1 eth0) 3ffe:1::2/64 MAG2 eth0) ra0) ffe:1:1::1/64 SSID: PMIP1 fe80::1 ra0) ffe:1:2::1/64 SSID: PMIP2 fe80::1 ra0) ffe:1:3::1/64 fe80::1 SSID: PMIP3 34/37 초기실행 : v6 VoD Client 초기실행 : v4 VoD Client

35 With KT Only Private IPv4 Network LMA (PC0) VoD (PC4) Subnet g a NAT1 NAT Subnet 1 Subnet 2 MAG1 MAG2 (PC1) (PC2) MAG3 (PC3) Subnet Notebook1 Notebook1 Notebook2 Notebook1 35/37

36 Only Private IPv4 테스트베드에서의실험결과 Handover Latency No. Events MAC Handover latency + EAP Auth. (ms) DHCP, PBU/PBAck (ms) 총응용계층 Handover Latency (ms) Average UDP Thoughput 전송률 평균 1.6 Mbps 3.0 M bps 2.5 M bps 2.0 M bps UDP Throughput Handover Events 1.5 M bps 1.0 M bps k bps 0.0 bps Time (sec) 36/37

37 Conclusions & Discussion 3GPP 및 WiMAX 의최근표준문서에 Mobile IPv4 와 Mobile IPv6 대신많이등장하는용어 DSMIPv6 PMIPv6 한사업자가서비스하는 Network 을한번에완벽히 IPv4 에서 IPv6 로변경을할수있다면 DSMIPv6 이불필요 그러나그것이항상가능한가? Mobile IPv4 고려없이 DSMIPv6 으로 IPv4 네트워크에서이동성서비스가능한가? 그렇다. 추후 IPv6 네트워크로변경을고려하여 IPv4 네트워크에서도 DSMIPv6 을이동성관리프로토콜로사용할것을추천 좀더효율적인이동성관리를위해서 MIPv6 대신 PMIPv6 를기본으로채택하고그위에 DSMIPv6 적용!!! 37/37

Microsoft Word - CPL-TR IETF-mobility.doc

Microsoft Word - CPL-TR IETF-mobility.doc IETF 이동성표준기술동향 2009 년 1 월 경북대학교통신프로토콜연구실 김지인 ( jiin16@gmail.com) 요약 본글에서는 IETF(International Engineering Task Force) 에서진행중인 IP 이동성표준기술 동향을 WG 별로주요 Draft Document 중심으로살펴보았다. 1 목 차 1. 서론... 3 2. MEXT (MOBILITY