Docstoc

11-11-0276-08-00ac-tgac-d0-1-comments

Document Sample
11-11-0276-08-00ac-tgac-d0-1-comments Powered By Docstoc
					            IEEE P802.11 Wireless LANs
            Submission
Designator: doc.: IEEE 802.11-11/0276r8
Venue Date: March 2011
First Author: Robert Stacey, Intel Corporation

Subject:      IEEE P802.11ac/D0.1 comment spreadsheet
Full Date:    2011-03-31
Author(s):    Robert Stacey
              Company: Intel Corporation
              Address
              Phone:     +1-503-724-0893
              Fax:
              email:     robert.j.stacey@intel.com
Abstract:
              This document tracks comment resolution for the IEEE P802.11ac/D0.1 draft.
Revision        Date
            0      2011-02-28
            1      2011-02-28
            2      2011-03-03
            3      2011-03-04
            4      2011-03-10
            5      2011-03-13
            6      2011-03-15
            7      2011-03-28
            8      2011-03-31
            9
           10
           11
           12
           13
           14
           15
           16
           17
           18
           19
           20
           21
           22
           23
           24
           25
           26
           27
           28
           29
           30
Description
Initial compilation of comments. Review by ad-hoc chairs with ad-hoc assignment for each comment
A few additional late comments added
Resolution column updated during Tgac telecon
Added Title and Revision history tabs. Resolutions to some of the editorial comments.
Work on editorial comments. Added volunteer names to resolve various comments.
Additional volunteer names added. Additional editor comments actioned. Summary worksheet added.
Updated with approved resolutions. Referenced documents proposing resolutions.
Implemented approved resolutions.
Unassigned comments given owners
                  Initial    Unassigned Unresolved
MAC                      195           0        147
PHY                      331           0        268
MU                       168           0         85
COEX                     102           0         88
Total Technical          796           0        588
Editorial              1016
Other                      3
Total                  1815
             Draft Updated
Resolved     or No Change
        48               48
        63               63
        83               77
        14               14
       208              202
         9              473
         0                 0
       217              675
CommentID   CommenterName     Subclause   Page   Line   CommentType


      1228 Stephens, Adrian               1      45     ER




       239 Hart, Brian        3.1         2      9      TR




       997 Seok, Yongho       3.1         2      9      ER




       180 Cordeiro, Carlos   3.1         2      10     TR




      1805 Yee, James         3.1         2      10     TR
 237 Hart, Brian      3.1   2   13   TR




 238 Hart, Brian      3.1   2   13   ER




1806 Yee, James       3.1   2   19   ER




1573 Zhu, Chunhui     3.1   2   22   TR




 693 Kneckt, Jarkko   3.2   2   25   TR




  19 Asai, Yusuke     3.2   2   42   ER
 240 Hart, Brian   3.2   2   49   ER




1807 Yee, James    3.2   2   50   ER




1808 Yee, James    3.2   2   50   ER




 241 Hart, Brian   3.2   2   53   ER
 242 Hart, Brian    3.2   2   57   TR




 243 Hart, Brian    3.2   2   64   TR




1574 Zhu, Chunhui   3.2   3   6    TR
 998 Seok, Yongho   3.2   3   20   ER




1517 SOHN, ILLSOO   3.2   3   20   ER




 999 Seok, Yongho   3.2   3   24   ER
 20 Asai, Yusuke     3.2   3   29   TR




244 Hart, Brian      3.2   3   29   TR




245 Hart, Brian      3.2   3   37   TR


246 Hart, Brian      3.2   3   37   ER

676 Kneckt, Jarkko   3.2   3   38   TR
1470 Lv, Kaiying      3.2   3   38   TR




 218 Gong, Michelle   3.2   3   39   ER




 219 Gong, Michelle   3.2   3   43   ER




 677 Kneckt, Jarkko   3.3   3   46   ER




1575 Zhu, Chunhui     3.3   3   50   ER
1000 Seok, Yongho       3.3     3   54   ER




1399 Kang, Byeongwoo    3.3     3   54   ER




1001 Seok, Yongho       3.3     3   62   ER




 181 Cordeiro, Carlos   7.1.2   4   9    ER




1118 Stacey, Robert     7.1.2   4   14   TR




1002 Seok, Yongho       7.1.2   4   27   ER


1119 Stacey, Robert     7.1.2   4   27   TR




1459 Lee, Daewon        7.1.2   4   27   ER
1229 Stephens, Adrian   7.1.2       4   33   ER


 934 Santosh Abraham,   7.1.3.1     4   40   TR
     Simone Merlin


1242 Stephens, Adrian   7.1.3.1.2   4   41   ER




  21 Asai, Yusuke       7.1.3.1.7   4   48   TR




  99 Au, Edward (Kwok   7.1.3.1.7   4   48   TR
     Shum)




 678 Kneckt, Jarkko     7.1.3.1.7   4   48   ER
695 Kneckt, Jarkko   7.1.3.1.7   4   48   TR
 696 Kneckt, Jarkko   7.1.3.1,7   4   48   TR




 758 Liu, Yong        7.1.3.1.7   4   48   TR




1723 Lee, Jae Seung   7.1.3.1.7   4   48   TR




1789 Patil, Sandhya   7.1.3.1.7   4   48   TR
  22 Asai, Yusuke       7.1.3.1.7   4   49   TR




 679 Kneckt, Jarkko     7.1.3.1.7   4   50   ER

 759 Liu, Yong          7.1.3.1.7   4   50   ER

1471 Lv, Kaiying        7.1.3.1.7   4   50   ER




1722 Lee, Jae Seung     7.1.3.1.7   4   50   ER

1230 Stephens, Adrian   7.1.3.3.7   4   65   TR




 247 Hart, Brian        7.1.3.3.7   5   1    TR




1804 Ye, Huanchun       7.1.3.3.7   5   1    TR
908 Santosh Abraham,   7.1.3.1.9   5   4   TR
    Simone Merlin
 907 Santosh Abraham,   7.1.3.5a   5   10   TR
     Simone Merlin




1352 Zhao, Shiwei       7.1.3.5a   5   10   ER




1472 Lv, Kaiying        7.1.3.5a   5   10   ER
1120 Stacey, Robert     7.1.3.5a   5   11   TR




1232 Stephens, Adrian   7.1.3.fa   5   15   ER
 906 Santosh Abraham,   7.1.3.5a   5   19   ER
     Simone Merlin




 233 Grandhi, Sudheer   7.1.3.5a   5   27   TR




1231 Stephens, Adrian   7.1.3.5a   5   30   ER
  23 Asai, Yusuke       7.1.3.5a    5   37      TR




1473 Lv, Kaiying        7.1.3.5a    5   42      TR




1233 Stephens, Adrian   7.1.3.5a    5   46      ER




1003 Seok, Yongho       7.1.3.3.7   5   1-2     TR


1400 Kang, Byeongwoo    7.1.3.3.7   5   1-2     TR




1344 Zhang, Hongyuan    7.1.3.5a    5   36-56   TR




 760 Liu, Yong          7.1.3.5a    5   37-56   ER


1234 Stephens, Adrian   7.1.3.5a    6   5       TR
 100 Au, Edward (Kwok   7.1.3.5a   6   1~5   TR
     Shum)




1576 Zhu, Chunhui       7.1.3.5a   7   5     ER




1577 Zhu, Chunhui       7.1.3.5a   7   26    ER




 909 Santosh Abraham,   7.1.3.5a   7   34    ER
     Simone Merlin

 885 Porat, Ron         7.1.3.5a   7   38    TR




1004 Seok, Yongho       7.1.3.5a   7   38    ER




1005 Seok, Yongho       7.1.3.5a   7   40    ER
1353 Zhao, Shiwei       7.1.3.5a    7   40      ER




1401 Kang, Byeongwoo    7.1.3.5a    7   40      ER

1578 Zhu, Chunhui       7.1.3.5a    7   40      ER




  24 Asai, Yusuke       7.1.3.5a    7   58      TR




 910 Santosh Abraham,   7.1.3.5a    7   64      ER
     Simone Merlin




1345 Zhang, Hongyuan    7.1.3.5a    7   58~64   TR




1006 Seok, Yongho       7.1.3.5.1   8   1       ER


1402 Kang, Byeongwoo    7.1.3.5.1   8   1       ER
1007 Seok, Yongho       7.1.3.5.3   8   19   TR




1442 Kang, Byeongwoo    7.1.3.5.3   8   19   TR




  25 Asai, Yusuke       7.1.3.5.3   8   21   TR




1235 Stephens, Adrian   7.1.3.5.3   8   22   TR




  26 Asai, Yusuke       7.1.3.5.3   8   31   ER


 680 Kneckt, Jarkko     7.1.3.5.3   8   36   ER
153 Carney, Bill     7.1.4     8   42   TR




683 Kneckt, Jarkko   7.2.1.1   8   50   TR
1236 Stephens, Adrian   7.2.1.1   8   55   TR




 220 Gong, Michelle     7.2.1.1   8   57   TR




 154 Carney, Bill       7.2.1.1   8   60   TR




1237 Stephens, Adrian   7.2.1.6   9   5    ER
698 Kneckt, Jarkko   7.2.1.6    9   7    TR




 27 Asai, Yusuke     7.2.1.11   9   12   ER




 28 Asai, Yusuke     7.2.1.11   9   12   ER




 29 Asai, Yusuke     7.2.1.11   9   12   ER
  30 Asai, Yusuke       7.2.1.11   9   12   TR




1809 Yee, James         7.2.1.11   9   12   ER




1238 Stephens, Adrian   7.2.1.11   9   14   ER




 912 Santosh Abraham,   7.2.1.11   9   18   TR
     Simone Merlin




1239 Stephens, Adrian   7.2.1.11   9   20   ER
 801 Loc, Peter         7.2.1.11   9   24   TR




1008 Seok, Yongho       7.2.1.11   9   27   ER




 681 Kneckt, Jarkko     7.2.1.11   9   28   ER

 761 Liu, Yong          7.2.1.11   9   28   ER


 911 Santosh Abraham,   7.2.1.11   9   28   ER
     Simone Merlin

1579 Zhu, Chunhui       7.2.1.11   9   28   ER

 682 Kneckt, Jarkko     7.2.1.11   9   36   ER
1009 Seok, Yongho       7.2.1.11   9    36       ER


1580 Zhu, Chunhui       7.2.1.11   9    41       ER




1240 Stephens, Adrian   7.2.1.11   9    44       ER


 221 Gong, Michelle     7.2.1.6    9    5-6      TR




1724 Lee, Jae Seung     7.2.1.11   9    36, 44   ER




1010 Seok, Yongho       7.2.1.11   10   1        ER




1241 Stephens, Adrian   7.2.1.11   10   5        ER

  31 Asai, Yusuke       7.2.1.11   10   9        TR




 762 Liu, Yong          7.2.1.11   10   9        TR


 913 Santosh Abraham,   7.2.1.11   10   9        ER
     Simone Merlin
1011 Seok, Yongho       7.2.1.11   10   9        ER
1445 Lee, Daewon        7.2.1.11   10   9    ER

1518 SOHN, ILLSOO       7.2.1.11   10   9    ER

1581 Zhu, Chunhui       7.2.1.11   10   9    ER

1726 Lee, Jae Seung     7.2.1.11   10   9    ER




 699 Kneckt, Jarkko     7.2.1.11   10   10   ER

 802 Loc, Peter         7.2.1.12   10   24   TR




  32 Asai, Yusuke       7.2.1.12   10   29   ER




 915 Santosh Abraham,   7.2.1.12   10   30   ER
     Simone Merlin

1582 Zhu, Chunhui       7.1.2.12   10   35   ER

 141 Banerjea, Raja     7.2.1.12   10   37   TR




 222 Gong, Michelle     7.2.1.12   10   37   TR




 763 Liu, Yong          7.2.1.12   10   37   TR

 914 Santosh Abraham,   7.2.1.12   10   37   TR
     Simone Merlin
1012 Seok, Yongho       7.2.1.12   10   37   TR

1243 Stephens, Adrian   7.2.1.12   10   37   TR




1446 Lee, Daewon        7.2.1.12   10   37   TR




1474 Lv, Kaiying        7.2.1.12   10   37   TR




 223 Gong, Michelle     7.2.1.12   10   44   ER




 700 Kneckt, Jarkko     7.2.1.12   10   44   ER

 764 Liu, Yong          7.2.1.12   10   44   TR
1013 Seok, Yongho      7.2.1.12   10   44   TR




1121 Stacey, Robert    7.2.1.12   10   44   ER




1403 Kang, Byeongwoo   7.2.1.12   10   44   TR
1519 SOHN, ILLSOO   7.2.1.12   10   44   TR




1110 Shapira, Nir   7.2.1.12   10   44   TR
1122 Stacey, Robert   7.2.3.0a   10   58    TR




1475 Lv, Kaiying      7.2.3.0a   10   60    ER


1727 Lee, Jae Seung   7.2.3.0a   10   63    ER


1725 Lee, Jae Seung   7.2.1.11   10   1,4   ER
 757 Kneckt, Jarkko     7.2.3.1   11   7    TR




 765 Liu, Yong          7.2.3.1   11   13   TR




1244 Stephens, Adrian   7.2.3.1   11   21   ER


1728 Lee, Jae Seung     7.2.3.1   11   21   ER
 684 Kneckt, Jarkko     7.2.3.1   11   22   ER




 916 Santosh Abraham,   7.2.3.1   11   22   ER
     Simone Merlin

1810 Yee, James         7.2.3.1   11   22   ER




1729 Lee, Jae Seung     7.2.3.5   11   27   ER




1730 Lee, Jae Seung     7.2.3.6   11   46   ER




1731 Lee, Jae Seung     7.2.3.6   11   59   ER


 685 Kneckt, Jarkko     7.2.3.6   11   60   ER




 917 Santosh Abraham,   7.2.3.6   11   60   ER
     Simone Merlin

1732 Lee, Jae Seung     7.2.3.7   12   1    ER




1245 Stephens, Adrian   7.2.3.7   12   3    ER




1733 Lee, Jae Seung     7.2.3.8   12   17   ER
 686 Kneckt, Jarkko     7.2.3.8    12   30   ER




 918 Santosh Abraham,   7.2.3.8    12   30   ER
     Simone Merlin

1734 Lee, Jae Seung     7.2.3.8    12   30   ER


1735 Lee, Jae Seung     7.2.3.9    12   38   ER




1736 Lee, Jae Seung     7.2.3.9    12   40   ER




1737 Lee, Jae Seung     7.2.3.10   12   53   ER




 687 Kneckt, Jarkko     7.2.3.10   13   9    ER




 920 Santosh Abraham,   7.2.3.10   13   9    ER
     Simone Merlin

1738 Lee, Jae Seung     7.2.3.10   13   9    ER


1014 Seok, Yongho       7.3.1.11   13   26   TR

 142 Banerjea, Raja     7.3.1.11   13   29   TR




 701 Kneckt, Jarkko     7.3.1.11   13   29   TR

1583 Zhu, Chunhui       7.3.1.11   13   29   TR
1739 Lee, Jae Seung     7.3.1.11   13   29       ER




 919 Santosh Abraham,   7.3.1.31   13   36       TR
     Simone Merlin




1123 Stacey, Robert     7.3.1.31   13   36       TR


1584 Zhu, Chunhui       7.3.1.31   13   43       ER

1740 Lee, Jae Seung     7.3.1.31   13   38, 49   ER




 101 Au, Edward (Kwok   7.3.1.31   13   41-46    TR
     Shum)




1124 Stacey, Robert     7.3.1.31   14   28       TR
1125 Stacey, Robert     7.3.1.31   14   33   TR




 923 Santosh Abraham,   7.3.1.31   14   34   ER
     Simone Merlin


1015 Seok, Yongho       7.3.1.31   14   34   ER




1404 Kang, Byeongwoo    7.3.1.31   14   34   ER


  33 Asai, Yusuke       7.3.1.31   14   36   ER




 103 Au, Edward (Kwok   7.3.1.31   14   36   ER
     Shum)

1016 Seok, Yongho       7.3.1.31   14   36   ER

1126 Stacey, Robert     7.3.1.31   14   36   ER
1405 Kang, Byeongwoo    7.3.1.31   14   36   ER

1476 Lv, Kaiying        7.3.1.31   14   36   ER




1585 Zhu, Chunhui       7.3.1.31   14   36   ER


1742 Lee, Jae Seung     7.3.1.31   14   36   ER

 104 Au, Edward (Kwok   7.3.1.31   14   39   ER
     Shum)

1127 Stacey, Robert     7.3.1.31   14   39   ER
1743 Lee, Jae Seung     7.3.1.31   14   39   ER

 921 Santosh Abraham,   7.3.1.31   14   40   ER
     Simone Merlin
  34 Asai, Yusuke       7.3.1.31   14   42   ER
1017 Seok, Yongho       7.3.1.32   14   55   TR




1449 Lee, Daewon        7.3.1.32   14   55   TR




1477 Lv, Kaiying        7.3.1.32   14   55   ER




1520 SOHN, ILLSOO       7.3.1.32   14   55   TR




  35 Asai, Yusuke       7.3.1.32   14   57   ER




 105 Au, Edward (Kwok   7.3.1.32   14   57   ER
     Shum)

1587 Zhu, Chunhui       7.3.1.32   14   57   ER


1744 Lee, Jae Seung     7.3.1.32   14   57   ER
1811 Yee, James          7.3.1.3.2   14   57      ER

   1 Aboul-Magd, Osama   7.3.1.32    14   58      ER

1128 Stacey, Robert      7.3.1.32    14   58      ER
 922 Santosh Abraham,    7.3.1.32    14   59      ER
     Simone Merlin
1741 Lee, Jae Seung      7.3.1.31    14   1,4     ER




 102 Au, Edward (Kwok    7.3.1.31    14   33-47   ER
     Shum)




1586 Zhu, Chunhui        7.3.1.31    14   42-46   ER

1129 Stacey, Robert      7.3.1.32    16   5       ER


 924 Santosh Abraham,    7.31.1.32   16   8       ER
     Simone Merlin




1745 Lee, Jae Seung      7.3.1.32    16   4, 32   ER




1746 Lee, Jae Seung      7.3.1.32    17   4, 33   ER




1747 Lee, Jae Seung      7.3.1.32    18   4       ER




1748 Lee, Jae Seung      7.3.1.32    19   4       ER
1130 Stacey, Robert      7.3.1.32   20   4    ER


1749 Lee, Jae Seung      7.3.1.32   20   4    ER




1131 Stacey, Robert      7.3.1.32   20   22   ER




1019 Seok, Yongho        7.3.1.32   20   38   ER




1323 van Zelst, Allert   7.3.1.32   20   38   TR




1406 Kang, Byeongwoo     7.3.1.32   20   38   ER
1020 Seok, Yongho       7.3.1.32   20   41, 43   ER




1407 Kang, Byeongwoo    7.3.1.32   20   41, 43   ER




1750 Lee, Jae Seung     7.3.1.32   21   4        ER




1751 Lee, Jae Seung     7.3.1.32   22   4        ER




 702 Kneckt, Jarkko     7.3.1.32   22   24       ER


 106 Au, Edward (Kwok   7.3.1.32   22   38       TR
     Shum)
 560 Kim, Youhan         7.3.1.32   22   38   TR




  36 Asai, Yusuke        7.3.1.32   22   41   TR




1021 Seok, Yongho        7.3.1.32   22   41   TR




1324 van Zelst, Allert   7.3.1.32   22   41   TR




1408 Kang, Byeongwoo     7.3.1.32   22   41   TR
 884 Pillai, Krishna   7.3.1.32   22   48   TR




1018 Seok, Yongho      7.3.1.32   22   48   ER

1450 Lee, Daewon       7.3.1.32   22   48   ER


1521 SOHN, ILLSOO      7.3.1.32   22   48   ER

 892 Porat, Ron        7.3.1.32   22   49   ER
1132 Stacey, Robert      7.3.1.32   22   56      TR




   2 Aboul-Magd, Osama   7.3.1.32   22   60      ER

  37 Asai, Yusuke        7.3.1.32   22   60      ER




1568 Zhao, Hui           7.3.1.32   22   60      ER




1752 Lee, Jae Seung      7.3.1.32   22   60      ER

1133 Stacey, Robert      7.3.1.32   22   61      ER
1247 Stephens, Adrian    7.3.1.32   22   61      ER
1346 Zhang, Hongyuan     7.3.1.32   22   37-43   TR
1753 Lee, Jae Seung     7.3.1.32   23   4    ER




1134 Stacey, Robert     7.3.1.32   23   43   TR




1246 Stephens, Adrian   7.3.1.32   23   43   ER
1621 Cheong, Minho      7.3.1.32   23   55   ER


1754 Lee, Jae Seung     7.3.1.33   23   65   ER


1248 Stephens, Adrian   7.3.1.33   24   17   ER

 891 Porat, Ron         7.3.1.33   24   23   TR




1022 Seok, Yongho       7.3.1.33   24   31   ER




1756 Lee, Jae Seung     7.3.1.33   27   4    ER
1380 Ecclesine, Peter    7.3.1.34   27   49      ER




 107 Au, Edward (Kwok    7.3.1.34   27   51      ER
     Shum)


1249 Stephens, Adrian    7.3.1.34   27   53      ER

1250 Stephens, Adrian    7.3.1.34   27   60      ER


1023 Seok, Yongho        7.3.1.34   27   65      ER


1757 Lee, Jae Seung      7.3.1.34   27   55,64   ER




1758 Lee, Jae Seung      7.3.1.34   28   9       ER




   3 Aboul-Magd, Osama   7.3.1.34   28   15      ER




  38 Asai, Yusuke        7.3.1.34   28   22      ER




 766 Liu, Yong           7.3.1.34   28   33      TR
1354 Zhao, Shiwei        7.3.1.34   28   33   ER




   4 Aboul-Magd, Osama   7.3.1.34   28   37   ER




  39 Asai, Yusuke        7.3.1.34   28   37   ER

1029 Seok, Yongho        7.3.1.34   28   37   ER




1135 Stacey, Robert      7.3.1.34   28   37   ER
1523 SOHN, ILLSOO        7.3.1.34   28   37   ER




1136 Stacey, Robert      7.3.1.34   28   40   ER
 561 Kim, Youhan    7.3.1.34   28   42   TR




1355 Zhao, Shiwei   7.3.1.34   28   42   ER




 558 Kim, EunSun    7.3.2      28   44   TR
 559 Kim, EunSun    7.3.2      28   44   TR




1030 Seok, Yongho   7.3.2      28   44   TR




1031 Seok, Yongho   7.3.2      28   44   TR




1032 Seok, Yongho   7.3.2      28   44   TR




1033 Seok, Yongho   7.3.2.46   28   44   TR




1453 Lee, Daewon    7.3.2      28   44   TR


1454 Lee, Daewon    7.3.2      28   44   TR


1455 Lee, Daewon    7.3.2      28   44   TR
1524 SOHN, ILLSOO       7.3.2        28   44      TR


1525 SOHN, ILLSOO       7.3.2        28   44      TR




1137 Stacey, Robert     7.3.2.0a     28   52      ER


1759 Lee, Jae Seung     7.3.2.0a     28   52      ER

1478 Lv, Kaiying        7.3.2.0a     28   53      ER

 925 Santosh Abraham,   7.3.2.0a     28   57      ER
     Simone Merlin

1024 Seok, Yongho       7.3.2        28   57      TR

1252 Stephens, Adrian   7.3.2.0a     28   57      TR


1409 Kang, Byeongwoo    7.3.2        28   57      TR
1451 Lee, Daewon        7.3.2        28   57      TR

1760 Lee, Jae Seung     7.3.2.0a     28   57      ER

1025 Seok, Yongho       7.3.2.0a     28   59      TR

1410 Kang, Byeongwoo    7.3.2.0a     28   59      TR
1452 Lee, Daewon        7.3.2.0a     28   59      TR

1028 Seok, Yongho       7.3.1.34     28   21,24,37 ER


1522 SOHN, ILLSOO       7.3.1.34     28   21,24,37 ER


 928 Santosh Abraham,   7.3.2.61.1   29   8       ER
     Simone Merlin
1251 Stephens, Adrian   7.3.2.61.1   29   13   TR




 562 Kim, Youhan        7.3.2.61.1   29   18   TR




 703 Kneckt, Jarkko     7.3.2.61.1   29   19   ER




 224 Gong, Michelle     7.3.2.61.1   29   20   TR




 767 Liu, Yong          7.3.2.61.1   29   20   ER

 926 Santosh Abraham,   7.3.2.61.1   29   20   TR
     Simone Merlin




 927 Santosh Abraham,   7.3.2.61.1   29   20   TR
     Simone Merlin

1036 Seok, Yongho       7.3.2.61.1   29   20   ER




1526 SOHN, ILLSOO       7.3.2.61.1   29   20   ER


1588 Zhu, Chunhui       7.3.2.61.1   29   20   ER
1812 Yee, James          7.3.2.61.1   29   20      ER




1813 Yee, James          7.3.2.61.1   29   20      ER




1034 Seok, Yongho        7.3.2.61.1   29   22      ER


1325 van Zelst, Allert   7.3.2.61.2   29   33      TR




1499 RISON, Mark         7.3.2.61.2   29   36      TR




1035 Seok, Yongho        7.3.2.61.2   29   53      ER


1761 Lee, Jae Seung      7.3.2.61.1   29   14,22   ER




1762 Lee, Jae Seung      7.3.2.61.2   29   28,53   ER




 108 Au, Edward (Kwok    7.3.2.61.2   29   31~50   TR
     Shum)
 109 Au, Edward (Kwok   7.3.2.61.2   29   31~50   TR
     Shum)




1589 Zhu, Chunhui       7.3.2.61.2   30   4       TR


1763 Lee, Jae Seung     7.3.2.61.2   30   4       ER




 216 Erceg, Vinko       7.3.2.61.2   30   5       TR

 688 Kneckt, Jarkko     7.3.2.61.2   30   10      ER


1138 Stacey, Robert     7.3.2.61.2   30   10      TR




1139 Stacey, Robert     7.3.2.61.2   30   10      TR




  40 Asai, Yusuke       7.3.2.61.2   30   14      ER
 806 Loc, Peter       7.3.2.61.2   30   17   TR




1140 Stacey, Robert   7.3.2.61.2   30   18   TR
 110 Au, Edward (Kwok    7.3.2.61.2   30   27   TR
     Shum)




 138 Banerjea, Raja      7.3.2.61.2   30   27   TR




1026 Seok, Yongho        7.3.2.61.2   30   27   TR

1141 Stacey, Robert      7.3.2.61.2   30   27   TR

1253 Stephens, Adrian    7.3.2.61.2   30   27   TR

1326 van Zelst, Allert   7.3.2.61.2   30   27   TR


1411 Kang, Byeongwoo     7.3.2.61.2   30   27   TR
1456 Lee, Daewon         7.3.2.61.2   30   27   TR
1480 Lv, Kaiying        7.3.2.61.2   30   27   TR




 929 Santosh Abraham,   7.3.2.61.2   30   28   TR
     Simone Merlin


 111 Au, Edward (Kwok   7.3.2.61.2   30   33   TR
     Shum)




1142 Stacey, Robert     7.3.2.61.2   30   33   TR
 139 Banerjea, Raja      7.3.2.61.2   30   34      TR




1027 Seok, Yongho        7.3.2.61.2   30   34      TR

1327 van Zelst, Allert   7.3.2.61.2   30   34      TR


1412 Kang, Byeongwoo     7.3.2.61.2   30   34      TR
1457 Lee, Daewon         7.3.2.61.2   30   34      TR

1479 Lv, Kaiying         7.3.2.61.2   30   34      TR




1143 Stacey, Robert      7.3.2.61.2   30   36      TR




 887 Porat, Ron          7.3.2.61.2   30   42      TR




1376 Ecclesine, Peter    7.3.2.62     30   55      TR

 930 Santosh Abraham,    7.3.2.61.2   30   57      TR
     Simone Merlin




1500 RISON, Mark         7.3.2.61.2   30   36,39,57 ER
                                           ,6
1347 Zhang, Hongyuan      7.3.2.61.2     30   42-45   TR




 768 Liu, Yong            7.3.2.61.2     31   3       ER




 704 Kneckt, Jarkko       7.3.2.61.2     31   4       TR




1254 Stephens, Adrian     7.3.2.61.2     31   4       TR




1513   RISON, Mark        7.3.2.61.2     31   11      ER
1501   RISON, Mark        7.3.2.61.2     31   12      ER
1255   Stephens, Adrian   7.3.2.61.2     31   15      ER
  41   Asai, Yusuke       7.3.2.61.1     31   16      ER
                          VHT
                          Capabilities
                          element
                          structure
  42 Asai, Yusuke       7.3.2.61.2 31     20    ER
                        VHT
                        Capabilities
                        Info field




1144 Stacey, Robert     7.3.2.61.3   31   23    TR




1037 Seok, Yongho       7.3.2.61.3   31   33    ER


1145 Stacey, Robert     7.3.61.3     31   45    TR




 548 Hsieh, Jing-Rong   7.3.2.61.2   31   3-7   ER
 549 Hsieh, Jing-Rong   7.3.2.61.2   31   9-12     TR




1764 Lee, Jae Seung     7.3.2.61.3   31   25,33    ER




1765 Lee, Jae Seung     7.3.2.61.3   31   37, 40   ER




1146 Stacey, Robert     7.3.2.61.4   32   3        TR




 140 Banerjea, Raja     7.3.2.61.4   32   5        TR
 689 Kneckt, Jarkko     7.3.2.61.4   32   10        ER


1038 Seok, Yongho       7.3.2.61.4   32   10        ER


 931 Santosh Abraham,   7.3.2.61.4   32   20        ER
     Simone Merlin
1590 Zhu, Chunhui       7.3.2.61.4   32   24        ER


1766 Lee, Jae Seung     7.3.2.61.4   32   10, 14,   ER
                                          24




1767 Lee, Jae Seung     7.3.2.61.4   33   4         ER




1147 Stacey, Robert     7.3.2.61.4   33   9         TR




1814 Yee, James         7.3.2.61.4   33   11        ER




1148 Stacey, Robert     7.3.2.61.4   33   16        ER

1502 RISON, Mark        7.3.2.61.4   33   16        TR
1256 Stephens, Adrian   7.3.2.61.4   33   19   TR




1039 Seok, Yongho       7.3.2.611.4 33    24   ER


1527 SOHN, ILLSOO       7.3.2.611.4 33    24   ER

 112 Au, Edward (Kwok   7.3.2.61.4   33   27   ER
     Shum)




 690 Kneckt, Jarkko     7.3.2.61.4   33   35   ER




1528 SOHN, ILLSOO       7.3.2.62     33   46   TR

1149 Stacey, Robert     7.3.2.62     33   54   TR
1481 Lv, Kaiying        7.3.2.62   33   54      TR




 769 Liu, Yong          7.3.2.62   33   57      ER




1040 Seok, Yongho       7.3.2.62   33   57      TR


1768 Lee, Jae Seung     7.3.2.62   33   50,58   ER




 770 Liu, Yong          7.3.2.62   34   1       ER


1377 Ecclesine, Peter   7.3.2.62   34   1       ER

 143 Banerjea, Raja     7.3.2.62   34   3       ER
1041 Seok, Yongho       7.3.2.62   34   3    ER


1150 Stacey, Robert     7.3.2.62   34   3    ER




1769 Lee, Jae Seung     7.3.2.62   34   7    ER




1151 Stacey, Robert     7.3.2.62   34   22   TR




1257 Stephens, Adrian   7.3.2.62   34   22   TR
 804 Loc, Peter         7.3.2.62   34   28   TR




1258 Stephens, Adrian   7.3.2.62   34   28   TR


 705 Kneckt, Jarkko     7.3.2.62   34   30   TR




 706 Kneckt, Jarkko     7.3.2.62   34   30   TR




 805 Loc, Peter         7.3.2.62   34   34   TR
1260 Stephens, Adrian   7.3.2.63   34   44   TR




1443 Kang, Byeongwoo    7.3.2.63   34   44   TR




1444 Kang, Byeongwoo    7.3.2.63   34   44   TR




1529 SOHN, ILLSOO       7.3.2.63   34   44   TR
1530 SOHN, ILLSOO       7.3.2.63   34   44       TR




1259 Stephens, Adrian   7.3.2.63   34   46       ER


1042 Seok, Yongho       7.3.2.63   34   52       TR




1458 Lee, Daewon        7.3.2.63   34   53       TR

 707 Kneckt, Jarkko     7.3.2.63   34   57       TR

1771 Lee, Jae Seung     7.3.2.63   34   58       ER




 771 Liu, Yong          7.3.2.63   34   63       TR

1152 Stacey, Robert     7.3.2.63   34   63       TR

1770 Lee, Jae Seung     7.3.2.62   34   12, 18   ER
1043 Seok, Yongho       7.4.3      35   3    TR




1044 Seok, Yongho       7.4.11.6   35   3    TR




 691 Kneckt, Jarkko     7.4.11     35   48   ER
1482 Lv, Kaiying        7.4.11     35   48   ER




1264 Stephens, Adrian   7.4.12     36   22   TR
1261 Stephens, Adrian   7.4.12.1   36   27       TR




1045 Seok, Yongho       7.4.12.1   36   43       ER

1413 Kang, Byeongwoo    7.4.12.1   36   43       ER
1772 Lee, Jae Seung     7.4.12.1   36   28, 32   ER




1773 Lee, Jae Seung     7.4.12.2   37   4        ER




 932 Santosh Abraham,   7.4.12.2   37   16       TR
     Simone Merlin




 772 Liu, Yong          7.4.12.3   37   29       TR




1046 Seok, Yongho       7.4.12.3   37   29       TR
1048 Seok, Yongho       7.4.12.3   37   29   TR




1330 Vermani, Sameer    7.4.12.3   37   29   TR




1531 SOHN, ILLSOO       7.4.12.3   37   29   TR


1532 SOHN, ILLSOO       7.4.12.3   37   29   TR




 933 Santosh Abraham,   7.4.12.3   37   30   ER
     Simone Merlin

1153 Stacey, Robert     7.4.12.3   37   31   TR




1154 Stacey, Robert     7.4.12.3   37   31   TR
 225 Gong, Michelle     7.4.12.3   37   32   TR


 226 Gong, Michelle     7.4.12.3   37   32   TR


 227 Gong, Michelle     7.4.12.3   37   32   TR


1262 Stephens, Adrian   7.4.12.3   37   33   TR




1263 Stephens, Adrian   7.4.12.3   37   34   ER


1483 Lv, Kaiying        7.4.12.3   37   38   TR




 807 Loc, Peter         7.4.12.3   37   40   ER




1265 Stephens, Adrian   7.4.12.3   37   40   TR


 710 Kneckt, Jarkko     7.4.12.3   37   41   ER
 711 Kneckt, Jarkko      7.4.12.3   37   41      TR




1381 Ecclesine, Peter    7.4.12.4   37   44      ER




1774 Lee, Jae Seung      7.4.12.4   37   49      ER




   5 Aboul-Magd, Osama   7.4.12.3   37   30-42   ER




1047 Seok, Yongho        7.4.12.3   37   40-42   TR
 808 Loc, Peter         7.4.12.4   37   46-50   TR




1775 Lee, Jae Seung     7.4.12.4   38   4       ER




  43 Asai, Yusuke       7.4a.1     38   30      TR




  44 Asai, Yusuke       7.4a.1     38   30      TR




1267 Stephens, Adrian   7.4a.1     38   34      ER




 773 Liu, Yong          7.4a.1     38   46      TR
  45 Asai, Yusuke       7.4a.1   38   50       TR




 712 Kneckt, Jarkko     7.4a.1   38   50       TR




1266 Stephens, Adrian   7.4a.1   38   50       ER

1591 Zhu, Chunhui       7.4a.1   38   54       ER


1815 Yee, James         7.4a.1   39   24       TR




1776 Lee, Jae Seung     7.4a.1   39   37, 45   ER
1268 Stephens, Adrian   7.4a.3      40   1    ER




  46 Asai, Yusuke       7.4a.3 A-   40   14   ER
                        MPDU
                        contents
 692 Kneckt, Jarkko     7.4a.3      40   14   ER

1777 Lee, Jae Seung     7.4a.3      40   14   ER

 935 Santosh Abraham,   7.4a.3      40   15   ER
     Simone Merlin

 936 Santosh Abraham,   7.4a.3      40   15   ER
     Simone Merlin


1155 Stacey, Robert     7.4a.3      40   15   ER
1712 Cheong, Minho      7.4a.3      40   15   ER


1713 Cheong, Minho      7.4a.3      40   15   ER


 937 Santosh Abraham,   7.4.a.3     40   18   ER
     Simone Merlin
 724 Kneckt, Jarkko     7.4a.3      40   26   ER


 725 Kneckt, Jarkko     7.4a.3      41   12   ER
 726 Kneckt, Jarkko     7.4a.3   41   17   ER




 727 Kneckt, Jarkko     7.4a.3   41   22   ER




 728 Kneckt, Jarkko     7.4a.3   41   27   ER


 163 Chu, Liwen         7.4a.3   41   31   ER




 729 Kneckt, Jarkko     7.4a.3   41   31   ER


 730 Kneckt, Jarkko     7.4a.3   41   37   ER


 161 Chu, Liwen         7.4a.3   41   56   TR




1269 Stephens, Adrian   7.4a.3   41   59   ER
 162 Chu, Liwen         7.4a.3   42   11   TR




1270 Stephens, Adrian   7.4a.3   42   11   TR
1187 Stanley, Dorothy   8.4.3         42   27      TR




1271 Stephens, Adrian   8.4.4         42   42      TR




1503 RISON, Mark        8.4.3;8.4.4   42   29;45   ER


 228 Gong, Michelle     9.1.5         44   15      ER
1337 Wang, Haiguang     9.2.0a       44   41   TR




  47 Asai, Yusuke       9.2.0a       44   45   TR




  48 Asai, Yusuke       9.2.0a       44   46   ER




1272 Stephens, Adrian   9.2.0a       44   46   TR




 774 Liu, Yong          9.2.0b.4.2   44   60   TR

 938 Santosh Abraham,   9.2.0b.4.4   45   1    TR
     Simone Merlin
  50 Asai, Yusuke     9.2.0b.4.4   45   29   ER


1778 Lee, Jae Seung   9.2.0b.4.4   45   29   ER

1484 Lv, Kaiying      9.2.0b.4.4   45   30   TR
 755 Kneckt, Jarkko   9.2.0b.6a   45   33   TR




 155 Carney, Bill     9.2.0b.6a   45   34   TR




1790 Patil, Sandhya   9.2.0b.6a   45   36   TR




1714 Cheong, Minho    9.2.0b.6a   45   38   ER
1273 Stephens, Adrian   9.2.0b.6a   45   39   ER




1791 Patil, Sandhya     9.2.0b.6a   45   41   TR




1274 Stephens, Adrian   9.2.0b.6a   45   44   ER
1485 Lv, Kaiying        9.2.0b.6a   45   49   TR




1792 Patil, Sandhya     9.2.0b.6a   45   49   TR




 708 Kneckt, Jarkko     9.2.0b.6a   45   50   TR




1275 Stephens, Adrian   9.2.0b.6a   45   50   TR
 756 Kneckt, Jarkko   9.2.0b.7   45   53   TR




  51 Asai, Yusuke     9.2.0b.7   45   55   ER




1793 Patil, Sandhya   9.2.0b.7   45   58   TR
1277 Stephens, Adrian   9.2.0b.7   45   61   ER




1276 Stephens, Adrian   9.2.0b.7   45   62   ER




 775 Liu, Yong          9.2.0b.7   45   64   ER
809 Loc, Peter          9.2.0b.7   45   61-65   TR




  7 Aboul-Magd, Osama   9.2.ob.7   45   64-65   TR
 713 Kneckt, Jarkko   9.2.0b.7   46   4    TR




1533 SOHN, ILLSOO     9.2.0b.7   46   9    TR




 776 Liu, Yong        9.2.0b.7   46   10   ER




 777 Liu, Yong        9.2.0b.7   46   10   TR




 709 Kneckt, Jarkko   9.2.0b.7   46   14   TR
714 Kneckt, Jarkko   9.2.0b.7   46   14   TR




715 Kneckt, Jarkko   9.2.0b.7   46   14   TR




716 Kneckt, Jarkko   9.2.0b.7   46   14   TR




717 Kneckt, Jarkko   9.2.0b.7   46   14   TR




718 Kneckt, Jarkko   9.2.0b.7   46   14   ER




719 Kneckt, Jarkko   9.2.0b.7   46   14   TR
 754 Kneckt, Jarkko      9.2.7      46   34     TR




 156 Carney, Bill        9.6        46   36     TR




 939 Santosh Abraham,    9.6.0e.1   46   39     TR
     Simone Merlin




 164 Chu, Liwen          9.6.0e.1   46   44     TR




   6 Aboul-Magd, Osama   7.2.0b.7   46   1-3    TR




1052 Seok, Yongho        9.2.0b.7   46   6~11   TR
 157 Carney, Bill      9.6.0e.6   47   2       TR




1156 Stacey, Robert    9.6.0e.6   47   6       TR




1414 Kang, Byeongwoo   9.6.0e.6   47   7       ER




1489 Lv, Kaiying       9.6.0e.6   47   14      TR




1779 Lee, Jae Seung    9.6.0e.6   47   16,22   ER
1053 Seok, Yongho       9.6.0e.6   47   48~52   ER




 113 Au, Edward (Kwok   9.6.0e.6   48   21      TR
     Shum)




 940 Santosh Abraham,   9.6.0e.6   48   26      ER
     Simone Merlin




 720 Kneckt, Jarkko     9.6.0e.6   48   33      ER

  52 Asai, Yusuke       9.7c       48   53      ER
1504 RISON, Mark   9.7c   48   53   TR
1780 Lee, Jae Seung     9.7d.2   49   6    TR




1794 Patil, Sandhya     9.7d.5   49   22   ER




1382 Ecclesine, Peter   9.7d.6   49   30   ER

 158 Carney, Bill       9.7d.6   49   35   TR




1495 RISON, Mark        9.7d.7   50   4    TR
 778 Liu, Yong          9.7d.7    50   7    TR




 941 Santosh Abraham,   9.7d.7    50   7    TR
     Simone Merlin




1496 RISON, Mark        9.7d.7    50   7    TR

1356 Zhao, Shiwei       9.7.d.7   50   8    TR




 165 Chu, Liwen         9.7d.7    50   15   TR




1357 Zhao, Shiwei       9.7.d.7   50   16   TR
 479 Hart, Brian      9.7e   50   24   TR




 721 Kneckt, Jarkko   9.7e   50   24   TR




1781 Lee, Jae Seung   9.7e   50   24   TR
1509 RISON, Mark        9.7e   50   26   ER




1512 RISON, Mark        9.7e   50   31   ER


1054 Seok, Yongho       9.7e   50   35   ER




1460 Lee, Daewon        9.7e   50   35   ER

1511 RISON, Mark        9.7e   50   35   ER




1278 Stephens, Adrian   9.7e   50   48   ER
1359 Zhao, Shiwei     9.7e      50   49      TR




 229 Gong, Michelle   9.7d.7    50   7-8     TR




1358 Zhao, Shiwei     9.7.d.7   50   17-18   TR




 779 Liu, Yong        9.9.1.2   51   3       ER


  53 Asai, Yusuke     9.9.1.2   51   5       ER




 722 Kneckt, Jarkko   9.9.1.2   51   5       TR




 723 Kneckt, Jarkko   9.9.1.2   51   6       TR
 654 Kneckt, Jarkko   9.9.1.2   51   14   TR




 167 Chu, Liwen       9.9.1.2   51   17   TR




 230 Gong, Michelle   9.9.1.2   51   17   TR




1497 RISON, Mark      9.9.1.2   51   17   TR




 653 Kneckt, Jarkko   9.9.1.2   51   21   TR
 166 Chu, Liwen         9.9.1.2   51   31   TR




 780 Liu, Yong          9.9.1.2   51   31   ER




1279 Stephens, Adrian   9.9.1.2   51   31   TR




1795 Patil, Sandhya     9.9.1.2   51   31   ER
 655 Kneckt, Jarkko     9.9.1.2a   51   41   TR




1280 Stephens, Adrian   9.9.1.2a   51   41   ER


 168 Chu, Liwen         9.9.1.2a   51   44   TR




 943 Santosh Abraham,   9.9.1.2a   51   45   TR
     Simone Merlin
1360 Zhao, Shiwei       9.9.1.2a   51   45   TR




1281 Stephens, Adrian   9.9.1.2a   51   46   TR




1716 Cheong, Minho      9.9.1.2a   51   49   TR




 171 Chu, Liwen         9.9.1.2a   51   51   TR




 232 Gong, Michelle     9.9.1.2a   51   52   TR
1592 Zhu, Chunhui       9.9.1.2a   51   52   TR




1796 Patil, Sandhya     9.9.1.2a   51   52   TR




  54 Asai, Yusuke       9.9.1.2a   51   53   ER
                        Sharing an
                        EDCA TXOP




 942 Santosh Abraham,   9.9.1.2a   51   53   TR
     Simone Merlin




1361 Zhao, Shiwei       9.9.1.2a   51   53   TR




1490 Lv, Kaiying        9.9.1.2a   51   53   TR
  55 Asai, Yusuke       9.9.1.4    51   60      ER




1383 Ecclesine, Peter   9.9.1.4    51   60      ER


 781 Liu, Yong          9.9.1.2a   51   39-53   TR




 231 Gong, Michelle     9.9.1.2a   51   46-47   TR




 114 Au, Edward (Kwok   9.9.1.4    52   5       TR
     Shum)




1492 Lv, Kaiying        9.9.1.4    52   5       TR

 731 Kneckt, Jarkko     9.9.1.4    52   6       ER

1715 Cheong, Minho      9.9.1.4    52   6       TR
  56 Asai, Yusuke        9.9.1.4   52   12   ER




 732 Kneckt, Jarkko      9.9.1.4   52   12   ER


1491 Lv, Kaiying         9.9.1.4   52   17   TR

1493 Lv, Kaiying         9.9.1.4   52   19   TR

 733 Kneckt, Jarkko      9.9.1.4   52   25   ER




 734 Kneckt, Jarkko      9.9.1.4   52   26   ER




 735 Kneckt, Jarkko      9.9.1.4   52   29   ER




1800 Liu, Jianhan        9.9.1.4   52   29   ER




 736 Kneckt, Jarkko      9.9.1.4   52   30   ER




1801 Liu, Jianhan        9.9.1.4   52   30   ER




   8 Aboul-Magd, Osama   9.9.1.4   52   41   TR
737 Kneckt, Jarkko     9.9.1.4   52   49   ER




174 Chu, Liwen         9.9.1.4   52   55   TR

656 Kneckt, Jarkko     9.9.1.4   52   55   TR




944 Santosh Abraham,   9.9.1.4   52   55   TR
    Simone Merlin
 173 Chu, Liwen         9.9.1.4   52   58   TR




1282 Stephens, Adrian   9.9.1.4   52   59   ER


 782 Liu, Yong          9.9.1.4   52   61   TR




 172 Chu, Liwen         9.9.1.4   53   1    TR
1283 Stephens, Adrian   9.9.1.4     53   1    TR




  57 Asai, Yusuke       6.0.0.1     53   11   ER




 551 Hsieh, Jing-Rong   9.9.1.5     53   11   ER


1284 Stephens, Adrian   6.0.0.1     53   11   ER

1340 Zhang, Hongyuan    9.9.1.5     53   11   ER
1415 Kang, Byeongwoo    9.9.1.5     53   11   ER


1494 Lv, Kaiying        9.9.1.5     53   11   ER

1505 RISON, Mark        "6.0.0.1"   53   11   ER

1593 Zhu, Chunhui       6.0.0.1     53   11   ER

1717 Cheong, Minho      9.9.1.5     53   11   ER

1782 Lee, Jae Seung     6.0.0.1     53   11   ER

1362 Zhao, Shiwei       9.9.1.5     53   12   ER
1384 Ecclesine, Peter   6.0.0.1   53   14   ER




1285 Stephens, Adrian   6.0.0.1   53   48   TR




1594 Zhu, Chunhui       6.0.0.1   53   48   TR




1718 Cheong, Minho      9.9.1.5   53   58   ER

1595 Zhu, Chunhui       6.0.0.1   53   60   TR




1286 Stephens, Adrian   6.0.0.1   53   61   TR
1596 Zhu, Chunhui   6.0.0.1   53   63   TR




 175 Chu, Liwen     9.15      54   1    TR




 159 Carney, Bill   9.15      54   8    TR




 176 Chu, Liwen     9.18.3    54   32   ER
 945 Santosh Abraham,    9.18.3   54   32   TR
     Simone Merlin




1288 Stephens, Adrian    9.18.3   54   33   TR




   9 Aboul-Magd, Osama   9.18.3   54   38   TR
  58 Asai, Yusuke       9.18.3   54   38   TR




1287 Stephens, Adrian   9.18.3   54   38   ER


1056 Seok, Yongho       9.18.3   54   41   ER




1461 Lee, Daewon        9.18.3   54   49   ER

  59 Asai, Yusuke       9.18.3   54   50   ER




1055 Seok, Yongho       9.18.3   54   50   ER

1363 Zhao, Shiwei       9.18.3   54   50   ER

1597 Zhu, Chunhui       9.18.3   54   50   ER

1783 Lee, Jae Seung     9.18.3   54   50   ER
 946 Santosh Abraham,   9.18.3   54   55   ER
     Simone Merlin
1289 Stephens, Adrian    9.18.3   54   55   TR




1057 Seok, Yongho        9.18.3   54   56   ER
1719 Cheong, Minho       9.18.3   54   60   ER


  10 Aboul-Magd, Osama   9.18.3   54   64   ER

  11 Aboul-Magd, Osama   9.18.3   54   64   TR




1364 Zhao, Shiwei        9.18.3   54   64   TR


1290 Stephens, Adrian    9.18.3   55   2    TR


1291 Stephens, Adrian    9.18.3   55   9    ER




1720 Cheong, Minho       9.18.3   55   14   TR


1058 Seok, Yongho        9.18.3   55   17   ER




1292 Stephens, Adrian    9.18.3   55   17   ER
  12 Aboul-Magd, Osama   9.18.3   55   20   ER

 115 Au, Edward (Kwok    9.18.3   55   20   ER
     Shum)
1062 Seok, Yongho        9.18.3   55   20   ER
1537 SOHN, ILLSOO        9.18.3   55   20   ER
1784 Lee, Jae Seung      9.18.3   55   20   ER
 116 Au, Edward (Kwok    9.18.3   55   23   ER
     Shum)


1060 Seok, Yongho        9.18.3   55   23   ER

1535 SOHN, ILLSOO        9.18.3   55   23   ER

1064 Seok, Yongho        9.18.3   55   38   TR

1073 Seok, Yongho        9.18.3   55   43   TR




1294 Stephens, Adrian    9.18.3   55   43   ER

1365 Zhao, Shiwei        9.18.3   55   43   TR
1462 Lee, Daewon        9.18.3   55   43   TR




1293 Stephens, Adrian   9.18.3   55   44   ER

1366 Zhao, Shiwei       9.18.3   55   44   ER

1061 Seok, Yongho       9.18.3   55   47   ER

1295 Stephens, Adrian   9.18.3   55   47   ER
1536 SOHN, ILLSOO       9.18.3   55   47   ER

1059 Seok, Yongho       9.18.3   55   52   ER

1463 Lee, Daewon        9.18.3   55   52   ER

1534 SOHN, ILLSOO       9.18.3   55   52   ER

1063 Seok, Yongho       9.18.3   55   54   TR

1296 Stephens, Adrian   9.18.3   55   64   ER




1108 Shapira, Nir       9.18.3   56   1    TR
1109 Shapira, Nir       9.18.3   56   1   TR




1297 Stephens, Adrian   9.18.3   56   1   ER

1114 Shapira, Nir       9.18.3   56   2   TR




1348 Zhang, Hongyuan    9.18.3   56   2   TR
1065 Seok, Yongho       9.18.3   56   7    ER


1538 SOHN, ILLSOO       9.18.3   56   7    ER




1598 Zhu, Chunhui       9.18.3   56   7    ER

 947 Santosh Abraham,   9.18.3   56   14   ER
     Simone Merlin




 886 Porat, Ron         9.18.3   56   15   TR




1367 Zhao, Shiwei       9.18.3   56   15   TR




1368 Zhao, Shiwei       9.18.3   56   21   TR


1066 Seok, Yongho       9.18.3   56   24   ER

1067 Seok, Yongho       9.18.3   56   24   ER
1107 Shapira, Nir       9.18.3   56   24   TR




1599 Zhu, Chunhui       9.18.3   56   24   ER

1369 Zhao, Shiwei       9.18.3   56   25   ER

1071 Seok, Yongho       9.18.3   56   26   ER


 117 Au, Edward (Kwok   9.18.3   56   28   ER
     Shum)


1068 Seok, Yongho       9.18.3   56   28   ER
1072 Seok, Yongho   9.18.3   56   28   TR




1074 Seok, Yongho   9.18.3   56   28   TR
1416 Kang, Byeongwoo    9.18.3   56   28   ER




1464 Lee, Daewon        9.18.3   56   28   TR




1465 Lee, Daewon        9.18.3   56   28   TR




1069 Seok, Yongho       9.18.3   56   30   ER




  60 Asai, Yusuke       9.18.3   56   32   ER




1070 Seok, Yongho       9.18.3   56   32   ER

 948 Santosh Abraham,   9.18.3   56   58   TR
     Simone Merlin
  61 Asai, Yusuke        9.21     56   65      ER




1386 Ecclesine, Peter    9.21     56   65      ER

  13 Aboul-Magd, Osama   9.18.3   56   1-3     TR




1785 Lee, Jae Seung      9.18.3   56   6, 24   ER
 803 Loc, Peter          9.21.5   57   1       TR
949 Santosh Abraham,   9.21.5   57   1   TR
    Simone Merlin




950 Santosh Abraham,   9.21.5   57   1   TR
    Simone Merlin
1079 Seok, Yongho   9.21.5   57   1   TR
1080 Seok, Yongho      9.21.5   57   1   TR




1423 Kang, Byeongwoo   9.21.5   57   1   TR
1539 SOHN, ILLSOO   9.21.5   57   1   TR




1540 SOHN, ILLSOO   9.21.5   57   1   TR




 160 Carney, Bill   9.21.5   57   2   TR
  62 Asai, Yusuke       9.21.5   57   5    ER




  64 Asai, Yusuke       9.21.5   57   13   ER


 170 Chu, Liwen         9.21.5   57   13   TR




1157 Stacey, Robert     9.21.5   57   13   ER

1158 Stacey, Robert     9.21.5   57   13   TR




1298 Stephens, Adrian   9.21.5   57   13   ER




  65 Asai, Yusuke       9.21.5   57   16   ER


1159 Stacey, Robert     9.21.5   57   16   ER

1190 Stephens, Adrian   9.21.5   57   35   ER
  63 Asai, Yusuke       9.21.5   57   36   ER
 952 Santosh Abraham,   9.21.5   57   42   TR
     Simone Merlin




1417 Kang, Byeongwoo    9.21.5   57   42   ER

1466 Lee, Daewon        9.21.5   57   42   TR




1075 Seok, Yongho       9.21.5   57   46   ER




1418 Kang, Byeongwoo    9.21.5   57   46   ER
 951 Santosh Abraham,   9.21.5   57   49       TR
     Simone Merlin




1160 Stacey, Robert     9.21.5   57   49       TR


1371 Zhao, Shiwei       9.21.5   57   42, 46   ER




 783 Liu, Yong          9.21.5   57   42-43    ER




 784 Liu, Yong          9.21.5   57   42-53    TR
1370 Zhao, Shiwei       9.21.5   57   43, 46   ER

 785 Liu, Yong          9.21.5   58   2        TR




1111 Shapira, Nir       9.21.5   58   12       TR




1112 Shapira, Nir       9.21.5   58   12       TR




 955 Santosh Abraham,   9.21.5   58   19       ER
     Simone Merlin
  14 Aboul-Magd, Osama   9.21.5   58   20   ER

  66 Asai, Yusuke        9.21.5   58   20   ER


 786 Liu, Yong           9.21.5   58   20   ER
1076 Seok, Yongho        9.21.5   58   20   TR

1191 Stephens, Adrian    9.21.5   58   20   ER
1419 Kang, Byeongwoo     9.21.5   58   20   TR

1486 Lv, Kaiying         9.21.5   58   20   TR




1514 RISON, Mark         9.21.5   58   20   TR


1600 Zhu, Chunhui        9.21.5   58   20   TR


1786 Lee, Jae Seung      9.21.5   58   20   ER


1161 Stacey, Robert      9.21.5   58   23   ER

 953 Santosh Abraham,    9.21.5   58   41   ER
     Simone Merlin




1162 Stacey, Robert      9.21.5   58   41   ER




 787 Liu, Yong           9.21.5   58   42   ER

1077 Seok, Yongho        9.21.5   58   42   TR
1420 Kang, Byeongwoo    9.21.5   58   42   TR


 788 Liu, Yong          9.21.5   58   43   ER

1192 Stephens, Adrian   9.21.5   58   43   TR


1601 Zhu, Chunhui       9.21.5   58   43   TR


 954 Santosh Abraham,   9.21.5   58   45   ER
     Simone Merlin




 957 Santosh Abraham,   9.21.5   58   45   TR
     Simone Merlin




1078 Seok, Yongho       9.21.5   58   45   ER


1421 Kang, Byeongwoo    9.21.5   58   45   ER
 958 Santosh Abraham,   9.21.5   58   49   TR
     Simone Merlin




 789 Liu, Yong          9.21.5   58   58   ER


1487 Lv, Kaiying        9.21.5   58   58   TR




 956 Santosh Abraham,   9.21.5   58   59   ER
     Simone Merlin
1372 Zhao, Shiwei       9.21.5   58   59   ER


1602 Zhu, Chunhui       9.21.5   58   64   TR
1787 Lee, Jae Seung     9.21.5   58   59 ~ 62 ER


  67 Asai, Yusuke       9.21.5   58   59-62   ER




1163 Stacey, Robert     9.21.5   59   1       TR




1193 Stephens, Adrian   9.21.5   59   1       ER

1603 Zhu, Chunhui       9.21.5   59   1       TR

1604 Zhu, Chunhui       9.21.5   59   6       TR




 790 Liu, Yong          9.21.5   59   8       ER
959 Santosh Abraham,   9.21.5   59   8   TR
    Simone Merlin
960 Santosh Abraham,   9.21.5   59   8   TR
    Simone Merlin
 961 Santosh Abraham,   9.21.5   59   8   TR
     Simone Merlin




 144 Banerjea, Raja     9.21.5   59   9   ER


1081 Seok, Yongho       9.21.5   59   9   TR
1422 Kang, Byeongwoo    9.21.5   59   9    TR




1541 SOHN, ILLSOO       9.21.5   59   9    TR




1605 Zhu, Chunhui       9.21.5   59   9    TR

1194 Stephens, Adrian   9.21.5   59   14   TR




  68 Asai, Yusuke       9.21.6   59   20   ER


1195 Stephens, Adrian   9.21.6   59   20   ER

1488 Lv, Kaiying        9.21.6   59   20   TR




1506 RISON, Mark        9.21.6   59   20   ER
1082 Seok, Yongho       9.21.6   59   29   ER




1424 Kang, Byeongwoo    9.21.6   59   29   ER

1542 SOHN, ILLSOO       9.21.6   59   29   ER
1084 Seok, Yongho       9.21.6   59   31      ER




1196 Stephens, Adrian   9.21.6   59   31      TR




1543 SOHN, ILLSOO       9.21.6   59   31      ER




 234 Grandhi, Sudheer   9.21.6   59   36      ER




1606 Zhu, Chunhui       9.21.6   59   36      ER




1083 Seok, Yongho       9.21.6   59   36~40   ER
1425 Kang, Byeongwoo    9.21.6      59   36~40   ER


 962 Santosh Abraham,   9.21.6      59   36-40   ER
     Simone Merlin
1387 Ecclesine, Peter   10.4.7      60   22      ER




1307 Stephens, Adrian   10.4        60           TR


1308 Stephens, Adrian   10.4        60           TR


 657 Kneckt, Jarkko     11.2.1.4a   61   13      ER




 659 Kneckt, Jarkko     11.2.1.4a   61   13      TR




 753 Kneckt, Jarkko     11.2.1.4a   61   13      TR


 658 Kneckt, Jarkko     11.2.1.4a   61   16      TR
 800 Loc, Peter         11.2.1.4a   61   16   TR




1197 Stephens, Adrian   11.2.1.4a   61   16   ER
1199 Stephens, Adrian   11.2.1.4a   61   17   TR




1198 Stephens, Adrian   11.2.1.4a   61   18   ER




1607 Zhu, Chunhui       11.2.1.4a   61   20   ER

 963 Santosh Abraham,   11.2.1.4a   61   30   ER
     Simone Merlin
 792 Liu, Yong          11.2.1.4a   61   31   ER




1200 Stephens, Adrian   11.2.1.4a   61   36   ER




1201 Stephens, Adrian   112.1.4a    61   40   ER

1373 Zhao, Shiwei       11.2.1.4a   61   43   ER
1608 Zhu, Chunhui        11.2.1.4a    61   43   ER




  15 Aboul-Magd, Osama   11.2.1.4b    61   45   ER

 553 Hsieh, Jing-Rong    11.2.1.4b    61   45   ER




 799 Loc, Peter          11.2.1.4b    61   45   ER

 965 Santosh Abraham,    11.2.1.4b    61   48   TR
     Simone Merlin




 554 Hsieh, Jing-Rong    11.2.1.4b    61   49   ER




 793 Liu, Yong           11.2.1.4b    61   49   TR




1085 Seok, Yongho        11.2.1.4b    61   49   TR


1426 Kang, Byeongwoo     11..2.1.4b   61   49   TR


1788 Lee, Jae Seung      11.2.1.4b    61   49   TR
 964 Santosh Abraham,   11.2.1.4b   61   56   TR
     Simone Merlin




1202 Stephens, Adrian   11.2.1.4b   61   56   TR




 119 Au, Edward (Kwok   11.2.1.4b   61   57   ER
     Shum)
 555 Hsieh, Jing-Rong   11.2.1.4b   61   57   ER




1552 Sun, Bo            11.2.14b    61   57   ER
 660 Kneckt, Jarkko     11.2.1.4b   61   61   TR
1203 Stephens, Adrian   11.2.1.4b   61   61      TR




 738 Kneckt, Jarkko     11.2.1.4b   61   65      ER

 556 Hsieh, Jing-Rong   11.2.1.4a   61   13-62   ER
552 Hsieh, Jing-Rong   11.2.1.4a   61   16-17   ER




118 Au, Edward (Kwok   11.2.1.4a   61   16-20   TR
    Shum)




791 Liu, Yong          11.2.1.4a   61   18-19   ER
1374 Zhao, Shiwei       11.2.1.4a   61   43, 52   TR




 794 Liu, Yong          11.2.1.4b   61   55-56    TR




 795 Liu, Yong          11.2.1.4b   61   61-62    TR




 169 Chu, Liwen         11.20.1     62   6        TR




1205 Stephens, Adrian   11.20.1     62   6        TR
 182 Erceg, Vinko       11.20.1   62   17   TR




1204 Stephens, Adrian   11.20.1   62   17   TR




  70 Asai, Yusuke       11.20.1   62   21   ER




1206 Stephens, Adrian   11.20.1   62   29   ER

1207 Stephens, Adrian   11.20.1   62   39   TR




1508 RISON, Mark        11.20.1   62   39   ER




 661 Kneckt, Jarkko     11.20.2   62   45   TR


 739 Kneckt, Jarkko     11.20.2   62   45   ER
740 Kneckt, Jarkko   11.20.2   62   49      ER




741 Kneckt, Jarkko   11.20.2   62   55      ER




742 Kneckt, Jarkko   11.20.2   62   63      ER




796 Liu, Yong        11.20.1   62   10-11   TR




 69 Asai, Yusuke     11.20.1   62   17-22   TR




743 Kneckt, Jarkko   11.20.2   63   17      ER




744 Kneckt, Jarkko   11.20.2   63   18      ER




745 Kneckt, Jarkko   11.20.2   63   24      ER
 184 Erceg, Vinko     11.20.2   63   27   ER




 186 Erceg, Vinko     11.20.2   63   27   TR




 185 Erceg, Vinko     11.20.2   63   37   TR




 746 Kneckt, Jarkko   11.20.2   63   40   ER




1797 Patil, Sandhya   11.20.2   63   49   TR




 187 Erceg, Vinko     11.20.3   63   64   TR
 183 Erceg, Vinko       11.20.2    63    19-24   TR




 810 Loc, Peter         11.20.2    63    39-42   TR




  71 Asai, Yusuke       12.3.5.10.2 64   19      ER




1208 Stephens, Adrian   12.3.5.10.2 64   19      TR




1553 Sun, Bo            12.3.5.10.2 64   20      ER

 248 Hart, Brian        12.3.5.10.2 64   22      ER
 249 Hart, Brian        12.3.5.10.2 64   36   TR




 250 Hart, Brian        12.3.5.10.2 64   49   ER

 251 Hart, Brian        12.3.5.10.2 64   49   ER
 966 Santosh Abraham,   7.1.3.5a    6    1    TR
     Simone Merlin




 252 Hart, Brian        12.3.5.10.2 65   8    ER




1086 Seok, Yongho       12.3.5.10.2 65   15   ER


1467 Lee, Daewon        12.3.5.10.2 65   15   ER

1545 SOHN, ILLSOO       12.3.5.10.2 65   15   ER

 253 Hart, Brian        12.3.5.10.3 65   26   TR




 188 Erceg, Vinko       12.3.5.10.3 65   35   TR

 189 Erceg, Vinko       12.3.5.10.3 65   45   TR

 190 Erceg, Vinko       12.3.5.10.3 65   50   TR
 747 Kneckt, Jarkko     12.3.5.10.3 65   50   ER

1375 Zhao, Shiwei       12.3.5.10.3 65   50   TR

 254 Hart, Brian        17.2.2      66   18   TR




 748 Kneckt, Jarkko     17.2.2      66   27   ER




1087 Seok, Yongho       17.2.2      66   27   ER




1388 Ecclesine, Peter   17.2.2.13   66   27   ER




 120 Au, Edward (Kwok   17.2.2      66   29   ER
     Shum)
 749 Kneckt, Jarkko     17.2.2.13   66   30   ER

 255 Hart, Brian        17.2.2      66   34   TR
1554 Sun, Bo            17.2.2.13   66   34      ER


 256 Hart, Brian        17.2.2.13   66   38      TR




 121 Au, Edward (Kwok   17.2.2.14   66   42      ER
     Shum)
 750 Kneckt, Jarkko     17.2.2.14   66   42      ER

 797 Liu, Yong          17.2.2.14   66   47-48   ER




1389 Ecclesine, Peter   17.2.3.6    67   20      ER


 257 Hart, Brian        17.3.2.1    67   60      TR




 258 Hart, Brian        17.3.5.4    68   27      ER

1209 Stephens, Adrian   17.3.5.4    68   27      TR




1390 Ecclesine, Peter   17.3.5.4    68   27      ER

1609 Zhu, Chunhui       17.3.5.4    68   33      ER
191 Erceg, Vinko     17.3.5.4   68   40   TR




662 Kneckt, Jarkko   17.3.5.4   68   40   TR




563 Kim, Youhan      17.3.5.4   68   44   TR




259 Hart, Brian      17.3.5.4   69   1    TR




 72 Asai, Yusuke     22         70   1    ER
  73 Asai, Yusuke      22.1.1   70   19   ER




1088 Seok, Yongho      22.1.1   70   19   ER




1427 Kang, Byeongwoo   22.1.1   70   19   ER




 260 Hart, Brian       22.1.1   70   22   ER




 261 Hart, Brian       22.1.1   70   23   ER




 262 Hart, Brian       22.1.1   70   27   ER

 816 Perahia, Eldad    22.1.1   70   27   ER
 868 Pillai, Krishna    22.1.1   70   34   TR




  74 Asai, Yusuke       22.1.1   70   38   TR




  75 Asai, Yusuke       22.2.2   71   9    ER




 197 Erceg, Vinko       2.22.2   72   1    ER




 264 Hart, Brian        22.2.2   72   15   ER
 235 Grandhi, Sudheer   22.2.2   72   18   ER




 265 Hart, Brian        22.2.2   72   18   ER




1089 Seok, Yongho       22.2.2   72   18   ER

1210 Stephens, Adrian   22.2.2   72   18   ER

1428 Kang, Byeongwoo    22.2.2   72   18   ER

1610 Zhu, Chunhui       22.2.2   72   18   ER
 564 Kim, Youhan    22.2.2   72   19   ER




 266 Hart, Brian    22.2.2   72   23   TR


 565 Kim, Youhan    22.2.2   72   26   TR




 267 Hart, Brian    22.2.2   72   34   TR


 195 Erceg, Vinko   2.22.2   72   40   TR


 268 Hart, Brian    22.2.2   72   42   ER

 269 Hart, Brian    22.2.2   72   42   ER

 271 Hart, Brian    22.2.2   72   44   TR


 566 Kim, Youhan    22.2.2   72   46   ER




 567 Kim, Youhan    22.2.2   72   46   TR




1090 Seok, Yongho   22.2.2   72   46   ER
1211 Stephens, Adrian   22.2.2   72   46       TR

1429 Kang, Byeongwoo    22.2.2   72   46       ER
1611 Zhu, Chunhui       22.2.2   72   46       ER


 270 Hart, Brian        22.2.2   72   49       ER




 272 Hart, Brian        22.2.2   72   58       TR




 192 Erceg, Vinko       22.2.2   72   113-19   ER

 817 Perahia, Eldad     22.2.2   72   13-18    ER

 818 Perahia, Eldad     22.2.2   72   42-46    ER

 274 Hart, Brian        22.2.2   73   1        TR




 967 Santosh Abraham,   22.2.2   73   1        TR
     Simone Merlin




 273 Hart, Brian        22.2.2   73   5        TR


 194 Erceg, Vinko       2.22.2   73   11       TR
 819 Perahia, Eldad   22.2.2   73   11      ER




1555 Sun, Bo          22.2.2   73   11      TR




 275 Hart, Brian      22.2.2   73   14      TR




 811 Loc, Peter       22.2.2   73   22-30   TR




 568 Kim, Youhan      22.2.2   74   7       ER
1091 Seok, Yongho       22.2.2   74   7    ER

1092 Seok, Yongho       22.2.2   74   7    ER


1212 Stephens, Adrian   22.2.2   74   7    TR




1430 Kang, Byeongwoo    22.2.2   74   7    ER

1431 Kang, Byeongwoo    22.2.2   74   7    ER


 276 Hart, Brian        22.2.2   74   17   TR




 569 Kim, Youhan        22.2.2   74   18   ER




 570 Kim, Youhan        22.2.2   74   21   ER


 145 Banerjea, Raja     22.2.2   74   26   TR




 277 Hart, Brian        22.2.2   74   26   TR
1612 Zhu, Chunhui       22.2.2   74   26   TR




 571 Kim, Youhan        22.2.2   74   27   ER




 572 Kim, Youhan        22.2.2   74   27   TR




 573 Kim, Youhan        22.2.2   74   28   TR




 574 Kim, Youhan        22.2.2   74   32   ER


1213 Stephens, Adrian   22.2.2   74   32   TR

1214 Stephens, Adrian   22.2.2   74   34   TR

 575 Kim, Youhan        22.2.2   74   36   ER


 576 Kim, Youhan        22.2.2   74   39   ER
 146 Banerjea, Raja   22.2.2   74   41      TR




 193 Erceg, Vinko     2.22.2   74   41      TR

 577 Kim, Youhan      22.2.2   74   41      ER


 578 Kim, Youhan      22.2.2   74   41      TR




1613 Zhu, Chunhui     22.2.2   74   41      TR




1093 Seok, Yongho     22.2.2   74   31~33   ER

 888 Porat, Ron       22.2.2   75   31      ER
1614 Zhu, Chunhui     22.2.2   75   33      ER

 278 Hart, Brian      22.2.2   75   35      TR
 147 Banerjea, Raja     22.2.2   75   52      TR


 579 Kim, Youhan        22.2.2   75   52      TR




1216 Stephens, Adrian   22.2.2   75   52      TR
1615 Zhu, Chunhui       22.2.2   75   52      ER


1094 Seok, Yongho       22.2.2   75   1~6     ER


1095 Seok, Yongho       22.2.2   75   14~16   ER


1096 Seok, Yongho       22.2.2   75   29~33   ER

 820 Perahia, Eldad     22.2.2   75   29-33   ER

1097 Seok, Yongho       22.2.2   75   35~39   ER


 969 Santosh Abraham,   22.2.2   76   1       ER
     Simone Merlin




 869 Pillai, Krishna    22.2.2   76   5       ER




1622 Cheong, Minho      22.2.2   76   5       ER

 580 Kim, Youhan        22.2.2   76   6       ER
 196 Erceg, Vinko      2.22.2   76   10   ER

1623 Cheong, Minho     22.2.2   76   10   ER


 581 Kim, Youhan       22.2.2   76   11   ER




 279 Hart, Brian       22.2.2   76   13   TR




 280 Hart, Brian       22.2.2   76   13   TR




1624 Cheong, Minho     22.2.2   76   14   ER

 870 Pillai, Krishna   22.2.2   76   15   ER




 582 Kim, Youhan       22.2.2   76   16   ER
 236 Grandhi, Sudheer   22.2.2      76    18   ER




1798 Patil, Sandhya     22.2.1       76   18   ER
                        Introduction




 583 Kim, Youhan        22.2.2      76    20   ER


 584 Kim, Youhan        22.2.2      76    20   ER




1625 Cheong, Minho      22.2.2      76    20   ER

 968 Santosh Abraham,   22.2.2      76    26   ER
     Simone Merlin

 585 Kim, Youhan        22.2.2      76    27   ER


 586 Kim, Youhan        22.2.2      76    29   ER




 587 Kim, Youhan        22.2.2      76    29   TR
1626 Cheong, Minho      22.2.2   76   29   ER

 148 Banerjea, Raja     22.2.2   76   35   TR

 281 Hart, Brian        22.2.2   76   35   TR

 588 Kim, Youhan        22.2.2   76   35   TR




1217 Stephens, Adrian   22.2.2   76   47   ER

 282 Hart, Brian        22.2.2   76   49   ER

 283 Hart, Brian        22.2.2   76   51   TR
 589 Kim, Youhan       22.2.2   76   51      ER


 871 Pillai, Krishna   22.2.2   76   51      ER




1498 RISON, Mark       22.2.2   76   51      ER

1556 Sun, Bo           22.2.2   76   52      ER




1616 Zhu, Chunhui      22.2.2   76   1-64    ER




 821 Perahia, Eldad    22.2.2   76   1-6     ER




1098 Seok, Yongho      22.2.2   76   1~6     ER


1100 Seok, Yongho      22.2.2   76   13~16   ER

 822 Perahia, Eldad    22.2.2   76   13-16   ER




1101 Seok, Yongho      22.2.2   76   17~20   ER

 823 Perahia, Eldad    22.2.2   76   17-20   ER




1102 Seok, Yongho      22.2.2   76   26~29   ER

 824 Perahia, Eldad    22.2.2   76   26-29   ER
 825 Perahia, Eldad   22.2.2   76   47-51   ER


1099 Seok, Yongho     22.2.2   76   7~11    ER

 284 Hart, Brian      22.2.2   77   1       TR




 290 Hart, Brian      22.2.2   77   1       TR


 285 Hart, Brian      22.2.2   77   17      TR


 286 Hart, Brian      22.2.2   77   26      TR




 287 Hart, Brian      22.2.2   77   38      ER
 288 Hart, Brian      22.2.2   77   48      ER
 289 Hart, Brian      22.2.2   77   48      TR
 970 Santosh Abraham,   22.2.2   77   49      TR
     Simone Merlin




 590 Kim, Youhan        22.2.2   77   52      TR




 591 Kim, Youhan        22.2.2   77   52      TR




1103 Seok, Yongho       22.2.2   77   47~51   ER
 557 Hsieh, Jing-Rong   22.2.2   77   47-51   ER




1104 Seok, Yongho       22.2.3   78   4       TR
1617 Zhu, Chunhui       22.2.3   78   4       TR

 149 Banerjea, Raja     22.2.3   78   5       TR


1218 Stephens, Adrian   22.2.3   78   5       TR
1433 Kang, Byeongwoo    22.2.3   78   5       ER
 291 Hart, Brian        22.2.4   78   13      TR




1105 Seok, Yongho       22.2.4   78   13      ER
292 Hart, Brian    22.2.4   78   14   ER




293 Hart, Brian    22.2.5   78   43   ER




295 Hart, Brian    22.3.2   79   8    TR




977 Seok, Yongho   22.3.2   79   10   ER
1219 Stephens, Adrian   22.3.2   79   12   TR




1569 Zhao, Hui          22.3.2   79   14   ER




1106 Seok, Yongho       22.3.2   79   19   ER


 974 Seok, Yongho       22.3.2   79   21   ER


 975 Seok, Yongho       22.3.2   79   24   ER
 294 Hart, Brian       22.3.2   79   34   ER




 826 Perahia, Eldad    22.3.2   79   35   ER




 976 Seok, Yongho      22.3.2   79   40   ER




1434 Kang, Byeongwoo   22.3.2   79   40   ER




1802 Liu, Jianhan      22.3.2   79   40   ER
 296 Hart, Brian     22.3.2   79   42   TR




 297 Hart, Brian     22.3.2   79   42   TR


 198 Erceg, Vinko    22.3.3   79   45   TR




 298 Hart, Brian     22.3.3   79   47   TR




1627 Cheong, Minho   22.3.3   79   60   TR




  76 Asai, Yusuke    22.3.3   79   62   ER




 299 Hart, Brian     22.3.3   79   64   TR
 978 Seok, Yongho      22.3.3   80   1      ER


1435 Kang, Byeongwoo   22.3.3   80   1      ER


1468 Lee, Daewon       22.3.3   80   1      ER


1546 SOHN, ILLSOO      22.3.3   80   1      ER


 302 Hart, Brian       22.3.3   80   7      TR


 300 Hart, Brian       22.3.3   80   14     ER


 301 Hart, Brian       22.3.3   80   32     TR




 303 Hart, Brian       22.3.3   80   35     TR




 304 Hart, Brian       22.3.3   80   65     TR

 827 Perahia, Eldad    22.3.3   80   7-26   ER
 828 Perahia, Eldad    22.3.3   80   45-62   ER




 305 Hart, Brian       22.3.3   81   6       TR


 306 Hart, Brian       22.3.3   81   39      TR




 307 Hart, Brian       22.3.3   81   49      ER


 308 Hart, Brian       22.3.3   82   21      ER
 592 Kim, Youhan       22.3.3   82   21      TR




1331 Vermani, Sameer   22.3.3   82   22      ER




 309 Hart, Brian       22.3.3   82   25      ER
 829 Perahia, Eldad    22.3.3   82   25      ER




 830 Perahia, Eldad    22.3.3   82   25      ER




 199 Erceg, Vinko      22.3.3   82   29      TR




 310 Hart, Brian       22.3.3   82   29      ER
 831 Perahia, Eldad   22.3.3     82   31   ER




 314 Hart, Brian      22.3.4.2   82   42   ER




 311 Hart, Brian      22.3.4.2   82   45   ER


 312 Hart, Brian      22.3.4.2   82   46   TR




 313 Hart, Brian      22.3.4.2   82   46   ER




1803 Liu, Jianhan     22.3.4.2   82   48   ER

 979 Seok, Yongho     22.3.4.2   82   50   ER

1547 SOHN, ILLSOO     22.3.4.2   82   50   ER
  77 Asai, Yusuke          22.3.4.2   82   51    ER




 315 Hart, Brian           22.3.4.2   82   51    ER




 893 Pulikkoonattu, Rethna 22.3.4.2   82   56    ER

 316 Hart, Brian           22.3.4.3   82   65    ER




 980 Seok, Yongho          22.3.4.3   82   62~   ER

1548 SOHN, ILLSOO          22.3.4.3   82   62~   ER
 317 Hart, Brian           22.3.4.3   83   1     ER
  78 Asai, Yusuke          22.3.4.3   83   2     ER




 319 Hart, Brian           22.3.4.3   83   2     ER




 320 Hart, Brian           22.3.4.3   83   2     TR




 593 Kim, Youhan           22.3.4.3   83   2     ER
 832 Perahia, Eldad     22.3.4.3   83   2    ER




1164 Stacey, Robert     22.3.4.3   83   2    ER
1220 Stephens, Adrian   22.3.4.3   83   2    ER
 318 Hart, Brian        22.3.4.3   83   3    ER


 321 Hart, Brian        22.3.4.3   83   9    ER
  79 Asai, Yusuke       22.3.4.4   83   23   ER




1221 Stephens, Adrian   22.3.4.4   83   23   ER
1507 RISON, Mark        22.3.4.4   83   23   ER

1165 Stacey, Robert     22.3.4.4   83   24   ER
 594 Kim, Youhan        22.3.4.4   83   26   ER




 595 Kim, Youhan        22.3.4.4   83   27   ER


1222 Stephens, Adrian   22.3.4.4   83   27   ER




 322 Hart, Brian        22.3.4.4   83   28   ER
 323 Hart, Brian        22.3.4.4   83   30   TR




1223 Stephens, Adrian   22.3.4.4   83   33   TR




 324 Hart, Brian        22.3.4.4   83   37   TR
 872 Pillai, Krishna       22.3.4.4   83   43   TR




 325 Hart, Brian           22.3.4.5   83   54   ER
 326 Hart, Brian           22.3.4.5   83   60   TR

 873 Pillai, Krishna       22.3.4.5   83   60   TR




 889 Porat, Ron            22.3.4.5   83   60   TR




 894 Pulikkoonattu, Rethna 22.3.4.6   84   4    ER




 327 Hart, Brian           22.3.4.6   84   6    ER




1224 Stephens, Adrian      22.3.4.6   84   7    TR




 328 Hart, Brian           22.3.4.6   84   11   ER

 874 Pillai, Krishna       22.3.4.6   84   14   TR




 329 Hart, Brian           22.3.4.6   84   15   ER
 895 Pulikkoonattu, Rethna 22.3.4.6   84   16   ER




 333 Hart, Brian           22.3.4.7   84   24   TR

1225 Stephens, Adrian      22.3.4.7   84   27   TR


 330 Hart, Brian           22.3.4.7   84   28   ER
1350 Zhang, Hongyuan       22.3.4.7   84   28   TR




1166 Stacey, Robert        22.3.4.7   84   32   ER
 331 Hart, Brian           22.3.4.7   84   33   ER




 332 Hart, Brian           22.3.4.7   84   35   ER
 875 Pillai, Krishna       22.3.4.7   84   42   ER




 896 Pulikkoonattu, Rethna 22.3.4.7   84   42   ER




 835 Perahia, Eldad        22.3.4.7   84   45   ER
 876 Pillai, Krishna       22.3.4.7     84   45      TR




1226 Stephens, Adrian      22.3.4.7     84   47      TR




 334 Hart, Brian           22.3.4.8.1   84   65      ER




 833 Perahia, Eldad        22.3.4.7     84   42-44   TR




 834 Perahia, Eldad        22.3.4.7     84   42-44   TR




 897 Pulikkoonattu, Rethna 22.3.4.8.1   85   1       ER
596 Kim, Youhan           22.3.4.8.1   85   3    TR




336 Hart, Brian           22.3.4.8.1   85   4    TR




837 Perahia, Eldad        22.3.4.8.1   85   10   ER




898 Pulikkoonattu, Rethna 22.3.4.8.1   85   15   ER
 597 Kim, Youhan       22.3.4.8.1   85   17   ER


 836 Perahia, Eldad    22.3.4.8.1   85   17   ER

1167 Stacey, Robert    22.3.4.8.1   85   17   ER
 337 Hart, Brian       22.3.4.8.1   85   18   ER


 338 Hart, Brian       22.3.4.8.1   85   24   ER




 877 Pillai, Krishna   22.3.4.8.1   85   29   TR




 335 Hart, Brian       22.3.4.8.2   85   45   TR


 598 Kim, Youhan       22.3.4.8.2   85   50   TR




 878 Pillai, Krishna   22.3.4.8.2   86   6    TR




1721 Cheong, Minho     22.3.4.9     86   24   ER
 122 Au, Edward (Kwok   20.3.4.9.1   86   25   ER
     Shum)
 339 Hart, Brian        22.3.4.9.1   86   25   ER
 340 Hart, Brian        22.3.4.9.2   86   30   ER




1227 Stephens, Adrian   22.3.4.9.2   86   30   ER

 838 Perahia, Eldad     22.3.5       86   55   ER




 599 Kim, Youhan        22.3.5       86   65   TR


 341 Hart, Brian        22.3.5       87   3    ER




1299 Stephens, Adrian   22.3.5       87   3    ER
 879 Pillai, Krishna       22.3.5   87   12      ER




 899 Pulikkoonattu, Rethna 22.3.6   88   4       TR




1563 Sun, Bo               22.3.6   88   54      TR

 342 Hart, Brian           22.3.6   88   55      TR




1628 Cheong, Minho         22.3.6   88   55      TR


1332 Vermani, Sameer       22.3.6   88   54-55   TR
                                         (Tab
343 Hart, Brian      22.3.6   89   4    TR




839 Perahia, Eldad   22.3.6   89   23   ER




 80 Asai, Yusuke     22.3.6   90   9    ER




346 Hart, Brian      22.3.6   90   12   TR
345 Hart, Brian           22.3.6   90   24   ER


347 Hart, Brian           22.3.7   90   59   ER
348 Hart, Brian           22.3.7   90   61   ER


349 Hart, Brian           22.3.7   90   61   ER

350 Hart, Brian           22.3.7   90   61   TR




900 Pulikkoonattu, Rethna 22.3.7   91   26   ER




351 Hart, Brian           22.3.7   91   31   TR

840 Perahia, Eldad        22.3.7   91   39   ER




352 Hart, Brian           22.3.7   91   43   TR




353 Hart, Brian           22.3.7   91   52   ER
1351 Zhang, Hongyuan   22.3.7   91   28~32   TR




1168 Stacey, Robert    22.3.7   92   2       ER


 354 Hart, Brian       22.3.7   92   3       ER




 355 Hart, Brian       22.3.7   92   8       TR




 356 Hart, Brian       22.3.7   92   8       TR




 357 Hart, Brian       22.3.7   92   28      TR




 358 Hart, Brian       22.3.7   92   28      TR
 359 Hart, Brian       22.3.7   92   28      TR




 880 Pillai, Krishna   22.3.7   92   36      TR




 361 Hart, Brian       22.3.7   92   46      ER
  81 Asai, Yusuke     22.3.7   92   47   ER




 360 Hart, Brian      22.3.7   92   47   ER
 600 Kim, Youhan      22.3.7   92   47   ER


 200 Erceg, Vinko     22.3.7   92   49   TR




 601 Kim, Youhan      22.3.7   92   49   TR


 362 Hart, Brian      22.3.7   92   50   ER

 363 Hart, Brian      22.3.7   92   51   ER
1169 Stacey, Robert   22.3.7   92   51   ER


 364 Hart, Brian      22.3.7   92   55   ER


 602 Kim, Youhan      22.3.7   92   56   TR




 365 Hart, Brian      22.3.7   92   58   ER
1170 Stacey, Robert   22.3.7   92   58   ER


 603 Kim, Youhan      22.3.7   93   23   ER




 366 Hart, Brian      22.3.7   93   41   ER
 367 Hart, Brian        22.3.7   94   26   ER




 370 Hart, Brian        22.3.8   94   30   TR

 372 Hart, Brian        22.3.8   94   30   ER


1300 Stephens, Adrian   22.3.8   94   33   ER




 368 Hart, Brian        22.3.8   94   35   ER
 369 Hart, Brian        22.3.8   94   35   ER


 841 Perahia, Eldad     22.3.8   94   35   ER




 842 Perahia, Eldad     22.3.8   94   40   ER
 371 Hart, Brian      22.3.8       94   42   TR




1629 Cheong, Minho    22.3.8       94   46   ER


 843 Perahia, Eldad   22.3.8       94   47   ER




 604 Kim, Youhan      22.3.8       94   53   ER


 844 Perahia, Eldad   22.3.8       94   54   ER




 845 Perahia, Eldad   22.3.8       94   59   ER




 846 Perahia, Eldad   22.3.8       95   2    ER




 981 Seok, Yongho     22.3.9.1.2   95   58   ER
1436 Kang, Byeongwoo   22.3.9.1.2   95   58   ER




 373 Hart, Brian       22.3.9.1.2   96   1    ER
 201 Erceg, Vinko      22.3.9.1.2   96   2    ER

1564 Sun, Bo           22.3.9.1.2   96   2    ER

 374 Hart, Brian       22.3.9.1.2   96   25   TR




 982 Seok, Yongho      22.3.9.1.3   96   38   ER




1437 Kang, Byeongwoo   22.3.9.1.3   96   38   ER




1171 Stacey, Robert    22.3.9.1.3   96   48   ER
1338 Ward, Lisa        22.3.9.1.3   96   48   ER




1339 Ward, Lisa        22.3.9.1.3   96   48   ER

1565 Sun, Bo           22.3.9.1.3   96   48   ER

 375 Hart, Brian       22.3.9.1.3   96   60   ER
 376 Hart, Brian       22.3.9.1.3   96   64   ER

 605 Kim, Youhan       22.3.9.1.3   96   65   ER
 202 Erceg, Vinko       22.3.9.1.3   96   41 and   TR
                                          51




 377 Hart, Brian        22.3.9.1.3   97   7        TR
1172 Stacey, Robert     22.3.9.1.3   97   7        ER

 378 Hart, Brian        22.3.9.1.4   97   23       ER

  82 Asai, Yusuke       22.3.9.1.4   97   27       ER


 751 Kneckt, Jarkko     22.3.9.1.4   97   27       ER


 379 Hart, Brian        22.3.9.1.4   97   28       ER
 606 Kim, Youhan        22.3.9.1.4   97   28       ER


 983 Seok, Yongho       22.3.9.1.4   97   28       ER

1301 Stephens, Adrian   22.3.9.1.4   97   28       ER


1438 Kang, Byeongwoo    22.3.9.1.4   97   28       ER
1549 SOHN, ILLSOO       22.3.9.1.4   97   28       ER
1646 Cheong, Minho      22.3.9.1.4   97   28       ER

 881 Pillai, Krishna    22.3.9.1.4   97   30       ER


 380 Hart, Brian        22.3.9.1.4   97   40       ER

 381 Hart, Brian        22.3.9.1.4   97   40       TR
1647 Cheong, Minho         22.3.9.1.4   97   46      TR




 382 Hart, Brian           22.3.9.1.4   97   48      ER


 383 Hart, Brian           22.3.9.1.4   97   56      ER




 984 Seok, Yongho          22.3.9.4     97   58      ER

1469 Lee, Daewon           22.3.9.4     97   58      ER

 847 Perahia, Eldad        22.3.9.1.4   97   27-34   ER
1618 Zhu, Chunhui          22.3.9.1.4   97   28-34   ER

 344 Hart, Brian           22.3.9.1.4   98   3       TR
 386 Hart, Brian           22.3.9.1.4   98   10      ER




 384 Hart, Brian           22.3.9.1.4   98   19      TR




 901 Pulikkoonattu, Rethna 22.3.9.1.4   98   23      ER


 389 Hart, Brian           22.3.9.1.4   98   31      ER
 848 Perahia, Eldad    22.3.9.1.4   98    53   ER


 385 Hart, Brian       22.3.9.1.4   98    54   ER
 607 Kim, Youhan       22.3.9.1.4   98    54   ER


 387 Hart, Brian       22.3.9.2.1   98    61   ER

 985 Seok, Yongho      22.3.9.2.1   98    61   ER




1439 Kang, Byeongwoo   22.3.9.2.1   98    61   ER




 388 Hart, Brian       22.3.9.2.1   99    2    ER

 882 Pillai, Krishna   22.3.9.2.2   99    14   ER




 390 Hart, Brian       22.3.9.2.2   99    18   ER

 391 Hart, Brian       22.3.9.2.2   99    56   ER
 392 Hart, Brian       22.3.9.2.2   99    56   ER

 393 Hart, Brian       22.3.9.2.2   100   1    ER
 608 Kim, Youhan       22.3.9.2.2   100   1    ER
 609 Kim, Youhan        22.3.9.2.2   100   3     ER


 129 Au, Edward (Kwok   22.3.9.2.3   100   8     TR
     Shum)




 849 Perahia, Eldad     22.3.9.2.2   100   1-2   ER




 203 Erceg, Vinko       22.3.9.2.2   100   1-4   ER

 850 Perahia, Eldad     22.3.9.2.2   100   3-4   ER




1302 Stephens, Adrian   22.3.9.2.3   101   7     ER




 204 Erceg, Vinko       22.3.9.2.3   101   11    TR
665 Kneckt, Jarkko   22.3.9.2.3   101   16   TR




666 Kneckt, Jarkko   22.3.9.2.3   101   16   TR
 667 Kneckt, Jarkko     22.3.9.2.3   101   16   TR




 668 Kneckt, Jarkko     22.3.9.2.3   101   16   TR




 972 Santosh Abraham,   22.3.9.2.3   101   18   TR
     Simone Merlin




1570 Zhao, Hui          22.3.9.2.3   101   30   ER
 394 Hart, Brian        22.3.9.2.3   101   34   TR

 124 Au, Edward (Kwok   22.3.9.2.3   101   51   TR
     Shum)




 395 Hart, Brian        22.3.9.2.3   101   51   TR




 973 Santosh Abraham,   22.3.9.2.3   101   51   TR
     Simone Merlin




1341 Zhang, Hongyuan    22.3.9.2.3   101   51   TR


 610 Kim, Youhan        22.3.9.2.3   101   53   TR




 663 Kneckt, Jarkko     22.3.9.2.3   101   53   ER
 664 Kneckt, Jarkko     22.3.9.2.3   101   53   TR




 669 Kneckt, Jarkko     22.3.9.2.3   101   53   TR




 971 Santosh Abraham,   22.3.9.2.3   101   53   TR
     Simone Merlin




1619 Zhu, Chunhui       22.3.9.2.3   101   53   TR




1343 Zhang, Hongyuan    22.3.9.2.3   101   55   ER

1566 Sun, Bo            22.3.9.2.3   101   55   ER
123 Au, Edward (Kwok   22.3.9.2.3   101   13-15   TR
    Shum)




986 Seok, Yongho       22.3.9.2.3   101   16~23   TR




550 Hsieh, Jing-Rong   22.3.9.23    101   52-54   TR




851 Perahia, Eldad     22.3.9.2.3   101   52-54   TR
 125 Au, Edward (Kwok   22.3.9.2.3   101   53,54   TR
     Shum)




1342 Zhang, Hongyuan    22.3.9.2.3   101   53-54   TR


  83 Asai, Yusuke       22.3.9.2.3   102   1       TR




 396 Hart, Brian        22.3.9.2.3   102   15      TR

 397 Hart, Brian        22.3.9.2.3   102   17      TR




 611 Kim, Youhan        22.3.9.2.3   102   17      TR
1636 Cheong, Minho      22.3.9.2.3   102   17      TR




 126 Au, Edward (Kwok   22.3.9.2.3   102   23      TR
     Shum)




 853 Perahia, Eldad     22.9.2.3     102   31      ER


 612 Kim, Youhan        22.3.9.2.3   102   57      TR


 127 Au, Edward (Kwok   22.3.9.2.3   102   60      TR
     Shum)




 852 Perahia, Eldad     22.9.2.3     102   26-32   ER




 398 Hart, Brian        22.3.9.2.3   103   5       TR
1631 Cheong, Minho      22.3.9.2.3   103   5    ER


 613 Kim, Youhan        22.3.9.2.3   103   6    ER


 128 Au, Edward (Kwok   22.3.9.2.3   103   8    TR
     Shum)


 854 Perahia, Eldad     22.9.2.3     103   11   ER


 399 Hart, Brian        22.3.9.2.3   103   21   ER
 614 Kim, Youhan        22.3.9.2.3   103   21   ER




  84 Asai, Yusuke       22.3.9.2.3   103   22   ER


 856 Perahia, Eldad     22.9.2.3     103   22   ER


 987 Seok, Yongho       22.3.9.2.3   103   22   ER

 991 Seok, Yongho       22.3.9.2.3   103   22   ER

1440 Kang, Byeongwoo    22.3.9.2.3   103   22   ER

1447 Lee, Daewon        22.3.9.2.3   103   22   ER

1550 SOHN, ILLSOO       22.3.9.2.3   103   22   ER

1571 Zhao, Hui          22.3.9.2.3   103   22   ER




1620 Zhu, Chunhui       22.3.9.2.3   103   22   ER


1632 Cheong, Minho      22.3.9.2.3   103   22   ER

 400 Hart, Brian        22.3.9.2.3   103   23   ER
 401 Hart, Brian         22.3.9.2.3   103   23   ER


 988 Seok, Yongho        22.3.9.2.3   103   24   ER




 402 Hart, Brian         22.3.9.2.3   103   30   TR


 615 Kim, Youhan         22.3.9.2.3   103   31   TR




 855 Perahia, Eldad      22.9.2.3     103        ER




 403 Hart, Brian         22.3.9.2.3   104   1    ER


 616 Kim, Youhan         22.3.9.2.3   104   18   ER


 857 Perahia, Eldad      22.9.2.3     104   18   ER




 989 Seok, Yongho        22.3.9.2.3   104   18   ER

 992   Seok, Yongho      22.3.9.2.3   104   18   ER
1441   Kang, Byeongwoo   22.3.9.2.3   104   18   ER
1551   SOHN, ILLSOO      22.3.9.2.3   104   18   ER
 990   Seok, Yongho      22.3.9.2.3   104   29   ER

1448 Lee, Daewon         22.3.9.2.3   104   29   ER




 404 Hart, Brian         22.3.9.2.4   104   48   TR




 405 Hart, Brian         22.3.9.2.4   105   12   ER
 406 Hart, Brian      22.3.9.2.4   105   12   ER
 205 Erceg, Vinko     22.3.9.2.4   105   25   ER




 617 Kim, Youhan      22.3.9.2.4   105   52   ER


 618 Kim, Youhan      22.3.9.2.4   105   54   ER


 407 Hart, Brian      22.3.9.2.4   106   7    TR


1634 Cheong, Minho    22.3.9.2.5   106   33   TR


1633 Cheong, Minho    22.3.9.2.5   106   48   ER




 408 Hart, Brian      22.3.9.2.5   106   57   ER




 409 Hart, Brian      22.3.9.2.5   107   30   ER




 410 Hart, Brian      22.3.9.2.5   108   18   ER
1173 Stacey, Robert   22.3.9.2.5   108   19   ER

  85 Asai, Yusuke     22.3.9.2.5   108   20   ER


 619 Kim, Youhan      22.3.9.2.5   108   20   ER


1635 Cheong, Minho    22.3.9.2.5   108   30   ER


 411 Hart, Brian      22.3.9.2.5   108   48   TR

 412 Hart, Brian      22.3.9.2.5   109   4    TR
1637 Cheong, Minho   22.3.9.2.5   109   38   TR


1638 Cheong, Minho   22.3.9.2.5   109   48   ER




1639 Cheong, Minho   22.3.9.2.5   110   2    ER




 620 Kim, Youhan     22.3.9.2.5   110   10   ER


 413 Hart, Brian     22.3.9.2.5   110   13   TR


1640 Cheong, Minho   22.3.9.2.6   110   21   ER

1641 Cheong, Minho   22.3.9.2.6   110   32   ER




 177 Chu, Liwen      22.3.9.2.6   110   35   TR




 178 Chu, Liwen      22.3.9.2.6   110   35   TR




 414 Hart, Brian     22.3.9.2.6   110   35   TR
1642 Cheong, Minho   22.3.9.2.6   110   61   ER


 415 Hart, Brian     22.3.9.2.6   111   1    ER
1643 Cheong, Minho   22.3.9.2.6   111   1    ER


 416 Hart, Brian     22.3.9.2.6   111   64   TR




1644 Cheong, Minho   22.3.9.2.6   112   12   ER




 417 Hart, Brian     22.3.9.2.6   112   52   TR


1645 Cheong, Minho   22.3.9.2.6   114   50   TR


 418 Hart, Brian     22.3.11      114   52   TR




 419 Hart, Brian     22.3.11      114   61   ER


1648 Cheong, Minho   22.3.11      115   3    TR




 420 Hart, Brian     22.3.11      115   11   TR
 421 Hart, Brian        22.3.11     115    13      TR




 422 Hart, Brian        22.3.11     115    27      ER
 993 Seok, Yongho       22.3.11     115    27      ER

 621 Kim, Youhan        22.3.11     115    30      TR




 423 Hart, Brian        22.3.11.1   115    61      ER

1649 Cheong, Minho      22.3.11.1   115    61      TR




1349 Zhang, Hongyuan    22.3.11     115    11~40   TR




1558 Sun, Bo            22.3.11.2   116    10      ER

1303 Stephens, Adrian   22.3.11.2   116    34      ER




 622 Kim, Youhan        22.3.11.4   117    5       ER




 424 Hart, Brian        22.3.11.4.1. 117   22      TR
                        1
1651 Cheong, Minho      22.3.11.4.1. 117   22      ER
                        1.
1650 Cheong, Minho    22.3.11.4.1. 117   34   ER
                      2

1559 Sun, Bo          22.3.11.4.2 117    51   TR




 207 Erceg, Vinko     22.3.11.4.2 117    53   TR




 858 Perahia, Eldad   22.3.11.4.2 118    19   ER




 859 Perahia, Eldad   22.3.11.4.3 118    21   ER

1652 Cheong, Minho    22.3.11.4.3 118    44   ER
1653 Cheong, Minho      22.3.11.4.3 118   46      ER




 623 Kim, Youhan        22.3.11.4.3 119   26      ER


1174 Stacey, Robert     22.3.11.4.3 119   26      ER

 624 Kim, Youhan        22.3.11.4.3 119   29      ER


1175 Stacey, Robert     22.3.11.4.3 119   29      ER

 625 Kim, Youhan        22.3.11.4.3 119   50      ER


1304 Stephens, Adrian   22.3.11.4.3 119   56      TR




 860 Perahia, Eldad     22.3.11.4.3 119   49-51   ER




 861 Perahia, Eldad     22.3.11.4.3 119   49-51   ER


1654 Cheong, Minho      22.3.11.5   120   23      TR




1655 Cheong, Minho      22.3.11.5   120   26      TR


 208 Erceg, Vinko       22.3.11.5   120   27      TR

 425 Hart, Brian        22.3.11.5   120   27      TR
1656 Cheong, Minho    22.3.11.5   120   33   TR


1657 Cheong, Minho    22.3.11.5   120   33   TR


1660 Cheong, Minho    22.3.11.5   120   33   ER




1176 Stacey, Robert   22.3.11.5   120   34   TR




 209 Erceg, Vinko     22.3.11.5   120   47   TR

 626 Kim, Youhan      22.3.11.5   120   47   ER


 862 Perahia, Eldad   22.3.11.5   120   47   ER




1177 Stacey, Robert   22.3.11.5   120   47   ER

1658 Cheong, Minho    22.3.11.5   120   47   ER


 426 Hart, Brian      22.3.11.5   120   50   TR
 902 Pulikkoonattu, Rethna 22.3.11.5   120   50      ER




1659 Cheong, Minho         22.3.11.5   120   51      ER




 427 Hart, Brian           22.3.11.5   120   52      TR

 428 Hart, Brian           22.3.11.5   120   53      TR




1560 Sun, Bo               22.3.11.5   120   53      ER


 210 Erceg, Vinko          22.3.11.5   120   26-36   TR




 863 Perahia, Eldad        22.3.11.5   120   53-56   ER




 864 Perahia, Eldad        22.3.11.5   120   58-59   ER
 429 Hart, Brian           22.3.11.6   121   2       TR




 430 Hart, Brian           22.3.11.6   121   7       TR
1661 Cheong, Minho    22.3.11.6   121   12   ER


1178 Stacey, Robert   22.3.11.6   121   22   ER

 431 Hart, Brian      22.3.11.6   121   31   TR




 432 Hart, Brian      22.3.11.6   121   36   TR
1179 Stacey, Robert   22.3.11.7   121   63   ER
 433 Hart, Brian      22.3.11.7   122   17   ER


 627 Kim, Youhan      22.3.11.7   122   19   ER


1662 Cheong, Minho    22.3.11.7   122   19   ER

1663 Cheong, Minho    22.3.11.7   122   22   ER

1664 Cheong, Minho    22.3.11.7   122   59   ER




1666 Cheong, Minho    22.3.11.7   123   1    ER




1665 Cheong, Minho    22.3.11.7   123   10   ER




 628 Kim, Youhan      22.3.11.7   123   15   ER


 629 Kim, Youhan      22.3.11.7   123   53   ER


1180 Stacey, Robert   22.3.11.7   123   53   ER
1667 Cheong, Minho    22.3.11.7   123   54   ER

1181 Stacey, Robert   22.3.11.8.1 124   65   ER

1668 Cheong, Minho    22.3.11.8.1 125   1    ER


1702 Cheong, Minho    22.3.11.8.1 125   57   ER


 630 Kim, Youhan      22.3.11.8.1 125   59   ER


1669 Cheong, Minho    22.3.11.8.1 125   59   ER

1670 Cheong, Minho    22.3.11.8.1 125   64   TR


1671 Cheong, Minho    22.3.11.8.1 125   64   ER




1672 Cheong, Minho    22.3.11.8.1 125   64   ER

 435 Hart, Brian      22.3.11.8.1 126   1    TR




1673 Cheong, Minho    22.3.11.8.1 126   2    TR

 434 Hart, Brian      22.3.11.8.1 126   3    TR




  86 Asai, Yusuke     22.3.11.8.1 126   10   ER

1674 Cheong, Minho    22.3.11.8.1 126   10   ER

1675 Cheong, Minho    22.3.11.8.1 126   16   ER
 631 Kim, Youhan        22.3.11.8.2 126   28      ER


1676 Cheong, Minho      22.3.11.8.2 126   28      ER

1681 Cheong, Minho      22.3.11.8.2 126   57      ER




 130 Au, Edward (Kwok   22.3.11.8.1 126   1, 4    ER
     Shum)




 131 Au, Edward (Kwok   22.3.11.8.1 126   8, 11   ER
     Shum)




 632 Kim, Youhan        22.3.11.8.2 127   11      TR




1677 Cheong, Minho      22.3.11.8.2 127   12      TR




1678 Cheong, Minho      22.3.11.8.2 127   14      TR
1182 Stacey, Robert   22.3.11.8.2 127   15   ER


1680 Cheong, Minho    22.3.11.8.2 127   16   ER




1682 Cheong, Minho    22.3.11.8.2 127   17   ER




1679 Cheong, Minho    22.3.11.8.2 127   22   ER

1683 Cheong, Minho    22.3.11.8.3 127   35   TR




 436 Hart, Brian      22.3.11.8.3 127   36   TR

 438 Hart, Brian      22.3.11.8.3 127   43   TR

 865 Perahia, Eldad   22.3.11.8.3 127   43   ER




 437 Hart, Brian      22.3.11.8.3 127   44   ER
 439 Hart, Brian      22.3.11.8.3 127   50   ER
 890 Porat, Ron          22.3.11.8.3 127   41-51   ER


 813 Luo, Zhendong       22.3.11.8.3 127   43-51   ER




1684 Cheong, Minho       22.3.11.8.3 128   3       ER

1685 Cheong, Minho       22.3.11.8.3 128   3       TR




 440 Hart, Brian         22.3.11.8.3 128   40      ER

 441 Hart, Brian         22.3.11.8.3 128   45      ER
 442 Hart, Brian         22.3.11.9   128   55      ER


 443 Hart, Brian         22.3.11.9   129   55      TR

  87 Asai, Yusuke        22.3.11.9   129   56      ER


 633 Kim, Youhan         22.3.11.9   129   56      ER


  88 Asai, Yusuke        22.3.11.9   129   60      ER




 634 Kim, Youhan         22.3.11.9   129   60      ER


1183 Stacey, Robert      22.3.11.9   129   60      ER

1328 van Zelst, Allert   22.3.11.9   129   60      ER




1686 Cheong, Minho       22.3.11.9   129   60      ER
 867 Perahia, Eldad   22.3.11.9    129   61      ER




1687 Cheong, Minho    22.3.11.9    129   61      ER

 444 Hart, Brian      22.3.11.9    129   64      ER
 866 Perahia, Eldad   22.3.11.9    129   60-61   ER


 445 Hart, Brian      22.3.11.10.1 130   11      TR

 446 Hart, Brian      22.3.11.10.1 130   11      ER

 447 Hart, Brian      22.3.11.10.1 130   11      TR


1572 Zhao, Hui        22.3.11.10.1 131   48      ER




 448 Hart, Brian      22.3.11.11   131   61      ER

 449 Hart, Brian      22.3.11.11   131   65      ER
 635 Kim, Youhan         22.3.11.11   132   4    ER




 636 Kim, Youhan         22.3.11.11   132   28   TR




1184 Stacey, Robert      22.3.11.11   132   28   TR




1557 Sun, Bo             22.3.11.11   132   30   ER




 150 Banerjea, Raja      22.3.11.11   132   31   TR




 450 Hart, Brian         22.3.11.11   132   31   ER

1329 van Zelst, Allert   22.3.11.11   132   31   TR
  89 Asai, Yusuke      22.3.12.1   132   41   ER

 451 Hart, Brian       22.3.12.1   132   48   TR




  90 Asai, Yusuke      22.3.12.1   132   52   ER




 452 Hart, Brian       22.3.12.1   132   54   ER

  91 Asai, Yusuke      22.3.12.1   132   57   ER


1688 Cheong, Minho     22.3.12.1   132   57   ER


 453 Hart, Brian       22.3.12.1   132   59   TR




 454 Hart, Brian       22.3.12.1   132   61   TR
 455 Hart, Brian       22.3.12.1   132   61   TR


1630 Cheong, Minho     22.3.12.1   132   61   TR

 456 Hart, Brian       22.3.12.1   132   63   TR

1333 Vermani, Sameer   22.3.12.1   132   63   ER
 457 Hart, Brian        22.3.12.1   133   7    ER




 458 Hart, Brian        22.3.12.1   133   12   ER


 994 Seok, Yongho       22.3.12.1   133   12   ER


 459 Hart, Brian        22.3.12.1   133   21   TR




 460 Hart, Brian        22.3.12.1   133   23   ER

 132 Au, Edward (Kwok   22.3.12.1   133   25   ER
     Shum)
 461 Hart, Brian        22.3.12.1   133   25   ER
1689 Cheong, Minho      22.3.12.1   133   25   ER




1305 Stephens, Adrian   22.3.12.1   133   28   ER




1334 Vermani, Sameer    22.3.12.1   133   33   ER




1306 Stephens, Adrian   22.3.12.2   133   40   ER
1690 Cheong, Minho   22.3.12.2   133   40   ER


 637 Kim, Youhan     22.3.12.2   133   41   ER


1691 Cheong, Minho   22.3.12.2   133   42   ER

1692 Cheong, Minho   22.3.12.2   133   45   TR




1561 Sun, Bo         22.3.12.2   133   48   ER




 462 Hart, Brian     22.3.12.2   133   53   TR




 463 Hart, Brian     22.3.12.2   133   62   TR
1693 Cheong, Minho   22.3.12.2   133   62   TR


1694 Cheong, Minho   22.3.12.3   134   4    ER




 464 Hart, Brian     22.3.12.3   134   5    ER




 465 Hart, Brian     22.3.12.3   134   10   ER
 466 Hart, Brian       22.3.12.3   134   13   ER
 467 Hart, Brian       22.3.12.3   134   13   ER




 468 Hart, Brian       22.3.12.3   134   13   TR




 469 Hart, Brian       22.3.12.3   134   15   ER
 470 Hart, Brian       22.3.12.3   134   15   TR

 211 Erceg, Vinko      22.3.12.3   134   17   TR


1335 Vermani, Sameer   22.3.12.3   134   17   ER




 471 Hart, Brian       22.3.12.3   134   19   ER
 472 Hart, Brian       22.3.12.3   134   20   ER
 473 Hart, Brian       22.3.12.3   134   21   TR

 474 Hart, Brian       22.3.12.3   134   21   TR




1695 Cheong, Minho     22.3.12.3   134   21   ER


 475 Hart, Brian       22.3.12.3   134   24   ER
 476 Hart, Brian       22.3.12.3   134   24   TR
 480 Hart, Brian    22.3.13   134   32   TR




 212 Erceg, Vinko   22.3.13   134   37   ER

 481 Hart, Brian    22.3.13   134   37   TR




1562 Sun, Bo        22.3.13   134   44   TR
 812 Luo, Zhendong       22.3.15     134   59     TR




1696 Cheong, Minho       22.3.15     134   62     TR




  17 Aboul-Magd, Osama   22.3.12.3   134   1-27   TR




 482 Hart, Brian         22.3.15     135   12     ER

 483 Hart, Brian         22.3.15     135   40     ER


 484 Hart, Brian         22.3.15     135   53     ER
1391 Ecclesine, Peter    22.3.15     135   54     TR




 638 Kim, Youhan         22.3.15     135   58     ER


 485 Hart, Brian         22.3.15     135   59     ER
 133 Au, Edward (Kwok   22.3.15     135   16, 21,   ER
     Shum)                                27




 486 Hart, Brian        22.3.16     136   31        TR


1309 Stephens, Adrian   22.3.16     136   31        TR




 487 Hart, Brian        22.3.19.1   136   53        TR
 488 Hart, Brian        22.3.19.1   136   58        TR




  92 Asai, Yusuke       22.3.19.1   137   60        ER




 489 Hart, Brian        22.3.19.1   139   5         ER
 490 Hart, Brian        22.3.19.1   139   36        TR
 151 Banerjea, Raja     22.3.19.2   139   48   TR




1310 Stephens, Adrian   22.3.19.2   139   48   TR
1705 Cheong, Minho      22.3.19.2   139   48   TR




 491 Hart, Brian        22.3.19.2   139   51   TR


 492 Hart, Brian        22.3.19.2   140   1    ER
 152 Banerjea, Raja     22.3.19.2   140   19   TR




1188 Stanley, Dorothy   22.3.19.2   140   19   TR

1697 Cheong, Minho      22.3.19.2   140   19   ER




1311 Stephens, Adrian   22.3.19.2   140   20   TR
 883 Pillai, Krishna    22.3.19.2   140   24   TR




1699 Cheong, Minho      22.3.19.3   140   30   TR


1698 Cheong, Minho      22.3.19.3   140   35   TR
 493 Hart, Brian          22.3.19.4   140    43       TR




1312 Stephens, Adrian     22.3.19.6.2 140    65       TR
1700 Cheong, Minho        22.3.19.6.3 141    9        TR
1701 Cheong, Minho        22.3.19.6.3 141    11       ER




 213 Erceg, Vinko         22.3.19.6.3 141    27       TR


 494 Hart, Brian          22.3.19.6.4 141    40       TR




 495 Hart, Brian          22.3.19.6.4 141    40       ER


 496 Hart, Brian          22.3.19.6.4 141    54       TR




 903 Pulikkoonattu, Rethna 22.3.19.6.4 141   61       TR




 134 Au, Edward (Kwok     22.3.19.6.4 141    59, 65   ER
     Shum)


 497 Hart, Brian          22.3.19.6.4 142    1        ER
904 Pulikkoonattu, Rethna 22.3.19.6.4 142   1   TR




206 Erceg, Vinko         22.3.19.6.4 142    2   TR




498 Hart, Brian          22.3.19.6.4 142    3   TR




905 Pulikkoonattu, Rethna 22.3.19.6.4 142   9   TR
1703 Cheong, Minho   22.3.19.6.4 142   11   TR

1704 Cheong, Minho   22.3.19.6.4 142   12   TR

 499 Hart, Brian     22.3.20     142   20   ER




 500 Hart, Brian     22.3.20.1   142   27   ER

1706 Cheong, Minho   22.3.20.1   142   28   ER


1707 Cheong, Minho   22.3.20.1   142   32   ER

 639 Kim, Youhan     22.3.20.2   142   63   ER


1708 Cheong, Minho   22.3.20.2   142   64   ER

  93 Asai, Yusuke    22.3.20.2   143   7    ER




 640 Kim, Youhan     22.3.20.2   143   7    ER


1709 Cheong, Minho   22.3.20.2   143   7    ER

 501 Hart, Brian     22.3.20.2   143   8    TR
 502 Hart, Brian        22.3.20.2   143   17   ER




 641 Kim, Youhan        22.3.20.3   143   51   ER


1710 Cheong, Minho      22.3.20.3   143   52   ER

 503 Hart, Brian        22.3.20.5   144   18   TR




  94 Asai, Yusuke       22.3.20.5   144   19   TR




1392 Ecclesine, Peter   22.3.20.5   144   19   TR




1313 Stephens, Adrian   22.3.20.5.1 144   40   ER
1799 Chu, Liwen       22.3.20.5.2 144   63   TR




 504 Hart, Brian      22.3.20.5.2 145   34   TR

 670 Kneckt, Jarkko   22.3.20.5.2 145   35   TR




 505 Hart, Brian      22.3.20.5.2 145   36   TR
 671 Kneckt, Jarkko     22.3.20.5.2 145   40   TR




1314 Stephens, Adrian   22.3.20.5.2 145   40   ER




 512 Hart, Brian        22.3.21    145    47   TR




 506 Hart, Brian        22.3.21    145    49   ER
 511 Hart, Brian        22.3.21    145    49   TR


 642 Kim, Youhan        22.3.21    145    50   ER


 507 Hart, Brian        22.3.21    145    51   ER

 508 Hart, Brian        22.3.21    145    51   ER

 509 Hart, Brian        22.3.21    145    52   ER




  95 Asai, Yusuke       22.3.21    145    54   ER




 643 Kim, Youhan        22.3.21    145    54   ER


 672 Kneckt, Jarkko     22.3.21    145    54   ER
 814 Luo, Zhendong      22.3.21    145    54   ER




1185 Stacey, Robert     22.3.21    145    54   ER
510 Hart, Brian      22.3.21    145    59      ER
513 Hart, Brian      22.3.21    145    61      TR

673 Kneckt, Jarkko   22.3.21    145    61      TR


514 Hart, Brian      22.3.21    145    62      TR




674 Kneckt, Jarkko   22.3.21    145    62      TR




515 Hart, Brian      22.3.21    145    64      TR

798 Liu, Yong        22.3.20.5.2 145   39-40   TR




516 Hart, Brian      22.3.21    146    14      TR

517 Hart, Brian      22.3.21    146    23      TR




815 Luo, Zhendong    22.3.21    146    25      ER




518 Hart, Brian      22.3.21    147    30      TR
521 Hart, Brian      22.3.21   148   6    TR




522 Hart, Brian      22.3.21   148   28   TR


520 Hart, Brian      22.3.21   148   35   TR

519 Hart, Brian      22.3.21   148   53   TR

536 Hart, Brian      22.3.22   149   10   TR


523 Hart, Brian      22.3.22   149   13   TR
524 Hart, Brian      22.3.22   149   14   TR

525 Hart, Brian      22.3.22   149   20   ER




537 Hart, Brian      22.3.22   149   27   TR




538 Hart, Brian      22.3.22   149   36   ER
644 Kim, Youhan      22.3.22   149   46   TR


539 Hart, Brian      22.3.22   149   50   ER
675 Kneckt, Jarkko   22.3.22   149   51   TR




526 Hart, Brian      22.3.22   150   14   TR
527 Hart, Brian      22.3.22   150   22   TR
 645 Kim, Youhan        22.3.22   150   23   TR


 528 Hart, Brian        22.3.22   150   24   TR


 529 Hart, Brian        22.3.22   150   24   ER
 646 Kim, Youhan        22.3.22   150   26   ER


1186 Stacey, Robert     22.3.22   150   26   ER

 530 Hart, Brian        22.3.22   150   36   ER




 531 Hart, Brian        22.3.22   150   43   TR


 532 Hart, Brian        22.3.22   150   43   ER
1316 Stephens, Adrian   22.3.22   151   15   TR




 533 Hart, Brian        22.3.22   151   19   TR

 534 Hart, Brian        22.3.22   151   26   TR


 535 Hart, Brian        22.3.22   151   37   ER
 478 Hart, Brian        22.3.22   152   1    TR


  96 Asai, Yusuke       22.3.22   152   23   TR
 540 Hart, Brian        22.3.22   152   34     TR




 541 Hart, Brian        22.4.1    152   64     ER
  97 Asai, Yusuke       22.4.2    153   2      ER

1317 Stephens, Adrian   22.4.2    153   3      TR

 647 Kim, Youhan        22.4.2    153   5      ER


 542 Hart, Brian        22.4.2    153   13     TR


 477 Hart, Brian        22.4.2    153   24     TR




1318 Stephens, Adrian   22.4.2    153   29     TR




 995 Seok, Yongho       22.4.2    153   3,25   TR

 543 Hart, Brian        22.4.3    154   35     TR




 544 Hart, Brian        22.4.3    154   45     TR
 545 Hart, Brian        22.4.4    155   46     TR

 996 Seok, Yongho       22.4.4    155   56     TR
1319 Stephens, Adrian   22.4.4    155   56     TR
 135 Au, Edward (Kwok   22.5      155   65     ER
     Shum)
 648 Kim, Youhan        22.5   155   65   TR


1336 Vermani, Sameer    22.5   156   2    TR




 649 Kim, Youhan        22.5   156   4    TR


 136 Au, Edward (Kwok   22.5   156   5    ER
     Shum)

1711 Cheong, Minho      22.5   156   12   TR




 546 Hart, Brian        22.5   156   26   TR
 547 Hart, Brian        22.5   164   41   TR




1567 Sun, Bo            22.5   165   41   TR




 650 Kim, Youhan        22.5   166   1    TR




1393 Ecclesine, Peter   I.1    170   5    TR




1189 Stanley, Dorothy   I.1    170   8    ER




1320 Stephens, Adrian   I.1    170   8    ER
 137 Au, Edward (Kwok   I.1       170   22   ER
     Shum)
  98 Asai, Yusuke       Annex I   170   23   ER


 214 Erceg, Vinko       Annex J   171   2    TR

1394 Ecclesine, Peter   J.1       171   15   TR




1398 Ecclesine, Peter   J.1       171   16   TR
 651 Kim, Youhan        J.1   171   40   TR




1397 Ecclesine, Peter   J.1   173   13   TR




 652 Kim, Youhan        J.1   173   34   TR


1395 Ecclesine, Peter   J.1   174   15   TR




1396 Ecclesine, Peter   J.1   174   24   TR
1049 Seok, Yongho     8.4.2.39   389       54        TR




1050 Seok, Yongho     8.4.2.39   392       1         TR




1051 Seok, Yongho     8.4.2.40   393       42        ER




1544 SOHN, ILLSOO     11.2.3     783       25        TR




1116 Shi, Wei         22.5       156 - 169 All the   ER
                                           no
1117 Shi, Wei         22.5       156 - 169 All the   ER
                                           no




1755 Lee, Jae Seung   7.3.1.33   25 ~ 26   4         ER
1516 RISON, Mark         7.4.3;7.4.11 35-36     various TR




  49 Asai, Yusuke        9.2.0b.6a    45 - 46           ER
                         VHT RTS
                         procedure -
                         9.2.0b.7 CTS
                         procedu

1113 Shapira, Nir        9.18.3       55,56     32,20   TR
                                                (res




  16 Aboul-Magd, Osama   22.2.2       72-77     many    ER




1432 Kang, Byeongwoo     22.2.2       74~77     31~33   ER
1510 RISON, Mark    22.2.2;22.3. 77;101   26;51   TR
                    9.2.3




1515 RISON, Mark    various     various   various TR




  18 Asai, Yusuke   TOC         xii       22.3.12. ER
                                          2
179 Cordeiro, Carlos   All       ER




215 Erceg, Vinko       General   TR




217 Erceg, Vinko       General   TR




263 Hart, Brian                  TR




694 Kneckt, Jarkko               ER
 697 Kneckt, Jarkko     7.2.1.5    TR




 752 Kneckt, Jarkko     9.2.0b.5   TR




1115 Shapira, Nir       11.8       TR




1215 Stephens, Adrian   22.2.2     ER




1315 Stephens, Adrian   General    ER




1321 Stephens, Adrian   General    TR
1322 Stephens, Adrian   General    TR
1378 Ecclesine, Peter   General   TR




1379 Ecclesine, Peter   General   ER


1385 Ecclesine, Peter   General   ER
Comment                      SuggestedRemedy                Response                     Assigned
                                                                                         ad-hoc

You need to cite all preceding Add em                       AGREE. "This amendment is     Ed
amendments, including TGaa,                                 based on IEEE P802.11REVmb
TGad, ...                                                   D7.0 amended by IEEE
                                                            P802.11v D16.0, IEEE P802.11u
                                                            D13.0, IEEE P802.11s D9.0,
                                                            IEEE P802.11ae D2.0, IEEE
                                                            P802.11af D1.0, IEEE
                                                            P802.11aa D3.0 and IEEE
                                                            P802.11ad D1.2"

MU-MIMO definition could be As in comment                   Yusuke.                      MU
confused with FDMA or
cellular. For greater
definitional power, append
"over the same bandwidth in
the same area; typically to or
from a common STA"

Unnecessary commas between Delete commas                    AGREE IN PRINCIPLE. Comma Ed
words "multi-user", "multiple                               after multi-user should be
input", and "multiple output"                               removed. Comma between
                                                            multiple input, multiple output
                                                            should remain.

You don't need "A contiguous Delete noted text              Chao-Chun                    COEX
transmission uses
one frequency segment, while
a non-contiguous transmission
uses two frequency segments"
in this definition - it is
redundant. The other
definitions of contiguous
transmission and non-
contiguous transmission
already covers this.


the MU-MIMO definition does Should clarify definition and   Yusuke.                      MU
not require any STA to have reuse MIMO definition in the
multiple antennas. It also  baseline spec.
seems to be redefining MIMO
when a definition already
exists.
11ad has redefined              Liase with 11ad to find a          Yusuke.                      MU
"downlink", so the 802.11       cleaner way forward
downlink is now a more
general term than many folk
realise, and as a modifier does
not automatically mean AP to
clients

"MU-MIMO transmitted" yet       MU-MIMO => "MU-MIMO                                             Ed
MU-MIMO is defined as a         technique where the PPDU is"
technique, which cannot be      (if we are defining a technique)
TXed                            or => "MU-MIMO PPDU" (if we
                                are defining a transmission)

the 2nd sentence of the        as per comment                                                   Ed
'frequency segment' definition
defines other terms and should
be deleted.

non-contiguous transmission is add "or more" after two             Chao-Chun                    COEX
defined as a transmission using
two nonadjacent frequency
segments. Although this is the
case in 11ac. It may be possible
in the future that non-
contiguous transmission can
use two or MORE nonadjacent
frequency segments.


The Definitions specific to     Add the definitions                Allan.                       MAC
802.11 is missing definitions
for primary and secondary AC
and primary and secondary
destinations.

"Clause 19 (High Throughput     As in comment.                     DISAGREE. With shift to REVmb Ed
(HT) PHY specification)" is                                        7.0 baseline, Clause 19
incorrect. "Clause 20" is                                          reference is correct.
correct.
AC                                Spell out acronyms in def   AGREE. "primary access         Ed
                                  section                     category (primary AC): the
                                                              access category (AC)
                                                              associated with the enhanced
                                                              distributed channel access
                                                              function (EDCAF) that gains
                                                              channel access. There can be
                                                              only one primary AC at a given
                                                              time".

in the definitions of             as per comment                                            Ed
primary/secondary AC and
primary/secondary
destinations, it should be
clarified that the context is
local and 'per QoS STA'. Insert
"per QoS STA" before "at" for
these 4 definitions.

be consistent in 'can be' vs.     as per comment                                            Ed
'could be' in these 4
definitions. Suggest 'can be'.

AC                                Spell out acronyms in def   AGREE. Similar to #240.        Ed
                                  section                     "secondary access category
                                                              (secondary AC): an access
                                                              category (AC) that is not
                                                              associated with the enhanced
                                                              distributed channel access
                                                              function (EDCAF) that gains
                                                              channel access. There could be
                                                              multiple secondary ACs at a
                                                              given time."
"Destinations" yet "one or         As in comment       Allan.      MAC
more". Suggest "destination(s).
And is "destination(s)"
adequately defined - should it
be destination STAs? And
destination in the DA or RA
sense? Clarify. Also, in the text,
I see this being defined but
never subsequently used - is a
defn even needed? Ditto
"Secondary destinations"




"and can be used to setup a       As in comment        Chao-Chun   COEX
VHT 40MHz BSS" is confusing.
It seems to imply, indirectly,
that the definition of a primary
40 MHz channel in a 40 MHz
BSS is the 40 MHz of the BSS
(fine). But this idea can be
expressed more clearly: either
just list 40 MHz with the other
bandwidths (since a subset can
always be the whole set; a
subchannel can be the whole
channel). If the preference is to
keep "subchannel" as a smaller
set, avoid the "and can be
used" since there is not much
"and" happening; write "or the
40 MHz channel that can ..."
Ditto primary 80




In a 160 or 80+80 VHT BSS, a Leave to the PHY ad hoc   Yusuke.     COEX
secondary 40MHz subchannel
may not always be adjacent to
the primary 40MHz channel. It
may be adjacent to another
secondary 40MHz channel.
missing a few words in           Insert missing words which will AGREE. As suggested.         Ed
"physical layer protocol data    read "physical layer
unit (PPDU)"                     convergence procedure
                                 protocol data unit (PPDU)"
Notations "physical layer        Use full notation "physical     AGREE. See #998              Ed
protocol data unit (PPDU)"       layer convergence procedure
                                 protocol data unit (PPDU)"

Grammer:                         Change the sentence to "very     DISAGREE. With the suggested Ed
"very high throughput (VHT)      high throughput (VHT) single     wording, an A-MPDU could
single medium access control     medium access control (MAC)      have multiple MPDUs but if
(MAC) protocol data unit (VHT    protocol data unit (VHT single   one had the EOF field set it
single MPDU): An MPDU that is    MPDU): An MPDU in a VHT          would still be considered a VHT
the only MPDU carried in an A-   PPDU that is the only MPDU       single MPDU. The 'and' (in 'and
MPDU carried in a VHT PPDU,      carried in an A-MPDU with the    with the EOF') is important.
and with the EOF subfield of     EOF subfield of the MPDU
the MPDU delimiter field equal   delimiter field indicating 1."
to 1."
In addition to "80 MHz mask      Insert the following definitions Yusuke           PHY
physical layer convergence       just after just after the
procedure (PLCP) protocol data   definition of "80MHz mask":
unit (PPDU)", "160 MHz mask      160 MHz mask physical layer
PPDU" and "80+80 MHz mask        convergence procedure (PLCP)
PPDU" should be also defined.    protocol data unit (PPDU): One
                                 of the following PPDUs:
                                 1) an 160 MHz VHT PPDU
                                 (TXVECTOR parameter
                                 CH_BANDWIDTH set to
                                 HT_CBW160);
                                 2) an 160 MHz non-HT
                                 duplicate PPDU (TXVECTOR
                                 parameter CH_BANDWIDTH
                                 set to NON_HT_CBW160);
                                 3) a 20 MHz non-HT, HT or VHT
                                 PPDU with the TXVECTOR
                                 parameter CH_BANDWIDTH
                                 set to NON_HT_CBW20 or
                                 HT_CBW20. The PPDU is
                                 transmitted using a 40 MHz
                                 transmit spectral mask defined
                                 in Clause 22. Or,
                                 4) a 40 MHz non-HT duplicate,
                                 HT or VHT PPDU with the
                                 TXVECTOR parameter
                                 CH_BANDWIDTH set to
"80 MHz mask PPDU" is not a      NON_HT_CBW40 or
                                 Rename                           Yusuke.          PHY
great name since sometimes
the mask is 40 MHz and
sometimes 80 MHz.

20 MHz PPDU yet a 40 MHz         As in comment                   Yusuke.           PHY
mask - seems wrong or please
explain
". Or," yet previous bullet      ". Or" -> "; or", or just ";"   AGREE. Just ";"   Ed
ended ";"
The paragraph talks about 20     Change: 'The PPDU is           Yusuke.            PHY
MHz bandwidth transmission.      transmitted using a 40 MHz
The Spectral mask should be      transmit spectral mask defined
20 MHz, right?                   in Clause 22.' to 'The PPDU is
                                 transmitted using a 20 MHz
                                 transmit spectral mask defined
                                 in Clause 22.'
the definition of "80 MHz mask     3) a 20 MHz non-HT, HT or VHT Yusuke.                   PHY
physical layer convergence         PPDU with the TXVECTOR
procedure (PLCP) protocol data     parameter CH_BANDWIDTH
unit (PPDU):" is not correct for   set to NON_HT_CBW20 or
the following case                 HT_CBW20. The PPDU is
3) a 20 MHz non-HT, HT or VHT      transmitted using a 40 80 MHz
PPDU with the TXVECTOR             transmit spectral mask defined
parameter CH_BANDWIDTH             in Clause 22.
set to NON_HT_CBW20 or             4) a 40 MHz non-HT duplicate,
HT_CBW20. The PPDU is              HT or VHT PPDU with the
transmitted using a 40 MHz         TXVECTOR parameter
transmit spectral mask defined     CH_BANDWIDTH set to
in Clause 22.                      NON_HT_CBW40 or
4) a 40 MHz non-HT duplicate,      HT_CBW40. The PPDU is
HT or VHT PPDU with the            transmitted using a 40 80 MHz
TXVECTOR parameter                 transmit spectral mask defined
CH_BANDWIDTH set to                in Clause 22.
NON_HT_CBW40 or
HT_CBW40. The PPDU is
transmitted using a 40 MHz
transmit spectral mask defined
in Clause 22.




The "40MHz transmit spectrual Change "40" to "80"               Yusuke.                    Ed
mask" should be "80MHz
transmit spectrual mask,"
because this is the defintion for
80MHz maks PPDU.

The "40MHz transmit spectrual Change "40" to "80"               Yusuke.                    Ed
mask" should be "80MHz
transmit spectrual mask,"
because this is the defintion for
80MHz maks PPDU.

Additional abbreviations and   multi-user, transmission                                    Ed
acronyms are recommended       opportunity (MU-TXOP), end of
                               frame (EOF), Galois/Counter
                               mode (GCM), and
                               Galois/Counter mode protocol
                               (GCMP)
Insert acronyms for GID, GID-L change accordingly            DISAGREE. These are field     Ed
and GID-H; they are not                                      names and do not need to be
defined in REVmb D4.0                                        defined.
In line 52, 'MU' is 'Multi-user'. Add '-' between 'Single' and                                     Ed
In line 54, 'SU' is 'Single user', 'user'; 'Single-user'
in which '-' is removed. The
terminology should be aligned.

When written in spec, 'MU' is Add '-' between 'Single' and                                         Ed
'Multi-user'. On the other    'user'; that is 'Single-user'
hand, 'SU' is 'Single user',
where '-' is removed.
Unnecessary commas between Delete commas                           AGREE IN PRINCIPLE. See #997. Ed
words "multi-user", "multiple                                      Removed comma after multi-
input", and "multiple output"                                      user but kept comma between
                                                                   multiple input and multiple
                                                                   output.
This subclause (in fact, the      As noted                                                       Ed
following ones as well) ignore
the changes that were made in
TGad. Since the TGad draft
precedes Tgac in the
amendment order, need to
change the Tgac draft to
comply with the changes in
TGad
The maximum MPDU size             Change to read: "The PPDU in AGREE IN PRINCIPLE.                 MAC
supported by the recipient may    which the frame is transmitted, Resolution text provided in
also limit the Frame Body size.   the maximum MSDU size (2304 11/396r2.
Also, the maximum A-MSDU          octets), the maximum A-MSDU
size applies to HT STAs and is    size supported by a HT STA
limited to 2 values (3835 and     recipient (3839 or 7935) or the
7935) not 3.                      maximum MPDU size
                                  supported by a VHT STA
                                  recipient (3895, 7991 or
                                  11454) may further limit the
                                  maximum MPDU size."

The caption of Figure 7-1 uses "- Change double dash to one        AGREE. Em dash added with       Ed
-".                               long dash for the consistency.   figure conversion to standard
                                                                   form.
A maximum frame body size of      Correct the figure to show       AGREE IN PRINCIPLE.             MAC
11424B is possible in a QoS       Frame body size range of 0-      Resolution text provided in
Data frame withput HT Control     11426. Replace the note with     11/396r2.
or Address 4. A maximum           one that states how this
frame body size of 11426B is      number is arrived at:
possible in a management          management frame without
frame.                            HT control.
Figure 7-1 caption typo "--".     change '--' to '-'               AGREE IN PRINCIPLE. See         Ed
                                                                   #1002
The style for notes is not     As in comment                  AGREE. Note style applied.   Ed
applied here. Use the style in
the template.
Subtype for control frames not Use 2 reserved values of       Robert                       MAC
defined                        Subtype for defining the
                               subtype of NDPA and for Poll

Show changes to type/subtype As in comment                    Duplicate. See #28.          Ed
fields for new frames (e.g.
control frames) with <ANA> for
number allocations

"MU TXOP" should be defined Insert the following definitions Yusuke                        MU
in section 3.2.               in section 3.2:
                              MU TXOP: A TXOP using MU-
                              MIMO transmission.
The sentence "… during a      Change the sentence into "… Edward                           MU
downlink MU TXOP to           during a downlink SU/MU
indicate..." shows the More   TXOP to indicate...".
Data field will be used in MU
TXOP. Since TXOP power save
can now be used in both MU
and SU modes, the sentence
should be updated accordingly
to include SU TXOP.


Include hyphen in 'MU TXOP'    MU-TXOP                                                     Ed
Why the more data bit is set  The more data bit should be       Allan.   MAC
only to devices that are      set for all active and power
operating in TXOP power save? save mode terminals without
                              restrictions.
                              The more data bit indication
                              helps the non-AP STAs to
                              decide when to change their
                              power mode or when to
                              perform handover to new AP.
                              Change the text in 7.1.3.1.7
                              page 86 line 8 in 802.11
                              revMb: "The More Data field is
                              1 bit in length and is used to
                              indicate to a STA in PS mode
                              that more BUs(#4023) are
                              buffered for that STA at the AP.
                              The More Data field is valid in
                              directed data or management
                              type frames transmitted by an
                              AP to a STA in PS mode. A
                              value of 1 indicates that at
                              least one additional buffered
                              BU(#4023) is present for the
                              same STA."
                              to: "The More Data field is 1 bit
                              in length and is used to
                              indicate to a STA in PS mode or
                              VHT STA in active mode that
The more data bit is set to 1 to   Please use the same more data Allan.   MAC
indicate further buffered          bit values for all devices in
frames and set to 0 to indicate    active mode, regardless are
that no buffered frames are        they operating in TXOP power
present for STAs in power save     save mode. The more data bit
mode.                              indication helps the non-AP
Currently the more data bit is     STAs to decide when to change
set to 0 in all individually       their power mode or when to
addressed frames destined to       perform handover to new AP.
active mode STA. Having the
More Data bit constantly set to
0 in active mode requires very
precise book keeping of the
devices that operate in TXOP
power save.
To simplify AP implementation
the same More Data field
values for all active and power
save mode.




What is the definition of          remove "MU"                   Sandya   MAC
"downlink MU TXOP"? Does
the TXOP power save mode
only apply to MU TXOP?

Since TXOP Power Save has     Change "during a downlink MU Allan.         MAC
been extended to SU, the      TXOP" to "during a downlink
More Data field has to be set MU TXOP and SU TXOP"
to 1 in frames transmitted by
VHT AP during a downlink MU
TXOP and SU TXOP to indicate
to the non-AP VHT STA that AP
has more frames for
transmission when the non-AP
VHT STA is in TXOP power save
mode


The use of More data bit is        Change MU TXOP to SU or MU Allan.      MAC
extended for SU TXOP also          TXOP
"TXOP power save mode"             Insert the following definitions Allan.              MAC
should be defined in section       in section 3.2:
3.2.                               TXOP power save mode: A
                                   power management scheme in
                                   which a non-AP VHT STA may
                                   either be in the Awake or Doze
                                   state during a TXOP obtained
                                   by the VHT AP for VHT
                                   transmissions.

§ 11.1.2.4b appears to be          § 11.2.1.4b                                          Ed
incorrect
section 11.1.2.4b - section        correct it                                           Ed
number is wrong
referred to wrong section          The More Data field is set to 1                      Ed
number 11.1.2.4b                   in frames transmitted by VHT
                                   AP during a downlink MU TXOP
                                   to indicate to the non-AP VHT
                                   STA that AP has more frames
                                   for transmission when the non-
                                   AP VHT STA is in TXOP power
                                   save mode as described in
                                   section 11.1.2.4b 11.2.1.4b.


reference section number           Change "11.1.2.4b" to                                Ed
"11.1.2.4b" is incorrect           "11.2.1.4b"
"For VHT STAs," - I'm not sure     Reorder and reword: "... set to Robert               COEX
this conditional is necessary or   one to signal presence of
sufficient.                        bandwidth indication field as
                                   described in x.y.z. Otherwise,
It is set to one for specific      it is set to zero."
frames sent by a VHT STA to
another VHT STA.
"bandwidth indication" is not a As in comment                        Robert             COEX
defined term - refer to a SAP
parameter. Ditto P52L56

Non-HT duplicate can be used delete the word “control”               Needs discussion   MAC
for Management and Data
frames, so having BW
indication allows reliable BW
determination of these frames
from 11n-2009 specs "7.1.3.1.9    change last bullet including the AGREE. Resolution text in   MAC
Order field                       VHT case: "When set to 1 in a 11/345r0.
The Order field is 1 bit in       QoS data or management
length. It is used for two        frame transmitted with a value
purposes:                         of HT_GF, HT_MF or VHT for
— When set to 1 in a non-QoS      the FORMAT parameter of the
data frame transmitted by a       TXVECTOR, it indicates that the
non-QoS STA, it indicates that    frame contains an HT Control
the frame contains an MSDU,       field.
or fragment thereof, which is     Otherwise, the Order field is
being transferred using the       set to 0.
StrictlyOrdered service class.
— When set to 1 in a QoS data
or management frame
transmitted with a value of
HT_GF or HT_MF for the
FORMAT parameter of the
TXVECTOR, it indicates that the
frame contains an HT Control
field.
Otherwise, the Order field is
set to 0." This does not alllow
for HT control frame in a VHT
PPDU
There is no capability           Add a new capability indication AGREE. Resolution text in     MAC
indication for the HT Control    for the HT control field in the 11/345r0.
field in the new VHT format. A   new VHT format; When
STA may support HTC but not      enabled, the capability
in the new VHT format, or vice   indicates that STA is capable of
versa, but that cannot be        receiving a HT control field
indicated                        with the new VHT format; A
                                 STA shall not receive frames
                                 with HT control field in the VHT
                                 format, unless it declares the
                                 capability in VHT capabilities
                                 info element; A STA shall not
                                 receive frames with HT control
                                 field in the HT format, unless it
                                 declares the capability in HT
                                 Extended capabilities element
                                 (currently called +HTC
                                 capable); VHT format
                                 Capability in VHT capabilities
                                 info can be indicated with 1 bit
                                 in position B22; Section 9.7a
                                 HT Control field operation
                                 need be updated accordingly;




This section now covers both     change from "HT control field"                                Ed
HT and VHT control field.        to "VHT control field"
Should change title to reflect
that.
wrong location of the section    move the section 7.1.3.5a HT      AGREE. Section moved with   Ed
7.1.3.5a HT Control field        Control field to page 8 line 40   REVmb 7.0 as baseline.
                                                                   11/345r0.
This section does not make a       Rename the field "HT/VHT      AGREE IN PRINCIPLE. See #906. MAC
lot of sense as amended.           Control". Define meaning to
Essentially two formats for this   "HT Control" and "VHT
field are described: HT Control    Control" (i.e. format
and VHT Control, distinguished     dependent on B0 setting).
by the setting of B0.              Rework format description for
Elsewhere, the field alternately   clarity.
referred to as HT Control and
VHT Control depending on
context. What is meant by the
name should be explicitly state
here. This section could be
reworked to more clearly
describe the two formats.


Don't get cute with the editing    Remove "intro" editing           AGREE. As suggested.     Ed
instructions. Lists of editing     instruction. Change each of
instructions is being cute.        the following to "change" or
Each must be an insert, delete,    "insert". Replace instruction
change or replace instruction.     at line 15 with figure showing
Replace only for figures.          tracked changes.
Change shows tracked
changes.
HT and VHT control fields       Suggest to introduce a            AGREE IN PRINCIPLE.            Ed
should have two independent     definition for an HT control      Resolution text in 11/345r0.
descriptions. For instance,     field in 'HT format' and one for
referring to this row of the    a HT control field in 'VHT
table, in VHT case MFB (as      format'; HT control field is
shown in the picture below)     defined as [B0=HT/VHT, B1-
includes the SNR, hence HT      B31=depending on HT/VHT
MFB and VHT MFB are             format]; HT format description
different. Also, MAI is not     for B1-B31 reflects 11n-2009
defined for the VHT case        and simply add text specifying
                                that this is the meaning when
                                B0 is set to 0. VHT format has
                                an independent description for
                                B1-B31 which uses the current
                                one in table 7-6h and is valid
                                only when B0 is set to 1; The
                                denomination +HTC is
                                intended to mean that an HT
                                control field is included (either
                                in HT or VHT format); When
                                relevant, the HT or VHT format
                                is explicitly indicated with
                                additional text;




Why have a VHT bit when a        Suggest removing this             DISAGREE. The bit B0 is needed MAC
frame transmission is either    redundant HT/VHT bit. Change       in case of control wrapper.
VHT or HT as indicated by the   "Figure 7-1--MAC frame             Control wrapper can be sent
SIGNAL field in the PHY         format" showing HT/VHT             with non-HT PPDUs, in which
preamble? Suggest removing      control field. Insert text         case B0 defines the type of the
this redundant bit.             indicating "HT/VHT control         field.
After VHT-SIG/HT-SIG auto-      field is a HT control field or a   Discussion on whether the
detection the information       VHT control field depending on     VHTC can be in HT PPDU and
about whether the frame is HT   whether the MPDU is a HT           vice versa;
or VHT may be passed through    MPDU or VHT MPDU
RXVECTOR from PHY to MAC.       respectively."
Also Change "Figure 7-1--MAC
frame format" accordingly.


Don't like HT/VHT field name: Replace field name with                                            Ed
1. contains a slash. 2. doesn't "IsVHT" or just "VHT".
indicate which is selected
when 1.
This modified row of Table 7-       As in comment.                     AGREE. As suggested.          MAC
6a should be removed,                                                  11/345r0.
because MFB subfield in VHT
control field is defined by Table
7-6h.
the definition of MFB/ASELC         if the HT/VHT subfield is set to   COUNTER. Description for HT   MAC
subfield is not accurate when it    the value 0, this subfield         format and VHT format have
is as a subfield of VHT control     contains recommended MFB           been placed in separate
field.                              expressed as an HT MCS, and if     sections. 11/345r0.
                                    the HT/VHT subfield is set to
                                    the value 1, the 4 highest
                                    numbered bits of this subfield
                                    contains a recommended VHT
                                    MCS ,and the lowest
                                    numbered 3 bits of this
                                    subfield contain a
                                    recommended VHT NSTS is
                                    interpreted as defined in
                                    Figure7-4f .

I don't understand why you're I think you need to remove the                                         Ed
describing a VHT MCS format changes at 4.46.
here and also at 7.25.

non-HT or non-HT duplicate                                             Chao-Chun                     COEX
format' includes legacy and
VHT.
non-HT or non-HT duplicate          Need an agreement                  Chao-Chun                     COEX
format' includes legacy and
VHT. Reconsider the definition
of 'non-HT'
Don't need to re-interpret          Remove the mentioned text          AGREE. As suggested.          MAC
MFB/ASELC field in Table 7-6a,      and table 7-6a.                    11/345r0.
because when HT/VHT field is
1, subsequent text, figures and
tables already explain the re-
define HTC field in details,
therefore this table is
redundant.
Table 7-6i defines the MFB          Remove the modifications to                                      Ed
field for VHTC. No need to          this table and add a reference
make changes here.                  to table 7-6i.
Fields such as AC Contstraint       Add them to table 7-6h,        AGREE. Added to the table;        MAC
are not defined.                    perhaps with "see table 7-6a" description points to the HT
                                    as a definition                format. 11/345r0.
Figure 7-4e only contains B1- Add B0 in the Figure 7-4e. The AGREE. As suggested with field MAC
B31. For the integrality of VHT content can be "HT/VHT = 1". name VHT. 11/345r0.
Control field, we propose to
add B0 in the figure.

Table 7-6h: Bits 29-31 of VHT add missing fields                Align with #760, i.e. probably Ed
control field are now defined.                                  just need references to exiting
For integrity, better include all                               definitions.
fields in the table.

Change "Value of 127, it         change accordingly             AGREE. Changed to read "The     Ed
indicates…" to "Value of 127                                    value 127 indicates that no
indicates..."                                                   feedback is present."

"in which the unsolicited MFB    change to "TO which the         AGREE. As suggested and also Ed
refers."                         unsolicited MFB refers."        added article: 'the Coding
                                                                 Type'.
The unsolicited feedback         If the Unsolicited MFB subfield DISAGREE. According to           MAC
should refer to SU or MU VHT     is set to 1 and the FB Tx Type description in 9.18.3, FB Tx
PPDU                             subfield is set to 1, the       Type subfield is set according
                                 unsolicited MFB refers to a     to the Beamformed indication
                                 beamformed SU-MIMO or MU- in SIG-A2, which only refers to
                                 MIMO VHT PPDU.                  SU case. The receiver of
                                                                 unsolicited feedback can use
                                                                 the GID(L and H) to determine
                                                                 if feedback is referred to an SU
                                                                 or MU PPDU.


Grammer:                         Change the sentence to "If the AGREE. As suggested.            Ed
"If the Unsolicited MFB          Unsolicited MFB subfield is set
subfield is set to 1 and FB Tx   to 1 and FB Tx Type subfield is
Type subfield is set to 0, the   set to 0, the unsolicited MFB
unsolicited MFB refers to        refers to either unbeamformed
either unbeamformed VHT          VHT PPDU or VHT PPDU with
PPDU, transmit diversity         STBC."
utilizing Alamouti coding VHT
PPDU."

The terminology 'Alamouti        Change 'Alamouti coding' to    AGREE. Modified to "using an    Ed
coding' is not used in REVmb     'STBC'                         STBC VHT PPDU".
4.01.
"….. refers to either             change to ""….. Refers to either AGREE. See #1004                 Ed
unbeamformed VHT PPDU,            unbeamformed VHT PPDU or
transmit diversity utilizing ….." transmit diversity utilizing ….."
What's the grammar there?
Shouldn't be "either….or……"?

The terminology 'Alamouti       modify 'Alamouti coding' to  AGREE. See #1005.                      Ed
coding' is not used in spec     'STBC'
For the Definition of FB Tx     change to "...either         AGREE. See #1004.                      Ed
Type, seems missing "or"        unbeamformed VHT PPDU, or
                                transmit diversity utilizing
                                Alamouti coding VHT PPDU.

"Nsts" should be defined in     Insert the following definitions      AGREE IN PRINCIPLE. Defined MAC
section 3.2 as well as "MCS".   in section 3.2:                       N_STS as acronym in section
                                Nsts: The number of space-            3.3 as per 11/345r0. (Editor: I
                                time streams.                         don't see the resolution text
                                                                      for MCS in 11/345r0. Also, use
                                                                      of subscripts in an acronym is
                                                                      questionable since it confuses
                                                                      the acronym with the
                                                                      parameter)

"SNR subfield contains the     add reference to formula 9-1                                         Ed
average SNR, which is a SNR
averaged over data subcarriers
and spatial streams": add
reference to formula

Need to describe how to set     Insert in table 7-6i: Nsts field is   AGREE IN PRINCIPLE. Added       MAC
Nsts, MCS and SNR fields in     set to true Nsts-1, MCS field is      reference to section 9.18.3
table7-6i.                      set to MCS, SNR field refer to        (Link Adaptation using the VHT
                                (9-1) in 9.18.3.                      control field), where more
                                                                      details are provided. 11/345r0.

Clause 7.1.3.5.1 is not under   Allocate the clause 7.1.3.5.1 in AGREE. Fixed with section          Ed
Clause 7.1.3.5.a but under      page under 7.1.3.5 QoS control renumbering.
Clause 7.1.3.1.                 field.
Clause 7.1.3.5.1 is now below   Allocate the clause 7.1.3.5.1 in AGREE. See #90.                    Ed
Clause 7.1.3.5a. The clause     page under 7.1.3.5 QoS control
should be below Clause          field.
7.1.3.1.
If AP transmits QoS Null+MRQ Describe a clear behavior.         Illsoo has proposed resolution MU
in MU-MIMO, MFB
transmitters respond with
immediate ACK and cause ACK
collisions. Therefore, the ACK
policy under the case where
QoS Null+MRQ is transmitted
in MU-MIMO is required. The
ACK policy for the case should
be defined as No ACK policy or
BA policy.

When QoS-Null+MRQ is sent in Define the behavior such as no Byeongwoo has presentation          MU
MU-MIMO, MFB transmitters ack policy or block ack policy
transmit immediate ACK and,
hence, have ACK collisions with
each other. Therefore, the ACK
policy for QoS Null+MRQ in
MU-MIMO needs modification.


"an A-MPDU subframe with         As in comment.                 Yusuke                          MAC
EOF subfield of the A-MPDU
delimiter field set to 1" should
be replaced with "VHT single
MPDU", because "VHT single
MPDU" is defined as "an MPDU
that is the only MPDU carried
in an A-MPDU carried in a VHT
PPDU, and with the EOF
subfield of the MPDU delimiter
field equal to 1".


Now that you have a definition change to "... or carried in a   Yusuke                          MAC
of a single VHT MPDU, you can single VHT MPDU".
use that definition to simplify
text.                           And change the guard on the
                                next block to "Otherwise:"

"A-MPDU delimiter" should be As in comment.                     DISAGREE. Correct term is "A-   Ed
replaced with "MPDU                                             MPDU delimiter".
delimiter".
Include hyphen in 'HT delayed' HT-delayed                       AGREE. Hyphen added.            Ed
In a VHT frame, the Duration Define a mechanism to reuse          COUNTER. See #479.              MAC
field will not be decodable by Duration Field.
most third party STA due to its
beamformed nature. It will be
beneficial to reuse the field for
other purposes, e.g. to indicate
BA transmission timing.


The enhanced RTS CTS               Please reserve static RTS         Jarkko presented (383r0, 384r0 COEX
signaling as defined in            values 72 - 132 to indicate       is the normative text). Jarkko
802.11ac has many challenges:      probing operation and             will work further and discuss
1. Long duration in RTS frame      calculate the value of the CTS with others.
may lead to unnecessary            duration field by (RTS duration -
locking of the NAV at the          72)*32 micro seconds. If the
secondary channels, if a frame     requested bandwidth is
is transmitted within the CTS      available for transmission. If
timeout. For instance, two RTS     the requested bandwidth was
frames that are transmitted in     not available send CTS to
a short time may lock a NAV        available channels and set the
for the channel.                   duration field to RTS duration -
2. Also the STA that transmits     (SIFS + CTS).
static RTS frame should get
indication if the reservation
was not done due to lack of
bandwidth, i.e. not because
hte transmission of RTS frame
failed. This enables the backoff
rules use with static RTS frame.
3. The device that wants to
test available bandwidht with
dynamic RTS including short
duration is forced to perform
second RTS CTS signaling to set
the duration of the reservation
correctly. Two RTS CTS
signaling causes overhead.
"The TA field is the address of    Change first sentence to cite all Jarkko. 383r0 covers this.   COEX
the STA transmitting the RTS       the bits of the TA address field,
frame. If the RTS frame is         except the Individual/Group
transmitted by a VHT               bit.
STA in a non-HT or non-HT
duplicate format and the
INDICATED_CH_BANDWIDTH
and
INDICATED_DYN_BANDWIDTH
TXVECTOR parameters
present, then the
Individual/Group bit in the
TA field is set to 1 to indicate
that the scrambling sequence
carries a bandwidth and
dynamic/static indication
(see section 17.3.2.1)."

The first sentence conflicts
with the second.

Section 9.2.0b.6a has defined Replace "present" with "are           Brian.                        COEX
how to determine the two        valid"
parameters are valid or not.
The term "valid" is used
consistently throughput
section 9.2.0b.6a and 9.2.0b.7.
Note that the two parameters
may be present in RXVECTOR
even though they may not be
valid.


Clarify what a third party non- Clarify.                            Chao-Chun                     COEX
VHT STA will do when receiving
an RTS frame with Group bit
set to 1.
"response is transmitted in a Move to a behavioural                                               Ed
non-HT or non-HT duplicate      subclause
format with the
INDICATED_CH_BANDWIDTH
TXVECTOR parameter
present."

This is a description of
behaviour, not structure
The legacy devices and OBSS        Append line 7 with the text:     Jarkko presented (383r0, 384r0 COEX
devices are not necessarily        "VHT TXOP holder may             is the normative text). Jarkko
capable to obtain increased        transmit a CTS with the RA       will work further and discuss
NAV duration from the              field set to its MAC address."   with others.
transmitted frames. The
CTS_To_self frame should be
possible to transmit during the
TXOP to lengthen the NAV
duration for the reserved
bandwidth or the subset of the
reserved bandwidth.


"NDPA" in TGac D0.1 is a           To avoid confusion, the name     DISAGREE. (Approved               Ed
control frame to inform the        of "NDPA" in TGac D0.1 should    resolution did not provide
existence of an NDP of VHT         be changed to "VHT NDPA          reason, but the editor feels this
format following NDPA itself       frame".                          NDPA as an acronym similar to
and specify the following                                           BAR or RTS is a suitable name.
sequence (the order and the                                         Also there is no confusion, at
number of users to be                                               least in the editor's mind,
requested CSI feedback). On                                         between this frame and the
the other hands, "NDP                                               NDP Announcement field in HT
Announcement" in                                                    Control) 11/346r0.
REVmbD4.01 is just one-bit flag
to inform whether an NDP of
HT format follows a control
frame that includes HT Control
field or not as described in
7.1.3.5a.
The terms between "NDPA" in
TGac D0.1 and "NDP
Announcement" in
REVmbD4.01 are almost
identical phrase but the
definitions are quite different,
which may make confusion.


NDPA is a control frame;        Add a new subtype for NDPA in AGREE. Table row added,                Ed
however, there is no definition Table 7-1.                    awaiting ANA for subtype
of subtype in Table 7-1 and                                   assignment.
should be added.

The title of 7.2.1.11 should be As in comment.                      AGREE. As suggested. Similar Ed
revised to "VHT NDPA frame                                          modification for Sounding Poll
format".                                                            section (7.2.1.12).
The rule for setting              Add the sentences for         AGREE IN PRINCIPLE. Changed MU
Duration/ID field in NDPA is      Duration/ID setting rule      8.2.5 which defines general
not defined in the draft.         definition.                   rules for setting the Duration
                                                                field. 11/346r0.

although "NDPA" acronym is        as per comment                DISAGREE. As with RTS or CTS, Ed
defined, its first use in a                                     the acronym definition should
subclause heading should be                                     be sufficient.
"Null Data Packet
Announcement (NDPA)"
instead.
Syntactically, frame names        insert "frame" after NDPA     AGREE. See #29               Ed
are adjectives, requiring         throughout.
"frame" after each use.

Reduce the sounding sequence      Reduce the sounding sequence AGREE. Resolution text in     MU
number in NDPA to 6 bits; this    number in NDPA to 6 bits,     11/346r0.
is still a sufficient number of   Reserved bits are in position
bits and allows for 2 reserved    128-129
bits; it also matches with
another proposal from another
comment about reducing the
sequence number from 8 to 6
in sounding Poll frame


Being picky here, but the         As in comment                 AGREE. As suggested.         Ed
Octets: should be in an
unruled column to the left of
the frame control field.
The text provides a reference      The duration/ID value of the      AGREE IN PRINCIPLE. Changed MU
to sub-section 7.1.4 for the       NDPA frame is the time, in        8.2.5 which defines general
definition of the duration/ID      microseconds, that covers the     rules for setting the Duration
field of the NDPA. However,        transmission of all NDPs,         field. 11/346r0.
sub-clause 7.1.4 provides the      compressed feedback reports
definition for the duration/ID     from the STAs that are
field for Management and Data      indicated in the NDPA, and
frame and NDPA is a control        multiple SIFS between
frame. Need a definition for       tranmissions. For example, if
duration/ID field of the NDPA      the NDPA contains n number
frame.                             of STAs, the duration is, in
                                   microseconds, the sum of the
                                   following frames: 1xNDP, (n-
                                   1)xSounding Poll frames plus
                                   nxCompressed feedback report
                                   frames plus 2nxSIFS. If the
                                   sounding poll frame is replaced
                                   by NDP (see next comment
                                   regarding the sounding poll
                                   frame) then the duration value
                                   of NDPA is the sum of nxNDP
                                   plus nxCompressed feedback
                                   frames plus 2nxSIFS




Grammer:                           Chage the sentence to "then       AGREE. As suggested.        Ed
"then the RA field is set to the   the RA field is set to the
address STA identified by the      address of the STA identified
STA ID in the STA Info field."     by the STA ID in the STA Info
                                   field."
Include 'of the' after '… to the   to the address of the STA         AGREE. See #1008            Ed
address …'
change "field is set to the      as comment                          AGREE. See #1008            Ed
address STA" to "field is set to
the address of the STA"
the RA field is set to the       change to: "the RA field is set     AGREE. See #1008            Ed
address STA                      to the address OF THE STA"

"set to the address STA" should change accordingly                   AGREE. See #1008            Ed
be "addressed STA"
Include 'Figure' before 7.2     Figure 7.2                           AGREE. Fixed with updated   Ed
                                                                     referencing.
The caption of Figure 7-2 uses "- Change double dash to one         AGREE. Fixed with conversion   Ed
-".                               long dash for the consistency.    of figure to table

This is the first time Nc        edit appropriately                 DISAGREE. Field definition     Ed
(Number of Column) is used. It                                      given in Table 7-1.
should be spelled out in full
here or in Table 7-1. Also there
is neither definition nor
acronym defined for Nc.

Review all figure captions and    As in comment                     AGREE. As suggested.           Ed
ensure they are given FigTitle
style
Section 9.2.0b.6a has defined     Replace "with the           Chao-Chun                            COEX
how to determine the two          INDICATED_CH_BANDWIDTH
parameters are valid or not.      TXVECTOR parameter present"
The term "valid" is used          with "with a valid
consistently throughput           INDICATED_CH_BANDWIDTH
section 9.2.0b.6a and 9.2.0b.7.   TXVECTOR parameter"
Note that the two parameters
may be present in RXVECTOR
even though they may not be
valid.


Duplicated Figure number.         Change figure number 7-2 to       AGREE. Figures renumbered.     Ed
Figure number 7-2 is already      other non duplicated number
used in the 802.11 baseline
document
Clarification:                    Change the sentence to "The       AGREE. As suggested.           Ed
"The subfields in the STA Info    subfields in the STA Info field
are described in Table 7-1"       are described in Table 7-1"

Fix table number. It's not table As in comment                      AGREE. New tables and figures Ed
7-1.                                                                renumbered.
There is no STA ID section in    Add STA ID section. To use a       Simone has proposed           MU
the draft.                       part of AID (lowest 12 bits) as    resolution
                                 STA ID is one of possible
                                 solutions.
Add description of STA ID        AID of the STA expected to         AGREE. Also, name AID is used MU
                                 prepare for the sounding           instead of STA ID. 11/346r0.
                                 feedback
STA ID <Add reference to STA add reference                          AGREE. See #762.               Ed
ID section>
Detailed description for STA ID Put definitions on STA ID.          AGREE. See #762.               Ed
subfield is missing.
STA ID reference missing          add reference and detailed      AGREE. See #762.              Ed
                                  description
No details for STA ID subfield.   Write details.                  AGREE. See #762.              Ed

There is no description for the add reference                   AGREE. See #762.                Ed
"STA ID" field.
There is no "STA ID section" in Create "STA ID section" in the AGREE. See #762.                 Ed
the current document            draft and add reference to it,
                                or add description on STA ID in
                                the table 7-1

Reference to STA ID section is Correct the description.           AGREE. See #762.              Ed
missing
According to 22.3.13, NDP shall Remove the sounding poll          Illsoo. 11/378r4. (Editor: I  MU
be the only sounding format. frame from this sub-clause.          originally had this as being
The use of sounding poll frame                                    addressed by 11/378 but that
violates this rule                                                does not seem to be the case.
                                                                  Needs reassignment.)

Sounding Poll is a control      Add a new subtype for             AGREE. Table row added,       Ed
frame; however, there is no     Sounding Poll frame in Table 7-   awaiting ANA for subtype
definition of subtype for       1.                                assignment.
Sounding Poll frame in Table 7-
1.
Figure of Poll frame need be                                      AGREE. Figure replaced with   Ed
improved                                                          more standard tabel form
                                                                  drawing.
There are two TBDs for this       resolve TBDs                    AGREE. See #141 and #1446.    Ed
frame.
The Duration field is not         Change to "The Duration field AGREE. As suggested.            MU
defined.                          is set as defined in 7.1.4
                                  (Duration/ID field (QoS STA))."

Why is Duration field TBD?    Define the duration field.          Duplicate. See #141.          MU
Once the sounding sequence is
defined, the duration of the
sequence can be determined.

Add setting of Duration field     as comment                      Duplicate. See #141.          MU

The Duration field is set to      Replace with: "Duration is set Duplicate. See #141.           MU
TBD.                              according to 7.1.4.2;
                                  Beamformer should set a value
                                  long enough to protect the
                                  completion of the sounding
                                  sequence"
TBD in Duration field              Find appropriate field design.    Duplicate. See #141.         MU

There are two TBDs in this         un-tbd them                       AGREE IN PRINCIPLE. See #141. MU
subclause                                                            Statement regarding additional
                                                                     fields removed (Ed).

If the sounding response is   resolve and finalized TBD fields AGREE IN PRINCIPLE.                MU
segmented due to limits of    of sounding poll frame           Resolution text provided in
MPDU, the sounding poll frame                                  11/378r4.
should contain information
regarding segment information

Duration field can be decided.     Defined the Duration field as     Duplicate. See #141.         MU
The duration field of Sounding     following:
Poll use same duration             The Duration field is set to as
protection with the duration of    defined in 7.1.4.
NDPA. If the Duration field in
the NDPA is set to the
remaining duration of the
TXOP, the duration field in
sounding poll is set to the
remaining duration of the
TXOP too. If the Duration field
in the NDPA is set to a NAV
value at receiving STAs that
protects up to the end of any
following frame plus any
additional overhead frames,
the duration field in sounding
poll is set to a NAV value at
receiving STAs that protects up
to the end of any following
frame plus any additional
overhead frames too.




Define the additional fields, if   As in comment                     AGREE. Statement removed.    Ed
any, in the sounding poll
frame. If there is no additonal
field, remove the statement.

TBD should not exists in the       Define appropriate value for      AGREE. See #141 and #1446.   Ed
standard                           TBD fields.
Add the "additional fields"        as comment                        AGREE IN PRINCIPLE. See      MU
                                                                     #1446. Resolution text
                                                                     provided in 11/378r4.
In current specification, a       Add a new Segment              AGREE IN PRINCIPLE. See        MU
Sounding Poll frame may           Information subfield in the    #1446. Resolution text
include some additional fields    Sounding Poll frame to support provided in 11/378r4.
to improve sounding               selective retransmission of
procedures. The following is      segments in a VHT Compressed
one suggestion for the usage of   Beamforming frame.
new fields.
VHT Compressed Beamforming
Report field can grow up to
approximately 26Kbytes, which
is larger than the maximum
allowed MPDU limit for
management frames. This
makes a VHT Compressed
Beamforming frame in the
form of A-MPDU. Since each
MPDUs in the A-MPDU can be
checked with individual FCS
whether the transmission is
success or not, selective
retransmission of only failed
segments in the A-MPDU can
considerably increase the
transmission efficiency in
sounding procedures. To
support the selective
retransmission of segments in
VHT Compressed Beamforming
"The Sounding Poll frame may      Delete statement                 AGREE. Statement removed.    Ed
include additional fields TBD."
This seems to allow
implementers to add fields at
will.
In link adaptaion (LA)            Add 'LA field' in the sounding   Illsoo has proposed resolution MU
operation, QoS-Null+MRQ can poll frame.
be sent in MU-MIMO. In this
case, polling frame for non-first
STAs' MFB is needed. One
option is to add one field in
sounding poll frame because
there is TBD field in sounding
poll frame.
There can be an additonal field Include a new field that       AGREE IN PRINCIPLE. See   MU
for Sounding Poll. Since VHT    indicates segment information. #1446. Resolution text
Compressed Beamforming                                         provided in 11/378r4.
Report may be segmented in
some cases, selective
retransmission of segmented
Compressed Beamforming
Report should make feedback
process efficient. To support
this retransmission procedure,
a new field which indicates the
segment information needs to
be adopted in Sounding Poll
frame.




Add sequence number to Poll Add required sequence            Reference 7.2.1.12 at       MU
frame to enable BFer to         number of Poll frame.        commenters request
control which CV is returned. A
Bfee that cannot comply with
the request shall return a Null
CV frame. This would save
overhead and simplify BFer
implementation since it will
not need to process the
sequence number and match it
to past NDPs
By my calculation, the           Change 11422 to 11426. An      AGREE IN PRINCIPLE.            MAC
maximum Frame Body size in a     argument could be made that Resolution text provided in
management frame is 11426        the Frame Body should be       11/396r2.
(not 11422) since the frame      limited to 11422 since the
may not include the HT Control   frame may dynamically include
field.                           HT Control based on lower
                                 MAC operation (e.g. link
                                 adaptation) and you wouldn’t
                                 want that to impact upper
                                 MAC functionality. However,
                                 this is an implementation
                                 consideration and the
                                 implementer could constrain
                                 the upper MAC
                                 implementation to always use
                                 the smaller size if there is a
                                 possibility that the lower MAC
                                 will dynamically insert HT
                                 Control.




Figure 7-18 describes the  change 'MAC' to 'Management' AGREE. As suggested.                   Ed
format of management frame

caption of Figure 7-18 in 11n    Change "MAC frame format" to AGREE. See #1475                 Ed
spec is "Management frame        "Management frame format"
format"
Duplicated Table number.         Change table number 7-1 to    AGREE. All tables and figures   Ed
Talbe number 7-1 is already      other non duplicated number   renumbered.
used in the 802.11 baseline
document
Both the transmitter of the RTS      Add the primary channel of the Jarkko to present      COEX
and the transmitter of the CTS       OBSS that is the most active
perform CCA on the secondary         and proxy MAC address
channels to ensure that the          information elements to
TXOP does not collide with           Beacon frame. AP sets these
ongoing TXOPs on the                 fields to recommend to
secondary channels. The CCA is       address RTS frames to proxy to
not as good protection as the        capture the NAV of both BSSs
virtual carrier sensing, i.e. NAV.   primary channels.
The STAs may set the RA of the
RTS message to other STA
address in OBSS. Thus the RTS
frame may be transmitted if
the NAV of the own BSS is hot
set and CTS may be
transmitted if hte NAV in the
OBSS is not set. Thus, the NAV
information of the OBSS may
be considered and hidden
terminal problems may be
avoided.
The Beacon should provide the
primary channel of hte OBSS
and recommended MAC
address of the proxy STA that
is a STA in OBSS and it may be
available to respond to RTS
messages when non-AP STAs
Modify the notes to the HT           as comment                     Yong                   MAC
Capabilities element and HT
Operation element with "the
HT Capabilities element / HT
Operation element is present
when the
dot11VHTOptionImplemented
attribute is true"

Cut and paste error                  Capabilities -> Operation      Duplicate. See #1810   Ed

Ditto 11.59, 12.30, 13.09
Note is incorrect                    Change "VHT Capabilities       Duplicate. See #1810   Ed
                                     element" to "VHT Operation
                                     element"
The notes describing VHT           The VHT Operation element is Duplicate. See #1810              Ed
Operation is the same as VHT       present when the
Capabilities which appears to      dot11VHTOptionImplemented
be incorrect                       attribute is true

(Table 7-8) Notes for VHT        Change Entry in Table 7-8 row Duplicate. See #1810             Ed
Operation and VHT Capabilities 2 col 3
are identical
In Tables 7-8, 7-11, 7-13, 7-15, as per comment                AGREE. As suggested and          Ed
the Notes corresponding to                                     applied to Tables 8-19, 8-22, 8-
'VHT Operation' should refer to                                24 and 8-26 (new numbering).
"VHT Operation" instead of
"VHT Capabilities".

Section number of "Association Change section number to         AGREE IN PRINCIPLE. Section       Ed
Request frame format" in       7.2.3.4                          numbers renumbered for
baseline document is 7.2.3.4                                    REVmb 7.0 baseline

Section number of "Association Change section number to         AGREE IN PRINCIPLE. Section       Ed
Response frame format" in      7.2.3.5                          numbers renumbered for
baseline document is 7.2.3.5                                    REVmb 7.0 baseline

Note is incorrect                  Change "VHT Capabilities     Duplicate. See #1810              Ed
                                   element" to "VHT Operation
                                   element"
The notes describing VHT           The VHT Operation element is Duplicate. See #1810              Ed
Operation is the same as VHT       present when the
Capabilities which appears to      dot11VHTOptionImplemented
be incorrect                       attribute is true

(Table 7-11) Notes for VHT         Change Entry in Table 7-11   Duplicate. See #1810              Ed
Operation and VHT Capabilities     row 2 col 3
are identical
Section number of                  Change section number to     AGREE IN PRINCIPLE. Section       Ed
"Reassociation Request frame       7.2.3.6                      numbers renumbered for
format" in baseline document                                    REVmb 7.0 baseline
is 7.2.3.6
The editing instruction should     As in comment                AGREE. As suggested (or            Ed
be Insert row for order 19 after                                similar) for Tables 8-19, 8-21, 8-
order 18 in table 7-12 as                                       22, 8-23, 8-24, 8-25, 8-26.
follows:
Section number of                  Change section number to     AGREE IN PRINCIPLE. Section       Ed
"Reassociation Response frame      7.2.3.7                      numbers renumbered for
format" in baseline document                                    REVmb 7.0 baseline
is 7.2.3.7
The notes describing VHT        The VHT Operation element is Duplicate. See #1810            Ed
Operation is the same as VHT    present when the
Capabilities which appears to   dot11VHTOptionImplemented
be incorrect                    attribute is true

(Table 7-13) Notes for VHT     Change Entry in Table 7-13      Duplicate. See #1810          Ed
Operation and VHT Capabilities row 2 col 3
are identical
Note is incorrect              Change "VHT Capabilities        Duplicate. See #1810          Ed
                               element" to "VHT Operation
                               element"
Section number of "Probe       Change section number to        AGREE IN PRINCIPLE. Section   Ed
Request frame format" in       7.2.3.8                         numbers renumbered for
baseline document is 7.2.3.8                                   REVmb 7.0 baseline

Order number is incorrect       Change "row with Order 19      AGREE. Fixed with alignment to Ed
                                following row with Order 18"   REVmb 7.0
                                to "row with Order 10
                                following row with Order 9"

Section number of "Probe        Change section number to       AGREE IN PRINCIPLE. Section   Ed
Response frame format" in       7.2.3.9                        numbers renumbered for
baseline document is 7.2.3.9                                   REVmb 7.0 baseline

The notes describing VHT        The VHT Operation element is Duplicate. See #1810            Ed
Operation is the same as VHT    present when the
Capabilities which appears to   dot11VHTOptionImplemented
be incorrect                    attribute is true

(Table 7-15)Notes for VHT      Change Entry in Table 7-15      Duplicate. See #1810          Ed
Operation and VHT Capabilities row 2 col 3
are identical
Note is incorrect              Change "VHT Capabilities        Duplicate. See #1810          Ed
                               element" to "VHT Operation
                               element"
TBD for Robust                 Further specification required. Yong                          MAC

VHT Action Management           Change Robust value from TBD Yong                            MAC
packets contain time critical   to No.
information, so they should
not be Robut Action
Management Packets.

TBD should not exists in the    Define appropriate value for   Yong                          MAC
standard                        TBD fields.
Robust field is TBD             resolve TBDs                   Yong                          MAC
reference subcluase number       Change "7.4.11" to "7.4.12"    AGREE IN PRINCIPLE. Section   Ed
"7.4.11" is incorrect                                           numbers renumbered for
                                                                REVmb 7.0 baseline

Specify how the absence of the   Use a reserved combination     AGREE IN PRINCIPLE.           MU
Bemaforming report field is      (1110) of bits 12-15; this     Resolution text provided in
indicated in the VHT MIMO        choice is compliant with the   11/378r4.
control field                    proposal presented in a
                                 different comment, referred to
                                 the indication of the segment
                                 numbering

The VHT MIMO Control field                                      AGREE IN PRINCIPLE. See #919. MU
needs a way of specifiying null                                 Resolution text provided in
feedback                                                        11/378r4.
Acronym for Nr is not defined define acronym                                                  Ed

Duplicated Figure number.        Change figure number 7-3 to      AGREE. All figures and tables Ed
Figure number 7-3 is already     other non duplicated number      renumbered to align with
used in the 802.11 baseline                                       REVmb 7.0, with unique
document                                                          assignments for new figures
                                                                  and tables.
The number of bits in the        Set B8 to be reserved (similar DISAGREE. There is no reason MU
"Channel Width" in Figure 7-3    to the BW index in VHT-SIG-A), to change. Two bits are fine as
is not consistant with that of   and shift B8-B11 to the right by it is.
"BW" in VHT-SIG-A.               one bit. Remark: The other
                                 MAC frame should follow the
                                 same changes.

The description does not sound Fix description                  AGREE IN PRINCIPLE. Grouping MU
accurate: "Number of carriers                                   is defined as “Grouping is a
grouped into one". Is there                                     method that reduces the size
some averaging going on or are                                  of the VHT Compressed
subcarriers just skipped?                                       Beamforming Report field by
                                                                reporting a single value for
                                                                each group of Ng adjacent
                                                                subcarriers” in 7.3.1.32. The
                                                                sentence needs to be clarified
                                                                with the reference.
The terms "SU-BF" and "MU-        "Set to 0 to indicate that the       AGREE IN PRINCIPLE. Editorial MU
BF" are undefined. Also, the      feedback is for SU-MIMO              correction required but details
description is incomplete since   Beamforming. For SU-MIMO             on different numbers of
the VHT Compressed                Beamforming, the VHT                 feedback bits seems not
Beamforming Report field is       Compressed Beamforming               appropriate in the table. Those
also different depending on       Report uses fewer bits phi and       should be written in 7.3.1.32 if
the setting (the codebook         psi (see Condebook                   necessary.
changes).                         Information field) and VHT
                                  Compressed Beamforming
                                  frame does not include the MU
                                  Exclusive Beamforming Report
                                  field (see ). Set to 1 to indicate
                                  that the feedback is for MU-
                                  MIMO Beamforming. For MU-
                                  MIMO Beamforming, the VHT
                                  Compressed Beamforming
                                  Report uses more bits for phi
                                  and psi and the VHT
                                  Compressed Beamforming
                                  frame includes the MU
                                  Exclusive Beamforming Report
                                  field."




(Table 7-2) Order of rows is      Interchange rows 5 and 6 of          AGREE. As suggested.        Ed
mismatched with order of          Table 7-2 to match the frame
fields in frame format            format figure.(Fig 7-3)

In Table 7-2, the order of Change the order.                           Duplicate. See #923         Ed
Feedback Type and Codebook
information is wrong.

Table 7-2 is wrong.           Change the order of Feedback Duplicate. See #923                     Ed
                              type and codebook
                              information.
The reference section for "MU Add the reference section    AGREE. Reference added.                 Ed
Exclusive Beamforming Report number of 7.3.1.62.
field" is missed.

Fill the clause number in the     The clause number should be          Duplicate. See #33          Ed
brackets.                         updated to "(see 7.3.1.33)".

No reference is referred in       Add the reference as (see xxxx) Duplicate. See #33               Ed
Feedback Type set to 0.
Missing reference                                                      Duplicate. See #33          Ed
No reference in Feedback Type Add the reference as (see xxxx)        Duplicate. See #33           Ed
= 0.
Missing reference in Table7-2 Set to 0 if the feedback report        Duplicate. See #33           Ed
                              is for SU-BF. If it is set to 0, the
                              feed-
                              back report frame shall not
                              include the MU Exclusive
                              Beamforming
                              Report field (see 7.3.1.33)
missing reference to the MU   add reference (7.3.1.33)               Duplicate. See #33           Ed
Exclusive Beamforming Report
field
section reference is missing  Change "(see )" to "(see               Duplicate. See #33           Ed
                              7.3.1.33)
Correct the clause number.    The clause number should be            AGREE. Reference corrected   Ed
                              updated to "(see 7.3.1.33)".           (note new clause number).

Invalid reference                                                Duplicate. See #104              Ed
section reference is incorrect   Change "7.3.1.62" to "7.3.1.33" Duplicate. See #104              Ed

use 'bits' instead for 'bit', when                                   Duplicate. See #34           Ed
appropriate
"bit" should be replaced with Modify Table 7.2 by replacing AGREE. As suggested.                  Ed
"bits".                            "bit" with "bits" in Codebook
                                   Information subfield as shown
                                   below:
                                   If Feedback Type is set to 0 (SU-
                                   BF)
                                   Set to 0 for 2 bits for ψ, 4 bits
                                   for φ
                                   Set to 1 for 4 bits for ψ, 6 bits
                                   for φ
                                   If Feedback Type is set to 1
                                   (MU-BF)
                                   Set to 0 for 5 bits for ψ, 7 bits
                                   for φ
                                   Set to 1 for 7 bits for ψ, 9 bits
                                   for φ
VHT Compressed Beamforming         Clarify the reporting         Illsoo has proposed resolution MU
Report field can grow up to        procedures when VHT
approximately 26Kbytes, which      Compressed Beamforming
is larger than the maximum         Report field can grow up to
allowed MPDU limit for             approximately 26Kbytes, which
management frames.                 is larger than the maximum
As the current specification       allowed MPDU limit for
does not support CB report to      management frames.
be made for some of the valid      Segmentation and PPDU
configurations it is broken. fix   trasmission in the form of A-
this.                              MPDU can be one solution.


Maximum size of VHT                support segmentation and     Illsoo has proposed resolution MU
Compressed Beamforming             transmission of segmented CB
report is more than 26Kbytes.      report and add appropriate
Segmentation of these large        description
payload should be considered.

A missing reference.               The VHT Compressed                AGREE. Reference added.   Ed
                                   Beamforming Report field is
                                   used by the VHT Compressed
                                   Beamforming frame
                                   (see7.4.12.2) to carry explicit
                                   feedback information

In some cases, VHT                 Clarify the behavior when VHT Illsoo has proposed resolution MU
Compressed Beamforming             Compressed Beamforming
Report field can grow over the     Report grows over limit. Some
limit of MPDU.                     segmentations may be
                                   required.

There is no reference for VHT      Insert "7.4.14.2" after "(see".   Duplicate. See #1477      Ed
Compressed Beamforming
frame.




Fill the clause number in the      The clause number should be       Duplicate. See #1477      Ed
brackets.                          updated to "(see 7.4.12.2)".

missing reference to VHT           add reference                     Duplicate. See #1477      Ed
Compressed Beamforming
frame
section reference is missing       Change "(see )" to "(see          Duplicate. See #1477      Ed
                                   7.4.12.2)
add missing reference in "(see as per comment                      Duplicate. See #1477            Ed
)"
(see), clause number is missing add the right clause number        Duplicate. See #1477            Ed

Missing reference                                                  Duplicate. See #1477            Ed
reference missing                                                  Duplicate. See #1477            Ed

Duplicated Table number.         Change table number 7-2 to        AGREE. All figures and tables   Ed
Talbe number 7-2 is already      other non duplicated number       renumbered to align with
used in the 802.11 baseline                                        REVmb 7.0, with unique
document                                                           assignments for new figures
                                                                   and tables.
The positions of "Feedback       Exchange their positions for      Duplicate: See #923             Ed
type" and "Codebook              consistency.
Information" in Table 7-2 are
different from those in Fig 7-3.

"bit" should be "bits" for ψ     change accordingly                Duplicate. See #34              Ed

It is unecessary to have          Combine into a single table.     Youhan. 11/422                  Ed
separate tables for Nr = 5, 6, 7.

(Table 7-3) Change 'Quantized    Change 'Quantized Steering' to                                    Ed
Steering' to 'Quantized          'Quantized Beamforming' for
Beamforming' for consistency     consistency with Tables 7-4, 7-
with Tables 7-4, 7-5 etc         5 etc

Duplicated Table number.         Change table numbers 7-3 and AGREE. All figures and tables        Ed
Table number 7-3 and 7-4 are     7-4 to other non duplicated  renumbered to align with
already used in the 802.11       number.                      REVmb 7.0, with unique
baseline document                                             assignments for new figures
                                                              and tables.
Duplicated Table number.         Change table numbers 7-5 and AGREE. All figures and tables        Ed
Table number 7-5 and 7-6 are     7-6 to other non duplicated  renumbered to align with
already used in the 802.11       number                       REVmb 7.0, with unique
baseline document                                             assignments for new figures
                                                              and tables.
Duplicated Table number.         Change table number 7-7 to   AGREE. All figures and tables        Ed
Table number 7-7 is already      other non duplicated number renumbered to align with
used in the 802.11 baseline                                   REVmb 7.0, with unique
document                                                      assignments for new figures
                                                              and tables.
Duplicated Table number.         Change table number 7-8 to   AGREE. All figures and tables        Ed
Table number 7-8 is already      other non duplicated number renumbered to align with
used in the 802.11 baseline                                   REVmb 7.0, with unique
document                                                      assignments for new figures
                                                              and tables.
It is unecessary to have           Combine tables into one using Youhan. 11/422       Ed
separate tables for 20 MHz, 40     parameters similar to Table 7-
MHz and 80 MHz.                    13.
Duplicated Table number.           Change table number 7-9 to                         Ed
Table number 7-9 is already        other non duplicated number
used in the 802.11 baseline
document
The name of the field and the     Change meaning to               Youhan. 11/422      Ed
meaning seem inconsistent         "Beamforming feedback marix
                                  V for subcarrier k=-28. Similar
                                  throughout.
Beamforming Feedback Matrix Erase the row of 'Beamforming Youhan. 11/422              Ed
V for carrier 2 is not in case of Feedback Matrix V for carrier
Grouping=4 (Refer Table 7-12 2'
in page 23).

The entry "Beamforming             Remove the entry                  Youhan. 11/422   MU
Feedback Matrix V for carrier      "Beamforming Feedback
2" isn't true for Ng = 4 (see      Matrix V for carrier 2" and
Table 7-12 for correct indices).   change the entries
Also the entry "Beamforming        "Beamforming Feedback
Feedback Matrix V for carrier      Matrix V for carrier 2+Ng" and
2+Ng" isn't correct for Ng = 4.    "Beamforming Feedback
                                   Matrix V for carrier 2+2Ng" to
                                   "Beamforming Feedback
                                   Matrix V for carrier 0+Ng" and
                                   "Beamforming Feedback
                                   Matrix V for carrier 0+2Ng",
                                   resp. And change the entry
                                   "Beamforming Feedback
                                   Matrix V for carrier 1" to "If Ng
                                   > 1, Beamforming Feedback
                                   Matrix V for carrier 1"
                                   (otherwise we'll get a double
                                   count for carrier 1 with above
                                   changes for Ng = 1)




Beamforming Feedback Matrix Erase the row of 'Beamforming Youhan. 11/422              Ed
V for carrier 2 is not in case of Feedback Matrix V for carrier
Grouping=4 (Refer Table 7-12 2'
in page 23).
Beamforming Feedback Matrix      Change 'Beamforming                 Youhan. 11/422                  Ed
V for carrier 2+Ng' and          Feedback Matrix V for carrier
'Beamforming Feedback Matrix     2+Ng' and 'Beamforming
V for carrier 2+2Ng' don't       Feedback Matrix V for carrier
match to in case of Crouping=4   2+2Ng' to ''Beamforming
in Table 7-12 (Page 23)          Feedback Matrix V for carrier
                                 Ng' and 'Beamforming
                                 Feedback Matrix V for carrier
                                 2Ng,' respectively.

Beamforming Feedback Matrix      Change 'Beamforming                 Youhan. 11/422                  Ed
V for carrier 2+Ng' and          Feedback Matrix V for carrier
'Beamforming Feedback Matrix     2+Ng' and 'Beamforming
V for carrier 2+2Ng' don't       Feedback Matrix V for carrier
match to in case of Crouping=4   2+2Ng' to ''Beamforming
in Table 7-12 (Page 23)          Feedback Matrix V for carrier
                                 Ng' and 'Beamforming
                                 Feedback Matrix V for carrier
                                 2Ng,' respectively.

Duplicated Table number.         Change table number 7-10 to                                         Ed
Table number 7-10 is already     other non duplicated number
used in the 802.11 baseline
document
Duplicated Table number.         Change table number 7-11 to         AGREE. All figures and tables   Ed
Table number 7-11 is already     other non duplicated number         renumbered to align with
used in the 802.11 baseline                                          REVmb 7.0, with unique
document                                                             assignments for new figures
                                                                     and tables.
The bit size is not correctly    Correct the bit size description,                                   Ed
defined in Table 7 - 11.         divide the values by 2.

The structure of the VHT         Clarify the spec text and clearly Youhan has a proposed             MU
compressed beamforming           define the structure of the VHT resolution
report field for 160M/80+80M     compressed beamforming
is not clearly defined.          report field for 160M/80+80M.
                                 Details of the proposed text
                                 change are presented in our
                                 contribution.
Need better wording to clarify Update paragraph starting on Youhan has a proposed         MU
that the two instances of 80 Hz line 38 for better clarification. resolution
Compressed Beamforming
report field are used to convey
the compressed beamforming
report for 160 and 80+80 MHz.


"±256" should be replaced with As in comment.                     Youhan has a proposed   MU
"±128".                                                           resolution




with tone shifring ±256' is        Change 'with tone shifring     Youhan. 11/422          MU
written. However, in case of       ±256' to 'with tone shifring
160MHz, the tone index is -        ±250'
250~+250.
From "For contiguous 160MHz, Clarify                              Youhan. 11/422          MU
the VHT Compressed
Beamforming Report field has
the structure defined in Table 7-
11 (VHT Compressed
Beamforming Report field (80
MHz)) with tone shifting ±256."
it is not clear if first the upper
or lower subband should be
included in the feedback report




the line says 'with tone shifring Change 'with tone shifring      Youhan. 11/422          MU
±256'. However, in case of        ±256' to 'with tone shifring
160MHz, the tone index is -       ±250'
250~+250.
Did not understand the term - Should it have been -10?         Youhan has a proposed   MU
22 in the text                 (Assuming 8 bits represents     resolution
                               from [0 to 63.75] in quarter dB
"The SNR values in Table 7-9   precision and the factor -10
(VHT Compressed                shifts it to [-10 to 53.75])?
Beamforming Report field (20
MHz)), Table 7-10 (VHT
Compressed Beamforming
Report field (40 MHz)) and
Table 7-11 (VHT Compressed
Beamforming Report
field (80 MHz)) are encoded as
an 8-bit twos complement
value of 4 ×(SNR_average –
22), where
SNR_average is the sum of the
values of SNR per tone (in
decibels) divided by the
number of tones represented.
This encoding covers the SNR
range from –10 dB to 53.75 dB
in 0.25 dB steps"




missing ' in "twos           Put ' as "two's complement".    AGREE. As suggested       Ed
complement".
missing apostrophy between o change                          Duplicate. See #1018      Ed
and s in 'twos complement'

typo "twos complement".       change to "two's               Duplicate. See #1018      Ed
                              complement".
SNR_average is no defined     Change "SNR_average is the                               Ed
                              sum" to "SNR_average is the
                              SNR in space time stream I
                              defined as the sum"
It is not clear from the            Sufficient to say for "group Ng Youhan. 11/422              MU
description, what exactly           of contiguous subcarriers"
grouping is. It is described as a   (remove adjacent - they can't
method for reporting a single       all be adjacent). The text needs
value for a group Ng of             to be specific as to whether
adjacent subcarriers. But what      this is a single subcarrier that
exactly is this single value? The   represents the group or
table seems to imply that it is     whether it is some average
for a specific subcarrier (the      value.
subcarrier identified in the
table).
(see), clause number is missing     I think the right clause number AGREE. Reference added.     Ed
                                    is 7.3.1.31
There is no reference to VHT        Insert "7.3.1.31" after "(see". Duplicate. See #2           Ed
MIMO Control field.




A missing reference                 With grouping, the size of the Duplicate. See #2 (missing   Ed
                                    VHT Compressed Beamforming reference is to section not
                                    Report field is Nc×8+Ns×(Na×( figure)
                                    bψ +bφ)/2) bits, where the
                                    number of subcarriers sent, Ns,
                                    is a function of Ng and the
                                    channel width defined by the
                                    Channel Width field in VHT
                                    MIMO Control field (see Figure
                                    7-3)


section reference is missing        Change "(see )" to "(see          Duplicate. See #2         Ed
                                    7.3.1.31)
Missing reference                                                     Duplicate. See #2         Ed
Missing xref                        add it                            Duplicate. See #2         Ed
Text in this paragraph is           Make new tables similar to 7-     Youhan. 11/422            MU
unclear. Need to describe in        11 for 80+80 non-contiguous
detail on the CV FB field for       and 160Contiguous modes.
80+80 and 160.                      Specify that there are two sets
                                    of SNR reports in 80+80 non-
                                    contiguous mode.
Duplicated Table number.           Change table number 7-12 to   AGREE. All figures and tables    Ed
Table number 7-12 is already       other non duplicated number   renumbered to align with
used in the 802.11 baseline                                      REVmb 7.0, with unique
document                                                         assignments for new figures
                                                                 and tables.
A note is insufficient here. This Convert note to normative text Youhan. 11/422                   MU
needs to be normative, i.e. For and also define the segment
160 MHz, the subcarrier           order
indicies included are for each
segment are given by the 80
MHz row. Also, it should be
stated which segment appears
first (I assume the low
frequency segment)


Wrong style for note          As in comment                       AGREE. Style noted.             Ed
"a 80+80" needs to be changed "an 80+80" (there are lots of       AGREE. As suggested.            Ed
into "an 80"                  same typos in the document)

section reference is incorrect     Change "7.3.1.12" to "7.3.1.31" AGREE. Reference corrected     Ed
                                                                   (note new clause number).

Varying font size on this page                                     AGREE. Fixed with equation     Ed
and on 26.47                                                       conversion edits.
The definition of N should be      Change line to: "is the average Ron has proposed resolution    MU
more tightly related to the        noise plus interference power
average SNR per stream             measured at the beamformee
                                   that was used to calculate SNR
                                   bar

Grammer:                           Change the sentence to "Each AGREE. Used "and quantized"       Ed
"Each Delta SNR subfield           Delta SNR subfield contains the instead of "which is
contains the delta SNR             delta SNR computed using         quantized".
computed using Equation (7-1)      Equation (7-1) which is
quantized to 4 bits in the range   quantized to 4 bits in the range
-8 dB to 7 dB and with 1 dB        -8 dB to 7 dB and with 1 dB
granularity."                      granularity."

Duplicated Table number.           Change table number 7-14 to    AGREE. All figures and tables   Ed
Table number 7-14 is already       other non duplicated number    renumbered to align with
used in the 802.11 baseline                                       REVmb 7.0, with unique
document                                                          assignments for new figures
                                                                  and tables.
The name of the field is too      per comment                     AGREE. Field name changed to Ed
broad for VHT amendment,                                          VHT Operating Mode.
and should be VHT Operating
Mode field.

Grammatical error.                Change "a Operating Mode      AGREE. As suggested                Ed
                                  Notification" into "an
                                  Operating Mode Notification".

All variable should be italic.    italic it                       AGREE. As suggested              Ed
Nss is not
Font in figures should be Arial   Change to arial. Review all                                      Ed
                                  figures and ensure arial font is
                                  used.
The caption of Figure 7-4 uses "- Change double dash to one        AGREE. All figures updated to   Ed
-".                               long dash for the consistency. use standard caption form.

Duplicated Figure number.         Change figure number 7-4 to     AGREE. All figures and tables    Ed
Figure number 7-4 is already      other non duplicated number     renumbered to align with
used in the 802.11 baseline                                       REVmb 7.0, with unique
document                                                          assignments for new figures
                                                                  and tables.
Duplicated Table number.          Change table number 7-15 to     AGREE. All figures and tables    Ed
Table number 7-15 is already      other non duplicated number     renumbered to align with
used in the 802.11 baseline                                       REVmb 7.0, with unique
document                                                          assignments for new figures
                                                                  and tables.
"If Max Nss for SU Present is     add an "it" before the word     DISAGREE. Grammer is             Ed
set to 1, indicates…". I think    "indicates"                     appropriate for fieldencoding
there is an "it" is missing                                       description
before the word "indicates"

"Max Nss For SU" should be        As in comment.                                                   Ed
revised as "Max Nss for SU."
The revision should be also
applied on the parts of 24th
and 37th lines in page 28.

What does the sentence "when clarify                              Ron has proposed resolution      MU
an MU type feedback is used to
do the transmission" mean?
Also, the following paragraph is
duplicated.
"… when an MU type feedback change 'do' to 'form'               AGREE. As suggested.          Ed
is used to do the transmission",
here the word 'do' is
ambiguous and is not
consistent with line 42

"If Max Nss for SU Present is   remove "bits"                   AGREE. Changed to read "the   Ed
set to 1, bits RX Nss                                           Rx Nss field…"
indicates…" The word "bits"
seem to be out of place

"bits" followed by "Rx Nss"     As in comment.                Duplicate. See #4.              Ed
should be removed.
Wrong word insered in "If Max Take out the word "bits" in the Duplicate. See #4.              Ed
Nss For SU Present is set to 1, sentence.
bits Rx Nss indicates the
maximum number of spatial
streams the beamformee can
receive in a single user
beamformed transmission"

Don't use word 'bits'.          Use 'field'.                    Duplicate. See #4.            Ed
Typo "bits" in "If Max Nss For Delete "bits" in the sentence.   Duplicate. See #4.            Ed
SU Present is set to 1, bits Rx
Nss indicates the maximum
number of spatial streams the
beamformee can receive in a
single user beamformed
transmission"

Don't use word 'allowed'.       Rephrase to use 'may'.          AGREE. Rephrased sentence to Ed
                                                                read "A beamformer may
                                                                ignore this threshold if SU type
                                                                feedback is used to form a
                                                                single user beamformed
                                                                transmission." Note use of
                                                                term 'form' as applied with
                                                                #1355
SU and MU transmissions           Define operating mode field   Youhan has a proposed         MU
require different signal          which allows STAs to change   resolution
processing capabilities at RX.    the maximum number of
Moreover, under some              spatial streams the STA can
channel conditions, it may be     received for MU packets.
beneficial for the RX to limit
the max. Nss it can receive for
MU transmissions to allow, for
example, interference
cancellation when there is non-
negligible interference leakage
from other streams. Hence, an
operation mode field to notify
the maximum number of
spatial streams the STA can
received for MU packets
should also be defined.




"… when an SU type feedback       change 'make' to 'form'       AGREE. As suggested           Ed
is used to make a single user
beamformed transmission",
here the word 'make' is
ambiguous and is not
consistent with line 33

When a VHT AP in a BSS or a       Add a new switch              AGREE IN PRINCIPLE.           MAC
VHT STA in an IBSS change to      announcement information      Resolution text provided in
80 MHz/160MHz/80+80MHz            element to channel switch     11/0305r1.
channel, a new VHT channel        announcement frame.
switch mechanism should be
defined.
For 160MHz and 80+80MHz            Clarify the maximum transmit AGREE IN PRINCIPLE.            MAC
transmission, the wide BW          power limits for 160MHz and Resolution text in 11/0306r2.
transmission can span across       80+80MHz transmission cases.
different operating classes        Also, specify a method to
(power regimes). The               announce this information.
maximum transmit power
constraints for transmit bands
can be different by regulations.
Specifications for the
maximum transmit power rules
and the method to anounce
this limits are required.


specification regarding         as per comment                  AGREE IN PRINCIPLE. See #559. MAC
Transmit Power control for
wider bandwidth such as
80MHz, 160Mhz, and
80+80Mhz is missing.
specification regarding channel as per comment                  AGREE IN PRINCIPLE. See #559. MAC
swithcing for wider bandwidth
(80MHz, 160Mhz, and
80+80Mhz) BSS is missing

specification regarding power as per comment                    AGREE IN PRINCIPLE. See #559. MAC
constraint element for 160Mhz
and 80+80Mhz transmission
where the wider BW
transmission can span across
different operating classes
(power regimes)

(Refer to IEEE802.11v D3.0)        Include VHT Capabilites and    Yongho has proposed          MAC
Non-transmitted BSSID Profile      VHT Operation elements in      resolution
needs to include VHT               Non-transmitted BSSID Profile.
Capabilities and VHT Operation
elements.
missing specification for          add TPC for 80/160MHz        AGREE IN PRINCIPLE. See #559. MAC
80/160MHz Transmit Power
control
missing specification for          add channel switch for       AGREE IN PRINCIPLE. See #558. MAC
80/160MHz channel switching        80/160MHz                    Resolution text provided in
                                                                11/0305r1.
missing specification for          add power constraint for     AGREE IN PRINCIPLE. See #559. MAC
80/160MHz power constraint         80/160MHz
element
There is no channel switching   Clarify the channel switching   AGREE IN PRINCIPLE. See #558. MAC
mecanisim for 80                mecanism for 80                 Resolution text provided in
MHz/160MHz/80+80MHz.            MHz/160MHz/80+80MHz.            11/0305r1.
Maximum power constraints       Clarify how to apply maximum    AGREE IN PRINCIPLE. See #559. MAC
for 160MHz/80+80MHz are         power limit for
unclear since BW lies across    160MHz/80+80MHz cases and
different power regimes.        signaling method.


Incorrect table number                                          AGREE. Correct table number       Ed
                                                                from REVmb 7.0 used.

Table number is incorrect       Change table number 7-16 to 7- Duplicate. See #1137               Ed
                                26
Typo                            Change to "Table 7-            Duplicate. See #1137               Ed
                                1626—Element IDs"
TBD can be removed based on replace TBD with fields size                                          Ed
the corresponding fields
definition
TBD in the length of VHT        Add value                      Robert                             MAC
capability element
Resolve the TBDs. Insert        As in comment                  Robert                             MAC
length for VHT BSS Load
element
TBD' is remained.               Add value                      Robert                             MAC
finalized TBD in VHT capability finalize                       Robert                             MAC
element
Element is incorrect            Change "VHT Capability" to     AGREE. As suggested                Ed
                                "VHT Capabilities"
TBD in the length of VHT        Add value                      Robert                             MAC
operation element
TBD' is remained.               Add value                      Robert                             MAC
finalized TBD in VHT operation finalize                        Robert                             MAC
element
Lower case letter for "for" in  Change the phrase to "Max Nss                                     Ed
"Max Nss For SU Present".       for SU Present" for
                                consistency.
Unnecessary uper case letter Change to "Max Nss for SU         AGREE. Consistently used all       Ed
for "for" in "Max Nss For SU    Present" for consistency.      caps field name.
Present".
Change line 8 to ' An STA       Change line 8 to ' An STA      DISAGREE. Use of 'declares' is     Ed
indicates it is a VHT STA by    indicates it is a VHT STA by   okay in this context. Consistent
transmitting the VHT            transmitting the VHT           with HT Capabilities element
Capabilities element'.          Capabilities element'.         description.
I don't like listing the frame it is Remove list, or add any other Robert                          MAC
present in, because it is almost frames that should containt
always wrong!                        the VHT capabilities, such as
                                     the TDLS setup frames.

VHT Supported MCS Set is TBD.        Come up with a VHT supported Youhan has presentation          MAC
It should be noted that SU and       MCS set definition which
MU transmissions require             allows STAs to declare
different signal processing          different support MCS set
capabilities at RX. Thus, a STA      between SU and MU packets.
should be allowed to declare
different supported MCS set
for SU and MU packets.


VHT Capabilities field size is 4     Define appropriate value for   AGREE. Changed TBD for VHT     Ed
octets, not TBD. Similarly VHT       TBD fields.                    Capabilties Info field to 4.
Supported MCS Set is TBD                                            Changed TBD for VHT
                                                                    Supported MCS Set to 8.
The VHT capabilities Info field      Replace "TBD" with "4"         Robert                         MAC
has been defined. The length
shouldn't be TBD (should be 4
octets).
change first TBD to 4 and the        as comment                     Duplicate. See #703            Ed
second TBD to 8
Remove TBDs; VHT Supported            Remove TBD and indicate field Robert                         MAC
MCS Set in figure 7-5 is defined     size
in 7.3.2.61.4. The VHT
Capabilities Info field is defined
in 7.3.2.61.2.

TBD can be removed based on replace TBD with fields size            Robert                         MAC
the corresponding fields
definition
The number of octets for VHT Change the field size TBD to 4         Duplicate. See #703            Ed
Capabilities Info filed is aleady octets.
set to 4 octet not TBD

The number of octets for VHT Change TBD to 4.                       Duplicate. See #703            Ed
Capabilities Info filed is 4
below.
The lengths of both "VHT     change to 4 and 8 octets               Duplicate. See #703            Ed
Capabilities Info" and "VHT  respectively
Supported MCS Set" have been
determined.
why is length of "VHT              as per comment                     Duplicate. See #703             Ed
Capabilities Info field" in Figure
7-5 TBD when it is defined
below at 4 octets?
why is length of "VHT              as per comment                     Duplicate. See #703             Ed
Supported MCS Set field" in
Figure 7-5 TBD when it is
defined below at 8 octets?
The caption of Figure 7-5 uses "- Change double dash to one           AGREE. All figures updated to   Ed
-".                                long dash for the consistency.     use standard caption form.

Short GI capability can be         Use B5 for the signalling and  Raja has presentation               PHY
signalled by only 1 bit            make B6 reserved, or
                                   renumber the bits starting at
                                   B6 and add one reserved bit at
                                   the end.
Allowing only 2 bits for Short     Increase field size to 4 bits. Raja has presentation               PHY
GI capability indication is
insufficient to allow each
bandwidth to have a different
capability, as in 11n.

The caption of Figure 7-6 uses "- Change double dash to one           AGREE. All figures updated to   Ed
-".                               long dash for the consistency.      use standard caption form.

Duplicated Figure number.          Change figure number 7-5 to        AGREE. All figures and tables   Ed
Figure number 7-5 is already       other non duplicated number        renumbered to align with
used in the 802.11 baseline                                           REVmb 7.0, with unique
document                                                              assignments for new figures
                                                                      and tables.
Duplicated Figure number.          Change figure number 7-6 to        AGREE. All figures and tables   Ed
Figure number 7-6 is already       other non duplicated number        renumbered to align with
used in the 802.11 baseline                                           REVmb 7.0, with unique
document                                                              assignments for new figures
                                                                      and tables.
In order to indicate clearly the   B5-B8 are used to indicate         Raja has presentation           PHY
bitmap for the Short GI with       Short GI for 20/40/80/160
different bandwidths, we           field. The original B7 to B21
propose to extend the Short GI     are then shifted to the right by
for 20/40/80/160 field to 4        2 bits, and B24-B31 are
bits.                              reserved. Definition of these
                                   bits can be found in our
                                   comment related to line 27 of
                                   page 30.
In order to indicate clearly the   Extend the Rx STBC field to 3 Edward to present                  MAC
STBC receiving capability of the   bits. The original bits at its right
STA, we propose to extend the      hand side are then shifted to
Rx STBC field to 3 bits.           the right by 2 bits, and the
                                   number of reserved bits should
                                   be reduced by 2. Definition of
                                   the bits can be found in our
                                   comment related to line 33 of
                                   page 30.

TBD encodings for "Short GI for    define encodings for these       Minho.                          PHY
20/40/80/160" and "Rx STBC"        fields
fields
Duplicated Table number.           Change table number 7-16 to      AGREE. All figures and tables   Ed
Table number 7-16 is already       other non duplicated number      renumbered to align with
used in the 802.11 baseline                                         REVmb 7.0, with unique
document                                                            assignments for new figures
                                                                    and tables.
Define TBDs in the table (few      As in comment                    Robert                          MAC
places)
Include parentheses for 'See       (See 9.7c)                       AGREE. As suggested.            Ed
9.7c'                                                               Reference uses new
                                                                    numbering.
A 20 MHz BPSKr1/2 modulated        Add a note to inform             Robert                          MAC
VHT frame is limited to around     implemeters of this limitation
4KB in length due to the 12-bit    and the potential impact to a
L-SIG length field. This has an    design.
impact on rate scaling and the
transmission of large
management frame. A large
MPDU that could be sent at
higher modulation could not
be sent if rate dropped to
BPSKr1/2. The is not clear in
the spec.

The relationship between the       Add normative text to describe Robert                            MAC
settings in VHT Capabilities       relationship
Maximum MPDU Length and
HT Capabilities Maximum A-
MSDU Length needs to be
normative

"7935" should be replaced As in comment.                                                            Ed
with "11398", because
maximum A-MSDU Length for
VHT is 11398 octets.
Supported channel width set Suggested change: Set to 0 if   DISAGREE. Requirement           MAC
does not allow for 80+80 MHz the STA supports 160 MHz       R3.1.D in the ‘Specification
non-contiguous setting only. Set to 1 if the STA supports   Framework for TGac’ (992r15)
                             80+80 MHz                      specifies that “Contiguous and
                             Set to 2 if the STA supports   non-contiguous 160 MHz
                             both 160 MHz and 80+80 MHz     devices shall be capable of
                             Set to 3 the STA does not      transmitting and receiving
                             support either 80+80 or        frames between each other
                             160MHz                         when the two segments of the
                                                            non-contiguous 160 MHz
                                                            device are placed in frequency
                                                            to match the tone allocation of
                                                            the contiguous 160 MHz
                                                            device.” Hence, an STA
                                                            supporting 80+80 MHz must be
                                                            capable of supporting 160 MHz
                                                            as well. See 11/370r0.




HT Capability setting for      As suggested                 Robert                        MAC
Channel Width Set is not clear
when VHT Capability element
is present. Require that HT
Capability Channel Width Set
be set to 40 MHz when VHT
Capability element is present.
Clarify the encoding of Short GI Change TBD to:                    Raja has presentation   PHY
for 20/40/80/160 field.          "A 4 bit bitmap indicates the
                                 support of short guard interval
                                 on 20MHz, 40MHz, 80MHz and
                                 160MHz/80+80MHz
                                 bandwidths.
                                  Bit 0 sets to 1 to indicate that
                                 short GI is supported on
                                 20MHz bandwidth.
                                  Bit 1 sets to 1 to indicate that
                                 short GI is supported on
                                 40MHz bandwidth.
                                  Bit 2 sets to 1 to indicate that
                                 short GI is supported on
                                 80MHz bandwidth.
                                  Bit 3 sets to 1 to indicate that
                                 short GI is supported on
                                 160MHz/80+80MHz
                                 bandwidth."

SGI value is not defined.       Define                          Raja has presentation      PHY
                                00 - SGI Not supported for all
                                BW
                                01 - SGI supported for 20 & 40
                                MHz BW
                                10 - SGI supported for 20, 40
                                and 80 MHz BW
                                11 - SGI supported for 20,40,80
                                and 80+80/160 MHz BW


TBD in the Encoding of Short GI Add value                        Raja has presentation     PHY
for 20/40/80/160
Replace TBD with something                                       Raja has presentation     PHY
meaningful
Resolve the TBDs on this page. As in comment                     Raja has presentation     PHY

Fill in the TBD for short GI    Change TBD to "Set to 0 if not   Raja has presentation     PHY
                                supported; Set to 1 if
                                supported"
TBD' is remained.               Add value                        Raja has presentation     PHY
TBD in the Encoding of Short GI finalize                         Raja has presentation     PHY
for 20/40/80/160
HT capability field shall be       In line 27-29 of figure 7-10,    Raja has presentation    PHY
supported by 11ac                  modify as
devices,it's natural to re-use     " TBDB5 set to 0 if Short GI for
short GI indication in HT          80/80+80MHz is not
Capabilities Info field to         supported;
indicate short GI capability for    B5 set to 1 if Short GI for
20MHz and 40MHz                    80/80+80MHz is supported;
respectively.                       B6 set to 0 if Short GI for
                                   160MHz is not supported;
                                    B6 set to 1 if Short GI for
                                   160MHz is supported;

                                   The Short GI support for
                                   20MHz and 40MHz refers to
                                   Short GI for 20MHz subfied and
                                   Short GI for 40MHz subfield in
                                   HT Capabilities Info field."

Encoding for Short GI              set the field to 1 bit and define Raja has presentation   PHY
capability: the field is not       the meaning: 1=short GI,
defined; also 2 bits are not       0=Long GI
necessary
Clarify the encoding of Rx STBC    Change "Indicates support for Edward to present           PHY
field.                             the reception of PPDUs using
                                   STBC" to:
                                   "Indicates the number of
                                   spatial streams supported for
                                   the reception of PPDUs using
                                   STBC"
                                   Change TBD to:
                                    " Set to 0 for not supporting
                                   reception of PPDUs using STBC.
                                      Set to 1 for supporting 1
                                   spatial stream.
                                      Set to 2 for supporting 1 or
                                   2 spatial stream(s).
                                      Set to 3 for supporting 1 or
                                   2 or 3 spatial stream(s).
                                      Set to 4 for supporting 1 or
                                   2 or 3 or 4 spatial stream(s).
                                      The values 5,6,7 are
                                   reserved."


Rx STBC: Replace TBD in            "Set to 0 if not supported. Set   Edward to present       PHY
encoding column with               to 1 if supported"
something meaningful
Rx STBC value is not defined.      Define                         Edward to present               PHY
                                   0 - RX STBC not supported
                                   1 -1 stream RX STBC
                                   supported
                                   2 - 2 stream Rx STBC supported
                                   3 - 3 stream Rx STBC supported
                                   4 - 4 stream Rx STBC supported




TBD in the Encoding of Rx STBC Add value                           Edward to present              PHY

Fill in the TBD for Rx STBC    Change TBD to "Set to 0 if not      Edward to present              PHY
                               supported; Set to 1 if
                               supported"
TBD' is remained.              Add value                           Edward to present              PHY
TBD in the Encoding of Rx STBC finalize                            Edward to present              PHY

In Table 7-16,Encoding of Rx add “Set to 0 if not supported        Edward to present              PHY
STBC is TBD                  Set to 1 if supported” for
                             Encoding of Rx STBC

Reference section where it    Reference 9.21.5                     Robert                         MAC
defines what it means to be a
single user beamformer. Ditto
for single user beamroformee.

 “Grouping Set” – Specifies      Recommend clarifying              Ron has proposed resolution MAC
supported Ng values, but is this                                   (Robert: Why do we need a
as beamformee or                                                   capability at all? Bfee can send
beamformer, or for both?                                           anything)
Basic MCS Set is undefined       Define it or delete it            Yongho has proposed              MAC
                                                                   resolution
Text allows to independently       Specify that whenever MU Rx     Simone                           MAC
declare SU or MU capability or     capability is set, then SU
both; to increase                  Beamformee capability is also
interoperability it is suggested   set; Specify that whenever MU
that a MU capable STA/AP shall     Tx capability is set, then SU
also be SU capable                 Beamformer capability is also
                                   set;
Wording is inconsistent:           Make the wording consistent.                                   Ed
Beamformer/ee v. tx/rx;
support for v. whether or not
the STA supports; single user v.
MU.
"Group set" field should be     Change the name and defintion Ron                         MAC
defined the same way as         of this field to the same as
"Minimal Grouping" in HT        "Minimal Group" field in 11n.
capability, which is a
Beamformee capability. The
current defintion sounds like a
BFMer capability.

The encoding description is not In Beacon and Probe Response                              Ed
very clear                      frames:
                                Set to 0 if the BSS does not
                                allow use of VHT TXOP PS
                                mode
                                Set to 1 if the BSS does allow
                                use of VHT TXOP PS mode
                                Otherwise:
                                Set to 0 if the STA is not in VHT
                                TXOP PS mode
                                Set to 1 if the STA is in VHT
                                TXOP PS mode

VHT TXOP PS encoding is not Change the text as in                   Allan.                MAC
specifying the frames to which comment.
the encoding is valid.
The encoding is saying in
negative message, it is better
to define what does the value
mean in posite way.


"Set to 0 if VHT TXOP PS Mode     Add "When transmitted by an Allan.                      MAC
at STAs in the                    AP" and "When transmitted by
BSS is not allowed.               a non-AP STA" as approprite.
Otherwise, set to 1.
Set to 0 if STA is not in VHT
TXOP PS mode.
Otherwise, set to 1." - this is
internall conflicting.
"included on".                    "included in".                    AGREE. As suggested   Ed
Should be "Request".              Capitalise first letter.          AGREE. As suggested   Ed
Note style (twice)                                                  AGREE. Fixed.         Ed
"N_sts" should be revised to      As in comment.                    AGREE. As suggested   Ed
"N_STS."
"NDP packet" should be           As in comment.                    AGREE. Deleted 'packet' in      Ed
revised to "NDP". There are                                        referenced sections.
same phrases on 10th line in
page 55, 32nd line in page 84,
and 28th line in page 106 and
they also should be revised.

Maximum A-MPDU Length           Place in VHT Capabilitieis Info    Robert                          MAC
Exponent could be included in field next to Maximum MPDU
the VHT Capabilities Info field Length
rather than as a separate
subfield.

The caption of Figure 7-7 uses "- Change double dash to one        AGREE. All figures updated to   Ed
-".                               long dash for the consistency.   use standard caption form.

Relationship between HT A-       As suggested                      Robert                          MAC
MPDU Parameters field and
VHT A-MPDU parameters field
is not explicit. Require that HT
A-MPDU Parameters field
match A-MPDU Parameters
field upto 64KB and then fix HT
value at 64 for longer values.


The description for the        Set to 0 if AP does not support                                     Ed
encoding of VHT TXOP PS        VHT TXOP PS mode in the BSS.
subfield used by AP is         Otherwise, set to 1.
suggested to be modified since
it is used in the initial
capabilities negotiation and
advertisement. It is used to
indicate whether or not AP
supports VHT TXOP PS mode.
However, the terms "allow"
and "not allow" seem to
presume that both sides
already support this feature.
The usage of VHT TXOP PS           Indicates whether or not STA Allan.                           MAC
subfield in VHT Capabilities       supports VHT TXOP PS mode.
Info field for STAs is suggested   Set to 0 if STA does not
to be modified as follows. For a   support VHT TXOP PS mode.
non-AP VHT STA, the VHT TXOP       Otherwise, set to 1. Use an
PS subfield is recommended to      alternative method to indicate
advertise whether or not "it       if a STA is in VHT TXOP PS
supports this functionality"       mode.
rather than indicating "it is in
VHT TXOP PS mode".
Otherwise, it may raise the
situation that non-AP VHT STA
has VHT TXOP PS subfield set
while VHT AP does not support
VHT TXOP PS mode. Even both
sides support this function, the
STA needs to perform
association process every time
to switch among VHT TXOP PS
mode, Active mode, and PS
mode. Hence, it is also
suggested to use an alternative
and more flexible method to
indicate whether or not the
STA is in VHT TXOP PS mode.



Duplicated Figure number.          Change figure number 7-7 to   AGREE. All figures and tables   Ed
Figure number 7-7 is already       other non duplicated number   renumbered to align with
used in the 802.11 baseline                                      REVmb 7.0, with unique
document                                                         assignments for new figures
                                                                 and tables.
Duplicated Table number.           Change table number 7-17 to   AGREE. All figures and tables   Ed
Table number 7-17 is already       other non duplicated number   renumbered to align with
used in the 802.11 baseline                                      REVmb 7.0, with unique
document                                                         assignments for new figures
                                                                 and tables.
Use better field alignment. Try Add reserved bits before Tx      Robert                          MAC
to get 16 bit fields byte       MCS Map so that it is byte
aligned.                        aligned. Note that the total
                                number of bits does not add to
                                64.
Why do we need this field,                                     Robert                            MAC
both Rx and Tx MCS
capabilities should be
advertized.
Missing word 'field' after        Figure 7-8--VHT Supported        AGREE. As suggested             Ed
'Figure 7-8--VHT Supported        MCS Set field
MCS Set'
The caption of Figure 7-8 uses "- Change double dash to one        AGREE. All figures updated to   Ed
-".                               long dash for the consistency.   use standard caption form.

Figure need be improved                                                                            Ed

Font type in Figure 7-9 seems    change to Times New Roman         AGREE. All figures updated to   Ed
wrong                            font                              use standard caption form.

Duplicated Figure numbers.    Change figure numbers 7-8 and        AGREE. All figures and tables   Ed
Figure number 7-8 and 7-9 are 7-9 to other non duplicated          renumbered to align with
already used in the 802.11    numbers                              REVmb 7.0, with unique
baseline document                                                  assignments for new figures
                                                                   and tables.
Duplicated Table number.         Change table number 7-18 to       AGREE. All figures and tables   Ed
Table number 7-18 is already     other non duplicated number       renumbered to align with
used in the 802.11 baseline                                        REVmb 7.0, with unique
document                                                           assignments for new figures
                                                                   and tables.
MCS options for HT format      As suggested                        Robert                          MAC
should align with VHT format
by require that the same MCS
set be supported for HT format
frames as for VHT format
frames for 20 and 40 MHz (less
256 QAM). This basically
means that MCS0-7 be
supported for HT frames by all
VHT STAs.

in Table 7-18, consistently use as per comment                                                     Ed
"N_ss" instead of "number of
spatial streams". Replace
'spatial stream number' with
'N_ss". Replace 'that N_ss'
with 'the N_ss'.

max --> maximum. Ditto                                             AGREE. As suggested in both     Ed
further down for Tx field.                                         places.
If the max data rate is non-   Clarify whether to truncate,        Robert                          MAC
integer, what value is passed? ceiling or round.
(Note 11n is similarly
underspecified.)
The Tx MCS Set Defined field is Remove field and require Tx     Sameer has resolution            PHY
unnecessary. It parallels a     MCS map always be
similar field that was added    appropriately set.
during the development of
.11n to maintain compatibility
with Draft 1 .11n devices. We
don't have that situation here.


Lower case letter in "Tx MCS    Change to uppercase for      AGREE. Uppercase M.                 Ed
map".                           consistency as "Tx MCS Map".

Notation in "Tx MCS map".      Change for consistency as "Tx Duplicate. See #1039                Ed
                               MCS Map".
Table 7-18 line 5 column 3 : If Tx MCS Set Defined is set to                                     Ed
The 2-bit max MCS for each     1, then the 2-bit max MCS for
spatial stream number is       each spatial stream number is
encoded as follows:            encoded as follows:
• 00 indicates support for MCS • 00 indicates max MCS
0-7                            supported is MCS 7.
• 01 indicates support for MCS • 01 indicates max MCS
0-8                            supported is MCS 8.
• 10 indicates support for MCS • 10 indicates max MCS
0-9                            supported is MCS 9.
• 11 indicates no support for • 11 indicates max MCS
that NSS                       supported is lower than MCS 7
Since some MCSs are not        for that NSS.
supported for all NSSs, MCS 0-
7,0-8,0-9 may not be accurate.


Missing word 'this' before      this indicates the max data rate DISAGREE. Consistent with        Ed
'indicates the max data rate …'                                  field descriptions elsewhere
                                                                 (subject is implied by context).

Basic MCS set required          Define Basic MCS sets           Yongho has proposed              MAC
                                                                resolution
Define "Basic MCS Set" or                                       Yongho has proposed              MAC
remove                                                          resolution
Basic MCS Set subfield in VHT    1). In figure 7-10,modify         Yongho has proposed           MAC
Operation element format is      "TBD"under Basic MCS Set to resolution
TBD which is used to indicate    "2",and
the MCS values that are          2). in line 39 on page 34, insert
supported by all VHT STA.The     " Basic MCS Set indicates the
design of Rx MCS Map in the      combinations of MCSs and
VHT Supported MCS Set Field is   spatial streams that are
sample and efficient , so we     supported by all VHT STAs in
can simply re-use the design     the BSS. It presents in
for Basic MCS Set subfield.      Beacon/Probe Response
                                 frames. Otherwise it's
                                 reserved.
                                 The Basic MCS Set consists of a
                                 16 bits field, 2 bits of which
                                 indicates the basic MCS
                                 support for a Nss from 1 to 8.
                                 Basic MCS Set values are
                                 defined as Rx MCS Map
                                 subfiled in 7.3.2.61.4 (VHT
                                 Supported MCS Set field). ".




change TBD to a number           as comment                     AGREE. VHT Operation             Ed
                                                                Information field is 3 octets.
                                                                Also named the field "VHT
                                                                Operation Information"
                                                                consistently throughout
                                                                section.
TBD in the length of VHT         Add value                      Yongho has proposed              MAC
Operational Information and                                     resolution
Basic MCS Set
Duplicated Figure number.       Change figure number 7-10 to AGREE. All figures and tables       Ed
Figure number 7-10 is already   other non duplicated number renumbered to align with
used in the 802.11 baseline                                  REVmb 7.0, with unique
document                                                     assignments for new figures
                                                             and tables.
Either remove the TBD fields or as comment                   AGREE. "Other fields"               Ed
add missed fields here                                       removed.

Other Fields is undefined, and   Define it or delete it         Duplicate. See #770              Ed
variable length.
Remove "Other Fields" from                                      Duplicate. See #770              Ed
VHT Operation Information
Field.
No subfield definition in VHT      Define the subfield.                                         Ed
Operational Information field

Remove "Other Fields". As a                                        Duplicate. See #770          Ed
result, VHT Operation
Information field will be
defined and TBD can be
removed from Figure 7-10.
Duplicated Figure number.          Change figure number 7-11 to AGREE. All figures and tables   Ed
Figure number 7-11 is already      other non duplicated number renumbered to align with
used in the 802.11 baseline                                       REVmb 7.0, with unique
document                                                          assignments for new figures
                                                                  and tables.
"STA Channel Width" is bandly      Change name to "Channel        Robert has a proposed         MAC
named. This is the BSS Channel     Width". Alternate encoding: 20 resolution
Width (logically grouped with      MHz: VHT Operation Channel
Center Frequency and other         Width = 0, HT Operation
channel definition paramters).     Channel Width = 0; 40 MHz:
Also, the encoding of this field   VHT Operation Channel Width
could be better aligned with HT    = 0, HT Operation Channel
Operation element.                 Width = 1; 80 MHz: VHT
                                   Operation Channel Width = 1,
                                   HT Operation STA CHannel
                                   Width = 1, 160 MHz: VHT
                                   Operation Channel Width = 2,
                                   HT Operation STA Channel
                                   Width = 1; 80+80MHz: VHT
                                   Operation Channel Width = 3,
                                   HT Operation Channel Width
                                   =1


There was a certain amount of      Either re-purpose the STA       Robert has a proposed        MAC
confusion during .11n whether      chanel width as a BSS channel   resolution
the STA Channel Width              width field, or add a BSS
represented the BSS operating      channel width field.
channel width, or the current
receiver capability of the AP.

This continues that confusion,
because we have a "current
receiver width" field, but no
operating channel width field.
There are inconsistencies          Clarify or redefine the            Robert has a proposed   MAC
between the field name,            definition of this field. Only for resolution
definition and value. The field    20 MHz, the channel number
name is "Channel Center            can be used to determine the
Frequency Segment 1" but the       center frequency. For 40, 80,
definition includes channel        160 and 80+80 MHz, the
center frequency for 20, 40,       center frequency can be either
80, 160. Also the field value is   the lowest or highest
given as the channel number        frequency of the channel n.
corresponding to the channel       Pick one.
center frequency of segment 1.


Channel numbers are                Add operating class to the      Yongho has proposed        MAC
meaningless without a              table.                          resolution
specified operating class.
The Channel Center Frequency       Please clarify what set to n    Yongho has proposed        MAC
encoding is not clearly            means. Also the channel         resolution
specified. Set to n is not         number should be IEEE channel
Standard text                      number.
The Channel Center Frequency       Change the Channel number       Yongho has proposed        MAC
encoding is not specifying the     corresponding to central        resolution
primary channel of the BSS.        frequency in Segment 1 to
The primary channel defines        lowest IEEE channel number of
the secondary channels and         the primary channel.
thus, the center frequency may
be calculated and the channel
number of the primary channel
is also signaled.


There are inconsistencies          Redefine the field value. If the Yongho has proposed       MAC
between the field name and         center frequency is the field    resolution
field value. The field name is     value, specify either the lowest
"Channel Center Frequency          or highest frequency of the
Segment 2" but the field value     channel to be the center
is given as the channel number     frequency of the operating
corresponding to the channel       bandwidth.
center frequency of segment 2.
Moreover, a single value n may
not be sufficient to determine
the center frequency for
segment 2.
Has anybody put forward a         Remove VHT BSS Load            AGREE IN PRINCIPLE.            MAC
compelling case for the need      element, or make it useful.    Resolution text in 11/303r2.
for this information? We
currently have unspecified
information having an
unspecified effect.

BW utilization' and 'SS           Add definition of 'BW field' and AGREE IN PRINCIPLE. See      MAC
utilization' are not finalized.   'SS utilization'                 #1260. 11/303r2.
11ac supports up to 8 SS and
up to 160MHz as well as
80+80MHz Transmission. VHT
BSS load element format
(Figure 7-12) needs some
modification.

The performance of MU-MIMO        Add a field for 'the number of AGREE IN PRINCIPLE. See        MAC
can be enhanced if MU-MIMO        MU-MIMO capable stations' in #1260. 11/303r2.
capable STAs can choose their     VHT BSS load element format
associatiation with BSS with      (Figure 7-12).
more MU-MIMO capable
advanced STAs. However, VHT
BSS load element does not
support this.


bandwidth utilization" and     Define "bandwidth utilization     AGREE IN PRINCIPLE. See        MAC
"spatial stream utilization"   field" and "spatial stream        #1260. 11/303r2.
have not defined yet, which    utilization".
are important information
indicating the load of network
serving VHT STAs.
In legacy BSS Load element,   Define a field 'MU-MIMO       AGREE IN PRINCIPLE. See            MAC
there exists a field that     capable STA count' in VHT BSS #1260. 11/303r2.
indicates the number of       load element format.
associated STAs. This
information gives critical
indication for the loading of
BSS. For the same reason, VHT
BSS also requires STA count
but in this case MU-MIMO
capable STA count. This
information together with
''bandwidth utilization" and
"spatial stream utilization"
provides a method to provide
an exact status of BSS load.


"additional". I suppose this is Remove "additional"             AGREE. Removed aditional.      Ed
in the same vein as "persil
washes whiter".
No details on Bandwidth         Define the field.               AGREE IN PRINCIPLE. See        MAC
Utilization and Spatial Stream                                  #1260. 11/303r2.
Underutilization field.

fill in TBD of bss load element   finalize section             AGREE IN PRINCIPLE. See         MAC
                                                               #1260. 11/303r2.
TBD should not exists in the      Define appropriate value for AGREE IN PRINCIPLE. See         MAC
standard                          TBD fields.                  #1260. 11/303r2.
Duplicated Figure number.         Change figure number 7-12 to AGREE. All figures and tables   Ed
Figure number 7-12 is already     other non duplicated number renumbered to align with
used in the 802.11 baseline                                    REVmb 7.0, with unique
document                                                       assignments for new figures
                                                               and tables.
complete the TBD fields           as comment                   AGREE IN PRINCIPLE. See         MAC
                                                               #1260. 11/303r2.
Remove editor's note                                           AGREE IN PRINCIPLE. See         MAC
                                                               #1260. 11/303r2.
Duplicated Table number.          Change table number 7-19 to AGREE. All figures and tables    Ed
Table number 7-19 is already      other non duplicated number renumbered to align with
used in the 802.11 baseline                                    REVmb 7.0, with unique
document                                                       assignments for new figures
                                                               and tables.
(Refer to IEEE802.11z D13.0) Include VHT Operation          AGREE. TDLS Operation                 MAC
To support TDLS operations in element in TDLS Setup Confirm element added as suggested.
VHT STAs, VHT Operation       frame.                        Resolution text in 11/310r0.
element should be included in
7.4.11.3 TDLS Setup Confirm
frame.

(Refer to IEEE802.11z D13.0)      Add VHT Channel Switch         AGREE IN PRINCIPLE. See #558. MAC
To support channel switching      Announcement element in        Resolution text provided in
for VHT STAs, information         7.4.11.6                       11/0305r1.
element which includes
80/160/80+80MHz should be
added.

Missing remark                    Insert Section 7.4.11:                                          Ed
There are no "7.4.11 TDLS         1). Insert following sentence in AGREE IN PRINCIPLE. Baseline   Ed
Action frame details","Table 7-   pg35/ln47:                       is now REVmb 7.0 and
57v2" and "Table 7-57v3" in       "Insert the following section as modified section is 8.5.13
Draft P802.11-REVmb/D4.01.        defined in the latest
                                  P802.11REVmb revision", and
                                  2). Modify line 52 in page 35
                                  as:
                                  "Change Table 7-57v2 as
                                  defined in the latest
                                  P802.11REVmb revision,
                                  appending the rows for Order
                                  18 and 19"; and
                                  3). Modify line 3 in page 36 as:
                                  "Change Table 7-57v3 as
                                  defined in the latest
                                  P802.11REVmb revision,
                                  appending the rows for Order
                                  18 and 19"


The structure of action frames Change all description of frame Robert                             MAC
is defined in your baseline.      body to action field in 7.4.12.
These action frames define the
format of the action field, not
the frame body. The
difference is significant
because the action field field is
followed by vendor specific
and management frame
protection elements.
Each category needs to define Add: These frames are            Robert                           MAC
the name and size of the <xxx> identified by the single octet
action field.                  VHT Action field, which follows
                               immediately after the Category
                               field.

                               And change "The Action field
                               values" to "The VHT Action
                               field values"

No details on Value 3 in Table 7- Clarify whether Value 3 is                                    Ed
20.                               reserved or not.
There is one vacant row           Erase the row.                AGREE. Row removed.             Ed
Duplicated Table number.          Change table number 7-20 to   AGREE. All figures and tables   Ed
Table number 7-20 is already other non duplicated number        renumbered to align with
used in the 802.11 baseline                                     REVmb 7.0, with unique
document                                                        assignments for new figures
                                                                and tables.
Duplicated Table number.       Change table number 7-21 to      AGREE. All figures and tables   Ed
Table number 7-21 is already   other non duplicated number      renumbered to align with
used in the 802.11 baseline                                     REVmb 7.0, with unique
document                                                        assignments for new figures
                                                                and tables.
Structure of the frame need    define the structure of frame    Youhan has proposed             MU
account for the 80+80 or 160   for the 160MHz case              resolution
MHz case. In that case there
can be 2 beamforming report
and 2 MU Exclusive report
fields
Define this frame using the    define new management field AGREE IN PRINCIPLE.                  MU
standard format                and use a table to include the Resolution text in 11/354r1.
                               field into the new action frame

Exact definition of Group ID    Explicitly describe the meaning AGREE IN PRINCIPLE. See #772. MU
field is required. The value of of the value 0~62 and           Resolution text in 11/354r1.
0~62 should indicate Group ID especially 63.
of individual groups. Group ID
63 is used to indicate special
meaning as described in
22.3.9.2.3.
In mesh network where VHT        Clarify the Group ID                  AGREE IN PRINCIPLE. Clarified MU
STAs transmit MU-MIMO            management precedure in               that AP transmits this frame
transmissions, a mesh point is mesh network.                           which is in sync with definition
supposed to receive mutiple                                            of DL MU-MIMO in the current
signals from different mesh                                            spec. 11/354r1.
points using different Group ID.
Specifications are not clear
which SSID and Group ID the
receiver should consider.


The locations of fields within     Define exact frame format for AGREE IN PRINCIPLE. See #772. MU
the groupID management             this frame, giving bit level field Resolution text in 11/354r1.
frame is not defined               locations

The definition of Group ID is      Define the value 0~62 and 63        AGREE IN PRINCIPLE. See #772. MU
unclear.                           which is for special use.           Resolution text in 11/354r1.

When a VHT STA receives         Clarify the Group ID                   AGREE IN PRINCIPLE. See       MU
signals from different VHT STAs management in multiple                 #1048. Resolution text in
using MU-MIMO, Group ID         reception cases.                       11/354r1.
may be the same in some
cases. However, this can cause
a problem when the spatial
steam allocations on both
transmitters differ.

A table with frame content (as     add table listing the frame         AGREE IN PRINCIPLE. See #772. MU
done for other action frames)      content                             Resolution text in 11/354r1.
is missing
The Group ID management            For ease of parsing the frame AGREE IN PRINCIPLE. See #772. MU
frame is inadequately defined.     should have a 8 octet            Resolution text in 11/354r1.
Define frame format.               membership status array (1 bit
                                   per subfield for 64 groups) and
                                   a 16 octet STA position array (2
                                   bits per STA position for 64
                                   groups). Both arrays are
                                   indexed by Group ID.

The Group ID management            Since this is a real-time frame -   Sameer. 11/354r1. (Editor: This MU
frame needs to be classified for   table update is immediate on        comment approved as
management frame                   receipt of the frame - the          resolved with 11/354r1, but
encryption.                        frame should be classified as       document states "This
                                   non-encrypted.                      classification might happen in a
                                                                       different section".) Another
                                                                       comment on this - yong.
"shall" shall not be used in     Replace "in such frames shall     AGREE IN PRINCIPLE. See #772. MU
section 7.                       consists of" with "includes"      Resolution text in 11/354r1.

The frame format of Group ID     Insert a table to define the      AGREE IN PRINCIPLE. See #772. MU
management frame is not          action frame body.                Resolution text in 11/354r1.
properly defined.
The format of the Group ID       Insert a figure to illustrate the AGREE IN PRINCIPLE. See #772. MU
Assignment field is not          Group ID assignment field.        Resolution text in 11/354r1.
properly defined.
"The frame body in such          Convert all shalls related to     AGREE IN PRINCIPLE. See #772. MU
frames shall consist of a" -     structure in clause 7 to          Resolution text in 11/354r1.
WG802.11 style is to avoid all   declarative language. Move
normative language in Clause     all shalls related to behaviour
old 7, with one all-             out of clause 7.
encompassing "shall" in old
7.1.
A picture or table would be      add one                           AGREE IN PRINCIPLE. See #772. MU
nice                                                               Resolution text in 11/354r1.

"STA position" is the name of    2 bits "STA position" that        AGREE IN PRINCIPLE. See #772. MU
2bit subfield.                   specifyies spatial time stream    Resolution text in 11/354r1.
                                 position of the STA in the
                                 corresponding group ID

There are 24 octets carrying 3   Remove the sentence               AGREE IN PRINCIPLE. See #772. MU
bits of STA info/group so the                                      Resolution text in 11/354r1.
exact location of the above
fields within the frame body
should not be TBD

TBDs                             resolve them                      AGREE IN PRINCIPLE. See #772. MU
                                                                   Resolution text in 11/354r1.

TBD should not exists in the     Define appropriate value for      AGREE IN PRINCIPLE. See #772. MU
standard                         TBD fields.                       Resolution text in 11/354r1.
The 3-bit indication is not      As in comment.                  DISAGREE. For ease of parsing, MU
having any reserved values for                                   it is a little better to keep
groups. Also the definition is                                   membership status and STA
not good standard text.                                          positions as separate, as that
I propose to combine the                                         ensures the fields cross over at
"membership status" and STA                                      byte boundaries. 11/354r1.
position fields to 3 bits fields
and use value 0 to indicate that
the STA is not present in the
group ID and values 1 - 4 to
indicate the position of the STA
in the Group and mark values 5
-7 as reserved.


The name of the field is too      per comment                    AGREE. Frame name changed       Ed
broad for VHT amendment,                                         to "VHT Operating Mode
and should be VHT Operating                                      Notification"
Mode Notification.

"See definition in 11.14.2" -->   Change "11.14.2" to "7.3.1.34" AGREE. Reference changed to     Ed
Operating Mode field is                                          8.4.1.36 which is the section
described in 7.3.1.34 .                                          for the VHT Operating Mode
                                                                 field definition using the
                                                                 updated section numbering.


It makes it easier to read of a add a sketch of the Group ID     AGREE IN PRINCIPLE. See #772. MU
draw the format of the Group management frame                    Resolution text in 11/354r1.
ID management frame is
available
TBD whether the action frame Define details.                     AGREE IN PRINCIPLE. See #772. MU
is "robust".                                                     Resolution text in 11/354r1.
TBD on the location of the                                       (Editor: Note that the
field.                                                           comment on whether or not
                                                                 the frame is "robust" is not
                                                                 addressed in the resolution.
                                                                 See #1154). Yong
The Operating Mode                Add text to state that although Reza                          MAC
Notification frame can be sent    a non-AP STA can send an
by both non-AP STA and AP         Operating Mode Notification
implies that any STA can decide   frame to change its operating
to operate with less than         channel width, it shall continue
80MHz bandwidth although          to operate with the current
the AP and other STAs still       channel width until the AP
operate with 80 MHz. This will    sends out a Operating Mode
create coexistence issues         Notification frame. This may
among the STAs operating in       need further discussion in the
the same BSS                      task group.




Duplicated Table number.          Change table number 7-22 to    AGREE. All figures and tables Ed
Table number 7-22 is already      other non duplicated number    renumbered to align with
used in the 802.11 baseline                                      REVmb 7.0, with unique
document                                                         assignments for new figures
                                                                 and tables.
"EOF pad" should be defined in Insert the following definitions: AGREE. Add EOF pad definition MAC
section 3.2.                   End of frame (EOF) Pad:           in section 3.2. Clarify the EOF
                               Padding octets for the last A- pad in 9.7d.6 A-MPDU padding
                               MPDU subframe to be padded for VHT format PPDU.
                               to the last octet of the PSDU or Resolution text in 11/374r0.
                               to a multiple of 4 octets in
                               length.

There is no definition of the     Add the definition of the bit    DISAGREE. It is implementation MAC
value of "EOF pad".               pattern of "EOF Pad". It seems   dependent. Same as Qword
                                  that one of the possible         pad for A-MPDU subframe.
                                  patterns is "all zero".          11/0374r0.

You can't have a "change"         Add separate "replace"           AGREE. Added instructions to Ed
instruction that replaces the     instructions for any replaced    replace Figrues 8-405 and 8-
figures.                          figures.                         407 and to insert Figure 8-ac16
                                                                   (new numbering)

The "last A-MPDU subframe" is change to "the last non-zero         AGREE. Change to “the last A- MAC
not very accurate here. The    length A-MPDU subframe"             MPDU subframe with non-zero
EOF delimiter can also be                                          MPDU length” 11/0374r0.
considered as a zero length A-
MPDU subframe.
"EOF delimiters" should be       As in comment.                  AGREE. Changed to “zero        MAC
replaced with "zero length A-                                    length A-MPDU subframes
MPDU subframes", because                                         with EOF field set to 1”.
"zero length A-MPDU                                               11/0374r0.
subframes" is used in Table 7-
57w.
The maximum frame size           Please clarify why the EOF and DISAGREE. Please refer to 11-   MAC
definition is tricky. When the   EOF Pad are not included to A- 11-0034-00-00ac-max-frame-
EOF and EOF bad are not          MPDU maximum size.             length-changes.ppt for the
included to maximum size, the                                   reason. 11/0374r0.
A-MPDU maximum size is not
known.

"1,048,575"                      replace commas with spaces      AGREE. As suggested            Ed
                                 for IEEE style
The format and font type is      change to the right font type   AGREE. Figure replaced with   Ed
wrong                            and size                        more standard table form
                                                                 drawing.
In Table 7-57w, wouldn't         please clarify.                 DISAGREE. Reserved bits are   MAC
changing MPDU delimeter field                                    used for the changes. The new
format as described still create                                 MPDU delimiter with length
problems for non-VHT STA or                                      extension is expected to be
complicate design? Isn't little-                                 received and decoded by VHT
endian assumed and this                                          STAs only. Agree that the
MPDU Length High subfield                                        added NOTES should be
should represent the lower                                       underlined. 11/0374r0.
sigficance bits? At least
editorially the added NOTES
should be underlined.


Duplicated Figure number.        Change figure number 7-13 to AGREE. All figures and tables     Ed
Figure number 7-13 is already    other non duplicated number renumbered to align with
used in the 802.11 baseline                                   REVmb 7.0, with unique
document                                                      assignments for new figures
                                                              and tables.
I wouldn't make the            Structure as a list, one entry     AGREE. As suggested: "An A- Ed
interpretation of any          for VHT and one for HT             MPDU is a sequence of MPDUs
normative text dependent on a                                     carried in a single PPDU
common interpretation of the                                      with the TXVECTOR/RXVECTOR
non-existent rules of operator                                    FORMAT parameter set to
precidence in English.                                            VHT, or
                                                                  with the TXVECTOR/RXVECTOR
                                                                  FORMAT parameter set to
                                                                  HT_MF or HT_GF and with the
                                                                  TXVECTOR/RXVECTOR
                                                                  AGGREGATION parameter set
                                                                  to 1."




The reference section for "A-    Add the reference section        AGREE. This is existing text and Ed
MPDU" is missed.                 number of 7.4a.3.                updated with shift to REVmb
                                                                  7.0 baseline.
Missing reference                contexts specified in Table 7-   Duplicate. See#46                Ed
                                 57x.
reference number is missing      Change "in " to "7-57x"          Duplicate. See#46               Ed

"transmitted in one of the       add reference                    Duplicate. See#46               Ed
contexts specified in ." Missing
reference
Incomplete sentence, "An         Complete sentence                Duplicate. See#46               Ed
AMPDU is transmitted in one
of the contexts specified in.

Missing reference                                                 Duplicate. See#46               Ed
section number of referering                                      Duplicate. See#46               Ed
section is missing.

Font size from line 15 to line 16 re-adjust the font-size         AGREE. As suggested.            Ed
seems different from others

Note 2 does not add any useful Remove Note 2.                                                     Ed
information
Missing reference name         as described in 7.3.1.14 (Block AGREE. Updated with shift to       Ed
                               Ack Parameter Set Field)        REVmb 7.0 as baseline

Missing reference name           Table 7-57ab1 (A-MPDU        AGREE. Updated with REVmb           Ed
                                 contents MPDUs in VHT single as baseline. Table reference
                                 MPDU context)                include title.
Table 7-57z appears to be      Table 7-57y (A-MPDU contents AGREE. Updated with REVmb          Ed
wrong and missing reference    in the data enabled immediate as baseline. Table reference
name                           response context)             include title.

Table 7-57aa appears to be     Table 7-57z (A-MPDU contents AGREE. Updated with REVmb          Ed
wrong and missing reference    in the data enabled no       as baseline. Table reference
name                           immediate response context) include title.

Table 7-57ab appears to be     Table 7-57aa (A-MPDU          AGREE. Updated with REVmb         Ed
wrong and missing reference    contents in the PSMP context) as baseline. Table reference
name                                                         include title.
What is the table number of    Add the missing number and AGREE. Updated with REVmb            Ed
"Control Response"? Why is     coordinate 11ac dract with    as baseline. Table reference
the number of "Data Enabled    11baseline standard.          include title.
Immediate Response" not the
same as the 802.11 baseline
specification?

Missing reference and           Table 7-57ab (A-MPDU            Duplicate. See #163            Ed
reference name                  contents MPDUs in the control
                                response context)
Missing reference name          Table 7-57ab2 (A-MPDU           AGREE. Updated with REVmb      Ed
                                contents MPDUs in MU PPDU       as baseline. Table reference
                                context)                        include title.
Why do you need to put a        Change to Any single data       Yong has resolution            MAC
RTS/CTS/ACK etc… in A-MDPU MPDU/MMPDU
in single MPDU context? One
possible use that I can imagine
is carrying VHTC field. But
Control wrapper frame can be
used to carry VHTC field. It
should be single data MPDU or
MMPDU.

"The delimiter preceding the Change to the "delimiter of the AGREE. As suggested.              Ed
MPDU has the EOF field set to subframe containing the
1." can be misinterpreted to  MPDU"
imply a preceding subframe.
Again, why do you need to put Change to Any data MPDUs /            Yong has resolution    MAC
a RTS/CTS/ACK etc… in A-      Action no ACK
MDPU in MU MPDU context?

Data MPDUs will be part of this
kind of A-MPDU. Does 11ac
still allow to use Action no ACK
frame? If the answer is yes, it
should be part of this kind of A-
MPDU. If the answe is no, it
should not be part of this kind
of A-MPDU. And the table
"Data Enabled Immediate
Response", "Data Enabled No
Immediate Response",
"Control Response" should also
be changed by removing
Action no ACK items.




"At most one A-MPDU in the          Replace with the following:      Yong has resolution   MAC
MU PPDU is allowed to contain       "The multi-user PPDU consists
one or more MPDUs that" -           of at multiple A-MPDUs, each
this is too broad, for example,     directed to a different user. At
it would allow an RTS to be         most one of these A-MPDUs
aggregated.                         generates an immediate
solicit an immediate response       response, and its contents are
                                    described in Table 7-57z. The
                                    remaining A-MPDUs generate
                                    no immediate response, and
                                    their contents are described in
                                    Table 7-57aa." Delete the
                                    "Any MPDU" to the left.
Remove the restriction on        Change from                       Matt has resolution         MAC
GCMP use. GCMP is required       "Within an ESS, a VHT STA shall
for the high throuhgput rates    eliminate TKIP and GCMP as
(1- 7Gbps) supported in 11ac     choices for the pairwise cipher
and for Suite B applications.    suite if CCMP
GCMP is a secure mode, its use   is advertised by the AP or if the
should be allowed, and indeed    AP included either an HT
may be required for              Capabilities element or a VHT
performance of the high 11ac     Capabilities element
throughput rates.                in its Beacon and Probe
                                 Response frames. The
                                 elimination of TKIP and GCMP
                                 as choices for the pairwise
                                 cipher suite may result in a lack
                                 of overlap of the remaining
                                 pairwise cipher suite choices,
                                 in which case the
                                 VHT STA shall decline to create
                                 an RSN association with that
                                 AP."
                                 to
                                 "Within an ESS, a VHT STA shall
                                 eliminate TKIP and WEP as
                                 choices for the pairwise cipher
                                 suite if CCMP or GCMP
                                 are advertised by the AP or if
                                 the AP included either an HT
"Beacon, Probe Response,         Capabilities element or a make Matt
                                 Either delete this list, or VHT                               MAC
DLS Request, or DLS Response it comprehensive (i.e. add TDLS
messages." - we really must      setup frames)
find a cure for listers disease.

Why is this normative the first Make the status consistent.                                    Ed
time but just a NOTE the
second?
This is the first time when "VHT Insert "(9.7d.7)" after "a VHT   AGREE. As suggested (using   Ed
single MPDU" is used. Please single MPDU"                         new numbering)
refer to the section that
defines "VHT single MPDU".
The collision avoidance          Spedify new RTS/CTS            Haiguang. 11/410r2.             COEX
mechanism using RTS/CTS is       procedure for protection in
not good enough to protect       MU-MIMO transmission. It
the MU-MIMO downlink when        should be compatible with
data packets are sent to         legacy station also. One of
multiple stations                possible solutions is using
simultaneously, especially       single RTS multiple CTS to
when there are overlapped APs    protect the MU-MIMO
and some of them have legacy     downlink when the coverage of
stations. Some new collision     BSs are overlap to each other.
avoidance mechansim should
be designed.


Explain how VHT STAs perform For e.g. add following text         Chao-Chun                      COEX
fast collision inference on     "using
secondary channels.             INDICATED_CH_BANDWIDTH
                                in CTS frame" at end of the line
                                47.
Regarding the sentence          "helping the VHT STA                                            Ed
"helping the STA originating    originating the RTS … ".
the RTS …", it is clearer if we
put the type of STA.

"STA originating the RTS to" - originating->transmitting         Chao-Chun                      COEX
what's wrong with
"transmitting"? Originator is a
term tied to the BA
mechanism, so it's gratuitous
use in other contexts should be
minimized.

A VHT STA shall set the RIFS     as comment                      Yong                           MAC
capability bit to 0
The RTS receiver need to have    Proposed solution: If NAV is    AGREE IN PRINCIPLE.            COEX
PIFS time to correctly assess    set, RTS with broadcast         Resolution text in 11/348r0.
the CCA state; When RTS is       address shall be sent with PIFS
sent immediately following a     separation from an
previous frame (SIFS), the       immediately preceding frame
receiver might not be able to
correctly estimate the CCA
state on all channels; Need to
define what to do when RTS is
sent immediately following a
previous frame;
Erroneous reference. Section      11.20.4 should be revised to     AGREE. As suggested.         Ed
11.20.4 does not exist.           11.20.2. (see page 62)

reference number is incorrect     Change "11.20.4" to "11.20.2" Duplicate. See #50              Ed

In the case of transmissions to   Add one below the item"A VHT     AGREE IN PRINCIPLE. See #938. COEX
multiple destinations within an   STA performing clear channel     I agree that some text is
TXOP, TXOP holder may use         assessment (CCA) in the          needed, but proposed text
RTS/CTS to protect the data       secondary 20/40/80 channels      seems inaccurate; the CCA is
transmission for each             before                           not performed by the TXOP
destination. PIFS interval        transmitting a                   holder, CCA is performed by
should be used before sending     40/80/160/80+80 MHz mask         the RTS receiver. Moreover,
RTS.                              PPDU using EDCA channel          there is no need to specify
                                  access as described in 11.20.4   “other than the previous
                                  (STA CCA sensing in a VHT        responder”; previous
                                  BSS)"                            responder is not well defined;
                                  A VHT TXOP holder performing     also, referring to a previous
                                  clear channel assessment (CCA)   responder implies that TXOP
                                  in the secondary 20/40/80        holder needs to store the
                                  channels before transmitting     address of the previous
                                  RTS to a responder other than    responder; if previous
                                  the previous responder.          responder is allowed to use
                                                                   SIFS, then the CCA for the
                                                                   previous responder will not
                                                                   function properly (and that is
                                                                   what we are trying to solve).
                                                                   11/348r0.
The enhanced RTS CTS               Please reserve static RTS         Jarkko presented (383r0, 384r0 COEX
signaling as defined in            values 72 - 132 to indicate       is the normative text). Jarkko
802.11ac has many challenges:      probing operation and             will work further and discuss
1. Long duration in RTS frame      calculate the value of the CTS with others.
may lead to unnecessary            duration field by (RTS duration -
locking of the NAV at the          72)*32 micro seconds. If the
secondary channels, if a frame     requested bandwidth is
is transmitted within the CTS      available for transmission. If
timeout. For instance, two RTS     the requested bandwidth was
frames that are transmitted in     not available send CTS to
a short time may lock a NAV        available channels and set the
for the channel.                   duration field to RTS duration -
2. Also the STA that transmits     (SIFS + CTS).
static RTS frame should get
indication if the reservation
was not done due to lack of
bandwidth, i.e. not because
hte transmission of RTS frame
failed. This enables the backoff
rules use with static RTS frame.
3. The device that wants to
test available bandwidht with
dynamic RTS including short
duration is forced to perform
second RTS CTS signaling to set
the duration of the reservation
correctly. Two RTS CTS
In order causes overhead.
signalingto protect against        As specified                   Sandya                          COEX
hidden nodes, CTS must be
sent by all STAs that are
receivers of VHT frames. To
minimize overhead, a VHT RTS
frame should be defined that
requests all receiveing STAs to
sequentially send CTSs.

The Individual/Group bit is set    Include "when            Sandya                                COEX
to 1 only when the VHT STA is      CH_BANDWIDTH TXVECTOR is
trying to transmit >20MHz          greater than 20MHz"
mask PPDU and not 20MHz
only
Hyphen is missing in               CH_BANDWIDTH_TXVECTOR          DISAGREE. CH_BANDWIDTH is Ed
CH_BANDWIDTH_TXVECTOR                                             a TXVECTOR parameter.
"If the VHT STA sending the      Remove VHT                        AGREE. As suggested.   Ed
RTS frame" - avoid
unnecessary qualifiers. You
know it's a VHT STA because it
is now "the STA", not "a STA",
and the antecdent that
establishes the identify of "the
STA" also determines that is is
a VHT STA.

If the VHT STA sending the RTS    INDICATED_DYN_BANDWIDTH Sandya                          COEX
frame is using dynamic            is more meaningful if it is
bandwidth operation, it shall     boolean and change the
set the                           dynamic or static to true of
INDICATED_DYN_BANDWIDTH           false in the sentence
TXVECTOR parameter to
Dynamic. Otherwise, the STA
shall set the TXVECTOR
parameter
INDICATED_DYN_BANDWIDTH
to Static.
"If a VHT STA receives a RTS      Describe observable behaviour                           Ed
frame with the                    at the STA resulting from this
Individual/Group subfield in      condition.
the TA field set to 1, then the
INDICATED_DYN_BANDWIDTH
RXVECTOR parameter and the
INDICATED_CH_BANDWIDTH
RXVECTOR parameter are
valid."

So what? This is supposed to
be a description of behaviour,
not whether the STA considers
these parameters to be valid or
not.

Ditto 46.31
"Multicast/Unicast "bit in TA      A VHT STA that initiates a TXOP Sandya     COEX
has been changed into "            by transmitting a RTS with the
Individual/Group bit"              Multicast/Unicast
                                   Individual/Group bit in the TA
                                   set to Multicast 1, shall not
                                   send a RTS to a legacy STA for
                                   the duration of the TXOP.

A VHT STA that initiates a TXOP    Is it necessary to include this   Sandya   COEX
by transmitting a RTS with the     condition for the transmitting
Multicast/Unicast bit in the TA    VHT STA? What in case when
set to Multicast, shall not send   there is not CTS received by
a RTS to a legacy STA for the      this STA?
duration of the TXOP.

The restriction for VHT STA not    Delete the sentence or justify    Sandya   COEX
to transmit to legacy STA?         why it is needed.
What is a legacy STA? Is it non-
VHT STA
"legacy STA" - no, no, no, no,     Say what you mean, i.e. what Sandya        COEX
no.                                combination of capabilities are
                                   you trying to express with use
There is no such thing as a        of the evil word "legacy".
legacy STA.
The enhanced RTS CTS               When static RTS with duration      Jarkko presented (383r0, 384r0 COEX
signaling as defined in            field set to value between 72 -    is the normative text). Jarkko
802.11ac has many challenges:      132 is received and all            will work further and discuss
1. Long duration in RTS frame      requested bandwidth is             with others.
may lead to unnecessary            reserved, the duration field is
locking of the NAV at the          set to (RTS duration field - 72)
secondary channels, if a frame     *32 microseconds. If not all
is transmitted within the CTS      bandwidht may be reserved,
timeout. For instance, two RTS     the duration field is set to
frames that are transmitted in     duration in RTS - (SIFS + CTS).
a short time may lock a NAV
for the channel.
2. Also the STA that transmits
static RTS frame should get
indication if the reservation
was not done due to lack of
bandwidth, i.e. not because
hte transmission of RTS frame
failed. This enables the backoff
rules use with static RTS frame.
3. The device that wants to
test available bandwidht with
dynamic RTS including short
duration is forced to perform
second RTS CTS signaling to set
the duration of the reservation
correctly. Two RTS CTS
"Edit" is causes action for
signalingunclear overhead.         Replace "Edit section 9.2.0b.7 AGREE.                           Ed
editing.                           as follows." to "Change the
                                   first paragraph of 9.2.0b.7" and
                                   "Insert the sentence 9.2.0b.7
                                   as follows."

A non-VHT STA that is              It is for all STAs and applies to Sandya                        COEX
addressed by an RTS frame          VHT STA also. In addition to
shall transmit a CTS frame after   this when the RXVECTOR
a SIFS period if the NAV at the    parameter
STA receiving the RTS frame        INDICATED_DYN_BANDWIDTH
indicates that the medium is       is valid the conditions in the
idle.                              next two paragraphs need to
                                   be met.
This paragraph is poorly         You can probably structure this                               Ed
structured.                      as: "A VHT STA that is
                                 addressed by an RTS frame
The ideal structure for          shall respond as follows:" and
behaviour is: "An <entity> that create a dashed list of the
<event> shall <action>". By      different response types.
tacking on bits of the condition
describing the event to the      Regardless, please reword to
beginning of the para, it        make it closer to the ideal
becomes more difficult to        structure.
understand.

"the VHT STA" - there is no   use an indefinite article.           DISAGREE. Antecedents in the Ed
antecedent for this.                                               'if' clause.
"the RTS frame" - there is no
antecedent for this.
change the                    as comment                           AGREE. As suggested.        Ed
"INDICATED_CH_BANDWIDTH
parameter" to the
"INDICATED_CH_BANDWIDTH
RXVECTOR parameter"
To meet the rule of this sub-        Add the following paragraph      Reza   COEX
clause, that                         after line 4, page 46: "To save
"the VHT STA addressed by the        processing cycles at the STAs,
RTS frame shall respond with a       a secondary CCA IDLE Count
non-HT or non-HT duplicate           Request frame (SCR) is used to
CTS frame over all channels          alert STAs of an incoming RTS.
that are specified by the            SCR frame is transmitted in the
INDICATED_CH_BANDWIDTH               primary channel PIFS before
parameter of the RTS frame if        the transmission of RTS. STAs
all non-primary channels             receiving SCR will turn on their
indicated by the RTS frame           CCA detecting blocks and begin
have met the following               counting their IDLE time. SCR
condition: the PHY-                  frame contains SU or MU
CCA.indication primitive             indication and address of the
indicates IDLE during an             target STA/STA group.
interval of PIFS before the RTS
frame is received. A VHT STA
that is addressed by the RTS
frame shall not respond with a
CTS frame if the condition is
not met for any nonprimary
channel indicated by the RTS
frame".
it requires that all active STAs
must constantly compute their
CCA IDLE time for non-primary
channels. However, since most
packets the STAs receive are
the statement "non-primary           Clarify                         Reza    COEX
channels indicated by the RTS
frame", I am not sure in which
part of the RTS frame this
information is carried. Is their a
new RTS format that is mission
from the draft?
Why the CCA measurement in Please clarify.                    Reza                             COEX
CTS frame transmission is not
performed at the primary
channel?
The CCA measurement is
performed a PIFS before RTS
transmission, so it could be
busy. Also the busy channel is
not setting the NAV, rather
AIFS delay is used after the
busy period.
Is the assumption that the RTS
frame cannot be received if the
channel quality is too poor and
no other protection is needed
for the primary channel?




The behavior of STA for CTS      Change "may" to "should".    Reza                             COEX
over non-primary channels is
described as "may". However,
this makes the behavior
ambiguous.
change the                       as comment                   AGREE. As suggested.             Ed
"INDICATED_CH_BANDWIDTH
parameter" to the
"INDICATED_CH_BANDWIDTH
RXVECTOR parameter"
Clarify that the channels used as comment                     Reza                             COEX
to transmit CTS shall be a valid
channel combination

EDCA has not had a possibility Please clarify or delete the   Simone will provide a            COEX
to save the TXOP holder. The saved TXOP holder.               resolution on this and related
mechanism is briefly                                          comments
mentioned for HCCA. Please
clarify how the receiving STAs
detect which STA should be set
as the save TXOP holder.
How the saved TXOP holder is Please clarify.                  Reza   COEX
maintained, if during the NAV a
other frame that has TA or RA
not set to TXOPholder. Is the
saved TXOPholder updated, or
is the STA maintaining the
same TXOP holder for the NAV
duration?


What happens if a STA receives Please clarify.                Reza   COEX
a frame that extends the NAV
duraiton from the saved TXOP
holder? Is the saved TXOP
holder maintained and just the
duration of the NAV extended?


When Reverse Direction Grant Please clarify.                  Reza   COEX
is used, is he saved TXOP
holder updated when the
reverse direction TXOP is taken
into use?
Does the saved TXOP holder      Please clarify                Reza   COEX
have to be from the same BSS?
May any TXOP holder be the
saved TXOP holder?

The meaning of the sentence is Please make the sentence              Ed
difficult to understand. Is the more understandable.
sentence saying: " If the NAV at
the STA receiving the RTS
indicates the mediium is not
idle and the TA matches to
saved TXOP holder (see section
9.9.2.2a) that STA shall
respond to the RTS frame."


Is there any restriction how    Please clarify and justify.   Reza   COEX
many RTS messages may be
transmitted within a TXOP?
The group addressed frames         Allow the RTS CTS transmission Jarkko will present   COEX
may not use RTS CTS signaling.     before the group addressed
If a 802.11ac network has only     frames. Allow multiple group
802.11ac devices and operates      addressed PPDU transmission
in OBSS state, the BSS cannot      in the same TXOP to increase
efficiently detect the available   the efficiency of the group
bandwidht to send the group        addressed frames
addressed frames. Also the RTS     transmission.
CTS signaling before the group
addresssed frames
transmission improves the
reliability of the group
addressed frames delivery.


Rules for how to send              Specify.                       Yongho has proposed   MU
Sounding Poll and NDPA                                            resolution
control frames should be
specified here.
Control frames carried in an A-    Cover the case of single A-    Yongho has proposed   MAC
MPDU that is not a VHT single      MPDU                           resolution
MPDU shall …"; is the case of
single MPDU defined
somewhere?
What is the rate selection rules   Clarify it.                    Yongho has proposed   MAC
for control frame in VHT single                                   resolution
MPDU? If the rules are same
as the rate selection rules of
VHT single MPDU, when should
control frame in VHT single
MPDU be used?

How a STA can anticipate the discuss                              Reza                  COEX
reception of an RTS and check
that all non-primary channel
ate IDLE for a period of PIFS in
advance? This rule seems to be
non-implementable, or at least
difficult to implement.

When                           Clarify the transmitted form of Reza                     COEX
INDICATED_DYN_BANDWIDTH a CTS frame considering tx BW.
RXVECTOR is set to Dynamic, it
is not clear whether a CTS
frame is non-HT or non-HT
duplicate.
Clarify whether and how SDMA Specify.                                Yongho has proposed             COEX
of PPDUs of different                                                resolution
bandwidth can be done.

Providing BW signaling in all      Change paragraph to read "A Robert has a proposed                 COEX
control frames is not necessary    VHT STA that transmits a        resolution
and complicates                    control frame carried in non-
implementation. In some            HT or non-HT duplicate format
implementations BAR/BA is          (40 MHz or wider) and
always 20 MHz (more robust).       addressed to a VHT STA and
Make BW signaling for 20 MHz       eliciting a control response
in Non-HT frames optional and      frame or a sounding feedback
only require it in 40 MHz (or      management frame shall set
wider) non-HT duplicate.           the
                                   INDICATED_CH_BANDWIDTH
                                   TXVECTOR parameter of the
                                   control frame to the same
                                   value as the CH_BANDWIDTH
                                   TXVECTOR parameter and shall
                                   set the Individual/Group bit in
                                   the TA field to 1. NOTE--A VHT
                                   STA is not required to signal
                                   frame badwdith in a 20 MHz
                                   non-HT format frame."




Grammer is wrong: '~ and           Change '~ and eliciting a         DISAGREE. Eliciting a control   Ed
eliciting a control response       control response frame ~' to '~   response is a feature of the
frame ~' should be '~ and          and elicits a control response    control frame, thus eliciting
elicits a control response frame   frame ~'                          (not elicits) is appropriate.
~'
The description here is not        change the first sentence to " Yongho has proposed                COEX
consistant with the description    An HT or VHT STA that receives resolution
in the immediately following       a frame without a valid
paragraph.                         INDICATED_CH_BANDWIDTH_
                                   RXVECTOR parameter and
                                   that…."

Duplicated Table number.           Change table number 9-3 to        AGREE. All figures and tables   Ed
Table number 9-3 is already        other non duplicated number       renumbered to align with
used in the 802.11 baseline                                          REVmb 7.0, with unique
document                                                             assignments for new figures
                                                                     and tables.
Clarification:                  Change the sentence to "A VHT                           Ed
"A VHT STA that receives a      STA that receives a frame that
frame with a valid              elicits a response frame and
INDICATED_CH_BANDWIDTH          have a valid
RXVECTOR parameter              INDICATED_CH_BANDWIDTH
and that elicits a response     RXVECTOR parameter
frame shall send the response   shall send the response frame
frame ~"                        ~"

When the                        Change "HT_CBW160,                Yongho has proposed   COEX
INDICATED_CH_BANDWIDTH          NON_HT_CBW20,                     resolution
RXVECTOR value is               NON_HT_CBW40,..." into
NON_HT_CBW80+80, the            "HT_CBW80+80,
mapping CH_BANDWIDTH            NON_HT_CBW20,
TXVECTOR value cannot be        NON_HT_CBW40,..."
HT_CBW160.
"may be set to                  Suggest to add "as specified in                         Ed
indicate a narrower bandwidth   9.2.0b7"
than indicated in the
INDICATED_CH_BANDWIDTH
RXVECTOR parameter
of the RTS frame."

BANDWDITH -> BANDWIDTH          As in comment.                    AGREE. As suggested   Ed

Regarding the text "… to a STA Change the text as follows:                              Ed
that exceeds…".                "… to a VHT STA that
                               exceeds…"
The maximum A-MSDU size is        Change to                       Mark   MAC
stated parenthetically in         "A STA shall not transmit an A-
section 7 to                      MSDU in a VHT format PPDU
be 11398 octets, which is         to a STA
clarified to be 11454 octets      that exceeds the maximum
minus the                         MPDU length capability
maximum size of a MAC             indicated in
header (36 octets), CCMP          the VHT Capability element
encapsulation (16                 minus 56 octets."
octets) and FCS (4 octets).       or define the sizes in the VHT
                                  Capabilities field as being the
However, 9.7c only requires       maximum A-MSDU length, as
the maximum MPDU length           in 11n (but then need to
not to be                         rework 7.2.3.0a).
exceeded. Hence if a non-
maximal MAC header is used
(i.e. one
without Address 4 and/or HT
Control) and/or encryption is
not used
then there appears to be
nothing normative stopping a
STA from
sending an A-MSDU of size
greater than 11398 octets (e.g.
11424
octets, for one without A4,
HTC or CCMP).
A-MPDU length limit rules for Change the paragraph in 9.7d.2 Jae Seung                    MAC
VHT should be added to this   in 802.11n spec to include A-
section. Additional note from MPDU length limit rules for
                              VHT. (1) Example sentence is
                              as follows: "A VHT STA
                              indicates a value in the
                              Maximum A-MPDU Length
                              Exponent field in its VHT
                              Capabilities element that
                              defines the maximum A-MPDU
                              length that it can receive. The
                              encoding of this field is defined
                              in Table 7-17 (Subfields of the
                              A-MPDU Parameters field).
                              Using this field, the STA
                              establishes at association the
                              maximum length of A-MPDUs
                              that will be sent to it. The STA
                              shall be capable of receiving A-
                              MPDUs of length up to the
                              value indicated by this field. A
                              VHT STA shall not transmit an
                              A-MPDU that is longer than the
                              value indicated by the
                              Maximum A-MPDU Length
                              Exponent field declared by the
                              intended receiver." (2)
A received PSDU is determined Following text should be added
                              RXVECTOR.FORMAT = VHT                                       Ed
to be an A-MPDU when the
associated PHY-
RXSTART.indication primitive
RXVECTOR AGGREGATION
parameter is set to 1 or the
TXVECTOR.FORMAT parameter
is set to VHT.

Editing instruction should also per comment                 AGREE IN PRINCIPLE. Editing   Ed
insert 9.7e                                                 instruction added.
Clarify whether the padding is Clarify/specify.             Yong                          MAC
only inserted at the end of the
AMPDU or if it can be
dispersed/distributed and if so,
how.

A-MSDUs may not be              Change to "a fragmented     Robert                        MAC
fragmented.                     MSDU or MMPDU".
1) A VHT Single MPDU may     clarify                       Robert      MAC
also be transmitted in a MU
PPDU (at most one Single
MPDU can be included in a MU
PPDU); 2) Why "results in
transmission of multiple VHT
single MPDUs" when TXOP
limit is 0?
A single MSDU, MMPDU or A- Not clear what this sentence is Robert      MAC
MSDU may be transmitted in a trying to indicate
SU PPDU when the TXOP limit
is 0, which may result in
transmission of multiple VHT
single MPDUs.

A-MSDUs may not be              Change to "A single MSDU or   Robert   MAC
fragmented.                     MMPDU".
Do not understand why this      Please clarify.               Robert   MAC
sentence ", which may result in
transmission of multiple VHT
single MPDUs."

I do not understand why you     Change the bullet to "VHT     Robert   MAC
just mention "A QoS+CF-ACK      single MPDU has the same
frame may also include an RDG   rules as non-VHT MPDU when
as described in 9.15.3" here.   RD operation is executed" and
Why don't you say that VHT      remove the following bullet.
single MPDU has the same
rules as non-VHT MPDU when
RD operation is executed.


How does this behavior is       delete it                     Robert   MAC
related to the topic of this
section "Transport of VHT
single MPDUs"?
Insertion of partial AID is        Resolve potential and certain   COUNTER. Although it is true MAC
described, but not reception. conflicts                            that energy-constrained
Processing of partial AID                                          devices are unlikely to process
potentially allows clients to not                                  non-intended packets once a
continue to receive the                                            disinteresting Partial AID is
Duration/ID field, with reduced                                    received, there are many non-
collision avoidance capacity. Is                                   energy constrained devices
this potential allowed? Also,                                      such as mains or PoE-powered
MU-MIMO transmissions,                                             APs. Moreover, such devices a)
especially MU-MIMO                                                 transmit the majority of the
transmissions where a STA is                                       downlink-dominated traffic, b)
assigned 0 STSs, has a similar                                     often have higher sensitivity
effect and in 22.3.12.3 it is                                      and/or c) more antennas, so in
explicitly stated that the client                                  this instance the Duration/ID
can drop the packet well                                           field is decodable and adds
before the Duration/ID field.                                      incremental value. Accordingly
However, potentially the                                           leave the Duration/ID field
partial AID language, and                                          unchanged. Partial AID was
certainly 22.3.12.3 is in conflict                                 introduced to allow non-
with 11.20.3 where it says "A                                      addressed clients to sleep
VHT STA shall update its NAV                                       during disinteresting frames.
using the Duration/ID field                                        11.20.3 is not in conflict with
value in any frame received in                                     this expectation since
a 20 MHz PPDU in the primary                                       “receiving” of these
20 MHz channel or received in                                      disinteresting frames is not
a 40 MHz PPDU in the primary                                       required. However, a note to
40 MHz channel or received in                                      this effect would reduce the
The partial AID in the PPDUs
a 80MHz PPDU in VHTprimaryis Please add the following text         likelihood of recommenting.
                                                                   Simone.                         MAC
not explained for mesh BSS.        to line 43: " In mesh BSS the
                                   AID of the peer mesh STA is
                                   obtained from the mesh
                                   peering establishment".

Text on Group ID field in a SU     Add the following text from       Simone. 11/0344r0.          MAC
VHT PPDU is missing (The           Sepc framework to section
description is in section 6.6 of   9.7e or to any other section on
the spec framework                 Group ID: "In a SU VHT PPDU,
document)                          if the PPDU carries MPDUs
                                   addressed to an AP STA, the
                                   Group ID field is set to all
                                   zeros, otherwise it is set to all
                                   ones."
"Partial AID parameter" is            Change to "PARTIAL_AID            AGREE. Consistently use         Ed
inconsistent with rest of             parameter".                       "TXVECTOR parameter
section.                                                                PARTIAL_AID" throughput this
                                                                        section. "PARTIAL_AID" in
                                                                        formula does not require the
                                                                        "TXVECVTOR parameter" prefix
                                                                        since it is clear from the
                                                                        preceding sentence that this is
                                                                        the value assigned to the
                                                                        parameter.

A DLS STA or IBSS STA is a non-       Add "sent by an AP" just before AGREE IN PRINCIPLE. Modified Ed
AP STA, so the text is self-          the comma.                      to "In a VHT PPDU sent by an
contradictory.                                                        AP…"
partial AID computation               change to a text equation form AGREE. Unweirded with         Ed
equation seems to be bitmap           used in other sections.         conversion to text.
image, and looks weird.

change bitmap image to text                                             Duplciate. See #1054            Ed
equation
It's not totally clear to me that     Clarify BSSID[0:7] construction                                   Ed
MAC Adresses have, and hence          and consider whether
the BSSID has, a well-defined         BSSID[2:9] should be used
endianness, in terms of the bit       instead.
numbering. The lsb of the first
octet on the air is the I/G bit; is
that the octet used in
construction of the partial AID
for from-AP MPDUs? If so, half
of the intended mixing has
been lost since the I/G and U/L
bits are fixed in an ESS BSSID.




"AP STA" - there is no such           seek and destroy globally         AGREE. Bam! (global search      Ed
term                                                                    only turned up this instance)
When a STA shares same lower Choose a special GID for STA-to- Simone. 11/0344r0.   MAC
9 bits of BSSID of a neighbor      AP packets.
AP, it won't be able to do AID-
based power save as seeing
any unicast packets to that AP.
The odds is still high, while it's
easy to solve by setting special
GID for STA-to-AP packets.


It's unclear what this       Please clarify.                       Robert          MAC
statement means. How can
one SU PPDU "result in
transmission of multiple VHT
single MPDUs"?
How does this behavior is    delete it                             Robert          MAC
related to the topic of this
section "Transport of VHT
single MPDUs"?
Should be an EDCAF of an AP as comment                                             Ed
has obtained a medium access

The information about the         In order to add some                             Ed
type of APs is needed. Since      explanation about the AP, the
legacy APs do not support         commentator proposes to
EDCA TXOP sharing we should       change the sentence
add some more explanation.        "of an AP has obtained …" to
                                  "of an AP that supports DL MU-
                                  MIMO transmission has
                                  obtained …".

The sharing of the EDCA TXOP Use the same language in the          Osama           MAC
is not using the appropriate introduction as in the
terminology, i.e. EDCAF as   normative text.
described in 9.9.1.2a

The text: M"in the same AP"       As in comment.                   Osama           MAC
seems not to have valid
meaning. Clarify the meaning
of this statement or delete it.
The bandwidth reservation      Please add the RTS-CTS-CTS-to- Jarkko presented (383r0, 384r0 COEX
scheme would benefit from      self message exchange for      is the normative text). Jarkko
possibility that the CTS       TXOPLimit 0 cases.             will work further and discuss
transmitter calculates the                                    with others.
duration for the TXOP based
on the RTS message
information. In this scheme
RTS- CTS and CTS-to-self
frames are transmitted. CTS
and CTS-to-self contain the
NAV for the reservation.

Why is VHT single MPDU         clearify it.                   Osama                        MAC
excluded here? What is the
rule to transmit VHT single
MPDU when TXOP limit is 0?

The statements says that the Please clarify                   Osama                        MAC
transmission rules are for "... A-
MPDU that is not a VHT single
MPDU…" Why is there a
difference in TXOP rules for A-
MPDU that is not a VHT single
MPDU and a VHT single
MPDU? If there is such a
difference, what are the TXOP
rules for VHT single MPDUs?

This appears to suggest VHT    Delete the added text.         Osama                        MAC
single MPDUs may not be used
if the TXOP Limit is 0 -- why?

The possibility to use a single Allow at least two RTS CTS    Jarkko                       COEX
RTS CTS signaling when the       message exchanges when the
TXOPlimit is set to 0 is         TXOPLimit is set to 0.
restricting unnecessarily the
TXOP holder possibility to first
detect the bandwidth of the
TXOP and in the next RTS CTS
adjust the duration of the
channel reservation based on
the reserved bandwidth.
"In addition, a TXOP holder           Rewrite the rules of single MU Osama   MAC
may transmit using a single MU        PPDU transmission per non-
PPDU A-MPDUs intended for             VHT PPDU transmission when
different users."                     TXOP limit is 0.

For non-VHT PPDU
transmimission when TXOP
limit is 0, the behavior is clearly
defined: you can use RTS/CTS
etc. to protect the
transmission, you can do
beamforming in the
transmission. It is not clear the
if they are still true in a single
MU PPDU transmission. I think
they are still true.


It is better to integrate the MU      as comment                             Ed
PPDU case into the above
frame types (allowed to be
transmitted when TXOP limit =
0)
"In addition, a TXOP holder           Replace with: "A VHT A-MPDU Osama      MAC
may transmit using a single MU        transmitted subject to this rule
PPDU A-MPDUs intended for             may be extended with A-
different users."                     MPDUs intended for other
                                      users, provided that this does
I'm not clear about what "in          not extend the duration of the
addition" means, but this             PPDU, and subject to the MU
seems imprecise given the             Context rules in 7.4a.3."
forgoing.

In addition, a TXOP holder may        Meaning of single MU PPDU A-           Ed
transmit using a single MU            MPDUs is not clear. Change to
PPDU A-MPDUs intended for             "In addition, the TXOP holder
different users.                      may transmit A-MPDUs
                                      intended for different STAs
                                      using single MU PPDU"
The sentence is saying: "Up to Please clarify.                     Allan.                 MAC
four STAs can be destinations
for a DL MU-MIMO
transmission." Is it clear that
one transmission refers to
trnasmission of a single PPDU
and not the TXOP?

"may choose to share" - the         "may share"                    AGREE. As suggested.   Ed
act of choosing by the STA is
not germain
"If a destination is targeted by    Change to "If a destination is Allan.                 MAC
frames in the queues of both        targeted by frames in the
primary AC and secondary AC,        queues of both primary AC and
it is still a primary destination   secondary AC, the frames in
and the frames in the primary       the primary AC queue should
AC queue should be added to         be added to the A-MPDU for
the A-MPDU for that                 that destination first. If the
destination first."                 frames in the primary AC
                                    queue should be added to the
I doubt about it. If the a          A-MPDU for that destination
destination is s targeted by        first, it is still a primary
frames in the queues of both        destination, otherwise it is
primary AC and secondary AC         called a secondary
and the frames from the             destination."
secondary AC queue is added
to A-MPDU, is the destinaiton
still called the primary
destination?


"If a destination is targeted by     the rule should be a Shall,   Allan.                 MAC
frames in the queues of both        otherwise an AP can contend
primary AC and secondary AC,        with parameters of the primary
it is still a primary destination   AC and then include traffic of
and the frames in the primary       the secondary AC at the last
AC queue should be added to         minute
the A-MPDU for that
destination first;"
The sentence "it is still a      Remove "it is still a primary   Allan.   MAC
primary destination" is          destination and" from the
redundant and not strictly       sentence.
correct here. If later on in
same TXOP frames in
secondary AC is transmitted,
it's not primary destination
anymore.

"should be added to the A-       Reword so that it does not give Allan.   MAC
MPDU for that destination        this impression. Perhaps show
first."                          a picture or two to illustrate
                                 the fundamental concepts.
It is hard to read this in any
way except as describing a
multi-destination A-MPDU.
It is a little ambiguous on                                      Allan.   MAC
whether any additiona
consideration of bandwith
indication/adjustment when
TXOP sharing is used
"When sharing, the TXOP          Change to "When sharing, the Allan.      MAC
duration is bounded by the       TXOP duration is bounded by
TXOP limit of the primary AC.    the TXOP limit of the primary
In addition, the AMPDU for       AC. In addition, the AMPDU for
one user in each DL MU-MIMO      at least one user in each DL
PPDU shall contain only MSDUs    MU-MIMO PPDU shall contain
from the primary AC."            only MSDUs from the primary
                                 AC. And the longest A-MPDU
Do you allow in a DL MU-         shall be A-MPDU from the
MIMO PPDU the longest A-         primary AC."
MPDU can be A-MPDU of
secondary AC? I think the
answer shoud be no.

The primary AC queue can         Modify the sentence to          Allan.   MAC
contain frames destined for      explicitly state how the TXOP
multiple different destinations. duration is determined.
The TXOP duration should be
determined by the duration of
the packets destined for one of
the primary destinations. Such
a rule is missing from the
section.
The sentence, "In addition, the this needs group discussion       Allan.   MAC
A-MPDU for one user in each
DL MU-MIMO PPDU shall
contain only MSDUs from the
primary AC", is confusing. we
defined the concept of stream
sets in earlier versions and we
require each PPDU shall
contain at least one stream set
for the primary AC. It seems
this concept has been removed
and the current description is
not clear.


In addition, the AMPDU for    MPDUs instead of MSDUs              Allan.   MAC
one user in each DL MU-MIMO
PPDU shall contain only MSDUs
from the primary AC.

"DL MU-MIMO PPDU" should           As in comment.                          Ed
be changed to "MU-MIMO
PPDU." "MU-MIMO PPDU"
inherently suggests downlink
transmission and "MU-MIMO
PPDU" is used at all of the
other sections.
"In addition, the AMPDU       Propose to specify "In addition, Allan.      MAC
for one user in each DL MU-   the AMPDU
MIMO PPDU shall contain only  for at least one user in each DL
MSDUs from the primary AC"    MU-MIMO PPDU shall contain
                              only MSDUs from the primary
                              AC"
Why "the A-MPDU for one user Did you want to say "at least     Allan.      MAC
in each DL MU-MIMO PPDU       one user's AMPDU in each DL
shall contain only MSDUs from MU-MIMO PPDU shall contain
the primary AC"?              MSDUs from the primary AC"?

The description is not clear. Is   Clarify the description as "In Allan.   MAC
the A-MPDU for only one user       addition, the A-MPDU for at
in a DL MU-MIMO PPDU or the        least one user in each DL MU-
A-MPDU for one of the users in     MIMO PPDU shall contain only
such a PPDU?                       MSDUs from the primary AC"
Some errors on Editor's note.    Propose to change the editor's AGREE. Instruction updated.     Ed
                                 note as follows:
                                 "Change the corresponding
                                 paragraphs in section 9.9.1.4 as
                                 shown here."
Editing instruction should refer per comment                      AGREE. Instruction updated.   Ed
to all the changed paragraphs

No need to define primary       Remove all text related to       Allan.                         MAC
destination and secondary       primary destination and
destination. The only rule for secondary destination
TXOP sharing is that a MU
PPDU shall contain at least one
A-MPDU with MPDUs
belonging to the primary AC.

The statement "… the frames      As in comment                   Allan.                         MAC
in the primary AC queues
should be added to the A-
MPDU for that destination
first." suggests that one A-
MPDU can contain frames
from multiple Acs. Is this the
intention? If so, response
behavior to such an A-MPDU
should be defined. If not,
remove the statement.


For the rule in clause 9.2.0b.4.2 Delete the sentence "(or RIFS, Jason.                         MAC
that a VHT STA shall not          under the conditions defined in
transmit frames separated by a 9.3.2.4.2 (RIFS))"
RIFS, the sentence "(or RIFS,
under the conditions defined in
9.3.2.4.2 (RIFS))" should be
deleted.

the term "STA" here is not       change "STA" to "TXOP holder"   Jason.                         MAC
clear
§ 9.3.2.4.2 (RIFS) appears to be § 9.2.0b.4.2 (RIFS)             AGREE. Reference updated       Ed
incorrect                                                        (new numbering)
Is it correct to include RIFS                                    Jason.                         MAC
here, because RIFS is deleted in
VHT.
Erroneous reference.             Change 9.24.4 into 9.15.4     AGREE IN PRINCIPLE. However, Ed
                                                               with renumbering to REVmb
                                                               7.0 reference is correct.

§ 9.24.4 (Rules for RD           § 9.15.4 (Rules for RD        Duplicate. See #732.          Ed
responder) appears to be         responder)
incorrect
the VHT STA should be            change "the HT STA" to "the HT Jason.                       MAC
contained                        or VHT STA"
the VHT STA should be            change "the HT STA" to "the HT Jason.                       MAC
contained                        or VHT STA"
§ 9.3.2.2 (CS mechanism)         § 9.2.0b.2 (CS mechanism)      AGREE IN PRINCIPLE. However, Ed
appears to be incorrect                                         with renumbering to REVmb
                                                                7.0 reference is correct.

§ 9.3.7 (DCF timing relations)   § 9.2.10 (DCF timing relations) AGREE IN PRINCIPLE. However, Ed
appears to be incorrect                                          with renumbering to REVmb
                                                                 7.0 reference is correct.

§ 9.19.2.5 (EDCA backoff         § 9.9.1.5 (EDCA backoff       AGREE IN PRINCIPLE. However, Ed
procedure) appears to be         procedure)                    with renumbering to REVmb
incorrect                                                      7.0 reference is correct.

that is described in 9.19.2.5    backoff procedure that is     AGREE IN PRINCIPLE. However, Ed
(EDCA backoff procedure).        described in 9.9.1.5 (EDCA    with renumbering to REVmb
                                 backoff procedure).           7.0 reference is correct.

§ 9.19.2.5 (EDCA backoff         § 9.9.1.5 (EDCA backoff       AGREE IN PRINCIPLE. However, Ed
procedure) appears to be         procedure)                    with renumbering to REVmb
incorrect                                                      7.0 reference is correct.

in 9.19.2.5 (EDCA backoff        in 9.9.1.5 (EDCA backoff      AGREE IN PRINCIPLE. However, Ed
procedure).                      procedure).                   with renumbering to REVmb
                                                               7.0 reference is correct.

The statement "a multiple      replace "not a STA" to "of a    Jason.                        MAC
frame transmission is granted STA"
to an EDCAF not a STA" is
confusing. It could imply that
multiple frame transmissions
could happen from the same
EDCAF from multiple stations.
§ 9.25 (PSMP Operation)           § 9.16 (PSMP Operation)           AGREE IN PRINCIPLE. However, Ed
appears to be incorrect                                             with renumbering to REVmb
                                                                    7.0 reference is correct.

Why isn't TXOP bandwidth text     Make the text normative.          Jason.                      MAC
normative?
Why the bandwidth of the          Allow the possibility to      Jason.                          MAC
TXOP cannot be increased          increase bandwidth during the
after the first PPDU              TXOP.
trnasmission? The bandwidth
increase during the TXOP
would increase the efficiency
of the system by reducing the
number of TXOP terminations
and being able to increase the
bandwidth without obtaining
the TXOP.


"A TXOP is obtained after a STA    The text for second sentence     Jason.                      MAC
transmitting an initial frame     should be more generic and
successfully receives a           include all frames with a valid
response frame. If the initial    BW indication and not only
frame is a data frame with        'data' frames
bandwidth indication, the
bandwidth indicated in the
data frame determines the
bandwidth obtained for the
TXOP " Why specify behavior
for only "data" frames? what
about control or management
frames etc.?
"For VHT STAs, if the response  Option 1:                      Jason.               MAC
                                For VHT STAs, when there are
frame to the initial frame is the
CTS frame, the bandwidth        multiple RTS/CTS exhcanges
indicated in the CTS frame      for protection and channel
determines the bandwidth        bandwith negotiation in a VHT
obtained for the TXOP."         TXOP, the bandwidh use for a
                                MPDU/MPDUs in a PPDU shall
This statement can not be used be the smallest bandwidth
by multiple RTS/CTS scenario in indicated by CTS that the
a TXOP.                         receiver/receivers of the PPDU
                                transmited.

                                    Option 2:
                                    For VHT STAs, when there are
                                    multiple RTS/CTS exchange for
                                    protection and channel
                                    bandwith negotiation in a VHT
                                    TXOP, the minimum bandwidth
                                    indicated in the CTS frames
                                    determine the bandwidth
                                    obtained for the TXOP.




"if the response frame to the       "a CTS frame"                   AGREE. the->a   Ed
initial frame is the CTS frame" -
incorrect article
"the STA" here is not very          clarify                         Jason.          MAC
clear. Is it TXOP holder only or
both the TXOP holder and
TXOP responder?
This paragraph does not deal        Change the draft to deal with 3 Jason.          MAC
with the following scenarios or     scenario mentioned in
should be improved for the          comment column.
following scenarios:
1), RTS/CTS protected TXOP,
2), CTS-to-self protected TXOP,
3), VHT BSS without
overlapping BSS and
overlapping BSSes have same
primary channel.
"If there is no non-HT duplicate Limit this statement to non-      Jason.                    MAC
frame exchange in a TXOP, the initial PPDUs.
TXOP holder shall set the
CH_BANDWIDTH
parameter in TXVECTOR of a
PPDU to be the same or
narrower than the
CH_BANDWIDTH parameter in
TXVECTOR of the preceding
PPDU that it has transmitted in
the same TXOP." - this creates
a problem when attempted to
be applied to the first PPDU in
the TXOP.




The section number (6.0.0.1) is As in comment.                     AGREE. Updated with new   Ed
incorrect. The correct number                                      numbering.
is 9.9.1.5.

A typo. The clause index should   As described.                    Duplicate. See #551.      Ed
be "9.9.1.5" rather than
"6.0.0.1."
Congratulations on the funky                                       Duplicate. See #551.      Ed
numbering
Clause number incorrect           6.0.0.1-->9.9.1.5                Duplicate. See #551.      Ed
A wrong clause index; EDCA        change '9.9.1.5 EDCA backoff     Duplicate. See #551.      Ed
backoff procedure is 9.9.1.5.     procedure'

the section number is wrong       change "6.0.0.1 " to "9.9.1.5"   Duplicate. See #551.      Ed

The clause numbering has gone Change to 9.9.1.5, probably.         Duplicate. See #551.      Ed
wrong.
Section number, "6.0.0.1",    change to the correct one            Duplicate. See #551.      Ed
seems wrong
section number is wrong       needs to be changed into             Duplicate. See #551.      Ed
                              9.9.1.5
Section number is incorrect.  Change section number 6.0.0.1        Duplicate. See #551.      Ed
                              to 9.9.15
the section number is wrong   change from "6.0.0.1" to             Duplicate. See #551.      Ed
                              "9.9.1.5"
Editing instruction should be     per comment                    AGREE. Editing isntruction          Ed
more precise about which                                         updated.
paragraphs are changed than
"the corresponding
paragraphs".

"PPDU or MU-MIMO PPDU" - Remove the chocolate cakes.             Allan.                              MU
this is syntacally equivalent to
saying "I like cakes or
chocolate cakes". That I like
chocolate cakes may be
determined from the fact I like
cakes.

And there's more chocolate
cake at line 65.
The following sentence was      this needs group discussion      Allan.                              MU
not clear since we have agreed
that the transmission can be
considered successful if one of
the PPDUs in a MU-MIMO
transmission is successful.
"All the MPDUs in the final
PPDU or MU-MIMO PPDU
transmission by the TXOP
holder initiated during the
TXOP for that AC was
successful and the TXNAV
timer has expired."


Font size seems different from    needs re-adjusting the font-   AGREE. Formatting corrected.        Ed
others                            size
The sentence is not very clear.   change accordingly             Allan.                              MU
Suggest adding "that counts
down to zero" after "the
backoff counter".
are we missing an e) ?            add one                        Ed. I don't think it is condition   MAC
                                                                 for backoff. I'm not sure what
                                                                 this means.
The following sentence could Define specifc rules for the         Allan.   MU
be OK for now as the first      events that were mentioned.
draft. However, it does not
regulate the backoff behavior
when the specified events
happen. Having different
backoff procedures at different
STAs may cause fairness issues.
"In addition, the backoff
procedure may be invoked for
an EDCAF when the
transmission of one or more
MPDUs in a non-initial PPDU or
MU-MIMO PPDU by the TXOP
holder fails."




VHT RD rules are not clear:     Make it clear that in VHT      Osama.      MAC
What you added is only for      transmission, only VHT single
QoS+CF-ACK in HCCA.             MPDU can use RD operation.
                                Otherwise the rules for DL MU-
                                MIMO should be clarified.

Use of RD should not be         Define a mechanism where RD Osama.         MAC
limited to only single MPDU. It frames from multiple STAs can
would be beneficial to allow    be requested.
RD to be utilized for VHT
sequence.

It is not clear what is +VHTC   Add (i.e., frames with an VHT              Ed
frame.                          Control field) following + VHTC
                                frame.
"A STA that supports VHT link     1) Introduce a "VHT link           Daewon. 11/304r0.   MU
adaptation using the VHT          Adaptation" capability
Control field shall set the MCS   indication in VHT Capability
Feedback field of the HT          element; Proposed changes:
Extended Capabilities field to    VHT Link Adaptation capability
Unsolicited or Both, depending    in VHT Capability element; 2
on its specific MCS feedback      bits (B23-24)
capability, in HT capabilities    Set to 0 (No Feedback) if the
elements that it transmits";      STA does not provide VHT MFB
Need to introduce an              Set to 2 (Unsolicited) if the STA
independent capability            provides only unsolicited VHT
indication for VHT Link           MFB Set to 3 (Both) if the STA
adaptation; an implementation     can provide VHT MFB in
may support HT link adaptation    response to VHT MRQ (either
but not VHT and vice versa.       Delayed or Immediate, see
                                  9.27.1 (Introduction)) as well
                                  as unsolicited VHT MFB; The
                                  value 1 is reserved; ---------- 2)
                                  in the text referenced by this
                                  comment, change the
                                  reference to HT Extended
                                  capability to the capability
                                  defined in point 1)




Is this supposed to be talking    Relate solely to VHT            Daewon. 11/304r0.      MU
about the HT or VHT               capabilities and behaviour
structures?

Why do we care about HT link
adaptation?
"+VHTC" needs to be defined Define +VHTC                          Daewon. 11/304r0.      MU
in the same way as +HTC is
defined in 802.11n
There is no definition of     Add the following sentences. Daewon. 11/304r0.      MU
"+VHTC" before to the section Insert the following sentences
and it should be added.       just after the definition of
                              "+HTC frame" in "7.1.1
                              Conventions".
                              A frame that contains the HT
                              Control field in which HT/VHT
                              subfield set to 1, including the
                              Control Wrapper frame, is
                              referred to as a +VHTC frame.


The +VHTC terminology has       Add description where +HTC is                     Ed
not been described anywhere     introduced.

Grammer:                        Better put comma as "In each                      Ed
"In each request the MFB        request,"
requester shall set the MSI
field to a value in the range 0
to 6"
STS should be subscript in VHT                                                    Ed
NSTS
"STS" in "NSTS" should be       As in comment.                                    Ed
subscript. There are also two
identical errors on the 7th and
24th line in page 56.


Inappropriate user of notation Use subscripts for "STS" in                        Ed
on "NSTS"                      "NSTS".
NSTS should be Nsts            change the font                                    Ed

NSTS should be Nsts (subscript) change accordingly                                Ed

misspelling                     Change NSTS to NSTS                               Ed
NDPA is a PPDU                  no need to explicitly mention Daewon. 11/304r0.   Ed
                                the "PPDU" as an independent
                                case; remove uneecessary text
This is more chocolate cake -        I really don't know what this   Daewon has a proposed   MU
with cream on top. An NDPA           statement is trying to say, but resolution
is transmitted within a PPDU,        reword it so that it says
so the choice between the two        something meaningful.
is gratuitous. Furthermore,
any MPDU is transmitted
within a PPDU, so the whole
statement is utterly
meaningless.

with the NDPA?? Or NDP??                                                Daewon. 11/304r0.    Ed
needs to refer to the related                                                                Ed
table number in capabilities

Extended HT Capability               should be "HT Extended             Daewon. 11/304r0.    Ed
                                     Capabilities"
The statement, "MFB                  clarify                            Daewon. 11/304r0.    MU
responder device Identified by
the MCS Feedback field….", it is
not clear to me how the MCS
field is used to identify a device


We are talking about the             change from "An MFB          Daewon. 11/304r0.          MU
capability of a STA here             responder device" to "An MFB
                                     capable STA"
"in a PPDU." - all OTA               Remove cited text or replace Daewon. 11/304r0.          MU
signalling is ultimately in a        with "PPDU that is not an
PPDU, so this says nothing.          NDP".
"responder initiates                 "responder computes the"                                Ed
computation of the" - it is not
the initiation that is germain,
but the computation

There is a little ambiguity on       needs to describe in more          Daewon. 11/304r0.    MU
how this can be correlated           detail

Clarification:                       Change the sentence to "a STA                           Ed
"the STA shall set the               shall set the Unsolicited MFB
Unsolicited MFB field in VHT         subfield in VHT Control field to
Control to 0."                       0."
MFB is a subfield, and VHTC is
a field.
"VHT Control" - this is              Add "field" after VHT Control,                          Ed
syntactically an adjective, so it    whereever absent.
needs to precede a noun
MFS                               should be MFSI                                        Ed

"MFS" should be "MFSI".           Change "MFS" into "MFSI".                             Ed

Wrong word "MFS".                 Change to "MFSI"                                      Ed
Typo "MFS".                       Change it to "MFSI"                                   Ed
misspelling                       Change MFS to MFSI                                    Ed
"an VHT" has a grammatical        Change "an VHT" into "a VHT".                         Ed
error, which is inconsistent
with "a VHT" in line 34 of page
2.
Grammer:                          Replace "an" with "a" or "the".                       Ed
"an VHT Control field"
Typo in "an VHT Control field"    Replace "an" with "a" or "the".                       Ed

Is SNR supposed to average in     Clarify the averaging.            Daewon. 11/304r0.   MU
dB scale?
In computation of MFB and to      For NDPA triggered MFB, STA Daewon. 11/304r0.         MU
allow interoperable Link          should compute MFB for the
Adaptation mechanics, the         same BW as the Compressed
MFB responder needs at least      Beamforming feedback BW
following information; { BW,      (not to be confused with the
Nsts, Coding, transmission type   the actual transmission BW of
(i.e. su-mimo, mu-mimo, etc) }.   the CB feedback PPDU). Similar
The section describes that the    change needed for PPDU
MFB responder is soley            triggered MFB.
repsonsible for choosing the
Nsts value, but leave out
fundamental MFB properties
such as BW and coding.
Specification unclear.
Incoporate BW and Coding
(BCC/LDPC) aspect into the
MFB computation and
feedback


"subfield in MFB" - grammar       "subfield of the MFB field"                           Ed

MCS is also limited in addition change to "the VHT Nsts and         Daewon. 11/304r0.   MU
to Nsts                         MCS subfield"
Specification is unclear as toadd description to say that STA Daewon. 11/304r0.          MU
what BW and Coding should     should compute MFB for the
the MFB responder should      same BW as the Compressed
assume when computing the     Beamforming feedback BW
recommended MFB for the       and coding information should
triggered MRQ in NDPA         be also fedback along with
                              MFB.
"Support MCS Field" - not how "Supported MCS field"                                      Ed
it's defined
"Support MCS" --> "Supported Correct it                                                  Ed
MCS"
Clarification:                Change to "MFB subfield"                                   Ed
"MFB field"
"in MFB field" - grammar      "in the MFB field"                                         Ed
MFB is not a field            Change it to "MFB subfield"                                Ed

the SNR equation text size         make the SNR equation text                            Ed
seems to be too big.               size smaller.
SNR equation is too large          change format                                         Ed
(physically)
The size of SNR equation is too    Make the size equal to other                          Ed
big                                text.
What is the definition of          Add the exact definition on       Daewon. 11/304r0.   MU
N_Data^{Tone}?                     N_Data^{Tone}.
"When a STA is sending             A VHT STA that sends                                  Ed
unsolicited MFB feedback, the      unsolicited feedback using the
STA shall set the                  VHT Control field shall set its
Solicited/Unsolicited bit in the   Solicited/Unsolicited field to 1.
VHT
Control field to 1." - awkward,
doesn't fit ideal model, and
too broad
In unsolicited MFB, Nss should     In unsolicited MFB, Nss should Daewon. 11/304r0.      MU
be constrained to the Nss          be no larger than Nss value in
value in the PPDU from which       PPDU from which MFB was
MFB is extracted. Bfee cannot      computed
estimate a larger Nss from just
Nss LTFs
Add BW recommendation to Add 3-bit BW recommendation Daewon. 11/304r0.               MU
unsolicited MFB. MCS, Nss and to MFB
SNR should refer to a particular
BW. BW should not be greater
than the BW used in the PPDU
on which recommendation was
based. Most recent PPDU
should match GID, CodingType,
BF_TX, and BW.


"reported in MFB of a" -         "reported in the MFB subfiled                       Ed
grammar                          of a"
The concept of identifying       ???                             Daewon. 11/304r0.   MU
PPDU by "most recent PPDU
received by the STA which
matches the description…" is
not well defined and might
lead to ambiguities. For several
reasons: 1) Not clear when
PPDU is actually received by
user, since: ( a. MFB might
come before BA, b.PPDU for all
users but first have no-ACK
policy, c. another PPDU might
be sent before MFB has a
TXOP, BFee needs to dump
MFB for consistency) 2) GID
might change between time of
PPDU and MFB. 3) BFer needs
to store history of PPDU
parameters per user. Not clear
how much history to save, also
complex. 4) GID not enough to
characterize PPDU, Nss
allocation vector is also needed




It is hard for the MFB       Change "most recent PPDU            Daewon. 11/304r0.   MU
responder to compute         received" to "a recent PPDU
unsolicited MFB based on     received"
"most recent PPDU received".
Missing commas and               Change the sentence to "MCS,                         Ed
inconsistency in "MCS SNR and    VHT NSTS, and SNR" with "STS"
NSTS".                           being subscipts.
Missing commas in "MCS SNR       Insert commas as "MCS, VHT                           Ed
and NSTS".                       NSTS, and SNR" and change
                                 "STS" being subscipts.

NSTS should be Nsts (subscript) change accordingly                                    Ed

"Note--The value of              Change text to "Note--The  Daewon. 11/304r0.         Ed
Unsolicited_Type field allows    value of GID_L and GID_H
to identify whether the          fields allows to identify
unsolicited feedback is          whether the unsolicited
estimated                        feedback is estimated
from a SU or MU-MIMO PPDU"       from a SU or MU-MIMO PPDU"
Unsolicited_Type is not
defined, it is GID_L and GID_H

The "Note--The value of          Change to: The values of GID-L Daewon. 11/304r0.     MU
Unsolicited_Type field allows    and GID-H can be used to
to identify whether the          identify whether the
unsolicited feedback is          unsolicited feedback is
estimated                        estimated
from a SU or MU-MIMO PPDU"
is incorrect
Should it be "FB TX Type"        Please clarify.                  Daewon. 11/304r0.   MU
instead of "Unsolicited_Type"?
If it meant "FB TX Type", the
description doesn't exactly
match how it is defined in
Table 7-6h.

This refers to a MFB to be sent change from "If the MFB is in" Daewon. 11/304r0.      MU
                                to "If the MFB is to be sent in"

Wrong notation "NSTS".           Change the "STS" to subscipts.                       Ed

Unnecessary upper case letter Change the phrase to "VHT                               Ed
"VHT Control Field"           Control field"
Currently Nss in an SU type       Allow Nss≤Nc in SU MFB. In   Daewon. 11/304r0.   MU
MFB is constrained to be equal    case Nss<Nc, MFB parameters
to Nc. This is an unnecessary     assume BFer uses a matrix of
restriction, and prevents the     reduced dimension, with
possibility for sending Nc for    dimension equal to Nss.
the maximum channel
dimension (to enable BFer
getting maximum information)
and still recommending a
lower Nss value. It also
prevents the BFer to even try a
larger value of Nss for testing
purposes, or for other internal
purposes besides data transfer
(like adapting rate adaptation
thresholds). The potential
practice of sending maximum
Nc value regardless of
recommended Nss has
negligible overhead, as
sounding frequency in SU is
supposedly low.




NSTS should be Nsts (subscript) change accordingly                                 Ed

NSTS should be Nsts               change the font                                  Ed

Clarification:                    Change the phrase to "VHT                        Ed
"Compressed Beamforming           Compressed Beamforming
frame"                            frame".
"an VHT" has a grammar error,     Change "an VHT" into "a VHT".                    Ed
which is inconsistent with "a
VHT" in line 34 of page 2.

Grammer:                          Replace "an" with "a" or "the".                  Ed
"an VHT Control field"
MFB is not done in case there      change to make STA feedback Daewon. 11/304r0.        MU
is mixture of SU-BF feedback       MFB only if SU-BF feedback if
and MU-BF feedback. This           configured for that particular
unnecessarily creates artificial   STA if MRQ is enabled in NDPA.
restriction where if the AP        For STAs configured with MU-
wants MFB as well as CB            BF feedback should disregard
feedback then it must only         the MRQ when MRQ is enabled
assign SU-BF feedback in the       in NDPA.
NDPA. Remove such                  Suggested text :
restriction.                       "The MFB responder shall
                                   include the corresponding MFB
                                   feedback in the VHT
                                   Compressed Beamforming
                                   frame that is the response of
                                   the same NDP-A and NDP
                                   sequence, if the MFB requester
                                   sends MRQ in an VHT NDP
                                   announcement frame where
                                   the Feedback Type subfield in
                                   the STA Info field for the MFB
                                   spresonder is set to 1 (meaning
                                   requesting SU-BF Feedbacks).

                                   The MFB responder shall
                                   indicate MFB=127 in the VHT
                                   Compressed Beamforming
                                   frame that that is the response
Section regarding how MFB          of the a section similar to NDPA Daewon. 11/304r0.
                                   Write same NDP-A and NDP                             MU
computation should be based        triggered MFB computation for
on is missing for NDPA             PPDU triggered MFB
triggered MFB, whereas how         computation.
MFB computation should be
based on is written for NDPA
triggered MFB.
The current text as it stands is
quite ambiguous on PPDU
triggered MFB. Clarify what
MFB computation is based on
(e.g. BW, Coding, Nsts, etc)
when MFB is for associated
PPDU in which MRQ is
triggered.
Grammer is wrong: 'If the MFB     Change 'If the MFB requester                         Ed
requester sends MRQ in an         sends MRQ in an VHT NDP ~' to
VHT NDP ~' should be 'If the      'If the MFB requester sends
MFB requester sends MRQ in a      MRQ in a VHT NDP ~'
VHT NDP ~'
restriction to only feedback      change the section to allow     Daewon. 11/304r0.    MU
MFB in case there is only SU-BF   support of mixture of MU-BF
feedback is not needed. The       and SU-BF.
MFB now as it stand does not
support mixture of MU-BF and
SU-BF.

specification is unclear as to    clarify what associated PPDU    Daewon. 11/304r0.    MU
what BW, coding, Nsts values      means in more detail.
the MFB responder should
assume when computing
recommended MFB for PPDU
triggered MFB.

In "MFB feedback", MFB            Delete the word "feedback"                           Ed
already includes the meaning
of feedback. Thus, the word
"feedback" after MFB is not
required.
"NDP-A" should be revised to      As in comment.                                       Ed
"NDPA".




Wrong notation "NDP-A".           Change the word to "NDPA".                           Ed

"4—A STA that sets the MCS        Need to define a VHT Link        Daewon. 11/304r0.   MU
Feedback field to 0 in the HT     adaptation capability indication
Extended Capabilities field of    in VHT capability element;
the HT Capability elements        Also, add a sentence "A STA
that it transmits does not        that sets the VHT MCS
respond to an MRQ." Text          Feedback field to 0 in the VHT
implies that a STA cannot         Capability elements that it
support VHT Link adaptation,      transmits does not respond to
unless it supports HT link        an VHT MRQ."
adaptation
Lack of information on editor's Change the editor's note as                                         Ed
note (on the italic text).      follows:
                                "Insert section 9.21.5 and
                                9.21.6 as shown below:"

Editing instruction should also per comment                                                         Ed
insert 9.21.6
the statement, "…are            Clarify                         Daewon. 11/304r0.                   MU
computed based on the most
recent PPDU received by the
STA which matches the
description indicated by GID-L,
GID-H, Coding Type,….", does
this mean that a STA has to
store this information for all
previously received PPDUs to
do the right match. It sounds
like a heavy burden on STA
implementation.

misspelling                      Change NSTS to NSTS                                                Ed
Sub-clause 22.3.13 states that   In Figure 9.37b, replace the   DISAGREE. Disagree                  MU
NDP is the only VHT sounding     sounding poll frames with      Sounding poll is used for solicit
format. The use of sounding      NDPs                           sounding FBs, not for sounding
poll as shown in Figure 9.37b                                   purpose. Don’t see why it
violates this rule                                              violates the rule. 11/349r2.
"A STA that has the value true   Add: A STA that has the value AGREE IN PRINCIPLE. See #170. MU
for                              true for                           11/349r2.
dot11VHTBeamformerEnabled        dot11VHTMUBeamformerEnab
shall set the SU Beamformer      led shall set the MU Tx Capable
Capability                       field to 1 in transmitted VHT
field to 1 in transmitted VHT    Capabilities elements. A STA
Capabilities elements. A STA     that has the value true for
that has the value true for      dot11VHTMUBeamformeeEna
dot11VHTBeamformeeEnabled        bled shall set the MU Rx
shall set the SU Beamformee      Capable field to 1 in
Capability field to 1 in         transmitted VHT Capabilities
transmitted VHT Capabilities     elements.
elements. A STA that does not    A STA that does not have the
have the value true for          value true for
dot11VHTBeamformerEnabled        dot11VHTBeamformerEnabled
shall not act in                 or
the role of a beamformer. A      dot11VHTMUBeamformerEnab
STA that does not have the       led shall not act in the role of a
value true for                   beamformer. A STA that does
dot11VHTBeamformeeEnabled        not have the value true for
shall                            dot11VHTBeamformeeEnabled
not act in the role of a         or
beamformee."                     dot11VHTBeamformeeEnabled
dot11VHTBeamformeeEnabled        shall not act in the role of a
is not defined anywhere          beamformee.



The section should be            change AP with beamformer AGREE. Resolution text in       MU
consistently using the concept and STA to beamformee when 11/349r2.
of beamformer and                appropriate;
beamformee instead of AP
and STA; the way it is currently
written would even forbid a
STA to STA SU TxBF;
In current specification, a       Add an optional STA behavior AGREE IN PRINCIPLE. See   MU
Sounding Poll frame may           to support the selective      #1446. Resolution text
include some additional fields    retransmission of segments in provided in 11/378r4.
to improve sounding               VHT Compressed Beamforming
procedures. The following is      frame.
one suggestion for the usage of
new fields.
VHT Compressed Beamforming
Report field can grow up to
approximately 26Kbytes, which
is larger than the maximum
allowed MPDU limit for
management frames. This
makes a VHT Compressed
Beamforming frame in the
form of A-MPDU. Since each
MPDUs in the A-MPDU can be
checked with individual FCS
whether the transmission is
success or not, selective
retransmission of only failed
segments in the A-MPDU can
considerably increase the
transmission efficiency in
sounding procedures. To
support the selective
retransmission of segments in
VHT Compressed Beamforming
In VHT sounding protocol, the     Clarify VHT sounding protocol.   AGREE IN PRINCIPLE. BW of      MU
specification is unclear on the   Some rules for specifiy BWs of   NDP is specified to be same as
relations of BWs of the frames;   NDPA, NDP, VHT Compressed        NDPA. BW of the Compressed
NDPA, NDP, VHT Compressed         Beamforming, and Sounding        beamforming not addressed in
Beamforming, and Sounding         Poll frames are required.        this resolution. 11/349r2.
Poll frames.

(a) What is the expected
behavior of a STA when it does
not have a valid channel
information (e.g., due to
interference) on some part of
the BW for which channel
information is requested by
the beamforer? May the STA
supposed to compute VHT
Compressed Beamforming
Report only using valid BW?
(b) In the above case that a STA
transmit may report VHT
Compressed Beamforming
Report on reduced BW than
requested, what is the transmit
BW of VHT Compressed
Beamforming frame PPDU?
(c) When the beamformer
receives VHT Compressed
Beamforming VHT sounding
Cluase 9.21.5 Report for only Define clear behavior.               Simone. 11/349r2. (Editor:    MU
protocol needs some more                                           Approved resolution in 11/349
clarification on the                                               calls this out as a "Deferred
transmission of NDPA, NDP,                                         resolution")
and VHT compressed
beamforming; that is, non-HT
duplicate form, Reporting
management under
interference in secondary
channels, etc.
There can be an additonal field   Describe an STA behavior to   AGREE IN PRINCIPLE. See      MU
for Sounding Poll. Since VHT      support the selective         #1446. Resolution text
Compressed Beamforming            retransmission of segments in provided in 11/378r4.
Report may be segmented in        VHT Compressed Beamforming
some cases, selective             frame. This can be optional.
retransmission of segmented
Compressed Beamforming
Report should make feedback
process efficient. To support
this retransmission procedure,
a new field which indicates the
segment information needs to
be adopted in Sounding Poll
frame. The selective
retransmission of segments is
an optional feature.




During the sounding            Clarify BWs of NDPA, NDP, VHT     Simone. 11/349r2. (Editor:    MU
procedures, BW indications for Compressed Beamforming, and       Approved resolution in 11/349
measurement and                Sounding Poll frames.             calls this out as a "Deferred
transmission are clear. For                                      resolution")
example, what is the PPDU BW
of the VHT Compressed
Beamforming Report when
there are NDPA decoding failur
in some secondary channels?
What is the BW of Sounding
Poll when beamformer have
received VHT Compressed
Beamforming Report of only
partial channel? etc.

If the NDPA frame and VHT         Define a mechanism where       Simone. 11/349r2. See       MU
Compress Beamforming              sounding and protection can    11/346?
frames are sent in non VHT        be provided at the same time
legacy format, the sounding       to improve efficiency.
sequence defined in this
subclause can provide
protection against hidden
nodes.
It is not clear what the idea of In order to make it more                                      Ed
this sentence is.                clearer, I propose to change
                                 the text
                                 "… used at the transmitter to
                                 optimize reception …" to
                                 "… used at the transmitter and
                                 to optimize reception …".

There is no field called "SU   Propose to change the text to                                   Ed
Beamformer Capability". (see "SU Beamformer Capable".
page 29)
You define how to decide SU add the text accordingly.             AGREE. Resolution text in    MU
Beamformer/Beamformee                                             11/349r2.
Capability field in a STA. But
the Mu TX/RX (MU
beamformer/beamformee ) is
missing.

The field is called "SU        Fix                                                             Ed
Beamformer Capable"
The description needs to be    Extend description                 AGREE. See #170. 11/349r2.   MU
extended for MU Rx Capable
and MU Tx Capable. Also, there
is a dependency: an MU Rx
Capable device is also SU
Beamformee Capable.

"dot11VHTBeamformerEnable Rename all "Enabled" variables                                       Ed
d" - please note naming      to "Activated"
convention in WG802.11 style
uses "Activated" not Enabled

There is no field called "SU    Propose to change the text to                                  Ed
Beamformee Capability". (see    "SU Beamformee Capable".
page 29)
The field is called "SU         Fix                                                            Ed
Beamformee Capable"
"a NDPA" - grammar              "an NDPA" - check globally                                     Ed
"a NDPA" should be revised to   As in comment.                                                 Ed
"an NDPA".
"A beamformee that receives           Suggest to change to: "A        AGREE IN PRINCIPLE.          MU
an NDPA from an AP to which           beamformee that receives an Resolution text in 11/349r2.
it is associated and that             NDPA from a beamformer to
contains the AID assigned it          which it is associated or has a
during association in the STA ID      DLS or TDLS session setup and
subfield of the first STA Info        that contains the beamformee
field shall [...]" this sentence is   AID [...] "
specific for AP to STA TXBF and
would not allow STA to STA
TxBF

grammer: 'assigned it' should         Add 'to' between 'assigned'                                  Ed
be 'assigned to it'                   and 'it'
bandwidth of poll frames is not       clarify                          Simone. 11/349r2. (Editor:    MU
clear, and bandwidth of                                                Approved resolution in 11/349
responses to the poll frame is                                         calls this out as a "Deferred
also not clear                                                         resolution")
Grammer is wrong: '~ that             Change '~ that contains the AID                                Ed
contains the AID assigned it          assigned it during ~' to '~ that
during ~' should be '~ that           contains the AID assigned to it
contains the AID assigned to it       during ~'
during ~'
Grammer is wrong: '~ that             Change '~ that contains the AID                              Ed
contains the AID assigned it          assigned it during ~' to '~ that
during ~' should be '~ that           contains the AID assigned to it
contains the AID assigned to it       during ~'
during ~'
There are cases when the            Propose to modify the            AGREE. (Simone)                MU
sounding feedback does not fit      paragraph as follows: "If the    As in comment. Need to clarify
in a PPDU, due to exceeded          beamformee does not have a       “If the beamformee does not
duration; this can happen in        valid VHT Compressed             have a valid VHT Compressed
case the Sounding Poll frame is     Beamforming Report, of if the    Beamforming Report”
sent with a BW smaller than         transmission duration of the      11/349r2.
the BW of the channel               VHT Compressed Beamforming
feedback included in the            Report frame would exceed
response frame; For this case it    the maximum PPDU duration,
is useful that the beamformee       the beamformee
responds with a short frame         shall transmit a VHT
not containing the feedback;        Compressed Beamforming
this is useful in enabling a more   frame without including the
robust operation in case other      VHT Compressed Beamforming
frames need be sent                 Report field or MU Exclusive
subsequently (e.g. a poll foe       Beamforming Report and
another STA); it also provides      indicating this in the VHT
the beamformee with the             MIMO Control field
indication that STA is still        as described in 7.3.1.31 (VHT
within range and is active;         MIMO Control field).G74




Change "AP" to beamformer                                            Simone, Yong, Illsoo have    MU
for consistency in description                                       resolutions

In line 42, it says "from an AP     should be consistent                                          Ed
to which it is associated";
In line 42, it says "from an AP
with which it is associated".


change "that contains the AID       as comment                                                    Ed
assigned it during association"
to "that contains the AID
assigned to it during
association" also the one in
line 45-46
Why using AP instead of             clarify that a non-AP            AGREE IN PRINCIPLE. Used       MU
beamformer here? Can a non-         beamformer can only send a       beamformer instead of AP.
AP beamformer send a NDPA           NDPA with a single STA info      Non-AP can also send NDPA
with multiple STA info fields?      field and using a unicast NDPA   with multiple STA Info field,
                                                                     there is no reason to impose a
                                                                     limit (Simone). 11/349r2.
"assigned it" --> "assigned to    change in both places                                     Ed
it"
"the Nc field in the VHT MIMO     When the Feedback Type is set AGREE. Resolution text in   MU
Control field may be set to any   to SU, Nc is determined by the 11/349r2.
value": this sentence is          beamformee
confusing
Current spec allows for           Limit sounding feedback to    DISAGREE. BFmer can control MU
feedback of delayed CV            maximum aging                 the timing of BF FB from
(matching an old sequence                                       BFmee; if aging limit exceeds,
number). This can impact MU                                     BFmer may choose to resound,
performance. Will also                                          instead of polling for FB
complicate scheduler. MU                                        (Yong). 11/349r2.
users can return CVs that
relate to different NDPs.
Solution: limit sounding
feedback to maximum aging.
Aging can be given in ms. If
after Poll the available CV
exceeds aging limit, BFee
returns a Null CV matrix. Aging
parameter can be carried in
either NDPA, Poll, GID
management, or any other
frame. Aging can be specific to
a STA or to a GID

Restrict BFee to always return                                  DISAGREE. It is not necessary MU
sounding feedback of the latest                                 to have this restriction. BFmer
NDP it received correctly.                                      knows the seq number and
Otherwise we leave a backdoor                                   timing of a FB frame, and can
for delayed response                                            decide whether to use the FB
implementation, that would                                      information for beamforming
impair MU performance. Bfee                                      11/349r2.
can declare itself to be MU
Receiver capable, but always
return old CV matrix




"Upon failure to receive         remove sentence                                            Ed
the feedback, the beamformer
may initiate poll-based
recovery as described in 9.x.x."
concept is already included in
sentence in line 65
in 9.x.x                          list the right clause                                           Ed

The section number of 9.x.x     As in comment.                                                    Ed
should be revised to 9.9.2.1.3.

what is 9.x.x here?             clarify                                                           Ed
9.x.x' needs a reference index. Add the clause.                     Simone, Yong, Illsoo have     MU
                                                                    resolutions
9.x.x                             fix reference                                                   Ed
9.x.x'. A reference index is      Add the clause.                   AGREE. Reference provided.    MU
missing.                                                            11/349r2.
The reference of "poll-based      Upon failure to receive the       AGREE. See #1419. 11/349r2.   MU
recovery "should be stated        feedback, the beamformer
clearly.                          may initiate poll-based
                                  recovery as described in 9.x.x
                                  9.9.1.4 (Multiple frame
                                  transmission in an EDCA TXOP)


What poll-based recovery?         Give reference to where poll-     AGREE. See #1419. 11/349r2.   MU
What is 9.x.x intended to point   based recovery is described.
at?
There is no "poll-based           add corresponding text for        AGREE. See #1419. 11/349r2.   MU
recovery" procedure defined in    "poll-based recovery"
this draft.
reference section number is       Change the section number or                                    Ed
incorrect                         add description on poll-based
                                  recovery
VHT Capability -> VHT                                                                             Ed
Capabilities
The Multi STA info field          This sentence can be changed                                    Ed
contains the IDs of the           to "The Multi STA info field is
beamformees required to           defined in section 7.2.1.11"
compute the sounding
feedback
and may include other
information TBD.
Meaning of this sentence is       Remove (it appears to be an                                     Ed
unclear                           early description for including
                                  multiple STA Info fields)

What is "Multi STA Info field"? clarify                                                           Ed
Change ID to AID
TBD' needs to be erased if no Either fill the TBD of erase TBD. Simone, Yong, Illsoo have         MU
other information is defined.                                   resolutions
TBD' is remained.                Complete 'TBD'                    AGREE IN PRINCIPLE. Sentence MU
                                                                   removed as per 11/349r2. See
                                                                   11/346?
what is "other information       clarify                                                        Ed
TBD"?
"may include other               resolve the TBD                   AGREE. Sentence removed.   MU
information TBD."                                                  11/349r2.
And at 59.09
Is this still a TBD?             need discussion                   AGREE IN PRINCIPLE. Sentence MU
                                                                   removed. 11/349r2.

The RA in the NDPA frame shall This sentence can be removed;                                  Ed
be set to the address of the   already included in line 23
beamformee when sounding
feedback is requested
from a single beamformee.

"The RA in the NDPA frame        change to: "When a single STA AGREE. Resolution text in      MU
shall be set to the address of   Info field is included, the RA in 11/349r2.
the beamformee when              the NDPA frame shall be set to
sounding feedback is             the MAC address of the
requested from a single          beamformee identified in the
beamformee": 'sounding           STA Info field" also paragraph
feedback is requested from a     starting at line 23 can be
single beamformee' may nt be     removed and replaced with
clear; add reference to the      "An SU only beamformee is a
indication in the frame          STA that, in its VHT Capability
                                 element, has set the SU
                                 Beamformee Capable field to 1
                                 and the MU Rx Capable field to
                                 0. When soliciting feedback
                                 from an SU only beamformee a
                                 single STA info field shall be
                                 included in the NDPA and the
                                 Feedback Type shall be set to
                                 SU"




The RA in the NDPA~' should      Change 'The RA in the NDPA~'                                 Ed
be changed as 'The RA field in   to 'The RA field in the NDPA ~'
the NDPA ~'
field' is missing after 'RA'     Add 'field' after 'RA'                                       Ed
"The RA field in the NDPA          change to: "The RA field in the AGREE. Resolution text in   MU
frame shall be set to the          NDPA frame shall be set to the 11/349r2.
broadcast address when             broadcast address when more
sounding feedback is               than one STA Info field is
requested from more than one       included in the NDPA"
beamformee" 'sounding
feedback is requested from
more than one beamformee'
may nt be clear; add reference
to the indication in the frame

This paragraph is redundant to delete it                                                       Ed
ln 55-59 in pg 57

The texts in Line58~65 present     Remove the following            AGREE. Removed. 11/349r2.   MU
the same meaning as described      sentence from Line 58~65 in
in Line 55~59 in P57, and          P58:
Line20 in P58.                     A beamformer that has
                                   transmitted an NDPA with
                                   more than one STA Info field
                                   should transmit any Sounding
                                   Poll frames needed to retrieve
                                   the expected VHT Compressed
                                   Beamforming frames within
                                   the TXOP that contained the
                                   NDPA while giving priority in
                                   attempting to satisfy this
                                   recommendation to the rules
                                   of 9.9.1.4
                                   (Multiple frame transmission in
                                   an EDCA TXOP).
                                   Recovery follows the rules for
                                   multiple frame transmission in
                                   an EDCA TXOP (9.9.1.4).




paragraph is repeated, see Pg      remove it                                                   Ed
57 line 55
This paragraph is duplicate to     Delete one of them                                          Ed
the paragraph in page 57
starting from line 55
9.9.1.4 does not really define a   need discussion (TBD: check    AGREE IN PRINCIPLE. Sentence MU
recovery procedure for MU          baseline document)             removed. 11/349r2.
case.
This paragraph is repetition of merge two paragraph                                          Ed
the paragraph in the page 57
(line 55 ~ 59)
repetition (see. Page: 57 lines: Delete the paragraph.                                       Ed
55-59)                           With this deletion, may be, we
                                 need to re-arrange the order of
                                 the other texts too.

It is not clear what this means,   Remove sentence                 COUNTER. Reworded (Simone) MU
i.e. what it means to describe                                     IN section 9.9.1.4. 11/349r2.
something as a valid frame
exchange for the purposes of
recovery
VHT-CB is used here without        Add to abbreviations or expand                              Ed
definition                         on use
Acronym for VHT-CB is not          define acronym                 COUNTER. Sentence removed. MU
defined                                                           11/349r2.
The sentence, "It also defines     define corresponding           AGREE IN PRINCIPLE. Recovery MU
the recovery procedure in case     procedure (TBD: check          text removed. 11/349r2.
of a missing response to NDPA      baseline document)
or Sounding Poll", is not true.
The procedure is not defined.


change TBD to up to 8              as comment                                                Ed
"If it would otherwise result in   Add indication of what to do     AGREE IN PRINCIPLE.           MU
an MMPDU that exceeds the          with MU Exclusive report field: Resolution text in 11/349r2.
maximum MPDU size, the VHT         "If it would otherwise result in
Compressed Beamforming             an MMPDU that exceeds the
Report field may be split into     maximum MPDU size, the VHT
up to TBD segments. Each           Compressed
segment shall contain an equal     Beamforming Report field and
number of octets except for        MU Exclusive report field may
the last segment, which may        be split into up to 8 segments.
be smaller. All segments shall     Each segment shall contain an
be sent within the same            equal number
A-MPDU." According to the          of octets except for the last
text, MU Exclusive filed is not    segment, which may be
split across multiple segments;    smaller. All segments shall be
this would result in duplicated    sent within the same
MU Exclusive field, increasing     A-MPDU. If segmented,
overhead.                          Beamforming Report field and
                                   MU Exclusive report field shall
                                   be split in the same number of
                                   segments."
It is useful to introduce a    Proposed approach: In section AGREE IN PRINCIPLE. See     MU
mechanism for selective        7.2.1.12 Sounding Poll,          #1446. Resolution text
retransmissions of erroneous   introduce a 1byte field in the provided in 11/378r4.
segments                       Sounding Poll message
                               containing a bitmap indicating
                               the segments to be
                               retransmitted; Each bit in the
                               Retransmission Bitmap is set to
                               1 to indicate that the
                               corresponding segment is
                               requested to be transmitted by
                               the recipient of the Poll frame.
                               Bit in position k (k=0 for LSB
                               and K=7 for MSB ) corresponds
                               to the segment with the
                               Remaining segment field set to
                               k.
                               All bits in the Retransmission
                               Bitmap shall be set to 1 unless
                               a selective retransmission is
                               requested, in which case the
                               bits corresponding to the
                               segments already correctly
                               received shall be set to 0;
                               IN the section pointed by this
                               comment add: A beamformer
                               shall Poll a beamformee
                               requesting the transmission of
"If it would otherwise result in   Add in VHT MIMO control field        AGREE. As in comment. Part of MU
an MMPDU that exceeds the          (7.3.1.31 VHT MIMO Control           this comment is addressed in
[...]". Segmentation of            field) a 3-bits (bits 12-14)         the Poll and MIMO Control
sounding feedback need more        "remaining segments"                 fields section (Simone).
detailed specification;            indication and a 1-bit (B15)         11/349r2.
Segments need be identified        "first segment" indication; ;
by an ID and receiver need be      ‘Remaining Segments is Set
able to determine if all           equal to the number of
segments are received;             remaining segments of the
                                   Compressed Beamforming
                                   Report field to be sent,
                                   excluding the current one. The
                                   field shall be set to the total
                                   number of segments minus 1 if
                                   the First Segment field set to 1.
                                   In case of a retransmitted
                                   segment, the field is set to the
                                   same value associated with the
                                   segment in the original
                                   transmission.
                                   In case of a Compressed
                                   Beamforming frame not
                                   carrying a Compressed
                                   Beamforming report field, the
                                   field is set to all ones;
                                   'First Segment' is Set to 1 if the
                                   segment of the Compressed
change TBD to multiple.            Beamforming Report field
                                   "Beamforming Report field                                        Ed
                                   may be split into up to TBD
                                   Multiple segments."
The maximum required               Add '7 segments' instead of          COUNTER. See #1422.         MU
number of segments for VHT         'TBD segments'                       11/349r2.
Compressed Beamforming
Report field is 7. This number
comes from the worst case
scenario when the maximum
size of VHT Compressed Rport
field is approximately 26kBytes
and the maximum A-MSDU
size of STA's VHT Capability is
only 3.8kBytes.
The maximum number of          Correct 'TBD' to '7'              COUNTER. Indicates 8          MU
segments of VHT Compressed                                       segments. 11/349r2.
Beamforming Report field is 7.

For the worst case scenario, Clarify 'TBD segments' with '7      COUNTER. See #1422.             MU
the maximum size of VHT      segments'.                          11/349r2. (Editor: Note that
Compressed Rport field grows                                     motion approving this
up to 26kBytes and the                                           resolution incorrectly referred
maximum A-MSDU size of                                           to #1544)
STA's VHT Capability is
3.8kBytes. Thus, the maximum
number of segmentations will
be 7.

Has this TBD been resolved?    determine the number of           AGREE. See #1422. 11/349r2.   MU
                               segments
"A beamformer shall only poll Add conditions as to why it        Illsoo. 11/378r4.             MU
an SU only beamformee if it    might want to poll the
received at least one segment beamformee.
of the feedback from
the beamformee." - I think     Also note "shall only <verb> if
there's something missing here <condition>" is always wrong.
                               Reword "shall <verb> only if
                               <condition>"

transmits -> transmit           As in comment. Delete "s".       AGREE. As suggested.          Ed


"shall transmits a" - grammar   transmits -> transmit            Duplicate. See #68.           Ed

When a STA transmits a VHT      On line 13,add"STBC shall be     Yong has a proposed resolution MU
format NDP,TXVECTOR             set to 0"
parameters STBC shall be set
to 0

"A STA shall transmits".        "A STA shall transmit".          Duplicate. See #68.           Ed
In 'The number of space time    Change 'The number of space      AGREE. As suggested.          Ed
streams sounded ~,' '-' is      time streams sounded ~' to
missed between 'space' and      'The number of space-time
'time.'                         streams sounded ~'

-' is missing between 'space'   Add '-' between 'space' and      Duplicate. See #1082.         Ed
and 'time.'                     'time'
missing '-' between 'space' and Change to 'space-time'.          Duplicate. See #1082.         Ed
'time.'
missing word in "the STA that Put a word "frame" as "the STA AGREE. As suggested.             Ed
is the intended recipient of the that is the intended recipient
VHT NDP".                        of the VHT NDP frame".

"the STA that is the intended Describe the MU case               Yong has a proposed resolution MU
recipient of the VHT NDP." -
this does not allow for the MU
case
To clarify the meaning in "the Change "VHT NDP" to "VHT          Duplciate. See #1084.        Ed
STA that is the intended       NDP frame"
recipient of the VHT NDP".

confusing and not readable      Rephrase for clarity and         AGREE. Rephrased as follows: Ed
especially when it comes to the readability.                     "A STA shall not transmit an
word "including"                                                 NDPA frame that is addressed
                                                                 to a STA or that includes a
                                                                 STA’s AID in one of the STA
                                                                 Info fields unless it has
                                                                 received from that STA a VHT
                                                                 Capabilities element and
                                                                 where the last VHT Capabilities
                                                                 element received from that
                                                                 STA:
                                                                 - has the SU Beamformee
                                                                 Capable field set to 1, or
                                                                 - has the MU Rx Capable field is
                                                                 set to 1, or
                                                                 - has both the SU Beamformee
                                                                 Capable and the MU Rx
                                                                 Capable fields set to 1."


"including" should be           revise for clarity               Duplciate. See #234.         Ed
"include"? This sentence is too
long and a bit confusing.

One sentence is too long and     Change as;                       Duplciate. See #234.        Ed
gramars are wrong. The           A STA shall not transmit an
sentence cannot be               NDPA unless the STA has
understood.                      received from its recipients the
                                 SU Beamformee Capable
                                 field=1, the MU Rx Capable
                                 field=1, or both fields=1 in VHT
                                 Capability element'
One sentence is too long to       Break the sentence to several Duplciate. See #234.          Ed
understand                        sentences with clear
                                  explanation.
Lines apply to NDPA               Move the lines to Clause 9.21.5                             Ed

Althought the editing             Change to say 10.4.7.1 and     AGREE. 6.4.7.3 and 6.4.7.4   Ed
instruction says change 10.4.7,   10.4.7.2, and do not show      (new numbering) removed.
10.4.7.3 and 10.4.7.4 are         10.4.7.3 or 10.4.7.4 in
shown unchanged.                  amendment if they remain
                                  unchanged.
Where are the PLME interfaces Add PLME interfaces.               Yongho has a proposed        MU
to configure group                                               resolution
membership?
Where are the PLME interfaces Add PLME interfaces.               Yongho has a proposed        MAC
to configure filtering by partial                                resolution
AID?
The structure of the clause is Please clarify the structure of                                Ed
unclear. The Power                the clause
management during VHT
transmissions having the same
content as the clause 11.2.1.4b
VHT TXOP Power
Management. Please organise
sections to describe AP
operations and non-AP STA
operations.
The VHT TXOP power save           Please allow TXOP power save   Allan.                       MAC
could operate also with SU-       mode use on all power save
MIMO transmissions and when modes.
STA is operating in normal PS
mode. Please allow TXOP
power save mode usa on these
power save modes as well

May a STA that is part of Group Please clarify.                  Allan.                       MAC
ID operate in power save
mode?
The management of the VHT As in comment.                         Allan.                       MAC
TXOP power save mode is not
clear. Please clarify what
happens when AP is not
allowing the use of TXOP
power save, also please clarify
how frequently the non-AP STA
may change its TXOP power
save mode.
The TXOP_PS_NOT_ALLOWED         Change the first paraph of this Allan.   MAC
bit does not apply to non-AP    sub-clause (lines 16 to 21) to:
STAs that are currently         "The power management
operating under the IEEE PS     scheme described in this
mode.                           section is applicable to non-AP
                                STAs that are not operating
                                under the PS mode and only
                                when VHT AP allows VHT TXOP
                                power save mode (see section
                                11.2.1.4b) at non-AP VHT STAs.
                                "


"when VHT AP" - grammar          insert an article                       Ed
The repeated use of the term Remove redundant use of non- Allan.         MAC
"non-AP VHT STA" throughout AP VHT STA throughout 11.2.1
is largely unnecessary, and will
doubtless cause negative
comment in any ballot. As
only a non-AP VHT STA can
perform TXOP power-saving, it
suffices to use STA or nothing
at all.

"transmissions shall indicate Reword in plain English                    Ed
non-AP VHT STAs using" - this
is almost impenetrable

amend "during a TXOP" at the change accordingly                          Ed
end of the sentence.
typo: "does not matches"     change to "does not match"                  Ed

"it finds that the frame is not clarify                                  Ed
destined to it." does it mean
the RA address in MAC header
is not matched?

"sends an appropriate           remove "appropriate"                     Ed
acknowledgement" - well we
wouldn't want inappropriate
behaviour would we?

"include NAV-set sequence" - add an article                              Ed
grammar
"in the Doze state" --> "in Doze as suggested                            Ed
state" (same as in line 52)
delete "for the remainder of    change accordingly                      Ed
the TXOP" from the sentence.
Note when a non-AP STA is not
a member of the group it can
enter Doze state for the entire
TXOP. So the use of remainder
here does not cover all cases.


VHT TXOP Power Mode            VHT TXOP Power Save Mode                 Ed

A typo. The clause title "VHT VHT TXOP power save mode                  Ed
TXOP power mode" should be
"VHT TXOP power save mode."

Missing "Save"                  Change to VHT TxOP Power                Ed
                                Save Mode
there is no reference to the    Need to add text specifying    Allan.   MAC
fact that mechanism is optional that mechanism support is
and a capability is present     indicated in capability
                                elements and add the correct
                                references
The mentioned "Table 10-1"      Change the "Table 10-1" to              Ed
should be "Table 11-1" instead "Table 11-1."
if referencing to the Draft
P802.11-REVmb/D4.01.

What is "VHT transmissions"? clarify                           Allan.   MAC
The VHT AP can only transmit
VHT PPDUs in the whole TXOP?
Why this constraint is needed?


Active mode is not described in Either add Active mode in      Allan.   MAC
Table 10-1.                     Table 10-1 or change the
                                reference to a proper one.
In table 10-1, active mode is   Either add Active mode in      Allan.   MAC
missing.                        Table 10-1 or change the
                                reference to a proper one.
Table number is incorrect       Change "see Table 10-1" to     Allan.   MAC
                                "see Table 11-1"
"Note that, the state of the    interaction with other power Allan.       MAC
non-AP VHT STA at the end of    save modes should be
the TXOP could be governed by   described more precisely. Also
other power save                the behavior of a STA in doze
mechanisms." sentence is not    mode at the end of the TXOP
clear;                          need be clarified (e.g can the
                                STA contend o teh medium?)


The interaction of TXOP power   Allow combinations of TXOP       Allan.   MAC
mode with other power           power mode and PS power
management modes is unclear.    management mode and
However, the logic for          describe here how they
disallowing a conventional      operate together.
power saver (i.e. in PS power
managment mode) from also
being a TXOP power saver
escapes me.

Typo.                          Change "in not in" into "is not            Ed
                               in".
Typo in "When the non-AP VHT When the non-AP VHT STA is                   Ed
STA "in" not in VHT TXOP       not in VHT TXOP power save
power save mode its operation mode its operation is the same
is the same as in Active power as in Active mode.
management mode."
Moreover, it is suggested that
the Active power management
mode can be shortened to
Active mode.

 "in" is not correct here       should modify "in" by "is"                Ed
It is not clear how the TXOP    Add explanation what happens Allan.       MAC
power save operates, if the     if the TXOP power save allows
duration of the NAV is          STA to be in Doze state and the
increased after the STA is in   duration of the NAV is
Doze state.                     extended.
"If the TXOP is truncated, then    Add note as follows:            Allan.   MAC
the VHT AP shall not transmit
frames to non-AP VHT STAs in    "NOTE--The operation of any
the Doze state                  other power-save mechanism
until the NAV duration of the   used by a STA might prevent
TXOP has expired."              the AP from transmitting to the
                                STA once the NAV has
This may be read to imply that expired."
the AP can transmit to STAs in
the doze state after the NAV
has expired. While this may
be true for TXOP power savers,
it is not true for conventional
power-savers that are in the
Doze state.

§ 11.19 does not exist in          Please clarify                           Ed
P802.11-REVmb/D4.01
Should the presenting order of     State "VHT TXOP power save               Ed
clauses "Power management          mode" in clause 11.2.1.4a and
during VHT transmissions" and      "Power management during
"VHT TXOP power save mode"         VHT transmissions" in clause
be exchanged with each other?      11.2.1.4b.
It seems that it can be followed
more readily if the idea of
TXOP PS mode is introduced
first and then the conditions
that STAs in TXOP PS mode are
allowed to enter Doze state.
In the TXOP PS mode, STA           Two possible changes are                 Ed
stays in the Awake state unless    provided. 1. The power
it is allowed to enter the Doze    management scheme
state for certain conditions.      described in this section is
Therefore, to clarify, should it   applicable only when VHT AP
be more appropriate that "the      allows non-AP VHT STAs in
non-AP VHT STAs in TXOP PS         TXOP PS mode (see section
mode to enter Doze state"          11.2.1.4b) to enter Doze state
rather than "VHT TXOP power        during a TXOP.      2. The
save mode at non-AP VHT            power management scheme
STAs" the VHT AP allows or         described in this section is
disallows? As an alternative,      applicable only when VHT AP
the sentence "the power            supports TXOP PS mode (see
management scheme is               section 11.2.1.4b).
applicable only when VHT AP
"supports" VHT TXOP power
save mode" should also be an
more appropriate statement.




The TXOP Power Save scheme         Change lines 18-20 of sub-      Allan.   MAC
allows any STA that is not         clause 11.2.1.4a as follows: 1)
addressed to by the SU/MU          A VHT AP that obtains a TXOP
packet goes into the Doze state    for VHT transmissions shall
during the TXOP. However,          indicate non-AP VHT STAs
within a TXOP, the AP may          using
transmit to multiple STAs or       TXOP_PS_NOT_ALLOWED in
groups, say first group A then     TXVECTOR whether or not they
group B. If a STA belongs to       are allowed to enter Doze
group B, it will go to to DOZE     state if within the obtained
state after receiving the packet   TXOP or the remaining TXOP, it
the AP transmits to group A.       only transmits to one STA or
The STAs in group B will fail to   STAs in the same Group.
receive any packet for the         Otherwise,
remainder of TXOP.                 TXOP_PS_NOT_ALLOWED shall
                                   be set to 1 and non-AP VHT
                                   STAs shall not enter Doze
                                   state.


which frame the TXVECTOR           clarify                                  Ed
associated with?
What matters is whether a STA    change from "that is in Doze    Allan.                       MAC
is allowed to enter Doze state   state" to "that is allowed to
but not whether it is IN Doze    enter Doze state"
state.
"Note that, the state of the     clarify                         Allan.                       MAC
non-AP VHT STA at the end of
the TXOP could be governed by
other power save
mechanisms." what does this
sentence mean?
TXOP trunction will cause        Suggest disallowing TXOP        Allan.                       MAC
some problems. For example,      trunction for TXOP PS mode
the STA in Awake mode will
have advantage to get the
medium. The STA in Doze state
cannot get the NAV setting
information for the next TXOP.
Not only AP but other peer STA
cannot transmit to the STA in
Doze mode (how does the peer
STA know that?)


"A VHT STA that is a member change the text to fix the           AGREE IN PRINCIPLE.            COEX
of a VHT BSS shall not transmit problem.                         Referenced paragraphs are
a 20 MHz VHT PPDU that does                                      updated. New sections added
not use the primary 20 MHz                                       for TDLS operation. Resolution
channel of the BSS."                                             text in 11/310r0.

This is not true when TDLS off
channel operation is used. The
same issues should be fixed in
paragraph #2, #3, #4, #5.


The first three paras can be     Replace with: "A VHT STA that Yongho has a proposed          COEX
simplified without loss.         is a member of a VHT BSS shall resolution
                                 not transmit a PPDU that does
                                 not use the primary 20 MHz
                                 channel of the BSS."
"A VHT STA shall not transmit a Better relate to adjacent          Yongho has a proposed       COEX
160 MHz VHT PPDU using a        80+80MHz transmissions.            resolution
160 MHz channel that cannot
be used to setup
a VHT 160 MHz BSS." This
sentence may not be
necessary.

"A VHT STA shall not transmit a Replace with something using       Yongho has a proposed       COEX
160 MHz VHT PPDU using a        defined terms.                     resolution
160 MHz channel that cannot
be used to setup
a VHT 160 MHz BSS." - "cannot
be used to setup" is not a
defined condition or term.

Ditto at line 22


"a 80+80 MHz VHT PPDU"         As in comment.                      AGREE. As suggested.        Ed
should be revised to "an 80+80
MHz VHT PPDU".


"it may" - normative language      "it might"                      AGREE. As suggested.        Ed
in a note
"The use of RIFS in a VHT BSS is   Replace "deprecated" with      Osama to own deprecation of COEX
deprecated. As such, a VHT AP      "not supported" and delete "As RIFS. Possibly move to REVmb.
shall set the RIFS Mode field in   such,"
the HT
Operation element to 0.". This
is not deprecation, but
prohibition.
If RIFS is merely deprecated,      Delete from "The use of RIFS"                               Ed
then there is no need to forbid    to "As such," inclusive. Same
it. But in any case it seems       change in 9.2.0b.4.2.
unnecessary to give a
justification.

Why only the EDCA is allowed? Please justify.                      Simone has proposed         COEX
Why the HCCA may not be                                            resolution
used?
§ 9.19.2 appears to be        § 9.9.1                              AGREE IN PRINCIPLE. However, Ed
incorrect                                                          with renumbering to REVmb
                                                                   7.0 reference is correct.
§ 9.19.2.3 appears to be          § 9.9.1.3                     AGREE IN PRINCIPLE. However, Ed
incorrect                                                       with renumbering to REVmb
                                                                7.0 reference is correct.

§ 9.19.2.3 appears to be          § 9.9.1.3                     AGREE IN PRINCIPLE. However, Ed
incorrect                                                       with renumbering to REVmb
                                                                7.0 reference is correct.

§ 9.19.2.3 appears to be          § 9.9.1.3                     AGREE IN PRINCIPLE. However, Ed
incorrect                                                       with renumbering to REVmb
                                                                7.0 reference is correct.

Why emphasize on the primary      change it to "A VHT STA that is Yongho has a proposed     COEX
20MHz channel only? For           a member of a VHT 40 MHz, 80 resolution
40/80MHz PPDU, primary            MHz, 160 MHz or 80+80 MHz
40/80 channel is the only valid   BSS shall transmit a 40 MHz
transmission channel              PPDU using the primary40
                                  MHZ channel", or remove the
                                  sentence (11.20.2 presents
                                  detailed rules already)

The phrase of "cannot be used Specify the conditions when a     Yongho has a proposed       COEX
to setup" is not clear.       channel "cannot be used to        resolution
                              setup" a VHT 160 MHz or
                              80+80 MHz BSS.

§ 9.3.7 appears to be incorrect § 9.2.10                        AGREE IN PRINCIPLE. However, Ed
                                                                with renumbering to REVmb
                                                                7.0 reference is correct.

§ 9.19.2.3 appears to be          § 9.9.1.3                     AGREE IN PRINCIPLE. However, Ed
incorrect                                                       with renumbering to REVmb
                                                                7.0 reference is correct.

§ 9.3.7 appears to be incorrect § 9.2.10                        AGREE IN PRINCIPLE. However, Ed
                                                                with renumbering to REVmb
                                                                7.0 reference is correct.
"If the secondary .." Is this     Please clarify.                 Go through the document and Ed
secondary 20MHz channel?                                          make sure we are consistent
Same in a) and b) below.                                          on use of secondary 20MHz
                                                                  channel throughout> Possibly
                                                                  same issue with primary 20
                                                                  MHz channel. Note this may
                                                                  mean changing the entire
                                                                  standard since primary channel
                                                                  was used in 11n.

"If the secondary channel,      Seems to require fixing.          Vinko has proposed resolution COEX
secondary 40 MHz channel or
secondary 80 MHz channel are
busy during this interval,
the STA may take one of the
following steps:" here it says
that the channels are busy, but
below in a) and b) it says that
they are idle.


c) sentence is not finished       Say: "Transmit a 20 MHz mask Vinko has proposed resolution COEX
                                  PPDU on the primary 20 MHz
                                  channel if the primary 20MHz
                                  channel is idle."

§ 9.19.2 appears to be            § 9.9.1                         AGREE IN PRINCIPLE. However, Ed
incorrect                                                         with renumbering to REVmb
                                                                  7.0 reference is correct.

Operating mode should define      Change to "If one or more       Allan.                       COEX
rules and not vice versa. "If a   channels are busy within
transmitter follows the rule      operating bandwidths, the rule
defined in step d) when one or    defined in step d) applies only
more channels are busy within     for the transmitter that is
its operating bandwidth, the      operatin in static BW mode."
transmitter operates in static
BW operation mode.
Otherwise, the transmitter
operates in dynamic BW
operation mode"

"frames" means PPDUs here?        Change to "PPDUs"               Vinko has proposed resolution COEX
"..the STA may transmit a        Sentence may be clearer to   Vinko has proposed resolution COEX
pending greater than 20 MHz include 40MHz and 80MHz
mask PPDU only if the            PPDUs.
secondary 20 MHz channel,
secondary 40 MHz channel and
secondary 80 MHz channel
that would be occupied
by the PPDU have also been
idle during the times the
primary 20 MHz channel CCA is
performed (defined
in 9.3.7 (DCF timing relations))
during an interval of a PIFS
immediately preceding the
expiration of
the backoff counter." Greater
than 20MHz PPDU seems to be
here only 160MHz PPDU.




The action to Restart the      Remove the step d)             Vinko has proposed resolution COEX
channel access should only be
done if the CCA of the 20 MHz
primary channel is idle during
the CCA sensing interval.

"… are listed in 12-1." should   As in comment.               AGREE. Table reference        Ed
be revised as "… are listed in                                corrected.
Table 12-1."


"Potential elements of this set Reword so it doesn't imply that Youhan has proposed         COEX
are listed" - what other        the specification here is       resolution
members of the set are you      incomplete.
hiding from me?
                                ie. "Table 12-1 defines the
                                members of this set.".
The description is not clear.   add "Table " before 12-1        Duplicate. See #71.         Ed

Is "Append" a defined editing    Change/insert?               AGREE. Editing instructions   Ed
term?                                                         perfected.
"at least one of the 20 MHz    a) report all cases (ugh) or b)      Youhan has proposed          COEX
channels in the secondary40 is refer to the CCA clause              resolution
busy" yet the CCA would also (easier!)
report busy on 40MHz ED or a
40MHz PPDU. Ditto
secondary80

"40, 80, 160" => "40, 80 and       As in comment                    AGREE. As suggested.         Ed
160"
a 80 => an 80                      As in comment                    AGREE. As suggested.         Ed
in figure 7-4e, the only           Move the                         AGREE. As suggested. Note:   COEX
reserved bit is in position 29;    'Solicited/unsolicited' bit in   Section of comment was
For helping the receiver           position 29 and have B1 to be    wrong. Comment refers to
parsing in case of future          reserved; modify table 7-6h      7.1.3.5a. 11/345r0.
extensions, the posistion of the   accordingly;
reserved bit should be within
the first byte;
For generality and to avoid        As in comment                                                 Ed
tunnel vision, it could be a
good idea to swap the P40 and
secodnary40 channels
The word "Primary" in 160Mhz       add "Primary" to 160MHz in                                    Ed
is missing from Figure 12-1        Figure 12-1

inconsistent 'primary' word        add "primary" to 160MHz in                                    Ed
usage in Figure 12-1               Figure 12-1
To clarify, "Primary 160MHz" in    Put the word "Primary" to                                     Ed
Figure 12-1                        160MHz in Figure 12-1
CCA for VHT is more                a) report all cases (ugh) or b) Youhan has proposed           COEX
complicated than described in      for VHT STAs, refer to the CCA resolution
this clause. Under some            clause (easier!)
circumstances aCCATime is
replaced by aCCAMidTime,
there is energy detect, at
P65L50 a constraint is missing
that the SIG field be on the
primary 20, there is no
language for non-primary
channels etc. Also, none of this
is normative language.

SIG should be L-SIG                As in comment                    Youhan has proposed          COEX
                                                                    resolution
SIG should be L-SIG                As in comment                    Youhan has proposed          COEX
                                                                    resolution
SIG should be L-SIG                As in comment                    Youhan has proposed          COEX
                                                                    resolution
SIG field appears to be          L-SIG field                      AGREE. As suggested.          Ed
incorrect
"SIG field" --> "L-SIG"          Correct it                       Youhan has proposed             COEX
                                                                  resolution
The "INDICATED_*" names are Change, e.g. to                       COUNTER. Agreed that the        COEX
not very descriptive        NONHT_PPDU_* or similar               current names are not very
                                                                  descriptive, yet NON_HT is
                                                                  more commonly used than
                                                                  NONHT, and NON_HT_PPDU_
                                                                  is not especially compact.
                                                                  Therefore change
                                                                  INDICATED_CH_BANDWIDTH
                                                                  =>
                                                                  CH_BANDWIDTH_IN_NON_HT
                                                                  and
                                                                  INDICATED_DYN_BANDWIDTH
                                                                  =>
                                                                  DYN_BANDWIDTH_IN_NON_H
                                                                  T. Resolution text in 11/413r1.


Section numbers appear to be     Insert sections 17.2.2.5 and     AGREE IN PRINCIPLE. REVmb Ed
incorrect. Change 'Insert        17.2.2.6 following 17.2.2.4 as   has sections through 17.2.2.6.
sections 17.2.2.14 and           follows:                         New sections inserted as
17.2.2.15 following 17.2.2.13                                     17.2.2.7 and 17.2.2.8.
as follows:' to
wrong section numbers:           Change the sentence to "Insert Duplicate. See #748.            Ed
"Insert sections 17.2.2.14 and   sections 17.2.2.5 and 17.2.2.6
17.2.2.15 following 17.2.2.13    following 17.2.2.4 as follows"
as follows"
Editing instruction should say   per comment                      Duplicate. See #748.          Ed
to insert whatever are the
correct numbers, but REVmb
D5.0 ends at 17.2.2.5

Typo.                            Change "17.2.2.13" into          Duplicate. See #748.          Ed
                                 "17.2.2.14".
§ 17.2.2.13 appears to be        § 17.2.2.4                       Duplicate. See #748.          Ed
incorrect
"in the Service field" is        Delete "in the Service field"    AGREE. 11/413r1.              COEX
redundant and not strictly
correct - the scrambing
sequence that happens to
overlap the service field is
modified, not bits in the
service field itself
Grammar issue                      Modify "Service Field" to         AGREE. As suggested. Ed: Note Ed
                                   "SERVICE Field"                   that this was deleted with
                                                                     resolution for #255.
This note refers to MAC            Insert reference                  COUNTER. Agreed, and adding COEX
behaviors, so a reference                                            appropriate text in the MAC
would make the note more                                             section (which currently does
powerful. Ditto P66L51                                               not exist), with
                                                                     implementation as per
                                                                     11/413r1.
Typo.                              Change "17.2.2.14" into           Duplicate. See #748.          Ed
                                   "17.2.2.15".
§ 17.2.2.14 appears to be          § 17.2.2.6                        Duplicate. See #748.         Ed
incorrect
change "CH_BANDWIDTH" to as comment                                  AGREE. As suggested.         Ed
"INDICATED_CH_BANDWIDTH"


Missing editing instruction to     per comment                       AGREE. Editing instruction   Ed
insert 17.2.3.6 and 17.2.3.7                                         added.

"Nonzero integer" is more     Relax the non-zero                     AGREE. Resolution text in    COEX
restrictive than necessary -  requirement                            11/413r1.
only the first 7 bits of the
scrambling sequence need to
be non-zero, and less
restriction creates more
entropy
New text should be underlined As in comment                          AGREE. Underscore added.     Ed

The table is only referenced for   Remove first data row and AGREE. 11/413r0.                     COEX
the case when                      column. Add "when
INDICATED_CH_BANDWIDTH is          INDICATED_CH_BANDWIDTH is
present, so the first data row     present" to title.
and column can be removed.

I also recommend qualifying
the title so as not to mislead.




Dashed list should be              per comment                       Duplicate. See #258.         Ed
underscored
The format for the title of the    use IEEE format for table title   AGREE. Format updated.       Ed
table is wrong.
second column in the table has Please clarify.                   COUNTER. Agree with         COEX
"-", not sure what that                                          comment but implementation
represents.                                                      is made redundant by #1209.
                                                                 See #1209 for text changes.
                                                                 11/413r0.

The first 7 bits of scrambling     Add CCA of the CTS transmitter Jarkko has proposed resolution COEX
sequence of the CTS message        to CTS frame. The CCA may use
are missing CCA inidcation. The    B3 and B4 of the CTS frame.
CTS transmitter is measuring       The decoding should be the
CCA for the BSS bandwidth or       same as in B5 and B6.
for the whole 80 MHz or 160
MHz bandwidth that has been
used. The CTS message may
easily contain the whole
available bandwidth and
enable devices to get
knowledge of the of the CCA at
hte CTS transmitter.
If multiple RTS CTS
transmissions are used, the
CCA of hte CTS transmitter
enables to query channel at
the CTS transmitter side and
the second RTS CTS may take
the available channels into use.




NON_HT_CBW80+80 is                 Change "11                  AGREE. 11/413r1.              COEX
missing.                           (NON_HT_CBW160)" to "11
                                   (NON_HT_CBW160/NON_HT_
                                   CBW80+80)"
"CH_BW" name is not aligned        Align.                      AGREE. Figrue updated and     COEX
with text                                                      aligned with text change from
                                                               #254. Resolution text in
                                                               11/413r1.
The sentence, "Insert the          As in comment. (It may be   AGREE IN PRINCIPLE. Adding    Ed
following clause (Clause 22)       "after Clause 20:" because  editing note for insertion.
after Clause 21:" should be        REVmbD4.01 does not include
inserted just before "22. Very     Clause 21.)
High Throughput (VHT) PHY
specification".
"for multi-user (MU)              As in comment.                                                  Ed
transmission" should be
revised to "for a multi-user
(MU) transmission".
it is better to describe more     Change 'In the case of a MU      AGREE IN PRINCIPLE. Changed Ed
clearly about the maximum         transmission, the number of      to read "An MU transmission
number of users and the           users is limited                 supports up to four users with
maximum number of streams         to four and the number of        up to four space-time streams
per user supported in VHT.        streams per user is limited to   per user."
                                  four' to 'In the case of a MU
                                  transmission, the number of
                                  users is up to four and the
                                  maximum number of streams
                                  per user is up to four'

may lead misunderstanding on      Add 'up to' in the discriptions: Duplicate. See #1088.          Ed
the maximum number of users       that is, 'In the case of a MU
and the maximum number of         transmission, the number of
streams per user supported in     users is up to four and the
VHT.                              maximum number of streams
                                  per user is up to four'

For clarity and to contrast with As in comment                     AGREE IN PRINCIPLE. See fix in Ed
the remainder of the sentence,                                     #261.
channel -> contiguous channel

After "as well as" reads badly. Try "20, 40, 80 and 160            AGREE IN PRINCIPLE. Changed Ed
Seems to need an article - but contiguous asnd 80+80 non-          to read "...for 20 MHz, 40 MHz,
which? Also, writing "as well as contiguous channel widths"        80 MHz and 160 MHz
support for" might be clearer                                      contiguous channel widths and
                                                                   support for 80+80 MHz non-
                                                                   contiguous channel width."

"or 256QAM" yet "and 160          and 256QAM                       AGREE. As suggested.           Ed
MHz" above
change Modulation wording to      Change "(16-QAM), 64-QAM,        DISAGREE. While it is true that Ed
make it clear that 256 QAM is a   additionally, VHT PHY            we describe the number of
new feature                       extended the modulation set      spatial streams supported as
                                  to support 256-QAM"              'extended' to 8, we don't do
                                                                   the same for bandwidth. Why
                                                                   for 256-QAM?
When specifying that VHT STA       Change to "single stream        AGREE.                       PHY
shall support "MCSs 0 through      (transmit or recive) for MCSs 0
7 in all supported channel         through 7 in all supported
widths" - its not clear about      channel widths"
the number of spatial streams

"2 or more streams" should be As in comment.                      AGREE.                        PHY
changed to "2 or more spatial
streams."

There are many erroneous           As in comment.                 AGREE. The trucated lines have Ed
cells in the table 22-1 and                                       been made visible again with
should be corrected as Table                                      conversion of the table to the
22-1 in 10/1361r3.                                                standard IEEE format.


This whole table needs to be       As in comment                  Duplicate. See #197.          Ed
verified. There may be errors
and unfinished sentences.

17(Orth                            17 (Orth                      Duplicate. See #197.           Ed
In Table 22-1--TXVECTOR and        Complete the description in   Duplicate. See #197.           Ed
RXVECTOR parameters, the           "Value" column of the first
description in "Value" column      field in Table 22-1--TXVECTOR
of the first field " FORMAT" is    and RXVECTOR parameters.
incomplete.
Impossible to review this table    Suggest a revised version of   Duplicate. See #197.          Ed
in any detail due to truncated     this table is prepared for
entries. (Including LHS column -   separate review
see e.g. RCPI)

One sentence ends as 'In this      Complete the sentence.         Duplicate. See #197.          Ed
case, the'
The value cell appears to be       untruncate.                    Duplicate. See #197.          Ed
truncated
One sentence ends in the           Complete the sentence.         Duplicate. See #197.          Ed
middle; 'In this case, the'
The sentence is not finished for   revise accordingly             Duplicate. See #197.          Ed
the value of the
"Format"parameter.
Missing sentences compared       Change the last sentence        Duplicate. See #197.      Ed
to 10/1361r3 under Value.        under Value to "In this case,
                                 the modulation is determined
                                 by the NON_HT_MODULATION
                                 parameter. HT_MF indicated
                                 HT-mixed format. HT_GF
                                 indicates HT-greenfield format.
                                 VHT indicates VHT format."


"NON_HT_DUP_OFDM" is only Probably another term is used COUNTER. Resolution provided PHY
used in this table        elsewhere - update table      in 11/372r2.

NON_HT_MODULATION         Indicate 'N' under both                   Youhan. As suggested   PHY
should not be present in  TXVECTOR and RXVECTOR.
TXVECTOR or RXVECTOR when
FORMAT is not NON_HT.

1 to 4095, but with VHT-STF,     Determine the true min value       Youhan.                PHY
VHT-LTFs, SIGB, 1 is not an      and insert
allowed value
Why is L_length not present      Please verify                      Robert.                PHY
for VHT format? Also for
L_datarate
in Mbps                         in units of Mbps. Also rate =>      AGREE. As suggested.   Ed
                                data rate
rate => data rate (vs code rate As in comment                       AGREE. As suggested.   Ed
etc)
TXVECTOR and RXVECTOR are Insert                                    Duplicate. See #567.   PHY
missing Y/N in this row and the
next 2 rows
Missing sentences compared Add the following to the Value:          Duplicate. See #197.   Ed
to 10/1361r3 under Value.       "6, 9, 12, 18, 24, 36, 48, and 54
                                OFDM: 6, 9, 12, 18, 24, 36, 48,
                                and 54"


L_DATARATE should be             Indicate 'Y' under both    AGREE                          PHY
present in both TXVECTOR and     TXVECTOR and RXVECTOR if
RXVECTOR if the FORMAT is        the FORMAT is NON_HT or
NON_HT or HT_MF.                 HT_MF. Indicate 'N' under
L_DATARATE should not be         both TXVECTOR and RXVECTOR
present in TXVECTOR or           if the FORMAT is HT_GF or
RXVECTOR if the FORMAT is        VHT.
HT_GF or VHT.

Values are not shown.            Complete the table.                Duplicate. See #197.   Ed
The value cell appears to be        untruncate.                    See #197                    PHY
truncated
No values.                          Complete the table.            Duplicate. See #197.        Ed
It seems something is missing       check and revise               Duplicate. See #197.        Ed
here in the value column

"Data rate value that is in the L- "data rate value that           AGREE IN PRINCIPLE. Changed Ed
SIG" is misleading - an            determines the RATE field of    to read "that is encoded in the
encoding of the data rate is       the L-SIG"                      L-SIG Rate field"
placed in the L-SIG
"HT_MF or VHT" but 9.13.5.4 As in comment                          COUNTER. Resolution provided PHY
only refers to HT_MM - either                                      in 11/372r2.
that needs updating with VHT
or we don't need VHT here

Sentence in the third column        Please finish the sentence.    Duplicate. See #197.        Ed
is not finished.
The cell is not complete ( Value    Add remaining text             Duplicate. See #197.        Ed
entry)
The cell is not complete ( Value    Add remaining text             Duplicate. See #197.        Ed
entry)
Although the spec has always        "7 zero bits and 9 bits reserved AGREE.                    PHY
used "null bits" in this context,   as zeros". Ditto P73L8
"null bits" has never been
defined.
Description should be updated                                      DISAGREE. The calculation of PHY
according to the usage of the                                      the transmitted bits during the
scrambling seed for the BW                                         scrambler sequence is
indication                                                         [zeros(1,7) zeros(1,9)] xor
                                                                   scrambling sequence, and it is
                                                                   the scrambling sequence that
                                                                   is modified by the BW
                                                                   indication. That is, [zeros(1,7)
                                                                   zeros(1,9)] is never modified
                                                                   by the BW indication.


"OFDM" or "OFDM or                  As in comment                  See #266                    PHY
NON_HT_DUP_OFDM (term
may need updating)"
For Service, when format is         Please verify                  Robert.                     PHY
VHT, why is it "not present"
Service field in VHT is listed as                                     Yes. The SERVICE field is    Ed
"not Present" Is this correct?                                        determined in the PHY by the
                                                                      INDICATED_CH_BANDWIDTH,
                                                                      INDICATED_DYN_BANDWIDTH
                                                                      and a random seed.


In table 22-1 SERVICE          In VHT raw, add "Scrambler             Robert.                       PHY
parameter is not present when initialization, 7 null bits + 9
format is VHT. While it should reserved null bits"
be the same description as
that of HT format.

This needs an "otherwise" for       As in comment                     AGREE. Resolution text in     PHY
VHT for TX, so it cannot be a                                         11/372r2.
pure reference to clause 20.
Ditto Agg, ext, antenna set

TXVECTOR AGGREGATION                Change "See corresponding         COUNTER. Although it is true PHY
should not be based on the          entry in Table 20-1" to "For      that all VHT frames are A-
corresponding entry of table        VHT format, set to 1, for other   MPDUs, in HT, the
20-1. For FORMAT VHT, this is       formats, see corresponding        AGGREGATION parameter is
set to 1 always.                    entry in Table 20-1"              only used at the PHY level to
                                                                      set a bit in the PLCP header (on
                                                                      TX) and report the value of
                                                                      that bit (on RX). But since all
                                                                      VHT frames are A-MPDUs,
                                                                      therefore an AGGREGATION bit
                                                                      is not required (it is implicit by
                                                                      virtue of the PPDU adopting a
                                                                      VHT format) and so the
                                                                      AGGREGATION parameter is
                                                                      not required. But the
                                                                      commenter is correct that
                                                                      special processing for VHT
                                                                      frames is required for this
                                                                      parameter – for this, see CID
                                                                      #275.




Missing sentences compared          Add the following to the Value: Duplicate. See #197.            Ed
to 10/1361r3 under Value.           "vector matrices.
                                    CSI_MATRICES indicates that
                                    CHAN_MAT is a set of channel
                                    state matrices."
The sentence of 'CHAN_MAT' is Complete the sentence.         Duplicate. See #197.        Ed
not enough.
In the row of 'FORMAT is      Add 'CSI_MATRICES'                                         Ed
HT_MF or HT_GF',
'CSI_MATRICES' is missing.
The value cell appears to be  untruncate.                    See #197                    PHY
truncated

also at 76.06, 76.11, 76.16,
76.20, 76.28, 76.51
The sentence of 'CHAN_MAT' is Complete the sentence.         Duplicate. See #197.        Ed
not enough.
In the row of 'FORMAT is       Add 'CSI_MATRICES'                                        Ed
HT_MF or HT_GF',
'CSI_MATRICES' is missing.
Seem to be missing the dual of Add                           See #197                    PHY
this - i.e. "EXPANSION_MAT",
"EXPASION_MAT_TYPE"

Missing word compared to      Add the following to the       Duplicate. See #197.        Ed
10/1361r3 under Condition.    Condition:
                              "CHAN_MAT_TYPE is
                              COMPRESSED SV"
Missing word compared to      Add the following to the       Duplicate. See #197.        Ed
10/1361r3 under Condition.    Condition:
                              "NON_COMPRESSED_SV"
Define CHAN_MAT for VHT.      Add "Contains a set of         AGREE IN PRINCIPLE. The size PHY
                              compressed beamforming         of the feedback is clearly
                              feedback matrices as defined   specified in 22.3.12.2, thus the
                              in 22.3.12.2 ( Beamforming     last sentence not needed in
                              feedback matrix V) based on    this table. Also, NDP is the
                              the                            only PPDU format for sounding
                              channel measured during the    in 11ac. Resolution text in
                              training symbols of the        11/363r2.
                              received PPDU. The
                              number of elements depends
                              on the number of spatial
                              streams and the
                              number of transmit chains"

There are 30 non-ANA TBDs      Resolve TBDs                  Brian                       PHY
that need to be rsolved before
going to WG LB
For the CHAN_MAT parameter: check and revise                   Duplicate. See #145.   PHY
the condition column is
incomplete (or has an extra
"and" at the end) and the value
column is TBD.

Missing word compared to          Add the following to the     Duplicate. See #197.   Ed
10/1361r3 under Condition.        Condition:
                                  "CHAN_MAT_TYPE is
                                  COMPRESSED_SV"
Section 7.3.1.32 specifies that Change 'TBD' in Value to       Duplicate. See #145.   PHY
the compressed bamforming "Contains a set of compressed
report field shall contain the    beamforming feedback
beamforming feedback matrix matrices as defined in
V given in 20.3.12.2.5. Also,     20.3.12.2.5 (Compressed
the delta SNR for each            beamforming feedback matrix)
subcarrier is included in case of based on the channel
feedback for MU.                  measured during the training
                                  symbols of the received
                                  PPDU."
CHAN_MAT should not be            Indicate 'N' under both      AGREE                  PHY
present in TXVECTOR or            TXVECTOR and RXVECTOR.
RXVECTOR when Condition is
'Otherwise'.
Missing alphabets.                Change 'RC' under Parameter Duplicate. See #197.    Ed
                                  to 'RCPI'

Name of parameter truncated untruncate.                        See #197               PHY

Condition truncated. Also at   untruncate.                     See #197               PHY
line 39 and 42.
Missing phrase compared to     Add "CHAN_MAT_TYPE is           Duplicate. See #197.   Ed
10/1361r3 under Condition.     CSI_MATRICES" to Condition.

Missing phrase compared to     Add "CHAN_MAT_TYPE is           Duplicate. See #197.   Ed
10/1361r3 under Condition.     COMPRESSED_SV or
                               NON_COMPRESSED_SV" to
                               Condition.
Define SNR for VHT                Add "Is a measure of the       AGREE                   PHY
                                  received SNR per stream. SNR
                                  indications of 8 bits are
                                  supported. SNR shall be the
                                  sum of the decibel values of
                                  SNR per tone
                                  divided by the number of tones
                                  represented in each stream as
                                  described in 7.3.1.32 (VHT
                                  Compressed Beamforming
                                  Report field)"


Define TBDs in the table (few     As in comment                  Youhan.11/412r0.        PHY
places)
Missing phrase compared to        Add "CHAN_MAT_TYPE is           Duplicate. See #197.   Ed
10/1361r3 under Condition.        COMPRESSED_SV" to
                                  Condition.
Per stream SNR is defined in      Change "TBD" in Value to "Is a See #146                PHY
7.3.1.32                          measure of the received SNR
                                  per stream. SNR indication of
                                  8 bits are supported. SNR shall
                                  be the sum of the decibel
                                  values of SNR per tone divided
                                  by the number of tones
                                  represented in each stream as
                                  described in 7.3.1.32 (VHT
                                  Compressed Beamforming
                                  Report field)."


For the SNR parameter: the        check and revise               See #197 and #146       PHY
condition column is incomplete
(or has an extra "and" at the
end) and the value column is
TBD.
The sentence of 'RCPI' is not     Complete the table.            Duplicate. See #197.    Ed
enough.
“RSSI” entry is incomplete.                                      Duplicate. See #197.    Ed
The value of the RSSI             check and revise               Duplicate. See #197.    Ed
parameter is incomplete
For clarity, since VHT uses MCS   As in comment                  Robert.                 PHY
in a difference sense than 11n,
"MCS" => modulation and
coding scheme and number of
spatial streams
Define REC_MCS             Add "Indicates the MCS that      Duplicate. See #579.   PHY
                           the STA’s receiver
                           recommends"
Recommended MCS is defined Change "TBD" in Value to         AGREE                  PHY
in 7.1.3.5a.               "Indicates the MCS that the
                           STA's receiver recommends."
                           Also, indicate "N" under
                           TXVECTOR and "O" under
                           RXVECTOR.

There's a TBD                     resolve it                Duplicate. See #579.   PHY
The value of the REC_MCS          check and revise                                 Ed
parameter when the FORMAT
is VHT is TBD
The sentence of 'FORMAT is        Complete the table.       Duplicate. See #197.   Ed
HT_MF or HT_GF' is not
enough.
The sentence of 'FORMAT is        Complete the table.       Duplicate. See #197.   Ed
HT_MF, HT_GF or VHT' is not
enough.
The sentence of 'RSSI' is not     Complete the table.       Duplicate. See #197.   Ed
enough.
The RSSI "value" Entry is not     Add remaining text        Duplicate. See #197.   Ed
complete
The sentence of 'FORMAT is        Complete the table.       Duplicate. See #197.   Ed
HT_MF or HT_GF' is not
enough.
First row: the enumerated         fix enumerated types      Duplicate. See #197.   Ed
types for CH_BANDWIDTH, in
case of HT_MF or HT_GF seem
incomplete; for the VHT it also
seems incomplete;

Enurmerated type not        Complete the details after  Duplicate. See #197.       Ed
complete for CH_BANDWIDTH - "HT_CBW20 for 20 MHz and 40
-> FORMAT is HT_MF or HT_GF MHz upper and 40…"
--> Enumerated type :
"HT_CBW20 for 20 MHz and 40
MHz upper and 40"


sentence for enumerated type sentence needs to be complete Duplicate. See #197.    Ed
is incomplete
Missing phrase compared to   Add "MHz lower modes          Duplicate. See #197.    Ed
10/1361r3 under Value        HT_CBW40 for 40 MHz" to
                             Value.
channel BW 80MHz and 160         Please include 80MHz and        Duplicate. See #197.             Ed
MHz is not included              160MHz BW
some are missing in the          some parts need to be           Duplicate. See #197.             Ed
enumerated type (e.g. 80, 160)   included

Missing phrase compared to       Add "HT_CBW80 for 80 MHz   Duplicate. See #197.                  Ed
10/1361r3 under Value            HT_CBW160 for 160 MHz
                                 HT_CBW80+80 for 80+80 MHz"
                                 to Value.
During VHT discussions, we       As in comment              COUNTER. Resolution text              PHY
realized that determining the                               provided in 11/372r2.
ch bw of legacy ppdus is a
harder problem, and so
probably this needs a modifier
for the received side i.e.
"channel bandwidth as
estimated by the receiver",
rather than the absolute
confidence impied here

BW is not a defined              Define BW as an abbreviation; COUNTER. Add definition for        PHY
abbreviation, but is used        but here, spelling it out in full BW. Resolution text provided
widely.                          would be preferred                in 11/372r2.

sentence for enumerated type sentence needs to be complete Duplicate. See #197.                   Ed
is incomplete
Enurmerated type not         Complete the details after    Duplicate. See #197.                   Ed
complete for CH_BANDWIDTH - "NON_HT_CBW80+80 for….
->FORMAT is
NON_HT --> Enumerated type :
"HNON_HT_CBW160 or
NON_HT_CBW80+80 for"

Missing phrase compared to       Add "non-HT duplicate format Duplicate. See #197.                Ed
10/1361r3 under Value            NON_HT_CBW20 for all other
                                 non-HT formats" to Value.
The parameters in Table 22-1--   Change the parameters    Duplicate. See #197.            Ed
TXVECTOR and RXVECTOR            "INDICATED_DYN_BAN" and
parameters                       "INDICATED_CH_BAND" in
"INDICATED_DYN_BAN" and          Table 22-1--TXVECTOR and
"INDICATED_CH_BAND" do not       RXVECTOR parameters to
match the parameters             INDICATED_DYN_BANDWIDTH
INDICATED_DYN_BANDWIDTH          and
and                              INDICATED_CH_BANDWIDTH
INDICATED_CH_BANDWIDTH           respectively.
respectively in Section
9.2.0b.6a VHT RTS procedure.




INDICATED_DYN_BANDWIDTH INDICATED_DYN_BANDWIDTH Duplicate. See #197.                      Ed
is enumerated type      is either dynamic or static. A
                        booloean with true or false
                        value is more meaning ful

Missing alphabets compared to Add "DWIDTH" to parameter.          Duplicate. See #197.    Ed
10/1361r3 under Parameter

Missing phrase compared to       Add "Static if the transmitter is Duplicate. See #197.   Ed
10/1361r3 under Value            capable of Static bandwidth
                                 operation
                                 Dynamic if the transmitter is
                                 capable of Dynamic bandwidth
                                 operation" to Value.

enumerated type is missing    enumerated type needs to be         Duplicate. See #197.    Ed
                              filled
The enumerated types for the add enumerated types                 Duplicate. See #197.    Ed
case FORMAT is
NON_HT are missing
Missing alphabets compared to Add "WIDTH" to parameter.           Duplicate. See #197.    Ed
10/1361r3 under Parameter

Missing phrase compared to       Add "NON_HT_CBW20,               Duplicate. See #197.    Ed
10/1361r3 under Value            NON_HT_CBW40,
                                 NON_HT_CBW80,
                                 NON_HT_CBW160" to Value.

NON_HT_CBW80+80 is               Change "NON_HT_CBW160" to AGREE (Editor: Note that this PHY
missing.                         "NON_HT_CBW160/NON_HT_ resolution is inconsistent with
                                 CBW80+80"                 Table 17-ac1 which has no
                                                           NON_HT_CBW80+80)
enumerated type is missing    enumerated type needs to be   Duplicate. See #197.         Ed
                              filled
Define CH_OFFSET                                            Duplicate. See #588.         PHY

CH_OFFSET/VHT is missing an Make it all a TBD?              Duplicate. See #588.         PHY
otherwise
CH_OFFSET is currently TBD.     Delete the CH_OFFSET row    AGREE. The following VHT PHY PHY
Note that given the BW of the from Table 22-1.              MIBs given in Table 22-23 is
BSS, location of the Primary 20                             sufficient to determine the
MHz and the BW of the packet                                location of primary 20 MHz,
(CH_BANDWIDTH), the portion                                 primary 40 MHz and primary
of the channel used for                                     80 MHz (for 160 MHz and
transmission is clearly defined                             80+80 MHz BSS) channels
(Primary20, Primary40,                                      within the spectrum used by
Primary80 or the entire                                     the BSS:
160/80+80 MHz channel).                                     •
Thus, CH_OFFSET is not                                      dot11CurrentChannelBandwidt
required and is redundant.                                  h
                                                            •
                                                            dot11CurrentChannelCenterFr
                                                            equencyIndex1
                                                            •
                                                            dot11CurrentChannelCenterFr
                                                            equencyIndex2
                                                            •
                                                            dot11CurrentPrimary20MHzCh
                                                            annel
                                                            Since PPDUs with BW less than
                                                            the BSS BW must be
                                                            transmitted using the primary
                                                            20/40/80 MHz channels,
                                                            CH_OFFSET is not necessary in
                                                            the TX_VECTOR. Hence
Numeric value with commas.    replace commas with spaces    CH_OFFSET should be deleted Ed
                                                            AGREE. As suggested.
Ditto 76.57
"useful data" is somewhat     Omit or find a better name                                 Ed
casual usage
"excluding the padding" -     Be specific - e.g. A-MPDU     Brian. 11/372r2. [Ed: Need to PHY
seems to be ambiguous - PHY   padding octets                revisit this resolution. Octets
padding or zero-length A-                                   are always 'whole'. More
MPDU subframe?                                              importantly the intent was to
                                                            exclude A-MPDU EOF delimiter
                                                            padding from the length not
                                                            just A-MPDU padding octets.]
Missing sentences compared        Copy the Value portion from      Duplicate. See #197.    Ed
to 10/1361r3 under Value.         10/1361r3

Incomplete sentence :          Fill in the details after (if…      Duplicate. See #197.    Ed
LENGTH->FORMAT is VHT : -->
"….last octet of the last non-
zero
length A-MPDU subframe but
excluding the padding (if"

Cell is too small so text has     Ensure all table cells are set to Duplicate. See #197.   Ed
been truncated.                   auto-fit.
The description of the            complete it with" (if present) Duplicate. See #197.      Ed
parameter "LENGTH" in             in the last subframe.
format VHT is not completed
with end of (if.
Many values on this page seem     check and revise                                         Ed
incomplete; they are not
shown well in the table. One of
the values is TBD

the Value entry for               Add remaining text               Duplicate. See #197.    Ed
CH_BANDWIDTH under
"FORMAT is HT_MF or HT_GF"
is not complete
The sentence of 'FORMAT is        Complete the table.              Duplicate. See #197.    Ed
HT_MF or HT_GF' is not
enough.
The sentence of 'FORMAT is        Complete the table.              Duplicate. See #197.    Ed
NON_HT' is not enough.
the Value entry for               Add remaining text               Duplicate. See #197.    Ed
CH_BANDWIDTH under
"FORMAT is NON_HT" is not
complete
The sentence of 'FORMAT is        Complete the table.              Duplicate. See #197.    Ed
NON_HT' is not enough.
the Value entry for               Add remaining text               Duplicate. See #197.    Ed
INDICATED_DYN_BAN under
"FORMAT is NON_HT" is not
complete
The sentence of 'FORMAT is        Complete the table.              Duplicate. See #197.    Ed
NON_HT' is not enough.
the Value entry for               Add remaining text               Duplicate. See #197.    Ed
INDICATED_CH_BAN under
"FORMAT is NON_HT" is not
complete
the Value entry for LENGTH        Add remaining text            Duplicate. See #197.            Ed
under "FORMAT is VHT" is not
complete
The sentence of 'FORMAT is        Complete the table.           Duplicate. See #197.            Ed
VHT' is not enough.
User indexing is confusing, and   a) All MU parameters in this  Brian                           PHY
probably would benefit from       table should be length-4,
the concept of a null user. For   indexed by USER_INDEX.
instance, user indices are 0-3,   Discard USER_NUM.
USER_NUM is another "index"       Parameters for null users (0
(see P77L59) that seems to run    STS) should be reserved.
1…NUM_USERS. (NUM_USERS           NUM_USERS should be the
!= USER_NUM is an error-          sum of non-null users.
prone distinction)                Or, b) Rename USER_INDEX to
                                  USER_SIGA_INDEX, and update
                                  the SIGA descriptions
                                  accordingly. Rename
                                  USER_NUM to
                                  USER_VECTOR_INDEX.
                                  Also, relate Nu to NUM_USERS,
                                  perhaps at Table 22-5

No reason why USER_INDEX          Change N -> O                 AGREE.                          PHY
should not be reported on RX

Range of groupID is missing       Add 0 - 63                    AGREE IN PRINCIPLE. Added        PHY
                                                                "Integer: range 0-63 (see Table
                                                                22-9)."
These partial AID rules are       Update and/or add reference   COUNTER. Rules are               PHY
oversimplified                    to relevant MAC section       complicated, so let’s just use
                                                                an integer range (typical for
                                                                this section) + reference to
                                                                9.7e. Since there are rules for
                                                                group addressed frame and
                                                                individually addressed frames,
                                                                this is ultimately a function of
                                                                RA, AID and/or BSSID, so the
                                                                term “intended recipients(s)” is
                                                                approrpriately broad.
                                                                Resolution text in 11/372r2.




rage                              range                         AGREE. As suggested.            Ed
indicates AP                      indicates that the AP         AGREE. As suggested.            Ed
What if the STA is not an AP?     Define                        Allan.                          PHY
the name of the parameter       use TXOP_PS_NOT_ALLOWED Allan.                                 PHY
TXO P_PS is not consistent with
the one used in 11.2.1.4a
(TXOP_PS_NOT_ALLOWED)

In case of MU feedback, delta Add a new row with Parameter       AGREE (Editor: This resolution PHY
SNR per tone also needs to be = "DELTA_SNR".                     does not make sense. How
sent from PHY to MAC.         If Condition = "FORMAT is          does the PHY know about the
                              VHT", then Value = "If receiving   Feedback Type field in the VHT
                              a beamforming feedback frame       MIMO Control field? This field
                              in which the Feedback Type         has yet to be generated by the
                              subfield in the VHT MIMO           MAC)
                              Control field is set to MU,
                              contains a set of delta SNR for
                              each space-time stream for a
                              subset of the subcarriers as
                              defined in 7.3.1.33 (MU
                              Exclusive Beamforming Report
                              field). Not present
                              otherwise.", TXVECTOR = "N",
                              RXVECTOR = "O".
                              If Condition = "Otherwise",
                              Value = "Not present",
                              TXVECTOR = "N", RXVECTOR =
                              "N".


In case of SU transmissions, the   Add a new row with Parameter AGREE                          PHY
TX needs to set the                = "Beamformed".
'Beamformed' bit in VHT-SIG-A.     If Condition = "FORMAT is VHT
Also, 22.3.4.4 refers to such      and NUM_USERS set to 1",
parameters in the TXVECTOR,        then Value = "Set to 1 if a
which is currently not defined.    beamforming steering matrix is
                                   applied. Set to 0 otherwise.",
                                   TXVECTOR = "Y", RXVECTOR =
                                   "O".
                                   If Condition = "Otherwise",
                                   Value = "Not present",
                                   TXVECTOR = "N", RXVECTOR =
                                   "N".

The sentence of 'FORMAT is         Complete the table.           Duplicate. See #197.          Ed
VHT' is not enough.
To be consistent with what         TXOP_PS_NOT_ALLOWED. 0                                             Ed
mentioned in line 19, page 61,     indicates AP allows non-AP
change the parameter name          VHT STAs to enter Doze state
from "TXOP_PS" to                  during a TXOP.
"TXOP_PS_NOT_ALLOWED."
Also, it is suggested to use the
term "Doze state" instead of
"doze mode."
TBD                                Fill descriptions.               Youhan.11/412r0.                  PHY
content of the whole section is    fill in the missing content      See #1104                         PHY
TBD
define the effect of                                                See #1104                         PHY
CH_BANDWIDTH, CH_OFFSET…

There's a TBD                      resolve it                       See #1104                         PHY
TBD' is remained.                  Fill 'TBD'                                                         Ed
Often a NON_HT_DUP packet          Generalize receiver to include   DISAGREE. NON_HT PPDU             PHY
is received by a clause 17         non ht dup on RX                 includes both OFDM and
receiver.                                                           NON_HT_DUP_OFDM PPDUs,
                                                                    so this is already generalized.

                                                                    A better question is by which
                                                                    clause NON_HT_DUP_OFDM
                                                                    PPDUs should be received – if
                                                                    by clause 17, then duplication
                                                                    cannot be detected or
                                                                    exploited, so setting a
                                                                    meaningful
                                                                    NON_HT_DUP_OFDM in
                                                                    RXVECTOR really requires
                                                                    clause 20 (arguably 11mb’s
                                                                    job) and clause 22 changes.
                                                                    See CID 279 for the changes.




Grammer:                       Clarify the sentence.                                                  Ed
"Likewise the PHY-
RXSTART.indication emitted
when a NON_HT PPDU is
received is defined in Clause
17, with mapping of RXVECTOR
parameters as defined in Table
22-2"
It would be helpful to include a As in comment                                Ed
reference to 11.3.11.11 so the
TX of non-HT dup packets can
be understood

I'd rewrite this para for clarity   When the FORMAT parameter                 Ed
                                    is set to HT_MF or HT_GF in
                                    the TXVECTOR of a VHT PHY-
                                    TXSTART.request issued by the
                                    MAC, the parameters in the
                                    TXVECTOR are mapped directly
                                    to the TXVECTOR parameters
                                    of an HT PHY according to
                                    Table 22-2 and a HT PHY-
                                    TXSTART.request is issued to
                                    invoke the operations defined
                                    in Clause 20. Likewise, when an
                                    HT_MF or HT_GF PPDU is
                                    received and an HT PHY-
                                    RXSTART.indication is issued
                                    according to the operations
                                    defined in Clause 20 the
                                    parameters in the RXVECTOR
                                    of the HT PHY-
                                    RXSTART.indication are directly
                                    mapped to RXVECTOR
                                    parameters of a VHT PHY-
                                    RXSTART.indication according
                                    to Table 22-2 and a VHT PHY-
                                    RXSTART.indication is issued to
                                    the MAC.


Atr this point, with current  As in comment                           Minho   PHY
terminology, we are
introducing elements rather
than fields, so I suggest
replacing "VHT-LTF … VHT-LTF"
in the diagram by "VHT-LTFs",
to harmonize with the table.

The caption of Figure 22-1 uses Change double dash to one                     Ed
"--". Same mistakes in all      long dash for the consistency.
figure's and Table's captions
hereafter.
We launch into block diagrams Add "Single User" to figure 22- Minho   PHY
without giving any description 1. Add a new figure "... Multi
of multi-user PPDU format.     User", which is a copy of
                               Figure 22-1, but replicates the
                               per-user fields (sig-b and data)
                               visually stacked to indicate
                               these are replicated per user.

                               At 79.43 add a new para: "All
                               fields up to and including the
                               VHT-LTFs are common to all
                               users. The VHT-SIG-B and
                               Data fields are per user."




The spelling of Table 22-3's   change "Non-HT Short Training          Ed
words is not unified           field" into "Non-HT Short
                               Training Field";
                               change "Non-HT Long Training
                               field" into "Non-HT Long
                               Training Field";
                               change "Non-HT SIGNAL field"
                               into "Non-HT Signal Field";
                               change "VHT Long Training
                               fields" into "VHT Long Training
                               Fields";
                               change "The data field" into
                               "The Data Field".


Non-HT' includes legacy and    Change 'Non-HT Short Training          Ed
VHT. Hence, 'non-HT' is not    field' to ' Legacy Short Training
proper.                        field'
Non-HT' includes legacy and    Change 'Non-HT Short Training          Ed
VHT. Hence, 'non-HT' is not    field' to ' Legacy Long Training
proper.                        field'
Non-HT' includes legacy and    Change 'Non-HT Short Training          Ed
VHT. Hence, 'non-HT' is not    field' to ' Legacy SIGNAL field'
proper.
Much confusion between fields As in comment                      AGREE IN PRINICIPLE.          Ed
and elements (and portions).                                     Resolution text provided in
From (22-3) and fig 22-1, a                                      11/372r2.
field is constructed from one
IFFT (LSTF, LLTF, LSIG, SIGA1,
SIGA2, VHTSTF, VHTLTF1,
VTHLTF2, .., SIGB, Data OFDM
symbol1, 2 ...) whereas an
element can cross multiple
IFFTs (SIGA, VHTLTFs, Data, as
well as LSTF, LLTF ...). But in
P91L44.5, it would be elements
that have timing boundaries
yet these timing boundaries
are ascribed to fields not
elements. And elsewhere
elements are called portions.
Need to resolve. If only
elements/portions can span
multiple IDFTs, then here the
Data field this should be the
"Data element/portion". BUT
"field" is used many times
when, with this terminology,
"element" is meant. And I
don't love "element" as a
name due to confusion with
MAC terminology.(Description) Change to: "The data field
Under Data Entry I'd prefer                                                                    Ed
the PSDU is incorrect           includes the PSDU (PHY Service
                                Data Unit)" to :" The data field
                                includes the PSDU (PLCP
                                Service Data Unit)"

One redundant 'in' is written;   Change 'In non-HT, non-HT                                     Ed
'In non-HT, non-HT duplicate     duplicate formats, and in HT
formats, and in HT formats'      formats' to 'In non-HT, non-HT
                                 duplicate formats, and HT
                                 formats'
Grammer: Allign 'in' in the      Change 'In non-HT, non-HT                                     Ed
sentence; 'In non-HT, non-HT     duplicate formats, and in HT
duplicate formats, and in HT     formats' to 'In non-HT, non-HT
formats'                         duplicate formats, and HT
                                 formats'
delete "in"                      duplicate formats, and HT                                     Ed
                                 formats, these fields are not
                                 present
frame = MPDU (e.g. 7.1.0a or As in comment                          Minho      PHY
7.1.1); so I think PPDU is
appropriate here, not "Frame".
Issue is repeated 12 times in
this clause - search/replace for
instances of "Frame" and
replace by PPDU (or packet?)
(excepting 22.3.12.3 "Group ID
Mgmt frame"). Also, "MU
transmission" sounds like
trying to find a term, when I
suggest "MU PPDU" is the right
term - search/replace also




Insert informative language         As in comment                   Minho      PHY
that an NDP does not contain a
Data element
In transmitter diagrams in          As in comment                   Youhan     PHY
some places instead of FEC
encoder BCC encoder can be
noted.
Confusing as written; should be     As in comment                   Youhan     PHY
more like "each element in a
VHT PPDU can be generated
…"
segment parser is also applied      "for non-contiguous             Youhan     PHY
to the contiguous 160MHz            transmission" needs to be
                                    changed into "for contiguous
                                    160MHz and non-contiguous
                                    80+80MHz transmission"

"Space time block encoder"          As in comment.                             Ed
should be revised to "Space
time block code (STBC)
encoder".

IDFT is used inconsistently in      Recommend IDFT excludes           Youhan   PHY
different places to include pilot   pilot insertion, and so add this
insertion (and duplication?) or     explicitly as a step in this list
not                                 and also in subsequent
                                    diagrams (e.g. blocks are
                                    renamed "pilot insertion,
                                    duplication and IDFT")
CSD is cyclic shift diversity.  Change 'Cyclic shift (CSD)         AGREE. As suggested.   Ed
                                insertion' to 'Cyclic shift
                                diversity (CSD) insertion'
CSD: cyclic shift diversity.    Change 'Cyclic shift (CSD)         Duplicate. See #978.   Ed
                                insertion' to 'Cyclic shift
                                diversity (CSD) insertion'
acronym for CSD is cyclic shift Change 'Cyclic shift (CSD)         Duplicate. See #978.   Ed
diversity not cyclic shift.     insertion' to 'Cyclic shift
                                diversity (CSD) insertion'
The word "CSD" means "cyclic Change the phrase to 'Cyclic          Duplicate. See #978.   Ed
shift diversity"                shift diversity (CSD) insertion'

Diagram for multiple segments Add (or constrain the figure         Youhan                 PHY
for L-SIG and VHT-SIG-A and     labels)
SIG-B is missing
FEC encoder => BCC encoder As in comment                           AGREE. As suggested.   Ed
(for consistency with fig 22-3)

In figs 22-2 - 22-7, and also in As in comment                     Youhan                 PHY
the numbered list preceding,
there are two distinct kinds of
CSD yet are labelled the same -
suggest that these be explicitly
distinguished (i.e. CSD per STS
and CSD per TX antenna)


"Multiply by 1st column of Pu" Replace and introduce               Youhan                 PHY
would probably be better if
given its own distinct name.
Also; by P99, [P]u is the first u
columns of P, so "first column
of [P]u likely needs more
clarification.

Number of FEC encoders is        Add                          Youhan                      PHY
missing an upper bound
In figure 22-2, for clarity and  Change "FEC Encoder" to "BCC Duplicate. See #300.        Ed
consistency, should keep the Encoder"
FEC encoder labeled as BCC
Encoder as in Figure 22-3, since
for the L-SIG and VHT-SIG-A
only the BCC Encoder is
possible.
In figure 22-4, Wouldn't it be       Create two figures, one for BCC                    Ed
more clear to create a figure        and one for LDPC
for both the LDPC and BCC
separately.
"More outputs than inputs" -         Be more specific                   Youhan          PHY
twice as many. For VHT we can
be more specific
In the text, segment merging is      Recommend an explicit              Youhan          PHY
described in the constellation       segment merging block in
mapper section, yet here the         diagram and its own section
segment merging is within the
IDFT block.

fig 22-6 caption shold limit it to   As in comment                                      Ed
data element within an SU
PPDU
of VHT                          of a VHT                         AGREE. As suggested.   Ed
Figure 22-2 is for both L-SIG   Change "transmit process for Youhan                     PHY
and VHT-SIG-A.                  the VHT-SIG-A" to "transmit
                                process for the L-SIG and VHT-
                                SIG-A".
The text "except BCC encoder Change the diagram as               Duplicate. See #300.   Ed
and interleaver" is not         everywhere else it is called BCC
consistent with the diagram 22- encoder.
2. The diagram calls the block
as FEC encoder.

the 20 MHz …                         20 MHz …                    AGREE. As suggested.   Ed
For clarity add SU when              Change:"to 20MHz, 40MHz and AGREE. As suggested.   Ed
discussing Figure 22-4               80MHz VHT format PPDUs." to
                                     "to 20MHz, 40MHz and 80MHz
                                     SU VHT format PPDUs.

The discussion is about VHT-         add text to state the VHT-LTF is                   Ed
STF and VHT-LTF fields. It then      shown in Figure 22-11 and the
references Figure 22-11.             VHT-STF is created as in figure
Figure 22-11 is specifically for     22-11 but without the A
the VHT-LTF only.                    Matrix.

Remove "linear precoding"        As in comment                          Youhan          PHY
sicne it hints that there may be
also non-linear precoding.

More natural to talk about SIG- Move SIGB sentence from L29 AGREE. As suggested.        Ed
B generation after VHT LTF and to L24
before Data element
generation
The text states that this is a DL   Remove linear precoding. Not                          Ed
MU-MIMO VHT PPDUs                   sure precoding even needs to
assuming linear precoding.          be stated.
Why is the limitation of linear
precoding added here? Does
this exclude non-linear
techniques?
Replace L-STF, L-LTF, L-SIG by      As in comment                  Ouch                   Ed
the L-STF field, the L-LTF field,
the L-SIG field, etc; search and
replace through clause 22

Sentence doesn't correctly      Append with "with the              AGREE. As suggested.   Ed
introduce numbered list.        following extensions and
                                highlights"
"Before Sequence generation" "Before sequence                      Minho                  PHY
yet not needed until IDFT; also generation:", or better
erratic capaitalization         "Beforehand:" or "Required
                                parameters:" Repeat for
                                P83L1, P83L25, P84L6, insert
                                equivalent at P83L54, P84L29,
                                P84L63, P85L44. But arguably
                                this bullet adds little value, and
                                these bullets should just be
                                discarded

Rewrite as "Generate the L-STF As in comment                                              Ed
and L-LTF sequences as
described ". Check each
numbered bullet in 22.3.4 to
ensure it is using the
imperative form, and rewrite if
not. Check especially
"constellation mapper" ,
"sequence generation", VHT-
LTF matrix mapping, spatial
mapping, encoder parser,
segment mapping, STBC, etc
etc

changed to Plural form              L-STF and L-LTF sequences are AGREE. As suggested.    Ed
                                    generated
wrong use of underbars at           Change underbars to dashes    AGREE. As suggested.    Ed
"L_STF" and "L_LTF"
Notations in "L_STF" and            Change to "L-STF" and "L-LTF" Duplciate. See #979.    Ed
"L_LTF"
"Inverse Fourier Transform"       As in comment.                                                Ed
should be "Inverse discrete
Fourier Transform" because
IDFT is an abbreviation of
"Inverse Discrete Fourier
Transform". There are same
phrases on e) of 22.3.4.3, e) of
22.3.4.4, b) of 22.3.4.5, f) of
22.3.4.6, j) of 22.3.4.7, m) of
22.3.4.8.1, l) of 22.3.4.8.2, and
b) of 22.3.4.9.4 and they also
should be revised.


Replace "Inverse Fourier        As in comment                 AGREE. As suggested.              Ed
Transform" by "Inverse
Discrete Fourier Transform", 9x
in clause 22
Insert GI and Window:           Insert GI and apply windowing                                   Ed

Rewrite as "Construct the L-SIG As in comment                      AGREE. As suggested.         Ed
as the SIGNAL field defined by
Clause 17 with the following
extensions and highlights"

Inconsistence abbreviation in     Change to "L-SIG" for            AGREE. As suggested.         Ed
"L-SIGNAL"                        consistency
Notation in "L-SIGNAL"            Change to "L-SIG"                Duplicate. See #980.         Ed
For VHT PPDU                      For a VHT PPDU                   AGREE. As suggested.         Ed
The reference section for         Add the number of "22.3.9.1.4"   AGREE. As suggested.         Ed
"LENGTH in the SIGNAL field" is   as the reference section.
missed.

Insert missing cross ref (also    As in comment                    AGREE. Cross references added Ed
P83L24, P84L32, P85L17,                                            (P150L26 which is equation
P132L57, P145L54, P150L26)                                         reference).

Sentence beginning "Add         Rewrite as "Set the Parity and     Minho                        PHY
calculated" tries to dup clause Tail bits as described in …)
17 rather than referring to it

Missing section reference.        Change "section ." to "section   Duplicate. See #78.          Ed
                                  22.3.9.1.4."
The sentence is not complete. Change: "Set the LENGTH in          Duplicate. See #78.    Ed
                              the SIGNAL field according to
                              section ." to "Set the LENGTH
                              in the SIGNAL field according
                              to section 22.3.9.1.4

Missing section reference        Should reference 22.3.9.1.4      Duplicate. See #78.    Ed
Missing reference                add it                           Duplicate. See #78.    Ed
Replace L-SIGNAL by SIGNAL       As in comment                    AGREE. As suggested.   Ed
(there is only L-SIG or SIGNAL).
Ditto P83L5
"described"                      "as described"                   AGREE. As suggested.   Ed
The reference section for "VHT- Add the number of "22.3.2" as     Duplicate. See #319.   Ed
SIG-A1 and VHT-SIG-A2" is        the reference section.
missed.

Missing reference                add it                           Duplicate. See #319.   Ed
The section reference is         Refer to 22.3.9.2.3, probably.   Duplicate. See #319.   Ed
missing.
Missing section reference        Should reference 22.3.2     Duplicate. See #319.        Ed
Why is there a [] around "SU-    Change "[SU-Beamformed]" to Missing BEAMFORMED          Ed
Beamformed"?                     "Beamformed (for SU only)". parameter in TXVECTOR?


No underbar in TXVECTOR          Change "TX_VECTOR" to            AGREE. As suggested.   Ed
                                 "TXVECTOR"

"appropriate reserved bit" - so Delete "appropriate"              AGREE. As suggested.   Ed
nice to know our reserve is not
inappropriate

reserved bit                     reserved bits                    AGREE. As suggested.   Ed
"Partition the SIG-A … first     Not sure that this partitioning, Minho                  PHY
modulated by the SIG-A1          after the bit field definitions,
symbol …" is not correct since   adds much value. Anyway,
the edge bits, once encoded,     change "modulated by" to
span both symbols.               "assigned to" x2

Under what conditions can sig- Delete bullet b)                   Minho                  PHY
a be LDPC encoded? Surely
none, given that it itself
contains signalling about
whether to use ldpc or bcc
coding on a per-user basis.

"rotated by 90deg" - which       "rotated by 90 deg counter-      Minho                  PHY
way?                             clockwise"
For VHT-SIG-A, the cyclic shift   Change to                        Minho                          PHY
to be applied is per-Tx chain     "CSD: Apply CSD for each
cyclic shift defined in Table     transmit chain as described in
22.3.9.2.1                        22.3.9.2.1."
However, the spec incorrectly
states
"CSD: Apply CSD for each
transmit chain as described in
22.3.9.2.2."
over bandwidth                    over the bandwidth             AGREE. As suggested.             Ed
VHT-STF should have Q applied     Add a bullet for spatial       Minho                            PHY
                                  mapping
For VHT-STF, the cyclic shift to Change to                       Minho                            PHY
be applied is per-space time      "CSD: Apply CSD for each space
stream cyclic shift. However, time stream as described in
the spec states:                  22.3.9.2.2."
"CSD: Apply CSD for each
transmit chain as described in
22.3.9.2.2."
Specify that spatial mapping Q add after c): Spatial Mapping: Minho                               PHY
is used, as is specified for VHT- Q matrix is applied as
LTF and VHT-SIGB.                 described in 22.3.11.10.1.

The transmitter provides          The transmitter provides                                        Ed
training for exactly              training (data) signal for the
the space time streams used       exact space time stream used
for transmission of the PSDU      for transmission of PSDU.

Change to "*Generate* *the*       As in comment                    AGREE. As suggested. Also      Ed
VHT-LTF … over *the*                                               updated corresponding
bandwidth                                                          paragraph in Construction of
                                                                   VHT-STF.
This could usefully describe Add such a description                Minho                          PHY
how to determine the number
of symbols of VHT-LTF

P Matrix … and R …               Apply the P matrix … and the R AGREE. As suggested.              Ed
                                 …
For VHT-LTF, the cyclic shift to Change to                      Minho                             PHY
be applied is per-space time     "CSD: Apply CSD for each space
stream cyclic shift. However, time stream as described in
the spec states:                 22.3.9.2.2."
"CSD: Apply CSD for each
transmit chain as described in
22.3.9.2.2."
Q matrix is applied              Apply the Q matrix …           AGREE. As suggested.              Ed
Change the t in transform to        IDFT: compute the Inverse         Duplicate. See #315.             Ed
caps                                Fourier Transform.
IDFT: compute the Inverse
Fourier transform.
No description of SIGB in a MU      Add                               Minho                            PHY
PPDU
"is constructed as follows",        "is constructed per user as       Minho                            PHY
but this takes place per user       follows"

) PSDU_LENGTH                       ) and PSDU_LENGTH                 AGREE. As suggested.             Ed
PSDU_LENGTH is Rxvector.            Change to LENGTH. Fix other       Minho                            PHY
Should use LENGTH here.             similar issues if there is any.
There might be some other
places in the spec that mixes
LENGTH and PSDU_LENGTH.

Missing section reference           Should reference 22.3.9.2.6       Duplicate. See #319.              Ed
the unique …defined                 a unique …defined per             AGREE IN PRINCIPLE. Reword Ed
                                    CH_BANDWIDTH                      as "...a unique fixed bit pattern
                                                                      is defined for each channel
                                                                      bandwidth."

bandwidth                           the bandwidth                  AGREE. As suggested.                Ed
Did not find the definition of      Does it mean first column of P                                     Ed
the term [P]u is else where         for each user? Define P[u] in
                                    the appropriate section.


Multiply with 1st Column of         Is "[P]u" referreing to the                                        Ed
[P]u:Have pilots inserted and       matrix "P" for the user "u"? In
1st column of P matrix              this case, we need to define it
calculation is applied. The total   and point to this location.
number of data and pilot
subcarriers is the same as the
data PSDU.

The reference for the CSD table Change: "described in                 AGREE. As suggested.             Ed
for each transmit chain is        22.3.9.2.2" to "described in
stated as 22.3.9.2.2. This is for 22.3.9.1.1"
VHT STF/LTF/SIG-B/VHT Data,
but not VHT-SIG-A. The
reference for VHT-SIG-A is
22.9.1.1
For VHT-SIG-B, the cyclic shift    Change to                      Minho                    PHY
to be applied is per-space time    "CSD: Apply CSD for each space
stream cyclic shift. However,      time stream as described in
the spec states:                   22.3.9.2.2."
"CSD: Apply CSD for each
transmit chain as described in
22.3.9.2.2."

Data and sig-b may have            Indicate how Q matrix is       Minho                    PHY
different #SS, so how does         applied when #SS of this users
the same Q matrix apply to         data is > 1.
them both.
Sentence is not as clear as it     Rewrite as "Include the CRC      AGREE. As suggested.   Ed
could be                           calculated for VHT-SIG-B in the
                                   Service field as described in xx
                                   then append the PSDU to the
                                   Service field

This is inconsistent with          This needs to be resolve as to Minho                    PHY
equation 22-35. The data is        the correct way. The
multiplied by a Row Vector of P    assumption is that Equation 22-
based on Mu and m (STS).           35.

This is inconsistent with          This needs to be resolve as to Minho                    PHY
equation 22-35. The pilot in       the correct way. The
equation 22-35 is NOT              assumption is that Equation 22-
multiplied by the P or R Matrix.   35.

PHY Padding: PHY pad bits and Provide link to Table 22.5                                   Ed
6NES tail bits are appended to
the PSDU. It is a good idea to
provide a description or a link
while referring to Nes. Nes is
the number of channel
encoders for single user case.
Provide a link to the Table 22.5
INDICATED_CH_BANDWIDTH Change step c) to "c)                      Minho                   PHY
and                               Scrambler: Scramble the PHY
INDICATED_DYN_BANDWIDTH padded data".
are defined only for NON_HT
packets. Since this section is
describing construction of VHT
packets, the initial state of the
scrambler should not be a
function of
INDICATED_CH_BANDWIDTH
or
INDICATED_DYN_BANDWIDTH.


INDICATED_CH_BANDWIDTH As in comment                              Minho                   PHY
and
INDICATED_DYN_BANDWIDTH
are not used in VHT format
packets - make explicit. This is
still needed for selected NON-
HT-DUP packets though.
Basically, make this dependent
according to whether these
parameters ar present in the
TXVECTOR or not. Ditto for
LDPC section

This should reference the BCC      Change " BCC encode as          AGREE. As suggested.   Ed
Encoder specifically which is in   described in 22.3.11.4" to "BCC
Section 22.3.11.4.1. This          encoder as described in
would then be consistent with      22.3.11.4.1."
the referencing on this page
line 53 for the LDPC encoder.
The reference used is for both
encoders.

Segment Parser (if needed):        Link to section 22.3.11.6?     Duplicate. See #319.    Ed
When contiguous 160 MHz or
non-contiguous 80+80 MHz
transmission is used, the
output bits of each stream
parser are divided into two
frequency segments as
described in xxx (Missing link)
Missing section reference.         Change "described in ." to      Duplicate. See #319.         Ed
                                   "described in 22.3.11.6."

This states: "described in .".     change: "described in ." to     Duplicate. See #319.         Ed
Incomplete sentence.               "described in 22.3.11.6"
Missing section reference          Should reference 22.3.11.6      Duplicate. See #319.         Ed
"respectively" but nothing to      Remove                          AGREE. As suggested.         Ed
apply this too. Ditto for LDPC
section
for BPSK … and 256QAM. Ditto      "of BPSK … or 256QAM"; or        AGREE. Reads: "Mat to BPSDK, Ed
for LDPC section                  better, "Map to BPSK, …or        … or 256-QAM coonstellation
                                  256QAM constellation points      points…"
                                  …"
For DATA, the cyclic shift to be Change to                         Minho                        PHY
applied is per space time         "CSD: Apply CSD for each space
stream cyclic shift. However, time stream as described in
the spec states:                  22.3.9.2.2."
"CSD: Apply CSD for each
transmit chain as described in
22.3.9.2.2."
LDPC sequence omits               Insert                           Minho                        PHY
reference to SIG-B inserted in
service field
INDICATED_CH_BANDWIDTH Change step c) to "c)                       Minho                        PHY
and                               Scrambler: Scramble the PHY
INDICATED_DYN_BANDWIDTH padded data".
are defined only for NON_HT
packets. Since this section is
describing construction of VHT
packets, the initial state of the
scrambler should not be a
function of
INDICATED_CH_BANDWIDTH
or
INDICATED_DYN_BANDWIDTH.


For DATA, the cyclic shift to be   Change to                      Minho                         PHY
applied is per space time          "CSD: Apply CSD for each space
stream cyclic shift. However,      time stream as described in
the spec states:                   22.3.9.2.2."
"CSD: Apply CSD for each
transmit chain as described in
22.3.9.2.2."
From here to page 87, the font     needs re-adjusting the font-    AGREE. Formattting corrected. Ed
size is different from other       size
parts
Grammatical error.             Change "combine" into           AGREE IN PRINCIPLE. See #339 Ed
                               "combines".                     fix.
"and combine"                  all users' data is combined     AGREE. As suggested.            Ed
"It is the same to the process "The construction of the Data   AGREE IN PRINCIPLE. Reword Ed
described in 22.3.4.8.1 before field/element with BCC          as "The construction of the
the spatial mapping block."    encoding is the same process    Data field with BCC encoding is
Ditto P86L35                   as described in 22.3.4.8.1      the same process described in
                               before the spatial mapping      22.3.4.8.1 (Using BCC) before
                               block, yet repeated for each    the spatial mapping block,
                               user that uses BCC encoding."   repeated for each user that
                                                               uses BCC encoding." And as:
                                                               "The construction of the Data
                                                               field with LDPC encoding is the
                                                               same process described in
                                                               22.3.4.8.2 (Using LDPC) before
                                                               the spatial mapping block,
                                                               repeated for each user that
                                                               uses LDPC encoding."




"same to the process" -         "same as the process" (twice) AGREE IN PRINCIPLE. See         Ed
grammar                                                       rewording in #340.
Section Label has additional    Change: "22.3.5 Modulation    DISAGREE. No extra space        Ed
space.                          and coding sc heme (MCS)" to detected.
                                "22.3.5 Modulation and coding
                                scheme (MCS)"

80+80 MHz missing.              Change "160 MHz." to           Brian.                         PHY
                                "160/80+80 MHz".

"one through eight" yet         1 to 8; 4x in this para. Replace AGREE. As suggested.         Ed
previously 1 to 8               "through" by "to", 8x in this
                                para and the next.

"one through eight" - this is an "one to eight"                AGREE. As suggested.           Ed
ugly americanism

Ditto line 13
The information in the last     Delete the last paragraph in                              Ed
paragraph of Sec 22.3.5 is a    Sec 22.3.5
duplicate of the information
provided in section 22.1.1
"Transmit and receive support
for MCS 0 through 7 in single
stream 20 MHz, 40 MHz and 80
MHz
PPDUs with 800 ns GI is
mandatory in both APs and
non-AP STAs. All other modes
are optional,
specifically including transmit
and receive support for 400 ns
GI, operation in 160 MHz
channel
width, support of MCSs 8 and
9, and support for more than 1
spatial stream."




Table 22-4—Timing-related                                      AGREE IN PRINCIPLE. Putting PHY
constants                                                      two columns as suggested in
It will be a good idea if we can                               this comments makes this
put two columns (one for the                                   table more readable. 11/386r0.
parameter and one for the
description)
the formula of TL-LTF is wrong Modify "TGIS" to "TGI2"         Duplicate. See #342.       PHY

TGIS                            TGI2                           AGREE IN PRINCIPLE. Current PHY
                                                               equation about TL-LTF in D0.1
                                                               is wrong. So, TGIS in that
                                                               equation shall change into TGI2
                                                               to make it correct. 11/386r0.

This equation for T_L_LTF is   this equation needs to be       Duplicate. See #342.       PHY
wrong                          changed into "2x T_DFT +
                               T_GI2"
TL-LTF should be a function of change to "8 µs = 2 x TDFT +    Duplicate. See #342.       PHY
TGI2 rather than TGIS          TGI2"
TLSIG = 4 us, yet (22-15) uses      Suggest writing 4 us = Tsym for AGREE IN PRINCIPLE. There is a PHY
TSYM not TLSIG                      TLSIG, TVHT-LTF; also,          little ambiguity about what
                                    arguably, TVHT-STF = 5*TDFT/4 TSYM really means in the
                                                                    current text (D0.1). In addition
                                                                    to that, (22-71) and (22-76),
                                                                    which are equations for the
                                                                    VHT data transmission and the
                                                                    non-HT duplicate data
                                                                    transmission, use TSYM in
                                                                    these, regardless of whether
                                                                    short GI is used or not, even
                                                                    though TSYM is the symbol
                                                                    duration by D0.1 only when
                                                                    long GI is used. So, I
                                                                    additionally define TSYML for
                                                                    the symbol duration when long
                                                                    GI is used, and set TSYM to be
                                                                    one between TSYML and
                                                                    TSYMS depending on which GI
                                                                    is used. 11/386r0.


The Note is difficult to read. It   Change: "NOTE 1 - Nst =Nsd +   AGREE IN PRINCIPLE. Note       Ed
looks like 1-Nst. Possibly          Nsp" to "NOTE 1: Nst=Nsd +     modified to conform to
removing the "-" and put a ":"      Nsp"                           standard style.
would clarify
N_CBPS, N_CBPSS, N_DBPS,            As in comment.                 AGREE. Italicised.             Ed
N_BPSC, N_BPSCS, N_RX, and
N_u should be expressed as
italic font.

To correctly define the BCC         As in comment                  AGREE IN PRINCIPLE.             PHY
interleaver with 160 MHz,                                          However, note that contiguous
need to introduce a NCBPSSS                                        160 MHz has only one
(per subcarrier per spatial                                        frequency segment, while it is
stream per segment) in this                                        still interleaved by two 80 MHz
table and update (22-56)-(22-                                      interleavers. Thus, number of
63) accordingly                                                    coded bits per symbol per
                                                                   spatial stream ‘per BCC
                                                                   interleaver block’ would be a
                                                                   more appropriate resolution.
                                                                   Resolution text in 11/362r0.
Inconsistent italicisation - some Harmonize                           Duplicate. See #80.            Ed
terms are ital, some not

which signal                        which the signal                  AGREE. As suggested.           Ed
of 20                               of the 20. Ditto "of a 40", "of   AGREE IN PRINCIPLE. "a 20", "a Ed
                                    an 80" "of a non-cont" in the     40", "an 80", "a 160", "a non-
                                    next few paras                    contig"
Signal is                           The signal is. 4x acros this &    AGREE. As suggested.           Ed
                                    next few paras
To refer to (22-2), should be       As in comment                     Youhan and Brian to talk and   PHY
r_{PPDU}. From fig 22-7,                                              reolve
shouldn't sum over segments -
delete summation, and keep
i_{seg} as a superscript of r_RF.
Also, r_PPDU depends on iTx,
so add iTx as a supersript to
r_RF and r_{PPDU}


"consists of" is not needed in      change to                         AGREE. As suggested.           Ed
the sentence                        "...represents the number of
represents the number of            frequency segments in the
frequency segments the              transmit signal."
transmit signal consists of
Nseg is defined in Table 22-4       Add reference                     AGREE. Reference added.        PHY

In the NOTE it discusses a                                                                           Ed
reference 3.1. Not sure what
document this is referring.
Should this possible point to
22.3.3?
If this was analog modulation, modilating => up-converting            AGREE. As suggested.           PHY
"modulating" would be fine,
but elsewhere we use
modulation for constellation
mapping, and up conversion
for this step

Last LTF is labelled VHT-LTFn       n => N_{VHTLTF}                   AGREE IN PRINCIPLE. Figure    Ed
but is really N_VHTLTF so we                                          updated to remove all VHT-LTF
can avoid n entirely                                                  numbering (since N_VHTLTF is
                                                                      above VHT-LTF group)
Nseg=2 only in one case: 80+80 Revise Nseg description as:     Hongyuan                          PHY
MHz Noncontiguous frequency Nseg=2 for 80+80 MHz, and
segments. It is not clear what Nseg=1 for all the other cases.
"noncontiguous transmission"
mean.

In Equation (22-2), N_VHT-LTF Fix                                 AGREE. As suggested.           Ed
should be N_VHTLTF (as
defined elsewhere)
Equation is squeezed          Unsqueezed                          AGREE. Equation unsqueezed     Ed
                                                                  with conversion to Frame
                                                                  Maker equation editor.

T_{VHT-LTFs} => T_{VHT-LTF} - As in comment                       AGREE. As suggested. Ed:        PHY
in (22-2) and (22-3)                                              assuming reference to (22-3) is
                                                                  actually to T_VHT-LTFs in
                                                                  'where' clause for (22-2).
Add 1 <= iSeg < Nseg, 1 <= iTx As in comment                      AGREE IN PRINCIPLE. Ranges      PHY
<= nTX (some indices start at 0,                                  added to 'where' clause. Ed:
some at 1, so clarity is always                                   Assuming N_Seg and not
valued)                                                           N_seg.
"per OFDM symbol" but are L- Delete "per OFDM symbol"             AGREE. Resolution text in       PHY
STF/L-LTF really a single OFDM                                    11/372r2.
symbol since Tsym etc is ~4us?

discrete FT                        inverse discrete FT             AGREE. As suggested.          PHY
"Each baseband waveform" is        If terminology converges to     AGREE. Resolution text in     PHY
not a well defined term, in part   element/field then change to 11/372r2.
because the element/field          field. If terminology converges
terminology is not yet properly    to field/field-component then
resolved.                          change to field-component.


The equation 22.3 is stated as Add per space time stream          Youhan                         PHY
the general representation       cyclic shift in the equation
which holds good for all fields.
However, the per space time
stream cyclic shift is missing.


"of MU transmissions" seems Start sentence with "For MU           AGREE IN PRINCIPLE. Begin      Ed
to bind to to VHT-SIG-A only, PPDUs" instead                      sentence "For MU
but should apply to all previous                                  transmissions…"
nouns.
The left parenthesis for       As in comment.                   AGREE. Correctedwith global Ed
"Equation 22-3)" is missed and                                  rework on equations and their
should be added.                                                references.




equation 22-3)                  (22-3). Ditto P96L65            Duplicate. See #81.         Ed
Missing bracket.                Change "Equation 22-3)." to     Duplicate. See #81.         Ed
                                "Equation (22-3)."

"..shall also use Nu=1.." No   As in comment                DISAGREE. Use of “shall” in     PHY
need to use "shall" here. Same                              these two sentences seems
for the next sentence.                                      approproiate since this is only
                                                            normative text indicating
                                                            number of users.
MU transmissions should have Change "1 <= Nu <= 4" to "2 <= AGREE                           PHY
at least 2 users.            Nu <= 4".

"1 <= Nu" is not a MU           2 <= Nu                         Duplicate. See #601.        Ed
transmission
represents                      represent                       AGREE. As suggested.        Ed
X_k is missing the user index   Add u subscript                 AGREE. As suggested.        Ed
(i.e. should be X_k_u)

"whose" binds to freq segment Change "Whose …" to and           AGREE IN PRINCIPLE. Changed Ed
                              values of NSR are listed …"       to "and has values listed in
                                                                Table 22-4"
Delta_F is not defined in       Add the following sentence at AGREE                          PHY
Equation (22-3).                the end of the paragraph
                                ending on line 56: "\Delta_F is
                                the subcarrier spacing (312.5
                                KHz)."

X with -N                       X within -N                     AGREE. As suggested.        Ed
X_k is missing the user index   Add u subscript                 AGREE. As suggested.        Ed
(i.e. should be X_k_u)

We usually refer to as non-     Change "non-contiguous 160 AGREE. As suggested.             Ed
contiguous 80+80 MHz.           MHz PPDU" to "non-
                                contiguous 80+80 MHz PPDU"

Using eqn as an adjective - not Change to The scale factor of   AGREE. As suggested.        Ed
ideally clear                   sqrt() in (22-3)
NON-HT-DUP is not a defined       Define / rename to Non-HT-                                    Ed
field name                        Data (and define); or change
                                  Table title to N^{Tone}_{X} and
                                  change "Field" in label table
                                  columns to "X"

Section is missing language for   Add                               AGREE. Resolution text in   PHY
80 in 80+80                                                         11/367r1.
This section might be             As in comment                                                 Ed
expressed more simply via a
table
"When transmitting a 20 MHz       Reword so that it relates to                                  Ed
PPDU in a 40 MHz channel, the     STA behaviour (i.e. transmitted
mathematical description of       waveform shall be) or turn into
transmission shall                a declarative "is" statement.
follow that of a 20 MHz
channel"

Normative "shall" statements
relate to what a STA shall do,
not what the authors of the
standard shall write.


(22-3)                            (22-1), 6x in this clause         AGREE. As suggested.        Ed
Remove equation from              As in comment                     Duplicate. See #368.        Ed
"equation (xx)" -
search/replace
This references Equation 22-3     Change "in Equation (22-3)" to Duplicate. See #368.           Ed
for to replace the variable fc    "in Equation (22-1)"
per segment. The equation 22-
3 does not include this
variable. This should point to
equation 22-1.

This references Equation 22-3 Change "in Equation (22-3)" to Duplicate. See #368.               Ed
for to replace the variable fc "in Equation (22-1)"
per segment. The equation 22-
3 does not include this
variable. This should point to
equation 22-1.
When operating in a 80+80        As in comment               DISAGREE. The TXVECTOR       PHY
BSS, transmitting a 20/40/80                                 defines the bandwidth of the
MHz packet, somewhere need                                   signal, and from Table 22-4
a statement that r^{iSeg}(t) = 0                             only (V)HT_CBW80+80 involves
for the iSeg that does not                                   2 segments, which by
include the primary                                          definition is not a 20/40/80
                                                             MHz packet.
"an 160" needs to be changed "a 160" (there are lots of same AGREE. As suggested.         Ed
into "a 160"                 typos in the document)

This references Equation 22-3 Change "in Equation (22-3)" to Duplicate. See #368.        Ed
for to replace the variable fc "in Equation (22-1)"
per segment. The equation 22-
3 does not include this
variable. This should point to
equation 22-1.

Missing "MHz".                 Change "80+80 channel" to     AGREE. As suggested.        Ed
                               "80+80 MHz channel".

This references Equation 22-3 Change "in Equation (22-3)" to Duplicate. See #368.        Ed
for to replace the variable fc "in Equation (22-1)"
per segment. The equation 22-
3 does not include this
variable. This should point to
equation 22-1.

This references Equation 22-3 Change "in Equation (22-3)" to Duplicate. See #368.        Ed
for to replace the variable fc "in Equation (22-1)"
per segment. The equation 22-
3 does not include this
variable. This should point to
equation 22-1.

This references Equation 22-3 Change "in Equation (22-3)" to Duplicate. See #368.        Ed
for to replace the variable fc "in Equation (22-1)"
per segment. The equation 22-
3 does not include this
variable. This should point to
equation 22-1.

Grammer is wrong: 'The L-STF Change 'The L-STF for 20 MHz AGREE. As suggested.           Ed
for 20 MHz and 40 Mhz are ~' and 40 Mhz are ~' to 'The L-STF
should be 'The L-STF for 20MHz for 20MHz and 40MHz is~'
and 40MHz is~'
Grammer: 'The L-STF for 20         Change 'The L-STF for 20 MHz Duplciate. See #981.               Ed
MHz and 40 Mhz are ~' should       and 40 Mhz are ~' to 'The L-STF
be 'The L-STF for 20MHz and        for 20MHz and 40MHz is~'
40MHz is~'
define                             defined. Ditto P96L48             AGREE. As suggested.          Ed
"defined" instead of "define"      As in comment                     Duplicate. See #373.          Ed

Grammar issue                      Modify "is define" to "is         Duplicate. See #373.          Ed
                                   defined"
These equations depend on          Insert BW on LHS, probably        Brian                         PHY
BW via Gamma_{k,BW}, but           10+ times.
the LHS does not list BW as a
parameter (but say P132L5
does have it listed)
Grammer is wrong: 'the L-LTF       Change 'the L-LTF pattern in                                    Ed
pattern in the VHT preamble        the VHT preamble are~' to 'the
are~' should be 'the L-LTF         L-LTF pattern in the VHT
pattern in the VHT preamble is     preamble is ~'
~'
Grammer: 'the L-LTF pattern' is    Change 'are' to 'is'              AGREE. As suggested. Also     Ed
singular. So, 'the L-Ltf pattern                                     changed the wording to group
in the VHT preamble is ~'                                            equation references with
                                                                     section reference: "… by
                                                                     Equations (20-11) and (20-12)
                                                                     in 20.3.9.3.4, respectively."

define -> defined                                                    AGREE. As suggested.          Ed
The equation for L-58,58 is     Change equation reference            AGREE. As suggested (using    Ed
referenced as 20-9, but 20-9 is from 20-9 to 20-12.                  updated numbering).
the equation for S-58,58.

There is a typo in: L-58,58 is     Change to L-58,58 is defined in   Duplicate. See #1338.         Ed
define in equation (20-9)          equation (20-9)
Grammar issue                      Modify "is define" to "is         Duplicate. See #1171.         Ed
                                   defined"
Where                              where                             AGREE. As suggested.          Ed
"for the 80MHz" is awkward         the 80 MHz L-LTF pattern.         AGREE. As suggested.          Ed
                                   Ditto P107L41
Missing bracket.                   Change "Equation 22-11)." to      AGREE. Updated globaly with   Ed
                                   "Equation (22-11)."               Equation reference fixes.
Instead of "..does not              As in comment                 AGREE IN PRINCIPLE. Wording PHY
include.." it is better to say " ..                               “include” may hint that
does not show"                                                    rotations are not needed.
                                                                  Wording “show” indicates
                                                                  more clearly that rotations are
                                                                  present. Resolution in
                                                                  11/359r1.
T_{VHT-LTF}                       T_{L-LTF}                       Brian                           PHY
W_T_VHT-LTF should be                                             AGREE. As suggested.            Ed
W_T_L-LTF
rate => data rate (vs code rate   As in comment                   AGREE. As suggested.           Ed
etc)
Figure 22-9 is not clear          Replace the current figure to   AGREE. Figure replaced.        Ed
because background color is       the clear one.
black.
Figure 22-9 appears 'all black'   Please improve the figure       Duplicate. See #82.            Ed
in print and looks very dark.

Figure is all black              Replace                          Duplicate. See #82.            Ed
Figure 22-9 is completely black. Replace figure.                  Duplicate. See #82.            Ed


Figure 22-9 is shown in Black.    Change the figure.              Duplicate. See #82.            Ed

Methinks some minor               Tweak away. I have visio files Duplicate. See #82.             Ed
tweaking is in order here.        from .11n if you're interested.

Figure 22-9 is in Black.          Change the figure.              Duplicate. See #82.            Ed
Figure 22-9 is too dark.          Fix the figure.                 Duplicate. See #82.            Ed
Figure 22-9 seems too dark to     Its gradation needs to be       Duplicate. See #82.            Ed
see in detail.                    adjusted
The figure above "Figure 22-9--   Add the figure for L-SIG        Duplicate. See #82.            Ed
L-SIG structure" is blackened     structure
out.
for 20 MHz                        for a 20 MHz                    DISAGREE. "spacing" --> non-   Ed
                                                                  unitary.
I struggle to endorse "channel Rewrite to "for the 20 MHz         Brian                          PHY
spacing" even this far         spacing column of Table 17-5"
There is a little ambiguity how     Add the following sentence            AGREE IN PRINCIPLE. Add how PHY
to express the calculated           after Equation (22-14), that is,      to express the calculated
Length value in the Length          "For fields, B5-B16, consisting       length value in the lenth field.
field.                              of 12 bits, the LSB of the field is   11/387r3. (Editor: The only
                                    mapped to the lowest bit              significant change here seems
                                    among the corresponding               to be defining B5 as the
                                    Length value in binary                holding the LSB. Editorial
                                    expression, which is calculated       changes regarding bit range for
                                    as described in Equation (22-         fields ignored since these are
                                    14)"                                  expressed in the figure
                                                                          (unnecessary duplication
                                                                          should be avoided). Added
                                                                          suggested text for Tail field.)


SIGB also has a Length field -      Rename one of these fields -                                         Ed
ambiguous; also 11a called this     e.g. VHT-SIG-B Length or LSIG
LENGTH                              LENGTH
reserved, parity                    Reserved, Parity                      AGREE IN PRINCIPLE.            Ed
                                                                          Capitalized field names and
                                                                          used 'field' instead of bit.

Wrong expression in "k=0..47" Change to "k=0,…,47".                       AGREE. As suggested.           Ed

missing comma in expression         Change to "k=0,…,47".                 Duplciate. See #984.           Ed
in "k=0..47"
The figure is blacked out           Correct formatting                    Duplicate. See #82.            Ed
figure 22-9 is not shown well       check and revise                      Duplicate. See #82.            Ed

T_SYM => T_LSIG                     As in comment                         Brian                          PHY
Delta_F and TGI not referenced      Insert ref to Table 22-4                                             Ed
below, in this equation and         forN_{TX}, Delta_F and TGI
elsewhere                           here and subsequently as
                                    required
It doesn't change the               Change                                Brian (Minho thinks might be   PHY
waveform, but a much more                                                 wrong)
natural Kshift mapping is (2i-(N-
1))*32 (preserves the sign of i)

There is no definition of the It is a good idea to provide                                               Ed
parameter d_k                 definition of d_k as well in the
                              adjacent table.
M'(k) should have an equation Insert                                                                     Ed
number since it is referenced
elsewhere
The reference of 22-7 is         Change: " with a value given in      Ed
referring to an equation. This   22-7." to "with a value give in
should refer to a table          Table 22-7"
22-7                             Table 22-7                           Ed
The word 'Table' is missing.     Change "given in 22-7." to           Ed
                                 "given in Table 22-7."

VHT preamble                     VHT portion of the preamble          Ed

Grammer is wrong: 'the VHT       The sentence should be 'the          Ed
preamble consists of the VHT-    VHT preamble consists of VHT-
STF, the VHT-LTFs, VHT-SIG-A     STF, VHT-LTFs, VHT-SIG-A and
and the VHT-SIG-B' has un-       the VHT-SIG-B'
necessary 'the'.
Grammer: Allign 'the' in the     Correct the sentence as 'the         Ed
sentence; 'the VHT preamble      VHT preamble consists of VHT-
consists of the VHT-STF, the     STF, VHT-LTFs, VHT-SIG-A and
VHT-LTFs, VHT-SIG-A and the      the VHT-SIG-B'
VHT-SIG-B'.

Many indices start at 0, many    Add "The index for the top left      Ed
at 1                             element of Q is (1,1).
Add VHT-DATA too to the list     Change                               Ed
to fields using per-space time   "The cyclic shift values defined
stream cyclic shift              in this subclause apply to the
                                 VHT-STF, VHT-LTFs, and VHT-
                                 SIG-B of the VHT format
                                 preamble."

                                 to
                                 "The cyclic shift values defined
                                 in this subclause apply to the
                                 VHT-STF, VHT-LTFs, VHT-SIG-B,
                                 and VHT-DATA of the VHT
                                 format preamble.

cyclic shift is                  cyclic shifting is / cyclic shifts   Ed
                                 are
shift are                        shifts are                           Ed
continuously                     sequentially (since this is a        Ed
                                 discrete thing)
22-5                             Table 22-5 (2x)                      Ed
The word 'Table' is missing.     Change "in 22-5" to "in Table        Ed
                                 22-5"
The word 'Table' is missing.       Change "in 22-5" to "in Table                             Ed
                                   22-5"

Group ID field (which has 6 bits   Add 1 MU/SU mode bit in VHT- Edward has presentation      PHY
in total) has not been used in     SIG-A1 to indicate MU/SU
the SU scenario, which is a        mode. Then in SU scenario,
waste of precious VHT-SIG A        this 6-bit Group ID field can be
bits.                              released. As an example, the
                                   saved Group ID bits for SU
                                   mode can be used together
                                   with the last 9 bits in Nsts field
                                   to indicate the full AID.

the reference is an Equation    Change" is defined in 22-5 and"                              Ed
reference. All table references to " is defined in Table 22-5
in the document have been       and"
using the word table first to
distinguish from and equation.
This needs to be added here as
well.

Correspondence to 20-5 seems As in comment                      References have been fixed   Ed
incorrect
the reference is an Equation    Change" is defined in 22-5." to                              Ed
reference. All table references " is defined in Table 22-5."
in the document have been
using the word table first to
distinguish from and equation.
This needs to be added here as
well.

This table looks a bit awkward, Possibly add a "symbol"                                      Ed
particularly with a straddle row column and place VHT-SIG-A1
just under the heading.          and A2 in this column. This
                                 could straddle the relevant
                                 rows as a means of visually
                                 grouping them.
It is not necessary to mention Write: "Reserved. Set to 1."        Vinko. 11/359r1.          PHY
"possible expansion of BW"
The transmitter of the group      Please reserve the group IDs     Jarkko (11/314r1)   PHY
addressed frames and the          62 and 63 for SU-MIMO
group address should be           transmissions. Please change
detetable from the VHT-SIG A      the text in the description
field. By getting an indication   field: " A value of 62 and 63
of the group addressed frames     indicates that transmission is a
transmitter and the group         single user transmission. The
address, the receiving device     B9 is set to 0 to indicate that
may use the same traffic          the transmission is destined to
filtering rule for individually   individual address. The B9 is
and group addressed frames.       set to 1 to indicate that the
The group addressed frames        transmission is destined to
are typically the only frames     group address ."
which are received during the
stand-by power save. The
group addressed frames may
be transmitted by network
maintenance protocols, like
ARP, or they may be destined
to other associated STA in the
BSS. When the device is
capable to avoid the reception
of the group addressed that it
is not interested, the power
consumption of the device is
reduced.


The explanation in Description    Please correct the language of Jarkko (11/314r1)     PHY
is very unclear. What is a        the description. State more
transmission that needs to        clearly what transmissions are
bypass a group, why not simply    transmitted when the group ID
state that it is a SU-MIMO        is set to 63. Reserve group ID
transmission to group address.    62 from SU-MIMO
Also a transmission where         transmissions to group address
group membership has not          and value 63 for SU-MIMO
been established is very          transmissions to individual
unclear statement. The            address.
transmission is SU-MIMO
transmission to individual
address.
Explaning issues through MU-
MIMO group is confusing,
The explanation in Description      Please correct the language of Jarkko (11/314r1)                  PHY
is very unclear. The Group ID       the description. State more
should define is SU-MIMO or         clearly what transmissions are
MU-MIMO transmission done.          transmitted when the group ID
                                    is set to 63. Reserve group ID
                                    62 from SU-MIMO
                                    transmissions to group address
                                    and value 63 for SU-MIMO
                                    transmissions to individual
                                    address.

The Partial AID contains good       Allow means to detect the         See #665?                       PHY
support for indicating the          group address to which the
recipient of the individually       frame is trnsmitted. The Group
addressed frame, but the            ID value 62 should be reserved
Partial AID fails to indicate the   for group addressed frames
group address to which the          transmission and when the
frame is transmitted.               Group ID is set to 62, the Nsts
The Nsts field indicating the       should contain both the BSSID
group address allow the             of the network (first 4 bits) and
receiving terminal to use the       the group address of the
same filtering logic for group      transmitted frame (last 5 bits).
addressed and individually
addressed frames.


"A value of 63 (all ones)           capture motion text: "In a SU       AGREE. Modified text to match PHY
indicates:                          VHT PPDU, if the PPDU carries       motion. 11/344r1. (Editor: This
A single user transmission          MPDUs addressed to an AP            should be revisited. This field is
A transmission where the            STA, the GROUP ID field is set      set directly from the
group membership                    to all zeros, otherwise it is set   TXVECTOR GROUP_ID
has not yet been established        to all ones"                        parameter and the description
A transmission that needs to                                            should reflect this. There are
bypass a group                                                          already ruls in the MAC section
(e.g. broadcast);" Motion #8                                            for selecting the appropriate
(PHY 11/0039) in January                                                Group ID value, or at least
Agenda DCN 11/0011r5                                                    there should be.)
defines two values for the GID
in STA-to-AP and AP-to-STA
PPDUs; motion is not captured
in this text

Grammar issue                       change "Set to 0 for 0 space                                      Ed
                                    time streams" into "Set 0 for 0
                                    space time stream".
Insert Values 5-7 are reserved As in comment                     Brian                            PHY

There is no description about   Change the text after line 36     See #1341                       PHY
the setting of B10-B21 for      into the following:
BC/MC scheme.                   For SU/BC/MC:
                                B10-B12
                                   Set to 0 for 1 space time
                                stream
                                   Set to 1 for 2 space time
                                streams
                                   Set to 2 for 3 space time
                                streams
                                   Set to 3 for 4 space time
                                streams
                                   Set to 4 for 5 space time
                                streams
                                   Set to 5 for 6 space time
                                streams
                                   Set to 6 for 7 space time
                                streams
                                   Set to 7 for 8 space time
                                streams
                                B13-B21
                                   Partial AID: 9 LSB bits of AID
                                for SU and set to all zeros
                                otherwise.
Partial AID is more complicated Refer to SAP parameter            See #1341                       PHY
than that, and anyway comes
from TXVECTOR

Patial AID field is incorrectly reference 9.7e Partial AID in    See #1341                        PHY
described; correct description VHT PPDUs for the content of
of content is in section 9.7e   partial AID
Partial AID in VHT PPDUs

partial AID description         Change description to "B13-         Hongyuan, Jarkko (11/314r1)   PHY
incorrect                       B21: Partial AID, defintion refer
                                to clause 9.7e"
The field name is "No TXOP      Please consider changing the Allan.                               PHY
PS", but a value of 1 means     polarity of the bit (i.e. 1 if TXOP
TXOP PS is allowed. This        PS is NOT permitted.)
seems a little confusing.
The bit No TXOP PS set to 1     Change: "No TXOP PS" to                                           Ed
logically suggests that TXOP PS "TXOP PS"
is not in use. "No" could be
removed from the name
How often the value of the "No Please add the details how    Allan.            PHY
TXOP PS" field may be          often the value of NO TXOP PS
changed? Once every PPDU       field may be changed.
transmission, once every TXOP
or once every beacon interval?

The Partial AID is not the 9 last Correct the Partial AID field.   See #1341   PHY
bits of the AID. It contains also
"specially XORed" and shifted
BSSID bits.

B22 "No TXOP PS" is set to 1 if     Motion 36 in January Agenda Allan.         PHY
TXOP PS permitted                  DCN 11/0011r4, which refers
Set to 0 otherwise;" bit setting   to slide #4 of 11/0091r0,
description is opposite of what    defines the B22=1 if no TXOP
name suggest. Description          PS is allowed, and B22=0 if
need be consistent with            TXOP PDS is allowed; Keep the
motion;                            field name and change the
                                   description to the "set to 1 if
                                   TXOP PS is not permitted; Set
                                   to 1 if TXOP PS is permitted";
                                   this is consistent with the
                                   definition of the parameter
                                   TXOP_PS_NOT_ALLOWED
                                   (11.2.1.4a); Note that it is also
                                   preferred from a PHY
                                   perspective: reserved bits in
                                   PHY preamble are set to 1; an
                                   AP which des not support the
                                   TXOP PS mode can leave the
                                   bit set to 1.




The field name "No TXOP PS" change the description to "Set Allan.              PHY
does not match the                to 1 if TXOP PS not permitted;
descriptions well; when it is set Set to 0 otherwise"
to 1 (which usually means
TRUE), the description says it
indicates TXOP PS permitted.


Incorrect number of reserved       change to 1 bit in the 3rd                  Ed
bits                               column.
In Table 22-9,the Bit Allocation   Modify "2" to "1"and                        Ed
for B23 is wrong                   modify"all ones" to "Reserved
                                   and set to 1 "
The sentence "Set to 1 if all        Change the sentence into "Set Edward.                        PHY
streams have space time block        to 1 if all streams have space
coding and set to 0 otherwise"       time block coding and set to 0
is not clear. Based on the           if none of streams has space
discription, if the STBC field set   time block coding".
to 0, it is possible that parts of
the spatial streams are STBC
encoded.

Exact definition of Group ID         Explicitly describe the meaning AGREE. See #972. 11/344r1.   PHY
field is required. The value of      of the value 0~62. Clarfy the
0~62 should indicate Group ID        senetence for the value 63
of individual groups. Does           adding "or".
Group ID 63 indicate one of the
following scenarios?


Originally, the "NO TXOP PS"         In the description of "NO TXOP Allan.                        PHY
subfield in the preamble of          PS" subfield, for the downlink
VHT PPDU does not have               VHT PPDU, it is set to 1 if non-
definition in the uplink             AP STAs are not allowed to
direction. If the VHT TXOP PS        enter Doze state during TXOP
subfield in VHT Capability Info      and set to 0 otherwise. As for
field is approved to represent       uplink VHT PPDU, the "NO
whether or not a STA supports        TXOP PS" subfield is set to 1 if
the TXOP PS mode as the              the STA is not in TXOP PS mode
comment above, it is                 and set to 0 otherwise. If the
suggested that "NO TXOP PS"          TXOP PS mode is not
can be used to indicate if the       supported, this subfield is
non-AP VHT STA is in VHT TXOP        ignored. As an alternative, the
PS mode. It can thus prevent         subfield can be renamed to
from executing the association       "TXOP PS" and its values and
process to change the power          definitions can be set
management mode.                     accordingly.




This is a new Bit. This could                                       Allan.                        PHY
use more definition. It is not
clear what this bit does and
there is no other description in
the PHY portion of the
document. Could this be
signaled in a packet instead of
using the SIG field.
The sentences "No TXOP PS:        These sentences should be       Allan.                        PHY
Set to 1 if TXOP PS permitted.    modified into "Set to 1 if TXOP
Set to 0 otherwise." are          PS not permitted. Set to 0
inconsistent with the             otherwise."
corresponding sentences in 11-
09-0992-21-00ac-proposed-
specification-framework-for-
tgac, which are "No TXOP PS:
Set to 1 to indicate that TXOP
PS is not allowed. Set to 0 to
indicate that TXOP PS is
allowed."


This field is named as "No TxOP   Change description to "Set to 0 Allan.                        PHY
PS field", so default should be   if TXOP PS permitted, Set to 1
1                                 otherwise"
The usage of short GI for DL      Add the sentence "In a MU-      Yusuke                        PHY
MU-MIMO transmission should       MIMO PPDU, short GI may be
be clear.                         used only when all of the STAs
                                  that receive the MU-MIMO
                                  frame support short GI mode."
                                  to the Description column of
                                  short GI in Table 22-9.

B3 is undefined for SU            Reserved 0 or reserved 1?       Youhan. Definition intended to PHY
                                                                  cover SU.
Given that some users have      Harmonize "user" language         Minho                          PHY
0STS, u starts from 0 but Userv with TXVECTOR language
starts from 1, precision and
consistency is important. Thus
"User 1/2/3/4" should relate to
the TXVECTOR, and is currently
called (oddly) USER_NUM not
"user"

User index in N_STS in VHT-SIG- Change "user 1" to "user 0" on Minho                            PHY
A1 is u=0,1,2,3. Also,          lines 17 and 22.
USER_INDEX in TXVECTOR is 0- Change "user 2" to "user 1" on
3 (Table 22-1). Suggest to      lines 37 and 42.
follow the same convention for Change "user 3" to "user 2" on
user index for 'coding' in VHT- lines 45 and 50.
SIG-A2.                         Change "user 4" to "user 3" on
                                lines 54 and 57.
There is a little ambiguity         How about this additional        Minho                    PHY
whether user index starts from      words at this field? : "user 1"
0 or 1? This sentence here          here needs to be changed into
cannot match to the                 "user 1 (user index described in
expression. In addition to that,    N_STS field (B10-B21) is 0
in all the equations in following   here)". In the similar way, user
text, user index, u has the         2, user 3 and user 4 also can be
range from 0 to N_u - 1. But,       changed in to one with
all the text which describes        additional supplementary
each user thing in MU-MIMO          words for clarification.
have the expression that user
1, 2, 3, 4. Because there are
already lots of these kind of
text, it may be very difficult to
modify all the text or
equations.

There is no description about       Add the following sentences     DISAGREE. SU transmissions PHY
the setting of B2 for BC/MC         after line 23:                  include unicast, broadcast and
scheme.                             For BC/MC, B2 is set to 0 for   multicast transmissions.
                                    BCC, or 1 for LDPC.             Suggest to clarify this at the
                                                                    beginning of clause 22.
                                                                    Resolution text in 11/368r1.


The reference here is incorrect Change: "as described in                                      Ed
                                 22.3.4" to "as describe in
                                 22.3.11.4.2"
If N_STS for the last user is 0, Change "B4 is reserved" to "B6 Youhan. Typo                  PHY
then B6 is reserved, not B4.     is reserved"

There is no description about Add the following sentences           DISAGREE. See #126.       PHY
the setting of B4-B7 for BC/MC after line 60:
scheme.                        For BC/MC:
                                 B2 is set to 0 for BCC, or 1
                               for LDPC.
This is not very clear. Maybe                                                                 Ed
more details could be added to
clarify why this is needed

"BF steering matrix … in       Use consistent terminology:          Brian                     PHY
20.3.11.10.1" yet 20.3.11.10.1 e.g. both spatial mapping
describes both CDD and Q       matrix or BF steering matrix.
(called "spatial mapping
matrix") but not BF steering
matrix
Only right parenthesis is         as described in section                                  Ed
inserted when referring the       20.3.11.10.1
related section
Unmatching bracket                Change "in 20.3.11.10.1)," to                            Ed
                                  "in 20.3.11.10.1,"

There is no description about     Add the following sentences        DISAGREE. See #126.   PHY
the setting of B8 for BC/MC       after line 8:
scheme.                           For BC/MC:
                                    Reserved and set to 1.
This references section                                                                    Ed
20.3.9.4.4. There is no such
section.
24 bits                           24 data bits                                             Ed
There is no Figure[TBD], and      Change "containing 24 bits, as                           Ed
frankly do not feel such a        shown in Figure[TBD]." to
figure is necessary. Table 22-9   "containing 24 bits, as shown
is sufficient.                    in Table 22-9."
"Figure [TBD]" should be          As in comment.                                           Ed
revised as "Figure 22-10".

No reference for figure. Says     Need to add figure showing                               Ed
Figure[TBD]                       VHT-SIG-A1 and VHT-SIG-A2

TBD for the figure of VHT-SIG-A Insert the figure.                                         Ed

The Figure of VHT-SIG-A is        Add the Figure and the index of                          Ed
needed.                           the figure
The Figure of VHT-SIG-A is        Add the Figure and the index of                          Ed
missing.                          the figure
add VHT-SIG-A figure which is     add figure and reference                                 Ed
now a TBD
Missing figure of VHT-SIG-A       Add the required figure                                  Ed

VHT-SIG-A1 and VHT-SIG-A2         The VHT-SIG-A is composed of                             Ed
have been described in Table      two symbols, VHT-SIG-A1 and
22-9                              VHT-SIG-A2, each containing
                                  24 bits, as shown in Table 22-9.

missing figure (TBD); are we      check and revise                                         Ed
refering to the table above?

Referring figure number is      as shown in Figure 22-10                                   Ed
missing
LSB ordering is a dup of Note 1 Remove dup                                                 Ed
at P103L17
0b001011 representation is   e.g. "001011 in binary"                         Ed
not traditional 802.11
terminology. Ditto P150L7
In the Group ID example      Change the sequence to                          Ed
(0b001011), wrong characters "001011".
are inserted in front.

For clarity, write "The first and As in comment                     Brian    PHY
second half of the stream of …"

Is it clear how to partition the                                    Youhan   PHY
96 complex numbers into two
groups of 48 complex
numbers?
There is no discussion of the                                                Ed
CRC calculation for the VHT -
SIG -A. There is one for VHT-
SIG-B, but not for A.

Refer to M'(k) by equation         As in comment                             Ed
number; start by giving it an
equation number
Incorrect figure reference.        Change "Figure 22-8" to                   Ed
                                   "Figure 22-10".

This reference is to (Figure 22-                                             Ed
8). It seems the reference
should be to Figure 22-10

Wrong Figure number for            Change Figure 22-8 to Figure              Ed
QBPSK                              22-10.
there is no Figure 22-8            Add Figure 22-8                           Ed
There is no Figure 22-8            Fill Figure 22-8                          Ed
Missing Figure 22-8                Put Figure 22-8                           Ed
Inconsistent abbreviation in       Change to "VHT-SIG-A".                    Ed
"VHTSIGA"
description saids 'VHT-SIG-A'      Change to text in figure 22-10            Ed
with the dashes, but the           to "VHT-SIG-A".
figures say 'VHTSIGA' without
dashes, which is inconsistent

"replicating it in each 20 MHz Remove "frequency shifting"          Brian    PHY
band" sounds like freq shifting
is happening as a byproduct

For consistency, "given in" =>     As in comment                             Ed
"given by". ALso P105L22
TCS,VHT … Table 22-6            22-8                                      Ed
Instead of "does not include" As in comment                               Ed
maybe it is better to say "does
not show". This makes it more
clear that rotations should be
applied.

Missing word 'Table'              Change "in 22-5" to "in Table           Ed
                                  22-5"

Missing word 'Table'              Change "in 22-6" to "in Table           Ed
                                  22-6"

"QAM mapper outputs" yet          QAM mapper => constellation Brian       PHY
BPSK is an allowed                mapper
constellation
There is a little ambiguity       Number of VHT LTFs              Minho   PHY
about the title of Table 22-10

There is a little ambiguity        one, two, four, six or eight           Ed
about what is the exact            number of VHT-LTF symbols
meaning of enumerated
numbers
It is desirable to add a note:     As in comment                          Ed
LLTFleft is the leftmost 26
entries of (17-8); LTFright is the
rightmost 26 entries of (17-8)

For consistency, replace "VHT- As in comment                              Ed
LTF" by "the sequence ot be
transmitted"

"of 80MHz transmissions"          of an 80 MHz transmission               Ed
Missing equation reference                                                Ed

Reference number of equation Add (22-29) as the reference                 Ed
is missed.                   number.

Missing Equation reference.       Change "Equation ." to                  Ed
                                  "Equation (22-29)."

N_STS, which referred in Figure   N_STS in A matrix and Q matrix          Ed
22-11 does not be defined in      needs to be changed into
SU case                           N_STS,total
"Generation of VHT-LTFs"          "Generation of VHT-LTFs per    Brian    PHY
                                  segment"
TVHTLTFs                          TVHTLTF                        Brian    PHY
N_STS, which referred in          N_STS in Equation 22-31 needs Minho                      PHY
Equation 22-31 does not be        to be changed into N_STS,total
defined in SU case
There is a little ambiguity       The VHT-LTF mapping matrix                               Ed
about what is the exact           for six symbols of VHT-LTFs
meaning of number described
here.
There is a little ambiguity       The VHT-LTF mapping matrix                               Ed
about what is the exact           for eight symbols of VHT-LTFs
meaning of number described
here.
Missing brackets.                 Change "Equation 20-27." to                              Ed
                                  "Equation (20-27)."

shall is redundant since it       Delete sentence or convert to Brian                      PHY
arises as a side effect of (22-   informative language
30)
suggest modification for more     "0101" in binary                                         Ed
readable expression
Because "80MHz, 160MHz,           80MHz, 160MHz, 80+80MHz                                  Ed
80+80MHz" expression cannot
fit in one row, comma needs to
be inserted here

Since VHT SIG-B includes          1), Use a reserved bit in VHT- Liwen has presention      PHY
Length field to indicate PSDU     SIG-A to indicate Aggregation
length, VHT single MPDU in A-     of PSDU
MPDU is not necessary. This       2), Change the Length
can simplfy the protocol by       description to "length of useful
removing VHT single MPDU          data in PSDU
related description.              in units of 4 octets when A-
                                  MPDU is PSDU, length of useful
                                  data in PSDU in units of octets
                                  when MPDU is PSDU"
                                  3), Delete VHT single MPDU
                                  related description.

16 bits Length in units of 4    Clarify it.                       Liwen has presentation   PHY
octets can describe max A-
MPDU length defined in 11ac
specification (1,048,575). Why
do you need the length of
Length field more than 16 bits?

This field is called Length,      Pick VHT-SIG-B Length (to       Brian                    PHY
length amd VHT-SIG-B Length       distinguish it from LSIG
                                  LENGTH) and stick with it
It is better to additionally       "unit of 4 octets" needs to be                                Ed
denote the unit of VHT-SIG-B       inserted in Equation (22-34)
Length here
where newline LENGTH               Remove newline                                                Ed
It is better to additionally       LENGTH is the TXVECTOR                                        Ed
denote the unit of Length here     LENGTH parameter (in octets)

NSTS is undefined for MU, and      Rewrite this section to deal     Minho                        PHY
SIGB is a MU field. Also the "as   with MU PPDUs (""For each
defined in" is misleading since    user, the VHT SIG B ...). Change
it is only P that is defined in    "as defined in" to "which is
22.3.9.2.5                         defined in"
p_z or p_3 (because z is always    p_z or p_3                                                    Ed
3) may be more readable
expression than p_0+z

Dk and M'(k) should have a         As in comment                     Brian                       PHY
"BW" subscript or superscript

There is a little ambiguity as I for user u (index starts from 0) Minho                          PHY
already pointed out at Line 17 at subcarrier k.
in page 100
"the constellation"              "a/the constellation point".     Brian                          PHY
                                 Also, move the parenthetical
                                 comment to the end of the
                                 sentence for clarity

Refer to the equation where        As in comment                                                 Ed
possible rather than the
section - i.e. (22-14)
There is a little ambiguity        add "the tail bits (6 N_ES bits   AGREE IN PRINCIPLE. N_ES is PHY
about whether MU or SU             for SU and 6 N_ES,u bits for      only defined for SU case in
                                   each user u in MU)"               Table 22-5. In MU case, the
                                                                     number of encoders may be
                                                                     different according to different
                                                                     users, so is it about the
                                                                     number of tail bits. Resolution
                                                                     text in 11/388r0.

Insert "For BCC encoding", to As in comment                          Brian                       PHY
distinguish it from (22-45).
And, this fix is incomplete since
NES,u is undefined for SU
LDPC. Add a separate equation
for SU LDPC
Nservice is regretably           Path of least resistance is just Brian                       PHY
undefined                        to replace it by 16. Also, there
                                 is no equation for calculating
                                 Ntail,u - need to add, or define

encodes                          encoders                                                     Ed
Wrong word "encodes".            Change the word to                                           Ed
                                 "encoders".
PHY padding computation for Change "In case of MU LDPC           Youhan                       PHY
LDPC encoding in case of SU      encoding," to "In case of LDPC
transmission is not defined.     encoding," on line 30. On line
Equation (22-45) also applies 42, change "Equation (22-50)"
to SU case as well in principle, to "Equation (22-50) in case of
with some additional             MU. N_{SYM_max_init} =
clarifications.                  N_{SYM,init} in case of SU
                                 where N_{SYM,init} is given by
                                 Equation 22-48)"

scrambler initialization needs   Define as all zeros                                          Ed
to be set to all zeros.
It may be better to fill the     Fill this blank with the      Minho. 11/388r0. (Brian: use   PHY
blank in Table 22-12             expression "see Table 17-6ac" better reference since BW
                                                               signaling not applicable)

PSDU_LENGTH is Rxvector,    Use LENGTH rather than                  Robert                    PHY
why use RxVector to compute PSDU_LENGTH.
Tx parameters (Npad)?

Grammar issue                      Modify "Service Field" to                                  Ed
                                   "SERVICE Field"
The IEEE style for a variable list remove line 34. Remove                                     Ed
doesn't admit a floating "and" trailing pnuctuation and the
and doesn't attempt to             and at line 47. Use variable
connect items of the list          list style to get correct text
                                   size. Apply throughout clause
                                   22.
Incorrect section reference.       Change "(LDPC) code defined                                Ed
                                   in 22.3.11.6." to "(LDPC) code
                                   defined in 22.3.11.4.2."

Range of i is not described      Report range of i (esp. does it Brian                        PHY
                                 start at 0 or 1?)
Equation number is missing       This Equation may become                                     Ed
here                             Equation (22-47). There is also
                                 need to re-number all the sub-
                                 sequent equations
{x_j_i} does not match to         needs to be changed into                                 Ed
Equation shown at line 40 in      {x_(j)_i}
page 116
"using equation 22-47 instead     1). modify equation 22-47 as AGREE IN PRINCIPLE.         PHY
of Equation 20-35" is not         "Npld=Nsym,init*NDBPS" and Resolution text in 379r1.
appropriate. If we use            move the text in pg117/ln59 to
Equation 22-47 following 22-48    pg118/ln10.
to calculate Npld, we will find   2). Insert following sentence in
Nsym,init is devided by Mstbc     pg118/ln11 after the equation
once more which changes the       22-48:
meaning of Npld.                  "Following the Npld
And this sentence implies that    calculation, Navbits for VHT
we calculate Navbits using        packets shall be computed
Equation 20-36 as 11n.            using Equation (22-xx) instead
Actually, as we have achieved     of Equation (20-35).
Nsym,init ,the calculation of       Navbits=Nsym,init*NCBPS
the Navbits could be simplified   (22-xx)"
to Navbits=Nsym,init*NCBPS,
instead of using Npld to
calculate as 20-36




Please verify if m_stbc is        As in comment                     Duplicate. See #1559   PHY
needed in EQ (22-47). m_stbc
in EQ (22-47) cancels it.

Reference is incorrect. It                                                                 Ed
references Section 20.3.11.8
for LDPC encoding Process for
MU packets. This is probably
referring to 22.3.11.4.3, but
that is for both encoders.
There is no section for LDPC
encoding process in case of
MU packets.

Delete space in title             Correct: "Encoding proc ess" to                          Ed
                                  "Encoding process"
It seems not nice to explain      Comprehensive representation                             Ed
N_ES,u with the use of N_ES,      may be needed in Table 22-5,
because N_ES is not defined       including MU and SU as well
for MU in Table 22-5
It seems not nice to explain      Comprehensive representation                                 Ed
N_DBPS,u with the use of          may be needed in Table 22-5,
N_DBPS, because N_DBPS is         including MU and SU as well
not defined for MU in Table 22-
5
Missing Equation reference.       Change "in Equation is" to "in                               Ed
                                  Equation (22-51) is"

Missing equation reference        Should reference (22-51)                                     Ed

Missing Equation reference.       Change "in Equation is" to "in                               Ed
                                  Equation (22-51) is"

Missing equation reference        Should reference (22-51)                                     Ed

Incorrect section reference.      Change "22.3.11.5 and                                        Ed
                                  22.3.11.6." to "22.3.11.4.1."

"then B3 of VHT-SIG-A2 should If a normative requirement,          Brian.                      PHY
be set to 1." - is this really just use "shall". Ditto next
a recommendation, or a              sentence.
normative requirement.

These references are incorrect,                                                                Ed
22.3.11.5 and 22.3.11.6 are the
Stream parser and segment
parser respectively. Not the
BCC encoding process.

There is no section called BCC                                                                 Ed
encoding process as
referenced here.
There are some amguities          needs to be changed into " "i AGREE. Resolution text in      PHY
about the expression in this      th bit of output of j th encoder 11/388r0.
sentence.                         is assigned to k th input bit of
                                  i_ss th spatial stream". Delete
                                  y_(j)_i because there is no
                                  other referrings.

There is no description about     add in Equation (22-53) "k=0,    AGREE. Resolution text in   PHY
range of k in Equation (22-53)    1, … , N_CBPSS"                  11/388r0.

"Input k" is not clear.           Please better define "input k", Vinko                        PHY
                                  its meaning.
Range of k not described          Report range of k (esp. does it See #208                     PHY
                                  start at 0 or 1?)
There is no description about     add in Equation (22-54) "k=0,   See #208   PHY
range of k in Equation (22-54)    1, … , N_CBPSS"

There is no description about     add in Equation (22-54)         Vinko      PHY
range of i_ss in Equation (22-    "i_ss=0, 1, … , N_ss"
54)
i' does not used in any part of    The summation element in                  Ed
Equation (22-54)                   Equation (22-54) needs to be
                                   changed into simply "(i_ss-
                                   1)*s"
Equation (22-54) appears to be Replace with conditional           Vinko      PHY
invalid for i_SS = 1 (at least the assignment for i_SS=1 and
sum term doesn’t make sense) otherwise. Line 47 could then
                                   be removed too.
Equation number is missing         Equation (22-54)               Vinko      PHY

Missing Equation reference.       Change "Equation has" to                   Ed
                                  "Equation (22-54) has"

There is no equation number    Change: "term in Equation has                 Ed
provided. It appears this      a value of 0." to "term in
should be Equation 22-54       Equation 22-54 has a value of
                               0."
Missing equation reference     Should reference Equation (22-                Ed
                               54)
It seems to have better        needs to be changed into "the                 Ed
expression about this sentence first term in Equation (22-54) is
                               neglected"
This paragraph is a good       Define these important special Youhan         PHY
introduction but is not as     cases via math. And normative
precise as math                language. As well, in the same
                               way that the math for a
                               deinterleaver is defined, define
                               the math for a stream deparser
The following paragraph looks Rephrase?                                        Ed
a bit cluttered.
"For 160 MHz MCSs, if each
BCC encoder does not
generate integer blocks of S
coded bits in each OFDM
symbol, then apply the same
stream parsing method above
until the last integer block
(floor(NCBPS/NES/S))
of S bits at each encoder....."


In some preceding part of the       Floor operator here needs to               Ed
document, gaussian symbolic         be replaced with gaussian
operation is used instead of        symbolic operator as in
floor operator                      Equation (22-54)
"until the last interger block      for floor() integer blocks of S   Youhan   PHY
(floor()) of S bits"                bits
Sentence starting "Assuming         Start with "At this stage, for    Youhan   PHY
that" needs a rewrite for clarity   the current OFDM symbol,
                                    each BCC encoder has Ms
                                    (where M = [insert equation]
                                    and M<s) residue bits …" and
                                    keep improving

"M.s " the product operators        fix product operators                      Ed
look as sub-index                   expression.

Equations (22-53) and (22-4)     Please verify the equations.         Vinko    PHY
seem to be in error. Instead of
s in the denominator it should
be S. Also first term in Eq (22-
54) (summation) should be a
function of k.

A variable is created as "M.s".                                                Ed
Not exactly sure of the
intended variable name,
possibly M_s? Is used in 3
places.
Change till to until                                                           Ed
This section is confusing since Rewrite using distinct                Minho    PHY
"blocks" is used in two distinct terminology
senses: P121L2 and P121L34

Should be NCBPSS/2-1                As in comment                     Minho    PHY
Front size is exceptionally large need to re-adjust the font size           Ed
(from line 13 to line 26)

Avoid k-th                       Rephrase as "is bit k of the               Ed
                                 subblock l"
This paragraph is a good         Define these important special Minho       PHY
introduction but is not as       cases via math. And with
precise as math                  normative language. As well, in
                                 the same way that the math
                                 for a deinterleaver is defined,
                                 define the math for a segment
                                 deparser.

Need an equation for R        As in comment                         Minho   PHY
Explicitly reference table                                                  Ed
"third operation" but P122L22 Use consistent terminology -                  Ed
"third permutation"           i.e. change third op to third
                              perm
Missing word "Table".         Change "given in 22-13." to                   Ed
                              "given in Table 22-13."

There is ambiguity on what this are given in Table 22-13                    Ed
number means
comma is missing in small       iss = 1, 2, … , N_ss                        Ed
equations about i_ss
It seems more readable to       N_ROT dot N_BPSCS                           Ed
include 'dot' as a meaning of
multiplication of symbolics

It seems better to change the    the spatial stream index                   Ed
expression for cohesiveness      (instead of "the index of the
with the mentioning in the       spatial stream")
preivous page

It seems more readable to        N_ROT dot N_BPSCS (this can                Ed
include 'dot' as a meaning of    be also applicable to several
multiplication of symbolics      subsequent similar cases)

Missing word "Table".            Change "given in 22-14." to                Ed
                                 "given in Table 22-14."

Missing Equation reference.      Change "by Equation ." to "by              Ed
                                 Equation (22-61)."

Missing equation reference       Should reference Equation (22-             Ed
                                 61)
Equation number is missing        Equation (22-61)                          Ed
here
Reference figure by Figure                                                  Ed
number
Constellation is not seen         Re-capturing of this figure is            Ed
overall. Some part of rightmost   needed
arrow is hidden
hyphen for 256-QAM is             needs to add hyphen, that                 Ed
neglected only here in the        means, 256-QAM
entire draft
Missing word "Figure".            Change "in 22-14" to "in Figure           Ed
                                  22-14"

There is ambiguity on what this Figure 22-14                                Ed
number means
N_SS is not defined for multi- N_SS,total can be used for           Minho   PHY
user case in Table 22-5         multi-user case

It is not easy to read            It seems more readable to                 Ed
                                  have a enough space between
                                  this equation and subsequent
                                  note for range of variables

There is no description of      Refer to the related equation               Ed
N_SD, N_SS, N_SYM               numbers
This describes the segment      Give segment deparsing its        Youhan    PHY
deparser as a minor section in  own section (e.g. after
the constellation mapper        constellation mapping), and
section                         align the diagrams in 22.3.3
                                with where you put it (e.g.
                                don't have per-segment STBC
                                or CSD blocks in fig 22-6 and 22-
                                7)
subblock index l needs to have the subblock l=0, which is         Youhan    PHY
explanatory notes               defined in Equation (22-55)
l is used two times in the same As in comment                     Youhan    PHY
section with two different
meaings - find a new variable
letter
In "l=0", l should be italic.   As in comment.                              Ed

Front style of subblock index l   subblock l=0 needs to be                  Ed
here is different                 change into itallic
Sentence is wrong because '='     The normalization factor for              Ed
also has the meaning of 'is'      256QAM is defined as in
                                  Equation (22-xx)
Missing word "Table".               Change "in 22-15." to "in Table      Ed
                                    22-15".

There is ambiguity on what this Table (22-15)                            Ed
number means
t(k) is the key equation for    Add equation number                      Ed
LDPC tone mapping. So, it is
not adequate for this not to
have its equation number

Grammatical error. In "the          Update the sentences to "the         Ed
output bits of the interleaver      output bits of the interleaver
corresponding to the subblock       corresponding to the subblock
l=0 is ..." and "while the output   l=0 are ..." and "while the
bits of the interleaver             output bits of the interleaver
corresponding to the subblock       corresponding to the subblock
l=1 is ...", both "is" should be    l=1 are ...".
"are".

Grammatical error. In "the          Update the sentences to "the         Ed
output bits of the interleaver      output bits of the interleaver
corresponding to the subblock       corresponding to the subblock
l=0 is ..." and "while the output   l=0 are ..." and "while the
bits of the interleaver             output bits of the interleaver
corresponding to the subblock       corresponding to the subblock
l=1 is ...", both "is" should be    l=1 are ...".
"are".

80+80 MHz is missing. Also,         Change "In case of 160 MHz" Youhan   PHY
contiguous 160 MHz has only         to "In case of 160/80+80 MHz"
one frequency segment.              on line 11.
                                    Change "80 MHz frequency
                                    segments," to "80 MHz
                                    frequency portions/segments"
                                    on line 13.

There is ambiguity on which   It seems better to change into See #632    PHY
'160MHz' means between        "In case of contiguous 160MHz
contiguous and non-contiguous or non-contiguous 80+80MHz
                              VHT PPDU transmissions"

There is ambiguity on which   It seems better to change into See #632    PHY
'160MHz' means between        'the overall LDPC tone mapping
contiguous and non-contiguous for contiguous 160MHz or non-
                              contiguous 80+80MHz VHT
                              PPDU transmissions"
Equation references missing       Should reference Equations (22-           Ed
(x2)                              64) and (22-65)

t(k) is the only function to      Hence, the overall LDPC tone              Ed
explain LDPC tone-mapping.        mapping for contiguous
So, expressions in Line 15 is     160MHz or nontiguous
not adequate.                     80+80MHz can be described as
                                  Equation (22-xx)

t(k) is the key equation for      Add equation number                       Ed
LDPC tone mapping. So, it is
not adequate for this not to
have its equation number

Proper indentation is needed                                                Ed

N_SS and N_STS are not            They need to be changed in    Minho       PHY
defined for multi-user case in    N_SS,u and N_STS,u
Table 22-5                        respectively (this kind of
                                  modifications are also needed
                                  in sub-sequent clauses)

"which are mapped to NTX           True, but not the subject of     Brian   PHY
transmit chains"                   this section - delete
In d_{k,1,m}, the 1 should be a As in comment                       Brian   PHY
i, 7x in this clause
It might be useful to either use                                            Ed
the d' from the LDPC tone
mapping section for d in this
section. In the LDPC tone
mapping section (22.3.11.8.3),
a d' was defined for both LDPC
and BCC… This section then
reuses the variable d, so it
could be interpreted that this
is the d before the LDPC tone
mapping. The other approach
is to note that in this section, d
= d' from the previous section
(LDPC tone mapping).


the input of                      input to                                  Ed
d and d and d is confusing        Rewrite as d and d, and the               Ed
                                  value of d
In all expressions for d_k,1,n                                             Ed
and d-tilde, change “1” to “i”.

In this paragraph, the second     Please modify the second                 Ed
subscripts of some                subscripts of these symbols to i
mathematical symbols
including dk,1,n, d~k,1,n,
dk,1,2m, dk,1,2m+1, etc., are
variables and should not be
limited to 1.
Line widths for this table are    need to re-capture this fiture           Ed
not even.
N_SS and N_STS are not            They need to be changed in    Minho      PHY
defined for multi-user case in    N_SS,u and N_STS,u
Table 22-5                        respectively (this kind of
                                  modifications are also needed
                                  in sub-sequent clauses)

Sinec NSTS is the new kid write   As in comment                            Ed
NSTS = NSS
andN                              and N                                    Ed
{-21,-7,7,21} is a partial        Change to k \element {-21,-              Ed
notation                          7,7,21}. Apply k \element 4x in
                                  this section
pk \nelement equation is          Add                             Minho.   PHY
missing
"22-17" should be revised as      is given in Table 22-17                  Ed
"Table 22-17".

Missing word "Table".             Change "given in 22-17." to              Ed
                                  "given in Table 22-17."

Reference number of equation "Equation and Table 22-17"                    Ed
is missed.                   should be revised as "Equation
                             (22-70) and Table 22-17".

Missing Equation reference        Change "Equation and 22-17"              Ed
and word "Table".                 to "Equation (22-69) and Table
                                  22-17."
Missing equation reference        Should reference Equation (22-           Ed
                                  69)
Missing reference to 80 MHz       Add reference to equation 22-            Ed
equation (22-69) in "… as         69.
specified in Equation and 22-
17.
Equation number is missing        Equation (22-69)                         Ed
here
Missing the word Table before Change "and 22-17" to " and                      Ed
22-17 so this is not confused Table 22-17"
with and equation number

There is ambiguity on what this Table (22-17)                                  Ed
number means
copied on                       copied to                                      Ed
Missing equation number         Change "specified in Equation                  Ed
                                and" to "specified in Equation
                                22-69 and"
equation is for Tsym and TGI    Add an equation for short GI          Minho.   PHY

NTones but at P130L39, NTone Change to NTone                                   Ed

The LHS is per segment, but        Get the math right for both 1      Minho.   PHY
the RHS, especially D, is not      and 2 segments
defined per segment
"Refer to the examples of          When Ntx <=4, refer to the                  Ed
listed in Section                  examples of listed in Section
20.3.11.10.1 for examples of       20.3.11.10.1 for examples of
that could be used for SU          that could be used for SU
packets". Actually,when Ntx>4      packets. When Ntx>=5, the
for "spatial expansion",the        spatial expansion may be
examples listed in Section         performed by duplicating some
20.3.11.10.1 is not practical,so   of the streams to form the
we need to state more clearly .    streams with each stream
                                   being scaled by the
                                   normalization factor
                                   sqrt(Nsts)/sqrt(Ntx) , or by set
                                   the Ntx-Nsts streams as zero.
                                   Note that implementations are
                                   not restricted to the spatial
                                   mapping matrix examples
                                   listed in Section 20.3.11.10.1.




length field                       Length or more accurately                   Ed
                                   LENGTH
data transmission                  the Data field. Ditto P131L1                Ed
N_{Field}^{Tone} in Table 22-6 In Equation (22-76), change                                    Ed
does not have a explicit input "N_{NON-
argument (BW).                 HT_DUP}^{Tone}(BW)" to
                               "N_{NON-HT_DUP}^{Tone}".
                               On line 32, change "N_{NON-
                               HT_DUP}^{Tone}(BW)" to
                               "N_{NON-HT_DUP}^{Tone}".




Table 22-7 defines CSD for non-     Change the description for       Youhan.                  PHY
HT portion of packet for upto 8     "T_{CS}^{i_{TX}}" to
antennas. No reason not to          "represents the cyclic shift for
use it for non-HT duplicate         transmitter chain i_{TX} with a
packets as well.                    value given in Table 22-7."

TBD doesn’t apply. For more                                            Duplicate. See #636.   PHY
than 4 antennas, cyclic shifts
have been defined

"For more than 4 antennas, the      1)modify in line 28 "represents                           Ed
cyclic shifts are TBD." actually,   the cyclic shift for transmitter
Cyclic shift for non-HT portion     chain iTX with a value given
of packet for more than 4           in Table 22-87"
antennas have solution in           2) Delete the following
Table 22-7                          sentence as "For more than 4
                                    antennas, the cyclic shifts are
                                    TBD."

Cyclic shift values for more        Cyclic shift values are defined Duplicate. See #636.      PHY
than 4 antennas are TBD.            in Table 22.7, page 95.
                                    Change text to "represents the
                                    cyclic shift for transmitter
                                    chain with a value given in
                                    Table 22.7. 20-8 (Cyclic shift
                                    for non-HT portion of packet)
                                    for up to 4 antennas. For more
                                    than 4 antennas, the cyclic
                                    shifts are TBD "


TBD is unnecessary - just point As in comment                                                 Ed
to Table 22-7
cyclic shifts are TBD -> fill in Change "cyclic shifts are TBD"        Duplicate. See #636.   PHY
TBD                              to "cyclic shifts are defined in
                                 Table 22-7".
"Q_k" should not be BOLD but       As in comment.                           Ed
italic.
Current description could be       Try "With MU-MIMO                Brian   MU
mistaken for groupcast. Also,      beamforming, the space-time
"subset" is relatively imprecise   streams are partitioned into
                                   two or more parts, with each
                                   part intended for a single STA."

Section 20.3.12.0a is referred As in comment.                               Ed
as Q_k; however, the detailed
text is found in Section
20.3.11.10.1 of REVmbD4.01
and the number of reference
section should be revised to
20.3.11.10.1.

BFer by BFee using compressed the BFer to the BFee using the                Ed
                              compressed
The reference number for the Add "7.3.1.32" as the number                   Ed
feedback report format is     of reference section.
missed.
Table number for VHT          described in Table 7-9, 7-10                  Ed
compressed beamforming        and 7-11 (VHT compressed
report field is missing       beamforming report field)
We are talking about BFee i,  Pick a way of indexing the     Brian          MU
and this is equivalent to the users and stick with it
(oddly named) USER_NUM in
the TXVECTOR

NTX                                NRX                              Brian   MU
"transmit signal vector" to me     Try "transmitted spatially       Brian   MU
implies a time domain              mapped signal vector"
representation
y_k_N_TX in the small              It needs to be changed into      Minho   MU
equation is wrong                  y_K_N_RX_i
"for multiple users up to the      for all Nu BFees/users           Brian   MU
Nu BFee"
In the text "up to the Nu          Change to the following: "is             Ed
beamformee", there is no role      shown in Equation (22-77),
of the word "up to". The           where x_k=[….], denotes the
number of receipients is Nu.       transmit signal vector for the
Moreover "beamformee"              Nu beamformees, x_k,i =[….]
should be a plural.                being the transmit signal for
                                   beamformee i."
Clearer if reorder by writing "in As in comment                              Ed
subcarrier k with dimensions
NRX x NTX". Ditto P133L15

of signal                           of the signal. Or better,                Ed
                                    "number of STS that are
                                    transmitted"
Wrong notation in "N STS i".        Use correct notation for                 Ed
                                    N_STS,i as in line#63 of
                                    Page#132.
Or additive colored noise or        "is additive noise and           Brian   MU
WiFi interference or non-WiFi       interference"
interference - no need to be so
constraining
"found" sounds kind of like a       "determined"                             Ed
random discovery
For "j=1,2,…,Nu.", it better to     Change into "where j=1, 2, …,            Ed
add a space behind ",".             Nu.".
BFee                                the BFee                                 Ed
index k in definition of V_k,j is   It needs to be changed into              Ed
missing                             "the beamforming feedback
                                    matrices for sub-carrier k and
                                    beamformee j, that is, V_k,j
                                    and SNR information from
                                    beamformee j at sub-carrier k,
                                    that is SNR_j,k, where
                                    j=1,2,…,N_u.

"may replace" - normative       may -> might                                 Ed
verbs are reserved for
description of the behaviour of
behavioural protocol entities.
And a beamforming matrix is
not such.

In the text "reduce crosstalk       Change the text to "reduce               Ed
interference between the            interference among the signals
beamformees. " , crosstalk and      intended for different
interference both mean the          beamformees"
same thing, so the text is
redundant, and the use of
"between" is incorrect as it
implies just 2 beamformees


font & fill style                                                            Ed
Front size from Line 40 to Line Front size is needed to re-                                    Ed
54, is different from other     adjust
parts
Missing word "Table".           Change "in 22-8" to "in Table                                  Ed
                                22-8"

There is ambiguity on what this   Table 22-8                                                   Ed
number means
V_k does not match to the        needs to be changed into V_k,j Minho                      MU
previous mentioning in this      or needs to add some
page                             explanatory note on which
                                 simulation between SU and
                                 MU
The angles, φ(k) and ψ(k), are Modify "Table 7-25j" to "Table AGREE. As suggested (updated Ed
quantized according toTable 7- 7-2"                             numbering)
25j. Table 7-25j is quantization
of angles for HT MIMO contrl
field, it should be modified to
new table for VHT MIMO
contrl field.

"BFing feedback format and no "Clause 22 BFing feedback              AGREE IN PRINCIPLE.       MU
other feedback format is          format defined."                   Resolution in 11/372r2.
allowed for interoperability".
Actually I think a) this is a MAC
observation, out of scope of
the PHY, and b) it is factually
wrong: a VHT AP should be
able to use other feedback
formats to talk with HT STAs


Refer to the source of SNRj     As in comment                        Brian                     MU
in multi-user cases, per-tone   needs to be changed into             Minho                     MU
SNR needs at carrier-by-carrier 'SNR_j,k'

Group ID is also used for some Needs to add this explanatory                                   Ed
limited purpose of non-MU          note: When single-user
cases                              transmission or other cases,
                                   e.g., broadcast transmission,
                                   the group Id field is set to be
                                   '63'
"informed" is not usually used informed by AP => sent by the                                   Ed
in the passive voice in this way - AP
the sTAs would be the subject

an STA. Ditto P134L24             a STA                                                        Ed
in the NSTS                        from the NSTS                                          Ed
its STA position; the "its" refers STA's (and likely some rewrite                         Ed
to NSTS field not the STA          too): "From the NSTS field, the
                                   STA extracts its [own] number
                                   of STS streams from the
                                   subfield that is determined by
                                   the group definition of the
                                   corresponding Group ID"

We are using NSTS in two         As in comment                       Brian                MU
senses in this section: "NSTS
field of all MU STAs" and "NSTS
subfield of a single STA"
(P134L24). Much cleaner &
clearer if the NSTS field is
renamed, perhaps to MU-NSTS
field, or NSTS vector field, etc

own signals                      own signal                                               Ed
the designated signals           a STA's designated space time Brian                      MU
                                 streams
Instead of "..but also to        As in comment                 AGREE.                     MU
supress" write "..but also may
be used to supress"
"also to suppress the            Change to " also to measure                              Ed
interference at a beamformee" the channel to interfering
is not quite correct as the VHT- signals"
LTFs are used to measure the
channel to the interfering
signals

the channel knowledge to         its channel knowledge of                                 Ed
which are                        that are                                                 Ed
"avoid" is too strong            "suppress"                     AGREE IN PRINCIPLE.       MU
                                                                Resolution in 11/359r1.
"eigenmodes" seems to            "interference from space time AGREE IN PRINCIPLE.        MU
assume SVD precoding or          streams that were imperfectly Resolution in 11/359r1.
similar                          precoded by the AP" seems
                                 more general, although this is
                                 not perfect either

beam-forming' is different      hyphen needs to deleted                                   Ed
from several expressions of the
same meaning
assigned                        its assigned                                              Ed
This sentence                                                        Brian                MU
"NDP shall be the only VHT           "The NDP is the only sounding Sun Bo. (check with brian)   PHY
sounding format" is too              format defined in Clause 22".
simplified to appear in the PHY      And to limit sounding
section, epsecially as               exchanges between VHT STAs
normative language. VHT APs          to the NDP, write/refer to MAC
may talk to HT clients, and use      text
HT sounding formats with
them. It is fair to say NDP is the
only VHT sounding format
defined in clause 22, but the
"shall" is redundant since it is
true by inspection, and the
"shall" is inappropriate since it
seems to constrain the spec
not implementations.


Remove "the" in front of VHT         As in comment                                              Ed
PPDU
The VHT NDP format … has the         Rewrite: "The format of a VHT Sun Bo. (check with brian)   PHY
following properties … it has        NDP PPDU is shown in fig xxx.
the same the VHT PPDU                The VHT NDP PPDU has the
format" reads badly                  following properties: - uses the
                                     VHT PPDU format without the
                                     Data field/element/portion - is
                                     a SU PPDU, as indicated by VHT-
                                     SIG-A - has the data bits of
                                     VHT-SIG-B set to a fixed bit
                                     pattern (see xxx)." And,
                                     actually, VHT-SIG-A introduces
                                     confusion: for other language
                                     (e.g. 22.3.22) it would
                                     beneficial if GID=63 was a
                                     synonym for SU, and the sub-
                                     list rewritten to allow this
                                     terminology




The number of VHT-LTFs in            Insert the description below     Sun Bo.                   PHY
NDP is not clear. The number         line 43:
of VHT-LTFs in NDP is indicated      "The number of VHT-LTFs in
by Nsts in VHT-SIG-A.                NDP is indicated by Nsts in VHT-
                                     SIG-A."
In the TGac spec framework,        According to R3.1.E in the TGac Zhendong.   PHY
R3.1.E requires that the draft     spec framework, please add
specification shall include        the following statement
support for an efficient           somewhere in 22.3.15, "This
channelization in China’s          amendment shall include
(5,725 ~ 5,850 MHz) spectrum.      support for an efficient
However, the current version       channelization in China’s
doesn't include the related        (5,725 ~ 5,850 MHz) spectrum,
statement.                         and the specific channelization
                                   solution is TBD."

may' is not adequate because needs to be changed into 'shall' Minho.           PHY
802.11ac PAR and 802.11ac
Functional Requiremenst
already specifies that the 11ac
amendnent shall … in 5GHz
band.

The Group ID is also used by   Describe the Group ID          Osama. Simone.   PHY
the VHT Control Filed. Need to operation when included in the
describe its operation when    VHT Control Field.
included in the VHT Control
field in this section

In case                            In the case, 3x in table; also              Ed
                                   P150L22
change to "where the ch st         As in comment                               Ed
freq is given by the op class".
Ditoo P135L52
insert "where the"                 As in comment                               Ed
Text is missing the restriction    Include 17.3.8.4.2 5 GHz         Minho.     PHY
that is present in clause 17       channel 0 restriction here after
Channel numbering "value null      the primary 20 MHz channel
for nch shall be reserved, and a   numbering definition.
channel center frequency of
5.000 GHz shall be
indicated by
dot11ChannelStartingFactor =
8000 and nch = 200."

Grammar.                           Change "may used." to "may                  Ed
                                   be used."

"to freq                           to a freq                                   Ed
For "Valid range = 0, 1, … ,    Change into "Valid range = 0, 1,                           Ed
200", it better to add a space …, 200.".
behind ",", while a space after
"…" is not required.

22.3.16 is "shall", 22.3.17 is "is   Harmonize                      Brian.                 PHY
defined" - which is needed?
Shall or cross ref?
"The transmitter RF delay shall      Reword so that it relates to   Duplicate. See #486.   PHY
follow 17.3.8.5." normative          STA behaviour or turn into a
verbs are reserved for               declarative statement
description of the behaviour of
behavioural protocol entities.
And an RF delay is not such


default is undefined.                default => 802.11           Brian.                    PHY
The mask is defined with             Change the spectral mask    Brian has a proposed      PHY
reference to the max PSD of          reference to                resolution
the signal. In 11ac, we have         min(maxPSD,mean(PSD[central
introduced sloppier flatness         subcarriers as listed in
requirements which allowsthe         22.13.19.2])+2). Repeat for
peak PSD to rise above the           20/40/80/160 MHz
mean by 4 dB. So for devices
with +4dB peaks, the mask
requirements are loosened
(higher slidelobes) by 2dB. This
a) creates moral risk that
vendors will be tempted to
create a 4dB peak, and b) was
not an identified issue during
tecnhical discussions


"a 80 MHz" should be revised         As in comment.                                        Ed
to "an 80 MHz". The revision
also should be applied on the
1st line of page 140.)

example of                     example of a                                                Ed
180 => 200. ALso, a linear sum As in comment                        Brian.                 PHY
will produce a curved line
Either define the number of          Change to "Let Ei, avg denote Ron.           PHY
symbols to average spectral          the average constellation
flatness over or if the number       energy of the subcarrier i
of symbols is not necessary          averaged over TBD of the VHT
remove it.                           data symbols"

There's a TBD                        resolve it                    Ron.           PHY
Why not setting this TBD VHT         How about setting this TBD to Ron.           PHY
data symbols for calculation of      the same duration to that of
the average constellation            EVM test, that is 16 OFDM
energy per each carrier, to be       data symbols?
the same duration to that of
EVM test, that is 16 OFDM
data symbols?

Information in this section          Create a table, and update      Ron/Brian.   PHY
would be better presented via        language to refer to table
a table
a 80 => an 80                        As in comment                                Ed
Do we need to define if the          If we need to define "All       Ron.         PHY
averaging is performed over          averaging performed in this
the linear or log domain?            section is performed in dB."

Resolve editor note re:              As in comment, also 7.3.2.63,   Ron.         PHY
averaging used.
Here, 'section' term is used.        needs to use one term for                    Ed
But, in other parts of this draft,   these expressions.
'sub-clause' term are used
many times.
Coin flip needed.                    Flip a coin.                    Ron.         PHY
"The tests for the spectral          Change to "The tests for the    Ron.         PHY
flatness requirements can be         spectral flatness requirements
performed with spatial               shall be performed with spatial
mapping"                             mapping"
Change 'can be performed' to
'shall be performed'
how about having a note on           add a note here with             Ron.        PHY
the definition of ppm?               parenthesis or the first part of
                                     this draft
It is depending on vendors'          So, it seems better to add this Ron.         PHY
option whether two carriers          explanatory note to this
are used or only one carrier is      sentence: 'if each 80MHz
used for contiguous 160MHz           segments is transmitted with
and non-contiguous 80+80             the use of separete carrier'
transmissions.
Signal extension is only           Is this section even needed? Or Ron.    PHY
required for 2.4 GHz, but 11ac     at least note that it has no
is prohibited from operation in    impact.
this band
There's a TBD                      resolve it                     Ron.     PHY
needs a explanatory note           N_SS=N_STS (no STBC)           Ron.     PHY
There is a little ambiguity on     Needs to be changed into "the           Ed
the exact meaning                  same requirement applieds 20,
                                   40, 80 and contiguous 160MHz
                                   transmissions, as well as non-
                                   contiguous 80+80MHz
                                   transmissions"

Change EVM requirement for As in comment                          Ron.     PHY
64_qam rate 5/6 from -28dB to
-27dB.
Non-contiguous is an exception As in comment                      Ron.     PHY
to the previous para, so need
to run them together "being
transmitted; excepting that for
non-contiguous …"

"with both segments being          "while both segments are                Ed
transmitted" is not quite          being transmitted"
precise
One sample resolution is           change to "with 50 ns          Ron.     PHY
overkill of a 160 MHz packet,      resolution"
given that the GI duration
hasn't changed. And many
implementations process the
primary only

Channel estimation procedure                                      Brian.   PHY
It is not explicit whether
channel estimation to be done
only from the training symbols.
Is it kept as open deliberately?
Say for instance, continuous
adaptation of channel from the
data is allowed?


Grammatical error.                 Change "according to                    Ed
                                   estimated phase" into
                                   "according to the estimated
                                   phase.".
vector, multiply                   vector, and multiply                    Ed
Channel tracking Enabled                                             Brian.                           PHY
Looks like channel tracking
(payload tracking) is technically
allowed? Is it going stay as it
is?
"Data OFDM symbols may              It seems better to remove this   AGREE. Agreed that this a)         PHY
be used to update or                sentence. An alternative is to   waters down the EVM
recompute the channel               use "shall" but then EVM         requirements by a fraction of a
estimate." Due to this              numbers need to be changed       dB or so, and b) does not
sentence Tx EVM is not defined      which may not be desirable.      guarantee reliable
accurately. Problem is in "may"                                      interoperability if a TX is tested
statement.                                                           assuming averaging but an RX
                                                                     is built without averaging.
                                                                     Statement removed.

"Data symbols may be used to Delete sentence                         Duplicate. See #206.             PHY
update … the channel
estimate" but a) this presumes
that the RX is performing such
updating which nowhere is
required or guaranteed, and in
fact is technically more difficult
with multiple STSs and or
users, b) because the packet
length under test is unbounded
(>16 sym up to ???), allowing
averaging means that a a weak
initial estimate can be
drowned out by long
averaging, so this encourages
poor initial channel estimation,
and c) since chanenl estimation
incurs a few dB of loss, this
sentence waters down the
EVM requirements by several
dB


How about adding a clause on        This is kind of already done and Ron.                             PHY
EVM measurement on the              may be obvious. An explicit
normalization? Say for              addition may provide a means
instance, i) Approporate            to quantify the constellation
normalization of the                error for not only additive
constellation is performed          noise, but others too such as
before computing the RMS            phase noise and various known
                                    RF impairments.
There is no definition of N_f   needs to add its definition or Ron.        PHY
                                delete this expression
There is ambiguity on what this at least 16 data OFDM symbols Ron.         PHY
number means                    long
Sentence is back-to-front and As in comment                                Ed
thereby confusing. Start the
sentence with the nuimber of
input ports in the DUT, and so
work back to the #ports in the
test equipment (and clarify
"transmtting STA" perhaps via
"transmitting STA (i.e. non-
DUT)")

"or less" is orphaned.          Move to immediately after                  Ed
                                10%
the term 'less' is used         The term 'or less' needs to be             Ed
duplicately                     deleted after mentioning
                                'Table 22-20'
Typo in table title             receiver minimum input level               Ed
                                sensitivity
Missing word "Table".           Change "in 22-20" to "in Table             Ed
                                22-20".

There is ambiguity on what this Table 22-20                                Ed
number means
"specified in 22-20" should be As in comment.                              Ed
revised to "specified in Table
22-20".

Missing word "Table".           Change "in 22-20" to "in Table             Ed
                                22-20".

There is ambiguity on what this Table 22-20                                Ed
number means
The interfering signal should   As in comment                    Youhan.   PHY
also be an 80+80 signal, with
each segment next to one of
the desired signal's segment.
Ditto for non-adjacent tests in
22.3.20.3
"The interference signal …         Invert the order of sentences           Ed
50%" is characterizing the test    at P143L17 and P143L16. Ditto
and so belongs next ot other       for P114L3
test characterizations such as
P143L14-15. Once
characterized, the limits can be
referred to
Missing word "Table".              Change "in 22-20" to "in Table          Ed
                                   22-20".

There is ambiguity on what this Table 22-20                                Ed
number means
It seems like in the following, Delete these two sentences          Reza   COEX
CCA requirements are spelt out
for clause 17 and 20 PHYs, so
no reference is needed

The reference section of CCA Delete "and 19.4.6".                   Reza   COEX
sensitivity requirement for non-
HT PPDUs in 2.4GHz band is
not needed because the
specifications in Clause 22 is
only for 5GHz transmission.


The clause 17 PHY provides for     Define CCA-ED option in          Reza   COEX
CCA-ED with                        primary 20 MHz channel in
dot11OFDMEDThreshold. The          order to have a stronger
22.3.20.5.1 should provide the     argument to share 5.35-5.47
same capability for signals        GHz band with aeronautical
occupying the primary 20 MHz       and maritime users.
channel as an option,
especially when this PHY gets
used in 5.25-5.725 GHz sharing
with government users.


I don't know why you need a Consider converting to regular                 Ed
dashed list inside the table cell. cellbody
Looks odd
In subclause 22.3.20.5.2, A VHT Clarify it.                      Reza                         COEX
STA will issue secondary
channel busy per the following
value
1st channel: "20 MHz channel
at or above -72 dBm"
2nd channel: "20 MHz sub-
channel of the secondary 40
MHz channel at or above -72
dBm"
3rd and 4th channel: "20 MHz
sub-channel of the secondary
80 MHz channel at or above -
69 dBm"

In subclause 17.3.10.6: "The
start of a valid OFDM
transmission at a receive level
equal to or greater than the
minimum modulation and
coding rate sensitivity (–82
dBm for 20 MHz channel
spacing,"

The secondary CCA detection
should be -82dBm (as
measured in a 20MHz
bandwidth). to accept -72 for
Motion was                        Change to -72                  AGREE. As per Motion 16 in   COEX
40 MHz PPDUs not -69                                             11/11r5.
The sensitivity levels for signals Please provide some details   Reza                         COEX
that do not occupy the primary how the preamble detection is
channel requires that the          performed.
receiver is capable to perform
preamble detection on every
separate 20 MHz channel. How
the detection of the preamble
is performed in the secondary
channels?


Motion was to accept -72 for      Change to -72                  AGREE. As per Motion 16 in   COEX
20 MHz PPDUs not -69                                             11/11r5.
Is the requirement of the       Please clarify.                      Reza     COEX
detection probability > 90% the
same for all signal
combinations? How the
detection probability is
possible to test? 90%
probability is still quite low.

25μs - please be aware that      25 μs                                        Ed
IEEE style requires the units to
be separated from the number

Seems to needs some              "shall be selected". Also     Eldad.         PHY
mandatory language here          "option" is perhaps the wrong
                                 word here - try "sub-
                                 procedures" or "sequences"

The other                        The second                                   Ed
What happens if this second      Define                              Eldad.   PHY
option is selected? Nothing
seems to be said
The word 'respectively' is not   Change "Non_HT,                              Ed
needed.                          respectively." to "NON_HT."

respectively wrt what?           Delete respectively. Also, x or y            Ed
                                 or z => x, y, or z
Odd to start a sentence with     Rewrite                                      Ed
"And"
This is barely a sentence        Rewrite, avoiding the                        Ed
                                 imperative. And this sounds
                                 like a third option (not 2 as
                                 mention at P145L46)

Reference numbers are            Revise "as defined in and" to                Ed
missed.                          "as defined in 22.3.8 and
                                 22.3.11.11".

Missing section reference.       Change "in and ." to "in 22.3.8              Ed
                                 and 22.3.11.11."

Missing reference                Please add the references.                   Ed
The number of the sections       Please complete this sentence                Ed
that defines 80MHz and           as "80 or 160 MHz channel as
160MHz channels are not          defined in 22.3.15 and Annex
provided.                        J."
Missing references               Should reference 22.3.8 and                  Ed
                                 22.3.11.11
with                              using                                               Ed
"clear channel" seems to          "clear channel for the intended Eldad.              PHY
simple                            bandwidth"
What are the circumstances to     Please clarify                  Eldad.              PHY
use the latest value of PHY-
CCA?
"Note under some                  As in comment                    Eldad.             PHY
circumstances" is vague -
needs a reference (and should
be most circumstances rather
than some circumstances, with
a SIFS transmission/response
as the main exception?)


What is the lastest PHY-       Please clarify                      Eldad.             PHY
CCA.indication? How old it may
be and how often it is updated

Subject of actin is not clear     shall be initiated by the PLCP   Eldad.             PHY

"The presence of a signal that clarify                             Reza               COEX
occupies one or more
secondary channels under the
conditions listed in this section
shall be detected with >90%
probability within a period
aCCAMidTime (< 25μs)." Is this
applied to -62 dBm (energy
detection) also?


"A modulation rate change" is     A change in MCS and/or           Eldad. 11/492r0.   PHY
stale                             number of STSs
As written "PHY-TXSTART" is a     Replace by "PSDU                 Eldad. 11/492r0.   PHY
state, but in reality it is a     transmission" or equivalent
primitive that cannot be
disabled. Ditto P146L29
There is a syntax error in this   Please add "of" between                             Ed
sentence "...according to the     "number" and "OFDM"
number OFDM symbols..."

"Non-VHT Preamble" and "VHT- Change to L-STF and L-LTF, and Eldad. 11/492r0.          PHY
Training" are not defined    VHT-LTFs. Ditto P147L18,
                             P148L22, P151L29
"and encoding" looks out of        "Get encoding (bits per        Eldad. 11/492r0.    PHY
place                              symbol)" probably makes
                                   sense but belongs at SETUP
                                   MPDU TX
"decrement bit count by bits       As in comment                  Eldad. 11/492r0.    PHY
per symbol" should be
"Decrement bit count by 8"
"N_Sym > 0" should be "N_Sym       As in comment                  Eldad. 11/492r0.    PHY
>0 or Bit_Count > 0
"Set length count" - should be     As in comment                  Eldad. 11/492r0.    PHY
"symbol count"?
"VHT-SIGA in order to set the      Delete VHT-SIGA                Eldad. 11/492r0.    PHY
max duration" yet SIGA doesn't
help here
Subject not clear                  Upon the PMD receiving …        Eldad. 11/492r0.   PHY
Subject not clear                  is indicated by the PLCP to the Eldad. 11/492r0.   PHY
                                   MAC
"PMD_RSSI … parameter              "The PMD primitive PMD_RSSI                        Ed
reported to the MAC", but          is issued to update the RSSI to
routing of this signal is not      the PLCP, and the PLCP
clear                              includes its most recently
                                   received RSSI value in the PHY-
                                   RXSTART.indication(RXVECTOR
                                   ) primitive


"missed preamble" language is Update. ALso, clarify, is this  Eldad. 11/492r0. (not   PHY
not used anymore              related to the primary20 or the discussed)
                              whole bandwidth? (I suspect
                              the former). Ditto P149L31

or the                             or a                                               Ed
Should we consider adding                                         Youhan.             PHY
'ceil()' around (L_LENGTH + 3) /
3?
and supported                      indicating a supported                             Ed
two values should be allocated     Please use values 62 and 63 for See #665?          PHY
for SU transmissions. Value 62     SU transmissions.
for group addressed SU
transmissions and value 63 for
individually addressed SU
transmissions.

Equation is missing TLSIG     Add                            Eldad. 11/492r0.         PHY
Should use named bits, rather Name fields; ditto P150L30 and Eldad. 11/492r0.         PHY
than bit positions            P150L32
MU user index is set to 0-3 in    Change "user 1, 2, 3 and 4" to   Minho will check entire spec   PHY
other places.                     "user 0, 1, 2 and 3".            for consistent use

"coding bit" but there are two    Update text to latest SIGA       Eldad. 11/492r0.               PHY
coding bits in SU, and more for   definition, using named fields
MU
BCC                               A BCC                                                           Ed
Missing equation reference.       Change "Equation using" to                                      Ed
                                  "Equation (22-47) using"

Missing equation reference        Should reference (22-47)                                        Ed

Wording could be improved. "If As in comment                                                      Ed
the VHT-SIG-B field is decoded
and the VHT-SIG CRC field is
checked and valid, the PHY
shall issue a PHY-
RXSTART.indication(RXVECTOR
).

"intended end" is vague - insert As in comment                     Eldad. 11/492r0.               PHY
"Determined by (22-80)

to RX IDLE state                 to the RX IDLE state                                             Ed
The C-PSDU less the tail bits is Show removal of padding bits      Eldad. 11/492r0.               PHY
not necessarily a whole          after tail bits.
number of octets. 0-7 padding
bits may need to be removed.

Diagram does not show             Add                              Eldad. 11/492r0.               PHY
dropping of pad bits
PMD_CHAN_MAT.ind should           Move                             Eldad. 11/492r0.               PHY
occur after VHT-training

VHT -SIG-B                        VHT-SIG-B                                                       Ed
Figure is silent on special       Add                              Eldad. 11/492r0.               PHY
processing arising from partial
AID
The reference section for non-    Delete "or 19.3.6" in Figure 22- Eldad. 11/492r0.               PHY
HT PPDUs in 2.4GHz band is        24.
not needed because the
specifications in Clause 22 is
only for 5GHz transmission.
VHT-SIGA => Unsupported            Harmonize the language           Eldad. 11/492r0.      PHY
mode but text refers to
"Reserved VHT-A Indication"

PLMERESET                       PLME-RESET                                                Ed
"Table 22-xx" should be revised As in comment.                                            Ed
to "Table 22-23".
There's a TBD                   resolve it                          Youhan has proposed   PHY
                                                                    resolution
Incorrect Table reference.         Change "Table 22-xx" to "Table                         Ed
                                   22-23".

and append "but shall not be       As in comment                    Youhan has proposed   PHY
updated by the PLME" for                                            resolution
clarity
To get RX-side power saving        Add a partial AID MIB variable Youhan has proposed     PHY
benefits from the partial AID,                                    resolution
the PHY should be configured
with its own partial AID

OK, so this interface tells the    Specify this algorithm          Youhan has proposed    PHY
PHY where its first segment        somewhere in the PHY. May resolution
channel is and how wide it is.     need to tell the phy the
But when the TXVECTOR              location of the primary channel
specifies a transmitted PPDU       to achieve this.
channel width of less than the
bandwidth indicated in this
table, how does the PHY
determine which bits of the full
channel width to use?


No specifications on TBD           Clarify TBD.               Youhan has proposed         PHY
                                                              resolution
This section is to determine    Change references at P154L35, Eldad. 11/492r0.            PHY
TXTIME, so we don't need        P154L37, P154L65, P155L2,
definitions, we need            P155L19, L155L40, P155L42
equations/values. Thus refer to (also the latter needs
Section 22-5 not table 22-5     clarification for MU)

using is                           using BCC is                     Eldad. 11/492r0.      PHY
Clause 10 work is needed to        As in comment                    Brian.                PHY
make this real
TBD in aPSDUMaxLength              Determine the value.             Brian.                PHY
There's a TBD                      resolve it                       Brian.                PHY
For "NSS=1,…,8", it is better to   Change into "NSS=1, …, 8".                             Ed
add a space behind ",".
80+80 MHz missing.                  Change "160 MHz" to            Minho has proposed resolution PHY
                                    "160/80+80 MHz".

The text "Support for MCS 1         Make changes to clarify the       Minho has proposed resolution PHY
through 7 (when listed as valid     text. Replace the line "Support
in the associated table) is         for MCS 1 through 7 (when
mandatory" does not make            listed as valid in the associated
sense in general. We have to        table) is mandatory" with the
remove this line. We should         following text:
instead clarify that if a certain   " If a certain combination of
combination of BW and               BW and number of spatial
number of spatial streams is        streams is supported, then
supported, then support for         support for MCS 1 through 7 is
MCS 1 through 7 for that            the minimum level of MCS
combination of BW and               support assumed for that
number of spatial streams is        combination of BW and
the minimum level of MCS            number of spatial streams
support assumed (except when        except when the values of Tx
the Tx highest supported data       highest supported data rate or
rate or the Rx highest              the Rx highest supported data
supported data rate sub-fields      rate sub-fields in the VHT
in the VHT Supported MCS Set        Supported MCS Set field result
field state otherwise).             in a cut-off, or a certain MCS is
                                    invalid."




80+80 MHz missing.               Change "Support for 160 MHz" Minho has proposed resolution        PHY
                                 to "Support for 160/80+80
                                 MHz".
For "NSS=2,…,8" and              Change into "NSS=2, …, 8" and                                     Ed
"NSS=1,…,8", it is better to add "NSS=1, …, 8".
a space behind ",".
N_ES, N_SS, N_DBPS are not       So, it needs to describe with Minho has proposed resolution       PHY
defined for multi-user cases     the exact definition of these
                                 values from Table 22-5, here
                                 and several subsequent
                                 paragraphgs
DR is not defined                Add definition                Minho has proposed resolution       PHY
Tables from here onwards are     Redefine the number of            Brian has presentation     PHY
hole-ier than Swiss cheese.      encoders for these higher
This arises from the choice of   rates. Where NES is currently
#encoders and the mod(..,DR)     set to
condition.                       1,2,3,4,5,6,7,8,9,10,11,12,
                                 change NES to
                                 1,2,3,4,6,6,8/9,8/9,9/12,12,12,
                                 12 or similar - e.g. instead of 5
                                 encoders, use 6, and so forth.
                                 This will fill in most of the
                                 holes, and for a device
                                 implementing 5 encoders,
                                 going to 6 is not much of a
                                 burden (and right now, 5
                                 encoders is only used for 2
                                 table entries only - i.e. 5 is a
                                 pretty useless special case)


In Table 22-48, the NDBPS is     Modify the NDBPS to 12480       Minho has proposed resolution PHY
11232 for MCS9, which            using MCS9
becomes the same as that for
MCS8
80+80 MHz missing.              Change "160 MHz" to             Minho has proposed resolution PHY
                                "160/80+80 MHz" in the
                                captions for Table 22-49 to 22-
                                56.
No new Behaviors are needed Remove all references to            Peter will have a proposed    COEX
for 80 MHz and 160 MHz          VHT80MHzBehavior and            resolution
operation. See REVmb 11-        VHT160MHzBehavior from the
10/1284r4 (CIDs 10168-          draft, and make no changes to
10176).                         Annex I.
Delete "Editor's note: Modify", Throughout the document,                                      Ed
and use the correct editing     there are occurrences of
instruction "Change" rather     "modify" in the editing
than "Modify"                   instructions where "Change"
                                needs to be used. Change,
                                Delete, Insert and Replace are
                                the valid editing instructions.

This red editor's note needs to as in comment                                                 Ed
be a bold italic editing
instruction without "Editor's
note"

Ditto Line 43 et seq
"an VHT80+80 BSS"                   Change into "a VHT80+80 BSS".                                Ed

"an VHT80+80 BSS" should be         As in comment.                                               Ed
revised to "a VHT80+80 BSS".

Define channel sets for 80 MHz      Please define.                  Peter will have a proposed   COEX
and 160MHz.                                                         resolution
TGmb has removed                    Remove all references to        Peter will have a proposed   COEX
IndoorOnlyBehavior and              IndoorOnlyBehavior and          resolution
DFS_50_100_Behavior, see            DFS_50_100_Behavior from
REVmb 11-10/1284r4 (CIDs            the draft.
10168-10176).
IndoorOnlyBehavior is defined
and used only where "location
of operation must be 'indoors'
as defined in the regulatory
domain." It is not a specified
behavior in any band without
radar regulatory requirements,
and should be removed from
the standard as all stations that
will be allowed to operate in
those bands will meet such
regulatory requirements.
DFS_50_100_Behavior is
defined and used only "where
radiolocation radar is primary,
and station operation has in-
service monitoring
requirements". It is not a
specified behavior in any band
without radar regulatory
requirements, and should be
removed from the standard as
all stations that will be allowed
DynamicFrequencySelectionBe    Remove all references to   Peter will have a proposed             COEX
havior is defined without any DynamicFrequencySelectionBe resolution
normative requirements. Its    havior in Annex J from the
existence in the standard adds draft.
no value.
REVmb D7.0 removed                * Remove                          Peter will have a proposed   COEX
IndoorOnlyBehavior,               "IndoorOnlyBehavior",             resolution
DynamicFrequencySelectionBe       "DynamicFrequencySelectionB
havior, DFS_50_100_Behavior       ehavior",
and                               "DFS_50_100_Behavior" and
TransmitPowerControlBehavio       "TransmitPowerControlBehavi
r. This can reduce the number     or" from Tables J-1, J-2, J-3 and
of additional operating classes   J-4.
needed fo 11ac.                   * Consolidate multiple <ANA>
                                  rows into a single row
                                  whenever possible (have the
                                  same Behavior limits set) in
                                  Tables J-1, J-2, J-3 and J-4.


TransmitPowerControlBehavio Remove all references to        Peter will have a proposed           COEX
r is defined without any       TransmitPowerControlBehavio resolution
normative requirements. Its    r in Annex J from the draft.
existence in the standard adds
no value.

Incorrect Channel center          Change "50" to "114" under      Youhan has proposed            COEX
frequency index                   "Channel center frequency       resolution
                                  index"
Since CS4msBehavior is            Remove all references to        Peter will have a proposed     COEX
required by Japanese              CS4msBehavior in Table J-3      resolution
regulations in unlicensed         from the draft.
operation, there is no
normative reason to require it
in Table J-3 Operating Classes
in Japan.
IBSSRestrictionsBehavior is       Remove all references to        Peter will have a proposed     COEX
defined and used only "where IBSSRestrictionsBehavior, in         resolution
an IBSS is required to            Annex J from the draft.
communicate with a
licensed operator or agent
designated by regulatory
authorities." It is not a
specified behavior in any band
without such regulatory
requirements, and should be
removed from the standard as
all stations that will be allowed
to operate in those bands will
meet such regulatory
requirements.
(Refer to Draft 802.11mb-        Add VHT bit in Neighbor Report AGREE IN PRINCIPLE.            MAC
D.6.0)                           element.                       Resolution text in 11/302r0.
To support VHT operations,
need to indicate VHT in
Neighbor Report element.
(Refer to Draft 802.11mb-        Add VHT Capabilities        AGREE IN PRINCIPLE.               MAC
D.6.0)                           subelement, VHT Operation   Resolution text provided in
To support VHT operations,       subelement, VHT Channel     11/0305r1.
VHT Capabilities subelement,     Switch Announcement element
VHT Operation subelement,        are required in Table 8-98.
VHT Channel Switch
Announcement element are
required in Table 8-98.

(Refer to Draft 802.11mb-       Change the sentence to "…,                                     Ed
D.6.0)                          Clause 19 (High
In the listing of Clauses for   Throughput (HT) PHY
PHY, a new clause for VHT       specification), and Clause 22
should be added.                (Very High
                                Throughput (VHT) PHY
                                specification)."
(Refer to IEEE802.11mb-D4.01) Define behavior.                  Illsoo.                        MU
SM power save mode is only
defined in 11n. However, some
modification is needed to
support SM power save mode
in MU-MIMO. No rule is
defined how to turn off
redundant power chain (In
11n, RA is used for SM power
save. However, in MU-MIMO,
not all STA will check every RA
in MU-MIMO packet)




Definition of DR cannot be        Please define DR.                                            Ed
found in the context
Does the rule                     Please clarify.                                              Ed
(mod(Ncbps/Nes, DR)~=0)
stated in the note still apply to
LDPC where Nes is always 1?

Duplicated Table number.         Change table number 7-13 to                                   Ed
Table number 7-13 is already     other non duplicated number
used in the 802.11 baseline
document
The absence of any qualifier       Add "if the                   Illsoo.   MAC
implies the Associaion ID is       dot11VHTOptionImplemented
present in all the (T)DLS Action   attribute is true" or similar
frames mentioned.                  qualification.

"a RTS" should be revised to       As in comment.                          Ed
"an RTS". There are eight "a
RTS"s.




Enable recommendation of No- For solicited add following       Illsoo.     MU
MCS Supported in MFB.           combination in page 55, line
Current draft spec forced       32: "- MFB contain MCS=15,
responder to recommend at       MSFI in the range 0 to 6: the
the minimum MCS0. With inter- responder is indicating no MCS
stream interference, MCS0 is can be supported for the
not always possible. Suggest to request that had the MSI value
assign an unused MCS index to that matches the MSFI value".
indicate No-MCS, e.g. MCS=15. For unsolicited add following
                                text in page 56, line 20: "A
                                value of MCS=15 indicates the
                                VHTC is indicating no MCS can
                                be supported for the PPDU
                                that matches the description
                                given by GID-L, GID-H, Coding
                                Type and FB TX Type fields"




some of the entries of the         correct                                 Ed
table are truncated, e.g.
FORMAT, RSSI, LENGTH, and
maybe in other places
The table is wrong. Many           Complete the table.                     Ed
missing elements and
explanations.
9.7e states that the           Change to refer to 9.7e for    Brian.                       PHY
PARTIAL_AID in TXVECTOR is 0, construction of partial AID.
the lsbs
of the BSSID, or a function of
the AID and the BSSID,
depending
on the context.

However the locations
referenced suggest it's the lsbs
of the
BSSID (or, in the first location,
0).
The treatment of VHT single       Answer the five questions   Yong has a proposed resolution MAC
MPDUs is                          posed and then update the
ambiguous/inconsistent.           spec accordingly.
There are two fundamental
questions:

1) Is a "VHT single MPDU"
considered to be a type of A-
MPDU
or is it considered to be a non-
A-MPDU?

2) May a "VHT single MPDU"
contain zero-length MPDUs? If
an
A-MPDU "contains a single
MPDU of non-zero length.", is
that
to be interpreted as "contains
a single MPDU of non-zero
length, and nothing else", or
"contains a single MPDU of
non-zero length, and any
number (including zero) of
MPDUs of
zero length"?


"V" in are three matrix V"
There "feedbacksubsidiary         As in comment.                                           Ed
should be italic. It also appears
on the fifth line of page 15.
Is this draft based off 802.11-   Clarify which version of 802.11                                   Ed
2007? Or a revision of TGmb?      standard this is based off. This
                                  should be called out in the
                                  draft as other draft
                                  amendments do.

Is it clear from the spec that a Please include a NOTE if            Youhan has proposed            COEX
40 MHz PPDU can not be           clarificatin is needed.             resolution
transmitted in the center of a
80 MHz channel, for example?

There are numerous TBDs in        As in comment                      Vinko has a proposed           Ed
the spec, Please perform                                             resolution
search for TBDs and define
them
11n PAR scope was "The scope      Change the PAR or add              Eldad has a proposed            TG
of this project is to define an   additional mandates on APs         resolution. Brian would like to
amendment that shall define       and clients                        withdraw this comment.
standardized modifications to
both the 802.11 physical layers
(PHY) and the 802.11 Medium
Access Control Layer (MAC) so
that modes of operation can
be enabled that are capable of
much higher throughputs, with
a maximum throughput of at
least 100Mbps, as measured at
the MAC data service access
point (SAP).", and this was
interpreted as 11n had to
define a mandatory mode
offering >100Mbps. 11ac PAR
langauge is equivalent "This
amendment defines
standardized modifications to
both the 802.11 physical layers
(PHY) and the 802.11 Medium
Access Control Layer (MAC)
that enable modes of
operation capable of
supporting: o A maximum
multi-station (STA) throughput
(measured at the MAC data
The Definitions specific to       Add the definitions                                               Ed
802.11 is missing definitions
for TXOP power save.
How the CF-End frame is         Please clarify                 Jarkko has proposed resolution MAC
transmitted in 802.11ac
networks:
1. Is it transmitted to all
channels to which the signaling
to set NAV is transmitted?
2. How the CF-End frame is
repeated by the AP?

What happens if a STA that has Please clarify.                 Jarkko presented (383r0, 384r0 COEX
NAV value set receives a RTS                                   is the normative text). Jarkko
frame, but does not receive                                    will work further and discuss
PHY-RXSTART.indication                                         with others.
primitive within (2 ×
aSIFSTime) + (CTS_Time) +
aPHY-RX-START-Delay + (2 ×
aSlotTime) starting at the PHY-
RXEND.indication primitive. Is
the earilier NAV value still in
use, or is the NAV value set to
0 in NAV reset?


TPC mechanism allows limiting Details will be provided in TG   Nir has a proposed resolution   COEX
power for all BSS members.     meeting
Suggest to add provisions for
controlling transmit power per
STA. Motivation is to add more
tools for AP to reduce induced
interference

Fonts used in tables should be Reformat using proper font.                                     Ed
cellbody/cellheading, which is
smaller than in this table.

Please be aware that TGv have   At some point (REVmb D7.1),                                    Ed
modified both the               you will need to update to
TXVECTOR/RXVECTOR table         include these changes. This
and also the PLCP procedure     should be posted by early
diagrams to support Time of     March.
departure measurement

There are no PICS entries       Add PICS entries.              Osama will work on this         Robert
There is no MIB                 Add a MIB.                                                     Robert
Because neither Transmit         See P802.11af_D1.0 for     Daewon. Possible resolution   MAC
Power Constraint nor Extended    evolved Channel Power      presented in 11/305r0.
Channel Switch Announcement      Management functions that
are extensible, consider using   control both constrained
11-10/767r1 Channel Power        maximum transmit power and
Management Announcement          channel
to manage both frequency and     frequencies/bandwidths.
transmit power in BSS.


"Edit" and "Modify" are not      Use any of the four valid                                Ed
valid editing instructions.      editing instructions as
                                 appropriate.
IEEE Style Manual 18.1, NOTE     per comment                                              Ed
paragraphs are not in italics,
and NOTE is followed by em
dash.
Comment   Draft
Status    Status

          Updated




          Updated
No change
Updated




Updated
Updated




Updated




No change
Updated
No change
           Updated




Approved   Updated




           Updated


Approved   Updated




           Updated
Updated




Updated
Approved   Updated
Approved   Updated




Approved   Updated
Approved   Updated




           Updated
Approved   Updated




Approved   No change
Approved   Updated




Approved   Updated




Approved   Updated




Approved   Updated
Approved   Updated




           Updated




           Updated


Approved   No change




           Updated




           Updated
           Updated




           Updated

           Updated




Approved   Updated




Approved   Updated




           Updated


           Updated
Approved   Updated
Approved   No change




Approved   Updated




           Updated
Approved   Updated




           Updated




Approved   Updated




           Updated
Approved   Updated




           Updated




           Updated

           Updated


           Updated




           Updated
           Updated




           Updated




           Updated




           Updated




           Updated




Approved   Updated


           Updated

           Updated
           Updated

           Updated

           Updated

           Updated




           Updated




Approved   Updated




           Updated


           Updated

Approved   Updated




Approved   Updated




Approved   Updated

Approved   Updated
Approved   Updated

Approved   Updated




Approved   Updated




Approved   Updated




Approved   Updated




           Updated

Approved   Updated
Approved   Updated




Approved   Updated
Approved   Updated
Approved   Updated




           Updated


           Updated


           Updated
Updated


Updated
Updated




Updated


Updated




Updated




Updated




Updated


Updated




Updated


Updated




Updated




Updated
Updated




Updated


Updated


Updated




Updated




Updated




Updated




Updated


Updated
           Updated




Approved   Updated




Approved   Updated




           Updated




Approved   No change




Approved   Updated
Approved   Updated




           Updated




           Updated




           Updated


           Updated




           Updated


           Updated

           Updated
Updated

Updated




Updated


Updated

Updated


Updated
Updated

Updated

Updated
Updated




Updated




Updated


Updated


Updated
Updated

Updated

Updated
Updated

Updated




Updated




Updated




Updated




Updated




Updated




Updated
Updated
Updated

Updated


Updated
Updated

Updated




Updated




Updated

Updated
Updated
Updated
Updated


Updated


Updated




Updated




Updated
Updated




Updated




Updated




Updated


Updated




Updated
Updated




Updated




Updated
           Updated




Approved   Updated
Approved   Updated




Approved   Updated




Approved   Updated




Approved   Updated




Approved   Updated


Approved   Updated


Approved   Updated
Approved   Updated


Approved   Updated




           Updated


           Updated

           Updated




           Updated




           Updated
Updated




Updated




Updated




Updated


Updated
Updated




Updated




Updated




Updated


Updated




Updated
Updated




Updated
Approved   No change
Updated
Updated
Updated
Updated
Updated




Updated
Updated




Updated
Updated


Updated




Updated


Updated




Updated




Updated
Updated
Updated




Updated




Updated


Updated

Updated
Updated




Updated
Approved   Updated




Approved   Updated




Approved   Updated




Approved   Updated
Approved   Updated




Approved   Updated


Approved   Updated




Approved   Updated

Approved   Updated

           Updated




Approved   Updated

Approved   Updated

           Updated
Approved   Updated




Approved   Updated




           Updated
           Updated
           Updated




           Updated




Approved   Updated




Approved   Updated
Approved   Updated




Approved   Updated




Approved   Updated


Approved   Updated




Approved   Updated


Approved   Updated




Approved
Approved   Updated


Approved   Updated


Approved   Updated


Approved   Updated




Approved   Updated


Approved   Updated




Approved   Updated




Approved   Updated


Approved   Updated
Approved   No change




           Updated




           Updated




Approved   Updated




Approved
           Updated




Approved   Updated




Approved   No change




           Updated




Approved   Updated
Approved   Updated




Approved   No change




           Updated

           Updated


Approved   Updated




           Updated
Updated




Updated


Updated

Updated

Updated


Updated




Updated
Updated


Updated




Updated


Updated
Updated




Updated




Updated


Updated




Updated


Updated




Updated
Updated
Approved   Updated
           Updated


           Updated

Approved   Updated
Updated
Updated
Updated
Updated
Updated
Updated
Approved   Updated
Updated




Updated


Updated




Updated




Updated
Updated
Updated




Updated
No change




No change




No change




No change




No change




No change




No change




No change
No change
Updated
Updated




Updated


Updated

Updated
Updated


Updated

Updated

Updated

Updated

Updated

Updated
Updated




Updated
Approved   No change
Approved   Updated




Approved   Updated
Approved   Updated
Approved   Updated




Approved
Approved   Updated




Approved




Approved
Approved   Updated




Approved   Updated
Approved   Updated




Approved
Approved   Updated




Approved   Updated
Approved   Updated




Approved   No change




Approved   No change
Approved   Updated

Approved   Updated




Approved   Updated


Approved   Updated
Approved   Updated




Approved   Updated


Approved   Updated




Approved   Updated
Approved   Updated




Approved   Updated




Approved   Updated
Approved   Updated




Approved   Updated

Approved   Updated
Approved   Updated
Approved   Updated
Approved   Updated




Approved   Updated
Approved   Updated




Approved   Updated




           Updated


           Updated




           Updated
           Updated
Updated




Updated




Updated
Updated




Updated
Approved   Updated
Updated




Updated




No change
No change




No change




No change




No change




No change




No change
Updated




Updated

Updated
           Updated

           Updated
Approved   Updated
           Updated




Approved   Updated




           Updated




           Updated




           Updated




           Updated

           Updated

Approved   Updated
           Updated


Approved   Updated




           Updated

           Updated

           Updated




           Updated


Approved   Updated




           Updated

Approved   Updated




           Updated

           Updated
Approved   Updated




Approved   Updated




Approved   Updated




           Updated
Updated




Updated




Updated




Updated




Updated

No change
Approved   Updated




Approved   Updated




           Updated




           Updated




           Updated
           Updated




           Updated




           Updated

           Updated

           Updated

           Updated
           Updated




Approved   Updated




           Updated

           Updated

Approved   Updated


           Updated




Approved   Updated




           Updated
           Updated
           Updated


           Updated




Approved   Updated




           Updated

           Updated

           Updated

Approved   Updated




Approved   No change
Approved   Updated




Approved   Updated




           Updated
           Updated




           Updated




           Updated




           Updated


Approved   Updated
Approved   Updated




           Updated




Approved   Updated




Approved   Updated




           Updated




           Updated


           Updated
Approved   Updated




           Updated




           Updated

           Updated
           Updated
Approved   Updated


Approved   Updated




Approved   Updated




           Updated


           Updated


           Updated

           Updated

           Updated


           Updated




           Updated




           Updated

           Updated
           Updated

           Updated


           Updated




Approved   Updated




Approved   Updated




           Updated

           Updated




           Updated
           Updated




           Updated




           Updated


           Updated




           Updated

           Updated


           Updated


           Updated




Approved   Updated
           Updated

Approved   Updated

Approved   Updated

Approved   Updated




           Updated




Approved
Updated


Updated




Updated

Updated




Updated




Updated


Updated

Updated




Updated

Updated




Updated

Updated
           Updated


           Updated




Approved   Updated


Approved   Updated


Approved   Updated




           Updated
           Updated
Approved   Updated




Approved   Updated
Approved   No change
Approved   Updated
Updated


Updated


Updated


Updated




Updated




Updated
Updated




Updated




Updated
Updated




Updated
Updated




Updated

Updated

Updated
Updated




Updated




Updated

Updated
Updated
Updated




Updated




Updated
Updated




Updated
Updated
Updated


Updated
Updated




Updated
Updated

Updated




Updated


Updated




Updated
Updated




Updated




Updated




Updated
Updated




Updated




Updated
Updated




Updated




Updated
Updated
Updated




Updated
Updated


Updated

Updated
Updated


Updated




Updated
Updated
Updated




Updated

No change




Updated




Updated
Approved   Updated




Approved   Updated

Approved   Updated




Approved   Updated


           Updated
Approved   Updated




           Updated




           Updated




Approved   Updated
           Updated


           Updated
           Updated


           Updated




           Updated




Approved   Updated




Approved   Updated




           Updated
           Updated


           Updated




Approved   Updated




Approved   Updated




Approved   Updated




Approved   Updated
Approved   Updated




           Updated
           Updated




           Updated
           Updated


Approved   No change




Approved   Updated


           Updated

           Updated
           Updated


           Updated


Approved   Updated




           Updated
           Updated


           Updated




           Updated
Approved   Updated




           Updated
           Updated


           Updated




           Updated
Approved   No change




           Updated


           Updated




           Updated


           Updated




           Updated




           Updated




           Updated
Updated




Updated
Updated

Updated




Updated




Updated
Updated




Updated

Updated

Updated
Updated

Updated
Approved   Updated




           Updated

           Updated

           Updated


           Updated


           Updated
           Updated


           Updated

           Updated


           Updated
           Updated
           Updated

           Updated


           Updated
Approved   Updated




           Updated




           Updated

           Updated

           Updated
           Updated
Approved   Updated
Approved   Updated
Approved   Updated




Approved   Updated
Approved   Updated
Approved   Updated
Approved   Updated




Approved   Updated
Approved   Updated




Approved   Updated
           Updated




Approved   Updated
Approved   Updated




Approved   Updated

Approved   Updated
Approved   Updated




Approved   Updated
Approved   Updated




Approved   Updated
Approved   Updated




Approved   Updated

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:2/13/2012
language:
pages:742