Submission doc.: IEEE /1345r0November 2008 Peter Ecclesine (Cisco Systems)Slide 1 Editor’s Meeting (November) Date: Authors:

Submission doc.: IEEE /1345r0 Peter Ecclesine (Cisco Systems)Slide 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 November 2008

Submission doc.: IEEE /1345r0 Peter Ecclesine (Cisco Systems)Slide 3 Roll Call Editor’s Present –P802.11n Amendment (HT) – Adrian Stephens –P802.11p Amendment (WAVE) – Wayne Fisher –P802.11s Amendment (MESH) – –P802.11y Amendment (CBP) – Peter Ecclesine –P802.11w Amendment (SEC) – Nancy Cam-Winget –P802.11z Amendment (TDLS) – Menzo Wentink, pro tem –P802.11u Amendment (IW) -- Necati Canpolat –P802.11v Amendment (WNM) – Emily Qi –P802.11aa Amendment (VTS) – Hang Liu 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, –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 November 2008

Submission doc.: IEEE /1345r0November 2008 Peter Ecclesine (Cisco Systems)Slide 4 Volunteer Editor Contacts TGn – Adrian Stephens – TGp – Wayne Fisher – TGr – Bill Marshall – TGs – TGT – Tom Alexander – TGu – Necati Canpolat – TGv – Emily Qi – TGw – Nancy Cam-Winget – TGy – Peter Ecclesine – TGz – Menzo Wentink– (permanent editor position TGmb – Not yet determined TGaa – Hang Liu – Editor Emeritus: –TGk – Joe Kwak–

Submission doc.: IEEE /1345r0 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 –All present receiving reflector traffic –No address changes requested November 2008 Peter Ecclesine (Cisco Systems)Slide 5

Submission doc.: IEEE /1345r0November 2008 Peter Ecclesine (Cisco Systems)Slide 6 IEEE Publication Status IEEE published and for sale on IEEE web –Published in June 2007 –Combines all existing amendments and includes maintenance work by TGma Publications completed for k, r and y 11n has gone through Mandatory Editorial Coordination ( ) 11w has gone through Mandatory Editorial Coordination (08-????)

Submission doc.: IEEE /1345r0 Alignment Process for k/r/y The 08/0644r3 Numbering Spreadsheet has all changes from publication of 11k and 11r and 11y (and 11n D6.01) November 2008 Peter Ecclesine (Cisco Systems)Slide 7

Submission doc.: IEEE /1345r0 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 November 2008

Submission doc.: IEEE /1345r0 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 Peter Ecclesine (Cisco Systems)Slide 9 November 2008

Submission doc.: IEEE /1345r0 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) Peter Ecclesine (Cisco Systems)Slide 10 November 2008

Submission doc.: IEEE /1345r0 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 to staff at time of REVCOM submission. – DONE for both k and r. 2.Editors provide a list of requests editorial corrections no later than REVCOM approval date. – Not yet done by either editor k is almost ready for submission. The r editor intends to wait until reviewing a publication draft for k to submit the draft since it is very dependent on the k text. 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. November 2008 Peter Ecclesine (Cisco Systems)Slide 11

Submission doc.: IEEE /1345r0 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 November 2008 Peter Ecclesine (Cisco Systems)Slide 12

Submission doc.: IEEE /1345r0 Peter Ecclesine (Cisco Systems)Slide 13 ANA Announcements Current ANA announced to group is r1. –See –All new requests received by end of meeting will be uploaded and announced via 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 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 in drafts! –Editors to replace any ANA controlled resources numbers with upon incorporation of material into drafts. November 2008

Submission doc.: IEEE /1345r0 Peter Ecclesine (Cisco Systems)Slide 14 Amendment Ordering Amendment NumberTask GroupREVCOM Date Amendment 1TGkMay 2008 (actual) Amendment 2TGrMay 2008 (actual) Amendment 3TGySept 2008 (actual) Amendment 4TGwSept Amendment 5TGnJune 2009 (was TBA) Amendment 6TGzSept Amendment 7TGpDec Amendment 8 (was 9)TGvDec Amendment 9 (was 10)TGuMar Amendment 10 (was 8)TGsMay 2010 (was Dec 2009) Revision802.11mbMar Amendment 1TGaaMay 2011 (new) TGTDec 2009 (plan to withdraw) Data as of Nov 11 from web. See Amendment numbering is editorial! No need to make ballot comments on these dynamic numbers! Amendment reordering was discussed by editors Nov 11 based on current timeline estimates and resulted announced herein. November 2008

Submission doc.: IEEE /1345r0 Peter Ecclesine (Cisco Systems)Slide 15 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! November 2008

Submission doc.: IEEE /1345r0 Peter Ecclesine (Cisco Systems) Draft Development Snapshot Most current doc shaded green. TGTG Published or Draft Baseline Documents SourceMEC Style Guide Editor Snapshot Date krywnzpvusmbaa k Frame 7.24/11/072006Joe Kwak19-Mar r Frame 7.14/11/072005Bill Marshall18-Mar y Frame 7.27/28/072007Peter Ecclesine 15-July w Frame 7.2No2007Nancy Cam- Winget 15-July n Frame 7.2No2007Adrian Stephens 15-July z WordNo2007Menzo Wentink 17-July p Frame 7.2No2007Wayne Fisher 15-July v Frame 7.2No2007Emily Qi15-July u Frame 7.2No2007Necati Canpolat 15-July s Frame 7.2No2007Tony Maida15-July mbmb No draft yetVacant15-July aaNo draft yetVacantxx T(1.01)Frame 6No2007Tom Alexander 20 -Mar Changes from last report shown in red. November 2008

Submission doc.: IEEE /1345r0 Terry L Cole (self)Slide 17 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) 1.Revise the editor’s guideline 2.Draft templates for FRAME (no Word) to help train new editors more rapidly 3.MIB element numbering and compiling 4.Guideline on non-technical front matter 5.Guideline describing expected editorial development and maturity of draft through stages in for consistency across TGs 6.Guidelines for primitives November 2008