1. IPv4/v6 Mobility & Proxy Mobile IPv6
Youn-Hee Han
Korea University of Technology and Education Internet Computing Laboratory

2. Outline IP Mobility - Why and What Mobile IPv4 (RFC 3344)
PMIPv6 (Proxy Mobile IPv6) Background
PMIPv6 Overview & Features
IPv4 Support for PMIPv6
PMIPv6 and MIPv6 (Mobile IPv6) Interworking
Summary
KT 세미나

3. IP Mobility - Why and What
KT 세미나

4. IP’s Routing Model Internet
Router
Internet
Router
Addresses are assigned in a topologically significant manner
Routing based on address prefixes
MN(Mobile Node) must be assigned a new address when it moves
KT 세미나

5. IP Session Continuity Internet TCP connections are defined by…
Router
Internet
Router
TCP connections are defined by…
[Source IP, Source Port, Destination IP, Destination Port]
MN’s address must be preserved regardless of its location to preserve the on-going IP session.
Threfore, when an MN moves,
Retain the MN address → Routing fails
Change the MN address → IP Session breaks
KT 세미나

6. Solutions : Two-tier IP addressing
Router
Internet
Router
MN keeps its static IP address, but uses a temporary a CoA(care-of address) when it moves to another subnet
HoA (Home Address) – the original static IP address –
CoA (Care-of Address) – the temporary IP address –
KT 세미나

7. Why Network-layer Mobility?
Transport Layer/ Application Layer transparency
Can even change physical media without breaking connections
Mobility management is related with addressing
KT 세미나

8. Things to be considered
IP Mobility가 이동통신망에서 필요한가? 현재 WiBro에서는..?
단말기를 단순한 클라이언트로만 생각한다면 IP Mobility Service는 필요 없고 단순한 L2 Path Extension 기능만 있어도 될 것 같아…
그러나, IP Session 유지 기간에 따라 IP Mobility Service에 대한 중요도가 높아질 것 같아.
IP Cloud for L 2
Mobility
Backbone
Network
Micro Mobility Zone
Subnet - 1
Routing
RAS3
RAS1
RAS2 L p a t h E x e n d
MSS ( )
HO using L
Path Extension
) ( 3
HO over different ACRs
using L
ACR
Anchor
PG 1
PG 2
KT 세미나

9. Things to be considered
IP Mobility 지원이 필요 없는 거 아니야?
단말기도 일종의 서버가 될 수 있다고 생각한다면 IP Mobility Service가 필요 하지 않을까…?
단말기들 사이의 Peer-to-Peer 서비스를 원할하게 제공해야 한다면 IP Mobility Service는 필요할 것 같아.
IP 세션을 사람의 개입 없이 기계들 끼리 자동으로 열고 닫고 한다면…?
The world of IPv6
DRINK
Mobile telephone
Image Server
Music
Data car
Map information
Vending machines
Data-compatible home appliances
Broadcasting
Settlement \
IPv６
KT 세미나

10. Things to be considered
도대체 WiBro 네트워크 내에 ACR의 개수가 몇 개인데?
Router 장비인 ACR (서브넷) 2~3 개 정도로 서울 시내를 모두 Cover 한다고 들었어… 그러면, L2 Path Extension 만으로도 충분하지 않을까?
도대체 서브넷을 이동하는 횟수가 얼마나 되는데?
대부분의 시간에 서브넷의 경계에 위치하는 사용자는?
만약에 WiBro가 전국 서비스망으로 확장된다면 ACR의 개수는 얼마나 될까? 만약에 10개 이상… 그 보다 더 많아진다면 IP Mobility는 필요할 것 같아…
WiBro와 WLAN 간의 이동은? WiBro와 3G (HSDPA) Network간의 이동은? 당연히 IP 가 바뀌겠지… IP Mobility가 필요하겠다.
KT 세미나

11. Mobile IPv4 (RFC 3344)
KT 세미나

12. Mobile IPv4 History Major Component
RFC 2002 (IP Mobility Support for IPv4), Oct. 1996
RFC 3344 (IP Mobility Support for IPv4), Aug. 2002
20 Major Changes, 16 Minor Changes since RFC 2002
draft-ietf-mip4-rfc3344bis-03.txt (IP Mobility Support for IPv4, revised), March 2007
20 Major Changes, 17 Minor Changes since RFC 3344
Major Component
HA – Home Agent
FA – Foreign Agent
MN – Mobile Node
KT 세미나

13. Operation Sketch of Mobile IPv4
Mobile IPv4 Operation
Basic Operation of Mobile IPv4 CN
Normal routing
MN in Home Network
MN has only HoA
KT 세미나

14. Operation Sketch of Mobile IPv4
Mobile IPv4 Operation
Operation Sketch of Mobile IPv4
Basic Operation of Mobile IPv4 CN
Normal routing
1) Agent Solicitation
2) Agent Advertisement
MN in Foreign Network
3) MN obtains a new CoA (FA-CoA)
KT 세미나

