1. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 1 New WG PARs that WG11 must consider in March 2009 Date: 2009-03-09 Authors:

2. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 2 Abstract This document contains the comment responses received from members of 802.11 WG. The WG has requested that this submission be used as the 802.11 WG response to the new 802 PARs that were under consideration for March 2009.

3. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 3 From Monday Agenda 4.1.5 New WG PARs that WG11 must consider in March 1.802.21 WG : Support for Emergency Services –The PAR and 5C can be found at: –http://mentor.ieee.org/802.21/file/09/21-09-0027-00-00es-emergency- services-par-and-5c.dochttp://mentor.ieee.org/802.21/file/09/21-09-0027-00-00es-emergency- services-par-and-5c.doc 2.802.21 WG : Multi-Radio Power Management –The PAR and 5C can be found at: –http://mentor.ieee.org/802.21/file/09/21-09-0021-00-mrpm-mrpm-revised-par- 5c.dochttp://mentor.ieee.org/802.21/file/09/21-09-0021-00-mrpm-mrpm-revised-par- 5c.doc 3.802.22 WG : TV WhiteSpace PAR Amendment to add mobile and portable device functionality –https://mentor.ieee.org/802.22/file/09/22-09-0029-00-0000-draft-22a-par.dochttps://mentor.ieee.org/802.22/file/09/22-09-0029-00-0000-draft-22a-par.doc –https://mentor.ieee.org/802.22/dcn/09/22-09-0030-01-0000-draft-22a-5c.dochttps://mentor.ieee.org/802.22/dcn/09/22-09-0030-01-0000-draft-22a-5c.doc

4. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 4 From Monday Agenda 4.1.5 New WG PARs that WG11 must consider in March 802.3ad PAR for Priority-based Flow Control MAC Control Frame This proposed PAR is to add a MAC Control Frame to IEEE 802.3 to support 802.1Qbb Priority-based Flow Control. Note that the 802.1 Working Group will be responsible for this PAR. As usual when doing a cross group PAR, 802.3 voters who request it will be added to the Working Group voting pool on this project. The PAR is at: http://www.ieee802.org/1/files/public/docs2008/bb-thaler-pfc-frame-par- 1108.pdfhttp://www.ieee802.org/1/files/public/docs2008/bb-thaler-pfc-frame-par- 1108.pdf Since this PAR is to support the 802.1Qbb PAR, the same 5 criteria applies to it: http://www.ieee802.org/1/files/public/docs2008/new-dcb-thaler-draft-pfc-5c- 0208-v3.pdfhttp://www.ieee802.org/1/files/public/docs2008/new-dcb-thaler-draft-pfc-5c- 0208-v3.pdf

5. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 5 From Monday Agenda item 4.1.6 March 2009 - Tutorials Monday, March 9, 2009 Tutorial #1 (6:30 pm): Multi-radio Power Conservation Management sponsored by Vivek Gupta –Dennis Edwards - CoCo Communications –Junghoon Jee - ETRI –H Anthony Chan - Huawei Technology Call for interest (8:00 pm): IEEE 802.3 Support for IEEE 802.1AS Time and Synchronization –Steve Carlson - High Speed Design –David Law - IEEE 802.3 WG Chair Tuesday, March 10, 2009 Tutorial #2 (6:30 pm): White Space Tutorial –Matthew Sherman - BAE Systems Tutorial #3 (9:00 pm): IEEE-SA Patent Pool Collaboration with Via Licensing –Edward Rashba - IEEE Standards Association –Torey Bruno - Via Licensing

6. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 6 Feedback to 802.1/802.3 No comment feedback received.

7. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 7 802.21 PAR Feedback (1) 802.21 WG : Multi-Radio Power Management –General comment: If you are managing Watts, then measure Watts. Power consumption is not generally available from Radio interfaces, so it is not meaningful to manage power control using measurements that are not available. (802.2 LLC does not expose power consumption). –Multiple Radio Power Management does not belong in 802.21. Handover control is not the same as Power management. –Power management in a client is truly an implementation issue not a standardization issue –The 5C provide insufficient justification for starting this project.

8. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 8 802.21 PAR Feedback (2) 802.21 WG : Support for Emergency Services –General comments: Emergency Services (E-911, PSAP, etc) are important services that may benefit from standardization. This needs to start soon, but we do not believe that 802.21 is not the proper place. We suggest that a separate 802 WG be considered to allow the autonomy and focus necessary to create a standard in a timely manner. This WG would also need to ensure cooperation and coexistence with the other 802 WGs. The PAR should be broken up into 3 separate destinct PARS –1-- Client to Authority (E-911) –2 – Authority to client (emergency warning broadcast – Amber alert) –3 – Authority to Authority (network prioritization and control)

9. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 9 802.21 PAR Feedback (3) 802.21 WG : Support for Emergency Services

10. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 10 802.22a PAR Feedback Comments (1) General comment: 802.22 is described as a Regional Area Network that is reusing the TV Bands. All PARs from this WG should reflect this in their scope and purpose. 5.1 – The Number of people claimed in the PAR does not match current voter list numbers or attendees of recent meetings of 802.22. Please explain the number of Attendees used.

11. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 11 802.22a PAR Feedback Comments (2) 5.2 – Information indicating the restricted network area that is envisioned should be added. Suggested change “…Operation is limited to operation in regional area networks utilizing the TV bands between….” 5.3 – The PAR claims that work needs to start now so that changes to the current draft can be identified prior to completion of the base draft; however, this suggests that the PAR for the base standard should be revised. Suggest that a PAR revision be considered prior to requesting This new PAR.

12. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 12 802.22a PAR Feedback Comments (3) 5C: Broad Market Potential –The first three paragraphs address the fixed 802.22 standard, not the topic of this 5C. It is very unclear that there is a broad market for fixed 802.22 in United States under the FCC 08-260 rules. Nothing here addresses whether the 802.22 fixed vendors will also vend mobile and portable user terminals, and nothing addresses the cost benefits of volume production (see Technical Feasibility). While 802.16 and 802.11 vendors are in volume production, 802.22 vendors are not. Nothing addresses whether silicon vendors who already have PAN, LAN and MAN circuits in their products would add another LAN or PAN for this band, when the others could be used.

13. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 13 802.22a PAR Feedback Comments (4) 5C: Compatibility –This paragraph addresses the fixed 802.22 standard, not the topic of this 5C. 5C: Distinct Identity –Distinct Identify has not been established. –For example, 802.11-2007 provides means to operate in bands with fixed and mobile licensed devices (see Technical Feasibility). 802.11y provides the control means for a database to allow operation on white space channels at a location, and to control power level and other operational characteristics. It is clear that 802.22a mobile and personal devices will use shorter symbol times than 802.22 fixed devices, and it is not clear how they differ from 802.16h mobile and portable devices.

14. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 14 802.22a PAR Feedback Comments (5) 5C: Technical Feasibility: –VHF is not allowed for personal/portable operation, only TV channels 21-51 in lower UHF. 5C: Technical Feasibility: –.16/.22 type protocols which are optimized for licensed bands, and yet are being applied to unlicensed bands. For Example, the sharing of the overlap RF coverage areas will degrade faster with a.16/.22 type protocol than a.11 protocol.

15. doc.: IEEE 802.11-09/0356r0 Submission March 2009 Jon Rosdahl, CSRSlide 15 References 11-09/0286r3 https://mentor.ieee.org/802.11/dcn/09/11-09-0286-03-0000-plenary- information-mar-09.ppthttps://mentor.ieee.org/802.11/dcn/09/11-09-0286-03-0000-plenary- information-mar-09.ppt 21-09-0027r0 http://mentor.ieee.org/802.21/file/09/21-09-0027-00-00es-emergency-services- par-and-5c.dochttp://mentor.ieee.org/802.21/file/09/21-09-0027-00-00es-emergency-services- par-and-5c.doc 21-09-0021r0 http://mentor.ieee.org/802.21/file/09/21-09-0021-00-mrpm-mrpm-revised-par- 5c.dochttp://mentor.ieee.org/802.21/file/09/21-09-0021-00-mrpm-mrpm-revised-par- 5c.doc 22-09-0029r0 and 0030r1 https://mentor.ieee.org/802.22/file/09/22-09-0029-00-0000-draft-22a-par.doc https://mentor.ieee.org/802.22/dcn/09/22-09-0030-01-0000-draft-22a-5c.doc 802.3 and 802.1 docs: http://www.ieee802.org/1/files/public/docs2008/bb-thaler-pfc-frame-par- 1108.pdf:http://www.ieee802.org/1/files/public/docs2008/bb-thaler-pfc-frame-par- 1108.pdf http://www.ieee802.org/1/files/public/docs2008/new-dcb-thaler-draft-pfc-5c- 0208-v3.pdfhttp://www.ieee802.org/1/files/public/docs2008/new-dcb-thaler-draft-pfc-5c- 0208-v3.pdf