Editor’s Meeting (May)

1. Editor’s Meeting (May) Authors: Date: 2008-05-13 Terry L Cole (AMD)

2. Abstract / Agenda • Roll Call / Contacts / Reflector • Publication Work Plan • Jun/July Work plan • Numbering of Annexes • Baseline Text Dependencies • Conference Calls • Amendment Ordering / ANA Status / Draft Snapshots • Editorial Streamlining Projects Terry L Cole (AMD)

3. Roll Call • 802.11 Editor’s Present (75% attendance) • P802.11k Amendment (RRM) – Joe Kwak • P802.11n Amendment (HT) – Adrian Stephens • P802.11p Amendment (WAVE) – Wayne Fisher • P802.11r Amendment (FAST ROAM) – Bill Marshall • P802.11s Amendment (MESH) – Anthony Maida • P802.11u Amendment (WIEN) -- Necati Canpolat • P802.11v Amendment (MGMT) – Emily Qi • P802.11y Amendment (CBP) – Peter Ecclesine • P802.11aa Amendment (VTS) – Hang Liu • 802.11 Editor’s Not Present • P802.11w Amendment (SEC) – Nancy Cam-Winget • P802.11T Recommended Practice (WPP) – Tom Alexander • P802.11z Amendment (DLS) – Menzo Wentink • Also present: • Clint Chaplin, Jun Li • IEEE Staff present • IEEE Staff not present and always welcome! • Michelle Turner – staff editor for 802, m.turner@ieee.org • Kim Breitfelder – manager publishing, k.breitfelder@ieee.org • Michael Kipness – our staff liaison, m.kipness@ieee.org Terry L Cole (AMD)

4. Volunteer Editor Contacts • TGk – Joe Kwak– joekwak@sbcglobal.net • TGn – Adrian Stephens – adrian.p.stephens@intel.com • TGp – Wayne Fisher – wfisher@arinc.com • TGr – Bill Marshall – wtm@research.att.com • TGs – Anthony Maida– amaida@efji.comTGT – Tom Alexander – tom@veriwave.com • TGu – Necati Canpolat – necati.canpolat@intel.com • TGv – Emily Qi – emily.h.qi@intel.com • TGw – Nancy Cam-Winget – ncamwing@cisco.com • TGy – Peter Ecclesine – pecclesi@cisco.com • TGz – Menzo Wentink– menzow@hotmail.com • TGmb – Not yet determined • TGaa – Hang Liu – hang.liu@thomson.net Terry L Cole (AMD)

5. Reflector Updates • Each editor is expected to be on the reflector and current. • If you didn’t receive the meeting notice from the reflector, please send email to terry.cole@amd.com • To be updated: • Add Anthony & Hang & Clint & Menzo • Remove former officers and Avinash Joshi (802.11s pro temp) • All others present receiving reflector traffic • No email address changes requested Terry L Cole (AMD)