15. Operation Sketch of Mobile IPv4
Mobile IPv4 Operation
Basic Operation of Mobile IPv4 CN
Binding Cache
2) Registration Request
HoA
CoA
Normal routing
3) Registration Reply
1) Registration Request
4) Registration Reply
MN in Foreign Network
KT 세미나

16. Operation Sketch of Mobile IPv4
Mobile IPv4 Operation
Basic Operation of Mobile IPv4 CN
Binding Cache
HoA
CoA
KT 세미나

17. Operation Sketch of Mobile IPv4
Mobile IPv4 Operation
Basic Operation of Mobile IPv4 CN
Binding Cache
HoA
CoA
1) Agent Solicitation
2) Agent Advertisement
3) MN obtains a new CoA (FA-CoA)
KT 세미나

18. Operation Sketch of Mobile IPv4
Mobile IPv4 Operation
Operation Sketch of Mobile IPv4
Basic Operation of Mobile IPv4
2) Registration Request CN
Binding Cache
HoA
New CoA
3) Registration Reply
4) Registration Reply
1) Registration Request
KT 세미나

19. Operation Sketch of Mobile IPv4
Mobile IPv4 Operation
Operation Sketch of Mobile IPv4
Basic Operation of Mobile IPv4 CN
Binding Cache
HoA
New CoA
KT 세미나

20. Characteristics of Mobile IPv4
Agent Discovery
Agent Solicitation/Agent Advertisement (ICMP Messages)
Registration
Registration Request/Registration Reply (UDP Messages)
Notes:
Triangle Routing
CN  HA  MN, MN  HA  CN
Two CoA Modes
FA-CoA
MNs receive a CoA from FA
FA manages ‘Visitor List’, which has the entry [HoA, Layer 2 ID]
Host Routing (Not Prefix Routing)
No duplication about new CoA
Co-located CoA
DHCP-based CoA allocation
DHCP server should guarantee the uniqueness of CoA
KT 세미나

21. Mobile IPv6 (RFC 3775)
KT 세미나

22. IPv6… Why IPv6? Why IPv6 and Mobile IPv6 Infinite Address Space
128 bits address
Autoconfiguration Service
IP address auto-configuration without DHCP
Efficient Routing
Managed prefix allocation
The number of routing entry will be reduced at routers
Perfect peer-to-peering
Built-in Security
Efficient Mobility
The world of IPv6
DRINK
Mobile telephone
Image Server
Music
Data car
Map information
Vending machines
Data-compatible home appliances
Broadcasting
Settlement \
IPv６
KT 세미나

23. Mobile IPv6 Why IPv6 and Mobile IPv6
RFC 3775, Mobility Support in IPv6, June 2004
D. Johnson (Rice Univ.), C. Perkins (Nokia), J. Arkko (Ericsson)
It takes almost 3 years to make it RFC.
Major Components HA MN
(no FA)
MIPv6 is a network-layer protocol, while MIPv4 is a application-layer protocol (with network-layer modification).
KT 세미나

