PMIPv6 구현기술 및 성능 테스트 Youn-Hee Han [email protected] Korea University of Technology and Education Internet Computing Laboratory 2008.

PMIPv6 구현기술 및 성능 테스트

Youn-Hee [email protected]

Korea University of Technology and EducationInternet Computing Laboratory

http://icl.kut.ac.kr

2008 년 제 1 차 IPv6 기술 워크샵

Outline

Proxy Mobile IPv6 Overview

IPv4 Support in PMIPv6

Implementation of Proxy Mobile IPv6 & IPv4

Support

Experimental Results & Conclusions

2/35

Proxy Mobile IPv6 Overview

3/35

PMIPv6 Overview

LMM (Localized Mobility Management)

Domain

MAG

LMA

Proxy Binding Update (PBU)Control message sent by MAG to LMA

to establish a binding between MN-HoA and Proxy-CoA

Home Network

Proxy Care of Address (Proxy-CoA)The address of MAG

That will be the tunnel end-point

IP Tunnel IP-in-IP tunnel between LMA and MAG

MAG

LMA: Local Mobility AnchorMAG: Mobile Access Gateway

LMA Address (LMAA)

MN’ Home Address (MN-HoA) MN continues to use it as long as

it roams within a same domain

That will be the tunnel entry-point

MN’s Home Network (Topological Anchor Point)

MN’s Home Network Prefix (MN-HNP)CAFE:2:/64

movement

4/35

5/35

PMIPv6 OverviewNew entities

LMA (Local Mobility Anchor) 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

<MN ID# - Home Network Prefix - Tunnel ID#>

<MN ID# - Home Network Prefix - Tunnel ID#>

<Home Network Prefix – Link-specific (MAC) Address>

LMA

MAG

PBU

PBAck

MAG

PBU

PBAck

6-to-4 Tunne

l

4-to-4 Tunne

l

6-to-6 Tunne

l

4-to-6 Tunne

l

6/35

PMIPv6 OverviewAssumptions (or Restrictions)

Link between MN and MAG is a point-to-point link (not shared link) Logically exclusive layer 3 link between MN and MAG

Per-MN Prefix model unique home network prefix is assigned to MN

AR/MAG

MN . . . MN

Point-to-point link Point-to-point link

Per-MN PrefixPer-MN Prefix

7/35

PMIPv6 Operation Flow

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

PBA with MN-ID, Home Network Prefix optionRA**

[MN-HoA:CN](data)[Proxy-CoA:LMAA][MN-HoA:CN](data)

[MN-HoA:CN](data)

Tunnel Setup

PBU: Proxy Binding UpdatePBA: Proxy Binding Ack.

DHCP ServerDHCP Request

DHCP Response

DHCP Request

DHCP Response

Optional

8/35

PMIPv6 Features

Proxy Registration LMA needs to understand the Proxy Registration RFC 3775 MIPv6 BU/BAck Reuse

PBU (Proxy Binding Update)

PBAck (Proxy Binding Acknowledgement)

9/35

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.

10/35

PMIPv6 Features

Any MN is just a IPv6 host 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. IPv6 protocol parameter consideration

Lower default-router list cache timeout

LLA: Link Local Address (e.g., MAC Address)

IPv4 Support in PMIPv6

11/35

12/35

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-06.txt, Nov., 2007

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, Nov., 2007

v4 Network

v4 Network

IPv4 Packet

IPv6 Packet

HA

v6 Network

v6 Network Movement

NAT

Tunneled to private IPv4 CoA

Tunneled to IPv4 CoA

Tunneled to IPv6 CoA

Private v4 Network

Movement

IPv4 CN

IPv4 CN

IPv4 Support for MIPv6 (RFC 3775)

13/35

IPv4 Support for PMIPv6

PMIPv6’s IPv4 Support

Dual Stack LMAOnly-IPv6 enabled(LMMAv6)

Dual Stack MNor

IPv4 MN

PBU (HoAv6, Proxy CoAv6, HoAv4)

HoAv4 and HoAv6

Proxy CoAv6

[Mobility Binding]

IPv6 Tunnel (LMAAv6Proxy CoAv6)

IPv4 trafficCNv4 HoAv4

IPv6 trafficCNv6->HoAv6Dual Stack MAG

Only-IPv6 enabled(Proxy CoAv6) <MN in IPv6 domain>

