ietf 에서의 이동성 관련 표준화 상황 -proxy mobile ipv6 (pmipv6) 중심으로 - youn-hee...
TRANSCRIPT
IETF 에서의 이동성 관련 표준화 상황-Proxy Mobile IPv6 (PMIPv6) 중심으로 -
Youn-Hee [email protected]
Korea University of Technology and EducationInternet Computing Laboratory
http://icl.kut.ac.kr
SG192/36
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
Outline
SG193/36
Background
SG194/36
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!).
SG195/36
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 theWLSM through your Layer 3 core network. No changes to the client devices or the underlying infrastructure are required
Background
SG196/36
IETF NetLMM WG started to standardize a network-based mobility management protocol.
63th IETF (2005.7) The first NetLMM BoF
64th IETF (2005.11) The second NetLMM BoF
65th IETF (2006.03) The first NetLMM WG
66th,67th,68th IETF (2006.07, 2006.11, 2007.03) 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 (2007.07) PMIPv6-01 introduced Other issues brought up
Route optimization, Fast Handover, MIPv6 interaction, Multi-homing, etc.
Background
SG197/36
IETF NetLMM WG History
NetLMM DT solution (draft-giaretta-netlmm-dt-protocol) : designed from the scratchCisco’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)
SG198/36
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.
Internet Drafts of PMIPv6
SG199/36
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.
Goal of PMIPv6
PMIPv6 Scenario(being extended)
registration
SG1910/36
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: Localized Mobility AgentMAG: 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
SG1911/36
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 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
SG1912/36
PMIPv6 Operation Flow
MN MAG AAA&Policy Store LMA CN
MN Attachment AAA Query with MN-ID
AAA Reply with ProfileRA*
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
SG1913/36
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.
SG1914/36
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)
SG1915/36
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
SG1916/36
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 LMARouting State for a MN stored in MAG
Routing State for a MN stored in LMA
SG1917/36
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)
SG1918/36
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.
SG1919/36
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
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
CN
CN
IPv4 Support for PMIPv6
SG1920/36
IPv4 Support for PMIPv6
PMIPv6’s IPv4 Support
Dual Stack LMA
Dual Stack MNor
IPv4 MN
PBU (V6 Addr., Proxy CoA v6, V4 Addr.)
V4 Addr. and V6 Addr.
Proxy CoAv6
[Mobility Binding]
IPv6 Tunnel (LMAAv6->Proxy CoAv6)
IPv4 trafficCNv4 V4 Addr.
IPv6 trafficCNv6->V6 Addr.
Dual Stack MAG
<MN in IPv6 domain>
Dual Stack LMA
Dual Stack MNor
IPv4 MN
PBU (V6 Addr., Proxy CoA v6, V4 Addr.)
V4 Addr. and V6 Addr.
Proxy CoAv4
[Mobility Binding]
IPv4 Tunnel (LMAAv4->Proxy CoAv4)
IPv4 trafficCNv4 V4 Addr.
IPv6 trafficCNv6->V6 Addr.
Dual Stack MAG
<MN in IPv4 domain>
SG1921/36
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).
PMIPv6 and MIPv6 Interworking
SG1922/36
Case #1. MN in a Home Domain
PMIPv6 Domain #1(Mobile IPv6 Home Domain)
MIPv6-HoA = MN-HoA #1
MIPv6-Home Agent = LMA #1
HoAHoA CoACoA
Binding Cache
Proxy FlagProxy Flag
MN-HoA #1MN-HoA #1 MAG#1-1’s Addr.MAG#1-1’s Addr. 11
PMIPv6 Domain #2 PMIPv6 Domain #3
MAG #1-2MAG #1-1
Proxy BU
In the interior of MN, MIPv6-CoA is not needed since all MAGs will emulate the home link.
PMIPv6 and MIPv6 Interworking
SG1923/36
PMIPv6 Domain #2 Non-PMIPv6 Domain
PMIPv6 is operated!Still… MIPv6-HoA = MN-HoA #1
Proxy BU
MIPv6-Home Agent = LMA #1
PMIPv6 Domain #1(Mobile IPv6 Home Domain)
MAG #1-1 MAG #1-2
In the interior of MN, MIPv6-CoA is still not needed since all MAGs will emulate the home link.
HoAHoA CoACoA
Binding Cache
Proxy FlagProxy Flag
MN-HoA #1MN-HoA #1 MAG#1-2’s Addr.MAG#1-2’s Addr. 11
Case #2. Movement in a Home Domain
PMIPv6 and MIPv6 Interworking
SG1924/36
PMIPv6 Domain #2 Non-PMIPv6 Domain
Both MIPv6 and PMIPv6 are operated!MN obtains MN-HoA #2
LMA #2MIPv6 BU
MIPv6-Home Agent = LMA #1
PMIPv6 Domain #1(Mobile IPv6 Home Domain)
MAG #2-1
MAG #2-2
HoAHoA CoACoA
Binding Cache
Proxy FlagProxy Flag
MN-HoA #1MN-HoA #1 MN-HoA #2MN-HoA #2 00
Proxy BUHoAHoA CoACoA
Binding Cache
Proxy FlagProxy Flag
MN-HoA #2MN-HoA #2 MAG#2-1’s Addr.MAG#2-1’s Addr. 11
MN maintains two addresses- MIPv6-HoA = MN-HoA #1- MIPv6-CoA = MN-HoA #2
Case #3. MN moves to a new domain
PMIPv6 and MIPv6 Interworking
SG1925/36
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 progressNext steps to be discussed after current work progress to last callIETF 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
SG1926/36
PMIPv6 Handover Latency Comparison
Time
DAD on New CoA
Link-layer handover comes to end
Send NS(for DAD)
ReceivePacketsfrom CN
Send BU to HA
Receive BAck from HA
MN
Movement Detection
Total Handover Latency
Send BUto CN
2tN
Send HoTI and CoTIto CN
Return Routability
Receive HoT and CoTfrom CN
max {2tL : 2tN }
Binding Update to CN
TMD
Binding Update to HA
2t H
Registration
TDAD
TR
Mobile IPv6
SG1927/36
Hierarchical Mobile IPv6 (Intra-domain)
DAD on New LCoA
Send NS(for DAD)
MN
Movement Detection
TDADTMD
MAP
Send BU to MAP
MN->MAP Latency
t M
MAP->MN Latency
Registration(Binding Update to MAP)
t M
Receive BAck & Packets
from MAP
Total Handover Latency (Intra-domain Movement)
Time
THR
Link-layer handover comes to end
s
PMIPv6 Handover Latency Comparison
SG1928/36
Proxy Mobile IPv6
PMIPv6 Handover Latency Comparison
MN
LMA
MAG->LMA Latency
t G
LMA->MAG Latency
Registration(Binding Update to LMA)
t G
MAG receive PBAck from LMA
Total Handover Latency
Time
TLR
Link-layer handover comes to end
AR/MAG
MAG sends PBU to LMAMN receives RA and data packets
SG1929/36
Comparison
<< <
PMIPv6 Handover Latency Comparison
SG1930/36
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!
Conclusions & Discussion
SG1931/36
(In near future) More Studies Needed Route Optimization in PMIPv6 Fast Handover in PMIPv6 Multihoming
Cross-layering Issues PMIPv6 over IEEE 802.16/WiBro
New Research Areas Network-based Global Mobility PMIPv6-based NeMo (MANEMO) PMIPv6-based 6LowPAN Sensor Node Mobility
Conclusions & Discussion
SG1932/36
69th IETF General Report
1146 people 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 인상 예상
US JP KRDE FR UKCA China Others
SG1933/36
69th IETF General Report
SG1934/36
69th IETF General Report
SG1935/36
69th IETF General Report
SG1936/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