1 Subject:Draft Responses to BBF Comments re. cdma2000 MO Preview Date: 25 January 2010 Source: Doug Knisely TSG-X FMOAHG Co-chair, BBF Liaison Contact: cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Airvana, Inc., 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. Airvana, Inc., is 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 Airvana, Inc., 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 Airvana, Inc. Airvana, Inc., specifically reserves the right to amend or modify the material contained herein and to any intellectual property of Airvana, Inc.,other than provided in the copyright statement above.

2 Proposed Responses from to BBF from FMOAHG that Require Consideration by TSG-X MMD Responses to Specific Comments (Relative to X R1)

3 Specific Comments from BBF (3) FAPservice.{i}.Transport.SIP.FCS – Consider either re-using TR-104 SIP object (Note: unlikely since the TR-104 object is for a generic SIP VoIP object, not for IMS.) or at least re-using the same attribute names and descriptions when they seem to be identical  Recommend harmonizing the attribute names, but not trying to re-use the object. Double check that attribute names are harmonized. 643 – OutGoingProxyUri – Should we define a separate URI for the RegistrarServer attribute (which is semantically typical for SIP provisioning)  Liaise to MMD. 643 – OutGoingProxyUri – Should we include Transport Protocol attributes for OutGoingProxyUri (and RegistrarServerUri), similar to TR-104 SIP object, even if the transport protocol is fixed for cdma2000 1x FAP usage?  Liaise to MMD. Seems unnecessary for our purposes given that we aren’t re-using the entire object. However, the transport stack may not be defined in X.S0059 Stage 3. Needs to be investigated.