802.11 Jan 2010 Closing Plenary Reports

1. 802.11 Jan 2010 Closing Plenary Reports Authors: Date: 2010-01-21 Adrian Stephens, Intel Corporation

2. Abstract • This document is a digest of the closing reports of all 802.11 sub-groups for presentation at the January 2010 closing plenary meeting. Adrian Stephens, Intel Corporation

3. 802.11 WG Editor’s Meeting (Jan ‘10) Date: 2010-01-16 Authors: Adrian Stephens, Intel Corporation from slide 1 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

4. Abstract This document contains agenda/minutes/actions/status as prepared/recorded at the IEEE 802.11 Editors’ Meeting Adrian Stephens, Intel Corporation from slide 2 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

5. Agenda for 2010-01-18 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 Lessons learned from TGw/TGn RevCom Lessons learned from editing of TGn Style Guide for 802.11 ISO JTC1 review of 802.11 Sponsor Ballot Drafts Adrian Stephens, Intel Corporation from slide 3 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

6. Roll Call – 2010-01-18 Editor’s Present P802.11mb Amendment (REVmb) – Adrian Stephens P802.11p Amendment (WAVE) – Wayne Fisher P802.11s Amendment (MESH) –Kazuyuki Sakoda (temporary) P802.11v Amendment (WNM) – Emily Qi Also present: Bill Marshall Clint Chaplin Vijay Auluck 802.11 Editor’s Not Present P802.11u Amendment (IW) -- Necati Canpolat P802.11z Amendment (TDLS) – Menzo Wentink P802.11aa Amendment (VTS) – Hang Liu IEEE Staff not present and always welcome! Kim Breitfelder – manager publishing, k.breitfelder@ieee.org? Michael Kipness – our staff liaison, m.kipness@ieee.org? Note: editors request that an IEEE staff member should be present at least during Plenary meetings Michelle Turner – staff editor for 802, m.turner@ieee.org Adrian Stephens, Intel Corporation from slide 4 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

7. Volunteer Editor Contacts TGp – Wayne Fisher – wfisher@arinc.com TGs – Temporary: Kazuyuki Sakoda - KazuyukiA.Sakoda@jp.sony.com TGu – Necati Canpolat – necati.canpolat@intel.com TGv – Emily Qi – emily.h.qi@intel.com TGz – Menzo Wentink– mwentink@qualcomm.com TGmb – Adrian Stephens – adrian.p.stephens@intel.com (TBC) TGaa – Hang Liu – hang.liu@thomson.net Editor Emeritus: TGk – Joe Kwak– joekwak@sbcglobal.net TGn – Adrian Stephens – adrian.p.stephens@intel.com TGr – Bill Marshall – wtm@research.att.com TGw – Nancy Cam-Winget – ncamwing@cisco.com TGy – Peter Ecclesine – pecclesi@cisco.com Adrian Stephens, Intel Corporation from slide 5 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

8. Round table status report REVmb – in LB160 resolution, have rolled in 11w, 11n this year 11p – Initial Sponsor Ballot comment resolution 11s – LB159 comment resolution 11z – Initial Sponsor Ballot comment resolution, probably recirc after Los Angeles 11aa – D0.03 in internal review Adrian Stephens, Intel Corporation from slide 6 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

9. 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 adrian.p.stephens@intel.com • To be updated: • None Adrian Stephens, Intel Corporation from slide 7 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

10. 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, 802.11n and 802.11w 11k now available with Get802 11r now available with Get802 11y now available with Get802 Adrian Stephens, Intel Corporation from slide 8 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

11. MEC Status P802.11pD7.0 has gone through Mandatory Editorial Coordination in June 2009 See 11-09-0659-00-000p-P802-11pD7 Mandatory Editorial Coordination MEC.doc P802.11uD6.0 has gone through Mandatory Editorial Coordination in July 2009 See 11-09-0788-00-000u-P802-11uD7 Mandatory Editorial Coordination MEC.doc P802.11vD6.0 has gone through Mandatory Editorial Coordination in July 2009 See 11-09-0801-00-000u-P802-11vD6 Mandatory Editorial Coordination MEC.doc P802.11zD5.0 has gone through Mandatory Editorial Coordination in July 2009 See 11-09-0810-00-000u-P802-11zD5 Mandatory Editorial Coordination MEC.doc Adrian Stephens, Intel Corporation from slide 9 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

12. Numbering Alignment Process Update from all published standards. Posted as 11-08/644r11 By Adrian Stephens TGz will start a new update cycle. Slide 12 Adrian Stephens, Intel Corporation from slide 10 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

