1. 1 WLAN IW Enhancement for IMS Support QUALCOMM:Raymond Hsu, rhsu@qualcomm.com Masa Shirota, mshirota@qualcomm.com KDDI:Kazushi Imamoto, kaz-imamoto@kddi.com Ryuhei Munakata, ry-munakata@kddi.comry-munakata@kddi.com Starent: Kuntal Chowdhury, kchowdhury@starentnetworks.comkchowdhury@starentnetworks.com NEC:Tomomichi Nogai, t-nogai@cj.jp.nec.com Fujitsu: Hitoshi Shibayama, shibayama.h@jp.fujitsu.comshibayama.h@jp.fujitsu.com Hitachi:Naruhito Nakahara, naruhito.nakahara.az@hitachi.com Koji Watanabe, koji.watanabe.az@hitachi.com Notice: Contributors grant 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. 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 Introduction The approved WLAN Enhancement WID [X10- 20061030-009r3] include the following items. –PDIF supports SBBC for QoS enforcement, charging rules, etc. –MS and PDIF may use null encryption. One usage example is not to encrypt IP packets, between MS and PDIF, that carry SIP signaling, because these packets are already encrypted between MS and P-CSCF.

3. 3 Proposal for SBBC Support After successful IKEv2 negotiation with a MS, PDIF establishes a Diameter session with PCRF for that MS. This allows PCRF to push subsequent PCC rules to the PDIF, when the MS establishes a new session (e.g., SIP call). Uses the Push model specified in X.P0013-012 (SBBC Stage 2) –During SIP call establishment, “Install PCC Rules” (charging, authorized QoS) are pushed from the PCRF to the PDIF. –During SIP call termination, “Update PCC Rules” are pushed from the PCRF to the PDIF. Because SBBC push is used, MS doesn’t need to send TFT and QoS request to PDIF. This proposal is also applicable to non-IMS services.

4. 4 Proposal for SBBC Support

5. 5 Proposal for Null Encryption Support During the initial IKEv2 negotiation, default SA is established to apply encryption on all traffic (non-IMS packets). –Set traffic selectors such that the default SA is applied to all traffic destined for (and originated from) the MS. If MS does not want to encrypt IP packets, between MS and PDIF, that carry SIP signaling, –MS uses Create-Child-SA exchange to establish null-encryption SA for SIP signaling; for this SA, MS can set traffic selectors to SIP client/server port numbers or P-CSCF’s address. –MS can obtain the SIP client/server port numbers via the exchange of SIP REGISTER/401. –MS can obtain the P-CSCF’s address via the P-CSCF discovery procedure. If MS does not want to encrypt other IP flows between MS and PDIF, MS uses the Informational exchange to update traffic selectors in the null- encryption SA.

6. 6 Recommendation Discuss and Adopt the proposals for the WLAN IW enhancements.