1. 802.11 WG Editor’s Meeting (Mar 09)
January 2009July 2007
July 2007
March 2009
WG Editor’s Meeting (Mar 09)
Date:
Authors:
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

2. March 2009
Summary of actions –
Michelle to check Get802 status for .11r
Nancy to publish MEC comments for .11w
Adrian to ping Menzo on whether he has updated 11-08/0644r5 (numbering spreadsheet)
Goal: get TGz and TGp to have updated the numbering spreadsheet by May 09 meeting.
All: please send draft status update via the editor’s reflector asap, but no later than Thursday am2 to update table on next page!
Necati to Michelle list of issues with templates
Adrian Stephens (Intel Corporation)

3. Abstract / Agenda Roll Call / Contacts / Reflector
January 2009July 2007
July 2007
March 2009
Abstract / Agenda
Roll Call / Contacts / Reflector
Publication Work Plan
Amendment Ordering / ANA Status / Draft Snapshots
Draft naming rules
Conference Calls
Editorial Streamlining Projects
Archival material
Lessons Learned
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

4. Roll Call March 2009 July 2007 January 2009July 2007
Editor’s Present
P802.11mb Amendment (REVmb) – Adrian Stephens
P802.11n Amendment (HT) – Adrian Stephens
P802.11p Amendment (WAVE) – Wayne Fisher
P802.11s Amendment (MESH) –Kazuyuki Sakoda (until end ‘09)
P802.11u Amendment (IW) -- Necati Canpolat
P802.11w Amendment (SEC) – Nancy Cam-Winget
P802.11v Amendment (WNM) – Emily Qi
P802.11aa Amendment (VTS) – Hang Liu
Also present:
IEEE Staff present:
Michelle Turner – staff editor for 802,
Editor’s Not Present
P802.11y Amendment (CBP) – Peter Ecclesine
P802.11z Amendment (TDLS) – Menzo Wentink
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
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

5. Volunteer Editor Contacts
January 2009July 2007
July 2007
March 2009
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 – (TBC)
TGaa – Hang Liu –
Editor Emeritus:
TGk – Joe Kwak–
TGr – Bill Marshall –
TGy – Peter Ecclesine –
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

6. January 2009July 2007
July 2007
March 2009
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
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

7. IEEE Publication Status
January 2009July 2007
July 2007
March 2009
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
Action: Michelle to check Get802 status for .11r
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

8. March 2009
MEC Status
P802.11n D6.0 has gone through Mandatory Editorial Coordination (document r0)
SCC14 coordination done
Second review by Michelle pending
11w has gone through Mandatory Editorial Coordination (09-????) in September
Action: Nancy to publish MEC comments for .11w
Adrian Stephens (Intel Corporation)

9. Alignment Process for 802.11k/r/y
March 2009
Alignment Process for k/r/y
The 08/0644r5 Numbering Spreadsheet has all changes from publication of 11k and 11r and 11y (and 11n D7.03 and 11w D7.0)
?? TGz has done it?
Action: Adrian to ping Menzo on whether he has updated 11-08/0644r5 (numbering spreadsheet)
TGp – Wayne
Goal: get TGz and TGp to have updated the numbering spreadsheet by May 09 meeting.
Then discuss at May Meeting, expectation TGv correct numbering.
Slide 9
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)

10. Amendment & other ordering notes
March 2009
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
Adrian Stephens (Intel Corporation)

11. Numbering of Annexes and Clauses
January 2009July 2007
July 2007
March 2009
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.
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

12. ANA Announcements Current ANA announced to group is 802.11-09-0031r2.
January 2009July 2007
July 2007
March 2009
ANA Announcements
Current ANA announced to group is r2.
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 <ANA> in drafts!
Editors to replace any ANA controlled resources numbers with <ANA> upon incorporation of material into drafts.
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

13. Amendment Ordering March 2009 Amendment Number Task Group REVCOM Date
July 2007
January 2009July 2007
March 2009
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 web.
See
Amendment Number
Task Group
REVCOM Date
Amendment 1
TGk
May 2008 (actual)
Amendment 2
TGr
Amendment 3
TGy
Sept 2008 (actual)
Amendment 4
TGw
Dec 2009
Amendment 5
TGn
Jan 2010
Amendment 6
TGz
Sept 2009
Amendment 7
TGp
June 2010
Amendment 8
TGv
Amendment 9
TGu
May 2010
Amendment 10
TGs
Sept 2010
Revision
802.11mb
Mar 2011
TGaa
May 2011
TGac
<no schedule>
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

14. Email Your Draft Status Updates
January 2009July 2007
September 2007
March 2009
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)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

15. Draft Development Snapshot Published or Draft Baseline Documents
July 2007
January 2009July 2007
March 2009
Draft Development Snapshot
Changes from last report shown in red.
Most current doc shaded green. TG
Published or Draft Baseline Documents
Source
MEC
Style Guide
Editor
Snapshot Date
802.11 k r y w n z p v u s mb aa
2007
2008
7.0
Frame 7.2
Yes
Nancy Cam-Winget
15-July
7.03
Adrian Stephens
Nov
6.0
3.0
Word No
Menzo Wentink
17-July
2.0
5.0
Wayne Fisher
4.0
4.01
Emily Qi
11.0
6.04 -
4.02
Necati Canpolat
1.0
2.06
Vacent
No draft yet
Vacant xx T
(1.01)
Frame 6
Tom Alexander
20 -Mar
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

16. Editorial Streamlining
January 2009July 2007
July 2007
March 2009
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 – Name a mentor for each new editor
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 for consistency across TGs
Guidelines for primitives – ARC to consider
Terry L Cole (self)
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

17. Draft naming convention
March 2009
Draft naming convention
Drafts and redlines are .pdf files
Syntax:
Draft <project>_<draft> [Redline [Compared to <project>_<draft>]].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.
Adrian Stephens (Intel Corporation)

18. AOB Nancy: participant lists. TGn, r, y all different.
March 2009
AOB
Nancy: participant lists. TGn, r, y all different.
How do we define contributor list?
Is second list, all letter balloters, or members, or sponsor balloters?
Michelle: every group does it differently.
Nancy: defer to chair
Necati: any update on templates?
Michelle: need to do another update with new frontmatter (new board members)
Issues with numbering of pages.
Action: Necati to Michelle list of issues.
Adrian Stephens (Intel Corporation)

19. March 2009
Archive Material
Adrian Stephens (Intel Corporation)

20. January 2009July 2007
July 2007
March 2009
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: 
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 to sponsor and IEEE staff letting them know the Working Group has signed off on the publication process.
Adrian Stephens (Intel Corporation)
Terry Cole (AMD)

21. Terry Cole on Changes to MIB elements
March 2009
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.
Adrian Stephens (Intel Corporation)

22. Publications: lessons learned
March 2009
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 22
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)

23. Publications: lessons learned (cont’d)
March 2009
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 23
Peter Ecclesine (Cisco Systems)
Adrian Stephens (Intel Corporation)