13. 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 Adrian Stephens, Intel Corporation from slide 11 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

14. ANA Announcements Current ANA announced to group is 802.11-09-0031r8. (8/6/2009) See https://mentor.ieee.org/802.11/file/08/11-09-0031-08-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. Adrian Stephens, Intel Corporation from slide 12 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

15. Amendment Ordering Amendment numbering is editorial! No need to make ballot comments on these dynamic numbers! • Data as of Jan 2010 • See http://grouper.ieee.org/groups/802/11/Reports/802.11_Timelines.htm Adrian Stephens, Intel Corporation from slide 13 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

16. 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! Adrian Stephens, Intel Corporation from slide 14 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

17. Draft Development Snapshot Jan 2010 Most current doc shaded green. Changes from last report shown in red. Slide 17 Adrian Stephens, Intel Corporation from slide 15 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

18. 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 Adrian Stephens, Intel Corporation from slide 16 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

19. 802.11 Style Guide See 11-09-1034-00-0000-wg11-style-guide.doc Adrian Stephens, Intel Corporation from slide 17 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

20. Conference Calls Are they of any value? Next Meeting: March 14-19 Any need for conference calls? Adrian Stephens, Intel Corporation from slide 18 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

21. Reference Material Adrian Stephens, Intel Corporation from slide 19 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

22. 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 – comments on 09/1034? 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 802.11 for consistency across TGs Guidelines for primitives – ARC to consider Adrian Stephens, Intel Corporation from slide 20 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

23. 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. Adrian Stephens, Intel Corporation from slide 21 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

24. 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. Adrian Stephens, Intel Corporation from slide 22 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

25. 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:  • 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 email to sponsor and IEEE staff letting them know the Working Group has signed off on the publication process. Adrian Stephens, Intel Corporation from slide 23 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

26. 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 from slide 24 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

27. 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 27 Adrian Stephens, Intel Corporation from slide 25 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

28. 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 Adrian Stephens, Intel Corporation from slide 26 of 11-10/0072r2 by Peter Ecclesine (Cisco Systems)

29. Closing Report Authors: Date: 2010-01-22 Adrian Stephens, Intel Corporation from slide 1 of 11-10/0181r0 by Clint Chaplin, Chair (Samsung)

30. Abstract Closing report for WNG SC for January 2010, January 2010, El Pueblo de la Reina de Los Angeles, California, USA Adrian Stephens, Intel Corporation from slide 2 of 11-10/0181r0 by Clint Chaplin, Chair (Samsung)

31. Three presentations at this meeting • Adding 900 MHz ISM band into 802.11 (11-09-1313-05-0wng-900-mhz-ism-band.ppt and 11-10-0001-04-0wng-900mhz-par-and-5c.doc) – Dave Halasz • Motion to take PAR and 5 Criteria to full 802.11 WG • Result: Yes - 15; No - 5; Abstain – 14: passed • Motion in full 802.11 WG on Wednesday: Yes – 36; no – 18; Abstain – 32: fails • IEEE 802.11 for High Speed Mobility (11-09-1000-04-0wng-ieee802-11-for-high-speed-mobility.ppt) - Hiroshi Mano • An Example Protocol for FastAKM (11-10-0059-00-0wng) - Hiroki Nakano • Does WNG think that we need tutorial session exploring the need for support for mobile communication? • Result: Yes - 18; No - 1; Abstain - 7. • Minutes • 11-10-0111r0 • Plans for March 2010 • 2 2 hour sessions Adrian Stephens, Intel Corporation from slide 3 of 11-10/0181r0 by Clint Chaplin, Chair (Samsung)

32. January 2010 TGmb Closing Report Authors: Date: 2010-01-21 Adrian Stephens, Intel Corporation from slide 1 of 11-10/0180r0 by Matthew Gast, Trapeze Networks

33. Abstract Closing report for TGmb for January 2010 interim meeting in Los Angeles, California, USA. Adrian Stephens, Intel Corporation from slide 2 of 11-10/0180r0 by Matthew Gast, Trapeze Networks

34. TGmb Status Oh, what a tangled web recirculation can be… Photo credit: bicyclesonly on Flickr; used with permission (Creative Commons license) http://www.flickr.com/photos/bicyclesonly/359861603/ Adrian Stephens, Intel Corporation from slide 3 of 11-10/0180r0 by Matthew Gast, Trapeze Networks

35. Accomplishments • No interpretation requests received • Comment processing from LB160 is making good progress • 246 comments received; 104 remain (50 editorial, 54 technical) • No change to end date of plan of record • Recirculation letter ballot expected out of March plenary Adrian Stephens, Intel Corporation from slide 4 of 11-10/0180r0 by Matthew Gast, Trapeze Networks

