1 / 136

802.11 Nov 2008 Closing Plenary Reports

802.11 Nov 2008 Closing Plenary Reports. Authors:. Date: 2008-11-14. Abstract. This document is a digest of the closing reports of all 802.11 sub-groups for presentation at the November 2008 closing plenary meeting. Editor’s Meeting (November). Date: 2008-11-11. November 2008. Authors:.

rhondaj
Télécharger la présentation

802.11 Nov 2008 Closing Plenary Reports

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 802.11 Nov 2008 Closing Plenary Reports Authors: Date: 2008-11-14 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 November 2008 closing plenary meeting. Adrian Stephens, Intel Corporation

  3. Editor’s Meeting (November) Date: 2008-11-11 November 2008 Authors: Slide 3 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 1 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  4. 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 Slide 4 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 2 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  5. Roll Call 802.11 Editor’s Present P802.11n Amendment (HT) – Adrian Stephens P802.11p Amendment (WAVE) – Wayne Fisher P802.11s Amendment (MESH) – P802.11u Amendment (IW) -- Necati Canpolat P802.11v Amendment (WNM) – Emily Qi P802.11y Amendment (CBP) – Peter Ecclesine P802.11w Amendment (SEC) – Nancy Cam-Winget P802.11z Amendment (TDLS) – Menzo Wentink, pro tem P802.11aa Amendment (VTS) – Hang Liu 802.11 Editor’s Not Present P802.11T Recommended Practice (WPP) – Tom Alexander Also present: Clint Chaplin, Jon Rosdahl, Bill Marshall IEEE Staff present Michelle Turner – staff editor for 802, m.turner@ieee.org 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 November 2008 Slide 5 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 3 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  6. Volunteer Editor Contacts TGn – Adrian Stephens – adrian.p.stephens@intel.com TGp – Wayne Fisher – wfisher@arinc.com TGs – TGT – Tom Alexander – tom@veriwave.com TGu – Necati Canpolat – necati.canpolat@intel.com TGv – Emily Qi – emily.h.qi@intel.com TGw – Nancy Cam-Winget – ncamwing@cisco.com TGz – Menzo Wentink– mwentink@qualcomm.com(permanent editor position open) TGmb – Not yet determined TGaa – Hang Liu – hang.liu@thomson.net Editor Emeritus: TGk – Joe Kwak– joekwak@sbcglobal.net TGr – Bill Marshall – wtm@research.att.com TGy – Peter Ecclesine – pecclesi@cisco.com November 2008 Slide 6 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 4 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  7. 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 • All present receiving reflector traffic • No email address changes requested November 2008 Slide 7 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 5 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  8. IEEE Publication Status IEEE 802.11-2007 published and for sale on IEEE web Published in June 2007 Combines all existing amendments and includes maintenance work by TGma Publications completed for 802.11k, 802.11r and 802.11y 11n has gone through Mandatory Editorial Coordination (08-1045) 11w has gone through Mandatory Editorial Coordination (08-????) November 2008 Slide 8 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 6 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  9. November 2008 Alignment Process for 802.11k/r/y • The 08/0644r3 Numbering Spreadsheet has all changes from publication of 11k and 11r and 11y (and 11n D6.01) Slide 9 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 7 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  10. November 2008 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 from slide 8 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  11. November 2008 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 11 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 9 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  12. November 2008 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 12 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 10 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  13. 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. November 2008 Slide 13 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 11 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  14. 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 Slide 14 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 12 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  15. ANA Announcements Current ANA announced to group is 802.11-08-0227r1. See https://mentor.ieee.org/802.11/file/08/11-08-0227-01-0000-ana-database-assigned-numbers.xls All new requests received by end of meeting will be uploaded and announced via 802.11 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 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 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. November 2008 Slide 15 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 13 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  16. Amendment Ordering November 2008 Amendment reordering was discussed by editors Nov 11 based on current timeline estimates and resulted announced herein. Amendment numbering is editorial! No need to make ballot comments on these dynamic numbers! • Data as of Nov 11 from 802.11 web. • See http://grouper.ieee.org/groups/802/11/Reports/802.11_Timelines.htm Slide 16 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 14 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  17. 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! November 2008 Slide 17 Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 15 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  18. November 2008 Draft Development Snapshot Changes from last report shown in red. Most current doc shaded green. Peter Ecclesine (Cisco Systems) Adrian Stephens, Intel Corporation from slide 16 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  19. 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 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 November 2008 Slide 19 Terry L Cole (self) Adrian Stephens, Intel Corporation from slide 17 of IEEE 802.11-08/1345r2 by ‹footer›Peter Ecclesine (Cisco Systems)

  20. WNG Closing Report, November Authors: Date: 2008-11-14 Adrian Stephens, Intel Corporation from slide 1 of IEEE P802.11-08/1405r0 by Tk Tan, GCT Semiconductor

  21. Abstract Closing Report for WNG Standing Committee (SC) for November 2008, Dallas, Texas USA. Adrian Stephens, Intel Corporation from slide 2 of IEEE P802.11-08/1405r0 by Tk Tan, GCT Semiconductor

  22. Tuesday I (cont’)11 November 2008, 08:00 – 10:00 • Hitoshi Morioka • 11-08-1337-00-0wng-broadband-access-for-high-speed-transportation.ppt • Woong Cho • 11-08-1273-01-0wng-hybrid-mac-for-vanet.ppt • Alex Reznik • 11-08-1259-00-0wng-security-of-wireless-networks-how-low-layers-security-can-help.ppt • Marc Emmelmann • 11-08-1346-00-0wng-topology-discovery-and-coverage-area-approximation-with-802-11k.ppt • Peter Ecclesine • 11-08-1254r1: "TV white space FCC action" Adrian Stephens, Intel Corporation from slide 3 of IEEE P802.11-08/1405r0 by Tk Tan, GCT Semiconductor

  23. white space SG motion • Request approval by IEEE 802 LMSC to form an 802 Study Group to review TV white space in the light of the FCC’sTV white space actions of November 4, 2008 , with the intent of creating a PAR and five criteria. • Moved Ivan Reede • Second Roger Durand • Vote 47-7-23 • WNG Motion Passes Adrian Stephens, Intel Corporation from slide 4 of IEEE P802.11-08/1405r0 by Tk Tan, GCT Semiconductor

  24. 802.11 Arc Standing Committee Authors: Date: 2008-11-10 Adrian Stephens, Intel Corporation from slide 1 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  25. Abstract Agenda, working document and report for ARC SC, Nov 2008, Dallas Adrian Stephens, Intel Corporation from slide 2 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  26. IEEE P802.11 Architecture Committee Agenda, working document & report. Nov 2008 sessions. Adrian Stephens, Intel Corporation from slide 3 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  27. Arc Agenda – Nov 2008 • Admin • Attendance • Policies • Meeting goals • Short recap of work from telecons • Continue work on MAC block diagrams • Future session planning Adrian Stephens, Intel Corporation from slide 4 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  28. Attendance • Reminder to attendees to sign in for .11 attendance credit Adrian Stephens, Intel Corporation from slide 5 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  29. IP policy • A SC is covered by the WG IP policy announcements. • Even though we don’t have to read the policy to SC attendees, all attendees are reminded that the policies are in effect and apply to SC sessions. Adrian Stephens, Intel Corporation from slide 6 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  30. Arc SC – Meeting Goals Short recap of Telecons since last session. Continuation of MAC block diagram work Adrian Stephens, Intel Corporation from slide 7 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  31. Discussion Topic Ground Rules • We are exploring - • Small group, open, honest dialog • Session is not oriented toward being a tutorial, • Participation requires familiarity with 2007 contents. Adrian Stephens, Intel Corporation from slide 8 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  32. MAC block diagram working documents • Doc 08/949r3 • Doc 08/1298r0 Adrian Stephens, Intel Corporation from slide 9 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  33. Session Summary • Reviewed work from telecons • Updated working docs to reflect consensus resulting in doc revisions • 08/949r4 • 08/1298r1 • Laid out next steps for model refinements • Continued MAC model discussion & refinement Adrian Stephens, Intel Corporation from slide 10 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  34. Planning for Jan • Will have 2 conf calls before Jan sessions • Tues, 13:00-14:00 ET • 12/16 • 1/13 • Next F2F session in Jan 2009 in los Angeles Adrian Stephens, Intel Corporation from slide 11 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  35. Relevant Documents • 08/9494r4 – updated historical record of diagrams as they have evolved • 08/1298r1 – MAC diagram working document. • 08/1256r2 – this report • 08/1426r0 – minutes for Nov Arc session Adrian Stephens, Intel Corporation from slide 12 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  36. Background material: Session notes • Notes are points informally captured during SC discussions - they are not minutes. Adrian Stephens, Intel Corporation from slide 13 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  37. Notes: Tues Am 1 • How much complexity in diagrams considering the goals? • Tentative Proposal: 5-7 “blocks” on a diagram page; 2 levels - 1 top, 1 of drill down; approx one page text per diagram page. • Seemed a good 1st cut goal • Don’t want clause references to drive explanatory level of detail. • 2007 vs. 1999 doc target shift – implications • We still agree 2007 is right target doc; diagrams to date are 1999 async data centric; more work to do for 2007. Adrian Stephens, Intel Corporation from slide 14 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  38. Notes Tues AM1 • Scope of MAC arc doc functionality • Probable 2 categories • Included functionality • Done and in doc • Work still to be done in doc • Ignored within doc • Not felt to be important by SC participants for goals • Generally considered obsolete • Low ROI on effort required to include Adrian Stephens, Intel Corporation from slide 15 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  39. Notes Tues AM1 • Driving message sequences • A Subset of 1999 was initial set • Were items left out ok to continue to ignore? • Or do we need to include some? • Included to date: • Basic async data slow • Leaving out: • PCF – supplanted by TGe in 2007 • Orig PHY related control stuff (FH, DS, IR phys, 1997 regulatory stuff). • What of (Delta 2007-1999) needs to be added? • Which big chucks of functionality? • Driving sequences to use? • Look ahead exercise (to be done later) • Diagrams “mostly ok” for post 2007 active TG impacts? Adrian Stephens, Intel Corporation from slide 16 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  40. Notes Tues AM1 • Misc to-do • Enhance intro text in doc • Purpose explanation • Useful framework to understand/discuss changes proposed by Task Groups • Intro to overall mac functionality before dive into standard itself Adrian Stephens, Intel Corporation from slide 17 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  41. Thurs AM2 notes • Driving sequences to try to get (2007-1999) impacts • Probable useful order for exercise? • Simple data missing ack • Finish Data flows cases, missing ack cases • Power saving impacts • Security • WEP • TGi • QOS sequences • Queuing in common • One or both schedulers? • EDCA 1st then HCCA • TGh • (management frame sequences => time bounds handled in what block(s)) • PHY control (rf pwr etc) Adrian Stephens, Intel Corporation from slide 18 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  42. Thurs AM2 notes • MIB variable mess • Temporal relation of mib value change vs. action • Control • Internal interfaces • External interfaces Adrian Stephens, Intel Corporation from slide 19 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  43. Thurs AM2 notes • Discussion: initial consideration of QOS addition to diagrams. • Re QOS impacts – where is logical queuing put for retry? Block 3 or 5? • Many or one thing at a time from 3 to 5? • Does 5 have any data store? • Is there flow control between 3/5? • What happens if we think of QOS as multiple instances of some part (maybe all) of the top level diagram? • Is it a virtual STA? (collisions happen at the common medium). • Prob less than the “sta”… Partition by state for medium access? (where is that in current diagram?) Adrian Stephens, Intel Corporation from slide 20 of IEEE 802.11-08/1256r1 by David Bagby, Calypso Ventures, Inc.

  44. November 2008 Closing Report Authors: Date: 2008-11-13 Adrian Stephens, Intel Corporation from slide 1 of IEEE 802.11-08/1428r0 by Matthew Gast, Trapeze Networks

  45. Abstract Closing report for TGmb (Maintenance) for November 2008 plenary meeting in Dallas, Texas, USA. Adrian Stephens, Intel Corporation from slide 2 of IEEE 802.11-08/1428r0 by Matthew Gast, Trapeze Networks

  46. Accomplishments • Processed one interpretation request (#15) • Approved revised PAR • Closed call for comments as input into revision process on November 10 • 104 comments received • 28 comments resolved • Sub-groups formed to propose resolutions in January interim meeting Adrian Stephens, Intel Corporation from slide 3 of IEEE 802.11-08/1428r0 by Matthew Gast, Trapeze Networks

  47. Interpretation Request #1 • Request received from Johannes Berg <johannes@sipsolutions.net> :In 802.11-2007, section 11.7.1.2 ("Setup procedure at the AP") [for DLS] notes:"[...] Send DLS Response frame to the STA that sent the DLS Request frame with a result code of Not a STA, if the destination STA [...]“Is this meant to say"[...] Send DLS Response frame to the STA that sent the DLS Request frame with a result code of Not QoS STA, if the destination STA [...]“(note "Not QoS STA") • Note: emphasis added Adrian Stephens, Intel Corporation from slide 4 of IEEE 802.11-08/1428r0 by Matthew Gast, Trapeze Networks

  48. Interpretation Response • Designation Number: 15 • Classification: Unambiguous • Relevant Clauses: 11.7.1.2 • Response:IEEE Std. 802.11-2007 contains a mapping of result codes from DLS setup primitives into status codes in Table 11-6. Table 11-6 contains the result codes NOT_ALLOWED, NOT_PRESENT, and NOT_QOS_STA. The status codes defined by IEEE Std. 802.11-2007 are found in Table 7-23, and use status code 50 for "The Destination STA is not a QoS STA.”The standard provides no additional detail. The question of whether additional detail is needed will be forwarded to the 802.11 Working Group for consideration in the next revision of the P802.11 standard. Adrian Stephens, Intel Corporation from slide 5 of IEEE 802.11-08/1428r0 by Matthew Gast, Trapeze Networks

  49. Teleconferences • Weekly, 4 pm ET on Wednesdays Adrian Stephens, Intel Corporation from slide 6 of IEEE 802.11-08/1428r0 by Matthew Gast, Trapeze Networks

  50. Objectives for January • Find a volunteer as technical editor • Prepare for March 2009 letter ballot • Continue initial review • Consider proposed resolutions and presentations to remaining comments Adrian Stephens, Intel Corporation from slide 7 of IEEE 802.11-08/1428r0 by Matthew Gast, Trapeze Networks

More Related