24. New Message and Options of Mobile IPv6
Why IPv6 and Mobile IPv6
New Message and Options of Mobile IPv6
New Signal Message related with Binging Management
Binding Update (BU)
Binding Acknowledgement (BAck)
Binding Refresh Request (BRR)
Binding Error (BE)
New Signal Message related with Binding Authentication
Home Test Init (HoTI)
Care-of Test Init (CoTI)
Home Test (HoT)
Care-of Test (CoT)
New Destination Option
Home Address Destination Option
New Routing Header Type
Routing Header Type 2
KT 세미나

25. Operation Sketch of Mobile IPv6
Why IPv6 and Mobile IPv6
Operation Sketch of Mobile IPv6
MN in Home Network CN
Home N/W
Internet AR HA
MN with Home Address
KT 세미나

26. Operation Sketch of Mobile IPv6
Why IPv6 and Mobile IPv6
Movement to a Foreign Network CN
Internet
Home N/W
Foreign N/W
3) MN sends a BU AR AR HA
4) HA acknowledges by returning BAck to MN
5) Setup Proxy Neighbor Cache
1) MN detects its Movements
2) MN configures New CoA
KT 세미나

27. Operation Sketch of Mobile IPv6
Why IPv6 and Mobile IPv6
Intercept packets sent from CNs CN
Internet
Home N/W
Foreign N/W AR AR HA MN
HA intercepts packets with
Home Address as its destination address
KT 세미나

28. Operation Sketch of Mobile IPv6
Why IPv6 and Mobile IPv6
Operation Sketch of Mobile IPv6
Packet Tunneling CN
Internet
Home N/W
Foreign N/W AR AR HA MN
HA sends encapsulated packets
to MN’s CoA
Looping Back
Process the packet (Decapsulation)
KT 세미나

29. Operation Sketch of Mobile IPv6
Why IPv6 and Mobile IPv6
Operation Sketch of Mobile IPv6
Return Routability with CN
5) CN generates ‘binding management key’ CN
4) MN sends CoTI to CN directly
Internet
Home N/W
Foreign N/W AR AR HA
3) MN sends HoTI to CN via HA MN
1) MN guesses that the CN has no Binding Cache for me 2) MN executes Return Routability
KT 세미나

30. Operation Sketch of Mobile IPv6
Why IPv6 and Mobile IPv6
Operation Sketch of Mobile IPv6
Return Routability with CN
5) MN sends BU with binding authorization data
6) CN need not return Binding Acknowledgement CN
2) CN sends CoT to MN directly
Internet
Home N/W
Foreign N/W AR AR HA
1) CN sends HoT to MN via HA MN
3) MN generates ‘binding management key’
4) MN computes binding authorization data (signature) for BU meesage
KT 세미나

31. Operation Sketch of Mobile IPv6
Why IPv6 and Mobile IPv6
Operation Sketch of Mobile IPv6
Data Routing after BU with CN CN
CN directly sends packets to MN’s CoA using Routing header type 2
Internet
Home N/W
Foreign N/W AR AR HA MN
KT 세미나

32. Operation Sketch of Mobile IPv6
Why IPv6 and Mobile IPv6
Operation Sketch of Mobile IPv6
When the binding’s lifetime of CN is near expiration
1) CN guesses that it is actively communicating with the mobile node and has indications, such as an open TCP connection to the MN
2) CN sends a BRR to the MN CN
Internet
Home N/W
Foreign N/W AR AR HA MN
3) MN replies by returning a BU to the CN
KT 세미나

33. Characteristics of Mobile IPv6
Why IPv6 and Mobile IPv6
How to make CoA?
Auto-configuration
Without DHCP
With DHCP
Duplication Address Detection (DAD) is required.
Route optimization supported
Triangle routing avoided
But, CN is required to be modified for the route optimization
Security
MN  HA : Strong Security (IPSec)
MN  CN : Weak Security (Return Routability)
Handover latency increased
KT 세미나

