1. 1 Notice Contributors grant a free, irrevocable license to 3GPP2 and its Organization 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 portions of the contribution; and at the Organization Partner’s sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication. 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. Contributors specifically reserve 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. Title:Tethered Device Call over MIPv6 in cdma2000 Source:Vinay Paradkar/Jun Wang/Masa Shirota QUALCOMM Incorporated Date:March 31, 2008 Recommendation:Discuss and adopt. 3GPP2 Meeting, March, 2008

2. 2 Introduction MN needs to support multiple tethered devices which can access data network via MN air interface –Example – Laptop, PDA etc. These devices need to have access to “Home Network” over Mobile IPv6 via the MN This requires MN supporting MIPv6 to be –Common node for carrying out the MIPv6 registration on behalf of all these tethered devices –Aggregator of the flows emerging from the tethered devices, to be routed via the HA –Router for the flows terminating at the tethered devices

3. 3 Requirements MN should support multiple tethered devices for a MIPv6 call MN should support embedded MIPv6 call simultaneously while supporting tethered MIPv6 calls Each of the tethered devices should have separate Home Address –Based on common unique home prefix –Randomly generated IID MN should be able to register with HA –To apprise the HA of its current point of attachment (CoA) –To establish a data tunnel with the HA –To aggregate all traffic emerging from the tethered devices –To route all traffic terminating at the tethered devices appropriately Need to minimize/optimize MIPv6 signaling traffic required to register each of the generated HoA’s, with the HA Need to reduce IPsec state associated with each of the HoA’s thus generated by MN if IPsec is used In summary, it is required for the MN to support a mobile network behind it with MN as the common (router) point of attachment

4. 4 Standards References MIPv6 base specification [R1] does not deal with mobile networks and the issues involved NEMO (Network Mobility) base specification [R2] discusses the issue and provides a framework for the solution –It allows MN to support a unique prefix to support multiple nodes with their own distinct home addresses –For the MN to act as a router for the Mobile Network supported by the MN Current 3GPP2 standards [S1][S2][S3], similarly, deal with MN as a host and not as a mobile router [S1][S2][S3] do not have provision to assign unique home prefix for each MN –This is required and standards need to be amended to include this requirement

5. 5 NEMO Highlights A Mobile Network consists of a Mobile Router (MR) supporting a set of nodes connected to it –MR acts as default gateway for the nodes connected to it –MR manages the mobility of the mobile network with the Home Agent –The nodes connected to MR remain transparent to the network mobility MR is assigned a unique prefix (or a set of prefixes) from the home network –MR can advertise that prefix to the nodes connected to it as a default router –On movement away from the home network –MR apprises the HA of its current CoA with a Binding Update –MR also registers the prefix(es) it is managing with the HA using the same BU –MN seeks to act as a MR by setting ‘R’ flag in the BU NEMO aware HA can process BU with ‘R’ flag set –HA registers current CoA for MN’s HoA and sets up an IP-in-IP tunnel with MN –HA sets up forwarding for the prefix for the Mobile Network via HA-MN tunnel –HA aggregates the Mobile Network’s prefix such that any packet destined to the Mobile Network is routed through the HA –HA responds to the MR’s BU with BA which has ‘R’ flag set

6. 6 Mobile Network Prefix Registration MR can include a Mobile Network Prefix option in the BU to indicate the prefix information to the HA –There could be multiple Mobile Network Prefix options one for each prefix supported by the MR –HA sets up forwarding for each prefix registered via Mobile Network Prefix option Prefix registration can happen in one of the following modes –Implicit mode –MR does not include Mobile Network Prefix option in the BU –HA relies on other mechanisms (For example – Static/Manual configuration) to determine the prefix(es) owned by the MR and set up forwarding for them –Explicit mode –MR explicitly includes the prefix(es) it supports in the BU –HA uses the prefix(es) in the BU to set up forwarding for the Mobile Network

7. 7 Prefix Delegation Prefix Delegation refers to the process by which an MR can dynamically obtain prefix(es) for the Mobile Network [R3] discusses the issue of dynamic prefix delegation for the Mobile Network –It introduces two new mobility options to aid dynamic assignment of Mobile Network Prefix(es) –Mobile Network Prefix Request option –Mobile Network Prefix Confirm option –It introduces new flags in BU/BA messages as well as the Mobile Network Prefix option to aid in dynamic prefix delegation management –It provides a possible framework for centralized dynamic prefix assignment for Mobile Networks –It allows the Mobile Network prefixes to have a lifetime –It is a work in progress

8. 8 NEMO for 3GPP2 Networks Base NEMO standard can be adopted as is by the 3GPP2 standards –It will solve the issue of MN supporting multiple tethered devices over MIPv6 –MN can also support embedded calls simultaneously over MIPv6 Changes in 3GPP2 standards required for NEMO support –Allocation of a unique home prefix per MN –This can be done by the AAA or HA –MN should be required to be NEMO aware and act as an MR –HA in 3GPP2 Networks should support NEMO functionality

9. 9 Proposal for Mobile Network Prefix Delegation Unique prefix assignment can be achieved in following two ways in 3GPP2 networks 1.Utilizing DHCPv6 bootstrapping as specified in [S1] –The bootstrapping procedures for MIPv6 include the provision for assignment of Home Prefix along with the Home Agents address –This information is stored in PDSN and MN acquires it via DHCPv6 signaling –In this case the AAA manages the unique prefix assignment to the MN via 3GPP2 signaling between AAA and PDSN –AAA also needs to communicate the prefix to HA via 3GPP2 signaling so that HA can expect a BU from the MN 2.Utilizing dynamic HoA assignment during the IKEv2 negotiation phase for MIPv6 as specified in [S2] [S3] –MN can request the primary HoA as a configuration parameter during IKEv2 negotiations with the PDIF or HA –The HA returns the primary HoA/HL Prefix length in INTERNAL_IP6_ADDRESS configuration parameter or the PDIF returns the primary HoA/HL prefix length in 3GPP2_MIP6_HL attribute –MN can derive the home prefix from the supplied HoA and the home prefix length –The HA or HAAA is the entity managing the prefix assignment to the MN Since all 3GPP2 entities (AAA,MN,HA) involved in MIPv6 know the assigned prefix, MN can use implicit mode to register the Mobile Network prefix with the HA –This reduces the size of signaling messages

10. 10 Recommendations Add the proposal in IS-835-D addendum Add the proposal in MIPv6 Enhancement (X.P0047) Add the proposal in WLAN Interworking Stage 3 text changes for all above documents are submitted as separate contributions

11. 11 References [R1] RFC 3775 – Mobility Support in IPv6 [R2] RFC 3963 – Network Mobility (NEMO) Basic Support Protocol [R3] draft-ietf-nemo-prefix-delegation-02.txt [S1] TIA-835-2D – CDMA 2000 Wireless IP network standard [S2] X.P0047-0v0.5 – 3GPP2 Mobile IPv6 Enhancement [S3] X.S0028 – WLAN Interworking