Dual Stack LMAOnly-IPv4 enabled(LMAAv4)

Dual Stack MNor

IPv4 MN

PBU (HoAv6, Proxy CoAv4, HoAv4)

HoAv4 and HoAv6

Proxy CoAv4

[Mobility Binding]

IPv4 Tunnel (LMAAv4Proxy CoAv4)

IPv4 trafficCNv4 HoAv4

IPv6 trafficCNv6->HoAv6Dual Stack MAG

Only-IPv4 enabled(Proxy CoAv4) <MN in IPv4 domain>

PMIPv6’s IPv4 Support by using DSMIPv6 proposal When MN moves to an IPv6 network

LMAMN’s IPv6 HoAMN’s IPv6 HoA IPv6 Proxy CoAIPv6 Proxy CoA

MN’s IPv4 HoAMN’s IPv4 HoA IPv6 Proxy CoAIPv6 Proxy CoA

IPv6 binding cache entry


MAGMN

IPv6 header (src=IPv6 Proxy CoA, dst=IPv6 LMMA)

Mobility header - Proxy BU [P flag is set]

Mobility Option - IPv6 Home Network Prefix (MN IPv6 HoA) - Timestamp Option - MN IPv4 HoA Option (possibly empty)

IPv6 header (src=IPv6 LMMA, dst=IPv6 Proxy CoA)

Mobility header - Proxy BAck [P flag is set]

Mobility Option - IPv6 Home Network Prefix (MN IPv6 HoA) - Timestamp Option - MN IPv4 HoA Ack. Option

Proxy BindingUpdate


IPv6 header (src=IPv6 HoA, dst=IPv6 CN_ADDR)

Payload


IPv6 header (src=IPv6 CN_ADDR, dst=IPv6 HoA)

Paylaod

IPv6 Data Traffic



Payload



Paylaod

IPv4 Data Traffic

14/35


PMIPv6’s IPv4 Support by using DSMIPv6 proposal When MN moves to a Public IPv4 network

LMA






UDP header



Mobility Option - IPv6 Home Network Prefix (MN IPv6 HoA) - Timestamp Option - MN IPv4 HoA Option - MN IPv4 CoA Option


UDP header



Mobility Option - IPv6 Home Network Prefix (MN IPv6 HoA) - Timestamp Option - MN IPv4 HoA Ack. Option - NAT Detection Option

Proxy BindingUpdate

IPv4 header (src=IPv4 Proxy CoA, dst=IPv4 LMAA)


Payload

IPv4 header (src=IPv4 LMAA, dst=IPv4 Proxy CoA)


Payload

IPv6 Data Traffic

MAGMN



Payload



Payload

IPv4 Data Traffic


15/35

PMIPv6’s IPv4 Support by using DSMIPv6 proposal When MN moves to a Private IPv4 network

LMAMN’s IPv6 HoAMN’s IPv6 HoA IPv4 Proxy CoAIPv4 Proxy CoA




MAGMNIPv4 NAT

IPv4 header (src=IPv4 Proxy CoA, dst=IPv4 LMAA)

UDP header


Payload

IPv4 header (src=IPv4 LMAA, dst=IPv4 Proxy CoA)

UDP header


Payload

IPv6 Data Traffic


UDP header


Payload


UDP header


Payload

IPv4 Data Traffic


UDP header



Mobility Option - IPv6 Home Network Prefix (MN IPv6 HoA) - Timestamp Option - MN IPv4 HoA Option - MN IPv4 CoA Option


UDP header



Mobility Option - IPv6 Home Network Prefix (MN IPv6 HoA) - Timestamp Option - MN IPv4 HoA Ack. Option - NAT Detection Option

Proxy BindingUpdate


16/35

Implementation of Proxy Mobile IPv6 & IPv4 Support

17/35

ScheduleSchedule

5 월 6 월 7 월 8 월 30 일 10 월

PMIPv6 구현 이슈 및 Implementation Scope 셋업

PMIPv6 구현

데모 시나리오 작성

MIPL Mobile IPv6 코드 분석 및 Kernel 2.6.10 으로의 Porting 작업

데모 시나리오 테스트 및 디버그

중간 데모

IPv4 Support 구현 이슈 및 Implementation Scope 셋업

IPv4 Support 구현 및 PMIPv6 구현 보완

