1. TGmb Agenda, July 2009 Date: 2009-07-10 Authors: July 2009 July 2009
doc.: IEEE /0732r4
July 2009
TGmb Agenda, July 2009
Date:
Authors:
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

2. July 2009
doc.: IEEE /0732r4
July 2009
Abstract
Agenda for the TGmb meeting in San Francisco, California from July 13-16, 2009.
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

3. Agenda Call meeting to order Letter ballot review
July 2009
doc.: IEEE /0732r4
July 2009
Agenda
Call meeting to order
Agenda review
Policies & procedures (including patent policy)
Attendance recording & meeting resources
Letter ballot review
Comment review & resolution
Plans for next meeting
Authorize teleconferences & ad hocs
Review timeline
AOB
Adjourn
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

4. Monday PM2 13 July 2009, 16:00 – 18:00 Call meeting to order July 2009
doc.: IEEE /0732r4
July 2009
Monday PM2 13 July 2009, 16:00 – 18:00
Call meeting to order
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

5. Participants, Patents, and Duty to Inform
July 2009
doc.: IEEE /0732r4
July 2009
Participants, Patents, and Duty to Inform
All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants:
“Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents
“Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims
“Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents)
The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group
Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2
Early identification of holders of potential Essential Patent Claims is strongly encouraged
No duty to perform a patent search
Slide #1
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

6. Patent Related Links July 2009
doc.: IEEE /0732r4
July 2009
Patent Related Links
All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development.
Patent Policy is stated in these sources:
IEEE-SA Standards Boards Bylaws
IEEE-SA Standards Board Operations Manual
Material about the patent policy is available at
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit
This slide set is available at
Slide #2
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

7. Call for Potentially Essential Patents
July 2009
doc.: IEEE /0732r4
Call for Potentially Essential Patents
July 2009
If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance:
Either speak up now or
Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or
Cause an LOA to be submitted
Slide #3
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

8. Other Guidelines for IEEE WG Meetings
July 2009
doc.: IEEE /0732r4
July 2009
Other Guidelines for IEEE WG Meetings
All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws.
Don’t discuss the interpretation, validity, or essentiality of patents/patent claims.
Don’t discuss specific license rates, terms, or conditions.
Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings.
Technical considerations remain primary focus
Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets.
Don’t discuss the status or substance of ongoing or threatened litigation.
Don’t be silent if inappropriate topics are discussed … do formally object.
See IEEE-SA Standards Board Operations Manual, clause and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.
Slide #4
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

9. Link to IEEE Disclosure of Affiliation
July 2009
doc.: IEEE /0732r4
July 2009
Resources – URLs
Link to IEEE Disclosure of Affiliation
Links to IEEE Antitrust Guidelines
Link to IEEE Code of Ethics
Link to IEEE Patent Policy
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

10. IEEE 802 is a world-wide professional technical organization
July 2009
doc.: IEEE /0732r4
July 2009
Meeting Etiquette
IEEE 802 is a world-wide professional technical organization
Meetings are to be conducted in an orderly and professional manner in accordance with the policies and procedures governed by the organization.
Individuals are to address the “Technical” content of the subject under consideration and refrain from making “personal” comments to or about the presenter.
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.
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

11. Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
doc.: IEEE /0732r4
July 2009
Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
Attendance recording procedures
See 11-09/0246r0
Must register before logging attendance
Must log attendance during each 2 hour session
Documentation
Use “TGm” for documents relating to the Revision PAR
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

12. Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
doc.: IEEE /0732r4
July 2009
Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
Approve Agenda
11-09/0732r2 (this document)
Approval of May 2009 (Montréal, Québec, Canada) meeting minutes: 11-09/0564r0
Approval of June 29 teleconference minutes: 11-09/0708r0
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

13. Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
doc.: IEEE /0732r4
July 2009
Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
Editorial update (Adrian Stephens)
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

14. Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
doc.: IEEE /0732r4
July 2009
Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
Letter Ballot Results
246 voters
155 affirmative (87%) , 23 negative (13%), with 29 abstentions
There were 730 comments received – stored in 11-09/0706
Further ballots will be recirculation ballots
All comments must be against changed text
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

