Hierarchical Mobility Management in IPv4/IPv6 Co-existed Networks

Jen-Yi Pan, Li-Wai Huang Department of Communications Engineering National Chung Cheng University Chia-yi, Taiwan, R.O.C.

Outline • Introduction • Related Works • Hierarchical Mobility Management in IPv4/IPv6 Coexisted Networks (HMIPv64) • Performance Comparison and Numerical Analysis • Prototype Implementation • Conclusions • References

• • • • • • •

Introduction Related Works HMIPv64 Performance Comparison and Numerical Analysis Prototype Implementation Conclusions References

Introduction (1/2) The Goal of Mobile IP : The link by which a mobile node is directly attached to the Internet may often be a wireless link. This link may thus have a substantially lower bandwidth and higher error rate than traditional wired networks. Moreover, mobile nodes are likely to be battery powered, and minimizing power consumption is important. Therefore, the number of administrative messages sent over the link by which a mobile node is directly attached to the Internet should be minimized, and the size of these messages should be kept as small as is reasonably possible. [5]

Introduction (2/2) • MIPv4 – The MIPv4 is limited due to the global IPv4 address is insufficient.

• MIPv6 – The MIPv6 is limited due to the infrastructure of IPv6 is unpopular so far. – Both MIPv4 and MIPv6 can not be interactive with each other.

• We provide a novel mobility management, called HMIPv64, by integrating MAP of HMIPv6 and Tunnel Server. • HMIPv64 is a extension of HMIPv6.

• Introduction • Related Works – – – –

• • • • •

Mobility Management (MIPv4 and MIPv6) IPv6 Translation and Tunnel Broker Mobility Management in IPv4/IPv6 Co-existed Networks Hierarchical MIPv6

HMIPv64 Performance Comparison and Numerical Analysis Prototype Implementation Conclusions References

Components of MIPv4 (1/2) •

• • • • • •

Mobile Node (MN) :具備IP行動能力的網際網路節點，該節點可移動到 網際網路的任何地方都可透過原位址(Home Address)與其他網路節點 通訊。 Home Agent (HA)：位於MN原網路的路由器，負責記錄MN目前的位 置資訊且轉送封包之代理人。 Foreign Agent (FA)：位於MN漫遊至的其他網路，當MN向它註冊後將 負責轉送由HA所轉送的封包之代理人。 Correspondent Node (CN)：與MN進行通訊的任何一個網際網路節點。 Home Network：MN所在的原網路。 Foreign Network：MN 漫遊到的其他網路，也就是MN原網路之外的 其他網路。 Mobile Agent：指Home Agent與Foreign Agent。

Components of MIPv4 (2/2) • • •

• •

Agent Advertisement：Mobility Agent定期發送的訊息為Router Advertisement [15] 的延伸，訊息包括提供給MN的CoA與使用期限。 Home Address：MN的永久網路位址，不論MN是否在其網路。 Care of Address (CoA)：MN漫遊到其他網路之暫時網路位址，CoA可 分為兩種：從Foreign Agent得到的Foreign Agent CoA與從外部分配機 制(如：DHCP [16] )所得到的Co-located CoA。當取得位址為Foreign Agent CoA時FA為tunnel的終點。而當取得Co-located CoA時MN本身 是tunnel的終點。 Binding：MN的Home address與CoA之連結，也就是MN向HA所做的 註冊動作，訊息為Binding Update (BU)與Binding Acknowledge (BA)。 Tunnel：封包封裝、轉送的一連串動作。

Mobile IPv4 Home Network 2

Mobile Node

Mobile Node

Home Address

Care-of Address

3 Home Agent

Foreign Agent

1 4 CN

Correspondent Node

Packets delivery (When MN in Home Network) Moving Path of MN Binding Messages Packets delivery (When MN in Foreign Agent)

Components of MIPv6 • •

•

• • •