34. Handover Latency of Mobile IPv6
Why IPv6 and Mobile IPv6
Handover Latency of Mobile IPv6
L2 handover MD
DAD BU
Standard MIPv6 (Reactive)
time
Up to 2.5 seconds
MD: Movement Detection
DAD: Duplicate Address Detection
BU: Binding Update
Mobile IPv6 is not a handover-related protocol, rather it is a location (and route) update protocol.
KT 세미나

35. PMIPv6 Background
KT 세미나

36. PMIPv6 Background
KT 세미나

37. PMIPv6 Background
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 CE OS
KT 세미나

38. PMIPv6 Background
WLAN switch device starts to provide link specific and proprietary solution for IP handover.
No change in MN protocol stack required!
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
KT 세미나

39. PMIPv6 Background
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!).
IETF NetLMM WG started to standardize a network-based mobility management protocol.
63th IETF (2005.7)
The first NetLMM BoF
64th IETF ( )
The second NetLMM BoF
65th IETF ( )
The first NetLMM WG
66th,67th,68thIETF ( , , )
The one of very active WGs in IETF meetings
Almost 150~200 persons usually participates in the NetLMM WG
Proxy Mobile IPv6 adopted as WG item
KT 세미나

40. IETF NetLMM WG History
NetLMM DT solution (draft-giaretta-netlmm-dt-protocol) : designed from the scratch
Cisco’s solution (draft-ietf-netlmm-proxymip6) : Proxy Mobile IPv6 (leverage MIPv6)
Motorola’s solution (draft-singh-netlmm-protocol)
WG Chair (James Kempf, NTT) resigned after 67th meeting → Vidya Narayanan (Qualcomm)
WG Chair (Phil Roberts, Motorola) resigned after 68th meeting → Jonne Soininen (Nokia)
KT 세미나

41. Internet Drafts of PMIPv6
IETF PMIPv6 Drafts History
Individual
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.
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-netlmm-proxymip6-00.txt, April 8, 2007.
KT 세미나

42. PMIPv6 Overview & Features
KT 세미나

43. Goal of PMIPv6
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.
registration
(being extended)
PMIPv6 Scenario
KT 세미나

44. PMIPv6 Overview LMA MAG1 MAG2
LMA: Localized Mobility Agent MAG: Mobile Access Gateway
IP Tunnel
A IPinIP tunnel LMA and MAG.
LMA
Home Network MN’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.
KT 세미나

45. PMIPv6 Overview New entities Assumptions (or Restrictions)
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 mobile node's attachment to the link and for signaling the MN's LMA
Assumptions (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
Support both Steteless and Stateful address configuration modes
KT 세미나

46. PMIPv6 Operation Flow MN MAG AAA&Policy Store LMA CN DHCP Server
PBU: Proxy Binding Update PBA: 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)
KT 세미나

47. PMIPv6 Features Home in Any Place
Network Entry (or Handover) Procedures
After MN attachment, MAG gets MN’s profile
MN-Identity
LMA address and other configuration parameters
Obtain MN’s home network prefix information
Static Scheme
Get it from Profile
Dynamic Scheme
Get it from LMA via PBU/PBA
Now MAG have enough information to emulate MN’s home link
Send the RA (Router Advertisement) messages advertising MN’s home network prefix and other parameters
MN will always obtain its “home network prefix”, any where in the network.
MAG runs on the access router will emulate the home link on its access link.
It will ensure that MN believes it is at its home.
KT 세미나

48. PMIPv6 Features Proxy Registration
LMA needs to understand the Proxy Registration
RFC 3775 MIPv6 BU/Back Reuse
PBU (Proxy Binding Update)
PBA (Proxy Binding Acknowledgement)
KT 세미나

