1. IEEE 802.11r: Fast BSS Transition TG Agenda
Month Year
doc.: IEEE yy/xxxxr0
June 2006
IEEE r: Fast BSS Transition TG Agenda
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < ieee802.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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Clint Chaplin, TGr Chair
John Doe, Some Company

2. Abstract IEEE 802.11 TGr June 2006 Ad-Hoc Agenda June 2006 Month Year
doc.: IEEE yy/xxxxr0
June 2006
Abstract
IEEE TGr June 2006 Ad-Hoc Agenda
Clint Chaplin, TGr Chair
John Doe, Some Company

3. Tuesday 20 June 2006, 09:00-17:00 June 2006 Call to Order
Month Year
doc.: IEEE yy/xxxxr0
June 2006
Tuesday 20 June 2006, 09:00-17:00
Call to Order
Review IEEE 802 and Policies and Procedures
Intellectual Property
Clint Chaplin, TGr Chair
John Doe, Some Company

4. Instructions for the WG Chair
Month Year
doc.: IEEE yy/xxxxr0
June 2006
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.
Approved by IEEE-SA Standards Board – March 2003 (Revised January 2006)
(Not necessary to be shown)
Clint Chaplin, TGr Chair
John Doe, Some Company

5. IEEE-SA Standards Board Bylaws on Patents in Standards
Month Year
doc.: IEEE yy/xxxxr0
IEEE-SA Standards Board Bylaws on Patents in Standards
June 2006
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)
Clint Chaplin, TGr Chair
John Doe, Some Company

6. Inappropriate Topics for IEEE WG Meetings
Month Year
doc.: IEEE yy/xxxxr0
June 2006
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 or visit
This slide set is available at
Slide #2
Approved by IEEE-SA Standards Board – March 2003 (Revised January 2006)
Clint Chaplin, TGr Chair
John Doe, Some Company

7. Month Year
doc.: IEEE yy/xxxxr0
June 2006
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
The Copyright Act of 1976 made a dramatic change to U.S. copyright law. Copyright was now deemed to exist from the moment of creation. Thus anything that is created is deemed to be owned by its creator. Additionally, a work no longer needs to be published in order to be protected. Therefore, even your scribbles on a piece of note paper constitute copyrighted material that you own and control.
The NII (National Information Infrastructure) and the GII (Global Information Infrastructure) are causing lawmakers and copyright owners to assess the ability of current copyright law to protect owners rights in a digital environment. While at this point the changes being talked about are not significant, they will make it clear that copyright protection is afforded to owners in the digital environment making it a requirement to honor the rights accorded to owners.
It is a requirement under the IEEE Bylaws that copyright ownership of all material published by the IEEE resides with the IEEE. The Standards Department accomplishes the transfer of copyright ownership from the volunteer authors to the Institute via the Project Authorization Request (PAR) form.
Clint Chaplin, TGr Chair
John Doe, Some Company

8. June 2006
IEEE Ethics
Clint Chaplin, TGr Chair

9. Tuesday (cont) 20 June 2006, 09:00-17:00
Month Year
doc.: IEEE yy/xxxxr0
June 2006
Tuesday (cont) 20 June 2006, 09:00-17:00
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
Pass around attendance sheet
Clint Chaplin, TGr Chair
John Doe, Some Company

10. Tuesday (cont) 20 June 2006, 09:00-17:00
Month Year
doc.: IEEE yy/xxxxr0
June 2006
Tuesday (cont) 20 June 2006, 09:00-17:00
Approve Agenda
Clint Chaplin, TGr Chair
John Doe, Some Company

11. Tuesday (cont) 20 June 2006, 09:00-17:00
Month Year
doc.: IEEE yy/xxxxr0
June 2006
Tuesday (cont) 20 June 2006, 09:00-17:00
Technical Issue #8: r-tgr-security-architecture.ppt – Sood, Cam-Winget, Walker, Calhoun, Chen (June/July); r-tgr-architectural-entities.ppt: Stanley
r-tgr-d2-0-security-issues.ppt
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.5A.6 Issues – Montemurro (After architecture discussion (0566) concludes)
Technical Issue #27: Remove PSK support – Ptasinski (June/July)
Technical Issue #22: Evaluate possible security hole with Authentication frames used for over-the-air reservations – Sood, Walker to develop security analysis of possible security threat
Clint Chaplin, TGr Chair
John Doe, Some Company

12. Tuesday (cont) 20 June 2006, 09:00-17:00
Month Year
doc.: IEEE yy/xxxxr0
June 2006
Tuesday (cont) 20 June 2006, 09:00-17:00
: Pre-authentication: Stanley
Technical Issue #43 (Comment 867): Provide details of possible AP architectures and Network Topologies – Walker, Sood
Technical Issue #44 (Comment 1041): Provide measurements of the FT mechanisms to show that they actually work – r-timing-criteria-and-conditions.doc: Dorothy
Technical Issue #45: Define a "sub-protocol id" to distinguish between base mechanism and reservation mechanism – Walker, Sood to develop attack.
Technical Issue #46: Take out multiple protocol options (base, reservation, air, DS, RSN, non-RSN): Commentor to develop specific criteria for satisfying the comment.
Technical Issue #60: Resource reservation provisional or reserved – TGr to stay as silent in this area as TGe was. Montemurro, Sood, Kumar
Technical Issue #56: r-impact-ktp-non-definition.ppt: modifications to Clause Stanley
r-qos-resource-control-flows.ppt: Montemurro, Kumar, Sood
r-reserve-option.doc: Montemurro, Marshall
r-rdie-status-codes.doc: Montemurro, Marshall
r-rdie-without-count.doc: Montemurro, Marshall
Status update of To-Do list
Recess until Wednesday 09:00
Clint Chaplin, TGr Chair
John Doe, Some Company

13. Wednesday 21 June 2006, 09:00-17:00 June 2006 Attendance reminder
Month Year
doc.: IEEE yy/xxxxr0
June 2006
Wednesday 21 June 2006, 09:00-17:00
Attendance reminder
Technical Issue #25: Protocol to Revoke Keys – Cam-Winget
Technical Issue #65: Security questions – Cam-Winget
Technical Issue #25: Key revocation – Cam-Winget
Comment Resolution
Status update of To-Do list
Recess until Thursday 09:00
Clint Chaplin, TGr Chair
John Doe, Some Company

14. Thursday 22 June 2006, 18:00-12:30 June 2006 Attendance reminder
Month Year
doc.: IEEE yy/xxxxr0
June 2006
Thursday 22 June 2006, 18:00-12:30
Attendance reminder
Comment Resolution
Status update of To-Do list
Adjourn
Clint Chaplin, TGr Chair
John Doe, Some Company

15. Thursday (continued) 18 May 2006, 16:00-18:00
Month Year
doc.: IEEE yy/xxxxr0
June 2006
Thursday (continued) 18 May 2006, 16:00-18:00
Attendance reminder
r-mandatory-optional-resources.doc
r-reserve-option.doc
Technical Issue #43 (Comment #867): Provide details of possible AP architectures and Network Topologies – Sood, Walker (June/July)
Adjourn
Clint Chaplin, TGr Chair
John Doe, Some Company