取消FA：MIPv6取消了原先FA存在的必要性，將其功能融入IPv6路由 器之中。 取消Foreign Agent CoA：MIPv6也取消了Foreign Agent CoA的設計， 因MIPv6所使用的IPv6協定有著128 bits的IPv6位址空間，不必擔心會 有位址不足的問題。 點對點安全(End to End Security)：MIPv6 可以使用 IPSec 規格來提供 必要的安全需求，像是認證 (Authentication) 、資料完整性保護 (Data Integrity Protection) 以及訊息回應保護機制 (Replay protection) 等功 能，都將比MIPv4來的更安全。 增進訊息傳遞效率：MIPv6可使用IPv6 Destination Option，利用封包 遞送同時傳遞Mobile IPv6訊息。 簡化Mobile IP訊息：MIPv6將Register、Request、BU、BA等訊息附加 在IPv6 Header Option之中。 路由最佳化：MIPv6將路由最佳化列為必要項目。當MN位於Foreign Network時將會同時傳送位址更新訊息給HA以及CN，路由最佳化是 為了解決三角路由問題。路由最佳化的封包傳遞流程圖如圖 4。

Mobile IPv6 Home Network 2

Mobile Node

Mobile Node

Home Address

Care-of Address

3 Router

Home Agent

1 CN c

Correspondent Node

3 4 Packets delivery (When MN in Home Network) Moving Path of MN Binding Messages Packets delivery (When MN in Foreign Agent)

The difference between MIPv4 and MIPv6 [7] Compared Items

Mobile IPv4

Mobile IPv6

Foreign Agent

YES

NO

Care-of address

FA or CCoA

CCoA only

Obtaining Care-of address

By FA or DHCPv4

IPv6 stateless and stateful mechanisms

Route Optimization

Option

Mandatory

Packet tunnel during route optimization

Require packet tunneling between MN and CN

Forward packets with no tunneling

HA involves route optimization

YES

NO

MIP messages format

ICMP and UDP packets

IP headers and ICMP packets

MIP messages

Reg. Req, Bing Update, …

Smooth hand-over

Option

Mandatory

Reverse tunneling

Solve ingress filtering

No ingress filtering problem [17]

Reduced and allow piggybacked in header

• Introduction • Related Works – – – –

• • • • •

Mobility Management (MIPv4 and MIPv6) IPv6 Translation and Tunnel Broker Mobility Management in IPv4/IPv6 Co-existed Networks Hierarchical MIPv6

HMIPv64 Performance Comparison and Numerical Analysis Prototype Implementation Conclusions References

IPv6 Translation and Tunnel Broker •

IPv6 Translation – – – – –

•

Automatic tunneling of IPv6 over IPv4 [14] Configured tunneling of IPv6 over IPv4 [14] 6to4 [18] ISATAP [19] Teredo [20]

Tunnel Broker [12]

IPv6 over IPv4 tunnel tunnel end-point

dual-stack node

tunnel end-point

Tunnel Server Tunnel Broker

DNS

Tunnel Server Tunnel Server

Mobility Management in IPv4/IPv6 Coexisted Networks • “Use of MIPv6 in IPv4 and MIPv4 in IPv6 networks” [21] – Case I (MIPv4-based): • Internet service provider has deployed MIPv4 and wants to work over IPv6 access network. • Such as Enhanced Mobile IPv4, “Dual Stack Mobile IPb4” [22]

– Case II (MIPv6-based): • Internet service provider has deployed MIPv6 and wants to work over IPv4 access network. • Such as Enhanced Mobile IPv6, “Dual Stack Mobile IPv64” [23]

– Case III (MIPv4-MIPv6): • Internet service provider has deployed MIPv4 and wants migrating to MIPv6. • Dual-Stack Mobile IPv4-Mobile IPv6, “Mobility Support for IPv4 and IPv6 Interconnected Networks based on Dual-Stack Model ” [24]

Dual Stack Mobile IPv64 [23] Home Network (IPv6)

