Introduction - IEEE 802.16 Working Group on Broadband Wireless

advertisement
IEEE C802.16m-09/2126r2
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
suggested remedy for the comment #244
Date
Submitted
2009-09-20
Source(s)
Youngkyo Baek
E-mail:
Phone :
Samsung Electronics
youngkyo.baek@samsung.com
+82-31-279-7321
*<http://standards.ieee.org/faqs/affiliationFAQ.html>
Shraga Avishay
Xiangying Yang
Intel Corporation
Gene Beck Hahn
LG Electronics
Chengyan Feng
ZTE Corporation
Re:
IEEE 802.16 Working Group Letter Ballot #30, on P802.16m/D1
Abstract
suggested remedy for the comment #244
Purpose
Accept the proposed specification changes on IEEE 802.16m/D1
Notice
Release
Patent
Policy
This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It
represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for
discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material
contained herein.
The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution,
and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name
any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole
discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The
contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.16.
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and
<http://standards.ieee.org/guides/opman/sect6.html#6.3>.
Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and
<http://standards.ieee.org/board/pat>.
suggested remedy for the comment #244
Youngkyo Baek
Samsung Electronics
Shraga Avishay
Xiangying Yang
Intel Corporation
Gene Beck Hahn
1
IEEE C802.16m-09/2126r2
LG Electronics
Chengyan Feng
ZTE Corporation
Introduction
This contribution proposes the suggested remedy for the comment #244.
Proposed Text
Adopt the proposed text as a suggested remedy for comment #244 (subclause 15.2.5.2.3, page 39 line3).
----------------------------------------------------- Start of Proposed Text --------------------------------------------------The maintenance of cached PMK and AK by either AMS or ABS does not differ from reference system. Besides, the
PMK and AK switching methods does not differ from reference system.
The active PMK and AK are maintained as follows:
a) PMK context management - An AMS and an Authenticator cache a new PMK context upon successful completion
of key agreement procedure. Upon caching a new PMK for a particular AMS and completing TEK update procedure
(updating both TEKs in each SA to be derived from the new PMK), any older PMK for that AMS (as well as all
associated derived keys) shall be discarded. For the case of full reauthentication or PMK update through keyagreement, deletion of old PMKs is done after full TEK update following the switchover mechanism described in this
sub clause.
b) AK activation and deactivation. Successful completion of the key agreement 3-way handshake causes the
activation of the AK associated with the new PMK on any BS under the current Authenticator (i.e., when the AMS
hands over or re-enters a target ABS, and the key agreement 3-way handshake associated with the newest PMK has
completed successfully at former ABS under the target ABS’s Authenticator, the AK associated with the newest PMK
and the target ABS is used without a new key agreement 3-way handshake at the target ABS). If CMAC_PN or
CMAC_KEY_COUNT reach their maximum value, the associated AK as well as PMK becomes permanently
deactivated. The ABS and AMS shall maintain the AK context as long as they retain the AK.
Once the key agreement 3-way handshake begins, the ABS and AMS shall use the new AK matching the new PMK
context for the key agreement MSG#2 and key agreement MSG#3 messages. The other MAC management messages
shall continue to use the old AK until the key agreement completes successfully. Upon successful completion of the
key agreement 3-way handshake, CMAC key from the new AK shall be used. The old AK matching the old PMK
context may be used for receiving packets before completion of TEK update procedure following the key agreement
3-way handshake.
--------------------------------------------------- End of Proposed Text------------------------------------------------------
2
Download