doc IEEE 802 11 100970 r 0 802

doc. : IEEE 802. 11 -10/0970 r 0 802. 11 WG Editor’s Meeting (Sept ‘ 10) Authors: Submission Date: 2010 -08 -11 Slide 1 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Abstract This document contains agenda/minutes/actions/status as prepared/recorded at the IEEE 802. 11 Editors’ Meeting Submission Slide 2 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Agenda for 2010 -09 -14 • • • Roll Call / Contacts / Reflector Go round table and get brief status report Review action items from previous meeting Numbering Alignment process Editors page discussion Amendment Ordering / ANA Status / Draft Snapshots MIB style and Frame practices (Frame. Maker 9. 0) Scope and Purpose statements Style Guide for 802. 11 Submission Slide 3 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Roll Call – 2010 -09 -14 • Editor’s Present • P 802. 11 mb Amendment (REVmb) – Adrian Stephens • P 802. 11 s Amendment (MESH) –Kazuyuki Sakoda • P 802. 11 u Amendment (IW) -- Necati Canpolat • P 802. 11 v Amendment (WNM) – Emily Qi • P 802. 11 z Amendment (TDLS) – Menzo Wentink • P 802. 11 ad Amendment (VHT 60) – Carlos Cordeiro • P 802. 11 af Amendment (TVWS) – Peter Ecclesine • 802. 11 Editor’s Not Present • P 802. 11 aa Amendment (VTS) – Hang Liu • Also present: – – Alex Ashley (P 802. 11 aa) Bill Marshall Bob Miller Clint Chaplin • IEEE Staff present and always welcome! • IEEE Staff not present and always welcome! – Kim Breitfelder – manager publishing, k. breitfelder@ieee. org? – Michael Kipness – our staff liaison, m. kipness@ieee. org? – Michelle Turner – staff editor for 802, m. turner@ieee. org • Note: editors request that an IEEE staff member should be present at least during Plenary meetings Submission Slide 4 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Volunteer Editor Contacts • • • TGs – Kazuyuki Sakoda - Kazuyuki. A. Sakoda@jp. sony. com TGu – Necati Canpolat – necati. canpolat@intel. com TGv – Emily Qi – emily. h. qi@intel. com TGz – Menzo Wentink– mwentink@qualcomm. com TGmb – Adrian Stephens – adrian. p. stephens@intel. com TGaa – Hang Liu – hang. liu@thomson. net TGad – Carlos Cordeiro – carlos. cordeiro@intel. com TGae – Henry Ptasinski – henryp@broadcom. com Tgaf – Peter Ecclesine – pecclesi@cisco. com Editor Emeritus: – 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 – TGw – Nancy Cam-Winget – ncamwing@cisco. com – TGy – Peter Ecclesine – pecclesi@cisco. com Submission Slide 5 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Round table status report • • • REVmb – in LB 167 comment resolution, Hope to recirc 11 s – in LB 166 comment resolution, Hope to recirc 11 u – in recirc Sponsor Ballot comment resolution, Hope to recirc 11 v – in recirc Sponsor Ballot comment resolution, Hope to recirc 11 z – in recirc Sponsor Ballot comment resolution, Hope to recirc 11 aa – in LB 164 comment resolution, 11 ad – in technical comment resolution, 11 ae – D 0. 01 technical review 11 af – D 0. 03 in internal review, have D 0. 04 based on MB D 5. 0 Submission Slide 6 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 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 Submission Slide 7 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 IEEE Publication Status • Publications completed for 802. 11 k, 802. 11 r and 802. 11 y, 802. 11 n and 802. 11 w – – – 11 k now available with Get 802 11 r now available with Get 802 11 y now available with Get 802 11 w now available with Get 802 11 n now available with Get 802 • Publication of 11 p announced July 16 th Submission Slide 8 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 MEC Status • P 802. 11 mb D 5. 0 has gone through Mandatory Editorial Coordination in August 2010 See 11 -10 -1070 -00 -000 m-revmb MEC comments. doc Submission Slide 9 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Numbering Alignment Process • Update from all published standards. Posted as 1108/644 r 17 By Bill Marshall • TGz started a new update cycle. 11 v, 11 u, 11 s next. • We use more columns for the two baselines. Submission Slide 10 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 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 after plenaries – We are seeing problems in MIB numbering (see next slide) Submission Slide 11 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 ANA Announcements • Current ANA announced to group is 802. 11 -09 -0031 r 12. (8/10/2010) – See https: //mentor. ieee. org/802. 11/file/08/11 -09 -0031 -09 -0000 -ana-database-assigned-numbers. xls – All new requests received by end of meeting will be uploaded announced via 802. 11 WG reflector • Procedure for ANA is contained in 07/0827 r 0. – 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 before 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. – ANA will control SMT, Groups Submission Slide 12 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 May 2010 Editors page • http: //www. ieee 802. org/11/editor_resources. html • Comments or changes? Submission Slide 13 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 • • Amendment numbering is editorial! No need to make ballot comments on these dynamic numbers! Editor Amendment Ordering Data as of September 2010 See http: //grouper. ieee. org/groups/802/11/Reports/802. 11_Timelines. htm Amendment Number Task Group REVCOM Date 802. 11 Amendment 7 TGz Sept 2010 802. 11 Amendment 8 TGv Sept 2010 802. 11 Amendment 9 TGu Dec 2010 802. 11 Revision 802. 11 mb June 2011 802. 11 -2011 Amendment 1 TGs June 2011 802. 11 -2011 Amendment 2 TGae Sept 2012 802. 11 -2011 Amendment 3 TGaf Dec 2011 802. 11 -2011 Amendment 4 TGaa Oct 2011 802. 11 -2011 Amendment 5 TGac Dec 2012 802. 11 -2011 Amendment 6 TGad Dec 2012 Submission Slide 14 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 May 2010 Frame. Maker V 9 transition • January 2011 IEEE-SA will use Frame. Maker 9. 0 exclusively for drafts submitted in Frame. Maker • Does not affect 11 u, 11 v and 11 z Submission Slide 15 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Email Your Draft Status Updates • Each editor, please send update for next page via the editor’s reflector no later than Thursday am 2 to update table on next page! Submission Slide 16 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Sept 2010 Draft Development Snapshot Changes from last report shown in red. TG Published or Draft Baseline Documents Publi shed p Z v z Y 11. 0 0 v Y 11. 7. 0 0 10. 0 u Y 11. 7. 0 0 11. 0 mb Y s Y u mb s ae af aa ac ad 10. 0 4. 01 11. 9. 0 0 11. 0 9. 0 3. 01 6. 0 Source MEC Style Guide Editor Snapshot Date Frame 7. 2 Yes 2009 Menzo Wentink 17 -July Frame 7. 2 Yes 2007 Emily Qi 18 -May Frame 7. 2 Yes 2007 Necati Canpolat 14 -July Frame 7. 2 No 2009 Adrian Stephens 13 -July Frame 8. 0 No 2009 Kazuyuki Sakoda 14 -July Henry Ptasinski 15 -July ae af Y 11. 8. 0 0 10. 0 9. 0 5. 0 0. 03 aa Y 11. 9. 0 0 11. 0 9. 0 5. 0 1. 0 Y 11. 0 0 10. 0 9. 0 5. 0 0. 1 1. 0 Most current doc shaded green. Frame 7. 1 No 2009 Peter Ecclesine 18 -May Word No 2009 Hang Liu 14 -July Word No 2009 Carlos Cordeiro 14 -July ac ad Submission 4. 0 0. 1 Slide 17 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Mar 2010 MIB style, Visio and Frame practices • I’m going to suggest going forward we use a single style with appropriately set tabs, and use leading Tabs to distinguish the syntax and description parts. (Adrian Stephens Feb 9, 2010) • Keep embedded figures using visio as long as possible – Near the end of sponsor ballot, turn these all into. wmf (windows meta file) format files (you can do this from visio using “save as”). Keep separate files for the. vsd source and the. wmf file that is linked to from frame. • Frame templates for 11 aa, 11 ac, 11 ad, 11 ae, 11 af Submission Slide 18 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 802. 11 Style Guide • See 11 -09 -1034 -00 -0000 -wg 11 -style-guide. doc Submission Slide 19 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Conference Calls • Are they of any value? • Next Meeting: Nov 12 -17, Dallas • Any need for conference calls? Submission Slide 20 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Mar 2010 Pre-Rev. Com IEEE-SA Review • Possibly near the end of Working Group Letter Ballot (3 rd recirc or 4 th recirc) , we will offer the draft to the publications editor for review. This allows ambiguities and errors to be addressed in Sponsor Ballot by comments, rather than discover the ambiguities and errors after Rev. Com. • It appears that during MEC is the least risky time for a publication editor’s review. • TGs Draft 7. 0 went to LB 166 out of July plenary, and by agreement with Ex. Com and IEEE SA staff, will go for professional editing for ~50 days, after which Draft 8. 0 will be available to start Sponsor Ballot. Submission Slide 21 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Mar 2010 Two Technical Editors • • Peter Ecclesine will run the face to face meetings Adrian Stephens will run the publication process Adrian Stephens is the ANA administrator All are on the Editor’s email list. Submission Slide 22 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Reference Material Submission Slide 23 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 • Editorial Streamlining Focus is on consistency across all TGs: – Completed • • Streamlined ANA processes – 07/0827 r 0 Consistent format for REDLINE contributions across TGs – 07/0788 r 0 Consistent process for editorial comment resolution across TGs (WG & Sponsor) – 07/2050 r 0 – Guideline for technical vs. editorial, sample editorial comment responses Format for comment reporting across TGs (WG & Sponsor) – 07/1990 r 0 (tool in 07/2116 r 0) Stable numbering method (See 07/2810 r 0) Consistent naming of redlines (See 07/2810 r 0) Draft templates for FRAME (no Word) to help train new editors more rapidly – Under Construction (in priority order) 1. 2. 3. 4. 5. 6. Revise the editor’s guideline – comments on 09/1034? Mentoring program – Name a mentor for each new editor Request in future Plenary sessions Mondays 7: 30 pm 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 7. Guidelines for primitives – ARC to consider Submission Slide 24 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Numbering of Annexes and Clauses • Proposal: TGMb will fix the ordering of annexes – Ample bad precedent set by 11 k – Bibliography should be the first or final annex per IEEE Standards Style Guide • Clause numbering has similar issue during rollup – TGn clause 3 a, 11 r clause 11 a, 11 y clause 11. 9 a • REVmb numbering will stay using “Amendment style” numbering until the very last possible moment before going to Sponsor Ballot. Submission Slide 25 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Draft naming convention • Drafts and redlines are. pdf files • Syntax: Draft <project>_<draft> [Redline [Compared to <project>_<draft>]]. pdf • Examples: • Draft P 802. 11 n_D 8. 0. pdf • Draft P 802. 11 n_D 8. 0 Redline. pdf • Draft P 802. 11 n_D 7. 04 Redline Compared to P 802. 11 n_D 7. 03. pdf Please use this convention for all drafts posted on the 802. 11 website. Submission Slide 26 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Lessons Learned from Rev. Com During Sponsor ballot… (see 09/1058 r 1) • Minimise cross references (“disagree – see CID 1234”) – Because not all CIDs are included in the “unsatisfied comments” listing, so this may end up a dangling reference. – Copy resolution + add (“same as resoution for CID 1234”) • Provide full URLs for doc references – Because some members of Rev. Com and the Sponsor Pool may not be familiar with how to get to Mentor • Minimise use of doc references – Cut and paste from reference doc, where-ever possible. This minimises work for sponsor ballot members getting reference documents. – Easier to audit process Submission Slide 27 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Publication Work Plan Note: 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: 1. 2. 3. 4. 5. 6. 7. 8. 9. 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. Submission Slide 28 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 Terry Cole on 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. Submission Slide 29 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 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 -1215 r 1 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 Submission Slide 30 Peter Ecclesine (Cisco Systems)

doc. : IEEE 802. 11 -10/0970 r 0 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) Submission Slide 31 Peter Ecclesine (Cisco Systems)