Docstoc

11-10-1284-05-000m-revmb-sponsor-ballot-comments

Document Sample
11-10-1284-05-000m-revmb-sponsor-ballot-comments Powered By Docstoc
					Month Year                                         Title                doc.: IEEE 802.11-yy/xxxxr0

            IEEE P802.11 Wireless LANs
            Submission
Designator: doc.: IEEE 802.11-10/1284r5
Venue Date: March 2011
First Author:Adrian Stephens, Intel Corporation

Subject:     REVmb Sponsor Ballot Comments
Full Date:   2011-03-11
Author(s):   Name(s) Adrian Stephens
             Company Intel Corporation
             Address

             Phone:
             Fax:
             email:     adrian.p.stephens@intel.com
Abstract:    This document contains comments submitted by voters for the IEEE-SA sponsor ballot on IEEE P802.11 (REVm
             It also contains comments submitted by voters for the 802.11 working group ballot and pre-ballot review on IEE

             It is a composite document in the sense that TGmb comment-resolution ad-hocs may publish spreadsheets contai
             responsible for updating. This document is periodically updated to reflect the status of those spreadsheets.

             The "Comments" tab contains the comments. The LB column identifies the ballot as shown below.
             The comment ID (CID) uniquely identifies the comment, and is allocated according to ballot as follows:

                 Non-Ballot comments
                 LB0, Pre-ballot comments: 1-104
                 LB0, D6.01, WG review of roll-in, 10500-10590

                 Working Group Letter Ballots
                 LB149, D1.0, (i.e. the first working group ballot): 1000 - 1729
                 LB160, D2.0, (the first recirculation ballot): 2000-2245
                 LB162, D3.0, 2nd recirculation ballot: 3000-3148
                 LB163, D4.0, 3rd recirculation ballot: 4000-4097
                 LB167, D5.0, 4th recirculation ballot: 5000-5015

                  Sponsor Ballots
                  LB1000, D6.0, First Sponsor ballot: 10001-10454. Note comments 10183-10454 were submitted in a file a
                  LB1001, D7.0, First Sponsor Recirculation ballot: 11000-11132 and 11200-11243. Note comments 11200
             the ballot period, and comments 11235-11243 were submitted as a file after the ballot period.




Submission                                            1                                     Name, Company
             Month Year                                         Title              doc.: IEEE 802.11-yy/xxxxr0




or ballot on IEEE P802.11 (REVmb).
allot and pre-ballot review on IEEE P802.11REVmb.

s may publish spreadsheets containing a subset of these comments, which they are
status of those spreadsheets.

llot as shown below.
rding to ballot as follows:




  10454 were submitted in a file accompanying comment 10182.
   11243. Note comments 11200-11234 were submitted as attachments /files during
e ballot period.




             Submission                                            2                             Name, Company
Revision Date

       0   2010-11-07
       1   2010-12-07
       2   2011-01-13
       3   2011-02-03
       4   2011-02-20
       5   2011-03-11
       6
       7
       8
       9
      10
      11
      12
      13
      14
      15
      16
      17
      18
      19
      20
      21
      22
      23
      24
      25
      26
      27
      28
      29
Description
Initial version. Contains comments from the initial Sponsor Ballot, and allocation to comment group and ad-
hoc
Addition of comments from TG review of D6.01 roll-in
Resolutions from TG review of D6.01 added
Resolutions approved in Jan 2011 meeting added
Comments from sponsor ballot recirculation 1 added.
Updated with EDITOR and GEN changes prior to March 802.11 session
CID    Commenter          LB     Draft Clause   Page(C)   Line(C) Type of   Part of No   Page
                                        Number(                   Comment   Vote
                                        C)
      1 Adrian Stephens        0      0 11.9    197              T          N              197.00




      2 Adrian Stephens        0    0 11.4     195               T          N              195.00




      3 Adrian Stephens        0    0 9.9.1    113        38     T          N              113.38
4 Adrian Stephens   0   03   1   20   t   N   1.20
5 Adrian Stephens   0   0 9.10.2   116   36   t   N   116.36




6 Adrian Stephens   0   0 9.10.2   116   37   t   N   116.37
7 Adrian Stephens   0   0 7.2.1.1   22    50   T   N    22.50




8 Adrian Stephens   0   0 11.9.6    198   10   T   N   198.10
 9 Adrian Stephens   0   0 Introducti v    17   T   N     0.17
                           on




10 Adrian Stephens   0   0 9.10.4    127   54   T   N   127.54
11 Adrian Stephens   0   03   2   22   T   N   2.22
12 Adrian Stephens   0   03          2   60   T   N   2.60




13 Adrian Stephens   0   0 Annex D            T   N   0.00
14 Adrian Stephens   0   03   2     22   T   N     2.22




15 Adrian Stephens   0   0U   522   1    E   N   522.01
16 Adrian Stephens   0   0 7.1.4      23   3   T   N   23.03




17 Adrian Stephens   0   0 7.3.1.24   48   1   T   N   48.01
18 Adrian Stephens   0   0 9.7a       122   39   T   N   122.39




19 Adrian Stephens   0   0 9.16.1.1   153   30   T   N   153.30




20 Adrian Stephens   0   0 11.2.2.3   209   51   T   N   209.51
21 Adrian Stephens   0   0D           419       27     T   N   419.27




22 Adrian Stephens   0   0 9.9.1.5    128       15     E   N   128.15




23 Krishna Pillai    0   0 17.3.2.1   596              E   N   596.00



24 Peter Ecclesine   0   0 1.2        1                T   N     1.00




25 Bill Marshall     0   0 8.5.1.5.3 26 of      Bottom t   N    26.00
                                     802.11r-   of page
                                     2008




26 Bill Marshall     0   03           5                t   N     5.00
27 Bill Marshall   0   0 5.1.1    23              e   N   23.00




28 Bill Marshall   0   07         59              e   N   59.00




29 Bill Marshall   0   07         59              t   N   59.00




30 Bill Marshall   0   0 7.1.3.5.6 69   first     t   N   69.00
                                        paragra
                                        ph of
                                        7.1.3.5.6

31 Bill Marshall   0   0 7.2.3    80    last     e    N   80.00
                                        sentenc
                                        e of
                                        paragra
                                        ph
                                        starting
                                        "The
                                        frame
                                        body
                                        consists
                                         of…"
32 Bill Marshall   0   0 7.2.3      80            t    N    80.00




33 Bill Marshall   0   0 7.2.3.8    84    first   t    N    84.00
                                          paragra
                                          ph



34 Bill Marshall   0   0 7.2.3.9    84    first   t    N    84.00
                                          paragra
                                          ph




35 Bill Marshall   0   0 7.3.1.4    91    last    t    N    91.00
                                          paragra
                                          ph


36 Bill Marshall   0   0 7.3.1.11   96    final    e   N    96.00
                                          paragra
                                          ph of
                                          7.3.1.11




37 Bill Marshall   0   0B           769           e    N   769.00
38 Bill Marshall     0   0C            783              e   N    783.00




39 Bill Marshall     0   0 G.2         1079   third     e   N   1079.00
                                              line of
                                              poem




40 Clint Chaplin     0   0 17.3.10.1                    T   N




41 Richard Roy       0   0 Table i.1                    E   N




42 Dorothy Stanley   0   0 6.1.3       9      1         T   N      9.01




43 Dorothy Stanley   0   0 7.2.3.1     10     45        T   N     10.45
44 Dorothy Stanley   0   0 7.3.22.10 30    56   T   N   30.56
                           a




45 Dorothy Stanley   0   0 7.3.2.22   26        E   N   26.00




46 Dorothy Stanley   0   0 7.3.2.6              E   N




47 Dorothy Stanley   0   0 7.2.3.6    14   65   E   N   14.65
48 Dorothy Stanley   0   0 7.3.2.31   33   57   T   N   33.57




49 Dorothy Stanley   0   0 7.3.2.31   29   62   T   N   29.62




50 Dorothy Stanley   0   0 7.3.2.31   29   62   T   N   29.62




51 Dorothy Stanley   0   0 7.3.2.31   32        T   N   32.00
52 Dorothy Stanley   0   0 7.3.2.25. 28   47   E   N   28.47
                           3




53 David Cipher      0   0 General             E   N




54 David Cipher      0   0 General             T   N




55 Mark Hamilton     0   0 5.2.4     28        E   N   28.00
56 Mark Hamilton   0   0 6.2.1.3   57-58   T   N    57.00




57 Mark Hamilton   0   0 10.3.10   342     T   N   342.00
58 Mark Hamilton   0   0 802.11k - 128   T   N   128.00
                         11.10.11
59 Mark Hamilton   0   0 9.1.3.1   254   3   T   N   254.03




60 Mark Hamilton   0   0 9.9.3.1   298       T   N   298.00
61 Mark Hamilton   0   0 11.2.1.1   426   T   N   426.00




62 Mark Hamilton   0   0 11.2.1     425   E   N   425.00




63 Mark Hamilton   0   0                      N
64 Matthew Fischer   0   0 7.3.2.15   112   T   N   112.00




65 Matthew Fischer   0   0 10.3.16.2 363    T   N   363.00
                           .2
66 Matthew Fischer   0   0 8.4.4   190   T   N   190.00




67 Matthew Fischer   0   0 5.2.5   29    T   N    29.00
68 Darwin Engwer   0   0M           1165   1         T   N   1165.01




69 John Kenney     0   0 17.3.2.1   596    15        T   N    596.15




70 John Kenney     0   0 17.3.8.1   612    Fig-17-   E   N    612.00
                                           12

71 John Kenney     0   0 17.3.8.3. 613               E   N    613.00
                         2
72 John Kenney   0   0 17.3.10.1 617       T   N   617.00




73 John Kenney   0   0 17.3.11   618-619   T   N   618.00
74 John Kenney   0   0 17.3.11   619             E   N   619.00




75 John Kenney   0   0 17.3.11   620   Fig 17-   T   N   620.00
                                       15
76 John Kenney   0   0 17.3.12   621   T   N   621.00




77 Youko Omori   0   0 7.3.2.4   102   T   N   102.00




78 Youko Omori   0   0 7.2.3.1   80    T   N    80.00
                       Beacon
                       frame
                       format
79 Clint Chaplin   0   0 17.3.10.1 617   first   T   N   617.00
                                         paragra
                                         ph




80 Clint Chaplin   0   0 11A.11.2 89     Table   T   N    89.00
                                         11A-2
                                         row
                                         "802.11
                                         QoS"




81 Clint Chaplin   0   0 8.4.10   24     24     T    N    24.24
82 Clint Chaplin   0   0 11A.1      50        1st     T   N    50.01
                                              paragra
                                              ph

83 Clint Chaplin   0   0 11A.4.2    53               T    N    53.00




84 Clint Chaplin   0   0 11A.4.3    56-57            T    N    56.00




85 Clint Chaplin   0   0 11A.5.2    57-59            T    N    57.00




86 Clint Chaplin   0   0 11A.5.4    61-62            T    N    61.00




87 Clint Chaplin   0   0 11A.5.5    63               T    N    63.00




88 Clint Chaplin   0   0 11A.5.5    63        5th     T   N    63.05
                                              paragra
                                              ph

89 Clint Chaplin   0   0 7.3.2.46   16        2nd     T   N    16.02
                                              paragra
                                              ph




90 Clint Chaplin   0   0 8.5.8.1-   236-242          T    N   236.00
                         8.5.8.4
91 Clint Chaplin   0   0 7.3.2.46   16   16    T   N   16.16




92 Clint Chaplin   0   0 8.4.10     24   25    T   N   24.25




93 Mark Rison      0   0 7.3.1.17   99   12?   T   N   99.12
94 Mark Rison      0   0 7.3.2.30   135   para 7   T   N   135.00




95 Jouni Malinen   0   0 Annex C                   T   N
96 Jouni Malinen   0   0 Clause          T   N
                         16




97 Jouni Malinen   0   0 Clause          T   N
                         14




98 Jouni Malinen   0   0 6.1.2    53     T   N    53.00




99 Jouni Malinen   0   0 8.3.2.4.1 173   T   N   173.00
100 Jouni Malinen   0   0 7.3.2.9    105   E   N   105.00




101 Jouni Malinen   0   0 11.2.1     425   T   N   425.00




102 Jouni Malinen   0   0 18.2.2.2   639   T   N   639.00
103 Adrian Stephens   0   0 7.1.4     T   N




104 Richard Roy       0   0 Annex J   T   N
1000 Armstrong, Lee   149   1 14.6.16   768   51   T   Y   768.51




1001 Ashley, Alex     149   1 9.3.2.2   382   28   T   Y   382.28
1002 Ashley, Alex   149   1 16        819   1    T   Y   819.01




1003 Ashley, Alex   149   1 9.9.1.5   400   13   E   Y   400.13




1004 Ashley, Alex   149   1 11.1.0a   579   7    E   N   579.07


1005 Bagby, David   149   1 General              T   Y
1006 Bagby, David   149   1 General   T   Y




1007 Bagby, David   149   1 14        T   Y   728.01




1008 Bagby, David   149   1 15        T   Y   780.01
1009 Bajko, Gabor   149   1 7.3.2.21. 146   40     T   Y   146.40
                            9




1010 Bajko, Gabor   149   1 7.3.2.22. 171   9-31   T   Y   171.00
                            9
1011 Bajko, Gabor   149   1 7.4.7.8   241   4-34   T   Y   241.00




1012 Bajko, Gabor   149   1 11.10.8.6 649   18     T   Y   649.18




1013 Bajko, Gabor   149   1 7.3.2.22. 171   9-31   T   Y   171.00
                            9
1014 Bajko, Gabor       149   1 7.3.2.31   192   43      T   N   192.43




1015 Bajko, Gabor       149   1 7.3.2.31   193   21      T   N   193.21




1016 Bumiller, George   149   1 Annex 0A 982     18-19   T   N   982.00



1017 Bumiller, George   149   1 Annex 0A 981     29-30   T   N   981.00




1018 Bumiller, George   149   1 Annex 0A 981     41-42   T   N   981.00
1019 Bumiller, George   149   1 Annex 0A 981   48-49   T   N   981.00



1020 Bumiller, George   149   1 Annex 0A 982   4-5     T   N   982.00


1021 Bumiller, George   149   1 Annex 0A 982   29-30   T   N   982.00


1022 Bumiller, George   149   1 Annex 0A 982   56-58   T   N   982.00


1023 Bumiller, George   149   1 Annex 0A 983   1-3     T   N   983.00




1024 Bumiller, George   149   1 Annex 0A 983   6-8     T   N   983.00


1025 Bumiller, George   149   1 Annex 0A 983   14-16   T   N   983.00




1026 Bumiller, George   149   1 Annex 0A 983   25-27   T   N   983.00




1027 Bumiller, George   149   1 Annex 0A 983   29-30   T   N   983.00



1028 Bumiller, George   149   1 Annex 0A 983   32-34   T   N   983.00



1029 Bumiller, George   149   1 Annex 0A 983   36-37   T   N   983.00
1030 Bumiller, George   149   1 Annex 0A 981   57   E   N   981.57




1031 Bumiller, George   149   1 Annex 0A 981        T   N   981.06




1032 Cam-Winget,        149   1 8.1.2   253    42   E   N   253.42
     Nancy




1033 Cam-Winget,        149   1 8.1.3   253    60   T   Y   253.60
     Nancy




1034 Cam-Winget,        149   1 8.1.3   254    64   T   Y   254.64
     Nancy
1035 Cam-Winget,   149   1 8.4.1.1.2 286   51   T   Y   286.51
     Nancy




1036 Cam-Winget,   149   1 8.4.1.1.3 286   60   T   Y   286.60
     Nancy




1037 Cam-Winget,   149   1 8.4.1.1.2 286   45   T   Y   286.45
     Nancy




1038 Cam-Winget,   149   1 8.4.1.2.1 288   51   T   Y   288.51
     Nancy
1039 Cam-Winget,   149   1 8.4.1.2.1 288   58   T   Y   288.58
     Nancy




1040 Cam-Winget,   149   1 8.4.6     292   38   T   Y   292.38
     Nancy




1041 Cam-Winget,   149   1 8.4.6.2   293   55   T   Y   293.55
     Nancy




1042 Cam-Winget,   149   1 8.4.8     295   30   T   Y   295.30
     Nancy
1043 Cam-Winget,   149   1 8.4.10    296   64   T   Y   296.64
     Nancy


1044 Cam-Winget,   149   1 General              T   Y
     Nancy




1045 Cam-Winget,   149   1 8.7.2     353   40   T   Y   353.40
     Nancy
1046 Chan, Douglas      149   1 General                 T   N




1047 Chan, Douglas      149   1 9.9.2.2   405   57-65   E   N   405.00




1048 Ecclesine, Peter   149   1 9.8.0a    390   45      E   N   390.45


1049 Ecclesine, Peter   149   1 9.8.2     391   30      T   N   391.30
1050 Ecclesine, Peter   149   1 9.8.2a     394   28   E   N   394.28




1051 Ecclesine, Peter   149   1 9.8.2      391   25   T   Y   391.25




1052 Ecclesine, Peter   149   1 18.4.6.7   929   38   T   Y   929.38




1053 Ecclesine, Peter   149   1 18.4.6.6   927   19   T   Y   927.19




1054 Ecclesine, Peter   149   1 18.4.6.2   923   30   T   Y   923.30
1055 Ecclesine, Peter   149   1 15.4.6.2   810   18   T   Y    810.18




1056 Ecclesine, Peter   149   1 Annex A    985   4    T   Y    985.04




1057 Ecclesine, Peter   149   1 Annex D 1308     15   T   Y   1308.15
1058 Ecclesine, Peter   149   1 Annex D 1307   46   T   Y   1307.46




1059 Ecclesine, Peter   149   1 Annex D 1316   40   T   Y   1316.40




1060 Ecclesine, Peter   149   1 Annex D 1311   51   T   Y   1311.51
1061 Ecclesine, Peter   149   1 Annex D 1370   2    T   Y   1370.02




1062 Ecclesine, Peter   149   1 Annex D 1380   39   T   Y   1380.39




1063 Ecclesine, Peter   149   1 16      819    1    T   Y    819.01
1064 Ecclesine, Peter   149   1 14        728    1    T   Y    728.01




1065 Ecclesine, Peter   149   1 Annex D 1385     55   T   Y   1385.55




1066 Ecclesine, Peter   149   1 Annex D 1385     22   T   Y   1385.22




1067 Ecclesine, Peter   149   1 Annex E   1421   1    E   Y   1421.01




1068 Ecclesine, Peter   149   1 Annex F   1422   1    T   Y   1422.01
1069 Ecclesine, Peter   149   1 Annex I   1492   9    E   N   1492.09




1070 Ecclesine, Peter   149   1 Annex J   1493   35   E   N   1493.35




1071 Ecclesine, Peter   149   1 Annex J   1494   52   E   N   1494.52


1072 Ecclesine, Peter   149   1 Annex M 1513     1    T   Y   1513.01
1073 Ecclesine, Peter   149   1 11.10.12 654   5   T   Y   654.05




1074 Ecclesine, Peter   149   1 7.5     248    1   E   N   248.01


1075 Ecclesine, Peter   149   1 10      425    1   T   Y   425.01
1076 Ecclesine, Peter   149   1 10.3.0a   427   2   T   Y   427.02




1077 Ecclesine, Peter   149   1 10.3.11   472   1   T   Y   472.01
1078 Ecclesine, Peter   149   1 1.2     2     13   T   Y     2.13




1079 Ecclesine, Peter   149   1 3.159   20    6    T   Y    20.06




1080 Ecclesine, Peter   149   1 3.159   20    5    E   N    20.05




1081 Ecclesine, Peter   149   1 13      726   1    E   Y   726.01
1082 Engwer, Darwin   149   1 6.1.3   64   5    E   Y   64.05




1083 Engwer, Darwin   149   1 6.1.3   64   22   E   Y   64.22
1084 Engwer, Darwin   149   1 6.1.3   64   25   E   Y   64.25




1085 Engwer, Darwin   149   1 6.1.3   64   27   E   Y   64.27
1086 Engwer, Darwin   149   1 general   1     1    E   Y   1.01




1087 Erceg, Vinko     149   1 Contents viii   57   E   N
1088 Erceg, Vinko    149   1 Contents viii        60   E   N




1089 Erceg, Vinko    149   1 Introducti iv        15   E   N
                             on

1090 Erceg, Vinko    149   1 Contents xxxi        43   E   N


1091 Erceg, Vinko    149   1 Contents xxxiv       27   E   N




1092 Erceg, Vinko    149   1 Contents xxxiv       28   E   N


1093 Gast, Matthew   149   1 3.147      19        1    E   N   19.01



1094 Gast, Matthew   149   1 3.4        6         32   T   N    6.32




1095 Gast, Matthew   149   1 7.5        248-252        E   N
1096 Gast, Matthew   149   1 14        728   1    T   N   728.01




1097 Gast, Matthew   149   1 11A.10.1 702    33   T   N   702.33




1098 Gast, Matthew   149   1 7.1.1     71    1    E   N    71.01



1099 Gast, Matthew   149   1 7.1.3.5.1 78    59   E   N    78.59




1100 Gast, Matthew   149   1 7.1.3.5.3 79    42   E   N    79.42




1101 Gast, Matthew   149   1 7.2.2     89    48   E   N    89.48



1102 Gast, Matthew   149   1 7.2.2     89    51   E   N    89.51



1103 Gast, Matthew   149   1 7.2.3.1   92    1    E   N    92.01
1104 Gast, Matthew   149   1 7.2.3.10   102     45   T   N   102.45




1105 Gast, Matthew   149   1 7.3.1.1    104     15   T   N   104.15




1106 Gast, Matthew   149   1 8.2.1.3    257     36   E   N   257.36




1107 Gast, Matthew   149   1C                        T   Y




1108 Gast, Matthew   149   1 Editors    lxxiv   7    E   N
                             notes
1109 Gast, Matthew   149   1 General   T   Y




1110 Gast, Matthew   149   1 General   T   Y




1111 Gast, Matthew   149   1 General   T   Y
1112 Gast, Matthew   149   1 General   T   Y




1113 Gast, Matthew   149   1 General   T   Y
1114 Gast, Matthew   149   1 General   T   Y




1115 Gast, Matthew   149   1 General   T   Y
1116 Gast, Matthew    149   1 General                   E   N




1117 Gast, Matthew    149   1 N.5        1523   20      T   N   1523.20




1118 Gast, Matthew    149   1 Participa vi      21      E   N
                              nts




1119 Gong, Michelle   149   1 11.1.2.1   579    63-64   T   N    579.00
1120 Gong, Michelle   149   1 11.1.2.2   580   33      T   N   580.33




1121 Gong, Michelle   149   1 11.1.2.2   580   45      T   N   580.45




1122 Gong, Michelle   149   1 11.1.2.3   580   64-65   T   N   580.00




1123 Gong, Michelle   149   1 11.1.3     582   36      T   N   582.36
1124 Gong, Michelle   149   1 11.1.3.5   585   28      T   N   585.28



1125 Gong, Michelle   149   1 11.2.1.1   588   7       E   N   588.07




1126 Gong, Michelle   149   1 11.2.1.4   589   36-38   T   N   589.00




1127 Gong, Michelle   149   1 11.2.1.4   590   18-19   T   N   590.18
1128 Gong, Michelle   149   1 11.2.1.5   590   57-60   T   N   590.00




1129 Gong, Michelle   149   1 11.2.1.5   591   4-8     T   N   591.00




1130 Gong, Michelle   149   1 11.2.2.1   595   33-42   E   N   595.00


1131 Gong, Michelle   149   1 11.2.2.1   596   59-65   T   N   596.00
1132 Gong, Michelle   149   1 11.2.2.4   597   54-55   T   N   597.00




1133 Gong, Michelle   149   1 11.3.2.5   605   19      E   N   605.19




1134 Gong, Michelle   149   1 11.4.1     606   39-40   T   N   606.00




1135 Gong, Michelle   149   1 11.4.2     607   16      T   N   607.16




1136 Gong, Michelle   149   1 11.4.4     609   1-26    T   N   609.01




1137 Hamilton, Mark   149   1 Introducti iv    15      T   Y
                              on
1138 Hamilton, Mark   149   1 1.2        1     64   T   Y     1.64




1139 Hamilton, Mark   149   1 11.2.2.1   595   44   E   N   595.44


1140 Hamilton, Mark   149   1 8.4.1.1.3 286    61   T   Y   286.61




1141 Hamilton, Mark   149   1 10.1       425   25   T   Y   425.25




1142 Hamilton, Mark   149   12           3     12   T   N     3.12




1143 Hamilton, Mark   149   1 3.28       8     65   E   N     8.65
1144 Hamilton, Mark   149   1 7.4.8.3    244   40   E   N   244.40




1145 Hamilton, Mark   149   1 11.10.14 657     5    T   Y   657.05




1146 Hamilton, Mark   149   1 11.2.1.4   589   34   T   Y   589.34




1147 Hamilton, Mark   149   1 6.2.3      68    1    T   Y    68.01
1148 Hamilton, Mark   149   1 9.9.3.1    408   33   T   Y   408.33




1149 Hamilton, Mark   149   1 7.1.3.7    82    10   E   N    82.10




1150 Hamilton, Mark   149   1 7.3.2.27   183   58   E   N   183.58
1151 Hamilton, Mark   149   1 7.3.1.11   113   28   T   Y   113.28




1152 Hamilton, Mark   149   1 11.3.0a    598   54   T   Y   598.54




1153 Hamilton, Mark   149   1 10.3.8.1. 463    8    T   Y   463.08
                              1

1154 Hamilton, Mark   149   1 10.3.8.2. 464    23   T   Y   464.23
                              2

1155 Hamilton, Mark   149   1 8.3.2.4.0 271    26   T   Y   271.26
                              a
1156 Hamilton, Mark   149   1 10.3.24.2 507   31   T   Y   507.31
                              .2




1157 Hamilton, Mark   149   1 10.3.29.2 538   21   T   Y   538.21
                              .2




1158 Hamilton, Mark   149   1 10.3.30.2 541   17   T   Y   541.17
                              .2
1159 Hamilton, Mark   149   1 10.3.31.2 544   17   T   Y   544.17
                              .2




1160 Hamilton, Mark   149   1 10.3.32.2 547   28   T   Y   547.28
                              .2




1161 Hamilton, Mark   149   1 11.4.5   610    64   T   Y   610.64
1162 Hamilton, Mark   149   1 9.9.3.1.2 409   22   T   Y   409.22




1163 Hamilton, Mark   149   1 7.3.2.21. 144   27   T   Y   144.27
                              7



1164 Hamilton, Mark   149   1 3.136    18     17   T   Y    18.17




1165 Hamilton, Mark   149   1 3.3      6      23   T   Y     6.23
1166 Hamilton, Mark   149   13          6     1    T   Y     6.01




1167 Hamilton, Mark   149   1 11.10.11 653    48   T   Y   653.48




1168 Hart, Brian      149   1 14        728   1    T   N   728.01




1169 Hart, Brian      149   1 16        819   1    T   N   819.01




1170 Hart, Brian      149   1 17.3.11   866   49   T   N   866.49
1171 Hart, Brian    149   1 17.3.11   868   22   E   N   868.22




1172 Hart, Brian    149   1 15        780   1    T   N   780.01




1173 Hart2, Brian   149   1 14        728   1    T   N   728.01




1174 Hart2, Brian   149   1 16        819   1    T   N   819.01




1175 Hart2, Brian   149   1 17.3.11   866   49   T   N   866.49




1176 Hart2, Brian   149   1 17.3.11   868   22   E   N   868.22
1177 Hart2, Brian   149   1 15         780   1    T   N   780.01




1178 Hart2, Brian   149   1 18.4.6.6   927   20   T   N   927.20




1179 Hart2, Brian   149   1 18.4.6.6   929   40   T   N   929.40




1180 Hart2, Brian   149   1 19.1.2     942   40   T   N   942.40




1181 Hart2, Brian   149   1 19.1.2     942   48   T   N   942.48
1182 Hart3, Brian   149   1 14        728   1    T   Y   728.01




1183 Hart3, Brian   149   1 16        819   1    T   N   819.01




1184 Hart3, Brian   149   1 17.3.11   866   49   T   N   866.49




1185 Hart3, Brian   149   1 17.3.11   868   22   E   N   868.22




1186 Hart3, Brian   149   1 15        780   1    T   Y   780.01
1187 Hart3, Brian   149   1 18.4.6.6   927   20   T   Y   927.20




1188 Hart3, Brian   149   1 18.4.6.6   929   40   T   Y   929.40




1189 Hart3, Brian   149   1 19.1.2     942   40   T   Y   942.40




1190 Hart3, Brian   149   1 19.1.2     942   48   T   Y   942.48




1191 Kennedy,       149   1 9.8.1      391   9    E   N   391.09
     Richard
1192 Kennedy,   149   1 1.3.37.4. 565   20        E   N    565.20
     Richard            2

1193 Kennedy,   149   1 Annex    1063   16 - 25   E   N   1063.00
     Richard            A.4.10




1194 Kennedy,   149   1 Annex    1073   3 - 10    E   N   1073.00
     Richard            A.4.13




1195 Kennedy,   149   1 Annex    1073   12 - 20   E   N   1073.00
     Richard            A.4.13




1196 Kennedy,   149   1 Annex    1073   22 - 30   E   N   1073.00
     Richard            A.4.13
1197 Kennedy,   149   1 Annex    1086   33 - 44   E   N   1086.00
     Richard            A.4.18




1198 Kennedy,   149   1 Annex    1086   46 - 65   E   N   1086.00
     Richard            A.4.18
1199 Kennedy,   149   1 Annex    1087   5 - 26    E   N   1087.00
     Richard            A.4.18




1200 Kennedy,   149   1 Annex    1087   37 - 63   E   N   1087.00
     Richard            A.4.18
1201 Kennedy,   149   1 Annex    1088   4 - 15   E   N   1088.00
     Richard            A.4.18




1202 Kennedy,   149   1 Annex D 1308    16       E   N   1308.16
     Richard            ASN.1



1203 Kennedy,   149   1 Annex I 1488    20       E   N   1488.20
     Richard            Table I.2




1204 Kennedy,   149   1 Annex I 1489    30       E   N   1489.30
     Richard            Table I.3
1205 Kennedy,     149   1 Annex I 1490    36   E   N   1490.36
     Richard              Table !.4




1206 Kennedy,     149   1 Annex I 1490    38   E   N   1490.38
     Richard              Table !.4




1207 Kolze, Tom   149   1 Abstract   ii   1    T   Y
1208 Kolze, Tom          149   1 Introducti iv    22   T   Y
                                 on




1209 Malarky, Alastair   149   1 7.3.2.25. 179    41   T   Y   179.41
                                 1




1210 Malarky, Alastair   149   1 7.3.2.26   183   37   T   Y   183.37
1211 Malarky, Alastair   149   1 7.3.2.26   183   37   T   Y   183.37




1212 Malarky, Alastair   149   1 7.4.5      228   15   T   Y   228.15




1213 Malarky, Alastair   149   1 7.4.5      228   34   T   Y   228.34
1214 Malarky, Alastair   149   1 General              T   Y




1215 Malinen, Jouni      149   1 10.3.19.1 498   33   E   Y   498.33
                                 .2
1216 Malinen, Jouni   149   1 J.1       1493        T   Y   1493.12




1217 Marshall, Bill   149   1 7.2.3.1   93     58   E   N     93.58




1218 Marshall, Bill   149   1 7.2.3.4   95     4    E   N     95.04
1219 Marshall, Bill   149   1 7.2.3.4    95    7    E   N    95.07




1220 Marshall, Bill   149   1 7.2.3.5    95    62   E   N    95.62


1221 Marshall, Bill   149   1 7.2.3.7    98    32   E   N    98.32




1222 Marshall, Bill   149   1 7.2.3.10   102   63   E   N   102.63




1223 Marshall, Bill   149   1 7.4.8      242   50   E   N   242.50




1224 Marshall, Bill   149   1 7.5        248   1    E   N   248.01


1225 Marshall, Bill   149   1 8.4.1.1.2 286    36   T   N   286.36




1226 Marshall, Bill   149   1 8.5.1.5.2 305    65   E   N   305.65
1227 Marshall, Bill   149   1 8.5.1.5.3 306    62   T   N    306.62




1228 Marshall, Bill   149   1 8.5.1.5.5 307    32   E   N    307.32




1229 Marshall, Bill   149   1 8.5.2     310    5    E   N    310.05




1230 Marshall, Bill   149   1 11.4.3    608    7    E   N    608.07




1231 Marshall, Bill   149   1 11A.3     668    17   T   N    668.17



1232 Marshall, Bill   149   1 11A.4.2   668    63   E   N    668.63




1233 Marshall, Bill   149   1 11A.4.2   670    31   T   N    670.31




1234 Marshall, Bill   149   1 11A.8.1   687    6    E   N    687.06


1235 Marshall, Bill   149   1D          1307   52   E   N   1307.52
1236 Marshall, Bill   149   1D           1307   64   E   N   1307.64




1237 McCann,          149   1 6.2.1.2    66     1    T   N     66.01
     Stephen




1238 McCann,          149   1 7.3.2.35   196    1    E   N    196.01
     Stephen
1239 McCann,   149   1 Annex D 1105     E   N   1105.00
     Stephen




1240 McCann,   149   1 Annexes 981      E   N    981.00
     Stephen




1241 McCann,   149   1 Annex C 1105     E   N   1105.01
     Stephen


1242 McCann,   149   1 Annex E   1421   E   N   1421.01
     Stephen
1243 McCann,   149   1 5.1a      30    20   T   N    30.20
     Stephen




1244 McCann,   149   1 5.2.3     32    50   E   N    32.50
     Stephen




1245 McCann,   149   1 5.2.3.1   34    22   E   N    34.22
     Stephen




1246 McCann,   149   1 5.4.4.1   50    3    T   N    50.03
     Stephen




1247 McCann,   149   1 7.3.2.25. 179   40   T   N   179.40
     Stephen           1
1248 McCann,   149   1 7.3.2.27   184   1, 45   E   N   184.00
     Stephen




1249 McCann,   149   1 7.3.2.27   184   1, 45   E   N   184.00
     Stephen




1250 McCann,   149   1 11.11.1    657   44      E   N   657.44
     Stephen
1251 Montemurro,   149   1 7.3.2.48   211   44   T   N   211.44
     Michael




1252 Montemurro,   149   1 7.3.1.7    109   14   T   N   109.14
     Michael




1253 Montemurro,   149   1 7.3.2.22. 160    45   T   N   160.45
     Michael               6


1254 Montemurro,   149   1 8.1.0a     253   7    T   N   253.07
     Michael
1255 Montemurro,   149   1 8.5.3.0a   317   41   T   N   317.41
     Michael




1256 Montemurro,   149   1 11.10.8.1 644    59   T   N   644.59
     Michael




1257 Montemurro,   149   1 11A.9.5.1 700    15   T   N   700.15
     Michael




1258 Montemurro,   149   1 8.5.2      310   5    T   N   310.05
     Michael
1259 Montemurro,   149   1 7.3.2.48   212   13   T   N   212.13
     Michael




1260 Montemurro,   149   1 8.5.3.2    320   23   T   N   320.23
     Michael
1261 Montemurro,   149   1 8.5.3.3   321   49   T   N   321.49
     Michael




1262 Montemurro,   149   1 7.3.2.21. 151   35   T   N   151.35
     Michael               10




1263 Montemurro,   149   1 11.10.8.8 651   46   T   N   651.46
     Michael
1264 Myles, Andrew   149   1 General   T   Y




1265 Myles, Andrew   149   1 General   T   N




1266 Myles, Andrew   149   1 10        T   Y   425.01
1267 Myles, Andrew   149   1 16               T   Y   819.01




1268 Myles, Andrew   149   1C                 T   Y




1269 Myles, Andrew   149   1 11.9.7.2   632   T   Y   632.51
1270 Myles, Andrew    149   1N                   T   Y




1271 Myles, Andrew    149   1E                   T   Y




1272 Myles, Andrew    149   1F                   T   Y




1273 Myles, Andrew    149   1O                   T   Y




1274 Myles, Andrew    149   1P                   T   Y




1275 Perahia, Eldad   149   1 14       728   1   T   Y   728.01




1276 Perahia, Eldad   149   1 12.3.4   712   1   E   N   712.01
1277 Perahia, Eldad   149   1 12.3.4.4   713   26   T   N   713.26




1278 Perahia, Eldad   149   1 12.3.5.4. 717    18   T   N   717.18
                              2




1279 Perahia, Eldad   149   1 12.3.5.10 723    35   T   N   723.35
                              .3




1280 Perahia, Eldad   149   1 12.3.5.10 723    35   T   N   723.35
                              .3




1281 Perahia, Eldad   149   1 17.3.2.4   842   51   E   N   842.51




1282 Perahia, Eldad   149   1 17.3.2.4   843   10   E   N   843.10


1283 Perahia, Eldad   149   1 17.3.3     846   7    E   N   846.07
1284 Perahia, Eldad   149   1 17.3.3     846   31   E   N   846.31


1285 Perahia, Eldad   149   1 17.3.4.3   848   7    T   Y   848.07




1286 Perahia, Eldad   149   1 17.3.8.1   857   22   T   N   857.22




1287 Perahia, Eldad   149   1 17.3.9.7   862   64   T   N   862.64


1288 Perahia, Eldad   149   1 17.3.9.7   862   64   E   N   862.64
1289 Perahia, Eldad   149   1 17.3.10.5 865   20   T   Y   865.20
1290 Perahia, Eldad   149   1 17.3.12   869   55   T   Y   869.55




1291 Perahia, Eldad   149   1 17.3.12   870   24   T   Y   870.24
1292 Perahia, Eldad   149   1 17.4.3   873   46   T   N   873.46




1293 Perahia, Eldad   149   1 17.5     874   1    T   N   874.01




1294 Perahia, Eldad   149   1 19.4.6   956   21   T   Y   956.21




1295 Perahia, Eldad   149   1 19.5.4   958   21   E   N   958.21
1296 Perahia, Eldad     149   1 19.9.5.0a 976    38   E   N    976.38


1297 Perahia, Eldad     149   1 19.9.5.0a 976    46   E   N    976.46


1298 Perahia, Eldad     149   1 19.9.5.0a 978    17   E   N    978.17


1299 Perahia, Eldad     149   1 I.1       1487   26   E   N   1487.26


1300 Perahia, Eldad     149   1 I.2.2     1490   38   T   Y   1490.38




1301 Perahia, Eldad     149   1 J.1       1494   1    T   Y   1494.01




1302 Perahia, Eldad     149   1 J.1       1495   21   E   N   1495.21


1303 Perahia, Eldad     149   1 J.1       1496   55   E   N   1496.55


1304 Ptasinski, Henry   149   1 General   1      1    T   Y      1.01




1305 Ptasinski, Henry   149   1 11A.8.4   689    7    T   Y    689.07


1306 Ptasinski, Henry   149   1 11A.8.5   690    4    T   Y    690.04
1307 Purnadi, Rene   149   1 7.3.2.47   210   12   T   N    210.12




1308 Purnadi, Rene   149   1 7.4.7.2    235   13   E   N    235.13


1309 Purnadi, Rene   149   1 Annex Q 1540     7    T   N   1540.07




1310 Purnadi, Rene   149   1 Annex Q 1554     44   T   N   1554.44




1311 Purnadi, Rene   149   1 Annex Q 1560     15   T   N   1560.15




1312 Purnadi, Rene   149   1 Annex Q 1564     63   T   N   1564.63




1313 Purnadi, Rene   149   1 Annex Q 1566     4    T   N   1566.04




1314 Purnadi, Rene   149   1 Annex Q 1568     21   T   N   1568.21




1315 Purnadi, Rene   149   1 Annex Q 1569     35   T   N   1569.35
1316 Purnadi, Rene   149   1 Annex Q 1581   1    T   N   1581.01




1317 Purnadi, Rene   149   1 Annex Q 1585   59   T   N   1585.59




1318 Purnadi, Rene   149   1 Annex Q 1590   30   T   N   1590.30




1319 Purnadi, Rene   149   1 Annex Q 1590   58   T   N   1590.58




1320 Purnadi, Rene   149   1 Annex Q 1596   62   T   N   1596.62




1321 Qi, Emily       149   17        248         E   N    248.00
1322 Qi, Emily   149   1 7.4.6.3   230   62   T   Y   230.62




1323 Qi, Emily   149   1 10.3.32   545   15   T   Y   545.15




1324 Qi, Emily   149   1 10.3.32   545   15   T   Y   545.15




1325 Qi, Emily   149   1 7.4.6.5   232   48   T   Y   232.48
1326 Qi, Emily   149   1 7.4.7.2   235   55   T   Y   235.55




1327 Qi, Emily   149   1 7.3.2     118   38   T   Y   118.38




1328 Qi, Emily   149   1 7.3.2     119   44   T   Y   119.44




1329 Qi, Emily   149   1 10.3.25   517   23   T   Y   517.23




1330 Qi, Emily   149   1 10.3.27   526   1    T   Y   526.01
1331 Qi, Emily   149   1 7.4.5    228    11   T   Y   228.11




1332 Qi, Emily   149   1 5.3.1    42     38   T   Y    42.38




1333 Qi, Emily   149   1 10.3.29.1 537   36   T   Y   537.36




1334 Qi, Emily   149   1 10.3.35.3 557   6    T   Y   557.06
1335 Qi, Emily     149   1 10.3.15.3 490    25   T   Y   490.25




1336 Ramamurthy,   149   1 9.13       420   58   T   N   420.58
     Harish




1337 Ramamurthy,   149   1 11.1.2.3   580   64   T   Y   580.64
     Harish
1338 Ramamurthy,   149   1 9.4   386   53   T   Y   386.53
     Harish




1339 Ramamurthy,   149   1 9.4   386   53   T   Y   386.53
     Harish
1340 Ramamurthy,   149   1 11.1.3.2. 583    31   E   N   583.31
     Harish                1




1341 Ramamurthy,   149   1 11.2.1.5   591   46   T   N   591.46
     Harish
1342 Ramamurthy,   149   1 11.3       599-600        T   N
     Harish




1343 Ramamurthy,   149   1 11.2.2.1   595       44   E   N   595.44
     Harish

1344 Ramamurthy,   149   1 9.4        386       65   T   Y   386.65
     Harish
1345 Ramamurthy,   149   1 9.2.5.4   370   59   T   Y   370.59
     Harish




1346 Ramamurthy,   149   1 9.9.1.2   396   39   T   N   396.39
     Harish
1347 Ramamurthy,   149   1 9.9.1.5   400   13   E   N   400.13
     Harish




1348 Ramamurthy,   149   1 9.9.1.5   400   17   E   N   400.17
     Harish




1349 Ramamurthy,   149   1 9.10.3    413   47   E   N   413.47
     Harish
1350 Ramamurthy,   149   1 9.10.3   413   27   T   Y   413.27
     Harish




1351 Ramamurthy,   149   1 7.1.3.1.7 75   1    E   N    75.01
     Harish




1352 Ramamurthy,   149   1 7.5      246   47   T   Y   246.47
     Harish
1353 Ramamurthy,    149   1 9.1.3.1    360       26      T   N   360.26
     Harish




1354 Ramamurthy,    149   1 9.1.3.1    360       20-29   T   Y   360.20
     Harish




1355 Rosdahl, Jon   149   1 7.3.2.21   134       49      E   Y   134.49




1356 Rosdahl, Jon   149   1 11.9.6     631       49      E   Y   631.49




1357 Rosdahl, Jon   149   1 11.3       599-606           T   Y
1358 Rosdahl, Jon   149   1 7, 11, etc.                     E   Y




1359 Rosdahl, Jon   149   1 3.163,        20, 13   20, 35   T   Y
                            3.87
1360 Rosdahl, Jon   149   1 7.2.3.0a   90   60   T   Y   90.60
1361 Rosdahl, Jon   149   1 7.2.3.1    191        T   Y   191.00




1362 Rosdahl, Jon   149   1 11.2.1.1   588        T   Y   588.00




1363 Rosdahl, Jon   149   1 7.1.3.3.3 77     15   T   Y    77.15
1364 Rosdahl, Jon   149   1 11.2.1.0a 586     53   T   Y   586.53




1365 Rosdahl, Jon   149   1 11.2.1.0a 587     1    T   Y   587.01




1366 Rosdahl, Jon   149   1 7.3.1.11    113   28   T   Y   113.28




1367 Rosdahl, Jon   149   1 10.3.33,               E   N
                            10.3.34
                            and
                            others




1368 Rosdahl, Jon   149   1 7, 9, 11,              E   Y
                            etc.
1369 Rosdahl, Jon   149   1 Annex C,              T   Y
                            E, & P




1370 Sakoda,        149   13           16    50   T   N    16.50
     Kazuyuki




1371 Sakoda,        149   1 7.2.3.2    94    14   E   N    94.14
     Kazuyuki



1372 Sakoda,        149   1 11.2.2.1   595   44   E   N   595.44
     Kazuyuki
1373 Sakoda,          149   1 A.4.4.2   1006   21   T   N   1006.21
     Kazuyuki




1374 Stacey, Robert   149   1 5.4.2.1   45     29   E   N     45.29


1375 Stacey, Robert   149   1 7.1.0a    70     21   E   N     70.21




1376 Stacey, Robert   149   1 7.2.1.1   83     46   T   Y     83.46




1377 Stacey, Robert   149   1 7.1.3.3.3 77     17   E   N     77.17
1378 Stacey, Robert   149   1 7.1.3.5.4 80   30   E   N   80.30




1379 Stacey, Robert   149   1 7.1.3.5.6 80   58   T   N   80.58




1380 Stacey, Robert   149   1 7.2.2    88    28   E   N   88.28
1381 Stacey, Robert   149   1 7.2.2      88   28   T   Y   88.28




1382 Stacey, Robert   149   1 7.2.3.0a   90   35   T   Y   90.35




1383 Stacey, Robert   149   1 7.2.3.1    92   37   E   N   92.37
1384 Stacey, Robert   149   1 7.3.1.4   106   56   T   Y   106.56




1385 Stacey, Robert   149   1 7.3.1.4   107   6    T   Y   107.06
1386 Stacey, Robert   149   1 7.3.1.4    107   52   T   Y   107.52




1387 Stacey, Robert   149   1 7.3.1.4    107   48   E   Y   107.48



1388 Stacey, Robert   149   1 7.3.1.11   112   58   T   N   112.58



1389 Stacey, Robert   149   1            120   52   E   N   120.52




1390 Stacey, Robert   149   1 9.14.0d    423   27   T   Y   423.27
1391 Stanley, Dorothy   149   1 7.3.2.40   202   5    T   N   202.05




1392 Stanley, Dorothy   149   1 7.3.2.22. 173    54   T   N   173.54
                                8
1393 Stephens, Adrian   149   1C        1105        E   N   1105.00




1394 Stephens, Adrian   149   1         10     10   E   N     10.10


1395 Stephens, Adrian   149   1         12     33   E   N     12.33




1396 Stephens, Adrian   149   1         12     60   E   N     12.60


1397 Stephens, Adrian   149   1         13     16   E   N     13.16


1398 Stephens, Adrian   149   1         9      36   E   N      9.36


1399 Stephens, Adrian   149   1         12     18   E   N     12.18



1400 Stephens, Adrian   149   1         12     64   E   N     12.64



1401 Stephens, Adrian   149   1 3.88    13     41   E   N     13.41


1402 Stephens, Adrian   149   1 3.104   15     51   E   N     15.51



1403 Stephens, Adrian   149   1 3.113   16     20   E   N     16.20




1404 Stephens, Adrian   149   1 3.133   17     64   E   N     17.64
1405 Stephens, Adrian   149   1 3.136   18     17   E   N     18.17




1406 Stephens, Adrian   149   1 3.151   19     27   E   N     19.27



1407 Stephens, Adrian   149   1 3.169   20     53   E   N     20.53




1408 Stephens, Adrian   149   1 3.159   20     5    E   N     20.05


1409 Stephens, Adrian   149   1 Annex C 1105   1    T   N   1105.01




1410 Stephens, Adrian   149   14        24     44   E   N     24.44




1411 Stephens, Adrian   149   14        24     62   E   N     24.62
1412 Stephens, Adrian   149   1 General             T   N




1413 Stephens, Adrian   149   1 5.2.3.2   34   32   E   N   34.32



1414 Stephens, Adrian   149   1 5.2.5     37   3    T   N   37.03
1415 Stephens, Adrian   149   1 5.2.6   37   29   T   N   37.29




1416 Stephens, Adrian   149   1 5.2.7   38   34   E   N   38.34




1417 Stephens, Adrian   149   1 5.2.7   38   65   T   N   38.65




1418 Stephens, Adrian   149   1 5.3.2   43   6    T   N   43.06
1419 Stephens, Adrian   149   1 5.4.1.1   44   41   T   N   44.41




1420 Stephens, Adrian   149   1 5.4.1.2   44   49   T   N   44.49
1421 Stephens, Adrian   149   15                  T   N   30.01




1422 Stephens, Adrian   149   1 5.4.3   47   14   T   N   47.14
1423 Stephens, Adrian   149   1 5.4.3.1   48   1    T   N   48.01




1424 Stephens, Adrian   149   1 5.7       53   39   T   N   53.39
1425 Stephens, Adrian   149   1 5.7      53     26   T   N    53.26




1426 Stephens, Adrian   149   1 10.3.29.1 537   10   T   N   537.10
1427 Stephens, Adrian   149   1 5.8.3.3   59    28   T   N    59.28




1428 Stephens, Adrian   149   1 6.1.5     65    1    E   N    65.01


1429 Stephens, Adrian   149   1 7.3.2.25. 179   47   T   N   179.47
                                1
1430 Stephens, Adrian   149   1 10.1      425   14   T   N   425.14




1431 Stephens, Adrian   149   1 10.1      426   1    T   N   426.01




1432 Stephens, Adrian   149   1 10.3.0a   427   1    T   N   427.01




1433 Stephens, Adrian   149   1 11.10.12 654    28   T   N   654.28
1434 Stephens, Adrian   149   1 10.3.2.2. 431   34   T   N   431.34
                                2




1435 Stephens, Adrian   149   1 10.3.2.2. 432   8    T   N   432.08
                                2




1436 Stephens, Adrian   149   1 10.3.2.2. 432   31   T   N   432.31
                                2




1437 Stephens, Adrian   149   1 10.3.2.2. 431   50   T   N   431.50
                                2
1438 Stephens, Adrian   149   1 10.3.2.2. 434    25   T   N   434.25
                                2




1439 Stephens, Adrian   149   1 10.3.2.2. 432    48   E   N   432.48
                                2

1440 Stephens, Adrian   149   1 10                    E   N   425.01




1441 Stephens, Adrian   149   1 10.3.6.3   450   23   E   N   450.23
1442 Stephens, Adrian   149   1 8.2.2.3.0 260    48   T   N   260.48
                                a




1443 Stephens, Adrian   149   1 10                    T   N   425.01




1444 Stephens, Adrian   149   1 11.3.0a    600   5    T   N   600.05




1445 Stephens, Adrian   149   1 11.3.2.5   605   8    T   N   605.08




1446 Stephens, Adrian   149   1 11.3.2.5   605   26   T   N   605.26
1447 Stephens, Adrian   149   1 11.10.5   640    19   T   N    640.19




1448 Stephens, Adrian   149   1           1317   12   E   N   1317.12




1449 Stephens, Adrian   149   1 10.3.9.1. 466    30   T   N    466.30
                                2




1450 Stephens, Adrian   149   1 10.3.9.2. 467    18   T   N    467.18
                                2
1451 Stephens, Adrian   149   1 Annex D             T   N   1307.01




1452 Stephens, Adrian   149   1 Annex D             T   N   1307.01




1453 Stephens, Adrian   149   1 10.3.10a. 471   5   T   N    471.05
                                1.3
1454 Stephens, Adrian   149   1 10.3.11   472   61   T   N   472.61




1455 Stephens, Adrian   149   1 10.3.11   476   30   T   N   476.30




1456 Stephens, Adrian   149   1 10.3.13.2 483   37   E   N   483.37
                                .2


1457 Stephens, Adrian   149   1 10.3.16.2 493   11   T   N   493.11
                                .2




1458 Stephens, Adrian   149   1 10.3.17.1 494   46   T   N   494.46
                                .2




1459 Stephens, Adrian   149   1 10.3.19.1 498   50   T   N   498.50
                                .4
1460 Stephens, Adrian   149   1 10.3.22.1 502   56   T   N   502.56
                                .4




1461 Stephens, Adrian   149   1 10.3.22.1 502   54   E   N   502.54
                                .4

1462 Stephens, Adrian   149   1 10.3.23.1 504   26   T   N   504.26
                                .2




1463 Stephens, Adrian   149   1 10.3.24.1 505   38   E   N   505.38
                                .1

1464 Stephens, Adrian   149   1 10.3.24.1 506   17   E   N   506.17
                                .2




1465 Stephens, Adrian   149   1 10.3.24.7 516   46   E   N   516.46
                                .3




1466 Stephens, Adrian   149   1 10.3.25.2 518   36   T   N   518.36
                                .2
1467 Stephens, Adrian   149   1 10.3.27.5 531   46   T   N   531.46
                                .4




1468 Stephens, Adrian   149   1 General              E   N



1469 Stephens, Adrian   149   1 10.3.30.3 542   28   T   N   542.28
                                .4




1470 Stephens, Adrian   149   1 10.3.31.2 544   39   T   N   544.39
                                .4




1471 Stephens, Adrian   149   1 10.3.31.3 545   32   E   N   545.32
                                .2

1472 Stephens, Adrian   149   1 10                   E   N   425.01


1473 Stephens, Adrian   149   1 10.3.33.6 552   49   E   N   552.49
                                .2
1474 Stephens, Adrian   149   1 10.4.1.1   569   16   T   N   569.16




1475 Stephens, Adrian   149   1 11.1.0a    579   7    E   N   579.07


1476 Stephens, Adrian   149   1 11.1.0a    579   9    T   N   579.09




1477 Stephens, Adrian   149   1 11.1.1     579   16   T   N   579.16



1478 Stephens, Adrian   149   1 General               T   N




1479 Stephens, Adrian   149   1 11.1.2.1   580   20   T   N   580.20
1480 Stephens, Adrian   149   1 11.1.2.1   580   1    T   N   580.01




1481 Stephens, Adrian   149   1 11.1.3.0a 582    23   E   N   582.23


1482 Stephens, Adrian   149   1 11.1.3.2. 583    32   T   N   583.32
                                1




1483 Stephens, Adrian   149   1 11.1.3.2. 583    34   T   N   583.34
                                1




1484 Stephens, Adrian   149   1 11.1.3.2. 583    58   T   N   583.58
                                2
1485 Stephens, Adrian   149   1 11.2.1.3   588   27   T   N   588.27




1486 Stephens, Adrian   149   1 11.2.1.4   590   19   T   N   590.19




1487 Stephens, Adrian   149   1 11.2.1.5   590   51   T   N   590.51




1488 Stephens, Adrian   149   1 11.2.1.5   591   14   T   N   591.14
1489 Stephens, Adrian   149   1 11.2.1.5   591   36   E   N   591.36


1490 Stephens, Adrian   149   1 11.2.1.5   591   37   T   N   591.37




1491 Stephens, Adrian   149   1 11.2.1.5   591   39   T   N   591.39




1492 Stephens, Adrian   149   1 11.2.1.5   591   50   T   N   591.50




1493 Stephens, Adrian   149   1 11.2.1.5   592   8    T   N   592.08




1494 Stephens, Adrian   149   1 11.2.1.5   592   30   T   N   592.30
1495 Stephens, Adrian   149   1 11.2.1.5   590   51   T   N   590.51




1496 Stephens, Adrian   149   1 11.2.1.6   593   21   T   N   593.21




1497 Stephens, Adrian   149   1 11.2.1.6   593   33   T   N   593.33




1498 Stephens, Adrian   149   1 11.2.1.9   594   62   T   N   594.62




1499 Stephens, Adrian   149   1 11.2.1.9   594   64   T   N   594.64




1500 Stephens, Adrian   149   1 11.2.1.9   595   2    T   N   595.02
1501 Stephens, Adrian   149   1 11.2.2.1   595   30   T   N   595.30




1502 Stephens, Adrian   149   1 11.2.2.1   596   19   T   N   596.19




1503 Stephens, Adrian   149   1 11.2.2.4   598   1    E   N   598.01




1504 Stephens, Adrian   149   1 11.2.2.4   598   12   T   N   598.12
1505 Stephens, Adrian   149   1 11.2.2.4   598   15   T   N   598.15




1506 Stephens, Adrian   149   1 11.2.2.4   598   41   T   N   598.41




1507 Stephens, Adrian   149   1 11.3.0a    600   30   T   N   600.30
1508 Stephens, Adrian   149   1 11.3.0a    600   42   T   N   600.42




1509 Stephens, Adrian   149   1 11.3.2.1   603   4    T   N   603.04




1510 Stephens, Adrian   149   1 11.5.3     618   65   T   N   618.65
1511 Stephens, Adrian   149   1 11.4.1   607   5    E   N   607.05


1512 Stephens, Adrian   149   1 11.4.2   607   18   T   N   607.18




1513 Stephens, Adrian   149   1 11.4.4   608   36   E   N   608.36



1514 Stephens, Adrian   149   1 11.6.1   619   28   T   N   619.28




1515 Stephens, Adrian   149   1 11.6.1   619   56   T   N   619.56
1516 Stephens, Adrian   149   1 11.6.2     620   19   T   N   620.19




1517 Stephens, Adrian   149   1 11.7.0a    620   42   T   N   620.42




1518 Stephens, Adrian   149   1 11.7.0a    621   39   E   N   621.39



1519 Stephens, Adrian   149   1 11.7.1.2   622   63   E   N   622.63
1520 Stephens, Adrian   149   1 General              T   N




1521 Stephens, Adrian   149   1 11.9.6    631   45   E   N   631.45


1522 Stephens, Adrian   149   1 11.7.5    626   5    E   N   626.05


1523 Stephens, Adrian   149   1 11.9.0a   629   1    E   N   629.01



1524 Stephens, Adrian   149   1 General              E   N




1525 Stephens, Adrian   149   1 11.9.0a   629   30   T   N   629.30



1526 Stephens, Adrian   149   1 11.9.2    630   11   T   N   630.11




1527 Stephens, Adrian   149   1 11.9.3    630   33   T   N   630.33
1528 Stephens, Adrian   149   1 11.9.6    630   53   T   N   630.53




1529 Stephens, Adrian   149   1 General              E   N




1530 Stephens, Adrian   149   1 11.10.8.4 647   62   E   N   647.62
1531 Stephens, Adrian   149   1 11.10.8.4 648   24   T   N   648.24



1532 Stephens, Adrian   149   1 11.10.8.6 649   28   T   N   649.28




1533 Stephens, Adrian   149   1 11.10.8.8 651   28   T   N   651.28




1534 Stephens, Adrian   149   1 11.10.9   652   18   T   N   652.18




1535 Stephens, Adrian   149   1 General              E   N
1536 Stephens, Adrian   149   1          653    1    T   N   653.01




1537 Stephens, Adrian   149   1 11.10.10 653    33   E   N   653.33
                                a

1538 Stephens, Adrian   149   1 11.10.11 653    50   T   N   653.50




1539 Stephens, Adrian   149   1 11.10.12. 655   23   E   N   655.23
                                1

1540 Stephens, Adrian   149   1 11.10.12. 655   49   E   N   655.49
                                1

1541 Stephens, Adrian   149   1 11.10.13 656    52   E   N   656.52
1542 Stephens, Adrian   149   1 11.10.13 656    53   T   N   656.53


1543 Stephens, Adrian   149   1 11.11.1   657   55   T   N   657.55




1544 Stephens, Adrian   149   1 11.11.2.2 659   5    T   N   659.05




1545 Stephens, Adrian   149   1 11.11.2.3 659   58   T   N   659.58
1546 Stephens, Adrian   149   1 11.11.2.3 659   58   T   N   659.58




1547 Stephens, Adrian   149   1 11.11.2.4 660   3    T   N   660.03




1548 Stephens, Adrian   149   1 11.11.2.2 659   21   T   N   659.21
1549 Stephens, Adrian   149   1 11.11.2.4 660   24   T   N   660.24




1550 Stephens, Adrian   149   1 11.11.3   661   4    T   N   661.04




1551 Stephens, Adrian   149   1 11A.1     665   41   T   N   665.41




1552 Stephens, Adrian   149   1 12.3.5.7. 720   22   T   N   720.22
                                3
1553 Stephens, Adrian   149   1 12.3.5.11 724   6    T   N   724.06
                                .1




1554 Stephens, Adrian   149   1 12.3.5.12 725   17   E   N   725.17
                                .2



1555 Stephens, Adrian   149   1 12.3.5.12 725   52   T   N   725.52
                                .3
1556 Stephens, Adrian   149   1 Clause               T   N   941.01
                                19




1557 Stephens, Adrian   149   1 A.4.4.1   992   23   T   N   992.23
1558 Stephens, Adrian   149   1 A.4.4.1   995    39   T   N    995.39




1559 Stephens, Adrian   149   1 A.4.2     989    24   E   N    989.24




1560 Stephens, Adrian   149   1 General               T   N




1561 Stephens, Adrian   149   1 A.4.4.4   1010   20   E   N   1010.20


1562 Stephens, Adrian   149   1 A.4.8     1051   42   E   N   1051.42
1563 Stephens, Adrian   149   1 Annex A              E   N    985.01




1564 Stephens, Adrian   149   1 Annex A   1089   1   E   N   1089.01




1565 Stephens, Adrian   149   1 Annex C 1105     1   T   N   1105.01




1566 Stephens, Adrian   149   1 Annex E   1421   1   T   N   1421.01
1567 Stephens, Adrian   149   1 Annex F   1423   1    T   N   1423.01




1568 Stephens, Adrian   149   1 K.3.2     1501   40   T   N   1501.40




1569 Stephens, Adrian   149   1 K.3.2     1502   48   E   N   1502.48


1570 Stephens, Adrian   149   1 K.3.2     1502   58   E   N   1502.58
1571 Stephens, Adrian   149   1 K.3.2   1504   34   E   N   1504.34




1572 Stephens, Adrian   149   1 K.3.2   1505   41   E   N   1505.41


1573 Stephens, Adrian   149   1 N.2     1518   44   T   N   1518.44




1574 Stephens, Adrian   149   1         1533        E   N   1533.00


1575 Stephens, Adrian   149   1Q        1535   22   T   N   1535.22



1576 Stephens, Adrian   149   1Q        1535   23   T   N   1535.23
1577 Stephens, Adrian   149   1Q   1535   33   T   N   1535.33




1578 Stephens, Adrian   149   1Q   1537   26   T   N   1537.26




1579 Stephens, Adrian   149   1Q   1540   34   E   N   1540.34


1580 Stephens, Adrian   149   1Q   1541   16   E   N   1541.16



1581 Stephens, Adrian   149   1Q   1543   25   T   N   1543.25



1582 Stephens, Adrian   149   1Q   1544   48   E   N   1544.48


1583 Stephens, Adrian   149   1Q   1588   29   E   N   1588.29



1584 Stephens, Adrian   149   1Q   1588   63   E   N   1588.63
1585 Stephens, Adrian   149   1Q   1599        T   N   1599.00




1586 Stephens, Adrian   149   1D   1307   51   E   N   1307.51




1587 Stephens, Adrian   149   1D   1308   54   T   N   1308.54



1588 Stephens, Adrian   149   1D   1345   40   T   N   1345.40
1589 Stephens, Adrian   149   1D               T   N




1590 Stephens, Adrian   149   1D   1351   35   T   N   1351.35




1591 Stephens, Adrian   149   1D   1352   42   E   N   1352.42




1592 Stephens, Adrian   149   1D   1376   54   E   N   1376.54
1593 Stephens, Adrian   149   1D   1378   34   T   N   1378.34




1594 Stephens, Adrian   149   1D   1396   23   T   N   1396.23




1595 Stephens, Adrian   149   1D               T   N
1596 Stephens, Adrian   149   1D                      E   N




1597 Stephens, Adrian   149   1D          1403   22   T   N   1403.22




1598 Stephens, Adrian   149   1 General               E   N
1599 Stephens, Adrian   149   1D          1408   63   T   N   1408.63




1600 Stephens, Adrian   149   1D                      E   N




1601 Stephens, Adrian   149   1 9.1.3.1   359    46   E   N    359.46




1602 Stephens, Adrian   149   1 9.1.3.2   360    51   T   N    360.51




1603 Stephens, Adrian   149   1 9.1.5     361    35   T   N    361.35
1604 Stephens, Adrian   149   1 9.1.5   361   41   T   N   361.41




1605 Stephens, Adrian   149   1 9.1.5   361   65   T   N   361.65
1606 Stephens, Adrian   149   1 9.2      362   30   T   N   362.30




1607 Stephens, Adrian   149   1 9.2.0a   362   56   T   N   362.56




1608 Stephens, Adrian   149   1 9.2.0a   363   8    T   N   363.08
1609 Stephens, Adrian   149   1 9.2.0a   363   16   T   N   363.16




1610 Stephens, Adrian   149   1 9.2.0a   363   22   T   N   363.22




1611 Stephens, Adrian   149   1 9.2.0a   363   26   T   N   363.26
1612 Stephens, Adrian   149   1 9.2.2     364   19   T   N   364.19




1613 Stephens, Adrian   149   1 9.2.3.3   365   43   T   N   365.43




1614 Stephens, Adrian   149   1 9.2.3.4   365   51   T   N   365.51




1615 Stephens, Adrian   149   1 9.2.3.4   365   55   E   N   365.55



1616 Stephens, Adrian   149   1 9.2.3.4   365   60   T   N   365.60
1617 Stephens, Adrian   149   1 9.2.4     366   30   T   N   366.30




1618 Stephens, Adrian   149   1 9.2.5.1   367   51   T   N   367.51




1619 Stephens, Adrian   149   1 9.2.5.3   369   48   E   N   369.48


1620 Stephens, Adrian   149   1 9.2.5.3   370   28   T   N   370.28




1621 Stephens, Adrian   149   1 9.2.6     374   30   T   N   374.30
1622 Stephens, Adrian   149   1 9.2.6   374   33   T   N   374.33




1623 Stephens, Adrian   149   1 9.2.6   374   35   T   N   374.35




1624 Stephens, Adrian   149   1 9.2.6   374   36   T   N   374.36




1625 Stephens, Adrian   149   1 9.2.6   374   41   T   N   374.41




1626 Stephens, Adrian   149   1 9.2.6   374   40   T   N   374.40
1627 Stephens, Adrian   149   1 9.2.7   374   53   T   N   374.53




1628 Stephens, Adrian   149   1 9.2.7   374   59   T   N   374.59




1629 Stephens, Adrian   149   1 9.2.9   375   55   T   N   375.55




1630 Stephens, Adrian   149   1 9.2.9   376   5    T   N   376.05
1631 Stephens, Adrian   149   1 9.2.9    376   12   T   N   376.12




1632 Stephens, Adrian   149   1 9.2.9    376   58   T   N   376.58




1633 Stephens, Adrian   149   1 9.2.11   378   36   T   N   378.36
1634 Stephens, Adrian   149   1 9.3.0a    379   10   T   N   379.10




1635 Stephens, Adrian   149   1 9.3.0a    379   14   T   N   379.14




1636 Stephens, Adrian   149   1 9.3.0a    379   16   T   N   379.16




1637 Stephens, Adrian   149   1 9.3.0a    379   57   T   N   379.57




1638 Stephens, Adrian   149   1 9.10.4               E   N   416.01




1639 Stephens, Adrian   149   1 9.3.4.1   386   15   E   N   386.15


1640 Stephens, Adrian   149   1 9.3.4.2   386   32   T   N   386.32
1641 Stephens, Adrian   149   1 9.4   386   53   T   N   386.53




1642 Stephens, Adrian   149   1 9.5   387   45   T   N   387.45
1643 Stephens, Adrian   149   1 9.5       387   61   T   N   387.61




1644 Stephens, Adrian   149   1 9.6a      389   25   E   N   389.25


1645 Stephens, Adrian   149   1 9.8.0a    390   45   E   N   390.45


1646 Stephens, Adrian   149   1 9.8.1     390   61   T   N   390.61




1647 Stephens, Adrian   149   1 9.9.1.2   397   1    T   N   397.01
1648 Stephens, Adrian   149   1 9.9.1.3    397   42   T   N   397.42




1649 Stephens, Adrian   149   1 9.9.1.3    397   46   T   N   397.46




1650 Stephens, Adrian   149   1 9.9.1.3    398   1    T   N   398.01




1651 Stephens, Adrian   149   1 9.9.1.5    400   13   E   N   400.13




1652 Stephens, Adrian   149   1 9.9.1.5    400   33   T   N   400.33




1653 Stephens, Adrian   149   1 9.9.1.6    400   48   T   N   400.48




1654 Stephens, Adrian   149   1 9.9.2.0a   401   64   E   N   401.64
1655 Stephens, Adrian   149   1 9.9.2.1.2 402   39   T   N   402.39




1656 Stephens, Adrian   149   1 9.9.2.1.3 403   24   T   N   403.24




1657 Stephens, Adrian   149   1 9.9.2.1.3 403   19   T   N   403.19




1658 Stephens, Adrian   149   1 9.9.2.1.3 403   26   T   N   403.26
1659 Stephens, Adrian   149   1 9.9.2.1.3 403   50   T   N   403.50




1660 Stephens, Adrian   149   1 9.9.2.1.3 403   14   E   N   404.14




1661 Stephens, Adrian   149   1 9.9.2.1.3 404   14   T   N   404.14




1662 Stephens, Adrian   149   1 9.9.2.1.3 404   31   E   N   404.31
1663 Stephens, Adrian   149   1 9.9.2.2a   405   18   T   N   405.18




1664 Stephens, Adrian   149   1 9.9.2.2a   405   24   T   N   405.24




1665 Stephens, Adrian   149   1 9.9.2.2a   405   30   T   N   405.30




1666 Stephens, Adrian   149   1 9.9.2.3.0 406    29   T   N   406.29
                                a




1667 Stephens, Adrian   149   1 9.9.2.3.0 407    19   E   N   407.19
                                a

1668 Stephens, Adrian   149   1 9.9.2.3.1 407    30   E   N   407.30
1669 Stephens, Adrian   149   1 9.0a      357   19   E   N   357.19




1670 Stephens, Adrian   149   1 9.1.2     358   27   T   N   358.27




1671 Stephens, Adrian   149   1 9.1.3.1   360   5    T   N   360.05




1672 Stephens, Adrian   149   1 9.2.5.2   369   35   E   N   369.35




1673 Stephens, Adrian   149   1 9.2.5.3   370   24   T   N   370.24




1674 Stephens, Adrian   149   1 9.2.11    378   28   E   N   378.28
1675 Stephens, Adrian   149   1 9.9.1.2    396   50      E   N   396.50




1676 Stephens, Adrian   149   1 9.9.1.5    400   13-18   E   N   400.00




1677 Stephens, Adrian   149   1 9.9.2.0a   401   28      E   N   401.28




1678 Stephens, Adrian   149   1 9.9.2.1.3 403    60      T   N   403.60




1679 Stephens, Adrian   149   1 9.9.2.2a   405   18      E   N   405.18
1680 Stephens, Adrian   149   1 9.9.2.3.2 407   58   E   N   407.58




1681 Stephens, Adrian   149   1 9.9.3.1.0 408   45   T   N   408.45
                                a




1682 Stephens, Adrian   149   1 9.9.3.1.1 409   12   E   N   409.12
1683 Stephens, Adrian   149   1 9.10.3     415   37   T   N   415.37




1684 Stephenson,        149   1 7.3.2.47   209   59   E   N   209.59
     Dave
1685 Stephenson,   149   1 9.9.3.1.0 408   33   T   Y   408.33
     Dave                  a
1686 Stephenson,   149   1 9.9.3.1.0 408   52   T   Y   408.52
     Dave                  a




1687 Stephenson,   149   1 9.9.3.1.2 409   25   T   Y   409.25
     Dave
1688 Stephenson,   149   1 9.9.3.1.2 410   5    T   Y   410.05
     Dave




1689 Stephenson,   149   1 11.4.3   607    34   T   Y   607.34
     Dave




1690 Stephenson,   149   1 11.4.3   607    42   T   Y   607.42
     Dave
1691 Stephenson,   149   1 11.4.4   609   44   T   Y   609.44
     Dave




1692 Stephenson,   149   1 11.4.6   611   49   T   Y   611.49
     Dave




1693 Stephenson,   149   1 11.4.6   611   51   T   Y   611.51
     Dave




1694 Stephenson,   149   1 11.4.6   611   55   T   Y   611.55
     Dave
1695 Stephenson,   149   1 11.4.6   612   5    T   Y   612.05
     Dave




1696 Stephenson,   149   1 11.4.6   612   11   T   Y   612.11
     Dave
1697 Stephenson,      149   1 11.4.7    612   52   T   Y   612.52
     Dave




1698 Thomson, Allan   149   13          20    48   T   Y    20.48


1699 Thomson, Allan   149   13          20    50   T   Y    20.50




1700 Thomson, Allan   149   1 7.2.3.1   92    37   E   Y    92.37




1701 Thomson, Allan   149   1 7.2.3.8   99    5    T   Y    99.05
1702 Venkatesan,   149   1 5.2.7.2    39   26-27   E   N   39.00
     Ganesh




1703 Venkatesan,   149   1 5.2.7.11   40   41-42   T   N   40.00
     Ganesh




1704 Venkatesan,   149   1 5.4        43   42-43   E   N   43.00
     Ganesh




1705 Venkatesan,   149   1 Table 7-8 92    35-38   E   N   92.00
     Ganesh
1706 Venkatesan,   149   1 7.3.1.4    107-108        T   N
     Ganesh




1707 Venkatesan,   149   1 7.3.2.21   134       31   E   N   134.31
     Ganesh
1708 Venkatesan,   149   1 7.3.2.21   134   60      T   N   134.60
     Ganesh




1709 Venkatesan,   149   1 Table 7-   135   24-25   E   N   135.00
     Ganesh                29

1710 Venkatesan,   149   1 7.3.2.21. 151            T   Y   151.00
     Ganesh                10




1711 Venkatesan,   149   1 7.3.2.21. 145    24      T   Y   145.24
     Ganesh                8
1712 Venkatesan,   149   1 7.3.2.{21|          T   Y   143.56
     Ganesh                22}.7




1713 Venkatesan,   149   1 7.3.2.22. 168/169   E   N
     Ganesh                8




1714 Venkatesan,   149   1 7.3.2.22. 173       T   N   173.13
     Ganesh                10
1715 Venkatesan,   149   1 7.3.2.21. 148, 173          T   N   148.00
     Ganesh                10,
                           7.3.2.22.
                           10




1716 Venkatesan,   149   1 7.3.2.25, 178, 183 31, 62   E   N   178.00
     Ganesh                7.3.2.27




1717 Venkatesan,   149   1 7.3.2.31                    T   Y   191.56
     Ganesh




1718 Venkatesan,   149   1 7.3.1.17   115              T   N   115.44
     Ganesh




1719 Venkatesan,   149   1 7.3.2.37   199       5-6    T   N   199.00
     Ganesh
1720 Venkatesan,   149   1 7.3.2     E   N   117.56
     Ganesh




1721 Venkatesan,   149   1 General   T   Y
     Ganesh
1722 Vlantis, George   149   1 G.2        1426   53   T   N   1426.53




1723 Yee, James        149   1 3.2.3      8      1    E   N      8.01


1724 Yee, James        149   1 9.1.1      357    62   E   N    357.62


1725 Yee, James        149   1 9.1.3.1    358    59   T   N    358.59




1726 Yee, James        149   1 9.2.0a     363    22   T   N    363.22




1727 Yee, James        149   1 9.2.3.0a   364    52   E   N    364.52
1728 Yee, James       149   1 9.9.2.0a   401    28   E   N    401.28




1729 Yee, James       149   1 19         941    1    E   N    941.01


2000 Armstrong, Lee   160   2 14.8.2.4   811    9    T   Y    811.09




2001 Armstrong, Lee   160   2 A.4.5      1048   47   T   Y   1048.47




2002 Armstrong, Lee   160   2 A.4.6      1058   50   T   Y   1058.50




2003 Armstrong, Lee   160   2 A.4.7      1062   23   T   Y   1062.23




2004 Armstrong, Lee   160   2 A4.8       1074   25   T   Y   1074.25




2005 Armstrong, Lee   160   2 A4.9       1094   40   T   Y   1094.40
2006 Armstrong, Lee   160   2 15.3.2   825    59   T   Y    825.59




2007 Armstrong, Lee   160   2 16.4     870    27   T   Y    870.27




2008 Armstrong, Lee   160   2 18.3.2   939    16   T   Y    939.16




2009 Armstrong, Lee   160   2 C.2      1189   2    T   Y   1189.02
2010 Armstrong, Lee   160   2D   1419   30   T   Y   1419.30




2011 Armstrong, Lee   160   2D   1419   65   T   Y   1419.65




2012 Armstrong, Lee   160   2D   1522   1    T   Y   1522.01
2013 Armstrong, Lee     160   2 14.8.2.1   809   18   T   Y   809.18




2014 Ashley, Alex       160   2 9.3.3.1    398   65   T   Y   398.65




2015 Ashley, Alex       160   2 11.4.2     644   44   T   Y   644.44




2016 Ecclesine, Peter   160   2 11.9a.1    672   19   T   Y   672.19




2017 Ecclesine, Peter   160   2 11.10.12. 693    42   E   Y   693.42
                                1
2018 Ecclesine, Peter   160   2 Annex D 1351   63   T   Y   1351.63




2019 Ecclesine, Peter   160   2 Annex D 1353   60   T   Y   1353.60




2020 Ecclesine, Peter   160   2 Annex D 1368   47   E   Y   1368.47


2021 Ecclesine, Peter   160   2 Annex D 1370   11   T   Y   1370.11




2022 Ecclesine, Peter   160   2 Annex D 1444   25   T   Y   1444.25
2023 Ecclesine, Peter   160   2 Annex D 1451   20   T   Y   1451.20




2024 Ecclesine, Peter   160   2 Annex D 1438   31   T   Y   1438.31




2025 Ecclesine, Peter   160   2 Annex D 1432   57   T   Y   1432.57
2026 Ecclesine, Peter   160   2 8.2.2.2   261    28   T   N    261.28




2027 Ecclesine, Peter   160   2 9.6a      404    25   T   Y    404.25




2028 Ecclesine, Peter   160   2 Annex A   1096   47   T   Y   1096.47




2029 Ecclesine, Peter   160   2 7.3.1.4   108    45   T   Y    108.45
2030 Ecclesine, Peter   160   2 Annex D 1354     20   T   Y   1354.20




2031 Ecclesine, Peter   160   2 Annex A   1020   20   T   Y   1020.20




2032 Ecclesine, Peter   160   2 Annex A   1020   15   E   Y   1020.15




2033 Ecclesine, Peter   160   2 Annex I   1625   43   T   Y   1625.43




2034 Ecclesine, Peter   160   2 Annex I   1628   39   T   Y   1628.39


2035 Ecclesine, Peter   160   2 Annex J   1633   40   T   Y   1633.40
2036 Ecclesine, Peter   160   2 Annex I   1626   20   E   Y   1626.20


2037 Ecclesine, Peter   160   2 11.1.3.0a 617    43   E   Y    617.43




2038 Ecclesine, Peter   160   2 7.1.3.3.1 78     30   E   Y     78.30




2039 Ecclesine, Peter   160   2 Annex D 1389     2    E   Y   1389.02




2040 Ecclesine, Peter   160   2 Annex B   1125   1    E   Y   1125.01




2041 Ecclesine, Peter   160   2 Annex I   1628   15   T   Y   1628.15



2042 Ecclesine, Peter   160   2 Annex J   1635   11   T   Y   1635.11




2043 Ecclesine, Peter   160   2 Annex J   1635   9    E   Y   1635.09
2044 Ecclesine, Peter   160   2 Annex J   1633   25   T   Y   1633.25




2045 Ecclesine, Peter   160   2 Annex J   1633   6    T   Y   1633.06




2046 Ecclesine, Peter   160   2 Annex A   1023   10   E   Y   1023.10
2047 Ecclesine, Peter   160   2 10.3.1.1. 443   41   E   Y    443.41
                                2




2048 Ecclesine, Peter   160   2 Annex D 1352    23   T   Y   1352.23




2049 Ecclesine, Peter   160   2 Annex D 1502    14   E   Y   1502.14
2050 Ecclesine, Peter   160   2 Annex D 1500   34   T   Y   1500.34




2051 Ecclesine, Peter   160   2 17.4.2   910   28   E   Y    910.28

2052 Ecclesine, Peter   160   2 Annex D 1440   31   T   Y   1440.31
2053 Ecclesine, Peter   160   2 Annex D 1440   18   T   Y   1440.18




2054 Ecclesine, Peter   160   2 Annex D 1449   52   T   Y   1449.52




2055 Ecclesine, Peter   160   2 Annex D 1449   31   T   Y   1449.31
2056 Ecclesine, Peter   160   2 Annex D 1449     30   T   Y   1449.30




2057 Ecclesine, Peter   160   2 11.11.2.2 696    43   E   Y    696.43

2058 Ecclesine, Peter   160   2 Annex A   1058   50   T   Y   1058.50




2059 Ecclesine, Peter   160   2 Annex A   1074   24   T   Y   1074.24




2060 Ecclesine, Peter   160   2 Annex A   1094   40   T   Y   1094.40
2061 Ecclesine, Peter   160   2 Annex D 1419     65   T   Y   1419.65




2062 Ecclesine, Peter   160   2 Annex A   1062   24   T   Y   1062.24


2063 Ecclesine, Peter   160   2 Annex A   1106   42   T   Y   1106.42




2064 Ecclesine, Peter   160   2 Annex A   1105   55   T   Y   1105.55




2065 Ecclesine, Peter   160   2 Annex A   1107   6    T   Y   1107.06


2066 Ecclesine, Peter   160   2 Annex A   1024   40   T   Y   1024.40
2067 Ecclesine, Peter   160   2 7.3.2.48   214   1    E   Y    214.01



2068 Ecclesine, Peter   160   2 7.4.7.9    243   60   E   Y    243.60




2069 Ecclesine, Peter   160   2 Annex D 1346     54   T   Y   1346.54




2070 Ecclesine, Peter   160   2 11.2.1.0a 621    50   T   Y    621.50
2071 Ecclesine, Peter   160   2 Annex D 1353   23   T   Y   1353.23




2072 Ecclesine, Peter   160   2 Annex D 1352   17   T   Y   1352.17




2073 Ecclesine, Peter   160   2 Annex D 1352   34   T   Y   1352.34




2074 Ecclesine, Peter   160   2 Annex D 1354   15   T   Y   1354.15
2075 Ecclesine, Peter   160   2 Annex D 1369   44   T   Y   1369.44




2076 Ecclesine, Peter   160   2 Annex D 1369   58   T   Y   1369.58




2077 Ecclesine, Peter   160   2 Annex D 1370   11   T   Y   1370.11
2078 Ecclesine, Peter   160   2 Annex D 1388        T   Y   1388.00




2079 Engwer, Darwin     160   2M        1651   1    T   Y   1651.01




2080 Engwer, Darwin     160   2 0A      1019   32   T   Y   1019.32




2081 Engwer, Darwin     160   2 9.8.2   406    22   T   Y    406.22
2082 Erceg, Vinko   160   2 17.3.10.5 ame   15-19   T   Y   902.20




2083 Erceg, Vinko   160   2 General                 E   N




2084 Erceg, Vinko   160   23          k     20      E   N    10.64




2085 Erceg, Vinko   160   2 5.4.1.2   ax    20      E   N    44.01

2086 Erceg, Vinko   160   2 5.4.3.3   bb    41      E   N    48.01




2087 Erceg, Vinko   160   2 5.4.4.1   bc    58      E   N    49.40




2088 Erceg, Vinko   160   2 17.3.8.3. alw   54      T   Y   895.34
                            1
2089 Fischer, Matthew   160   2 9.14.0b    sd    64   T   N   438.28




2090 Fischer, Matthew   160   2 9.8.2      qu    46   T   N   406.06




2091 Fischer, Matthew   160   2 11.2.1.1   aak   26   T   N   622.19




2092 Hamilton, Mark     160   2 6.2.3.2    71    6    T   Y    71.06




2093 Hamilton, Mark     160   2 6.3.2.2    71    2    T   N    71.02
2094 Hamilton, Mark   160   2 10.1     441    30   T   Y   441.30




2095 Hamilton, Mark   160   2 9.9.3.1.0 423   40   T   Y   423.40
                              a




2096 Hamilton, Mark   160   2 10.3.20.2 515   1    T   Y   515.01
2097 Hamilton, Mark   160   2 8.5.6.0a   345   19      E   N   345.19

2098 Harkins, Dan     160   2 8.4.1.1.1 288    1-2     T   Y   289.01




2099 Harkins, Dan     160   2 8.4.1.1.1 288    4       T   Y   289.04




2100 Harkins, Dan     160   2 8.4.6.2    299   32-33   T   Y   299.00
2101 Harkins, Dan       160   2 8.5.1.2   307   41-42   T   Y   307.00




2102 Hiertz, Guido R.   160   2 3.196     19    1-4     T   Y    19.00




2103 Kolze, Tom         160   2 17.3.10.5 ame   15-19   T   Y   902.20
2104 Kolze, Tom       160   2 17.3.8.3. alw   54   T   Y   895.34
                              1




2105 Malinen, Jouni   160   2 6.1.2    65     32   T   Y    65.32




2106 Malinen, Jouni   160   2 7.3.2.25. 181   50   T   Y   181.50
                              1
2107 Malinen, Jouni   160   2 7.3.2.48   214   37   T   Y   214.37




2108 Malinen, Jouni   160   2 8.5.2      318   39   E   Y   318.39




2109 Malinen, Jouni   160   2 8.5.6.0a   344   54   E   Y   344.54
2110 Malinen, Jouni   160   2 11.3.0a   634   33   T   Y   634.33




2111 Malinen, Jouni   160   2 11.3.1.0a 635   57   T   Y   635.57
2112 Malinen, Jouni   160   2 11.3.2.3   640   44   T   Y   640.44




2113 Malinen, Jouni   160   2 7.3.2.54   219   21   T   Y   219.21
2114 Marshall, Bill   160   2 Annex D 1527    38   E   N   1527.38




2115 Marshall, Bill   160   2 Annex D              T   N   1342.01




2116 Marshall, Bill   160   2 Annex C 1138    1    T   N   1138.01




2117 Marshall, Bill   160   2 11.7.0a   658   31   E   N    658.31
2118 Marshall, Bill   160   2 Annex D               E   N   1342.01




2119 Marshall, Bill   160   2 General               E   N




2120 Marshall, Bill   160   2 11.3.1.3   637   33   E   N    637.33
2121 Marshall, Bill   160   2 Annex D             T   N   1342.01




2122 Marshall, Bill   160   2 Annex Q 1671   10   E   N   1671.10
2123 Marshall, Bill   160   2 19.1.1    977    34   T   N    977.34




2124 Marshall, Bill   160   2 11.1.3.0a 617    43   T   N    617.43




2125 Marshall, Bill   160   2 Annex A   1020   16   E   N   1020.16




2126 Montemurro,      160   2 General               E   N
     Michael
2127 Montemurro,   160   2 7.4.9a     374   27   T   N   250.09
     Michael




2128 Montemurro,   160   2 11.3       809   1    T   N   633.34
     Michael




2129 Montemurro,   160   2 11.3.1.4   814   40   T   N   637.61
     Michael
2130 Montemurro,        160   2 11.3.2.8   820   51   T   N   643.28
     Michael




2131 Ptasinski, Henry   160   2 8.1.3      254   58   E   N   254.58


2132 Ptasinski, Henry   160   2 8.1.3      255   59   T   Y   255.59




2133 Ptasinski, Henry   160   2 8.1.3      255   6    E   N   255.06




2134 Ptasinski, Henry   160   2 8.1.3      255   10   E   N   255.10




2135 Ptasinski, Henry   160   2 8.1.3      255   10   T   Y   255.10



2136 Ptasinski, Henry   160   2 8.3.3.3.3 283    30   T   Y   283.30
2137 Ptasinski, Henry   160   2 8.3.3.3.5 284   6    T   Y   284.06




2138 Ptasinski, Henry   160   2 8.3.3.4.0 284   51   T   Y   284.51
                                a


2139 Ptasinski, Henry   160   2 8.3.3.4.1 285   5    T   Y   285.05




2140 Purnadi, Rene      160   2 7.4.7.2   235   13   E   N   237.19




2141 Purnadi, Rene      160   2 11.9a.1   634   47   E   N   672.13




2142 Purnadi, Rene      160   2 11.9a.3.1 635   47   T   N   672.55
2143 Purnadi, Rene    160   2 11.9a.3.2 636   32      T   N   673.47




2144 Purnadi, Rene    160   2 11.10.3   637   65      E   N   675.17




2145 Raja, Banerjea   160   2 9.13      437   20-34   T   N   437.00
2146 Raja, Banerjea   160   2 11.2.2.4    632   56-57   T   N   632.00




2147 Raja, Banerjea   160   2 10.3.2.2.   447   54      T   N   447.54
                              2
2148 Raja, Banerjea   160   2 10.3.10.1   482   45      T   N   482.45
                              .2
2149 Raja, Banerjea   160   2 10.3.10a.   484   64      T   N   484.64
                              1.2
2150 Raja, Banerjea   160   2 10.3.10.1   482   49      T   N   482.49
                              .2
2151 Rosdahl, Jon   160   23            11   1   T   Y    11.01




2152 Rosdahl, Jon   160   2 11.2.1.0a            T   Y   621.47
2153 Rosdahl, Jon   160   2 1.2        1     51   T   Y     1.51




2154 Rosdahl, Jon   160   23           11    61   E   N    11.61



2155 Rosdahl, Jon   160   2 11.3.0a    633   45   T   Y   633.45




2156 Rosdahl, Jon   160   2 11.3.0a    634   42   T   Y   634.42




2157 Rosdahl, Jon   160   2 11.3.1.3   637   36   T   Y   637.36
2158 Rosdahl, Jon   160   2 11.3.1.4   638   1   E   Y   638.01




2159 Rosdahl, Jon   160   2 11.3.2.4   642   8   T   Y   642.08




2160 Rosdahl, Jon   160   2 11.3.0a    634       T   Y   634.00
2161 Rosdahl, Jon   160   2 11.3.1.0a 636    1    T   Y   636.01




2162 Rosdahl, Jon   160   2 11.3.2.0a 638    34   T   Y   638.34




2163 Rosdahl, Jon   160   2 11.3.1.1   636   12   T   Y   636.12
2164 Rosdahl, Jon   160   2 11.3.1.4   637   54   T   Y   637.54




2165 Rosdahl, Jon   160   2 11.3.2.6   642   49   T   Y   642.49
2166 Rosdahl, Jon   160   2 11.3.1.2   637   4    T   Y   637.04




2167 Rosdahl, Jon   160   2 11.3.2.1   638   55   T   Y   638.55




2168 Rosdahl, Jon   160   2 11.3.2.5   642   17   T   Y   642.17
2169 Rosdahl, Jon   160   2 11.3.1.3   637   17   T   Y   637.17




2170 Rosdahl, Jon   160   2 11.3.0a    635   12   E   Y   635.12

2171 Rosdahl, Jon   160   2 11.3.0a    635   32   E   Y   635.32

2172 Rosdahl, Jon   160   2 11.3                  E   Y   633.34
2173 Rosdahl, Jon   160   2 11.3   E   Y   633.34




2174 Rosdahl, Jon   160   2 11.3   E   Y   633.34




2175 Rosdahl, Jon   160   23       T   Y     6.01
2176 Rosdahl, Jon       160   2 11.2                  T   Y    621.39




2177 Sakoda,            160   23          15     56   T   N     15.56
     Kazuyuki




2178 Sakoda,            160   2 A.4.4.2   1039   20   T   N   1039.20
     Kazuyuki




2179 Stephens, Adrian   160   2           iv     28   T   N
2180 Stephens, Adrian   160   2   33    44   T   Y    33.44




2181 Stephens, Adrian   160   2   108   6    T   Y   108.06




2182 Stephens, Adrian   160   2   108   26   T   Y   108.26
2183 Stephens, Adrian   160   2   109   22   T   Y   109.22




2184 Stephens, Adrian   160   2   109   45   T   N   109.45




2185 Stephens, Adrian   160   2   135   36   T   Y   135.36




2186 Stephens, Adrian   160   2   214   29   T   N   214.29
2187 Stephens, Adrian   160   2           243   53   T   Y   243.53


2188 Stephens, Adrian   160   2           280   37   T   N   280.37




2189 Stephens, Adrian   160   2 General              T   N




2190 Stephens, Adrian   160   2           342   49   T   Y   342.49




2191 Stephens, Adrian   160   2           365   10   T   N   365.10




2192 Stephens, Adrian   160   2           369   34   T   N   369.34
2193 Stephens, Adrian   160   2   441   23   T   N   441.23




2194 Stephens, Adrian   160   2   555   20   T   Y   555.20




2195 Stephens, Adrian   160   2   572   25   T   Y   572.25
2196 Stephens, Adrian   160   2   636   39   T   N   636.39
2197 Stephens, Adrian   160   2   637   36   T   N   637.36
2198 Stephens, Adrian   160   2   642   5   T   N   642.05
2199 Stephens, Adrian   160   2   739    47   T   Y    739.47




2200 Stephens, Adrian   160   2   1432   30   T   Y   1432.30
2201 Stephens, Adrian   160   2             1432   38   T   N   1432.38




2202 Stephens, Adrian   160   2             1438   28   T   N   1438.28




2203 Stephens, Adrian   160   2             1502   14   T   Y   1502.14




2204 Stephens, Adrian   160   2             1622   42   E   N   1622.42



2205 Stephens, Adrian   160   2 7.1.3.1.7               T   N     76.46




2206 Stephens, Adrian   160   2 7.4.7.10                T   Y    245.01
2207 Stephens, Adrian   160   2 10.3.40   T   N   587.45




2208 Stephens, Adrian   160   2 10.3.44   T   Y   603.01
2209 Stephens, Adrian   160   2 11.2.2.3              T   Y   632.01




2210 Stephens, Adrian   160   2            635   29   E   N   635.29



2211 Stephens, Adrian   160   2 General               E   N

2212 Stephens, Adrian   160   2            696   57   T   Y   696.57
2213 Stephens, Adrian   160   2 11.11.2.4              T   N   697.38




2214 Stephens, Adrian   160   2 General                E   N




2215 Stephens, Adrian   160   2 17.4.3      910   38   E   Y   910.38
2216 Stephens, Adrian   160   2 11.6.2               E   N    658.01




2217 Stephens, Adrian   160   2 F.0a     1559   19   E   N   1559.19

2218 Stephens, Adrian   160   2 7.3.2.21. 136   11   E   N    136.11
                                1
2219 Stephens, Adrian   160   2 8.5.3.5   331   17   T   Y   331.17




2220 Stephenson,        160   2 7.1.3.3.3 79    6    T   Y    79.06
     Dave




2221 Stephenson,        160   2 10.3.24.3 524   65   E   N   524.65
     Dave                       .3
2222 Stephenson,   160   2 11.2.1.0a 621   47-52   T   Y   621.00
     Dave
2223 Stephenson,   160   2 11.2.1.0a 621    54-57   T   Y   621.00
     Dave




2224 Stephenson,   160   2 11.2.1.0a 622    11      T   Y   622.11
     Dave




2225 Stephenson,   160   2 11.2.1.4   624   46      T   Y   624.46
     Dave
2226 Stephenson,   160   2 11.2.1.5   625   42   T   Y   625.42
     Dave




2227 Stephenson,   160   2 11.2.1.9   629   45   T   Y   629.45
     Dave




2228 Stephenson,   160   2 11.2.1.9   629   49   T   Y   629.49
     Dave
2229 Stephenson,   160   2 11.3.1.0a 635   56   T   Y   635.56
     Dave




2230 Stephenson,   160   2 11.3.1.0a 635   58   T   Y   635.58
     Dave
2231 Stephenson,   160   2 11.3.1.0a 635   58   T   Y   635.58
     Dave




2232 Stephenson,   160   2 11.4.3   644    57   T   Y   644.57
     Dave




2233 Stephenson,   160   2 11.4.3   645    47   T   Y   645.47
     Dave
2234 Stephenson,   160   2 11.4.4   646   48      T   Y   646.48
     Dave




2235 Stephenson,   160   2 11.4.4   647   16      T   Y   647.16
     Dave

2236 Stephenson,   160   2 11.4.4   647   25      T   Y   647.25
     Dave




2237 Stephenson,   160   2 11.4.4   647   24-31   T   Y   647.00
     Dave




2238 Stephenson,   160   2 11.4.6   649   50      T   Y   649.50
     Dave




2239 Stephenson,   160   2 11.4.6   649   55      E   N   649.55
     Dave
2240 Stephenson,      160   2 11.4.6      649    55   T   Y    649.55
     Dave




2241 Stephenson,      160   2 11.4.6      649    55   T   Y    649.55
     Dave




2242 Stephenson,      160   2 11.4.6      650    1    T   Y    650.01
     Dave


2243 Stephenson,      160   2 11.4.8      650    55   E   N    650.55
     Dave




2244 Stephenson,      160   2 11.4.8      650    58   E   N    650.58
     Dave



2245 Venkatesan,      160   2 Table 7-                E   N    136.03
     Ganesh                   29 and 7-
                              30




3000 Armstrong, Lee   162   3 20.3.20     1279   12   T   Y   1279.12
3001 Armstrong, Lee   162   3A         1330   56   T   Y   1330.56




3002 Armstrong, Lee   162   3A         1354   47   T   Y   1354.47




3003 Armstrong, Lee   162   3A         1380   7    T   Y   1380.07




3004 Armstrong, Lee   162   3A         1399   10   T   Y   1399.10




3005 Armstrong, Lee   162   3D         1879   27   T   Y   1879.27




3006 Armstrong, Lee   162   3 19.8.2   1196   29   T   Y   1196.29




3007 Armstrong, Lee   162   3 20.4.2   1294   40   T   Y   1294.40
3008 Armstrong, Lee   162   3C         1518   1    T   Y   1518.01




3009 Armstrong, Lee   162   3C         1518   2    T   Y   1518.02




3010 Armstrong, Lee   162   3D         1878   53   T   Y   1878.53




3011 Armstrong, Lee   162   3D         1921   38   T   Y   1921.38




3012 Bajko, Gabor     162   3 7.3.2.22. 213   9    T   N    213.09
                              9
3013 Bajko, Gabor    162   3 7.3.2.21. 188     7    T   N    188.07
                             9




3014 Cypher, David   162   30                       T   N




3015 Cypher, David   162   3 14.8.2.4   1001   1    T   Y   1001.01




3016 Cypher, David   162   3 17.4.2     1098   54   T   Y   1098.54


3017 Cypher, David   162   3 19.8.2     1196   29   T   Y   1196.29


3018 Cypher, David   162   3 20.3.20    1279   7    T   Y   1279.07


3019 Cypher, David   162   3 20.4.2     1294   45   T   Y   1294.45
3020 Cypher, David      162   3 A.4.3     1330   56-63   T   Y   1330.00




3021 Cypher, David      162   3 A.4.5     1354   47-51   T   Y   1354.00




3022 Cypher, David      162   3 A.4.8     1380   6-15    T   Y   1380.00



3023 Cypher, David      162   3 A.4.9     1399   10-15   T   Y   1399.00



3024 Cypher, David      162   3 D.3       1878   56      T   Y   1878.56




3025 Ecclesine, Peter   162   3 Annex A   1401   34      T   N   1401.34



3026 Ecclesine, Peter   162   3 Annex J   2067   31      T   N   2067.31
3027 Ecclesine, Peter   162   3 Annex J   2067   36   T   N   2067.36




3028 Ecclesine, Peter   162   3 20.3.20   1279   7    T   Y   1279.07




3029 Ecclesine, Peter   162   3 10.3.37.1 739    62   T   N    739.62
                                .3
3030 Ecclesine, Peter   162   3 Annex I   2051   3    T   N   2051.03




3031 Ecclesine, Peter   162   3 11.11.5   867    60   E   N    867.60


3032 Ecclesine, Peter   162   3 3.1       8      21   E   N      8.21
3033 Ecclesine, Peter   162   3 3.1   8   12   E   N   8.12
3034 Ecclesine, Peter   162   3 3.1   8   21   E   N   8.21
3035 Ecclesine, Peter   162   3 3.1   6   49   E   Y   6.49
3036 Ecclesine, Peter   162   3 3.1   9   50   E   Y   9.50
3037 Ecclesine, Peter   162   3 3.1        11    20   E   Y    11.20




3038 Liwen, Chu         162   3 7.1.3.5.3 92     40   T   Y    92.40




3039 Liwen, Chu         162   3 7.1.4.2    99    38   T   Y    99.38




3040 Liwen, Chu         162   3 7.3.2.31   237   11   E   Y   237.11
3041 Liwen, Chu   162   3 9.1.3.1    453   58   T   Y   453.58




3042 Liwen, Chu   162   3 9.1.5      455   60   T   Y   455.60




3043 Liwen, Chu   162   3 9.2.0b.3   458   24   T   Y   458.24




3044 Liwen, Chu   162   3 9.2.0b.4. 460    52   T   Y   460.52
                          6




3045 Liwen, Chu   162   3 9.2.0b.6   462   26   T   Y   462.26




3046 Liwen, Chu   162   3 9.9.1.2    510   30   T   Y   510.30




3047 Liwen, Chu   162   3 9.9.1.3    510   54   T   Y   510.54
3048 Liwen, Chu   162   3 11.1.3.2. 780    6    T   Y   780.06
                          2




3049 Liwen, Chu   162   3 11.2.1.0a 784    50   T   Y   784.50




3050 Liwen, Chu   162   3 11.2.1.4   788   24   T   Y   788.24




3051 Liwen, Chu   162   3 11.2.1.5   788   48   T   Y   788.48




3052 Liwen, Chu   162   3 11.2.1.5   789   18   E   Y   789.18
3053 Liwen, Chu   162   3 11.2.1.9   793   31   T   Y   793.31




3054 Liwen, Chu   162   3 11.2.1.12 794    5    T   Y   794.05
3055 Liwen, Chu   162   3 11.2.1.12 794    26   T   Y   794.26




3056 Liwen, Chu   162   3 11.2.2.4   797   43   T   Y   797.43




3057 Liwen, Chu   162   3 11.4.44    814   38   T   Y   814.38




3058 Liwen, Chu   162   3 9.16.1.7   562   56   T   Y   562.56
3059 Liwen, Chu    162   3 11.9.7.3   839   30      T   Y   839.30




3060 Liwen, Chu    162   3 7.3.27     227   28      T   Y   227.28




3061 Montemurro,   162   3 7.3.2.37   242   60      T   N   242.60
     Michael




3062 Ramamurthy,   162   3 7.3.2.27   228   38-52   T   N   228.00
     Harish


3063 Ramamurthy,   162   3 11.1.3.2. 779    40-44   T   Y   779.00
     Harish                1
3064 Ramamurthy,   162   3 11.2.1.0a 784    17-20   T   Y   784.00
     Harish




3065 Ramamurthy,   162   3 11.2.1.1   785   53-54   T   Y   785.00
     Harish
3066 Ramamurthy,   162   3 7.3.2.4    163   4-5     T   Y   163.00
     Harish




3067 Ramamurthy,   162   3 11.1.2.2   776   57-58   T   Y   776.00
     Harish




3068 Ramamurthy,   162   3 11.2.2.1   795   5-9     T   Y   795.00
     Harish
3069 Ramamurthy,   162   3 11.2.2.1   795   13-16   T   Y   795.00
     Harish




3070 Ramamurthy,   162   3 11.2.2.4   797   43-46   T   Y   797.00
     Harish
3071 Ramamurthy,   162   3 11.2.2     794           T   Y   794.00
     Harish




3072 Ramamurthy,   162   3 11.2.1.5   789   22-24   T   Y   789.00
     Harish
3073 Rosdahl, Jon   162   3 11.3      800   25   T   Y   800.25




3074 Rosdahl, Jon   162   3 11.3.0a   801        T   Y   801.00
3075 Rosdahl, Jon   162   3 11.3.1.2   802   50   T   Y   802.50




3076 Rosdahl, Jon   162   3 11.3.1.0a 802    8    T   Y   802.08




3077 Rosdahl, Jon   162   3 11.3.2.0a 804    31   T   Y   804.31




3078 Rosdahl, Jon   162   3 11.3.2.6   808   39   T   Y   808.39
3079 Rosdahl, Jon   162   3 11.3.2.7   808    64   T   Y    808.64




3080 Rosdahl, Jon   162   3 11.3.1.2   802    62   T   Y    802.62




3081 Rosdahl, Jon   162   3 A.4.11     1407   13   T   N   1407.13
3082 Rosdahl, Jon   162   3 A.4.4.1   1344   23   T   Y   1344.23




3083 Rosdahl, Jon   162   3 20.3.12.1 1269   25   T   Y   1269.25
3084 Sakoda,            162   3 7.4       279         E   N    279.01
     Kazuyuki




3085 Sakoda,            162   3 7.4.2.1   282    34   T   N    282.34
     Kazuyuki




3086 Sakoda,            162   3 A.4.5.3   1360   27   T   N   1360.27
     Kazuyuki




3087 Stephens, Adrian   162   3 General               E   N
3088 Stephens, Adrian   162   3           133   30   T   N   133.30



3089 Stephens, Adrian   162   3 General              E   N




3090 Stephens, Adrian   162   3           255   1    E   N   255.01




3091 Stephens, Adrian   162   3           543   6    T   N   543.06




3092 Stephens, Adrian   162   3           739   58   T   N   739.58
3093 Stephens, Adrian   162   3   784   8    T   Y   784.08




3094 Stephens, Adrian   162   3   784   60   T   N   784.60




3095 Stephens, Adrian   162   3   784   63   T   N   784.63




3096 Stephens, Adrian   162   3   794   59   T   Y   794.59
3097 Stephens, Adrian   162   3           802   49   T   N   802.49




3098 Stephens, Adrian   162   3 General              E   N




3099 Stephens, Adrian   162   3           803   36   T   N   803.36
3100 Stephens, Adrian   162   3   808   25   T   N   808.25




3101 Stephens, Adrian   162   3   808   54   T   N   808.54




3102 Stephens, Adrian   162   3   809   26   T   N   809.26
3103 Stephens, Adrian   162   3   233    5    T   Y    233.05




3104 Stephens, Adrian   162   3   894    47   T   Y    894.47




3105 Stephens, Adrian   162   3   894    57   T   Y    894.57




3106 Stephens, Adrian   162   3   1259   56   T   N   1259.56



3107 Stephens, Adrian   162   3   1279   10   T   Y   1279.10
3108 Stephens, Adrian   162   3   1291   50   T   N   1291.50




3109 Stephens, Adrian   162   3   1292   4    T   N   1292.04




3110 Stephens, Adrian   162   3   1407   13   T   Y   1407.13
3111 Stephens, Adrian   162   3           1669   32   T   Y   1669.32




3112 Stephens, Adrian   162   3           1763   27   T   Y   1763.27



3113 Stephens, Adrian   162   3           1788   32   T   N   1788.32


3114 Stephens, Adrian   162   3           1945   37   T   N   1945.37




3115 Stephens, Adrian   162   3 General               E   N


3116 Stephens, Adrian   162   3           2051   4    T   Y   2051.04




3117 Stephens, Adrian   162   3           2052   30   E   N   2052.30


3118 Stephens, Adrian   162   3           2112   32   E   N   2112.32
3119 Stephens, Adrian   162   3            296   40   E   N   296.40


3120 Stephens, Adrian   162   3 8.7.2.4               E   N   447.42



3121 Stephens, Adrian   162   3 11.5.2.1              T   N   821.56



3122 Stephenson,        162   3 11.2.1.1   785   29   T   Y   785.29
     Dave




3123 Stephenson,        162   3 11.2.1.1   785   49   T   Y   785.49
     Dave
3124 Stephenson,   162   3 11.2.1.4   787   26   E   N   787.26
     Dave




3125 Stephenson,   162   3 11.2.1.5   789   4    T   Y   789.04
     Dave




3126 Stephenson,   162   3 11.2.1.5   789   23   T   Y   789.23
     Dave




3127 Stephenson,   162   3 11.2.1.5   789   54   T   Y   789.54
     Dave
3128 Stephenson,   162   3 11.2.1.7   792   35   T   Y   792.35
     Dave




3129 Stephenson,   162   3 11.2.1.11 793    62   T   Y   793.62
     Dave
3130 Stephenson,   162   33       18    1    T   Y    18.01
     Dave




3131 Stephenson,   162   3 11.4   809   40   T   Y   809.40
     Dave
3132 Stephenson,       162   3 11.4.3   810    47   T   Y    810.47
     Dave




3133 Stephenson,       162   3 9.9.3.1.1 524   30   T   Y    524.30
     Dave




3134 Stephenson,       162   3 9.9.3.1.1 524   30   T   Y    524.30
     Dave




3135 Vlanits, George   162   3 19.8.2   1196   28   T   Y   1196.28
3136 Vlanits, George   162   3 20.3.20   1279   7    T   Y   1279.07




3137 Vlanits, George   162   3 20.4.2    1294   44   T   Y   1294.44




3138 Vlanits, George   162   3 A.4.3     1330   53   T   Y   1330.53




3139 Vlanits, George   162   3 A.4.3     1330   56   T   Y   1330.56




3140 Vlanits, George   162   3 A.4.5     1354   47   T   Y   1354.47




3141 Vlanits, George   162   3 A.4.8     1380   6    T   Y   1380.06
3142 Vlanits, George   162   3 A.4.9   1399   10   T   Y   1399.10




3143 Vlanits, George   162   3 C.2     1518   12   T   N   1518.12




3144 Vlanits, George   162   3D        1878   56   T   N   1878.56



3145 Vlanits, George   162   3D        1879   27   T   N   1879.27




3146 Vlanits, George   162   3D        1879   28   T   Y   1879.28




3147 Vlanits, George   162   3D        1921   39   T   N   1921.39
3148 Vlanits, George   162   3 G.3.6      2010   50   T   Y   2010.50




4000 Armstrong, Lee    163   4A           1316   55   T   Y   1316.55



4001 Armstrong, Lee    163   4D           1863   16   T   Y   1863.16




4002 Bahr, Michael     163   4 7.3.2.6    164    25   E   N    164.25




4003 Bahr, Michael     163   4 7.3.2.48   258    1    E   N    258.01




4004 Bahr, Michael     163   4 7.3.2.48   258    1    E   N    258.01
4005 Bahr, Michael   163   4 7.3.2.0a   158       38      E   N   158.38




4006 Bahr, Michael   163   4 7.3.2.1    161       64      E   N   161.64


4007 Bahr, Michael   163   4 7.3.2.1    161       64      E   N   161.64




4008 Bahr, Michael   163   4 7.3.2.2    162       6       E   N   162.06




4009 Bahr, Michael   163   4 7.3.2.3    162-163   65-1    E   N   162.65




4010 Bahr, Michael   163   4 7.3.2.4    163       31      E   N   163.31




4011 Bahr, Michael   163   4 7.3.2.5    163       46-49   E   N   163.00




4012 Bahr, Michael   163   4 7.3.2.7    165       5       E   N   165.05
4013 Bahr, Michael   163   4 7.3.2.8    165   20-21   E   N   165.00




4014 Bahr, Michael   163   4 7.3.2.14   169   55      E   N   169.55




4015 Bahr, Michael   163   4 7.3.2.25. 221    41      E   N   221.41
                             0a



4016 Bahr, Michael   163   4 7.3.2.25. 221    41-42   E   N   221.41
                             0a




4017 Bahr, Michael   163   4 7.3.2.26   228   14,16   E   N   228.14




4018 Bahr, Michael   163   4 7.3.2.39   247   53-54   E   N   247.53




4019 Bahr, Michael   163   4 9.8.3      507   26      E   N   507.26




4020 Bahr, Michael   163   4 11.10.9.2 844    28      E   N   844.28




4021 Bahr, Michael   163   4 7.3.2.37   245   56      E   N   245.56




4022 Bahr, Michael   163   4 11.10.9.2 844    30      E   N   844.30
4023 Chu, Liwen   163   4 7.1.3.1.7 86    11   E   N    86.11




4024 Chu, Liwen   163   4 7.2.2.2   115   34   T   Y   115.34




4025 Chu, Liwen   163   4 7.1.3.5.3 92    40   T   Y    92.40




4026 Chu, Liwen   163   4 7.1.3.1.8 86    44   T   Y    86.44
4027 Chu, Liwen   163   4 7.1.3.5.0 90     6    T   Y    90.06
                          a




4028 Chu, Liwen   163   4 7.1.3.1    83    19   T   Y    83.19




4029 Chu, Liwen   163   4 11.2.1.5   774   51   T   Y   774.51
4030 Chu, Liwen      163   4 11.2.1.1   771    41   T   Y    771.41




4031 Cypher, David   163   4A           1316   56   T   Y   1316.56
4032 Ecclesine, Peter   163   4 J.1        2040   6    E   N   2040.06




4033 Ecclesine, Peter   163   4 16         1032   7    E   N   1032.01


4034 Hamilton, Mark     163   4 7.3.2.30   235    11   T   Y    235.11




4035 Hamilton, Mark     163   4 3.1        12     61   T   Y     12.61




4036 Hamilton, Mark     163   4 7.3.1.6    136    5    E   N    136.05


4037 Hamilton, Mark     163   4 7.3.2.12   169    8    E   N    169.08
4038 Hamilton, Mark   163   4 7.4.8      310   9    T   Y   310.09




4039 Hamilton, Mark   163   4 7.3.2.31   240   51   E   N   240.51




4040 Hamilton, Mark   163   4 11.2.1.7   777   39   T   Y   777.39




4041 Hamilton, Mark   163   4 11.3.0a    785   5    T   Y   785.05




4042 Hamilton, Mark   163   4 11.3.1.3   788   46   T   Y   788.46
4043 Hamilton, Mark   163   4 11.3.1     787   18   T   Y   787.18




4044 Hamilton, Mark   163   4 11.3.1     787   18   T   Y   787.18




4045 Hamilton, Mark   163   4 11.3       784   29   T   Y   784.29




4046 Hamilton, Mark   163   4 11.3.1.1   787   18   T   Y   787.18




4047 Hamilton, Mark   163   4 11.3.1.3. 788    43   T   Y   788.43
                              b
4048 Hamilton, Mark   163   4 11.3.2     789   12   T   Y   789.12



4049 Hamilton, Mark   163   4 11.3.2     789   12   T   Y   789.12




4050 Hamilton, Mark   163   4 11.4.4     797   50   T   Y   797.50




4051 Hamilton, Mark   163   4 11.3.1.1   787   18   T   Y   787.18
4052 Hiertz, Guido    163   43           19    1-4   T   Y    19.01




4053 Marshall, Bill   163   4 11.3.0a    785   33    T   Y   785.33




4054 Marshall, Bill   163   4 11.3.1.2   787   59    T   Y   787.59
4055 Marshall, Bill   163   4 11.3.0a    784   16      T   Y    784.16




4056 Purnadi, Rene    163   4 7.4.1.1    286   52      E   N    281.41




4057 Purnadi, Rene    163   4 7.4.6.1    297   58      E   N    292.31


4058 Purnadi, Rene    163   4 Annex D 1835     58      E   N   1835.58




4059 Ramamurthy,      163   4 7.3.2.38   247   42-46   T   Y    247.00
     Harish
4060 Ramamurthy,   163   4 9.2.4   469   54-58   T   Y   469.54
     Harish




4061 Ramamurthy,   163   4 11.5    805           T   Y   805.04
     Harish
4062 Ramamurthy,    163   4 7.3.1.15   142   44-45   T   Y   142.44
     Harish




4063 Ramamurthy,    163   4 7.4.4.2    290   55      T   Y   290.55
     Harish




4064 Ramamurthy,    163   4 11.2.1.0a 770    10      E   Y   770.10
     Harish




4065 Ramamurthy,    163   4 11.5.3     822   33      T   Y   808.30
     Harish




4066 Rosdahl, Jon   163   4 11.2.1.0a 770    11      T   Y   770.11
4067 Rosdahl, Jon   163   4 20.3.12.1 1255   25   T   Y   1255.25




4068 Rosdahl, Jon   163   4 11.3.2.2   790   64   E   N    790.64



4069 Rosdahl, Jon   163   4 11.3.2.2   790   42   E   N    790.42
4070 Rosdahl, Jon   163   4 Annex D 1822     27   E   N   1822.27




4071 Sakoda,        163   4 7.3.2.6    164   11   E   N    164.11
     Kazuyuki



4072 Sakoda,        163   4 7.4.1.0a   281   25   E   N    281.25
     Kazuyuki




4073 Sakoda,        163   4 7.4.7.1    297   56   E   N    297.56
     Kazuyuki



4074 Sakoda,        163   4 7.4                   E   N    281.01
     Kazuyuki




4075 Sakoda,        163   4 7.4.1.1    281   41   E   N    281.41
     Kazuyuki
4076 Seok, Yongho       163   4 11.9a.3.1 831    49-50   T   Y   826.49




4077 Seok, Yongho       163   4 11.11.5    858   49-51   T   Y   853.00




4078 Stephens, Adrian   163   4 1.4.1.0a   281   25      E   N   281.25
4079 Stephens, Adrian   163   4 11.1.2.2   763   5    E   N   763.05




4080 Stephens, Adrian   163   4 11.3.0a    784   16   T   Y   784.16




4081 Stephens, Adrian   163   4 11.3.0a    784   22   T   Y   784.22




4082 Stephens, Adrian   163   4 11.3.0a    784   26   T   Y   784.26




4083 Stephens, Adrian   163   4 11.3.1.2   788   1    T   Y   788.01




4084 Stephens, Adrian   163   4 11.3.1.3   788   40   T   Y   788.40
4085 Stephens, Adrian   163   4 11.3.2.2   791   25   T   Y   791.25




4086 Stephens, Adrian   163   4 11.3.2.3   792   11   T   Y   792.11




4087 Stephens, Adrian   163   4 11.3.2.4   792   37   T   Y   792.37




4088 Stephens, Adrian   163   4 11.3.2.4   792   45   T   Y   792.45
4089 Stephens, Adrian   163   4 11.3.2.4   793   38   T   Y   793.38




4090 Stephens, Adrian   163   4 11.3.2.5   793   64   T   Y   793.64




4091 Stephens, Adrian   163   4 11.3.2.7   794   42   T   Y   794.42




4092 Stephens, Adrian   163   4 11.3.2.2   790   41   T   N   790.41
4093 Vlantis, George   163   4 7.4.6.4   295   1   T   Y   295.01
4094 Vlantis, George   163   4 11.10.8.7 841   31   T   Y   841.31
4095 Vlantis, George   163   4 9.9.1.3   510   32   T   Y   510.32
4096 Vlantis, George   163   4 11.10.8.6 840   26   T   Y   840.26
4097 Vlantis, George    163   4 8.4.11    382   49   T   Y   382.49




5000 Canpolat, Necati   167   5 8.4.1.9   284   38   E   N   284.38
5001 Canpolat, Necati   167   5 8.4.1.9   284   38   T   Y   284.38




5002 Chu, Liwen         167   5 11.4.13   766   33   T   Y   766.33
5003 Chu, Liwen   167   5 10.14   698   36   T   Y   698.36
5004 Chu, Liwen         167   5 10.2.1.6   619   34   T   Y   619.34




5005 Ecclesine, Peter   167   5 8.5.9.4    455   17   E   N   455.17




5006 Ecclesine, Peter   167   5 12.2.1     836   34   E   N   836.34
5007 LANDT,        167   5 INTRO     iv    9    E   N    -3.91
     JEREMY




5008 Ramamurthy,   167   5 10.5.4    651   44   T   Y   651.44
     Harish




5009 Ramamurthy,   167   5 8.3.1.1   248   55   E   N   248.55
     Harish
5010 Ramamurthy,   167   5 8.3.3.9    271   37      E   N   271.37
     Harish




5011 Ramamurthy,   167   5 8.4.1.17   290   16-25   T   Y   290.16
     Harish




5012 Ramamurthy,   167   5 11.2.3.3. 725    44-46   T   N   725.44
     Harish                3




5013 Ramamurthy,   167   5 11.5.2     779   39-40   E   N   779.39
     Harish
5014 Vlantis, George   167   5 8.5.7.5   441   1   T   Y   441.01
5015 Vlantis, George    167   5 10.11.9.7 684   31   T   Y    684.31




#### Landt, Jeremy     1000   6                      T   Y




#### Song, Jae-Hyung 1000     6 Annex    1636   1    T   Y   1636.01
                                E.1
#### Song, Jae-Hyung 1000   6 Annex    1639   28   T   Y   1639.28
                              E.1




#### Anslow, Peter   1000   6 15.4.7.10 971   62   T   Y    971.62
#### Anslow, Peter   1000   6 3.3        31    59   T   N    31.59




#### Landt, Jeremy   1000   6 6.3.31.3   176   27   T   Y   176.27
#### Trainin, Solomon   1000   6 8.4.2.1   304   56   G   N   304.56




#### Stephens, Adrian 1000     6 10.3      628   58   T   Y   628.58
#### Landt, Jeremy   1000   6 Annex D 1630        1    T   Y   1630.01




#### Landt, Jeremy   1000   6 Annex E      1635   1    T   Y   1635.01




#### Mccann,         1000   6 8.4.2.10     311    54   E   N    311.54
     Stephen




#### Mccann,         1000   6 16.4.6.6. 1008      58   E   N   1008.58
     Stephen                  1


#### Mccann,         1000   6 Annex        1613   13   E   N   1613.13
     Stephen                  C.3


#### Mccann,         1000   6 Annex        1225   13   E   N   1225.13
     Stephen                  A.1



#### Mccann,         1000   6 Boilerplat          8    T   N
     Stephen                  e
#### Mccann,   1000   6 8.4.2.37   389   12   T   N   389.12
     Stephen




#### Mccann,   1000   6 8.4.2.1    304   45   E   N   304.45
     Stephen


#### Mccann,   1000   6 8.4.2.45   397   63   E   N   397.63
     Stephen
#### Mccann,   1000   6 8.3.3.2    265   36   T   N   265.36
     Stephen




#### Mccann,   1000   6 8.4.2.1    305   25   T   N   305.25
     Stephen
#### Adachi, Tomoko   1000   6 8.3.1.8   252   1   T   Y   252.01




#### Adachi, Tomoko   1000   6 8.3.1.9   255   1   T   Y   255.01
#### Fischer, Matthew   1000   6 9.20.4     549   41   T   Y   549.41




#### Fischer, Matthew   1000   6 9.20.7.2   551   13   T   Y   551.13
#### Fischer, Matthew   1000   6 9.20.7.6. 555    9    T   Y    555.09
                                 2




#### Fischer, Matthew   1000   6 9.20.7.6. 555    21   T   Y    555.21
                                 2




#### Fischer, Matthew   1000   6 19.3.20.2 1182   43   T   Y   1182.43




#### Fischer, Matthew   1000   6 19.3.20.1 1181   39   T   Y   1181.39
#### Fischer, Matthew   1000   6 4.2.3      35    35   T   Y    35.35




#### Fischer, Matthew   1000   6 9.19.2.4   530   34   T   Y   530.34
#### Fischer, Matthew   1000   6 9.3.2.11   487   1    T   Y   487.01




#### Fischer, Matthew   1000   6 9.3.2.11   487   12   T   Y   487.12
#### Fischer, Matthew   1000   6 9.19.2.4   530   7    T   Y   530.07




#### Fischer, Matthew   1000   6 9.18.5     525   37   T   Y   525.37




#### Fischer, Matthew   1000   6 9.3.2.11   487   9    T   Y   487.09
#### Fischer, Matthew   1000   6 6.3.3.3.2 84   36   T   Y   84.36




#### Fischer, Matthew   1000   6 6.3.3.3.2 86   46   T   Y   86.46

#### Fischer, Matthew   1000   6 4.3.7    42    48   T   Y   42.48
#### Fischer, Matthew   1000   6 10.8.5   662   19   T   Y   662.19
#### Fischer, Matthew   1000   6 10.8.5   1369   11   T   Y   1369.11




#### Fischer, Matthew   1000   6 10.8.2   660    62   T   Y    660.62




#### Fischer, Matthew   1000   6 10.8.1   660    17   T   Y    660.17




#### Fischer, Matthew   1000   6 10.8.3   661    15   T   Y    661.15
#### Fischer, Matthew   1000   6 10.8.4     661   65   T   Y   661.65




#### Fischer, Matthew   1000   6 8.1        227   12   T   Y   227.12




#### Fischer, Matthew   1000   6 8.1        227   15   T   Y   227.15




#### Fischer, Matthew   1000   6 6.3.14.1   129   46   T   Y   129.46
#### Fischer, Matthew   1000   6 3.1        11    39   T   Y    11.39




#### Fischer, Matthew   1000   6 8.4.1.11   286   16   T   Y   286.16
#### Fischer, Matthew   1000   6 8.5.8.2   444    50   T   Y    444.50




#### Fischer, Matthew   1000   6 8.5.8.2   446    46   T   Y    446.46




#### Fischer, Matthew   1000   6 B.3.4     1229   58   T   Y   1229.58




#### Fischer, Matthew   1000   6 8.3.3.2   264    7    T   Y    264.07
#### Fischer, Matthew    1000   6 9.3.2.8.1 483   39   T   Y   483.39




#### Adachi, Tomoko      1000   6 8.2.5.2   246   37   E   Y   246.37



#### Adachi, Tomoko      1000   6 8.2.5.2   246   37   E   Y   246.37




#### Seibert, Cristina   1000   6 5.2.13.5. 10    52   G   N    10.52
                                  4 and
                                  others




#### Seibert, Cristina   1000   6 5.2.13.5. 10    52   G   N    10.52
                                  4 and
                                  others
#### Fischer, Matthew   1000   6 10.11.9.1 678   6   T   Y   678.06




#### Fischer, Matthew   1000   6 10.11.9.1 678   6   T   Y   678.06




#### Armstrong, Lee     1000   6                     E   N
#### Sakoda,     1000   6 C.3       1382   16   T   N   1382.16
     Kazuyuki




#### Sakoda,     1000   6 C.3       1382   64   T   N   1382.64
     Kazuyuki




#### shi, yang   1000   6           89     44   E   N     89.44



#### shi, yang   1000   6 3.1       93     25   E   N     93.25




#### shi, yang   1000   6 1.3       91     9    E   N     91.09




#### shi, yang   1000   6 4.3.8.1   132    61   E   N    132.61
#### shi, yang        1000   6 8.2.2     316    36   E   N    316.36




#### shi, yang        1000   6 11.3.1    817    6    G   N    728.06




#### Perahia, Eldad   1000   6 17.3.9.7. 1182   38   T   N   1182.38
                               3




#### Perahia, Eldad   1000   6 17.3.11   1056   23   T   N   1056.23




#### Perahia, Eldad   1000   6 17.3.12   1058   27   T   N   1058.27




#### Perahia, Eldad   1000   6 19        1109   1    T   N   1109.01
#### Perahia, Eldad   1000   6 19.4.3    1202   51   T   N   1202.51




#### Perahia, Eldad   1000   6 19.3.22   1189   50   T   N   1189.50




#### Perahia, Eldad   1000   6 19.3.23   1193   14   T   N   1193.14




#### Perahia, Eldad   1000   6 19.3.20.1 1181   56   T   N   1181.56




#### Perahia, Eldad   1000   6 19.3.20.2 1182   38   T   N   1182.38
#### Perahia, Eldad   1000   6 19.3.11.4 1152   39   T   N   1152.39




#### Stephens, Adrian 1000   6 Annex C               T   Y   1350.00
#### Stanley, Dorothy   1000   6 8.4.1.1   277   59   T   Y   277.59




#### Stanley, Dorothy   1000   6 11.5.2    779   44   T   Y   779.44
#### Stanley, Dorothy   1000   6 11.3                  T   N    728.00




#### Stanley, Dorothy   1000   6 10.3     629     4    T   Y    629.04




#### Stanley, Dorothy   1000   6                       G   Y



#### Ptasinski, Henry   1000   6 19.3.20.2 1182   44   T   Y   1182.44




#### Ptasinski, Henry   1000   6 19.3.20.1 1181   39   G   Y   1181.39
#### Fischer, Matthew   1000   6 17.3.9.3   1049   21   T   Y   1049.21




#### Fischer, Matthew   1000   6 19.3.20.1 1181    39   T   Y   1181.39




#### Hansen,            1000   6 29         300    51   E   Y    300.51
     Christopher
#### Hansen,          1000   65         1143         E   Y   1143.00
     Christopher




#### Hansen,          1000   6 19.3.20.2 1182   43   T   Y   1182.43
     Christopher




#### Hansen,          1000   6 19.3.20.1 1181   39   T   Y   1181.39
     Christopher




#### Hamilton, Mark   1000   6 10.3     628     58   T   Y    628.58
#### Hamilton, Mark   1000   6 10.3   628   58   T   Y   628.58




#### Hamilton, Mark   1000   6 10.3   628   58   T   Y   628.58




#### Hamilton, Mark   1000   6 10.3   628   58   T   Y   628.58




#### Hamilton, Mark   1000   6 10.3   628   58   T   Y   628.58




#### Hamilton, Mark   1000   6 10.3   628   58   T   Y   628.58




#### Hamilton, Mark   1000   6 10.3   628   58   T   Y   628.58
#### Hamilton, Mark   1000   6 10.3.2.3   632   5    T   Y   632.05




#### Hamilton, Mark   1000   6 10.3       628   58   T   Y   628.58




#### Hamilton, Mark   1000   6 10.3       628   58   T   Y   628.58
#### Hamilton, Mark   1000   6 10.3   628   58   T   Y   628.58




#### Rosdahl, Jon     1000   6                   T   Y
#### Rosdahl, Jon   1000   6   626        T   Y   626.00




#### Rosdahl, Jon   1000   6   561   42   T   Y   561.42
#### Rosdahl, Jon   1000   6               T   Y




#### Rosdahl, Jon   1000   6   1645   21   T   Y   1645.21
#### Rosdahl, Jon   1000   6   1636   T   Y   1636.00




#### Rosdahl, Jon   1000   6          T   Y
#### Rosdahl, Jon   1000   6         T   Y




#### Rosdahl, Jon   1000   6   615   T   Y   615.00
#### Rosdahl, Jon   1000   6   626   T   Y   626.00




#### Rosdahl, Jon   1000   6   628   T   Y   628.00
#### Rosdahl, Jon      1000   6            1172   29   T   Y   1172.29




#### Worstell, Harry   1000   6 10.11.16 673      64   T   Y    673.64




#### Worstell, Harry   1000   6 10.11.11 687      42   T   Y    687.42




#### Worstell, Harry   1000   6 10.3.3.2   634    5    T   Y    634.05
#### Worstell, Harry   1000   6 12.9.3.1   863   54   T   Y   863.54




#### Worstell, Harry   1000   6 12.9.3.1   864   23   T   Y   864.23




#### Worstell, Harry   1000   6 12.9.5.1   868   49   T   Y   868.49




#### Worstell, Harry   1000   6 12.9.5.1   869   27   T   Y   869.27




#### Worstell, Harry   1000   6 11.5.2     779   33   T   Y   779.33
#### Worstell, Harry   1000   6C           1482   34   T   Y   1482.34




#### Worstell, Harry   1000   6 10.3.1     629    33   T   Y    629.33




#### Worstell, Harry   1000   6 10.3.2.3   632    5    T   Y    632.05
#### Worstell, Harry   1000   6                     T   Y




#### Worstell, Harry   1000   6          413   26   E   Y   413.26


#### Worstell, Harry   1000   6 10.9.1   662   46   E   Y   662.46



#### Worstell, Harry   1000   6 8.2.4    229   16   E   Y   229.16
#### Worstell, Harry   1000   6 8.4.2.29   375   14   E   N   375.14




#### Worstell, Harry   1000   6 11.3.2.5. 740    48   E   N   740.48
                                4
#### Worstell, Harry   1000   6 11.5.1.7 774     1    E   N   774.01




#### Worstell, Harry   1000   6 11.5.4.8   796   1    E   N   796.01




#### Worstell, Harry   1000   6 13.7.5     907   1    E   N   907.01


#### Worstell, Harry   1000   6 15.4.4.4   956   52   E   N   956.52

#### Worstell, Harry   1000   6 15.4.6.3   966   38   E   N   966.38


#### Worstell, Harry   1000   6 16.2.5     986   51   E   N   986.51
#### Fischer, Matthew   1000   6 Q.4      2000   47   T   Y   2000.47




#### Malinen, Jouni     1000   6 10.1.4.3. 610   46   T   Y    610.46
                                 2
#### Malinen, Jouni   1000   6 11.5.4.4   792   34   T   Y   792.34
#### Malinen, Jouni   1000   6 8.4.2.2    307   65   T   Y   307.65




#### Malinen, Jouni   1000   6 10.3       629   10   T   N   629.10




#### Malinen, Jouni   1000   6 10.3.2.3   632   22   T   Y   632.22
#### Malinen, Jouni   1000   6 11.5.2     779   33   E   Y   779.33




#### Malinen, Jouni   1000   6 11.7.2.7   832   12   T   Y   832.12




#### Malinen, Jouni   1000   6 11.7.2.7   832   44   T   Y   832.44
#### Vlantis, George   1000   6 8.5.7.5   441   1   T   Y   441.01
#### Vlantis, George   1000   6 10.11.9.7 684    31   T   Y    684.31




#### Vlantis, George   1000   6 10.15.1   698    59   T   Y    698.59




#### Kim, Youhan       1000   6 17.3.9.7. 1049   22   T   Y   1049.22
                                3
#### Kim, Youhan   1000   6 19.3.20.1 1181   39   T   Y   1181.39




#### Kim, Youhan   1000   6 19.3.20.1 1182   3    T   Y   1182.03




#### Kim, Youhan   1000   6 19.3.20.2 1182   43   T   Y   1182.43




#### Kim, Youhan   1000   6 Q.4      2000    53   T   Y   2000.53
#### Hiertz, Guido   1000   6                       T   Y




#### Hiertz, Guido   1000   6 3.1        18         T   Y    18.00




#### Hiertz, Guido   1000   6 3.3        34    62   T   Y    34.62




#### Hiertz, Guido   1000   6 11.5.7.1   809        T   Y   809.00
#### Hiertz, Guido   1000   6 H.2   1676   T   Y   1676.00




#### Hiertz, Guido   1000   6 H.2   1699   T   Y   1699.00




#### Hiertz, Guido   1000   6 H.3   1730   T   Y   1730.00




#### Hiertz, Guido   1000   6 H.3   1796   T   Y   1796.00
#### Hiertz, Guido      1000   6 H.4   1805        T   Y   1805.00




#### Hiertz, Guido      1000   6 H.4   1810        T   Y   1810.00




#### Hiertz, Guido      1000   6 H.4   1867        T   Y   1867.00




#### Ecclesine, Peter   1000   6 D.1   1633   39   T   Y   1633.39
#### Ecclesine, Peter   1000   6 D.1   1632   14   T   Y   1632.14




#### Ecclesine, Peter   1000   6 E.1   1636   14   T   Y   1636.14




#### Ecclesine, Peter   1000   6 E.1   1638   21   T   Y   1638.21




#### Ecclesine, Peter   1000   6 E.1   1641   51   T   Y   1641.51




#### Ecclesine, Peter   1000   6 E.1   1645   31   T   Y   1645.31
#### Ecclesine, Peter   1000   6 E.1       1638   16   T   Y   1638.16




#### Ecclesine, Peter   1000   6 E.1       1641   50   T   Y   1641.50




#### Ecclesine, Peter   1000   6 E.1       1646   50   T   Y   1646.50




#### Ecclesine, Peter   1000   6 10.10.1   669    17   T   N    669.17
#### Ecclesine, Peter   1000   6 9.18.5   525   28   T   Y   525.28




#### Ecclesine, Peter   1000   6 9.18.6   525   54   T   Y   525.54




#### Ecclesine, Peter   1000   6 9.18.5   525   40   T   Y   525.40




#### Ecclesine, Peter   1000   66         79    1    T   Y    79.01
#### Hunter, David   1000   61      1    1    G   Y    1.01




#### Hunter, David   1000   6 3.1   5    62   E   Y    5.62




#### Hunter, David   1000   6 3.1   7    8    T   Y    7.08




#### Hunter, David   1000   6 3.1   12   21   T   Y   12.21




#### Hunter, David   1000   6 3.1   15   32   T   Y   15.32




#### Hunter, David   1000   6 3.2   20   10   T   Y   20.10




#### Hunter, David   1000   6 3.2   20   17   T   Y   20.17




#### Hunter, David   1000   6 3.2   22   26   E   Y   22.26




#### Hunter, David   1000   6 3.2   25   40   T   Y   25.40
#### Hunter, David   1000   6 3.2       25   45   E   Y   25.45




#### Hunter, David   1000   6 3.3       31   15   E   Y   31.15




#### Hunter, David   1000   6 3.3       31   24   E   Y   31.24




#### Hunter, David   1000   6 4.2.3     35   47   T   Y   35.47




#### Hunter, David   1000   6 4.2.4     36   15   T   Y   36.15




#### Hunter, David   1000   6 4.3.4.2   39   64   T   Y   39.64




#### Hunter, David   1000   6 4.3.7     42   34   T   Y   42.34
#### Hunter, David   1000   6 4.3.9.5   46   62   T   Y   46.62




#### Hunter, David   1000   6 4.5.3.3   52   15   T   Y   52.15




#### Hunter, David   1000   6 4.5.3.3   52   21   T   Y   52.21




#### Hunter, David   1000   6 4.5.3.4   52   49   T   Y   52.49




#### Hunter, David   1000   6 4.6       57   65   T   Y   57.65




#### Hunter, David   1000   6 4.7       60   1    T   Y   60.01



#### Hunter, David   1000   6 4.8       60   20   E   Y   60.20
#### Hunter, David   1000   6 4.8       60   22   E   Y   60.22




#### Hunter, David   1000   6 4.9.3.2   61   39   T   Y   61.39


#### Hunter, David   1000   6 4.9.3.4   65   56   T   Y   65.56




#### Hunter, David   1000   6 4.9.4.2   66   12   T   Y   66.12


#### Hunter, David   1000   6 4.9.4.3   66   42   T   Y   66.42


#### Hunter, David   1000   6 4.9.4.4   67   45   T   Y   67.45




#### Hunter, David   1000   6 4.9.5     68   46   T   Y   68.46


#### Hunter, David   1000   6 5.1.1.1   70   14   T   Y   70.14




#### Hunter, David   1000   6 5.1.1.5   72   10   E   Y   72.10
#### Hunter, David   1000   6 5.1.3     73   44   T   Y   73.44


#### Hunter, David   1000   6 5.2.2.2   75   56   T   Y   75.56


#### Hunter, David   1000   6 5.2.3.2   76   58   E   Y   76.58




#### Hunter, David   1000   6 6.3.2.2.2 81   28   E   Y   81.28




#### Hunter, David   1000   6 6.3.3.2.2 83   17   T   Y   83.17




#### Hunter, David   1000   6 6.3.3.3.2 85   27   T   Y   85.27


#### Hunter, David   1000   6 6.3.3.3.2 88   23   T   Y   88.23




#### Hunter, David   1000   6 6.3.4.2.2 91   25   T   Y   91.25




#### Hunter, David   1000   6 6.3.4.2.2 91   33   T   Y   91.33


#### Hunter, David   1000   6 6.3.5.2.2 93   20   T   Y   93.20




#### Hunter, David   1000   6 6.3.5.3.2 94   7    T   Y   94.07
#### Hunter, David   1000   6 6.3.7.2.2 99    31   T   Y    99.31




#### Hunter, David   1000   6 6.3.8.2.2 108   25   T   Y   108.25




#### Hunter, David   1000   6 6.3.10.2. 119   5    T   Y   119.05
                              3

#### Hunter, David   1000   6 6.3.11.2. 120   49   T   Y   120.49
                              2

#### Hunter, David   1000   6 6.3.11.2. 121   53   T   Y   121.53
                              2

#### Hunter, David   1000   6 6.3.11.2. 122   33   T   Y   122.33
                              3




#### Hunter, David   1000   6 6.3.11.2. 122   38   T   Y   122.38
                              3

#### Hunter, David   1000   6 6.3.12.1. 123   64   T   Y   123.64
                              3

#### Hunter, David   1000   6 6.3.12.1. 124   2    T   Y   124.02
                              3

#### Hunter, David   1000   6 6.3.12.1. 124   2    E   Y   124.02
                              3

#### Hunter, David   1000   6 6.3.14.2. 129   61   E   Y   129.61
                              2




#### Hunter, David   1000   6 6.3.14.2. 130   11   T   Y   130.11
                              2



#### Hunter, David   1000   6 6.3.14.2. 130   12   T   Y   130.12
                              2
#### Hunter, David   1000   6 6.3.16.3. 135   5    T   Y   135.05
                              2



#### Hunter, David   1000   6 6.3.19.1. 143   35   T   Y   143.35
                              4



#### Hunter, David   1000   6 6.3.24.1. 148   57   T   Y   148.57
                              4



#### Hunter, David   1000   6 6.3.26.2. 151   34   T   Y   151.34
                              1



#### Hunter, David   1000   6 6.3.29.3. 168   6    T   Y   168.06
                              2


#### Hunter, David   1000   6 6.3.29.5. 170   6    T   Y   170.06
                              2


#### Hunter, David   1000   6 6.3.29.7. 172   6    T   Y   172.06
                              3


#### Hunter, David   1000   6 6.3.39.1. 199   24   T   Y   199.24
                              2



#### Hunter, David   1000   6 6.3.39.2. 200   20   T   Y   200.20
                              2


#### Hunter, David   1000   6 6.4.3.4   208   22   T   Y   208.22




#### Hunter, David   1000   6 6.4.4.2   209   32   T   Y   209.32




#### Hunter, David   1000   6 6.4.4.2   209   34   T   Y   209.34
#### Hunter, David   1000   6 6.4.4.3   211   17   T   Y   211.17




#### Hunter, David   1000   6 6.4.5.2   211   39   E   Y   211.39




#### Hunter, David   1000   6 6.4.7.1   213   31   T   Y   213.31




#### Hunter, David   1000   6 6.4.8.1   213   64   T   Y   213.64




#### Hunter, David   1000   6 7.3.5.2.4 218   47   T   Y   218.47




#### Hunter, David   1000   6 7.3.5.3.3 219   6    T   Y   219.06




#### Hunter, David   1000   6 7.3.5.4.3 219   33   T   Y   219.33




#### Hunter, David   1000   6 7.3.5.4.3 219   34   T   Y   219.34




#### Hunter, David   1000   6 7.3.5.4.4 219   40   T   Y   219.40




#### Hunter, David   1000   6 7.3.5.5.3 219   64   T   Y   219.64
#### Hunter, David   1000   6 7.3.5.5.4 220   4    T   Y   220.04




#### Hunter, David   1000   6 7.3.5.6.1 220   16   T   Y   220.16




#### Hunter, David   1000   6 7.3.5.6.3 220   30   T   Y   220.30




#### Hunter, David   1000   6 7.3.5.6.4 220   37   T   Y   220.37




#### Hunter, David   1000   6 7.3.5.7.3 220   59   T   Y   220.59




#### Hunter, David   1000   6 7.3.5.7.4 220   65   T   Y   220.65




#### Hunter, David   1000   6 7.3.5.8.3 221   22   T   Y   221.22




#### Hunter, David   1000   6 7.3.5.12. 223   58   E   Y   223.58
                              2




#### Hunter, David   1000   6 8.2.4.1.2 229   46   T   Y   229.46
#### Hunter, David   1000   6 8.2.4.1.7 231    46   T   Y   231.64




#### Hunter, David   1000   6 8.2.4.1.8 232    10   E   Y   232.10



#### Hunter, David   1000   6 8.2.4.1.9 232    47   T   Y   232.47


#### Hunter, David   1000   6 8.2.4.5.4 238    41   E   Y   238.41



#### Hunter, David   1000   6 8.2.5.4    246   56   E   Y   246.56




#### Hunter, David   1000   6 8.3.3.2    265   55   E   Y   265.55


#### Hunter, David   1000   6 8.4.1.15   288   63   T   Y   288.63




#### Hunter, David   1000   6 8.4.1.17   290   40   T   Y   290.40




#### Hunter, David   1000   6 8.4.2.14   315   42   E   Y   315.42




#### Hunter, David   1000   6 8.4.2.23. 321    37   T   Y   321.37
                              1



#### Hunter, David   1000   6 8.4.2.23. 322    24   T   Y   322.24
                              1
#### Hunter, David   1000   6 8.4.2.23. 338     53   T   Y   338.53
                              11



#### Hunter, David   1000   6 8.4.2.23. 339     29   T   Y   339.29
                              11



#### Hunter, David   1000   6 8.4.2.24. 343     14   T   Y   343.14
                              2




#### Hunter, David   1000   6 8.4.2.24.   343   18   E   Y   343.18
                              2
#### Hunter, David   1000   6 8.4.2.24.   362   4    E   Y   362.04
                              10
#### Hunter, David   1000   6 8.4.2.24.   363   38   E   Y   363.38
                              11
#### Hunter, David   1000   6 8.4.2.23.   363   38   T   Y   363.38
                              11



#### Hunter, David   1000   6 8.4.2.47. 370     35   T   Y   370.35
                              3

#### Hunter, David   1000   6 8.4.2.27. 371     38   E   Y   371.38
                              3




#### Hunter, David   1000   6 8.4.2.27. 373     35   T   Y   373.35
                              4
#### Hunter, David   1000   6 8.4.2.27. 374    5    E   Y   374.05
                              5




#### Hunter, David   1000   6 8.4.2.29   376   43   T   Y   376.43




#### Hunter, David   1000   6 8.4.2.30   378   2    T   Y   378.02



#### Hunter, David   1000   6 8.4.2.30   378   2    T   Y   378.02




#### Hunter, David   1000   6 8.4.2.32   380   39   E   Y   380.39

#### Hunter, David   1000   6 8.4.2.32   383   20   E   Y   383.20




#### Hunter, David   1000   6 8.4.2.32   383   20   T   Y   383.20




#### Hunter, David   1000   6 8.4.2.33   384   52   E   Y   384.52

#### Hunter, David   1000   6 8.4.2.33   385   33   E   Y   385.33



#### Hunter, David   1000   6 8.4.2.33   385   34   T   Y   385.34


#### Hunter, David   1000   6 8.4.2.34   387   29   T   Y   387.29

#### Hunter, David   1000   6 8.4.2.34   387   29   T   Y   387.29
#### Hunter, David   1000   6 8.4.2.42   395   30   T   Y   395.30




#### Hunter, David   1000   6 8.4.2.45   397   10   T   Y   397.10



#### Hunter, David   1000   6 8.4.2.50   403   53   E   Y   403.53


#### Hunter, David   1000   6 9.3.1      476   31   E   Y   476.31


#### Hunter, David   1000   6 9.3.2.6    482   2    T   Y   482.02




#### Hunter, David   1000   6 9.3.2.6    482   6    T   Y   482.06




#### Hunter, David   1000   6 9.3.2.6    482   7    T   Y   482.07




#### Hunter, David   1000   6 9.3.2.8.1 483    52   T   Y   483.52




#### Hunter, David   1000   6 9.3.2.8.1 483    65   T   Y   483.65




#### Hunter, David   1000   6 9.3.4.3    491   2    T   Y   491.02




#### Hunter, David   1000   6 9.3.4.4    492   6    T   Y   492.06
#### Hunter, David   1000   6 9.4.2     497   64   E   Y   497.64




#### Hunter, David   1000   6 9.7.3     505   63   E   Y   505.63




#### Hunter, David   1000   6 9.7.5.2   508   54   T   Y   508.54




#### Hunter, David   1000   6 9.8       516   55   T   Y   516.55




#### Hunter, David   1000   6 9.12.2    518   60   T   Y   518.60




#### Hunter, David   1000   6 9.12.2    519   1    T   Y   519.01




#### Hunter, David   1000   6 9.18.1    521   13   T   Y   521.13




#### Hunter, David   1000   6 9.18.1    521   18   T   Y   521.18
#### Hunter, David   1000   6 9.18.1     521   20   T   Y   521.20



#### Hunter, David   1000   6 9.18.3     523   47   T   Y   523.47




#### Hunter, David   1000   6 9.19.2.7   526   26   T   Y   526.26




#### Hunter, David   1000   6 9.19.3.3   537   56   T   Y   537.56




#### Hunter, David   1000   6 9.19.3.3   537   57   T   Y   537.57


#### Hunter, David   1000   6 9.20.7.7   556   34   T   Y   556.34




#### Hunter, David   1000   6 9.22.2     559   28   T   Y   559.28




#### Hunter, David   1000   6 9.22.2     559   38   T   Y   559.38




#### Hunter, David   1000   6 9.22.2     560   32   T   Y   560.32




#### Hunter, David   1000   6 9.22.4     564   53   T   Y   564.53




#### Hunter, David   1000   6 9.25.1.1   574   46   T   Y   574.46
#### Hunter, David   1000   6 9.27.2     584   54   T   Y   584.54




#### Hunter, David   1000   6 9.28.2.3   589   64   T   Y   589.64




#### Hunter, David   1000   6 9.29.2     599   65   T   Y   599.65




#### Hunter, David   1000   6 9.29.2     602   44   T   Y   602.44




#### Hunter, David   1000   6 9.29.2     602   46   T   Y   602.46




#### Hunter, David   1000   6 9.29.2     602   48   T   Y   602.48




#### Hunter, David   1000   6 10.1.4.1   609   33   T   Y   609.33




#### Hunter, David   1000   6 10.1.4.5   612   6    T   Y   612.06




#### Hunter, David   1000   6 10.1.4.6   613   23   T   Y   613.23
#### Hunter, David   1000   6 10.1.4.6   613   26   T   Y   613.26




#### Hunter, David   1000   6 10.1.4.6   613   27   T   Y   613.27




#### Hunter, David   1000   6 10.1.5     613   64   T   Y   613.64




#### Hunter, David   1000   6 10.1.8     614   63   T   Y   614.63




#### Hunter, David   1000   6 10.2.1.2   616   28   E   Y   616.28




#### Hunter, David   1000   6 10.2.1.6   619   18   E   Y   619.18


#### Hunter, David   1000   6 10.4.6     643   30   E   Y   643.30

#### Hunter, David   1000   6 10.4.9     645   65   T   Y   645.65




#### Hunter, David   1000   6 10.8.1     660   41   T   Y   660.41




#### Hunter, David   1000   6 10.9.1     663   12   T   Y   663.12




#### Hunter, David   1000   6 10.9.8.3   666   38   T   Y   666.38
#### Hunter, David   1000   6 10.9.8.3   667   17   T   Y   667.17




#### Hunter, David   1000   6 10.11.1    671   24   T   Y   671.24




#### Hunter, David   1000   6 10.11.4    672   50   T   Y   672.50




#### Hunter, David   1000   6 10.11.4    672   57   T   Y   672.57




#### Hunter, David   1000   6 10.11.6    675   60   T   Y   675.60




#### Hunter, David   1000   6 10.11.1    671   24   T   Y   671.24




#### Hunter, David   1000   6 10.11.9.4 682    33   T   Y   682.33




#### Hunter, David   1000   6 10.11.9.4 682    36   T   Y   682.36




#### Hunter, David   1000   6 10.11.9.6 684    7    E   Y   684.07

#### Hunter, David   1000   6 10.11.9.8 685    29   T   Y   685.29


#### Hunter, David   1000   6 10.11.10. 686    55   T   Y   686.55
                              1
#### Hunter, David   1000   6 10.11.12 688    6    T   Y   688.06




#### Hunter, David   1000   6 10.11.15. 690   26   T   Y   690.26
                              2



#### Hunter, David   1000   6 10.16.3   714   23   T   Y   714.23




#### Hunter, David   1000   6 10.18     715   55   T   Y   715.55




#### Hunter, David   1000   6 10.18     716   13   T   Y   716.13




#### Hunter, David   1000   6 10.18     716   21   T   Y   716.21
#### Hunter, David   1000   6 11         717   1    T   Y   717.01




#### Hunter, David   1000   6 11.1.6     719   55   T   Y   719.55


#### Hunter, David   1000   6 11.1.6     719   62   T   Y   719.62


#### Hunter, David   1000   6 11.2.3.1   723   64   T   Y   723.64


#### Hunter, David   1000   6 11.3.2.1. 729    39   T   Y   729.39
                              2



#### Hunter, David   1000   6 11.3.2.2   731   27   T   Y   731.27


#### Hunter, David   1000   6 11.3.2.4. 734    39   T   Y   734.39
                              1


#### Hunter, David   1000   6 11.3.2.4. 734    40   T   Y   734.40
                              1
#### Hunter, David   1000   6 11.3.2.4. 736   41   T   Y   736.41
                              2




#### Hunter, David   1000   6 11.3.2.5. 741   39   T   Y   741.39
                              4



#### Hunter, David   1000   6 11.3.3.4. 747   48   T   Y   747.48
                              2




#### Hunter, David   1000   6 11.4.1.1. 751   23   T   Y   751.23
                              1

#### Hunter, David   1000   6 11.4.1.2. 755   24   T   Y   755.24
                              2



#### Hunter, David   1000   6 11.4.1.2. 755   42   T   Y   755.42
                              2



#### Hunter, David   1000   6 11.4.1.2. 755   45   T   Y   755.45
                              2

#### Hunter, David   1000   6 11.4.1.2. 756   12   T   Y   756.12
                              2

#### Hunter, David   1000   6 11.4.5   758    59   T   Y   758.59


#### Hunter, David   1000   6 11.4.5   759    6    E   Y   759.06

#### Hunter, David   1000   6 11.4.5   759    10   T   Y   759.10


#### Hunter, David   1000   6 11.4.5   759    27   T   Y   759.27
#### Hunter, David   1000   6 11.4.5     759   27   E   Y   759.27



#### Hunter, David   1000   6 11.4.8.3   762   51   T   Y   762.51




#### Hunter, David   1000   6 11.4.9     763   26   T   Y   763.26


#### Hunter, David   1000   6 11.4.10    764   43   T   Y   764.43



#### Hunter, David   1000   6 11.4.11    765   1    T   Y   765.01


#### Hunter, David   1000   6 11.4.11    765   56   T   Y   765.56




#### Hunter, David   1000   6 11.5.1.2   768   44   T   Y   768.44




#### Hunter, David   1000   6 11.5.1.2   768   45   T   Y   768.45




#### Hunter, David   1000   6 11.5.1.2   768   47   T   Y   768.47



#### Hunter, David   1000   6 11.5.1.2   768   47   T   Y   768.47
#### Hunter, David   1000   6 11.5.1.3   769   4    E   Y   769.04




#### Hunter, David   1000   6 11.5.1.3   769   36   T   Y   769.36




#### Hunter, David   1000   6 11.5.1.3   769   41   T   Y   769.41




#### Hunter, David   1000   6 11.5.1.3   769   47   T   Y   769.47




#### Hunter, David   1000   6 11.5.1.3   769   49   T   Y   769.49




#### Hunter, David   1000   6 11.5.1.3   769   54   T   Y   769.54
#### Hunter, David   1000   6 11.5.1.3   770   13   T   Y   770.13




#### Hunter, David   1000   6 11.5.1.4   770   58   T   Y   770.58




#### Hunter, David   1000   6 11.5.2     781   64   T   Y   781.64



#### Hunter, David   1000   6 11.5.3     787   52   E   Y   787.52




#### Hunter, David   1000   6 11.5.4.1   789   4    T   Y   789.04




#### Hunter, David   1000   6 11.5.4.6   795   27   T   Y   795.27
#### Hunter, David   1000   6 11.5.4.6   795   29   T   Y   795.29




#### Hunter, David   1000   6 11.5.6.6   806   20   T   Y   806.20




#### Hunter, David   1000   6 11.5.7.3   812   32   T   Y   812.32


#### Hunter, David   1000   6 11.5.7.3   812   40   T   Y   812.40




#### Hunter, David   1000   6 11.5.7.3   812   42   T   Y   812.42
#### Hunter, David   1000   6 11.5.8     813   64   T   Y   813.64




#### Hunter, David   1000   6 11.5.9.1   814   7    T   Y   814.07



#### Hunter, David   1000   6 12.5.2     842   45   T   Y   842.45




#### Hunter, David   1000   6 12.5.3     844   25   T   Y   844.25




#### Hunter, David   1000   6 12.5.4     846   37   T   Y   846.37


#### Hunter, David   1000   6 12.5.5     847   39   T   Y   847.39


#### Hunter, David   1000   6 12.6.2     849   9    T   Y   849.09
#### Hunter, David   1000   6 12.5.2     850   9    T   Y   850.09




#### Hunter, David   1000   6 12.6.3     851   19   T   Y   851.19




#### Hunter, David   1000   6 12.6.3     852   10   T   Y   852.10




#### Hunter, David   1000   6 12.8.1     856   38   E   Y   856.38




#### Hunter, David   1000   6 13.4.2     883   23   T   Y   883.23



#### Hunter, David   1000   6 13.4.4.2. 887    41   T   Y   887.41
                              2

#### Hunter, David   1000   6 13.4.4.4. 894    19   T   Y   894.19
                              2

#### Hunter, David   1000   6 13.9.2.1   920   60   T   Y   920.60


#### Hunter, David   1000   6 13.9.2.2   921   32   T   Y   921.32
#### Hunter, David   1000   6 14.3.1     929    14   T   Y    929.14



#### Hunter, David   1000   6 14.5       941    27   T   Y    941.27


#### Hunter, David   1000   6 16.3.3.6   981    46   T   Y    981.46




#### Hunter, David   1000   6 16.4.6.7   1011   22   T   Y   1011.22




#### Hunter, David   1000   6 17.3.9.3   1049   14   T   Y   1049.14


#### Hunter, David   1000   6 18.7.3.3   1095   10   T   Y   1095.10




#### Hunter, David   1000   6 19.3.2     1125   29   T   Y   1125.29




#### Hunter, David   1000   6 19.3.12.2 1170    51   T   Y   1170.51




#### Hunter, David   1000   6 19.3.7     1134   29   T   Y   1134.29
#### Hunter, David   1000   6 B.3.1     1228   51   T   Y   1228.51




#### Hunter, David   1000   6 B.4.1     1230   40   T   Y   1230.40




#### Hunter, David   1000   6 B.4.4.1   1245   23   E   Y   1245.23




#### Hunter, David   1000   6 C.3       1351   11   T   Y   1351.11




#### Hunter, David   1000   6 C.3       1491   33   E   Y   1491.33




#### Hunter, David   1000   6 C.3       1504   34   E   Y   1504.34
#### Hunter, David   1000   6 C.3   1557   33   T   Y   1557.33




#### Hunter, David   1000   6 D.1   1632   13   T   Y   1632.13
#### Hunter, David   1000   6 D.1   1633   52   E   Y   1633.52




#### Hunter, David   1000   6H      1667   47   T   Y   1667.47




#### Hunter, David   1000   6 H.2   1683   15   T   Y   1683.15
#### Hunter, David   1000   6 H.3   1731       43   E   Y   1731.43




#### Hunter, David   1000   6 H.3   1841       17   E   Y   1841.17




#### Hunter, David   1000   6 Q.2   1991       36   E   Y   1991.36




#### Kenney, John    1000   6       9.3.2.11        T   N      0.00
#### Armstrong, Lee   0   6.01   T   N     2.00




#### Armstrong, Lee   0   6.01   T   N    43.00




#### Armstrong, Lee   0   6.01   E   N   181.00


#### Armstrong, Lee   0   6.01   E   N   182.00




#### Armstrong, Lee   0   6.01   E   N   182.00


#### Armstrong, Lee   0   6.01   T   N   244.00
#### Armstrong, Lee   0   6.01   E   N   217.00


#### Armstrong, Lee   0   6.01   E   N   386.00




#### Armstrong, Lee   0   6.01   E   N   440.00




#### Armstrong, Lee   0   6.01   T   N




#### Armstrong, Lee   0   6.01   E   N   452.00




#### Armstrong, Lee   0   6.01   E   N   213.00




#### Armstrong, Lee   0   6.01   E   N   742.64
#### Armstrong, Lee   0   6.01   T   N   1270.00




#### Armstrong, Lee   0   6.01   T   N   1282.13




#### Armstrong, Lee   0   6.01   T   N   1282.20




#### Armstrong, Lee   0   6.01   T   N   1282.27




#### Armstrong, Lee   0   6.01   T   N   1282.38




#### Armstrong, Lee   0   6.01   T   N   1282.52




#### Armstrong, Lee   0   6.01   T   N   1283.53




#### Armstrong, Lee   0   6.01   T   N   1283.60




#### Armstrong, Lee   0   6.01   T   N   1284.17
#### Armstrong, Lee   0   6.01   T   N   1316.00



#### Armstrong, Lee   0   6.01   T   N   1323.56


#### Armstrong, Lee   0   6.01   T   N   1323.40


#### Armstrong, Lee   0   6.01   E   N   1631.00




#### Armstrong, Lee   0   6.01   E   N   1631.00



#### Armstrong, Lee   0   6.01   T   N   1680.00




#### Armstrong, Lee   0   6.01   T   N
#### Armstrong, Lee     0   6.01   T   N   1683.00




#### Armstrong, Lee     0   6.01   T   N




#### Armstrong, Lee     0   6.01   T   N




#### Ecclesine, Peter   0   6.01   E   N   1679.44


#### Ecclesine, Peter   0   6.01   E   N   1683.00
#### Goodall, David   0   6.01   T   N     48.00




#### Hamilton, Mark   0   6.01   T   N      2.00



#### Hamilton, Mark   0   6.01   E   N    246.00




#### Hamilton, Mark   0   6.01   E   N    318.00




#### Hamilton, Mark   0   6.01   T   N   1394.00




#### Kenney, John     0   6.01   E   N      2.00
#### Kenney, John   0   6.01   T   N   244.56




#### Kenney, John   0   6.01   T   N   272.00




#### Kenney, John   0   6.01   T   N   316.00
#### Kenney, John   0   6.01   E   N    386.00




#### Kenney, John   0   6.01   T   N    386.00




#### Kenney, John   0   6.01   E   N    742.64



#### Kenney, John   0   6.01   E   N   1085.00




#### Kenney, John   0   6.01   T   N   1270.00




#### Kenney, John   0   6.01   T   N   1281.00
#### Kenney, John   0   6.01   T   N   1323.00




#### Kenney, John   0   6.01   T   N   1323.00




#### Kenney, John   0   6.01   E   N   1682.00




#### Kenney, John   0   6.01   T   N   1683.14
#### Kenney, John        0   6.01   T   N   1683.00




#### LANDT,              0   6.01   E   N    386.00
     JEREMY




#### LANDT,              0   6.01   E   N    742.64
     JEREMY




#### LANDT,              0   6.01   E   N   1085.00
     JEREMY




#### Malarky, Alastair   0   6.01   E   N
#### Malarky, Alastair   0   6.01   E   N




#### Malarky, Alastair   0   6.01   E   N     2.00


#### Malarky, Alastair   0   6.01   T   N




#### Malarky, Alastair   0   6.01   E   N   213.55




#### Malarky, Alastair   0   6.01   E   N   316.13
#### Malarky, Alastair   0   6.01   E   N    316.22




#### Malarky, Alastair   0   6.01   E   N    386.00




#### Malarky, Alastair   0   6.01   E   N    452.40




#### Roy, Dick           0   6.01   T   N




#### Roy, Dick           0   6.01   T   N   1690.37




#### Stephens, Adrian    0   6.01   T   N    182.00




#### Stephens, Adrian    0   6.01   T   N    213.00
#### Stephens, Adrian   0   6.01   T   N   237.00




#### Stephens, Adrian   0   6.01   T   N   270.00


#### Stephens, Adrian   0   6.01   T   N   272.00


#### Stephens, Adrian   0   6.01   T   N   288.00




#### Stephens, Adrian   0   6.01   T   N   316.00
#### Stephens, Adrian   0   6.01   T   N    316.00




#### Stephens, Adrian   0   6.01   T   N    386.00




#### Stephens, Adrian   0   6.01   T   N    386.00




#### Stephens, Adrian   0   6.01   T   N    452.00




#### Stephens, Adrian   0   6.01   T   N    467.00




#### Stephens, Adrian   0   6.01   T   N    712.00




#### Stephens, Adrian   0   6.01   T   N   1270.00




#### Stephens, Adrian   0   6.01   T   N   1281.00
#### Stephens, Adrian   0   6.01   T   N   1316.00



#### Stephens, Adrian   0   6.01   T   N   1323.44



#### Stephens, Adrian   0   6.01   T   N   1631.00




#### Stephens, Adrian   0   6.01   E   N




#### Vlantis, George    0   6.01   E   N   1679.00




#### Vlantis, George    0   6.01   T   N   1682.00




#### Vlantis, George    0   6.01   T   N   1682.00
#### Vlantis, George    0   6.01   T   N   1696.00




#### Stephens, Adrian   0     6    T   N      0.00




#### Stephens, Adrian   0   6.02   T   N      0.00
#### Stephens, Adrian 1001   7 6.3.7.5.2 111    21   T   Y   111.21




#### Stephens, Adrian 1001   7 6.3.8.5.2 120    23   T   Y   120.23


#### Stephens, Adrian 1001   7 8.2.4.1.8 283    37   T   Y   283.37


#### Stephens, Adrian 1001   7 8.4.1.11   340   5    T   Y   340.05




#### Stephens, Adrian 1001   7                       E   N




#### Stephens, Adrian 1001   7 8.4.2.27. 425    30   T   Y   425.30
                               3

#### Stephens, Adrian 1001   7 8.5.8.12   512   50   T   Y   512.50
#### Stephens, Adrian 1001   7 10.2.1.14 699    47   T   Y   699.47


#### Stephens, Adrian 1001   7 10.2.1.15 702    43   T   Y   702.43


#### Stephens, Adrian 1001   7 10.3.2.3   712   18   T   Y   712.18




#### Stephens, Adrian 1001   7 10.3.3.2   714   10   T   Y   714.10




#### Stephens, Adrian 1001   7 10.3.3.3   714   24   T   Y   714.24




#### Stephens, Adrian 1001   7 10.3.3.3   715   6    T   Y   715.06
#### Stephens, Adrian 1001   7 10.3.3.3   715   47   T   Y   715.47




#### Stephens, Adrian 1001   7 10.3.3.4   716   31   T   Y   716.31




#### Stephens, Adrian 1001   7 10.10.1    750   23   T   Y   750.23




#### Stephens, Adrian 1001   7 11.5.11.4 919    29   T   N   919.29
                               .2



#### Stephens, Adrian 1001   7 11.5.11.4 920    58   T   N   920.58
                               .3

#### Stephens, Adrian 1001   7 11.5.11.4 921    48   T   Y   921.48
                               .4
#### Stephens, Adrian 1001   7 12.9.3.1   964    42   T   N    964.42




#### Stephens, Adrian 1001   7 Annex S    2099   12   T   Y   2099.12




#### Stephens, Adrian 1001   7 Annex                  T   Y
                               C.3
#### Stephens, Adrian 1001   7 General               T   Y




#### Stephens, Adrian 1001   7 17.3.9.7. 1153   22   T   Y   1153.22
                               3




#### Stephens, Adrian 1001   7 8.5.8.11   511   63   T   N    511.63
#### Stephens, Adrian 1001   7 General               T   Y



#### Malinen, Jouni   1001   7 8.5.13.3   526   35   T   Y   526.35




#### Malinen, Jouni   1001   7 8.5.13.4   528   58   T   Y   528.58
#### Malinen, Jouni   1001   7 8.5.13.7   530   31   T   Y   530.31




#### Malinen, Jouni   1001   7 8.5.13.7   530   34   T   Y   530.34
#### Malinen, Jouni   1001   7 11.5.11.2 917   18   T   Y   917.18




#### Malinen, Jouni   1001   7 11.5.11.4 919   2    T   Y   919.02
                               .2




#### Malinen, Jouni   1001   7 11.5.11.4 919   32   E   Y   919.32
                               .2




#### Malinen, Jouni   1001   7 10.22.5   802   42   T   Y   802.42
#### Malinen, Jouni   1001   7 10.22.6.2 806    58   E   Y    806.58
                               .1




#### Malinen, Jouni   1001   7 10.22.6.2 806    62   T   N    806.62
                               .1




#### Malinen, Jouni   1001   7 10.22.5   803    1    E   Y    803.01




#### Malinen, Jouni   1001   7 D.2.3     1721   62   E   N   1721.62




#### Malinen, Jouni   1001   7 E.1       1727   61   E   N   1727.61
#### Malinen, Jouni   1001   7 10.22.6   805   58   T   Y   805.58
#### Malinen, Jouni   1001   7 8.4.1.11   340    6    T   Y    340.06




#### Malinen, Jouni   1001   7 C.3        1470   31   T   N   1470.31
#### Malinen, Jouni   1001   7 8.4.2.2   361   59   T   Y   361.59
#### Malinen, Jouni   1001   7 10.3.2.4   712   23   T   Y   712.23




#### Malinen, Jouni   1001   7 6.3.9.1.3 122    39   T   N   122.39
#### Kraemer, Bruce   1001   7 10.2.1.15 703   57    T   Y   703.57
                               .2




#### Kraemer, Bruce   1001   7 11.5.11.4 920   63    E   Y   920.63
                               .3


#### Kraemer, Bruce   1001   7 10.22.6   805   57    T   Y   805.57




#### Kraemer, Bruce   1001   7 11.5.11.4 53    921   T   Y    71.21
                               .4
#### Kraemer, Bruce   1001   7 11.4.1.2   847   16   E   Y   847.16



#### Kraemer, Bruce   1001   7 8.5.13.2   524   52   E   Y   524.52




#### Kraemer, Bruce   1001   7 10.2.1.15 703    11   T   Y   703.11
#### Malinen, Jouni   1001   7           0     14   E   Y     0.14




#### Malinen, Jouni   1001   7 8.4.2.1   360   47   T   N   360.47




#### Malinen, Jouni   1001   7 8.4.2.1   361   24   E   N   361.24
#### Kim, Youhan        1001   7 17.3.9.7. 1153   22   T   Y   1153.22
                                 3




#### Fischer, Matthew   1001   7 10.15.2   780    28   T   N    780.28




#### Fischer, Matthew   1001   7 10.15.2   780    28   T   N    780.28
#### Fischer, Matthew   1001   7 8.6.3    535   41   T   N   535.41




#### Fischer, Matthew   1001   7 3.1      4     49   T   N     4.49



#### Fischer, Matthew   1001   7 4.2.3    37    52   T   N    37.52

#### Fischer, Matthew   1001   7 8.1      278   12   T   N   278.12




#### Malinen, Jouni     1001   7 9.27.2   659   15   E   Y   659.15

#### Malinen, Jouni     1001   7 11.4.2   849   22   E   Y   849.22

#### Malinen, Jouni     1001   7 11.4.2   849   22   T   N   849.22
#### Malinen, Jouni   1001   7 11.5.2     875    28   T   Y    875.28




#### Malinen, Jouni   1001   7 12.10.3    975    4    T   Y    975.04




#### Malinen, Jouni   1001   7C           1478   15   E   Y   1478.15




#### Malinen, Jouni   1001   7 10.3.2.2   711    23   T   Y    711.23




#### Malinen, Jouni   1001   7 10.3.2.5   712    64   E   N    712.64
#### Malinen, Jouni   1001   7 10.3.3.3   714    46   T   Y    714.46




#### Malinen, Jouni   1001   7 10.3.3.3   715    48   T   Y    715.48




#### Stephens, Adrian 1001   7 B.3.1      1331   44   T   Y   1331.44
#### Malinen, Jouni   1001   7 10.3.3.5   718   9   T   Y   718.09




#### Malinen, Jouni   1001   7 10.3.3.5   717   9   T   Y   717.09
#### Fischer, Matthew   1001   7 8.3.3.2    315   39   T   N   315.39




#### Montemurro,        1001   7 3.2        21    21   T   Y    21.21
     Michael




#### Montemurro,        1001   7 10.2.1.6   696   27   T   Y   696.27
     Michael

#### Montemurro,        1001   7 8.2.4.1.8 283    30   T   Y   283.30
     Michael
#### Fischer, Matthew   1001   7 10.3.3.3   715   6    G   N   715.06




#### Ptasinski, Henry   1001   7 10.3.3.3   715   11   T   Y   715.11
#### Ptasinski, Henry   1001   7 3.1      14     1    T   Y    14.01




#### Ptasinski, Henry   1001   7 3.1      21     10   G   Y    21.10




#### Ptasinski, Henry   1001   7 3.1      22     52   T   Y    22.52




#### Ptasinski, Henry   1001   7 3.1      21     20   T   Y    21.17


#### Ptasinski, Henry   1001   7 3.3      33     5    T   Y    33.05




#### Ptasinski, Henry   1001   7 4.3.12   50     21   T   Y    50.21



#### Ptasinski, Henry   1001   7 6.3.42.2. 232   56   G   Y   222.56
                                 2



#### Ptasinski, Henry   1001   7 6.3.42.2. 232   59   G   Y   222.59
                                 2
#### Ptasinski, Henry   1001   7 6.3.43.1. 234   13   T   Y   234.13
                                 1

#### Ptasinski, Henry   1001   7 6.3.43.1. 235   51   G   Y   226.50
                                 4




#### Ptasinski, Henry   1001   7 6.3.43.2. 236   7    G   Y   236.07
                                 2




#### Ptasinski, Henry   1001   7 6.3.44.2. 229   20   G   Y   229.20
                                 2


#### Ptasinski, Henry   1001   7 6.3.44.4. 230   47   G   Y   230.47
                                 4
#### Ptasinski, Henry   1001   7 6.3.45.1. 233   31   T   Y   233.31
                                 2




#### Ptasinski, Henry   1001   7 6.3.45.2. 234   13   T   Y   234.13
                                 2




#### Ptasinski, Henry   1001   7 6.3.45.3. 235   4    G   Y   235.04
                                 4



#### Ptasinski, Henry   1001   7 6.3.45.4. 245   34   G   Y   245.34
                                 2
#### Ptasinski, Henry   1001   7 6.3.45.6. 237    4    G   Y    237.04
                                 4


#### Ptasinski, Henry   1001   7 6.3.45.7. 237    35   G   Y    237.35
                                 2




#### Ptasinski, Henry   1001   7 6.3.45.9. 239    4    G   Y    239.04
                                 4


#### Vlantis, George    1001   7                       G   Y




#### Ptasinski, Henry   1001   7 6.3.49    252    3    G   Y    252.03




#### Vlantis, George    1001   7 10.22.3   800    35   T   Y    800.35




#### Ecclesine, Peter   1001   7 D.1       1720   49   T   Y   1720.49
#### Ecclesine, Peter   1001   7 D.1   1719   36   T   Y   1719.36




#### Ecclesine, Peter   1001   7 D.1   1720   6    T   Y   1720.06




#### Ecclesine, Peter   1001   7 D.1   1719   23   T   Y   1719.23




#### Ecclesine, Peter   1001   7 D.1   1710   31   T   Y   1710.31




#### Ecclesine, Peter   1001   7 E.1   1729   50   T   Y   1729.50




#### Ecclesine, Peter   1001   7 E.1   1729   14   T   Y   1729.14
#### Ecclesine, Peter   1001   7 D.1        1719   15   T   Y   1719.15




#### Ecclesine, Peter   1001   7 D.1        1719   19   T   Y   1719.19




#### Ecclesine, Peter   1001   7 10.10.1    750    23   T   N    750.23




#### Ecclesine, Peter   1001   7 8.5.8.12   512    54   E   N    512.54
#### Ecclesine, Peter   1001   7 8.5.8.12   513   9    E   N   513.09




#### Ecclesine, Peter   1001   7 8.5.8.12   513   4    E   N   513.04




#### Ecclesine, Peter   1001   7 8.5.13.2   525   20   E   N   525.20




#### Ecclesine, Peter   1001   7 8.5.13.2   525   24   E   N   525.24




#### Ecclesine, Peter   1001   7 8.5.13.2   525   36   E   N   525.36




#### Ecclesine, Peter   1001   7 8.5.13.2   525   40   E   N   525.40
#### Ecclesine, Peter   1001   7 8.5.13.2   525    44   E   N    525.44




#### Ecclesine, Peter   1001   7 E.2.2      1738   2    T   Y   1738.02




#### Ecclesine, Peter   1001   7 D.1        1717   52   E   N   1717.52

#### Ecclesine, Peter   1001   7 D.1        1717   57   E   N   1717.57


#### Ecclesine, Peter   1001   7 17.3.10.3 1156    10   E   N   1156.10
#### Ecclesine, Peter   1001   7 D.2.5    1724   1   T   Y   1724.01




#### Struik, Rene       1001   72         2          T   N      2.00




#### Struik, Rene       1001   7 11.1.6   811        T   N    811.00
#### Struik, Rene   1001   78   T   N




#### Struik, Rene   1001   78   T   N
#### Struik, Rene       1001   78   T   N




#### Fischer, Matthew   1001   7    T   N   0.00
#### Fischer, Matthew   1001   7   T   N    0.00




#### Hunter, David      1001   7   E   Y    8.61


#### Hunter, David      1001   7   E   Y   13.29



#### Hunter, David      1001   7   T   Y   21.06
#### Hunter, David   1001   7   E   Y   27.16




#### Hunter, David   1001   7   E   Y   27.17




#### Hunter, David   1001   7   E   Y   32.21
#### Hunter, David   1001   7   G   N   32.21




#### Hunter, David   1001   7   E   Y   32.22




#### Hunter, David   1001   7   E   N   32.52




#### Hunter, David   1001   7   E   Y   33.32
#### Hunter, David   1001   7   T   Y   48.62




#### Hunter, David   1001   7   G   Y   84.29
#### Hunter, David   1001   7   G   Y   136.60
#### Hunter, David   1001   7   G   Y   259.65




#### Hunter, David   1001   7   G   Y   280.45




#### Hunter, David   1001   7   G   N   369.32
#### Hunter, David   1001   7   E   Y   418.29




#### Hunter, David   1001   7   E   Y   419.09




#### Hunter, David   1001   7   E   Y   450.54




#### Hunter, David   1001   7   E   Y   457.44




#### Hunter, David   1001   7   E   Y   681.27
#### Hunter, David   1001   7   E   Y   683.36




#### Hunter, David   1001   7   T   Y   708.48




#### Hunter, David   1001   7   E   Y   736.02




#### Hunter, David   1001   7   E   Y   820.16




#### Hunter, David   1001   7   E   Y   842.38
#### Hunter, David   1001   7   E   Y    842.31




#### Hunter, David   1001   7   T   Y    916.23




#### Hunter, David   1001   7   E   Y    916.24

#### Hunter, David   1001   7   E   Y   1407.22


#### Hunter, David   1001   7   T   Y   1407.23


#### Hunter, David   1001   7   E   Y   1492.15
#### Hunter, David     1001   7   E   Y   1492.27




#### Vlantis, George   1001   7   T   Y    528.48
#### Vlantis, George   1001   7   T   Y    802.60




#### Hamilton, Mark    1001   7   T   Y    799.51




#### Hamilton, Mark    1001   7   T   Y   1331.44




#### Hamilton, Mark    1001   7   T   Y    772.55




#### Hamilton, Mark    1001   7   E   N    313.61
#### Hamilton, Mark   1001   7   T   Y   104.60




#### Hamilton, Mark   1001   7   T   Y   104.60




#### Hamilton, Mark   1001   7   T   Y   159.62




#### Hamilton, Mark   1001   7   T   Y   424.34



#### Hamilton, Mark   1001   7   T   Y   602.19
Line   Clause   Duplicate   Resn Assignee   Submission Motion
                of CID      Status                     Number

0      11.9                 D




0      11.4                 D




38     9.9.1                P
20   3   U
36   9.10.2   D




37   9.10.2   A
50   7.2.1.1   P




10   11.9.6    A
17   Introducti   D
     on




54   9.10.4       P
22   3   D
60   3   D




0    D   D
22   3   D




1    U   A
3   7.1.4      A




1   7.3.1.24   D
39   9.7a       D




30   9.16.1.1   D




51   11.2.2.3   P
27   D           A




15   9.9.1.5     D




     17.3.2.1    A



     1.2         A




0    8.5.1.5.3   A




     3           A
    5.1.1       A




    7           A




    7           P




0   7.1.3.5.6   A




0   7.2.3       A
    7.2.3      P




0   7.2.3.8    A




0   7.2.3.9    D




0   7.3.1.4    A




0   7.3.1.11   A




    B          A
     C           P




0    G.2         P




     17.3.10.1   A




     Table i.1   P




1    6.1.3       D




45   7.2.3.1     P
56   7.3.22.10   D
     a




     7.3.2.22    P




     7.3.2.6     A




65   7.2.3.6     A
57   7.3.2.31   U




62   7.3.2.31   A




62   7.3.2.31   A




     7.3.2.31   A
47   7.3.2.25.   P
     3




     General     D




     General     D




     5.2.4       D
6.2.1.3   D




10.3.10   A
802.11k -   D
11.10.11
3   9.1.3.1   P




    9.9.3.1   P
11.2.1.1   P




11.2.1     P




           D
7.3.2.15    A




10.3.16.2   D
.2
8.4.4   A




5.2.5   P
1    M           D




15   17.3.2.1    A




0    17.3.8.1    A


     17.3.8.3.   A
     2
17.3.10.1   A




17.3.11     A
    17.3.11   A




0   17.3.11   P
17.3.12   D




7.3.2.4   D




7.2.3.1   D
Beacon
frame
format
0    17.3.10.1   A




0    11A.11.2    A




24   8.4.10      A
1   11A.1      D



    11A.4.2    D




    11A.4.3    D




    11A.5.2    D




    11A.5.4    D




    11A.5.5    D




5   11A.5.5    D



2   7.3.2.46   P




    8.5.8.1-   P
    8.5.8.4
16   7.3.2.46   A




25   8.4.10     P




12   7.3.1.17   P
0   7.3.2.30   P




    C          P
Clause      D
16




Clause      D
14




6.1.2       A




8.3.2.4.1   P
7.3.2.9    D




11.2.1     P




18.2.2.2   P
7.1.4   U




J       A
51   14.6.16   P   Lee           e-mail in      56
                   Armstrong/bil adhoc
                   l Marshall    notes/09/124
                                 4r1




28   9.3.2.2   D                                42
1    16        P                               20




13   9.9.1.5   P                                6




7    11.1.0a   A                                6


     General   A   Bill Marshall   11-09/910   38
    General   A   37




1   14        P   14




1   15        D   14
40   7.3.2.21.   D   4
     9




     7.3.2.22.   D   4
     9
     7.4.7.8     D   4




18   11.10.8.6   D   4




     7.3.2.22.   D   4
     9
43   7.3.2.31   P   32




21   7.3.2.31   P   32




     0A         A    7



     0A         D    7




     0A         A    7
0A   A    7



0A   A    7


0A   A    7


0A   A    7


0A   P    7




0A   A    7


0A   P    7




0A   P   18




0A   P   18



0A   P   18



0A   P   18
57   0A      P    6




6    0A      D   14




42   8.1.2   A    6




60   8.1.3   A   10




64   8.1.3   A    5
51   8.4.1.1.2   D   15




60   8.4.1.1.3   A    5




45   8.4.1.1.2   D    5




51   8.4.1.2.1   A    5
58   8.4.1.2.1   P   15




38   8.4.6       P   15




55   8.4.6.2     P   10




30   8.4.8       P   10
64   8.4.10    D   10



     General   D   15




40   8.7.2     D   10
     General   D   19




     9.9.2.2   D    6




45   9.8.0a    A    6


30   9.8.2     P    7
28   9.8.2a     P                            6




25   9.8.2      P                           44




38   18.4.6.7   P                           44




19   18.4.6.6   P                           44




30   18.4.6.2   P   Peter       09/1111r2   45
                    Ecclesine
18   15.4.6.2   P   Peter       09/1111r2   45
                    Ecclesine




4    A          D                           19




15   D          D                           54
46   D   P                           33




40   D   P   Peter       09/1111r2   45
             Ecclesine




51   D   D                           33
2    D    A   54




39   D    P   33




1    16   P   20
1    14   P   14




55   D    P   33




22   D    U    0




1    E    P    6




1    F    P   19
9    I   P    6




35   J   A    6




52   J   A    6


1    M   D   31
5   11.10.12   D   10




1   7.5        A    6


1   10         D    2
2   10.3.0a   D    2




1   10.3.11   D   54
13   1.2     A   19




6    3.159   A   44




5    3.159   A    6




1    13      A    6
5    6.1.3   P   23




22   6.1.3   P   23
25   6.1.3   P   23




27   6.1.3   P   23
1    general    A   23




57   Contents   P    6
60   Contents     D   6




15   Introducti   A   6
     on

43   Contents     A   6


27   Contents     A   6




28   Contents     A   6


1    3.147        P   6



32   3.4          D   7




     7.5          P   6
1    14          P   14




33   11A.10.1    P   29




1    7.1.1       P    6



59   7.1.3.5.1   P    6




42   7.1.3.5.3   P    6




48   7.2.2       P    6



51   7.2.2       P    6



1    7.2.3.1     P    6
45   7.2.3.10   D   54




15   7.3.1.1    D   54




36   8.2.1.3    A    6




     C          P   18




7    Editors    P    6
     notes
General   U   7




General   U   7




General   U   7
General   A   37




General   D   14
General   D   14




General   P   12
     General     D    6




20   N.5         P   40




21   Participa   P    6
     nts




     11.1.2.1    P   48
33   11.1.2.2   D   48




45   11.1.2.2   P    7




     11.1.2.3   P   34




36   11.1.3     P   54
28   11.1.3.5   A   34



7    11.2.1.1   D    6




     11.2.1.4   D   27




     11.2.1.4   P   31
11.2.1.5   A   27




11.2.1.5   D   27




11.2.2.1   A    6


11.2.2.1   P   57
     11.2.2.4     A   7




19   11.3.2.6     P   6




     11.4.1       P   7




16   11.4.2       P   7




     11.4.4       A   7




15   Introducti   U   7
     on
64   1.2         P    7




44   11.2.2.1    A    6


61   8.4.1.1.3   A   10




25   10.1        A   34




12   2           A   19




65   3.28        A    6
40   7.4.8.3    A    6




5    11.10.14   A   26




34   11.2.1.4   A   27




1    6.2.3      P   30
33   9.9.3.1    P   Mark       43
                    Hamilton




10   7.1.3.7    P               6




58   7.3.2.27   P               6
28   7.3.1.11    P                           32




54   11.3.0a     P   Jon Rosdahl 11-09/705   41




8    10.3.8.1.   A                           34
     1

23   10.3.8.2.   A                           34
     2

26   8.3.2.4.0   P                           10
     a
31   10.3.24.2   A   54
     .2




21   10.3.29.2   P   54
     .2




17   10.3.30.2   P   54
     .2
17   10.3.31.2   P   54
     .2




28   10.3.32.2   P   54
     .2




64   11.4.5      P   26
22   9.9.3.1.2   D   42




27   7.3.2.21.   P    7
     7



17   3.136       A   44




23   3.3         P   44
1    3          A                        51




48   11.10.11   P                        10




1    14         P                        14




1    16         P                        20




49   17.3.11    A   Adrian     09/1233   53
                    Stephens
22   17.3.11       A     6




1    15            D    14




1    14            P    14




1    16            P    20




49   17.3.11   1170 A   53




22   17.3.11       A     6
1    15             D    14




20   18.4.6.6   1187 P   44




40   18.4.6.6   1188 D   44




40   19.1.2     1189 P   14




48   19.1.2     1190 P   14
1    14            P    14




1    16            P    20




49   17.3.11   1170 A   53




22   17.3.11       A     6




1    15            D    14
20   18.4.6.6   P   44




40   18.4.6.6   D   44




40   19.1.2     P   14




48   19.1.2     P   14




9    9.8.1      P    6
20   1.3.37.4.   A   6
     2

     A.4.10      D   6




     A.4.13      D   6




     A.4.13      D   6




     A.4.13      D   6
A.4.18   D   6




A.4.18   D   6
A.4.18   D   6




A.4.18   D   6
     A.4.18        D                            6




16   D ASN.1       D                            6




20   I Table I.2   P   Peter       09/1111r2   45
                       Ecclesine




30   I Table I.3   A   Peter       09/1111r2   45
                       Ecclesine
36   I Table    A   Peter       09/1111r2   45
     !.4            Ecclesine




38   I Table    A   Peter       09/1111r2   45
     !.4            Ecclesine




1    Abstract   S                            7
22   Introducti   S    7
     on




41   7.3.2.25.    D   46
     1




37   7.3.2.26     D   46
37   7.3.2.26   P   46




15   7.4.5      D   46




34   7.4.5      P   46
     General     P   19




33   10.3.19.1   A    6
     .2
12   J.1       P   Peter       09/1111r2   45
                   Ecclesine




58   7.2.3.1   P                            6




4    7.2.3.4   A                            6
7    7.2.3.4     P    6




62   7.2.3.5     A    6


32   7.2.3.7     P    6




63   7.2.3.10    P    6




50   7.4.8       P    6




1    7.5         A    6


36   8.4.1.1.2   A   10




65   8.5.1.5.2   A    6
62   8.5.1.5.3   P   10




32   8.5.1.5.5   P    6




5    8.5.2       A    6




7    11.4.3      U    6




17   11A.3       A   10



63   11A.4.2     P    6




31   11A.4.2     A   10




6    11A.8.1     A    6


52   D           A    6
64   D          P    6




1    6.2.1.2    S   31




1    7.3.2.35   P    6
    D         1596 P   17




    Annexes       D     6




1   C             D    18



1   E             P     6
20   5.1a        P   44




50   5.2.3       D    6




22   5.2.3.1     P    6




3    5.4.4.1     P   10




40   7.3.2.25.   D   46
     1
     7.3.2.27   P   6




     7.3.2.27   P   6




44   11.11.1    P   6
44   7.3.2.48    P   32




14   7.3.1.7     A   54




45   7.3.2.22.   A   32
     6


7    8.1.0a      P   10
41   8.5.3.0a    A   10




59   11.10.8.1   P   15




15   11A.9.5.1   A   10




5    8.5.2       P   29
13   7.3.2.48   P   32




23   8.5.3.2    P   10
49   8.5.3.3     P   10




35   7.3.2.21.   D   32
     10




46   11.10.8.8   A   10
    General   P   14




    General   U   14




1   10        D    2
1    16         P   20




     C          D   18




51   11.9.7.2   D   10
    N        D   25




    E        P   14




    F        P   14




    O        D   13




    P        A   14




1   14       P   14




1   12.3.4   P    6
26   12.3.4.4    P   46




18   12.3.5.4.   P   46
     2




35   12.3.5.10   D   35
     .3




35   12.3.5.10   P   35
     .3




51   17.3.2.4    P    6




10   17.3.2.4    A    6


7    17.3.3      A    6
31   17.3.3     A                         6


7    17.3.4.3   P   Adrian     09/1233   53
                    Stephens




22   17.3.8.1   P                        22




64   17.3.9.7   D                        22


64   17.3.9.7   A                         6
20   17.3.10.5   P   Adrian     09/1233   53
                     Stephens
55   17.3.12   P   Adrian     09/1233   53
                   Stephens




24   17.3.12   P   Adrian     09/1233   53
                   Stephens
46   17.4.3   P   22




1    17.5     D   44




21   19.4.6   D   44




21   19.5.4   A    6
38   19.9.5.0a   A                            6


46   19.9.5.0a   A                            6


17   19.9.5.0a   A                            6


26   I.1         A                            6


38   I.2.2       A   Peter       09/1111r2   45
                     Ecclesine




1    J.1         P   Peter       09/1111r2   45
                     Ecclesine




21   J.1         A                            6


55   J.1         A                            6


1    General     P                           12




7    11A.8.4     A                           10


4    11A.8.5     A                           10
12   7.3.2.47   D   46




13   7.4.7.2    A    6


7    Q          D   54




44   Q          D   33




15   Q          D   33




63   Q          D   33




4    Q          A   33




21   Q          P   36




35   Q          D   33
1    Q   D   33




59   Q   D   33




30   Q   A   33




58   Q   D   33




62   Q   P   46




     7   P    6
62   7.4.6.3   D   36




15   10.3.32   A   34




15   10.3.32   D   54




48   7.4.6.5   D   36
55   7.4.7.2   D   36




38   7.3.2     D   36




44   7.3.2     D   54




23   10.3.25   A   34




1    10.3.27   A   34
11   7.4.5       D                          54




38   5.3.1       D   Adrian     09/1233r0   52
                     Stephens




36   10.3.29.1   A                          54




6    10.3.35.3   A                          54
25   10.3.15.3   D   36




58   9.13        D   40




64   11.1.2.3    D   54
53   9.4   P   30




53   9.4   A   24
31   11.1.3.2.   P    6
     1




46   11.2.1.5    D   27
     11.3       P   Jon Rosdahl 11-09/705   41




44   11.2.2.1   A                            6


65   9.4        P                           31
59   9.2.5.4   D   24




39   9.9.1.2   P   39
13   9.9.1.5   P   6




17   9.9.1.5   P   6




47   9.10.3    D   6
27   9.10.3      P   30




1    7.1.3.1.7   P    6




47   7.5         P   36
26   9.1.3.1    A                             31




     9.1.3.1    A                             31




49   7.3.2.21   A                              6




49   11.9.6     A                              6




     11.3       A   Jon Rosdahl 11-09/705r4   41
7, 11, etc.   D    6




3.163,        P   23
3.87
60   7.2.3.0a   P   36
     7.2.3.1     P    7




     11.2.1.1    P   31




15   7.1.3.3.3   A   32
53   11.2.1.0a   A   31




1    11.2.1.0a   D   42




28   7.3.1.11    A   32




     10.3.33     A    6




     7, 9, 11,   D    6
     etc.
     C          P                          18




50   3          D   Adrian     09/1233r0   52
                    Stephens




14   7.2.3.2    A                           6




44   11.2.2.1   A                           6
21   A.4.4.2     D   44




29   5.4.2.1     A    6


21   7.1.0a      P    6




46   7.2.1.1     A   32




17   7.1.3.3.3   A    6
30   7.1.3.5.4   P    6




58   7.1.3.5.6   A   32




28   7.2.2       D    6
28   7.2.2      A   32




35   7.2.3.0a   A   32




37   7.2.3.1    A    6
56   7.3.1.4   A   32




6    7.3.1.4   A   32
52   7.3.1.4    A   32




48   7.3.1.4    A    6



58   7.3.1.11   P   32



52   7.3.2.0a   P    6




27   9.14.0d    P   24
5    7.3.2.40    D   36




54   7.3.2.22.   D   32
     8
     C       P   6




10   3       A   6


33   3       P   6




60   3       A   6


16   3       A   6


36   3       A   6


18   3       P   6



64   3       A   6



41   3.88    A   6


51   3.104   A   6



20   3.113   A   6




64   3.133   A   6
17   3.136   A    6




27   3.151   A    6



53   3.169   A    6




5    3.159   A    6


1    C       D   18




44   4       A    6




62   4       A    6
     General   D   13




32   5.2.3.2   A    6



3    5.2.5     P   44
29   5.2.6   A   31




34   5.2.7   A    6




65   5.2.7   D   10




6    5.3.2   D   51
41   5.4.1.1   D   13




49   5.4.1.2   D   14
1    5       P   21




14   5.4.3   A   10
1    5.4.3.1   P   10




39   5.7       D   51
26   5.7         D   51




10   10.3.29.1   A   34
28   5.8.3.3     D   10




1    6.1.5       A    6


47   7.3.2.25.   A   46
     1
14   10.1       P   54




1    10.1       A   34




1    10.3.0a    A   54




28   11.10.12   P   15
34   10.3.2.2.   A   34
     2




8    10.3.2.2.   D   54
     2




31   10.3.2.2.   A   54
     2




50   10.3.2.2.   A   54
     2
25   10.3.2.2.   A   54
     2




48   10.3.2.2.   A    6
     2

1    10          P    6




23   10.3.6.3    A    6
48   8.2.2.3.0   A                           10
     a




1    10          A                           36




5    11.3.0a     A                           10




8    11.3.2.5    P   Jon Rosdahl 11-09/705   41




26   11.3.2.5    P   Jon Rosdahl 09/705r4    41
19   11.10.5     A   10




12   D           P    6




30   10.3.9.1.   D   54
     2




18   10.3.9.2.   A   34
     2
1   D           P   46




1   D           P   46




5   10.3.10a.   P   54
    1.3
61   10.3.11     P   36




30   10.3.11     A   54




37   10.3.13.2   A    6
     .2


11   10.3.16.2   P   54
     .2




46   10.3.17.1   A   54
     .2




50   10.3.19.1   A   34
     .4
56   10.3.22.1   P   34
     .4




54   10.3.22.1   A    6
     .4

26   10.3.23.1   A   54
     .2




38   10.3.24.1   A    6
     .1

17   10.3.24.1   A    6
     .2




46   10.3.24.7   P    6
     .3




36   10.3.25.2   A   34
     .2
46   10.3.27.5   D   54
     .4




     General     A    6



28   10.3.30.3   P   54
     .4




39   10.3.31.2   A   54
     .4




32   10.3.31.3   A    6
     .2

1    10          A    6


49   10.3.33.6   A    6
     .2
16   10.4.1.1   P   46




7    11.1.0a    A    6


9    11.1.0a    A   34




16   11.1.1     A   34



     General    A   19




20   11.1.2.1   A   34
1    11.1.2.1    P   48




23   11.1.3.0a   A    6


32   11.1.3.2.   A   54
     1




34   11.1.3.2.   A   54
     1




58   11.1.3.2.   D   54
     2
27   11.2.1.3   P   27




19   11.2.1.4   A   27




51   11.2.1.5   A   31




14   11.2.1.5   A   27
36   11.2.1.5       A     6


37   11.2.1.5       P    30




39   11.2.1.5       A    31




50   11.2.1.5   1490 P   30




8    11.2.1.5   1490 P   30




30   11.2.1.5       A    31
51   11.2.1.5       A    31




21   11.2.1.6   1490 P   30




33   11.2.1.6   1490 P   30




62   11.2.1.9       P    31




64   11.2.1.9       A    31




2    11.2.1.9       A    27
30   11.2.2.1   P   30




19   11.2.2.1   A   31




1    11.2.2.4   P    6




12   11.2.2.4   A    7
15   11.2.2.4   A    7




41   11.2.2.4   A   31




30   11.3.0a    D   10
42   11.3.0a    P   Jon Rosdahl 11-09/705   41




4    11.3.2.1   A                           34




65   11.5.3     A                            7
5    11.4.1   A               6


18   11.4.2   A              31




36   11.4.4   A               6



28   11.6.1   D              54




56   11.6.1   P   Adrian     55
                  Stephens
19   11.6.2     A   54




42   11.7.0a    P   30




39   11.7.0a    A    6



63   11.7.1.2   P    6
     General   A   22




45   11.9.6    A    6


5    11.7.5    A    6


1    11.9.0a   A    6



     General   D    6




30   11.9.0a   A   10



11   11.9.2    A   10




33   11.9.3    P   15
53   11.9.6      A   10




     General     P    6




62   11.10.8.4   A    6
24   11.10.8.4   A   10



28   11.10.8.6   D   10




28   11.10.8.8   A   10




18   11.10.9     P   10




     General     P    6
1    11.10.9.2   P   10




33   11.10.10    A    6
     a

50   11.10.11    P   10




23   11.10.12.   A    6
     1

49   11.10.12.   A    6
     1

52   11.10.13    P    6
53   11.10.13    A                           31


55   11.11.1     P                            7




5    11.11.2.2   A   Peter       09/1111r2   45
                     Ecclesine




58   11.11.2.3   P   Peter       09/1111r2   45
                     Ecclesine
58   11.11.2.3   P   Peter       09/1111r2   45
                     Ecclesine




3    11.11.2.4   P   Peter       09/1111r2   45
                     Ecclesine




21   11.11.2.2   P   Peter       09/1111r2   45
                     Ecclesine
24   11.11.2.4   P   Peter       09/1111r2   45
                     Ecclesine




4    11.11.3     P   Peter       09/1111r2   45
                     Ecclesine




41   11A.1       A                            7




22   12.3.5.7.   P   Adrian      09/1233r0   55
     3               Stephens
6    12.3.5.11   A   35
     .1




17   12.3.5.12   A    6
     .2



52   12.3.5.12   P    7
     .3
     19        P   Adrian     09/1233r0   53
                   Stephens




23   A.4.4.1   P                           7
39   A.4.4.1   P   21




24   A.4.2     A    6




     General   P    7




20   A.4.4.4   A    6


42   A.4.8     A    6
1   A   P    6




1   A   A    6




1   C   P   18




1   E   A    7
1    F       P   19




40   K.3.2   A    7




48   K.3.2   A    6


58   K.3.2   A    6
34   K.3.2   P    6




41   K.3.2   A    6


44   N.2     D   30




     P       A    6


22   Q       P    7



23   Q       P    7
33   Q   P   47




26   Q   D   54




34   Q   A    6


16   Q   A    6



25   Q   D   33



48   Q   A    6


29   Q   P    6



63   Q   A    6
     Q   P   47




51   D   P    6




54   D   P    7



40   D   A   33
     D   P    7




35   D   A   33




42   D   P    6




54   D   A    6
34   D   P                          36




23   D   D                          54




     D   P   Adrian     09/1233r0   55
             Stephens
     D         P   17




22   D         P   47




     General   P    6
63   D         D   54




     D         A    6




46   9.1.3.1   P    6




51   9.1.3.2   A   30




35   9.1.5     A   31
41   9.1.5   A   31




65   9.1.5   P   30
30   9.2      A   30




56   9.2.0a   P   24




8    9.2.0a   A   24
16   9.2.0a   P   24




22   9.2.0a   D   24




26   9.2.0a   A   24
19   9.2.2     A   24




43   9.2.3.3   A   24




51   9.2.3.4   P   24




55   9.2.3.4   A    6



60   9.2.3.4   A   24
30   9.2.4     A   24




51   9.2.5.1   A   30




48   9.2.5.3   A    6


28   9.2.5.3   A    7




30   9.2.6     A   24
33   9.2.6   A    7




35   9.2.6   P    7




36   9.2.6   P    7




41   9.2.6   P   23




40   9.2.6   P    7
53   9.2.7   A   24




59   9.2.7   P   24




55   9.2.9   A    7




5    9.2.9   A   24
12   9.2.9    A   24




58   9.2.9    A    7




36   9.2.11   A   30
10   9.3.0a    P   16




14   9.3.0a    A   31




16   9.3.0a    A   16




57   9.3.0a    D   31




1    9.10.4    P    6




15   9.3.4.1   A    6


32   9.3.4.2   P    7
53   9.4   P   40




45   9.5   P   40
61   9.5       A   30




25   9.6a      A    6


45   9.8.0a    A    6


61   9.8.1     P   14




1    9.9.1.2   P   39
42   9.9.1.3    A   24




46   9.9.1.3    A   24




1    9.9.1.3    A   24




13   9.9.1.5    P    6




33   9.9.1.5    A   24




48   9.9.1.6    P   24




64   9.9.2.0a   A    6
39   9.9.2.1.2   P   39




24   9.9.2.1.3   A   39




19   9.9.2.1.3   A   40




26   9.9.2.1.3   A   24
50   9.9.2.1.3   A   24




14   9.9.2.1.3   P    6




14   9.9.2.1.3   P   24




31   9.9.2.1.3   P    6
18   9.9.2.2a    P   24




24   9.9.2.2a    A   24




30   9.9.2.2a    A   40




29   9.9.2.3.0   A   40
     a




19   9.9.2.3.0   A    6
     a

30   9.9.2.3.1   A    6
19   9.0a      P    6




27   9.1.2     A   31




5    9.1.3.1   P   24




35   9.2.5.2   P    6




24   9.2.5.3   P   31




28   9.2.11    P    6
50   9.9.1.2     D    6




     9.9.1.5     P    6




28   9.9.2.0a    A    6




60   9.9.2.1.3   P   24




18   9.9.2.2a    P    6
58   9.9.2.3.2   D    6




45   9.9.3.1.0   D   30
     a




12   9.9.3.1.1   A    6
37   9.10.3     P   30




59   7.3.2.47   P    6
33   9.9.3.1.0   P   Dave         43
     a               Stephenson
52   9.9.3.1.0   D   Dave         43
     a               Stephenson




25   9.9.3.1.2   D                23
5    9.9.3.1.2   P   23




34   11.4.3      P    7




42   11.4.3      A   26
44   11.4.4   U   Dave         11-09/1063r0    0
                  Stephenson




49   11.4.6   D                               23




51   11.4.6   P                               26




55   11.4.6   A                               26
5    11.4.6   P   23




11   11.4.6   P   26
52   11.4.7    D   26




48   3         A   22


50   3         P    7




37   7.2.3.1   D    6




5    7.2.3.8   D   46
5.2.7.2     A    6




5.2.7.11    P   10




5.4         P    6




Table 7-8   A    6
     7.3.1.4    A   36




31   7.3.2.21   P    6
60   7.3.2.21    A   32




     Table 7-    A    6
     29

     7.3.2.21.   A   32
     10




24   7.3.2.21.   D   54
     8
     7.3.2.21.   D   49
     7




     7.3.2.22.   P   32
     8




13   7.3.2.22.   D   54
     10
     7.3.2.21.   D   50
     10




     7.3.2.25    P    6




56   7.3.2.31    D   36




44   7.3.1.17    P   54




     7.3.2.37    A   32
56   7.3.2     P    6




     General   D   44
53   G.2        P    7




1    3.2.3      A    6


62   9.1.1      A    6


59   9.1.3.1    D   24




22   9.2.0a     A   31




52   9.2.3.0a   P    6
28   9.9.2.0a   P    6




1    19         A    6


9    14.8.2.4   A   61




47   A.4.5      D   59




50   A.4.6      P   61




23   A.4.7      A   61




25   A.4.8      D   59




40   A.4.9      D   59
59   15.3.2   P   81




27   16.4     A   61




16   18.3.2   A   61




2    C.2      D   59
30   D   P   81




65   D   P   81




1    D   P   59
18   14.8.2.1    A   61




65   9.3.3.1     P   84




44   11.4.2      P   63




19   11.9a.1     P   65




42   11.10.12.   A   72
     1
63   D   A   59




60   D   A   59




47   D   A   72


11   D   P   59




25   D   A   59
20   D   P   81




31   D   P   67




57   D   P   67
28   8.2.2.2.1   P   Peter E   87




25   9.6a        D             62




47   A.4.10      P             67




45   7.3.1.4     D             62
20   D       A   59




20   A.1     A   60




15   A.1     P   72




43   I.1     A   59




39   I.2.2   A   59


40   J.1     A   81
20   I.1         A   72


43   11.1.3.0a   P   72




30   7.1.3.3.1   P   72




2    D           P   73




1    B           P   72




15   I.2.2       A   59



11   J.1         A   59




9    J.1         A   72
25   J.1     A   59




6    J.1     A   59




10   A.4.1   D   72
41   10.3.1.1.   U   72
     2




23   D           A   59




14   D           P   59
34   D        U   Peter E    0




28   17.4.2   A             72

31   D        P             59
18   D   P   59




52   D   P   69




31   D   P   59
30   D           P   59




43   11.11.2.2   A   72

50   A.4.6       P   61




24   A.4.8       D   59




40   A.4.9       D   59
65   D        P   81




24   A.4.7    A   59


42   A.4.12   A   59




55   A.4.12   A   59




6    A.4.12   A   59


40   A.4.3    D   59
1    7.3.2.48    A   72



60   7.4.7.9     A   62




54   D           P   59




50   11.2.1.0a   P   63
23   D   P   59




17   D   P   59




34   D   A   59




15   D   P   59
44   D   A   59




58   D   A   59




11   D   P   59
     D       D   59




1    M       S   76




32   0A      A   59




22   9.8.2   A   59
20   17.3.10.5   D   59




     General     D   72




64   3           D   72




1    5.4.1.2     A   72

1    5.4.3.3     P   72




40   5.4.4.1     D   72




34   17.3.8.3.   D   59
     1
28   9.14.0b    D                           64




6    9.8.2      D                           59




19   11.2.1.1   P                           63




6    6.2.3.2    P   Adrian     11-10/0308   80
                    Stephens




2    6.2.3.2    A                           62
30   10.1        A   59




40   9.9.3.1.0   A   62
     a




1    10.3.20.2   P   59
19   8.5.6.0a    A                 72

1    8.4.1.1.1   D   Dan Harkins   83




4    8.4.1.1.1   D   Dan Harkins   83




     8.4.6.2     D   Dan Harkins   83
     8.5.1.2     D   Dan Harkins   83




     3           D                 60




20   17.3.10.5   D                 59
34   17.3.8.3.   D                   59
     1




32   6.1.2       P   Bill Marshall   87




50   7.3.2.25.   A                   87
     1
37   7.3.2.48   P   62




39   8.5.2      A   65




54   8.5.6.0a   A   72
33   11.3.0a     P   Bill Marshall   11-10/390r0   85




57   11.3.1.0a   P   Jon Rosdahl 11-10-0302        71
44   11.3.2.3   A   Jon Rosdahl 11-10-302r2    85




21   7.3.2.54   P   Peter       11-10/0210r6   74
                    Ecclesine
38   D         P                                 72




1    D         A   Bill Marshall   11-10/300r1   70




1    C         U                                  0




31   11.7.0a   A                                 72
1    D          A   59




     General    P   72




33   11.3.1.3   A   72
1    D   D   67




10   Q   A   72
34   19.1.1      A   59




43   11.1.3.0a   A   59




16   A.1         P   72




     General     D   72
9    7.4.9a     U                            62




34   11.3       D   Jon Rosdahl 11-10-0302   71




61   11.3.1.4   P   Jon Rosdahl 11-10-0302   71
28   11.3.2.8    P   Jon Rosdahl 11-10-0302   71




58   8.1.3       A                            72


59   8.1.3       P                            65




6    8.1.3       P                            72




10   8.1.3       P                            72




10   8.1.3       A                            65



30   8.3.3.3.3   A                            65
6    8.3.3.3.5   D   87




51   8.3.3.4.0   P   65
     a


5    8.3.3.4.1   D   87




19   7.4.7.2     D   64




13   11.9a.1     D   72




55   11.9a.3.1   D   65
47   11.9a.3.2   D   65




17   11.10.3     D   72




     9.13        P   64
     11.2.2.4    A   66




54   10.3.2.2.   A   59
     2
45   10.3.10.1   A   59
     .2
64   10.3.10a.   A   59
     1.2
49   10.3.10.1   D   59
     .2
1   3           A   59




    11.2.1.0a   D   62
51   1.2        U                            59




61   3          A                            72



45   11.3.0a    A   Jon Rosdahl 11-10-0302   71




42   11.3.0a    P                            85




36   11.3.1.3   A   Jon Rosdahl 11-10-0302   71
1   11.3.1.4   A                            72




8   11.3.2.4   P   Jon Rosdahl 11-10-0302   71




    11.3.0a    P   Jon Rosdahl 11-10-0302   85
1    11.3.1.0a   P   Jon Rosdahl 11-10-0302   86




34   11.3.2.0a   A   Jon Rosdahl 11-10-0302   71




12   11.3.1.1    A   Jon Rosdahl 11-10-0302   71
54   11.3.1.4   A   Jon Rosdahl 11-10-0302    71




49   11.3.2.6   P   Jon Rosdahl 11-10/302r1   71
4    11.3.1.2   P   Bill Marshall   11-10/390r0   85




55   11.3.2.1   A   Jon Rosdahl 11-10-0302        71




17   11.3.2.5   P   Jon Rosdahl 11-10-0302        71
17   11.3.1.3   P   59




12   11.3.0a    A   72

32   11.3.0a    A   72

34   11.3       P   72
34   11.3   P                 72




34   11.3   A                 72




1    3      P   Jon Rosdahl   69
39   11.2        P   63




56   3           D   59




20   A.4.4.2     D   59




28   Frontmatt   P   59
     er
44   5.2.3.2   A                             87




6    7.3.1.4   P                             81




26   7.3.1.4   P   Adrian     11-10/0308r0   80
                   Stephens
22   7.3.1.4    P   64




45   7.3.1.4    A   62




36   7.3.2.21   P   62




29   7.3.2.48   P   62
53   7.4.7.9    A   62


37   8.3.3.1    A   65




     General    P   67




49   8.5.6.0a   P   65




10   8.7.2.3    D   87




34   8.7.2.4    D   87
23   10.1        A   59




20   10.3.29.2   A   59
     .2




25   10.3.35.3   A   59
     .2
39   11.3.1.2   P   Jon Rosdahl 11-10-0302   71
36   11.3.1.3   P   Jon Rosdahl 11-10-0302   71
5   11.3.2.4   A   Jon Rosdahl 10-11-0302r1   85
47   11A.10.1   P                             87




30   D          P   Adrian     11-10-0216r2   69
                    Stephens
38   D           P   67




28   D           P   67




14   D           A   59




42   H.8         D   72



46   7.1.3.1.7   P   62




1    7.4.7.10    A   64
45   10.3.40   P   67




1    10.3.44   A   67
1    11.2.2.3    A   84




29   11.3.0a     P   72



     General     A   72

57   11.11.2.2   A   67
38   11.11.2.4   A   68




     General     P   73




38   17.4.3      A   72
1    11.6.2      P   72




19   F.0a        A   72

11   7.3.2.21.   A   72
     1
17   8.5.3.5     P   75




6    7.1.3.3.3   P   62




65   10.3.24.3   P   72
     .3
11.2.1.0a   P   63
     11.2.1.0a   P   63




11   11.2.1.0a   P   62




46   11.2.1.4    S   66
42   11.2.1.5   P   66




45   11.2.1.9   P   77




49   11.2.1.9   P   77
56   11.3.1.0a   P   Jon Rosdahl 11-10-0302   71




58   11.3.1.0a   P   Jon Rosdahl 11-10-0302   71
58   11.3.1.0a   A   Jon Rosdahl 11-10-0302   71




57   11.4.3      D                            79




47   11.4.3      A                            66
48   11.4.4   U   79




16   11.4.4   A   62


25   11.4.4   A   62




     11.4.4   A   78




50   11.4.6   D   79




55   11.4.6   P   62
55   11.4.6     D   62




55   11.4.6     D   79




1    11.4.6     A   62



55   11.4.8     P   72




58   11.4.8     P   72




     7.3.2.21   P   72




12   20.3.20    A   91
56   A        D   91




47   A        A   91




7    A        A   91




10   A        A   91




27   D        D   91




29   19.8.2   A   91




40   20.4.2   A   91
1    C           D                 91




2    C           D                 91




53   D           A                 91




38   D           D                 91




9    7.3.2.22.   D   Gabor Bajko   89
     9
7    7.3.2.21.   P   89
     9




     0           A   91




1    14.8.2.4    D   91




54   17.4.2      A   91


29   19.8.2      A   91


7    20.3.20     A   91


45   20.4.2      A   91
     A.4.3    D   91




     A.4.5    A   91




     A.4.8    A   91



     A.4.9    A   91



56   D.3      P   91




34   A.4.10   P   91



31   J.1      A   91
36   J.1         P            91




7    20.3.20     A            91




62   10.3.37.1   P   Kaberi   91
     .3
3    I.1       A   91




60   11.11.5   A   88


21   3.1       D   88
12   3.1   D   88
21   3.1   D   88
49   3.1   D   88
50   3.1   D   88
20   3.1         D   88




40   7.1.3.5.3   P   91




38   7.1.4.2     P   91




11   7.3.2.31    P   88
58   9.1.3.1     P   91




60   9.1.5       A   89




24   9.2.0b.3    P   91




52   9.2.0b.4.   D   90
     6




26   9.2.0b.6    D   90




30   9.9.1.2     P   91




54   9.9.1.3     D   90
6    11.1.3.2.   D   Kaberi              91
     2




50   11.2.1.0a   P            Adrian     90
                              Stephens




24   11.2.1.4    P            Adrian     90
                              Stephens




48   11.2.1.5    P            Adrian     90
                              Stephens




18   11.2.1.5    P                       88
31   11.2.1.9    D   Adrian     90
                     Stephens




5    11.2.1.12   P   Adrian     90
                     Stephens
26   11.2.1.12   P   Adrian     90
                     Stephens




43   11.2.2.4    D   Adrian     90
                     Stephens




38   11.4.44     D              91




56   9.16.1.7    U              91
30   11.9.7.3    D   91




28   7.3.27      D   91




60   7.3.2.37    D   90




     7.3.2.27    A   90



     11.1.3.2.   D   91
     1
11.2.1.0a   P   Adrian     90
                Stephens




11.2.1.1    D   Adrian     90
                Stephens
7.3.2.4    P                             90




11.1.2.2   P   Harish     11-10/0604r0   91
               Ramamurthy




11.2.2.1   D                             90
11.2.2.1   P   Adrian     90
               Stephens




11.2.2.4   D   Adrian     90
               Stephens
11.2.2     D   Adrian     90
               Stephens




11.2.1.5   P   Adrian     90
               Stephens
25   11.3.0a   P   91




     11.3.0a   D   91
50   11.3.1.2    P            91




8    11.3.1.0a   A            91




31   11.3.2.0a   A   Kaberi   91




39   11.3.2.6    P   Kaberi   91
64   11.3.2.7   P   Kaberi   91




62   11.3.1.2   P            91




13   A.4.11     P   Kaberi   91
23   A.4.4.1     A   Kaberi   91




25   20.3.12.1   D            91
1    7.4       P   Adrian     91




34   7.4.2.1   P              90




27   A.4.5.3   D   Kazuyuki   91
                   Sakoda




     General   A              88
30   7.3.1.4     A            90



     General     A            88




1    7.3.2.47    A            88




6    9.13.2      A            90




58   10.3.37.1   P   Kaberi   91
     .3
8    11.2.1.0a   A   Adrian     90
                     Stephens




60   11.2.1.0a   A   Adrian     90
                     Stephens



63   11.2.1.0a   A   Adrian     90
                     Stephens




59   11.2.2.1    P   Adrian     90
                     Stephens
49   11.3.1.2   P   91




     General    P   88




36   11.3.1.3   P   91
25   11.3.2.5   P   Kaberi   91




54   11.3.2.6   A   Kaberi   91




26   11.3.2.8   A            91
5    7.3.2.30    D   91




47   11A.4.2     A   90




57   11A.4.2     A   90




56   20.3.11.8   A   91
     .1


10   20.3.20     A   91
50   20.3.24   A   91




4    20.3.24   A   91




13   A.4.11    A   91
32   D.2       P   91




27   D.3       A   91



32   D.3       A   91


37   D.3       A   91




     General   A   88


4    I.1       P   91




30   I.1       A   88


32   S.1       A   88
40   7.4.7.1a   A              88


42   8.7.2.4    P              88



56   11.5.2.1   A              90



29   11.2.1.1   P   Adrian     90
                    Stephens




49   11.2.1.1   D   Adrian     90
                    Stephens
26   11.2.1.4   P   Adrian     90
                    Stephens




4    11.2.1.5   P   Adrian     90
                    Stephens




23   11.2.1.5   P   Adrian     90
                    Stephens




54   11.2.1.5   D   Adrian     90
                    Stephens
35   11.2.1.7    D   Adrian     90
                     Stephens




62   11.2.1.11   P   Adrian     90
                     Stephens
1    3      A   Adrian   11-10/0532r0   91




40   11.4   P                           89
47   11.4.3      D   91




30   9.9.3.1.1   P   89




30   9.9.3.1.1   P   89




28   19.8.2      A   91
7    20.3.20   A   91




44   20.4.2    A   91




53   A.4.3     D   91




56   A.4.3     D   91




47   A.4.5     A   91




6    A.4.8     A   91
10   A.4.9   A   91




12   C.2     D   91




56   D       A   91



27   D       D   91




28   D       D   91




39   D       D   91
50   G.3.6      A   91




55   A          A   95



16   D          D   95




25   7.3.2.6    A   93




1    7.3.2.48   A   93




1    7.3.2.48   A   93
38   7.3.2.0a   P   93




64   7.3.2.1    A   93


64   7.3.2.1    P   93




6    7.3.2.2    A   93




     7.3.2.3    P   93




31   7.3.2.4    A   93




     7.3.2.5    A   93




5    7.3.2.7    A   93
     7.3.2.8     A   93




55   7.3.2.14    A   93




41   7.3.2.25.   A   93
     0a



41   7.3.2.25.   D   93
     0a




14   7.3.2.26    A   93




53   7.3.2.39    A   93




26   9.8.3       A   93




28   11.10.9.2   A   93




56   7.3.2.37    A   93




30   11.10.9.2   A   93
11   7.1.3.1.7   P   93




34   7.2.2.2     D   94




40   7.1.3.5.3   D   94




44   7.1.3.1.8   P   94
6    7.1.3.5.0   P   94
     a




19   7.1.3.1     P   94




51   11.2.1.5    D   94
41   11.2.1.1   P   94




56   A          P   95
6    J.1        A   93




1    16         A   93


11   7.3.2.30   A   94




61   3.1        A   95




5    7.3.1.6    A   93


8    7.3.2.12   A   93
9    7.4.8      P                          94




51   7.3.2.31   A                          93




39   11.2.1.7   A                          94




5    11.3.0a    D   Mark       11-10-826   98
                    Hamilton




46   11.3.1.3   D   Mark       11-10-826   98
                    Hamilton
18   11.3.1      D   Mark       11-10-826   98
                     Hamilton




18   11.3.1      D   Mark       11-10-826   98
                     Hamilton




29   11.3        D   Adrian     11-10-768   98
                     Stephens




18   11.3.1.1    D   Mark       11-10-826   98
                     Hamilton




43   11.3.1.3.   D   Adrian     11-10-768   98
     b               Stephens
12   11.3.2     D                          95



12   11.3.2     D   Mark       11-10-826   98
                    Hamilton




50   11.4.4     P                          94




18   11.3.1.1   D   Mark       11-10-826   98
                    Hamilton
1    3.1        D   Dorothy                97
                    Stanley




33   11.3.0a    D   Mark       11-10-826   98
                    Hamilton




59   11.3.1.2   D   Mark       11-10-826   98
                    Hamilton
16   11.3.0a    A   95




41   7.4.1.1    A   93




31   7.4.6.1    A   93


58   D          A   93




     7.3.2.38   A   94
    9.2.4   A   94




4   11.5    D   94
44   7.3.1.15    P              94




55   7.4.4.2     P              94




10   11.2.1.0a   P              94




30   11.5.3      P   Kaberi     94
                     Banerjee




11   11.2.1.0a   D              94
25   20.3.12.1   P   Dorothy   96
                     Stanley




64   11.3.2.2    A             93



42   11.3.2.2    P             93
27   D          P   93




11   7.3.2.6    A   93




25   7.4.1.0a   A   93




56   7.4.7.1    A   93




1    7.4        P   93




41   7.4.1.1    D   93
49   11.9a.3.1   D   94




     11.11.5     D   95




25   7.4.1.0a    A   93
5    11.1.2.2   P                             93




16   11.3.0a    D   Adrian     11-10-0728r1   98
                    Stephens




22   11.3.0a    D   Adrian     11-10-0728r1   98
                    Stephens




26   11.3.0a    D   Adrian     11-10-0728r1   98
                    Stephens




1    11.3.1.2   D   Adrian     11-10-0728r1   98
                    Stephens




40   11.3.1.3   D   Adrian     11-10-0728r1   98
                    Stephens
25   11.3.2.2   D   Adrian     11-10-0728r1   98
                    Stephens




11   11.3.2.3   D   Adrian     11-10-0728r1   98
                    Stephens




37   11.3.2.4   D   Adrian     11-10-0728r1   98
                    Stephens




45   11.3.2.4   D   Adrian     11-10-0728r1   98
                    Stephens
38   11.3.2.4   D   Adrian     11-10-0728r1   98
                    Stephens




64   11.3.2.5   D   Adrian     11-10-0728r1   98
                    Stephens




42   11.3.2.7   D   Adrian     11-10-0728r1   98
                    Stephens




41   11.3.2.2   D   Adrian     11-10-0728r1   98
                    Stephens
1   7.4.6.4   D   94
31   11.10.8.7   D   94
32   9.9.1.3   A   Kaberi     94
                   Banerjee
26   11.10.8.6   P   94
49   8.4.11    A    94




38   8.4.1.9   P   101
38   8.4.1.9   5000 P   101




33   11.4.13       U      0
36   10.14   U   0
34   10.2.1.6   U     0




17   8.5.9.4    P   101




34   12.2.1     P   101
9    General   P   101




44   10.5.4    U     0




55   8.3.1.1   P   101
37   8.3.3.9     P   101




16   8.4.1.17    U     0




44   11.2.3.3.   P   101
     3




39   11.5.2      P   101
1   8.5.7.5   U   0
31   10.11.9.7   U     0




                 P   107




1    E.1         D   112
28   E.1         D   112




62   15.4.7.10   A   107
59   3.3        P   107




27   6.3.31.3   D   107
56   8.4.2.1   P   107




58   10.3      P   108
1    D            D   109




1    E            D   109




54   8.4.2.10     D   106




58   16.4.6.6.    P   106
     1


13   C.3          A   106



13   A.1          A   106




8    Boilerplat   P   107
     e
12   8.4.2.37   D   109




45   8.4.2.1    A   106



63   8.4.2.45   A   106

36   8.3.3.2    P   107




25   8.4.2.1    D   109
1   8.3.1.8   P   Adrian     113
                  Stephens




1   8.3.1.9   P   Adrian     113
                  Stephens
41   9.20.4     P   104




13   9.20.7.2   P   104
9    9.20.7.6.   P           104
     2




21   9.20.7.6.   P           104
     2




43   19.3.20.2   P   Vinko   111




39   19.3.20.1   P   Vinko   110
35   4.2.3      A   107




34   9.19.2.4   D   104
1    9.3.2.11   P   Matthew   11-11/138r0   109
                    Fischer




12   9.3.2.11   P   Matthew   11-11/138r0   109
                    Fischer
7    9.19.2.4   P   104




37   9.18.5     P   108




9    9.3.2.11   A   104
36   6.3.3.3.2   D   107




46   6.3.3.3.2   A   107

48   4.3.7       P   104
19   10.8.5   P   104
11   10.8.5   P   104




62   10.8.2   P   104




17   10.8.1   D   104




15   10.8.3   P   104
65   10.8.4     P             104




12   8.1        D   Matthew   113
                    Fischer




15   8.1        A             107




46   6.3.14.1   D             107
39   3.1        D             107




16   8.4.1.11   D   Matthew   113
                    Fischer
50   8.5.8.2   D   112




46   8.5.8.2   D   112




58   B.3.4     P   107




7    8.3.3.2   P   107
39   9.3.2.8.1   A   108




37   8.2.5.2     A   106



37   8.2.5.2     A   106




52   5.2.13.5.   U     0
     4 and
     others




52   5.2.13.5.   U   107
     4 and
     others
6   10.11.9.1   P   108




6   10.11.9.1   P   108




                P   106
16   C.3       D   112




64   C.3       D   112




44             A   106



25   3.1       D   109




9    1.3       A   109




61   4.3.8.1   P   106
36   8.2.2       P           106




6    11.3.1      P           108




38   17.3.9.7.   P   Vinko   111
     3




23   17.3.11     P           109




27   17.3.12     P           109




1    19          D           109
51   19.4.3      P           109




50   19.3.22     A           109




14   19.3.23     A           109




56   19.3.20.1   P   Vinko   110




38   19.3.20.2   P   Vinko   111
39   19.3.11.4   P   109




1    C           A   109
59   8.4.1.1   P   Dan Harkins                109




44   11.5.2    A   Dan Harkins 11-10/1071r1   109
1    11.3        D           104




4    10.3        D           108




                 P           107



44   19.3.20.2   P   Vinko   111




39   19.3.20.1   P   Vinko   110
21   17.3.9.3    D   109




39   19.3.20.1   D   109




51   8.4.1.29    A   106
     5           D           112




43   19.3.20.2   P   Vinko   111




39   19.3.20.1   P   Vinko   110




58   10.3        P           108
58   10.3   P   108




58   10.3   P   108




58   10.3   P   108




58   10.3   P   108




58   10.3   P   108




58   10.3   P   108
5    10.3.2.3   P   108




58   10.3       P   108




58   10.3       P   108
58   10.3   P   108




            P   109
     P   104




42   D   104
     8.4.2.37   D   109




21              A   112
P   112




P   109
10.2   P   104




       D   104
P   104




P   108
29              D   113




64   10.11.16   P   104




42   10.11.11   A   104




5    10.3.3.2   P   108
54   12.9.3.1   A   108




23   12.9.3.1   A   108




49   12.9.5.1   A   108




27   12.9.5.1   A   108




33   11.5.2     A   108
34   C          D   Mark       112
                    Hamilton




33   10.3.1     P              108




5    10.3.2.3   P              108
              P   106




26            A   106


46   10.9.1   A   106



16   8.2.4    A   106
14   8.4.2.29    U   106




48   11.3.2.5.   A   106
     4
1    11.5.1.7    A   106




1    11.5.4.8    D   109




1    13.7.5      A   106


52   15.4.4.4    A   106

38   15.4.6.3    A   106


51   16.2.5      A   106
47   Q.4         P   109




46   10.1.4.3.   P   107
     2
34   11.5.4.4   A   104
65   8.4.2.2    D   113




10   10.3       D   108




22   10.3.2.3   P   108
33   11.5.2     A   106




12   11.7.2.7   A   104




44   11.7.2.7   A   104
1   8.5.7.5   P   112
31   10.11.9.7   P           104




59   10.15.1     P           108




22   17.3.9.7.   P   Vinko   111
     3
39   19.3.20.1   P   Vinko   110




3    19.3.20.1   U             0




43   19.3.20.2   P   Vinko   111




53   Q.4         P           109
                D   107




     3.1        D   107




62   3.3        D   107




     11.5.7.1   D   104
H.2   D   107




H.2   D   107




H.3   D   107




H.3   D   107
     H.4   D                107




     H.4   D                107




     H.4   D                107




39   D.1   A   Michael      112
               Montemurro
14   D.1   A   Micheal      112
               Montemurro




14   E.1   A                112




21   E.1   A                112




51   E.1   A                112




31   E.1   A                112
16   E.1       A   112




50   E.1       A   112




50   E.1       A   112




17   10.10.1   P   108
28   9.18.5   D               104




54   9.18.6   P               104




40   9.18.5   U   Peter         0
                  Ecclesine




1    6        D               107
1    1     P   107




62   3.1   P   106




8    3.1   A   106




21   3.1   A   106




32   3.1   P   106




10   3.2   D   106




17   3.2   A   106




26   3.2   P   106




40   3.2   A   106
45   3.2       P   106




15   3.3       D   106




24   3.3       P   106




47   4.2.3     P   106




15   4.2.4     A   106




64   4.3.4.2   P   106




34   4.3.7     P   106
62   4.3.9.5   D   106




15   4.5.3.3   A   106




21   4.5.3.3   P   107




49   4.5.3.4   A   106




65   4.6       A   106




1    4.7       P   106



20   4.8       A   106
22   4.8       A   109




39   4.9.3.2   A   106


56   4.9.3.4   A   106




12   4.9.4.2   A   106


42   4.9.4.3   A   106


45   4.9.4.4   A   106




46   4.9.5     A   106


14   5.1.1.1   P   106




10   5.1.1.5   A   106
44   5.1.3       A   106


56   5.2.2.2     A   106


58   5.2.3.2     A   106




28   6.3.2.2.2   D   106




17   6.3.3.2.2   A   106




27   6.3.3.3.2   A   106


23   6.3.3.3.2   P   106




25   6.3.4.2.2   A   106




33   6.3.4.2.2   A   106


20   6.3.5.2.2   A   106




7    6.3.5.3.2   P   106
31   6.3.7.2.2   A   106




25   6.3.8.2.2   A   106




5    6.3.10.2.   A   106
     3

49   6.3.11.2.   A   106
     2

53   6.3.11.2.   A   106
     2

33   6.3.11.2.   P   106
     3




38   6.3.11.2.   A   106
     3

64   6.3.12.1.   A   106
     3

2    6.3.12.1.   A   106
     3

2    6.3.12.1.   A   106
     3

61   6.3.14.2.   D   106
     2




11   6.3.14.2.   A   106
     2



12   6.3.14.2.   A   107
     2
5    6.3.16.3.   A   106
     2



35   6.3.19.1.   A   106
     4



57   6.3.24.1.   A   106
     4



34   6.3.26.2.   A   106
     1



6    6.3.29.3.   P   106
     2


6    6.3.29.5.   P   106
     2


6    6.3.29.7.   P   106
     3


24   6.3.39.1.   P   106
     2



20   6.3.39.2.   P   106
     2


22   6.4.3.4     A   106




32   6.4.4.2     A   106




34   6.4.4.2     A   106
17   6.4.4.3     A   106




39   6.4.5.2     D   106




31   6.4.7.1     A   106




64   6.4.8.1     A   106




47   7.3.5.2.4   A   106




6    7.3.5.3.3   A   106




33   7.3.5.4.3   A   106




34   7.3.5.4.3   P   106




40   7.3.5.4.4   A   106




64   7.3.5.5.3   A   106
4    7.3.5.5.4   A   106




16   7.3.5.6.1   A   106




30   7.3.5.6.3   A   106




37   7.3.5.6.4   A   106




59   7.3.5.7.3   A   106




65   7.3.5.7.4   A   106




22   7.3.5.8.3   A   106




58   7.3.5.12.   P   106
     2




46   8.2.4.1.2   D   106
46   8.2.4.1.7   A   106




10   8.2.4.1.8   P   106



47   8.2.4.1.9   A   106


41   8.2.4.5.4   A   106



56   8.2.5.4     P   106




55   8.3.3.2     A   106


63   8.4.1.15    A   106




40   8.4.1.17    A   106




42   8.4.2.14    D   106




37   8.4.2.23.   A   106
     1



24   8.4.2.23.   A   106
     1
53   8.4.2.23.   A   106
     11



29   8.4.2.23.   P   106
     11



14   8.4.2.24.   A   106
     2




18   8.4.2.24.   A   106
     2
4    8.4.2.24.   A   106
     10
38   8.4.2.24.   A   106
     11
38   8.4.2.23.   P   106
     11



35   8.4.2.47.   A   106
     3

38   8.4.2.27.   P   106
     3




35   8.4.2.27.   P   106
     4
5    8.4.2.27.   D   106
     5




43   8.4.2.29    A   106




2    8.4.2.30    A   107



2    8.4.2.30    A   106




39   8.4.2.32    A   106

20   8.4.2.32    A   106




20   8.4.2.32    A   106




52   8.4.2.33    A   106

33   8.4.2.33    A   106



34   8.4.2.33    A   106


29   8.4.2.34    A   107

29   8.4.2.34    P   106
30   8.4.2.42    P   106




10   8.4.2.45    A   107



53   8.4.2.50    A   106


31   9.3.1       A   106


2    9.3.2.6     A   106




6    9.3.2.6     A   106




7    9.3.2.6     A   106




52   9.3.2.8.1   A   106




65   9.3.2.8.1   A   106




2    9.3.4.3     A   106




6    9.3.4.4     A   106
64   9.4.2     A   106




63   9.7.3     P   106




54   9.7.5.2   P   106




55   9.8       P   106




60   9.12.2    P   106




1    9.12.2    A   106




13   9.18.1    A   106




18   9.18.1    A   106
20   9.18.1     P   106



47   9.18.3     A   106




26   9.19.2.7   A   106




56   9.19.3.3   A   106




57   9.19.3.3   A   106


34   9.20.7.7   P   106




28   9.22.2     A   106




38   9.22.2     A   106




32   9.22.2     A   106




53   9.22.4     P   106




46   9.25.1.1   A   106
54   9.27.2     D   106




64   9.28.2.3   P   106




65   9.29.2     P   109




44   9.29.2     A   106




46   9.29.2     A   106




48   9.29.2     A   106




33   10.1.4.1   P   106




6    10.1.4.5   A   106




23   10.1.4.6   A   106
26   10.1.4.6   A   106




27   10.1.4.6   A   106




64   10.1.5     A   106




63   10.1.8     A   106




28   10.2.1.2   D   109




18   10.2.1.6   A   106


30   10.4.6     A   106

65   10.4.9     A   106




41   10.8.1     A   106




12   10.9.1     A   106




38   10.9.8.3   A   106
17   10.9.8.3    A   106




24   10.11.1     P   106




50   10.11.4     D   106




57   10.11.4     A   106




60   10.11.6     A   106




24   10.11.1     P   106




33   10.11.9.4   A   106




36   10.11.9.4   A   106




7    10.11.9.6   A   106

29   10.11.9.8   A   106


55   10.11.10.   P   106
     1
6    10.11.12    A   106




26   10.11.15.   A   106
     2



23   10.16.3     A   106




55   10.18       P   106




13   10.18       P   106




21   10.18       P   106
1    11          P   106




55   11.1.6      A   106


62   11.1.6      A   106


64   11.2.3.1    P   106


39   11.3.2.1.   A   106
     2



27   11.3.2.2    A   106


39   11.3.2.4.   A   106
     1


40   11.3.2.4.   A   106
     1
41   11.3.2.4.   P   106
     2




39   11.3.2.5.   A   106
     4



48   11.3.3.4.   P   106
     2




23   11.4.1.1.   A   106
     1

24   11.4.1.2.   A   106
     2



42   11.4.1.2.   A   106
     2



45   11.4.1.2.   A   106
     2

12   11.4.1.2.   A   106
     2

59   11.4.5      A   106


6    11.4.5      A   106

10   11.4.5      A   106


27   11.4.5      P   106
27   11.4.5     P   106



51   11.4.8.3   P   106




26   11.4.9     A   106


43   11.4.10    P   106



1    11.4.11    A   106


56   11.4.11    A   106




44   11.5.1.2   P   108




45   11.5.1.2   P   104




47   11.5.1.2   D   104



47   11.5.1.2   P   108
4    11.5.1.3   P   109




36   11.5.1.3   P   106




41   11.5.1.3   D   108




47   11.5.1.3   A   106




49   11.5.1.3   P   106




54   11.5.1.3   A   106
13   11.5.1.3   P   106




58   11.5.1.4   P   108




64   11.5.2     P   106



52   11.5.3     D   106




4    11.5.4.1   A   106




27   11.5.4.6   P   109
29   11.5.4.6   P   109




20   11.5.6.6   P   104




32   11.5.7.3   A   106


40   11.5.7.3   P   109




42   11.5.7.3   P   109
64   11.5.8     P   106




7    11.5.9.1   P   106



45   12.5.2     P   106




25   12.5.3     P   106




37   12.5.4     A   106


39   12.5.5     A   106


9    12.6.2     P   106
9    12.5.2      P   106




19   12.6.3      P   106




10   12.6.3      P   106




38   12.8.1      A   106




23   13.4.2      A   106



41   13.4.4.2.   A   106
     2

19   13.4.4.4.   A   106
     2

60   13.9.2.1    A   106


32   13.9.2.2    A   106
14   14.3.1      P   106



27   14.5        A   106


46   16.3.3.6    P   106




22   16.4.6.7    P   106




14   17.3.9.3    A   106


10   18.7.3.3    P   106




29   19.3.2      P   106




51   19.3.12.2   A   106




29   19.3.7      A   106
51   B.3.1     A   106




40   B.4.1     A   106




23   B.4.4.1   D   106




11   C.3       P   107




33   C.3       P   106




34   C.3       A   106
33   C.3   P   Trish Gerdon   113




13   D.1   A                  106
52   D.1   P   106




47   H     P   106




15   H.2   D   106
43   H.3        D   106




17   H.3        D   106




36   Q.2        P   106




0    9.3.2.11   P   109
16   1.3         A   105




56   4.3.7       D   105




59   6.3.31.2.   A   105
     2

39   6.3.31.3    P   105




64   6.3.31.3.   A   105
     2

54   8.2.4.3.4   A   105
22   6.3.43.3.   A   105
     2

36   8.4.2.28    A   105




8    8.4.2.63    D   105




                 P   105




39   8.5.6       A   105




59   6.3.42.1.   P   105
     1




64   10.2        A   105
26   B   P   105




13   B   D   105




20   B   D   105




27   B   D   105




38   B   D   105




52   B   D   105




53   B   D   105




60   B   D   105




17   B   D   105
38   B   A   105



44   B   A   105


56   B   A   105


30   C   P   105




40   C   P   105



     D   U   105




     D   U   105
8    D       P   105




             A   105




             P   105




44   D.1     A   105


25   D.2.2   A   105
64   4.3.11      D   105




1    1.2         P   105



1    8.2.4.3.4   A   105




8    8.4.1.31    P   105




63   C           A   105




1    1.3         A   105
57   8.2.4.3.4   P   105




62   8.3.3.1     A   105




24   8.4.1.31    A   105
25   8.4.2.28    P   105




27   8.4.2.28    A   105




64   10.20       A   105



7    17.3.10.3   A   105




29   B.4.4.1     A   105




40   B.4.4.1     A   105
47   B4.8    A   105




58   B4.8    A   105




33   D.1     A   105




22   D.2.2   D   105
60   D.2.3       D   105




27   8.4.2.28    A   105




64   10.20       A   105




7    17.3.10.3   A   105




     Abstract    A   105
Keywords    A   105




1.3         A   105


6.3.31      D   105




6.3.42.1.   A   105
1




8.4.1.31    P   105
     8.4.1.31    P   105




26   8.4.2.28    P   105




     8.5.6       P   105




                 U   105




     E/F         U   105




39   6.3.31.3.   P   105
     2



55   6.3.42.1.   P   105
     1
59   8.2.2      A   105




4    8.3.2.1    A   105


61   8.3.3.1    A   105


53   8.3.3.15   A   105




8    8.4.1.31   P   105
13   8.4.1.31    P   105




10   8.4.2.28    A   105




13   8.4.2.28    A   105




35   8.5.6       A   105




53   8.5.8.11    A   105




52   10.11.10.   A   105
     3




28   B.4.4.1     P   105




40   B.4.4.1     P   105
40   B.4.8     A   105



47   B.4.8     A   105



35   D.3       A   105




     General   A   105




50   D.1       A   105




42   D.1       D   105




42   D.1       D   105
45   E.1    D   105




0    10.3   A   103




0               109
21   6.3.7.5.2       Adrian
                     Stephens




23   6.3.8.5.2


37   8.2.4.1.8


5    8.4.1.11




                 A




30   8.4.2.27.
     3

50   8.5.8.12
47   10.2.1.14


43   10.2.1.15


18   10.3.2.3




10   10.3.3.2




24   10.3.3.3




6    10.3.3.3
47   10.3.3.3




31   10.3.3.4




23   10.10.1




29   11.5.11.4
     .2



58   11.5.11.4
     .3

48   11.5.11.4
     .4
42   12.9.3.1




12   S




     C.3        A
     General     Adrian
                 Stephens




22   17.3.9.7.
     3




63   8.5.8.11
     General    A



35   8.5.13.3




58   8.5.13.4
31   8.5.13.7




34   8.5.13.7
18   11.5.11.2




2    11.5.11.4
     .2




32   11.5.11.4   A
     .2




42   10.22.5
58   10.22.6.2   P
     .1




62   10.22.6.2
     .1




1    10.22.5     P




62   D.2.3       A




61   E.1         A
58   10.22.6
6    8.4.1.11




31   C.3
59   8.4.2.2
23   10.3.2.4




39   6.3.9.1.3
57    10.2.1.15
      .2




63    11.5.11.4   A
      .3


57    10.22.6




921   11.5.11.4
      .4
16   11.4.1.2



52   8.5.13.2




11   10.2.1.15
14             A




47   8.4.2.1




24   8.4.2.1   A
22   17.3.9.7.
     3




28   10.15.2




28   10.15.2
41   8.6.3




49   3.1



52   4.2.3

12   8.1




15   9.27.2   A

22   11.4.2   A

22   11.4.2
28   11.5.2




4    12.10.3




15   C          P




23   10.3.2.2




64   10.3.2.5   P
46   10.3.3.3




48   10.3.3.3




44   B.3.1
9   10.3.3.5




9   10.3.3.5
39   8.3.3.2




21   3.2




27   10.2.1.6


30   8.2.4.1.8
6    10.3.3.3




11   10.3.3.3
1    3.1




10   3.1




52   3.1




20   3.1


5    3.3




21   4.3.12



56   6.3.42.2.
     2



59   6.3.42.2.
     2
13   6.3.43.1.
     1

51   6.3.43.1.
     4




7    6.3.43.2.
     2




20   6.3.44.2.
     2


47   6.3.44.4.
     4
31   6.3.45.1.
     2




13   6.3.45.2.
     2




4    6.3.45.3.
     4



34   6.3.45.4.
     2
4    6.3.45.6.
     4


35   6.3.45.7.
     2




4    6.3.45.9.
     4


                 U   0




3    6.3.49




35   10.22.3




49   D.1
36   D.1




6    D.1




23   D.1




31   D.1




50   E.1




14   E.1
15   D.1




19   D.1




23   10.10.1




54   8.5.8.12
9    8.5.8.12




4    8.5.8.12




20   8.5.13.2




24   8.5.13.2




36   8.5.13.2




40   8.5.13.2
44   8.5.13.2




2    E.2.2




52   D.1         A

57   D.1         A


10   17.3.10.3   A
1   D.2.5




    2




    11.1.6
8




8
    8




0
0




61   3.1   A


29   3.1   A



6    3.2   A
16   3.2   P




17   3.2   S




21   3.3   S
21   3.3   D




22   3.3   P




52   3.3   P




32   3.3   A
62   4.3.9.5     A




29   6.3.2.2.2   D
60   6.3.14.2.
     2
65   6.4.5.2




45   8.2.4.1.2




32   8.4.2.4
29   8.4.2.24.   P
     11




9    8.4.2.24.   P
     11




54   8.4.2.44    P




44   8.4.2.49    P




27   10.1.1      P
36   10.1.3.3   P




48   10.3.1




2    10.7.1     P




16   11.3.1     A




38   11.3.4.6   A
31   11.3.4.6




23   11.5.11.2




24   11.5.11.2   A

22   B.4.10      A


23   B.4.10


15   C.3         D
27   C.3        D




48   8.5.13.4
60   10.22.6




51   10.22.1




44   B.3.1




55   10.11.17




61   8.3.3.1    A
60   6.3.7.2.2




60   6.3.7.2.2




62   6.3.24.1.
     4




34   8.4.2.27.
     3


19   9.19.2.3
Comment                           Proposed Change                    Resolution                       Owning
                                                                                                      Ad-hoc

TGn comment: The STA              TGn Resolution:MAC: 2007-          Reject. There is no proposed     EDITOR
defined quiet element may be      07-19 16:15:31Z Reject - The       change to this comment.
issued by a STA both in the       requested change to the draft      TGmb encourages the
Infrastructure and IBSS           seems to be out of scope of        commentor to submit a
modes. In the former case it      the work of TGn. The group         proposal for consideration, if
could be used by the STA to       suggests taking the comment        desired.
complete measurements             to TGmb, although it is not
without disruption and also       clear if that is the appropriate
allow for the completion any      venue either.
co-located BT transmissions.
TGn comment: The STA may          TGn Resolution:MAC: 2007-          Reject. There is no proposed     EDITOR
also reserve medium time for      07-19 16:12:47Z Reject - The       change to this comment.
its own communication needs       requested change to the draft      TGmb encourages the
(to participate concurrently in   seems to be out of scope of        commentor to submit a
multiple wireless networks)       the work of TGn. The group         proposal for consideration, if
via a TSPEC; the use of the       suggests taking the comment        desired.
medium time reserved in this      to TGmb, although it is not
manner shall not be used to       clear if that is the appropriate
communicate with the AP or        venue either.
DLS neighbor; the signal
strength of the STA's
communications during these
reservation periods shall be
such that it does not interfere
with the infrastructure BSS
operations.The STA shall use
these reservation periods to
participate in other wireless
network protocols.



TGn comment: The sentence         TGn Resolution:MAC: 2007-          Counter. The text will be       EDITOR
of measurement period in the      07-19 16:25:31Z Reject - The       modified in clause 11.9.6, last
basic spec seems to be wrong      text that the commentor refers     paragraph on page 465 to be:
in relation to time estimation    to is directly quoted and          "… switches take
that the channel switch takes.    unmodified from the baseline       dot11ChannelSwitchTime per
It should be not less than the    standard and is with reference     switch"
related parameter. Proposed       to a topic which is
Change: Change the last           unaddressed and unmodified
sentence in the first             by the TGn draft. Therefore,
paragraph "… switches take        the issue raised by the
not less than                     commentor should be
dot11ChannelSwitchTime per        addressed to TGmb. TGn will
switch."                          forward this comment to
                                  TGmb.
TGn comment: LongNAV in           TGn Resolution:MAC: 2007-         UNRESOLVABLE (EDITOR: EDITOR
EDCA has some problems,           07-17 21:20:45Z Reject - the      2010-05-20 09:24:36Z) - In
esp at the AP because frames      issue cited here applies to the   9.2.1, 3rd paragraph, replace
for different STAs are mixed      baseline standard, and is not     “and use of the NAV in HCF is
together unlike in HCCA.1.        necessarily related to anything   described in 9.9.2.2.1” with
Say the AP starts the TXOP        that has been introduced by       “and the use of the NAV in
by performing a self-CTS for      TGn, with the exception that      HCF is described in 9.9.1.2
LongNAV protection. If it         some of the rationales for the    and 9.9.2.2.1”.
wants to perform a RTS/CTS        given behavior are related to     Add a new paragraph to the
transaction with a STA in the     TGn features, but others are      end of subclause 9.9.1.2:
same TXOP, the STA will not       not, and therefore, the           “A STA shall save the TXOP
respond with CTS.2. Say the       problem is one that can exist     holder address for the BSS in
AP starts the TXOP by             in the baseline, and as such,     which it is associated, which
performing an RTS/CTS             the issue should be raised        is the MAC address from the
frame exchange for LongNAV        with TGmb.                        Address 2 field of the frame
with the first STA for which                                        that initiated a frame
data is pending in the AC                                           exchange sequence. If an
queue. Subsequently if it                                           RTS frame is received with
wants to perform an RTS/CTS                                         the RA address matching the
frame exchange with another                                         MAC address of the STA and
STA in the same TXOP, the                                           the MAC address in the TA
other STA will not respond                                          field in the RTS frame
with the CTS.Why will it want                                       matches the saved TXOP
to perform RTS/CTS inside a                                         holder address, then the STA
TXOP?1. For Beamforming.2.                                          shall send the CTS frame
For MIMO PS.3.                                                      after SIFS, without regard for,
Implementation specific stuff..                                     and without resetting, its NAV.
 Proposed Change: HCCA                                              When a STA receives a frame
had LongNAV much before                                             addressed to it and requires
EDCA had. See section                                               an acknowledgment, it shall
9.9.2.2.1 which says that all                                       respond with an ACK frame
STAs should keep track of                                           independent of its NAV. The
who is the TXOP holder and                                          saved TXOP holder address
TGn comment: 2005 Style            TGn Resolution:GEN: 2007-           Reject. As per original TGn    EDITOR
Guide 10.5.2 states                07-19 17:41:28Z Reject -            commenter, no action is
"Definitions shall not include     submission 11-07-2145r1:            necessary, as the clause was
references to other parts of                  Reject. The              fixed in TGn draft 6.
the standard". Proposed            commenter correctly quotes
Change: remove the                 the style guide. The 802.11
references to "Clause 17",         baseline uses the definitions
"Clause 19", "Clause 20". This     for two purposes: a) generic
problem needs to be fixed at       definitions suitable for
the following page.lines: 1.20     inclusion in IEEE 100; b)
(3 times), 1.25 (3 times), 1.36,   IEEE 802.11 specific
1.44, 2.09, 2.14, 2.32, 2.43,      definitions that make no
3.15, 3.20, 3.24                   sense outside the context of
                                   the 802.11 standard. The
                                   definitions that the commenter
                                   identifies fall into the latter
                                   category and there is no
                                   obvious way to avoid the use
                                   of Clause references as they
                                   identify PHY capabilities.
                                                            This has
                                   been discussed with the IEEE-
                                   SA editorial staff. They
                                   suggest that we address this
                                   in REVmb, by introducing a
                                   new section for local terms,
                                   which is not intended to
                                   provide definitions for IEEE
                                   100.
                                    Until then, it makes no sense
                                   to attempt to do this
                                   piecemeal in 802.11
TGn comment: I would hope          amendments, so no action is
                                   TGn Resolution:MAC: 2007-           Accept the proposed          EDITOR
that the receiving STA is the      06-20 00:30:24Z Reject -            resolution embedded in the
intended STA!. Proposed            comment rejected by MAC             "Comment" column. Proposed
Change: delete "which is the       adhoc because the comment           Change: delete "which is the
intended STA"                      is out of scope - This              intended STA"
                                   comment questions language
                                   that is part of the baseline
                                   standard and that is not
                                   changed by the proposed
                                   TGn amendment. The correct
                                   venue for raising this issue is
                                   within TGmb. The TGn group
                                   will forward this comment to
                                   TGmb.
TGn comment: identify which       TGn Resolution:MAC: 2007-         Counter. Reword the last       EDITOR
STA is accepting. Proposed        06-20 00:30:24Z Reject -          sentences of the first para of
Change: change to "When the       comment rejected by MAC           9.10.2 as follows: "The
receiving STA accepts"            adhoc because the comment         recipient(#7) STA(#6) has the
                                  is out of scope - This            option of accepting or
                                  comment questions language        rejecting the request. When
                                  that is part of the baseline      the recipient(#7) STA accepts,
                                  standard and that is not          then a Block Ack agreement
                                  changed by the proposed           exists between the originator
                                  TGn amendment. The correct        and recipient. When the
                                  venue for raising this issue is   recipient(#7) STA accepts, it
                                  within TGmb. The TGn group        indicates the type of Block
                                  will forward this comment to      Ack and the number of buffers
                                  TGmb.                             that it shall allocate for the
                                                                    support of this block. If the
                                                                    intended recipient(#7) STA
                                                                    rejects the request, then the
                                                                    originator shall not use the
                                                                    Block Ack mechanism. "

TGn comment: The sentence         TGn Resolution:Reject.            Accept TGn resolution to     EDITOR
leads to several                  Reason to reject: This text is    reject, but note that the
interpretations. Is it the TXOP   in baseline and should be         references do not match.
Limit (as communicated by         addressed by TGmb through
the AP in the beacon) or just     an interpretation request.
any value between zero and                 A strawpoll was
the TXOP Limit?. Proposed         conducted and the proposed
Change: Clarify.                  to reject was accepted
                                  Unanimously
TGn comment: Draft 2.0 uses    TGn Resolution:Reject - The           Reject. Not applicable to    EDITOR
elements of IEEE P802.11k      commenter does not indicate           TGmb.
D7.0. The Introduction to      any changes to the draft.
Draft 2.0 states that the Draft                        In
2.0 amendment specifies        answer to the commenter,
enhancements from other        REVmb will wrap in one or
drafts, as well: IEEE P802.11  more of the drafts listed as
Rev-ma D9.0; IEEE 802.11r      our dependencies. One or
D4.1; IEEE 802.11p D2.0..      more of these dependencies
Proposed Change: Assuming      may be replaced by IEEE
Draft 2.0 is approved for      802.11 200x where 200x is its
recirculation ballots, please  publication date, if this occurs
clarify whether transition of  during TGn's ballot process.
TGn's draft to sponsor ballot                               If any
be dependent upon the          of the drafts have not been
completion of these other      wrapped into an 802.11
                               revision at the time of TGn's
drafts (i.e. either completion of
their recirculation or sponsor publication, it will list the
ballot or ExecCom approval or  dependencies as shown here.
IEEE publication). If not,       The published TGn draft can
please clarify the IEEE 802.11 only depend on published
mechanism to incorporate any   802.11 standards and
changes from these other       amendments, and so this list
drafts.                        is dependent on the order of
                               completion of amendments,
                               which is dependent on the
                               progress that task groups
                               make through letter and
                               sponsor ballot. This may
                               result in the list of our
                               dependencies being adjusted
                               at any time during the
TGn comment: The lost          balloting process as the
                               TGn Resolution:MAC: 2008-             Counter. Add "or missing"       EDITOR
MSDU should be considered 01-11 01:54:51Z Reject -                   after the word "incomplete", in
here. Otherwise 11 MAC may               This issue is not           the cited sentence.
send out of order frame to the related to the .11n. All
upper layer which is not       problems found in the basic
allowed.. Proposed Change: spec should be fixed in the
Change the sentence to:        TGmb.
Upon arrival of a
BlockAckReq frame, the
recipient shall pass up the
MSDU and A-MSDU starting
with the starting sequence
number sequentially until
there is an incomplete MSDU
or A-MSDU or lost MSDU.
TGn comment: Was                   TGn Resolution:Reject: The        Reject. As per original TGn    EDITOR
LB97/9492005 Style Guide           commenter correctly quotes        commenter, no action is
10.5.2 states "Definitions shall   the style guide. The 802.11       necessary, as the clause was
not include references to          baseline uses the definitions     fixed in TGn draft 6.
other parts of the                 for two purposes: a) generic
standard"Resolution given          definitions suitable for
was: Reject. The commenter         inclusion in IEEE 100; b)
correctly quotes the style         IEEE 802.11 specific
guide. The 802.11 baseline         definitions that make no
uses the definitions for two       sense outside the context of
purposes: a) generic               the 802.11 standard. The
definitions suitable for           definitions that the commenter
inclusion in IEEE 100; b)          identifies fall into the latter
IEEE 802.11 specific               category and there is no
definitions that make no           obvious way to avoid the use
sense outside the context of       of Clause references as they
the 802.11 standard. The           identify PHY capabilities. This
definitions that the commenter     has been discussed with the
identifies fall into the latter    IEEE-SA editorial staff. They
category and there is no           suggest that we address this
obvious way to avoid the use       in REVmb, by introducing a
of Clause references as they       new section for local terms,
identify PHY capabilities. This    which is not intended to
has been discussed with the        provide definitions for IEEE
IEEE-SA editorial staff. They      100. Until then, it makes no
suggest that we address this       sense to attempt to do this
in REVmb, by introducing a         piecemeal in 802.11
new section for local terms,       amendments, so no action is
which is not intended to           proposed in the TGn draft in
provide definitions for IEEE       resolution of this comment.
100. Until then, it makes no
sense to attempt to do this
piecemeal in 802.11
TGn comment: 2005 Style          TGn Resolution:Reject: The        Reject. As per original TGn      EDITOR
Guide 10.5.2 states              commenter correctly quotes        commenter, no action is
"Definitions shall not include   the style guide. The 802.11       necessary, as the clause was
references to other parts of     baseline uses the definitions     fixed in TGn draft 6.
the standard". Proposed          for two purposes: a) generic
Change: Remove "The value        definitions suitable for
is defined in 9.6.0c."           inclusion in IEEE 100; b)
                                 IEEE 802.11 specific
                                 definitions that make no
                                 sense outside the context of
                                 the 802.11 standard. The
                                 definitions that the commenter
                                 identifies fall into the latter
                                 category and there is no
                                 obvious way to avoid the use
                                 of Clause references as they
                                 identify PHY capabilities. This
                                 has been discussed with the
                                 IEEE-SA editorial staff. They
                                 suggest that we address this
                                 in REVmb, by introducing a
                                 new section for local terms,
                                 which is not intended to
                                 provide definitions for IEEE
                                 100. Until then, it makes no
                                 sense to attempt to do this
                                 piecemeal in 802.11
                                 amendments, so no action is
                                 proposed in the TGn draft in
                                 resolution of this comment.


TGn comment: There're MIB        TGn Resolution:GEN: 2008-         Reject. Not applicable to        EDITOR
variables listed that the 11n    05-15 17:33:20Z Reject -          TGmb. The commentor is
amendment text does not use               The 11n amendment        encouraged to supply a list of
or even refer to at all, like    simply follows the practice       MIB variables that need to be
"dot11HTgreenfieldOptionEna      followed by 802.11 regarding      removed.
bled", just to give a random     MIB variables. This issue is
example. Why do we specify       beyond the scope of TGn.
them if we never set them        This comment will be
properly or use them?.           forwarded to TGmb for
Proposed Change: Decide          considerations.
this issue and amend
accordingly.
TGn comment: IEEE Style         TGn Resolution:Reject. The          Reject. As per original TGn      EDITOR
Guide clearly states            commenter correctly quotes          commenter, no action is
"Definitions should not include the style guide. The 802.11         necessary, as the clause was
references to other parts of    baseline uses the definitions       fixed in TGn draft 6.
the standard".. Proposed        for two purposes: a) generic
Change: Remove the              definitions suitable for
references to clause numbers    inclusion in IEEE 100; b)
from the definitions            IEEE 802.11 specific
                                definitions that make no
                                sense outside the context of
                                the 802.11 standard. The
                                definitions that the commenter
                                identifies fall into the latter
                                category and there is no
                                obvious way to avoid the use
                                of Clause references as they
                                identify PHY capabilities.
                                                         This has
                                been discussed with the IEEE-
                                SA editorial staff. They
                                suggest that we address this
                                in REVmb, by introducing a
                                new section for local terms,
                                which is not intended to
                                provide definitions for IEEE
                                100.
                                 Until then, it makes no sense
                                to attempt to do this
                                piecemeal in 802.11
                                amendments, so no action is
                                proposed in the TGn draft in
                                resolution of this comment."
TGn comment: LB115/5442         TGn Resolution:EDITOR:              Accept. Also add an editorial    EDITOR
was accepted, but not           2008-04-24 13:36:00Z Reject -       comment to the beginning of
implemented in D4.0.                             In a previous      the annex to indicate that the
Proposed Change: Move the draft the change indicated in             Bilbliography is always the
Bibliography to the final annex the resolution to 5442 had          last annex.
                                been implemented. The
                                change was undone in D4.0
                                because it proved to be
                                difficult to coordinate the
                                updates to the Annex
                                insertions across the multiple
                                current amendments.
                                                      This change
                                can be handled while rolling
                                amendments into the
                                anticipated REVmb revision.
                                                             This
                                comment will be forwarded to
                                the TGmb.
TGn comment: the definition          TGn Resolution:EDITOR:            Accept in principle.        EDITOR
of the Duration/ID field             2008-06-26 10:23:41Z Reject -     Changes to be made once the
belongs in 7, but this text           There is no rule in the style    amendment is available for
defines the procedures and           guide that requires Clause 7      incorporation, based on the
normative behavior of the            not to have normative text.       resolution to Comment 29.
STA to set the value of the          While a separation of
field. It belongs in 9, not in 7..   structure versus behavior is
  Proposed Change: move this         beneficial, the TGn draft is an
text to clause 9. Change cross       amendment to an existing
ref in 7.1.3.2 (where the field      baseline. The description of
is adequately defined in             how to calculate the contents
clause 7) to point to its new        of this field is present in the
place in 9 instead of 7.1.4.         baseline in clause 7. The
Change cross ref in 7.2.1.7.1        TGn amendment is merely
to point to new place in 9.          reworking and extending
                                     existing clause 7 material to
                                     cover the mechanisms
                                     introduced by TGn.
                                       Attempted piecemeal
                                     reorganization of the baseline
                                     through its amendments is not
                                     beneficial.
                                             The correct place to
                                     change where this description
                                     should be put is in REVmb,
                                     where all such text relating to
                                     calculations can be
                                     addressed consistently.




TGn comment: The PSMP                TGn Resolution:EDITOR:           Reject. This is not applicable   EDITOR
Parameter Set field occurs           2008-06-26 13:10:13Z Reject - to TGmb.
only in a single frame, the           The baseline contains
PSMP Action frame, in                mutliple examples of fields
7.4.10.4. As such it is not a        used in only one action frame
multiply-used field to qualify       being specified in 7.3.1. STD-
for inclusion in 7.3.1.              2007 7.4 contains no example
Proposed Change: move the            of an action frame defining
definition of the PSMP               one of its constituent fields.
Parameter Set field to 7.4.10.4                                If the
                                     commenter wishes to change
                                     this style, it should be done
                                     by comment to REVmb
                                     (rather than in comment to
                                     TGn) where it can be treated
                                     consistently rather than
                                     piecemeal.
TGn comment: This              TGn Resolution:MAC: 2008-         Reject. This paragraph is not EDITOR
paragraph duplicates the       07-10 15:23:42Z Counter -         included in TGmb at this time.
requirements of the previous   TGn editor to make changes        This issue may be addressed
paragraph. Proposed            shown under any heading that      when P802.11n is rolled into
Change: delete it              includes CID 7226 within the      TGmb.
                               document 11-08-0742r4. The
                               paragraphs are different,
                               since they include different
                               reasons for setting the same
                               field to the same value. Note
                               to REVmB - some of this
                               behavior is intended to be
                               performed by SME, but there
                               is no clause in the baseline to
                               describe SME behavior, such
                               a clause needs to be added,
                               and needs to be populated
                               with all of the SME behavior
                               that appears spread
                               throughout the entire baseline
                               document.

TGn comment: source of the      TGn Resolution:MAC: 2008-        Reject. Source of               EDITOR
value of aDTT2UTTTime           07-11 21:59:02Z Reject - This    characteristics can be easily
should be mentioned.            attribute comes from the         found using global text
Proposed Change: insert         same location (PLME-             search, so this change adds
"(provided by the PHY in the    CHARACTERISTICS.confirm)         very little value to the
PLME-                           as aSIFStime. There are 84       document.
CHARACTERISTICS.confirm         instances of aSIFStime in the
primitive, see 10.4.3.2)"       baseline, none of which
                                include this reference.
                                        If the commenter
                                believes references to be
                                necessary, this should be
                                handled consistently in
                                REVmb, rather than
                                piecemeal in TGn
TGn comment: "if and only if" TGn Resolution:EDITOR:             Counter. Change "A STA may EDITOR
is being used here for literary 2008-07-01 09:23:30Z Reject -    enter PS mode if and only if
emphasis, not for its technical The cited text is unchanged      the value of the ATIM window
meaning. The rejection of       text quoted from the STD-        in use within the IBSS is
LB124/6239 is incorrect in its 2007 baseline.                    greater than zero." to "A STA
analysis. See my comment on Notwithstanding that the             may enter PS mode if the
11.14.3.3 (page 221 line 25)    responses to LB129               value of the ATIM window in
for further explanation..       comments on "if and only if"     use within the IBSS is greater
Proposed Change: change "if have been to change this form        than zero. A STA shall not
and only if" to "if"            in new text within TGn, it is    enter PS mode if the value of
                                better to address the issue of   the ATIM window in use within
                                this language consistently in    the IBSS is equal to zero."
                                REVmb, rather than
                                piecemeal in the current
                                amendments.
TGn comment: addition of          TGn Resolution:GEN: 2008-     Accept the proposed                   EDITOR
dot11SMTbase3 was a goof          07-16 15:19:26Z Reject -      resolution in the Comment
in 11k and should be fixed.                                     column. Delete
                                           This correction is not
Proposed Change: delete           in the scope of TGn and       dot11SMTbase3 from the
dot11SMTbase3 from the            should be forwarded to        IEEE 802.11k-2008
OPTIONAL-GROUPS (show             TGmb.                         amendment as referenced,
deletion with strikethrough)                                    when merging with IEEE
                                                                802.11-2007.
TGn comment: only a single        TGn Resolution:EDITOR:        Reject. TGn addressed this            EDITOR
ordered list is allowed per       2008-06-19 12:52:04Z Reject - comment, and no action is
subclause, see 11.3 in Style       The cited text is quoted     necessary by TGmb.
Manual. Proposed Change:          baseline text that is not
since its important that the      modified by TGn (it is quoted
middle list in this subclause     to provide context). This
be an ordered list (so the        comment will be passed on to
items can be referenced at        TGmb for their consideration.
lines 12-13 on page 128), this
third list needs to be changed
to a dash list
the variable N_{CBPS} should Replace N_{CBPS} should be Accept.                                       EDITOR
be replaced by N_{BPSC} in     replaced by N_{BPSC}
Section 17.3.2.1, bullet (i).

No Regulations and                The final sentence should be        Accept.                         EDITOR
conformance tests are listed      deleted.
in Clause 2, and Annexes I
and J point to regulatory
matters.
"— Defines mechanisms for
dynamic frequency selection
(DFS) and transmit power
control (TPC) that
may be used to satisfy
regulatory requirements for
operation in the 5 GHz band.
The regulations and
conformance tests are listed
in Clause 2."


802.11r added a normative         insert a new item to the dash       Accept.                         EDITOR
reference to FIPS PUB 180-2- list at bottom of this page,
2002, but failed to reference it. following the dash list entry for
                                  "Truncate-128", new text to
                                  read "SHA256 shall be as
                                  defined in FIPS PUB 180-2-
                                  2002"
With the addition by TGn of a Spreadsheet page "802.11-               Accept. Move all 16             EDITOR
new definition clause,            specific definitions" contains a    definitions in tab to 802.11-
containing definitions that are list of definitions to move from      specific definition clause.
specific to 802.11 and not        existing clause 3
appropriate for _The
Authoritative Dictionary of
IEEE Standards Terms_, the
existing definitions in clause 3
should be evaluated to
determine the appropriate
clause.
Subheadings x.y.z.1 should         spreadsheet page               Accept in principle. Editor       EDITOR
only appear when there is          "extraneous subheadings"       empowered to conform to
also x.y.z.2; where there is       contains a list of subheadings intent of comment.
only a .1 subheading, it should    to either (1) remove, or (2)
be removed                         insert another subheading at
                                   same level, fixing them as
                                   "hanging paragraphs"

The IEEE Style Guide               Spreadsheet page "hanging      Accept in principle. Editor       EDITOR
prohibits "hanging                 paragraphs" contain a list of  empowered to conform to
paragraphs", where a               places in the document that    intent of comment.
paragraph of text appears          need to be fixed. Insert a new
after a heading and before a       subheading "General" in front
next-level subheading. This        of each of these hanging
text is unable to be referenced    paragraphs.
by a subclause number. See
Style Guide 11.1 for examples
and potential ways to fix.

Clause 7 is intended to            Spreadsheet page "7-            Counter. Adopt proposal in     EDITOR
contain frame formats, and         normative formats" contains     submission 11-09/0433r1.
not the procedures that are        changes needed to add           Accept the changes
followed by a STA that either      normative text to clause 7      recommended in the "7-
generate or process the            where needed to define the      procedures" tab.
frame. There are two               frame formats. Spreadsheet      Add a new paragraph to
problems with the current text -   page "7-procedures" contains    clause 7 (will eventually
 (1) that it doesn't include       changes needed to remove        become clause 7.1.1) stating
normative language that            procedures that are current     the following:
mandates the frame contents,       contained in clause 7.          "A compliant STA shall
and (2) it often contains                                          transmit frames using only the
procedures that are followed                                       frame formats described in
by the STAs to                                                     Clause 7."
generate/process the frame.
where it says "If the calculated   change "factor" to "multiple"   Accept.                          EDITOR
TXOP duration requested is
not a factor of 32us", it really
means "multiple of 32us"

replace "IE" in this sentence      as in comment                   Accept in principle. Make a      EDITOR
with "information element"                                         global change of "IE" to
(twice)                                                            "information element",
                                                                   deleting the use of "IE" where
                                                                   it is being defined as an
                                                                   abreviation.
Several of the notes in Tables    delete the use of "only" in the Counter. See CID 29.           EDITOR
7-8 through 7-18 use the          Notes to Tables 7-8 through 7-
wording "<xxx> is present only    18, changing "only if" to "if"
if <yyy>". The formal meaning     throughout.
of this phrase is "If <yyy> is
false, then <xxx> shall not be
present, otherwise <xxx> may
be present." However that is
not the intention here; rather
the intent is "If <yyy> is true
then <xxx> shall be present."
The "only if" (also called the
contrapositive form) is, in
addition to not making the
statement of inclusion that is
desired, also restricting any
future use of the information
elements. Such restrictions
on the future should be
avoided in the standard.



second and third sentences of     delete second and third           Accept.                      EDITOR
this paragraph duplicate          sentences of this paragraph.
information elsewhere in the
subclause, and do not follow
the style of other frame
formats in 7.2.3
Use of the "Requested             change final sentence of first    Reject. The FH parameters    EDITOR
Information" may result in        paragraph to "Note that the       element is mentioned
many pieces of information        information returned as a         explicitly because it is a
appearing in the Probe            result of a Probe Request         special case.
Response twice, not just the      frame with a Request
FH parameters and FH              information element may
Pattern Table. There is no        include items replicating the
reason to identify them           optional elements identified in
specifically.                     Table 7-15."
since all the bits of the         delete final paragraph of         Accept.                      EDITOR
Capabilities Information field    7.3.1.4
have now been assigned,
there is no need to reserve
the unused bits
The additional fixed fields       delete this paragraph             Accept.                      EDITOR
used within Action frames are
not in the subclauses
referenced here. Also, a
range of subclauses with the
first number higher than the
second (7.3.2.12 through
7.2.1.17) makes no sense.
Possibly its a double typo, and
what was intended was
"7.3.1.12 through 7.3.1.17";
even so the paragraph should
be deleted.
Tables B.1, B.2, and B.3 do       Add a reference to these        Accept                         EDITOR
not have any references in the    tables in the text on page 769.
text.
This informative annex is no      delete annex C                     Counter. See CID 95         EDITOR
longer informative, as it is so
far out of date that it no longer
describes a reasonable
subset of MAC operation.

actually, this is only one          perhaps change first line of   Counter. We applied the       EDITOR
possible translation of that line   G.2 from "of the well-known"   "BROOM" function.
of Friederick von Schiller's An     to "of a mis-typed translation
de Freude, and it is "Fire-         of the well-known". Or just
inspired we tread" (Not "Fire-      sweep this one under the rug.
insired"). Someone did a typo.
(BTW, its "Wir betreten
feuertrunken/ Himmlische,
dein Heiligtum" in the original,
literally "We enter, drunk with
fire/Heavenly one, your
sanctuary". Its not surprising
that there are multiple
translations of this phrase.)


"The packet error rate (PER)        Clarify the sentence             Accept. See comment 72.     EDITOR
shall be less than 10% at a
PSDU length of 1000 octets
for rate-dependent input
levels shall be the numbers
listed in Table 145 or less."
Sentence makes no sense at
all
In the behavior limits set table    change to 389                    Counter. Replace "EN 301    EDITOR
I-3 we find ETSI EN 301 389-                                         389-1" with "EN 301 893"
1, but in                                                            throughout the document.
Table I.1—Regulatory
requirement list
we find ETSI EN301 893
It seems there may be a typo
893 -> 389. There is a 893
doc that does contain
emission requirements for
Europe.
There is no rules defined to        Clarify the transmission order   Reject. The text in this      EDITOR
specify the transmssion order       rules for frames which are       paragraph states that the
of the MSDUs which are              targetted to different           MAC does not reorder frames
targetted to different unicast      addresses. If there are no       for non-QoS STA's, except for
or groupcast addresses. Also        rules to specify the             "power management"
the clause 6.1.3 is difficult to    trnasmission order between       procedures.
understand                          different destinations delete
                                    the text which proposes such
                                    functionality.
normative statements about          change "is optionally present"   Counter. See CID 29.        EDITOR
presence of IEs in frames are       to "may be present"
appropriate in clause 7
The text states "The Multicast    Clarify the text.              Reject. The Supported Rate      EDITOR
Rate field specifies the data                                    IE always refers to the PHY
rate, 0.5 Mb/s units …". The                                     data rate.
text is ambiguous since data
rate can have multiple
meanings? For example, it is
the PHY rate or the MSDU
data rate. If it's MDSU data
rate, how does the STA know
the rate of the multicast
stream?

It is important to awknowledge    Please add the phrase           Counter. Add "Spectrum         EDITOR
(at least for outdoor networks)   “Spectrum Management” in        Management" to the third
that location is a key part of    the 3rd column entry for any    column for the "LCI" row.
spectrum management. I think      row in the table that clearly
that column 3 of the              has to do with location data or
measurement report table          its format.
should have a 2nd
“measurement use”
descriptions in any row who's
report has to do with location
information. (LCI etc) For
future considerations, it
makes sense to specify that
location is more than simply a
“radio resource
measurement” parameter--but
also has a role to play in
“spectrum management” as
well.


"that bits numbered (N2 + 1) × Replace "through" with "to".      Accept in principle. Globally   EDITOR
8 through 2007                                                   replace any use of "through"
in the bitmap are all 0."                                        with "to", where it expresses
                                                                 a range. Do not make any
This is an ugly American                                         changes in Annex C.
Colloquialism
since N1 is already defined to remove FLOOR function             Accept.                         EDITOR
be an even number, the
FLOOR function unnecessary
for (N1)/2
There should be a classifier      Add Classifier Type: "For         UNRESOLVABLE (EDITOR:             EDITOR
type which will allow             Classifier Type 4, the            2010-05-20 09:24:40Z) - In
classification based on the       classifier parameters are the     Table 7-42 replace the last
802.1D UP and/or 802.1Q           following parameters in an        two lines with:
VLAN ID in an 802.1Q tag          IEEE 802.1Q tag header:
header independently.             IEEE 802.1D-2004 [Bxx] User       2         IEEE 802.1Q
                                  Priority and IEEE 802.1Q-         parameters
                                  2003 [Byy] VLAN ID. The           4         IEEE 802.1D/Q
                                  Frame Classifier field for        parameters
                                  Classifier Type 4 is defined in   3, 5-255 Reserved
                                  Figure xx. The CFI bit cannot     [Note: 3 reserved for expected
                                  be used for classification.       use by 802.11v.]
                                  The subfields in the classifier
                                  parameters are represented        At the end of section 7.3.2.31
                                  and transmitted in big-endian     add:
                                  format." and add a suitable
                                  figure.                           For Classifier Type 4, the
                                                                    classifier parameters are the
                                                                    following
                                                                    parameters in an IEEE
                                                                    802.1Q-2003 [B14] tag
                                                                    header:
                                                                    Priority Code Point (PCP;
                                                                    equivalent to IEEE 802.1D-
                                                                    2004 [B12] User
                                                                    Priority), Canonical Format
                                                                    Indicator (CFI) and VLAN ID
                                                                    (VID). The
                                                                    Frame Classifier field for
                                                                    Classifier Type 4 is defined in
                                                                    Figure 7-90x.
                                                                    The subfields in the classifier
The endianness of the             Suggestion: add at 802.11-        parameters are represented
                                                                    Accept.                           EDITOR
"802.1Q Tag Type" field in        2007, 7.3.2.31 on page 137 --
Type 2 (802.1Q) TCLASes           "as in IEEE 802.1Q-2003
should be specified. In 802.11-   [Bxx]"
2007, 7.3.2.31. (page 137)
This should be added in the
TGv Draft
The endianness of the             Suggestion: add at 802.11-        Accept.                           EDITOR
"[Ethernet] Type" field in Type   2007, 7.3.2.31 on page 136
0 (Ethernet) TCLASes should       "as in "Ethernet" [Bxx]".
be specified. See 802.11-
2007, 7.3.2.31 (page 136).
This should be added in the
TGv Draft
The text for Type 2 (802.1Q)      Add editor instructions to        Accept.                           EDITOR
TCLASes implies the UP and        amend test to read "For
the VLAN ID can be matched        Classifier Type 2, the
independently, but Figure 7-      Classifier Parameter is the
90 shows otherwise.               IEEE 802.1Q-2003 [Bxx]
See also 802.11-2007,             VLAN Tag TCI". Amend
7.3.2.31 page 137                 Figure 7-90 to say "802.1Q
                                  VLAN TCI".
"The RSN Capabilities field       "The RSN Capabilities field        Counter. Change the second EDITOR
indicates requested or            indicates requested or             sentence of the first
advertised capabilities. The      advertised capabilities. The       paragraph of 7.3.2.25.3 to the
value of each of the RSN          value of each of the RSN           following:
Capabilities fields is 0 if the   Capabilities fields is 0 if that   "If the RSN Capabilities field
RSN Capabilities field is not     RSN Capabilities field is not      is not present, the default
available in the RSN              available in the RSN               value of 0 is used for all its
information element."             information element."              subfields."
IEEE 802.11 is under the          First reach agreement on           Reject.                          EDITOR
IEEE 802, which is under          each and every unwritten rule      No specific change is
IEEE-SA. IEEE-SA has an           and document it. (If the first     requested.
IEEE Standards Style Manual,      cannot be accomplished, then       While the TG understands the
which applies to all standards    for any comment that is            commentors sentiments,
produced under the IEEE-SA.       submitted with the premise         unwritten conventions or
This document defines the         that it is an unwritten rule, a    assumptions in standards
mandatory clauses that shall      long standing tradition the        development are inevitable.
be present within all IEEE-SA     comment is discredited             The process for applying
Standards. This document          without documented proof. A        these rules or assumptions is
also defines word usage (e.g.,    comment resolution /               up to the group that
shall and may) along with         disposition cannot be based        addresses the issues. The
many other items. However         under the guise of an              commentor is encouraged to
there appears to be a             unwritten rule or a long           participate in the activities of
movement within IEEE 802.11       standing tradition. In other       the TG.
by some individuals that there    words a comment cannot be
are other requirements that       dismissed simply based on an       TGmb has approved the
are neither written nor           unwritten rule.) Second            following responses to the
documented anywhere.              recognize that these agreed-       "unwritten rules" enumerated
These unwritten rules are         to unwritten rules (now            given in the "Comment" field:
causing two problems. 1)          documented) are only               A) IEEE 802.11 will keep its
Comments being made to            applicable to 802.11 drafts        MIB.
802.11 working group drafts       and standards and are not          B) IEEE 802.11 will keep a
are being dismissed due to        applicable to other working        PICS proform.
these unwritten rules. The        groups' drafts or standards        C) and D) refer to comment
comments would most likely        within 802 or under IEEE-SA        29.
not be made or reoccur with       and that individuals should        E) An informative annex
such frequency, if they were      keep this in mind when voting      should not include normative
known and if these rules were     on drafts outside of 802.11.       text. If normative text is
document for all to see. 2)       Third that any item not            included in an informative
Some individuals of 802.11        covered by the IEEE-SA IEEE        annex, it should be changed.
when they vote on non-802.11      Standards Style Manual and         F) This is an editorial matter
drafts a MIB (Annex D) is
Since are claiming these          Update 802.11 membership
                                  that the the normative             and should not be discussed
                                                                     Reject. The document is          EDITOR
required for 802.11, will the     references, which are              consistent with the current
normative references for their    currently dated as ISO/IEC         quoted references. The
creation be updated and so        8825-x 1995, and the MIB in        commentor is encouraged to
too the MIB itself based on       Annex D accordingly.               create a submission with the
these updated normative                                              changes required to address
references?                                                          this suggestion.
Figure 5-4 has never come         Replace Figure 5-4 with a          Reject. This figure is the       EDITOR
through well in the published     better representation.             original graphic.
Std. Can we get back to an
original (that I suspect was
useful), or replace this with a
new diagram that actually is
worth 1,000 words?
There appears to be              Change 6.2.1.3.1's "status       Reject. The proposed change EDITOR
confusion about what the MA-     information" and                 does not contain the specifics
UNITDATA.confirm primitive's     "corresponding preceding"        necessary to update the draft.
behavior is, or, as a result,    phrases to be clear. Change      The commentor is
when it is generated. The        6.2.1.3.3's "status of the       encouraged to create a
1999 version of 802.11 had a     service provided" to be clear.   submission with the changes
MA-UNITDATA-                                                      required to address this
STATUS.indication primitive,                                      suggestion.
which was apparently
replaced by this .confirm.
That primitive provided
information about the
successful/unsuccessful
delivery of an MSDU to the
peer entity (apparently?). The
2007 MA-UNITDATA.confirm
appears to only provide
immediate response status as
to the MAC's ability and
readiness to perform the
delivery service as described
in the Standard, without
regard to whether this will
result in actual successful
delivery to any peer MAC.
The wording is not clear in
this regard, however.


There is no concept of           Add MLME-STOP mechansim          Accept the proposed                 EDITOR
terminating a BSS once           and primitives. Detailed         resolution contained in
started. With "controller-       changes provided in separate     document 11-08/1340r0,
based" AP structures             presentation.                    excluding the following two
becoming popular, and the                                         paragraphs:
concept of multiple BSS APs                                       'The following paragraph can
being introduced in 802.11k,                                      be included if 802.11v BSS
there is a need for a                                             Transition Management with
mechanism that ends BSSs                                          Termination information is
created by MLME-START.                                            available:

                                                                  It is desirable, but not required
                                                                  that the SME notify associated
                                                                  non-AP STAs of imminent
                                                                  infrastructure BSS termination
                                                                  before issuing the MLME-
                                                                  STOP.request. This can be
                                                                  done with the BSS Transition
                                                                  Management procedure,
                                                                  using the Termination
                                                                  information.'
802.11k introduces the           Relate the "Multiple BSS set"    DISAGREE (EDITOR: 2010- EDITOR
concept of "Multiple BSSID       concept to the architectural     05-20 09:24:46Z) - Decline.
set" but does provide any        concepts in 802.11-2007          MBSSID should be further
architectural description of     Section 5, especially Sections   defined in the task groups that
how these are represented.       5.2 and 5.5.                     are currently using the
The last paragraph would                                          concept.
imply that the multiple BSSIDs
are actually multiple,
individual APs. If this is the
case, then it would imply
multiple, individual MACs and
PHYs (except for the antenna
connector), which would lead
to independent medium
access, and frame queuing,
so coordination occurs only
when actual collisions occur
at the antenna connector.
This does not seem
effieicient, nor what most
implementations do. Further,
there is no discussion of the
relationship between these
BSSes and their ESSes, nor
how DS Associations or Portal
(integration service) address
mappings are maintained
such that the system can
integrate into an 802 network
unambiguously.
The 802.11-2007 Std says,         Clarify in 9.1.3.1 or 9.9.3.1.2,   Change the 8th paragraph of EDITOR
"The management frames            whether the management             9.9.3.1.2 as follows: “The
shall be sent using the access    frames sent using AC_VO AC         MPDUExchangeTime equals
category AC_VO without            shall count toward the             the time required to transmit
being restricted by admission     used_time parameter or not.        the MPDU sequence. For the
control procedures." But, this                                       case of an MPDU transmitted
leaves it ambiguous whether                                          with Normal Ack policy and
these frames count toward the                                        without RTS/CTS protection,
used_time parameter                                                  this equals the time required
described in 9.9.3.1.2.                                              to transmit the MPDU plus the
                                                                     time required to transmit the
                                                                     expected response frame plus
                                                                     one SIFS. Frame exchange
                                                                     sequences for Management
                                                                     frames are excluded from the
                                                                     used_time update. If the
                                                                     used_time value reaches or
                                                                     exceeds the admitted_time
                                                                     value, the corresponding
                                                                     EDCAF shall no longer
                                                                     transmit using the EDCA
                                                                     parameters for that AC as
                                                                     specified in the QoS
                                                                     Parameter Set element.
                                                                     However, a non-AP STA may
                                                                     choose to temporarily replace
                                                                     the EDCA parameters for that
                                                                     EDCAF with those specified
                                                                     for an AC of lower priority, if
                                                                     no admission control is
                                                                     required for those ACs.”

Section 9.9.3.1 says, "A non-     Clarify that the use of a EDCA Comment has been              EDITOR
AP STA may support                parameters for a lower priority withdrawn.
admission control procedures      (non admission mandatory)
in 9.9.3.1.2 to send frames in    AC does not require
the AC where admission            modification of the QoS
control is mandated; but, if it   control field.
does not support that
procedure, it shall use EDCA
parameters of a lower priority
AC, as indicated in Table 9-1,
that does not require
admission control" and also "If
a STA desires to send data
without admission control
using an AC that mandates
admission control, the STA
shall use EDCA parameters
that correspond to a lower
priority and do not require
admission control." Nothing in
this section discusses the
setting of the TID(UP) field in
the QoS control when this is
done.
Section 11.2.1.1 says, "The       To clarify the meaning of        Counter. Adopt the changes   EDITOR
Power Managment bit shall         "shall not be set" change this   in document 11-09/0003r4.
not be set in any management      phrase to "is reserved, and
frame, except an Action           shall be ignored on reciept".
frame." What does "not set"
mean? Is this meant to say
"set to zero"? It's not clear
where this statement
orignated, and it would put an
undue restriction on non-AP
STAs, if it said "set to zero."
Since management frames
from the AP to non-AP STA
are explicitly buffered when
the STA is in Power Save
(Section 11.2.1.5(a)), there is
no reason to restrict an
associated non-AP STA from
doing management frame
transactions while in PS mode.


This section discusses the      Change "MSDUs" to "MSDUs           Counter. See the resolution ot EDITOR
behavior for buffering MSDUs and management frames"                comment 61
when a non-AP STA is in PS throughout 11.2.1.
mode. But, Section
11.2.1.5(a) makes it clear that
this applies to management
frames as well. It is confusing
that management frames are
not mentioned in 11.2.1.

The Standard contains             Formulate a approach to use      Reject. The proposed change EDITOR
inconsistent approaches to        of these terms and concepts      does not contain the specifics
the terms “mandatory” and         in the main body and PICS,       necessary to update the draft.
“optional”, especially when a     and then edit the Standard to    The commentor is
feature could be either or both   apply this approach              encouraged to create a
“implemented” or “enabled.”       consistently.                    submission with the changes
Further, the relationship                                          required to address this
between the main body                                              suggestion.
normative text containing
discussion of “mandatory” or
“optional”, and the PICS
entries for M/O is inconsistent
and confusing.
In the description of the           Replace "The field is coded   Accept.                        EDITOR
Power Constraint field of the       as an unsigned integer in
Power Constraint Element,           units of decibels relative to
the following sentence              1mW." with "The field is
appears: "The field is coded        coded as an unsigned integer
as an unsigned integer in           in units of decibels."
units of decibels relative to
1mW." This sentence is
different from the one that
appeared in the originally
approved 11h amendment. In
the amendment, the sentence
appeared as: "The field is
coded as an unsigned integer
in units of dB." I believe that
the original was correct and
that the attempt to remove the
abbreviations dB and dBm
from the rollup have
introduced an error. Some
other fields were correctly
translated from "dBm" to
"decibels relative to 1mW"
because those fields contain
an absolute value of signal
level. But this field is intended
to be used as a relative value
of signal - specifically, it is
used as an adjustment to a
specific absolute maximum
signal power, as indicted in
this subclause by the
The Transmit "The local
following text: Power and Link      Resolve the mismatch            Reject. The Transmit Power      EDITOR
Margin entries in the table in      between the SAP and the field   and Link Margin field
this subclause show that            that is used to carry the       descriptions in clause 7.3.2.18
these parameters are integers       information.                    are defined to be signed
with a range of -127 to 127,                                        integers.
but the field descriptions in
the frames that carry this
information indicate that the
values in the fields are
unsigned integers, suggesting
that a different range should
be specified here, or that the
the fields in the frames should
be integers.
The Text says:                     Change the sentence: "The       Accept                    EDITOR
When an IBSS STA’s SME             pair of STAs shall use the
wants to set up a security         pairwise cipher suite specified
association with a peer STA,       in Message 3 of the 4-Way
but does not know the peer’s       Handshake sent by the
policy, it must first obtain the   Authenticator STA with the
peer’s security policy using a     higher MAC address (see
Probe Request frame. The           8.5.1)." to read "If the 4-Way
SME entities of the two STAs       Handshake is succesfully
select the pairwise cipher         completed, then the pair of
suites using one of the 4-Way      STAs shall use the pairwise
Handshakes. The SMEs of            cipher suite specified in
each pair of STAs within an        Message 2 of the 4-Way
IBSS may use the EAPOL-            Handshake initiated by the
Key 4-Way Handshake to             Authenticator STA with the
select a pairwise cipher suite.    higher MAC address (see
As specified in 8.5.2,             8.5.1)."
Message 2 and Message 3 of
the 4-Way Handshake convey
an RSN information element.
The Message 2 RSN
information element includes
the selected pairwise cipher
suite, and Message 3 includes
the RSN information element
that the STA would send in a
Probe Response frame.

The pair of STAs shall use the
pairwise cipher suite specified
in Message 3 of the 4-Way
Handshake sent by the
Authenticator STA with the
Figure 5.6 uses the term        Change the term to use the        Counter. Changed to IEEE   EDITOR
"802.xLAN", but this term is    more recognized standard          802 LAN
never defined in the standard. one.
IEEE Std. 802-2001 uses the
term "IEEE 802 LANs and
MANs"
The issue might be named            I think this should be            Reject. The proposed change EDITOR
"gratuitous double-                 documented in Annex M,            does not contain the specifics
encapsulation". It involves         since the behavior is out there   necessary to update the draft.
deliberately (and incorrectly)      in the field. Whether we want     The commentor is
placing an additional               to discourage it or not is open   encouraged to create a
RFC1042 SNAP header                 to debate.                        submission with the changes
around the contents of a                                              required to address this
frame that already has such a                                         suggestion.
header (in particular, an
AppleTalk Phase II frame) to
encode the length field. The
decoding rules for the default
case of 802.1H then cause a
correct implementation to strip
the outer SNAP header and
turn it into an 802.3 length
field, leaving the interior
SNAP header alone (since the
length field in the outer SNAP
header is neither the
AppleTalk nor IPX special-
case encoding/decoding rules
value).
    There are implementations
out there that do this on
purpose, since then an
incorrect (always remove
SNAP header) and a correct
(do not remove SNAP header
if it's one of the special values
or is the BTEP header)
implementation both produce
the same 802.3 frame the the
Item (i) starts: "Divide on         Change N sub CBPS to N sub Accept.                                 EDITOR
resulting coded and                 BPSC.
interleaved data string into
groups of NCBPS bits."
(CBPS is a subscript, referring
to the number of coded bits
per symbol). I believe the
correct variable is N sub
BPSC (number of bits per
subcarrier). Clause 17.3.5.7
uses the latter.
The abbreviations FEC, AGC          Add entries to Clause 4 for       Accept. See submission in 11- EDITOR
and AFC are not includced in        FEC, AGC and AFC.                 09/0051r1.
clause 4
Three things. 1) missing            Fix these three editorial         Accept in principle. Editor is   EDITOR
period at end of "nch = 0, 1,       problems.                         directed to solve issues to
…, 200" (this is the end of a                                         match style guide.
sentence). 2) The
indendation is screwed up for
two paragraphs following that
equation. 3) There is a space
missing between "frequency"
and "is" in the first sentence
following that equation.
First sentence of 17.3.10.1      Fix grammer. Maybe it should Accept.                       EDITOR
reads "The packet error rate     read "The packet error rate
(PER) shall be less than 10%     (PER) shall be 10% or less
at a PSDU length of 1000         when the PSDU length is
octets for rate-dependent        1000 octets and the rate-
input levels shall be the        dependent input level is as
numbers listed in Table 17-13    shown in Table 17-13."
or less." I'm not sure exactly
what this should say, but the
grammer is obviously wrong
with the two occurence of
"shall be".

Third paragraph of clause        1) add "shall begin" following Accept. See submission in 11- EDITOR
17.3.11 has several problems.    "PLCP header" in the second 09/0051r1.
1) There is something missing    sentence.             2) correct
from the second sentence:        the third and fourth sentences.
"The PLCP shall then issue a
PMD_TXSTART.request, and
transmission of the PLCP
preamble and PLCP header,
based on the parameters
passed in the PHY-
TXSTART.request primitive."
Perhaps the words "shall
begin" should follow "PLCP
header"?
2) The third sentence states
that scrambling shall begin
immediately after
transmission of the preamble
is started. This contradicts
clause 17.3.2.1 point (b),
which states: "The contents of
the SIGNAL field are not
scrambled."
3) The fourth sentence says
that scrambled and encoded
data are exchanged between
the MAC and the PHY, which I
believe is not correct. I
believe that the sending PHY
scrambles and encodes, the
receiving PHY unscrambles
and unencodes, and the MAC
sublayer never sees
The last sentence of the          Reword sentence as: "If the     Accept.                             EDITOR
paragraph following Figure 17-    coded PSDU (C-PSDU)
14 reads: "If the coded PSDU      length is not a multiple of the
(C-PSDU) is not multiples of      OFDM symbol length NCBPS,
the OFDM symbol, bits shall       the PSDU is padded prior to
be stuffed to make the C-         scrambling and coding (see
PSDU length multiples of the      clause 17.3.5.3)".
OFDM symbol." This is
misleading because it implies
that bit padding is done after
coding. Clause 17.3.5.3
explains how the number of
pad bits is determined. Also,
the word "stuffed" is used
instead of "padded" and the
phrases "is not multiples of"
and "to make C-PSDU length
multiples of" are not correct
grammar.

The TX Preamble state block       Edit this block so that it is      Counter. Edit this block so      EDITOR
incorrectly says that the         correct. For example, it could     that it says: "followed by the
training symbols consist of the   say that the training symbols      SIGNAL field".
SIGNAL contents.                  are FOLLOWED BY the
                                  indicated fields (rate, etc.) It
                                  would be better to say the
                                  training symbols are followed
                                  by the SIGNAL symbol.
The paragraph following         Clarify both aspects of the first Reject. See submission in 11- EDITOR
Figure 17-16 begins: "Upon      sentence following Figure 17- 09/0051r1.
receiving the transmitted       16.
PLCP preamble,
PMD_RSSI.indicate shall
report a significant received
signal strength level to the
PLCP. This indicates activity
to the MAC via
PHY_CCA.indicate." The
words "upon receiving" are
ambiguous. Do they mean
upon receiving a complete
preamble? I don't think so
since that would require more
time than is alloted for CCA
Activity indication in Clause
17.3.10.5. How much of the
preamble should be received
before the PMD issues this
indication? This should be
clarified, either to provide a
specific portion of the
preamble or at least to avoid
implying a PMD waits until it
receives the entire preamble.
Also, the words "shall report a
significant received signal
strength level" are unclear.
What is "significant"?


DS Parameter Set element       Extend DS Parameter Set          Reject. The current text does EDITOR
support only 2.4 GHz band it's element to 5GHz band.            not prevent the DS Parameter
because DSSS is used only      (Name would be change.)          Set from being used for the 5
2.4GHz. However STA, in                                         GHz band.
5GHz band, have a difficulty
to recognize current channel
correctly because of inter
channel interference.

Table 7-8 includes many        Consider to reduce a length of   Reject. Making this proposed   EDITOR
information element and it's   beacon. for example.             change would affect the
getting long when new             - Allow to include IE's in    interoperability of current
amendments comes. Current      Probe/Association request        implementations of IEEE
standard require to include    only.                            802.11.
such IEs into both of Beacon      - Beacon include a part of
and Probe/Association          IE's and only DTIM Beacon
response. But long beacon      include whole IE's.
affect to power consumption
and band efficiency.
"The packet error rate (PER)      Clarify the sentence             Accept. See comment 72.          EDITOR
shall be less than 10% at a
PSDU length of 1000 octets
for rate-dependent input
levels shall be the numbers
listed in Table 145 or less."
Sentence makes no sense at
all
In table 11A-2, The text in the   Amend the sentence to read       Accept the first option of the   EDITOR
table states, "In a response:     as follows, "In a response: a    proposed change.
TSPEC (see 7.3.2.30),             TSPEC element (see
followed by zero or one           7.3.2.30), followed by zero or
Schedule (See 7.3.2.34)".         one Schedule elements (See
This is confusing since it        7.3.2.34), followed by zero or
implies that some IEs             more Delay elements (see
mandated by clause 11.4 are       7.3.2.32), followed by other
not required in a response.       optional elements as specified
(Submitted on behalf of Dave      in 11.4".
Stephenson)                       Note: I think the elements
                                  which are not part of the non-
                                  AP STA's request, but may be
                                  part of the AP's response are
                                  worth mentioning explicitly.
                                  For the sake of brevity, I
                                  suggested referring to clause
                                  11.4 to address other
                                  elements which may be
                                  present in the response.
                                  Alternatively, the following
                                  resolution could also be used:
                                  "In a response: a TSPEC
                                  element (see 7.3.2.30),
                                  followed by zero or one
                                  Schedule elements (See
                                  7.3.2.34), followed by zero or
                                  one Delay elements (see
                                  7.3.2.32), followed by zero or
                                  more TCLAS elements (see
                                  7.3.2.31), followed by zero or
                                  on TCLAS processing
"The IEEE 802.1X Controlled       elements (see 7.3.2.33)". If
                                  Delete both the sentences.       Accept. Delete both              EDITOR
Port returns to being blocked.    these are considered within      sentences.
As a result, all data frames      scope of 11r PAR, then either
are unauthorized before           delete the second sentence.
invocation of an MLME-            OR, change:"As a result of the
DELETEKEYS.request                802.1X Controlled port being
primitive." - this change         blocked, all data frames are
seems out-of-scope for this       unauthorized before
group, as this is not pertinent   invocation of an MLME-
to 11r. Moreover, the second      DELETEKEYS.request
sentence is ambiguous and         primitive."
even, technically incorrect.
The data frames may be valid
before invocation of the
DELETEKEYS.requst
primitive.
Not just any "STA" - this     Change "STA" to "non-AP           Reject. In this case, the use of EDITOR
should be a non-AP STA        STA" twice in first paragraph     STA is clear since it refers to
                              of 11A.1                          the process of BSS-Transition.

Not just any "STA" - this     Based on the page/line as         Reject. In this case, the use of EDITOR
should be a non-AP STA        they appeared in P802.11r-        STA is clear since it refers to
                              D8.0-redline.pdf, change          the process of BSS-Transition.
                              "STA" to "non-AP STA" on
                              (page.line) 56.64, 57.06,
                              57.10, 57.13, 57.20, 57.40,
                              57.51, 57.54, 57.55
Not just any "STA" - this     Based on the page/line as         Reject. In this case, the use of EDITOR
should be a non-AP STA        they appeared in P802.11r-        STA is clear since it refers to
                              D8.0-redline.pdf, change          the process of BSS-Transition.
                              "STA" to "non-AP STA" on
                              (page.line) 59.04, 59.35,
                              59.43, and 59.48
Not just any "STA" - this     Based on the page/line as         Reject. In this case, the use of EDITOR
should be a non-AP STA        they appeared in P802.11r-        STA is clear since it refers to
                              D8.0-redline.pdf, change          the process of BSS-Transition.
                              "STA" to "non-AP STA" on
                              (page.line) 61.06, 61.22,
                              61.64, 62.01, 62.04, 62.06,
                              62.08, 62.16, 62.58
Not just any "STA" - this     Based on the page/line as         Reject. In this case, the use of EDITOR
should be a non-AP STA        they appeared in P802.11r-        STA is clear since it refers to
                              D8.0-redline.pdf, change          the process of BSS-Transition.
                              "STA" to "non-AP STA" on
                              (page.line) 65.35, 65.55,
                              65.60, 65.63, 65.64
Not just any "STA" - this     Based on the page/line as         Reject. In this case, the use of EDITOR
should be a non-AP STA        they appeared in P802.11r-        STA is clear since it refers to
                              D8.0-redline.pdf, change          the process of BSS-Transition.
                              "STA" to "non-AP STA" on
                              (page.line) 66.37, 66.60, 66.63

Not just any "STA" - this     Change "MAC address of the Reject. In this case, the use of EDITOR
should be a non-AP STA        STA" to "MAC address of non- STA is clear since it refers to
                              AP STA"                      the process of BSS-Transition.

"Current mesage number" is a In second sentence of second Counter. See comment 91               EDITOR
duplicate definition of "RSC paragraph, change from "The
value", and is not needed    RSC field gives the current
                             message number for the GTK,
                             to allow a STA" to "Delivery of
                             the RSC field value allows a
                             STA"

The REVma MEC told the        change all of the remaining       Counter. Change all             EDITOR
editor to change every        occurrences of "RC4" to           occurences of RC4 to ARC4,
occurrence of "RC4" to        "ARC4"                            excluding entries in the PICS
"ARC4", and this was done                                       and Annex C.
throughout the draft at that
time. However, a later
submission (PeerKey
Handshake) incorporated
during the Sponsor Ballot
process added further uses of
"RC4"
"Current mesage number" is a Change from "The RSC field Accept.                              EDITOR
duplicate definition of "RSC gives the current message
value", and is not needed    number for the GTK, to allow
                             a STA" to "Delivery of the
                             RSC field value allows a STA"

The last sentence in the          Change to "...are               Counter. See CID 81        EDITOR
paragraph: "As a result, all      unauthorized after receipt of
data frames are unauthorized      the MLME Association or
before invocation of an MLME-     Reassociation confirm
DELETEKEYS.request                primitive that is not part of a
primitive" seems to be            Fast BSS Transition, MLME
missing a statement of the        Disassociation or
beginning of the interval.        Deauthentication primitive and
                                  before invocation of an MLME-
                                  DELETEKEYS.request
                                  primitive."

Section 7.3.1.17 says that the    Remove the sentence "This        Counter. Make the proposed EDITOR
Max SP Length subfield of the     subfield is also reserved when   change AND remove the
QoS Info field is reserved        all four U-APSD flags are set    phrase
when all four U-APSD flags        to 0."                           "and at least one of the four U-
are set to 0.                                                      APSD flags is set to 1" from
Section 7.1.1 says that                                            the
reserved fields and subfields                                      sentence following the
are set to 0 on transmission                                       deletion.
and ignored upon reception.
This implies the value in this
field (which should be 0) has
no meaning.
So if a non-AP STA sets all
four U-APSD flags to 0 in the
QoS Info field in the QoS
Capability IE in the
Association Request, and
then uses an ADDTS Request
to set up a delivered-enabled
TS (and also sets up a trigger-
enabled TS -- perhaps the
same TS), how many buffered
MSDUs and MMPDUs may
the AP deliver to this non-AP
STA during an SP triggered
by this non-AP STA?
Section 7.3.2.30 says that          Add to the end of the               Counter. Add the following         EDITOR
"The Minimum PHY Rate field         paragraph in question:              text in Clause 11.4.2:
is 4 octets long and contains       The Minimum PHY Rate is in          "The value of the minimum
an unsigned integer that            the AP's operational rate set,      PHY rate in a TSPEC shall
specifies the desired               for an uplink TS.                   satisfy the following
minimum PHY rate to use for         The Minimum PHY Rate is in          constraints:
this TS, in bits per second,        the non-AP STA's operational        The Minimum PHY Rate is in
that is required for transport of   rate set, for a downlink TS.        the AP's operational rate set,
the MSDUs belonging to the          The Minimum PHY Rate is in          for an uplink TS.
TS in this TSPEC. This rate         the AP's operational rate set       The Minimum PHY Rate is in
information is intended to          and non-AP STA's operational        the non-AP STA's operational
ensure that the TSPEC               rate set, for a bidirectional TS.   rate set, for a downlink TS.
parameter values resulting                                              The Minimum PHY Rate is in
from an admission control                                               the AP's operational rate set
negotiation are sufficient to                                           and non-AP STA's operational
provide the required                                                    rate set, for a bidirectional TS."
throughput for the TS. In a                                             The editor is directed to re-
typical implementation, a TS                                            word the text as necessary.
is admitted only if the defined
traffic volume can be                                                   Add a reference to clause
accommodated at the                                                     11.4.2 at the cited location.
specified rate within an
amount of WM occupancy
time that the admissions
control entity is willing to
allocate to this TS."
There is no further clarification
on the allowable values.
Annex K.2 (informative) refers
to duration (Nominal MSDU
Size, Minimum PHY Rate).
This is not well-defined if the
Annex C PHY Rate is
Minimum has not been not a          Remove Annex C and all              Counter. Insert a sentence      EDITOR
maintained for ages and it          references to it (18.1.2,           describing the date of last
does not match with the             A.4.4.1, A.4.4.2, A.4.4.3,          maintenance of Annex C.
normative behavior described        A.4.4.4, A.4.9).
elsewhere in the standard. It
is questionable whether it
would still be of any real
benefit to include the SDL
description. Since the IEEE
802.11 standard is already
very long and is getting longer
with the new amendments, it
would be useful to get rid of
unneeded areas in the
standard.
Clause 16 has not been         Remove Clause 16 and all          Reject. This clause has      EDITOR
maintained for ages and may references to it.                    already been marked as not
not match with the normative                                     being maintained.
behavior described elsewhere
in the standard. There does
not seem to be any interest in
implementing or deploying
802.11 with IR PHY. Since the
IEEE 802.11 standard is
already very long and is
getting longer with the new
amendments, it would be
useful to get rid of unneeded
areas in the standard.

Clause 14 describes               Remove Clause 14 and all       Reject. The are currently     EDITOR
techonology that is not used      references to it.              deployed devices that support
anymore. Since the IEEE                                          Clause 14 and this clause
802.11 standard is already                                       helps administrators of these
very long and is getting longer                                  systems to support their
with the new amendments, it                                      network.
would be useful to get rid of
unneeded areas in the
standard.
TKIP has reached the end of       Add following paragraph to      Accept.                     EDITOR
its designed lifetime and         the end of 6.1.2: “The use of
number of critical deficiencies   TKIP is deprecated. The TKIP
in its security has already       algorithm is unsuitable for the
been identified. Consequently,    purposes of this standard.”
TKIP cannot be considered         Replace “TKIP and CCMP”
secure and its use not should     with “CCMP” elsewhere in
be promoted in any way.           6.1.2.

8.3.2.4 recommends an             Add following informative note Counter. TKIP will be        EDITOR
additional security feature of    into 8.3.2.4.1 item b) 2) “Note deprecated by TGmb.
rekeying PTK (and GTK in          – Authenticator should
case of Authenticator) when       change the PTK or GTK
Michael MIC failure is            whenever a Michael MIC
detected. The way this is         failure is detected or reported.”
written in 8.3.2.4 can be read
to include even the case of
the first Michael MIC failure
(i.e., not TKIP
countermeasures that are
started after two failures
within 60 seconds). 8.3.2.4.1
does not include such
recommendation and may
result in implementations that
do not rekey PTK/GTK in case
of active attacks against TKIP
(e.g., chopchop decryption
with 60 second wait per octet
to avoid hitting TKIP
countermeasures). It would be
better to recommend rekeying
of PTK/GTK in 8.3.2.4.1, too.
“The minimum length of the         Replace “The minimum length Reject. The information and      EDITOR
information element is 8           of the information element is 8 the statement are correct.
octets.” can be a bit confusing    octets.” with “The minimum
in the same paragraph that         length of the information
talks about IE fields, one of      element, including the
which is “Length”. The total       Element ID and Length fields,
length (including Element ID       is 8 octets.”
and Length) has indeed
minimum length of 8 octets,
but the minimum Length field
value is 6.

11.2.1 describes power             Make sure that 11.2.1 (and in   Counter. See the resolution ot EDITOR
management buffering for           general, the whole standard)    comment 61
MSDUs, but not for MMPDUs.         describes PS buffering to
This could mean that only          include Action frames and
Data frames are buffered and       Deauthentication and
all Control and Management         Disassociation frames for
frames to a STA that is in PS      associated STAs.
mode are sent immediately
which would result in the
receiving STA not seeing
them. This would break
multiple current and future
functions in 802.11 (e.g.,
measurement requests in
802.11k and ping procedure
in 802.11w). It looks like
power save buffering should
also apply to add at least
some Management frames (at
least Action frames and
Deauthentication/Disassociatio
n to associated STAs). Some
other areas of 802.11 seem to
describe PS buffering also for
MMPDUs (e.g., 7.1.3.1.7), but
the standard does not seem
to be very clear on which
frame types/subtypes are to
be buffered.


“all management traffic is         Add normative requirement       Counter. See submission in   EDITOR
returned with the same type        for a receiver of a             11-09/0051r1.
preamble as received” seems        management frame to use the
to suggest that there would be     same type preamble that was
a “shall” requirement              received in the request into a
somewhere in the standard          suitable clause or remove this
for a receiver to use the same     comment from 18.2.2.2 if it is
type preamble for                  referring to a behavior that is
“management traffic”               not actually mandated
(whatever that is referring to).   anywhere in the standard.
However, I could not find such
requirement anywhere.
TGn comment: The                  TGn Resolution:EDITOR:           UNRESOLVABLE (EDITOR:      EDITOR
procedures for calculation of     2008-08-11 05:42:22Z Reject - 2010-05-20 09:24:52Z) - See
the Duration/ID field do not                      There is no rule comment 16.
belong in clause 7. The           in the style guide that requires
reasoning behind the rejection    Clause 7 not to have
of CID 7118, that the base        normative text. While a
standard is wrong and TGn         separation of structure versus
should do nothing to fix it, is   behavior is beneficial, the
not an adequate technical         TGn draft is an amendment to
resolution to the technical       an existing baseline. The
comment.. Proposed                description of how to calculate
Change: Adopt the changes         the contents of this field is
proposed in CID 7118              present in the baseline in
                                  clause 7. The TGn
                                  amendment is merely
                                  reworking and extending
                                  existing clause 7 material to
                                  cover the mechanisms
                                  introduced by TGn.
                                    Attempted piecemeal
                                  reorganization of the baseline
                                  through its amendments is not
                                  beneficial.
                                          The correct place to
                                  change where this description
                                  should be put is in REVmb,
                                  where all such text relating to
                                  calculations can be
                                  addressed consistently.
                                                       (The
                                  above is the same resolution
                                  as CID 7118, which is
Annex J needs to be cleaned       deemed to be an adequate
                                  Counter. See 11-09/0050r1.                                  EDITOR
up.
Operating temperature should       Remove all references to        AGREE IN PRINCIPLE (GEN: EDITOR
not be a part of this PHY/MAC      operating temperature in the    2009-11-18
standard. It belongs in a          standard, deleting subclauses   21:47:06Z)Operating
product specification but not a    14.6.16, 15.4.6.10, 16.3.2.4,   temperatures should not be
PHY/MAC function standard.         17.3.8.8, 18.4.6.14, and        part of the normative clauses
This is a specification that is    applicable places in Annex A.   defining the PHYs. Delete
implementation specific and                                        cited subclauses.
should be left between the                                         Change 17.3.8.0a (General)
device manufacturer and                                            from:
implementors. This comment                                            "General specifications for
is also applicable to all places                                   the BPSK OFDM, QPSK
in the standard that apply,                                        OFDM, 16-QAM OFDM, and
such as 15.4.6.10, 16.3.2.4,                                       64-QAM OFDM PMD
17.3.8.8, 18.4.6.14, and                                              sublayers are provided in
Annex A.                                                           17.3.8.1 (Outline description)
                                                                   to 17.3.8.8 (Transmit and
                                                                   receive operating
                                                                      temperature range). These
                                                                   specifications apply to both
                                                                   the receive and transmit
                                                                   functions and general
                                                                      operation of the OFDM
                                                                   PHY."
                                                                   to
                                                                       "General specifications for
                                                                   the BPSK OFDM, QPSK
                                                                   OFDM, 16-QAM OFDM, and
                                                                   64-QAM OFDM PMD
                                                                       sublayers are provided in
                                                                   17.3.8.1 (Outline description)
                                                                   to 17.3.8.7 (Transmit and
                                                                   receive antenna port
Clause 9.3.2.2 (page 382)          Resolve this conflict. My       impedance ). These
                                                                   DISAGREE (MAC: 2009-10-         EDITOR
says "The PC shall transmit a      suggestion is to change         23 15:47:14Z). In the
CF-End or CF-End+ACK               clause 9.3.2.2 to check         overlapping BSS case, it is
frame at the end of each CFP.      BSSID in CF-End frames and      necessary for all STAs to
A STA that receives either of      leave 9.3.3.1 and 9.9.2.2a      update the NAV so that the
these frames, from any BSS,        unchanged.                      CFP is ended on the wireless
shall reset its NAV".                                              medium. Change cited
Clause 9.3.3.1 says "All STAs                                      sentence in 9.3.3.1 to a
of the BSS receiving a CF-                                         NOTE-- and rewrite to read:
End or CF-End+ACK shall                                            "All STAs receiving a CF-End
reset their NAVs so they may                                       or CF-End+ACK reset their
attempt to transmit during the                                     NAVs according to the
CP.".                                                              procedures described in
Clause 9.9.2.2a says "A non-                                       9.3.2.2 so they may attempt to
AP STA that receives a CF-                                         transmit during the CP." See
End frame containing the                                           also CID 1665.
BSSID of the BSS, in which
the non-AP STA is
associated, shall reset the
NAV value to 0."
These seem to be in conflict
as to whether the BSSID
should be checked for CF-
End frames.
Remove this clause, as it is                                         AGREE IN PRINCIPLE (GEN: EDITOR
not used and is an                                                   2009-09-24 00:11:25Z) Agree
unnecessary burden on the                                            in Principle -- Mark the IR
maintenance of the standard.                                         PHY as obsolete and subject
                                                                     to removal in a future revision:
                                                                     instruct the editor to insert the
                                                                     following line at the beginning
                                                                     of clause 16:"This clause is
                                                                     obsolete and is subject to
                                                                     removal from a future
                                                                     revision."

"If the backoff procedure is      Change bullet list on lines 1 to   AGREE IN PRINCIPLE             EDITOR
invoked for reason a) above, 11 to a alphabetically                  (EDITOR: 2009-07-02
the value of CW[AC] shall be numbered list.                          15:43:28Z) - See resolution to
left unchanged. If the backoff                                       CID 1651, which addresses
procedure is invoked because                                         this issue.
of reason b) above, the value
of CW[AC] shall be reset to
CWmin[AC]." But the above
list is a "-" bullet list, when I
think it should be a numbered
list ("a .. d").

Sub-clause title is "General("    Change to "General"                AGREE (EDITOR: 2009-07-      EDITOR
                                                                     03 13:13:18Z)

There are multiple issues with    Review the MB draft wrt to the     AGREE (GEN: 2009-09-22          EDITOR
the usage of MIB variables        11-09-533 and revise as            22:00:17Z) Editor is instructed
within the standard.              necessary to bring the             to make the changes as
Significant discussion of these   document into accord with the      recorded in 11-09/910r6 and
topics has occurred in the        recommendations.                   11-09/1196r0.
ARC SC and elsewhere. This
has resulted in a
recommendation for MOB
variable usage (ref doc 11-09-
533 R1). The MB draft should
be reviewed wrt to this
recommendation and brought
into compliance. While this
will not resolve all mib
variable usage issues, it will
significantly improve the
quality of the document. While
the reviewer acknowledges
that the referenced
recommendation has not
been formally adopted by the
WG, there has been near
universal consensus that this
would improve a significant
issue within the document and
the WG Chair has
encouraged members to
support the recommendation.
Over the years a concept has      Review the MB draft and          AGREE (EDITOR: 2009-12-    EDITOR
somehow crept into the .11        rework all places where the      01 02:52:37Z) - Changes
standard which I believe to be    concept of "non-AP STA" is       given in 11-09/1068r0
significantly incorrect. Within   used in the language and
the .11 document all ends of a    remove the meaningless
.11 link are stations (Noted as   phrase. Determine if the
STA in the document). In the      content of the afflicted section
case of an infrastructure ESS,    is correct and rewrite as
some stations also provide        necessary. I suggest that
DSS; these STAs are               searching for "non-AP" may
commonly known as Access          be the best starting point as
Points ("APs"). All APs are       the language used often is
also Stations - by definition     structured as <phrase about
APs are functionally a            stations><"non-AP"><rest of
superset of the STA               phrase>.
functionality. Yet the phrase
"non-AP STA" has been
introduced and appears in
multiple places in the
document. I suspect that most
(if not all) places where this
phrasing is used indicate a
place where the original
author)s) of the text have
included a misunderstanding
of the 802.11 architecture.
The phrase is semantically
meaningless as a "non-AP
STA" is a "STA".


This phy (FH) is no longer        Deprecate the section and      AGREE IN PRINCIPLE (GEN: EDITOR
commercially viable and the       adjust any other sections of   2009-09-22 07:30:18Z) Agree
contents of this section are      the document that are          in Principle -- Mark the FH
not worth maintaining going       impacted by this action.       PHY as deprecated and
forward.                                                         subject to removal in a future
                                                                 revision Editor to add
                                                                 immediately following the
                                                                 clause heading the following
                                                                 new paragraph: This clause is
                                                                 obsolete and is subject to
                                                                 removal in a future revision.

This phy (DSSS) is no longer      Deprecate the section and       DISAGREE (GEN: 2009-09-     EDITOR
commercially viable and the       adjust any other sections of   22 07:35:54Z) Products are
contents of this section are      the document that are          still being produced and
not worth maintaining going       impacted by this action.       developed using this PHY.
forward.
LCI field in 802.11-2007 is     as suggested.   DISAGREE                     EDITOR
based on IETF RFC3825. The                      (ARCHITECTURE: 2009-07-
representation and encoding                     15 03:44:11Z) No explanation
of fields in the RFC was                        of why the current RFC3825
subject to long debate in                       method is broken was
IETF, with the outcome that                     provided. Any consideration
the RFC is broken, the                          of an updated RFC from IETF
representation and encoding                     would have to be considered
of location information is                      after it is done.
wrong. Specifically, the
Longitude, Latitude and
Altitude Resolution field
definitions are ambigous.
Therefore, the LCI definition
has to be revised. There is a
new proposal in IETF which is
backward compatible with the
length of the fields but
changes their meaning. What
are currently known as
Resolution fields for the
coordinates will be replaced
by uncertainty and the
meaning adjusted
correspondingly. As a
consequence, the Latitude
Requested Resolution,
Longitude Requested
Resolution and Altitude
Requested Resolution field
will need to be removed from
figure 7-62i. Fixing LCI
requires format has tospec in As suggested.
The LCI changes the be                          DISAGREE                     EDITOR
changed. See my previous                        (ARCHITECTURE: 2009-07-
comment on 7.3.2.21.9. It is                    15 03:49:59Z) No explanation
not clear which TG is in                        of why the current RFC3825
charge to fix LCI in the 802.11                 method is broken was
spec, but someone has to fix                    provided. Any consideration
it. A new version of 802.11                     of an updated RFC from IETF
should not be published with                    would have to be considered
this broken LCI format. Fixing                  after it is done.
it in TGv would be another
option, but their PAR does not
include anything on that. If
TGmb does not want to fix the
LCI, then clear guidance
should be requested from the
plenary on which TG is in
charge of doing it. And the
new version of the spec
should not be published until
that TG fixes the LCI format
and all other issues which
come along with it.
same as comment for            as suggested.      DISAGREE                     EDITOR
7.3.2.22.9                                        (ARCHITECTURE: 2009-07-
                                                  15 03:52:30Z) No explanation
                                                  of why the current RFC3825
                                                  method is broken was
                                                  provided. Any consideration
                                                  of an updated RFC from IETF
                                                  would have to be considered
                                                  after it is done.

                                                  Note: commenter is referring
                                                  to CID 1010.

The NOTE has text copied       delete the NOTE.   DISAGREE (SECURITY:               EDITOR
from RFC3825, an                                  2009-07-15 04:19:22Z)
interpretation of the fields                      The comment does not
which causes the problem.                         indicate a problem that needs
                                                  to be fixed as far as this group
                                                  is concerned. The text
                                                  doesn't seem to be copied
                                                  from RFC 3825.
 If LCI format is changed, its  as suggested.     DISAGREE                          EDITOR
name has to be changed as                         (ARCHITECTURE: 2009-07-
well. Currently LCI stands for                    15 04:01:42Z) There seem to
Location Configuration                            be two interpretations of the
Information, but only includes                    comment: 1) The LCI element
binary encoding of                                in 802.11 does not match
geolocation. TGv defined a                        exactly the RFC's LCI, so
'Civic Location Report', for                      rename it. Disagree as this is
Civic Location. Therefore                         a lot of work (there are a lot of
there are currently in 802.11                     MIB attributes with this name
(and all across the industry)                     in them) and of marginal
two location formats available:                   value; 2) The LCI element
geo and civic. The new name                       may be changed if/when the
of LCI should reflect its                         IETF makes a new RFC (per
geolocation nature, eg GLI                        CID 1009), and the LCI name
(GeoLocation Information).                        should change. Disagree as
                                                  we are not making any
                                                  changes to the LCI until/if the
                                                  IETF is done with their update.
The Frame Classifier Type 1      Change "TCP/UDP IP            AGREE IN PRINCIPLE               EDITOR
lists "TCP/UDP IP". there are    parameters" to "transport     (ARCHITECTURE: 2009-07-
transport protocols other than   protocol parameters" or       19 02:28:38Z) A change
TCP and UDP, eg SCTP and         "TCP/UDP/SCTP/DCCP            supporting classifiers for non
DCCP. Those should be            parameters"                   TCP and non UDP protocols
supported as well. The                                         is present in P802.11v-D6.0.
abbreviation "IP" doesn't have                                 Accept in principle, but make
to be there.                                                   no text change because the
                                                               change will be made when
                                                               802.11v is incorporated.




The text says: "In a TCP or      Change "In a TCP or UDP    AGREE IN PRINCIPLE                  EDITOR
UDP header: Source Address,      header: Source Address,    (ARCHITECTURE: 2009-07-
Destination Address, Source      Destination Address, Source19 02:30:11Z) A change
Port, Destination Port, and      Port, Destination Port, andadding classifier type 4 for
Version"                         Version"                   other protocols is present in
                                                            P802.11v-D6.0. Accept in
There are other transport    to "In a TCP, UDP, SCTP or     principle, but make no text
protocols, like SCTP or      DCCP header: Source            change because the change
DCCP, which should be listed Address, Destination Address, will be made when 802.11v is
also.                        Source Port, Destination Port, incorporated.
                             and
                             Version"

                                 or "In a transport protocol
                                 header: Source Address,
                                 Destination Address, Source
                                 Port, Destination Port, and
                                 Version"


[B15] IEEE Std 802.10 is not     Remove this reference.        AGREE (EDITOR: 2009-08-          EDITOR
referred to anywhere in                                        07 09:00:27Z)
D_1.0. It is a _withdrawn_
standard.
[B4] is not referred to          Remove this reference.        DISAGREE (EDITOR: 2009-          EDITOR
anywhere in D_1.0. Also not                                    08-07 10:24:22Z) -
referred to anywhere in                                        Please see CID 1049 for a
802.11-2007.                                                   change that cites this
                                                               reference.
[B7] is not referred to          Remove this reference.        AGREE (EDITOR: 2009-08-          EDITOR
anywhere in D_1.0. Also not                                    07 08:55:39Z)
referred to anywhere in
802.11-2007.
[B9] is not referred to       Remove this reference.   AGREE (EDITOR: 2009-08-           EDITOR
anywhere in D_1.0. Also not                            07 08:54:48Z)
referred to anywhere in
802.11-2007.
[B12] is not referred to      Remove this reference.   AGREE (EDITOR: 2009-08-           EDITOR
anywhere in D_1.0                                      07 08:59:31Z)

[B18] is not referred to      Remove this reference.   AGREE (EDITOR: 2009-08-           EDITOR
anywhere in D_1.0                                      07 09:00:51Z)

[B27] is not referred to      Remove this reference.   AGREE (EDITOR: 2009-08-           EDITOR
anywhere in D_1.0                                      07 08:57:27Z)

[B28] is not referred to      Remove this reference.   AGREE IN PRINCIPLE                EDITOR
anywhere in D_1.0                                      (EDITOR: 2009-08-07
                                                       09:08:27Z)
                                                       Insert "(following the model
                                                       described in ITU-T
                                                       Recommendation X.210
                                                       [B28])" in 10.3.0a after "in an
                                                       abstract way".
[B29] is not referred to      Remove this reference.   AGREE (EDITOR: 2009-08-           EDITOR
anywhere in D_1.0                                      07 09:13:20Z)

[B31] is not referred to      Remove this reference.   AGREE IN PRINCIPLE           EDITOR
anywhere in D_1.0                                      (EDITOR: 2009-08-07
                                                       09:05:38Z)
                                                       Replace the reference in N.2
                                                       to "Schneier [B32]" with
                                                       "Rumbaugh [B31]".
                                                       Remove Bib entry B32.
[B33] is not referred to      Remove this reference.   AGREE IN PRINCIPLE           EDITOR
anywhere in D_1.0                                      (EDITOR: 2009-08-07
                                                       09:15:14Z) - Remove Heading
                                                       0A.2 and its 3 entries.

[B34] is not referred to      Remove this reference.   AGREE IN PRINCIPLE                EDITOR
anywhere in D_1.0                                      (EDITOR: 2009-08-07
                                                       09:17:19Z) - Please see
                                                       resolution of CID 1026
[B35] is not referred to      Remove this reference.   AGREE IN PRINCIPLE                EDITOR
anywhere in D_1.0                                      (EDITOR: 2009-08-07
                                                       09:18:17Z) - Please see
                                                       resolution of CID 1026
[B36] is not referred to      Remove this reference.   AGREE IN PRINCIPLE                EDITOR
anywhere in D_1.0                                      (EDITOR: 2009-08-07
                                                       09:17:57Z) - Please see
                                                       resolution of CID 1026
footnote 39 (ANSI                 add: ANSI and other            AGREE IN PRINCIPLE              EDITOR
Publications) mentions their      standards publications are     (EDITOR: 2009-07-23
web site, http://www.ansi.org/.   also available from the ANSI   12:10:58Z) -
Suggest that the ANSI             eStandards Store               Add " and
eStandards Store also be          (http://webstore.ansi.org/)    http://webstore.ansi.org/"
included in the footnote.                                        before the closing
                                                                 parenthesis.

                                                            To the commenter, whether
                                                            other standards are available
                                                            or not is not relevant in this
                                                            footnote. The proposed
                                                            wording could be read as a n
                                                            advertisement, so the
                                                            minimal addition described
                                                            above is to be preferred.
add footnote applicable to the Add new footnote to the      DISAGREE (GEN: 2009-09-              EDITOR
Bibliography annex in general, Bibliography Annex:          22 07:45:12Z) Proposed
that the ANSI eStandards       Standards from more than     Resolution: Decline. There
Store has other standards      100 standards publishers are are numerous secondary
from more than 100 standards available from the ANSI        sources for obtaining copies
publishers available for       (American National Standards of approved standards, and
purchase. The site enables     Institute) eStandards Store. there is no obligation to list all
purchase in US dollars of non- Single copies and site       of those places. The primary
US standards. This may be a licenses are available.         sources are listed in the
convenient way for many        (http://webstore.ansi.org/)  appropriate footnotes.
purchasers to obtain
standards of other publishers.
There probably are other
standards publishers in other
countries that have similar e-
stores and provide a similar
convenience with regard to
purchase in the local
currency. If any are known,
they could be added as well.

Reference should be cited at      In the comment                 AGREE (EDITOR: 2009-07-         EDITOR
the end of the sentence to                                       02 11:05:41Z)
read "…RSN information
element described in 7.3.2.25
(RSN information element)."

As there are now more than     In the comment                    AGREE (SECURITY: 2009-08- EDITOR
one key management protcol,                                      21 15:55:06Z)
this line number should be                                       Change
more explicit to this and                                        "using the protocol defined by
perhaps define which ones                                        8.5 (Keys and key
are used based on the                                            distribution)"
selected AKM. One possible                                       to
fix ione of the protocols as                                     "using the protocol defined by
defined by 8.5 (Keys and key                                     8.5 (Keys and key distribution)
distribution) or 11A (Fast BSS                                   or 11A (Fast BSS Transition)."
Transition).".

"shared authentication"           In the comment                 AGREE (SECURITY: 2009-07- EDITOR
should be "Shared Key                                            14 21:40:10Z)
authentiation" as defined by
8.2.2.3.
A PTKSA should have the           In the comment   DISAGREE (SECURITY:               EDITOR
identities of its full lineage,                    2009-09-22 00:22:32Z)
including the PMKR0Name.                           The PMKR0Name is already
Inlcude as a subitem                               bound into the list as it is used
"PMKR0Name" in the FT key                          to derive the PTKName.
hierarchy list.




The GTK is also distributed  In the comment        AGREE (SECURITY: 2009-07- EDITOR
during the FT protocol. The                        14 21:46:11Z)
sentence should be updated
to read "….4-Way
Handshake, FT 4-Way
Handshake, FT Protocol, FT
Resource Request Protocol or
the Group Key Handshake…."

A PTKSA should also be        In the comment       DISAGREE (SECURITY:             EDITOR
bound to the associated                            2009-07-14 21:46:22Z)
pairwise cipher suite. A new                       The text is already included.
item under the PTKSA should
be added to include "Pairwise
cipher suite selector"

As TGmb is merging 802.11r In the comment          AGREE (SECURITY: 2009-07- EDITOR
into the base, this section                        14 21:46:50Z)
seems to either focus on non-
FT enabled STAs or this
section must be updated to
state that the key
management invoked will
depend on whether it is a
"simple" RSN or an FT. One
possible update to remedy
this is to change this sentence
to read "STA uses one of the
key confirmation handshakes,
e.g. the 4-Way Handshake or
FT 4-Way Handshake, to
complete...."
This first sentence is true only In the comment   AGREE IN PRINCIPLE              EDITOR
for the non-FT case. Perhaps                      (SECURITY: 2009-07-14
the simplest update is to state                   21:46:57Z)
"When FT is not enabled, the                      Adopt the second change in
case of (re)association                           the comment:
followed…." or in line 56,                        Change the sentence to
(since the rest of the items                      "When FT is not enabled, a
seems to also suggest non-                        STA roaming within an ESS
FT) change the sentence to                        establishes a new PMKSA by
"When FT is not enabled, a                        one of the three schemes:"
STA roaming within an ESS
establishes a new PMKSA by
one of the three schemes:". A
last alternative is to rename
all of clause 8.4.1.2.1 to be
non-FT Security association in
an ESS.

This section while parts can    In the comment    AGREE IN PRINCIPLE              EDITOR
apply to an FT enabled link, is                   (SECURITY: 2009-07-14
more relevant for when the                        21:48:43Z)
link is not FT enabled.                           Change:"When establishing
Suggest this be renamed to                        an RSNA,"
"non-FT enabled RSNA                              to
authentication in an ESS",                        "When establishing an RSNA
otherwise, we'll have to                          in a non-FT environment or
sprinkle clarifications                           during an FT initial mobility
throughout this clause and                        domain association,"
sub-clauses for when FT
kicks in. For instance, line 38
"Open System Authentication"
is only usedwhen either the 4-
Way Handshake or FT 4-Way
Handshake are used and not
during the FT Protocol or FT
Resource Request PRotocol.


As this is part of 8.4.6, my     In the comment   AGREE IN PRINCIPLE            EDITOR
previous comment is                               (SECURITY: 2009-07-14
highlighted by the relevance                      21:49:33Z)
of this clause mainly applying                    Change: "A STA" to "In a non-
to the non-FT case. Suggest                       FT environment, A STA".
this be renamed if the whole
of 8.4.6 is not…to ensure that
this section only applies to
AKMs 1 and 2.
Again, this section only         In the comment   SECURITY: 2009-08-14          EDITOR
applies to the non-FT (e.g.                       15:27:28Z - AGREE IN
AKMs 1 and 2 only) and                            PRINCIPLE
should be state as such. Or                       Change "The AS transfers…"
the clause could be adapted                       to "In an non-FT environment,
to referent 11A for the FT                        the AS transfers…" in the
case as well.                                     second sentence of the first
                                                  paragraph.
It is also possible to also                      DISAGREE (SECURITY:           EDITOR
invoke the FT Protocol.                          2009-08-14 15:30:50Z)
                                                 FT does not apply to an IBSS.

In looking at the flow of the   In the comment   DISAGREE (SECURITY:            EDITOR
document, it appears that we                     2009-09-22 05:47:36Z)
sometimes refer to the very                      The FT 4-way handshake is
first FT association as either                   defined in 11A.4.2 on page
the FT 4-Way handshake or                        670, line 27, and it makes a
initial mobility domain                          reference to clause 8.5.3.
association. There is no
formal description of the
former that the latter is in
11A.4 which actually fully
desribes the full association
procedures. One possible
way to make this consistant is
to allow 11A.4 to remain and
to relabel 8.5.3 as "4-Way
Handshake and FT 4-Way
Handshake". Also with this
update an update to the
General section should
highlight that the message
flows are indeed the same,
with the only distinction being
the selection of AKM values 3
or 4 for the FT 4-Way
Handshake.

Given that state machine        In the comment   DISAGREE (SECURITY:             EDITOR
descriptions are already                         2009-08-14 15:32:54Z)
provided both in visual and                      The pseudo-code is the most
long prose formats, there                        formal description we have of
seems to be little value gained                  the logic.
by providing this pseudo-code                    Provided it is up to date with
other than adding bloat to the                   the description, there is value
document and another                             in having it present.
tedious section that may not                     Non-native speakers find it
be consistant with the state                     much easier to understand
machine. Please consider                         pseudo-code
removing this whole clause.                      and diagrams than 50-word
                                                 paragraphs full of conditional
                                                 phrases and subordinate
                                                 phrases
                                                 and member-invented jargon
                                                 and conventions.
During the development of the       Consider providing a list of   DISAGREE (GEN: 2009-09-         EDITOR
802.11 standard and its             essential submissions on the   22 22:17:25Z)Disagree : Nice
amendments, there have              results, rationales and        idea, but impractical. All the
been numerous technical             background of the current      submissions and Minutes that
results submitted by                802.11 protocols, perhaps to   are used for creating the draft
participants to illustrate and to   be added in the appendix.      are available -- "see
support the protocol that is                                       mentor.ieee.org/802.11/docum
finally in the current text. For                                   ents" Also the Task group is
example, there must have                                           not making any statements of
been numerous simulation                                           Essentiality of any of the IP.
results on the PHY and MAC                                         Also the submissions are not
performance. But these                                             the final version of what is in
submissions are never (if not                                      the standard, so the historical
rarely) mentioned in the final                                     view is left as an exercise for
specification. Granted,                                            the student.
participants originally involved
with them have knowledge of
the protocols' origins, but in
general, readers are not
aware of their reasons and
sources, especially new
implementers. They will have
to rely on an exhaustive and
tedious search on our
document database or
anedoctal references if they
wish to learn of the rationale
of our the 802.11 protocols,
say if they wish to provide
further research on them.
Thus, I propose it may be
beneficial to future generation
of implementers and
These footnotes should be on        Pls fix, if deemed to be an    DISAGREE (EDITOR: 2009-          EDITOR
the previous page. The same         error.                         07-03 10:32:46Z)
for footnote 34 in the following                                   The footnotes are positioned
page.                                                              automatically, and the
                                                                   REVmb editor has no control
                                                                   of the positioning. In this
                                                                   case, however, the
                                                                   positioning is correct.

                                                                   The commenter will note that
                                                                   if the footnote 32 was to be
                                                                   moved backwards, there
                                                                   would no longer be room on
                                                                   this page for the reference to
                                                                   it. So then we would have
                                                                   the footnote on the page
                                                                   preceding the reference.
                                                                   This is even less logical.
Third sentence "mechanisms" per comment                            AGREE (EDITOR: 2009-07-          EDITOR
should be "mechanism"                                              02 15:08:35Z)

"please see the references."        per comment                    AGREE IN PRINCIPLE               EDITOR
should read "please see the                                        (EDITOR: 2009-08-06
references in [B4]."                                               13:33:16Z) -
                                                                   Replace cited text with:
                                                                   "please see the reference
                                                                   [B4]".
The equations and references per comment                           AGREE IN PRINCIPLE           EDITOR
should be renumbered to 9-2,                                       (EDITOR: 2009-07-02
9-3 and 9-4.                                                       15:32:07Z)
                                                                   Add contiguous (9-<number>)
                                                                   labels to all equations in
                                                                   Clause 9, add references so
                                                                   that each is referenced, and
                                                                   reword where statements as
                                                                   necessary in 9.8.2a.

The HCC and EHCC                  Remove Reference [B4] and        AGREE IN PRINCIPLE (GEN: EDITOR
frequency hop method              all mention of HCC and           2009-11-18 02:16:54Z) Insert
specified here and 7.3.2.10 is    EHCC, including 7.3.2.10 ,       at cited locations: "The use of
obsolete, and is not in current   9.6a, 9.8.2, and Annex A.4.10    mechanisms described in this
products that claim 802.11        MD7                              subclause is obsolete, and
conformance. I do not know of                                      this subclause may be
any products introduced since                                      removed in a later revision of
2004 that claim to use HCC or                                      the standard."
EHCC.
The High Rate Channel Agility     Remove all mention of            AGREE IN PRINCIPLE (GEN: EDITOR
option specified here is          Channel Agility, including the   2009-11-18 02:09:27Z) - Mark
obsolete, and is not in current   CA bit in 7.3.1.4, in clause     Annex F as obsolete and
products that claim 802.11        18, the PICs and remove          subject to removal in a future
conformance. I do not know of     Annex F (which has no            revision.
any products introduced since     redeeming value).
2004 that claim to support the
Channel Agility option of the
High Rate PHY.

The PBCC option specified         Remove all mention of PBCC,      AGREE IN PRINCIPLE (GEN: EDITOR
here is obsolete, and is not in   including the PBCC bit in        2009-11-18 02:07:02Z) Insert
current products that claim       7.3.1.4, in clauses 9.6, 9.6a,   in 7.3.1.4 (P107.12), 18
802.11 conformance. I do not      18, 19, the PICs and remove      (P885.34), Annex A (P998.35
know of any products              Annex F (which has no            PC17 under "Protocol
introduced since 2004 that        redeeming value).                Capability"):
claim to support the PBCC                                          "The use of the PBCC option
option of the High Rate PHY,                                       is obsolete, and this option
nor the ERP PHY.                                                   may be removed in a later
                                                                   revision of the standard."


The frequency plan specified      Deprecate this table and add     AGREE IN PRINCIPLE (GEN: EDITOR
here is obsolete, and is not      Regulatory Classes for China     2009-11-16 13:01:46Z) -
used in current products that     in Annexes I and J. Add a        Accept in Principle based on
claim 802.11 conformance.         requirement to support J.1       discussion and editorial
Amendment 1, 11k, added 2.4       class 12, J.2 class 4, J.3       instructions in 09/1111r2:
GHz band Regulatory Classes       classes 30 and 31, and the       1054, 1055, 1059, 1205 and
for US, ETSI and Japan. This      China 2.4 GHz class.             1216 see
clause should be like                                              (https://mentor.ieee.org/802.11
17.3.8.3.3, "The set of valid                                      /dcn/09/11-09-1111-02-000m-
operating channel numbers by                                       lb149-proposed-regulatory-
regulatory domain is defined                                       comment-resolutions.doc)
in Annex J."
The frequency plan specified    Deprecate this table and add   AGREE IN PRINCIPLE (GEN: EDITOR
here is obsolete, and is not    Regulatory Classes for China   2009-11-16 12:48:56Z) -
used in current products that   in Annexes I and J. Add a      Accept in Principle based on
claim 802.11 conformance.       requirement to support J.1     discussion and editorial
Amendment 1, 11k, added 2.4     class 12, J.2 class 4, J.3     instructions in 09/1111r2
GHz band Regulatory Classes     classes 30 and 31, and the     (https://mentor.ieee.org/802.11
for US, ETSI and Japan. This    China 2.4 GHz class.           /dcn/09/11-09-1111-02-000m-
clause should be like                                          lb149-proposed-regulatory-
17.3.8.3.3, "The set of valid                                  comment-resolutions.doc)
operating channel numbers by
regulatory domain is defined
in Annex J."

The PICS is for comparison       Remove the PICS proforma or   DISAGREE (GEN: 2009-09-     EDITOR
shopping, and does not           make it informative.          24 00:40:53Z) Disagree: As
belong in the standard. There                                  part of the 802.11 Revision
are no PICS in 802.16 or                                       PAR request and approval, a
802.15.4 standards. 802.11T                                    PICS proforma was
Recommended Practice for                                       specifically requested and
testing procedures was                                         required by the 802 EC. The
terminated for lack of interest,                               TG also debated the comment
and Annex A should share the                                   and the consensus was that
same fate. If the PICS annex                                   the PICs provides value and
is not removed, make it                                        belongs in the standard.
informative with the statement
"This clause is no longer
maintained and may not be
compatible with or describe all
features of this standard."




Annex D SMT Attributes        Remove SMT Attributes that       DISAGREE                      EDITOR
states "The SMT object class are not referred to in            (ARCHITECTURE: 2009-11-
provides the necessary        normative text.                  18 20:33:37Z) DISAGREE
support at the station to                                      The commentor is
manage the processes in the                                    encouraged to provide more
station such that the station                                  details of any proposed
may work cooperatively as a                                    improvement, but without the
part of an IEEE 802.11                                         details of what is proposed,
network." This is not a true                                   the group cannot evaluate the
statement, and I know of no                                    technical merit at this time.
products introduced since
2004 that claim the SMT
object class provides the
necessary support ... . The
time to remove SMT Attributes
is now, as all SNMP scripts
will have to change with this
maintenance of the standard.
The ieee802dot11 MODULE           per comment                    AGREE IN PRINCIPLE           EDITOR
needs to be updated to be                                        (ARCHITECTURE: 2009-07-
correct at the time of REVmb                                     31 15:39:21Z) - See
publication - correct the                                        resolution CID #1586 for one
information herein. It is time to                                example of the updates being
maintain all of Annex D.                                         done. Annex D is being
                                                                 updated as part of the
                                                                 Revision process.
Country string third character Change the description of the AGREE IN PRINCIPLE (GEN: EDITOR
values "space", "I", and "O" do third character to allow only    2009-11-16 12:27:29Z) -
not allow the possbility of     "space" for a country or "X" for Accept in Principle based on
complying with some             a non-country.                   discussion and editorial
environments of the country                                      instructions in 09/1111r2:
but not all. The distinction is                                  1054, 1055, 1059, 1205 and
obsolete, and I know of no                                       1216
products introduced since
2004 that use "I" or "O" or
correctly use "space".




Annex D contains many object per comment                     DISAGREE                          EDITOR
definitions whose STATUS is                                  (ARCHITECTURE: 2009-07-
deprecated. Remove those                                     16 06:01:00Z) - We generally
objects. It is false to think that                           keep, but deprecate, facilities
legacy managers of 802.11                                    that are not to be used
stations rely on receiving                                   anymore, for historical
"deprecated" as any SNMP                                     reasons.
scripts will be updated when
REVmb changes the
ieee802dot11 MODULE.
In dot11PHYType, the "OFDM per comment                        AGREE (ARCHITECTURE:              EDITOR
5GHz" should be changed to                                    2009-11-18 20:01:02Z)
"OFDM" as 11k and 11y
expanded the application of
OFDM outside 5 GHz.




The                            per comment                    AGREE IN PRINCIPLE                EDITOR
dot11RegDomainsSupported                                      (ARCHITECTURE: 2009-07-
Table is obsolete, and is not                                 16 06:01:50Z) We generally
necessary to manage the                                       keep, but deprecate, facilities
processes in the station or                                   that are not to be used
with other stations. The                                      anymore, for historical
Supported Regulatory                                          reasons. Set the status to
Classes construct is more                                     deprecated.
comprehensive, and used
from 11k onward. Remove the
dot11RegDomainsSupported
table,
dot11CurrentRegDomain and
related fields in PHY objects.




The IR PHY is obsolete and     remove all mention of the IR   AGREE IN PRINCIPLE (GEN: EDITOR
should be removed as part of   PHY.                           2009-09-24 00:11:08Z) -
this maintenance.                                             Agree in Principle -- Mark the
                                                              IR PHY as obsolete and
                                                              subject to removal in a future
                                                              revision: instruct the editor to
                                                              insert the following line at the
                                                              beginning of clause 16:"This
                                                              clause is obsolete and is
                                                              subject to removal from a
                                                              future revision."
The FH PHY clause and             remove all mention of the FH      AGREE IN PRINCIPLE (GEN: EDITOR
operation is not considered in    PHY or make clause 11.1.5,        2009-09-22 07:33:58Z) Agree
11k or any newer                  14, Annex B and Annex F           in Principle -- Mark the FH
amendments. It either should      informative. If this comment is   PHY as deprecated and
be removed as part of this        not rejected, Annex A and D       subject to removal in a future
maintenance or be made            will need to also be              revision Editor to add
informative with the statement    maintained.                       immediately following the
"This clause is no longer                                           clause heading the following
maintained and may not be                                           new paragraph: This clause is
compatible with all features of                                     obsolete and is subject to
this standard." This comment                                        removal in a future revision.
also applies to Annex B and
the FH PHY in Annex F.

dot11FrequencyBandsSupport per comment                              AGREE IN PRINCIPLE                EDITOR
ed is obsolete, and is not                                          (ARCHITECTURE: 2009-07-
necessary to manage the                                             16 06:03:13Z) We generally
processes in the station or                                         keep, but deprecate, facilities
with other stations. It was not                                     that are not to be used
updated by 11y, nor is it being                                     anymore, for historical
changed in 11p. The                                                 reasons. Set the status to
Supported Regulatory                                                deprecated.
Classes construct is more
comprehensive and used
from 11k forward. Remove
dot11FrequencyBandsSupport
ed.
dot11TIThreshold is             per comment                         UNRESOLVABLE (EDITOR:             EDITOR
deprecated and not used in                                          2009-11-19 22:03:57Z) -
dot11PhyOFDMComplianceGr                                            Withdrawn by commenter
oup3. Remove
dot11TIThreshold from
dot11PhyOFDMEntry, and its
object definition.
Are we reserving Annex E for remove Annex E                         AGREE IN PRINCIPLE              EDITOR
the junior prom?                                                    (EDITOR: 2009-07-24
                                                                    08:42:03Z)
                                                                    Please see resolution of CID
                                                                    1242, which adds an editorial
                                                                    note.
"High Rate PHY/FH               remove Annex F or add               AGREE IN PRINCIPLE (GEN: EDITOR
interoperability" is an         disclaimer.                         2009-09-24 01:09:09Z) Agree
oxymoron. The clause                                                in Principle -- Mark Annex F
provides no value to the users                                      as deprecated and subject to
of the standard, and should                                         removal in a future
be removed, or begin with the                                       revision.The editor will put in
statement "This clause is no                                        the first part of the ….
longer maintained and may
not be compatible with all
features of this standard." ;-)
Figure I.1 has the Mask labels Change the Mask labels to            AGREE IN PRINCIPLE            EDITOR
in color, not black            black.                               (EDITOR: 2009-07-24
                                                                    08:47:43Z)
                                                                    Change Mask labels, "xBW",
                                                                    and the axis arrows to black.
                                                                    Move the mask labels clear of
                                                                    the grid and remove the grey
                                                                    blobs behind them.
                                                                    Reposition the callout arrows
                                                                    appropriately.

"wherein further transmission     per comment                       AGREE (EDITOR: 2009-07-     EDITOR
requirements may be found"                                          24 08:50:50Z)
is inaccurate, ignoring
operational requirements.
Change to "where further
operational requirements may
be found."
Missing "Reserved" in             per comment                       AGREE (EDITOR: 2009-07-     EDITOR
Transmit power limit (EIRP)                                         24 08:51:38Z)
column.
Given the Public Action           Add references to                 DISAGREE (MAC: 2009-09-      EDITOR
Frames that operate outside       submissions that illustrate the   30 14:20:15Z) - As per the
the context of the BSS, if we     problems of inserting an          comment, Annex M should be
agree the concept of " the DS"    802.11 bridged link into an       removed only if the DS is
is not relevant, and remove       802.1 architecture.               removed; the resolution to
the DS concept from clause 5,                                       CID 1412 retains the concept
then this apology (Annex M)                                         of the DS.
for breaking 802.1 bridging
should be removed. If this
annex remains, both Annex M
and O should have pointers to
802.1 presentations that
describe how 802.1 bridging
is broken by 802.11, and
propose resolutions
http://www.ieee802.org/1/files/
public/docs2008/avb-nfinn-
802-11-bridging-0108-v1.pdf
and subsequent prezos)
The Measurement Pilot option Remove the Measurement              DISAGREE (SECURITY:           EDITOR
specified here is obsolete,    Pilot option from the standard.   2009-07-14 21:36:43Z)
and is not in current products                                   Reject. This is a new feature
that claim 802.11                                                that is less than a year old,
conformance. I do not know of                                    and should be given time to
any products or plans to                                         be implemented before
implement Measurement                                            removal. The proposed
Pilots. The option would add                                     change may make existing
lots of noise in whatever band                                   802.11 devices non-compliant
it is used in (Note 1 pg 655,                                    with the standard.
Note 2 and NOTE, pg 656).                                        The comment has not justified
Commenter will make a                                            the change. This comment
submission removing                                              was previously rejected as
7.3.2.42, 7.4.7.2, 11.10.12                                      CID 158 in 11-07/2642r9.
and whatever other text
changes are needed to
remove the Measurement
Pilot Transmission option from
the standard.

remove these blank pages       per comment                       AGREE (EDITOR: 2009-07-      EDITOR
that come before Clause 8.                                       02 11:03:04Z)

This clause should be marked per comment                         DISAGREE                       EDITOR
informative. There is nothing                                    (ARCHITECTURE: 2009-07-
here that is externally visible                                  15 03:10:25Z) There are
or other normative text                                          normative dependencies on
outside clause 10 that                                           this clause. These are the
depends on the presence of                                       bones of the architecture, and
normative text in clause 10 for                                  are needed to support the rest
specified operation. If there is,                                of the normative text. The
move such normative text                                         behavior defined based on
from clause 10 to the correct                                    these interfaces is not
place.                                                           intended to be
                                                                 implementation, but is meant
                                                                 to be the structure for
                                                                 describing important behavior,
                                                                 and helps focus on one part of
                                                                 the whole of an 802.11 STA.
                                                                 The Standard needs to define
                                                                 end-point behavior, too, not
                                                                 just over-the-air protocol.
There is nothing here that is     per comment                     DISAGREE                       EDITOR
externally visible or other                                       (ARCHITECTURE: 2009-07-
normative text outside clause                                     15 03:14:35Z) There are
10 that depends on the                                            normative dependencies on
presence of normative text in                                     this clause. These are the
clause 10.3 for specified                                         bones of the architecture, and
operation. If there is, move                                      are needed to support the rest
such normative text from                                          of the normative text. The
clause 10.3 to the correct                                        behavior defined based on
place. After the last sentence                                    these interfaces is not
insert the statement "The                                         intended to be
remainder of this clause is no                                    implementation, but is meant
longer maintained and may                                         to be the structure for
not be compatible with all                                        describing important behavior,
features of this standard." ;-)                                   and helps focus on one part of
                                                                  the whole of an 802.11 STA.
                                                                  The Standard needs to define
                                                                  end-point behavior, too, not
                                                                  just over-the-air protocol.

This set of figures and text      Move 10.3.11 to within 11.9.6   DISAGREE                        EDITOR
belong outside clause 10,         Radio Measurement, and          (ARCHITECTURE: 2009-11-
which otherwise is a collection   update the references in the    18 20:03:50Z) The
of elements and fields. There     start of the third paragraph.   commentor is encouraged to
are no references to 10.3.11.                                     provide more details of any
                                                                  proposed improvement, but
                                                                  without the details of what is
                                                                  proposed, the group cannot
                                                                  evaluate the technical merit at
                                                                  this time.
The TPC and DFS               per comment     AGREE (GEN: 2009-09-22        EDITOR
mechanisms are required for                   22:23:25Z) However this
operation in the the 3.65 GHz                 change will cause a PAR
band, and IEEE 802.16h                        modification to possibly me
requires the quieting                         required. Note that the Scope
procedure to attempt                          and Purpose of the final
coexistence with 802.11 in                    document and the PAR must
any band. Change "regulatory                  match.
requirements for operation in
the 5 GHz band." to
"regulatory requirements for
operation in any band."

The OFDM phy is used in        per comment    AGREE (GEN: 2009-11-18      EDITOR
many bands, and the                           02:03:50Z)
definition of OFDM transmitter
power should be frequency
band agnostic. Change
"operation of a 5 GHz IEEE
802.11 " to "operation of an
IEEE 802.11".

This definition of transmitter  per comment   AGREE (EDITOR: 2009-07-     EDITOR
power is 802.11 OFDM                          01 12:27:29Z)
specific, and should be
moved to clause 3A.
Someone should generalize
this (look at other 802
wireless standards) if it is to
remain in the general section.

This clause contains no        per comment    AGREE (EDITOR: 2009-07-     EDITOR
normative text and should                     23 10:46:56Z)
become 12.4 at the end of
clause 12. The original 1997
standard's MAC and three
PHYs structure is not relevant
to the standard going forward.
The terms                       Change "broadcast and          AGREE IN PRINCIPLE (MAC: EDITOR
broadcast/multicast,            multicast MSDUs, relative to   2009-09-23 03:58:46Z)
unicast/directed have been      directed MSDUs" to "group      Review all uses of broadcast,
deprecated for use within       addressed MSDUs, relative to   multicast and unicast and
IEEE 802. The appropriate       individually addressed         replace as follows:
terms are "group addressed"     MSDUs"                         (1) "Unicast" changes to
and "individually addressed".                                  "individual" or "individually
                                                               addressed" according to
                                                               context
                                                               (2) "multicast", "broadcast /
                                                               multicast" or "broadcast or
                                                               multicast" changes to "group"
                                                               or "group addressed"
                                                               according to context. This
                                                               specifically applies to MIB
                                                               variables of the form
                                                               {something}Multicast{somethin
                                                               gelse}, which change to
                                                               {something}Group{somethinge
                                                               lse}
                                                               (3) "broadcast" remains the
                                                               term to use when specifically
                                                               referring to the broadcast
                                                               address

                                                               See also CID 1086.


The terms                       Change "broadcast and          AGREE IN PRINCIPLE (MAC: EDITOR
broadcast/multicast,            multicast MSDUs, relative to   2009-09-23 03:59:03Z) -
unicast/directed have been      unicast MSDUs" to "group       Review all uses of broadcast,
deprecated for use within       addressed MSDUs, relative to   multicast and unicast and
IEEE 802. The appropriate       individually addressed         replace as follows:
terms are "group addressed"     MSDUs"                         (1) "Unicast" changes to
and "individually addressed".                                  "individual" or "individually
                                                               addressed" according to
                                                               context
                                                               (2) "multicast", "broadcast /
                                                               multicast" or "broadcast or
                                                               multicast" changes to "group"
                                                               or "group addressed"
                                                               according to context. This
                                                               specifically applies to MIB
                                                               variables of the form
                                                               {something}Multicast{somethin
                                                               gelse}, which change to
                                                               {something}Group{somethinge
                                                               lse}
                                                               (3) "broadcast" remains the
                                                               term to use when specifically
                                                               referring to the broadcast
                                                               address

                                                               See also CID 1086.
The terms                       Change "broadcast and        AGREE IN PRINCIPLE (MAC: EDITOR
broadcast/multicast,            multicast MSDUs" to "group   2009-09-23 03:59:16Z) -
unicast/directed have been      addressed MSDUs"             Review all uses of broadcast,
deprecated for use within                                    multicast and unicast and
IEEE 802. The appropriate                                    replace as follows:
terms are "group addressed"                                  (1) "Unicast" changes to
and "individually addressed".                                "individual" or "individually
                                                             addressed" according to
                                                             context
                                                             (2) "multicast", "broadcast /
                                                             multicast" or "broadcast or
                                                             multicast" changes to "group"
                                                             or "group addressed"
                                                             according to context. This
                                                             specifically applies to MIB
                                                             variables of the form
                                                             {something}Multicast{somethin
                                                             gelse}, which change to
                                                             {something}Group{somethinge
                                                             lse}
                                                             (3) "broadcast" remains the
                                                             term to use when specifically
                                                             referring to the broadcast
                                                             address

                                                             See also CID 1086.


The terms                       Change "unicast MSDUs" to    AGREE IN PRINCIPLE (MAC: EDITOR
broadcast/multicast,            "individually addressed      2009-09-23 03:59:35Z) -
unicast/directed have been      MSDUs"                       Review all uses of broadcast,
deprecated for use within                                    multicast and unicast and
IEEE 802. The appropriate                                    replace as follows:
terms are "group addressed"                                  (1) "Unicast" changes to
and "individually addressed".                                "individual" or "individually
                                                             addressed" according to
                                                             context
                                                             (2) "multicast", "broadcast /
                                                             multicast" or "broadcast or
                                                             multicast" changes to "group"
                                                             or "group addressed"
                                                             according to context. This
                                                             specifically applies to MIB
                                                             variables of the form
                                                             {something}Multicast{somethin
                                                             gelse}, which change to
                                                             {something}Group{somethinge
                                                             lse}
                                                             (3) "broadcast" remains the
                                                             term to use when specifically
                                                             referring to the broadcast
                                                             address

                                                             See also CID 1086.
The terms                         Throughout the draft, change    AGREE (MAC: 2009-09-23        EDITOR
broadcast/multicast,              "broadcast", "multicast",       03:50:06Z) - Review all uses
unicast/directed have been        "broadcast or multicast",       of broadcast, multicast and
deprecated for use within         "broadcast and multicast" to    unicast and replace as
IEEE 802. The appropriate         "group addressed".              follows:
terms are "group addressed"       Throughout the draft, change    (1) "Unicast" changes to
and "individually addressed".     "unicast" to "individually      "individual" or "individually
    There are (rare) cases        addressed".                     addressed" according to
where it is valid to use the      The changes required for        context
terms multicast and               "directed" are more complex     (2) "multicast", "broadcast /
broadcast. Those cases are        since this word is often used   multicast" or "broadcast or
the instances where reference     in other contexts. When         multicast" changes to "group"
is being made to a non-IEEE       "directed" in used in the       or "group addressed"
protocol, for example an IETF     context of "directed frame",    according to context. This
protocol, where the the           "directed MPDU", or "directed   specifically applies to MIB
protocol is defined in terms of   MSDU" it should be changed      variables of the form
a broadcast or multicast          to "individually addressed      {something}Multicast{somethin
construct. For example, the       {identifier}".                  gelse}, which change to
802.11u and 802.11v                                               {something}Group{somethinge
amendments are known to                                           lse}
introduce a few such                                              (3) "broadcast" remains the
instances into the 802.11                                         term to use when specifically
standard where a specific                                         referring to the broadcast
protocol is referenced or                                         address
where the handling of group
addressed MSDUs/frames is
specified differently for
broadcasts than it is for
specific multicast group(s).
   When reference is made to
IEEE 802 entities,
mechanisms, procedures and
constructs the terms "group
"...BSS61" Editorial              As in comment                   AGREE IN PRINCIPLE                  EDITOR
                                                                  (EDITOR: 2009-06-30
                                                                  12:33:56Z)
                                                                  Add a space to the template
                                                                  before the last tab.

                                                                  In response to the
                                                                  commenter, the TOC embeds
                                                                  lots of compromises.
                                                                  Ultimately it's a matter of style
                                                                  as interpreted by the IEEE
                                                                  publishing editor.
"…STA 62" Editorial             As in comment                     DISAGREE (EDITOR: 2009-          EDITOR
                                                                  06-30 12:35:56Z)

                                                                  See also comment CID 1087.
                                                                  For that comment I inserted
                                                                  some space. However, as I
                                                                  interpret this comment, the
                                                                  commenter wants the 62 right
                                                                  aligned. The REVmb editor
                                                                  does not know how to do this
                                                                  without manual editing of the
                                                                  TOC, which is not feasible.

                                                                  This is ultimately a matter of
                                                                  style, as interpreted by the
                                                                  IEEE-SA publication editor.

...ammendments" spelling        As in comment                     AGREE (EDITOR: 2009-07-          EDITOR
                                                                  01 11:45:52Z)

"General(" Editorial            As in comment                     AGREE (EDITOR: 2009-06-          EDITOR
                                                                  30 12:25:48Z)

Please make a space             As in comment                     AGREE (EDITOR: 2009-06-          EDITOR
between # and letter                                              29 11:45:27Z)




Please make a space             As in comment                     AGREE (EDITOR: 2009-06-          EDITOR
between # and letter                                              29 11:46:25Z)

TK is often used as an          Add "(TK)" to the title of this   AGREE IN PRINCIPLE               EDITOR
abbreviation for the temporal   definition.                       (EDITOR: 2009-08-03
key.                                                              14:06:19Z) - As specified, and
                                                                  add TK to acronyms.
AAD should be an 802.11-         Move AAD to clause 3A.           DISAGREE (EDITOR: 2009- EDITOR
specific definition, because as                                   08-06 11:15:30Z) -
used in this document it is tied                                  The rule we have used to
to the specification of CCMP.                                     move items to 3A is whether
                                                                  the definition is itself
                                                                  dependent on the 802.11
                                                                  standard in some way. This
                                                                  definition is not, and therefore
                                                                  should not be moved.

Text on these pages is hard to Use black letters instead of       AGREE IN PRINCIPLE               EDITOR
read.                          white letters.                     (EDITOR: 2009-06-29
                                                                  11:48:57Z)
                                                                  Remove surplus pages.
The FH PHY should be             Deprecate this clause.            AGREE IN PRINCIPLE (GEN: EDITOR
deprecated since it is no                                          2009-09-22 07:31:59Z) Agree
longer used and has speeds                                         in Principle -- Mark the FH
such that it is no longer                                          PHY as deprecated and
commercially viable.                                               subject to removal in a future
                                                                   revision Editor to add
                                                                   immediately following the
                                                                   clause heading the following
                                                                   new paragraph: This clause is
                                                                   obsolete and is subject to
                                                                   removal in a future revision.

"The current AP encapsulates     Two options: (1) change the       AGREE IN PRINCIPLE            EDITOR
the FT Action frame (Request     definition of "encapsulate" in    (SECURITY: 2009-11-06
or Confirm) inside a Remote      3.49 so that it does not          16:04:25Z) -
Request frame and transmits      require cryptography, or (2)      Accept option 2. Change the
it to the target AP over the     change the usage of               sentence to
DS." By definition,              "encapsulate" in this clause to   "The current AP includes the
"encapsulate" (3.49) refers      some other word.                  contents of the FT Action
only to encrypting frames, not                                     frame (Request or Confirm) in
the act of putting a higher                                        a Remote Request frame"
layer frame inside a lower
layer type.

"7.1.3.1.1" is a vampirical      Write cross link on a wooden      AGREE IN PRINCIPLE                EDITOR
reference.                       stake, and drive it into the      (EDITOR: 2009-07-01
                                 reference to kill it.             14:38:53Z)
                                                                   Replace with live reference.
"7.3.2.30" is dead, Jim, it's    I'm a doctor, not a technical     AGREE IN PRINCIPLE                EDITOR
dead!                            editor. How would I know?         (EDITOR: 2009-07-01
                                                                   14:42:24Z)
                                                                   The technical editor, being
                                                                   also a doctor, is instructed to
                                                                   resurrect this reference.


Are "9.2.8" and "9.3.3" live     Take pulse and, if no             AGREE IN PRINCIPLE                EDITOR
references or dead               response, begin CPR and call      (EDITOR: 2009-07-01
references?                      911 to summon emergency           14:46:34Z)
                                 link enlivening services.         Replace with live references.

7.1.3.4 is an ex-reference.     See if it can be returned to the AGREE IN PRINCIPLE             EDITOR
                                reference store, or if it's well (EDITOR: 2009-07-01
                                and truly passed on.             14:56:09Z) - Replace with live
                                                                 reference.
7.1.3.5 has gangrene.           Reattach it to a link to the     AGREE IN PRINCIPLE             EDITOR
                                section header and hope it       (EDITOR: 2009-07-01
                                grows back?                      14:56:38Z)
                                                                 Replace with live reference.
Table 7-8 mixes up all sorts of I believe the TG has decided AGREE IN PRINCIPLE                 EDITOR
MIB references. Sometimes       on "set to TRUE"?                (EDITOR: 2009-07-27
variables "are true,"                                            11:06:38Z)
sometimes they are "set to
TRUE". Use one consistent                                        Please see resolution of CID
method of reference.                                             1535.
Deprecate shared key              Change "Shared Key" to      DISAGREE                             EDITOR
"authentication" in the table,    "Shared Key (deprecated)"   (ARCHITECTURE: 2009-11-
since it doesn't supply actual                                19 01:12:28Z) - Shared key
authentication.                                               authentication is only used
                                                              with WEP, and WEP has
                                                              already been deprecated. No
                                                              change is needed to
                                                              deprecate shared key
                                                              authentication.
Deprecate shared key              Change "Shared Key" to      DISAGREE                             EDITOR
"authentication" in the text,     "Shared Key (deprecated)"   (ARCHITECTURE: 2009-11-
since it doesn't supply actual                                19 01:14:41Z) - Shared key
authentication.                                               authentication is only used
                                                              with WEP, and WEP has
                                                              already been deprecated. No
                                                              change is needed to
                                                              deprecate shared key
                                                              authentication.
The informative NOTE              Combine the two paragraphs. AGREE (EDITOR: 2009-07-              EDITOR
apparently consists of two                                    02 11:06:56Z)
paragraphs, based on
formatting. It may not be
readily apparent that the
second paragraph is also
informative.
Annex C is not up to date.        Remove Annex C.               AGREE IN PRINCIPLE                 EDITOR
Deprecating the annex would                                     (EDITOR: 2009-08-11
dramatically reduce the size                                    14:16:06Z)
of the document and improve                                     Please see resolution of CID
its readability. One downside                                   1241.
is that the chair might feel as
if he was leading a less
important group since its
output document would
become significantly smaller.

"<your name could go here!>" Increase type size to 72 points.   AGREE IN PRINCIPLE                 EDITOR
is not sufficiently noticeable to                               (EDITOR: 2009-07-01
attract attention, and thus,                                    10:11:41Z) -
people to the editorial team.                                   Editors are subtle creatures,
                                                                and easily offended by use of
                                                                72 pt type. Such a change
                                                                would be counter productive.

                                                                Add the following text after the
                                                                cited text: "Please contact
                                                                adrian.p.stephens@intel.com
                                                                if you wish to assist with
                                                                editing this standard. Some
                                                                knowledge of IEEE-SA style is
                                                                helpful, and access to
                                                                Framemaker is essential. On
                                                                the job training will be given."
Incorporate IEEE 802.11n into Add the ratified and published UNRESOLVABLE (EDITOR: EDITOR
REVmb.                        version of 802.11n to the      2009-08-06 08:13:22Z) - This
                              REVmb draft.                   comment is unresolvable
                                                             because at the time of ballot,
                                                             there is no published version
                                                             of the cited document. TGmb
                                                             cannot approve any
                                                             instruction to its editor that
                                                             would resolve the comment.

Incorporate IEEE 802.11w      Add the ratified and published UNRESOLVABLE (EDITOR:          EDITOR
into REVmb.                   version of 802.11w to the      2009-08-06 08:17:38Z) -
                              REVmb draft.                   Please see resolution of CID
                                                             1109.




Incorporate IEEE 802.11z into Add the ratified and published UNRESOLVABLE (EDITOR:          EDITOR
REVmb.                        version of 802.11z to the      2009-08-06 08:18:07Z) -
                              REVmb draft.                   Please see resolution of CID
                                                             1109.
Come up with a better term        Be creative. Surprise me,       AGREE (EDITOR: 2009-12-        EDITOR
than "non-AP STA" to refer to     since I don't have a good       01 02:54:22Z) - Changes
what is typically called a        suggestion. Go "creatively      given in 11-09/1068r0
"client device." Adding           nuts," although that is scary
qualifications to the term        marching orders.
"STA" is unwieldy. Is there a
better way to say "non-AP non-
QoS FT-capable HT STA"?




The "data confidentiality"        Stop amusing me. Rename         DISAGREE (GEN: 2009-09-           EDITOR
service refers to WEP.            "data confidentiality" into     22 07:10:33Z) Decline. IEEE
Calling WEP "data                 something that sounds like      802.11 provides a data
confidentiality" is very funny.   less of a lie, such as "WEP     confidentiality service,
                                  data scrambling".               described in 5.4.3.3, which
                                                                  includes several alternatives.
                                                                  The alternatives provide a
                                                                  range between zero
                                                                  confidentiality (which arguably
                                                                  includes WEP) and currently
                                                                  a high degree of
                                                                  confidentiality (CCMP). The
                                                                  degree of confidentiality
                                                                  utilized in a particular wireless
                                                                  network is determined by the
                                                                  network operator.
Calling the 802.11               Decrease choking hazard by     DISAGREE (GEN: 2009-09-        EDITOR
authentication protocol the      renaming "authentication       22 07:24:19Z) Decline. IEEE
"authentication service" is      service" as the "identity      802.11 provides an
almost as funny as calling       assertion service" or          authentication service,
WEP "data confidentiality." It   something else less amusing.   described in 5.4.3.1, which
makes readers of the                                            includes several alternatives.
standard choke on their                                         The alternatives provide a
beverages when they read it.                                    range between zero
                                                                authentication (Open System)
                                                                and a high degree of
                                                                authentication (Fast BSS
                                                                Transition). The degree of
                                                                authentication utilized in a
                                                                particular wireless network is
                                                                determined by the network
                                                                operator.




Make cipher suite extensible.    Adopt 11-09/0601r0 or a        AGREE IN PRINCIPLE           EDITOR
                                 similar proposal.              (SECURITY: 2009-09-22
                                                                23:53:32Z) -
                                                                Make the changes given in
                                                                document 11-09/601r2
It seems kind of silly to have    Reorder clauses as 1-2-3-4-5- DISAGREE (EDITOR: 2009-            EDITOR
the DSSS and HR/DSSS              7-9-8-11-11A-14-16-15-18-17- 07-27 08:03:19Z) -
clauses separated, or the         19-6-12-10-13.
OFDM and ERP clauses                                            Clauses and annexes will be
separated, and the                                              renumbered towards the end
MLME/PLME clauses are not                                       of working group ballot
widely needed by                                                following the scheme:
implementers.
                                                                    Clauses: 1-2-3-3A-4-5-6-10-
                                                                    12-13-7-9-11-8-11A-14-16-15-
                                                                    18-17-19
                                                                    Annexes: starting with
                                                                    Bibliography, then all
                                                                    normative Annexes, then all
                                                                    informative.

                                                                    Because a resolution cannot
                                                                    promise future action, this
                                                                    has to be marked as a
                                                                    disagree.
"Moving data consists of          Two options: (1) change the       AGREE IN PRINCIPLE (MAC: EDITOR
moving encapsulated MSDUs         definition of "encapsulate" in    2009-10-23 16:27:15Z) -
among the APs (including          3.49 so that it does not          Remove the word
returning MSDUs to the            require cryptography, or (2)      "encapsulate" from the cited
source AP for MU-to-MU            change the usage of               text.
communications) and               "encapsulate" in this clause to
between the APs and the           some other word.
portal(s)." By definition,
"encapsulated" (3.49) refers
only to encrypted frames,
which should be decrypted at
the logical AP interface.
The chair prefers that his        Change "Matthew Gast" to          AGREE IN PRINCIPLE             EDITOR
middle initial be used. He        "Matthew S. Gast"                 (EDITOR: 2009-06-30
does, however, express                                              12:26:01Z) - And also note
gratitude that the editor knows                                     that somebody has taken the
that it has two "t"s, which                                         P out of Adrian P. Stephens.
seems to be a remarkably                                            Insert S. and P. as
difficult problem for many                                          appropriate.
people.
It states "Time zero is defined   Please clarify how Time Zero      AGREE IN PRINCIPLE                EDITOR
to be a TBTT with the Beacon      is used. Please separate the      (ARCHITECTURE: 2009-11-
frame being a DTIM and            defintion of Time Zero for        19 17:48:21Z)in reply to the
transmitted at the                EDCA and HCCA.                    commenter: Accept in
beginning of a CFP." It's                                           Principle "TimeZero is defined
unclear in the draft how Time                                       to be a TBTT" is a non-
Zero is used. In addition, if                                       mathematical way of saying
only EDCA is used,                                                  that TSF times that satisfy (tsf-
"transmitted at the beginning                                       time modulo
of a CFP." is not necessary                                         dot11BeadonPeriod) = 0 are
because there will not be a                                         TBTTs. Delete "And
CFP.                                                                transmitted at the beginning of
                                                                    the CFP".
"Time zero is defined to be a    Please clarify how Time Zero     DISAGREE                          EDITOR
TBTT." It's not clear from the   is used.                         (ARCHITECTURE: 2009-11-
draft how Time Zero is used                                       19 17:51:32Z) : in reply to the
and why such a definition is                                      commenter:Disagree
necessary.                                                        "TimeZero is defined to be a
                                                                  TBTT" is a non-mathematical
                                                                  way of saying that TSF times
                                                                  that satisfy (tsf-time modulo
                                                                  dot11BeadonPeriod) = 0 are
                                                                  TBTTs

It's not clear what an "ATIM     Please clearly state that if a AGREE IN PRINCIPLE              EDITOR
backoff timer" is. Presumably,   STA has a buffered ATIM        (EDITOR: 2009-08-06
it is a timer for sending ATIM   frame, it shall start          14:14:15Z) -
management frames. If a          decrementing the backoff       Add " if the STA has a
STA does not have an ATIM        timer for the ATIM frame.      buffered ATIM frame" at the
frame, it shouldn't start                                       end of the cited phrase.
decrementing a backoff timer.                                   Add a note below bullet d)
                                                                thus:
                                                                NOTE—The buffered ATIM
                                                                frame might be left over from
                                                                a failed channel access
                                                                attempt during an earlier ATIM
                                                                window, or it may be a new
                                                                ATIM generated by the
                                                                operation of the protocol in
                                                                11.2.2.1 (Basic approach).
"STAs in an infrastructure       Please replace "other          AGREE IN PRINCIPLE              EDITOR
network shall only use other     information" with "information (ARCHITECTURE: 2009-07-
information in received          that is not the CF Parameter   16 06:10:55Z) Need separate
Beacon frames, if the BSSID      Set". Or, move this paragraph paragraph to keep straight
field is equal to the MAC        to the end of the previous     from IBSS in the third
address currently in use by      paragraph.                     paragraph. Accept changing
the STA contained in the AP                                     "other information" to
of the BSS." What is "other                                     "information that is not the CF
information"?                                                   Parameter Set" and do the
                                                                same in the third paragraph.

Because the value of           Replace "the STA's                 AGREE IN PRINCIPLE                EDITOR
dot11StationID can be          dot11StationID." with "the         (ARCHITECTURE: 2009-11-
changed, it better to use "the STA's default dot11StationID."     18 19:59:54Z) - MIB variable
STA's default dot11StationID."                                    is noted as changes take
                                                                  effect with the next MLME-
                                                                  START.request change. This
                                                                  was done in conjuction with
                                                                  CID 1005
Both Supported Rate                Insert "Supported Rate         AGREE (ARCHITECTURE:            EDITOR
Information and Extended           Information and" before        2009-07-16 06:13:01Z)
Supported Information can be       "Extended Supported Rate
used in this case.                 Information"
In "it shall perform CCA", "it"    Delete "it"                     DISAGREE (EDITOR: 2009- EDITOR
is redundant.                                                      07-03 13:22:26Z)
                                                                   The commenter is incorrect.
                                                                   The text she cites is part of "in
                                                                   order to transmit shall perform
                                                                   CCA until". The "it" at the
                                                                   end of "transmit" is not
                                                                   redundant.
This statement does not            Please clarify whether there is DISAGREE (MAC: 2009-09-           EDITOR
clearly specify any normative      any normative behavior at the 25 03:16:30Z) - The end of
behavior: "An unscheduled          STA and how a STA would         the SP is signaled by the
SP ends after the AP has           know the SP has ended when EOSP bit, and the More Data
attempted to transmit at least     multiple MSDUs are              bit signals when the AP has
one MSDU or                        transmitted                     more data for a particular AC.
MMPDU associated with a                                            The cited statement is an
delivery-enabled AC and                                            informative description of how
destined for the non-AP STA,                                       the STA interprets these bits.
but no more than the
number indicated in the Max
SP Length field if the field has
a nonzero value."
Furthermore, it's not clear how
a STA would know when an
unscheduled SP ends if there
are multiple buffered MSDUs
transmitted during the SP.


"The AP may modify the        Please describe in more detail      AGREE IN PRINCIPLE (MAC: EDITOR
service start time by         wrt how the response frame is       2009-09-30 14:24:00Z) - "The
indicating so in the Schedule formed                              AP may modify the service
element in ADDTS Response                                         start time by indicating so in
frame and in Schedule                                             the Schedule element in
frames." In this case, does                                       successful ADDTS Response
the AP accept the request or                                      frame and in Schedule
reject the request? What is                                       frames."
the status code in the ADDTS
Response frame?
"MSDUs, or management              Delete "MSDUs, or                 AGREE (MAC: 2009-09-25       EDITOR
frames destined for PS STAs,       management frames,                03:16:43Z)
shall be temporarily buffered      destined for PS STAs using
in the AP.                         APSD shall be temporarily
MSDUs, or management               buffered in
frames, destined for PS STAs       the APSD-capable AP."
using APSD shall be
temporarily buffered in
the APSD-capable AP." The
second statement is exactly a
subset of the first statement.

"At every beacon interval, the     Please describe in more detail    DISAGREE (MAC: 2009-09-         EDITOR
APSD-capable AP shall              how a partial virtual bitmap is   25 03:16:54Z) - Assembly of
assemble the partial virtual       assembled in Annex L. Or, if      the partial virtual bitmap is
bitmap                             Annex L provides sufficient       explained in normative text in
containing the buffer status of    information, refer to Annex L     7.3.2.6. Annex L is
nondelivery-enabled ACs (if        somewhere in this section.        informative, and therefore, not
there exists at least one                                            appropriate.
nondeliveryenabled
AC) per destination for non-
AP STAs in PS mode and
shall send this out in the TIM
field of
the Beacon frame. When all
ACs are delivery-enabled, the
APSD-capable AP shall
assemble the
partial virtual bitmap
containing the buffer status for
all ACs per destination for non-
AP STAs." More detail should
be provided regarding how
partial virtual bitmap is
assembled because the
statement quoted here show
that the partial virtual bitmap
is assembled differently in
different situations. Is
providing a reference on
Annex L sufficient?

This paragraph is exactly the      Delete this paragraph             AGREE (EDITOR: 2009-07-      EDITOR
duplicate of the second                                              03 13:25:12Z)
paragraph in this section.
Estimating the power               Please define additional rules    AGREE IN PRINCIPLE (MAC: EDITOR
management state of other          so that the notification of PS    2009-11-13 20:03:58Z) -
STAs through transmitting          mode transition is more           Make the changes shown in
and lossing packets can            reliable.                         submission 11-09-1089-02-
interfere with many rate                                             000m-lb149-comment-
adaptation algorithms, which                                         resolution-cid-1131.doc,
rely on packet losses as an                                          which improve the reliability of
indication of bad channel.                                           the communication of PS
                                                                     states in IBSS, while
                                                                     preserving legacy
                                                                     compatibility.
This sentence is redundant.     Delete it.                     AGREE (EDITOR: 2009-08-        EDITOR
                                                               07 06:29:46Z) -

                                                               Note, the sentence is
                                                               redundant re the last
                                                               sentence of 11.2.2.1.
Remove "Non-AP" from the        Delete "Non-AP" from the       AGREE IN PRINCIPLE             EDITOR
section title to make it more   section title                  (EDITOR: 2009-07-03
uniform wrt the rest of the                                    13:55:14Z)
section titles                                                 Aggree that there is
                                                               inconsistency in the use of
                                                               this term.

                                                           Resolve the inconsistency by
                                                           adding "non-AP" to the
                                                           headings and in the first
                                                           sentence of subclauses of
                                                           11.3.2 as appropriate
                                                           (i.e. where the rules are
                                                           clearly specified for a non-AP
                                                           STA).
what is the "corresponding      Replace "the corresponding AGREE IN PRINCIPLE             EDITOR
QoS Action frame"? State it     QoS Action frame" with     (EDITOR: 2009-08-07
explicitly.                     "ADDTS Rquest frame and/or 14:12:01Z) - Replace cited
                                ADDTS Response frame"      sentence with: "... are
                                                           transported on the air by the
                                                           ADDTS Request frame and
                                                           the ADDTS Response frame,
                                                           and across the MLME SAP ...".

This sentence doesn't read      Replace "where certain" with   AGREE IN PRINCIPLE             EDITOR
well.                           "which"                        (EDITOR: 2009-08-07
                                                               08:27:48Z) - Replace cited
                                                               sentence with: "However,
                                                               K.3.2 (TSPEC construction)
                                                               describes parameter choice."
There is no "ADDTS QoS          Replace "ADDTS QoS Action      AGREE (EDITOR: 2009-08-        EDITOR
Action Request" frame.          Request" with "ADDTS           07 08:46:31Z)
                                Request". Replace "ADDTS
                                QoS Action Response" with
                                "ADDTS Response"

The TGmb draft should not       Wait until 802.11n (and        UNRESOLVABLE (EDITOR:          EDITOR
proceed to Sponsor Ballot       802.11w?) are ratified and     2009-08-06 08:18:49Z) -
until more Amendments are       include them into this draft   Please see resolution of CID
included, especially 802.11n.   before Sponsor Ballot.         1109.
The term "ad hoc" used to         Replace "ad hoc" with           AGREE IN PRINCIPLE            EDITOR
describe an IBSS is only a        "independent" in 1.2, 2nd       (EDITOR: 2009-08-06
vernacular. So, stop using it,    paragraph, 1st bullet.          11:12:54Z)
except as the hint provided in    Replace "ad hoc" with "IBSS"    As proposed by commenter,
Clause 3, 5.2.1, and N.2.         in 5.2.3.1(d). Delete the 2nd   except the last change,
                                  sentence in 5.6. Delete "ad     instead delete "or ad hoc
                                  hoc" in 11.2.2.1, 2nd           network" at cited location.
                                  sentence. Replace "ad hoc
                                  network" with "IBSS" in
                                  14.4.2.2.
This paragraph (2nd in            Delete 2nd paragraph of         AGREE (EDITOR: 2009-07-       EDITOR
11.2.2.1) is a duplicate of the   11.2.2.1.                       03 13:25:50Z)
previous paragraph.
2nd sentence, "In an ESS,         Replace "In an ESS" with "In    AGREE (SECURITY: 2009-07- EDITOR
there is one GTKSA, …" is         an infrastructure BSS".         14 21:51:56Z)
confusing. There is one
GTKSA per BSS, in
infrastructure mode.
The phrase "such as the           Replace "between MAC and        AGREE (ARCHITECTURE:          EDITOR
interfaces between MAC and        MLME and between PLCP           2009-07-16 06:13:44Z)
MLME and between PLCP             and PLME" with "between
and PLME, represented as          MLME, PLME and SME"
double arrows within Figure
10-1 (GET and SET
operations" is confusing,
since the double-arrows in 10-
1 are between the LMEs and
the SME.




Do we need references to      If possible, delete reference to AGREE (GEN: 2009-09-22           EDITOR
both revesions FIPS PUB       FIPS PUB 180-1-1995              22:26:17Z) Accept. Delete
180?                                                           normative reference to FIPS
                                                               PUB 180-1. Move footnote 2
                                                               to FIPS PUB 180-2.
                                                               In 8.5.2 b)1)ii) change 180-1-
                                                               1995 to 180-2-2002.
Footnotes 13 and 25 seem      Delete footnotes 13 and 25.      AGREE (EDITOR: 2009-07-          EDITOR
redundant with footnote 10 on                                  01 11:47:55Z)
page 6.
1st sentence of subclause        Replace first sentence with,    AGREE (EDITOR: 2009-07-   EDITOR
doesn't read well.               "The FT Confirm frame in an     02 10:59:43Z)
                                 RSN is confirmation to the
                                 target AP of receipt of the
                                 ANonce and indicates the
                                 liveness of the PTKSA.
In 2nd paragraph, 2nd            Replace "the current BSS        AGREE (MAC: 2009-08-07    EDITOR
sentence, reference to "BSS      Load value" with "the           00:33:01Z)
Load value" is ambiguous.        Available Admission Capacity
Should be reference to AAC       field value of the BSS Load
field of BSS Load element(?) element".
The phrase "frame associated Change "associated with" to         AGREE (MAC: 2009-09-25    EDITOR
with … AC" is confusing. For "using" in both occurances in       03:28:30Z)
example, does it include         this paragraph, and both
Management frames                occurances in the 10th
transmitted using AC_VO?         paragraph (pg 590, line 32),
                                 and both occurances in
                                 11.2.1.5(d) that are
                                 "associated with … AC(s)",
                                 and four occurances in
                                 11.2.1.5(h). Also change
                                 "belonging to" to "using" in
                                 11.2.1.5(d), 11.2.1.5(g) and
                                 11.2.1.9(b). Also change
                                 "belong to" to "use" in
                                 11.2.1.5(g), and both
                                 occurances in 11.2.1.9(d).
802.2 describes the expected Revert MA-                          AGREE IN PRINCIPLE (MAC: EDITOR
interface provided to LLC by     UNITDATA.confirm to MA-         2009-11-13 19:39:12Z) -
the MAC sublayer, and it has UNITDATA-                           Change any occurances of
an MA-UNITDATA-                  STATUS.indication,              MA-UNITDATA.confirm to MA-
STATUS.indication primitive      consistent with 802.2, X.210,   UNITDATA-
and no MA-                       and similar to 802.11-1999      STATUS.indication.
UNITEDATA.confirm
primitive.. Also, X.210 does
not support the concept of a
".confirm" service primitive for
a connectionless data service.
 The MA-UNITDATA-
STATUS.indication primitive
change to MA-
UNITDATA.confirm seemed
like a good idea at the time
(TGma), but it was actually in
error. This error has led to
confusion that the MA-
UNITDATA primitive set
provides what amounts to a
guaranteed delivery service,
which is not the case, nor the
intent. MA-UNITDATA is not a
confirmed facility. In fact, the
description of the .confirm
does not describe waiting for
successful transmission (and
ACK or other response) or
transmission exhaustion with
failure, as the name would
imply.
Section 9.9.3.1 says, "A non-     Clarify that the use of a EDCA     AGREE IN PRINCIPLE (MAC: EDITOR
AP STA may support                parameters for a lower priority    2009-11-19 16:26:57Z) -
admission control procedures      (non admission mandatory)          Incorporate the changes from
in 9.9.3.1.2 to send frames in    AC does not require                11-09/1063r1 and replace the
the AC where admission            modification of the QoS            2 paragraphs starting at
control is mandated; but, if it   control field.                     408.33:
does not support that
procedure, it shall use EDCA                                         "A non-AP STA may support
parameters of a lower priority                                       admission control procedures
AC, as indicated in Table 9-1,                                       in 9.9.3.1.2 (Procedure at non-
that does not require                                                AP STAs) to send frames in
admission control" and also "If                                      the AC where admission
a STA desires to send data                                           control is mandated; but, if it
without admission control                                            does not support that
using an AC that mandates                                            procedure and
admission control, the STA                                           dot11RejectUnadmittedTraffic
shall use EDCA parameters                                            is false or not present, it shall
that correspond to a lower                                           use EDCA parameters of a
priority and do not require                                          lower priority AC, as indicated
admission control." Nothing in                                       in Table 9-1 (UP-to-AC
this section discusses the                                           mappings), that does not
setting of the TID(UP) field in                                      require admission control.
the QoS control when this is                                         When a STA uses a lower
done.                                                                priority AC for this purpose,
                                                                     the lower priority AC affects
                                                                     only the EDCA parameters
                                                                     used for channel access, i.e.,
                                                                     it has no effect on the
                                                                     contents of the transmitted
                                                                     frame. APs shall support
                                                                     admission control procedures,
                                                                     at least to the minimal extent
Lack of punctuation makes         Replace "results" with             of advertising that admission EDITOR
                                                                     AGREE IN PRINCIPLE
sentence confusing.               "results," (add comma).            (EDITOR: 2009-07-01
                                                                     14:50:35Z)
                                                                     Too many commas. Enclose
                                                                     "in the absence of
                                                                     transmission errors" in
                                                                     parentheses.
The Capability Information        Replace "when these bits are       AGREE IN PRINCIPLE                EDITOR
Field bits are now fully          fully allocated" with "since the   (EDITOR: 2009-07-02
allocated, we don't need the      CIF bits are fully allocated"      06:38:54Z)
anticipatory language                                                Replace ", intended to
anymore.                                                             augment the Capability
                                                                     Information field (CIF) when
                                                                     these bits are fully allocated."
                                                                     with " that augment the
                                                                     Capability Information field
                                                                     (CIF)"
Action Category value 17          Add a row to Table 7-24,         AGREE IN PRINCIPLE              EDITOR
(0x11) is being used by WFA       showing Category value with      (ARCHITECTURE: 2009-07-
for WMM signaling. To             code 17 as "Reserved for Wi-     19 02:31:37Z) There is no
prevent a usage collision in      Fi Alliance use", changing the   need to mark the field as
the future, this value should     existing "Reserved" row to       reserved for use by another
be explicitly listed as           appropriately reserve values     body. This is an ANA issue.
Reserved for this purpose in      before and after 17.             ANA assignments are
Table 7-24.                                                        handled at the direction of the
                                                                   TG's technical editor, and the
                                                                   editor is working with the ANA
                                                                   representative to handle this.
                                                                   No text change.

With the addition of RSNA         Add the concept of RSNA           AGREE IN PRINCIPLE             EDITOR
capability, the term              authentication to the state      (GEN: 2009-11-19 05:15:59Z)
"authentication" as it applies    variables and state machine      The Editor is instructed to
to states like the ones in        shown in 11.3.0a. This will      incorporate into the REVmb
11.3.0a, has taken on multiple    need a submission.               draft document 11-09/705r4.
meanings. That's fine, except                                      (https://mentor.ieee.org/802.11
many people seem to get                                            /dcn/09/11-09-0705-04-000m-
confused by which                                                  proposed-corrections-to-11-3-
authentication is being                                            sta-authentication-and-
referred to in different                                           association.doc)
contexts. This could perhaps
be alleviated by showing the
RSNA authentication process
in these state tables, like the
simple authentication.

Disassociation is not only        Delete "that is within an AP."   AGREE (ARCHITECTURE:          EDITOR
from non-AP STA to AP, as                                          2009-07-16 06:14:15Z)
implied by the description.
How can a DISASSOCIATE            Delete TIMEOUT and               AGREE (ARCHITECTURE:          EDITOR
request fail for either timeout   REFUSED as valid values for      2009-07-16 06:14:44Z)
or refusal?                       the ResultCode.
This behavior for MLME-           Delete the sentence              AGREE IN PRINCIPLE            EDITOR
EAPOL.confirm is not              describing the MLME-             (SECURITY: 2009-08-14
consistent with a                 EAPOL.confirm primitive in       15:41:50Z)
connectionless MAC and            this subclause, and delete       Change the last sentence of
X.210-based primitive             10.3.20.2.                       the paragraph to: "MLME-
methods. It also does not                                          EAPOL.confirm primitive
appear to serve any real                                           indicates to the Supplicant
purpose in the EAPOL-Key                                           when the EAPOL-Key frame
exchanges since everything                                         has been transmitted." In
uses handshakes.                                                   clause 10.3.20.1, change
                                                                   "acknowledged" to
                                                                   "transmitted". In clause
                                                                   10.3.20.2, change
                                                                   "acknowledged by" to
                                                                   "transmitted to". In clause
                                                                   10.3.20.4, change
                                                                   "acknowledged" to
                                                                   "transmitted".10.3.20.4,
                                                                   change "acknowledged by" to
                                                                   "transmitted to".
What does the ResultCode of Delete                           AGREE (ARCHITECTURE:          EDITOR
TRANSMISSION_FAILURE            TRANSMISSION_FAILURE         2009-11-18 20:07:03Z)
mean? This sounds like it is    from the valid ResultCodes
reporting the lack of a MAC
layer ACK to the MLME-
ADDTS.request, which is not
consistent with a
connectionless MAC layer
service. Besides, this is
better reported as a TIMEOUT
error, and only after the
timeout has expired, since the
sender has no way of knowing
if the reciever got the request
simply because the ACK was
not received (which is why
X.210-based service
primitives have the style that
they do).


The procedure for Vendor          Delete TIMEOUT and         AGREE IN PRINCIPLE            EDITOR
Specific Action frames is not     TRANSMISSION_FAILURE       (ARCHITECTURE: 2009-11-
particularly clear, but there     as valid values for the    18 20:10:17Z) Delete MLME-
does not appear to be any         ResultCode. (Or, delete    VSPECIFIC.confirm
response from the peer entity     MLME-VSPECIFIC.confirm     completely.
expected, beyond the MAC          completely.)
layer ACK. So, this should
follow the X.210 model for
connectionless service, which
has no .confirm primitive,
perhaps (in which case,
delete the .confirm
completely). But, at the very
least, there is no concept of a
TIMEOUT or
TRANSMISSION_FAILURE
response to the request.
Since there is no immediate       Delete TIMEOUT and         AGREE IN PRINCIPLE            EDITOR
response from the peer entity     TRANSMISSION_FAILURE       (ARCHITECTURE: 2009-11-
to a Neighbor Report Request      as valid values for the    18 20:12:23Z) delete the
(the Response is handled by       ResultCode. (Or, delete    Transmission_Failure result
a completely different set of     MLME-                      code.
primitives), there can be no      NEIGHBORREPREQ.confirm
useful concept of TIMEOUT         completely.)
or
TRANSMISSION_FAILURE in
a .confirm primitive. The
.confirm primitive itself is
probably not correct under the
X.210 model, and could
perhaps just be deleted.
There is no response from the      Delete                         AGREE IN PRINCIPLE         EDITOR
peer entity to a Neighbor          TRANSMISSION_FAILURE           (ARCHITECTURE: 2009-11-
Report Request (beyond the         as valid values for the        18 20:14:27Z) delete MLME-
MAC layer ACK). So, this           ResultCode. (Or, delete        NEIGHBORREPRESP.confirm
should follow the X.210 model      MLME-                           completely
for connectionless service,        NEIGHBORREPRESP.confirm
which has no .confirm              completely.)
primitive, perhaps (in which
case, delete the .confirm
completely). But, at the very
least, there is no useful
concept of a
TRANSMISSION_FAILURE
response to the request.
What does the ResultCode of        Delete                         AGREE IN PRINCIPLE          EDITOR
TRANSMISSION_FAILURE               TRANSMISSION_FAILURE           (ARCHITECTURE: 2009-11-
mean? This sounds like it is       from the valid ResultCodes.    18 20:17:27Z) Delete
reporting the lack of a MAC        Consider adding a TIMEOUT      TRANSMISSION_FAILURE
layer ACK at some point in the     ResultCode if the Link         from the valid ResultCodes
exchange, which is not             Measurement Response is        and Add TIMEOUT
consistent with a                  not received within some       ResultCode should be added.
connectionless MAC layer           described timeout (add this
service. Besides, this is          concept to 11.10.10).
better reported as a TIMEOUT
error, and only after a timeout
has expired, since the sender
has no way of knowing if the
reciever got the request
simply because the ACK was
not received (which is why
X.210-based service
primitives have the style that
they do).


The non-AP STA has no way          Replace all this text with a   AGREE IN PRINCIPLE             EDITOR
of knowing if it is experiencing   simple description of a        (EDITOR: 2009-11-19
case 1 in Figure 11-9 and the      timeout mechanism that         13:29:41Z) - AGREE IN
ACK is getting lost, or case 2.    causes the MLME-               PRINCIPLE (MAC: 2009-08-
Therefore, it cannot               ADDTS.confirm to report        07 15:21:43Z) - remove the
definitively distinguish these     failure due to TIMEOUT.        phrase "with a result code of
two cases. This is why             Delete Figure 11-9.            TRANSMISSION_FAILURE in
connectionless/datagram                                           the former case and" as well
service primitives are not                                        as "in the latter case"
designed with this sort of error                                  following the word TIMEOUT.
reporting via .confirm                                            Also change the introductory
primitives. Reporting                                             phrase of the next sentence to
transmission failures of                                          read "In either case". Do not
various types is either inexact                                   change the figure.
or impossible. There should
only be a single failure report
for all such errors, and
TIMEOUT seems to be the
best of the existing choices.
It is never made clear if         Add text to clarify that Medium   DISAGREE (MAC: 2009-11-         EDITOR
admitted_time and used_time       Time is to include both uplink    18 20:49:10Z) - The
are meant to cover both uplink    and donwlink directions (so an    commentor is encouraged to
and downlink directions. For      AP needs to account for both      provide more details of any
example, admitted_time            directions in the computation     proposed improvement, but
would appear to be a total        like K.2.2), and that             without the details of what is
time used on behalf of the        used_time needs to capture        proposed, the group cannot
non-AP STA (for uplink or         time used on behalf of the        evaluate the technical merit at
downlink), but the used_time      non-AP STA for both               this time.
discussion is focused on "time    directions of data traffic.
to transmit" from the non-AP
STA's perspective ("the
amount of time used ... by the
non-AP STA" and "the time
required to transmit the
MPDU sequence"). K.2.2, in
discussing how an AP might
compute MediumTime does
not double the time if the
request is for a bi-directional
link, either.


What is "the wildcard             Add text to specify what is       AGREE IN PRINCIPLE           EDITOR
address"?                         meant here.                       (EDITOR: 2009-08-06
                                                                    11:25:55Z)
                                                                    Replace "wildcard" by
                                                                    "broadcast".
A STA does not have to be         Change the definition of STA      AGREE (GEN: 2009-11-18       EDITOR
contained within a single         to: "A logical entity that is a   01:46:21Z)
physical device (examples are     singly addressable instance of
"upper MAC" and "lower            an IEEE 802.11-conformant
MAC" implementations,             medium access control (MAC)
"controller based" APs, etc.).    and physical layer (PHY)
The point of a "STA" is that it   interface to the wireless
is a single instance of a MAC     medium (WM)."
and PHY, and that it is
uniquely identified and
addressed by its MAC
address.




It isn't clear that an AP has     Change the definition of AP       AGREE IN PRINCIPLE (GEN: EDITOR
exactly one STA (that is, only    to: "Any entity that contains     2009-11-18 01:47:29Z)
one STA). The current             one station (STA) and             Change the definition of AP
defintion could be read such      provides access to the            to: "An entity that contains one
that an AP contains more than     distribution services, via the    station (STA) and provides
one STA. But, if this is          wireless medium (WM) for          access to the distribution
allowed, many, many               associated STAs."                 services, via the wireless
assumptions within the                                              medium (WM) for associated
Standard will fall apart.                                           STAs."
With no definition of Multiple   Add a definition of a Multiple      AGREE (GEN: 2009-11-18              EDITOR
BSSID Set, the concept just      BSSID Set: "A collection of         20:23:39Z)
sort of "happens" in 11.10.11.   cooperating APs, such that all
                                 the APs use a common
                                 regulatory class, channel, and
                                 antenna connector."
Multiple BSSID Set APs must      Add (at least), "Channel            AGREE IN PRINCIPLE                  EDITOR
share more facilities "in        Access Functions" to the list       (SECURITY: 2009-08-14
common" than those listed.       of common facilities in the first   15:50:00Z)
                                 bullet. There are probably          Add "Channel Access
                                 more things that should be          Functions" to the first bullet in
                                 listed. This will need study.       11.10.11. The commentor is
                                                                     encouraged to make a more
                                                                     detailed comment on future
                                                                     recirculation letter ballots.

The FH PHY is a poor             Mark the FH PHY as                  AGREE IN PRINCIPLE (GEN: EDITOR
coexister in the 2.4 GHz band    deprecated for new designs,         2009-09-22 07:30:06Z) Agree
and offers low data rates with   or remove this clause (and          in Principle -- Mark the FH
an inefficient MAC               related MAC material and            PHY as deprecated and
                                 Annex B) entirely                   subject to removal in a future
                                                                     revision Editor to add
                                                                     immediately following the
                                                                     clause heading the following
                                                                     new paragraph: This clause is
                                                                     obsolete and is subject to
                                                                     removal in a future revision.

The IR PHY offers low data       Mark the IR PHY as                  AGREE IN PRINCIPLE (GEN: EDITOR
rates with a LOS technology      deprecated for new designs,         2009-09-24 00:12:58Z) -
with an inefficient MAC          or remove this clause (and          Agree in Principle -- Mark the
                                 related MAC material) entirely      IR PHY as obsolete and
                                                                     subject to removal in a future
                                                                     revision: instruct the editor to
                                                                     insert the following line at the
                                                                     beginning of clause 16:"This
                                                                     clause is obsolete and is
                                                                     subject to removal from a
                                                                     future revision."

"Once PLCP preamble              Rewrite to "Once PLCP         AGREE (GEN: 2009-11-18                    EDITOR
transmission is started, the     preamble transmission is      19:10:07Z)
PHY entity shall immediately     started, the PHY entity shall
initiate PLCP header             immediately initiate PLCP
encoding then data               header encoding then data
scrambling and data              scrambling and data
encoding. The data shall then    encoding, where the data
be exchanged between the         shall be exchanged between
MAC and the PHY through a        the MAC and the PHY through
series of PHY-                   a series of PHY-
DATA.request(DATA)               DATA.request(DATA)
primitives issued by the MAC"    primitives issued by the MAC"
is anti-causal as data
encoding commences before
data is exchanged to the PHY.
"TX training symbols.              Rewrite to "TX training          AGREE (EDITOR: 2009-07-      EDITOR
Followed by the SIGNAL field,      symbols followed by the          23 12:06:18Z)
which consists of:" is not ideal   SIGNAL field, which consists
since the verb TX is needed        of:"
to make the "Followed" make
sense.
The 1 and 2 Mbps DSSS PHY          Mark a clause-15-only PHY as     DISAGREE (GEN: 2009-09-      EDITOR
offers low data rates and has      deprecated for new designs:      22 07:35:54Z) Products are
a very inefficient preamble        i.e. require that the minimum    still being produced and
with an inefficient MAC            PHY be clause 18.                developed using this PHY.

The FH PHY is a poor               Mark the FH PHY as               AGREE IN PRINCIPLE (GEN: EDITOR
coexister in the 2.4 GHz band      deprecated for new designs,      2009-09-22 07:32:37Z) Agree
and offers low data rates with     or remove this clause (and       in Principle -- Mark the FH
an inefficient MAC                 related MAC material and         PHY as deprecated and
                                   Annex B) entirely                subject to removal in a future
                                                                    revision Editor to add
                                                                    immediately following the
                                                                    clause heading the following
                                                                    new paragraph: This clause is
                                                                    obsolete and is subject to
                                                                    removal in a future revision.

The IR PHY offers low data         Mark the IR PHY as               AGREE IN PRINCIPLE (GEN: EDITOR
rates with a LOS technology        deprecated for new designs,      2009-09-24 00:10:33Z) Agree
with an inefficient MAC            or remove this clause (and       in Principle -- Mark the IR
                                   related MAC material) entirely   PHY as obsolete and subject
                                                                    to removal in a future revision:
                                                                    instruct the editor to insert the
                                                                    following line at the beginning
                                                                    of clause 16:"This clause is
                                                                    obsolete and is subject to
                                                                    removal from a future
                                                                    revision."

"Once PLCP preamble                Rewrite to "Once PLCP         AGREE (GEN: 2009-11-18          EDITOR
transmission is started, the       preamble transmission is      19:10:07Z)
PHY entity shall immediately       started, the PHY entity shall
initiate PLCP header               immediately initiate PLCP
encoding then data                 header encoding then data
scrambling and data                scrambling and data
encoding. The data shall then      encoding, where the data
be exchanged between the           shall be exchanged between
MAC and the PHY through a          the MAC and the PHY through
series of PHY-                     a series of PHY-
DATA.request(DATA)                 DATA.request(DATA)
primitives issued by the MAC"      primitives issued by the MAC"
is anti-causal as data
encoding commences before
data is exchanged to the PHY.

"TX training symbols.              Rewrite to "TX training          AGREE (EDITOR: 2009-07-      EDITOR
Followed by the SIGNAL field,      symbols followed by the          23 12:07:08Z)
which consists of:" is not ideal   SIGNAL field, which consists
since the verb TX is needed        of:"
to make the "Followed" make
sense.
The 1 and 2 Mbps DSSS PHY        Mark a clause-15-only PHY as      DISAGREE (GEN: 2009-09-         EDITOR
offers low data rates and has    deprecated for new designs:       22 07:37:28Z)Products are
a very inefficient preamble      i.e. require that the minimum     still being produced and
with an inefficient MAC          PHY be clause 18.                 developed using this PHY.

The PBCC option is not widely Mark the PBCC option as              AGREE IN PRINCIPLE (GEN: EDITOR
used and is inferior to the   deprecated for new designs,          2009-11-18 02:07:56Z)
OFDM PHY                      or remove this section (and          Insert in 7.3.1.4 (P107.12), 18
                              related material) entirely           (P885.34), Annex A (P998.35
                                                                   PC17 under "Protocol
                                                                   Capability"):
                                                                   "The use of the PBCC option
                                                                   is obsolete, and this option
                                                                   may be removed in a later
                                                                   revision of the standard."


The channel agility option is    Mark the channel agility option   DISAGREE (GEN: 2009-11-         EDITOR
not widely used and makes        as deprecated for new             18 02:05:08Z) While the
coexistence and frequency        designs, or remove this           indended requested outcome
planning much more difficult     section (and related material)    is clear, the changes to
                                 entirely                          achieve this outcome are
                                                                   substantial and non-obvious.
                                                                   The commenter is solicited to
                                                                   provide the changes in a
                                                                   submission.

The ERP-PBCC option is not       Mark the ERP-PBCC option          AGREE IN PRINCIPLE (GEN: EDITOR
widely used and is inferior to   as deprecated for new             2009-09-22 07:43:04Z) Agree
the OFDM PHY                     designs, or remove this option    in principle. Insert in 7.3.1.4
                                 entirely                          (P107.12), 9.6a (P389.50
                                                                   under "Description"), 19
                                                                   (p941.36), Annex A
                                                                   (P1063.63 under "PHY
                                                                   Features")
                                                                   "The use of the ERP-PBCC
                                                                   option is deprecated, and this
                                                                   option may be removed in a
                                                                   later revision of the standard."


The DSSS-OFDM option is          Mark the DSSS-OFDM option         AGREE IN PRINCIPLE (GEN: EDITOR
not widely used, introduces      as deprecated for new             2009-09-22 07:44:38Z)Agree
complexity, and is not           designs, or remove this option    in principle. Insert in 7.3.1.4
markedly better than OFDM +      entirely                          (P107.60), 9.6a (P389.52
MAC protection                                                     under "Description", 19
                                                                   (P941.36),
                                                                   Annex A (P998.40 under
                                                                   "Protocol Capability",
                                                                   P1064.13 under "PHY
                                                                   features")
                                                                   "The use of the DSSS-OFDM
                                                                   option is deprecated, and this
                                                                   option may be removed in a
                                                                   later revision of the standard."
The FH PHY is a poor               Mark the FH PHY as               AGREE IN PRINCIPLE (GEN: EDITOR
coexister in the 2.4 GHz band      deprecated for new designs,      2009-09-22 07:27:11Z) -
and offers low data rates with     or remove this clause (and       Agree in Principle -- Mark the
an inefficient MAC                 related MAC material and         FH PHY as deprecated and
                                   Annex B) entirely                subject to removal in a future
                                                                    revision Editor to add
                                                                    immediately following the
                                                                    clause heading the following
                                                                    new paragraph: This clause is
                                                                    obsolete and is subject to
                                                                    removal in a future revision.

The IR PHY offers low data         Mark the IR PHY as               AGREE IN PRINCIPLE (GEN: EDITOR
rates with a LOS technology        deprecated for new designs,      2009-09-24 00:10:13Z) Agree
with an inefficient MAC            or remove this clause (and       in Principle -- Mark the IR
                                   related MAC material) entirely   PHY as obsolete and subject
                                                                    to removal in a future revision:
                                                                    instruct the editor to insert the
                                                                    following line at the beginning
                                                                    of clause 16:"This clause is
                                                                    obsolete and is subject to
                                                                    removal from a future
                                                                    revision."

"Once PLCP preamble                Rewrite to "Once PLCP         AGREE (GEN: 2009-11-18          EDITOR
transmission is started, the       preamble transmission is      19:10:07Z)
PHY entity shall immediately       started, the PHY entity shall
initiate PLCP header               immediately initiate PLCP
encoding then data                 header encoding then data
scrambling and data                scrambling and data
encoding. The data shall then      encoding, where the data
be exchanged between the           shall be exchanged between
MAC and the PHY through a          the MAC and the PHY through
series of PHY-                     a series of PHY-
DATA.request(DATA)                 DATA.request(DATA)
primitives issued by the MAC"      primitives issued by the MAC"
is anti-causal as data
encoding commences before
data is exchanged to the PHY.

"TX training symbols.              Rewrite to "TX training          AGREE (EDITOR: 2009-07-      EDITOR
Followed by the SIGNAL field,      symbols followed by the          23 12:07:55Z)
which consists of:" is not ideal   SIGNAL field, which consists
since the verb TX is needed        of:"
to make the "Followed" make
sense.
The 1 and 2 Mbps DSSS PHY          Mark a clause-15-only PHY as     DISAGREE (GEN: 2009-09-      EDITOR
offers low data rates and has      deprecated for new designs:      22 07:37:49Z) Products are
a very inefficient preamble        i.e. require that the minimum    still being produced and
with an inefficient MAC            PHY for 2.4GHz be clause 18.     developed using this PHY.
The PBCC option is not widely Mark the PBCC option as              AGREE IN PRINCIPLE (GEN: EDITOR
used and is inferior to the   deprecated for new designs,          2009-11-18 02:07:56Z)
OFDM PHY                      or remove this section (and          Insert in 7.3.1.4 (P107.12), 18
                              related material) entirely           (P885.34), Annex A (P998.35
                                                                   PC17 under "Protocol
                                                                   Capability"):
                                                                   "The use of the PBCC option
                                                                   is obsolete, and this option
                                                                   may be removed in a later
                                                                   revision of the standard."


The channel agility option is    Mark the channel agility option   DISAGREE (GEN: 2009-11-          EDITOR
not widely used and makes        as deprecated for new             18 02:05:08Z) While the
coexistence and frequency        designs, or remove this           indended requested outcome
planning much more difficult     section (and related material)    is clear, the changes to
                                 entirely                          achieve this outcome are
                                                                   substantial and non-obvious.
                                                                   The commenter is solicited to
                                                                   provide the changes in a
                                                                   submission.

The ERP-PBCC option is not       Mark the ERP-PBCC option          AGREE IN PRINCIPLE (GEN: EDITOR
widely used and is inferior to   as deprecated for new             2009-09-22 07:43:04Z) Agree
the OFDM PHY                     designs, or remove this option    in principle. Insert in 7.3.1.4
                                 entirely                          (P107.12), 9.6a (P389.50
                                                                   under "Description"), 19
                                                                   (p941.36), Annex A
                                                                   (P1063.63 under "PHY
                                                                   Features")
                                                                   "The use of the ERP-PBCC
                                                                   option is deprecated, and this
                                                                   option may be removed in a
                                                                   later revision of the standard."


The DSSS-OFDM option is          Mark the DSSS-OFDM option         AGREE IN PRINCIPLE (GEN: EDITOR
not widely used, introduces      as deprecated for new             2009-09-22 07:44:38Z)Agree
complexity, and is not           designs, or remove this option    in principle. Insert in 7.3.1.4
markedly better than OFDM +      entirely                          (P107.60), 9.6a (P389.52
MAC protection                                                     under "Description", 19
                                                                   (P941.36),
                                                                   Annex A (P998.40 under
                                                                   "Protocol Capability",
                                                                   P1064.13 under "PHY
                                                                   features")
                                                                   "The use of the DSSS-OFDM
                                                                   option is deprecated, and this
                                                                   option may be removed in a
                                                                   later revision of the standard."


Phrase "frame reception"         Add "frame reception"             AGREE IN PRINCIPLE               EDITOR
omitted from the text            between "this" and                (EDITOR: 2009-07-02
                                 "transmission"                    15:13:40Z)
                                                                   Replace " and until this
                                                                   transmission occurs," with ",
                                                                   and until this Beacon frame is
                                                                   received,"
Space missing             peerMAC should be peer MAC AGREE (EDITOR: 2009-07-          EDITOR
                                                     03 13:12:42Z)

Table entries confusing   Table entries should line up        DISAGREE (EDITOR: 2009- EDITOR
                          better for clarity: “Multiple       07-23 12:44:33Z)
                          classes in Country information      This is an artefact of the long
                          element” should line up with        cross-reference format.
                          first “9.8.3” Reference and         When this is switched to the
                          “CF15:M” Status; line up            short format (probably at the
                          Support field “Multiple classes     start of sponsor ballot), the
                          in Association and                  reference and status rows will
                          Reassociation frames” should        line up properly.
                          line up with second “9.8.3”
                          Reference and “CF15:M”
                          Status; line up Support field


Table entries confusing   Table entries should line up        DISAGREE (EDITOR: 2009- EDITOR
                          better for clarity in RC5:          07-23 12:46:58Z) - This is an
                          “Coverage classes 0–31”             artefact of the long cross-
                          should line up with first “9.8.4”   reference format. When this
                          Reference and “CF15:M”              is switched to the short format
                          Status; line up Support field;      (probably at the start of
                          “Coverage class operation           sponsor ballot), the reference
                          when not associated” should         and status rows will line up
                          line up with second “9.8.4”         properly.
                          Reference and “CF15:M”
                          Status; line up Support field

Table entries confusing   Table entries should line up        DISAGREE (EDITOR: 2009- EDITOR
                          for clarity in RC6: “Power          07-23 12:46:40Z) - This is an
                          level, equivalent maximum           artefact of the long cross-
                          transmit power level and            reference format. When this
                          regulatory class” should line       is switched to the short format
                          up with first “9.8.4” Reference     (probably at the start of
                          and “CF15:M” Status; line up        sponsor ballot), the reference
                          Support field; “Power level         and status rows will line up
                          operation when not                  properly.
                          associated” should line up
                          with second “9.8.4” Reference
                          and “CF15:M” Status; line up
                          Support field
Table entries confusing   Table entries should line up        DISAGREE (EDITOR: 2009- EDITOR
                          for clarity in RC7: “Power          07-23 12:46:17Z)This is an
                          level, different maximum            artefact of the long cross-
                          transmit power level and            reference format. When this
                          regulatory class” should line       is switched to the short format
                          up with first “9.8.4” Reference     (probably at the start of
                          and “CF15:M” Status; line up        sponsor ballot), the reference
                          Support field; “Power level         and status rows will line up
                          operation when not                  properly.
                          associated” should line up
                          with second “9.8.4” Reference
                          and “CF15:M” Status; line up
                          Support field
Table entries confusing   Table entries should line up    DISAGREE (EDITOR: 2009- EDITOR
                          better for clarity in DSE4:     07-23 12:47:27Z) - This is an
                          “Transmission of DSE            artefact of the long cross-
                          measurement request by an       reference format. When this
                          AP” should line up with first   is switched to the short format
                          “11.11.15” Reference and        (probably at the start of
                          “(CF15&CF1):M” Status; line     sponsor ballot), the reference
                          up Support field;               and status rows will line up
                          "Transmission of DSE            properly.
                          measurement report by a
                          STA” should line up with
                          second “11.11.15” Reference
                          and “(CF15&CF2):M” Status;
                          line up Support field

Table entries confusing   Table entries should line up    DISAGREE (EDITOR: 2009- EDITOR
                          better for clarity in DSE5:     07-23 12:48:04Z) - This is an
                          “Transmission of Association    artefact of the long cross-
                          Request frame with              reference format. When this
                          Supported Regulatory            is switched to the short format
                          Classes element by a STA”       (probably at the start of
                          should line up with “9.8.3      sponsor ballot), the reference
                          (Operation with regulatory      and status rows will line up
                          classes), 11.3.2.1 (STA         properly.
                          association procedures)”
                          Reference and
                          “(CF15&CF2):M” Status; line
                          up Support field;
                          “Transmission of Association
                          Response frame with
                          Supported Regulatory
                          Classes element by an AP”
                          should line up with “9.8.3
                          (Operation with regulatory
                          classes), 11.3.2.2 (AP
                          association procedures)”
                          Reference and
                          “(CF15&CF1):M” Status; line
                          up Support field
Table entries confusing   Table entries should line up     DISAGREE (EDITOR: 2009- EDITOR
                          for better clarity in DSE6:      07-23 12:48:23Z) - This is an
                          “Transmission of                 artefact of the long cross-
                          Reassociation Request frame      reference format. When this
                          with Supported Regulatory        is switched to the short format
                          Classes element by a STA”        (probably at the start of
                          should line up with “9.8.3       sponsor ballot), the reference
                          (Operation with regulatory       and status rows will line up
                          classes), 11.3.2.3 (STA          properly.
                          reassociation procedures)”
                          References and
                          “(CF15&CF2):M” Status; line
                          up Support field;
                          “Transmission of
                          Reassociation Response
                          frame with Supported
                          Regulatory Classes element
                          by an AP” should line up with
                          “9.8.3 (Operation with
                          regulatory classes), 11.3.2.4
                          (AP reassociation
                          procedures)” References and
                          “(CF15&CF1):M” Status; line
                          up Support field
Table entries confusing   Table entries should line up     DISAGREE (EDITOR: 2009- EDITOR
                          for better clarity in DSE9:      07-23 12:48:39Z) - This is an
                          “Transmission of extended        artefact of the long cross-
                          channel switch announcement      reference format. When this
                          and channel switch procedure     is switched to the short format
                          by an AP” should line up with    (probably at the start of
                          first “11.9a.3 (Selecting and    sponsor ballot), the reference
                          advertising a new channel        and status rows will line up
                          and/or regulatory class)”        properly.
                          Reference and
                          “(CF15&CF1):M” Status; line
                          up Support field;
                          “Transmission of extended
                          channel switch announcement
                          and channel switch procedure
                          by a STA” should line up with
                          second “11.9a.3 (Selecting
                          and advertising a new
                          channel and/or regulatory
                          class)” Reference and
                          “(CF15&CF2):M” Status; line
                          up Support field; Reception of
                          extended channel switch
                          announcement and channel
                          switch procedure by a STA”
                          should line up with third
                          “11.9a.3 (Selecting and
                          advertising a new channel
                          and/or regulatory class)”
                          Reference and “CF15:M”
                          Status; line up Support field
Table entries confusing         Table entries should line up   DISAGREE (EDITOR: 2009- EDITOR
                                for better clarity in DSE10:   07-23 12:48:52Z) - This is an
                                “Transmission of DSE power     artefact of the long cross-
                                constraint announcement by     reference format. When this
                                an enabling STA” should line   is switched to the short format
                                up with first “11.11.5         (probably at the start of
                                (Dependent STA operation       sponsor ballot), the reference
                                with DSE)” Reference and       and status rows will line up
                                “(CF15&CF1):M” Status; line    properly.
                                up Support field; “Reception
                                of DSE power constraint
                                announcement by a
                                dependent STA” should line
                                up with second “11.11.5
                                (Dependent STA operation
                                with DSE)” Reference and
                                “CF15:M” Status; line up
                                Support field
Typo                            “Station ManagemenT” should   DISAGREE (EDITOR: 2009- EDITOR
                                be “Station Management        07-23 13:28:07Z)
                                                              The "T" is capitalized to
                                                              explain its presence in the
                                                              SMT acronym.
Reference for 5.25 - 5.35 and   In the row labeled “4 Part 15 AGREE IN PRINCIPLE (GEN: EDITOR
5.47 - 5.725 bands missing      License Exempt bands” add “, 2009-11-18 05:43:21Z) -
                                15.407” in the column labeled Accept in Principle based on
                                “United States”               discussion and editorial
                                                              instructions in 09/1111r2:
                                                              1054, 1055, 1059, 1216 and
                                                              1301.




Reference for 5.25 - 5.35 and   In the row labeled “10 Part 15 AGREE (GEN: 2009-11-16   EDITOR
5.47 - 5.725 bands missing      License Exempt bands” add “, 12:20:40Z)
                                15.407” in the column labeled
                                “United States”
Power limit is incorrect      In the row labeled “5.25–5.35“ AGREE (GEN: 2009-11-16          EDITOR
                              change “200” to “250” in the   12:20:54Z)
                              column labeled “United States
                              (Maximum output power with
                              up to 6 dBi antenna gain)
                              (mW)”



No power limit shown          In the row labeled            AGREE (GEN: 2009-11-16           EDITOR
                              “5.470–5.725 “insert “250     12:23:41Z)
                              (12.5 mW/MHz)” in the
                              column labeled “United States
                              (Maximum output power with
                              up to 6 dBi antenna gain)
                              (mW)”




This document explains in its Provide redlines for the      OUT OF SCOPE (EDITOR:           EDITOR
abstract "This revision         changes which are made in   2009-08-06 08:12:09Z) - This
specifies technical corrections this revision document.     comment is out of scope
and clarifications to IEEE Std                              because it does not relate to
802.11 for                                                  the contents of the draft being
wireless local area networks                                balloted (i.e. it does not
(WLANS) as well as                                          propose any change to that
enhancements to the existing                                draft).
medium access
control (MAC) and physical                                  Please also see the resolution
layer (PHY) functions."                                     of comment 1208.
However there are no
indications of the previous
state of the standard or what
"technical corrections and
clarifications" have been
introduced in this revision to
the standard. I do not believe
this document is ready to be
balloted in this state.
This document explains in the Provide redlines for the               OUT OF SCOPE (EDITOR:           EDITOR
Introduction "In addition, this changes which are made in            2009-08-06 08:12:09Z) - This
revision specifies technical    this revision document.              comment is out of scope
corrections and clarifications                                       because it does not relate to
to IEEE Std 802.11 as well as                                        the contents of the draft being
enhancements…" However,                                              balloted (i.e. it does not
there are no indications of the                                      propose any change to that
previous state of the standard                                       draft).
or what "technical corrections
and clarifications" have been                                        In reply to the commenter:
introduced in this revision to
the standard. I do not believe                                       This project is a revision of
this document is ready to be                                         802.11. There is no
balloted in this state.                                              requirement during initial
                                                                     balloting of a revision draft to
                                                                     provide a redline to the
                                                                     previous revision.

                                                                   Draft 1.0 comprises the IEEE
                                                                   STD 802.11-2007 standard
                                                                   plus amendments IEEE STD
                                                                   802.11k-2008, IEEE STD
                                                                   802.11r-2008 and STD
                                                                   802.11y-2008 plus changes
                                                                   approved by TGmb as
                                                                   documented in 11-
                                                                   09/1127r20. There are
                                                                   incremental redlines in the
                                                                   802.11 members area
                                                                   showing the following steps:
                                                                   1. Incorporation of .11k
                                                                   2. Incorporation of .11r
Figure 7-73 and Table 7-73        Address how the current IEEE- 3. Incorporation of .11y
                                                                   DISAGREE                             EDITOR
Only allow for 3 octet            RAC assigned longer OUI          (ARCHITECTURE: 2009-11-
organization identifiers.         based organization identifiers 17 22:41:23Z) This is
Within the OUI identifier         are to be supported so that      addressed by TGp when it is
space, the IEEE-RAC have          the "entity that has defined the rolled in.
been issuing OUI based            content of the particular
identifiers to organizations      Vendor Specific information
that are longer than 3 octets,    element" can be identified.
specifically the IAB (36 bits     (see also general comment by
long) and OUI-36 (36 bits         same commenter for more
long). (see also general          information)
comment by same
commenter for more
information)
 Within the OUI identifier        Address how the current IEEE-      DISAGREE                           EDITOR
space, the IEEE-RAC have          RAC assigned longer OUI            (ARCHITECTURE: 2009-11-
been issuing OUI based            based organization identifiers     17 22:41:23Z) This is
identifiers to organizations      are to be supported so that        addressed by TGp when it is
that are longer than 3 octets,    the "entity that has defined the   rolled in.
specifically the IAB (36 bits     content of the particular
long) and OUI-36 (36 bits         Vendor Specific information
long). The OUI cannot in          element" can be identified.
itself identify the "the entity   (see also general comment by
that has defined the content of   same commenter for more
the particular Vendor Specific    information)
information element".
The bit ordering for the OUI is Add "The order of the                AGREE IN PRINCIPLE            EDITOR
not specified.                  organizationally unique              (ARCHITECTURE: 2009-11-
                                indentifier (OUI) field follows      17 22:59:05Z) See CID 1429
                                the ordering convention for          for proposed change
                                MAC addresses from 7.1.1
                                (Conventions)."




Figure 7-73 and Table 7-73        Address how the current IEEE-      DISAGREE                      EDITOR
Only allow for 3 octet            RAC assigned longer OUI            (ARCHITECTURE: 2009-11-
organization identifiers.         based organization identifiers     17 22:41:23Z) This is
Within the OUI identifier         are to be supported so that        addressed by TGp when it is
space, the IEEE-RAC have          the "entity that has defined the   rolled in.
been issuing OUI based            particular vendor specific
identifiers to organizations      action" can be identified. (see
that are longer than 3 octets,    also general comment by
specifically the IAB (36 bits     same commenter for more
long) and OUI-36 (36 bits         information)
long). The OUI cannot in
itself identify the "the entity
that has defined the content of
the particular Vendor Specific
information element".

The bit ordering for the OUI is Add "The order of the                AGREE IN PRINCIPLE            EDITOR
not specified.                  organizationally unique              (ARCHITECTURE: 2009-11-
                                indentifier (OUI) field follows      17 22:59:05Z) See CID 1429
                                the ordering convention for
                                MAC addresses from 7.1.1
                                (Conventions)."
Within the OUI identifier           Address how the current IEEE-      AGREE IN PRINCIPLE (GEN: EDITOR
space, the IEEE-RAC have            RAC assigned longer OUI            2009-09-22 22:04:14Z)Agree
been issuing OUI based              based organization identifiers     in Principle -- P802.11p
identifiers to organizations        are to be supported so that        addresses this. The current
that are longer than 3 octets;      the organizations can be           plan of Record is that TGp
specifically the IAB (36 bits       uniquely defined. One              would be finished in time for
long) and OUI-36 (36 bits           possible option is proposed in     inclusion into RevMB. Doc
long), where the first 24 bits of   P802.11pD7.0 where OUI in          09/98r8 is the proposal made
each are an OUI allocated           sections 7.3.2.26 and 7.4.5 is     to TGp. (note that we could
back to the IEEE-RA for the         replaced by Organization           include Doc 09/98r8 now but
purpose of creating IAB or          Identifier, which is a new field   when TGp is rolled in, any of
OUI-36 identifiers. This results    defined in 7.3.1.21 to be a        the changes we make may be
in multiple organizations           public unique organization         subtly different in TGp and
sharing the same OUI value,         identifier assigned by the         possibly overwrite any TGmb
with the last 12-bits of the IAB    IEEE, and is a variable length     changes made early).
or OUI-36 distinguishing            field, minimum 3 octets, which
between the organizations           contains the organizationally
that have the same first 24         unique identifier, and follows
bits in the identifier. A means     the ordering convention for
is needed so that the unique        MAC addresses from 7.1.1.
organization can be identified.     This field can therefore take
 This has impact also to            the form of an OUI, OUI-36 or
P802.11p, P802.11u &                IAB assigned by the IEEE.
P802.11v.                           The first 3 octets always
                                    contain the OUI portion
                                    allowing a receiving STA to
                                    interpret whether the field
                                    contains an OUI, an OUI-36
                                    or an IAB, or in the case of
                                    legacy STAs ignore the
                                    information including the
                                    vendor defined fields since
Typo                                Replace “the receive frame”
                                    the OUI will not match one it      AGREE (EDITOR: 2009-07-   EDITOR
                                    with “the received frame”.         03 12:59:36Z)
Annex J defines regulatory         Specify how 802.11 frames        AGREE IN PRINCIPLE (GEN: EDITOR
classes for a subset of            that include Regulatory Class    2009-11-16 12:27:36Z) -
regions (US, Europe, Japan).       octet are to be used in places   Accept in Principle based on
In theory, providing               outside the three regions (US,   discussion and editorial
information only for some          EU, JP) defined in Annex J or    instructions in 09/1111r2:
regions in 802.11 seems            make Annex J define              CIDs 1054, 1055, 1059, 1205
reasonable. However, the way       regulatory classes for all       and 1216;
that regulatory classes are        countries.                       https://mentor.ieee.org/802.11/
now used in couple of frames                                        dcn/09/11-09-1111-02-000m-
and will be used in future                                          lb149-proposed-regulatory-
amendments introduce a                                              comment-resolutions.doc.
serious limitation to the
applicability of the standard in
major areas like China,
Australia, South America,
Africa, and so on.
Furthermore, the way that the
regulatory class numbers are
defined by using a separate
numbering space for each
region can make it difficult to
use this number with a
channel number as an
identifier for a channel since
STAs would always need to
know in which region they are
(which may or may not be that
clear depending on whether
there are Beacon frames
available with Country IE).

"is set to TRUE" appears           make the upper/lower case        AGREE IN PRINCIPLE                  EDITOR
many places, and "is true"         "true" vs "TRUE" vs "True"       (EDITOR: 2009-07-30
appears many others.               consistent throughout the        13:05:59Z) - For the
                                   document. Make the "is set to"   capitalization issue - please
                                   vs "is" consistent throughout    see response to CID 1535.
                                   the document.
                                                                    Replace "is set to", "is set to a
                                                                    value", or "has the value of"
                                                                    with "is" in a conditional
                                                                    phrase (usually related to a
                                                                    MIB variable).

                                                                    Replace "if set to" with "if" in
                                                                    conditional phrases.
                                                                    Otherwise, remove "set to"
                                                                    where used as part of a
                                                                    conditional phrase.
                                                                    Reword as necessary to
                                                                    preserve syntax.
"is present within Association     change "withing Association      AGREE (EDITOR: 2009-07-             EDITOR
Request frames only                Request frames only              01 16:12:34Z)
generated by STAs that have"       generated by STAs that have"
doesn't match wording agreed       to "if".
in 0433r1
"is present when" doesn't         change "when" to "if". Make       AGREE IN PRINCIPLE             EDITOR
match wording agreed in           similar changes throughout        (EDITOR: 2009-07-01
0433r1                            document, matching the style      16:17:36Z)
                                  given in 0433r1..                 Change any "present when" to
                                                                    "present if" that occur during
                                                                    "presence tables". There is
                                                                    one occurance in clause 7
                                                                    and one in clause 10.

extraneous line break             remove extraneous line break AGREE (EDITOR: 2009-07-           EDITOR
between "MDIE" and "(i.e.,"                                    01 16:19:37Z)

Second sentence starts "This                               AGREE IN PRINCIPLE
                                  change to "These information                             EDITOR
information element", but                                  (EDITOR: 2009-07-01
                                  elements", here and for the
"This" refers to "One or more     Vendor Specific rows     16:29:32Z) - Change cited
vendor-specific information       throughout               sentence to "These
elements" (plural)                                         information elements follow all
                                                           other information elements."
                                                           throughout.
"If dot11RSNAEnabled is set change to "Fast bss transition AGREE IN PRINCIPLE              EDITOR
to TRUE fast BSS transition  and RSN are present if        (EDITOR: 2009-07-01
and RSN are present" doesn't dot11RSNAEnabled is set to 06:47:31Z)
follow agreed style in 433r1 TRUE." Similar changes        Change cited text to: "The
                             throughout Table 7-17.        Fast BSS Transition and RSN
                                                           information elements are
                                                           present if dot11RSNAEnabled
                                                           is set to TRUE.

                                                                    Make similar changes
                                                                    throughout Table7-17.

hanging paragraph                 insert a new subheading           AGREE IN PRINCIPLE           EDITOR
                                  7.4.8.0a with appropriate title   (EDITOR: 2009-07-02
                                                                    10:58:09Z)
                                                                    Add subclause heading
                                                                    "General"
numerous blank pages here         as in comment                     AGREE (EDITOR: 2009-07-      EDITOR
to delete                                                           02 11:02:51Z)

"between Message 1 and            change "of a 4-Way                AGREE (SECURITY: 2009-07- EDITOR
Message 3 of a 4-Way              Handshake" to "of the             14 21:53:52Z)
Handshake." but the phrase        handshake"
should include the FT 4-Way
Handshake added earlier in
the sentence.
footnote duplicates the           delete this footnote; it was      AGREE (EDITOR: 2009-07-      EDITOR
information given in footnote 8   included in the published         02 11:12:36Z)
on page 4                         802.11r as it was the first
                                  reference to Annex P, but not
                                  needed in the rollup. Also the
                                  footnote on page 4 should
                                  refer to Annex 0A, not P.
unclear whether normative        make the statements              AGREE IN PRINCIPLE                  EDITOR
"shall" is neede here, or        consistent. In either case,      (SECURITY: 2009-07-14
whether a simple declarative     insert a hyphen into SHA-256     21:54:21Z)
statement "SHA-256 is as                                          Replace "SHA256 shall be as
defined in …" matching the                                        defined in" with "SHA-256 is
style of the surrounding                                          as defined in"
statements is sufficient
Inconsistent wording, "The       make consistent. My              AGREE IN PRINCIPLE                  EDITOR
first-level FT key hierarchy     preference is "The first-level   (EDITOR: 2009-07-02
key…" (306.13), "The second-     key in the FT key hierarchy…"    13:10:47Z)
level key in the FT key          etc.                             Change initial phrase of
hierarchy…" (307.4) and "The                                      8.5.1.5.3-5 to match: "The
third level of the key                                            first-level key in the FT key
hierarchy" (307.32)                                               hierarchy,"
footnote duplicates the          delete this footnote; it was     AGREE (EDITOR: 2009-07-       EDITOR
information given in footnote    included in the published        02 13:12:17Z)
11 on page 7                     802.11r as it was the first
                                 reference to Clause 2, but not
                                 needed in the rollup
lines in upper left corner of    make straight instead of wavy UNRESOLVABLE (EDITOR: EDITOR
Figure 11-7 appear drunk.                                       2009-07-03 14:23:26Z)
                                                                I haven't done anything to fix
                                                                this, but in the source for the
                                                                figure, the .wmf it produces,
                                                                the frame-maker window and
                                                                a trial print of clause 11, the
                                                                innebriated lines did not make
                                                                an appearance.

                                                                  So I can't do anything to fix it,
                                                                  because I can't reproduce the
                                                                  problem.

dot11FTOver-DSEnabled            drop hyphen here                 AGREE (SECURITY: 2009-07- EDITOR
doesn't have the hyphen in                                        14 21:55:15Z)
MIB

some space is needed         add space, here and                  AGREE IN PRINCIPLE            EDITOR
between the message          throughout 11A                       (EDITOR: 2009-07-22
endpoint identifiers and the                                      10:02:30Z)
message contents, "STA-                                           Ensure each such occurance
>AP:<spaces/tab>Authenticati                                      consists of one space
on-Request…"                                                      followed by one tab after the
                                                                  colon.
The "Data(…)" notation came      drop "Data(" and ")" from        AGREE (SECURITY: 2009-07- EDITOR
from an early draft of 11i; it   these four entries, and drop     14 21:55:47Z)
was dropped before               the note at line 61
publication of 802.11i and
never appeared in REVma,
but was only caught in 11r at
publication time (too late).
entries in middle column of      as in comment                    AGREE (EDITOR: 2009-07-             EDITOR
this table should follow the                                      22 10:21:53Z)
guidelines in 0433r1
update Chair's name and          as in comment                    AGREE (EDITOR: 2009-07-             EDITOR
contact information                                               23 13:24:03Z)
update Editor's contact          as in comment                 AGREE IN PRINCIPLE            EDITOR
information                                                    (EDITOR: 2009-07-23
                                                               13:24:37Z)
                                                               Update email, remove
                                                               address and telephone details
                                                               as these are subject to
                                                               change.
Comment forwarded, on          A discussion needs to occur,    OUT OF SCOPE (MAC: 2009- EDITOR
behalf of TGu, from TGu letter as to which clause deals with   07-14 21:27:47Z) - This is an
ballot LB148                   "rate limiting" as opposed to   issue with the TGu
                               "LLC" beahviour. There is       amendment which is not part
TGu rejected the following     some sympathy within TGu,       of REVmb draft 1.0.
comment (TGu CID #6034) as that some of the behaviour
it appeared to be a more       within clause 6.2.1 be moved
general issue with the base    to clause 9.
standard.

===

I have comment about
removing rate limiting from
6.2.1.2 which is rejected (in
TGu) with reason "This same
question also came up during
LB132 (see CID #421, 422 in
11-08-0722r27)". TGu, with
advice from WG vice-chair,
agreed that this clause is the
proper place for the text. The
text describes new behavior
for the primitive which is
responsible for sending data
frames from a STA to a peer
STA--the MA-Unitdata.request
primitive. TGu is not aware of
any other clause in IEEE
802.11 which is more
appropriate."

Let meappears to why putting A discussion needs to occur,
There show you be some                                         AGREE IN PRINCIPLE             EDITOR
inconsistency in the way that to decided which of these two    (EDITOR: 2009-07-29
octet and bit fields are drawn "styles" is appropriate.        14:17:04Z)
in figures such as Figure 7-95                                 Please see resolution of CID
and Figure 7-95a, although                                     1248, which attempts a
this is not restricted to these                                systematic improvement in
two figures alone. It appears                                  consistency.
that two drawing styles have
converged into this single
document.
Can the MIBs in Annex D and     Compile and correct any         AGREE IN PRINCIPLE             EDITOR
Annex Q be compiled (or         errors in Annex D and Annex     (EDITOR: 2009-08-04
processed by a MIB syntax       Q.                              16:16:01Z) - Make changes
checker), to ensure that the                                    as shown in document 11-
MIB can be used.                                                09/0921r1. These result in a
                                                                combined MIB that compiles
                                                                without errors or warnings.

                                                                Note, this necessitated
                                                                renumbering
                                                                dot11RegulatoryClassGroup
                                                                (dot11Groups 29) to avoid
                                                                collision with
                                                                dot11RSNSMKcachingGroup.



                                                                Also correct any references
                                                                outside Clause Q from
                                                                "dot11RMStatisticsMeasaurem
                                                                entEnabled" to
                                                                "dot11RMStatisticsMeasureme
                                                                ntEnabled".
Spot the commentor who          1) I suggest that the annexes   DISAGREE (EDITOR: 2009- EDITOR
started his review with the     should be all clearly marked    07-27 08:03:47Z)
annexes !                       normative/informative (and
                                useless if you really have to). Please see resolution of
1) The annexes have built up Then order them with                 comment 1116.
over time to be many and        normative first and informative
varied. They also fall into 4   last, e.g. A, I, J, D, Q and then
classes: normative,             the informative ones.
informative, <blank> and
useless(Annex C).               2) Annex 0A should be re-
    Please can the annexes be named annex R (or annex S
re-arranged into some sort of to avoid the R=Bibliography,
order - see column to right for as opposed to R=Reference
a suggestion.                   confusion) and put at the end.

2) Annex 0A appears to be a
bit lost and needs a name
change - see column to right
for a suggestion
I think annex C has outstayed   Please remove this Annex, as    DISAGREE (EDITOR: 2009-        EDITOR
its welcome at the IEEE         it should not be present in a   09-23 18:50:52Z) - See
802.11 party.                   professional standards          comment resolution of CID
                                document any longer.            1369.
Ho, ho, another annex trying    Please remove this Annex, as    AGREE IN PRINCIPLE             EDITOR
to keep its foot in the door.   it should not be present in a   (EDITOR: 2009-07-24
                                professional standards          08:40:20Z)
                                document any longer.            Add editor's note explaining
                                                                this will be removed in due
                                                                course.

                                                                Note to commenter - this
                                                                annex will be removed when
                                                                the major renumbering
                                                                exercise is performed,
                                                                probably serveral WG ballot
                                                                cycles in to the future.
Annex I and Annex J do           Adding a reference to Annex I    AGREE IN PRINCIPLE (GEN: EDITOR
provide some assistance with    and J at this point may be        2009-11-18 01:53:43Z) - The
country specific issues.        useful for the country specific   Editor will fix the hanging
                                requirements sentence.            paragraph at 5.1a. The editor
                                                                  shall delete the last two
                                                                  sentances in that paragraph
                                                                  (the hanging one).

Replace the phrase "station-    Change to "STA-to-STA"            DISAGREE (EDITOR: 2009-       EDITOR
to-station"                                                       07-01 12:52:03Z)
                                                                  There are no occurances of
                                                                  STA-to-STA and 19
                                                                  occurances of station-to-
                                                                  station in the standard.

                                                              STA and station are
                                                              synonyms. Therefore the
                                                              change does not correct an
                                                              error, and introduces
                                                              inconsistency.
I think the words "space" and   Change "space" to "location" AGREE IN PRINCIPLE                 EDITOR
"location" imply the same       to maintain consistency. Then (EDITOR: 2009-07-01
entity here. Clause 5.2.4       perhaps change the result of 12:56:03Z)
further confuses this issue by  this to "area".               Change cited space to
stating that "area" should be                                 "location".
used P36L28.
A reference to Annex I or J     Add a reference to Annex I        AGREE IN PRINCIPLE            EDITOR
may be appropriate here. This and/or J to indicate more           (SECURITY: 2009-07-14
also applies to clause 5.4.4.2. information is available for      21:56:08Z)
                                country radio regulations.         Update the first sentence of
                                                                  Clause 5.4.4 as follows:
                                                                  "Two services are required to
                                                                  satisfy requirements in some
                                                                  regulatory domains ( See
                                                                  Annex I and Annex J for more
                                                                  information) for operation in
                                                                  the 5 GHz band."



Comment forwarded on            Consider all occurances of        DISAGREE                      EDITOR
behalf of TGu:                  OUIs in the document and          (ARCHITECTURE: 2009-11-
                                decide whether they should        17 22:41:23Z) This is
Recent work in TGp, has         be adapted to be either 3 or 5    addressed by TGp when it is
shown that the length of OUIs octet versions.                     rolled in.
is no longer 3 octets, as the
IEEE now caters for 5 octet
long values to be shared over
multiple organizations (OUI-
36/IAB). Hence all references
to OUIs should now consider
the new extended 32 bit (5
octet) version and even the
EUI 48 bit varient
<http://standards.ieee.org/rega
uth/oui/tutorials/EUI48.html>
Figures 7-76 and 7-77 have    Determine which style is        AGREE IN PRINCIPLE           EDITOR
inconsistent styles on the    consistent and change all       (EDITOR: 2009-07-29
Octets row, one using arrows, figures accordingly.            14:16:20Z) - This was
the other not.                                                analysed in 11-09-0714 and
                                                              discussed in the July 2009
                                                              TGmb meeting. The
                                                              consensus of the meeting was
                                                              to improve consistency by
                                                              replacing the arrowed styles
                                                              with non-arrowed ones,
                                                              except where arrows are used
                                                              to indicate/span structure.

                                                              For octet-aligned structures,
                                                              use single ruling. "Octets:" in
                                                              plain text.
                                                              Redraw figures:
                                                              7-37, 7-38, 7-39, 7-40, 7-41, 7-
                                                              42, 7-43, 7-44, 7-45
                                                              7-51, 7-73, 7-77, 7-78, 7-79, 7-
                                                              82, 7-85, 7-86, 7-87, 7-88, 7-
                                                              89, 7-90, 7-91, 7-92, 7-93, 7-
                                                              95
                                                              7-95o11, 7-95o13, 7-95o14, 7-
                                                              101h1, 7-101h2, 7-101h3, 7-
                                                              101h4, 7-101h5, 7-101h6, 7-
                                                              101h8
                                                              Adjust any other figures
                                                              already in this style for
                                                              consistency.

                                                              Convert figures using a
Figures 7-76 and 7-77 have      Determine which style is      mixture of octet/bit notation to
                                                              AGREE IN PRINCIPLE                 EDITOR
inconsistent styles regarding   consistent and change all     (EDITOR: 2009-07-02
the value of the Element ID.    figures accordingly.          07:58:09Z)
One includes this in the                                      Remove any such values
diagram (Figure 7-77) whilst                                  embedded values.
the other includes the value in
the text P183L62.                                             These occur in: BSS Load,
                                                              EDCA Parameter Set,
                                                              TSPEC, TCLAS, TS Delay,
                                                              TCLAS Processing, Schedule
                                                              and QoS Capability elements.

The abbreviation US is not     Add US "United States" as an   AGREE IN PRINCIPLE                 EDITOR
defined. Additionally, the     abbreviation. Replace U.S.     (EDITOR: 2009-07-22
abbreviation U.S. is           with US throughout the         09:46:49Z) - There are 15
sometimes used, e.g. P40L64    document, although this        occurances of U.S. and 5 of
                               cause problems with some of    US in the draft.
                               the normative reference        Furthermore there are 3
                               footnotes on page 3            occurances of U.S. and none
                                                              of US in the 2009 style
                                                              guide.

                                                              For consistency change all
                                                              "US" to "U.S.".
The GTK is wrapped in the       Correct the If value 2 refers to   AGREE IN PRINCIPLE               EDITOR
FTIE. It's length should be 16- the wrapped GTK, its range         (ARCHITECTURE: 2009-07-
43. It is wrapped (with AES)    should be changed to 35-51.        19 02:33:25Z) Make several
there is an extra 8 octet to                                       changes:
make the range 24-51. The                                          1. In Table 7-43g, change
field must include the padding.                                    "contents of data field" for
                                                                   value 2 from "GTK" to "GTK
                                                                   subelement"
                                                                   2. In Table 7-43g, change
                                                                   length of data field for value 2
                                                                   from "15-42" to "35-51"
                                                                   3. In Figure 7-95o6, change
                                                                   name of field "Key" to
                                                                   "Wrapped Key"
                                                                   4. In Figure 7-95o6, change
                                                                   length of Wrapped Key field to
                                                                   24-40 octets.
                                                                   5. In between the paragraphs
                                                                   at 212.28 and 212.31, before
                                                                   the paragraph beginning
                                                                   "When sent by a non-AP
                                                                   STA,...", add a new paragraph
                                                                   reading: "The Wrapped Key
                                                                   field contains the encrypted
                                                                   GTK as described in 11A.8.5."




During the FT-Initial              Add reason codes in Table 7- AGREE (ARCHITECTURE:             EDITOR
Association, there are cases       22 for:                         2009-11-18 20:25:09Z)
where the STA can give             - Invalid FT Action frame count
feedback to the AP on failed       - Invalid pairwise master key
FT attempts. There should be       identifier (PMKID)
reason codes added to table        - Invalid MDIE
7-22 to allow the STA to           - Invalid FTIE
communicate errors to the AP.

The Length field does not          Remove the sentence             AGREE (ARCHITECTURE:          EDITOR
exist in this IE. Therefore this   beginning with "The Length      2009-07-16 06:15:19Z)
description does not exist.        field equals …."

This looks like an important       Either add a statement that   AGREE IN PRINCIPLE              EDITOR
place to state that WEP and        TKIP and WEP are              (SECURITY: 2009-08-14
TKIP are deprecated.               deprecated in this clause, or 15:54:24Z)
                                   refer to clause 6.1.2.        Take the text that appears in
                                                                 the last two paragraphs of
                                   Alternative, move the         Clause 6.1.2 and copy them
                                   statement that WEP and TKIP to end of Clause 8.1.0a.
                                   are deprecated to this clause
                                   and add a reference in clause
                                   6.1.2.
The 4-way handshake is also        Add the following text after the AGREE (SECURITY: 2009-07- EDITOR
used for FT Initial Association.   first paragraph.                 14 21:58:31Z)
It would be beneficial to add      "The FT Initial Mobility
some text and a cross-             Domain Association uses the
reference to clause 11A.4.2.       FT 4-way handshake to
                                   establish an initial FT Security
                                   Association, that is based on
                                   this protocol. The FT 4-way
                                   handshake protocol is
                                   described in Clause 11A.4."

The paragraph states that if       Clarify the use of AP Channel     AGREE IN PRINCIPLE            EDITOR
the Channel Number field is        Report in the Beacon Report       (SECURITY: 2009-09-22
255, the STA conducts              as follows:                       05:57:26Z)
measurements on all                1) If the Channel Number          Changes as given in
channels included in the AP        Field is 0, the STA shall use     document 11-09/982r2.
Channel Report. However it         uses the regulatory domain
does not indicate where the        information.
STA receives the Channel           2) If the Channel Number
Report (I assume the               Field is 255, the STA uses the
Beacon). In the next               AP Channel report sub-
paragraph, the text states that    element(s) (if included) or the
an optional Channel Report         last AP Channel Report IE
sub-element can be used to         received in the last Beacon
supply a list of channels in the   frame.
Beacon Report.                     3) If the Channel Number
                                   Field specifies any other
                                   channel number, the STA will
                                   generate a Beacon Report
                                   response using that channel
                                   number.

                                   I can prepare a submission to
                                   clean up the last paragraph
                                   on pg 644 and first two
                                   paragraphs on pg. 645.

FT-Transition-Auth (R1KH-ID)       Move "FT-Transition-Auth          AGREE (SECURITY: 2009-07- EDITOR
to CALC-PMK_R1 S0KH SM             (R1KH-ID) to CALC-PMK_R1          14 21:58:54Z)
occurs too early. The              S0KH SM" to the FT-PTK-
supplicant may not know the        CALC state, after the
R1KH-ID at this point so it        Reassociationdeadlinetimer.
cannot calculate the PMK-R1.

It would be beneficial to          Change the text from:             AGREE IN PRINCIPLE            EDITOR
include the RFC reference as       "defined by FIPS SP800-38B"       (SECURITY: 2009-11-06
well as the FIPS publication       to:                               16:07:28Z) -
reference.                         "defined by FIPS SP800-38B        Change the text as proposed
                                   and also found in RFC 4493."      and add an inormative
                                   and add RFC 4493 to the           reference to RFC 4493.
                                   references.
The "Key Length field" in the    Key Length field is the actual    AGREE IN PRINCIPLE             EDITOR
description is ambiguous.        length of the Key field in        (ARCHITECTURE: 2009-07-
                                 octets.                           16 06:15:51Z) It seems pretty
                                                                   clear, with the next sentence.
                                                                   But, if change is desired, the
                                                                   proposed change doesn't
                                                                   really help much. Need to
                                                                   combine the two sentences:
                                                                   Change to, "The Key Length
                                                                   field is the length of the Key
                                                                   field in octets, not including
                                                                   any padding (see 11A.8.5)."

The RSN IE in message 2 of       Modify the text as follows:       AGREE IN PRINCIPLE                  EDITOR
the FT Intial Association will   2) If the MIC is valid, the       (SECURITY: 2009-08-14
not bitwise match the RSN IE     Authenticator checks that the     16:05:32Z)
used in the Reassociation        RSN information element bit-      Change clause 8.5.3.2 b) 2)
Request.                         wise matches that from the        on page 320, line 23 as
                                 (Re)Association Request           follows:
                                 message. For FT Intial            Change "If the MIC is valid,"
                                 Association, the RSN IE           to "If the MIC is valid and it is
                                 cannot be bit-wised compared      part of a Fast BSS-Transition
                                 because the PMKR1Name             Initial Mobility Domain
                                 will be included in the RSN IE    Association, see 11A.4.2. If
                                 field as part of Message 2. In    the MIC is valid and it is not
                                 that case, the remainder of       part of the Fast BSS-
                                 the RSN IE in message 2 is        Transition Initial Mobility
                                 checked against the RSN IE        Domain Association,"
                                 included in the Reassociation
                                 Request.
                                 i) If these are not exactly the
                                 same, the Authenticator uses
                                 MLME-DEAUTHENTICATE.
                                 request primitive to terminate
                                 the association.
                                 ii) If they do match bit-wise,
                                 the Authenticator constructs
                                 Message 3.
The RSN IE in message 3 of         Modify the text as follows:        AGREE IN PRINCIPLE                 EDITOR
the FT Intial Association will     Verifies the RSNIE. If it is not   (SECURITY: 2009-08-14
not match the RSN IE used in       identical to that the STA          16:15:34Z)
the Beacon or Probe                received in the Beacon or          Modify Clause 8.5.3.3 a) on
Response.                          Probe Response frame, the          page 321 line 49 as follows:
                                   STA shall disassociate. For        Change: "If it is not identical"
                                   FT Initial Association, the        to "If it is part of a Fast BSS-
                                   RSN IE will differ from the        Transition Initial Mobility
                                   RSN IE in Beacon and Probe         Domain Association, see
                                   Response messages becuse           11A.4.2. Otherwise if it is not
                                   it will contain the                identical"
                                   PMKR1Name in the PMKID
                                   field. For FT Initial
                                   Association, the PMKID field
                                   is ignored in the RSN IE
                                   comparison. If a second RSN
                                   information element is
                                   provided in the message,the
                                   Supplicant uses the pairwise
                                   cipher suite specified in the
                                   second RSNIE or
                                   deauthenticates.
The description of the             Modify the text as follows:        DISAGREE                           EDITOR
Management Count field is          The Measurement Count field        (ARCHITECTURE: 2009-07-
confusing. It would be better      contains a number of MSDUs.        16 06:16:42Z) Commenter's
to not provide text in this sub-   This value is used to calculate    proposal is same as current
clause and rely on the             an average discard count for       text?
description in Clause 11.          the Average trigger condition.
                                   It is also used in place of
                                   measurement duration in
                                   determining the scope of the
                                   reported results when a report
                                   is triggered; see 11.10.8.8
                                   (Transmit Stream/Category
                                   Measurement Report).


It makes sense that the            Modify the first sentence of       AGREE (SECURITY: 2009-07- EDITOR
Measurement Count field            the paragraph as follows:          14 21:59:54Z)
would be interpreted as the        Traffic stream metrics             Note only "successfully and
the total of successfully and      reported in a triggered            unsuccessfully" was added to
unsuccessfully transmitted         transmit stream/category           the sentence.
MSDU's. The current text is        measurement report shall be
ambiguous.                         the values accumulated over
                                   the number of successfully
                                   and unsuccessfully
                                   transmitted MSDUs prior to
                                   the trigger event given in the
                                   Measurement Count field of
                                   the transmit stream/category
                                   measurement request that
                                   established the trigger
                                   condition.
802.11mb D1.0 is 1602 pages       Now is the time to delete large   AGREE IN PRINCIPLE (GEN: EDITOR
long. Much of the text is         sections of text, particularly    2009-09-22 07:15:02Z) -
obsolete, useless and poorly      those self contained sections     Agree in Prinicple: TGmb is
written                           are obsolete.                     processing comments to
                                                                    address "obsolete, useless
                                  Ideally all obsolete features     and poorly written" sections of
                                  will be removed.                  the draft. Each Comment
                                  Unfortunately, many obsolete      submitted shall have due
                                  features are too intertwining     diligence done to determine
                                  with useful features, eg PCF      the best response and
                                                                    disposition. No specific
                                                                    change requested, but the
                                                                    new draft will be an
                                                                    improvement.

There have been suggestions Do not add any new non trivial          UNRESOLVABLE (GEN:             EDITOR
that the revision process   functionality to the standard in        2009-09-22 07:13:29Z)
should be used to add new   TGmb                                    Unresolvable: Comment does
features to the standard.                                           not address the draft under
                                                                    consideration. No Specific
However, new features should                                        change to the draft requested.
only be added when                                                  TGmb is processing
supported by a fully                                                comments to address all
developed and validate set of                                       sections of the draft. Each
market requirements.                                                Comment submitted shall
                                                                    have due diligence done to
This is a function that is much                                     determine the best response
better considered in a SG                                           and disposition. No specific
                                                                    change requested.

Clause 10 has virtually no        Reduce clause 10 to a few         DISAGREE                       EDITOR
value because all the material    pages that describes the          (ARCHITECTURE: 2009-07-
is (or should be ) covered        MLME structure and the            15 03:25:14Z) There are
elsewhere in the standard.        interfaces in very general        normative dependencies on
Worse, too much time is           terms and notes that it is left   this clause. These are the
spent developing clause 10        to the implementor to             bones of the architecture, and
which almost no one reads,        determine the details.            are needed to support the rest
even during the ballot process                                      of the normative text. The
                                                                    behavior defined based on
                                                                    these interfaces is not
                                                                    intended to be
                                                                    implementation, but is meant
                                                                    to be the structure for
                                                                    describing important behavior,
                                                                    and helps focus on one part of
                                                                    the whole of an 802.11 STA.
                                                                    The Standard needs to define
                                                                    end-point behavior, too, not
                                                                    just over-the-air protocol.
The IR PHY clause is obsolete Remove it      AGREE IN PRINCIPLE (GEN: EDITOR
                                             2009-09-23 23:53:20Z)Agree
                                             in Principle -- Mark the IR
                                             PHY as obsolete and subject
                                             to removal in a future revision:
                                             instruct the editor to insert the
                                             following line at the beginning
                                             of clause 16:"This clause is
                                             obsolete and is subject to
                                             removal from a future
                                             revision."




The SDL spec has almost no       Remove it   DISAGREE (EDITOR: 2009-        EDITOR
connection to the current                    09-23 18:51:35Z) - See
standard - and it is full of                 comment resolution of CID
errors                                       1369.




The procedure to select a new Remove it      DISAGREE (SECURITY:            EDITOR
channel in an IBSS is only                   2009-07-14 21:35:44Z)
claimed to be "best effort" at               The proposed change may
best. At worst, it may not even              make existing 802.11 devices
work.                                        non-compliant with the
                                             standard. The comment has
The reality is that after 5+                 not justified the change.
years there is no known
implemenation of this feature,
indicating it is unnecessary
This annex has no value as      Remove it                     DISAGREE (MAC: 2009-07-           EDITOR
part of the standard                                          14 21:16:34Z) It is believed
                                                              there is value in the standard.



This annex is empty             Remove it                     AGREE IN PRINCIPLE (GEN: EDITOR
                                                              2009-09-22 07:20:33Z) see
                                                              resolution of CID 1242: Add
                                                              Editor note that this Annex will
                                                              be removed in due course.

This informative annex is no   Remove it                      AGREE IN PRINCIPLE (GEN: EDITOR
longer relavant given the very                                2009-09-22 07:49:57Z) Agree
small number of FH systems                                    in Principle -- Mark the FH
                                                              PHY as deprecated and
                                                              subject to removal in a future
                                                              revision Editor to add
                                                              immediately following the
                                                              clause heading the following
                                                              new paragraph: This clause is
                                                              obsolete and is subject to
                                                              removal in a future revision

This annex has no value as      Remove it                       DISAGREE (GEN: 2009-09-        EDITOR
part of the standard                                            22 06:20:12Z) Annex O
                                                                gives the abstracts desription
                                                                of the DS SAP and is
                                                                considered of value.
This annex is empty             Remove it                       AGREE (GEN: 2009-09-22         EDITOR
                                                                07:19:58Z) see resolution of
                                                                CID 1242: Add Editor note
                                                                that this Annex will be
                                                                removed in due course.
FHSS is not longer in use (or   Add the following subclause: AGREE IN PRINCIPLE (GEN: EDITOR
perhaps never was). We          14.0a General                   2009-09-22 07:31:15Z) Agree
should not waste energy         This clause is no longer        in Principle -- Mark the FHSS
maintaining this clause or      maintained and may not be       PHY as deprecated and
making sure that other          compatible with all features of subject to removal in a future
clauses are compatible with     this standard.                  revision Editor to add
this clause.                                                    immediately following the
                                                                clause heading the following
                                                                new paragraph: This clause is
                                                                obsolete and is subject to
                                                                removal in a future revision.

sometimes ".indicate" is used   pick one and unify usage in   AGREE IN PRINCIPLE               EDITOR
in the draft (225 times) and    the draft                     (EDITOR: 2009-07-22
sometimes ".indication" is                                    10:28:14Z)
used (300 times).                                             Change all ".indicate" to
                                                              ".indication" as this appears to
                                                              be the commonest usage.
                                                              Do not make any changes in
                                                              Annex C.
Aren't the required PHY         please clarify                       AGREE IN PRINCIPLE             EDITOR
parameters in the                                                    (ARCHITECTURE: 2009-11-
TXVECTOR listed in the                                               17 21:53:13Z) change in
corresponding subclause (i.e.                                        12.3.4.4 (page 712 line 63)
17). There seem to be more                                           "the parameter values" to "the
PHY parameters required                                              minimum parameter values"
then identified in Table 12-4.
What's the point of table 12-4?




Aren't the required PHY             please clarify                   AGREE IN PRINCIPLE             EDITOR
parameters in the                                                    (ARCHITECTURE: 2009-11-
TXVECTOR listed in the                                               17 21:50:06Z) - Editor to
corresponding subclause (i.e.                                        change 12.3.5.4.2 (page 717
17).                                                                 line 18) by changing "required
                                                                     PHY parameters" to
                                                                     "minimum required PHY
                                                                     parameters.
"The PHY maintains the              Perhaps something more           DISAGREE                       EDITOR
channel busy indication until       generic like, "… until the       (ARCHITECTURE: 2009-07-
the period indicated by the         period indicated by fields in    16 06:56:04Z) Superseded
LENGTH field in a valid PLCP        the signal signal field…"        by resolution to CID 1280.
header has expired." Its not
really just LENGTH. In
Clause 17, the period is
based on RATE and
LENGTH. Seeing into the
future, in Clause 20 it will be
based on lots of parameters.
In clause 17, the PHY also          adding here all the conditions   AGREE IN PRINCIPLE                 EDITOR
maintains the channel busy in       when PHY maintains channel       (ARCHITECTURE: 2009-07-
the presense of energy above        busy is too combursome. I        16 06:18:43Z) Accept
a threshold (energy detect).        suggest deleting "The PHY        deletion. Also add sentence
This language could lead to         maintains the channel busy       in its place, "Refer to specific
the misinterpretation that ED       indication until the period      PHY clauses for details about
is not being performed.             indicated by the LENGTH field    CCA behavior for a given
                                    in a valid PLCP header has       PHY."
                                    expired." and forcing people
                                    to look at the specific PHY
                                    subclauses to learn about
                                    CCA behavior.

In eq 17-1 fix the font of "<t>",                                    AGREE IN PRINCIPLE                 EDITOR
it looks like a subscript                                            (EDITOR: 2009-07-23
                                                                     10:54:57Z)
                                                                     Promote <t> inline to equals
                                                                     sign
Eq 17-3 is partially cut off                                         AGREE (EDITOR: 2009-07-            EDITOR
                                                                     23 10:56:09Z)

Eq 17-7 is partially cut off                                         AGREE (EDITOR: 2009-07-            EDITOR
                                                                     23 10:56:44Z)
Eq 17-9 is partially cut off                                 AGREE (EDITOR: 2009-07-       EDITOR
                                                             23 10:57:10Z)

Lots of discussion took place define                         AGREE IN PRINCIPLE (GEN: EDITOR
in 11n about what was the                                    2009-11-18 19:04:47Z) -
default value of the reserve                                 Agree in Principle: See Doc
bit. Confusion regarding what                                09/1233r0 for editing
was the default value lead to it                             instructions.
not being used for future use.




A bunch of acronyms in Fig     define unless they are already AGREE IN PRINCIPLE (GEN: EDITOR
17-12 are not defined: IQ,     IEEE standards terms           2009) - Agree in principle.
HPA, LNA,                                                     Add "IQ       In phase and
                                                              Quadrature" to abbreviations
                                                              Add "HPA       High power
                                                              amplifier" to abbreviations
                                                              Add "LNA       Low noise
                                                              amplifier" to abbreviations

                                                             Comment:
                                                             IQ is not in IEEE.100.
                                                             HPA is not in IEEE.100.
                                                             LNA is in IEEE.100 meaning
                                                             "launch numerical aperture"


I don't think IF is defined    define unless they are already DISAGREE (GEN: 2009-09-      EDITOR
anywhere                       IEEE standards terms           24 23:18:41Z) Disagree. IF
                                                              is defined in IEEE.100.
guessing that the F in IF is   delete frequency               AGREE (EDITOR: 2009-07-      EDITOR
frequency, then "low IF                                       23 10:57:47Z)
frequency" has an extra
frequency
The language here is              This section needs to be       AGREE IN PRINCIPLE (GEN: EDITOR
misleading. "If the preamble      cleaned up as described in     2009-11-18 19:07:20Z) -
portion was missed, the           my comment.                    Replace the note at the end of
receiver shall hold the CCA                                      17.3.10.5 as follows:
signal busy for any signal 20     It was also clear from 11n     Replace: "NOTE -- CCA-ED
dB above the minimum              discussions that non-802.11    can be used in bands when
modulation and coding rate        people do not understand that not required by Annex J. In
sensitivity" is energy detect     basic clause 17 functionality  these cases, the
and is part of the basic clause   requires energy detect of non- recommended CCA-ED
17 CCA mechanism. "For            802.11 systems. Perhaps a      threshold is equal to 20 dB
improved spectrum sharing,        note stating this would be     above the minimum
CCA-ED is required in some        sufficient.                    modulation and coding rate
bands..." makes it sound like                                    sensitivity (-62 dBm for 20
sometimes energy detect is                                       MHz channel spacing, -65
not performed with clause 17,                                    dBm for 10 MHz channel
which is not true.                                               spacing, and -68 dBm for 5
                                                                 MHz channel spacing)."
                                                                 with
                                                                 "NOTE--The requirement to
                                                                 hold the CCA signal busy for
                                                                 any signal 20dB above the
                                                                 minimum modulation and
                                                                 coding rate sensitivity (-62
                                                                 dBm for 20 MHz channel
                                                                 spacing, -65 dBm for 10 MHz
                                                                 channel spacing, and -68
                                                                 dBm for 5 MHz channel
                                                                 spacing) is a mandatory
                                                                 energy detect requirement on
                                                                 all Clause 17 receivers.
                                                                 Support for CCA-ED is an
                                                                 additional requirement that
                                                                 relates specifically to the
"...PHY_CCA.indicate(BUSY)          clarify the CCA text to           AGREE IN PRINCIPLE (GEN: EDITOR
shall be issued for reception       highlight that energy detection   2009-11-18 19:11:09Z)
of a signal prior to correct        is performed even on non-         Please see the resolution to
reception of the PLCP               802.11 systems. Perhaps a         CID 1289, which adds a
frame. The PMD primitive            note is appropriate               NOTE a suggested.
PMD_RSSI is issued to
update the RSSI and
parameter reported to the
MAC.

After PHY-CCA.indicate is
issued, the PHY entity shall
begin receiving the training
symbols...".

My interpretation of this text is
again that basic energy
detection is required by
clause 17. That fact that this
is spread out between 17.3.6,
17.3.10.5, and 17.3.12 has
made it very difficult for non-
802.11 people to understand
that 802.11 clause 17 does in
fact require energy detection
of non-802.11 systems.


In 17.3.12 "The OFDM PHY         please clarify                       AGREE IN PRINCIPLE (GEN: EDITOR
will ensure that the CCA                                              2009-11-18 19:13:26Z) See
indicates a busy medium for                                           09/1233r0 for editing
the intended duration of the                                          instructions.
transmitted packet." and
12.3.5.10.3 "The PHY
maintains the channel busy
indication until the period
indicated by the LENGTH field
in a valid PLCP header has
expired." it makes is sound
like its required to maintain
CCA busy based on
rate/lengh in sig field.
However in 17.3.2.0a, "In
addition, the CCA mechanism
can be augmented by
predicting the duration of the
packet from the contents of
the RATE and LENGTH
fields, even if the data rate is
not supported by the STA."
makes is sound like its
optional. But in none of these
citations is there any
normative language.
Line 34 says that Eq 17-29    please clarify                  AGREE IN PRINCIPLE (GEN: EDITOR
shall be used to compute                                      2009-09-24 23:19:57Z) Agree
TXTIME, but then line 46 says                                 in principal.
the Eq. 17-30 may be used.                                    1. Replace "Ceiling(...)" with
This seems illogical to me.                                   N_SYM
Wouldn't a shall always                                       2. Remove parenthetical
supersede a may?                                              sentence on P873.41
                                                              3. Add ", according to Table
                                                              17-13" after "is derived from
                                                              the DATARATE parameter"
                                                              4. Remove lines 46-53 (i.e.
                                                              "A simplified ... T_SYM/2.")




Do any implementers even       perhaps get rid of it          DISAGREE (GEN: 2009-11-         EDITOR
pay attention to PMD                                          18 02:05:08Z) While the
sublayer?                                                     indended requested outcome
                                                              is clear, the changes to
                                                              achieve this outcome are
                                                              substantial and non-obvious.
                                                              The commenter is solicited to
                                                              provide the changes in a
                                                              submission.

what happens when with an    please clarify                   DISAGREE (GEN: 2009-11-       EDITOR
invalid signal? For ERP-                                      18 02:31:45Z) - The
OFDM do we default to clause                                  commentor is invited to
17 rules?                                                     provide more information of
                                                              what is being requested. The
                                                              Clause 19 description of CCA
                                                              defines what is done with a
                                                              "valid signal" and does not
                                                              describe what is done with an
                                                              "invalid signal" in the CCA
                                                              clause.
transmit masks moved back      change to "The transmit        AGREE (EDITOR: 2009-07-       EDITOR
to clause 17                   spectral mask for the ERP-     01 09:48:01Z)
                               OFDM modes shall follow
                               17.3.9.2 (Transmit spectrum
                               mask) and is shown in Figure
                               17-12a therein."
"MODU-LATION"                    change to MODULATION            AGREE (EDITOR: 2009-07-         EDITOR
                                                                 01 09:49:14Z)

"MODU-LATION"                    change to MODULATION            AGREE (EDITOR: 2009-07-         EDITOR
                                                                 01 09:49:41Z)

"DISALBED"                       change to DISABLED              AGREE (EDITOR: 2009-07-         EDITOR
                                                                 01 09:50:35Z)

"inter-operability"              change to interoperability      AGREE (EDITOR: 2009-07-         EDITOR
                                                                 24 08:43:13Z)

there is no tx power or EIRP     add tx power or EIRP level      AGREE (GEN: 2009-11-16          EDITOR
level for US in Table I.4 for                                    12:22:19Z) - see discussion
the 5.47-5.725 band. It may                                      and editorial instructions in
be implied that operation in                                     09/1111r2
this band in the US is not
permitted, which is not true.




we have transmit power           pick one location and unify     AGREE IN PRINCIPLE (GEN: EDITOR
regulatory information in both   information in the draft        2009-11-16 12:26:50Z) --
Annex I (Tables I.4-6) and                                       Accept in Principle based on
Annex J (Tables J.1-3).                                          discussion and editorial
                                                                 instructions in 09/1111r2:
                                                                 changes noted in section for
                                                                 CID1054, 1055, 1059, 1205
                                                                 and 1216;
                                                                 https://mentor.ieee.org/802.11/
                                                                 dcn/09/11-09-1111-02-000m-
                                                                 lb149-proposed-regulatory-
                                                                 comment-resolutions.doc.



everywhere else in the tables,   remove the dash and write out AGREE (EDITOR: 2009-07-           EDITOR
channel numbers are explicit     the channel number            24 08:52:53Z)
written
everywhere else in the tables,   remove the dash and write out AGREE (EDITOR: 2009-07-           EDITOR
channel numbers are explicit     the channel number            24 08:53:40Z)
written
Make cipher suite text more      Incorporate changes from doc AGREE IN PRINCIPLE         EDITOR
general to allow for other       09/0601                       (SECURITY: 2009-09-22
ciphers to be more easily                                      01:38:24Z)
added.                                                         Make the changes given in
                                                               document 11-09/601r2
MIC calculation includes the     Delete “Contents of the” from AGREE (SECURITY: 2009-07- EDITOR
IE headers.                      RSNIE, MDIE, and FTIE.        14 22:00:09Z)

MIC calculation includes the     Delete “Contents of the” from   AGREE (SECURITY: 2009-07- EDITOR
IE headers.                      RSNIE, MDIE, and FTIE.          14 22:00:15Z)
Does MDID globally unique?     Add explanation      DISAGREE                        EDITOR
                                                    (ARCHITECTURE: 2009-11-
                                                    17 22:52:04Z) MDID is not
                                                    globally unique.




Table 7-57e instead of Table   modify accordingly   AGREE (EDITOR: 2009-07-         EDITOR
7-57c                                               02 10:56:20Z)

where is the other             modify accordingly   DISAGREE                        EDITOR
measurement types: Basic,                           (ARCHITECTURE: 2009-11-
CCA and RPI?                                        18 20:36:54Z) - The
                                                    commentor is encouraged to
                                                    provide more details of any
                                                    proposed improvement, but
                                                    without the details of what is
                                                    proposed, the group cannot
                                                    evaluate the technical merit at
                                                    this time.
the measurement report         modify accordingly   DISAGREE                        EDITOR
mode in section 7.3.2.22                            (ARCHITECTURE: 2009-07-
figure 7-64 page 153 indicates                      16 06:20:23Z) ChannelLoad,
that latebit(0), but here it                        being an RRM measurement,
indicates a success bit?                            cannot be "Late" per 7.3.2.22

the measurement report         modify accordingly   DISAGREE                        EDITOR
mode in section 7.3.2.22                            (ARCHITECTURE: 2009-07-
figure 7-64 page 153 indicates                      16 06:23:26Z)
that latebit(0), but here it                        NoiseHistogram, being an
indicates a success bit?                            RRM measurement, cannot
                                                    be "Late" per 7.3.2.22
the measurement report         modify accordingly   DISAGREE                        EDITOR
mode in section 7.3.2.22                            (ARCHITECTURE: 2009-07-
figure 7-64 page 153 indicates                      16 06:24:30Z) Beacon
that latebit(0), but here it                        report, being an RRM
indicates a success bit?                            measurement, cannot be
                                                    "Late" per 7.3.2.22
Should dot11FrameRprtRSNI      modify accordingly   AGREE (ARCHITECTURE:            EDITOR
be dot11FrameRprtLastRSNI                           2009-07-16 06:25:30Z)
to make more consistent with
section 7.3.2.22.7 page 163
line 33 (figure 7-68g)

Should dot11FrameRprtRSNI      modify accordingly   AGREE IN PRINCIPLE              EDITOR
be dot11FrameRprtLastRSNI                           (ARCHITECTURE: 2009-11-
to make more consistent with                        16 15:54:34Z) - Change
section 7.3.2.22.7 page 163                         dot11FrameRprtRSNI to
line 33 (figure 7-68g)                              "dot11FrameRprtLastRSNI"
                                                    globally.
the measurement report         modify accordingly   DISAGREE                        EDITOR
mode in section 7.3.2.22                            (ARCHITECTURE: 2009-07-
figure 7-64 page 153 indicates                      16 06:26:03Z) Frame report,
that latebit(0), but here it                        being an RRM measurement,
indicates a success bit?                            cannot be "Late" per 7.3.2.22
the measurement report         modify accordingly    DISAGREE                           EDITOR
mode in section 7.3.2.22                             (ARCHITECTURE: 2009-07-
figure 7-64 page 153 indicates                       16 06:26:54Z) STAStatistics,
that latebit(0), but here it                         being an RRM measurement,
indicates a success bit?                             cannot be "Late" per 7.3.2.22

the measurement report         modify accordingly    DISAGREE                           EDITOR
mode in section 7.3.2.22                             (ARCHITECTURE: 2009-07-
figure 7-64 page 153 indicates                       16 06:27:49Z) LCI report,
that latebit(0), but here it                         being an RRM measurement,
indicates a success bit?                             cannot be "Late" per 7.3.2.22

It is more consistent with     modify accordingly    AGREE (ARCHITECTURE:         EDITOR
Reporting Reason field in                            2009-07-16 06:28:41Z)
Figure 7-68q, section                                replace as noted in comment.
7.3.2.22.10 page 174 line 5 if
averageTrigger,
consecutiveTrigger and
delayTrigger are used instead
of averageError,
consecutiveError and
delayError
the measurement report         modify accordingly    DISAGREE                           EDITOR
mode in section 7.3.2.22                             (ARCHITECTURE: 2009-07-
figure 7-64 page 153 indicates                       16 06:28:57Z)
that latebit(0), but here it                         TransmitStream report, being
indicates a success bit?                             an RRM measurement,
                                                     cannot be "Late" per 7.3.2.22

table 7-43b in section 7.3.2.37 modify accordingly   AGREE IN PRINCIPLE           EDITOR
page 198 line 50 has                                 (ARCHITECTURE: 2009-11-
Measurement Pilot                                    17 22:16:52Z)change Table 7-
Transmission information                             43b from "Measurement Pilot
(refer to section 7.3.2.42)                          Transmission information" to
instead of Measurement Pilot                         "Measurement Pilot
interval (refer to section                           Transmission"
7.3.1.18)
Page 248-252, 578, 727 are      See comment.         AGREE IN PRINCIPLE                 EDITOR
empty pages. Shall be deleted.                       (EDITOR: 2009-07-02
                                                     11:00:29Z)

                                                     Delete superfluous pages at
                                                     the end of Clause 7.

                                                     Note to commenter: these
                                                     pages may come back.
                                                     Frame is set to delete
                                                     superflous pages on save,
                                                     but this doesn't always appear
                                                     to work, for reasons not know
                                                     to the REVmb editor. The
                                                     other cited pages are required
                                                     to allow the following clause to
                                                     start on a right hand page,
                                                     and are deliberate.
I don’t think we need to           1. P230l62 - P231L28 and        DISAGREE                      EDITOR
include Optional Subelements       P232L14-L45 shall be            (ARCHITECTURE: 2009-11-
field in this frame to make this   removed.                        16 15:41:04Z) The description
frame to be extensible, for the    2. Remove the Optional          of the frame includes the
following reasons:                 subelements field from Figure   optional subelements to make
1. From my understanding, all      7-101c and Figure 7-101d        the description complete.
action frames (management
frames) can be inserted
additional information element
when it is needed in future
amendments.
2. Vendor Specific element
can be inserted in any action
frames according to 7.2.3.12.
There is no need to restate
here.
This comment shall be
applied to 7.4.6.4 as well.


Vendor Specific element may         L15: add VendorSpecificInfo    AGREE (ARCHITECTURE:         EDITOR
be included in all action          in MLME-                        2009-07-16 06:30:06Z)
frames according to 7.2.3.12.      LINKMEASURE.request. Also
                                    VendorSpecificInfo shall be
                                   added in MLME-
                                   LINKMEASURE.confirm.
It appears that only two           Add MLME-                       DISAGREE                        EDITOR
primitives MLME-                   LINKMEASURE.indication          (ARCHITECTURE: 2009-11-
LINKMEASURE.request and            and MLME-                       18 20:37:24Z) The
MLME-                              LINKMEASURE.request             commentor is encouraged to
LINKMEASURE.confirm are            primitives.                     provide more details of any
defined. Indication primitive                                      proposed improvement, but
and Response primitives shall                                      without the details of what is
be defined.                                                        proposed, the group cannot
                                                                   evaluate the technical merit at
                                                                   this time.

It is unnecessary to               1. Add SSID in Figure 7-101e    DISAGREE                      EDITOR
include/define Optional            and remove the Optional         (ARCHITECTURE: 2009-11-
Subelements field. For the         subelements field from Figure   16 15:41:04Z) The description
following reasons:                 7-101e.                         of the frame includes the
1. SSID element can be             2. P233L46 change "SSID         optional subelements to make
optionally included in             subelement can be included      the description complete.
Neighbor Report Request            in a Neighbor Report Request
frame.                             frame ..." to "SSID element
2. all action frames               can be included in a Neighbor
(management frames) can be         Report Request frame...".
inserted additional information    3. remove P233 L9-L43.
element when it is needed in
the future amendments.
3. Vendor Specific element
can be inserted in any action
frames according to 7.2.3.12.
There is no need to restate
here.
It is unnecessary to              1. Add Multiple BSSID in          DISAGREE                      EDITOR
include/define Optional           Figure 7-101g and remove          (ARCHITECTURE: 2009-11-
Subelements field, for the        the Optional subelements field    16 15:41:04Z) The description
following reasons:                from Figure 7-101g.               of the frame includes the
1. Multiple BSSID element         2. remove P235 L55 to             optional subelements to make
can be optionally included in     P236L27.                          the description complete.
Neighbor Report Request
frame, directly.
2. all action frames
(management frames) can be
inserted additional information
element when it is needed in
the future amendments.
3. Vendor Specific element
can be inserted in any action
frames according to 7.2.3.12.
There is no need to restate
here.

  Define a generic format for     Define a generic format for       DISAGREE                      EDITOR
the extensible element to         the extensible element to         (ARCHITECTURE: 2009-11-
include optional subelements.     include optional subelements.     16 15:24:56Z) the commentor
If any new element (defined in    Commenter would be                is encouraged to provide
11k, 11r, 11y and any future      interested in preparing a         more details of any proposed
element) is the extensible        submission if the idea is         improvement, but without the
element, it shall be extensible   accepted in principle.            details of what is proposed,
by including optional                                               the group cannot evaluate the
subelements. IMHO, all new                                          technical merit at this time.
elements defined in 11k, 11r,
and 11y shall be extensible.


Why are the following             clarify it, or include optional   DISAGREE                        EDITOR
elements extensible?              subelements.                      (ARCHITECTURE: 2009-11-
RCPI, RSNI, BSS Average                                             18 20:38:13Z) The
Access Delay, Antenna                                               commentor is encouraged to
Information, BSS Available                                          provide more details of any
Admission Capacity, BSS AC                                          proposed improvement, but
Access Delay.                                                       without the details of what is
                                                                    proposed, the group cannot
                                                                    evaluate the technical merit at
                                                                    this time.
According to 7.2.3.12, Vendor see comment.                          AGREE (ARCHITECTURE:            EDITOR
Specific element may be                                             2009-07-16 06:30:54Z)
included in all action frames.
The VendorSpecificInfo
parameter shall be added in
all primitives defined in
10.3.25.

According to 7.2.3.12, Vendor see comment.                          AGREE (ARCHITECTURE:         EDITOR
Specific element may be                                             2009-07-16 06:31:12Z)
included in all action frames.
The VendorSpecificInfo
parameter shall be added in
all primitives defined in
10.3.27.
Is Vendor-Specific action          Define a public vendor-           DISAGREE                        EDITOR
frame a class 1 frame or class     specific action, or clarify it.   (ARCHITECTURE: 2009-11-
3 action frame? If it is class 3   Commenter would be                18 20:39:33Z) The
action frame, a public Vendor-     interested in preparing a         commentor is encouraged to
Specific action frame shall be     submission if the idea is         provide more details of any
defined.                           accepted in principle.            proposed improvement, but
                                                                     without the details of what is
                                                                     proposed, the group cannot
                                                                     evaluate the technical merit at
                                                                     this time.
I think the service "Radio         L39, change "Radio                DISAGREE (GEN: 2009-11-         EDITOR
measurement" shall be              measurement" to "Radio            18 18:39:50Z)There is no
applied to "RRM facility only",    measurement (RRM facility         definition of the meaning of
and "DSE" shall be applied         only)". L40 and L63: Change       the "<something> facility only"
"DSE facility only".               "DSE" to "DSE (DSE facility       terms that occur in these
                                   only)".                           related subclauses. The
                                                                     proposed change corrects no
                                                                     error and introduces the
                                                                     undefined terms "RRM facility"
                                                                     and "DSE facility"

Vendor Specific Action frame       change "Any valid individual      AGREE (ARCHITECTURE:         EDITOR
could be transmitted as a          MAC address" to "Any valid        2009-11-18 20:26:42Z)
broadcast frame. Peer MAC          individual MAC
Address could be group MAC         address, or any valid group
address.                           MAC address." Apply the
                                   same change to P539L23.




Extended Channel Switch            change "Any valid individual      AGREE (ARCHITECTURE:         EDITOR
frame can be transmitted as a      MAC address" to "Any valid        2009-11-18 20:27:19Z)
broadcast frame. Peer MAC          individual MAC
Address could be group MAC         address, or any valid group
address.                           MAC address."
Channelswitch frame can be          change "Any valid individual   DISAGREE                       EDITOR
transmitted as a broadcast          MAC address" to "Any valid     (ARCHITECTURE: 2009-11-
frame. Peer MAC Address             individual MAC                 16 16:00:59Z) The Peer MAC
could be group MAC address.         address, or any valid group    address is the sender of the
                                    MAC address."                  frame even if the Channel
                                                                   Switch is sent to the Group.

The distinction between          Clarify use of                   DISAGREE (MAC: 2009-10-         EDITOR
NonERP_Present and               NonERP_present bit or            23 16:13:46Z) -
Use_Protection bit is not clear. replace all occurances of        NonERP_Present is
                                 NonERP_present bit with          informative to the receiver in
                                 Use_Protection bit               that a STA may decide to use
                                                                  protection, but is not required
                                                                  to. Use_Protection is
                                                                  mandatory and requires that
                                                                  the receiver use protection for
                                                                  transmissions. The proposed
                                                                  comment resolution does not
                                                                  include sufficient detail to
                                                                  clarify this behavior.
                                                                  However, the commenter is
                                                                  encouraged to bring a
                                                                  submission to TGmb for
                                                                  consideration and discussion
                                                                  in a future ballot.
The following text                  Add the following text at the DISAGREE                        EDITOR
"STAs in an infrastructure          begenning of clause 11.1.2.3 (ARCHITECTURE: 2009-11-
network shall only use other        "While doing scan STA may     18 20:54:28Z) The text “in an
information in received             process all the received      infrastructure network”
Beacon frames, if the BSSID         beacons, while not doing scan already means the STA is
field is equal to the MAC           the following rules apply."   associated, and therefore is
address currently in use by                                       not doing a scan.
the STA contained in the AP
of the BSS.
STAs in an IBSS shall use
other information in any
received Beacon frame for
which the IBSS subfield of the
Capability field is set to 1, the
content of the SSID element
is equal to the SSID of the
IBSS, and the TSF value is
later than the receiving STA’s
TSF timer." disallows
processing of beacon
information received from
other BSS.
There might be some
information element contained
in the received beacon that
should be processed
irrespective of BSS, e.g., ERP
information element (clause
7.3.2.13). In partiuclar,
7.3.2.13 statement that "A
NonERP infrastructure or
independent BSS is
overlapping (a NonERP BSS
In the following text "The           Extend the WEP rules for RSN      AGREE IN PRINCIPLE (MAC: EDITOR
length of a fragment shall                                             2009-10-23 16:01:16Z) -
never be larger than                                                   Change cited sentence to
dot11FragmentationThreshold                                            read: "The length of a
unless WEP is invoked for the                                          fragment shall never be larger
MPDU. If WEP is active for                                             than
the MPDU, then the MPDU                                                dot11FragmentationThreshold
shall be expanded by IV and                                            unless security encapsulation
ICV (see 8.2.1); this may                                              is invoked for the MPDU. If
result in a fragment larger                                            security encapsulation is
than                                                                   active for the MPDU, then the
dot11FragmentationThreshold.                                           MPDU shall be expanded by
", it is not clear if this appies to                                   the encapsulation overhead
TKIP/AES as well?                                                      and this may result in a
                                                                       fragment larger than
                                                                       dot11FragmentationThreshold.
                                                                       "

The following text "The length      Correct the definition of          AGREE (MAC: 2009-09-24           EDITOR
of a fragment shall never be        dot11FragmentationThreshold        21:43:49Z) - Change
larger than                         to allow security fields like IV   definition of
dot11FragmentationThreshold         and ICV to be not counted for      dot11FragmentationThreshold
unless WEP is invoked for the       the threshold                      to read: "This attribute
MPDU. If WEP is active for                                             specifies the current
the MPDU, then the MPDU                                                maximum size, in octets, of
shall be expanded by IV and                                            the MPDU that may be
ICV (see 8.2.1); this may                                              delivered to the security
result in a fragment larger                                            encapsulation. An MSDU is
than                                                                   broken into fragments if its
dot11FragmentationThreshold.                                           size exceeds the value of this
", is not consistent with the the                                      attribute after adding MAC
definition of MIB                                                      headers and trailers. Fields
dot11FragmentationThreshold                                            added to the frame by security
clause Annex D text "This                                              encapsulation are not counted
attribute shall specify the                                            against the limit specified by
current maximum size, in                                               this attribute. An MSDU or
octets, of the MPDU that may                                           MMPDU is fragmented when
be delivered to the PHY. An                                            the resulting frame has an
MSDU shall be broken into                                              individual address in the
fragments if its size exceeds                                          Address1 field, and the length
the value of this attribute after                                      of the frame is larger than this
adding MAC headers and                                                 threshold, excluding security
trailers. An MSDU or MMPDU                                             encapsulation fields."
shall be fragmented when the
resulting frame has an
individual address in the
Address1 field, and the length
of the frame is larger than this
threshold." Similar text is
present in Annex-D, pp 1351,
line 19
"STAs receiving Probe           Delete "STAs receiving Probe    AGREE IN PRINCIPLE              EDITOR
Request frames shall respond    Request frames shall respond    (EDITOR: 2009-07-03
with a probe response when      with a probe response when      13:19:17Z)
the SSID in the probe request   the SSID in the probe request   Aggree that the paras at line 7
is the wildcard SSID or         is the wildcard SSID or         and 16 contain duplicate text.
matches the specific SSID of    matches the specific SSID of     The entire contents of the
the STA. Probe Response         the STA." and                   para at line 7 is reproduced in
frames shall be sent as         Delete "Probe Response          line 30 on.
directed frames to the          frames shall be sent as
address of the STA that         directed frames to the          The cleanest solution is to
generated the probe request.    address of the STA that         delete the whole para at line
The probe response shall be     generated the probe request.    7.
sent using normal frame         The probe response shall be
transmission rules. An AP       sent using normal frame         Editor: Delete the para at line
shall respond to all probe      transmission rules. An AP       7: "Probe Response Frames
requests meeting the above      shall respond to all probe      shall be sent ... request."
criteria. In an IBSS, the STA   requests meeting the above
that generated the last         criteria. In an IBSS, the STA
Beacon frame shall be the       that generated the last
STA that responds to a probe    Beacon frame shall be the
request." is redundant.         STA that responds to a probe
Compare with lines 7-11.        request."


The sentence "When all ACs Clarify.                             DISAGREE (MAC: 2009-09-           EDITOR
associated with the non-AP                                      25 03:29:46Z) - The first cited
STA are delivery-enabled, the                                   sentence refers to delivery-
More Data field shall be set to                                 enabled ACs and the second
indicate the presence of                                        cited sentence refers to non-
further buffered MSDUs or                                       delivery-enabled ACs. There
management frames                                               is no consistency problem.
belonging to delivery enabled
ACs" is not consistent with the
previous sentence "For a non-
AP STA using U-APSD, the
More Data field shall be set to
indicate the presence of
further buffered MSDUs or
management frames that do
not belong to delivery-enabled
ACs.".
The definitions of class 1 data Clarify.                            AGREE IN PRINCIPLE (GEN: EDITOR
frame and class 3 data frame                                        2009-11-19 05:15:59Z) The
are not clear especially in                                         Editor is instructed to
IBSS networks. A data frame                                         incorporate into the REVmb
with FromDS = ToDS = 0                                              draft document 11-09/705r4.
belongs to class 1 in IBSS                                          (https://mentor.ieee.org/802.11
and class 3 in other cases.                                         /dcn/09/11-09-0705-04-000m-
The question is how to                                              proposed-corrections-to-11-3-
determine whether a data                                            sta-authentication-and-
frame belongs to class 1 in                                         association.doc)
the IBSS or not when STA is
in state 1? For example, if
STA resets, it may lose state
information and subsequently
a data frame received from
peer STA cannot be marked
as IBSS or BSS frame, and
therefore cannot be classified
whether belongs to class 1 or
3.

Paragraph 1 and Paragraph 2 Delete paragraph 2.                     AGREE (EDITOR: 2009-07-   EDITOR
are identical.                                                      03 13:25:20Z)

"A STA shall be capable of        Modify "A STA shall be            AGREE IN PRINCIPLE (MAC: EDITOR
receiving fragments of            capable of receiving              2009-09-22 19:09:38Z).
arbitrary length." Here instead   fragments of arbitrary length."   Change "A STA shall be
of allowing arbirarty length      as "A STA shall be capable of     capable of receiving
frame reception capability,       receiving fragments of            fragments of arbitrary length."
STA should check if the           arbitrary length that is less     to read "A STA shall be
length is valid < Max MSDU        than max allowed MSDU             capable of receiving
size (2304 octets). Similar       size." Modify figures 7-1, and    fragments of arbitrary length
issues exist in                   7-18 appropriately                that is less than maximum
Clause 7.1.2 (pp 71, ln 55):                                        allowed MSDU size, plus any
MSDU size is not consistent                                         encapsulation headers."
with figure 7-1                                                     Figures 7-1 and 7-18 show a
Clause 7.2.3.0a (pp 90):                                            strikethrough for Frame Body
Frame body size is not                                              length, and should be
consistent with Figure 7-18                                         corrected to be "2324".
The last paragraph in this          One solution is to replace          DISAGREE (MAC: 2009-09-      EDITOR
clause states that "A STA that      PHY-RX-START.indication             24 21:05:19Z) - For
used information from an RTS        with PHY-CCA.indication             CCK/DSSS STAs, the
frame as the most recent            (BUSY)                              (CTS_Time) included in the
basis to update its NAV             Replace text with "A STA that       calculation provides enough
setting is permitted to reset its   used information from an RTS        time to protect the OFDM
NAV if no PHY-                      frame as the most recent            exchange because the OFDM
RXSTART.indication is               basis to update its NAV             exchange will be transmitted
detected from the PHY during        setting is permitted to reset its   at a higher rate than the
a period with a duration of (2      NAV if no PHY-CCA.indication        RTS/CTS.
× aSIFSTime) + (CTS_Time)           (BUSY) is detected..."
+ aPHY-RX-START-Delay +
(2 × aSlotTime) starting at the
PHY-RXEND.indication
corresponding to the detection
of the RTS frame. The
“CTS_Time” shall be
calculated using the length of
the CTS frame and the data
rate at which the RTS frame
used for the most recent NAV
update was received."
If RTS frame is sent at a
CCK/DSSS rate to protect
subsequent MPDUs sent at
OFDM rates in presence of
11b STAs, the 11b STAs will
not set their NAV due to lack
of PHY-RXSTART.indication
after the "duration". This may
defeat the purpose of using
RTS in the first place.
"A TXOP limit value of 0            Clarify, or replace "A TXOP         AGREE IN PRINCIPLE (MAC: EDITOR
indicates that a single MSDU        limit value of 0 indicates that a   2009-10-16 15:15:43Z) -
or MMPDU, in addition to a          single MSDU... " with "A            Insert "When the TXOP limit
possible RTS/CTS exchange           TXOP limit value of 0               is non-zero, . . ." at the
or CTS to itself, may be            indicates that a single             beginning of the paragraph on
transmitted at any rate for         MPDU..."                            page 396 line 50.
each TXOP."
As per the fourth paragraph
"A STA shall fragment a
unicast MSDU so that the
transmission of the first
MPDU of the TXOP does not
cause the TXOP limit to be
exceeded at the PHY rate
selected for the initial
transmission attempt ...".
MSDU may consist of multiple
fragments and therefore it
would be appropriate to
replace text "A TXOP limit
value of 0 indicates that a
single MSDU " with "A TXOP
limit value of 0 indicates that a
single MPDU. "
The list above this text "If theNumber the list (list items a-d)   AGREE IN PRINCIPLE             EDITOR
backoff procedure is invoked    above the text "If the backoff     (EDITOR: 2009-07-02
for reason a) above, the value  procedure is invoked for           15:44:12Z) - See resolution to
of CW[AC] shall be left         reason a) above, the value of      CID 1651, which addresses
unchanged. If the               CW[AC] shall be left               this issue.
backoff procedure is invoked    unchanged. If the
because of reason b) above,     backoff procedure is invoked
the value of CW[AC] shall be    because of reason b) above,
reset to CWmin[AC]." is not     the value of CW[AC] shall be
numbered.                       reset to CWmin[AC]."
The list above this text "If theNumber the list (list items a-d)   AGREE IN PRINCIPLE             EDITOR
backoff procedure is invoked    above the text "If the backoff     (EDITOR: 2009-07-02
because of a failure event      procedure is invoked for           15:44:33Z) - See resolution to
[either reason c) or d) above],"reason a) above, the value of      CID 1651, which addresses
is not numbered.                CW[AC] shall be left               this issue.
                                unchanged. If the
                                backoff procedure is invoked
                                because of reason b) above,
                                the value of CW[AC] shall be
                                reset to CWmin[AC]."
The sentence "The RA field of Modify sentence "The RA field        DISAGREE (EDITOR: 2009-        EDITOR
the frames shall be the         of the frames shall be the         07-03 10:43:13Z)
recipient’s unicast address.", recipient’s unicast                 The term "recipient" in this
in the first paragraph does not address." in the first             context is unambiguous, as
clearly state that whether RA paragraph with "The RA field         determined by the last
is the ADDBA recipient or not. of the frames shall be the          sentence of 9.10.1: "In this
To make pragraph consistent ADDBA recipient’s unicast              subclause, the STA with data
this RA shall be ADDBA          address."                          to send using the Block Ack
recipient.                                                         mechanism is referred to as
                                                                   the originator, and the
                                                                   receiver of that data as the
                                                                   recipient. "
It seems the sentence "After       Modify as follows-         AGREE IN PRINCIPLE (MAC: EDITOR
setting up for the Block                                      2009-11-13 19:43:23Z) -
                                   "If no protective mechanism is
exchange following the                                        Change cited text to read:
                                   used, the first frame that is
procedure in 9.10.2, the                                      "After setting up for the Block
                                   sent in the block shall be sent
originator may transmit a                                     exchange following the
                                   as a QoS Data frame with Ack
block of QoS data frames           Policy subfield in the QoS procedure in 9.10.2 (Setup
separated by SIFS period," in      Control field set to Normaland modification of the Block
paragraph one conflicts with                                  Ack parameters), and having
                                   Ack. The duration field of such
the sentence "If no protective                                gained access to the medium
                                   a first frame should be set so
mechanism is used, then the                                   and established protection, if
                                   that the response frame shall
first frame that is sent as a                                 necessary, the originator may
                                   have the Duration field to set
block shall have a response        NAV with appropriate valuestransmit a block of QoS data
frame and shall have the           at all STAs in the BSS."   frames separated by SIFS
Duration field set so that the                                period, with the total number
NAVs are set to appropriate                                   of frames not exceeding the
values at all STAs in the                                     Buffer Size subfield value in
BSS." in paragraph four.                                      the associated ADDBA
It is assumed that after setting                              Response frame and .subject
up Block Ack, transmitter                                     to any additional duration
transmits a series of frames                                  limitations based on the
each separated by SIFS                                        channel access mechanism.
without any immediate Ack,                                    Each of the frames shall have
however, later transmitter                                    the Ack Policy subfield in the
requests for a response frame                                 QoS Control field set to Block
 from the receiver.                                           Ack. The RA field of the
                                                              frames shall be the recipient’s
                                                              unicast address. The
                                                              originator requests
                                                              acknowledgment of
                                                              outstanding QoS data frames
                                                              by sending a BlockAckReq
                                                              frame. The recipient shall
It would be more appropritate Move sentence "The More         AGREE a PRINCIPLE
                                                              maintainIN Block Ack record     EDITOR
to move sentence "The More Data field is set to 0 in all      (EDITOR: 2009-07-01
Data field is set to 0 in all  other directed frames" to the  06:38:46Z)
other directed frames" at the  end of this subclause.         Move the last para of 7.1.3.1.7
end of this subclause.                                        to before the cited para. This
                                                              ensures that all specification
                                                              for directed frames is
                                                              described before the
                                                              "otherwise". The para
                                                              following the cited para is
                                                              unrelated as it refers to
                                                              broadcast, and should
                                                              therefore not separate the
                                                              directed cases and the
                                                              directed "other" statement.
Table 7-58, allows             Remove Disassociation frame AGREE IN PRINCIPLE                 EDITOR
disassociation frame in an     in case of IBSS; Add a dash in (ARCHITECTURE: 2009-11-
IBSS. Why is this allowed      IBSS column correspoding to 16 15:49:39Z) - Note that
here? In fact subclause 10.3.8 row disassociation.            Clause 7.5 is removed by
and 11.3.2.6 do not describe                                  TGn, so no change is required
how this is used in IBSS.                                     by the Editor.
"For the purpose of                "For the purpose of              AGREE (MAC: 2009-08-06         EDITOR
determining the proper AC for      determining the proper AC for 22:51:02Z)
an RTS frame, the RTS frame        an RTS frame, the RTS frame
shall inherit the UP of the data   shall inherit the UP of the data
or management frame(s) that        or AC of management
are included in the frame          frame(s) that are included in
exchange sequence where            the frame exchange sequence
the RTS is the first frame."       where the RTS is the first
UP may not be an appropriate       frame."
term for management frames.


There is no rule to derive AC      Replace ""For the purpose of       AGREE (MAC: 2009-08-06       EDITOR
for CTS2Self frame.                determining the proper AC for      22:49:05Z)
                                   an RTS frame, the RTS frame
                                   shall inherit the UP of the data
                                   or management frame(s) that
                                   are included in the frame
                                   exchange sequence where
                                   the RTS is the first frame."
                                   with
                                   "When the first frame in the
                                   frame exchange sequence is
                                   an RTS or CTS, the RTS or
                                   CTS frame shall inherit the
                                   UP of the data or AC of
                                   management frame(s) of the
                                   frame exchange sequence."
Grammar Error in table 7-28:       It should be "….requesting the     AGREE (EDITOR: 2009-07-      EDITOR
The transmitting STA is            destination STA not send           02 06:12:36Z)
indicating to the destination      autonomous…." --- delete the
STA that it can accept             "to"
measurement requests and is
requesting the destination
STA not to send autonomous
or triggered measurement
reports of the type indicated in
the Measurement Type field
(see NOTE)."

Grammar Error: "A STA shall        Change to "A STA shall report AGREE (EDITOR: 2009-07-           EDITOR
report it is incapable a           it is incapable of performing a 15 02:29:03Z)
measurement request if any         measurement request if any
of the following conditions        of the following conditions
exists:"                           exists:" -- add "of performing"

The specification of STA       Change as shown in doc:11-             AGREE (GEN: 2009-11-19          EDITOR
authentication and association 09/0705                                05:12:46Z) instruct the editor
in section 11.3 is incomplete,                                        to incorporate into the REVmb
ambiguous, inconsistent and                                           draft document 11-09/705r4.
sometimes just wrong.                                                 (https://mentor.ieee.org/802.11
                                                                      /dcn/09/11-09-0705-04-000m-
                                                                      proposed-corrections-to-11-3-
                                                                      sta-authentication-and-
                                                                      association.doc)
The word "frame" is used too        Add "Also known as a frame."     DISAGREE (EDITOR: 2009-          EDITOR
loosely. Sometimes it refers        to the definition of MPDU in     07-27 10:04:41Z)
to a MSDU or MMPDU, rather          section 3.
than an MPDU forming part of        Throughout the spec, change      This was discussed at length
a fragmented MSDU or                uses of "[data/management]       in TGmb, and no consensus
MMPDU. This affects, for            frame" to "MSDU or               was present for making any
example, whether the PM             MMPDU"/"MMPDU"/"MSDU"            changes. (see 11-09-0714r2
mode can change during a            where appropriate.               for background).
fragmented MSDU or MMPDU.           Simplify "Management frame
                                    of subtype Foo" to "Foo          The proposed change "as
                                    MMPDU".                          appropriate" gives inadequate
                                                                     detail. Changing from a frame
                                                                     to an MSDU/MMPDU is a
                                                                     technical change. The
                                                                     commenter is invited to
                                                                     provide specific details about
                                                                     which locations need to be
                                                                     changed as technical
                                                                     comments in a later ballot.


The definitions of "unicast"        In the two definitions, remove   AGREE IN PRINCIPLE (MAC: EDITOR
and "multicast" are unclear;        the "or control frame"s and      2009-09-23 03:58:06Z)
this makes understanding the        replace the "(RA)"s with         Review all uses of broadcast,
exact intent of e.g. "unicast       "(Address 1)"s.                  multicast and unicast and
Probe Request" difficult.                                            replace as follows:
Specifically, it is not clear how                                    (1) "Unicast" changes to
these are defined for                                                "individual" or "individually
MMPDUs, and there is a                                               addressed" according to
confusing special mention of                                         context
control frames as distinct from                                      (2) "multicast", "broadcast /
other MPDUs.                                                         multicast" or "broadcast or
                                                                     multicast" changes to "group"
                                                                     or "group addressed"
                                                                     according to context. This
                                                                     specifically applies to MIB
                                                                     variables of the form
                                                                     {something}Multicast{somethin
                                                                     gelse}, which change to
                                                                     {something}Group{somethinge
                                                                     lse}
                                                                     (3) "broadcast" remains the
                                                                     term to use when specifically
                                                                     referring to the broadcast
                                                                     address

                                                                     See also CID 1086.
The rules for the BSSID in      Change as follows:               AGREE IN PRINCIPLE               EDITOR
management frames are           The BSSID of the                 (ARCHITECTURE: 2009-11-
unclear. Specifically, the      management frame is              16 15:30:39Z) - Change to:
BSSID to use in an ESS when     determined as follows:           "The BSSID of the
not associated, and the         a) If the STA is an AP or is     management frame is
meaning of "a member of an      associated withtransmitting      determined as follows:
IBSS" and "a specific BSSID",   the management frame to an           a) If the STA is an AP or is
are unclear.                    AP, the BSSID is the address     transmitting the management
                                currently in use by the STA      frame to an AP, the BSSID is
                                contained in the AP.             the address currently in use
                                b) If the STA is transmitting    by the STA contained in the
                                the management frame to one      AP.
                                or morea members of an               b) If the STA is
                                IBSS, the BSSID is the BSSID     transmitting the management
                                of the IBSS.                     frame to one or more
                                c) In management frames of       members of an IBSS, the
                                subtype Probe Request, the       BSSID is the BSSID of the
                                BSSID is either a specific       IBSS.
                                BSSID as specified in (a) or          c) In management frames
                                (b), or the wildcard BSSID as    of subtype Probe Request,
                                defined in the procedures        the BSSID is either a specific
                                specified in 11.1.3 (Acquiring   BSSID as specified in (a) or
                                synchronization, scanning).      (b), or the wildcard BSSID as
                                                                 defined in the procedures
                                                                 specified in 11.1.3 (Acquiring
                                                                 synchronization, scanning)."
TGmb-agreed changes to           Change the draft as           AGREE IN PRINCIPLE             EDITOR
TCLAS element text missing       previously agreed in CIDs 48- (EDITOR: 2009-08-06
from D1.0.                       50. See Doc: 11-08/1127r18    13:01:12Z) -
                                                               Make changes as shown for
                                                               CID 48 in document 11-08-
                                                               1127r20 as amended thus:
                                                               1. The inserted table is an
                                                               octet-aligned structure. Sizes
                                                               are in octets.
                                                               2. Remove the note in square
                                                               brackets.

                                                                   CID 49 proposes adding "as
                                                                   in IEEE 802.1Q-2003 [Bxx]",
                                                                   but the text describing the
                                                                   Type 2 classifier states: "For
                                                                   Classifier Type 2, the
                                                                   Classifier Parameter is the
                                                                   IEEE 802.1Q-2003 [B14]
                                                                   VLAN Tag TCI." Adding "as
                                                                   in IEEE 802.1Q-2003 [Bxx]"
                                                                   would be redundant. Instead
                                                                   add the following:
                                                                   "The endianness of the
                                                                   802.1Q VLAN TCI field is as
                                                                   defined IEEE 802.1Q-2003
                                                                   [B14] for the VLAN Tag TCI."

                                                               Likewise for CID 50, add after
                                                               "For Classifier Type 0, ... and
                                                               Type ("Ethernet" [B4])." add:
                                                               "The endianness of the Type
It is not clear what the         Add "The Power Management field is as defined in Ethernet EDITOR
                                                               AGREE IN PRINCIPLE (MAC:
meaning of the PM bit is in      bit shall be ignored in frame 2009-09-25 03:33:24Z) -
MSDUs/MMPDUs which are           exchanges initiated by the AP Insert the text: "The Power
not acknowledged.                or which do not elicit an ACK Management bit shall be
                                 from the AP." to the          ignored in frame exchanges
                                 penultimate paragraph of this initiated by the AP. The non-
                                 section.                      AP STA shall not change
                                                               power management state
                                                               using a frame exchange that
                                                               does not receive an ACK."
                                                               before the last sentence in the
                                                               penultimate paragraph of
                                                               11.2.1.1.

It is not clear how the wildcard Add "When the wildcard            AGREE (ARCHITECTURE:             EDITOR
BSSID is to be used.             BSSID is used in such a           2009-07-16 06:31:51Z)
                                 frame, the Address 1 (DA)
                                 field is also set to all 1s to
                                 indicate the broadcast
                                 address." to the end of the
                                 last paragraph of this section.
Disassociation,                    Change so that only Action       AGREE (MAC: 2009-09-30          EDITOR
Deauthentication and Probe         frames (both unicast and         14:53:09Z)
Response frames should not         group) are buffered.
be buffered.




This section does not account      Change to cover all types and    DISAGREE (MAC: 2009-11-         EDITOR
for U-APSD, e.g. if there are      scenarios of power               18 20:50:05Z) The
MSDUs on delivery-enabled          management, or delete            commentor is encouraged to
ACs only but not all ACs are       sentences which duplicate        provide more details of any
delivery-enabled, then the TIM     information in other sections,   proposed improvement, but
will not signal their presence.    and replace with general         without the details of what is
                                   statement.                       proposed, the group cannot
                                                                    evaluate the technical merit at
                                                                    this time.
Category code 17 needs to be Have a dedicated line for 17,          AGREE (ARCHITECTURE:            EDITOR
reserved in a permanent way, and inform the assignment              2009-07-16 06:32:10Z)
as it is used for a widely-  authority.
deployed spec (*cough* WMM
*cough*).

The use of underscores in the      Replace underscores with         AGREE (EDITOR: 2009-07-         EDITOR
MLME-                              hyphens.                         01 10:07:03Z)
RESOURCE_REQUEST,
MLME-
RESOURCE_REQUEST_LOC
AL and MLME-
REMOTE_REQUEST
primitives is inconsistent with
existing usage.
The conventions described in       Extend section 7.1.1 to          DISAGREE (EDITOR: 2009-         EDITOR
7.1.1 are not clear and            describe conventions             07-27 08:05:10Z)
complete enough. E.g.:             pertaining to the term "data     The proposed change does
- Does "data frame" mean           frame" and related terms.        not include enough detail to
"frame of type Data" or "frame     Ensure that text in other        determine what specific
of subtype Data (+ whatever)",     sections conforms to these       changes would resolve this
and if the latter (i.e. excludes   conventions.                     comment.
the CF-only ones) does it or
does it not include QoS?                                            The commenter is invited to
Note a distinction between                                          submit additional detail in a
"data frame" and "Data frame"                                       subsequent ballot.
is poor, because the
distinction vanishes at the
start of a sentence.
- Does "QoS data frame"
(note lowercase d) include
e.g. "QoS Null"?
Some of this may be helped
by saying "MSDU" instead of
"frame", but not all.
While I will be the first to claim   With a new revision, the     AGREE IN PRINCIPLE            EDITOR
that for a historical value, this    Annexes should be            (EDITOR: 2009-09-23
annex should be left in, I am        renumbered as necessary      18:33:57Z) - Add to Annex C
willing to concede and allow         and the deprecated and       immediately after the heading
not only it, but Annex E and P       reserved Annexes removed.    the following: "This Annex is
should be removed.                                                obsolete and may be removed
                                                                  in a future revision of this
                                                                  standard."

                                                                  Note, this allows time to
                                                                  determine if there is any
                                                                  behaviour in Annex C that
                                                                  needs to be moved to other
                                                                  Clauses.



The definition of QoS facility is Please clarify which function   DISAGREE (GEN: 2009-11-        EDITOR
vague. Does this implies that is mandatory for a QoS STA.         18 22:52:44Z) Functions that
the QoS facility means the                                        are mandatory for a QoS STA
use of EDCA as a minimum                                          are reported in the PICs and
set?                                                              defined in the Normative text.
If the STA is in IBSS, there
are no HCF and HCCA is not
used. However, if we look at
the PICS table in A.4.16, all
the HCCA rules are
mandatory for a QoS STA. It
looks like a contradiction.




The title of the clause reads        Rename the title of this     AGREE (EDITOR: 2009-07-      EDITOR
"IBSS ATIM frame format".            subclase to be ATIM frame    01 15:53:51Z)
However, other part of the           format.
specification call out this
frame as ATIM frame.
The first paragraph of 11.2.2.1      Remove the second            AGREE (EDITOR: 2009-07-      EDITOR
and the second paragraph of          paragraph of 11.2.2.1.       03 13:25:39Z)
11.2.2.1 contain the same
text. Must be a copy and
paste error.
The table in A.4.4.2 does not   Please clarify.                DISAGREE (GEN: 2009-11-         EDITOR
contain all the defined frame                                  18 02:01:58Z) The table in
types. Why is that?                                            A.4.4.2 only contains those
                                                               frame types that the baseline
                                                               standard and its amendments
                                                               have seen fit to describe here,
                                                                and the table makes no
                                                               claims to be totally inclusive.




Are square brackets             Add comma after "STAs" and     AGREE (EDITOR: 2009-07-           EDITOR
necessary?                      remove square brackets         01 14:32:57Z)

Belongs with text in 7.0a       Move paragraph to section      AGREE IN PRINCIPLE                EDITOR
                                7.0a and delete heading. The   (EDITOR: 2009-07-01
                                adjective compliant is         14:35:39Z)
                                superfluous.                   Move the cited text as
                                                               specicied.

                                                               Do not change "compliant".
                                                               This text was drafted during a
                                                               TGmb telecon. The text is the
                                                               best compromise between the
                                                               various views expressed to
                                                               this group, and the adjective,
                                                               while it may be superflous
                                                               according to the opinion of the
                                                               commenter, does no harm.


This sentence is inaccurate   Change to "…pending data,        AGREE (ARCHITECTURE:              EDITOR
since the sequence RTS-CTS- management or control              2009-07-16 06:32:28Z)
BAR-BA is permitted, i.e. the frame."
pending frame is a control
frame. See p420 l22.




The convention is to capitalize Capitalize as Probe Request.   AGREE (EDITOR: 2009-07-           EDITOR
references to specific frame                                   01 14:41:26Z)
type/subtypes
It is not clear why the             Remove reference or clarify    AGREE IN PRINCIPLE        EDITOR
reference to 9.9.3.0a is            with an additional statement   (EDITOR: 2009-07-01
needed. 9.9.3.0a makes              why the reader is being        14:48:40Z)
general statements about            directed to this section.      Remove the reference.
admission control and a
reference here seems out of
place.
This paragraph has clumsy           Rephrase paragragh as            AGREE (ARCHITECTURE:    EDITOR
phrasing. A) the use of "STA        follows "The TXOP Duration       2009-07-16 06:32:42Z)
desires for its next TXOP" in       Requested subfield is present
first sentence and then             in QoS data frames sent by
"calculated TXOP duration           non-AP STAs associated in a
requested" in the 3rd               BSS with bit 4 of the QoS
sentence. B) The sentence           Control field set to 0. The
describing when the field           TXOP Duration Requested
appears in a frame (sentence        subfield is an 8-bit field that
4) is mixed in with                 indicates the duration, in units
descriptions of content. C)         of 32 us, that the sending STA
The newly inserted sentence         determines it needs for its
("If the calculated TXOP... is      next TXOP for the specified
not a multiple of 32... that is a   TID. A value of 0 indicates
factor of 32 us") inconsistently    that no TXOP is requested for
uses the terms multiple and         the specified TID in the
factor (multiple is the correct     current SP. A non-zero value
term).                              represents a requested TXOP
                                    duration in the range 32 us to
                                    8160 us in increments of 32
                                    us. See 9.9.2.3.1."


For consistency with other          Insert section heading         DISAGREE (EDITOR: 2009- EDITOR
sections at this level, there       "7.2.2.0a Format of data       07-01 14:55:10Z) -
should be a section 7.2.2.0a        frames"                        While this may get an extra
inserted. I suspect this is                                        level of nesting when 11n is
awaiting 11n.                                                      incorporated, as the ballot
                                                                   draft stands, there is no error.
                                                                    Furthermore, introducing a
                                                                   single heading at any level is
                                                                   an error according to IEEE-SA
                                                                   style.
This statement is possibly        Change to "The format of a       AGREE (ARCHITECTURE:    EDITOR
incorrect and at a minimum        data frame is defined in         2009-07-16 06:33:07Z)
incomplete (that the format is    Figure 7-17. The Frame
dependent on the QoS              Control, Duration/ID, Address
subfield). In addition to being   1, Address 2, Address 3 and
dependent on the QoS              Sequence Control fields are
subfield, the format is           present in all data frame
dependent on the To DS and        subtypes. The presence of the
From DS fields (and Order         Address 4 field is determined
subfield when 11n is              by the setting of the To DS
incorporated). A more explicit    and From DS subfields in the
statement can be made up          Frame Control field (see
front concerning when certain     below). The QoS Control field
fields are present.               is present in when the QoS
                                  subfield of the Subtype field is
                                  set to 1." A similar statement
                                  concerning the HT Control
                                  field can be added when 11n
                                  is incorporated. Delete the
                                  last sentence in the second
                                  paragraph (p88 l45): "Data
                                  frames with a value of 0...".


It is not necessary to state      Change to "The format of a   AGREE (ARCHITECTURE:        EDITOR
that the management frame         management frame is defined 2009-07-16 06:33:22Z)
format is independent of the      in Figure 7-18. The Frame
subtype. It is sufficient, when   Control, Duration, Address 1
describing generic frame          (DA), SA, BSSID and
formats, to indicate that         Sequence Control fields are
certain fields may not be         present in all management
present (as is done for the       frame subtypes."
generic frame format and data
frames).
Duplicate 'present'               Unduplicate 'present'       AGREE (EDITOR: 2009-07-      EDITOR
                                                              01 15:52:43Z)
The bracketed text "(as well     Delete the text "(as well as      AGREE (ARCHITECTURE:    EDITOR
as STAs in IBSSs)" is not        STAs in IBSSs)" from this         2009-07-16 06:33:41Z)
comprehensive treatment of       paragraph. Add a subsequent
optional short preamble use in   paragraph dealing with IBSS
IBSSs. Also, this paragraph      operation following the
does not make sense when         paragraph on p107 l1: "STAs
applied to IBSS STAs;            within an IBSS set the Short
specifically reference to BSS    Preamble subfield in
at end of sentence and           transmitted Beacon frames
reference to Probe Response,     according to the setting of
Association Response, etc.       their
which are not used in an IBSS.   dot11ShortPreambleOptionIm
                                 plemented MIB atrribute. If
                                 this attribute is true, the Short
                                 Preamble subfield is set to 1,
                                 otherwise it is set to 0."
                                 Normative text is probably
                                 needed elsewhere to deal
                                 IBSSs where a mix of short
                                 capable and non-capable
                                 STAs operate (I suspect that
                                 there are no or very few STAs
                                 that are not short capable).


The addition of bracket text     See previous comment.        AGREE (ARCHITECTURE:         EDITOR
"(as well as STAs in IBSSs)"                                  2009-07-16 06:33:58Z) See
is not comprehensive                                          CID 1384.
treatment of optional PBCC
use in IBSSs.
The use of "as well as STAs      See previous comment.           AGREE (ARCHITECTURE:        EDITOR
in IBSSs" is not                                                 2009-07-16 06:34:13Z) See
comprehensive treatment of                                       CID 1384.
DSSS-OFDM operation in an
IBSS.




The last sentence should refer Change last sentence of           AGREE (EDITOR: 2009-07-     EDITOR
to non-AP STAs, not just       paragraph to "Non-AP STAs         01 16:32:17Z)
STAs.                          always set this subfield to 0."

It is not clear why there is a   Remove reference or clarify   AGREE IN PRINCIPLE               EDITOR
reference to 9.14.0c here.       with an additional statement  (ARCHITECTURE: 2009-07-
                                 why the reader is being       16 06:34:31Z) Remove
                                 directed to this section.     reference.
Grammer                          "                             AGREE IN PRINCIPLE               EDITOR
                                                               (EDITOR: 2009-07-01
                                                               16:58:08Z)
                                                               Add quotes around "Yes" and
                                                               "Subelements" in lines 52 and
                                                               54.
The value of the Dialog Token Change paragraph text to: "A AGREE IN PRINCIPLE (MAC: EDITOR
field is NOT arbitrary. A STA Dialog Token is an integer       2009-09-24 21:35:59Z) -
should select a unique dialog value that assits a STA in       Replace only first sentence in
token. Also, its use is not   grouping management frames paragraph with proposed text,
limited to action frame       sent or received at different    while correcting spelling of the
request/response exchanges times as part of the same           word "assists" (9th word in
(see timing measurement       dialog. The algorithm by which proposed change).
feature in 11v).              the integer value for the dialog
                              is selected is implementation
                              specific but should be
                              selected in a manner that
                              minimizes the probability of a
                              frame associated with one
                              dialog being incorrectly
                              associated with another
                              dialog."
Comment submitted per TGv           This may be a TGmb problem       DISAGREE                      EDITOR
LB140 comment resolution;           however. If so, send it on.      (ARCHITECTURE: 2009-11-
LB140 CID 447 below                 TGv TG discussed and             16 15:35:12Z) STAs may
(submitter R. Roy)addressed         agreed that it is a TGmb         assign Antenna ID numbers to
TGk Text:This clause states         issue. TGv chair will forward    "antenna configurations"
that for example "If during         the issue on to the TGmb         which can represent the
frame reception, different          group.                           multiple antenna/smart
antennas are used to receive                                         antenna processing
the preamble and body, the                                           situations, by assigning
antenna ID identifies the                                            unique numbers to the
antenna that receives the                                            (meaningfully) different
frame body." and allocates a                                         configurations. If the system
byte for describing all possible                                     is too complex to still be
antenna configurations. What                                         represented in this fashion,
happens when smart antenna                                           the STA can return 255. Any
signal processing is used to                                         further complication in
receive the frame (e.g., with                                        description is probably not
multi-dimensional (i.e., multi-                                      useful.
antenna) decision directed
feedback)? This section
needs work.


Comment submitted per TGv           Remove sentence and update       DISAGREE                        EDITOR
LB146 comment resolution;           draft with any other changes     (ARCHITECTURE: 2009-07-
LB146 CID below (submitter          required to convey duration of   16 06:35:04Z) 7.3.2.22.10
G. Venkatesan):The sentence         a measurement period for         seems to be okay already. So
"In a triggered STA statistics.."   triggered reporting.             does 7.3.2.21.20. The field is
suggests the duration field is      Resolution in TGv was as         defined in 7.3.2.22.10 and the
reserved for triggered report.      follows:                         behaviour in 11.10.8.8
Why? Is it not useful to            Delete the sentence as           descripes setting this to 0. No
convey the duration it took to      recommended. Delete P29L9-       change required.
trigger the report?                 10: "In a triggered STA
                                    Statistics report the
                                    Measurement Duration field is
                                    reserved."
                                    Also replace P201L56-58 with
                                    the following:

                                    "Measurement duration shall
                                    not be specified when
                                    requesting a triggered STA
                                    statistics measurement and
                                    the Measurement Duration
                                    field in the corresponding
                                    Measurement Request shall
                                    be set to 0."

                                    To make this consistent, the
                                    corresponding text in
                                    7.3.2.22.10 (P802.11k-2008)
                                    needs to be deleted (P54). If
                                    this is not in scope for TGv,
                                    this should be submitted as a
                                    comment to TGmb.
                                    Corresponding edits need to
The sentence "This clause is       Convert or reposition so that it AGREE IN PRINCIPLE             EDITOR
no longer maintained..."           doesn't appear in the TOC.       (EDITOR: 2009-07-23
appears in the TOC.                                                 12:56:18Z) - See resolution of
                                                                    CID 1241, which removes
                                                                    this Annex.
"an protected"                     change to "a protected"          AGREE (EDITOR: 2009-07-        EDITOR
                                                                    01 11:54:19Z)

The abbreviation LCI is used       expand/re-order as necessary. AGREE IN PRINCIPLE             EDITOR
before being defined.                                            (EDITOR: 2009-07-01
                                                                 11:59:33Z)
                                                                 Expand LCI in p12.37 and
                                                                 p12.38 and reorder.
This note is redundant             Remove it.                    AGREE (EDITOR: 2009-07-        EDITOR
                                                                 01 12:01:37Z)

The last sentence of 3.84 is       Move it into a NOTE-- to         AGREE (EDITOR: 2009-07-     EDITOR
802.11-specific                    follow 3.84.                     01 12:04:13Z)

The last sentence of 3.42 is       Move it into a NOTE-- to         AGREE (EDITOR: 2009-07-     EDITOR
802.11-specific                    follow 3.42.                     01 11:53:40Z)

This definition appears to be      Either move to 3A, or reword     AGREE IN PRINCIPLE          EDITOR
802.11-specific                    to remove 802.11.                (EDITOR: 2009-07-01
                                                                    11:56:45Z)
                                                                    Delete: "non-IEEE-802.11"
"This key is at least 64           Replace with a NOTE:             AGREE (EDITOR: 2009-07-     EDITOR
octets..." is specific to 802.11   "NOTE--In 802.11, this key is    01 12:03:16Z)
                                   at least 64 octets in length."

"A medium access control           Replace with "... set to 1."     AGREE (EDITOR: 2009-07-     EDITOR
(MAC) address that has the                                          01 12:05:08Z)
group bit set." - set to what?
", employed by some IEEE          Replace with a NOTE:              AGREE (EDITOR: 2009-07-     EDITOR
802.11 security protocols." -     "NOTE, a per-frame                01 12:06:35Z)
802.11 specific                   encryption key is employed by
                                  some ..."
"A static key that is distributed Replace with: "A static key       AGREE (EDITOR: 2009-07-     EDITOR
to the units in the system by a that is distributed to the units    01 12:07:35Z)
method outside                    in the system by some out-of-
the scope of this standard,       band means."
always by some out-of-band
means." - implicit reference to
802.11.
"3.133 selector: An item          Move to Clause 3A                 AGREE (EDITOR: 2009-07-     EDITOR
specifying a list constituent in                                    01 12:10:00Z)
an IEEE 802.11 Management
Message information
element." - specific to 802.11
"3.136 station (STA): Any        I would say move to 3A,        AGREE (EDITOR: 2009-07-        EDITOR
device that contains an IEEE     however all dependent          01 12:23:38Z)
802.11-conformant medium         definitions would also have to
access control (MAC)             move. Replace with:
and physical layer (PHY)         "3.136 station (STA): Any
interface to the wireless        device that contains a
medium (WM)." - specific to      medium access control (MAC)
802.11                           and physical layer (PHY)
                                 interface to the wireless
                                 medium (WM)."

                                 Add in clause 3A:"3a.x IEEE
                                 802.11 station (STA): Any
                                 station that is conformant to
                                 IEEE 802.11. Any reference
                                 to the term station (STA) in
                                 this standard where not
                                 qualfied by the term IEEE
                                 802.11 implicitly refers to an
                                 IEEE 802.11 station.


"However, such classification    Turn into a NOTE--.               AGREE (EDITOR: 2009-07-     EDITOR
is beyond the scope of this                                        01 12:25:49Z)
standard." - 802.11 specific

WEP is specific to 802.11.       Move it and its dependent         AGREE (EDITOR: 2009-07-     EDITOR
                                 defintions into 3A: These         01 12:41:56Z)
                                 are: TSN and all definitions
                                 dependent on RSN: 3.75,
                                 3.97b, 3.97f, 3.97i, 3.97k,
                                 3.126, 3.127, 3.130, 3.132,

802.11-specific.                 Move to Clause 3A                 AGREE (EDITOR: 2009-07-     EDITOR
                                                                   01 12:27:20Z)

Annex C serves no useful         Fell Annex C, split it into its   DISAGREE (EDITOR: 2009-     EDITOR
purpose. It is out of date and   component parts and lovingly      09-23 18:52:05Z) - See
potentially misleading. It       feed them to a virtual fire,      comment resolution of CID
takes up 200 pages of virtual    SDL statement by SDL              1369.
tree.                            statement.

The abbreviation for DSSS-       Replace with "Direct              AGREE (EDITOR: 2009-07-     EDITOR
OFDM is self referential         sequence spread spectrum          01 12:46:00Z)
                                 othogonal frequency division
                                 multiplexing" and move a
                                 matching definition to 3A.
The abbreviation for ERP is      Add an abbreviation, and          AGREE (EDITOR: 2009-07-     EDITOR
more like a definition           move this definition to 3A.       01 12:50:32Z)

Same comment for ERP-*,
NonERP
While I expect this comment        Excoriate the concept of the   DISAGREE (GEN: 2009-09-       EDITOR
to get rejected, it is worth       DS from the standard.          22 06:20:12Z) The concept of
getting it off my chest.                                          the DS by definition is
                                                                  described in "other" places.
The concept of the DS is                                          Removing the concept would
unhelpful. Describing it in the                                   not facilitate the interface
abstract, without providing                                       without the notion of a DS.
concrete interfaces to allow                                      The concept of removal of the
interoperable                                                     DS would not necessarily be
implementations, is without                                       any more helpful.
value, unless someone else
has taken up the burden of
providing this instantiation. In
current practice, almost every
AP is also a portal, and
"distribution" takes place
according to 802.1 bridging
(or in the network layer),
where it is invisible to us.

The exception to "every AP is
also a portal" is when a
manufacturer create an
instance of the DS between
its APs. There, the APs
need not contain portals.
However, the APs must
necessarily instantiate the
abstract DS interface provided
in Annex O, so that they can
talk together. The result is
that the user cannot mix and
matchthe expanded heading
Keep APs that share a DS.          As in comment.                 AGREE (EDITOR: 2009-07-     EDITOR
of 5.2.3.2 (for consistency                                       01 12:56:54Z)
with previous heading) and
remove the note.
"The integration service is        Remove "frame format         AGREE IN PRINCIPLE (GEN: EDITOR
responsible for any                changes" and replace "frames 2009-11-18 01:57:04Z)
addressing or frame format         pass" with "MSDUs pass".     Remove " or frame format
changes that might be                                           changes" and replace "frames
required when frames pass                                       pass" with "MSDUs pass"
between the DS and the
integrated LAN."

Frame do not pass above the
MAC SAP. Although it is
unclear from the architecture
diagram where the MAC
SAPs are, it is certainly
beneath the interface of the
portal and the external
network.
"A comprehensive statement          On the understanding that any AGREE (MAC: 2009-07-16           EDITOR
on mandatory and optional           statements about mandatory / 16:37:32Z)
functionalities is available in     optional QoS features are
Annex A."                           already present in clauses 6-
                                    11, remove the cited text.
While the PICS is normative,
it is not definitive. Statements
about mandatory or optional
features should exist in the
body proper.

"either in the APs or in the        Change "individual devices" to AGREE (EDITOR: 2009-07-         EDITOR
individual devices" - 'individual   "non-AP STAs". Also remove 01 12:58:28Z)
devices' is not defined, and        the two redundant "the's".
could reasonably include the
AP
"health and efficiency" is a        If anybody is going to confuse    DISAGREE (SECURITY:            EDITOR
possibly trademarked term,          the 802.11 standard with a        2009-07-16 15:35:18Z)
being the name of a Naturist        Naturist publication, this term   The phrase does not appear
magazine.                           should be changed. e.g. to        to infringe on any trademarks.
                                    "efficiency and health".

The problem with this             Add to figure 5-7 a                 DISAGREE (GEN: 2009-11-         EDITOR
"architecture" is that it doesn't designation to show where           18 20:40:26Z) - The
map onto the architecture         the MAC Data SAPs are.              commentor is encouraged to
diagram in figure 6. We have                                          provide more details of any
some services for which no                                            proposed improvement, but
behaviour (and certainly no                                           without the details of what is
interfaces) is defined in                                             proposed, the group cannot
802.11. It would be nice to                                           evaluate the technical merit at
know where these services                                             this time.
sat. Then we can discover
whether we have truly failed to
describe a bit of functionality
within our scope, or whether
the non-existent services are
unnecessary myths.

It would also be nice to know
where the MAC SAP is. For
example, is the DS below or
above the MAC Data SAP?
"While IEEE Std 802.11 does       Remove cited paragraph, or      DISAGREE (GEN: 2009-09-     EDITOR
not specify DS                    replace with a statement that   22 06:40:50Z) While the
implementations, it does          there is no standardized way    commenter may disagree, the
recognize and support the use     to use the 4-address frame to   group believes that the
of the WM as the DSM. This        provide a wireless DS.          sentence is correct.
is specifically supported by
the IEEE 802.11 frame
formats."

Come off it. Just defining a
frame format doesn't ensure
interoperability. There is no
interoperable way for APs of
different manufacturers to use
the 4-address format frames
to provide a wireless DS.
Until such a mechanism is
defined, the use of 4-address
format as a wireless DS
should be considered a
proprietary extension.

"While IEEE Std 802.11 does Rewrite to acknowledge the            DISAGREE (GEN: 2009-09-      EDITOR
not specify DS                limitation of the DS.               22 06:51:54Z) The
implementations, it does                                          commenter is sollicited to
recognize and support the use                                     provide a submission. The
of the                                                            DS within the AP is not
WM as the DSM. This is                                            essentially an Association
specifically supported by the                                     Table.
IEEE 802.11 frame formats."

This is not how it works. The
DS within an AP is essentially
its association table. An AP
decides to relay within its BSS
or send it up to its MAC SAP
based on this table. The
802.1 bridging component
above the MAC SAP decides
which interfaces of any
attached integrated LAN
media the MSDU is sent to.
When two STAs within two
BSSs are members of the
same ESS (notionally the
same DS according to our
architecture), a message
from one to the other exits the
DS, is bridged by 802.1, and
re-enters the DS at the AP
supporting.

The notion of ESS is
important, because it probably
implies that all APs of this
There are a handful of shalls      Consider moving normative     AGREE IN PRINCIPLE (GEN: EDITOR
and mays in clause 5.              statements out of clause 5.   2009-09-24 19:38:53Z) --
                                                                 Agree in principle -- all the
Please consider whether                                          listed instances of "shall" in
normative requirements                                           clause 5 already have
should be allowed in Clause                                      normative text in other
5. If it is considered that this                                 sections, so the cited changes
material is introductory,                                        do not change any normative
people may miss normative                                        behavior.
requirements there.
                                                                 Editor is instructed to make
                                                                 following changes:
                                                                 5.2.2, change "STA shall
                                                                 become" to "STA becomes"
                                                                 5.2.6, penultimate paragraph,
                                                                 change "shall not use" to "do
                                                                 not use"
                                                                 5.2.6, final paragraph, change
                                                                 "shall act" to "acts"
                                                                 5.4.1.2, change "shall invoke"
                                                                 to "invokes"
                                                                 5.4.2, change "shall be" to
                                                                 "is"
                                                                 5.4.2.2, second paragraph,
                                                                 change "shall first become" to
                                                                 "first becomes"
                                                                 5.4.2.4, final paragraph,
                                                                 change "STAs shall attempt"
                                                                 to "STAs attempt"
                                                                 5.4.3.1, second paragraph,
                                                                 change "shall not be
                                                                 established" to "is not
"Two services are provided to Delete cited text.                 established"
                                                                 AGREE (SECURITY: 2009-08- EDITOR
bring the IEEE 802.11                                            14 16:29:04Z)
functionality in line with wired
LAN assumptions:
authentication and data
confidentiality. Authentication
is used instead of the wired
media physical
connection. Data
confidentiality is used to
provide the confidential
aspects of closed wired
media."

This material has been
superseded by the following
two paras.
"Management information          Remove cited text, or replace AGREE IN PRINCIPLE           EDITOR
base (MIB) functions are         it with something meaningful. (SECURITY: 2009-08-14
provided in Annex D to                                         16:30:24Z)
support the standardized                                       Delete the cited text.
authentication schemes."

What does this mean? I
haven't the foggiest, and I
suspect that TGmb won't
either.
If the SME is a separate part    Review clause 10 and 11 for   DISAGREE (GEN: 2009-11-         EDITOR
of our architecture, we should   normative requirements on     18 20:41:02Z) - The
have a separate clause           the SME and move them into    commentor is encouraged to
devoted to specifying its        a new clause called "SME".    provide more details of any
normative requirements.                                        proposed improvement, but
                                                               without the details of what is
At the present there are a                                     proposed, the group cannot
number of normative                                            evaluate the technical merit at
requirements on the SME,                                       this time.
usually couched in terms of "a
STA shall...", e.g. A STA
shall authenticate before it
associates.

These are usually in clause
10 or 11. Clause 11 is
definitely the wrong place for
them, and nobody reads
clause 10.
The use of EAPOL requires        Add a SAP at the top of the       DISAGREE (GEN: 2009-11-         EDITOR
that data frames encode the      MLME with a MLME-                 18 20:41:24Z) - The
data using a specific            ManagementData.request            commentor is encouraged to
Ethertype. The multiplexing      primitive that takes the usual    provide more details of any
or demultiplexing by Ethertype   parameters, plus an               proposed improvement, but
must occur above the MAC         EtherType as parameters.          without the details of what is
data SAP, because it is part                                       proposed, the group cannot
of the MSDU, and a service       Add descriptive text split into   evaluate the technical merit at
must consider its data to be     the usual primitive sections      this time.
arbitrary and opaque.            something like: "This primitive
                                 is generated by the higher
The MLME is the recipient of     layers to route MSDUs that
these EAPOL frames,              actually carry MAC
because it later emits various   management information
MLME-EAPOL primitives to         back into the MAC. The
the SME.                         MLME uses the EtherType
                                 parameter to determine which
So how does the data get         encapsulation protocol is
back from the demultiplexing     being employed. The entity
entity to the MLME?              in the link layer that
                                 demultiplexes received
                                 MSDUs on EtherType sends
                                 those carrying one of the
                                 EtherTypes used by 802.11 to
                                 carry management
                                 information to this SAP."

                                 Recommend this issue is
                                 discussed with ARC before
                                 adopting a resolution.

The VSPECIFIC primitives         Change the description of the     AGREE (ARCHITECTURE:         EDITOR
describe the                     VendorSpecificParmeter to         2009-07-16 06:35:52Z)
VendorSpecificContent thus:      something like:
"A set of information elements
as                               "Determined by the entity to
defined in 7.3.2 (Information    whom the OUI is registered."
elements). A set of vendor-
specific fields specifying the
required fields for the Vendor
Specific Action frame."

The implication is that the
frame following the OUI can
be parsed as a set of
information elements. This is
not the consistent with Clause
7.
"If the SME wants to set up a     Remove cited sentence, or          DISAGREE (SECURITY:             EDITOR
security association to the       add appropriate SAP                2009-08-14 16:32:52Z)
peer STA, but does not            interfaces to support this         The SME can use the
know the security policy of the   function.                          MLME.Scan primitive to
peer, it should send a Probe                                         determine the security policy
Request frame to the peer                                            on the peer STA.
STA to find its
security policy before setting
up a security association to
the peer STA."

How does it achieve this?
What SAP interfaces does the
SME use to send this probe
request.

"defragmentation if security is   change to: defragmentation if      AGREE (EDITOR: 2009-07-         EDITOR
used" - missing a "not"           security is not used               01 14:34:04Z)

"The order of the                 Seeing that the OUI doesn't       AGREE (ARCHITECTURE:             EDITOR
organizationally unique           have an individual/group bit      2009-11-17 22:58:38Z)
indentifier (OUI) field follows   and is not specified as an
the ordering convention for       ordered sequence of bits, this
MAC                               specification is utterly useless.
addresses from 7.1.1
(Conventions)."                   Add: "OUIs are specified in
                                  two forms: an ordered
But in 7.1.1, the only thing      sequence of octets, and a
that is said about MAC            numeric form. Treating the
addresses is: "MAC                OUI as an ordered sequence
addresses are assigned as         of octets, the leftmost octet is
ordered sequences of bits.        always transferred first. This
The Individual/Group bit is       is equivalent to transmitting
always transferred                the most significant octet of
first and is bit 0 of the first   the numeric form first."
octet."
                                  Add reference to this to
                                  replace the first cited text in
                                  the comment, and perform
                                  the same on p312.62.
"The exact functions of the   Another of my comments             AGREE IN PRINCIPLE            EDITOR
SME are not specified in this suggests bundling all of the       (ARCHITECTURE: 2009-11-
standard,"                    SME requirements into a new        18 20:28:21Z) - Replace cited
                              clause. If this is done, the       text with: "Some of the
This is misleading. There are cited text can be replaced by      functions of the SME are
many requirements expressed a reference to this clause.          specified in this standard"
as "a STA shall..." that are
executed by the SME. For      Otherwise replace cited text
example, the need to          with: "Some of the functions
authenticate before           of the SME are specified in
association.                  this standard", or perhaps:

                                "We were too lazy to sort this
                                out for ourselves, but some
                                bits of the SME are specified
                                and others are not - but we're
                                not going to tell you which is
                                which. You go figure."



"In particular, PHY             Remove cited text.               AGREE (ARCHITECTURE:            EDITOR
implementations are not                                          2009-07-16 06:36:08Z)
required to have separate
interfaces
defined other than their
interfaces with the MAC and
MLME."

This is misleading an
unnecessary. The only
requirments on a PHY
implementation are its OTA
behaviour. The PHY-MAC
and PHY-SME interfaces are
not exposed.
"SAP primitives are of the   Replace cited text with: "SAP       AGREE (ARCHITECTURE:            EDITOR
general form ACTION.request primitives are of the general        2009-11-18 20:29:41Z)
followed by ACTION.confirm." form ACTION.request
                             followed by ACTION.confirm
What about                   (for an exchange initiated by
indication/response?         the SAP client) and
                             ACTION.indication followed
                             by ACTION.response (for an
                             exchange initiated by the
                             MLME)."

What we have here is a table    Separate out capability and      AGREE IN PRINCIPLE              EDITOR
that provides a mixture of      status information into two      (SECURITY: 2009-09-22
static capability and active    MIB variables.                   00:44:12Z)
status as the encoding for a                                     Delete the first sentence in
MIB variable.                                                    the first two rows in the
                                                                 "Notes" column, and change
This is confusing, and                                           the table title to match any
counter to the ARC group's                                       renaming of the MIB variable.
policy on MIB variables.
"Present only if the value of Replace "greater than 1" with        AGREE (ARCHITECTURE:         EDITOR
dot11RRMMeasurementPilotC "non-zero".                              2009-07-16 06:36:23Z)
apability is greater than 1."

This excludes the case of 1,
which includes a STA
receiving measurement pilots.

"The parameter sets relevant      List, for each attached PHY,     DISAGREE                        EDITOR
to the PHY from the received      which are the relevant           (ARCHITECTURE: 2009-11-
Beacon or Probe Response          parameters.                      18 20:41:45Z) - The
frame."                                                            commentor is encouraged to
                                                                   provide more details of any
This is inadequate                                                 proposed improvement, but
specification.                                                     without the details of what is
                                                                   proposed, the group cannot
                                                                   evaluate the technical merit at
                                                                   this time.
"The STA must be able to          Remove cited text in both        AGREE (ARCHITECTURE:            EDITOR
receive at each of the data       rows.                            2009-11-19 01:20:16Z) -
rates listed in
the set."

This is odd - certainly when
BSS Description relates to a
scan confirm primitive. Which
STA? "Must" is deprecated
by the IEEE-SA style guide.

Ditto in the previous row.

This table references "the        Add the following after          AGREE (ARCHITECTURE:         EDITOR
STA" - but the antecedent is      "elements" on line 48:           2009-11-19 01:16:07Z)
not clear. Is it the local STA,
or some other STA? In some        ", in which the term
cases it is the local STA         <italic>peer STA</italic>
(Local Time), and in others a     refers to the STA transmitting
property of the BSS               the Beacon frame or Probe
(BSSBasicRateSet) or the          Response frame from which
STA transmitting the              the BSSDescription was
Beacon/ProbeResponse              determined and the term
(OperationalRateSet).             <italic>local STA</italic>
                                  refers to the STA performing
                                  the scan"

                                  Insert peer at 432.30, 432.38.
                                  Insert local at 432.3.
This table references "the        Add the following after           AGREE (ARCHITECTURE:             EDITOR
STA" - but the antecedent is      "elements" on line 48:            2009-11-19 01:16:34Z)
not clear. Is it the local STA,
or some other STA?                ", in which the term
                                  <italic>peer STA</italic>
                                  refers to the STA transmitting
                                  the Measurement Pilot frame
                                  from which the
                                  BSSDescription was
                                  determined and the term
                                  <italic>local STA</italic>
                                  refers to the STA performing
                                  the scan"

                                  Insert peer at 434.44, 434.50.
                                  Insert local at 434.36.


"only present" is wrong           Change to "present only" and      AGREE (EDITOR: 2009-07-          EDITOR
                                  move sentence to end of cell.     03 12:54:53Z)

Often one or both of the          For each entry where this         AGREE IN PRINCIPLE               EDITOR
Type/Valid Range columns          occurs, replace "as defined in    (EDITOR: 2009-07-03
have "As defined in frame         frame format" in the Type         13:27:31Z) - Replace each
format".                          entry with the name of the        "as defined in frame format"
                                  type "e.g. EDCA Parameter         or "frame format" as follows:
This is lazy specification.       Set element" and replace "as
                                  defined in frame format" in the   Where this occurs in the Type
                                  Valid range entry with "As        entry, replace with the name
                                  defined in 7.x.x.x." with         of the type "e.g. EDCA
                                  reference to the subclause        Parameter Set element".
                                  where the element is defined.     Where this occurs in the Valid
                                                                    Range entry, replace with "As
                                                                    defined in 7.x.x.x." with
                                                                    reference to the subclause
                                                                    where the element is
                                                                    defined.

                                                                    Merge with any existing
                                                                    additional specification in
                                                                    these cells.

                                                                    However, do not modify BSS
                                                                    Description / PHY Parameter
                                                                    Set, as it is not obvious from
                                                                    the description what are the
                                                                    appropriate
                                                                    structures/references.

                                                                    In 10.3.14.1.2, 10.3.13.2.2,
                                                                    10.3.14.3.2
                                                                    replace:
                                                                     "as defined in the
Some newlines missing from        Insert missing newlines and       Measurement Report element EDITOR
                                                                    AGREE (EDITOR: 2009-07-
RCPI,...                          align text                        03 12:57:13Z)
"Shared Key authentication          Replace with: "Shared Key          AGREE (SECURITY: 2009-07- EDITOR
can be used if and only if          authentication may be used if      14 22:01:14Z)
WEP has been selected."             WEP has been selected and
                                    shall not be used otherwise."
"can" and "if and only if" are
conflicting - one implies
information, the other
expresses a constraint.
There's a lot of "if and only if"   Change "if and only if" as         AGREE (ARCHITECTURE:     EDITOR
going on in clause 10.              follows:                           2009-11-16 15:56:54Z)
                                    p446.05 -> if
These uses are often wrong          p448.51 -> only if
or unnecessary. In a request        p451.19 & 26 -> only if
or response, it is more             p453.25 & 32 -> if
appropriate to use "if" - i .e.     p455.4 -> if
expressing a requirement to         p455.51 -> only if
be present. In an indication        p460.31 & 36 -> only if
or confirmation, it is more         p462.27 & 35 -> if
appropriate to use "only if" -      p469.37 -> if
meaning that this information
is not availble if not some
condition (and there are often
additional reasons for it not to
be present that are not
admitted in the "if and only if"
construct).


Incorrect use of "if and only if"   Replace "if and only if" with      AGREE (SECURITY: 2009-07- EDITOR
- which implies logical             "only if" on line 5 and line 23.   14 22:01:40Z)
correspondance. i.e. line 5
implies that all frames are
class 2 if the STA is
authenticated - which is
clearly rubbish.
Incorrect use of "if and only if"   Replace cited sentence with:      AGREE IN PRINCIPLE (GEN: EDITOR
- which implies logical                                               2009-11-19 05:15:59Z) The
correspondance, not a               "The state variable for the AP Editor is instructed to
sequence of dependent               shall be set to State 2 if it was incorporate into the REVmb
events.                             not State 1, and shall not be draft document 11-09/705r4.
                                    modified otherwise."              (https://mentor.ieee.org/802.11
                                                                      /dcn/09/11-09-0705-04-000m-
                                                                      proposed-corrections-to-11-3-
                                                                      sta-authentication-and-
                                                                      association.doc)

Incorrect use of "if and only if"   Replace cited sentence with:      AGREE IN PRINCIPLE (GEN: EDITOR
- which implies logical                                               2009-11-19 05:15:59Z) The
correspondance, not a               "The state variable for the AP Editor is instructed to
sequence of dependent               shall be set to State 2 if it was incorporate into the REVmb
events.                             not State 1, and shall not be draft document 11-09/705r4.
                                    modified otherwise."              (https://mentor.ieee.org/802.11
                                                                      /dcn/09/11-09-0705-04-000m-
                                                                      proposed-corrections-to-11-3-
                                                                      sta-authentication-and-
                                                                      association.doc)
Incorrect use of "if and only if"   Note, cited text already      AGREE (SECURITY: 2009-07- EDITOR
in the following: "A STA shall      contains a normative          14 22:01:49Z)
accept a Measurement                requirement to reject
Request with the parallel bit       "otherwise" so the wrong "and
field enabled if and only if        only if" is also redundant.
dot11RRMParallelMeasurenm
entEnabled is true; otherwise,      Delete: "and only if" from the
the STA shall reject the            cited text.
Measurement Request by
returning a Measurement
Report with the Incapable bit
set in the Measurement
Report Mode field."

Incorrect use of "if and only if" Replace "A STA will use the       AGREE IN PRINCIPLE                EDITOR
                                  defined TPC and DFS               (EDITOR: 2009-07-23
Same comment line 56.             procedures if and only if this    14:18:42Z)
                                  attribute is TRUE."               Replace cited sentence with:
                                                                    "A STA will use the defined
                                    With: "A STA will use the       TPC and DFS procedures if
                                    defined TPC and DFS             this attribute is TRUE;
                                    procedures if this attribute is otherwise it will not use the
                                    TRUE, otherwise it will not     defined TPC and DFS
                                    use the defined TPC and DFS procedures."
                                    procedures."
                                                                    Replace sentence at 1317.55
                                    Make matching change in line with: "A STA will use the
                                    55.                             defined regulatory classes
                                                                    procedures if this attribute is
                                                                    TRUE; otherwise it will not
                                                                    use the defined regulatory
                                                                    classes procedures.(#1448)"

"The default values are         Clarify how the default values       DISAGREE                        EDITOR
implementation dependent."      can be implementation                (ARCHITECTURE: 2009-11-
                                dependent, while many of             18 20:42:03Z) - The
If this is true, why do we have them are also specified in           commentor is encouraged to
defval statements in Annex D? Annex D.                               provide more details of any
                                                                     proposed improvement, but
                                                                     without the details of what is
                                                                     proposed, the group cannot
                                                                     evaluate the technical merit at
                                                                     this time.
What point is there in having       Remove ResultCode                AGREE (ARCHITECTURE:            EDITOR
a parameter which carries an        parameter.                       2009-07-16 06:37:12Z)
a-priori known value?
The MIB is a mess.                    This confusion can be          AGREE IN PRINCIPLE             EDITOR
Specifically there is confusion       remedied by labelling each     (ARCHITECTURE: 2009-11-
as to which entity writes many        MIB variable as described in   17 22:26:14Z) See CID 1005 --
variables, and the effect of          11-09/0533r1.                   "Editor is instructed to make
this writing.                                                        the changes as recorded in
                                 Where no such labelling can         11-09/910r6."
                                 be applied, consider either
                                 removing the MIB variable, or
                                 splitting it into multiple
                                 variable, each with a clear
                                 label.
There are lots of "shalls" in    Clarify, in the case of control     AGREE IN PRINCIPLE              EDITOR
Annex D: "shall specify", "shall variables, which entity polices     (ARCHITECTURE: 2009-11-
indicate", "shall be", "shall    the "shall"s. Or remove the         17 22:29:16Z) Remove the
include".                        shalls.                             shalls.

In cases where this is a status
or capability, I suppose that it
is clear that the normative
requirement is on the local
entity to fill that variable with a
value as specified. Although
puttin a normative
requirement into the
description text seems a bit
off.

In the case where the variable
is a control, written by a
remote entity, the question
arises as to who is
responsible for ensuring
compliance to any normative
requirement expressed in the
description. Is it the user
(who can read the
description), the remote
management entity, or the
local entity?
"or IBSS (where the MAC         I think the RESET request            AGREE IN PRINCIPLE              EDITOR
entity was the first STA in the does everything you need for         (ARCHITECTURE: 2009-11-
IBSS)."                         the IBSS case, so I'd make           19 01:17:40Z) Delete cited
                                this primitive specific to the       text and the fourth and fifth
While it is possible to stop    infrastructure case.                 sentances in 10.3.10a.1.4
operation of the local STA in
an IBSS, once a STA has         Alternatively describe it as
started an IBSS, it has no      having local significance only
control over the continued      in the IBSS case and take out
existence of the IBSS in the    the contraint in the
case that other STAs have       parenthesis of the cited text.
joined the IBSS.
"Note that..."                     If not, turn into a proper      AGREE IN PRINCIPLE               EDITOR
                                   "NOTE--". If so, use the        (ARCHITECTURE: 2009-11-
Does this text introduce any       proper normative languge.       16 15:58:29Z) Just delete the
new normative requirements?                                        cited Text




Text earlier in 10.3.11            Remove the MLME-                AGREE (ARCHITECTURE:             EDITOR
indicates these figures are        CHANNELSWITCH.cmf at the 2009-11-19 01:18:28Z)
illustrative only. .confirms are   bottom right of figure 10-6 and
(by convention) associated         the box "channel switch
with matching .requests.           complete".
This figure shows a .confirm
without a matching .request.
There are no normative
statements that describe this
behaviour.
I wonder how many will notice      Translate caption into English. AGREE (EDITOR: 2009-07-          EDITOR
this one.                                                          03 12:58:01Z)

Anyway, it's all greek to me.
This primitive highlights a   Add at least a parameter             AGREE IN PRINCIPLE               EDITOR
weakness in the MLME-SME indicating the rate of the                (ARCHITECTURE: 2009-11-
interface. The question is    request frame in the .confirm.       18 21:18:43Z) Add a
who selects the rate at which                                      parameter indicating the rate
frames (and in particular the                                      of the measured request
TPC Request frame) are sent?                                       frame to the .confirm
                                                                   parameters.
Knowing a link margin is of no
use without also knowing what
rate or MCS it relates to.


"Authenticator/Supplicant or       Replace with "Is                AGREE (ARCHITECTURE:             EDITOR
Initiator/Peer"                    Authenicator". Replace          2009-11-18 21:18:23Z) (note
                                   description with: "Indicates    typo -- "configures" should be
Taking the "/" as "or" - there     whether the key is configures   "configured")
are two levels of or in this. It   by the Authenticator or
is not immediately clear           Supplicant. True indicates
whether the boolean value          Authenticator."
selects the innermost "/" or
the outmost level.
If the SME is required to          Consider adding reference to    AGREE (ARCHITECTURE:             EDITOR
respond to MIC failures in         8.3.2.4                         2009-07-16 06:37:38Z) Add
some way, this should be                                           "(see 8.3.2.4)".
referenced here.
"Rx: Specifies that data          Replace with: "Rx: Specifies      AGREE IN PRINCIPLE             EDITOR
frames from MAC address is        that data frames from MAC         (ARCHITECTURE: 2009-07-
protected."                       address are protected (i.e.,      31 15:47:09Z) - As specified
                                  any data frames without           by commenter. Also, insert
Surely it is specifying that data protection received from the      "the" ahead of "MAC address"
frames received from the          MAC address will be               where necessary in all bullets
MAC address without               discarded)."                      in this list.
protection will be discarded?
It cannot affect whether the
peer chooses to use
protection or not, it can only
determine what the local entity
does with those frames.

Grammar: "is" should be            As in comment.                   AGREE (EDITOR: 2009-07-         EDITOR
"are" throughout this list.                                         03 13:01:26Z)

Encryption is limiter to per-   Replace "SA" with "TA".             AGREE (ARCHITECTURE:            EDITOR
link, so the correct address to                                     2009-11-18 21:22:12Z)
use for Address1 is the
transmitter address, not the
source address.

"It is valid at the non-AP STA"    the -> a                         AGREE (EDITOR: 2009-07-         EDITOR
- no antecedent has been                                            03 13:02:37Z)
established
The "(0 or more)" against          Remove cited text. Add           AGREE (EDITOR: 2009-07-         EDITOR
TCLAS should be in the             "Zero or more TCLAS              03 13:07:24Z)
Description column for             elements." at the front of the
consistency.                       Description column.

                                   Make same change wherever
                                   this occurs in Clause 10.

                                   Likewise, remove "(HC only)"
                                   in the Name column and
                                   replace "(At the HC only)" in
                                   the Description column with
                                   "Present only at the HC."
                                   throughout Clause 10.


"as a result of receipt of an      Replace cited text with          AGREE IN PRINCIPLE              EDITOR
initiation to delete a TS ..." -   "having received a DELTS         (EDITOR: 2009-08-11
ah, truly awesome English.         frame from the specified peer    12:26:33Z) - Replace cited
                                   MAC entity"                      text with "when it receives a
                                                                    DELTS frame from the
                                                                    specified peer MAC entity"
"Specifies the operational    Replace cited text with:              AGREE (ARCHITECTURE:            EDITOR
capability definitions to be  "Specifies the capabilities of        2009-07-16 06:38:20Z)
used by the peer MAC entity." the peer MAC entity."

We cannot specify the peer's
capabilities.

Same comment at 519.26
This fails to specify what         Indicate what happens to          DISAGREE                        EDITOR
happens to any buffered            buffered MPDUs when this is       (ARCHITECTURE: 2009-11-
MPDUs at the time of the           received.                         18 20:43:03Z) - The
delete.                                                              commentor is encouraged to
                                   To avoid creating any             provide more details of any
                                   backwards-compliance              proposed improvement, but
                                   issues, this should be            without the details of what is
                                   phrased as a                      proposed, the group cannot
                                   recommendation.                   evaluate the technical merit at
                                                                     this time.
                                   For example: "The STA
                                   should pass up the protocol
                                   stack any MPDUs for this
                                   Block Ack agreement held in
                                   the reordering buffer.
Review and remove any              As in comment.                    AGREE (EDITOR: 2009-06-        EDITOR
Editor's Note that relates to                                        29 11:39:49Z)
interpretations of the k,r,y
amendments.
"On receipt of this primitive      If they do, the cited statement   AGREE IN PRINCIPLE             EDITOR
the SME should operate             is unnecessary. In that case      (ARCHITECTURE: 2009-11-
according to the procedure in      replace "should operate" with     19 01:19:10Z) - Change
11.11.2."                          "operates".                       "should operate" to
                                                                     "operates", and change cross
Either the procedures in           If they don't, extend 11.11.2     reference to 11.10.9.2.
11.11.2 adequately                 so that they do, and also
normatively describe what          make the change indicated
should be done on receiving a      above.
Neighbor Report request, or
they do not.                       Make similar changes
                                   whereever similar language is
                                   used in Clause 10.
"On receipt of this primitive,     Replace cited text with "No   AGREE (ARCHITECTURE:               EDITOR
the SME evaluates the              effect is specfied for the    2009-11-18 21:23:36Z)
ResultCode."                       receipt of this primitive."

Oh whoopty do. I sense             Scan all primitives and
straws being clutched: "what       replace similar nugatory
shall we specify for this bit?".   specification with a similar
                                   phrase.
If no effect is specified - say
as such.

superfluous space before           Remove it.                        AGREE (EDITOR: 2009-07-        EDITOR
"element"                                                            03 13:10:49Z)

Generally in clause 10 "only       Replace with "present only"       AGREE (EDITOR: 2009-07-        EDITOR
present" is incorrect.             globally.                         03 12:51:00Z)

superfluous space before "(s)" Remove it.                            AGREE (EDITOR: 2009-07-        EDITOR
                                                                     03 13:11:48Z)
"This primitive is a request by    remove "by the LME".                AGREE IN PRINCIPLE           EDITOR
the LME to reset the PHY"                                              (ARCHITECTURE: 2009-11-
                                                                       17 21:39:13Z) Change "LME"
1. There is no such thing as                                           to "SME" in the following
an LME                                                                 clauses:
2. The client is not important,                                        10.4.1.1 and 10.4.2.1,
and could be MLME or SME                                               10.4.2.3, 10.4.5.1, and
                                                                       14.4.3.2.
Ditto comment p570.06,
p170.19




Spurious left paren.               Remove it.                          AGREE (EDITOR: 2009-07-      EDITOR
                                                                       03 13:13:40Z)

A normative requirement            Replace "shall be" with "are".      AGREE (ARCHITECTURE:         EDITOR
cannot be placed on more                                               2009-07-16 06:38:38Z)
than one STA.

The sentence here doesn't
add to any existing normative
statment.
"All STAs shall maintain a         remove "shall".                     AGREE (ARCHITECTURE:         EDITOR
local TSF timer."                                                      2009-07-16 06:38:53Z)

Adds nothing to line 48.
There are 15 instances of          Replace all "shall always" with AGREE (GEN: 2009-09-22           EDITOR
"shall always". But a shall        "shall"                         22:03:00Z)
statement is normative, not
normative some of the time.
"shall always" is therefore
unnecessary.
"If a STA that does not            Indicate this rule is specific to   AGREE (ARCHITECTURE:         EDITOR
support Short Slot Time            a Clause 19 AP.                     2009-07-16 06:39:08Z)
associates, the AP shall use
long slot time beginning at the
first Beacon subsequent to
the association of the long slot
time STA."

This should be specific to PHY
"shall adopt that beacon       Relate to some observable             AGREE IN PRINCIPLE                EDITOR
period" - what does this mean? change in state or behaviour.         (ARCHITECTURE: 2009-11-
                                                                     19 17:49:47Z) Change cited
Same comment for any other                                           text "and STAs shall adopt
use of "shall adopt"                                                 that beacon period when
                                                                     joining the BSS."
                                                                     To
                                                                     "and a STA shall adopt that
                                                                     beacon period when joining
                                                                     the BSS, i.e., the STA sets its
                                                                     dot11BeaconPeriod variable
                                                                     to that beacon period".

"wildcard SSID" appears to be Ajust font as necessary.               AGREE (EDITOR: 2009-07-           EDITOR
in a smaller font                                                    03 13:14:56Z)

"The probe response shall be     Either remove cited sentence, AGREE (ARCHITECTURE:           EDITOR
sent using normal frame          or adjust it to cite which rules 2009-11-18 21:24:45Z)Delete
transmission rules." - i.e.,     are to be used.                  the cited text
stop using abnormal rules :0)

This is not specific enough
"In an IBSS, the STA that        Replace with: "In an IBSS, a        AGREE (ARCHITECTURE:              EDITOR
generated the last Beacon        STA that transmitted a              2009-11-18 21:24:57Z)
frame shall be the STA that      Beacon frame since the last
responds to a probe request."    TBTT shall respond to probe
                                 requests."
This may not be correct.
There may be more than one
STA, so "the STA" is
incorrect.



"Wait until the ProbeDelay       I think we should at least          DISAGREE                        EDITOR
time has expired" - what         recommend a default value           (ARCHITECTURE: 2009-11-
constraints are there on the     for this, otherwise there is        18 20:43:32Z) The
SME in choosing a value for      little value in having the delay.   commentor is encouraged to
this parameter? (answer:                                             provide more details of any
none).                                                               proposed improvement, but
                                                                     without the details of what is
What value do manufacturers                                          proposed, the group cannot
typically choose (some                                               evaluate the technical merit at
choose zero delay)?                                                  this time.

The purpose of ProbeDelay is
to avoid damaging onging
communications that the
scanning STA cannot receive
(either range or unsupported
options). As such, it should
be scaled to a "typical packet
size" - whatever that is.
"using normal frame                 Cite the specific rules.       AGREE IN PRINCIPLE (MAC: EDITOR
transmission rules," - it is                                       2009-09-25 03:49:24Z) -
unclear which rules are                                            Remove all references to
abnormal, and therefore also                                       "normal" access rules.
which are normal.                                                  Change the cited sentence to
                                                                   read: "...AP shall transmit
                                                                   buffered broadcast/multicast
                                                                   MSDUs, before transmitting
                                                                   any unicast frames." Also,
                                                                   strike sentences at 583.8 and
                                                                   583.31 using the phrase
                                                                   "normal transmission rules"
                                                                   because the phrase has no
                                                                   normative meaning. At
                                                                   596.19, change the sentence
                                                                   regarding "normal DCF
                                                                   access procedure" to read
                                                                   "These frames shall be
                                                                   transmitted using the DCF or
                                                                   EDCAF." At 618.65, delete
                                                                   the phrase "using the normal
                                                                   access mechanisms." At
                                                                   619.2, delete the phrase
                                                                   "using the normal access
                                                                   mechanisms." At 366.23,
                                                                   delete the word "normal".


"The AP may modify the            Replace cited text with: "The    AGREE (MAC: 2009-09-25   EDITOR
service start time by             AP may modify the service        03:50:19Z)
indicating so in the Schedule     start time by indicating so in
element in ADDTS Response         the Schedule element in an
frame and in Schedule frames"     ADDTS Response frame
                                  (which is sent in response to
It is not clear if this is giving an ADDTS Request frame)
the AP permission to transmit and in Schedule frames
unsolicited ADDTS Response (which are sent at other
frames.                           times)."

"temporarily buffer the MSDU        replace "management frame"     AGREE (MAC: 2009-09-30   EDITOR
or management frame                 with MMPDU                     14:54:20Z)
destined to the STA" - chalk
and cheese                          Make similar changes
                                    throughout 11.2.1.5 in this
                                    context.




"shall buffer frames" - but it is   Change to "shall buffer        AGREE (MAC: 2009-09-25   EDITOR
MSDUs and MMPDUs that               MSDUs"                         03:50:51Z)
are buffered.
"For a non-AP STAs" -          STAs -> STA                      AGREE (EDITOR: 2009-07-   EDITOR
grammar                                                         03 13:23:55Z)

"For a non-AP STAs using U- Replace "frame" with "MSDU"         AGREE IN PRINCIPLE (MAC: EDITOR
APSD, the AP transmits one                                      2009-07-14 16:24:30Z) - The
frame destined for the non-AP                                   unit of buffering is the
STA from any AC that is not                                     MSDU/MMPDU. The editor is
delivery-enabled in response                                    instructed to make similar
to PS-Poll from the non-AP                                      changes to "frame" language
STA."                                                           in 7.3.2.6, 9.3.2.1, 9.9.2.0a,
The unit of buffering is the                                    11.2.1.4, and 11.2.1.5.
MSDU, not the frame.

When all ACs associated with Replace "frame" with "MSDU"        AGREE (MAC: 2009-08-07    EDITOR
the non-AP STA are delivery-                                    00:11:31Z)
enabled, AP transmits one
frame from the highest priority
AC.
The unit of buffering is the
MSDU, not the frame
"If there are buffered frames   Replace "frames" with           AGREE IN PRINCIPLE (MAC: EDITOR
to transmit to the STA" - unit  "MSDUs or MMPDUs"               2009-07-14 16:24:30Z) - The
of buffering is wrong                                           unit of buffering is the
                                Make same change to             MSDU/MMPDU. The editor is
                                "pending frames" (line 52 and   instructed to make similar
                                line 55).                       changes to "frame" language
                                                                in 7.3.2.6, 9.3.2.1, 9.9.2.0a,
                                                                11.2.1.4, and 11.2.1.5.


Multiple occurances of         Replace frames with "MSDUs AGREE IN PRINCIPLE (MAC: EDITOR
buffered frames - unit of      or MMPDUs" on lines:       2009-07-14 16:24:30Z) - The
buffering is wrong.            8,10,15,18,20, 47.         unit of buffering is the
                                                          MSDU/MMPDU. The editor is
                                                          instructed to make similar
                                                          changes to "frame" language
                                                          in 7.3.2.6, 9.3.2.1, 9.9.2.0a,
                                                          11.2.1.4, and 11.2.1.5.


An MSDU is not                 In "If the AP does not receive   AGREE (MAC: 2009-08-07    EDITOR
acknowledged - a Data frame    an acknowledgment to a           01:16:51Z)
is.                            directed MSDU or
                               management frame sent"
                               replace "MSDU" with "data
                               frame"

                               Make same change on line 39
                               and on 594.41, 594.44
"An AP shall, depending on        The "shall buffer" related to      AGREE (MAC: 2009-08-07   EDITOR
the Power Management mode         management frames should           01:16:31Z)
of the STA, temporarily buffer    be restricted to action frames
the MSDU or management            only - i.e. "shall ... buffer an
frame destined to the STA."       MSDU or MMPDU that will be
                                  transmitted using an Action
                                  frame."

                              Make similar changes
                              throughout 11.2, making
                              adjustment for grammar as
                              necessary.
The unit of buffering is the  Replace frames with "MSDUs             AGREE IN PRINCIPLE (MAC: EDITOR
MSDU/MMDPU, not the           or MMPDUs" on lines:                   2009-07-14 16:24:30Z) - The
frame.                        21.                                    unit of buffering is the
                              Replace "MSDUs" with                   MSDU/MMPDU. The editor is
Action frames may be          "MSDUs and MMPDUs" on                  instructed to make similar
buffered, and these may have lines 23, 24, 25 and 594.11,            changes to "frame" language
a broadcast receiver address, 594.13, 594.15, 594.32,                in 7.3.2.6, 9.3.2.1, 9.9.2.0a,
 so MSDU needs to includ      594.34, 594.35, 594.36                 11.2.1.4, and 11.2.1.5.
MMPDU.

The unit of buffering is the      Replace "buffered broadcast        AGREE IN PRINCIPLE (MAC: EDITOR
MSDU/MMDPU, not the               and multicast frames" with         2009-07-14 16:24:30Z) - The
frame.                            "buffered MSDUs and                unit of buffering is the
                                  MPDUs" on line 33.                 MSDU/MMPDU. The editor is
                                                                     instructed to make similar
                                                                     changes to "frame" language
                                                                     in 7.3.2.6, 9.3.2.1, 9.9.2.0a,
                                                                     11.2.1.4, and 11.2.1.5.


"MSDUs and MMPDUs                 What are the rules for             AGREE IN PRINCIPLE (MAC: EDITOR
belonging to those ACs" - so      determination of the AC of an      2009-09-30 14:57:21Z) - The
what AC does an MMPDU             MMPDU? They should be              "belonging to" language is
belong to?                        referenced here.                   changed by CID 1146. In
                                                                     D1.0 clause 9.1.3.1, the text
                                                                     states that "...management
                                                                     frames shall be sent using the
                                                                     access category AC_VO
                                                                     without being restricted by
                                                                     admission control procedures."


"The non-AP STA shall             replace "QoS data frame" with AGREE (MAC: 2009-08-07        EDITOR
remain awake until it receives    "QoS data frame or            01:17:13Z)
a QoS data frame addressed        management Action frame".
to it, with the
EOSP subfield in the QoS
Control field set to 1." - this
can also be terminated by a
management frame
"deliver-enabled ACs" -type       deliver -> delivery                AGREE (MAC: 2009-09-25   EDITOR
                                                                     03:54:15Z)
The description in this     Add MMPDUs to the                        AGREE IN PRINCIPLE (MAC: EDITOR
subclause does not          description here.                        2009-11-13 20:03:05Z) - Add
acknowledge power-saving of                                          "and MMPDU" or "or MMPDU"
MMPDUs.                                                              as appropriate throughout this
                                                                     subclause after "MSDU",
                                                                     making any changes
                                                                     necessary to preserve
                                                                     grammar.

"Transmission of these              Replace "the normal DCF        AGREE (MAC: 2009-08-07               EDITOR
frames shall be done using          access procedure" with "either 00:12:50Z)
the normal DCF access               the DCF (for non-QoS STAs)
procedure."                         or the EDCAF (for QoS
                                    STAs)."
Strictly, this prevents QoS
STA from supporting power-          Make same change in 598.8
savers, because they do not         and 598.22.
use DCF for delivery of data.

"ATIM management frames             "shall only be transmitted" ->   AGREE IN PRINCIPLE                 EDITOR
shall only be transmitted           "shall be transmitted only"      (EDITOR: 2009-07-03
during the ATIM Window." -                                           13:27:35Z)
grammar
                                                                     "shall only" is (except in
                                                                     exceptional circumstances) an
                                                                     error. **

                                                                     Globally replace "shall only
                                                                     <verb> if/when <condition>"
                                                                     with "shall <verb> only if/when
                                                                     <condition>"

                                                                     **Consider the statement:
                                                                     "the pedestrian shall only
                                                                     cross the road when the light
                                                                     is green." This is incorrect
                                                                     unless is the the intention of
                                                                     the statement to also stop him
                                                                     from breathing, his heart from
                                                                     beating etc... when the light is
                                                                     green.

"the STA shall retain the     Change "shall" to "should"             AGREE (EDITOR: 2009-08-            EDITOR
buffered MSDU(s) and                                                 07 06:54:48Z)
attempt to transmit the ATIM
during the next ATIM Window."

But a STA is allowed to
discard buffered data for
various reasons - e.g.
incoming traffic exhausts
buffer, or timout. The cited
statement is conflicts with this.
"Immediately following the     Add "any" before "buffered"..   AGREE (EDITOR: 2009-08-   EDITOR
ATIM Window, a STA shall                                       07 08:23:00Z)
begin transmission of buffered
broadcast/multicast frames for
which an ATIM was previously
transmitted."
This is only true if the MSDU
has not been expunged - e.g.
due to a timeout.

"In no case shall a frame be   Replace "In no case shall a     AGREE (MAC: 2009-07-14    EDITOR
discarded that has been        frame" with "A frame should     16:36:48Z)
buffered for less than         not"
dot11BeaconPeriod."

A STA with finite resources
may be saturated with MSDUs
for a power-saving STA in
less than this time. This
requirement is not
implementable.
"Data frames between STAs   Change BSS to "infrastructure DISAGREE (SECURITY:            EDITOR
in a BSS" - it means        BSS".                         2009-07-14 22:02:15Z)
infrastructure BSS                                        The text cited applies to an
                                                          IBSS.
BlockAck and BlockAckReq         Change cited location to be       AGREE IN PRINCIPLE (GEN: EDITOR
are permitted in an IBSS         specified to infrastructure and   2009-11-19 05:15:59Z) The
                                 add them as Class 1 frames        Editor is instructed to
                                 for IBSS.                         incorporate into the REVmb
                                                                   draft document 11-09/705r4.
                                                                   (https://mentor.ieee.org/802.11
                                                                   /dcn/09/11-09-0705-04-000m-
                                                                   proposed-corrections-to-11-3-
                                                                   sta-authentication-and-
                                                                   association.doc)




"The SME shall establish an      Replace with: If policy within AGREE (ARCHITECTURE:         EDITOR
RSNA, or it shall enable WEP     the SME requires secure        2009-07-16 06:39:33Z)
by calling                       communication, the SME shall
MLMESETPROTECTION.requ           establish an RSNA, or it shall
est primitive with ProtectType   enable WEP by calling
set to “Rx_Tx,” or it shall do   MLMESETPROTECTION.requ
nothing if it does not wish to   est primitive with ProtectType
secure communication."           set to “Rx_Tx,”.

This is very odd - "you shall  Make similar change to
do this, unless you don't want 603.41, 604.18 and 604.55
to". It has no normative
effect.

Furthermore, SMEs don't
have desires, wishes,
aspirations, wants.... The
language used is
anthropomorphic, and used
to hide the condition under
which the rule obtains.



"normal access mechanisms". replace "using normal access           AGREE (EDITOR: 2009-08-   EDITOR
  Jolly good we're not using mechanisms" with "within its          07 08:48:27Z)
abnormal ones.               own TXOP". Make same
                             change at 619.02.G123
"EDCA or HCCA or HEMM."           Replace with: "EDCA, HCCA, AGREE (EDITOR: 2009-07-              EDITOR
                                  or HEMM."                  03 14:17:19Z)

This is dumb and                  Replace line 18-25 with: "The AGREE (MAC: 2009-08-07            EDITOR
overcomplicated. You need         value of the Minimum PHY       00:19:28Z)
any rate to be in both peer's     Rate in a TSPEC shall be in
operational rate sets, or there   both the AP's operational rate
will be no communication at       set and non-AP STA's
that rate.                        operational rate set."

The lowermost state should        Change as in comment.              AGREE (EDITOR: 2009-07-      EDITOR
be "suspended", not                                                  03 14:33:37Z)
"suspend"                     Also make capitalization of
                              state names consistent.
"Higher layer timer           Replaced cited sentence with           DISAGREE                        EDITOR
synchronization is beyond the a description of what is, and          (ARCHITECTURE: 2009-11-
scope of this standard" - It  what is not in scope.                  18 20:44:00Z) - The
may be life, but not as we                                           commentor is encouraged to
know it, Jim.                                                        provide more details of any
                                                                     proposed improvement, but
If it's beyond the scope of the                                      without the details of what is
standard, why have we got                                            proposed, the group cannot
clause 10 interfaces to                                              evaluate the technical merit at
support it? And why have we                                          this time.
got some itsey-bitsey polka-
dot shall statements in 11.6
(e.g. 620.19).
"The last symbol of the Sync      In .11n, we discovered that        AGREE IN PRINCIPLE            EDITOR
frame is indicated by the PHY     the Clause 19 state machines       (ARCHITECTURE: 2009-11-
using the PHY-                    were inadquate to shed light       18 19:28:59Z) - See CID 1556
TXEND.confirm and                 on this subject. We modified       that is resolved with changes
PHYRXEND.                         the Clause 20 state machines       as documented in 11-
indication primitives in the      to explicitly show that the        09/1233r0.
transmitter and receiver of the   signal extension occurs prior
Sync frame, respectively."        to any TXEND/RXEND.

Does the TXEND/RXEND              I think the assumption of this
occur before or after any         sublclause is that it is the
signal extension in ERP           physical end, not the logical
STAs?                             end of the packet that is
                                  significant. But it's not clear.

                                  Can I request that REVmb
                                  create a place to record
                                  comments pending some
                                  draft being rolled in. I would
                                  like to squirrel this one away
                                  marked "when TGn is
                                  incorporated". We can then
                                  review if TGn is inconsistent
                                  with this subclause.
"A MAC that supports the         Add "and that has room to    AGREE (ARCHITECTURE:              EDITOR
MLME-HL-SYNC primitives          record another group address 2009-11-19 01:22:26Z)
shall respond to a MLME-HL-      for the purpose of Higher
SYNC.request                     layer timer synchronization"
primitive with an MLME-HL-       before "shall respond".
SYNC.confirm primitive
containing a result code of      Add a status code of "too
SUCCESS." - resource limits      many addresses" to the HL-
may prevent this - e.g., if      SYNC.confirm primitive.
2^46 multicast addresses
were registered.




"In general, STAs are not        Remove cited sentence and      AGREE IN PRINCIPLE (MAC: EDITOR
allowed to transmit frames       "However, " of following       2009-08-07 00:30:01Z) -
directly to other STAs in a      sentence.                      Replace cited sentence with
BSS and should always rely                                      an editor note reading "Editor
on the AP for the delivery of                                   Note -- update the following
the frames."                                                    when 802.11z is rolled in."
                                                                and the following sentence:
I don't know what "in general"                                  "In an infrastructure network,
means. And it certainly                                         non-AP STAs are not allowed
doesn't allow for IBSS.                                         to transmit frames directly to
                                                                other non-AP STAs, except
                                                                when using DLS."

"differnent"                     Spell check the whole          AGREE (EDITOR: 2009-07-         EDITOR
                                 document.                      15 01:57:29Z)


"Not a STA" - a pretty odd       Change to "Not a QoS STA"      AGREE IN PRINCIPLE           EDITOR
error code                       and update any matching        (EDITOR: 2009-07-15
                                 status/enumeration in Clause   02:01:55Z)
                                 7 and Clause 10.               Change "Not a STA" to "Not a
                                                                QoS STA".

                                                                No other changes are
                                                                necessary, as the result code
                                                                in clause 7 already uses this
                                                                phrase.
NOTE--s should not carry          Change as follows:                    AGREE (GEN: 2009-09-24         EDITOR
normative verbs "may" or          254.19 & 35: may->can                 23:13:14Z)
"shall" (e.g. 625.09)             289.62: "may attempt" ->
                                  "attempts"
Note that I had an email          292.52: may->can
exchange with our IEEE-SA         293.14: may->might
project editor on this topic,     328.08: may->might
and specifically whether          580.05: shall be->are
"should" should be included in 625.09: may->can
the list of verbs that are        636.53: may->might
deprecated in informative text. 641.52: may->can
  She is of the opinion that it's 649.22: may->can
OK to include "should" in         649.51 & 53: may->can
informative text because it       652.28: may->can
has no absolute normative         652.30: may-> can
effect. So, I have not            653.59: may not->cannot
included any "should"s in the 653.60: may->can
list of things to change.         656.39: may->might
                                  1479.48: may be->is set to
NOTE uses the wrong format Set using the correct style                  AGREE (EDITOR: 2009-07-        EDITOR
                                                                        15 02:22:34Z)

"shall be commenced" - it's          "shall start"                      AGREE (EDITOR: 2009-07-        EDITOR
English, Jim, but not as we                                             15 02:15:40Z)
know it
"defined in this subclause" -        Replace "this subclause" with      AGREE (EDITOR: 2009-07-        EDITOR
with the addition of heading         "subclauses 11.9.0a to             15 02:18:50Z)
...0a, the reference is              11.9.7a"
incorrect.
The word "bit" is used,              Replace all uses of the word       DISAGREE (EDITOR: 2009-        EDITOR
wrongly, as a synonym for            "bit" that are not dependent in    07-27 11:07:30Z)
"field" in a 1-bit sized field.      that context on the field being
This confuses purpose (a             precisely 1 bit in size and that   TGmb does not support this
field) with representation (a        are not calling out individual     change - i.e., it was
single bit).                         bits from a bitfield.              discussed at length in July
                                                                        2009, but no consensus
                                                                        emerged in support.
It is not exactly clear which of Indent the para starting "A            AGREE (SECURITY: 2009-07- EDITOR
the three dashed list items are STA may operate when..."                14 22:02:34Z)
part of the exception.

"Only the STA starting an            Change to: "Only the STA           AGREE (SECURITY: 2009-07- EDITOR
IBSS may specify a schedule          that is the DFS owner in an        14 22:02:42Z)
of quiet intervals" - isn't it the   IBSS may specify a schedule
job of the DFS owner? The            of quiet intervals"
STA that started the IBSS
may be long dead and buried.

"A STA shall not transmit in a       Relate to observable state or      AGREE IN PRINCIPLE             EDITOR
channel unless it has been           on-the-air signalling.             (SECURITY: 2009-08-14
tested for the presence of                                              16:45:51Z)
radars according to                                                     In Clause 11.9.3, replace
regulatory requirements."                                               "shall not" with "does not".
                                                                        In Clause 11.9.4, replace
Presumably it uses its well-                                            "shall discontinue" with
honed telepathic abilities to                                           "discontinues".
determine if the channel has
been tested.
The author has forgotten that   p630.53: BSS->infrastructure   AGREE (SECURITY: 2009-07- EDITOR
the term BSS applies both to    BSS                            14 22:02:57Z)
infrastructure and              p630.58: "BSS or IBSS" ->
indepdendent.                   BSS (make change globally)




STAs are not living, breathing There are 3 "desire"s, 16       AGREE IN PRINCIPLE             EDITOR
entities. They have no wants, "wants". Replace as              (EDITOR: 2009-07-01
desires, aspirations etc..     appropriate with non-           14:31:45Z) - In 3.77: desired-
                               anthropomorthic language.       >required
Remove anthropomorhpic                                         p38.36: delete "desired"
language                                                       p44.27: desired->intended
                                                               p59.01: Replace "If the SME
                                                               wants to set up a security
                                                               association to the peer STA,
                                                               but does not know the security
                                                               policy of the peer, it should
                                                               send..." with
                                                               "In order to set up a security
                                                               association to the peer STA, a
                                                               SME that does not know the
                                                               security policy of the peer
                                                               should send..."
                                                               p59.09: Replace "If a STA
                                                               received a 4-Way Handshake,
                                                               wants to set up a security
                                                               association to the peer STA,
                                                               but does not know the security
                                                               policy of the peer, it should
                                                               send..."
                                                               with " In order to set up a
                                                               security association to the
                                                               peer STA, a STA that
                                                               received a 4-Way Handshake
                                                               but does not know the security
                                                               policy of the peer should
                                                               send"
                                                               p 59.21 & 22: wants-
The equation on line 62 is      Set as a display equation.     >intends(EDITOR: 2009-07-
                                                               AGREE                          EDITOR
hard to parse with all the      Move units into the where      20 11:29:41Z)
brackets and microseconds.      clause
"defined in dBm using the         remove "units and"             AGREE (SECURITY: 2009-07- EDITOR
same units"                                                      14 22:03:01Z)

But dBm are the units.
"shall be as required for         Turn para into note, and add   DISAGREE (SECURITY:           EDITOR
operation in the regulatory       references to any known        2009-08-21 15:29:25Z)
domain"                           regulations on this matter.    The value is dependent on the
                                                                 regulatory domain that the
- this is a useless statement.                                   STA is operating in. There is
If regulations require                                           no single reference for this
something, this says                                             value.
effectively "you shall do what
you shall do", without actually
specifying what that is.



"If                            Change cited text to: If          AGREE (SECURITY: 2009-07- EDITOR
dot11RRMTriggeredTransmitS     dot11RRMTriggeredTransmitS        14 22:03:10Z)
treamCategoryMeasurementE      treamCategoryMeasurementE
nabled is true, a QoS STA      nabled is true and has no
shall accept a triggered       resource contraint that
Transmit Stream/Category       prevents it from being able to
Measurement and shall reject   make the requested
it otherwise."                 measurement, a QoS STA
                               shall accept a
This contradicts the previous triggered Transmit
sentence that allows a         Stream/Category
resource limit to generate a   Measurement and shall reject
rejection.                     it otherwise.
"A Neighbor Report is sent by Describe what "validated"          AGREE IN PRINCIPLE              EDITOR
an AP and it contains          means in this context.            (SECURITY: 2009-07-14
information on validated AP’s"                                   22:03:33Z)
                                                                 "Propose Counter.
The concept of a valid or                                        Replace ""on valdiated AP's""
invalid AP is not known to me.                                   with
                                                                 ""on neighboring AP's"""

There are ~1000 instances of      Research rules for             AGREE IN PRINCIPLE              EDITOR
"true" of which, 3/4 use the      capitalization of true and     (EDITOR: 2009-07-27
lower-case form and 1/4 use       false, and then apply them     10:40:37Z)
the upper case form. There        consistently throughout the
appears to be no rhyme or         standard.                      	 ake all “true” and “false”
                                                                 M
reason as to which to use for                                    lower case, except where they
any particular purpose.                                          are part of or reference
                                                                 pseudo-code or code.
"A serving AP shall include a        Scan the entire draft for       AGREE IN PRINCIPLE               EDITOR
TSF information field in the         occurances of "shall <verb>     (SECURITY: 2009-08-21
Neighbor Report element only         only if <condition>" and for    15:35:10Z)
if it is able to                     each convert to one of these    Change the following
guarantee an accumulated             unambiguous forms.              occurences as indicated:
error of 1.5 TU or better on                                         p379.58: "shall inspect the
the TSF Offset subfield."            In this case (and, I suspect,   frame body only if the frame
                                     in most), form A is             is"
"... shall <verb> only if            appropriate.                    ->
<condition> " is highly                                              "shall not inspect the frame
ambiguous.                                                           body unless the frame is"

What does it mean?                                                   p643.58: "the STA shall
A: "shall not <verb> if not                                          respond with a Beacon Report
<condition>"                                                         only if the indicated Beacon
B: "may <verb> if <condition>                                        Reporting Condition is true."
and shall not <verb>                                                 ->
otherwise"                                                           "the STA shall respond with a
C: "shall <verb> if                                                  Beacon Report if the indicated
<condition> and shall not                                            Beacon Reporting Condition
<verb> otherwise"                                                    is true. Otherwise, the STA
                                                                     shall not respond with a
                                                                     Beacon Report."

                                                                     p645.65: "the STA shall
                                                                     create and transmit a Beacon
                                                                     Report element for that
                                                                     measured frame only if the
                                                                     condition indicated in Table 7-
                                                                     29g (Reporting Condition for
                                                                     Beacon Report) is true.
                                                                     Otherwise, a Beacon Report
It is difficult to read the inline   Convert to a display equation   element (EDITOR: 2009-07-
                                                                     AGREE is not created for that EDITOR
equation.                            with a where clause.            20 11:36:39Z)

I'm sure that there are              Work out the actual constraint AGREE IN PRINCIPLE              EDITOR
constraints within the system        and insert it here.            (SECURITY: 2009-08-21
(e.g. in TIM encoding, or                                           15:44:36Z)
where per-BSSID information                                         Change
is packed into a single                                             "The set has a maximum size
MMPDU) that limits the                                              of 2n for at least one n, where
number of BSSIDs to less                                            1 ≤ n ≤ 46."	
2**46 - which is a                                                  To
guzumpingly large number.                                           "The set has a maximum
                                                                    range of 2n for at least one n,
                                                                    where 1 ≤ n ≤ 46."
This equation split over two         Convert to a display equation AGREE (EDITOR: 2009-07-          EDITOR
lines is ugly                        over 1 line.                   20 11:47:45Z)

Spurious hyphen in                   de-hyphenify it                 AGREE (EDITOR: 2009-07-          EDITOR
dot11RRM...                                                          22 08:39:11Z)

"using the DCF or EDCA" -            Change to "the DCF or the       AGREE IN PRINCIPLE               EDITOR
EDCA is not a noun                   EDCAF"                          (EDITOR: 2009-08-10
                                                                     13:40:03Z) - Globally replace
                                                                     all uses of "DCF or EDCA"
                                                                     with "DCF or EDCF"
"For the BSS AC Access          insert "infrastructure" before    AGREE (MAC: 2009-08-07     EDITOR
Delay measurement" - we're      BSS                               00:31:17Z)
missing an adjective
"The DSE procedures may         may->might                        AGREE IN PRINCIPLE           EDITOR
also satisfy needs in other                                       (EDITOR: 2009-08-13
frequency bands and be                                            10:51:31Z) - Make the change
useful for other purposes."                                       as specified, and similar
                                                                  change to 11.9.0a, second
This was surely not intended                                      para, second sentence.
to be a normative statement.
It is unnecessary to indicate   In bullet a), change         AGREE (GEN: 2009-11-16          EDITOR
the type, subtype, category     "enablement message" to      12:11:21Z)
and action fields for this      "DSE Enablement frame".
message. It suffices to say     Delete the Dashed list items
that it formats a DSE           for message type and subtype
Enablement frame. Further       and direction of message.
the direction "from requester
to responder" is unnecessary,   This now leaves a single
because the procedure is        dashed list entry. Collapse
describing a frame              that entry into item 1) as
transmitted by the requester.   follows: "Specific information
                                items in the enablement
                                message are as follows:",
                                and promote the four bulleted
                                items up one level of nesting,
                                while changing the style to the
                                proper style for a 3-nested
                                ordered list.

                                Make matching changes in
                                11.11.2.3 and 11.11.2.4


No value is specified for the   Specify how this is set.          AGREE IN PRINCIPLE (GEN: EDITOR
Enablement identifier                                             2009-11-16 12:13:28Z)
                                                                  Accept in Principle based on
                                                                  discussion and editorial
                                                                  instructions in 09/1111r2:
                                                                  1545, 1547, 1548, 1549 and
                                                                  1550
No value is specified for the     Specify how this is set.        AGREE IN PRINCIPLE (GEN: EDITOR
Reason result code                                                2009-11-18 05:40:33Z)
                                                                  Accept in Principle based on
                                                                  discussion and editorial
                                                                  instructions in 09/1111r2:
                                                                  1545, 1547, 1548, 1549 and
                                                                  1550




A confirm should be indicated Change the logic so that a          AGREE IN PRINCIPLE (GEN: EDITOR
for every .request, including   confirm is issued in all cases.   2009-11-16 12:16:50Z)
when the enablement state                                         Accept in Principle based on
variable is not set to Enabled.                                   discussion and editorial
                                                                  instructions in 09/1111r2:
                                                                  1545, 1547, 1548, 1549 and
                                                                  1550




According to this logic, the      Assuming that the DSE           AGREE IN PRINCIPLE (GEN: EDITOR
confirm is issued at the end of   Enablement frame is             2009-11-16 12:12:18Z)
the management frame              acknowledged:                   Accept in Principle based on
transmission, before              1. Add "On receipt of an Ack    discussion and editorial
receiving any Ack, and            frame that acknowledges the     instructions in 09/1111r2
regardless of whether an Ack      DSE Enablement frame, "
is ever received or not.          before item b).
                                  2. Add a new item c) "If no
                                  acknowledgement is received
                                  for the DSE Enblement frame
                                  within a period of
                                  EnablementTimeLimit TUs
                                  measured from the receipt of
                                  the MLME-
                                  ENABLEMENT.request
                                  primitive, issue an MLME-
                                  ENABLEMENT.confirm
                                  primitive with ResultCode set
                                  to TIMEOUT.
Under what conditions can the    Define in items 1) and 2) what   AGREE IN PRINCIPLE (GEN: EDITOR
deenablement not be              comprises successful             2009-11-16 12:17:18Z)
successful? According to the     deenablement. For instance,      Accept in Principle based on
logic shown, there are no        is this the receipt of an Ack    discussion and editorial
such conditions.                 frame to the DSE                 instructions in 09/1111r2 for
                                 Denablement frame within an      CIDs 1548, 1549, and 1550
                                 unspecified timeout?


"A registered STA that is not Describe in more detail what        AGREE IN PRINCIPLE (GEN: EDITOR
an enabling STA may operate this relay is.                        2009-11-16 12:18:05Z) -
as an AP in an infrastructure                                     Accept in Principle based on
BSS and relay Public Action                                       discussion and editorial
frames (specifically, DSE                                         instructions in 09/1111r2 for
Enablement, DSE                                                   CIDs 1548, 1549, and 1550
Deenablement, DSE
Measurement Request, DSE
Measurement Report, DSE
Power Constraint) from a
dependent STA to its enabling
STA."

This is underspecified.
During the "relay" what fields
of the DSE frames are
preserved, and what
updated? Is the scope of the
relay within the AP's BSS, or
its BSA?

If the terms defined in this     Promote material in note to      AGREE (EDITOR: 2009-08-     EDITOR
note are used in normative       body (i.e., regular text)        07 08:50:26Z)
text, it is not sufficient to
define them in an informative
note.
In the ERP phy, there is an      Change the last half of the      AGREE IN PRINCIPLE            EDITOR
extension field that occurs      para starting "immediately" as   (ARCHITECTURE: 2009-11-
after the physical end of the    follows:                         18 19:28:59Z) - See CID 1556
packet that is the timing        "... immediately after the       that is resolved with changes
reference.                       symbol containing the last       as documented in 11-
                                 data octet has been              09/1233r0.
                                 transmitted and any signal
                                 extension has expired."
"This primitive is an indication   Replace with: "This primitive    AGREE (ARCHITECTURE:          EDITOR
by the PHY to the local MAC        is an indication by the PHY to   2009-07-16 06:39:52Z) At
entity that the PLCP has           the local MAC entity that the    these prices, I've stopped
received a valid start frame       PLCP has received a valid        buying lard.
delimiter (SFD) and PLCP           start of a PPDU, including a
header."                           valid PLCP header."

This was written in those
charmingly quaint days of
yore when tuppence would
buy a pound of lard, PHY
rates could be expressed in
an octet field with a resolution
of 500kbps, and packets had
SFD fields.

Unfortunately - this is no
longer true - the price of lard
has risen.
The editor is an idiot. He      Add an "s" after "parameter".       AGREE (EDITOR: 2009-07-       EDITOR
says he corrected this line for                                     23 10:42:09Z)
grammar, but forgot all about
plural and singular forms.

In the case of a signal            Add a note: "NOTE--When a        AGREE IN PRINCIPLE            EDITOR
extension, this primitive must     signal extension is present      (EDITOR: 2009-08-07
be delayed until the end of the    after the physical end of the    08:52:05Z)
signal extension - because         PPDU, this primitive is issued   Add note as specified after
that is the timing reference for   at the end of the signal         first para of 12.3.5.12.3.
the MAC.                           extension."

A note here would usefully
clarify this point.
TGn found it necessary to     Either:                            AGREE IN PRINCIPLE (GEN: EDITOR
modify the PLCP tx and rx     1. Introduce state machines        2009-11-18 19:16:27Z) see
state machines to represent   for clause 19 (a lot of work) or   09/1233r0 for editing
the timing of the signal      2. Make normative statements       instructions.
extension related to the      in 12.3.5.7.3 and 12.3.5.12.3
RXEND and TXEND               that achieves this effect. See
primitives.                   also my other two comments
                              to these subclauses which will
There is no normative         need to be adjusted as they
statement that shows the      assume option 1, or
RXEND.indication or           3. Make normative statements
TXEND.confirm for a clause    in 19.3.4 and 19.3.6 that
19 PHY occuring at the end of achieves this effect.
the signal extension.




RSNA Security services         Promote to its own bullet. Or, AGREE IN PRINCIPLE           EDITOR
management is a sub-item of    if PC34 suffices, remove       (EDITOR: 2009-08-07
WEP!                           PC2.3.                         09:24:36Z) - Remove PC2.3.
There is confusion in the        Add a CF2.1 and a CF2.2          AGREE IN PRINCIPLE (GEN: EDITOR
definition of CF2 as to          which are "operation in an       2009-09-24 19:49:52Z) -
whether it applies to a non-AP   infrastructure BSS" and          Accept in principle -- In
STA in an infrastructure BSS,    "operation in an IBSS", with     addition to defining CF2.1 and
or a STA in an IBSS. I           status CF2:M for the first and   CF2.2 as in proposed change:
believe it is quiet reasonable   CF2:O for the second..
to have a STA that is not        Review all all uses of CF2 in    "Add a CF2.1 and a CF2.2
capable of operating in an       the status column and change     which are "operation in an
IBSS, but PC11.2 says any        to CF2.1 or CF2.2 where they     infrastructure BSS" and
non-AP STA has to be able to     are specific to either mode of   "operation in an IBSS", with
perform IBSS timing.             operation.                       status CF2:M for the first and
                                                                  CF2:O for the second,
                                 Note PC11.3 should not be
                                 required for a non-IBSS-     Adjust other PICS as follows:
                                 capable non-AP STA.          PC5CF2.1
                                                              PC11.2CF2.2
                                                              PC11.6CF2.2
                                                              PC11.7CF2.1 or CF2.2
                                                              PC11.8CF2.1 or CF2.2
                                                              PC12.1CF2.1 or CF2.2
                                                              PC12.5CF2.1 or CF2.2
                                                              PC13CF2.2
                                                              PC13.1CF2.2
                                                              PC13.2CF2.2
                                                              PC13.3CF2.2
                                                              PC14.2       CF2.1
                                                              PC14.4       CF2.1
                                                              PC34.1.9CF2.2
                                                              FT1CF2.1
                                                              FT3CF2.1
                                                              FT5CF2.1 or CF2.2
                                                              FT8CF2.1 or CF2.2
A date format of dd/mm/yy      Change format to yyyy-mm-dd FT12CF2.1
                                                              AGREE (EDITOR: 2009-07-              EDITOR
has a couple of problems with                                 23 12:40:59Z)
it:
1. it is ambiguous with
respect to centuries and
millenia
2. It may be misread by those
who use mm/dd/yy
There's a lot of duplicate     Review the draft and replace AGREE IN PRINCIPLE                     EDITOR
specification of how to treat  all phrases such as "set to 0  (EDITOR: 2009-08-06
fields that are reserved under on transmission and ignored    08:22:56Z)
all or certain circumstances.  on reception" with "reserved". Please see resolution of CID
                                                              1707, which performs this
7.1.1 suffices to define a                                    review in Clause 7.
treatment for all reserved
fields. It is not necessary to
repeat this elsewhere.

The "N/A" entry it not           Remove the "N/A" option.         AGREE (EDITOR: 2009-07-          EDITOR
appropriate to a mandatory                                        23 12:41:52Z)
feature
The "heading" OF10 has           Join them up.                    AGREE (EDITOR: 2009-07-          EDITOR
gotten separated from the                                         23 12:43:28Z)
following two rows.
Whereever the Status column Review Annex A and insert            AGREE IN PRINCIPLE               EDITOR
is not an unqualified M, "N/A" missing N/A options where         (EDITOR: 2009-07-23
should be one of the options. the Status is not a plain "M".     12:14:19Z)
It is not always present (e.g.                                   Add "N/A" where item is
1071.08)                                                         optional. An item is optional if
                                                                 any of the chain items
                                                                 referenced in the Status
                                                                 column is itself optional.

                                                                 In A4.7, add missing "No"
                                                                 options where Status contains
                                                                 only "Yes"
                                                                 Add missing Yes/No to
                                                                 HRDS9
Two blank pages                     Remove them                  AGREE (EDITOR: 2009-07-       EDITOR
                                                                 23 12:49:57Z)




The SDL hasn't been updated         Remove Annex C and any       AGREE IN PRINCIPLE             EDITOR
for a long time (at least 10        references to it. Trim the   (EDITOR: 2009-09-23
years). While it used to have       Bibliography to remove the   18:52:42Z) - The bibliograpy
normative value in answering        SDL references.              has been trimmed as in
some questions, any relevant                                     comment resolution to CID
such answers should now be                                       1026. See also comment
part of the text through                                         resolution of CID 1369.
REVma comment resolution.

It is at best just an annoying
padding of 200 pages of
diagrams.

It is, at its worst, misleading -
where normative rules it
expressed from the early
802.11 mesolithic era were
modified by subsequent
amendments.


Annex E one line 4 claims to        Change "informative" to      AGREE (EDITOR: 2009-08-        EDITOR
be informative.                     "uninformative".             07 09:26:38Z)

I beg to differ. This, one a
scale that encompasses the
literary output of a newt's
brain at one end (rating zero)
and the collected works of
Vogon poetry at the other
(rating 10), scores about -1.
Channel agility was added for Deprecate this feature in no         AGREE IN PRINCIPLE (GEN: EDITOR
political reasons during the  uncertain terms - or remove it       2009-09-24 01:11:00Z) Agree
early days of 802.11b. As far entirely.                            in Principle -- Mark this Annex
as I know, nobody ever used                                         as deprecated and subject to
it.                                                                removal in a future revision
                                                                   Editor to add immediately
Furthermore, coexistence of                                        following the clause heading
a wide-band frequency                                              the following new paragraph:
hopper and wide-band non                                           This annex is obsolete and is
frequency hoppers is likely to                                     subject to removal in a future
be very bad. So if anybody                                         revision
was daft enough to actually
use this, most of the time
they would encounter a partial
overlap with static 802.11b/g
devices.

"However, if a TSPEC is          In annex K, replace all "may"     AGREE (EDITOR: 2009-08-   EDITOR
generated subsequently by        with "can" and all "shall be"     07 14:12:08Z)
the SME, the TSPEC               with "is".
generated autonomously by
the MAC shall be overridden"     From my research on the
                                 topic, I see nothing that calls
A Normative verb is not          out "should" as a word that
allowed in an informative        cannot be used in an
Annex.                           informative annex, so I think
                                 these can stand.
The top of this equation is      Untruncate it                     AGREE (EDITOR: 2009-07-   EDITOR
truncated                                                          24 08:55:06Z)

The top of this equation is      Untruncate it                     AGREE (EDITOR: 2009-07-   EDITOR
truncated                                                          24 11:18:23Z)
This equation and the            Restructure it.          AGREE IN PRINCIPLE               EDITOR
following one and the                                     (EDITOR: 2009-07-24
previous text should be                                   11:33:23Z)
restructured as necessary to                              Replace the paragraph at
give a "where" paragraph that                             1504.20 with the following:
fully describes the variables of                          "For the calculation of the
the equation.                                             TXOP duration for an
                                                          admitted stream, the
                                                          scheduler uses the following
                                                          parameters: Mean Data Rate
                                                          and Nominal MSDU Size; and
                                                          from the negotiated TSPEC,
                                                          the Scheduled Service
                                                          Interval calculated above,
                                                          Physical Transmission Rate,
                                                          Maximum Allowable Size of
                                                          MSDU, and Overhead. The
                                                          Physical Transmission Rate is
                                                          the minimum PHY rate
                                                          negotiated in the TSPEC. If
                                                          the minimum PHY rate is not
                                                          committed in the ADDTS
                                                          Response frame, the
                                                          scheduler can use the
                                                          observed PHY rate as the
                                                          Physical Transmission Rate.
                                                          The Overhead includes IFSs,
                                                          ACK frames and CF-Poll
                                                          frames. For simplicity, details
                                                          for the Overhead calculation
                                                          are omitted in this description.
                                                          The TXOP duration is
The top of this equation is      Untruncate it            calculated as follows: First,
                                                          AGREE (EDITOR: 2009-07-          EDITOR
truncated                                                 24 11:42:42Z)

I find the naming of "WLAN    Rename "WLAN system" to     DISAGREE (MAC: 2009-08-        EDITOR
system" confusing. I'd expect "WLAN infrastructure"       07 00:39:31Z) Definition 3.171
the MU to be part of that                                 defines a WLAN system as
system, i.e. they are clearly                             excluding mobile units.
part of a WLAN, but
apparently not part of a WLAN
system.
2 blank pages                 remove                      AGREE (EDITOR: 2009-07-       EDITOR
                                                          24 11:43:47Z)

This describes the use of Add NDIS expansion to           AGREE IN PRINCIPLE            EDITOR
NDIS. However NDIS is not abbeviations. Add NDIS          (EDITOR: 2009-08-07
defined.                  reference to Bibliography and   10:22:57Z) - Delete cited
                          cite from here.                 sentence.
This describes the use of Add SNMP expansion to           AGREE IN PRINCIPLE            EDITOR
SNMP. However SNMP is not abbeviations. Add SNMPv2        (EDITOR: 2009-08-07
defined.                  reference to Bibliography and   10:30:45Z) -
                          cite from here.                 Add RFC1157 to the
                                                          Bibliography and reference
                                                          from here.
It is dangerous to define an         Move definition of this           AGREE IN PRINCIPLE            EDITOR
object identifier using              identifier to Annex D, add        (ARCHITECTURE: 2009-11-
dot11smt away from where             comment there saying that the     18 00:35:20Z) Annex Q will be
the other identifiers are            object itself is defined in       merged into Annex D.
defined, because somebody            Annex Q. Add comment at
may not check this separate          cited location to say this
Annex and attempt to re-use          identifier is defined in Annex
the same number.                     D.




"It shall update this attribute to   Move description of how the       DISAGREE                        EDITOR
a proper value other than 0 as       SME maintains the RRM MIB         (ARCHITECTURE: 2009-11-
soon as it is capable of             to a normative clause outside     18 20:44:41Z) The
receiving new measurement            the SME MIB.                      commentor is encouraged to
requests."                                                             provide more details of any
                                     This will involve searching for   proposed improvement, but
As I understand it, the              shalls in this Annex and          without the details of what is
purpose of the description is        moving/restructuring text as      proposed, the group cannot
to carry information to help         appropriate.                      evaluate the technical merit at
the user of the object                                                 this time.
understand how to interact
with it. This is normative
specification for the SME,
and belongs in a normative
subclause outside the MIB.
unwanted linebreak                   remove                            AGREE (EDITOR: 2009-07-        EDITOR
                                                                       24 11:46:26Z)

Wrong font for "Annex J",            fix font                          AGREE (EDITOR: 2009-07-        EDITOR
ditto line 18.                                                         24 11:49:54Z)

Ditto 1553.56
What't the point in defining an Somebody explain to me the             DISAGREE                       EDITOR
enumeration of only one         value of this MIB entry - or           (ARCHITECTURE: 2009-07-
member?                         remove it.                             16 06:40:31Z) Typical future
                                                                       looking stuff, this.
Awkward line break                   fix it                            AGREE (EDITOR: 2009-07-        EDITOR
                                                                       24 11:54:28Z)

Wrong indent                         fix it                            AGREE IN PRINCIPLE             EDITOR
                                                                       (EDITOR: 2009-07-24
                                                                       11:57:02Z) - Adjust indent and
                                                                       change "filed" to "field".
Wrong indent - 3 lines               fix it                            AGREE (EDITOR: 2009-07-        EDITOR
                                                                       24 11:58:48Z)
It is dangeration defining       Add comment in AnnexD in         AGREE IN PRINCIPLE            EDITOR
children of the dot11Groups      appropriate place so that it's   (ARCHITECTURE: 2009-11-
object in Annex Q.               painfully clear where the        18 00:35:20Z) Annex Q will be
                                 numbering has to restart. Or     merged into Annex D.
                                 move these definitions into
                                 AnnexD, with a comment
                                 here indicating that these
                                 objects are defined in AnnexD.

The contact information is      Remove WG Email. Update           AGREE IN PRINCIPLE          EDITOR
incorrect.                      chair.                            (EDITOR: 2009-07-23
1. The chair details have                                         13:23:32Z)
changed                                                           As specified, also update
2. It is useless to quote WG                                      Tech Editor and remove
E-mail as only those within the                                   unknown details.
WG have access to this, and
they already know about it.

Either explain this reference    As in comment.                   AGREE IN PRINCIPLE          EDITOR
or remove it.                                                     (EDITOR: 2009-08-07
                                                                  09:26:17Z) - remove cited
                                                                  reference.
", and is accessed big-endian." Remove cited text.                AGREE (ARCHITECTURE:        EDITOR
                                                                  2009-07-16 06:41:04Z)
This makes no sense.               Same action on lines 52, 64,
Endianness is only of a            1346.10, 22, 24, 55, 1347.2,
concern when extracting a          15, 29, 44
smaller field from a larger
field. Here we have an
integer of range 0..63, and
that's all that it is necessary to
say.
There's a number of MIB           Wherever possible, move all      AGREE IN PRINCIPLE             EDITOR
variables that define a default   statements of default value      (EDITOR: 2009-08-07
value in the description, but     solely into a DEFVAL part.       14:10:48Z) - Add any missing
have no DEFVAL statement.                                          defval statements, and
                                                                   remove any specification of
There are other variables that                                     default value in the
do both - which creates a                                          description in the following
maintenance issue.                                                 variables:

                                                                   Annex D:
                                                                   dot11MediumOccupancyLimit

                                                                   dot11PrivacyOptionImplement
                                                                   ed
                                                                   dot11MultiDomainCapabilityIm
                                                                   plemented
                                                                   dot11MultiDomainCapabilityEn
                                                                   abled
                                                                   dot11SpectrumManagementIm
                                                                   plemented
                                                                   dot11SpectrumManagementR
                                                                   equired
                                                                   dot11RegulatoryClassesImple
                                                                   mented
                                                                   dot11RegulatoryClassesRequi
                                                                   red
                                                                   dot11QosOptionImplemented

                                                                   dot11ImmediateBlockAckOptio
                                                                   nImplemented
                                                                   dot11DelayedBlockAckOptionI
                                                                   mplemented
"The value of this attribute      Remove cited text.               dot11DirectOptionImplemente EDITOR
                                                                   AGREE (ARCHITECTURE:
shall never be less than 256."                                     2009-07-16 06:41:21Z)

This is unnecessary, because
the syntax already captures
this.

The description should be         Replace superscript with ^.      AGREE IN PRINCIPLE             EDITOR
readable as ascii text.           Ditto on line 55, and 1360.65,   (EDITOR: 2009-07-23
                                  and 1363.06, 24                  14:30:38Z)
                                                                   As specified and make same
                                                                   change at 1360.47.
Bad formatting                    Fix                              AGREE (EDITOR: 2009-07-        EDITOR
                                                                   24 08:37:54Z)
"Valid values are:              If we are allowed to change       AGREE IN PRINCIPLE                EDITOR
energy detect only              this, change the syntax to an     (ARCHITECTURE: 2009-11-
(ED_ONLY) = 01,                 enumeration with these            16 15:52:45Z) Remove the
carrier sense only              values, and remove values         meaningless "or the logical ...
(CS_ONLY) = 02,                 from the description.             values"
carrier sense and energy
detect (ED_and_CS)= 04          In any case remove the
or the logical sum of any of    meaningless "or the logical ...
these values."                  values"
The term "logical sum" is
poorly defined.

Speaking logically, we can
only have 3 meaningful
values, and these have
already been enumerated.
There are more notifications    Update the description to  DISAGREE                        EDITOR
                                                           (ARCHITECTURE: 2009-11-
than these defined in this MIB. indicate the basis of selection
                                of this group (i.e. those  18 20:44:57Z) - The
                                supported by all STA).     commentor is encouraged to
                                                           provide more details of any
                                                           proposed improvement, but
                                                           without the details of what is
                                                           proposed, the group cannot
                                                           evaluate the technical merit at
                                                           this time.
The SNMP-v2 RFCs indicate Update the description of        AGREE IN PRINCIPLE              EDITOR
that when an object-group is  each deprecated object group (ARCHITECTURE: 2009-11-
marked as deprecated, the     to indicate "superseded by   18 19:21:38Z) - see
description should be updated <object-name>".              09/1233r0 for editing
to indicate why.                                           instructions.
How can REVmb be sure that Run a MIB compiler on it and          AGREE IN PRINCIPLE             EDITOR
the MIB is syntactically   correct any syntactic errors.         (EDITOR: 2009-08-04
correct?                                                         16:16:01Z) - Make changes
                                                                 as shown in document 11-
                                                                 09/0921r1. These result in a
                                                                 combined MIB that compiles
                                                                 without errors or warnings.

                                                                 Note, this necessitated
                                                                 renumbering
                                                                 dot11RegulatoryClassGroup
                                                                 (dot11Groups 29) to avoid
                                                                 collision with
                                                                 dot11RSNSMKcachingGroup.



                                                                 Also correct any references
                                                                 outside Clause Q from
                                                                 "dot11RMStatisticsMeasaurem
                                                                 entEnabled" to
                                                                 "dot11RMStatisticsMeasureme
                                                                 ntEnabled".
dot11FTComplianceGroup           The three missing entries are   AGREE IN PRINCIPLE            EDITOR
object number is not             in Annex Q. Move them here      (ARCHITECTURE: 2009-11-
contiguous                       or reference them from here     18 00:35:20Z) Annex Q will be
                                 so that the numbering is        merged into Annex D.
                                 explained.




Numerous references in the       Check every reference in the    AGREE IN PRINCIPLE              EDITOR
standard are not "live" - i.e.   draft and replace non-live      (EDITOR: 2009-06-30
they do not show a link in the   references with live ones.      11:11:58Z) -
.pdf when the cursor is                                          Update references at at least
hovered over them.                                               the following locations: 52.10,
                                                                 361.31, 365.44, 401.04,
This is dangerous, as it                                         423.13, 597.06, 597.10,
means that any future                                            597.14, 735.27, 735.45,
renumbering may result in an                                     766.64, 786.10, 786.15,
incorrect reference.                                             801.18, 802.17, 803.17,
                                                                 812.05, 817.09, 817.16,
                                                                 820.52, 822.24, 886.13,
                                                                 938.47, 1388.29, 1390.58,
                                                                 1391.04, 1391.15, 1391.26,
                                                                 1391.37, 1391.48 and
                                                                 1423.16.

                                                                 Note, this does not address
                                                                 any references in Annex C.
The correct treatment of a      Either show the two missing     DISAGREE                        EDITOR
deprecated attribute is to      attributes, or replace the      (ARCHITECTURE: 2009-11-
show the definition with a      comment that these entries      18 20:45:12Z) - The
status of deprecated.           are not in use.                 commentor is encouraged to
                                                                provide more details of any
                                                                proposed improvement, but
                                                                without the details of what is
                                                                proposed, the group cannot
                                                                evaluate the technical merit at
                                                                this time.
There are a number of places Remove trailing blank              AGREE (EDITOR: 2009-06-         EDITOR
where a DEFVAL line ends     comments from all MIB lines.       29 11:54:34Z)
with a blank comment. This
is unnecessary.

There's a note embedded in      Replace "Note, however, "       AGREE IN PRINCIPLE            EDITOR
the para in the wrong format.   with "NOTE--" and format        (EDITOR: 2009-07-02
                                appropriately.                  13:18:39Z)
                                                                Convert to note as follows:
                                                                "NOTE--This collision
                                                                behavior does not..."
"An AP may indicate              Replace with: "An AP may       AGREE (MAC: 2009-07-14        EDITOR
availability of CF-Polls to non- transmit a CF-Poll to a non-   15:32:20Z). Accept the
QoS STAs"                        QoS STA"                       proposed change.

This is not what it means.
"Only MPDUs with a unicast      Delete cited text.              AGREE (MAC: 2009-07-14        EDITOR
receiver address shall be                                       15:33:09Z)
fragmented."

This is problematical. Which
of the three possible
interpreations of "only
<condition> shall <verb>"
apply here?

It's also redundant given the
next sentence.
"that would result in a length   Replace cited text with: "that AGREE (MAC: 2009-07-14           EDITOR
greater than                     would result in an MPDU of     15:33:57Z)
dot11FragmentationThreshold      length greater than
when the                         dot11FragmentationThreshold
MAC header and FCS are           "
added"

This ignores the effect of any
other encapsulations done in
the MAC layer, for example,
security or tunnelling of
MMPDUs.




The last sentence of p361 up     Merge the conditions for        AGREE IN PRINCIPLE (MAC: EDITOR
to line 7 of 362 appear to say   sending fragments of a single   2009-09-24 21:40:13Z) -
almost-but-not-quite-the-        MSDU or MMPDU into a            Change cited paragraph as
same-thing twice - i.e. they     single list.                    follows:
are partly redundant and
partly inconsistent.                                             "The MPDUs resulting from
                                                                 the fragmentation of an
                                                                 MSDU or MMPDU are sent as
                                                                 independent transmissions,
                                                                 each of which is separately
                                                                 acknowledged. This permits
                                                                 transmission retries to occur
                                                                 per fragment, rather than per
                                                                 MSDU or MMPDU. The
                                                                 fragments of a single MSDU
                                                                 or MMPDU are either
                                                                 - Sent during a CFP as
                                                                 individual frames obeying the
                                                                 rules of the PC medium
                                                                 access procedure or
                                                                 - Sent as a burst in an EDCA
                                                                 or HCCA TXOP, subject to
                                                                 TXOP limits and medium
                                                                 occupancy limits for the
                                                                 attached PHY"
Some bits of the DCF have       Create a new subclause "Bits    AGREE (MAC: 2009-11-13            EDITOR
been reused by EDCA, and        of DCF used by EDCA" and        19:44:43Z) - Create a new
some superseded. There is       move the bits of DCF that are   subclause
no clear distinction between    used by EDCA into this          9.2.5.0a (Procedures
these.                          subclause. This should          common to the DCF and
                                include:                        EDCAF), with the following
                                CS Mechanism, IFS, Setting      new subclause:
                                and resetting the NAV,
                                RTS/CTS with fragmentation,     "9.2.5.0a.1 (Introduction)
                                CTS procedure, Ack              Subclause 9.2.5.0a contains
                                Procedure, Duplicate            procedures common to the
                                detection and recovery, DCF     operation of the CSMA/CA
                                timing relationships, NAV       channel access mechanisms
                                distribution, operation of      defined in this standard, i.e.,
                                aSlotTime.                      the DCF and the EDCAF."

                                                                Move the following
                                                                subclauses from 9.2.5 into
                                                                9.2.5.0a, renumbering
                                                                appropriately.
                                                                -CS mechanism
                                                                -MAC-Level
                                                                Acknowledgements
                                                                -IFS
                                                                -Setting and resetting the
                                                                NAV
                                                                -RTS/CTS with
                                                                fragmentation
                                                                -CTS procedure
                                                                -ACK procedure
                                                                -Duplicate detection and
                                                                recovery
"All STAs...". A normative    Delete "shall" in cited           -NAV distribution
                                                                AGREE IN PRINCIPLE (MAC: EDITOR
requirement cannot be placed sentence.                          2009-09-24 21:11:10Z) -
on more than one STA.                                           Rewrite sentence as: "A STA
Furthermore, "shall learn" is                                   receiving either the RTS (sent
not defined.                                                    by the originating STA) or the
                                                                CTS (sent by the destination
                                                                STA) shall process the
                                                                medium reservation."


"The medium reservation         Replace "BSA" with "BSS".       AGREE (MAC: 2009-09-24            EDITOR
mechanism works across the                                      21:34:26Z)
BSA boundaries."

Actually it doesn't. It works
across BSS boundaries in the
same or partly overlapping
BSA.
"The RTS/CTS mechanism           Replace "need" with "is".   AGREE IN PRINCIPLE (MAC: EDITOR
need not be used for every                                   2009-09-24 21:13:01Z) -
data frame transmission."                                    Replace "need not be used"
                                                             with "is not used".
This appears to give license
not to use the mechanism,
but the following paragraph
indicates that the mechanism
is controled solely through a
MIB variable. So to whom is
the "not always justified"
directed? Surely the
management entity that sets
this MIB variable, and not the
MAC sublayer.

"This attribute may be set on    Remove cited text.          DISAGREE (MAC: 2009-09-       EDITOR
a per-STA basis."                                            24 20:56:38Z) - "May" is
                                                             informative language, and the
This is true, but doesn't                                    language may offer useful
require this statement to make                               guidance to implementers.
it so.
"A STA configured not to         Remove normative language   AGREE (MAC: 2009-09-24           EDITOR
initiate the RTS/CTS             and turn into a NOTE--.     20:58:47Z) - Replace
mechanism shall still update                                 sentence with an informative
its virtual CS mechanism with                                note reading: "NOTE-- A STA
the                                                          configured not to initiate the
duration information contained                               RTS/CTS mechanism
in a received RTS or CTS                                     updates the virtual CS
frame, and shall always                                      mechanism with the duration
respond to an RTS addressed                                  information contained in a
to it with a CTS if permitted by                             received RTS or CTS frame,
medium access rules."                                        and responds to an RTS
                                                             addressed to it with a CTS if
But the rules specified                                      permitted by medium access
elsewhere for these protocols                                rules."
make no exception for a STA
that doesn't transmit RTS, so
this statement is unnecessary.
"To the initiator of the frame    Change the cited sentence to   AGREE (MAC: 2009-09-24         EDITOR
exchange, this                    something that is true.        21:31:03Z) - Change the cited
condition is indistinguishable                                   sentence to read: "When an
from an error occurring in the                                   ACK is lost, the MAC that
initial frame."                                                  initiated the frame exchange
                                                                 does not receive a protocol
Actually, it's not true. In the                                  indication whether the initial
case of a corrupted Ack, the                                     frame was correctly received."
initiator will see at least
energy, and probably PHY-
RXSTART at the expected
time.

We rely on the PHY-
RXSTART behaviour in a
number of places in the spec.


"A STA using the DCF shall       Replace "shall be allowed to"   AGREE (MAC: 2009-09-24           EDITOR
be allowed to transmit if its CS with "may". That wasn't too     21:31:12Z)
mechanism (see 9.2.1)            painful was it?
determines that the medium is
idle at the TxDIFS slot
boundary as defined in 9.2.10
after a correctly received
frame, and its backoff time
has expired."

"Shall be allowed" is
wonderfully opaque and of
doubtful normative relevance.
"The AIFS shall be used by    Add "that access the medium        AGREE IN PRINCIPLE (MAC: EDITOR
QoS STAs to transmit all data using the EDCAF" after             2009-09-24 21:21:38Z) -
frames"                       "STAs".                            Change cited text to read
                                                                 "The AIFS shall be used by
Too broad. For example it                                        QoS STAs that access the
creates a conflict with data                                     medium using the EDCAF to
transmitted under HCCA.                                          transmit: all data frames, . . ."

                                                                 Note to editor: a colon is
                                                                 added after the word transmit,
                                                                 which is why the resolution is
                                                                 an agree in principle.


"the EDCA" - EDCA is an           Globally replace any "the     AGREE (EDITOR: 2009-07-           EDITOR
adjectival phrase, not a noun     EDCA" with "the EDCAF"        02 13:31:12Z)
                                  where not followed by a noun.

This para "A STA using the        Delete cited para.             AGREE (MAC: 2009-09-24           EDITOR
EDCA..." is talking about                                        21:31:21Z)
EIFS, not AIFS.

Furthermore, the content is
redundant with 9.2.3.5.
"A STA desiring to initiate     Insert: "using the DCF" after      AGREE (MAC: 2009-09-24    EDITOR
transfer of data MPDUs          MMPDUs.                            21:31:31Z)
and/or MMPDUs shall invoke
the CS mechanism (see
9.2.1) to determine the
busy/idle state of the medium."

This is only true for DCF.

"Basic access refers to the        Insert "using the DCF" at the   AGREE (MAC: 2009-10-30    EDITOR
core mechanism a STA uses          end.                            16:00:30Z)
to determine whether it may
transmit." - too general

"may not" is not the intent here may not -> might not              AGREE (EDITOR: 2009-07-   EDITOR
                                                                   02 13:34:38Z)

"This duplicate MSDU shall be      Replace cited text with a       AGREE (EDITOR: 2009-08-   EDITOR
filtered at the receiving STA      footnote:                       07 14:11:31Z)
using the normal duplicate         "This duplicate MSDU is
frame                              filtered at the receiving STA
filtering mechanism."              using the duplicate frame
                                   filtering mechanism."
There are several problems:
1. The duplicate cache is of
limited depth, filtering cannot
be guaranteed
2. There is no need for a
normative statement here,
becuase there is nothing
special in this case about
duplicate detection
3. "normal" implies there's
also an "abnormal"
"A STA shall use an RTS/CTS        Replace with: "A STA using     AGREE (MAC: 2009-09-24     EDITOR
exchange for individually          the DCF shall use an           21:31:37Z)
addressed frames only when         RTS/CTS exchange for
the length of the MPDU             individually addressed frames
is greater than the length         when the length of the MPDU
threshold indicated by the         is greater than the length
dot11RTSThreshold attribute."      threshold indicated by the
                                   dot11RTSThreshold attribute,
A "shall ... only" statement.      or when required to do so to
Which of the possible three        achieve protection (see 9.13).
meanings are intended here?        Otherwise a STA using the
Also, other reasons to use         DCF shall not use the
RTS exist when protection is       RTS/CTS exchange."
required - is this statement too
broad.
"The dot11RTSThreshold          "shall be" -> "is"; "may" ->    AGREE (EDITOR: 2009-08-       EDITOR
attribute shall be a managed    "can".                          07 14:11:39Z)
object within the MAC MIB,
and its value may be set
and retrieved by the MLME."

The MIB syntax determines
whether such variables exist
or not, not statements such
as this.
"The value 0 shall be used to   Replace "shall be used to       AGREE IN PRINCIPLE            EDITOR
indicate..."                    indicate" with "indicates".     (EDITOR: 2009-08-07
                                                                14:11:55Z) - "If
Exactly who is this "shall"                                     dot11RTSThreshold is 0, all
aimed at? The SME? The                                          MPDUs shall be delivered
MAC?                                                            with the use of RTS/CTS."
This is unnecessary.
"shall indicate"                Replace "shall indicate" with    AGREE IN PRINCIPLE            EDITOR
                                "indicates".                     (EDITOR: 2009-08-07
Who is the target of this shall?                                 06:26:05Z) - Rewrite sentence
  Where shall that entity                                        to read: "If the value of
indicate: at the top of a very                                   dot11RTSThreshold is larger
tall building in flashing neon,                                  than the maximum MSDU
on the blinking turn lights of                                   length, all MPDUs shall be
the nearest automobile?                                          delivered without RTS/CTS
                                                                 exchanges."
"No regard shall be given to     Either replace "shall be" with AGREE IN PRINCIPLE (MAC: EDITOR
the busy or idle status of the   "is" and format as a NOTE--, 2009-09-23 04:06:15Z)
medium when transmitting         or define the verb of regarding Accept the first proposed
this data frame"                 (presumably with the aid of     change.
                                 my nurgling iron), define the
Which entity is steadfastly      qualified verb of not regarding
ignoring this signal? (use of    and cite that definition from
passive voice considered         here.
dangerous). The act of
paying regard and not paying
regard has not been specified.

"the asynchronous data frame" Remove "asynchronous" here        AGREE IN PRINCIPLE            EDITOR
                               and in lines 44 and 47.          (EDITOR: 2009-08-25
This term has not been         (These are the only 3            10:41:44Z) - Make the change
defined. It hearkens back to occurances in the standard.)       as indicated, and also remove
the dim and dark past of                                        "asynchronous" from 1.2,
802.11 when it included                                         6.1.1, and 14.3.2.0a.
isochronous data services
(aka time-bounded data
services). That was removed
well before the publication of
the first 802.11 standard.
"To DS field clear"                replace "clear" with "set to 0"     AGREE (MAC: 2009-09-24    EDITOR
                                                                       21:31:44Z)
This field takes only two          Review all uses of "clear" and
values: 0 and 1. "Clear" is        change those related to the
not one of these.                  value of a field in a similar
                                   fashion. (there are about 10
                                   such changes necessary).

                                   Likewise, do the same with all
                                   the word "set" where used by
                                   itself to indicate a field set to
                                   the value 1.

"The STA originating the           Change the first sentence to:       AGREE (MAC: 2009-08-06      EDITOR
message shall receive the          "The STA originating the            23:23:35Z). Note to editor:
message as a                       message receives the                broadcast/multicast is
broadcast/multicast message.       message as a                        replaced by another comment
Therefore, all STAs shall filter   broadcast/multicast message         resolution.
out broadcast/multicast            (prior to any filtering)."
messages that contain their
address as the source
address."

I'm confused. Doesn't the
first sentence say that the
STA shall receive its own
broadcasts with ToDS set,
and the second say it shall
throw them away? Which is
correct?

"The sole exception is that        Prepend: "Under the DCF, "          AGREE (EDITOR: 2009-08-   EDITOR
recognition of a valid data        to cited text.                      07 06:27:34Z)
frame sent by the recipient of
a PS-Poll frame shall also be
accepted
as successful
acknowledgment of the PS-
Poll frame."

There are other exceptions.
For example, places where a
STA sends an Ack or a QoS
Data+CF-Ack.
"Such duplicate frames shall       Replace cited text with: "The       AGREE (MAC: 2009-09-24    EDITOR
be filtered out within the         procedures defined in this          21:31:51Z)
receiver MAC."                     subclause attempt to filter out
                                   these duplicates."
This is only possible with a
cache of infinite size - well,
OK, not infinite, but a really
really big size.
"and different MSDUs shall       Either replace with "...should   AGREE (MAC: 2009-09-24          EDITOR
(with a high probability) have (really really most of the time,   21:32:17Z) - Adopt the
a different sequence number." honest guv)..." or "... MSDUs       second proposed resolution
                                 have (with high probability) a   from the commenter, as the
hmmm. 'Shall (with a high        different..."                    first one uses an English
probability)' is not a normative                                  colloquialism which is not well
verb I recognize.                                                 understood by most members
                                                                  of the 802.11 WG, excepting
                                                                  (with high probability) those
                                                                  Americans that watch too
                                                                  much British TV on PBS.

"The receiver STA shall           Turn into a NOTE--. and "shall AGREE (EDITOR: 2009-08-       EDITOR
perform the ACK procedure         perform" -> "performs".        07 06:27:58Z)
on all successfully received
frames requiring
acknowledgment, even if the
frame is discarded due to
duplicate filtering."

There is nothing in the Ack
procedure that excuses
duplicate frames, so this
statement is unnecessary.
"STAs employing a NAV             Either provide an interface     AGREE (MAC: 2009-11-13        EDITOR
distribution mechanism            that allows CTS-to-self to be   19:41:16Z) - Changing 9.26, p
should choose a mechanism         managed by the SME, or          274.30 as follows:
such as CTS-to-self or            provide precidence rules for    "A STA shall use an RTS/CTS
RTS/CTS that is appropriate       the setting of the              exchange for individually
for the given network             RTSThreshold variable.          addressed frames only when
conditions"                                                       the length of the MPDU is
                                                                  greater than the length
Which entity makes this                                           threshold indicated by the
decision?                                                         dot11RTSThreshold attribute.
If it's the SME, the SME has                                      A STA may also use an
no means of determining the                                       RTS/CTS exchange for
use of CTS-to-self (i.e. no MIB                                   individually addressed frames
variable controls this).                                          when it is necessary to
                                                                  distribute the NAV or when it
If it's the MLME, it means that                                   is necessary to establish
it is writing to the                                              protection (see 9.13)."
RTSThresholdVariable, and
no rules are defined to
determine precidence
between an SME write and a
local MLME write of this
variable.
"The PC shall reside in the       Either define the normative       AGREE IN PRINCIPLE               EDITOR
AP."                              significance of "shall reside",   (EDITOR: 2009-09-22
                                  or change to "resides".           03:09:07Z) -
I reside in Cottenham, a nice                                       Delete cited sentence. Add:
little town of 4,000 people,                                        "A non-AP STA shall not
elevation 50 feet. How nice                                         become a PC." after the
that we've provided a place                                         sentence: "It is an option for
for the PC to stay. Pity we                                         an AP to be able to become
don't let it get out and about                                      the PC.".
though.

What's the normative
significance of "shall reside".
"that all STAs are able to        Either define "proper             AGREE IN PRINCIPLE (MAC: EDITOR
operate properly"                 operation", or remove             2009-07-31 16:13:20Z)
                                  "properly".                       Remove "properly"
Ah how nice. A protocol that
guarantees nothing improper
will ever happen. But what
does this mean?
"are able to receive all frames remove "all".                       AGREE (EDITOR: 2009-09-          EDITOR
sent under PCF control."                                            22 03:04:37Z)

Ah. Mechanism to banish
packet errors. How nice.

", but shall inspect the frame    Remove cited text.                DISAGREE (MAC: 2009-07-      EDITOR
body only if the frame is of                                        31 16:35:29Z) - Removing the
subtype Data, Data+CF-Ack,                                          cited phrase would leave the
Data+CF-Poll, or Data+CF-                                           previous phrase hanging with
Ack+CF-Poll"                                                        uncertain technical effect.

This duplicates the first
sentence of the para, and the
normative effect of "shall
inspect" is not defined.


There is MA-UNIDATA.              It should be MA-UNITDATA          AGREE IN PRINCIPLE               EDITOR
                                                                    (EDITOR: 2009-07-03
                                                                    10:45:09Z)
                                                                    Make change as indicated in
                                                                    this comment twice in this
                                                                    subclause.
There is no need for the italics Remove the italics                 AGREE (EDITOR: 2009-07-          EDITOR
in this para                                                        02 15:06:00Z)

"If a STA desires to change       Replace cited text with:          AGREE IN PRINCIPLE            EDITOR
the PC’s record of                "NOTE--A STA can perform a        (EDITOR: 2009-08-07
CFPollability,                    reassociation in order to         06:28:27Z) -
that STA shall perform a          change the PC’s record of         Replace cited text with:
reassociation."                   CFPollability." & add para        "NOTE—A STA can perform a
                                  breaks before and after.          reassociation in order to
There is no need for this as a                                      change the PC’s record of its
normative statement. It is                                          CF-Pollability." and add para
already true.                                                       breaks before and after.
"The length of a fragment     Indicate how other security        AGREE IN PRINCIPLE              EDITOR
shall never be larger than    encapsulations are treated wrt     (EDITOR: 2009-11-19
dot11FragmentationThreshold fragmentation.                       13:29:50Z) - AGREE IN
unless WEP is invoked for the                                    PRINCIPLE (MAC: 2009-10-
MPDU. If WEP is active for                                       23 16:01:16Z) - Change cited
the MPDU, then the MPDU                                          sentence as instructed in CID
shall be expanded by IV and                                      1338 to extend fragmentation
ICV (see 8.2.1 (Wired                                            rules for non-WEP
equivalent privacy (WEP)));                                      encapsulations.
this may result in a fragment
larger than
dot11FragmentationThreshold.
"

This is incomplete because it
misses out other possible
encapsulations. i.e. Does the
MIC extend the size of an
MPDU containing a fragment
or not.
"If WEP has been applied to      Define how to treat the other   AGREE IN PRINCIPLE (MAC: EDITOR
the fragment, it shall be        security encapsulations,        2009-10-23 16:05:35Z).
decrypted before the fragment    ideally by describing in        Change cited sentence to
is used for defragmentation of   generic terms.                  read: "If security
the MSDU or MMPDU."                                              encapsulation has been
                                                                 applied to the fragment, it
What about the other security                                    shall be de-encapsulated and
encapsulations?                                                  decrypted before the fragment
                                                                 is used for defragmentation of
                                                                 the MSDU or MMPDU."
"There is also an attribute,      Define this attribute          Change the paragraph at      EDITOR
aMaxReceiveLifetime..."           somewhere, or remove any       387.58 as follows:
                                  reference to this term.
No there isn't.                                                  "The destination STA shall
                                                                 maintain a Receive Timer for
                                                                 each MSDU or MMPDU being
                                                                 received, for a minimum of
                                                                 three MSDUs or MMPDUs.
                                                                 The STA may implement
                                                                 additional timers to be able to
                                                                 receive additional concurrent
                                                                 MSDUs or MMPDUs. The
                                                                 receiving STA shall discard all
                                                                 fragments that are part of an
                                                                 MSDU or MMPDU for which a
                                                                 timer is not maintained. The
                                                                 receive MSDU or MMPDU
                                                                 timer starts on the reception
                                                                 of the first fragment of the
                                                                 MSDU or MMPDU. If the
                                                                 receive MSDU timer exceeds
                                                                 an implementation-defined
                                                                 value, then all received
                                                                 fragments of this MSDU or
                                                                 MMPDU are discarded by the
                                                                 destination STA. If additional
                                                                 fragments of an individually
                                                                 addressed MSDU or MMPDU
                                                                 are received after received
                                                                 fragments of an MSDU or
                                                                 MMPDU have been discarded
                                                                 because of the operation of a
Heading is missing a space        fix                            receive timer, those
                                                                 AGREE (EDITOR: 2009-07-         EDITOR
                                                                 02 15:07:36Z)

"When this mechanisms is          mechanisms->mechanism          AGREE (EDITOR: 2009-07-      EDITOR
active" - grammar                                                02 15:08:23Z)

Is this a requirement for the     If the former change "a STA"   AGREE IN PRINCIPLE (GEN: EDITOR
SME, or a requirement for the     to "The SME of a STA..."       2009-07-15
MAC to ignore the ScanType                                       00:42:58Z)Change "shall
parameter of the                                                 default to" to "uses".
SCAN.request?
"A STA shall save the TXOP        Specify unambiguously,         AGREE IN PRINCIPLE (MAC: EDITOR
holder address for the BSS in     under all permitted frame      2009-10-16 15:26:58Z) -
which it is associated, which     exchange sequences, how to     Replace the sentence clause
is the MAC address                determine this.                "...which is the MAC address
from the Address 2 field of the                                  from the Address 2 field of the
frame that initiated a frame                                     frame that initiated a frame
exchange sequence."                                              exchange sequence." with
                                                                 "which is the MAC address
How does it know? For                                            from the Address 2 field of the
example, can it tell the                                         frame that initiated a frame
difference between a CTS-to-                                     exchange sequence except
self that initializes a TXOP                                     when this is a CTS frame, in
and a CTS response?                                              which case the TXOP holder
                                                                 address is the Address 1
                                                                 field.".
"Following AIFSN[AC] ×           Change to "Following        AGREE (MAC: 2009-09-24             EDITOR
aSlotTime –                      AIFSN[AC] × aSlotTime –     21:52:57Z)
aRxTxTurnaroundTime of idle      aSIFSTime -
medium after SIFS"               aRxTxTurnaroundTime of idle
                                 medium after SIFS"
Is this correct? It is
inconsistent with figure 9-18.
This formula includes two
SIFS, one inside the AIFSN
and one explicitly.

Same comment line 56 and
61.
"EIFS – DIFS + AIFSN[AC] × Remove "+ aSIFSTime"                   AGREE (MAC: 2009-09-24        EDITOR
aSlotTime + aSIFSTime –                                           21:56:13Z)
aRxTxTurnaroundTime of idle
medium"

Why is the extra aSIFSTime
here? It's already in the
AIFSN.
"Following AIFSN[AC] ×      Remove "+ aSIFSTime"                  AGREE (MAC: 2009-09-24        EDITOR
aSlotTime + aSIFSTime –                                           21:56:49Z)
aRxTxTurnaroundTime of idle
medium after the last
indicated idle medium as
indicated by the CS
mechanism"

This double-counts SIFS.
"If the backoff procedure is    Change preceding list to          AGREE IN PRINCIPLE            EDITOR
invoked for reason a) above," - lettered, and following list to   (EDITOR: 2009-07-02
 but there is no a) above.      dashed.                           15:40:50Z)
                                                                  Make following list dashed
                                                                  and then indented bullets,
                                                                  which appears to be a style
                                                                  used elsewhere for this
                                                                  purpose.
"All backoff slots occur         Add: ", except as defined in     AGREE (MAC: 2009-09-24        EDITOR
following an AIFS[AC] period     9.9.1.3, which allows the        21:48:52Z)
during which the medium is       medium to be busy during the
determined to be idle for the    initial aSIFSTime of this
duration of the AIFS[AC]         period under certain
period"                          conditions" to the end of this
                                 sentence.
This is inconsistent with
397.42: "(not necessarily idle
medium during the SIFS
duration)"
"After transmitting a frame      Add "immediate" before           AGREE IN PRINCIPLE (MAC: EDITOR
that requires                    "acknowledgement"                2009-09-24 21:57:42Z) add
acknowledgment" - there are                                       "an immediate" before
multiple methods of                                               acknowlegement.
acknowledgement
"can" - wrong verb               can->might                       AGREE (EDITOR: 2009-07-       EDITOR
                                                                  02 15:49:13Z)
"When the WM is determined Replace with a statement that AGREE IN PRINCIPLE (MAC: EDITOR
to be idle for one PIFS period," is true.                2009-10-16 15:35:40Z) -
                                                         Replace "When the WM is
This is not strictly true. By                            determined to be idle for one
analogy with 9.9.1.3, under                              PIFS period," with "When the
certain circumstances the                                WM is determined to be idle
medium may be busy during                                at the TxPifs slot boundary as
the initial SIFS, and the HC                             defined in 9.2.10," The editor
is blind to the state of the                             is instructed to make a similar
medium for the final                                     change to page 403 line 02.
RxTxTurnaround time of this
period.

Same comment p403.02


"PIFS after the end of the       Clarify.                        AGREE (MAC: 2009-10-16          EDITOR
HC’s last transmission only if                                   16:01:25Z) - Replace bullet a)
PHY-CCA.indication primitive                                     with: "If the transmitting STA
is clear."                                                       is the HC, it may initiate
                                                                 recovery by transmitting at the
The timing of when CCA                                           TxPifs slot boundary after the
needs to be clear is unclear.                                    end of
In particular, the HC is blind                                   the HC’s last transmission
to this during the last                                          only if the PHY-
RxTxTurnaround time of the                                       CCA.indication primitive is
PIFS.                                                            clear during the CCAdel
                                                                 period preceding the TxPifs
                                                                 slot boundary as shown in
                                                                 Figure 9-12."

These procedures do not say Relate to the counters in            AGREE (MAC: 2009-10-23          EDITOR
what happens if a fragment of 9.9.1.6.                           15:45:32Z) - Rewrite sentence
an MPDU is retried during                                        on P403L38 to read: "When
both EDCA and HCCA txops.                                        there is a transmission failure
                                                                 within a polled TXOP, the long
Do the same retry counters                                       or short retry counter (as
increment?                                                       described in 9.9.1.6)
                                                                 corresponding to the AC of
                                                                 the failed MSDU or MMPDU
                                                                 shall be incremented."

point b) doesn't allow for an    Add exception in the case that AGREE (MAC: 2009-09-24            EDITOR
MSDU being retired due to        there is no MPDU to transmit. 22:03:39Z) - Replace point b
excessive retries or timeout.                                   with: "If the transmitting STA
                                                                is a non-AP QoS STA, and
                                                                there is an MPDU for
                                                                transmission, it shall initiate
                                                                recovery by transmitting at a
                                                                PIFS after the end of the last
                                                                transmission, if the polled
                                                                TXOP limit is greater than 0
                                                                and at least one frame
                                                                (re)transmissions can be
                                                                completed within the
                                                                remaining duration of a
                                                                nonzero polled TXOP limit."
"then the HC shall assume        Rewrite relating to obsevable     AGREE (MAC: 2009-09-24          EDITOR
that the transmitted QoS         behaviour, or replace "shall      22:06:57Z) - Accept second
(+)CF-Poll frame was             assume" with "assumes".           option in proposed change.
successfully received by the
polled non-AP STA."

The normative effect of
"assume" is unclear.
This is an over-long para.       Split it into smaller paras, if   AGREE IN PRINCIPLE                EDITOR
                                 possible.                         (EDITOR: 2009-07-03
                                                                   10:21:50Z)
                                                                   Restructure as follows:
                                                                   1. Reword first sentence as:
                                                                   "Within a polled TXOP, the
                                                                   unused portion of TXOPs
                                                                   shall be returned back to the
                                                                   HC as follows:"
                                                                   2. Format "The recipient of the
                                                                   final frame, with the Ack
                                                                   Policy ... QoS Control field
                                                                   set to 0." as list item a).
                                                                   3. Format "If a PHY-
                                                                   CCA.indication(busy) primitive
                                                                   occurs ... HC may be
                                                                   incorrectly received." as
                                                                   nested item 1).
                                                                   4. Format "Note that while
                                                                   PHY-CCA.indication(busy)
                                                                   primitive is used in this
                                                                   instance to determine the
                                                                   control of the channel, it is not
                                                                   used for determining the
                                                                   success or failure of the
                                                                   transmission." as a footnote to
                                                                   item 1)
                                                                   5. Format "If the beginning of
                                                                   the reception of an expected
                                                                   ACK response frame to the
                                                                   final frame does not occur, ...
                                                                   TXOP for sending such a
"Within a polled TXOP, the       Clarify or turn into an           frame." as nested item 2).
                                                                   AGREE IN PRINCIPLE (MAC: EDITOR
unused portion of TXOPs          informative statement.            2009-09-24 22:08:06Z)
shall be returned back to the                                      rewrite as ". . . any unused
HC."                                                               portion of the TXOP shall not
                                                                   be used by the STA, and may
Passive voice considered                                           be reallocated by the HC."
dangerous. What is the
normative effect of "shall be
returned". Who is the subject
responsible for returning?

"slot following SIFS after the   insert "a"                        AGREE IN PRINCIPLE              EDITOR
end" - missing article                                             (EDITOR: 2009-07-03
                                                                   10:28:02Z)
                                                                   Replace "following SIFS" with
                                                                   "following a SIFS" globally.
"prevent its transmitting" -      its->it                         AGREE IN PRINCIPLE (MAC: EDITOR
genative is inappropriate                                         2009-09-24 22:08:56Z) -
                                                                  Replace "prevent its
                                                                  transmitting" with "prevent it
                                                                  from transmitting"

"it may reset the NAVs of all Add the word "QoS" before           AGREE (MAC: 2009-09-24          EDITOR
STAs in the BSS by sending a "STAs".                              22:11:38Z)
QoS CF-Poll frame with the
RA matching its own MAC
address and with the
Duration/ID field set to 0."

As I understand it, this will
only affect QoS STA. So the
statement is at least
misleading.

It also begs the question
whether it is fair to reset the
NAVs of only the QoS STAs.

"A non-AP STA that receives       Resolve the inconsistency.      AGREE (MAC: 2009-10-23          EDITOR
a CF-End frame containing                                         15:24:01Z). Delete the cited
the BSSID of the BSS, in                                          sentence, and add a note to
which the non-AP STA is                                           clause 9.9.2.2a following the
associated, shall reset the                                       paragraph where the first
NAV value to 0."                                                  cited sentence was present
                                                                  that reads: "NOTE--A STA
appears to be inconsistent                                        resets its NAV when it
with (382.38 9.3.2.2): "The                                       receives a CF-End or CF-
PC shall transmit a CF-End or                                     End+ACK frame according to
CF-End+ACK frame at the                                           the procedures described in
end of each CFP. A STA that                                       9.3.2.2."
receives either of
these frames, from any BSS,
shall reset its NAV."
"If a CF-Poll is piggybacked      Relate frame TID carrying the   AGREE (MAC: 2009-10-23        EDITOR
with a QoS data frame, then       TSID of a TS for which a        15:37:26Z) - "If a CF-Poll is
the                               minimum phy rate was            piggybacked with a QoS data
MSDU may be transmitted at        specified with the RA of that   frame, then the MSDU may be
the rate that is below the        frame.                          transmitted at a rate that is
negotiated minimum PHY                                            below the negotiated
rate."                                                            minimum PHY rate in the
                                                                  TSPEC related to that data."
Negotiated how? With
whom?
"and it has to send more          replace with "and it has more   AGREE (EDITOR: 2009-07-         EDITOR
MPDUs." - grammar                 MPDUs to send."                 03 10:37:34Z)

"in the QoS data or QoS Null      replace with "in a QoS data     AGREE (EDITOR: 2009-07-         EDITOR
frame" - grammar                  frame or a QoS Null frame"      03 10:39:11Z)
(Submitted on behalf of           As noted                       AGREE IN PRINCIPLE              EDITOR
Carlos Cordeiro) For                                             (EDITOR: 2009-07-02
completeness, 9.14 (MAC                                          13:14:53Z)
Frame Processing) should be                                      Add "Rules for processing
included at the end of the                                       MAC frames are described in
paragraph+F275                                                   9.14 (MAC frame
                                                                 processing(11k))." to the end
                                                                 of the cited text.
(Submitted on behalf of           Rewrite removing the "shall"   AGREE (MAC: 2009-07-14          EDITOR
Carlos Cordeiro) The                                             15:25:29Z). Change
sentence: "The use of a                                          sentence to read "The use of
smaller IFS implies that point-                                  a smaller IFS implies that
coordinated traffic shall have                                   point-coordinated traffic has
priority access to the medium                                    priority access to the medium
over STAs in overlapping                                         over STAs in overlapping
BSSs operating under the                                         BSSs operating under the
DCF access method." The                                          DCF access method."
use of "shall" here seems
improper. How can this be
tested? What is the normative
behavior here?
(Submitted on behalf of           Add " and (Re)Association      AGREE IN PRINCIPLE (MAC: EDITOR
Carlos Cordeiro) The EDCA         Response" after "… Probe       2009-09-24 22:13:00Z) -
parameter set can also be         Response"                      change end of cited sentence
changed in a (Re)Association                                     to read ". . .Beacon frame,
Response frame                                                   Probe Response frame, and
                                                                 (Re)Association Response
                                                                 frame."

Replace "nonbeacon" by "non As noted                             AGREE IN PRINCIPLE           EDITOR
Beacon"                                                          (EDITOR: 2009-07-02
                                                                 13:31:59Z)
                                                                 Replace by non-Beacon
                                                                 globally (2 occurances).
(Submitted on behalf of          Replace "shall" by "may"        AGREE IN PRINCIPLE (MAC: EDITOR
Carlos Cordeiro) The                                             2009-09-24 22:26:08Z) -
sentence: "… then the STA                                        Remove ",at its convenience"
shall retry the sequence, by                                     from the cited sentence.
transmitting another PS-Poll
frame, at its convenience."
This is not enforcable. The
sentence states "shall" but "at
its convenience". If the
intention is to allow the STA to
decide to retransit when it
sees fit (or not retransmit at
all), "shall" should not be used
here
(Submitted on behalf of          As noted                        AGREE IN PRINCIPLE              EDITOR
Carlos Cordeiro) Replace                                         (EDITOR: 2009-07-02
"nonbasic" by "non basic"                                        13:34:58Z)
                                                                 Replace by non-basic.
(Submitted on behalf of          1) Replace "so that" by "if"   DISAGREE (EDITOR: 2009- EDITOR
Carlos Cordeiro) Propose to      2) Replace "does not cause"    07-02 15:36:08Z)
rewrite this sentence to make    by "causes"                    The change results in "if
the intent clear, which is not                                  transmission of the first
the case now                                                    mpdu.. causes the txop limit to
                                                                be exceeded". The point is
                                                                that we want to prevent this
                                                                occuring, not respond to it.

                                                                The implication of the change
                                                                is to try transmission, and if
                                                                you observe the TXOP limit is
                                                                exceeded, then fragment.
                                                                This is not the desired
                                                                behaviour.


(Submitted on behalf of       Change the enumeration of         AGREE IN PRINCIPLE               EDITOR
Carlos Cordeiro) There are no the bullets from dash to "a)",    (EDITOR: 2009-07-02
"a)", "b)", "c)" or "d)". The "b)", "c)" and "d)"               15:42:57Z)
enumeration needs to change                                     See resolution to CID 1651,
                                                                which addresses this issue.
(Submitted on behalf of          Delete comma                   AGREE (EDITOR: 2009-07-          EDITOR
Carlos Cordeiro) Although I                                     02 15:48:25Z)
am not a native english
speaker (but a native ESL), I
am pretty sure that the
comma in this sentence is
grammatically wrong. In this
case, one cannot separate the
verb with a comma
(Submitted on behalf of          Insert ", including a CF-End   AGREE IN PRINCIPLE (MAC: EDITOR
Carlos Cordeiro) It would be     frame (see 9.9.2.2a (NAV       2009-09-24 22:18:51Z)
desirable to explicitly state    operation during a TXOP)),"    Change last phrase in cited
that the HC can transmit a CF-   following "… other             sentence to read: ". . .and the
End (or a QoS CF-Poll with       transmissions"                 HC may initiate other
the duration set to 0) to end                                   transmissions, send a CF-End
the CFP                                                         frame (see 9.9.2.2.a), or allow
                                                                the channel to go into the CP."

(Submitted on behalf of          As noted                       AGREE IN PRINCIPLE              EDITOR
Carlos Cordeiro) Replace                                        (EDITOR: 2009-07-03
"transmitting" by                                               10:35:46Z)
"transmission"                                                  Replace "its transmitting" with
                                                                "it from transmitting" in cited
                                                                location.
(Submitted on behalf of         Move note 34 to page 407      DISAGREE (EDITOR: 2009-            EDITOR
Carlos Cordeiro) Note 34                                      07-03 10:39:44Z)
should appear on this page,                                   Moving Note 34 to the
but is on the next one                                        preceding page would force
                                                              the text containing the
                                                              reference onto the next page,
                                                              so the note would then
                                                              preceed the reference.

                                                              The editor has no control over
                                                              the precise placement of
                                                              these notes. However, in this
                                                              case, the Frame tools are
                                                              doing precisely the right thing.

Is "lifetime" of a BSS defined? Clarify                       The statement indicates that       EDITOR
Is it the time in between power                               an AP does not change the
up events? I believe this is the                              value of this bit during the
intent and wonder if this                                     lifetime of its BSS. This bit is
should be called out to                                       part of the EDCA Parameter
distinguish it from, for                                      Set element, which is a
example, when the AP stops                                    parameter of the MLME-
functioning altogether                                        START.request primitive.
                                                              The "lifetime of its BSS" may
                                                              be interpreted as the time
                                                              between the start of the
                                                              MLME-START.request
                                                              primitive and a subsequent
                                                              MLME-STOP.request or
                                                              MLME-RESET.request.

(Submitted on behalf of         Replace "a local matter" by   AGREE (EDITOR: 2009-07-            EDITOR
Carlos Cordeiro) "local         "implementation dependent"    27 11:13:41Z)
matter" is a weird term.
(Submitted on behalf of           Suggest to include the           AGREE IN PRINCIPLE (MAC: EDITOR
Carlos Cordeiro) A STA can        conditional statement that the   2009-11-13 19:59:37Z) -
only continue transmitting        total number of frames shall     Change the cited paragraph
MPDUs after transmission of       not exceed the reordering        to read: "The originator may
the BlockAckReq frame             buffer                           continue to transmit MPDUs
provided the total number of                                       (subject to the negotiated
outstanding frames do not                                          buffer size constraint) to the
exceed the reordeing buffer at                                     recipient after transmitting the
the receiver (Buffer Size field                                    BlockAckReq frame, but
in the ADDBA Response                                              before receiving the BlockAck
frame)                                                             frame (applicable only to
                                                                   delayed Block Ack). The
                                                                   bitmap in the BlockAck frame
                                                                   shall include the status of
                                                                   frames received between the
                                                                   start sequence number and
                                                                   the transmission of the
                                                                   BlockAckReq frame. A
                                                                   recipient sending a delayed
                                                                   BlockAck frame may update
                                                                   the bitmap with information on
                                                                   QoS data frames received
                                                                   between the receipt of the
                                                                   BlockAckReq frame and the
                                                                   transmission of the BlockAck
                                                                   frame."


MDIE should be refered to as      Delete the word "information"    AGREE IN PRINCIPLE           EDITOR
the Mobility Domain element.      as appropriate throughout this   (EDITOR: 2009-07-28
                                  clause for consistency with      11:12:25Z) - Replace all
                                  clause 7.3.2.                    “information element” with
                                                                   “element” – except in the
                                                                   heading of 7.3.2. and 7.3.1
                                                                   Remove redundant
                                                                   “information” from name of
                                                                   elements in table 7-26 and
                                                                   make matching changes to
                                                                   references throughout the
                                                                   standard, except in
                                                                   dot11RMAntennaInformationE
                                                                   nabled, replace "Antenna
                                                                   Information" with "Antenna
                                                                   information", and in
                                                                   dot11RMMeasurementPilotTra
                                                                   nsmissionInformationEnabled
                                                                   description, lower case the
                                                                   "information".
                                                                   Globally replace any
                                                                   abbreviations that expand to
                                                                   <something> information
                                                                   element with new names (e.g.
                                                                   MDIE->MDE), excepting TIE,
                                                                   which is already correct for
                                                                   the new terminology.
The text states "A non-AP         Specify that the TID value is     AGREE IN PRINCIPLE (MAC: EDITOR
STA may support admission         changed to correspond to the      2009-11-19 16:19:13Z) -
control procedures in             next lower AC that doesn't        Instruct the editor to apply the
9.9.3.1.2 (Procedure at non-      require admission control and     changes in 11-09/1063r1.
AP STAs) to send frames in        that the frame is enqueued in
the AC where admission            that lower AC.
control is mandated; but, if it
does not support that             This change means that the
procedure, it shall use EDCA      priority carried in the
parameters of a lower priority    QoS_control field properly
AC, as indicated in Table 9-1     reflects the over-the-air
(UP-to-AC mappings), that         priority on the link. The EDCA
does not require admission        parameters used by an
control." This text is            EDCAF are not observable to
ambiguous since it does not       a receiver; neither is the fact
describe whether the TID          that the frame is downgraded
subfield in the QoS_control       to a lower AC as there is no
field in the MAC header is        indication in the MAC header
changed.                          that downgrading has
                                  occurred UNLESS the TID is
                                  also changed. Any HC
                                  attempting to manage the WM
                                  needs this information (i.e.,
                                  WM usage by AC); note that
                                  the HC needs to know WM
                                  usage by AC for BSSs other
                                  than the BSS of the AP
                                  containing the HC.

                                  This change is required for
                                  proper operation of the
                                  standard.
The text states "If a STA        Specify that the TID value is      AGREE IN PRINCIPLE (MAC: EDITOR
desires to send data without     changed to correspond to the       2009-11-19 16:19:13Z) -
admission control using an       next lower AC that doesn't         Instruct the editor to apply the
AC that mandates admission       require admission control and      changes in 11-09/1063r1.
control, the STA shall use       that the frame is enqueued in
EDCA parameters that             that lower AC.
correspond to a lower priority
and do not require admission     This change means that the
control." This text is           priority carried in the
ambiguous since it does not      QoS_control field properly
describe whether the TID         reflects the over-the-air
subfield in the QoS_control      priority on the link. The EDCA
field in the MAC header is       parameters used by and
changed.                         EDCAF are not observable to
                                 a receiver; neither is the fact
                                 that the frame is downgraded
                                 to a lower AC as there is no
                                 indication in the MAC header
                                 that downgrading has
                                 occurred UNLESS the TID is
                                 also changed. Any HC
                                 attempting to manage the WM
                                 needs this information (i.e.,
                                 WM usage by AC); note that
                                 the HC needs to know WM
                                 usage by AC for BSSs other
                                 than the BSS of the AP
                                 containing the HC.

                                 This change is required for
                                 proper operation of the
                                 standard.
The text states "The             Change the text to "The            DISAGREE (MAC: 2009-09-         EDITOR
admitted_time and used_time admitted_time and used_time             23 03:10:46Z) - The proposed
shall be set to 0 at the time of shall be set to 0 at the time of   change has potentially large
(re)association."                association."                      ripple effects because it
Reassociation to the same AP                                        eliminates the ability to reset
should not cause these times                                        the state of a QoS STA
to be set to 0--for example, a
non-AP STA may wish to
reassociate in order to change
the QoS Info field in the EDCA
parameter element included in
a reassociation request frame.
The text states "However, a       Add text indicating that the    AGREE IN PRINCIPLE (MAC: EDITOR
non-AP STA may choose to          priority is not changed (else   2009-09-23 03:16:10Z) The
temporarily replace the EDCA      the EDCAF would change and      text is not ambiguous
parameters for that EDCAF         frame re-ordering could         because it does not need to
with those specified for an AC    occur).                         specify that the TID field is
of lower priority, if no                                          unchanged. However, this
admission control is required                                     could be clarified by adding
for those ACs." This text is                                      the following note: "NOTE --
ambiguous since it does not                                       when a frame is transmitted
describe whether the TID                                          using temporary EDCA
subfield in the QoS_control                                       parameters, the TID field of
field in the MAC header is                                        that frame is not modified"
changed.
What is the definition of an      Provide a definition.           AGREE IN PRINCIPLE            EDITOR
"inactive TS". Is this the same                                   (EDITOR: 2009-08-07
as unadmitted traffic?                                            08:36:54Z) -
                                                                  Replace the sentence
                                                                  reading: "A STA shall not
                                                                  transmit any QoS data frames
                                                                  using an inactive TS." with
                                                                  one that reads:
                                                                  "A STA shall not transmit any
                                                                  QoS data frames in which the
                                                                  TID subfield of the QoS
                                                                  Control field matches an
                                                                  inactive TS."

                                                                  In reply to the commenter,
                                                                  the change clarifies that no
                                                                  traffic whatsever may be
                                                                  transmitted using an inactive
                                                                  TS.
The text states "Following a      Clarify the text.               AGREE (EDITOR: 2009-11-       EDITOR
successful TS setup initiated                                     19 13:30:00Z) - AGREE
by the non-AP STA, the TS                                         (MAC: 2009-08-07 15:14:10Z)
becomes active, and either                                        change "transmit QoS data
the non-AP                                                        frames using this TSID" to
STA or the HC may transmit                                        "transmit QoS data frames
QoS data frames using this                                        whose TID contains this
TSID". How does a STA                                             TSID."
transmit a frame using a
TSID? The TSID is a TSPEC
identifier and is not part of any
frame of type=data that is
transmitted when the access
mechanism is EDCA.
There is no text stating when   Add rules which define the   UNRESOLVABLE (MAC:         EDITOR
a result code of                interaction of TSID, user    2009-11-19 16:58:10Z) -
INVALID_PARAMETERS              priority, direction and      Comment withdrawn on 11/18
should be used.                 successful/rejected          AM2 session because no
                                replacement.                 action is required.




The text states "After the     Change the text.              DISAGREE (MAC: 2009-09-       EDITOR
setup of a TSPEC, MSDUs                                      24 19:27:08Z) - The priority
are classified above the MAC                                 parameter takes a TSID,
and are sent to the MAC                                      which is a number in the
through the MAC_SAP using                                    range 8-15 which identifies a
the service primitive MA-                                    TS. Over the air this is for
UNITDATA.request with the                                    EDCA converted to a UP in
priority parameter encoded to                                the range 0-7. The union of
the TSID." In the MA-                                        UPs and TSIDs are TIDs, but
UNITDATA.request primitive,                                  this is not what is passed in
the priority should be encoded                               MA-UNITDATA in the case of
to the TID (not TSID)--see                                   MSDUs belonging to a TS.
6.1.1.2.
The text states "The MAC       Change the text.              AGREE IN PRINCIPLE             EDITOR
delivers the MSDUs based on                                  (EDITOR: 2009-11-19
a schedule using QoS data                                    13:30:04Z) - AGREE IN
frames. In the case of a non-                                PRINCIPLE (MAC: 2009-08-
AP STA, the MSDUs are                                        07 15:27:51Z) - Delete the two
transmitted using QoS data                                   cited sentences because they
frames, when the non-AP                                      do not have a normative
STA is polled by the HC."                                    requirement.
Polling is only used in HCCA
and HEMM access
mechanisms, but not EDCA.
The text should be corrected.

The abbreviation TSID is        Change the text.             AGREE (EDITOR: 2009-11-     EDITOR
incorrect--the priority is                                   19 13:30:09Z) - AGREE
carried in the TID. This same                                (MAC: 2009-08-07 00:26:57Z)
mistake is propagated                                        Change "TSID" to TID"
throughout the paragraph.
The text states "When an       Per comment.             AGREE IN PRINCIPLE (MAC: EDITOR
MSDU arrives from the                                   2009-09-23 03:39:51Z) -
MAC_SAP with a TSID for                                 Delete the final paragraph in
which there is no associated                            clause 11.4.6 on page 612.
TSPEC, then the MSDUs
shall be sent using EDCA                                Add the statement "See
using the access category                               6.1.1.2 for the treatment of an
AC_BE."                                                 MSDU with a TSID for which
                                                        there is no associated
First, the MA-                                          TSPEC." to the end of the
UNITDATA.request primitive                              second paragraph in in 11.4.6.
doesn't use TSID, it uses
priority.

Secondly, this text is
ambiguous because it doesn't
state what value should be
placed in the TID subfield in
the QoS_control field in the
MAC header. The text should
state that the TID should be
set to 0 (best effort) in this
case.
The text states "When the      Delete this paragraph.   AGREE IN PRINCIPLE                EDITOR
Processing subfield of the                              (EDITOR: 2009-11-19
TCLAS Processing                                        13:30:15Z) - AGREE IN
information element is set to                           PRINCIPLE (MAC: 2009-08-
1, then the receiver cannot                             07 15:50:21Z) - Replace the
recover the original UP unless                          cited paragraph with the
it does a reverse mapping                               statement: "When an MSDU
based on the TCLAS                                      is classified using a TCLAS
parameters." Even if the                                information element, the
receiver attempts to perform                            original UP cannot be
the reverse mapping, how will                           recovered by the receiver."
it know the original UP? A
non-AP STA does not know
the CoS to UP mapping used
by the LAN.
Reassociation to the same AP Change the text.                    DISAGREE (EDITOR: 2009- EDITOR
should not cause the TSs to                                      11-19 13:30:20Z) -
be deleted--for example, a                                       DISAGREE (MAC: 2009-08-
non-AP STA may wish to                                           07 15:59:47Z) - Reassociation
reassociate in order to change                                   may change the capabilities of
the QoS Info field in the EDCA                                   a non-AP STA, which may
parameter element included in                                    have change the validity of
a reassociation request frame.                                   existing TSs. The proposed
                                                                 resolution does not provide
Also, association to the same                                    enough detail to implement
AP should cause the TSs to                                       this change.
be deleted--that way the non-
AP STA can always get back
to a known state (this is
critical because U-APSD
operation sets non-AP
queuing state on AP and if
this gets out-of-sync for any
reason, there should be a way
to reset it).

This change is required for
proper operation of the
standard.


"A special BSSID". Define        Change to "A BSSID value (all   AGREE (GEN: 2009-09-24      EDITOR
"special"? Somehow the IEEE      binary 1s) used to represent    23:14:35Z)
spec has feelings?               all BSSIDs"
"A special SSID". Define         Change to "A SSID value         AGREE IN PRINCIPLE            EDITOR
"special"? Somehow the IEEE      (null) used to represent all    (EDITOR: 2009-08-06
spec has feelings?               SSIDs"                          11:17:50Z)
                                                                 Make change as proposed,
                                                                 and similar change for
                                                                 "wildcard BSSID".
11k text states for Power  Fix                                   DISAGREE (EDITOR: 2009- EDITOR
Constraint "and can be                                           07-01 15:50:10Z)
present                                                          Since .11k was rolled in,
if                                                               changes have been made to
dot11RadioMeasurementEnab                                        unify the "presence" language
led is true." whereas 11mb                                       according to document 11-09-
states "and is optionally                                        0433r1.
present present if                                               The change cited is part of a
dot11RadioMeasurementEnab                                        process to improve the
led is true".                                                    consistency of language used
                                                                 in Clause 7.
DS Parameter set is              Include regulatory domain       DISAGREE                      EDITOR
insufficient to identify the     whenever DS Parameter set       (ARCHITECTURE: 2009-11-
channel uniquely. Regulatory     is included.                    17 22:47:26Z) making such a
domain must be included. As                                      change would change
supported reg class is only                                      behaviour and break legacy
included when extended                                           devices.
channel switch is true then it
seems there is a whole if DS
Parameters are included but
ECSA is false.
"The Measurement Pilot              Delete this sentence.           AGREE (EDITOR: 2009-07-      EDITOR
frame is a compact Action                                           01 12:59:29Z)
frame transmitted periodically
by an AP at a small interval
relative to a Beacon Interval."
This sentence is redundant.
The next sentence conveys
this information in a better
way.
"ongoing traffic stream link". Is   Replace "ongoing traffic        AGREE IN PRINCIPLE             EDITOR
there one such term?                stream link" with a more        (SECURITY: 2009-07-14
Ongoing traffic stream or           appropriate term.               22:04:34Z)
ongoing traffic stream over                                         Replace the text with "ongoing
the link is appropriate.                                            traffic stream".




Use of Radio Measurement            Use either Radio                AGREE IN PRINCIPLE           EDITOR
and Radio Resource                  Measurement or Radio            (EDITOR: 2009-07-01
Measurement. Are they the           Resource Measurement in all     13:00:39Z)
same or different? Cl. 5.2.7        places. It appears that Radio
uses Radio Resource                 Measurement (206) is used in    Change all "radio resource
Measurement while it is             more instances than Radio       measurement" to "radio
referred to as Radio                Resource Measurement (19).      measurement".
Measurement here.
                                                                    Change all "RRM" to "RM".
                                                                    (about 740 instances)

                                                                    Also remove any embedded
                                                                    hyphens in these names
"The Power Constraint         Remove the extra 'present' in         AGREE (EDITOR: 2009-07-      EDITOR
element is present if         the Notes column.                     01 14:58:01Z)
dot11SpectrumManagementR
equired is true and is
optionally present present if
dot11RadioMeasurementEnab
led is true."
The need for the prefix "MIB       Remove the prefix "the MIB           AGREE (ARCHITECTURE:              EDITOR
attribute". Why is this used in    attribute"                           2009-11-16 15:28:29Z)
some cases and not in
others? For instance:

"A STA sets the Radio
Measurement subfield in the
Capability Information field to
1 when the MIB attribute
dot11RadioMeasurementEnab
led is true, and sets it to 0
otherwise."

If the prefix is needed here,
why is it not needed in the
Notes column corresponding
to Antenna Information in
Table 7-15?
Consistency in describing          Limit description of reserved        AGREE IN PRINCIPLE            EDITOR
Reserved bits. There are           fields/ bits to "is/are reserved".   (EDITOR: 2009-07-27
three variations:                                                       08:07:06Z)
(i) All other bits are reserved.                                        Review Clause 7 for use of
(ii) All other bits are reserved                                        the term "reserved" and
and are set to 0.                                                       remove any spurious
(iii) All other bits are reserved;                                      specification of behaviour or
and are set to 0 upon                                                   value for a reserved field in
transmission and ignored                                                Clause 7, excepting 7.1.1 and
upon reception.                                                         any Notes.

In most cases, (i) is what                                              Note the contradiction at the
should be used. Cl. 7.1.1                                               end of 7.1.3.5, which defines
clearly describes what                                                  a reserved field as having an
reserved means.                                                         unspecified value, when 7.1.1
                                                                        clearly indicates that a
                                                                        reserved field is set to 0.
                                                                        This contradiction is resolved
                                                                        by removing the last phrase of
                                                                        7.1.3.5.

                                                                        In the 5th para of 7.3.2.19,
                                                                        replace: "The Link Margin
                                                                        field is(11k) set to 0 and
                                                                        is(#29) ignored" with "The
                                                                        Link Margin field is reserved"

                                                                        In the last phrase of 7.3.2.50,
                                                                        replace: "Status Code field is
                                                                        set to 0 and ignored upon
                                                                        receipt" with "Status Code
                                                                        field is reserved"
The Note in Table 7-28 is mis-     Moce the note to the             AGREE (ARCHITECTURE:         EDITOR
placed. This applies to the        "Measurement Request             2009-07-16 06:41:41Z)
"Measurement Request               Meaning" cell corresponding
Meaning" cell for the last row     to the last row in Table 7-28.
in the table.




extra characters after "STA                                         AGREE (EDITOR: 2009-07-      EDITOR
statistics request"                                                 02 06:13:38Z)

What is the requirement on         Specify that the fields are      AGREE (ARCHITECTURE:         EDITOR
Average Error Threshold,           reserved if the corresponding    2009-07-16 06:42:01Z)
Consecutive Error Threshold        bits are set to 0.
and Delay Threshold, if the
corresponding bits in the
trigger conditions bit-field is
set to 0?
Two issues with the                Make the description             DISAGREE                        EDITOR
description of the                 consistent with other            (ARCHITECTURE: 2009-11-
Measurement Duration field in      measurement request              18 20:49:49Z) The
the STA statistics request         elements. Add the special        commentor is encouraged to
element:                           case of what it means to         provide more details of any
                                   specify a measurement            proposed improvement, but
(a) While all other request        duration of 0.                   without the details of what is
elements describe                                                   proposed, the group cannot
Measurement Duration as                                             evaluate the technical merit at
"The Measurement Duration                                           this time.
field is set to the preferred or
mandatory duration of the
requested measurement,
expressed in units of TUs.
See 11.10.3 (Measurement
Duration).", description in STA
statistics request is "The
Measurement Duration field is
set to the duration of the
requested measurement in
TUs." Why is the choice of
preferred/mandatory duration
and the reference to clause
11.10.3 missing?
(b) STA statistics request has
a special case for
Measurement Duration --
when the specified
Measurement Duration is 0,
the reporting STA (assuming
it supports STA statistics
reporting), is expected to
report a snapshot of the
There appears to be nothing         Recommend having the                DISAGREE                        EDITOR
optional about the optional         measuring STA report a frame        (ARCHITECTURE: 2009-11-
sub-elements in the Frame           count in the Frame Report at        19 17:22:59Z) - the requested
Report Information Element. A       all times. The Frame Report         change is not compatible with
Frame Request IE without a          sub-element may report              legacy devices. On the
Frame Request Type is               additional values based on          optional sub-elements item:
invalid (it is a mandatory          optional sub-elements               Disagree. This is for general
field). This means that the         specified in the Frame              structure and future use of the
corresponding Frame Report          Request. In addition, specify       Frame Report when a
is required to include a Frame      (in Cl. 11) that the reporting      subelement may not be
Count Report (at all times)         STA shall respond with              required. On the
which is described as an            'Incapable' if the requesting       wastefulness of transmitting
optional sub-element.               STA were to request reporting       values that cannot be
                                    of a measurement (using the         reported: Disagree, because it
In addition, a reporting STA        optional sub-element in the         is a bad idea to make the
may not have support for all        request) that the reporting         frame format overly complex
the information described in        STA does not support.               to support this suggested
the Frame Count Report sub-                                             change.
element (for instance, a STA
may not have the ability to
measure RCPI, RSNI, etc).
Although there are specific
RCPI/RSNI values defined to
indicate that it is 'unknown', it
is wasteful to send the value
in a frame report when the
STA has already advertised
that it cannot report these
values via the RRM Enabled
Capabilities element.


Inconsistency between the           Fix Figure 7-68l to use a 1-        AGREE IN PRINCIPLE               EDITOR
length of                           octet sub-field for                 (ARCHITECTURE: 2009-07-
dot11BSSAverageAccessDela           dot11STAStatisticsStationCou        16 06:42:24Z) The MIB
y group statistics in Table 7-      nt.                                 defines this to have values up
31f (specifies length as 7                                              to 64K, so it needs to be 2
octets) and in Figure 7-68l                                             octets. Figure 7-68l is correct.
(shows 8 octets)                                                         Change Table 7-31f to show
                                                                        the length as 8 octets.

Should the 'Bin 0 Range'            Clarify if the report should just   DISAGREE                        EDITOR
returned in the report be the       echo the value in the request.      (ARCHITECTURE: 2009-11-
same as the one in the              Or could the reporting STA          18 20:50:14Z) - The
request? There is no                adjust the Bin 0 value in such      commentor is encouraged to
requirement on what is              a way that the histogram            provide more details of any
allowed and what is not as far      covers a range where there is       proposed improvement, but
as Bin 0 Range goes both            something to report.                without the details of what is
here in Clause 7 and in                                                 proposed, the group cannot
Clause 11.10.8.8.                   In cases where the report is        evaluate the technical merit at
                                    generated autonomously the          this time.
                                    reporting STA can determine
                                    a Bin 0 Range that makes the
                                    most sense and report that
                                    accordingly.
Bin 0 Range is a perfect          Move Bin 0 Range to Optional      DISAGREE                        EDITOR
candidate for the Optional        Subelements in the request        (ARCHITECTURE: 2009-11-
Subelements. This provides        and the corresponding             19 17:22:59Z) - on first
the flexibility of reporting      elements/fields to the Optional   appearance the requested
stream statistics for TID         Subelements in the report.        change is not compatible with
versus reporting stream                                             legacy devices. The
statistics and the distribution                                     commentor is solicited to
of corresponding delays for a                                       provide a submission that
TID.                                                                explains the proposal in a way
                                                                    that provides backwards
                                                                    compatibility.
"Element ID is 48 decimal (30     Delete this description. Or       AGREE IN PRINCIPLE              EDITOR
hex)". All elements described     Make the description of           (EDITOR: 2009-07-02
in Clause 7.3.2 do not include    Element ID consistent across      06:17:04Z)
a description of the element      all the elements.                 Replace any statement in
ID since the element ID is                                          7.3.2 of the form "Element ID
defined in Table 7-26 which is                                      is <some value>" with
at the start of Clause 7.3.2.                                       "Element ID is set to the value
Why is it explicitly described                                      for <name of element>,
(re-described) for the RSN IE?                                      specified in Table 7-26"

Similar issue with 7.3.2.27                                         Note - this affects the
(Extended Capabilities IE)                                          Country, Hopping Pattern
                                                                    Table, Request, RSN and
Some elements do describe                                           Extended Capabilities
the Element ID field as                                             elements.
follows: "The Element ID field
is equal to the <xxx> value in
Table 7-26 (Element IDs)."


Task Group v has                                                    DISAGREE                     EDITOR
clarified/corrected several                                         (ARCHITECTURE: 2009-11-
issues in the TCLAS element                                         16 15:32:27Z) -- No proposed
description. These changes                                          resolution, Comment not
were done in TGv only                                               complete.
because they were identified
after TGma closed. It would
be appropriate for the work to
be included in TGmb for two
reasons: (a) get wider review
of the changes and (b)

Where is the description for      Add description of the EDCA       AGREE IN PRINCIPLE              EDITOR
the "EDCA Parameter Set           Parameter Set Update Count        (ARCHITECTURE: 2009-11-
Update Count" subfield in the     or refer to where it is           18 20:55:03Z) Insert at line 64
QoS Info field (Clause            described (Clause: 7.3.2.29)      "EDCA Parameter Set Update
7.3.1.17)?                                                          Count is described in 9.1.3.1."

length of RRM Enabled                                               AGREE (ARCHITECTURE:         EDITOR
Capabilities should be 5 (See                                       2009-07-16 06:42:53Z)
7.3.2.45 RRM Enabled
Capabilities Element)
Inconsistency in how                                           AGREE IN PRINCIPLE                EDITOR
"element" is used in the title of                              (EDITOR: 2009-07-01
sub-clauses -- it is Element in                                16:33:25Z)
some and element in others.
                                                               Change upper cased Element
                                                               to lower-case, except where
                                                               an initial E is required at the
                                                               start of a sentence, or where
                                                               "Element" forms part of a field
                                                               name.

                                                               Change Element->element in
                                                               heading of 7.3.2.46, 7.3.2.45


"Station Bridge" functionality      Add support for "Station   DISAGREE (GEN: 2009-11-           EDITOR
is not supported in 802.11.         Bridge" in 802.11          13 16:54:58Z) - Disagree:
                                                               New features and functions
In a device that includes a                                    such as this should be
802.11 non-AP STA interface                                    presented and vetted in the
and a 802.2.3 wired LAN                                        802.11 WNG-SC. A
interface, internally bridged                                  submission would be needed
together, a broadcast                                          as well as the proposal
message for instance an ARP
Request, that ingresses via
the 802.3 interface where the
Target MAC Address does not
resolve to the device, gets
sent out via the 802.11
interface to the BSS that the
device is associated with. In
such cases, the AP receiving
ARP request (assuming that
the Target MAC Address does
not resolve to the AP)
broadcasts the ARP message
to all the STAs associated
with it (including the one that
sent it in the first place).
Without proprietary non-
standard counter measures,
this causes the ARP
broadcast to egress off of the
802.3 interface through which
the ARP originated. This
violates the expected
behavior --
broadcast/multicast
As pointed out by other            I suggest, minimally,           Insert: "In each Annex G             EDITOR
comments (and my own) the          incorporating the data tables   Table which has "Binary Val"
CRC value for the Annex G.2,       of 802.11n, Annex G.1 into      columns, the bit positions of
Table G.1, is incorrect. The       the .11mb draft.                the binary values are
last four bytes should be:                                         specified in the header of the
0x67, 0x33, 0x21, 0xB6,                                            Table. " at the end of G.1.
instead of 0xDA, 0x57, 0x99,
0xED. This has a "rippling                                         Replace table G.1 with that in
effect" that cause the data                                        P802.11n D11.0.
tables for the last symbol, i.e.
"Last 144 DATA bits" to be                                         In G.5.1, replace: "The data
incorrect throughout the                                           bits are shown in Table G.13
remainder of Annex G.                                              (First 144 DATA bits) and
                                                                   Table G.14 (Last 144 DATA
In 802.11n, Draft 11.0, the                                        bits). For clarity, only the first
correct information is present                                     and last 144 bits are shown."
for the BCC example. The                                           with "The DATA bits are
format has been changed to                                         shown in Table G.13."
include the all the symbols, as
well as pointing out that the                                      Replace Table G.13 with that
FEC code being used is BCC                                         in P802.11n D11.0 and delete
(as opposed to LDPC for                                            Table G.14.
802.11n) throughout. (This
became necessary to                                                In G.5.2, replace: "The first
illustrate the various pre-                                        and last 144 scrambled bits
processing techniques:                                             are shown in Table G.16 (First
padding, shortening, and                                           144 bits after scrambling) and
repetition. It was also                                            Table G.17 (Last 144 bits
necessary to renumber the                                          after scrambling),
subclauses, inserting a higher                                     respectively." with "The
level G.1-G.3 numbering, for                                       scrambled DATA bits are
the three examples in                                              shown in Table G.16."
802.11n).
"during operation" should be    as noted.                          AGREE (EDITOR: 2009-07-        EDITOR
"during the operation"                                             01 11:46:36Z)

"a gap…exist between"            as noted.                         AGREE (EDITOR: 2009-07-              EDITOR
should be "a gap exists                                            02 13:16:08Z)
between"
"using eight different UPs"      as suggested.                     DISAGREE (MAC: 2009-09-              EDITOR
should state "using up to eight                                    24 22:22:07Z) - The cited text
different UPs", since "using" is                                   refers to the EDCA
different from "supporting"                                        mechanism, which provides
and a STA can use only a                                           eight UPs.
subset of the allowed UPs.

"to use RTS/CTS" should be       as suggested.                     AGREE (MAC: 2009-07-14               EDITOR
"to initiate RTS/CTS" since                                        15:42:52Z)
the dot11RTSThreshold is
only for triggering the initial
RTS/CTS frame.
In the figure, if by "DIFS/AIFS" as noted.                         AGREE IN PRINCIPLE            EDITOR
we mean "DIFS or AIFS", it                                         (EDITOR: 2009-07-02
should be stated as such.                                          13:27:32Z) - replace "Medium
Also, "Medium is free" is not                                      is free >= DIFS/AIFS[i]" with
the same as the "medium is                                         "Medium is idle >= DIFS or
idle" description used in the                                      AIFS[i]" in figure 9-3.
rest of the document.
"a HC" should be "an HC" to    as noted.                    AGREE IN PRINCIPLE              EDITOR
be consistent and correct.                                  (EDITOR: 2009-07-02
                                                            15:46:31Z)
                                                            Make this change globally (3
                                                            occurances)
Expand clause heading to       as noted.                    AGREE (EDITOR: 2009-07-         EDITOR
"Extended Rate PHY (ERP)                                    01 09:45:21Z)
Specification"
In previous ballot, my         Delete subclause 14.8.2.4    AGREE (GEN: 2010-01-21          EDITOR
comment, #1000 regarding                                    00:30:00Z)
operating temperature, was
approved, but not all of the
changes were made.


In previous ballot, my         Delete FH8.20, FH8.20.1, and DISAGREE (GEN: 2010-01-      EDITOR
comment, #1000 regarding        FH8.20.2 (while row for each) 20 07:46:55Z) PICS entries
operating temperature, was                                    for temperature were
approved, but not all of the                                  intentionally kept. See
changes were made.                                            resolution to CID #1000 in
                                                              LB149.
In previous ballot, my         Delete DS12, DS12.1,           AGREE IN PRINCIPLE (GEN: EDITOR
comment, #1000 regarding       DS12.2, and DS12.3 (while      2010-01-21 01:08:34Z) -
operating temperature, was     row for each)                  Move the PICS entries for
approved, but not all of the                                  DS12 ( temperature Items)
changes were made.                                            from A.4.6 to A.4.3.
                                                              Renaming the items
                                                              appropriately.




In previous ballot, my         Delete IR24 (while row)      AGREE (GEN: 2010-01-21          EDITOR
comment, #1000 regarding                                    01:12:00Z) -
operating temperature, was
approved, but not all of the
changes were made.
In previous ballot, my         Delete OF3.10, OF3.10.1,     DISAGREE (GEN: 2010-01-         EDITOR
comment, #1000 regarding       OF3.10.2, and OF3.10.3       20 07:50:40Z) -- PICS entries
operating temperature, was     (while row for each)         for temperature were
approved, but not all of the                                intentionally kept. See
changes were made.                                          resolution to CID #1000 in
                                                            LB149.
In previous ballot, my         Delete HRDS15, HRDS15.1,     DISAGREE (GEN: 2010-01-         EDITOR
comment, #1000 regarding       and HRDS15.2(while row for   20 07:51:35Z) - PICS entries
operating temperature, was     each)                        for temperature were
approved, but not all of the                                intentionally kept. See
changes were made.                                          resolution to CID #1000 in
                                                            LB149
In previous ballot, my         Delete                       AGREE IN PRINCIPLE            EDITOR
comment, #1000 regarding       dot11PHYdot11TempType        (EDITOR: 2010-03-15
operating temperature, was     and dot11TempType rows of    20:35:50Z)
approved, but not all of the   Table 15-1                   Agree in principle, remove
changes were made.                                          "dot11Temp" from the
                                                            dot11PHYdot11TempType
                                                            and remove the following row.




In previous ballot, my         Delete dot11TempType row     AGREE (GEN: 2010-01-21        EDITOR
comment, #1000 regarding       of Table 16-8                00:32:19Z)
operating temperature, was
approved, but not all of the
changes were made.




In previous ballot, my         Delete dot11TempType row     AGREE (GEN: 2010-01-21        EDITOR
comment, #1000 regarding       of Table 18-4                00:33:26Z)
operating temperature, was
approved, but not all of the
changes were made.
In previous ballot, my         Delete "synonym              DISAGREE (GEN: 2010-01-       EDITOR
comment, #1000 regarding       dot11TempType Integer = 01;" 20 07:56:29Z) Reject. Annex
operating temperature, was                                  C is not maintained
approved, but not all of the
changes were made.
In previous ballot, my         Delete dot11TempType line   AGREE IN PRINCIPLE             EDITOR
comment, #1000 regarding       from Dot11PhyOperationEntry (EDITOR: 2010-03-16
operating temperature, was                                 20:51:56Z) - Mark it
approved, but not all of the                               Deprecated (page 1420 line
changes were made.                                         3) change status of
                                                           dot11TempType object to
                                                           "Deprecated" -Insert in the
                                                           beginning of the description:
                                                           "The use of dot11TempType
                                                           is deprecated, because
                                                           references to this variable
                                                           have been removed from the
                                                           normative text of IEEE Std
                                                           802.11-<year>, and this entity
                                                           may be removed in a later
                                                           revision of the standard."

In previous ballot, my         Delete all of dot11TempType   AGREE IN PRINCIPLE             EDITOR
comment, #1000 regarding       OBJECT-TYPE                   (EDITOR: 2010-03-16
operating temperature, was                                   20:51:56Z) - Mark it
approved, but not all of the                                 Deprecated (page 1420 line
changes were made.                                           3) change status of
                                                             dot11TempType object to
                                                             "Deprecated" -Insert in the
                                                             beginning of the description:
                                                             "The use of dot11TempType
                                                             is deprecated, because
                                                             references to this variable
                                                             have been removed from the
                                                             normative text of IEEE Std
                                                             802.11-<year>, and this entity
                                                             may be removed in a later
                                                             revision of the standard."

In previous ballot, my         Delete dot11TempType from AGREE IN PRINCIPLE (GEN: EDITOR
comment, #1000 regarding       dot11PhyOperationComplianc 2010-01-20 08:27:05Z) --
operating temperature, was     eGroup OBJECT-GROUP        Accept in principle. Create a
approved, but not all of the                              new
changes were made.                                        dot11PhyOperationComplianc
                                                          eGroup with dot11TempType
                                                          not included and deprecate
                                                          existing
                                                          dot11PhyOperationComplianc
                                                          eGroup.
In previous ballot, my           Delete dot11TempType row           AGREE (GEN: 2010-01-21    EDITOR
comment, #1000 regarding         from Table 14-22                   00:28:28Z)
operating temperature, was
approved, but not all of the
changes were made.
CID 1001 in LB149                Please decide if BSSID             AGREE IN PRINCIPLE (MAC: EDITOR
highlighted a conflict between   should ever be checked for a       2010-03-17 19:09:27Z).
NAV reset in clauses 9.3.2.2,    NAV reset from a CF-End.           Change 9.9.2.2a to read:
9.3.3.1 and 9.9.2.2a. The        Once this decision has been        "When the AP contains a PC,
changes made in draft 2 has      made, make all three sited         during the CFP, it may reset
changed the clause that is the   clauses follow the chosen          the NAVs of all receiving
"odd one out" but alas not       behaviour.                         STAs by sending a CF-End
removed conflicting normative                                       frame, regardless of how the
behaviour. Clause 9.3.3.1                                           NAVs have been originally
says "All STAs of the BSS                                           set." Additionally change
receiving a CF-End or CF-                                           9.3.3.1 to read: "A STA
End+ACK shall reset their                                           receiving a CF-End or CF-
NAVs", clause 9.3.2.2 says                                          End+ACK shall reset its NAV."
"The PC shall transmit a CF-
End or CF-End+ACK frame at
the end of each CFP. A STA
that receives either of these
frames, from any BSS, shall
reset its NAV." and clause
9.9.2.2a says "When the AP
contains a PC, during the
CFP, it may reset the NAVs of
all STAs within the BSS (i.e.,
corresponding to the same
BSSID) by sending a CF-End
frame, regardless of how the
NAVs have been originally
set."


Does "The value of the           Change to "The value of the        AGREE IN PRINCIPLE (MAC: EDITOR
Minimum PHY Rate in a            Minimum PHY Rate in a              2010-01-20 02:15:00Z).
TSPEC shall be in both the       TSPEC shall be in both the         Revert changes made in
AP’s operational rate set and    AP’s operational rate set and      response to CID 1512 to
non-AP STA’s operational         non-AP STA’s operational           restore directionality of
rate set." need to mention the   rate set of the direction of the   transmission rates.
direction, because operational   TS."
rates can be different in each
direction?

dot11ExtendedChannelSwitch per comment                              AGREE IN PRINCIPLE         EDITOR
Enabled should be                                                   (SECURITY: 2010-01-12
dot11ExtendedChannelSwitch                                          21:31:08Z)
Activated                                                           Change
                                                                    dot11ExtendedChannelSwitch
                                                                    Enabled to
                                                                    dot11ExtendedChannelSwitch
                                                                    Activated.
Note 1 b) refers to "Supported per comment                          AGREE (EDITOR: 2010-01-    EDITOR
RM Capabilities Enabled                                             20 14:51:58Z)
bitmask", but should refer to
"RM Enabled Capabilities
bitmask" (see 7.3.2.25).
dot11MultiDomainCapabilityIm per comment   AGREE (GEN: 2010-01-20    EDITOR
plemented is a capability, and             07:59:38Z)
should have MAX-ACCESS of
"read-only" instead of "read-
write"
dot11RegulatoryClassesImple per comment    AGREE (GEN: 2010-01-20    EDITOR
mented is a capability, and                08:02:49Z)
should have MAX-ACCESS of
"read-only" instead of "read-
write"
Description "BSS Availabele" per comment   AGREE (EDITOR: 2010-01-   EDITOR
should be "BSS Available"                  20 14:53:00Z)

dot11ExtendedChannelSwitch per comment     AGREE IN PRINCIPLE (GEN: EDITOR
Activated. Description "It is              2010-01-20 08:07:02Z);.
written by the SME when the                Change to "It is written by the
device is initialized." is                 SME when the device is
incomplete, and should be "It              initialized for operation in a
is written by the SME when                 band defined by a Regulatory
the device is initialized for              Class."
operation in a band defined by
a Regulatory Class." Multi-RC
operation will commonly
change DFS/TPC and
Extended Channel Switch as
the STA changes channels
(5.725 GHz does not have
radar detection requirements,
but 5.6 GHz does).

dot11ERPBCCOptionActivated per comment     AGREE (GEN: 2010-01-20    EDITOR
. Should have MAX-ACCESS                   08:21:01Z)
of "read-write", and
description should match
dot11DSSSOFDMOptionActiv
ated - "It is written by an
external management entity.
Changes take effect for the
next MLME-START.request or
MLMEJOIN.
request."
dot11RMRqstTimeStamp           per comment   AGREE IN PRINCIPLE              EDITOR
should have MAX-ACCESS of                    (EDITOR: 2010-03-16
"read-create" like the rest of               20:59:50Z) - Make change as
RMRqst.                                      indicated.

                                             Also change "It is written by
                                             an external management
                                             entity when requesting a
                                             measurement(#1005)." to "It
                                             is written by the SME when
                                             dot11RMRequestRowStatus
                                             is set to Active."

                                             Also delete: "Changes take
                                             effect when
                                             dot11RMRqstRowStatus is
                                             set to
                                             Active(#1005)." and "This
                                             attribute is(#1452) set by this
                                             STA
                                             or AP automatically, not by an
                                             SNMP manager."
dot11FrequencyBandsImplem per comment        AGREE IN PRINCIPLE (GEN: EDITOR
ented. Description of                        2010-01-21 22:22:51Z) Add to
deprecated entry should begin                description "Superseded by
"Superseded by subband-                      subband-specific supported
specific supported regulatory                regulatory classes."
classes." and remove the text
that D2.0 inserted - "This is a
capability variable.
Its value is determined by
device capabilities."

dot11RegDomainsSupportedE per comment        AGREE IN PRINCIPLE (GEN: EDITOR
ntry should have status                      2010-01-21 22:17:25Z)
"deprecated" as it does not                  Change the status to
function with channel                        Deprecated and Add the
switching and                                following to the description:
SupportedRegulatoryClasses.                  "Superceded by
It is deprecated is because                  dot11RegulatoryClassesTable.
determining legal operation is               "
above the PLCP and PMD
(clause 9.8) - checking validity
of channel switch commands
is above the PHY.
The open authentication and     I'm hoping the editor will      AGREE IN PRINCIPLE            EDITOR
shared key authentication       provide guidance if I have to   (SECURITY: 2010-03-05
handshake description can be    make a submission about         16:28:29Z)
be streamlined like 11.11.2.2   anything in clause 8 ;-)        Incorporate the changes given
DSE Enablement has been                                         in document 11-10/206r0.
changed in D2.0 - remove
message type, subtype and
direction of message. Noone
should use 8.2.2.2 or 8.2.2.3
as a template for a handshake
specification, and I request
that someone submit the text
changes.

D1.0 CID 1053 resolution        per comment                     DISAGREE (MAC: 2010-01-         EDITOR
incomplete. The other                                           19 06:10:14Z). It is already
deprecated modulations (FH                                      marked as such. No need to
PHY and ERP-PBCC PHY)                                           separately mark every
should have similar end of life                                 occurrence in the text of the
statements as what was                                          feature.
added to the DSSS-OFDM
"The use of the DSSS-OFDM
option is deprecated, and this
option
may be removed in a later
revision of the standard."
D1.0 CID 1051 resolution        per comment                     AGREE IN PRINCIPLE (GEN: EDITOR
incomplete. MD7 (and other                                      2010-01-21 23:20:10Z) CID
deprecated modulations) did                                     1051 did indicate that the
not receive the agreed                                          statement was to be placed in
resolution text. Please                                         the "cited locations". Add the
indicate in Multi-Domain PICS                                   sentence "The use of hopping
each deprecated PHY with                                        patterns is obsolete, and may
text like appears in A.4.14                                     be removed in a later revision
ERP ERP2.                                                       of the standard."




D1.0 CID 1052 resolution         per comment                    DISAGREE (MAC: 2010-01-         EDITOR
incomplete. Channel agility                                     19 06:11:16Z). It is already
description (and other                                          marked as such. No need to
deprecated capabilities)                                        separately mark every
should be followed by text like                                 occurrence in the text of the
that added after ERP-PBCC -                                     feature.
"The use of the ERP-PBCC
option is deprecated, and this
option may be removed in a
later revision of the standard."
dot11RegulatoryClassesRequi       End the description text with   AGREE (GEN: 2010-01-20        EDITOR
red changed description adds      "is true." and delete ";        08:03:54Z)
new requirement - ";              otherwise it will not use the
otherwise it will not use the     defined regulatory classes’
defined regulatory classes’       procedures."
procedures." - that is not
compatible with legacy
systems that use
SupportedRegulatoryClasses
when
dot11ExtendedChannelSwitch
Activated is true in the 2.4
GHz and 5 GHz bands.
The PICS does not describe        per comment                     AGREE (GEN: 2010-01-21        EDITOR
operational combinations of                                       01:18:49Z)
mandatory and optional
elements, only what element
implementation is claimed.
Add a warning after the third
sentence - "This clause may
not be compatible with
operation in any Regulatory
Domain or describe
combinations of usable
features in any Regulatory
Domain."
PICS The reference in the first   Fix the reference.              AGREE IN PRINCIPLE               EDITOR
sentence is incorrect "claimed                                    (EDITOR: 2010-01-29
to conform to IEEE Std                                            14:16:20Z) - Replace 2007 by
802.11-2007"                                                      "<year>" and move the
                                                                  following editorial note (occurs
                                                                  later in Annex A) to just after
                                                                  the A.1 heading: "<year> will
                                                                  be replaced with the year of
                                                                  publication during publication
                                                                  of this standard by the IEEE-
                                                                  SA editorial staff."

D1.0 CID 1055 resolution          Add a row to Table I-1 China AGREE (GEN: 2010-01-20           EDITOR
incomplete. The Regulatory        : Ministry of Industry and    08:27:41Z)
information for China 2.4 GHz     Information Technology (MIIT)
and 5.8 GHz is missing.           : Xin Bu Wu [2002] #353, Xin
                                  Bu Wu [2002] #277 : MIIT

ETSI Fixed operation in 5.725- Change the last row/last           AGREE (GEN: 2010-01-20        EDITOR
5.875 GHz allows 4W EIRP.      column of Table I.4 from           08:28:23Z)
                               emdash to "4 W"
Table J.3 Japan. RC 1 - The    add channels 36-48 to RC 1         AGREE (GEN: 2010-01-20        EDITOR
old channels 34, 38, 42, 46    and add a footnote for             08:29:39Z)
are only allowed until 2012,   channels 34, 38, 42 and 46
and the normal 36, 40, 44, 48 indicating they cannot be
have been allowed since        used after 2012.
2005. The old channels
should have a footnote
indicating they cannot be
used after 2012 (MIC EO
49.20).
Table I.2 Japan regulator for     Change reference to MIC          AGREE (EDITOR: 2010-01-         EDITOR
Emissions limits 4 is MIC, not    here and in table I.3 P1627      29 15:44:45Z)
MPHPT (prior name)                line 30.
No reference in clause 2 or       Update and provide correct       AGREE IN PRINCIPLE              EDITOR
Annex 0A describes the            reference for definition of      (EDITOR: 2010-01-28
current standard "address as      IEEE MAC address.                12:08:15Z)
defined in 5.2 of IEEE Std 802-                                    Update reference to: "9.2 of
1990"                                                              IEEE Std 802-2001".
No reference in clause 2 or       Update and provide correct       AGREE IN PRINCIPLE              EDITOR
Annex 0A describes the            reference for definition of      (EDITOR: 2010-01-27
current standard "address as      IEEE MAC address here and        15:26:06Z)
defined in 5.2 of IEEE Std 802-   7.1.3.3.2.                       Change reference to "9.2 of
1990"                                                              IEEE Std 802-2001".
dot11xxxIfIndex are Integer32     Change Annex D IfIndex           Agree in principle. Make the    EDITOR
almost everywhere, but            SYNTAX to be one value           changes as shown in
should not be negative. In        throughout.                      document 11-10/0216r2.
SNMP (RFC-2587) terms,
ifIndex could be "SYNTAX
InterfaceIndex", which could
be unsigned 32 but not
negative. "It is recommended
that values are assigned
contiguously " starting from 1.


It is time to get rid of Annex    Add an Editorial note that the   AGREE IN PRINCIPLE              EDITOR
styles for tables and figures,    Editor will change all Annex     (EDITOR: 2010-01-29
and make standards creation       table and figure numbering to    14:44:44Z)
easier for ourselves. The         match the main text "clause-     Adjust Annex table and figure
main body text names tables       number" when the draft is        labelling to replace dot with
with "clause-number" but          renumbered.                      hyphen.
Annex B uses
"clause.number". The IEEE
2009 Style Manual says be
consistent in clause 12.
Japan permits unlicensed          Insert final row in Table I.6 for AGREE (GEN: 2010-01-20         EDITOR
Fixed operation in 5.47-5.725     this band per comment             08:28:04Z)
GHz at power < 10 mW/MHz
EIRP.
Japan permits unlicensed          Insert Regulatory Class 33 : 5 AGREE (GEN: 2010-01-20            EDITOR
Fixed operation in 5.47-5.725     : 20 : 100, 104, 108, 112, 116, 08:30:03Z)
GHz at power < 10 mW/MHz          120, 124, 128, 132, 136, 140 :
EIRP.                             (22 transmit power column
                                  gets deleted) : 1 : 1, 3, 4, 6, 10




RC 32 Channel starting            per comment                      AGREE (EDITOR: 2010-01-         EDITOR
frequency is "5.0" and should                                      29 15:47:13Z)
be "5"
ETSI Fixed operation in 5.725- Insert Regulatory Class 5 : 5 : AGREE (GEN: 2010-01-20              EDITOR
5.875 GHz allows 4W EIRP.      20 : 149, 153, 157, 161, 165, 08:29:18Z)
                               169 : (4 transmit power
                               column gets deleted) : 3, 4




D1.0 CID 1301 resolution          per comment                    AGREE (GEN: 2010-01-20            EDITOR
incomplete. The transmit                                         08:28:45Z)
power columns in Annex J.1
tables J.2 and J.3 should be
removed, as that information
is in tables I.4 and I.6 - D1.0
approved resolutions
09/1111r2 says "Propose
Accept in Principle CID 1301
and remove transmit power
from Annex J.1" - with editing
instruction "Delete seventh
paragraph text and Table
Columns labelled “Transmit
power limit” in Annex J.1 "

Annex A tables are not          Add an Editorial note that the   DISAGREE (EDITOR: 2010-           EDITOR
labeled, unlike main body text. Editor will change all Annex     01-29 14:20:38Z)
Tables should have labels.      table numbering to match the     While acknowledging that the
                                main text "clause-number"        IEEE-SA style guide
                                convention when the draft is     recommends all tables have
                                renumbered.                      titles, this is unnecessary
                                                                 here because each table
                                                                 occupies its own subclause.
                                                                 Reference to each table as a
                                                                 whole can be made through
                                                                 its subclause.

                                                                 Each entry is identified in the
                                                                 first column, so that reference
                                                                 to any entry can be made
                                                                 unambiguously.

                                                                 The table titles would exactly
                                                                 mirror the subclause title -
                                                                 adding no value. Adding table
                                                                 titles would also necessitate a
                                                                 sentence to reference it, i.e.
                                                                 "The Implementation
                                                                 identification is shown in
                                                                 Table A-1", which adds text
                                                                 with no value.
Clause 10 tables are not         Add an Editorial note that the    UNRESOLVABLE (EDITOR:            EDITOR
labeled, unlike the rest of      Editor will label all clause 10   2010-01-28 11:58:31Z)
main body text. Tables should    tables to match the main text     Withdrawn by commenter
have labels.                     convention when the draft is      2010-01-27 in email to editor.
                                 renumbered.

dot11MultiDomainCapabilityAc     Remove final sentence and       AGREE (GEN: 2010-01-20             EDITOR
tivated changed description      leave it unspecified what parts 08:00:43Z) Accept. Remove
adds new requirement - "The      of MultiDomainCapability (e.g. final sentence.
capability is disabled           Country information) are
otherwise." - that is not        available when not "activated".
compatible with legacy
systems that have
implemented
MultiDomainCapability. I think
there are some parts of
MultiDomainCapability that
are used (e.g. Country
information) even when
MultiDomainCapability is not
"Required", and want this new
requirement justified by
analysis of legacy STAs or
removed.
I object to the resolution of    Remove p1502 line 14            AGREE IN PRINCIPLE (GEN: EDITOR
D1.0 CID 1588. Some              Editor's note about big-endian. 2010-01-20 08:25:40Z) -
location variables are more                                      Accept in principle. The value
than one octet                                                   of the MIB variable is an
(e.g.dot11LCIDSELatitudeInte                                     integer. Endianness only
ger), and SNMP access has                                        matters when values are
endianness. Editor's note                                        stored as sequences of bytes.
about D1.0 CID 1588 "and is                                      Remove Editor's Note.
accessed big-endian" should                                       Additional changes given for
be removed, as the editor did                                    CID 2203.
the right thing in D2.0.
dot11LCIDSE Table is               Commenter will make a             UNRESOLVABLE (GEN:          EDITOR
inadequate, containing an          submission with separate MIB      2010-03-08 19:46:45Z) -
entry from the STA's               entries for the STA itself, and   GEN: 2010-03-08 19:44:27Z -
management entity and              dot11LCIDSE table for             From the comment
entries from received beacons      observed IEs from other STAs.     submitter:
and public action frames.                                            I submitted CID 2050 about
There needs to be another set                                        the MIB dot11LCIDSETable:
of MIB variables for the STA
itself, and this table remains                                       "dot11LCIDSE Table is
for observed LCIDSE                                                  inadequate, containing an
information elements.                                                entry from the STA's
                                                                     management entity and
                                                                     entries from received beacons
                                                                     and public action frames.
                                                                     There needs to be another set
                                                                     of MIB variables for the STA
                                                                     itself, and this table remains
                                                                     for observed LCIDSE
                                                                     information elements."

                                                                       After more closely looking at
                                                                     the scenarios for enabling
                                                                     STAs and dependent STAs, I
                                                                     see that each STA picks one
                                                                     entry to be active for itself,
                                                                     and the others are for/from
                                                                     other STAs. A dependent STA
                                                                     does not know it’s location,
                                                                     but uses the location in the
                                                                     enablement message.

                                                                      I request that my CID 2050
dot11EDThreshold should be         per comment                     be withdrawn from 2010-01-
                                                                   AGREE (EDITOR: the LB160 EDITOR
dot11OFDMEDThreshold.                                              29 14:08:43Z)
dot11OFDMEDThreshold "It is        Make this change wherever       AGREE IN PRINCIPLE (GEN: EDITOR
written by the SME when the        the MIB entry value is affected 2010-01-20 08:20:41Z) -
device is initialized" should be   by a channel switch action.     Accept in principle. Change to
"It is written by the SME when                                     "It is written by the SME when
the device is initialized for                                      the device is initialized for
operation in a particular band                                     operation in a band defined by
or regulatory class, and can                                       a Regulatory Class, or written
be written by an external                                          by an external management
management entity."                                                entity."
dot11OFDMCCAEDRequired. Make this change wherever                   AGREE IN PRINCIPLE (GEN: EDITOR
The MIB description "It is        the MIB entry value is affected   2010-01-20 08:18:35Z) -
written by the SME when the by a channel switch action.             Accept in principle. Change to
device is initialized." is                                          "It is written by the SME when
incorrect. Many multiband                                           the device is initialized for
STAs with multiple Regulatory                                       operation in a band defined by
Classes will use different                                          a Regulatory Class."
radio modes depending on
Regulatory Classes, and will
update the MIB when
changing channels, not "when
the device is initialized.". The
text should read "It is written
by the SME when the device
is initialized for operation in a
particular band or regulatory
class."

dot11RMRqstToken MAX-             Describe when it is created.      AGREE IN PRINCIPLE (GEN: EDITOR
ACCESS is read-create, how                                          2010-02-26) Global change all
does it get written?                                                "It is written by an external
                                                                    management entity when
                                                                    requesting a measurement."
                                                                    To "It is written by an external
                                                                    management entity when the
                                                                    table entry is created, i.e.,
                                                                    when requesting a
                                                                    measurement."


"It is written by an external                                       AGREE IN PRINCIPLE (GEN: EDITOR
management entity", and it is                                       2010-01-20 08:23:25Z) -
written by the SME too. The                                         Accept in principle. Change to
description is inaccurate. Fix                                      "It is written by an external
the description whenever the                                        management entity when
MIB item is alse written by the                                     requesting a measurement,
STA.                                                                and by the SME when
                                                                    accepting a measurement
                                                                    request."
dot11RMRqstRowStatus is a           Change to read "This is a         AGREE IN PRINCIPLE (GEN: EDITOR
status, not a control variable. I   status variable." If it remains   2010-01-20 08:23:05Z)
don't know why it appears in        as a control variable, add        Accept in principle. Change to
the Rqst table, but it can only     descriptive text noting that it   "It is written by an external
have the value "NotInService"       shall be written as               management entity when
at the time of a request.           "NotInService".                   requesting a measurement,
                                                                      and by the SME when
                                                                      accepting a measurement
                                                                      request."




"ReasResultCode" should be          per comment                       AGREE (EDITOR: 2010-01-      EDITOR
"ReasonResultCode"                                                    20 14:52:20Z)
DS12 - PICS for DSSS                per comment                       AGREE IN PRINCIPLE (GEN:     EDITOR
temperature should be                                                 2010-01-21 01:08:34Z) -
removed.                                                              Move the PICS entries for
                                                                      DS12 ( temperature Items)
                                                                      from A.4.6 to A.4.3.
                                                                      Renaming the items
                                                                      appropriately.
OF3.10 - PICS for OFDM              per comment                       DISAGREE (GEN: 2010-01-      EDITOR
temperature should be                                                 20 07:50:08Z) PICS entries
removed.                                                              for temperature were
                                                                      intentionally kept. See
                                                                      resolution to CID #1000 in
                                                                      LB149.
HRDS15 - PICS for HRDS              per comment                       DISAGREE (GEN: 2010-01-      EDITOR
temperature should be                                                 20 07:51:11Z) PICS entries
removed.                                                              for temperature were
                                                                      intentionally kept. See
                                                                      resolution to CID #1000 in
                                                                      LB149.
dot11TempType should be           per comment   AGREE IN PRINCIPLE             EDITOR
deprecated and text referring                   (EDITOR: 2010-03-16
to setting it should be                         20:51:56Z) - Mark it
preceeded by text like "The                     Deprecated (page 1420 line
use of dot11TempType is                         3) change status of
deprecated, and this entity                     dot11TempType object to
may be removed in a later                       "Deprecated" -Insert in the
revision of the standard." . It's               beginning of the description:
value is specified in each PHY                  "The use of dot11TempType
clause, and it is part of                       is deprecated, because
dot11PhyOperation, which is                     references to this variable
part of                                         have been removed from the
dot11PhyOperationComplianc                      normative text of IEEE Std
eGroup.                                         802.11-<year>, and this entity
                                                may be removed in a later
                                                revision of the standard."

IR24 - PICS for IR          per comment         AGREE (GEN: 2010-01-21       EDITOR
temperature should be                           01:13:35Z)
removed.
SM18 CF2.1 should be CF2.2 per comment          AGREE (GEN: 2010-01-20       EDITOR
since DFS owner only exists                     07:54:17Z)
in IBSS (see 11.9.7.2).




SM10 CF2.1 should be CF2, per comment           AGREE (GEN: 2010-01-20       EDITOR
since reporting maximum                         07:53:20Z) -- Change to
transmit power levels also is                   "CF2.1 or CF2.2"
required in IBSS operation. I
think there are several other
CF2 modifications made in
D2.0 that are not correct (e.g.,
SM20), and trust the comment
resolution committee will
rigorously correct those
errors, or make the PICS
informative. RIP


SM19 CF2.1 should be CF2.2 per comment          AGREE (GEN: 2010-01-20       EDITOR
since DFS owner only exists                     07:54:55Z)
in IBSS.
In D2.0, CF2 is changed to    per comment       DISAGREE (GEN: 2010-01-      EDITOR
add CF2.1 and CF2.2 without                     20 07:44:51Z) -- Changes are
showing changebars in the                       shown in the way that
redlined D2.0. For D3.0                         FrameMaker shows changed
redlined, show the                              tables.
changebars everywhere
CF2.1 and CF2.2 exist, as the
changes should be flagged to
reviewers, or change Annex A
to informative.
There are two figures labeled     Fix figure numbering            AGREE (EDITOR: 2010-01-          EDITOR
Figure 7-95o7 (TIE format is                                      20 14:25:45Z)
the other one).

The size of the Local Power       Change Figure 7-101h8 to        AGREE (MAC: 2010-01-19           EDITOR
Constraint field should be 1      show the field size to be one   06:12:31Z).
octet.                            octet.




"It is written by an external     Change to "It is also written by AGREE IN PRINCIPLE (GEN: EDITOR
management entity", and it is     external management entities." 2010-01-20 07:59:04Z)
written by the SME too. The                                        Accept in principle. Change to
description is inaccurate both                                     "It is written by the SME or
in number of writers and                                           external management entity"
identity of the writers - e.g.,
CAPWAP has several
management entities.
I disagree with the change of     Restore D1.0 frame types for    AGREE IN PRINCIPLE (MAC: EDITOR
frame types from                  power save action.              2010-01-19 23:35:27Z).Insert
"management frames of the                                         the following paragraph within
following subtypes: Action,                                       clause 11.2.1.0a:
Disassocation,                                                    "A bufferable management
Deauthentication, or Probe                                        frame is a unicast
Response (when sent in                                            management frame,
response to a unicast Probe                                       addressed to an associated
Request)" to "an Action                                           STA, of the following
frame", and want this                                             subtypes: Action,
unchanged in REVmb.                                               Disassociation,
                                                                  Deauthentication, or Probe
                                                                  Response (when sent in
                                                                  response to a unicast probe
                                                                  request); or a group-
                                                                  addressed management
                                                                  frame of the following
                                                                  subtypes: Action,
                                                                  Disassociation, or
                                                                  Deauthentication. A
                                                                  bufferable MMPDU is an
                                                                  MMPDU that will be
                                                                  transmitted using a bufferable
                                                                  management frame."

                                                                  Wherever "Action frame" is
                                                                  used in clause 11.2.1, replace
                                                                  with "bufferable management
                                                                  frame". Wherever "MMPDU"
                                                                  is used in clause 11.2.1,
                                                                  replace with "bufferable
                                                                  MMPDU." Make changes for
                                                                  consistency or to remove and
dot11SpectrumManagementR Change the description to            AGREE IN PRINCIPLE (GEN: EDITOR
equired can be set or cleared include extended channel        2010-01-20 08:02:24Z) -
by the SME when changing          switch.                     Accept in principle. There is
channels, and is a                                            no such thing as a
control/status variable. If set                               control/status variable.
by an external management                                     Change to "It is written by the
entity, then "It is written by an                             SME or external management
external management entity.                                   entity"
Changes take effect for the
next MLME-START.request.",
otherwise the SME may
change it when changing
regulatory classes.

dot11MultiDomainCapabilityAc Change the description to        AGREE IN PRINCIPLE (GEN: EDITOR
tivated can be set or cleared     include extended channel    2010-01-20 08:00:15Z)
by the SME when changing          switch.                     Accept in principle. There is
channels, and is a                                            no such thing as a
control/status variable. If set                               control/status variable.
by an external management                                     Change to "It is written by the
entity, then "It is written by an                             SME or external management
external management entity.                                   entity"
Changes take effect for the
next MLME-START.request.",
otherwise the SME may
change it when changing
regulatory classes.

dot11CountryString can be        Change the description to be AGREE (GEN: 2010-01-20           EDITOR
changed by the SME when          a status variable written by the 08:01:37Z) Accept. Change to
changing channels, and is        SME.                             "It is written by the SME"
read-only. It is NOT a control
variable, not written by an
external management entity.

dot11RegulatoryClassesRequi Change the description to         AGREE IN PRINCIPLE (GEN: EDITOR
red can be set or cleared by      include extended channel    2010-01-20 08:03:16Z)
the SME when changing             switch.                     Accept in principle. There is
channels, and is a                                            no such thing as a
control/status variable. If set                               control/status variable.
by an external management                                     Change to "It is written by the
entity, then "It is written by an                             SME or external management
external management entity.                                   entity"
Changes take effect for the
next MLME-START.request.",
otherwise the SME may
change it when changing
regulatory classes.
dot11LCIDSERequired can be Change the description to         AGREE (GEN: 2010-01-20           EDITOR
changed by the SME when        include extended channel      08:04:15Z) - Accept. Change
changing channels, and is      switch.                       to "It is written by the SME".
read-only. It is NOT a control                               Change to read-only.
variable, not written by an
external management entity.




dot11DSERequired can be          Change the description to   AGREE (GEN: 2010-01-20           EDITOR
changed by the SME when          include extended channel    08:04:39Z) - Accept. Change
changing channels, and is        switch.                     to "It is written by the SME".
read-only. It is NOT a control                               Change to read-only.
variable, not written by an
external management entity.




dot11ExtendedChannelSwitch Change the description to         AGREE IN PRINCIPLE (GEN: EDITOR
Activated can be changed by include Regulatory Classes       2010-01-20 08:07:47Z)
the SME when initializing for a Required.                    Accept. Change to "It is
band defined by a Regulatory                                 written by the SME when the
Class, and is read-only. This                                device is initialized for
replaces my earlier comment.                                 operation in a band defined by
                                                             a Regulatory Class."
dot11LCIDSETable is read-         Change the description to be DISAGREE (GEN: 2010-01-               EDITOR
only, with SME values for         a status variable written by the 20 08:11:13Z) -- Variables
operation in a Regulatory         SME.                              written by the SME and used
Class that requires DSE.                                            by the MAC are control
                                                                    variables, not status variables.
                                                                     If it was written by the SME
                                                                    and only used by external
                                                                    entities, then it would be
                                                                    considered status.
"The issue might be named         Extend Annex M to document OUT OF SCOPE (MAC: 2010- EDITOR
""gratuitous double-              and specific the details of how 03-12 17:28:55Z). This
encapsulation"". It involves      to do this in an interoperable    comment is not directed to
deliberately (and incorrectly)    fashion, since the behavior is changed text between REVmb
placing an additional             out there in the field. Note that Draft 1.0 and Draft 2.0 and is
RFC1042 SNAP header               whether we want to                out of scope for recirculation
around the contents of a          discourage it or not is open to LB 160.
frame that already has such a debate.
header (in particular, an
AppleTalk Phase II frame) to
encode the length field. The
decoding rules for the default
case of 802.1H then cause a
correct implementation to strip
the outer SNAP header and
turn it into an 802.3 length
field, leaving the interior
SNAP header alone (since the
length field in the outer SNAP
header is neither the
AppleTalk nor IPX special-
case encoding/decoding rules
value).
    There are implementations
out there that do this on
purpose, since then an
incorrect (always remove
SNAP header) and a correct
(do not remove SNAP header
if it's one of the special values
or is the BTEP header)
implementation both produce
the same 802.3 frame on the Restore the Titlebaum
The Titlebaum reference                                             AGREE (GEN: 2010-01-20           EDITOR
(B35) is required as a source reference (B35) and add a             06:32:54Z) - Restore the
of the material in clause         corresponding link or             referene (B35) and in 9.8.2
clause 9.8.2. It was present in reference to clause 9.8.2 to        (page 406 line 22) Change
D1.0 but has been removed         anchor the reference.             text from "please see the
from D2.0                                                           reference [B4]" to "please see
                                                                    the references [B4] and [B35]."

Also need to cite Titlebaum     Change text from "please see AGREE (GEN: 2010-01-20               EDITOR
reference (B35).                the reference [B4]" to "please 06:30:35Z)
                                see the references [B4] and
                                [B35]."
In this Note, sentence             Please remove the Note.           DISAGREE (GEN: 2010-01-        EDITOR
"Support for CCA-ED is an          Three paragraphs above this       20 07:39:29Z) Reject. The text
additional requirement that        note are already clear enough     is clear, note is helpful in
relates specifically to the        about this. The Note serves       understanding the rational
sensitivities described in I.2.4   only as a confusion.              behind the text
(CCA-ED threshold)" may
lead a reader to conclude that
CCA-ED requirement at -72
dBm is for all clause 17
devices.
Fix page numbering.                As in comment.                    DISAGREE (EDITOR: 2010-          EDITOR
                                                                     01-20 14:55:33Z)
                                                                     The draft sent to ballot had
                                                                     correct page numbering.
                                                                     (Note to commenter:
                                                                     Comments should not be
                                                                     based on the redline draft.)
Is it too early to specify in      Make it a more a specific         DISAGREE (EDITOR: 2010-          EDITOR
definitions bit settings?          definition without explicit bit   01-27 14:50:40Z)
                                   settings.                         By definition, A group
                                                                     address is one in which the
                                                                     group bit is set to 1, because
                                                                     this is the only property of a
                                                                     group address that
                                                                     distinguishes it from an
                                                                     individual address.

                                                                     As this is fundamental to the
                                                                     specification of a group
                                                                     address, there is no problem
                                                                     including it in the definition
                                                                     clause.
"invoke" instead of 'invokes"      As in comment.                    AGREE (EDITOR: 2010-01-          EDITOR
                                                                     20 14:23:52Z)
Can "in the clear" be better       As in comment.                    AGREE IN PRINCIPLE               EDITOR
explained?                                                           (EDITOR: 2010-01-27
                                                                     15:00:54Z)
                                                                     Add ", i.e., without protection"
                                                                     to the end of the cited
                                                                     sentence.
After "..transmitter power         As in comment.                    DISAGREE (EDITOR: 2010- EDITOR
control" include "(TPC)"                                             01-27 15:04:53Z)
                                                                     The acronym is quoted as
                                                                     "transmit power control
                                                                     (TPC)" in the immediately
                                                                     previous subclause, and there
                                                                     is no need to repeat this.

"The OFDM PHY shall use            Please delete this sentence.      DISAGREE (GEN: 2010-01-          EDITOR
dot11CurrentFrequency to                                             20 07:36:56Z) Reject.
determine the operating                                              dot11CurrentFrequency is a
frequency." This sentence                                            control variable, written by the
with "shall" statement is not                                        SME. This sentence forces
necessary here. This relates                                         the PHY to use it.
to configuration attributes of
the device.
Does there need to be a             Clarify whether FCS result          DISAGREE (MAC: 2010-01-       EDITOR
mention here of the success         needs to be mentioned here.         20 01:58:36Z). Frames are
of the FCS result?                                                      only received after passing
                                                                        the FCS check, according to
                                                                        the conventions in 7.1.1 (7th
                                                                        paragraph). Frames which do
                                                                        not pass the FCS check are
                                                                        not processed further.

What is the difference, in the      Clarify whether the correct         DISAGREE (GEN: 2010-01-        EDITOR
context of 802.11, of being         adjective has been used.            20 06:28:04Z) Correct
obsolete vs deprecated?                                                 adjective has been used in
                                                                        this case. Deprecated
                                                                        functions fail to perform the
                                                                        function described (e.g.,
                                                                        WEP); obsolete functions
                                                                        works as described, but are
                                                                        not used in any known
                                                                        products. If a function marked
                                                                        as "obsolete" is actually used
                                                                        in an 802.11 implementation,
                                                                        it should be brought to the
                                                                        Task Group's attention and
                                                                        the marking of "obsolete" will
                                                                        be removed
You say "power management           Make the change indicated.          AGREE IN PRINCIPLE (MAC: EDITOR
state" in this sentence, but I                                          2010-01-20 02:24:02Z) -
believe that you mean to say                                            Change P622L63 from: "A
"power management mode"                                                 non-AP STA shall not change
                                                                        power management state..."
                                                                        to read "A non-AP STA shall
                                                                        not change power
                                                                        management mode..."

MA-UNITDATA-                        Change "that was used" to           AGREE IN PRINCIPLE (MAC: EDITOR
STATUS.indication is almost         "that is anticipated to be used"    2010-03-15 18:10:24Z).
cleaned up from looking like it     in the penultimate paragraph        Change 6.2.3.2 as shown in
was a guaranteed delivery           of 6.2.3.2, and "used" to "that     11-10/0308r0. This removes
service. But, there are minor       will be used" in the ultimate       any implication about the
hints of this left, like the last   paragraph of 6.2.3.2. Also,         relative timing of this primitive
two paragraphs of 6.2.3.2           start both of these paragraphs      and the related act of
which use past tense to             with, "If the transmission          transmission.
describe the data unit              status is Successful," to clarify
transfer. MA-UNITDATA-              that these parameters may
STATUS.indication is a local        not make sense in the
indication that the MAC has         unsuccessful cases.
accepted the request, or not
(and why not), and is not
synchronized to the actual
frame/unit data delivery. The
past tense implies a
synchronization that has been
a confusion for many readers.


What "integer" is this              Change "an integer" to "a           AGREE (MAC: 2010-01-19       EDITOR
referencing?                        requested priority"                 06:16:48Z)
This paragraph still has          Change the paragraph to,         AGREE (GEN: 2010-01-20   EDITOR
problems, as noted by the         "The various entities within     06:36:16Z)
Editor.                           this model interact in various
                                  ways. Certain of these
                                  interactions are defined
                                  explicitly within this standard,
                                  via a SAP across which
                                  defined primitives are
                                  exchanged. This definition
                                  includes the GET and SET
                                  operations between MLME,
                                  PLME and SME as well as
                                  other individually defined
                                  service primitives,
                                  represented as double arrows
                                  within Figure 10-1. Other
                                  interactions are not defined
                                  explicitly within this standard,
                                  such as the interfaces
                                  between the MAC and MLME
                                  and between the PLME and
                                  PLCP and PMD;the specific
                                  manner in which these MAC
                                  and PHY LMEs are integrated
                                  into the overall MAC sublayer
                                  and PHY is not specified
                                  within this standard."

The STA does not "use" a          Change, "… uses a lower          AGREE (MAC: 2010-01-19   EDITOR
lower priority AC when it         priority AC for this purpose,    06:17:47Z)
downgrades traffic, rather is     the lower priority AC affects
uses the usual AC, but uses       only …" to "… uses the EDCA
the EDCA parameters of a          parameters of a lower AC for
lower AC, for that                this purpose, it affects only …"
transmission.
The MLME-EAPOL.confirm            Delete clause 10.3.20.2, and   AGREE IN PRINCIPLE (GEN: EDITOR
primitive does not seem           reference to the MLME-         2010-01-20 06:43:04Z) -
useful. Since there is no         EAPOL.confirm on page 272,     Accept in principle. Michael
guarantee that the EAPOL-         line 48.                       MIC failure notifications are
Key frame was completely                                         transmitted in EAPOL-Key
delivered to the remote peer,                                    frames. Timing of
this primitive cannot serve any                                  countermeasures is relative to
real security purpose. I don't                                   the transmission of the
think any such guarantee is                                      EAPOL-Key frame, and
ever needed, though, as all                                      therefore, this primitive is
critical such transmissions are                                  required. Change third line of
included within a handshake                                      five line rectangular box in
procedure.                                                       Figure 8-12 from "Wait for
                                                                 send report frame to
                                                                 complete" to "Wait for MLME-
                                                                 EAPOL.confirm". Also
                                                                 change "MLME-
                                                                 MICHEALMICFAILURE.indicat
                                                                 ion" on page 272 line 44 to
                                                                 "MLME-
                                                                 MICHAELMICFAILURE.indicat
                                                                 ion"
Extra blank line in error.       Edit out blank line between       AGREE (EDITOR: 2010-01-       EDITOR
                                 "set to" and "Pairwise".          27 16:08:48Z)
There are possibly more than     Change bullet item to:            DISAGREE (SECURITY:           EDITOR
1 PMKID, one for every           "PMKIDs, as defined in            2010-03-18 20:41:13Z) - The
available BSSID on the           8.5.1.2 (Pairwise key             group could not reach
authenticator.                   hierarchy). Each PMKID            consensus on any changes
                                 identifies the security           that would address this
                                 association via a BSSID to the    comment.
                                 authenticator."




authentication is between a    remove the authenticator            DISAGREE (SECURITY:           EDITOR
(supplicant) STA and the AS    MAC address from the                2010-03-18 20:41:28Z) - The
associated with the other      PMKSA.                              group could not reach
STA's authenticator, even                                          consensus on any changes
when an external AS (e.g. a                                        that would address this
RADIUS server) is not used.                                        comment.
The AS is an entity outside of
802.11 and has no knowledge
of a MAC address. A key
derived by an AS and shared
by an AS and a STA cannot,
therefore, be bound to an
identity that was not part of
the authentication and key
establishment process. There
is NO cryptographic binding
between the PMK and any
address the authenticator may
have.

the STA has to calculate the     Make the first sentence: "If a    DISAGREE (SECURITY:           EDITOR
PMKID based on the BSSID         STA in an ESS has                 2010-03-18 20:41:37Z) - The
of the AP to which it is about   determined it has a valid         group could not reach
to (re)associate.                PMKSA with an AP to which it      consensus on any changes
                                 is about to (re)associate-- for   that would address this
                                 example, through the Key          comment.
                                 Scope bit of a Neighbor
                                 Report (section 7.3.2.37)-- it
                                 calculates a PMKID using the
                                 BSSID of the AP to which it is
                                 about to (re)associate as the
                                 AA according to 8.5.1.2, it
                                 then includes the PMKID for
                                 the PMKSA in the RSN
                                 element in the
                                 (Re)Association Request."
there can be more than one    Make the period a comma        DISAGREE (SECURITY:           EDITOR
AA.                           and add: "and AA is a BSSID    2010-03-18 20:41:46Z) - The
                              through which communication    group could not reach
                              with the authenticator is      consensus on any changes
                              accomplished. Note: more       that would address this
                              than one PMKID can identify    comment.
                              the same PMKSA."

The term WDS is absolutely     Delete the term WDS and all   DISAGREE (GEN: 2010-01-        EDITOR
useless. The definition of the of its occurences.            21 00:50:58Z) On first
term WDS explains that is                                    investigation of this comment,
doesn't explain anything:                                    we found that figure 8-38 uses
"3.196 wireless distribution                                 "WDS" in a normative
system (WDS): A mechanism                                    manner. The removal of
for wireless communication                                   WDS would not work in this
using a four address frame                                   instance. A submission
format specified in this                                     descriping the specific
standard. This standard                                      changes would be required to
describes such a frame                                       make the suggested change.
format, but does not describe
how such a mechanism or
frame format would be used."
So why give it a name then?
The following definition
provides the same amount of
information and is as useless
as the WDS definition for
802.11 implementors:
"Coffee: A brewed drink
heavily relied on by standards
developer. 802.11 members
drink this beverage but this
standard does not describe
how to brew it."

All other occurences of WDS
are either in the list of
abbreviations, Figure 8-38, or
in Annex C, which is marked
as obsolete.
The following sentence in this Remove the sentence.          DISAGREE (GEN: 2010-01-        EDITOR
note adds confusion, leading                                 20 07:38:32Z) Reject. The text
a reader to possibly believe                                 is clear, note is helpful in
that CCA-ED level is at -72                                  understanding the rational
dBm for all clause 17 devices.                               behind the text
 The sentence is: "Support for
CCA-ED is an additional
requirement that relates
specifically to the sensitivities
described in I.2.4 (CCA-ED
threshold)."
The following sentence              Delete entire sentence.         DISAGREE (GEN: 2010-01-          EDITOR
contains a SHALL                                                    20 07:37:35Z) Reject.
requirement which is not                                            dot11CurrentFrequency is a
needed, as this relates to                                          control variable, written by the
device configuration                                                SME. This sentence forces
attributes. The sentence is:                                        the PHY to use it.
"The OFDM PHY shall use
dot11CurrentFrequency to
determine the operating
frequency."
The change from CCMP to             Revert the changes from         AGREE IN PRINCIPLE            EDITOR
“enhanced data cryptographic        “CCMP” to “enhanced data        (SECURITY: 2010-03-12
encapsulation mechanisms”           cryptographic encapsulation     16:19:56Z)
(which includes TKIP) here          mechanisms” in 6.1.2, i.e.,     Accept the comment and
does not look reasonable            only describe the security      make the proposed changes
taken into account the flaws        services to be provided by      to clause 6.1.2.
identified in TKIP and the          CCMP. In addition, reconsider
statement in this same              introduction of the “enhanced
subclause indicating that           data cryptographic
“TKIP algorithm is unsuitable       encapsulation mechanism”
for the purposes of this            throughout the draft.
standard”. I do not think it is a
good idea to claim that TKIP
would provide data
confidentiality or
authentication and would
prefer these services to be
described only for the ciphers
that are currently believed to
be secure. In addition,
including TKIP as an
“enhanced data cryptographic
encapsulation mechanism” is
questionable with the current
knowledge of weaknesses in
its construction.


“WEP” is not a valid cipher         Replace “TKIP or WEP with       AGREE (SECURITY: 2010-03- EDITOR
suite (“WEP-40” and “WEP-           TKIP” with “TKIP, WEP-104,      17 19:26:12Z)
104” would be).                     or WEP-40 with TKIP”.
                                    Similarly, replace “TKIP or
                                    WEP” with “TKIP, WEP-104,
                                    or WEP-40” on line 61.
As an answer to the editor's     Replace “Key” with “Wrapped        AGREE IN PRINCIPLE (MAC: EDITOR
note on line 30: “yes”. To be    Key” in the rightmost field in     2010-01-19 06:19:11Z).
consistent with Figure 7-95o7,   Figure 7-95o6a (i.e., do not       Replace "Key" with "Wrapped
the “Key” field in Figure 7-     change “Key Length”. On line       Key" in the rightmost field in
95o6a should indeed be           59, replace “The Key field is      Figure 7-95o6a (i.e., do not
renamed to “Wrapped Key”.        the IGTK being distributed”        change "Key Length". On line
                                 with “The Wrapper Key field        59, replace "The Key field is
                                 contains the wrapped IGTK          the IGTK being distributed"
                                 being distributed”. On lines 59-   with "The Wrapped Key field
                                 60, replace “Key field” with       contains the wrapped IGTK
                                 “Wrapper Key field”.               being distributed". On lines 59-
                                                                    60, replace "Key field" with
                                                                    "Wrapped Key field".

                                                                    [Note to editor: this is the
                                                                    same as the commenter's
                                                                    proposed resolution, but
                                                                    changes "wrapper key" to
                                                                    "wrapped key."

Table 8-2 style change seems Add a new row to the end of            AGREE (SECURITY: 2010-01- EDITOR
to have overriden the change Table 8-2 with the following           19 01:22:30Z)
from IEEE Std 802.11w-2009 contents: BIP | 16 | 128.
that described the key length
used with BIP.

The leftover “SetProtection”     Remove “SetProtection” text        AGREE (EDITOR: 2010-01-        EDITOR
text outside the                 outside the PTKINITDONE            27 16:07:22Z)
PTKINITDONE box should not box in Figure 8-37.
be there. The spelling of this
primitive was fixed in IEEE
Std 802.11w-2009, but it looks
like the old, incorrect spelling
somehow ended up remaining
on the side..
Why would unsuccessful             Remove the transition from      AGREE IN PRINCIPLE (GEN: EDITOR
association move the state         State 4 to State 2 with         2010-03-17 21:51:11Z) Apply
from State 4 to State 2? This      condition “Unsuccessful         the changes in doc 11-
seems to break any possible        Association”. On page 638       10/390r0.
protection we introduce            line 19 in 11.3.2.0a, replace
against DoS attacks (e.g., the     “Unsuccessful association
protections added in FT) since     when not in State 1 sets the
the association would be           STA's state to State 2” with
dropped in case of such an         “Unsuccessful association
attack (e.g., fake association     does not change STA's state”.
request sent to the AP).           On page 638 line 22, replace
Furthermore, this type of state    “Unsuccessful reassociation
change is not defined for          when not in State 1 sets the
State 3. Is there a difference     STA's state to State 2” with
on failed (re)association          “Unsuccessful reassociation
behavior between the States        does not change STA's state”.
3 and 4?




The text describing                Replace “Unsuccessful           AGREE IN PRINCIPLE (GEN: EDITOR
unsuccessful authentication is     authentication sets the STA's   2010-03-12 13:27:33Z)Accept
in conflict with the transitions   state to State 1” with          in principle. Replace the
shown in Figure 11-6. The text     “Unsuccessful authentication    second paragraph in
claims a failure to result in      does not change STA's state”.   11.3.1.0a with "Successful
transition to State 1 while the                                    authentication sets the STA's
figure claims there is no                                          state to State 2. Unsuccessful
transition in such a case. I                                       authentication leaves the
believe the behavior in the                                        STA's state unchanged. The
figure is correct since it is                                      STA shall not transmit Class 3
needed to maintain DoS                                             frames unless in State 3 or
protection provided for FT.                                        State 4. Authentication
                                                                   notification when in State 3 or
                                                                   4 implies disassociation as
                                                                   well."
The introduction of the new      Replace “State 3 if RSNA           AGREE (GEN: 2010-03-16   EDITOR
State 4 did not seem to take     establishment is required”         21:40:17Z)
into account FT protocol for     with “State 3 if RSNA
reassociation cases. When        establishment is required and
FT is used, 4-way handshake      FT Protocol is not used”.
does not follow the              Similarly, on page 641 line 49
reassociation. Instead, the      in 11.3.2.4, replace “State 3 if
STA should end up in State 4     RSNA establishment is
at the successful completion     required on the new AP” with
of reassociation.                “State 3 if RSNA
                                 establishment is required on
                                 the new AP and FT Protocol is
                                 not used”.
Regulatory class definition      Extend the regulatory class        AGREE IN PRINCIPLE (MAC: EDITOR
and use in IEEE 802.11 is        definitions or provide an          2010-03-05 16:53:53Z).
limited to not cover all         alternative mechanism to           Accept the changes in
countries where IEEE 802.11 allow regulatory specific rules         document 11-10/0210r6.
can be used due to Annex J       and channel specification to
only defining regulatory         be used in all countries where
classes for US, EU, and JP.      IEEE 802.11 can be used.
                                 This comment is not explicitly
This comment relates to CID requesting Annex J to be
781 in LB 147 (802.11s/D3.0) extended to cover all
that was rejected with the       regulatory rules, i.e., some
claim that it would be out of    generic mechanism for
scope for TGs to resolve and describing channels
TGmb was suggested as the (regulatory class,channel
place for resolving the issue. number pairs) outside the
While I may not fully agree      US/EU/JP areas (that are
with the part of making          defined in Annex J) could also
P802.11s work in all countries resolve the comment.
being out of scope for TGs, I
do agree that this is a more
generic issue and review in
TGmb would be useful. I also
realize that this WG
recirculation LB may not be
procedurally the best time to
submit this comment and will
understand if this gets ruled
out of order (and will resubmit
the same comment in the
initial sponsor ballot). Anyway,
I consider this to be an
important issue that needs a
resolution as soon as possible.
The resolution adopted to CID      Move the definition of            AGREE IN PRINCIPLE            EDITOR
1597, merging Annex Q into         dot11Groups 27 through 29 to      (EDITOR: 2010-01-29
Annex D, didn't addres the         follow dot11Groups 26             15:39:20Z)
issue raised by the comment -      (moving page 1555 line 13         As specified, except move all
namely that the dot11Groups        through page 1556 line 35 to      dot11Compliances to come
are not contiguous in the MIB      page 1527 line 30). Move the      after all dot11Groups.
definition. The same problem       definition of dot11groups 52 to   This results in dot11Groups
also exists for the dot11smt       the end of Annex D (moving        52 coming before the first
definitions.                       page 1527 line 29 through         compliance statement, not
                                   page 1527 line 44 to page         at the end of the MIB as
                                   1556 line 35). Also the same      indicated in the resolution.
                                   treatment for dot11smt. Move
                                   the definitions of dot11smt 9
                                   through dot11smt 12 to follow
                                   dot11smt 8 (moving page
                                   1538 line 58 through page
                                   1554 line 55 to page 1384 line
                                   10), and move the definition of
                                   dot11smt14 to follow
                                   dot11smt 13 (moving page
                                   1445 line 41 through page
                                   1520 line 10 to page 1385 line
                                   21).

The resolution approved for        Follow the guidance given by      AGREE (GEN: 2010-03-15      EDITOR
CID 1005 is incomplete, as it      ARC (as documented in             23:23:26Z) see specific
also needs to be applied           09/533r1) to add MIB text         details of changes in 11-
when TGn is incorporated into      regarding the variables added     10/300r1
REVmb                              by TGn




Regarding rejected CID 1241: Delete Annex C                          UNRESOLVABLE (GEN:          EDITOR
The proponents of Annex C,                                           2010-01-20 07:55:40Z)
claiming there is behavior                                           Comment withdrawn by
defined in Annex C that does                                         commenter in January 2010
not appear elsewhere in the                                          session Tuesday PM2.
standard, have had nearly a
full year to identify such gaps.
Time is up.

The resolution to CID 1517 is      Change first sentence to "DLS AGREE (EDITOR: 2010-01-         EDITOR
certainly correct, that "In an     is a protocol that enables a   20 13:11:33Z)
infrastructure network, non-       STA in an infrastructure
AP STAs are not allowed to         network to transmit frames
transmit frames directly to        directly to another STA in the
other non-AP STAs, except          same infrastructure network."
when using DLS." However,          Delete the Editor's Note, as
the sentence it replaced           this sentence does not need
provided the antecedent for        modification when TGz is
"this protocol" in the following   incorporated.
sentence. The resulting text
is unclear.
CID 1558 only changes some      remove remaining                   AGREE (GEN: 2010-01-20    EDITOR
of the occurrances of "and is   occurrances of "and is             07:56:49Z)
accessed big-endian"            accessed big-endian" in
                                Annex D (ten places)




Several hanging paragraphs      Fixing hanging paragraph in        AGREE IN PRINCIPLE        EDITOR
have appeared since this        5.2, 5.2.7, 5.2.8, 5.3, 5.4,       (EDITOR: 2010-01-26
problem was addressed prior     5.4.2, 5.4.3, 5.4.4, 5.8, 5.8.2,   15:18:55Z)
to D1.0                         5.8.3, 6.1.1, 6.2, 7.1.3.1,        As indicated by the
                                7.1.3.3, 7.1.3.4, 7.1.3.5,         commenter, plus the
                                7.3.2.21, 7.3.2.22, 7.3.2.25,      following in D 2.01:
                                7.4.1, 7.4.2, 7.4.3, 7.4.4,        20.1.3
                                7.4.6, 7.4.9, 8.3.4, 8.4.1.1,      20.3.9.5
                                11.1.1, 11.9a.3, 11.10,            20.3.11
                                11.10.9, 11.10.12, 11A.9.2,        20.3.11.8
                                11A.9.3, 11A.9.4, 11A.9.5,         20.3.11.10
                                17.1.2, and everywhere else        20.3.12
                                they appear as part of             20.3.12.2
                                incorporating TGn.                 20.3.13
                                                                   20.3.15
                                                                   20.3.22.5
"for a reason unrelated to      delete "any" from this phrase      AGREE (EDITOR: 2010-01-   EDITOR
every any reason code"                                             28 16:18:17Z)
Several MIB variables are        For each of these MIB            DISAGREE (GEN: 2010-01-         EDITOR
identified as written by an      variables, change all            21 21:56:51Z) While
external management entity,      occurrences in the text from     accepting that there are
but changes only take effect     dot11<NAME> to                   multiple improvements and
on a MLME-START or MLME-         dot11Current<NAME>. Insert       clarifications that may be
JOIN. This leads to confusion    a new table in the MIB,          made in the MIB, the amount
at the external management       dot11CurrentBSSParameters,       of effort is signficant and the
entity upon reading one of       using the next dot11smt          benefit is limited. On balance,
these variables and not          value, containing all of these   we prefer to make no change.
knowing whether the value        dot11Current<NAME>
read has taken effect yet or     variables. All are MAX-
not. For reasons of backward     ACCESS read-only.
compatibility, the confusion     Description for all of these
must be retained. But a          contain "This is a status
method can be included that      variable. It is written by the
unambiguously tells the          MAC when an MLME-
external management entity       START.request or MLME-
what is currently happening.     JOIN.request is received. This
In D2.0 this affects the         is a copy of the MIB variable
following MIB variables:         dot11<NAME> that is copied
dot11StationID,                  at the time of the MLME-
dot11BeaconPeriod,               START.request or MLME-
dot11DTIMPeriod,                 JOIN.request."
dot11MultiDomainCapabiityAct
ivated, dot11CountryString,
dot11SpectrumManagementR
equired,
dot11RegulatoryClassesRequi
red,
dot11RadioMeasurementActiv
ated,
dot11RMLinkMeasurementActi
vated, telling what
This line                        change this line to Editor's     AGREE (EDITOR: 2010-01-      EDITOR
happened to Annex Q should       Note                             20 14:54:12Z)
be an Editor's Note, rather
than text to keep in the final
document
Status of PBCC in D2.0 is        Change "deprecated" to    AGREE (GEN: 2010-01-20                     EDITOR
inconsistent. With HR/DSSS "obsolete" at page 977 line 34 07:40:42Z)
(Clause 18) it is noted as       and at page 1098 line 18.
obsolete (page 922 line 35),
but with ERP (Clause 19) it is
marked deprecated (page 977
line 34). In the PICS (Annex
A) PC17 says obsolete (page
1032 line 13) and ERP2 is
deprecated (page 1098 line
18). It is further noted (page
978 line 48) that ERP-PBCC
is an extension to DSSS-
PBCC. The comments that
led to this new text (#1053,
#1178, #1187 for HR/DSSS,
and #1180, #1189 for ERP)
make no claim that the PBCC
option doesn't work, nor that it
doesn't meet the design
goals, nor that using PBCC is
harmful in any way. Therefore,
the proper change is to
consistently mark it "obsolete".


normative reference is made      change reference in 11.1.3.0a AGREE (GEN: 2010-01-20                 EDITOR
here to IEEE Std 802-1990,       to IEEE Std 802-2001. Same 06:47:21Z)
but that version doesn't         change in 7.1.3.3.2 on page
appear in Clause 2.              78 line 54.


Almost everywhere, IEEE Std      change IEEE Std 802.11-            AGREE IN PRINCIPLE                EDITOR
802.11 is given either without   2007 to IEEE Std 802.11-           (EDITOR: 2010-01-29
a year, or as 802.11-<year>      <year> with the appropriate        14:16:07Z)
(with instructions to change     Editor's Note following it.        Replace 2007 by "<year>"
<year> to the year of                                               and move the following
publication). One was missed                                        editorial note (occurs later in
                                                                    Annex A) to just after the A.1
                                                                    heading: "<year> will be
                                                                    replaced with the year of
                                                                    publication during publication
                                                                    of this standard by the IEEE-
                                                                    SA editorial staff."

                                                                    (Same resolution as to CID
                                                                    2032)

It looks as though the page      Although I like it. I think most   DISAGREE (EDITOR: 2010- EDITOR
numbering has been done as       readers would prefer the           01-20 14:58:31Z) - The draft
alphabetical. (I just had to     pages of the document to be        sent to ballot had correct page
enter this comment)              numbered. :-)                      numbering.
                                                                    (Note to commenter:
                                                                    Comments should not be
                                                                    based on the redline draft.)
Calling the frames "Protected   Replace "Protected Dual of        UNRESOLVABLE (MAC:           EDITOR
Dual of Public Action" frames   Public Action" with "Protected    2010-01-19 07:03:14Z) -
is unnecessary.                 Public Action" and add the        Comment withdrawn by
                                follow sentence after the first   commenter during Monday
                                sentence of the first             EVE in January 2010 meeting.
                                paragraph of section 7.4.9a.1.
                                "Protected Dual of Public
                                Action frames are used
                                between STA's when
                                Management Frame
                                Protection has been enabled,
                                and after a security
                                association has been
                                established between them."
Figure 11-10 should be          Remove Figure 11-10               DISAGREE (GEN: 2010-01-         EDITOR
replaced by Figure 11-11.                                         20 06:48:31Z) -
                                                                  No change required. The
                                                                  figure is correct in the non-
                                                                  redline version of the draft.



The second sentence of the      Replace the paragraph with        AGREE IN PRINCIPLE (GEN: EDITOR
paragraph does not provide      the following text:               2010-03-12 05:50:43Z) A
any useful information to the   "The STA shall indicate that      consistency to the cited
reader.                         reason code from Table 7-28       sentence was made. CID
                                (Reason codes) of                 2197 has the specific
                                7.3.1.7(Reason Code field)."      changes listed in this clause
                                                                  and several others.
The second sentence of the        Replace the paragraph with           AGREE IN PRINCIPLE (GEN: EDITOR
paragraph does not provide        the following text:                  2010-03-12 15:13:22Z) The
any useful information to the     "The STA shall indicate that         specific text change is noted
reader.                           reason code from Table 7-28          in CID 2197. Also for
                                  (Reason codes) of                    consistency, other places
                                  7.3.1.7(Reason Code field)."         where this text was reiterated
                                                                       was fixed as well.




Items a, b, c and d are           Use the same phrasing for all        AGREE (EDITOR: 2010-01-     EDITOR
inconsistently worded.            4 (e.g. start all of them with “If   27 15:57:28Z)
                                  an RSNA is ...”)
“Hence ...” incorrectly claims    Revise d)3) to be more               AGREE IN PRINCIPLE            EDITOR
that the two authentications      consistent with c)3).                (SECURITY: 2010-01-11
are happening in parallel.                                             22:32:41Z)
While they may happen in                                               Replace "Hence two such key
parallel, they may also be                                             management algorithms are
serialized. Item c)3) correctly                                        happening in parallel between
states that they may happen                                            any two STA’s Supplicants
simultaneously.                                                        and Authenticators." with
                                                                       "Note that two peer STAs may
                                                                       follow
                                                                       this procedure
                                                                       simultaneously."

Items a)6) and b)5) are           Use the same phrasing for            AGREE IN PRINCIPLE           EDITOR
inconsistently worded.            both.                                (EDITOR: 2010-01-27
                                                                       15:59:11Z)
                                                                       Replace first sentence of a6
                                                                       with the contents of b5.
Items a)7) and b)6) are           Use the same phrasing for            AGREE IN PRINCIPLE           EDITOR
inconsistently worded.            both.                                (EDITOR: 2010-01-27
                                                                       16:02:17Z)
                                                                       Replace b6 with contents of
                                                                       a7.
The “STA programs the ...” is     Change to “the STA's SME             AGREE (SECURITY: 2010-01- EDITOR
vague and inconsistent with       programs the ...”                    11 22:31:38Z) - Accept.
the beginning of the
procedure.
“, bits 0 to 3 of the Priority    Change to “, the Priority            AGREE (SECURITY: 2010-01- EDITOR
field” should have been           subfield”                            12 20:04:57Z)
update to reflect the change
of Prority field to Priority
subfield.
Which TK? PTK? GTK? STK? Specify which TK.                   DISAGREE (SECURITY:             EDITOR
                                                             2010-01-29 16:37:17Z)
                                                             The use of TK (temporal key)
                                                             appears to be correct. See
                                                             8.5.1.2 and 8.5.1.4
“may be concatenated” or      Change “may” to “are”, or      AGREE IN PRINCIPLE              EDITOR
may be what?                  provide information on other   (SECURITY: 2010-01-12
                              possible actions.              20:15:09Z)