36. Major Remaining Technical Issues • Tight coupling of regulatory regimes with normative behavior • See 11-10/0146r0 for an overview • Clause 11.3 state diagram • Opportunistic Keying comment group • Presentation to document existing implementation expected at March plenary meeting Adrian Stephens, Intel Corporation from slide 5 of 11-10/0180r0 by Matthew Gast, Trapeze Networks

37. References • Agenda: 11-10/0063r2 • Minutes: 11-10/0075r0 Adrian Stephens, Intel Corporation from slide 6 of 11-10/0180r0 by Matthew Gast, Trapeze Networks

38. TGp Closing Report Date: 2010-01-21 Author: Adrian Stephens, Intel Corporation from slide 1 of 11-10/0176r0 by Lee Armstrong (Armstrong Consulting, Inc.)

39. Abstract TGp closing report for January meetings Adrian Stephens, Intel Corporation from slide 2 of 11-10/0176r0 by Lee Armstrong (Armstrong Consulting, Inc.)

40. January Meetings Summary Sponsor Ballot #0 close, on 22 November, 93.4 % affirmative 9 time slots during the week Completed resolution of all comments prior to and during the week, resolution document is 11-09/1200r11 Voted to go to recirculation ballot as soon as possible Adrian Stephens, Intel Corporation from slide 3 of 11-10/0176r0 by Lee Armstrong (Armstrong Consulting, Inc.)

41. Status D10.0 will be going to recirculation ballot Weekly teleconferences planned for every Thursday @ 1500 Piscataway time (resuming after recirculation ballot is complete) Plan is to complete next round of comment resolutions before or during March meetings Adrian Stephens, Intel Corporation from slide 4 of 11-10/0176r0 by Lee Armstrong (Armstrong Consulting, Inc.)

42. TGs LA Closing Report Date: 2010-1-20 Author: Adrian Stephens, Intel Corporation from slide 1 of 11-10/0179r0 by Dee Denteneer

43. Abstract TGs closing report for January 2010 meeting. Adrian Stephens, Intel Corporation from slide 2 of 11-10/0179r0 by Dee Denteneer

44. Status • TGs passed LB 159 with 85% approval rate and 809 comments (Jan 2010) • During meeting • Appointed Guido Hiertz as vice Chair • Guenael Strutt as temporary secretary • Resolved comments 57% of comments (see table) • Annotated agenda in 11-10/0036r8, minutes 10/102r0 Adrian Stephens, Intel Corporation from slide 3 of 11-10/0179r0 by Dee Denteneer

45. Next Steps • Produce Draft 4.01 • Work on submissions for March meetings (most comments have clear owners) • TGs is holding teleconferences on Wednesdays through the January Plenary at 10am (ET)for up to 1½ hours on the Following Dates • February 3 and 17, and March 3 • Goal for the March 2010TGs meeting in Orlando, USA: • Resolve open comments and go to recirculation Adrian Stephens, Intel Corporation from slide 4 of 11-10/0179r0 by Dee Denteneer

46. Moved to schedule TGs teleconferences on february 3, and 17 and March 3 at 10:00 AM ET for a maximum of 90 minutes to resolve comments and discuss agendas. • Approved by unanimous consent Adrian Stephens, Intel Corporation from slide 5 of 11-10/0179r0 by Dee Denteneer

47. Closing Report Authors: Date: 2010-01-22 Adrian Stephens, Intel Corporation from slide 1 of 11-10/0172r0 by Stephen McCann, RIM

48. Abstract Closing report for TGu Interworking with External Networks for January 2010, Los Angeles, California, USA Adrian Stephens, Intel Corporation from slide 2 of 11-10/0172r0 by Stephen McCann, RIM

49. Initial Sponsor Ballot (#0) progress • Initial meeting of TGu CRC • Resolved 72 technical comments this week, with 1 remaining • 9 submissions presented and approved to resolve comments • 11-09-1120r16 • Next sponsor re-circulation ballot mid February 2010 • Teleconferences • Wednesdays at 12 ET (from 3rd February 2010) • Fridays at 11 ET (from 5th February 2010) • Plans for March 2010 • Resolve 2nd sponsor ballot comments Adrian Stephens, Intel Corporation from slide 3 of 11-10/0172r0 by Stephen McCann, RIM

50. January 2010 Closing Report Authors: Date: 2010-01-21 Adrian Stephens, Intel Corporation from slide 1 of 11-10/0177r0 by Dorothy Stanley (Aruba Networks)