Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems)Slide WG Editors Meeting (July 09) Date: Authors:

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Abstract This document contains a agenda/minutes/actions/status as recorded at the IEEE Editors Meeting Slide 2

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems)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 MB (87% approval) discussion –15 mins Conference Calls

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems)Slide 4 Roll Call – Editors Present –P802.11mb Amendment (REVmb) – Adrian Stephens –P802.11n Amendment (HT) – Adrian Stephens –P802.11s Amendment (MESH) –Kazuyuki Sakoda (until end 09) –P802.11w Amendment (SEC) – Nancy Cam-Winget –P802.11z Amendment (TDLS) – Menzo Wentink –Alex Ashley (For Hang Liu) –Lee Armstrong (for Wayne F) Also present: –Dave Bagby, Clint Chaplin, IEEE Staff present: –Michelle Turner – staff editor for 802, Editors Not Present –P802.11y Amendment (CBP) – Peter Ecclesine –P802.11p Amendment (WAVE) – Wayne Fisher –P802.11u Amendment (IW) -- Necati Canpolat –P802.11v Amendment (WNM) – Emily Qi –P802.11aa Amendment (VTS) – Hang Liu 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 is present at this plenary meeting

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

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Round table status report Slide 6

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Summary of actions – Slide 7

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Reflector Updates Each editor is expected to be on the reflector and current. If you didnt receive the meeting notice from the reflector, please send to To be updated: –None Slide 8

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems)Slide 9 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, –11k now available with Get802 –11r now available with Get802 –11y now available with Get802

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) MEC Status P802.11n D6.0 has gone through Mandatory Editorial Coordination (document r0) –SCC14 coordination done –Second review by Michelle performed in Sponsor Ballot 2. P802.11w D6.0 has gone through Mandatory Editorial Coordination in September 2008 –See w-tgw-d6-0-mec.doc Slide 10

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Alignment Process for /p/v The 08/0644r8 Numbering Spreadsheet has all changes from publication of 11k and 11r and 11y (and 11n D7.03, 11p D7.0, 11vD6.01 and 11w D7.0) Slide 11

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) 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 12

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems)Slide 13 ANA Announcements Current ANA announced to group is r5. (6/6/2009) –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.

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems)Slide 14 Amendment Ordering Amendment NumberTask GroupREVCOM Date Amendment 4TGwSept Amendment 5TGnNov 2009 – was Jan Amendment 6TGzJan Amendment 7TGpJune Amendment 8TGvJune Amendment 9TGuSept 2010 – was May Amendment 10TGsSept Revision802.11mbJune Amendment 1TGaaJune Amendment 2TGacDec Amendment 3TGadDec 2012 Data as of July 2009 See Amendment numbering is editorial! No need to make ballot comments on these dynamic numbers!

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems)Slide 15 Your Draft Status Updates Each editor, please send update for next page via the editors reflector no later than Thursday am2 to update table on next page!

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Draft Development Snapshot Most current doc shaded green. TGTG Published or Draft Baseline Documents Sourc e MEC Style GuideEditor Snapsho t Date krywnzpvusmbaa w Frame 7.2 Yes2007Nancy Cam- Winget 10-Mar n Frame 7.2 Yes2009Adrian Stephens 12-May z WordNo2007Menzo Wentink 17-July p Frame 7.2 No2007Wayne Fisher 11-Apr v Frame 7.2 No2007Emily QiNov u Frame 7.2 No2007Necati Canpolat Nov s Frame 8.0 No2007Kazuyuki Sakoda 13-May mbmb 2007 Inc 2008 Inc Frame 7.2 No2009Adrian Stephens 12-May a 0.01NoHang Lui Changes from last report shown in red. Slide 16

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) MB discussion Document m-revmb-wg-ballot- comments.xls – the comments themselves MIB comments Annex removal comments PHY removal comments Slide 17

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Conference Calls Are they of any value? Next Meeting: September 20-25, Waikoloa Cancel a week in advance if no agenda items. 29 June (t-2 weeks) Slide 18

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Reference Material Slide 19

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems)Slide 20 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 editors guideline 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

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) 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. Slide 21

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) 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 22

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Publication Work Plan Note: to be included in the editors 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 23

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) 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 24

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) 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 editors operations manual and during balloting, should comment that Annexes should be fully titled with good reason to vote No in balloting Slide 25

Submission doc.: IEEE /0753r0July 2009 Peter Ecclesine (Cisco Systems) Publications: lessons learned (contd) Acronym rules are inconsistent –Styleguide doesnt 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 26