Foreign Network (IPv4) 2

Dual Stack Node

Mobile Node

Mobile Node

Home Address

IPv4 Address

3 IPv4 Router

Dual Stack Node Home Agent

5 1 4

Packets delivery (When MN in Home Network)

CN

Moving Path of MN

Correspondent Node

Tunneling and Binding Messages Packets delivery (When MN in Foreign Agent)

• Introduction • Related Works – – – –

• • • • •

Mobility Management (MIPv4 and MIPv6) IPv6 Translation and Tunnel Broker Mobility Management in IPv4/IPv6 Co-existed Networks Hierarchical MIPv6

HMIPv64 Performance Comparison and Numerical Analysis Prototype Implementation Conclusions References

Hierarchical MIPv6 (1/4) • •

•

• •

MAP (Mobility Anchor Point) : HMIPv6將網路劃分為多個區域，MAP 即為區域頂端管理者；MAP可視為區域性Home Agent。 LCoA (On-Link Care-of-address) : LCoA是與MN的存取路由路由 (Access Router)有相同的Prefix，和MIPv6的CoA功用雷同。MAP區域 之外的通訊節點並不需知道LCoA位址便能與MN溝通，由MAP負責 RCoA與LCoA位址對應。 RCoA (Regional Care-of-address) : RCoA則是與MAP有相同的Prefix， 和MIPv6之Home Address功用雷同。 RCoA需在MN取得LCoA且向 MAP註冊之後才能取得，RCoA位址主要用來與HA及CN溝通時所 用，當MN在某個MAP之網路涵蓋範圍內移動時，MN的RCoA位址不 會改變；當離開原MAP之涵蓋範圍到另一個MAP涵蓋範圍時，MN的 RCoA才會改變。 Mirco-mobility : 在同一MAP之中的移動，LCoA改變而RCoA不變。 Marco-mobility : 在不同MAP之間的移動，LCoA與RCoA皆改變。

Hierarchical MIPv6 (2/4) CN HA

Internet Internet(IPv6) (IPv6)

Home Network

MAP

a

Router-1

Router-2

Marco- mobility Foreign Network Mirco- mobility

Foreign Network

MN

Hierarchical MIPv6 (2/3) CN HA

Internet Internet(IPv6) (IPv6) Tunne{src:HA addr., dst: RCoA]

Home Network

MAP Tunne{src:MAP addr., dst: LCoA]

Router-1

Router-2

Marco -mobility Foreign Network

Foreign Network

Mirco- mobility

MN

Standard IPv6 Routing (only the first packet) Tunneling (only the first packet) Moving Path Standard IPv6 Routing (other packets after the first) Tunneling (other packets after the first)

The architecture of HMIPv6 (3/3) Internet Internet

Mobile Node Access Point Moving Path

MAP

MAP MAP

MAP

Router-v6 Router-v6 Router-v6 Router-v6 Router-v6 Router-v6 Router-v6

The architecture of HMIPv64 Internet Internet Mobile Node Access Point MAP

MAP MAP-TS

Router-v6 Router-v6 Router-v6

Moving Path

MAP-TS

DHCP Domain

DHCP Domain DHCP Domain

DHCP Domain

• Introduction • Related Works • HMIPv64 – – – – –

• • • •

The architecture of HMIPv64 Operations of MAP-TS Operations of Mobile Nodes MAP-TS Discovery (for tunnel setting) Implementation Issues

Performance Comparison and Numerical Analysis Prototype Implementation Conclusions References

The architecture of HMIPv64 (1/2) • Mobile Node – – – –

Mobile Node of HMIPv6 Dual Stack Node DHCP Client Tunnel Client

• MAP-TS – – – – –

MAP of HMIPv6 Dual Stack Node IPv6 Router and IPv4 Router Tunnel Server Some DHCP Servers (IPv4 Domain) under MAP-TS