6. IEEE Publication Status • IEEE 802.11-2007 published and is now part of get802 on IEEE web (http://standards.ieee.org/getieee802/) • Published in June 2007 combining all previous amendments • Publications in progress • REVCOM has recommended publication of 802.11k and 802.11r. Pending approval by Standards Board • IEEE staff and WGTE preparing publication. Targets: • 802.11k 30 days following final approval by Standards Board • 802.11r 60 days following final approval by Standards Board • We plan to update our current numbering document doc:08/2213r14 in June once we get back the publication numbers for 802.11k & 802.11r. • Starting to plan with IEEE staff for publication of 802.11y (“When it rains, it pours.”) Terry L Cole (AMD)

7. Publication Work Plan Here is the workflow we have used for a number of years with IEEE staff on publication of 802.11 publications:  • Editors provide FRAME source and any freestanding graphics to staff at time of REVCOM submission. – DONE for both 802.11k and 802.11r. • Editors provide a list of requests editorial corrections no later than REVCOM approval date. – Not yet done by either editor. 802.11k is almost ready for submission. The 802.11r editor intends to wait until reviewing a publication draft for 802.11k to submit the draft since it is very dependent on the 802.11k text. • Staff prepares a publication draft and highlights changes they have made and questions they need addressed or confirmed. This draft is sent to Task Group Editor and the Working Group Technical Editor (me). This typically occurs about 2-3 weeks after approval for publication, since the preparation work is usually (but not always) begun ahead of approval. This is also typically the draft peer reviewed by IEEE staff. • The Task Group Editor responds to all questions on domain specific questions, with copy to Working Group editor (me). This typically takes about 3-5 days. • The Working Group Technical Editor reviews responses from the Task Group editor, completes any responses, and provides a list of WG officers and voting members valid for the document as of the opening day of the Sponsor ballot. This typically only takes one additional day from the prior step as most of the work is done in parallel by the two editors. • Final draft is submitted by the IEEE staff to Working Group Technical Editor and Task Group Editor for sign-off. Any changes from the responses or IEEE peer review are highlighted and explained. This typically takes only one or two days more after the responses are received from the editors. • Task Group Editor gives final approval. No changes are expected. This usually occurs within 24 hours. • Working Group Technical Editor signs off and provides draft to Working Group Chair. No changes are expected. This usually occurs within 24 hours and in parallel with the previous step. • Working Group Chair sends email to sponsor and IEEE staff letting them know the Working Group has signed off on the publication process. Terry L Cole (AMD)

8. WGTE Work Plan for June/July • Terry will be on paid time off (Sabbatical) the entire months of Jun/Jul • Terry would appreciate your support to make this time operate smoothly for 802.11 WG. He will be fully engaged in other activities in a full-time internship outside the technical field. He is happy to talk with you about this. • Work plan for IEEE WGTE • Editor’s meeting in July will be chaired by Nancy Cam-Winget • Terry’s planned activities for IEEE 802.11 during sabbatical: • Terry will oversee publication of 802.11k and 802.11r and 802.11y. • Terry will update ANA database in early August. • No other work for IEEE 802.11 is planned by Terry. • Terry does not plan to attend Denver meeting. • In the event of urgent needs that cannot wait until early August, two courses of action are available: • Work with Nancy Cam-Winget to have the issue addressed in the editors’ meeting in Denver • Send email to terry.cole@amd.com labeled URGENT 802.11 in subject heading. Terry L Cole (AMD)

9. Numbering of Annexes • Proposal: User IEEE Correct numbering to insert annexes in appropriate order • E.g., Annex N, Annex O1, Annex O2, Annex P • Allow insertion before final mandatory bibliography section. • Allows insertion of any new normative annexes prior to informative annexes • Do we want to do this way if the IEEE is willing to do it this way? • Straw poll showed the answer to be yes, but not unanimously • Terry should alert IEEE staff to this issue and find out what they plan to do. • Motion to table until we see the IEEE publication of 802.11k Terry L Cole (AMD)

10. Overlapping Text Issues • 11.3.1 text in last ballots were conflicting in the last three drafts. • Comment was put into ballot so TGs will be dealing with this. Terry L Cole (AMD)

11. Editors’ Conference Call Announcement • Announced via Administrative Calendar link on 802.11 web. See http://www.ieee802.org/11/. • Call #1 for Denver: Monday May 26 • noon ET / 9am PT • Will announce logistics on editors reflector • Will use audio conference and webex • Call #2 for Denver: cancelled – will use reflector instead Terry L Cole (AMD)

12. ANA Announcements • Current ANA announced to group is 802.11-08-0227r1. • See https://mentor.ieee.org/802.11/file/08/11-08-0227-01-0000-ana-database-assigned-numbers.xls • All new requests received by end of meeting will be uploaded and announced via 802.11 WG reflector after the editor’s conference call #1 • No requests have been received directly from editors this week and acted on in preparation for publishing next version. • Others as may arise before the editors conference call #1 will be included • Procedure for ANA is contained in 07/0827r0. • See http://mentor.ieee.org/802.11/public/07/11-07-0827-00-0000-assigned-number-authority-ana-mechanisms.ppt • Editorial Guidance • ANA assignments should be done at the time of moving from WG LB to Sponsor ballot. • If a resource number is not in the ANA Database, please use <ANA> in drafts! • Editors to replace any ANA controlled resources numbers with <ANA> upon incorporation of material into drafts. Terry L Cole (AMD)

13. Amendment reordering was discussed by editors Mar 30 based on current timeline estimates and resulted announced herein. Amendment numbering is editorial! No need to make ballot comments on these dynamic numbers! Amendment Ordering • Data as of March 30 from 802.11 web. Next update: ~May 30 • See http://grouper.ieee.org/groups/802/11/Reports/802.11_Timelines.htm Terry L Cole (AMD)

14. Email Your Draft Status Updates • Each editor, please send update for next page via the editor’s reflector no later than Thursday pm2 to update table on next page! • We discussed the utility of this information. • The most useful information is the MEC data. • Straw poll indicated that we should continue providing this information. Terry Cole (AMD)

15. Draft Development Snapshot Changes from last report shown in red. Most current draft shaded green. Terry L Cole (AMD)

16. Editorial Streamlining • Focus is on consistency across all TGs: • Completed • Streamlined ANA processes – 07/0827r0 • Consistent format for REDLINE contributions across TGs – 07/0788r0 • Consistent process for editorial comment resolution across TGs (WG & Sponsor) – 07/2050r0 • Guideline for technical vs. editorial, sample editorial comment responses • Format for comment reporting across TGs (WG & Sponsor) – 07/1990r0 (tool in 07/2116r0) • Stable numbering method (See 07/2810r0) • Consistent naming of redlines (See 07/2810r0) • Under Construction(in priority order) • Revise the editor’s guideline – (first draft doc 08/452r0; Bill plans to update again.) • Draft templates for FRAME (no Word) to help train new editors more rapidly • MIB element numbering and compiling • Guideline on non-technical front matter • Guideline describing expected editorial development and maturity of draft through stages in 802.11 for consistency across TGs • Guidelines for primitives Terry L Cole (AMD)