최종 보고 및 데모

11 월 20일

9 월4 월3 월

데모 시나리오 보완

최종 테스트 및 디버그

18/35

실험실 테스트 베드MAG/LMA Specification MAG (MAG1, MAG2, MAG3)

• CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz, • Memory: 1GB• 802.3 NIC: Marvel 88E8001• 802.11 NIC: Linksys Dual-Band PCI Adapter WMP-55AG• OS: Debian 3.1 sarge, kernel 2.6.10

LMA• CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz• Memory: 1 GB• 802.3 NIC: Realtek-8139 (x 2 개 )

, 3Com 3c905c-TX• OS: Debian 3.1 sarge, kernel 2.6.10

CN• CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz• Memory: 1 GB• 802.3 NIC: Marvel 88E8001• OS: Windows XP SP2

MN ( 노트북 )• CPU: Intel Centrino, Pentium Dual Core

1.86 GHz• Memory: 2 GB• OS: Windows XP SP2

19/35

실험실 테스트 베드 구축 모습

20/35

Implementation Issues

Issue #1. RA 의 전송 시점 In the Draft…

Case 1: Policy Profile 에서 AAA-Reply 를 통하여 제공하는 경우 MAG 에서 AAA-Reply 를 받은 이후 RA 전송 가능

Case 2: LMA 에서 PBA 를 통하여 제공되는 경우 MAG 에서 PBA 를 받은 이후 RA 전송 가능

Selected Approach LMA 에서 PBA 를 통하여 제공

Issue #2. PBU 갱신 시 MN 존재 유무 파악 In the Draft…

Binding Cache 를 갱신하기 위한 PBU 를 전송하는 경우 MN 의 존재를 재확인 해야 함 드래프트에 기술된 재확인 방법들

Link-layer event specific to the access technology PPP Session termination event on point-to-point link types IPv6 NUD event from IPv6 stack Absence of data traffic from MN on the link for a certain duration of time

Selected Approach MAG 에서 PBU 에 대한 lifetime 이 끝나가게 되면 NUD 를 MN 에게 수행한 후 MN 이 존재하는 것이

확인되면 PBU 전송

21/35


Issue #3. default gateway 의 변경 In the Draft…

Handover 이후 MN 에서 NUD 과정에 따른 Default Gateway 변경 지연 드래프트에서 제안된 방법들

Lower Default-Router List Cache Time-out By using a context transfer, new MAG multicasts an RA using the link-local address

that of the previous MAG and with the Router Lifetime field set to value 0. assignment of a unique link-local address for all the ARs in the PMIPv6 Network.

Selected Approach 세 번째 방법의 변형

모든 AR 의 link-local address 는 원래대로 다르게 셋팅함 RA 메시지를 만들어 보낼 때 모든 MAG 마다 같은 link-local address 를 Source Address

로 셋팅해서 보냄

Issue #4. MN 들에게 RA 메시지를 Unicast 로 전달하는 방법 Selected Approach

특별한 기법 사용 없이 구현 가능 IP Destination: All-node Multicast Address MAC Destination: Unicast MAC Address

22/35


Issue #5. WLAN 에서 Peer-to-Peer 링크 구현 이슈 In the Draft…

WLAN 이 Peer-to-Peer 링크가 아님으로써 발생하는 문제

Selected Approach RA 를 Unicast 로 전송 물리적으로 같은 서브넷에 위치한 두 Neighbor MN 들이 지닌 Neighbor Cache 에

대한 Status 때문에 발생하는 통신 단절 서로 다른 서브넷 Prefix 를 가진 단말들끼리 Direct Communication 을 위한 ARP Cache

를 가지게 되면 두 단말 중 어느 한 단말이 이동하게 되면 Session 이 끊어지게 됨 . 테스트 결과 일반적인 데이터 통신상에서 Off-link Prefix 에 대해서는 무조건 Default

Router 로 패킷을 보내기 때문에 문제가 없음 . 하지만 , Unsolicited Neighbor Advertisement 가 발생되는 경우에는 문제가 발생

Unsolicited Neighbor Advertisement 가 발생되는 경우 ?

AR/MAG

MN . . . MN

Point-to-point link Point-to-point link

Per-MN PrefixPer-MN Prefix

Issue #6. IPv4-HoA 할당 방법