The architecture of HMIPv64 (2/2) CN

TB

DNS

According MAP-TS Discover

HA MAP-TS IPv6 Connectivity AR

AR

IPv6 Access Network

DHCP Domain

DHCP Domain dual-stack node IPv4 Access Networks

MAP Domain

IPv4 Connectivity TB Operation IPv6 over IPv4 tunnel Movement

Operations of MAP-TS (1/2) • Binding Table of MAP-TS – Could store IPv6 addr. Fitting IPv4 in LCoA • Ex: IPv4 compatible addr.

MAP-TS MAP

TS

Binding Table RCoA Ù LCoA global inet6 addr. Ù global inet6 addr. global inet6 addr. Ù IPv6 addr. fitting IPv4

• Router Advertisement – adopts parallel unicast method to tunnel the RA to these MNs according LCoAs of IPv4 in binding Table – adopts subnet broadcasting (IPv4 Router should support) – adopts DHCPOFFER message (Should modify the DHCP)

Operations of MAP-TS (2/2) • Packet Delivery of MAP-TS intercept packets

trigger the Tunnel

find MN’s LCoA

Version V4 of LCoA V6

tunnel packet to V4 LCoA

transmits packet to V6 LCoA

Operations of Mobile Nodes • Packet Delivery of MN packets producing

Version V4 of access networks V6

trigger the Tunnel

tunnel packet to MAP-PS transmits packet to CN

• Location Update of MN No

1.move to new location?

MN gets IPv4 address from DHCP server and IPv6 address from V6 router.

Yes

2.Receive new address

4.Trigger tunnel client and register to TS or TB 5.Building the Tunnel between client and TS

6.change MAP? 3.address version?

V4 No

V6

9.change MAP?

Yes

Yes

No

10.Send BU (LCoARCoA) to MAP 11.Send BU (LCoARCoA) to MAP and send BU (RCoAHome Address) to HA

7.Send BU (LCoA-RCoA) to MAP using IPv6 over IPv4 8.Send BU (LCoA-RCoA) to MAP and send BU (RCoA-Home Address) to HA using IPv6 over IPv4

MAP-TS MN

DHCP Server

TB

TS

MAP

HA

1.Discovery DHCP Server 2.Servers offer IP address and config info 3.Request configuration 4.Acknowledge Request 5.Tunnel Request 6.Acknowledge Request Tunneling

IPv4 Only

7.Router Solicitation (using tunnel in IPv4) 8.Router Advertisement (using tunnel in IPv4) 9.Binding Update (LCoA Ù RCoA) (using tunnel in IPv4) 10.Binding Ack (using tunnel in IPv4) 11.Binding Update (RCoA Ù Home address) 12.Binding Ack

For macro-mobility

MAP-TS DISCOVER (for tunnel setting) • Method 1: – This requires manual configuration of the DHCP servers which belong to the domain of MAP-TS. The DHCP servers periodically advertise the information of tunnel server’s address.

• Method 2: – The MAP-TS adopts subnet broadcasting the information of tunnel server address to mobile user. Each IPv4 router under the MAP-TS must support broadcast mechanism.

• Method 3(Tunnel Broker Support): – All MNs default a tunnel broker address. Once it arrives to a new IPv4 access network, it will register at this TB with default TB address.

MAP-TS DISCOVER Registering speed

1

2

3

fast middle (need to wait a interval time) slow (TB may not be in the local site)

Difficulty of deployment middle (must be manual configuration) easy (if router supporting broadcast) Hard (need to establish a tunnel broker)

Preferred scenario Local site (e.g., school) Local site Global site (e.g., city and country)

Implementation Issues • How to detect the connectivity of IPv4 ? – Router Advertisement – Modify DHCP

• How to manage the users ? – Authentication and Authorization – Tunnel Broker or MIPv6

• Integrate MAP and TS ? (loosing or tightly coupling) – Combine Tunnel Request, Tunnel Ack, Router Solicitation, Router Advertisement, Binding Update, Binding Ack

