May 2006 doc IEEE 802 11 060660 r

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 IEEE 802. 11 r: Fast BSS Transition TG Agenda Date: 2006 -05 -15 Authors: Notice: This document has been prepared to assist IEEE 802. 11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: 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. 11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http: // ieee 802. org/guides/bylaws/sb-bylaws. pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard. " Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stuart. kerry@philips. com> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802. 11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee. org>. Submission 1 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Abstract IEEE 802. 11 TGr May 2006 Agenda Submission 2 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Monday 15 May 2006, 10: 30 -12: 30 • • Call to Order Review IEEE 802 and 802. 11 Policies and Procedures – Intellectual Property Submission 3 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Instructions for the WG Chair • • At Each Meeting, the Working Group Chair shall: Show slides #1 and #2 of this presentation Advise the WG membership that: – The IEEE’s patent policy is consistent with the ANSI patent policy and is described in Clause 6 of the IEEE-SA Standards Board Bylaws; – Early disclosure of patents which may be essential for the use of standards under development is encouraged; – Disclosures made of such patents may not be exhaustive of all patents that may be essential for the use of standards under development, and that neither the IEEE, the WG, nor the WG Chairman ensure the accuracy or completeness of any disclosure or whether any disclosure is of a patent that, in fact, may be essential for the use of standards under development. Instruct the WG Secretary to record in the minutes of the relevant WG meeting: – That the foregoing advice was provided and the two slides were shown; – That an opportunity was provided for WG members to identify or disclose patents that the WG member believes may be essential for the use of that standard; – Any responses that were given, specifically the patents and patent applications that were identified (if any) and by whom. (Not necessary to be shown) Submission Approved by IEEE-SA Standards Board – March 2003 (Revised 4 January 2006) Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 IEEE-SA Standards Board Bylaws on Patents in Standards 6. Patents IEEE standards may include the known use of essential patents and patent applications provided the IEEE receives assurance from the patent holder or applicant with respect to patents whose infringement is, or in the case of patent applications, potential future infringement the applicant asserts will be, unavoidable in a compliant implementation of either mandatory or optional portions of the standard [essential patents]. This assurance shall be provided without coercion. The patent holder or applicant should provide this assurance as soon as reasonably feasible in the standards development process. This assurance shall be provided no later than the approval of the standard (or reaffirmation when a patent or patent application becomes known after initial approval of the standard). This assurance shall be either: a) A general disclaimer to the effect that the patentee will not enforce any of its present or future patent(s) whose use would be required to implement either mandatory or optional portions of the proposed IEEE standard against any person or entity complying with the standard; or b) A statement that a license for such implementation will be made available without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination. This assurance shall apply, at a minimum, from the date of the standard's approval to the date of the standard's withdrawal and is irrevocable during that period. Slide #1 Approved by IEEE-SA Standards Board – March 2003 (Revised January 2006) Submission 5 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Inappropriate Topics for IEEE WG Meetings • Don’t discuss the validity/essentiality of patents/patent claims • Don’t discuss the cost of specific patent use • Don’t discuss licensing terms or conditions • Don’t discuss product pricing, territorial restrictions, or market share • Don’t discuss ongoing litigation or threatened litigation • Don’t be silent if inappropriate topics are discussed… do formally object. If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee. org or visit http: //standards. ieee. org/board/pat/index. html This slide set is available at http: //standards. ieee. org/board/pat-slideset. ppt Slide #2 Approved by IEEE-SA Standards Board – March 2003 (Revised January 2006) Submission 6 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Copyright • Under the current US copyright law — the author of information is deemed to own the copyright from the moment of creation • The IEEE Bylaws require copyright of all material to be held by the IEEE – Must consult with IEEE for re-use of copyright material • The IEEE Standards accomplishes transfer of copyright ownership through the Project Authorization Request (PAR) process Submission 7 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 IEEE Ethics Submission 8 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Monday (cont. ) • • 15 May 2006, 10: 30 -12: 30 Does anybody have any questions about the patent policy? Does the WG chair need to be aware of any patents pertaining to this group? Please minute that notice was given, and the answer to the questions. Attendance – – – http: //newton/11/attendance http: //172. 16. 0. 10/11/attendance/ Local server (no VPN) Must register before logging attendance Must log attendance during each 2 hour session Submission 9 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Monday (cont. ) • • 15 May 2006, 10: 30 -12: 30 Minutes – Approval of Minutes of March 2006 Meeting - 11 -06 -0365 -01 -000 r-tgr-meeting-minutesmarch-2006 -session. doc – Approval of Minutes of March-May 2006 Teleconference Meetings - 11 -06 -0604 -02 -000 rtgr-teleconference-minutes-march-may-2006. doc – Approval of Minutes of April Ad-Hoc meeting – 11 -06 -0564 -01 -000 r-tgr-adhoc-meetingminutes-april-2006. doc Approve Agenda Submission 10 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Monday (cont. ) • 15 May 2006, 10: 30 -12: 30 2. 6 Motions – A motion may be made at any time during the meetings. However, a motion that changes a draft shall be presented in a submission that has been; • • • Accepted by document control (see 2. 5) Available electronically (via electronic wireless Wi-Fi™ medium or on the server). 1. WG draft – – – • 2. 3. 4. 5. 6. 1. 2. 3. 4. Press releases Liaison letters 802 EC Other WGs/Tags 1. 2. 3. To WG Liaison letters Press releases Internal Motions – – – Technical Editorial Technical Comment resolutions TG/SG/SC/Ad-Hoc External Motions – – – • 1. 2. 3. PARs and Five Critera WG External Motions – – • Technical Editorial Technical Comment resolutions TG draft – – – • • 1. 2. 3. 1. 2. Selection Criteria Functional requirements A motion that effects the technical content of the draft can only be voted on when its submission has been available to all voters who are participating in the session for a time not less than four WG session hours before the vote. Submission 11 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Monday (cont. ) • • • 15 May 2006, 10: 30 -12: 30 ftp: //802 server/11/Task_Group_Temporary/TGr/ Technical Issue #43 (Comment 867): Provide details of possible AP architectures and Network Topologies – Walker, Sood (by the June ad-hoc) Technical Issue #44 (Comment 1041): Provide measurements of the FT mechanisms to show that they actually work – Michael to ask TGT for any applicable info; redirect ad-hoc group to address question? Technical Issue #45: Define a "sub-protocol id" to distinguish between base mechanism and reservation mechanism – Walker, Sood to develop attack. (By June ad-hoc) Technical Issue #60: Resource reservation provisional or reserved – TGr to stay as silent in this area as TGe was. Michael to talk to commenter. Comment Resolution (until 12: 00) Motion: Accept all Editorial, Trivial Technical, and Technical resolutions to LB 82 comments, as agreed at the TGr ad-hoc meeting in April 2006, as highlighted in yellow and marked as part of Group #1 and Group #2 in 11 -06 -0537 -11 -000 r-d 2 -comments. xls Motion: Accept all Editorial, Trivial Technical, and Technical resolutions to LB 82 comments, as agreed at the TGr ad-hoc meeting in April 2006, as highlighted in yellow and marked as part of Group #3 in 11 -06 -0537 -11 -000 r-d 2 -comments. xls Motion: Accept all Editorial, Trivial Technical, and Technical resolutions to LB 82 comments, as agreed at the TGr ad-hoc meeting in April 2006, as highlighted in yellow and marked as part of Group #4 in 11 -06 -0537 -11 -000 r-d 2 -comments. xls Motion: Accept all Editorial, Trivial Technical, and Technical resolutions to LB 82 comments, as agreed at the ad-hoc group after the TGr ad-hoc meeting in April 2006, as highlighted in yellow and marked as part of Group #5 in 11 -06 -0537 -11 -000 r-d 2 -comments. xls Motion: Accept all Editorial, Trivial Technical, and Technical resolutions to LB 82 comments, as agreed at the TGr teleconferences, as highlighted in yellow and marked as part of Group #6 in 11 -06 -0537 -11000 r-d 2 -comments. xls Recess until Monday 13: 30 Submission 12 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Monday • • 15 May 2006, 13: 30 -15: 30 Attendance reminder Technical Issue #1, #63: Use of Reassociation/Association frames – – • Technical Issue #2: Assignment of frame types to Class 1/2/3 – – • 11 -06 -0603 -00 -000 r-initial-association-non-rsn. doc – Marshall (5 Minutes) Technical Issue #6: Use of Timeout IEs and MICs – • • • 11 -06 -0560 -01 -000 r-resource-types. doc – Marshall (5 Minutes) 11 -06 -0561 -00 -000 r-7 -3 -2 -46 -and-8 a-7 -reorg. doc – Marshall (5 Minutes) 11 -06 -0562 -00 -000 r-single-ric-ie. doc – Marshall (5 Minutes) Technical Issue #5: Initial association in non-RSN – • 11 -06 -0620 -00 -000 r-rrb-message-forwarding. doc – Marshall (5 Minutes) Technical Issue #35: Take out ability to make reservations (20 Minutes) Technical Issue #4, #14, #33, #36: RIC definition, examples, text re-org – – – • 11 -06 -0559 -00 -000 r-clause-5 -6 -option-2. doc – Marshall (5 minutes) 11 -06 -0558 -00 -000 r-clause-5 -6 -option-3. doc – Marshall (Only if 11 -06 -0559 Fails) Technical Issue #3, #48, #49, #51: RRB as forwarding only – • • 11 -06 -0554 -00 -000 r-ft-use-reassociation. doc – Marshall (5 minutes) 11 -06 -0555 -00 -000 r-ft-initial-association-use-association. doc – Marshall (10 Minutes) 11 -06 -0605 -01 -000 r-key-lifetime-reassociation-deadline. doc – Marshall (10 Minutes) Technical Issue #56: 11 -06 -0642 -00 -000 r-impact-ktp-non-definition. ppt – Stanley (30 minutes) Comment Resolution: Technical Issues Recess until Tuesday 10: 30 Submission 13 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Tuesday • • • 16 May 2006, 10: 30 -12: 30 Attendance reminder – http: //172. 16. 0. 10/11/attendance/ Comments #825, #826, #827, #828, #833: 8. 4. 1. 1. 2 Update – Marshall (10 Minutes) 11 -06 -0624 -00 -000 r-tgr-d 2 -0 -security-issues. ppt – Walker, Housley, Sood (25 minutes) 11 -06 -0623 -00 -000 r-method-to-protect-tgr-reservation-scheme: – Sood, Walker, Zhao (30 minutes) Comment Resolution: Technical Issues Recess until Tuesday 13: 30 Submission 14 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Tuesday • • • 16 May 2006, 13: 30 -15: 30 Attendance reminder Technical Issue #8: 11 -06 -0566 -01 -000 r-tgr-security-architecture. ppt – Sood, Cam-Winget, Walker, Calhoun, Chen (45 minutes) LB 82 Comment #33 – – • Appointment of Chair Pro-Tem 11 -03 -0770 -03 -frfh-make-before-break. doc – Chaplin (30 Minutes) Recess until Tuesday 16: 00 Submission 15 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Tuesday • • • 16 May 2006, 16: 00 -18: 00 Attendance reminder Technical Issue #55, #62: 11 -06 -0637 -00 -000 r-secure-key-distribution-and-authorizationprotocol. doc, 11 -06 -0695 -00 -000 r-secure-three-party-protocol-preso. ppt: Secure 3 party protocol – Harkins (60 minutes) Comment #1195, #1237: 11 -06 -0685 -00 -000 r-resource-query-procedures. doc, 11 -06 -044701 -000 r-qos-resource-query-overview. ppt – Emeott Comment #1407: 11 -06 -0723 -00 -000 r-ric-processing-ap. doc - Marshall Comment Resolution: Technical Issues Recess until Tuesday 19: 30 Submission 16 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Tuesday • • • 16 May 2006, 19: 30 -21: 30 Attendance reminder Technical Issue #22 (Comments #1253, #1254): Evaluate possible security hole with Authentication frames used for over-the-air reservations - Discuss Technical Issue #23 (Comment #1262): Evaluate possible security hole with Action frames used for over-the-DS reservations – Discuss Technical Issue #46 (Comment #1064): Remove multiple protocol options (base, reservation, air, DS, RSN, non-RSN) – Discuss Technical Issue #47 (Comment #1202, #1203): Remove multiple protocol options (base, reservation, air, DS, RSN, non-RSN) – Discuss Technical Issue #50 (Comments #1349, #1350, #1351): Take out RRB request/response message definitions – Discuss Technical Issue #52 (Comment #677): Provide empirical-based guidelines for setting Timeout intervals – Discuss Technical Issue #54: Complaints about complexity of criteria for including IEs in frames – Discuss Technical Issue #57 (Comments #1022, #1109, #1132, #1148): Unavoidable race condition with final message of sequence – Discuss Technical Issue #63 (Comment #1054): 802. 11 r and 802. 11 i must be made mutually exclusive for 802. 11 r capable STAs after the initial contact - Discuss Comment Resolution: Technical Issues Recess until Thursday 08: 00 Submission 17 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Thursday 18 May 2006, 08: 00 -10: 00 • • • Attendance reminder 11 -06 -0752 -00 -000 r-expanded-ftie. doc - Marshall Technical Issue #63 (Comment #1054): 802. 11 r and 802. 11 i must be made mutually exclusive for 802. 11 r capable STAs after the initial contact - Discuss Technical Issue #35: Take out ability to make reservations – David Hunter Comment Resolution Recess until Thursday 10: 30 Submission 18 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Thursday 18 May 2006, 10: 30 -12: 30 • • • Attendance reminder Comment #1497: MIB Variable. Technical Issue #41: 11 -06 -0730 -00 -000 r-overloading-more-bit. ppt: Remove “More Data” bit – Kumar Technical Issue #34, #61: 11 -06 -0650 -00 -000 r-qos-resource-controlflows. ppt: Remove mandatory/optional designation of RDIEs – Montemurro, Sood, Kumar Comment Resolution Recess until Thursday 13: 30 Submission 19 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Thursday 18 May 2006, 13: 30 -15: 30 • • Attendance reminder Status update of To-Do list Location of June 20 -22 ad-hoc Authorize August ad-hoc Update official IEEE TGr schedule Comment Resolution Recess until Thursday 15: 30 Submission 20 Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Thursday 18 May 2006, 16: 00 -18: 00 • • Attendance reminder LB 35 802. 11 i D 2. 0 March 25 th, 2002 LB 52 802. 11 i D 3. 0 December 2 nd, 2002 LB 57 802. 11 i D 4. 0 May 22 nd, 2003 LB 60 802. 11 i D 5. 0 August 4 th, 2003 LB 61 802. 11 i D 6. 0 September 24 th, 2003 LB 62 802. 11 i D 7. 0 October 20 th, 2003 Submission 21 44% 76% 78% 87% 92% 95% Clint Chaplin, TGr Chair