15. Current TGmb Plan of Record
July 2009
doc.: IEEE /0732r4
July 2009
Current TGmb Plan of Record
May 2008 – Issue Call for Comment/Input
July 2008 – begin process input and old Interpretation requests
Acknowledge previous Task Group referrals
Sept 2008 – PAR revision process started
Nov 2008 – close receipt of new input
Nov 2008 – WG/EC approval of PAR Revision
Dec 2008 – NesCom/SASB approval PAR Revision
May 2009 – First WG Letter ballot
(includes All published Amendments as of May 2009)
Sep/Nov 2009 – Recirc start
January 2010 – Form Sponsor Pool (45 days)
March 2010 – Sponsor Ballot Start
(Include all published amendments as of March 2010)
July 2010 – Sponsor Recirc
March 2011 – WG/EC Final Approval
June 2011 – RevCom/SASB Approval
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

16. Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
doc.: IEEE /0732r4
July 2009
Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
Scheduled comment discussions appear in this agenda document
Topics are assigned a time slot, and specific comments are called out for discussion
If there is leftover time after discussion, the time will be used for ad hoc comment resolution mode
Schedule for comment discussions
Monday PM2: open meeting, security & MAC management comments
Tuesday PM1: MAC comments
Tuesday PM2 - General comments
Tuesday EVE - Architecture comments
Wednesday PM2 – editorial coordination meeting
Thursday AM2 – closing business
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

17. Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
doc.: IEEE /0732r4
July 2009
Monday PM2 (continued) 13 July 2009, 16:00 – 18:00
Security and MAC Management comments
CID 1073: remove measurement pilot frame
CID 1269: remove clause (channel selection in an IBSS)
CIDs 1357, 1342, 1152, 1444, 1507, 1508, 1305, and 1307 and document 11-09/0705r0: proposed changes to 11.3, authentication and association
Additional comment resolution
Reminder: ad hoc comment resolution leaders to meet following close of this meeting
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

18. Tuesday PM1 14 July 2009, 13:30 – 15:30 MAC comments
doc.: IEEE /0732r4
July 2009
Tuesday PM1 14 July 2009, 13:30 – 15:30
MAC comments
CID 1270: Remove Annex N
CID 1237: Rate limiting behavior
CID 1131: Proposed additional rules for notification of power save mode transitions
CIDs 1685, 1686, 1687, and admission control operations
Additional comment resolution
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

19. July 2009
doc.: IEEE /0732r4
July 2009
Tuesday PM2 14 July 2009, 16:00 – 18:00
General comments: does deprecation mean removal?
A definition: dep·re·cate (děp'rĭ-kāt')
tr.v. de·pre·cat·ed, de·pre·cat·ing, de·pre·cates
To express disapproval of; deplore.
To belittle; depreciate.
Computer Science To mark (a component of a software standard) as obsolete to warn against its use in the future so that it may be phased out.
[Latin dēprecārī, dēprecāt-, to ward off by prayer : dē-, de- + precārī, to pray; see prek- in Indo-European roots.]
(Source:
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

20. Tuesday PM2 (continued) 14 July 2009, 16:00 – 18:00
doc.: IEEE /0732r4
July 2009
Tuesday PM2 (continued) 14 July 2009, 16:00 – 18:00
Comment list
CIDs 1267 &c: Remove clause 16 (IR PHY)
CIDs 1275 &c: Deprecate clause 14 (FH PHY)
CIDs 1107 &c: Remove Annex C (SDL)
CIDs 1068 &c: Remove Annex F (HR/DSSS & FH interoperability)
CIDs 1189 &c: Deprecate DSSS-OFDM in ERP PHY
Fixing Regulatory Issues
Additional comment resolution
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

21. Tuesday EVE 14 July 2009, 19:30 – 21:30 Architecture comments
doc.: IEEE /0732r4
July 2009
Tuesday EVE 14 July 2009, 19:30 – 21:30
Architecture comments
CIDs 1104, 1105: Deprecate shared key authentication
CIDs 1075, 1076, 1266: Major changes to clause 10 (delete or make informative)
CIDs 1009, 1010, 1011, 1013: Change LCI to synchronize with recent IETF work
Additional comment resolution
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

22. July 2009
doc.: IEEE /0732r4
July 2009
Wednesday PM2 15 July 2009, 16:00 – 18:00
Editorial coordination meeting
Several large editorial issues in the revision may affect other TGs, and are discussed in 11-09/0714r0
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks

23. July 2009
doc.: IEEE /0732r4
July 2009
Thursday AM2 16 July 2009, 10:30 – 12:30
Editorial instruction motion on exact duplicate comments
Comment resolution approval votes
Preparation for September 2009 meeting
Teleconferences/ad hocs
Review timeline
Any changes needed to plan of record (slide 14)?
AOB
Adjourn
Matthew Gast, Trapeze Networks
Matthew Gast, Trapeze Networks