• • • •

Introduction Related Works HMIPv64 Performance Comparison and Numerical Analysis – Performance Comparison – Performance Analysis of Location Update – Performance Analysis of Packet Delivery

• Prototype Implementation • Conclusions • References

Performance Comparison Roaming in IPv6

Roaming in IPv4

MIPv6

V

HMIPv6

V

“Dual Stack Mobile IPv64” [23]

V

V

HMIPv64

V

V

Reduce Cost (location update and packet delivery)

V

V

Numerical Analysis of Location Update (1/3) • HMIPv64 / “Dual Stack Mobile IPv64” [23] ρ

the probability of marco-mobility.

α

the probability of changing to IPv6 access network.

BUmap

the cost of sending Binding Update message to MAP.

BAmap

the cost of receiving Binding Ack message from MAP.

Tc

the cost of establishing tunnel. (Tunnel Ack + Tunnel request)

BUha

the cost of sending Binding Update message to HA.

BAha

the cost of receiving Binding Ack form HA.

C1

the registering cost of our providing mechanism.

C2

the registering cost of [6] providing mechanism.

γ

the ratio of reduced cost between C1 and C2 Î (C2-C1)/C2

Numerical Analysis of Location Update (2/3) ⎡ ⎛ Tc + BUmap ⎞ ⎤ C1 = (1 − ρ ) × ⎢α ( BUmap + BAmap ) + (1 − α ) ⎜ ⎟⎥ BAmap + ⎝ ⎠⎦ ⎣ = BUmap + BAmap + (1 − α ) × Tc + ρ × ( BUha + BAha ) ......................(1)

C 2 = α ( BUha + BAha ) + (1 − α )( BUha + BAha ) = BUha + BAha................................................................................(2)

C 2 − C1 γ= C2 BUmap + BAmap + (1 − α ) × Tc .......................................(3) = (1 − ρ ) − BUha + BAha

Performance Analysis of Location Update (3/3) Case

ρ

α

BUmap BAmap

Tc

BUha BAha

γ

A

0.1

0.5

1

2

10

75%

B

0.2

0.5

1

2

10

65%

C

0.3

0.5

1

2

10

55%

D

0.1

0.5

1

2

20

82.5%

E

0.2

0.5

1

2

20

72.5%

F

0.3

0.5

1

2

20

62.5%

G

0.1

0.5

1

20

10

30%

H

0.2

0.5

1

20

10

20%

I

0.3

0.5

1

20

10

10%

J

0.1

0.5

1

20

20

60%

K

0.2

0.5

1

20

20

50%

L

0.3

0.5

1

20

20

40%

• (BUmap=1, BUha=10, Tc=2)

-0.2 0.0 0.2 0.4 0.6 0.8 1.0

0.8

0.6

0.4

0.2

0.9

0.0

th ma e pro cro ba mo bilit bil y o ity f

0.8

0.6

-0.2

0.4 0.8

0.2

0.6

α: th 0.4 e prob movin ability o f g to I Pv6 N etwor k

ρ:

cost γ: the ratio of reduced C2 between C1 and

1.0

0.2

0.1

0.0

• (BUmap=1, BUha=10, Tc=20)

1.0

-1.0 -0.8 -0.6 -0.4 -0.2 0.0 0.2 0.4 0.6 0.8 1.0

0.6 0.4 0.2 0.0 -0.2 -0.4

0.9

-0.6

th ma e pr rco oba mo bili bil ty o ity f

0.8

0.6

-0.8 -1.0

0.4 0.8

0.2

0.6

α: th 0.4 e prob 0.2 movin ability of g to I Pv6 N etwor k

ρ:

d cost γ: the ratio of reduce C2 between C1 and

0.8

0.1

0.0

Performance Analysis of Packet Delivery (1/2) (“Dual Stack Mobile IPv64” [23]) CN

