1. Submission doc.: IEEE 11-14/0319r0 March 2014 Jon Rosdahl, CSRSlide 1 802-11 Proposed PAR Review March 2014 Date: 2014-03-18 Authors:

2. Submission doc.: IEEE 11-14/0319r0 March 2014 Jon Rosdahl, CSRSlide 2 Abstract PARS under consideration: Mar 16 - 21, 2014, Beijing, China: 1.802.3bp - amendment: 1 Gb/s Operation over Single Twisted Pair Copper Cable, PAR modification request and unmodified CSD responses (grandfathered 5 Criteria responses)PAR modification requestunmodified CSD responses 2.802.3bs - amendment: 400 Gb/s Ethernet, PAR and CSDPARCSD 3.802.11 HEW (High Efficiency WLAN), PAR and CSD (not covered here)PARCSD 4.802.15.3d 100Gbps wireless switched point-to-point physical layer, PAR and CSDPARCSD 5.802.15.4r Radio based Distance Measurement Techniques, PAR and CSDPARCSD 6.802.22 Revision PAR for 802.22-2011, PAR and CSDPARCSD 7.802.1Qcd PAR modification

3. Submission doc.: IEEE 11-14/0319r0 No comment from 802.11 1.802.3bp - amendment: 1 Gb/s Operation over Single Twisted Pair Copper Cable, PAR modification request and unmodified CSD responses (grandfathered 5 Criteria responses)PAR modification requestunmodified CSD responses 2.802.3bs - amendment: 400 Gb/s Ethernet, PAR and CSDPAR CSD Slide 3Jon Rosdahl, CSR March 2014

4. Submission doc.: IEEE 11-14/0319r0 4. 802.15.3d 100Gbps wireless switched point-to-point physical layer, PAR and CSDPARCSD 5.2.a and 5.2.b The scope is not bounded sufficiently. 5.2a and 5.2b Stakeholders will not be able to determine if this is a project if of interest with the scope as written. 5.2a and 5.2b It would seem that this project may overlap other projects. 5.2.b – The scope is not defined to a range that is definitive. Remove “or more” as a start, but the scope would need to be defined more crisply. 5.5 The last sentence is not true. (i.e. 802.11ad) 5.5 “guaranteed” is not possible when using unlicensed wireless bands. Slide 4Jon Rosdahl, CSR March 2014

5. Submission doc.: IEEE 11-14/0319r0 802.15.3d PAR (cont) 5.1 Would you check the number that is actively involved? 100 seems high (only 20 people from 11 organizations attended the Study Group in January) 7.1 – There would seem to be some projects of similar scope – i.e. 802.15.3c, 802.11ad, Transferjet, etc. General Question – Is this the project that is getting the.1AC MAC address space correction? General: The CSD includes a suggested range of “up to several 100m” Slide 5Jon Rosdahl, CSR March 2014

6. Submission doc.: IEEE 11-14/0319r0 802.15.3d CSD (cont)CSD 1.2.1 a) “guaranteed” – this is not possible – reword sentence. 1.2.1 a) The use cases seem too broad to be believable. 1.2.2 – Is 48-bit addressing required to be conformant with 802.1AC, if so, is this PAR proposing to use 48-bit addressing? 1.2.5 Is the proposed application consistent with modern data centers? Does this apply more to older deployed data centers for retro upgrade? If the data center is wired up, the change of configuration is typically done via software. So does this wireless technology provide a benefit given the wired connectivity? Slide 6Jon Rosdahl, CSR March 2014

7. Submission doc.: IEEE 11-14/0319r0March 2014 Jon Rosdahl, CSRSlide 7 5. 802.15.4r Radio based Distance Measurement Techniques, PAR and CSDPARCSD 5.5 – expand RTLS the first instance it is used. CSD – 14.2.3 The first sentence does not parse well. Consider rewording This statement does not seem to indicate a distinct identity, but rather a change to the radio being used. “needs of IEEE 802.15.4” - the standard has not the “need” but rather the users of the standard. Could this statement simply be that you are adding ranging to your 802.15.4 radio?

8. Submission doc.: IEEE 11-14/0319r0March 2014 Jon Rosdahl, CSRSlide 8 6. 802.22 Revision PAR for 802.22-2011, PAR and CSD PARCSD General – This seems to be a word document that does not capture the correct PAR format. Please put into myProject and allow it to generate the proper output file to give the correct change bars and edit changes. 2.1 Title – dropping the TV from the “TV bands” leaves the title without bound of the frequencies being used. Suggest add “bands between 1300 MHz to 1750 MHz, 2700 MHz to 3700 MHz and 54 MHz to 862 MHz. “ to the title to ensure people know what this standard is covering. 7.1 802.11af should be lower-case.

9. Submission doc.: IEEE 11-14/0319r0 802.22 Revision PAR (Cont) 8.1 the text there does not belong – it does not indicate which section it is giving extra explanation to. Delete all the text in 8.1 – consider adding to CSD or to section 5.5 Need for project. Use approved CSD form: CSD 1.2.2 – missing template or question…not from the approved template? CSD 1.2.4 missing template or question…not from the approved template? CSD 802.11af should be lowercase letters. Change all instances. CSD 1.2.4 last sentence does not parse correctly. Look at how this “802.22 (Wi-Far)” is described. Slide 9Jon Rosdahl, CSR March 2014

10. Submission doc.: IEEE 11-14/0319r0 7. 802.1Qcd Par Modification 5.2b – this section does not read correctly. The “Minor addition” seems like an editorial instruction or an informative word that should be removed. Are you changing the scope of the project as shown in both paragraphs in 5.2b? Is the scope change just the addition of the new text. It seems to be a summary for the scope of the project (potentially) or if it is the incremental addition to the scope, then just rewrite the scope of the project as such. 8.1 -- PAR modification form requires a statement of what and why (rationalization) the PAR is being changed be included in 8.1. Please add. Slide 10Jon Rosdahl, CSR March 2014

11. Submission doc.: IEEE 11-14/0319r0March 2014 Jon Rosdahl, CSRSlide 11 References PARS under consideration are listed here: http://grouper.ieee.org/groups/802/PARs.shtml