Editor’s Meeting (November)

1. Editor’s Meeting (November) Authors: Date: 2009-01-19 Peter Ecclesine (Cisco Systems)

2. Abstract / Agenda • Roll Call / Contacts / Reflector • Publication Work Plan • Alignment Process to the new amendments (11w & 11n) • Amendment Ordering / ANA Status / Draft Snapshots • Lessons Learned • Numbering of Annexes • Baseline Text Dependencies • Conference Calls • Editorial Streamlining Projects Peter Ecclesine (Cisco Systems)

3. Roll Call • 802.11 Editor’s Present • P802.11n Amendment (HT) – Adrian Stephens • P802.11p Amendment (WAVE) – Wayne Fisher • P802.11s Amendment (MESH) –Kazuyuki Sakod (temporary) • P802.11u Amendment (IW) -- Necati Canpolat • P802.11v Amendment (WNM) – Emily Qi • P802.11y Amendment (CBP) – Peter Ecclesine • P802.11w Amendment (SEC) – Nancy Cam-Winget • P802.11z Amendment (TDLS) – Menzo Wentink, pro tem • P802.11aa Amendment (VTS) – Hang Liu • 802.11 Editor’s Not Present • P802.11T Recommended Practice (WPP) – Tom Alexander • Also present: • Clint Chaplin, Jon Rosdahl, Bill Marshall • 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? • Note: editors request that an IEEE staff member should be present at least during Plenary meetings Peter Ecclesine (Cisco Systems)

4. Volunteer Editor Contacts • TGn – Adrian Stephens – adrian.p.stephens@intel.com • TGp – Wayne Fisher – wfisher@arinc.com • TGs – Not yet determined (Kazuyuki Sakoda - KazuyukiA.Sakoda@jp.sony.com) • TGu – Necati Canpolat – necati.canpolat@intel.com • TGv – Emily Qi – emily.h.qi@intel.com • TGw – Nancy Cam-Winget – ncamwing@cisco.com • TGz – Menzo Wentink– mwentink@qualcomm.com(permanent editor position open?) • TGmb – Not yet determined • TGaa – Hang Liu – hang.liu@thomson.net • Editor Emeritus: • TGk – Joe Kwak– joekwak@sbcglobal.net • TGr – Bill Marshall – wtm@research.att.com • TGy – Peter Ecclesine – pecclesi@cisco.com Peter Ecclesine (Cisco Systems)

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 adrian.p.stephens@intel.com • To be updated: • None • All present receiving reflector traffic • No email address changes requested Peter Ecclesine (Cisco Systems)

6. IEEE Publication Status • IEEE 802.11-2007 published and for free download with Get802 • Published in June 2007 • Combines all existing amendments and includes maintenance work by TGma • Publications completed for 802.11k, 802.11r and 802.11y • 11n has gone through Mandatory Editorial Coordination (08-1045) • 11w has gone through Mandatory Editorial Coordination (08-????) Peter Ecclesine (Cisco Systems)

7. Alignment Process for 802.11k/r/y • The 08/0644r4 Numbering Spreadsheet has all changes from publication of 11k and 11r and 11y (and 11n D6.01 and 11w D7.0) Slide 7 Peter Ecclesine (Cisco Systems)

8. Amendment & other ordering notes • Editors define publication order independent of working group public timelines: • Since official timeline is volatile and moves around • Publication order helps provide stability in amendment numbering, figures, clauses and other numbering assignments • Editors are committed to maintain a rational publication order • Numbering spreadsheet 08/0644: • Succeeding amendments to do their respective updates • Must match the official timeline

9. Publications: lessons learned • When quoting baseline text inaccurately, the baseline text is changed whether or not the changes were marked. The IEEE staff will actually do the appropriate changes as if the task group had actually intended to change the baseline. • Drafts can minimally quote baseline text to minimize such changes • Should revisit the decision to include full context during insertion • Full Annex titles have to be shown in the amendment; more importantly included “normative” vs. “informative” • TGk inadvertently changed Annex A to be fully informative • TGr battled to fix Annex A but caused ripples • TGy 08-1215r1 has brief review of significant things changed for publication • In editor’s operations manual and during balloting, should comment that Annexes should be fully titled with good reason to vote “No” in balloting Slide 9 Peter Ecclesine (Cisco Systems)

10. Publications: lessons learned (cont’d) • Acronym rules are inconsistent • Styleguide doesn’t include definitions • Every document is treated as standalone, thus first acronym reference must be spelled out. Even though, other amendments or baseline may have defined and used the acronym earlier. • Goal should be to have as few changes between the final balloted amendment and final published amendment. • How do we deal with subjective decisions made by the IEEE copy editors as their styles vary? • Booleans should be capitalized: TRUE and FALSE • when “set to” • Booleans should be lower case: is true and is false (raise the issue with Style Guide update) Slide 10 Peter Ecclesine (Cisco Systems)

11. Publication Work PlanNote: to be included in the editor’s operations manual 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 (Powerpoint, Visio. TIF) to staff at time of REVCOM submission. • Editors provide a list of requests editorial corrections no later than REVCOM approval date. • 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. Peter Ecclesine (Cisco Systems)

12. Numbering of Annexes and Clauses • Proposal: TGMb will fix the ordering of annexes • Ample bad precedent set by 11k • Bibliography should be the final annex per IEEE Standards Style Guide • Clause numbering has similar issue during rollup • TGn clause 3a, 11r clause 11a, 11y clause 11.9a Peter Ecclesine (Cisco Systems)

13. Changes to MIB elements • You can incrementally add to a MIB element without deprecation at any level. That is, add new values and meaning pairs. • You can change the description of a MIB element without deprecation at any level. That is add new text clarifying or even changing the meaning of the element to keep up with the standard. • I would advise deprecation when changing the definition of some value of a MIB from one thing to another. However, I don't know of any rules requiring this.

14. ANA Announcements • Current ANA announced to group is 802.11-09-0031r2. • See https://mentor.ieee.org/802.11/file/08/11-09-0031-02-0000-ana-database-assigned-numbers.xls • All new requests received by end of meeting will be uploaded and announced via 802.11 WG reflector • 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. Peter Ecclesine (Cisco Systems)

15. Amendment reordering was discussed by editors Jan 20 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 Jan 20 from 802.11 web. • See http://grouper.ieee.org/groups/802/11/Reports/802.11_Timelines.htm Peter Ecclesine (Cisco Systems)

16. Email Your Draft Status Updates • Each editor, please send update for next page via the editor’s reflector no later than Thursday am2 to update table on next page! Peter Ecclesine (Cisco Systems)

17. Draft Development Snapshot Changes from last report shown in red. Most current doc shaded green. Peter Ecclesine (Cisco Systems)

18. 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) • Draft templates for FRAME (no Word) to help train new editors more rapidly • Under Construction(in priority order) • Revise the editor’s guideline • Mentoring program • Request in future Plenary sessions Mondays 7:30pm Frame surgery • MIB element numbering and compiling – publish a rolled-up MIB of k/r/y • 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 (self)