May 2006 doc. : IEEE 802. 11 -06/0660 r 7 Thursday (continued) 18 May 2006, 16: 00 -18: 00 • • • • Attendance reminder 11 -06 -0791 -01 -000 r-mandatory-optional-resources. doc 11 -06 -0792 -01 -000 r-reserve-option. doc Technical Issue #43 (Comment #867): Provide details of possible AP architectures and Network Topologies – Sood, Walker (June/July) Adjourn Technical Issue #8: 11 -06 -0566 -01 -000 r-tgr-security-architecture. ppt – Sood, Cam-Winget, Walker, Calhoun, Chen (June/July) Technical Issue #9: Add STA and Target AP addresses to Authentication frames to make them independent of transport - Stanley, Ptasinski (After architecture discussion (0566) concludes) Technical Issue #13: is a version number needed for the FT Authentication sequence? - Sood Technical Issue #28 and Comment #977, #992, #993, #994, #1005, #1006, #1008: Remove MDC, 8. 5 A. 6 Issues – Montemurro (After architecture discussion (0566) concludes) Technical Issue #25: Protocol to Revoke Keys – Cam-Winget (June/July) Technical Issue #45: Define a "sub-protocol id" to distinguish between base mechanism and reservation mechanism – Sood, Walker (June/July) Technical Issue #65: Security questions – Cam-Winget (June/July) Technical Issue #27: Remove PSK support – Ptasinski (June/July) Submission 22 Clint Chaplin, TGr Chair