HA

Internet Internet

V4-Router IPv6 Connectivity IPv4 Connectivity

MN

Performance Analysis of Packet Delivery (2/2) (HMIPv64) CN

HA

Internet Internet

MAP-TS IPv6 Connectivity IPv4 Connectivity

MN

• • • • •

Introduction Related Works HMIPv64 Performance Comparison and Numerical Analysis Prototype Implementation – Environment of Prototype Implementation – Program Architecture – Demo

• Conclusions • References

Environment of Prototype Implementation (1/2) • Linux Open Source – – – – –

Redhat 7.3 mipv6-0.9.3-v2.4.18 hmipv6 linux-kernel-patch against MIPL 0.9.3 radvd-0.7.2 udhcp-0.9.8

Environment of Prototype Implementation (2/2)

CN

fec0::2222:250:fcff:fe40:eae6/64

HA fec0::1111:220:18ff:fed6:6c81/64

140.123.1.222

MAP-TS

Subnet-B

140.123.2.111 fec0::3333:230:1bff:feac:79ea/64

fec0::3333:209:6bff:fed0:cd62/64

fec0::1111:240:f4ff:fe6f:f6d0/64

Router-A 140.123.2.222 fec0::2222:2d0:68ff:fe01:b852/64

fec0::3333:211:2fff:fe00:9efd/64 fec0::3333:211:2fff:fe00:9efd/64

Router-B fec0::4444:220:18ff:fec1:4917/64

V4-Router DHCP SERVER

Router-C fec0::5555:240:95ff:fe31:70b8/64

140.123.3.111

Subnet-H Subnet-A

fec0::1111:20e:a6ff:feaa:2bb5/64

Subnet-C

Subnet-D

Subnet-V4 MN

Router

Hub

Moving Path

Program Architecture (1/2) • Adopt automatic tunneling • Modify DHCP Server and Client – Add MAP-Info into DHCPOFFER – Continue sending DHCPDISCOVER

• hmipv64_proc module – Interconnect DHCP Client and mipv6 module

• detect_ipv6

Program Architecture (2/2) hmipv64_proc module

mipv6 module

Kernel Mode User Mode rs_state route_info. map_info.

Setting v4 ip and default router detect_ipv6

dhcp-client

Internet Internet(IPv4) (IPv4)

dhcp-server

Trigger sit0 up

START

detect_ipv6

Yes

stop dhcp-client (if dhcp client is runnimg)

rs_state = 2 ? No

dhcp-client start dhcp-client

Yes

v4 subnet change ?

send dhcpdiscover receive dhcpoffer

Setting ipv4 addr. Setting ipv4 df gw Clean ipv6 df gw Setting ipv6 df gw

send map and v6-router info. to hmipv64_proc hmipv64_proc module

mipv6_map_add

mipv6_node_moved

mipv6 module

Binding Update to MAP-TS from MN 4500 0064 0000 4000 4029 1bbf 8c7b 03de 8c7b 01de 6000 0000 0028 3cff 0000 0000 0000 0000 0000 0000 8c7b 03de fec0 0000 0000 2222 0250 fcff fe40 eae6 3c02 0102 0000 c910 fec0 0000 0000 2222 020e a6ff feaa 2bb5 3b01 c608 b800 0001 0000 02bb 0102 0000

03:28:15.351245 140.123.3.222 > 140.123.1.222: ::140.123.3.222 > fec0::2222:250:fcff:fe40:eae6: DSTOPT (padn)(homeaddr: fec0::2222:20e:a6ff:feaa:2bb5) DSTOPT (bu: ARDres, prefixlen: 0, sequence: 1, lifetime: 699) (padn)no next header (len 40, hlim 255) (DF) (ttl 64, id 0, len 100)

