1. 1 DSMIP6 Support QUALCOMM Inc. Jun Wang, George Cherian, Masa Shirota jwang/gcherian/mshirota@qualcomm.com jwang/gcherian/mshirota@qualcomm.com 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, non- discriminatory 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.

2. 2 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

3. 3 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. Access Network Visited Network MN HA DSMIPv6 Tunnel Local breakout Home Connection Home Network HA PDSN HoA1 HoA2 CoA Anchored Local breakout

4. 4 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 Access Network 2 Access network 1 DSMIPv6 HA MS DSMIP Single, access independent DSMIP PDSN GW CoA1 CoA2

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

6. 6 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 IPv4- only access networks »Both private and public IPv4 addresses are supported

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

8. 8 DSMIP6 Call Flow

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

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

11. 11 IP Services (IP Type) Selection Algorithm

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