1. IETF에서의 이동성 관련 표준화 상황 -Proxy Mobile IPv6 (PMIPv6) 중심으로-
Youn-Hee Han
Korea University of Technology and Education Internet Computing Laboratory

2. Outline Background PMIPv6 (Proxy Mobile IPv6) Overview PMIPv6 Features
Some related technologies of PMIPv6
IPv4 Support for PMIPv6
PMIPv6 and MIPv6 (Mobile IPv6) Interworking
69th IETF NetLMM WG Report
PMIPv6 Handover Latency
69th IETF General Report
SG19

3. Background
SG19

4. 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 OS
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!).
SG19

5. 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
SG19

6. Background
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,68th IETF ( , , )
The one of very active WGs in IETF meetings
Almost 150~200 persons usually participates in the NetLMM WG
Proxy Mobile IPv6 (PMIPv6) adopted as WG item
69th IETF ( )
PMIPv6-01 introduced
Other issues brought up
Route optimization, Fast Handover, MIPv6 interaction, Multi-homing, etc.
SG19

7. 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)
SG19

8. 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.
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-01.txt, June 18, 2007.
SG19

9. 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
SG19

10. PMIPv6 Overview LMA MAG MAG
LMA: Localized Mobility Agent MAG: 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 (PBU)
Control message sent 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
SG19

11. 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
SG19

12. 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)
SG19

13. PMIPv6 Features Home in Any Place
Network Entry (or Handover) Procedures
After MN attachment, MAG gets MN’s profile
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 has enough information to emulate MN’s home link
Send the RA (Router Advertisement) messages advertising MN’s home network prefix and other parameters
MAG runs on the access router 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.
SG19

14. 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)
SG19

15. PMIPv6 Features M:1 Tunnel
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.
RA (Router Advertisement) should be UNICASTed to an MN
It will contain MN’s Home Network Prefix
SG19

16. PMIPv6 Features LMA’s Prefix-based Routing
LMA will add prefix routes to MN’s home network prefix over the tunnel.
MAG establishes IPv6 in IPv6 tunnel with LMA
Routing State for a MN stored in LMA
Routing State for a MN stored in MAG
SG19

17. 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)
SG19

18. 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.
SG19

19. 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
SG19

20. 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>
SG19

21. 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).
SG19

22. 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
SG19

23. 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
SG19

24. 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)
SG19

25. 69th IETF NetLMM WG Report
Base protocol and IPv4 support reasonably stable
More reviews and updates needed before the documents can be sent to last call
PMIP6-MIP6 interactions work in progress
Next steps to be discussed after current work progress to last call
IETF NetLMM WG Milestones
Done Initial version of the Protocol draft submitted
Done Initial version of the IPv4 support document
Aug 07 Initial version of the PMIP6-MIP6 interactions document
Aug 07 WG LC on MN-AR document
Aug 07 WG LC on the Protocol document
Sep 07 WG LC on the IPv4 support document
Oct 07 WG LC on the PMIP6-MIP6 Interactions document
Oct 07 Submit Protocol, IPv4 support and MN-AR documents for AD review
Nov 07 Submit PMIP6-MIP6 Interactions document for AD review
Dec 07 Re-charter
SG19

26. PMIPv6 Handover Latency Comparison
Mobile IPv6
SG19

27. PMIPv6 Handover Latency Comparison
Hierarchical Mobile IPv6 (Intra-domain)
SG19

28. PMIPv6 Handover Latency Comparison
Proxy Mobile IPv6
SG19

29. PMIPv6 Handover Latency Comparison
<<
<
SG19

30. Conclusions & Discussion
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!
PMIPv6 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!
In the handover latency aspect, PMIPv6 is very good protocol!
SG19

31. Conclusions & Discussion
(In near future) More Studies Needed
Route Optimization in PMIPv6
Fast Handover in PMIPv6
Multihoming
Cross-layering Issues
PMIPv6 over IEEE /WiBro
New Research Areas
Network-based Global Mobility
PMIPv6-based NeMo (MANEMO)
PMIPv6-based 6LowPAN Sensor Node Mobility
SG19

32. 69th IETF General Report 1146 people 40 countries 120 WGs
IETF66 - Montreal: 1236 total
40 countries
IETF66 - Montreal: 44
120 WGs
2 New WGs, 10 Closed WGs
103 RFCs published
47 Standards Track; 5 BCP
IETF has Budget problem
Meeting Fee 인상 예상
SG19

33. 69th IETF General Report
SG19

34. 69th IETF General Report
SG19

35. 69th IETF General Report
SG19

36. 69th IETF General Report Some Movements MEXT : MIP6, NEMO, MONAMI6
Chartering is almost done
Sensor Networks: 6lowpan, RSN(RL2N)
Many IRTF Research Group Meetings
SG19