Binding Ack to MN from MAP-TS 4500 0064 0000 4000 3f29 1c2e 8c7b 026f 8c7b 03de 6000 0000 0028 2bff fec0 0000 0000 2222 0250 fcff fe40 eae6 0000 0000 0000 0000 0000 0000 8c7b 03de 3c02 0001 0000 0000 fec0 0000 0000 2222 020e a6ff feaa 2bb5 3b01 0007 0b00 0001 0000 02bb 0000 022f

03:28:15.351856 140.123.2.111 > 140.123.3.222: fec0::2222:250:fcff:fe40:eae6 > ::140.123.3.222: srcrt (len=2, type=0, segleft=1, rsv=0x0, [0]fec0::2222:20e:a6ff:feaa:2bb5) DSTOPT (pad1)(ba: status: 0, sequence: 1, lifetime: 699, refresh: 559) no next header (len 40, hlim 255) (DF) (ttl 63, id 0, len 100)

Binding Update to HA from MN 4500 0074 0000 4000 4029 1bbf 8c7b 03de 8c7b 01de 6000 0000 0038 3cff 0000 0000 0000 0000 0000 0000 8c7b 03de fec0 0000 0000 1111 0220 18ff fed6 6c81 3c02 0102 0000 c910 fec0 0000 0000 1111 020e a6ff feaa 2bb5 3b03 c61c e000 0002 0000 02bb 0100 0310 fec0 0000 0000 2222 020e a6ff feaa 2bb5

03:28:15.352099 140.123.3.222 > 140.123.1.222: ::140.123.3.222 > fec0::1111:220:18ff:fed6:6c81: DSTOPT (padn)(homeaddr: fec0::1111:20e:a6ff:feaa:2bb5) DSTOPT (bu: AHR, prefixlen: 0, sequence: 2, lifetime: 699, padn, sopt_type 0x03: len=16) no next header (len 56, hlim 255) (DF) (ttl 64, id 0, len 116)

Binding Ack to MN from HA 4500 008c 0000 4000 3f29 1c06 8c7b 026f 8c7b 03de 6000 0000 0050 29ff fec0 0000 0000 2222 0250 fcff fe40 eae6 0000 0000 0000 0000 0000 0000 8c7b 03de 6000 0000 0028 2bfd fec0 0000 0000 1111 0220 18ff fed6 6c81 fec0 0000 0000 2222 020e a6ff feaa 2bb5 3c02 0001 0000 0000 fec0 0000 0000 1111 020e a6ff feaa 2bb5 3b01 0007 0b00 0002 0000 0257 0000 01df

03:28:15.378702 140.123.2.111 > 140.123.3.222: fec0::2222:250:fcff:fe40:eae6 > ::140.123.3.222: fec0::1111:220:18ff:fed6:6c81 > fec0::2222:20e:a6ff:feaa:2bb5: srcrt (len=2, type=0, segleft=1, rsv=0x0, [0]fec0::1111:20e:a6ff:feaa:2bb5) DSTOPT (pad1)(ba: status: 0, sequence: 2, lifetime: 599, refresh: 479) no next header (len 40, hlim 253) (len 80, hlim 255) (DF) (ttl 63, id 0, len 140)

• • • •

Introduction Related Works HMIPv64 Performance Comparison and Numerical Analysis • Prototype Implementation • Conclusions • References

Conclusions • A novel mobility management called HMIPv64 is proposed in this thesis. • HMIPv64 not only can reduce the cost of location update when MNs handoff with micro-mobility but also can shorten the routing path when MNs reside in IPv4 networks. • We also implemented the prototype of HMIPv64. • In the transient age from IPv4 to IPv6, the scheme is the most appropriate mobility management for no longer limited by underlying network layer protocols.

Future Work • Improve the code of prototype. • Combine Tunnel Request、Tunnel Ack、Router Solicitation、Router Advertisement、Binding Update. • Authentication and Authorization • Combine the NAT mechanism into HMIPv64

Publications • Presented in WIRELESSCOM 2005 • Attend the quarterfinal of cc2005

