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

Submission

doc.: IEEE 802.11-09/0753r0July 2009

Peter Ecclesine (Cisco Systems)Slide 1

802.11 WG Editor’s Meeting (July 09)

Date: 2009-07-12

Name Affiliation Address Phone email Peter Ecclesine Cisco Systems [email protected]

Authors:

Submission

doc.: IEEE 802.11-09/0753r0July 2009

Peter Ecclesine (Cisco Systems)

Abstract

This document contains a agenda/minutes/actions/status as recorded at the IEEE 802.11 Editors’ Meeting

Slide 2

Submission

doc.: IEEE 802.11-09/0753r0July 2009


Agenda for 2009-07-14

• 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 802.11-09/0753r0July 2009


Roll Call – 2009-07-14• Editor’s 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, [email protected]

• 802.11 Editor’s 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, [email protected]?– Michael Kipness – our staff liaison, [email protected]?

• 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 802.11-09/0753r0July 2009


Volunteer Editor Contacts• TGn – Adrian Stephens – [email protected]

• TGp – Wayne Fisher – [email protected]

• TGs – Temporary: Kazuyuki Sakoda - [email protected]

• TGu – Necati Canpolat – [email protected]

• TGv – Emily Qi – [email protected]

• TGw – Nancy Cam-Winget – [email protected]

• TGz – Menzo Wentink– [email protected]

• TGmb – Adrian Stephens – [email protected] (TBC)

• TGaa – Hang Liu – [email protected]

• Editor Emeritus:

– TGk – Joe Kwak– [email protected]

– TGr – Bill Marshall – [email protected]

– TGy – Peter Ecclesine – [email protected]

Submission

doc.: IEEE 802.11-09/0753r0July 2009


Round table status report

Slide 6

Submission

doc.: IEEE 802.11-09/0753r0July 2009


Summary of actions – 2009-07-14

Slide 7

Submission

doc.: IEEE 802.11-09/0753r0July 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 email to [email protected]

• To be updated:– None

Slide 8

Submission

doc.: IEEE 802.11-09/0753r0July 2009


IEEE Publication Status

• IEEE 802.11-2007 published and for free download with Get802– Published in June 2007

– Combines all existing amendments and includes maintenance work by TGma

• Publications completed for 802.11k, 802.11r and 802.11y, – 11k now available with Get802

– 11r now available with Get802

– 11y now available with Get802

Submission

doc.: IEEE 802.11-09/0753r0July 2009


MEC Status

• P802.11n D6.0 has gone through Mandatory Editorial Coordination (document 11-08-1045r0)– 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 11-09-0600-00-000w-tgw-d6-0-mec.doc

Slide 10

Submission

doc.: IEEE 802.11-09/0753r0July 2009


Alignment Process for 802.11/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 11Slide 11

Submission

doc.: IEEE 802.11-09/0753r0July 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 after plenaries

Slide 12

Submission

doc.: IEEE 802.11-09/0753r0July 2009


ANA Announcements• Current ANA announced to group is 802.11-09-0031r5. (6/6/2009)

– See https://mentor.ieee.org/802.11/file/08/11-09-0031-05-0000-ana-database-assigned-numbers.xls

– All new requests received by end of meeting will be uploaded and announced via 802.11 WG reflector

• Procedure for ANA is contained in 07/0827r0.– 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.

Submission

doc.: IEEE 802.11-09/0753r0July 2009


Amendment Ordering

Amendment Number Task Group REVCOM Date

802.11 Amendment 4 TGw Sept 2009

802.11 Amendment 5 TGn Nov 2009 – was Jan 2010

802.11 Amendment 6 TGz Jan 2010

802.11 Amendment 7 TGp June 2010

802.11 Amendment 8 TGv June 2010

802.11 Amendment 9 TGu Sept 2010 – was May 2010

802.11 Amendment 10 TGs Sept 2010

802.11 Revision 802.11mb June 2011

802.11-2011 Amendment 1 TGaa June 2011

802.11-2011 Amendment 2 TGac Dec 2012

802.11-2011 Amendment 3 TGad Dec 2012

• Data as of July 2009• See http://grouper.ieee.org/groups/802/11/Reports/802.11_Timelines.htm

Amendment numbering is editorial! No need to make ballot comments on these dynamic numbers!

Submission

doc.: IEEE 802.11-09/0753r0July 2009


Email 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!

Submission

doc.: IEEE 802.11-09/0753r0July 2009


Draft Development Snapshot Most current doc shaded green.

TG

Published or Draft Baseline DocumentsSourc

eMEC

Style Guide Editor

Snapshot Date

802.11 k r y w n z p v u s mb aa

w 2007 2008 2008 2008 9.0 Frame 7.2

Yes 2007 Nancy Cam-Winget

10-Mar

n 2007 2008 2008 2008 7.0 9.0 Frame 7.2

Yes 2009 Adrian Stephens

12-May

z 2007 2008 2008 2008 6.0 7.0 3.0 Word No 2007 Menzo Wentink

17-July

p 2007 2008 2008 2008 8.0 8.0 4.0 6.01 Frame 7.2

No 2007 Wayne Fisher

11-Apr

v 2007 2008 2008 2008 6.0 7.0 2.0 4.0 4.01 2.0 2.0 Frame 7.2

No 2007 Emily Qi Nov

u 2007 2008 2008 11.0 6.0 6.04 - - 4.0 4.02 Frame 7.2

No 2007 Necati Canpolat

Nov

s 2007 2008 2008 2008 7.0 7.02 3.0 5.0 4.01 4.02 3.0 Frame 8.0

No 2007 Kazuyuki Sakoda

13-May

mb

2007 Inc

2008 Inc

2008 Inc

2008 Inc

- - - - - - - 0.05 - Frame 7.2

No 2009 Adrian Stephens

12-May

aa

0.01 No Hang Lui

Changes from last report shown in red.

Slide 16

Submission

doc.: IEEE 802.11-09/0753r0July 2009


MB discussion

• Document 11-09-0706-00-000m-revmb-wg-ballot-comments.xls – the comments themselves

• MIB comments

• Annex removal comments

• PHY removal comments

Slide 17

Submission

doc.: IEEE 802.11-09/0753r0July 2009


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 802.11-09/0753r0July 2009


Reference Material

Slide 19

Submission

doc.: IEEE 802.11-09/0753r0July 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)1. Revise the editor’s guideline2. Mentoring program – Name a mentor for each new editor3. Request in future Plenary sessions Mondays 7:30pm Frame surgery 4. MIB element numbering and compiling – publish a rolled-up MIB of k/r/y5. Guideline on non-technical front matter6. Guideline describing expected editorial development and maturity of draft through

stages in 802.11 for consistency across TGs7. Guidelines for primitives – ARC to consider

Submission

doc.: IEEE 802.11-09/0753r0July 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.

Slide 21

Submission

doc.: IEEE 802.11-09/0753r0July 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 802.11 website.

Slide 22

Submission

doc.: IEEE 802.11-09/0753r0July 2009


Publication Work PlanNote: 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. 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 email to sponsor and IEEE staff letting them know the Working Group has signed off on the publication process.

Slide 23

Submission

doc.: IEEE 802.11-09/0753r0July 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.

Slide 24

Submission

doc.: IEEE 802.11-09/0753r0July 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 08-1215r1 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 25Slide 25

Submission

doc.: IEEE 802.11-09/0753r0July 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 26Slide 26