Submission doc.: IEEE /0321r1 Slide WG Editor’s Meeting (Mar ‘10) Date: Authors: Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Abstract This document contains agenda/minutes/actions/status as prepared/recorded at the IEEE Editors’ Meeting Slide 2Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Slide 3 Agenda for Roll Call / Contacts / Reflector Go round table and get brief status report Review action items from previous meeting Numbering Alignment process Amendment Ordering / ANA Status / Draft Snapshots MIB style and Frame practices Scope and Purpose statements Style Guide for Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Slide 4 Roll Call – Editor’s Present –P802.11mb Amendment (REVmb) – Adrian Stephens –P802.11p Amendment (WAVE) – Wayne Fisher P802.11s Amendment (MESH) –Kazuyuki Sakoda P802.11u Amendment (IW) -- Necati Canpolat P802.11v Amendment (WNM) – Emily Qi P802.11z Amendment (TDLS) – Menzo Wentink P802.11aa Amendment (VTS) – Hang Liu Also present: –Bill Marshall –Clint Chaplin Editor’s Not Present IEEE Staff not present and always welcome! –Kim Breitfelder – manager publishing, –Michael Kipness – our staff liaison, Note: editors request that an IEEE staff member should be present at least during Plenary meetings –Michelle Turner – staff editor for 802, Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Slide 5 Volunteer Editor Contacts TGp – Wayne Fisher – TGs – Kazuyuki Sakoda - TGu – Necati Canpolat – TGv – Emily Qi – TGz – Menzo Wentink– TGmb – Adrian Stephens – TGaa – Hang Liu – Editor Emeritus: –TGk – Joe Kwak– –TGn – Adrian Stephens – –TGr – Bill Marshall – –TGw – Nancy Cam-Winget – –TGy – Peter Ecclesine – Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Round table status report REVmb – in LB160 resolution, have rolled in 11w, 11n 11p – Initial Sponsor Ballot comment resolution 11s – LB159 comment resolution 11u – 11v – 11z – Recirculation Sponsor Ballot comment resolution 11aa – D0.04 in internal review Slide 6Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 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 to To be updated: –None Slide 7Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Slide 8 IEEE Publication Status IEEE published and for free download with Get802 –Published in June 2007 –Combines all existing amendments and includes maintenance work by TGma Publications completed for k, r and y, n and w –11k now available with Get802 –11r now available with Get802 –11y now available with Get802 Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 MEC Status P802.11p D7.0 has gone through Mandatory Editorial Coordination in June 2009 See p-P802-11p D7 Mandatory Editorial Coordination MEC.doc P802.11u D6.0 has gone through Mandatory Editorial Coordination in July 2009 See u-P802-11u D7 Mandatory Editorial Coordination MEC.doc P802.11v D6.0 has gone through Mandatory Editorial Coordination in July 2009 See u-P802-11v D6 Mandatory Editorial Coordination MEC.doc P802.11z D5.0 has gone through Mandatory Editorial Coordination in July 2009 See u-P802-11z D5 Mandatory Editorial Coordination MEC.doc Slide 9Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Numbering Alignment Process Update from all published standards. Posted as /644r11 By Adrian Stephens TGz will start a new update cycle. Slide 10 Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 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 Slide 11Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Slide 12 ANA Announcements Current ANA announced to group is r9. (2/8/2010) –See –All new requests received by end of meeting will be uploaded and announced via WG reflector Procedure for ANA is contained in 07/0827r0. –See 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 in drafts! –Editors to replace any ANA controlled resources numbers with upon incorporation of material into drafts. Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Slide 13 Amendment Ordering Amendment NumberTask GroupREVCOM Date Amendment 6TGzJuly Amendment 7TGpNov Amendment 8TGvJune Amendment 9TGuJun Amendment 10TGsJan Revision802.11mbJune Amendment 1TGaaOct Amendment 2TGacDec Amendment 3TGadDec Amendment 4TGaeJun Amendment 5TGafDec 2012 Data as of Mar 2010 See Amendment numbering is editorial! No need to make ballot comments on these dynamic numbers! Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Slide 14 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)

Submission doc.: IEEE /0321r1 Most current doc shaded green. TGTG Published or Draft Baseline Documents SourceMEC Style GuideEditor Snapshot Date krywnzpvusmbaa z WordYes2007Menzo Wentink 17-July p Frame 7.2Yes2009Wayne Fisher19-Jan v Frame 7.2No2007Emily Qi18-Nov u Frame 7.2Yes2007Necati Canpolat 18-Nov s Frame 8.0No2007Kazuyuki Sakoda 20-Jan mbmb 2007 Inc 2008 Inc 2009 Inc Frame 7.2No2009Adrian Stephens 18-Jan aa NoHang Liu18-Nov Changes from last report shown in red. Slide 15 Mar 2010 Draft Development Snapshot Slide 15Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 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 11aa, 11ac, 11ad, 11ae, 11af Mar 2010 Peter Ecclesine (Cisco Systems)Slide 16

Submission doc.: IEEE /0321r1 Scope and Purpose Statements We have invited IEEE-SA staff to present the frontmatter discussion of Scope and Purpose Mar 2010 Peter Ecclesine (Cisco Systems)Slide 17

Submission doc.: IEEE /0321r Style Guide See wg11-style-guide.doc Slide 18Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Conference Calls Are they of any value? Next Meeting: May Any need for conference calls? Slide 19Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Reference Material Slide 20Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Slide 21 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) 1.Revise the editor’s guideline – comments on 09/1034? 2.Mentoring program – Name a mentor for each new editor 3.Request in future Plenary sessions Mondays 7:30pm Frame surgery 4.MIB element numbering and compiling – publish a rolled-up MIB of k/r/y 5.Guideline on non-technical front matter 6.Guideline describing expected editorial development and maturity of draft through stages in for consistency across TGs 7.Guidelines for primitives – ARC to consider Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 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 REVmb numbering will stay using “Amendment style” numbering until the very last possible moment before going to Sponsor Ballot. Slide 22Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Draft naming convention Drafts and redlines are.pdf files Syntax: Draft _ [Redline [Compared to _ ]].pdf Examples: Draft P802.11n_D8.0.pdf Draft P802.11n_D8.0 Redline.pdf Draft P802.11n_D7.04 Redline Compared to P802.11n_D7.03.pdf Please use this convention for all drafts posted on the website. Slide 23Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 Lessons Learned from RevCom During Sponsor ballot… (see 09/1058r1) 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 RevCom 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 Slide 24Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 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 publications: 1.Editors provide FRAME source and any freestanding graphics (Powerpoint, Visio. TIF) to staff at time of REVCOM submission. 2.Editors provide a list of requests editorial corrections no later than REVCOM approval date. 3.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. 4.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. 5.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. 6.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. 7.Task Group Editor gives final approval. No changes are expected. This usually occurs within 24 hours. 8.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. 9.Working Group Chair sends to sponsor and IEEE staff letting them know the Working Group has signed off on the publication process. Slide 25Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 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. Slide 26Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 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 r1 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 27 Peter Ecclesine (Cisco Systems)

Submission doc.: IEEE /0321r1 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 28 Peter Ecclesine (Cisco Systems)