49. PMIPv6 Features M:1 Tunnel LMA’s Prefix-based Routing
LMA-MAG tunnel is a shared tunnel among many MNs.
1:1 relation  m:1 relation
One tunnel is associated to multiple MNs’ Binding Caches.
Life-time of a tunnel should not be dependent on the life time of any single BCE.
LMA’s Prefix-based Routing
LMA will add prefix routes to MN’s home network prefix over the tunnel.
Routing State for a MN stored in LMA
KT 세미나

50. PMIPv6 Features MAG establishes IPv6 in IPv6 tunnel with LMA
RA (Router Advertisement) should be UNICASTed to an MN
It will contain MN’s Home Network Prefix
Routing State for a MN stored in MAG
KT 세미나

51. 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)
KT 세미나

52. IPv4 Support for PMIPv6
KT 세미나

53. IPv4 Support for PMIPv6 Two functions supported
IPv4 Transport Network Support
IPv6 in IPv4 tunnel, IPv4 in IPv4 tunnel, NAT Traversal
IPv4 Home Address Mobility
An IPv4-only or dual-stack MN will be able to obtain an IPv4 address (IPv4-MN-HoA) and will be able to roam in that PMIPv6 domain using that address.
The signaling protocol is based on Proxy Mobile IP6.
KT 세미나

54. IPv4 Support for PMIPv6
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
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-00.txt, May 2007 CN HA
Tunneled to IPv6 CoA
v4 Network
IPv4 Packet
v6 Network
Movement
Tunneled to IPv4 CoA
IPv6 Packet CN
v6 Network
v4 Network
NAT
Tunneled to private IPv4 CoA
Private v4 Network
Movement
KT 세미나

55. IPv4 Support for PMIPv6 PMIPv6’s IPv4 Support
[Mobility Binding]
V4 Addr. and V6 Addr.
Dual Stack MN or IPv4 MN
PBU (V6 Addr., Proxy CoA v6, V4 Addr.)
Proxy CoAv6
IPv4 traffic
CNv4  V4 Addr.
IPv6 Tunnel (LMAAv6->Proxy CoAv6)
Dual Stack MAG
Dual Stack LMA
IPv6 traffic
CNv6->V6 Addr.
<MN in IPv6 domain>
[Mobility Binding]
V4 Addr. and V6 Addr.
Dual Stack MN or IPv4 MN
PBU (V6 Addr., Proxy CoA v6, V4 Addr.)
Proxy CoAv4
IPv4 traffic
CNv4  V4 Addr.
IPv4 Tunnel (LMAAv4->Proxy CoAv4)
Dual Stack MAG
Dual Stack LMA
IPv6 traffic
CNv6->V6 Addr.
<MN in IPv4 domain>
KT 세미나

56. MIPv6 & PMIPv6 Interworking
KT 세미나

57. 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).
KT 세미나

58. Case #1. MN in a Home Domain
PMIPv6 and MIPv6 Interworking
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
KT 세미나

59. PMIPv6 and MIPv6 Interworking
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
KT 세미나

60. PMIPv6 and MIPv6 Interworking
Case #3. MN moves to a new domain
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
Both MIPv6 and PMIPv6 are operated!
MN obtains MN-HoA #2
MN maintains two addresses
- MIPv6-HoA = MN-HoA #1
MIPv6-CoA = MN-HoA #2
PMIPv6 Domain #1 (Mobile IPv6 Home Domain)
KT 세미나

61. Summary
PMIPv6 can be a way to facilitate the deployment of IP mobility
Reuse deployed infrastructure & Mobile IPv6 functionality
Favorable to ISPs
PMIPv6 is New Idea?
Absolutely No!, but new trend!. It’s a turn for the better!
PMIP is a good example of compromise
Until now, long confrontation
Telecommunication Operators  Internet Developers and Users
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 /WiBro (Cross-layering Issues)
New Research Areas using PMIPv6
Network-based Global Mobility
PMIPv6-based NeMo (MANEMO)
PMIPv6-based 6LowPAN Sensor Node Mobility
KT 세미나