Transcript DSMIPv6

DSMIP6 Support
QUALCOMM Inc.
Jun Wang, George Cherian, Masa Shirota
jwang/gcherian/[email protected]
Notice ©2009. All rights reserved.
The contributors grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other
copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications;
to copyright and sell in Organizational Partner’s name any Organizational Partner’s standards publication even though it
may include all or portions of this contribution; and at the Organizational Partner’s sole discretion to permit others to
reproduce in whole or in part such contribution or the resulting Organizational Partner’s standards publication. The
contributors are also willing to grant licenses under such contributor copyrights to third parties on reasonable, nondiscriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this
contribution.
This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed
to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. The
contributors specifically reserves the right to amend or modify the material contained herein and nothing herein shall be
construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than
provided in the copyright statement above.
1
Why Do We Need DSMIP6?
• Provides optimal global mobility and roaming solution for 3G and
Beyond 3G multi-access systems
• Allows faster deployment of IPv6 without having to upgrade PDSN for
support of IPv6 transport
• No impact on IPv4 based applications
–
•
Currently many applications are IPv4 based
Allows multiple HAs connectivity over already deployed CDMA access
network
–
Inbuilt support for simultaneous local breakout and home routed traffic
•
Allows the MS to reach the home agent using multiple access networks
simultaneously.
•
Simpler and more effective security model (IPsec between MS and HA)
both for IPv4 and IPv6 applications
Supports different access types, including 3GPP and 3GPP2 access systems
and WiFi without any changes to those access networks that are already
deployed
•
–
Minimizes access network complexity
2
Multiple HAs connectivity
• In DSMIPv6 the access network always has single IP connection ( CoA)
between itself and MS
– The access network allocates a simple IP address for the MS
• The MS can be assigned with multiple HoAs
• The MS uses this single simple IP connection as needed:
– LBO traffic without any tunneling
– DSMIP tunneled traffic anchored at home network
– DSMIP tunneled LBO traffic anchored at visited network (Dynamic HA)
All this is transparent to the access network.
Anchored
Local breakout
Visited Network
HoA1
Local
HA
breakout
Access Network
CoA
HoA2
PDSN
MN
Home Network
HA
DSMIPv6 Tunnel
3
Home Connection
Multiple Access Connections
• The MS can connect to the home agent using multiple access networks
simultaneously.
– Easy extendibility to support IP-flow/service based mobility between access systems
• DSMIP is independent of the access network mechanisms
• DSMIP has it's own E2E signaling, no need to convey access specific
information to mobility anchor (HA)
• No drive to have different flavors of DSMIP for different types of access
systems
• See draft-ietf-monami6-multiplecoa-13.txt
PDSN
Access network 1
CoA1
Single, access
independent DSMIP
DSMIP
MS
GW
Access Network 2
CoA2
4
DSMIPv6
HA
MIPv6
• Defined in RFC3775, RFC 4877 and RFC 5026
• MN and HA share an IPsec security association
• MN has one Home Address (HoA) which is bound to a
Care-of Address (CoA) through Binding Update messages
– HoA is IPv6
– CoA is IPv6
• Implications
– HoA is IPv6: only IPv6 applications can be used
– CoA is IPv6: access network must support IPv6 – the MN cannot
move into an IPv4-only access network (In current 3GPP2
networks, the MN can use IPv4/MIPv4 for IPv4 access network.)
5
DSMIPv6
• Defined in draft-ietf-mext-nemo-v4traversal-10
• DSMIPv6 extends MIPv6 to address the
limitations mentioned in the previous slide
– MN can have an IPv4 HoA in addition to IPv6 HoA and
run IPv4 applications
– CoA can be also IPv4: the MN can also move to IPv4only access networks
» Both private and public IPv4 addresses are supported
6
DSMIPv6: how it works
• MN obtains CoA from the Access Network
– The CoA can be IPv4 or IPv6 depending on Access network
• MN always has an IPv6 HoA obtained via IKEv2 from HA
• In addition, MN can request an IPv4 HoA in the BU/BA
exchange
• When MN is in IPv4 access network
– MN configures/obtains an IPv4 CoA from the access network
– MN sends a BU with IPv4 CoA to the IPv4 address of the HA
» BU is an IPv6 packet tunneled in IPv4
– Data are tunneled to the HA via an IPv6 in IPv4 tunnel (if IPv6
HoA is used) or an IPv4 in IPv4 tunnel (if IPv4 HoA is used)
• BU/BA are used for NAT detection
– In case of NAT is detected packets are tunneled over UDP/IPv4
7
DSMIP6 Call Flow
MS
AN
MS generates IPv6 global unicast
address via IPv6 stateless address
autoconfiguration
PDSN
HA
HAAA
1. IPv6 Router Advertisment
w/Prefix
And/or
1' MS obtains IPv4 address
2. MS performs MIP6/
DSMIP6 HA address
discovery
3. IKE_SA_INIT message exchange
4. IKE_AUTH(IDi, CP(CFG_REQUEST), SAi)
5. EAP Exchanges via IKEv2
5. EAP Exchanges
(via AAA messags)
6. IKE_AUTH(AUTH)
7. IKE_AUTH{CP[CFG_REPLY(INTERNAL_IP6_ADDRESS=IPv6 HoA)], SAr, AUTH}
To/from
the Internet
8. MIP6 BU and BA message exchange (The MS binds IPv4 or IPv6 CoA with HoA. The HA
can assign additional IPv4 HoA to the MS.)
9. Bidirectional
Tunnel between MS and HA (IPv6 in IPv6, IPv4 in IPv6, IPv6 over IPv4, or IPv4 in IPv4)
IPv4 or IPv6
packets to/from
the MS
8
9. IPv4 or IPv6
packets
HA Discovery (1)
• Using DHCP mechanism:
– Already specified in X.S0011-D-2
» The PDSN shall support DHCPv6 Stateless Server Function (RFC 3736)
» The PDSN shall also support DHCPv6 proxy function for HA
assignment as defined in draft-ietf-mip6-hiopt-17.
• Home Network Information Option can be included in
Information-Request and Reply
– Home Network Identifier can be included
• The information delivered to the MS:
– Includes HA IP address or FQDN of the HA;
– May include Home Network Prefix.
» HA-Protocol-Capability in a DHCPv6 Vendor Specific option
has also been specified:
• Indicate to use auth protocol or IP sec
• May need a minor change to include DSMIP6 protocol with IPsec (not
critical)
9
HA Discovery (2)
• Using DNS Mechanism
– Specified in RFC 5026
– MS is pre- configured with the domain name of MSP
(Mobility Service Provider)
– Two DNS look up methods are specified:
» DNS lookup by HA name (FQDN of HA):
• For example: HA1.example.com (example. com is the domain name)
» DNS lookup by service name
• RFC 2782 specifies SRV RR (service resource record)
• For example: set QNAME to be “_mip6._ipv6.example.com” and QTYPE to be SRV
• The DNS server returns FQDN of HA (may include AAAA record as well to include
HA IP address)
10
IP Services (IP Type) Selection Algorithm
AT sends IPCP-Config-Req
(no-adderss-option)
An AT that supports
MIP6/DSMIP6
proceeds with the
further steps
Response from the PDSN
AT uses the IP
address (CCoA) that
is obtained
AT performs HA discovery
Successful HA Discovery?
AT is not on homelink or AT has no HNPrefix information
AT sets up IKEv2
session with the HA
No
Yes
If AT has HN-Prefix available (from
DHCP), AT checks the HN-prefix
to see if the AT is already connected
to HA/LMA
AT is already on
home-link
AT is already on
home-link
AT obtains HN-Prefix , AT checks
the HN-prefix
to see if the AT is already connected
to HA/LMA
AT is already connected
to HA/LMA using PMIP
(X.S0061)
AT is not on home-link
AT perform MIP6/
DSMIP6 BU/BA
AT is connected to HA
using MIP6/DSMIP6
IPCP-Config-Ack
(no address option)
IPCP-Config-Nak
(address option)
Network selected either
Simple-IP or PMIP (but
AT doesn’t know yet)
11
AT uses MIPv4 FA
mode based
procedure as
defined in X.S0011
Conclusions
• DSMIPv6 provides many benefits
– PDSN can continue to support IPv4 transport
– Support legacy IPv4 Applications
– Support WiFi Interworking
– Easy to add flow mobility support
• DSMIP is a very small delta on top of MIPv6
which is already supported in X.S0011-D
• Recommendation:
– Add DSMIPv6 support in X.P0011-E
12