• • • •

Introduction Related Works HMIPv64 Performance Comparison and Numerical Analysis • Prototype Implementation • Conclusions • References

References [1] [2]

J. Postel, "Internet Protocol", RFC 791, September 1981. S. Bradner and A. Mankin, "The Recommendation for the IP Next Generation Protocol", RFC 1752 January 1995. [3] IEEE 802.11, Wireless LAN Medium Access Control and Physical Layer specifications, 1999. [4] IEEE 802.16, Air Interface for Broadband Wireless Access. [5] C. Perkins, "IP Mobility Support for IPv4", RFC 3344, August 2002. [6] D. Johnson, C. Perkins, and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004. [7] Computer & Communication Research Labs, [Online]. Available: http://www.ccl.itri.org.tw/. [8] Digital cellular telecommunication system, General Packet Radio Service, Service description, Stage 2, GSM 03.60, Version 6.0, ETSI, 1998. [9] H. Soliman, C. Catelluccia, and L. Bellier, "Hierarchical Mobile IPv6 mobility management (HMIPv6)", draft-ietf-mipshop-hmipv6-04.txt, December 2004. [10] E. Gustafson, A. Johnson, and C. Perkins, "Mobile IP Regional Registration", draft-ietf-mip4-reg-tunnel-00, November 2004.

References [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]

D. New, "The TUNNEL Profile", RFC 3260, October 2003. A. Durand, P. Fasano, I. Guardini and D.Lento, "Ipv6 Tunnel Broker", RFC 3053, January 2001. P. Srisuresh and K. Egevang, "Traditional IP Network Address Translator (Traditional NAT)", RFC 3022, January 2001. R. Gilligan and E. Nordmark, “Transition Mechanisms for IPv6 Hosts and Routers”, RFC2893, August 2000. D. Haskin, "Default Route Advertisement In BGP2 And BGP3 Versions Of The Border Gateway Protocol", RFC1397, January 1993. R. Troll, "DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients", RFC 2563, May 1999. P. Ferguson and D. Senie, “Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing”, RFC 2827, May 2000. ]B. Carpenter and K. Moore, “Connection of IPv6 Domains via IPv4 Clouds”, RFC 3056, February 2001. ]F. Templin, T. Gleeson, M. Talwar and D. Thaler, "Intra-Site Automatic Tunnel Addressing Protocol", draft-ietf-ngtrans-isatap-24.txt, January 2005. C. Huitema, "Teredo: Tunneling IPv6 over UDP through NATs", draft-huitemav6ops-teredo-05.txt, April 2005.

References [21] T. Larsson, E. Gustafssin and H. Levkowetz, “Use of MIPv6 in IPv4 and MIPv4 in IPv6 networks”, draft-larsson-v6ops-mip-scenarios-01, February 2004. [22] ]George Tsirtsis and Hesham Soliman, "Dual Stack Mobile IPv4", drafttsirtsis-v4v6-mipv4-00, August 2003. [23] ]Hesham Soliman and George Tsirtsis, "Dual Stack Mobile IPv64", draftsoliman-v4v6-mipv4-01, October 2004. [24] Shiao-Li Tsao, Jen-Chi Liu and Wolfgang Boehm, “Mobility Support for IPv4 and IPv6 Interconnected Networks based on Dual-Stack Model”, draft-tsao-mobileip-dualstack-model-02, February 2000. [25] ]Linux, [Online]. Available: http://www.linux.org/ linux/. [26] Mobile-IPv6.org, [Online] Available: http://www.mipl.mediapoli.com/. [27] ]Hierarchical Mobile IPv6 Research at CTIE, [online]. http://www.ctie.monash.edu.au/ipv6/hmipv6.htm/. [28] Linux IPv6 Router Advertisement Daemon, [online]. Available: http://v6web.litech.org/radvd/. [29] UDHCP, [online]. Available: http://udhcp.busybox.net/.