LMA 를 통한 동적 할당 방법으로 구현 절차

IPv4 단말이 보내는 DHCP discovery 을 MAG 에서 Catch MAG 가 이미 IPv4-HoA 를 가지고 있는지 판단 . MAG 가 이미 IPv4-HoA 를 지니고 있지 않으면 PBU-PBACK 교환을 LMA 와 수행

PBU always contains “IPv4 HoA option” defined in DSMIPv6 and the option is set 0.0.0.0. PBAck contains rightful IPv4 address for the MN-NAI MAG gets an IPv4-address for the MN-NAI

MAG 에서 DHCP offer 를 보낼 때 IPv4 HoA 를 옵션으로 넣어줌 단말이 보내는 DHCP Request 를 MAG 에서 Catch 다시 DHCP Ack. 보냄


23/35

Issue #7. 인증 방법 및 LMA 주소 할당 방법 IEEE 802.1x EAP 인증 절차와 PMIPv6 의 Policy Store 연동 방법 변경

사용자 인증을 위해 EAPoL 과 MD5 프로토콜 을 이용


24/35

MN MAG/AP Policy Server (RADIUS)

Authenticator RAIDUS client

EAPoLStart

802.1x

EAPoLPacket

EAP- Req Identity=?

EAP- RespIdentity=”MN- ID”

EAPoLPacket

RADIUSEAP- RespIdentity=”MN- ID”

Access Request

RADIUS EAP- Req Challenge

Access Challenge

EAPoLPacket

EAP- Req Challenge

EAP RespChallenge response EAPoLPacket

MD5

RADIUSEAP RespChallenge response

Access Request

RADIUS EAP Success

Access Accept

EAPoLPacket

EAP Success LMAA

LMA

System Block Diagram

System Block

25/35

IPv6 Networking(MIPv6 patched)

<Kernel>

<User>

WLAN Driver

HostAP daemon

(WLAN AP functionality)

PMIPv6 MAG daemon

(MIPv6-MN)

MAG

App.

control

data

NetlinkRtNetlink

IPv6 Networking(MIPv6 patched)

<Kernel>

<User>

LAN Driver

PMIPv6 LMA daemon

(MIPv6-HA)

LMA

App.

control

data

NetlinkRtNetlink

Radius Client

Radius Server

DHCPv4

IEEE 802.11 MAC Control

Link-Up Event

Link-Up Event Processing

Address Configuration

PMIPv6 Routing & Tunneling

PBU/PBAck

Data PacketProcessing & Routing

Address Configuration

PMIPv6 Routing & Tunneling

PBU/PBAck

IPv6 ND Message Exchange

Data PacketProcessing & Routing

종합 테스트 베드 구축

MN has Dual Stack and both addresses are always

enabled

종합 테스트 베드

SSID: PMIP1SSID: PMIP2

SSID: PMIP3

MAG1/DHCP4

ra0) 192.168.101.13ffe:1:1::1/64

fe80::1

eth0) 3ffe:1::2/64

ra0) 192.168.102.13ffe:1:2::1/64

fe80::1

eth0) 192.168.1.2

ra0) 10.0.1.13ffe:1:3::1/64

fe80::1

eth0) 10.0.0.1V6 network

V4 network

초기 실행 : v6 VoD Client초기 실행 : v4 VoD Client

LMA/RadiusCN

NAT 192.168.1.3

eth0) 192.168.1.13ffe:1::1/64

eth1) 192.168.2.13ffe:2::1/64

eth0) 192.168.2.23ffe:2::2/64

V4/V6 network

Private V4 network

MAG2/DHCP4

MAG3/DHCP4

26/35

6-to-udp-4Tunnel

4-to-udp-4Tunnel

6-to-4Tunnel

4-to-4Tunnel

27/35

LMA 와 MAG 사이의 시그널링 및 터널 설정

LMA

MAG1 MAG2

PBU

PBAck

6-to-6Tunnel

4-to-6Tunnel

MAG3

PBU

PBAck

PBU

PBAckNAT

종합 테스트 베드 터널 설정

IPv4 Only 테스트 베드 구축

LMA(PC0)

VoD(PC4)

Subnet 4

NAT1 NAT2

MAG1(PC1)

MAG2(PC2)

Subnet 1 Subnet 2MAG3(PC3)

Subnet 3

Notebook1 Notebook2Notebook1 Notebook1

802.11g 802.11a192.168.1.2 192.168.3.2

192.168.1.1

192.168.3.1

192.168.4.1 192.168.4.2

10.0.1.1 10.0.2.1

10.0.1.2 10.0.2.2

10.0.1.1

10.0.1.2

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

28/35

6-to-udp-4Tunnel

4-to-udp-4Tunnel

6-to-udp-4Tunnel

4-to-udp-4Tunnel

6-to-udp-4Tunnel

4-to-udp-4Tunnel

29/35

LMA 와 MAG 사이의 시그널링 및 터널 설정

LMA

MAG1 MAG2

PBU

PBAck

MAG3

PBU

PBAck

PBU

PBAckNAT

IPv4 Only 테스트 베드 터널 설정

NAT NAT

테스트 목적 및 시나리오테스트 목적 및 시나리오 Target Goal

이동 단말이 미디어 스트리밍 서버로 부터 실시간으로 동영상을 받아 Play 하면서 서로 다른 IP Network 을 움직일 때 세션이 끊기지 않음을 보임

이동 단말 (Windows XP Operating System) 에는 어떠한 변경도 하지 않음

테스트 시나리오 Case 1

CN: VLC 서버를 IPv4 로 구동하여 IPv4 MN 으로 Traffic 보냄 MN: VLC 클라이언트를 IPv4 로 구동 MN 은 3 개의 네트워크를 차례대로 이동함

IPv6 IPv4 Private IPv4

Case 2 CN: VLC 서버를 IPv6 로 구동하여 IPv6 MN 에게 Traffic 보냄 MN: VLC 클라이언트를 IPv6 로 구동 MN 은 3 개의 네트워크를 차례대로 이동함

IPv6 IPv4 Private IPv4

Case 3 CN: VLC 서버를 IPv4 로 구동하여 IPv4 MN 으로 Traffic 보냄 MN: VLC 클라이언트를 IPv4 로 구동 Private IPv4 Only Network 에서 실험

30/35

Experimental Results & Conclusions

31/35

종합 테스트 베드에서의 실험 결과

Handover Latency (IPv6 네트워크로의 이동 )

UDP Thoughput 전송률

평균 3.0 Mbps

No.Events

1 2 3 4 5 6 7 8 9 10Averag

eMAC HO

latency(ms)2 2 2 2 3 2 2 2 2 2 2

EAP Auth. (ms) 103 92 85 151 148 94 74 98 118 106 107

PBU/PBAck (ms) 24 20 19 21 21 26 20 22 19 20 21총 응용계층

Handover Latency (ms)

151 141 133 214 226 145 134 146 170 173 163

32/35

Handover

Events

종합 테스트 베드에서의 실험 결과

Packet Tracing (IPv6 네트워크로의 이동 )

33/35

Private IPv4 Only 테스트 베드에서의 실험 결과

Handover Latency (Private-IPv4 네트워크로의 이동 )

UDP Thoughput 전송률

평균 1.6 Mbps

No.Events

1 2 3 4 5Averag

eMAC Handover

latency + EAP Auth. (ms)

92 37 116 29 65 68

DHCP, PBU/PBAck (ms) 201 118 317 220 125 196

총 응용계층 Handover Latency

(ms)293 155 433 249 190 264

HandoverEvents

34/35

35/35

PMIPv6 can be a way to facilitate the deployment of IP mobility Favorable to ISPs PMIPv6 is New Idea? Absolutely No!, but new trend!. It’s a turn for the

better! In the handover latency aspect, PMIPv6 has a very good performance. PMIPv6 + IPv4 support is well working.

No H/W Upgrade, Just S/W issue In current system, IPv6 signaling is trivial!!!

More Study and Standardization Needed Route Optimization in PMIPv6 Fast Handover in PMIPv6, Multihoming Cross-layering Issues

PMIPv6 over IEEE 802.11/16/WiBro Fast Handover with leverage of IEEE 802.21 Vertical Handover based on PMIPv6 Network-based Global Mobility PMIPv6-based NeMo (MANEMO) PMIPv6-based 6LowPAN Sensor Node Mobility

Conclusions

PMIPv6 구현기술 및 성능 테스트 Youn-Hee Han [email protected] Korea University of Technology and Education Internet Computing Laboratory 2008.

Documents