Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

Download - IEEE

VIEWS: 18 PAGES: 903

									                IEEE P802.11 Wireless LANs
                Submission
Designator:     doc.: IEEE 802.11-11/0558r0
Venue Date:     April 2011
First Author:   Guido Hiertz (Philips)

Subject:        SB3 G-general and G-base comments
Full Date:
Author(s):




Abstract:       Proposed resolution for comments identified by label ""grh
ments identified by label ""grh-2011-04-18" in cloumn Y.
                 Must   Categor Subclaus Pag Lin                  Issue
CID    Name                                               Topic
                 Be     y         e       e      e                ID




       Hunter,          Technic                           Gene G-
3034             Yes              11C.1   204        21
       David            al                                ral     Base




       Hunter,          Technic                           Gene G-
3035             Yes                  11.9 197        2
       David            al                                ral     Base
       Hunter,         Technic                     Gene G-
3036             Yes               11.9 197    1
       David           al                          ral    Base




       Hunter,         Technic                     Gene G-
3037             Yes               11.8 196   59
       David           al                          ral    Base




       Hunter,         Technic                     Gene G-
3038             Yes               11.7 196   48
       David           al                          ral    Base




                                                          G-
       Hunter,                                     Gene
3066             Yes   Editorial     3   4    22          Gener
       David                                       ral
                                                          al
                                                              G-
       Hunter,          Technic                        Gene
3068              Yes                   3    4     8          Gener
       David            al                             ral
                                                              al




                                                              G-
       Hunter,          Technic                        Gene
3069              Yes                   3    4     2          Gener
       David            al                             ral
                                                              al




                                                              G-
       Hunter,          Technic                        Gene
3070              Yes                   3    4     2          Gener
       David            al                             ral
                                                              al



                                                              G-
       Bahr,            Technic 5.2.14.5.              Gene
3210              No                        14     7          Gener
       Michael          al        10                   ral
                                                              al




                                                              G-
       Sakoda,          Technic 10.3.10.1              Gene
3217              No                        145   22          Gener
       Kazuyuki         al        .2                   ral
                                                              al
       Sakoda,                                        Gene G-
3237              No   Editorial 5.2.14.4   11    6
       Kazuyuki                                       ral   Base




       Sakoda,                                        Gene G-
3238              No   Editorial 5.2.14.4   10    6
       Kazuyuki                                       ral   Base




       Sakoda,                                        Gene G-
3239              No   Editorial 5.2.3.1    7    41
       Kazuyuki                                       ral   Base
                                                                                 Resolutio
Comment                                   Proposed Change
                                                                                 n Status




Why does a mesh STA not support
TDLS? At least the OOB functionality      Mention why a mesh STA is not
                                                                                 Disagree
of TDLS would seem to be very useful      allowed to support TDLS.
to some MBSSs.




Unfortunately adding this clause splits
the "in which the Spectrum                For MBSSs add a separate dashed-
Management bit is 1" from its original    item to the list, and make no
object, "BSS". In addition, do the        changes to this (legacy) requirement Principle
frames received in the BSS influence      for BSSs. In this new item state the
the status of the MBSS? The current       requirement just for the MBSS case.
wording states that.
Joining is a synchronization process,
while the meaning here is association,    Do not make this change on line 1.       Principle
not synchronization.




Subclause 11.8.4 (10.5.8 in 11mb)
does not talk about any TPC               Either add a specification of TPC
constraints, only about TPC               negotiation in for an MBSS (if that is
negotiations. What is a "TPC                                                       Principle
                                          different from negotiations for a
constraint", anyway? Where is that        BSS), or delete this addition.
term defined? If any text is added here
for MBSSs, it needs to specify how
                                          Replace "where frames are sent
Need to be clear that this addition is    directly from one STA to another"
                                          with "because frames in an MBSS          Principle
only about MBSSs, not BSSs.
                                          are always sent directly from one
                                          MBSS STA to another."




Since mesh STAs have such different
                                          Replace "STA" with "MSTA" when
functionalities, why not call them                                                 Disagree
                                          the term applies only to mesh STAs.
"MSTAs"?
                                         Either change this defnition to be a
"per peering" indicates that a mesh
                                         single number per mesh STA, or in
STA that has many peerings will have
                                         the main body of text rewrite the
many such power modes. However,
                                         instances of this term that indicate a
this term is not used that way in the
                                         single power mode per mesh STA.           Disagree
text. Note, for instance, 3.15, 3.27,
                                         For uses such as 3.15 and 3.27 a
19.59 and 22.54, which seem to
                                         new term indicating the 'overall
indicate that there is only one mesh
                                         mesh STA power level' may need to
power mode in the mesh STA.
                                         be invented.




There is no definiton of "active mesh
peering protocol". How is this different Define "active mesh peering
from just "mesh peering protocol"?       protocol" sufficiently to distinguish it Disagree
What is the inactive mesh peering        from other mesh peering protocols.
protocol like?




Why can't a definition of "peering" be   Replace this defintion with one that
given that does not involve the word     does not use the term "peer". Even
"peer"? Something is wrong if the        if the details are specific to a set      Disagree
concept is so opaque that it cannot be   procedure, the concept still needs to
defined.                                 be definable without recourse to that
                                         procedure.
                                         add at the end of second paragraph
Hint to the definition of proxy          the following (line 7): "The details of
functionality would be good.             the proxy functionality are described Agree
                                         in 11C.10.3 (Data forwarding at
                                         proxy mesh gates)."
Consider adding more argument for
MLME-START.request primitive,
although it may not be required. There
are more information elements for        As in comment.                            Disagree
mesh beacons, but only Mesh ID and
Mesh Configuration are added in the
MLME-START.request primitive.
Figure 5-6c should look something
more similar to Figure 5-2 in the base    As in comment.                         Disagree
standard.




Figure 5-6b should look something
                                          Submission 11-11/423 was not
more similar to Figure 5-7 in the base
                                          implemented as it breaks the
standard. Also, TGs may want to
                                          context in the base standard. Please
amend some part in clause 5.3.2 (DSS)                                            Principle
                                          revisit how to amend 5.3 in the base
and Figure 5-7 in the base standard, as
                                          standard. and provide an alternative
there is no mentioning of mesh BSS in
                                          resolution.
the clause and the figure.




"An MBSS is not further unified, and
therefore the ESS concept does not        Make the sentence more reader
                                                                                 Principle
apply to the MBSS." It is not clear what friendly.
is meant by this paragraph.
                                      Submissio Updated    Respons Accept_    #Mot Edit
Resolution Detail
                                      n        (to editor) eStatus   RejectDa ion   Status
DLS and TDLS are remedies for a
problem that exists in an
infrastructure BSS but not in a
mesh BSS (MBSS). In an
infrastructure BSS, STAs benefit
from communicating directly with
each other since the indirection
via the AP can be saved. In an                 grh-2011-
                                                           Open
MBSS there is no AP. Thus, a                   04-18
mesh STA communicates directly
with all other mesh STAs in range.
Only when mesh STA are not in
mutual range they use multi-hop
communication to communicate.
In such scenario, however, neither
DLS nor TDLS would be of any
help. Thus, both cannot be
Replace the first paragraph on
page 197 with
"- A STA shall set
dot11SpectrumManagementRequi
red to true before associating with
a BSS in which the Spectrum
Management bit is 1 in the
Capability Information field in
Beacon frames and Probe                        grh-2011-
                                                           Open
Response frames received from                  04-18
the BSS.
- A mesh STA shall set
dot11SpectrumManagementRequi
red to true before becoming a
member of an MBSS in which the
Spectrum Management bit is 1 in
the Capability Information field in
Beacon frames and Probe
Response frames received from
Replace the first paragraph on
page 197 with
"- A STA shall set
dot11SpectrumManagementRequi
red to true before associating with
a BSS in which the Spectrum
Management bit is 1 in the
Capability Information field in
Beacon frames and Probe               grh-2011-
                                                  Open
Response frames received from         04-18
the BSS.
- A mesh STA shall set
dot11SpectrumManagementRequi
red to true before becoming a
member of an MBSS in which the
Spectrum Management bit is 1 in
the Capability Information field in
Beacon frames and Probe
Response frames received from


Delete the sentence on line 59 on     grh-2011-
                                                  Open
page 196.                             04-18



Replace "where frames are sent
directly from one STA to another"     grh-2011-
with "because frames in an MBSS                   Open
                                      04-18
are always sent directly from one
mesh STA to another."
IEEE 802.11e introduces the QoS
STA. Throughout the 802.11e
standard, QoS STA is abbreviated
as QSTA. IEEE 802.11-2007
integrates 802.11e. However, all
occurences of the term QSTA
                                      grh-2011-
have been removed from IEEE                       Open
                                      04-18
802.11-2007. 802.11s follows the
same rational. This was
intensively discussed within TGs.
The TG decided to use the term
"mesh STA" following the
principles in 802.11-2007. The TG
802.11s defines the "mesh power
mode" as follows "Represents the
activity level of a mesh station
(STA) per peering. Three mesh
power modes are defined: active,
light sleep, and deep sleep mode."
                                      grh-2011-
                                                  Open
Thus, a mesh power mode is            04-18
always link specific. A mesh STA
may be in active mode with mesh
STA X while being in deep sleep
mode with another mesh STA Y at
the same time. This concept
allows independent transitioning
802.11s provides several open
frameworks for different functions.
Mesh peering in 802.11s is an
open framework. 7.3.2.98.7
describes the Mesh Peering
Protocol Identifier. The latter       grh-2011-
                                                  Open
identifies which mesh peering         04-18
protocol is currently in use in the
MBSS. Thus, the term "active
mesh peering protocol" refers to
the "mesh peering protocol" that is
currently in use because a mesh
The term "mesh peering"
describes a logical relationship
                                      grh-2011-
between two mesh STAs. There is                   Open
                                      04-18
no circular usage of the term
peering in this definition.


                                      grh-2011-
                                                  Open
                                      04-18




After extensive checks we could
not find any other values that        grh-2011-
                                                  Open
would be needed witht eh START        04-18
primitive.
It is unclear what should look
more familiar. Is the font, the font
size, or the line size? The figure is
black and white, uses boxes and
the element of a cloud. Text is         grh-2011-
                                                    Open
contained at the same places as         04-18
in figure 5-2. Does the commenter
miss the indication of the DSM?
Here, the DSM is not present
since the logical components of a
Figure 5-6b shows several
aspects that can occur with
802.11s.
1st) An MBSS may have multiple
gates.
2nd) The gates connect to similar
or dissimilar DSs.
3rd) Through the DS, an MBSS
access a portal.
4th) An MBSS may be used to
interconnect different                  grh-2011-
infrastructure BSSs.                                Open
                                        04-18
5th) An MBSS contains mesh
STAs only.
6th) An MBSS connects to an
infrastructure BSS through the
DS, therefore needing a gate.
7th) The gate connects to the DS
only, it does not integrate with non-
802.11 networks
8th) The role of the 802.11 portal
is independent of 802.11s.

Replace the sentence "An MBSS
is not further unified, and therefore
the ESS concept does not apply
to the MBSS." with "Instead an          grh-2011-
                                                    Open
MBSS forms a single set of              04-18
independent mesh STAs. This set
is undivided and cannot be further
unified. Therefore, the ESS
concept does not apply to the
             Edited
Edit Notes
             in Draft
Issue IDs are used to identify groups of CIDs that are related to the sa
General                                      total      closed   open assignee        resolved
 G-Base    Unification with base standard.       13          2     11   Guido               13
 G-Def     Terminology                            0          0      0                        0
 G-Arch    Architecture, definition, etc.         0          0      0                        0
 G-Discovery                                     22          0     22   Kaz                 22
                                                 etc)
 G-Editor Editorial fixes (wording, typo fixing, 23         23      0   Kaz                 23
 G-Frame General Frame Format                     7          0      7   Kaz                  7
 G-General                                        6          0      6   Guido                6
           Emergency services
 G-Emergency                                      1          1      0   Kaz                  1
 G-Prim    MLME primitive                         0          0      0                        0
 G-PH      Placeholder                            0          0      0                        0
 G-MIB                                            2          1      1   Kaz                  1
 G-PICS                                           0          0      0                        0
                                                 74         27     47                       73
MAC
 M-BS        Beaconing and Synchronization       43          0     43   Kaz                 43
 M-CC        Congestion Control                   0          0      0                        0
 M-CS        Channel Selection                    0          0      0                        0
 M-General                                        1          1      0   Kaz/Jarkko           1
 M-MCCA      MCCA                                38         32      6   Dee/Guido/Michael   32
 M-PM        Power Management                    14          0     14   Jarkko              14
 M-QoS       QoS related issues                   0          0      0                        0
 M-11n       11n compatibility                    0          0      0                        0
                                                 96         33     63                       90
RFI
 R-LM      Link Metric                            2          0      2   Michael              0
 R-FWD     Forwarding                             1          1      0   Michael              1
 R-General                                        0          0      0   Michael              0
 R-HWMP                                          11          8      3   Michael              8
 R-MeshGate                                       3          0      3   Michael              0
 R-Proxy                                          5          2      3   Michael              2
                                                 22         11     11                       11
Security
 S-General                                        5          0      5   Dan                  4
 S-Edit    Editorial                              2          0      2   Dan                  2
 S-GroupKey                                       2          0      2   Dan                  2
 S-MPM     Mesh Peering Management               41          0     41   Dan/Guenael         39
 S-SAE     SAE                                    4          0      4   Dan                  4
                                                 54          0     54                       51
Overall Statistics
         Overall Summary   Total     Open     Closed    % Closed   Edited
         Total Comments:       246      175        71   28.86%          71
         General                 4        1         3   75.00%
         Editorial              78       54        24   30.77%
         Technical             164      120        44   26.83%
         Total Comments:       246      175        71   28.86%
         General                74       47        27   36.49%
         MAC                    96       63        33   34.38%
         RFI                    22       11        11   50.00%
         Security               54       54         0   0.00%
elated to the same issue
       remaining
             0
             0
             0
             0
             0
             0
             0
             0
             0
             0
             1
             0
             1


             0
             0
             0
             0
             6
             0
             0
             0
             6


             2
             0
             0
             3
             3
             3
            11


             1
             0
             0
             2
             0
             3
Overall statistics
                                                        SB0     SB1   SB2   SB3
                  Total Comments:                       307     367   291   246
                  General                                15       2     5     4
                  Editorial                             118     184   142    78
                  Technical                             174     181   144   164
                  Total Comments:                       307     367   291   246
                  General                               134      46    87    74
                  MAC                                    60     236   118    96
                  RFI                                    75      54    25    22
                  Security                               38      31    61    54

Comment categorization
     General                                            SB0     SB1   SB2   SB3
        G-Base Unification with base standard.              3     1     7    13
        G-Def    Terminology                              14      0     0     0
        G-Arch                                              0     0     8     0
        G-Discovery                                         1     1     0    22
                                                          61
        G-Editor Editorial fixes (wording, typo fixing, etc)     31    45    23
        G-Frame General Frame Format                      16      7     4     7
        G-General                                           4     1     1     6
                 Emergency services
        G-Emergency                                         6     4     4     1
        G-PH     Placeholder                              29      0     0     0
        G-Prim MLME primitive                               0     0    18     0
        G-MIB                                               0     1     0     2
        G-PICS                                              0     0     0     0
        Total                                            134     46    87    74
        MAC
        M-BS    Beaconing and Synchronization              5    166    70    43
        M-CC    Congestion Control                         4      2     0     0
        M-CS    Channel Selection                          3      0     0     0
        M-General                                          1      1     1     1
        M-MCCA MCCA                                       35     40    43    38
        M-PM    Power Management                           6     27     4    14
        M-QoS QoS related issues                           6      0     0     0
        M-11n   11n compatibility                          0      0     0     0
        Total                                             60    236   118    96
        RFI
        R-LM    Link Metric                                4      4     2     2
        R-FWD Forwarding                                  32     28     3     1
        R-General                                          0      0     1     0
        R-HWMP                                            10      6    12    11
       R-MeshGate                                    22          5         2          3
       R-Proxy                                        7         11         5          5
       Total                                         75         54        25         22
       Security
       S-General                                      6          3         4          5
       S-Edit   Editorial                             1          0        30          2
       S-GroupKey                                     0          0         0          2
       S-MPM Mesh Peering Management                 11          2         9         41
       S-SAE    SAE                                  20         26        18          4
       Total                                         38         31        61         54

No votes per commenter
                                                   SB0        SB1       SB2        SB3
              Strutt, Guenael                        0          0         0          0
              Bahr, Michael                         84         95        40         33
              Benveniste, Mathilde                   1          0         0          0
              Denteneer, Theodorus                   0          0         0          0
              Hiertz, Guido                          0          0         0          0
              Housley, Russell                       0          0         1          0
              Mccann, Stephen                        2          0         0          0
              Methley, Steven                        0          0         0          0
              Montemurro, Michael                    1          0         0          0
              Odman, Knut                            6          0         0          0
              Rosdahl, Jon                           5          0         0          0
              Sakoda, Kazuyuki                       0          0         0          0
              Seibert, Cristina                      0          0         0          0
              shi, yang                              0          0         0          0
              Turner, Michelle                       1          0         0          0
              Zuniga, Juan                           0          0         0          0
              Chaplin, Clint                         0          0         0          0
              Struik, Rene                           0         25         0          0
              Malinen, Jouni                         0          0         0          0
              Hunter, David                          0          0       133         66
              Total                                100        120       174         99
              Total                                100        120       174         99

Previous sponsor ballot comments:
       SB0:   https://mentor.ieee.org/802.11/dcn/10/11-10-1283-14-000s-p802-11s-sponsor-ballot-comments.xls
       SB1:   https://mentor.ieee.org/802.11/dcn/11/11-11-0027-10-000s-p802-11s-sponsor-ballot-1st-recirc-commen
       SB2:   https://mentor.ieee.org/802.11/dcn/11/11-11-0287-08-000s-p802-11s-sponsor-ballot-2nd-recirc-commen
11s-sponsor-ballot-comments.xls
11s-sponsor-ballot-1st-recirc-comments.xls
11s-sponsor-ballot-2nd-recirc-comments.xls
Resolution Status
        Agree          We accept the comment and the way the commenter proposes to resolve it. No additional tec
        Principle      We accept the comment, but propose an alternative way of resolving it. The resolution must b
        Disagree       We disagree with the comment, and don’t propose making any changes. The resolution must
        Scope          The comment is out of scope, e.g. relates to material in a recirculation that has not changed, a
        Unresolvable   The comment cannot be resolved. E.g., it requires action, but not affecting the draft; or the CR
Edit Status
        I              Implemented
        IR             Implemented as specified, but editor has made notes on issues that should be considered by t
        M              Implemented with editorial modifications that the editor believes are obvious and don’t require
        MR             Implemented with modifications that the editor believes require further discussion in the CRC,
        R              Not implemented. The editor cannot implement the resolution as specified by the CRC, either
er proposes to resolve it. No additional technical input is required from the CRC to permit any editor to implement the resolution.
e way of resolving it. The resolution must be specified in sufficient detail that any editor could implement it.
 making any changes. The resolution must indicate why, and must be responsive to all the points raised by the commenter.
al in a recirculation that has not changed, and is not affected by changed portions of the draft and does not relate to unsatisfied comments fr
action, but not affecting the draft; or the CRC agrees with the comment, but nobody knows how to propose an implementable resolution.



es on issues that should be considered by the CRC
 tor believes are obvious and don’t require further discussion
 ves require further discussion in the CRC, i.e. the editor has exercised technical discretion.
  resolution as specified by the CRC, either because it is badly written, or it directly conflicts other resolutions in a way that requires too much
y editor to implement the resolution.

oints raised by the commenter.
 and does not relate to unsatisfied comments from a previous ballot.
how to propose an implementable resolution.




ther resolutions in a way that requires too much technical creativity to resolve.
Revisision     Date                     Notes / Summary of Changes
                          Compilation of comments gathered through the sponsor ballot
                          3rd recirculation.
             2011-04-11   Preliminary Topic Category and Issue Identifier are put in
    r0                    column R and column S of "SB3_comments" sheet.
                          Some suggested resolutions to comments are included. Some
             2011-04-11
    r1                    issue identifiers are changed.
                          Tentative assignments to comments are included in
             2011-04-11   "SB3_statistic" tab. Some suggested resolutions to G-
    r2                    Discovery comments and G-Frame comments are included.
                          Additional suggested resolutions to G-Discovery comments
             2011-04-13
    r3                    and M-BS comments are included.
                          Results from the TGs call on April 14 are included. Additional
             2011-04-15   suggested resolutions on AID fields are also included. This
    r4                    comment spreadsheet is aligned with D10.02.
                 Must   Categor Subclaus Pag Lin       Issue
CID    Name                                      Topic
                 Be     y       e        e   e         ID

       Hunter,                                      Gene G-
2001             Yes    Editorial        226   47
       David                                        ral  Editor


       Hunter,                                      Gene G-
2002             Yes    Editorial        225    1
       David                                        ral  Editor




       Hunter,                                      Secu
2003             Yes    Editorial        220   59          S-Edit
       David                                        rity




       Hunter,                                      Gene G-
2004             Yes    Editorial        220   55
       David                                        ral  Editor




                                                       S-
     Hunter,                                      Secu
2005             Yes    Editorial        220   49      Gener
     David                                        rity
                                                       al




       Hunter,                                      Secu
2006             Yes    Editorial        219   42        S-Edit
       David                                        rity



       Hunter,                                      Gene G-
2007             Yes    Editorial        220   24
       David                                        ral  Editor


       Hunter,                                      Secu
2008             Yes    Editorial        220   14        S-Edit
       David                                        rity



       Hunter,                                      Gene G-
2009             Yes    Editorial        220   12
       David                                        ral  Editor
       Hunter,                                Gene G-
2010             Yes   Editorial   219   65
       David                                  ral  Editor


       Hunter,                                Secu
2011             Yes   Editorial   219   58        S-Edit
       David                                  rity




       Hunter,                                Secu
2012             Yes   Editorial   219   54        S-Edit
       David                                  rity




       Hunter,                                Secu
2013             Yes   Editorial   219   52        S-Edit
       David                                  rity




       Hunter,                                Secu
2014             Yes   Editorial   219   49        S-Edit
       David                                  rity




       Hunter,                                Gene G-
2015             Yes   Editorial   219   36
       David                                  ral  Editor




       Hunter,                                Secu
2016             Yes   Editorial   219   34        S-Edit
       David                                  rity
       Hunter,                                Secu
2017             Yes   Editorial   219   24        S-Edit
       David                                  rity




       Hunter,                                Secu
2018             Yes   Editorial   219   21        S-Edit
       David                                  rity




       Hunter,                                Secu
2019             Yes   Editorial   219   18        S-Edit
       David                                  rity




       Hunter,                                Secu
2020             Yes   Editorial   219   16        S-Edit
       David                                  rity




       Hunter,                                Secu
2021             Yes   Editorial   219   13        S-Edit
       David                                  rity




       Hunter,                                Secu
2022             Yes   Editorial   219   12        S-Edit
       David                                  rity




       Hunter,                                Secu
2023             Yes   Editorial   219   11        S-Edit
       David                                  rity
       Hunter,                                Secu
2024             Yes   Editorial   219    8        S-Edit
       David                                  rity




       Hunter,                                Secu
2025             Yes   Editorial   219    6        S-Edit
       David                                  rity




       Hunter,                                Secu
2026             Yes   Editorial   219    1        S-Edit
       David                                  rity




       Hunter,                                Secu
2027             Yes   Editorial   218   63        S-Edit
       David                                  rity




       Hunter,                                Secu
2028             Yes   Editorial   218   61        S-Edit
       David                                  rity




       Hunter,                                Secu
2029             Yes   Editorial   218   60        S-Edit
       David                                  rity




       Hunter,                                Gene G-
2030             Yes   Editorial   218   29
       David                                  ral  Editor




       Hunter,                                Secu
2031             Yes   Editorial   218   26        S-Edit
       David                                  rity
       Hunter,                                Gene G-
2032             Yes   Editorial   218   26
       David                                  ral    Editor



       Hunter,                                Secu S-
2033             Yes   Technical   217    9
       David                                  rity   MPM




       Hunter,                                Gene G-
2034             Yes   Editorial   217    1
       David                                  ral  Editor



       Hunter,                                Secu
2035             Yes   Technical   209   43        S-Edit
       David                                  rity



       Hunter,                                Secu
2036             Yes   Editorial   207   22        S-Edit
       David                                  rity




       Hunter,                                Secu
2037             Yes   Technical   207   18        S-Edit
       David                                  rity




       Hunter,                                Secu
2038             Yes   Editorial   207   18        S-Edit
       David                                  rity




       Hunter,                                Secu
2039             Yes   Technical   203   38        S-Edit
       David                                  rity
       Hunter,                                Secu
2040             Yes   Technical   203   35        S-Edit
       David                                  rity




       Hunter,                                Gene
2041             Yes   Editorial   176   39        G-Prim
       David                                  ral




       Hunter,                                Gene
2042             Yes   Editorial   176   39          G-Prim
       David                                  ral



       Hunter,                                Gene
2043             Yes   Editorial   176   39        G-Prim
       David                                  ral



       Hunter,                                Gene
2044             Yes   Editorial   176   39        G-Prim
       David                                  ral


       Hunter,                                Gene
2045             Yes   Editorial   176   39          G-Prim
       David                                  ral


       Hunter,                                Gene
2046             Yes   Editorial   174   14          G-Prim
       David                                  ral

       Hunter,                                       M-
2047             Yes   Technical   163   21 MAC
       David                                         MCCA

       Hunter,                                Gene
2048             Yes   Editorial   158   53        G-Prim
       David                                  ral



       Hunter,                                Gene
2049             Yes   Editorial   157   24        G-Prim
       David                                  ral




       Hunter,                                Gene
2050             Yes   Editorial   156    1        G-Prim
       David                                  ral
       Hunter,                                Gene
2051             Yes   Editorial   154   39        G-Prim
       David                                  ral


       Hunter,                                Gene
2052             Yes   Editorial   153    8        G-Prim
       David                                  ral

       Hunter,                                Gene
2053             Yes   Editorial   153    1        G-Prim
       David                                  ral


       Hunter,                                Gene
2054             Yes   Editorial   152   24        G-Prim
       David                                  ral

       Hunter,                                Gene
2055             Yes   Editorial   152   22        G-Prim
       David                                  ral

       Hunter,                                Gene
2056             Yes   Editorial   150   54        G-Prim
       David                                  ral




       Hunter,
2057             Yes   Technical   149   64 MAC M-PM
       David




       Hunter,                                Gene
2058             Yes   Editorial   149   58        G-Prim
       David                                  ral


       Hunter,                                Gene
2059             Yes   Editorial   149   50        G-Prim
       David                                  ral
       Hunter,                                Gene
2060             Yes   Editorial   149   50        G-Prim
       David                                  ral




       Hunter,                                Gene G-
2061             Yes   Editorial   143   36
     David                                  ral      Editor
     Hunter,                                Gene     G-
2062             Yes   Technical   143   35
     David                                  ral      Editor
     Hunter,                                Gene     G-
2063             Yes   Technical   143   32
     David                                  ral      Editor
     Hunter,                                Gene     G-
2064             Yes   Technical   143   27
     David                                  ral      Editor
       Hunter,                                Gene G-
2065             Yes   Technical   138   36
       David                                  ral  Editor

       Hunter,                                Gene G-
2066             Yes   Editorial   136   24
       David                                  ral  Editor

       Hunter,                                       M-
2067             Yes   Editorial   112   39 MAC
       David                                         MCCA

       Hunter,                                Secu
2068             Yes   Technical   105   56        S-Edit
       David                                  rity


       Hunter,                                Secu
2069             Yes   Technical    92   42          S-SAE
       David                                  rity




       Hunter,                                Secu
2070             Yes   Technical    90   46        S-SAE
       David                                  rity
       Hunter,                               Secu
2071             Yes   Technical   90   43        S-SAE
       David                                 rity




       Hunter,                               Secu
2072             Yes   Technical   90    9        S-SAE
       David                                 rity




       Hunter,                               Secu
2073             Yes   Technical   89   40          S-SAE
       David                                 rity


       Hunter,                               Secu
2074             Yes   Technical   87   40        S-SAE
       David                                 rity




       Hunter,                               Secu
2075             Yes   Technical   87   22        S-SAE
       David                                 rity




       Hunter,                               Secu
2076             Yes   Technical   87   13        S-SAE
       David                                 rity




       Hunter,                               Secu
2077             Yes   Technical   86   55        S-SAE
       David                                 rity




       Hunter,                               Secu
2078             Yes   Technical   86    8        S-SAE
       David                                 rity
       Hunter,                               Secu
2079             Yes   Technical   86    8        S-SAE
       David                                 rity




       Hunter,                               Secu
2080             Yes   Technical   85   45        S-SAE
       David                                 rity




       Hunter,                               Secu
2081             Yes   Technical   85   44        S-SAE
       David                                 rity



       Hunter,                                   R-
2082             Yes   Technical   65   28 RFI
       David                                     Proxy

       Hunter,                                   R-
2083             Yes   Technical   61   61 RFI
       David                                     HWMP
       Hunter,                                   M-
2084             Yes   Technical   55   48 MAC
       David                                     MCCA


       Hunter,                               Secu
2085             Yes   Technical   36   43        S-SAE
       David                                 rity




       Hunter,                               Secu
2086             Yes   Technical   36   28        S-SAE
       David                                 rity




       Hunter,                               Secu
2087             Yes   Technical   36   11        S-SAE
       David                                 rity
       Hunter,                               Secu
2088             Yes   Editorial   36   11        S-SAE
       David                                 rity




       Hunter,                               Secu
2089             Yes   Technical   35   49        S-SAE
       David                                 rity




       Hunter,                               Gene G-
2090             Yes   Editorial   34   23
       David                                 ral   Editor




       Hunter,                               Secu
2091             Yes   Technical   15   36        S-Edit
       David                                 rity




                                                G-
       Hunter,                             Gene
2092             Yes   Technical   13   16      Emerg
       David                               ral
                                                ency
                                                G-
       Hunter,                             Gene
2093             Yes   Technical   13   21      Emerg
       David                               ral
                                                ency
       Hunter,                                     R-
2094             Yes   Technical   12   64 RFI
       David                                       Proxy



       Hunter,                               Gene G-
2095             Yes   Editorial   12   60
       David                                 ral  Editor



       Hunter,                               Gene G-
2096             Yes   Technical   12   54
       David                                 ral  Editor
       Hunter,                               Gene G-
2097             Yes   Editorial   12    6
       David                                 ral  Editor



       Hunter,                               Gene G-
2098             Yes   Editorial   11   31
       David                                 ral  Editor
       Hunter,                               Gene G-
2099             Yes   Editorial   11   30
       David                                 ral  Editor




       Hunter,                               Gene G-
2100             Yes   Editorial   11   29
       David                                 ral  Editor




       Hunter,                               Gene G-
2101             Yes   Editorial   11   29
       David                                 ral   Editor
       Hunter,                               Gene G-
2102             Yes   Editorial   11   23
       David                                 ral   Editor

     Hunter,                               Gene    G-
2103             No    Editorial   11    8
     David                                 ral     Editor
     Hunter,                               Gene    G-
2104             Yes   Editorial   10   57
     David                                 ral     Editor
       Hunter,                               Gene G-
2105             Yes   Editorial   10   42
       David                                 ral  Editor

       Hunter,                               Gene G-
2106             Yes   Technical   10    2
       David                                 ral  Editor
       Hunter,                               Gene G-
2107             Yes   Editorial    8   65
       David                                 ral  Editor

       Hunter,                               Gene G-
2108             Yes   Editorial    8   59
       David                                 ral  Editor
       Hunter,                              Gene
2109             Yes   Technical   8   59        G-Arch
       David                                ral




       Hunter,                              Gene
2110             Yes   Technical   8   56        G-Arch
       David                                ral




       Hunter,                              Gene G-
2111             Yes   Editorial   8   56
       David                                ral  Editor


       Hunter,                              Gene G-
2112             Yes   Technical   8   49
       David                                ral  Base




       Hunter,                              Gene G-
2113             Yes   Editorial   8   38
       David                                ral   Base




       Hunter,                              Gene G-
2114             Yes   Editorial   8   36
       David                                ral  Base
       Hunter,                              Gene G-
2115             Yes   Editorial   8   30
       David                                ral  Editor

       Hunter,                              Gene G-
2116             Yes   Editorial   8   28
       David                                ral  Editor
       Hunter,                              Gene G-
2117             Yes   Editorial   8   23
       David                                ral  Editor


       Hunter,                              Gene
2118             Yes   Technical   8   16        G-Arch
       David                                ral


       Hunter,                              Gene G-
2119             Yes   Editorial   8   16
       David                                ral    Editor




       Hunter,                              Gene G-
2120             Yes   Technical   8   15
       David                                ral  Editor




       Hunter,                              Gene G-
2121             Yes   Technical   8    7
       David                                ral    Editor




       Hunter,                              Gene
2122             Yes   Technical   8    1          G-Arch
       David                                ral




       Hunter,                              Gene G-
2123             Yes   Editorial   8    1
       David                                ral  Editor
       Hunter,                              Gene G-
2124             Yes   Editorial   7   64
       David                                ral    Editor
       Hunter,                              Gene G-
2125             Yes   Editorial   7   39
       David                                ral  Editor




       Hunter,                              Gene
2126             Yes   Technical   7   33        G-Arch
       David                                ral




       Hunter,                              Gene
2127             Yes   Technical   7   30        G-Arch
       David                                ral
       Hunter,                              Gene
2128             Yes   Technical   7   16        G-Arch
       David                                ral




       Hunter,                              Gene G-
2129             No    Editorial   5   42
       David                                ral   Editor
       Hunter,                                  M-
2130             Yes   Technical   5   28 MAC
       David                                    MCCA




       Hunter,
2131             Yes   Editorial   5   15 MAC M-PM
       David




                                                R-
       Hunter,
2132             Yes   Editorial   5   1 RFI    Gener
       David
                                                al




       Hunter,                             Gene
2133             Yes   Technical   4   5        G-Arch
       David                               ral
                                                     R-
       Hunter,
2134             Yes   Technical       3   49 RFI    MeshG
       David
                                                     ate




       Hunter,                                  Gene G-
2135             Yes   Editorial       3   18
       David                                    ral  Editor




       Bahr,                                    Gene G-
2136             Yes   Technical   3   3    6
       Michael                                  ral  Base
       Bahr,
2137             Yes   Technical7.1.3.1.7   19   29 MAC M-PM
       Michael




       Bahr,
2138             Yes   Technical7.1.3.1.7   19   23 MAC M-PM
       Michael




     Bahr,                                          Gene   G-
2139             Yes   Technical7.1.3.6.3   23   37
     Michael                                        ral    Frame
     Bahr,                                          Gene   G-
2140             Yes   Technical7.3.2       37    9
     Michael                                        ral    Frame
       Bahr,                                           Gene G-
2141             No    Technical7.3.2        37   61
       Michael                                         ral  Editor




       Bahr,                                                M-
2142             Yes   Technical7.3.2        37   61 MAC
       Michael                                              MCCA

     Bahr,                                               M-
2143             Yes   Technical7.3.2        37   39 MAC
     Michael                                             MCCA
     Bahr,                                               M-
2144             Yes   Technical7.3.2        37   37 MAC
     Michael                                             MCCA

                                                          G-
     Bahr,                                           Gene
2145             No    Editorial 7.3.2.90    41   45      Emerg
     Michael                                         ral
                                                          ency




       Bahr,                                           Gene G-
2146             Yes   Technical7.3.2.98.7   45   47
       Michael                                         ral  Frame




       Bahr,
2147             Yes   Technical7.3.2.98.9   46   55 MAC M-BS
       Michael




       Bahr,
2148             Yes   Technical7.3.2.105    52   21 MAC M-BS
       Michael
       Bahr,                                              M-
2149             No   Editorial 7.3.2.108   54   64 MAC
       Michael                                            MCCA




       Bahr,                                              M-
2150             No   Editorial 7.3.2.108   54   40 MAC
       Michael                                            MCCA




       Bahr,                                              M-
2151             No   Editorial 7.3.2.108   54   40 MAC
       Michael                                            MCCA



     Bahr,                                              M-
2152             No   Editorial 7.3.2.108   55   36 MAC
     Michael                                            MCCA
     Bahr,                                              M-
2153             No   Editorial 7.3.2.108   55   26 MAC
     Michael                                            MCCA
     Bahr,                                              M-
2154             No   Editorial 7.3.2.108   55   10 MAC
     Michael                                            MCCA
       Bahr,                                              M-
2155             No   Technical7.3.2.109.2 56    64 MAC
       Michael                                            MCCA

       Bahr,                                              M-
2156             No   Technical7.3.2.109.2 56    60 MAC
       Michael                                            MCCA



       Bahr,                                              M-
2157             No   Editorial 7.3.2.109.1 56   32 MAC
       Michael                                            MCCA




       Bahr,                                              M-
2158             No   Editorial 7.3.2.109.1 56   23 MAC
       Michael                                            MCCA
       Bahr,                                                M-
2159             No    Editorial 7.3.2.109.1 56    16 MAC
       Michael                                              MCCA




       Bahr,                                                M-
2160             No    Editorial 7.3.2.109.3 57    28 MAC
       Michael                                              MCCA


       Bahr,                                                M-
2161             No    Technical7.3.2.109.3 57     25 MAC
       Michael                                              MCCA

       Bahr,                                                M-
2162             No    Technical7.3.2.109.2 57      1 MAC
       Michael                                              MCCA



                                                            R-
     Bahr,
2163             No    Editorial 7.3.2.113    60   47 RFI   MeshG
     Michael
                                                            ate



       Bahr,                                                R-
2164             No    Technical7.3.2.116     65   13 RFI
       Michael                                              Proxy



       Bahr,                                                M-
2165             No    Editorial 7.4.15       78    4 MAC
       Michael                                              MCCA



       Bahr,                                                M-
2166             No    Editorial 7.4.15.9     79   58 MAC
       Michael                                              MCCA
       Bahr,                                                M-
2167             No    Editorial 9.9a.3.2    113   43 MAC
       Michael                                              MCCA




       Bahr,                                                M-
2168             Yes   Technical9.9a.3.1     113   34 MAC
       Michael                                              MCCA
       Bahr,                                              M-
2169             No   Technical9.9a.3.1    113   39 MAC
       Michael                                            MCCA


       Bahr,                                              M-
2170             No   Editorial 9.9a.3.1   113   15 MAC
       Michael                                            MCCA



       Bahr,                                              M-
2171             No   Editorial 9.9a.3.3   114   16 MAC
       Michael                                            MCCA

       Bahr,                                              M-
2172             No   Editorial 9.9a.3.7.4b120   60 MAC
       Michael                                            MCCA
       Bahr,                                              M-
2173             No   Editorial 9.9a.3.7.4a120   40 MAC
       Michael                                            MCCA
       Bahr,                                              M-
2174             No   Editorial 9.9a.3.7.4 120   22 MAC
       Michael                                            MCCA

       Bahr,                                              M-
2175             No   Editorial 9.9a.3.7.4b121    5 MAC
       Michael                                            MCCA

       Bahr,                                              M-
2176             No   Editorial 9.9a.3.10 124    27 MAC
       Michael                                            MCCA

       Bahr,                                              R-
2177             No   Technical9.22.2      125   58 RFI
       Michael                                            FWD


       Bahr,                                              R-
2178             No   Technical9.22.2      126   16 RFI
       Michael                                            FWD


       Bahr,                                              R-
2179             No   Editorial 9.22.3     127   54 RFI
       Michael                                            FWD
       Bahr,                                              M-
2180             No   Technical10.3.81.1.2163    18 MAC
       Michael                                            MCCA

       Bahr,                                              M-
2181             No   Editorial 10.3.81.7.1168   52 MAC
     Michael                                            MCCA
     Bahr,                                              M-
2182             No   Editorial 10.3.81.8.2169   59 MAC
     Michael                                            MCCA
       Bahr,                                              M-
2183             No   Editorial 10.3.81.8.2169   53 MAC
       Michael                                            MCCA

     Bahr,                                              M-
2184             No   Editorial 10.3.81.7.3169   18 MAC
     Michael                                            MCCA
     Bahr,                                              M-
2185             No   Editorial 10.3.81.8.2169   41 MAC
     Michael                                            MCCA
       Bahr,                                                M-
2186             No                         1
                       Editorial 10.3.81.10.2 71   27 MAC
       Michael                                              MCCA

       Bahr,                                                M-
2187             No                         1
                       Editorial 10.3.81.10.2 71   15 MAC
       Michael                                              MCCA



       Bahr,
2188             Yes   Technical      11.1 190     34 MAC M-BS
       Michael




       Bahr,
2189             Yes   Technical11.1.3      190    35 MAC M-BS
       Michael




       Bahr,
2190             Yes   Technical      11.1 190     34 MAC M-BS
       Michael




       Bahr,
2191             No    Editorial 11.1.1.3   190    26 MAC M-BS
       Michael
       Bahr,
2192             No    Technical11.1.1.3   190   29 MAC M-BS
       Michael




       Bahr,                                          Gene G-
2193             No    Editorial 11C.9.7   237   62
       Michael                                        ral  Editor



       Bahr,                                               R-
2194             Yes   Technical11C.9.8.3 239    61 RFI
       Michael                                             HWMP

       Bahr,                                               R-
2195             Yes   Technical11C.9.9.3 242    49 RFI
       Michael                                             HWMP
       Bahr,                                               R-
2196             Yes   Technical11C.9.9.3 243    57 RFI
       Michael                                             HWMP

       Bahr,                                               R-
2197             Yes   Technical11C.9.9.3 246    15 RFI
       Michael                                             HWMP


       Bahr,                                               R-
2198             Yes   Technical11C.9.9.4.3251   19 RFI
       Michael                                             HWMP


       Bahr,                                               R-
2199             No    Technical11C.9.11.3 257   46 RFI
       Michael                                             HWMP

       Bahr,                                               R-
2200             No    Technical11C.9.11.3 259   52 RFI
       Michael                                             HWMP

       Bahr,                                               R-
2201             Yes                       260
                       Technical11C.9.11.4.3     44 RFI
       Michael                                             HWMP

       Bahr,                                               R-
2202             Yes                       260
                       Technical11C.9.11.4.3     38 RFI
       Michael                                             HWMP

       Bahr,                                               R-
2203             Yes                       260
                       Technical11C.9.11.4.3     33 RFI
       Michael                                             HWMP

       Bahr,                                               R-
2204             No    Technical11C.10.4.3 269   10 RFI
       Michael                                             Proxy
       Bahr,
2205             No                        273
                       Technical11C.12.2.2.1     40 MAC M-BS
       Michael




       Bahr,
2206             Yes                       273
                       Technical11C.12.2.2.1     37 MAC M-BS
       Michael




       Bahr,
2207             No                        273
                       Technical11C.12.2.2.2     54 MAC M-BS
       Michael




       Bahr,
2208             No    Technical11C.12.2.1 273   11 MAC M-BS
       Michael




       Bahr,
2209             No    Technical11C.12.2.2 273   22 MAC M-BS
       Michael
       Bahr,
2210             No                         273
                       Editorial 11C.12.2.2.2     65 MAC M-BS
       Michael




       Bahr,
2211             No                        273
                       Technical11C.12.2.2.1      32 MAC M-BS
       Michael




       Bahr,
2212             Yes                       274
                       Technical11C.12.2.2.3      24 MAC M-BS
       Michael
       Bahr,
2213             No                        274
                       Technical11C.12.2.2.2     1 MAC M-BS
       Michael




       Bahr,
2214             No                        274
                       Technical11C.12.2.2.3     63 MAC M-BS
       Michael




       Bahr,
2215             Yes                       274
                       Technical11C.12.2.2.3     56 MAC M-BS
       Michael




       Bahr,
2216             Yes                       274
                       Technical11C.12.2.2.3     57 MAC M-BS
       Michael




       Bahr,
2217             Yes                       274
                       Technical11C.12.2.2.3     37 MAC M-BS
       Michael




       Bahr,
2218             No                        274
                       Technical11C.12.2.2.3     24 MAC M-BS
       Michael
       Bahr,
2219             Yes                       274
                       Technical11C.12.2.2.3      35 MAC M-BS
       Michael




       Bahr,
2220             Yes                       274
                       Technical11C.12.2.2.3      56 MAC M-BS
       Michael




       Bahr,
2221             Yes                       274
                       Technical11C.12.2.2.3      46 MAC M-BS
       Michael




       Bahr,
2222             No                        274
                       Technical11C.12.2.2.3      30 MAC M-BS
       Michael




       Bahr,
2223             No                        274
                       Technical11C.12.2.2.2      17 MAC M-BS
       Michael




       Bahr,
2224             No                         274
                       Editorial 11C.12.2.2.2     6 MAC M-BS
       Michael
       Bahr,
2225             No   Technical11C.12.3.1 275    13 MAC M-BS
       Michael




       Bahr,
2226             No   Technical11C.12.3.2 275    30 MAC M-BS
       Michael




       Bahr,
2227             No   Editorial 11C.12.4.1 275   64 MAC M-BS
       Michael




       Bahr,
2228             No   Technical11C.12.4.1 275    62 MAC M-BS
       Michael
       Bahr,
2229             No    Editorial 11C.12.3.2 275   30 MAC M-BS
       Michael




       Bahr,
2230             No    General 11C.12.3.2 275     40 MAC M-BS
       Michael




       Bahr,
2231             No    Editorial 11C.12.3.2 275   34 MAC M-BS
       Michael




       Bahr,
2232             Yes                       276
                       Technical11C.12.4.2.3      65 MAC M-BS
       Michael




       Bahr,
2233             No                         276
                       Editorial 11C.12.4.2.3     63 MAC M-BS
       Michael
       Bahr,
2234             Yes                       276
                       Technical11C.12.4.2.2      54 MAC M-BS
       Michael




       Bahr,
2235             No                        276
                       Technical11C.12.4.2.2      52 MAC M-BS
       Michael




       Bahr,
2236             No                         276
                       Editorial 11C.12.4.2.2     40 MAC M-BS
       Michael




       Bahr,
2237             No                         276
                       Editorial 11C.12.4.2.2     34 MAC M-BS
       Michael




       Bahr,
2238             No                        276
                       Technical11C.12.4.2.1      11 MAC M-BS
       Michael




       Bahr,
2239             No                        276
                       Technical11C.12.4.2.1      8 MAC M-BS
       Michael
       Bahr,
2240             No                        276
                       Technical11C.12.4.2.1      7 MAC M-BS
       Michael




       Bahr,
2241             Yes   Technical11C.12.4.2 276    1 MAC M-BS
       Michael




       Bahr,
2242             No                         277
                       Editorial 11C.12.4.2.4     55 MAC M-BS
       Michael




       Bahr,
2243             No                         277
                       Editorial 11C.12.4.2.4     49 MAC M-BS
       Michael
       Bahr,
2244             No                        277
                      Editorial 11C.12.4.2.4     48 MAC M-BS
       Michael




       Bahr,
2245             No                        277
                      Editorial 11C.12.4.2.4     35 MAC M-BS
       Michael




       Bahr,
2246             No                        277
                      Editorial 11C.12.4.2.4     34 MAC M-BS
       Michael




       Bahr,
2247             No                        277
                      Editorial 11C.12.4.2.4     34 MAC M-BS
       Michael




       Bahr,
2248             No                        277
                      Editorial 11C.12.4.2.4     32 MAC M-BS
       Michael




       Bahr,
2249             No                        277
                      Editorial 11C.12.4.2.3     1 MAC M-BS
       Michael


       Bahr,
2250             No                       277
                      Technical11C.12.4.2.3      1 MAC M-BS
       Michael
       Bahr,
2251             No   Editorial 11C.12.4.3 278   64 MAC M-BS
       Michael




       Bahr,
2252             No   Technical11C.12.4.3 278    56 MAC M-BS
       Michael




       Bahr,
2253             No                       278
                      Technical11C.12.4.2.5      17 MAC M-BS
       Michael
       Bahr,
2254             Yes                       278
                       Technical11C.12.4.2.5      15 MAC M-BS
       Michael




       Bahr,
2255             No                         278
                       Editorial 11C.12.4.2.5     48 MAC M-BS
       Michael




       Bahr,
2256             No                        278
                       Technical11C.12.4.2.5      43 MAC M-BS
       Michael




       Bahr,
2257             No                         278
                       Editorial 11C.12.4.2.5     29 MAC M-BS
       Michael




       Bahr,
2258             No                         278
                       Editorial 11C.12.4.2.5     21 MAC M-BS
       Michael
       Bahr,
2259             No                         278
                       Editorial 11C.12.4.2.4     1 MAC M-BS
       Michael




       Bahr,
2260             Yes                       279
                       Technical11C.12.4.4.1      23 MAC M-BS
       Michael




       Bahr,
2261             No                        279
                       Technical11C.12.4.4.1      22 MAC M-BS
       Michael




       Bahr,
2262             Yes                       279
                       Technical11C.12.4.4.1      15 MAC M-BS
       Michael




       Bahr,
2263             No                         279
                       Editorial 11C.12.4.4.1     15 MAC M-BS
       Michael
       Bahr,
2264             Yes   Technical11C.12.4.3 279    2 MAC M-BS
       Michael




       Bahr,
2265             No                         279
                       Editorial 11C.12.4.4.3     53 MAC M-BS
       Michael




       Bahr,
2266             Yes                       279
                       Technical11C.12.4.4.3      62 MAC M-BS
       Michael
       Bahr,
2267             Yes                       279
                       Technical11C.12.4.4.3     58 MAC M-BS
       Michael




       Bahr,                                                 M-
2268             No    TechnicalD         313    10 MAC
       Michael                                               MCCA

       Bahr,                                                 R-
2269             No    TechnicalY.7       335    49 RFI
       Michael                                               HWMP




       Strutt,                                        Secu S-
2270             No    Technical11C.4.3   208    14
       Guenael                                        rity   MPM
       Strutt,                                      Secu S-
2271           No     Technical11C.4.2   206   44
       Guenael                                      rity MPM




       Strutt,                                      Secu S-
2272             No   General 11C.4.2    206   44
       Guenael                                      rity   MPM
       Strutt,                                      Secu S-
2273           No     Technical11C.3.2   203   59
       Guenael                                      rity MPM




       Strutt,                                      Secu S-
2274             No   General 11C.4.3.4 209    49
       Guenael                                      rity   MPM
       Strutt,                                     Secu S-
2275           No     General 11C.4.3.3 209   18
       Guenael                                     rity MPM




       Strutt,                                     Secu S-
2276             No   General 11C.4.3.2 208   44
       Guenael                                     rity   MPM
       Strutt,                                    Secu S-
2277           No    Technical11C.3   203     9
       Guenael                                    rity MPM




       Sakoda,
2278            No   Technical11C.8   231     1 RFI   R-LM
       Kazuyuki




                                                     G-
     Sakoda,                                    Gene
2279          No     Technical    11.3 191   52      Gener
     Kazuyuki                                   ral
                                                     al
       Sakoda,
2280            No   Technical10.3.85.2.2183    25 RFI   R-LM
       Kazuyuki




                                                       M-
       Sakoda,
2281            No   Technical9.9.1.2     112   32 MAC Gener
       Kazuyuki
                                                       al




       Sakoda,                                       Gene G-
2282            No   Technical7.4.15.1     75   13
       Kazuyuki                                      ral  Frame




       Sakoda,                                           R-
2283            No   Technical7.3.2.116    65   34 RFI
       Kazuyuki                                          Proxy
                                                           S-
     Sakoda,                                          Secu
2284          No       Technical7.2.3.10      32   59      Gener
     Kazuyuki                                         rity
                                                           al




       Sakoda,                                          Gene G-
2285            No     Technical5.2.3.1        7   21
       Kazuyuki                                         ral  Base




       Sakoda,                                          Gene G-
2286              No   Editorial 5.2.14.4     10    8
       Kazuyuki                                         ral   Base




       Sakoda,                                          Gene G-
2287            No     Editorial 5.2.14.4      9    8
       Kazuyuki                                         ral  Base




                                                           S-
     Malinen,                                         Secu
2288          No       Editorial 8.2a.7.2.4   93   51      Gener
     Jouni                                            rity
                                                           al




       Malinen,                                               M-
2289            No     Technical7.3.2         37   61 MAC
       Jouni                                                  MCCA
                                                        S-
     Housley,                                      Secu
2290          Yes   Technical11C.3.2.1                  Gener
     Russell                                       rity
                                                        al




                                                        G-
       Mccann,                                     Gene
2291           No   Technical11.23.6     197   6        Emerg
       Stephen                                     ral
                                                        ency
                                                                                 Resoluti
Comment                                 Proposed Change
                                                                                 on
Names of state machines do not need     Replace the figure name with "Table
to be in caps.                          11C-3--Finite state machine of the Agree
                                        authenticated mesh peering
                                        exchange protocol"
Names of state machines do not need     Replace the table name with "Table
to be in caps.                          11C-2--Authenticated mesh peering Agree
                                        exchange finite state machine"
English clean up.                       Replace "element" with "elements"
                                        after both "RSN" and "AMPE".
                                        Insert "the" before "Authenticated"
                                        and, since the following terms do
                                        not refer to the field names, on lines Principle
                                        61 through 64 replace
                                        "Authenticated Mesh Peering
                                        Exchange" with "authenticated
                                        mesh peering exchange".(twice)
The capitalized names do not refer to   and "Mesh Peering Management"
                                        Replace "Authenticated Mesh
frame, field, primitve, etc. names.     Peering Exchange" with
                                        "authenticated mesh peering
                                        exchange".and "Mesh Peering              Agree
                                        Management" with "mesh peering
                                        management" throughout the draft
                                        when the terms do not directly refer
In this heading "exchange" is not       Replace "Mesh Peering
                                        Management" with "mesh peering
                                        management".                             Principle



The indicator "the" for the peer STA    Replace "the peer" with "its peer".
brings up the question "which one?".
                                                                                 Agree



Need colon.                             Place a colon at the end of the line.
                                                                                 Agree

Passive.                                Replace "When verifying ..
                                        followed:" with:
                                        "When the mesh STA verifies a     Agree
                                        Mesh Peering Management frame, it
                                        shall follow the procedure:"

Need period.                            Place a period at the end of the line.
                                                                                 Agree
Need colon.                             Place a colon at the end of the line.
                                                                                Agree

Passive.                                Replace "When constructing ...
                                        followed:" with "When the mesh
                                        STA constructs a Mesh Peering           Agree
                                        Management frame, it shall follow
                                        the procedure:"

Requirements can't be stated in         Replace "NOTE--" with "Note that".
informative notes, and "required" and   Replace "is required to" with "shall".
"must" are both deprecated in IEEE      Replace "must" with "shall".           Agree
standards.


Need a pause after "FAIL".              Insert a comma after "FAIL".


                                                                                Agree



Subortinate clause needs a comma.       Insert a comma after
                                        "authenticating"
                                                                                Agree



In references to action frames, the     Replace "Action" with "action" on
word "Action" is not capitalized.       both lines 29 and 40.                   Disagree


"protection in the Mesh Peering Open Replace this complete paragraph
action frame' sounds like the protection with "A mesh STA shall announce in
is inside the frame.                     a Mesh Peering Open action frame
                                        the group cipher suite it uses for
                                        broadcast protection. When it
                                        receives a Mesh Peering Open
                                        frame from a candidate peer, it shall
                                        verify that it supports the
                                        candidate's announced group cipher Agree
                                        suite . In addition, if the mesh STA
                                        receives a Mesh Peering Confirm
                                        frame, it shall verify that it supports
                                        the group cipher suite listed in that
                                        frame. If either selection fails, the
                                        mesh STA shall issue the
                                        appropriate reply frame with the
                                        MESH-INVALID-SECURITY-
"selector of the selected"               "


                                                                                 Agree



"if generating" is not clear enough.     Insert "it is" before "generating".


                                                                                 Agree



Passive.                                 Insert "the mesh STA shall generate
                                         the" before "failure" and delete
                                         "shall be generated".                   Agree



Confusing writing                        Replace "the chosen pairwise cipher
                                         suites as the result of step b). If they
                                         do not match," with "the pariwise        Agree
                                         cipher suite chosen in step b). If
                                         there is no match,".

Passive.                                 Insert "the mesh STA shall generate
                                         the" before "failure" and delete
                                         "shall be generated".                   Agree



"chosen" needs to be closer to the       Move "chosen" from its current
name of the entity doing the choosing.   location to one immediately
                                         following "suite".                      Agree



Too many repetitions of "the mesh        Replace "the mesh STA supports"
STA" for clarity.                        with "it supports" (since it is clear
                                         that this reference is the              Agree
                                         decisionmaker mesh STA).
"STA with the largest" is vague.       Replace "with" with "that has" and
                                       replace "in the lexicographic
                                       ordering" with "(in lexicographic      Agree
                                       order)".


"not empty and contains more than one Delete "is not empty and".
entry" is redundant.
                                                                              Agree



Missing indicator and passive.         Replace "and" with ", the mesh STA
                                       generates the" before "failure" and
                                       replace "shall be generated and     Agree
                                       corresponding actions shall be
                                       taken according to" with " and then
                                       takes the corresponding actions
English clean up.                      Replace "shall independently make
                                       decision on" with "shall make its
                                       decision about" and "based on       Agree
                                       intersection" with "based on the
                                       intersection".

Missing indicator.                     Insert "the" before "last".


                                                                              Agree



Bulky writing.                         Replace "most preferred cipher
                                       suite by the mesh STA" with "mesh
                                       STA's most preferred cipher suite".    Agree



In references to action frames, the    Replace "Action" with "action" on
word "Action" is not capitalized.      both lines 29 and 40.                  Disagree


Misplaced apostrophe.                  Replace "STAs'" with "STA's" as this
                                       refers to a single STA. Alternatively,
                                       could replace just with "STA".         Agree
"Mesh" in "Mesh TKSA" does not need Replace "Mesh TKSA" with "mesh
to be capitalized.                  TKSA".                                     Agree

"via the active authenticaion protocol"   Delete "via the active authentication
is confusing at best.                     protocol" as that concept is
                                          incorporated in "initiation of the    Agree
                                          protocol".


In this heading "Authenticated Mesh       Replace "Authenticated Mesh
Peering Management" does not refer to Peering Exchange" with
a frame, field, primitive name,       "Authenticated mesh peering              Agree
parameter name, etc.                  exchange" throughout the draft,
                                          whenever this term does not apply
                                          directly to a frame, field, primitive
"NOTE--" is used only with informative    Replace "NOTE--" with "Note that".
statements, while "is required to" and    Replace "is required to" with "shall". Disagree
"must" indicate normative behavior.       Replace "must" with "shall".
Antecedent clause needs a comma.          Insert a comma after "STA".


                                                                               Agree



"must" is deprecated in IEEE              Replace "must be" with "is".
standards.
                                                                               Agree



Antecedent clause needs a comma.          Insert a comma after "AMPE".


                                                                               Agree



"must" is deprecated in IEEE              Replace "must" with "shall".
standards.
                                                                               Principle
"must" is deprecated in IEEE         Replace "must" with "shall".
standards.
                                                                      Agree



In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     MWMPMeshPathSelection" with
                                     "MLME-                            Agree
                                     MWMPMESHPATHSELECTION"
                                     throughout the draft.
In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     MeshLinkMetricReport" with "MLME-
                                     MESHLINKMETRICREPORT"             Agree
                                     throughout the draft.

In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     MeshLinkMetricRead" with "MLME- Agree
                                     MESHLINKMETRICREAD"
                                     throughout the draft.
In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     MBSSGateAnnouncement" with
                                     "MLME-                          Agree
                                     MBSSGATEANNOUNCEMENT"
                                     throughout the draft.
In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     MBSSProxyUpdate" with "MLME- Agree
                                     MBSSPROXYUPDATE" throughout
In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     MBSSCongestonControl" with   Agree
                                     "MLME-
                                     MBSSCONGESTIONCONTROL"
"must" is deprecated in IEEE         Replace "must be" with "is".
                                                                  Agree
standards.
In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     MeshTBTTAdjustment" with "MLME- Agree
                                     MESHTBTTADJUSTMENT"
                                     throughout the draft.
In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     NeighborOffsetSyncStop"" with
                                     "MLME-                          Agree
                                     NEIGHBOROFFSETSYNCSTOP"
                                     throughout the draft.
In the 802.11 naming style "MLME-"   Replace "MLME-
primitive names are in all-caps.     MeshNeighborOffsetMeasure" with
                                     "MLME-                          Agree
                                     MESHNEIGHBOROFFSETMEASU
                                     RE" throughout the draft.
In the 802.11 naming style "MLME-"       Replace "MLME-
primitive names are in all-caps.         NeighborOffsetSyncStart"" with
                                         "MLME-                                 Agree
                                         NEIGHBOROFFSETSYNCSTART"
                                         throughout the draft.
In the 802.11 naming style "MLME-"       Replace "MLME-
primitive names are in all-caps.         MeshPOWERMGT" with "MLME-    Agree
                                         MESHPOWERMGT" throughout the
The words in heading titles should not   Replace MeshPOWERMGT in the
be concatenated.                         heading with "Mesh power     Agree
                                         management"
Parameter name style does not match      Replace "peerMAC" with
others.                                  "PeerMAC" both here and in the         Principle
                                         table below.

Incorrect primitive type.                Replace ".confirm" with ".response".
                                                                                Agree

Parameter name style does not match      Replace "peerMAC" with
others.                                  "PeerMAC" both here and in the         Principle
                                         table below.

The function subclause needs to say      What is sending that frame asking
what the function is that sending that   the other STA to do? Where is that
frame accomplishes.                      functionality specified?
                                                                                Principle




In the 802.11 naming style "MLME-"       Replace "MLME-
primitive names are in all-caps.         MeshPeeringManagement" with
                                         "MLME-                                 Agree
                                         MESHPEERINGMANAGEMENT"
                                         throughout the text.
The words in heading titles should not   Replace
                                                                                Agree
be concatenated.                         "MeshPeeringManagement" with
The words in heading titles should not   Replace
be concatenated.                         "MeshPeeringManagement:" with
                                         "Mesh peering management".




                                                                              Agree




Typo: Peerig                             Replace "Peerig" with "Peering" in
                                                                              Agree
                                         the MLME primitive name.
"must" is deprecated in IEEE             Replace "must be" with "is".
                                                                              Principle
standards.
"must" is deprecated in IEEE             Replace "must be" with "is".
                                                                              Principle
standards.
"must" is deprecated in IEEE             Replace "must be" with "is".
                                                                              Principle
standards.
"must" is deprecated in IEEE             Replace "must" with "shall".
standards.                                                                    Principle

The mesh is not in TU.                   Move "(in TU)" to the location
                                         immediately following "period" in    Agree
                                         this phrase.
The title of a major subclause,          Replace "MCF" with "Mesh
especially one defining a significant    coordination function (MCF)".        Agree
functionality, should be written out.
"must" is deprecated in IEEE             Replace "must" with "shall".
                                                                              Disagree
standards.
"must" is deprecated in IEEE             Replace "must then include" with
standards.                               "then includes".
                                                                              Principle



"can" is discouraged in IEEE            This is a statement of permission
standards. The same is true of lines 47 given by the standard. Replace
and 49.                                 "can" with "may".                     Agree
"can" is discouraged in IEEE             Replace "can be" with "are".
standards.
                                                                             Agree



"can" is discouraged in IEEE             Replace "can be" with "is".
standards.
                                                                             Agree



"can" is discouraged in IEEE             This is a statement of permission
standards.                               given by the standard. Replace      Disagree
                                         "can" with "may".

"can" is discouraged in IEEE             This is a statement of permission
standards.                               given by the standard. Replace      Disagree
                                         "can" with "may".

"can" is discouraged in IEEE             This is a statement of permission
standards.                               given by the standard. Replace
                                         "can" with "may".                   Agree



"can" is discouraged in IEEE             Replace "can" with "might".
standards.
                                                                             Agree



"must" is deprecated in IEEE             Replace "must be" with "is".
standards.
                                                                             Principle



The last two sentences of this           Delete both sentences.
paragraph do not appear to be testable
components of a MAC or PHY,                                                  Principle
"can" is discouraged in IEEE                 This is a statement of permission
standards.                                   given by the standard. Replace
                                             "can" with "may".                       Agree



"must" is deprecated in IEEE                 Replace "must" with "need to".
standards.
                                                                                     Agree



"can" is discouraged in IEEE                 This is a statement of permission
standards.                                   given by the standard. Replace
                                             "can" with "may".                       Agree



"can" is discouraged in IEEE                 This is a statement of permission
standards.                                   given by the standard. Replace          Principle
                                             "can" with "may".
"can" is discouraged in IEEE                 Replace "can be" with "is".
                                                                                     Agree
standards.
"can" is discouraged in IEEE                 Replace "can" with "might".
                                                                                     Agree
standards.
Contrary to the claim, the Finite Cyclic     Define the Finite Cyclic Group field.
Group field is not defined in this figure.
The figure just shows a box for it.                                                  Agree



Contrary to the claim, the Confirm field Define the Confirm field.
is not defined in this figure. The figure
just shows a box for it.                                                             Agree



Contrary to the claim, the Element field Define the Element field.
is not defined in this figure. The figure
just shows a box for it.                                                             Agree
Indicator missing.                      Insert "The" before "Element".


                                                                                Agree



Contrary to the claim, the Anti-clogging Define the Anti-clogging Token field.
Token field is not defined in this figure.
The figure just shows a box for it.                                            Agree



"case of" is unnecessary (and           Delete "case of".
incorrect) verbiage.
                                                                                Principle



"must" is deprecated in IEEE            Replace "must" with "shall".
standards.



                                                                                Agree




There is no "ES" defined in either      Define "ES" both in clause 3 and in
802.11mb or 802.11s.                    the main text.                          Principle

There is no "PSAP" defined in either    Delete "(such as a PSAP)".
802.11mb or 802.11s.                                                            Disagree

Is proxy functionality defined?         If it is defined, point to that location.
                                        Otherwise create a technical              Disagree
                                        definition of the proxy functionality.
Bulky language.                         Replace "that in case multiple mesh
                                        gates are present in the mesh BSS
                                        that have access to the same DS," Agree
                                        with "that, when multiple mesh
                                        gates that have access to the same
                                        DS are present in the mesh BSS,"
"can" is strongly discouraged in IEEE In these cases "can" seems to mean
standards because it might or might not "may". Replace "can": with "may"   Agree
mean "may".                             on lines 54 and 55.
In the 802.11 standard the names of   Replace "Hybrid Wireless Mesh
protocols, mechanisms and other terms Protocol" with "hybrid wireless mesh
that are not the names of frames,            protocol" and "Airtime Link Metric"     Agree
fields, etc. are not in initial caps.        with "airtime link metric" (of course
                                             with appropriate caps for the first
                                             word of a sentence or title)
"is..specified to" sounds like it doesn't.   Replace "is also specified to
                                                                                     Agree
                                             mitigate" with "mitigates".
"Neighbor Offset Synchronization" is         Replace "Neighbor Offset
not the name of a frame, field, primitive, Synchronization" with "neighbor           Agree
etc.                                       offset synchronization" througout
"can" is strongly discouraged in IEEE Replace "can" with "might".
standards because it might or might not
mean "may".


                                                                                     Principle




"periodically" needs to be closer to the Move "periodically" to the location
                                                                             Agree
agent.                                       immediately following "STAs".
"authenticated mesh peering                  Replace "Mesh Peering Exchange"
exchange" is not the name of a frame,        with "mesh peering exchange".   Agree
field, etc.
Missing comma.                               Insert a comma after "and".
                                                                                     Agree

Need a period after "BSS".                   Insert period after "BSS".
                                                                                     Agree

Initial caps are not used for protocols,     Replace "Peering Management""
etc.                                         with "peering management".              Agree

"can" is discouraged in IEEE                 Replace "can" with "might".
                                                                                     Principle
standards.
This is true even if the DS conatins a       Replace "a portatl that is explained
portal that is not explained in that         in" with "a portal. See"                Agree
subclause.
"For example," is unneccessary.              Delete "For example," and change
                                                                                     Agree
                                             "the" to "The".
A mesh gate is only a "logical point"?    Replace this term with somethng
IT might be a point of contact, but       that more accurately describes the
"logical" seems inappropriate.            function.




                                                                                     Disagree




What does it mean that a "Mesh BSS        If so, say so. If not, say why not.
may access the DS". Do mesh STAs
exchange Data and management
frames with non-mesh STAs? In this                                                   Principle
context being able to forward data
through a bridge does not constitute
"accessing" the DS.
"distribution system" is not in initial   Replace "Distribution System" with
caps in IEEE 802.11.                      "distribution system" throughout the Agree
                                          draft.
Is TDLS incorporated or not?              Need to include that in this list, if it is
                                          not supported, otherwise in the list
                                          above.                                      Principle



Very bulky writing.                       Perhaps replace the two sentences
                                          (until the colon) with "A mesh BSS
                                          does not incorporate the full hybrid
                                          coordinator (HC) and BSS QoS          Agree
                                          functionality. MBSSs do not
                                          incorporate:" and replace the traffic
                                          specification line with "Traffic
The a list at the end of the sentence     specificatons (TSPECs).
                                          Insert a period after "(optional)".
                                                                                Agree
completes the sentence.
"The Subset is as follows:" is            Delete that sentence and replace
redundant.                                the period at the end of the previous Agree
                                          sentence with a colon.
Missing quotes indicating the term.       Insert double quotes around "mesh
                                                                                Agree
                                          station".
"the QoS BSS" brings up the question      Delete "the" from "the QoS BSS".
                                                                               Agree
of "which one is that?"
The first clause of this sentence         Rewrite this sentence for accuracy --
indicates that the only transmission      perhaps "STAs in a mesh BSS may
options of a mesh STA are source or       be sources, sinks or propagators of Agree
sink. The second clause denies that       traffic; some may only propagate
indication.                               traffic for other STAs."
The join of two independent clauses       Insert a comma after "traffic".
                                                                                Agree
requires a comma.
"can" is discouraged in IEEE              On line 15 replace both "can" and
standards. Also, the clause 5 general     "may" with "might". On line 18
description shouldn't include normative   replace "may" with "might" and
statements.                               delete "can".



                                                                               Agree




"can" is strongly discouraged in IEEE     Replace can with "are able to" and
standards because it might or might not   on line replace "can benefit" with   Principle
mean "may".                               "benefits".
Quantities of mechanisms are not the      Replace "The quantity of certain
correct subject. For example, how         mesh-specific" with "The mesh-
many (quantity) of the EDCA               spcific".
mechanism are implemented in an
MBSS? This and many other
sentences in this draft need to be
rewritten into precise English, or may                                         Principle
lead to ambiguities.




Missing quotes indicating the term. Insert double quotes around "the
                                                                       Agree
                                    mesh facility".
Number mismatch: STAs that have not Replace "For mesh STAs that have
become *a* member.                  not" with "For a mesh STA that has Agree
                                    not"
Passive text is discouraged.            Insert "For infrastructure BSS and
                                        IBSS" ath the beginning of the
                                        sentence, and do not delete "This
                                        standard provides" (but replace           Agree
                                        "The" with "the") and do not insert
                                        "are specified for the infrastructure
                                        BSS and IBSS".
This statement indicates that any QoS   If this is not true, rewrite this text.
STA, notably including mesh STAs,
may associate with a non-QoS AP. Are
mesh STAs allowed to associate with
non-QoS APs?




                                                                                  Principle




Use of the word "between" here          If true, explain why no broadcast or
indicates that transactions among     multicast is supported in MBSSs. If Agree
mesh STAs are only peer-to-peer, that false, then replace "between" with
is, no broadcast or multicast is        "among".
As it is rewritten, this paragraph now      If true, then explain why there is no
indicates that only an infrastructure       association in an MBSS. If not true,
BSS incorporates association -- and         then rewrite to indicate that both
that an MBSS does not.                      infrastructure BSSs and MBSSs
                                            require association.




                                                                                    Principle




Words that are not capitalized for other Replace the definitions in this
reasons (such as names of frames,           section with the appropriate
fields, etc.) are not capitalized in IEEE   definition that follows:
acronym appreviations. In addition,         "authenticated mesh peering
acronyms in the defintions need             exchange"
themselves to be defined.                   "gate announcement"
                                            "hybrid wireless mesh protocol"
                                            "MCCA access fraction"
                                            "mesh Beacon collision avoidance"
                                            "mesh coordination function (MCF)
                                            coordinated channel access"
                                            "mesh coordination function (MCF)       Agree
                                            coordinated channel access
                                            opportunity"
                                            "mesh peering management"
                                            "path error"
                                            "path reply"
                                            "path request"
                                            "proxy update"
                                            "proxy update confirm"
                                            "root announcement"
                                            "resource allocation vector"
                                            "receiver service period initiated"
What is the definition of "reduced     Need to oinclude that in this list.
contention access method".                                                   Principle


Bulky language.                        Replace "where" with "during which"
                                       and "in awake state afte its Beacon
                                       or Probe Response frame               Agree
                                       transmission that" with "in the
                                       awake state after its transmission of
                                       a Becon or Probe Response frame
Bulky language.                        Replace "as the link to" with
                                       "because the link in"




                                                                             Principle




This definition defines "peering" in   Defiine "peering". If it means
terms of "peering". What is a peering? "establish a wireless peer-to-peer
What does it do functionally?          link", define it as such.




                                                                             Disagree
What is the difference between a mesh Unless there are some technical
gate and a mesh portal. The "mesh     differences between a gate and a
gate"s shown in the figure on page 9     portal, replace "mesh gate" with
seem to have the same functionality as ":mesh portal" throughout this draft.
a portal that contains a mesh STA.     If there are technical differences, list
                                       at least some of them in this
                                       definition.




                                                                                  Disagree




As a noun "Beacon" refers only to a      Replace "beacon" with "Beacon"
Beacon frame. So it must be written in through out the text when it refers to
initial cap.                           the Beacon frame. Note that termas Agree
                                       containing "beacon", such as
                                       "beaconing" and "beacon period"
                                       are not in intial caps.
since the term WDS is obsolete it      remove of all occurences of WDS in
should be removed from the base        802.11-2007 (or whatever the
standard.                              baseline document is), especially in
                                       the UML descriptions. Only the text Principle
                                       in 3 Definitions might be kept.
The current text is valid for any data     Add restriction, that this is only the
transmission. However, it has to be        rule when peer mesh STAs use
restricted to the cases where this         power save. Restrict to buffered
makes sense (PS).                          packets, because the more MSDUs
                                           might be transmitted only tomorrow.




                                                                                    Principle




The current text is valid for any data     Add restriction, that this is only the
transmission. However, it has to be        rule when peer mesh STAs use
restricted to the cases where this         power save. Restrict to buffered
makes sense (PS and buffered               packets, because the more MSDUs
packets).                                  might be transmitted only tomorrow.




                                                                                    Principle




"for all values" is not correct, because   Change "for all values" into "for
                                                                                    Principle
"11" is reserved.                          values 01 (binary) and 10 (binary)"
Not all 11s information elements are       Check extensibility for all and
                                                                                    Agree
extensible.                                correct accordingly.
Why element ID 174 for MCCAOP              Move MCCAOP Advertisement
Advertisement Overview element             Overview element before MCCAOP
instead of contiguous?                     Advertisement element, so that it
                                           has element ID 123 and increase        Disagree
                                           the others accordingly.


The total length of the MCCAOP             "8" in column Total length
Advertisement overview element is not                                             Agree
correct.
The total length of the MCCAOP             "4 to 257" in column Total length
                                                                                  Agree
Advertisement element is not correct.
MCCAOP Setup Reply element is not          "No" in column Extensible
                                                                                  Agree
extensible.
The clause on the Interworking element     Change clause to 7.3.2.92
is actually 7.3.2.92 in 11u.               change heading into "Interworking
Furthermore, the title in 11u is not right - information element" as given in 11u Agree
Interworking information element.            and delete (strike-through) the
                                           "information"
The assignment scheme of the Mesh          Assign protocol identifiers similar to
Peering Protocol identifier is different   the scheme used for the Mesh
from the assignment schemes of the         Peering Protocol identifier, that is,
other protocol identifiers.                protocol identifier 0 is HWMP for
                                           path selection protocol, Airtime Link
                                           metric for path selection metric, and Principle
                                           Neighbor Offset for Synchronization
                                           method.




The MBCA Enabled subfield is not set       Change "activated" into "used"
to 1 when MBCA is activated. It is set
to 1 when MBCA is used. According to
11-09-533, dot11...Activated indicates                                            Principle
that a capability is enabled. Same
issue, it cannot be enabled (activated)
because it is already enabled.
The Neighbor TBTT field is 3 octets        Use Neighbor TBTT field efficiently.
long but the contained value is
truncated to only 19 bits. This is a
waste of 5 bits.                                                                  Principle
"advertisements set sequence number" "advertisement set sequence
should be                            number" (twice)
                                                                                 Agree



"MCCAOP advertisements set" should "MCCAOP advertisement set"
be                                 (multiple occurrences)
                                                                                 Principle



wrong name of element                      MCCAOP Advertisement elements


                                                                                 Principle



length.and                                 length and
                                                                                 Agree

missing space between "integer." and       as in comment
                                                                                 Agree
"The"
wrong field name                           Accept Reservations
                                                                                 Agree

The indication is for a specific report    change "if a Broadcast Report field
field. The name of this field is           is present" into "if the Broadcast    Agree
incomplete.                                Times Report field is present
The indication is for a specific report    change "if a TX-RX Report field is
field. The name of this field is           present" into "if the TX-RX Times     Agree
incomplete.                                Report field is present
error-prone repetition of the content of   point the the clause with the
the Interfering times report.              definition of the content of the
                                           Interfering times report.             Principle



error-prone repetition of the content of   point the the clause with the
the Broadcast times report.                definition of the content of the
                                           Broadcast times report.               Principle
error-prone repetition of the content of   point the the clause with the
the TX-RX times report.                    definition of the content of the TX-
                                           RX times report.                       Principle



Last sentence needs better wording.     Each MCCAOP Reservation field is
                                        5 octets in length and its format is
                                        shown in Figure 7-95o145              Agree
                                        (MCCAOP Reservation field) in
                                        7.3.2.106.2 (MCCAOP Reservation
The MCCAOP Reservations are not         change "reported in this field." into
reported in the Number of Reported      "reported in this MCCAOP              Agree
MCCAOP Reservations field (this field). Reservation Report field."
The indication is for a specific report change "if an Interfering Times
field.                                  Report field is present" into "if the Agree
                                           Interfering Times Report field is
"non-mesh gate" is ambiguous. Is it a      (0 = no mesh gate, ...)
gate that is not a mesh STA?

                                                                                  Principle




The concept of the PXU sequence            as in comment
number seems to be a little bit crude.                                            Disagree
Needs improvement.
rethink for all MCCA frame types           either MCCA ... or MCCAOP ...
whether MCCA ... or MCCAOP ...
                                                                                  Agree



wrong name of element                      MCCAOP Advertisement elements
                                                                                  Agree

bad wording                                better wording
                                                                                  Principle

A restricted number of DTIM interval       This needs rethinking. Possible
lengths that increase exponentially is     solution: Require that all MCCA-
not a good idea. The same concept has      enable mesh STAs use the same
been one of the reasons why the IEEE       DTIM interval or DTIM intervals that
802.15.4 beacon-enabled mode has           are multiples of the largest one.    Disagree
not been adopted. The beacon interval
is simply to inflexible for the set of
applications.
Isn't the content of Note 2 the normal   delete Note 2
                                                                                Agree
understanding?
wrong name of frame                      an MCCA Setup Request frame


                                                                                Agree



last part of the last sentence of the    delete "and terminated when the
paragraph is duplicated with last        MCCAOP reservation is torn down" Principle
sentence of next paragraph.              from lines 15-16
insertion numbering                      make it 9.9a.3.7.6 and update
                                                                          Agree
                                         subsequent clauses accordingly.
insertion numbering                      make it 9.9a.3.7.5 and update
                                                                          Agree
                                         subsequent clauses accordingly.
get ride of pseudo code                  provide lyrical paragraphs that
                                         describe the procedure and       Disagree
                                         conditions.
get ride of pseudo code                  provide lyrical paragraphs that
                                         describe the procedure and       Disagree
                                         conditions.
apostrophe for dead object "a mesh       change "a mesh STA's MCCAOP
STA's", upper case                       Advertisements" into "an MCCAOP Agree
                                         advertisement of a mesh STA"
it's the active mesh path selection      insert "active" so that it reads "... by
protocol                                 the active mesh path selection           Agree
                                          protocol ..."
it's the additional parameters            "Details on the additional
                                          parameters of the forwarding
                                          information constructed by the     Disagree
                                          Hybrid Wireless Mesh Protocol
                                          (HWMP) are described in 11C.9.8.4
Do we really need to spell out "WDS       delete "(previously called WDS
                                                                             Agree
format"?                                  format)"
The mesh STA waits not for an update change into "... waits for an
of an advertisement, it waits for the     MCCAOP advertisement."             Agree
advertisement.
Wrong name of the frame                   MCCAOP Advertisement Request
                                                                             Agree
                                          frame
It's only a single advertisement in lower MCCAOP advertisement
                                                                             Agree
case
It's only a single advertisement          MCCAOP Advertisement //
                                          MCCAOP Advertisement // ... // One Agree
                                         or more MCCAOP Advertisement
Advertisement is unspecified             MCCAOP advertisement
                                                                                Agree

It's only a single advertisement         MCCAOP Advertisement,
                                                                                Agree
It's only a single advertisement         MCCAOP Advertisement //
                                         MCCAOP Advertisement // ... // One Agree
                                         or more MCCAOP Advertisement
It's only a single advertisement         MCCAOP Advertisement,
                                                                                Agree

clause 11.1.2.3 on beacon reception      append text for MBSS in clause
does not contain text for MBSS           11.1.2.3 Beacon Reception. Blue
                                         print might be taken from
                                         11C.12.3.2                             Principle




Clause "11.1.3 Acquiring                 extend clause "11.1.3 Acquiring
synchronization, scanning" has not       synchronization, scanning" with text
been extended for MBSS.                  for MBSS, especially the
                                         paragraphs directly under 11.1.3
                                         (before 11.1.3.1).



                                                                                Principle




clause on beacon generation in MBSS Add new clause "11.1.2.2a Beacon
is missing in 11.1.                 generation in an MBSS"


                                                                                Principle




11.1.1.2 talks about the TSF for an      change heading into "TSF for an
IBSS. Be consistent with this heading.   MBSS"


                                                                                Agree
The link between the TSF (timing        Start paragraph with new sentence
synchronisation function) and the       "The TSF in an MBSS is provided
active synchronization method is        by the active synchronization
missing.                                method."                             Principle




always use square brackets


                                                                             Principle



what is a modulo 2^32 comparison?       Describe the modulo 2^32
How is it done?                         comparison                           Disagree

The originator of the PREQ in Case A    "Bit 0: 0 (no mesh gate)"
                                                                             Principle
(path discovery) cannot act as mesh
The originator of the PREQ in Case B    "Bit 0: 0 (no mesh gate)"
(path maintenance) cannot act as mesh                                        Principle
gate
The originator of the PREQ in Case D "Bit 0: 0 (no mesh gate)"
(root path confirmation) cannot act as                                       Principle
mesh gate
In some earlier comment resolution, we adapt clause accordingly
decided to always propagate the PREQ
with TO=1 in case of an intermediate                                         Disagree
path reply. This has not yet been
reflected in this clause.
If the forwarding information is missing, delete paragraph.
the HWMP sequence number cannot                                              Disagree
be increased.
The determination of the value of the     review and change accordingly
HWMP Sequence Number field has to                                            Disagree
be coordinated with the rules in
The flow of the decision tree is not      include condition on reason code
described well.                                                              Disagree

The flow of the decision tree is not    include condition on reason code
described well.                                                              Disagree

item b) is unclear                      review and change accordingly
                                                                             Disagree

whole clause: The concept of the PXU as in comment
sequence number seems to be a little                                         Disagree
bit crude. Needs improvement.
The mesh STA does not stop               insert "using the Neighbor Offset
synchronization in general after receipt Synchronization method" after
of                                       "synchronization".
MeshNeighborOffsetSyncStop.request                                           Agree




It is nowhere specified when the        Specify the issueing of
MeshNeighborOffsetSyncStart.request MeshNeighborOffsetSyncStart.requ Disagree
primitive is issued. I assume it is not est.
done out of the blue.
"update" seems to imply that there is   Change paragraph into: When
always a timing offset value            dot11MeshActiveSynchronizationM
independent of the active                ethod is 1 (Neighbor Offset
synchronization method. This is not the Synchronization), the mesh STA
case.                                   shall calculate the timing offset
                                        value with respect to the neighbor
                                        mesh STAs, with which it maintains Principle
                                        synchronization. The calculation of
                                        the timing offset value is based on
                                        time stamps from the received
                                        Beacon and Probe Response
                                        frames as follows:

English needs to be improved - too       Change "However, to accommodate
many parts of the sentence in front of   various application needs, the
subject. Furthermore, flexibility is     framework allows flexibility to
provided not allowed.                    integrate future synchronization
                                                                             Agree
                                         methods for MBSSs." into "The
                                         framework allows to integrate other
                                         synchronization methods for MBSSs
                                         in order to accommodate various
whole clause: inconsistencies in the     application needs."
                                         review 11C.12.2 and 10.3.79
use of neighbor peer mesh STA,
neighbor mesh STA, neighbor STA
                                                                             Principle
apostrophe in "in the mesh STA's TSF       in the TSF timer of the mesh STA
timer"


                                                                                  Agree




Semantics of                               Since
dot11MeshNbrOffsetMaxNeighbor is           dot11MeshNbrOffsetMaxNeighbor
unclear. The requirement, that it has to   is only used internally and has no
be at least as large as the max number     effect on any communication with or
of peer neighbors is missing, it is used   information sent to neighbor
                                                                               Disagree
for two different and distinct sets of     stations,
neighbors (MBSS and non-MBSS), but         dot11MeshNbrOffsetMaxNeighbor
the definition in Annex D puts both sets   might be safely deleted. Deletion of
into one. That is, the text in             dot11MeshNbrOffsetMaxNeighbor
11C.12.2.2.1 allows twice as many          is the suggested resolution.
I am withconvinced that it is Annex D.
STA still synchronization as               make 11C.12.2.2.3 clock drift
advantageous, if the Neighbor Offset       adjustment a separate mechanism
method only calculates the Offset and      and move it to clause 11C.12.2a.
Clock drift, but does not do any TSF       extend the neighbor offset
adjustments. TSF adjustments should        synchronization method with clock
be specified as a separate procedure       drift calculation.
which is called by the 11s mechanisms      reference clock drift adjustment
that need it (MCCA, MBCA, although       procedure in all 11s mechanisms
MBCA has it's own mechanism to deal that need it or use it (MCCA, MBCA)
with TBTT drifting). The two main
advantages are:
- Power Save does not need clock drift                                   Disagree
adjustment (TSF adjustment). What
power save needs is to know the TBTT
of a neighbor mesh STA in order to
wake up at the right time. This can be
easily achieved by calculating the
offset and clock drift. Furthermore, the
requirement to do the TSF adjustment
as currently specified requires the
power save nodes to stay awake
longer and to do additional
computations. This requires power that
twos complement is too implementation Either delete this sentence or say
specific. Everything how it is        "The offset value is a signed
represented is implementation specific integer."
here.                                                                               Principle




It is not allowing some jitter of TSF        change "allowing" into "introducing"
                                                                                    Disagree
timer, it is introducing jitter of the TSF
step d) seems not to take into account       Support distributed nature of MBSS
the distributed nature of an MBSS
completely.
                                                                                    Principle




What is the largest T_ClockDrift value, - Specify.
                                                                                    Disagree
5 or +3?
What is a particular neighbor STA?        Specify.




                                                                                    Principle




It's not the clock drift that is adjusted    Use proper wording.
but the TSF.                                                                        Disagree
This is nice! The clock drift adjustment Fix the process
will never be done since every mesh
STA will hav no previous offset at the
beginning. Therefore, it will not operate                                         Principle
the clock drift adjustment. q.e.d.



Step d) contains the potential for ripple Verify that this does not lead to TSF
effects throughout the whole mesh         flapping, that is, verify that the
network and for TSF flapping which          algorithm converges.
would be counterproductive (non-                                                  Disagree
convergence of algorithm)


indices for time are given in increasing previous reception has to be index
chronological order                      0, current reception has to be index
                                         1
                                                                                  Principle




The counting frequency of a TSF is a        Find correct noun instead of
physical process and cannot be              counting frequency
aligned.
                                                                                  Principle




The first sentence on the MLME-             Move first sentence to clause
MeshNeighborOffsetMeasure.request           10.3.79.3
belongs into clause 10.3

                                                                                  Disagree




apostrophe in "measured in a neighbor measured in the TSF of a neighbor
mesh STA's TSF"                       mesh STA


                                                                                  Agree
The text of this clause might be better a Move text to new clause 11.1.2.2a
new clause 11.1.2.2a Beacon
generation in an MBSS




                                                                                  Principle




The text of this clause might be better   Move text to 11.1.2.3
placed in 11.1.2.3.


                                                                                  Principle




missing article                           ... set the MBCA Enabled subfield ...



                                                                                  Agree




dot11MBCAActivated is true means          change "shall activate" with "shall
that it is already activated, so the mesh use"
STA cannot activate it. According to 11-
09-533, dot11...Activated indicates that                                          Agree
a capability is enabled. Same issue, it
cannot be enabled (activated) because
it is already enabled.
if clause sounds strange in the middle    move if clause at the end of
of sentence.                              sentence.




                                                                              Principle




Wrong name of the element                 MCCAOP Advertisement element



                                                                              Agree




Wrong name of the element                 MCCAOP Advertisement element



                                                                              Agree




What is "neighbor STA identification". It Clarify.
is used only once and not defined.


                                                                              Principle




comma too much                            delete comma after identification



                                                                              Agree
"calculated for the first time since the   correct this.
latest update of the status number" is
not understandable. Furthermore, it
seems to contradict "time predicted                                            Principle
from the previous TBTT" in line 45.



indices for time are given in increasing previously received beacon frame
chronological order                      has to be index 0, received beacon    Disagree
                                           frame has to be index 1
missing article                            The T_TBTT is used ...



                                                                               Agree




apostrophe in "in the receiving mesh       in the TSF timer of the receiving
STA's TSF timer"                           mesh STA


                                                                               Agree




particular is not defined, and it is not  delete "particular"
                                                                             Disagree
necessary.
The condition is difficult to understand, Make condition easy to understand.
especially the when. It is always set to Improve wording.
0 and than incremented to 1 every
time? Also some English "since it has
updated"



                                                                               Principle
The status number is not given by a      Change "The status number, given
modulo-16 counter, it is such a counter. by a modulo-16 counter, is
                                          initialized with 0 ..." into "The status Disagree
                                          number is modulo-16 counter. It is
                                          initialized with 0 ..."
The beacon timing advertisement           1) add a overview description of
comes out of the blue. The overview       MBCA including the beacon timing
was talking about MBCA, but did not       advertisement into clause
introduce a beacon timing                 11C.12.4.1 Overview.
advertisement. Furthermore,               2) reorganize 11C.12.4 in such a
11C.12.4.2.1 starts with a very specific way that the reader can follow the
detail, the maintenance of the status    specification and that there is a line
number. But where does this status       of thought that develops by building
number come from?                         on the information of the previous
                                          subclauses within 11C.12.4 MBCA.

                                                                                  Principle




article too many: "the maximum            "maximum number of ..."
number of ..."


                                                                                  Agree




"In such case"                            "In this case"
                                                                                  Disagree
all tuples need to be put into Beacon    Change "When the beacon timing
Timing Information elements.             information set is divided, the mesh
                                         STA shall include one of the
                                         successive tuples of beacon timing
                                         information in the Beacon Timing
                                                                              Disagree
                                         element." into
                                         "When the beacon timing
                                         information set is divided, the mesh
                                         STA shall include the successive
                                         tuples of beacon timing information
article too many                         "...the Beacon Timing elements."
                                         in an interger multiple of
                                         dot11MeshBeaconTimingReportInte
                                         rval."
                                                                                  Agree




different article                        "... is present in a Beacon frame ..."



                                                                                  Agree




Make last sentence a separate          as in comment
                                                                                  Disagree
paragraph (because the sister variable
simplify sentence "The mesh STA shall The mesh STA shall also include
also include the Beacon Timing         the Beacon Timing element in
element in Beacon frames as specified    Beacon frames as specified by
by the attributes of the beacon timing   dot11MeshBeaconTimingReportInte
                                                                         Agree
report procedure given by                rval and
dot11MeshBeaconTimingReportInterva       dot11MeshBeaconTimingReportMa
l and                                    xNum.
dot11MeshBeaconTimingReportMaxNu
m."
number representation                    better write 524,288 TU
                                                                                  Disagree


Might be a good idea to put this value   as in comment
in a variable.                                                                    Disagree
wrong article, use plural                  "... shall look for a timing of its
                                           beacon transmissions ..."


                                                                                  Agree




The information obtained from the          Add information received from the
Beacon Timing elements is not              beacons of the neighbors.
enough.
                                                                                  Principle




This sentence (last sentence of this       Move this to the general clause of
paragraph) is more of a general nature.    MBCA. In clause 11C.12.4.2.5
In any way, it does not belong to the      Receiver's procedure, only
procedures done in lieu of the             normative text that directly follows
reception of a beacon timing element. It   out of the reception of the beacon
does not say what to do when a             timing element belongs in this
beacon timing element is received.         clause.
Instead it talks about general
procedures to be done when
dot11MBCAActivated is true.

                                                                                  Principle
How can a mesh STA obtain the            change "beacon reception timing"
beacon reception timing (i.e. the time   into "TBTT" or what it actually
when a beacon has been received)         means. Maybe beacon timing
from a beacon timing element? The       information?
fields in the beacon timing information
                                                                              Principle
of the beacon timing element are the
Neighbor STA ID, the Neighbor Last
Beacon Time which indicates a TBTT,
and the Neighbor Beacon Interval. But I
guess, it is the beacon timing
information stored
simplify, apostropeat this neighbor     "... represents the correct beacon
                                        reception by the neighbor mesh
                                         STA."
                                                                              Agree




"assigned by this peer mesh STA" is      "assigned to this mesh STA"
the wrong term


                                                                              Agree




word order and grammar, simplification "NOTE2--Once the entire beacon
                                       timing information set with a
                                       particular Status Number is
                                       obtained, the mesh STA does not        Agree
                                         need to retrieve beacon timing
                                         information as long as the Status
                                         Number remains the same."
better wording for "When a mesh STA      "When a mesh STA receives a
receives a Beacon frame containing       Beacon frame with a Beacon Timing
Beacon Timing element that indicates     element that contains only a subset
only a subset of the beacon timing       of the beacon timing information set, Agree
information set is contained, ..."       ..."
missing article                              ... to advertise a fragmented beacon
                                             timing information set ...


                                                                                    Agree




The structure of and distribution            as in comment
between scanning and adjustment
procedure needs to be revised.


                                                                                    Disagree




coming later is not a sufficient             provide complete differantiation
differentiation. Especially in a collision   criterion
situation, the TBTTs might be the
same.

                                                                                    Disagree




The mesh STA should not parse the            parse or analyse or what other
Beacon Timing element. It might              better verb the beacon timing
contain only incomplete information,         information.
and there might be none available                                                   Principle
when it wants to parse it.



spelling                                     rage --> range



                                                                                    Agree
There is a contradiction. The             resolve the contradiction
specification of the MLME-
START.request primitive says "the
MLME-START.request primitive must
be generated before an
MLMEMeshNeighborOffsetSync.
request primitive and MLME-
MeshPeerigManagement.request have
been used." But in this clause, the
MLME-START.request primitive is only
                                                                              Principle
used after a mechanism that requires
the usage of MLME-
MeshNeighborOffsetSync.request.




Clause 11C.12.4.4.3 TBTT adjustment rewrite in a procedural style, still
procedure should be improved.       lyrics, but in a step by step manner Disagree
                                    where the steps are in chronological
What does the mesh STA with         delete step b)
dot11MBCAActived do all the time? I       delete the term "scanning
thought it is supposed to collect the     procedure" and related stuff from
recent beacon timing information.         clause 11C.12.4.4.3
                                                                              Principle
Therefore, step b) is not necessary
(that is, the scanning procedure is not
necessary).
Setting the TBTT Adjusting field in the    move step a) to the correct place,
Mesh Configuration element has             that is, just before the actual TBTT
serious implications to the                adjustment.
synchronization method performed at
the neighbor mesh STAs. Therefore, it
should be only set when an adjustment
is really performed. It is a bad idea to
set this flag when the mesh STA is only
collecting information and is only doing                                           Disagree
internal calculations that do not have
any effect on neighbor mesh STAs.




The mesh STA waits not for an update change into "... waits for an
of an advertisement, it waits for the MCCAOP advertisement."                       Agree
advertisement.
clause on proactive RANN mechanism as in comment
of HWMP needs review.                                                              Disagree

Since I suggested we delete 11C4.3.2, If there is any material of interest in
11C4.3.3 and 11C4.3.4, it is silly to      11C.4.3.1, move it to a relevant
keep "11C.4.3.1 Overview" as a             clause. The rest can be deleted
standalone clause.                         (e.g. statements such as "When two
                                           HT mesh STA establish a mesh
                                           peering, and they support a
                                           common HT capability, the HT
                                           feature may be used for the mesh
                                           peering communication." and
                                           "frames are either accepted or
                                                                                   Principle
                                           silently discarded" provide no
                                           actionable information).


                                           This should result in the deletion of
                                           11C.4.3, but we can use the title of
                                           11C.4.3 for the previous 11C.4.4
                                           (i.e. the state machine, which is the
                                           means by which Mesh Peering
                                           Management frames are
                                           processed).
Some text in this section is redundant Thoroughly rewrite the clause to
(e.g. "or if the frame was dropped and if specify behaviour without ambiguity.
the frame is a Mesh Peering Open
frame", "If the frame contains a group
address in TA or RA, it shall be silently
discarded") or erroneous ("If the Mesh
Peering Open frame is not discarded,
the mesh peering instance controller
shall generate a new protocol finite
state machine and actively reject or
                                                                                 Principle
accept the mesh peering open request"
indicates that a duplicate Open frame
should start a new state machine,
which contradicts "If the mesh peering
instance controller finds a matching
mesh peering instance it shall process
the frames
according to the frame type", which
BTW is as vague as it gets)


This clause is a peering instance          Move 11C.4.2 to 11C.3.2.5 Pre-
controller function, it therefore deserves processsing Mesh Peering
to be in 11C.3.2 Mesh peering instance Management frames
controller




                                                                                 Principle
The separation of the mesh peering        Replace "Functions" with
instance controller clause into           "Overview". Remove "creation" and
"Functions", "creation" and "deletion" is "deletion" clauses and replace with
inappropriate. In a functional spec,      something along the lines of
everything is a function, so I think it   "creating a new instance", "updating
should be rename overview. And the        a partially identified instance",
issue of managing peering instances is    "deleting a mesh peering instance".
a lot more involved than just creating    Then make references to clause
andd deleting them                        13C.3.2.5 where the actual decision-
                                          making occurs.
                                                                                 Principle




This clause is a repetition of the     11C.4.3.4
equivalent frame format clause and the
element preprocessing clause
(11C.4.2)




                                                                                 Principle
This clause is a repetition of the     In compliance with the TGs motto,
equivalent frame format clause and the remove the whole clause.
element preprocessing clause
(11C.4.2)




                                                                           Principle




This clause is a repetition of the     In compliance with the TGs motto,
equivalent frame format clause and the remove the whole clause.
element preprocessing clause
(11C.4.2)




                                                                           Principle
The clause contains many "shall"           Remove all unactionable "shall",
statement that are not testable, or        and severely limit the number of
sometimes not even actionable. For         untestable ones.
example: "When
dot11MeshSecurityActivated is true,
the mesh STA shall manage mesh
peerings and Mesh
TKSAs for each peer mesh STA.", "one
of the following protocols shall be
invoked", "A mesh STA shall use a
                                                                                Principle
mesh peering instance controller"




It is not clear which metric value         Specify it.
(measured metric value or the metric
value used for path selection) are                                              Disagree
reported through the link metric
reporting, when Airtime Link Metric is
In the base standard (REVmb D4.0),         1) Add "Self-protected Action"or
subclause 11.3.0a talks about the          "Mesh Peering Open/Confirm/Close
authentication, association, and frame     frames" to Class 2 frames entry.
classes. I think TGs needs to have a       2) Add some pointer information on
similar diagram for mesh peering           mesh peering for mesh BSS in 11.3.
management. At least, Mesh Peering         3) Also, delete ", or Mesh Peering
Management frames should be defined        Management frames," in subclause Disagree
as class 2 frames (not sure if it is the   10.3.4.1.3 and in subclause
case for Mesh Group Key                    10.3.5.1.3.
Inform/Acknowledge frames). The            4) Draw a state diagram for mesh
omission causes architectural flaw.        peering management and place it
Need to add pointer information for        somewhre in 11C.3.
mesh peering in this subclause, and
add the class 1/2/3 frames diagram for
MLME- MeshLinkMetricRead.confirm() Change the primitive argument to
reports on a single LinkMetricValue. include these 3 different values.
However, there are some link metric
values internally as follows:
1) the link metric value measured at the
local STA
2) the link metric value reported from its                                    Disagree
neighbor peer STA (through link metric
report frame)
3) the link metric value used for the
path selection
They should be reported to SME in a
separate manner. OR 3) might be given
Backoff after every single group           Please consider the possibility to
addressed frame transmission sounds transmit multiple group addressed
like very heavy and resource               frames in the same EDCA TXOP as
consuming operation. Is the backoff      in infrasrtucture network. Mesh
really needed after every transmitted    operation can be more efficient than Disagree
group addressed frame? In mesh BSS, IBSS. Also, random backoff does
it is very likely that there are many    not help minimizing collisions in a
small size broadcast traffic, regardless hidden node scenario.
of management or data, and it could be
useful Action field value is notdelivery
Mesh to have more efficient              Change the value assignment to be
contiguous assignment. This causes      more TGae friendly.
unnecessary signal processing when
conforming to TGae.




                                                                             Principle




It is very confusing to have optional   Remove Proxy MAC address
Proxy MAC address subfield in the       subfield from Proxy Information
Proxy Inforamtion field. If the Proxy   field.                               Disagree
MAC address is different, those
information should be transmitted via
different information elements.
In table 7-17, "Finite Cyclic Group is      As in comment.
present if Status is zero." should read
"Finite Cyclic Group is present if Status                                            Agree
is zero or 76."


5.2.3.1. is the subclause from the base Clarify.
stndard. It is not clear if mesh BSS is a
part of ESS or not.
                                                                                     Principle




Figure 5-6c should look something           As in comment.
more similar to Figure 5-2 in the base
standard.                                                                            Disagree



Figure 5-6b should look something      As in comment.
more similar to Figure 5-7 in the base
standard. Also, TGs may want to
amend some part in clause 5.3.2 (DSS)
and Figure 5-7 in the base standard, as
there is no mentioning of mesh BSS in
                                                                                     Principle
the clause and the figure.




Typo                                        Replace "point a infinity" with "point
                                            at infinity".
                                                                                     Agree



The MCCAOP Advertisement Overview Replace "6" with "8" in the Total
has incorrect total length in Table 7-26. length column.
7.3.2.108 defines this element as                                                    Agree
having a fixed Length field value of 6,
i.e., having total length of 8.
My previous comment does not seem      Incorporate support for IEEE
to be addressed. Support for IEEE      802.1X.
802.1X authentication is not fully
incorporated.
                                                                                 Agree




The use of the word "unspecified" is not Change the paragraph to read:
very clear. Change the paragraph to be "In a mesh STA when
clearer.                                 dot11ESNetwork is false, it is
                                         unable to support the mesh peering
                                       of ES
                                       and ESR shall be set to 0. When
                                                                                 Principle
                                       that mesh STA receives a Mesh
                                       Peering Open frame, that includes
                                       the
                                       Interworking element with the ASRA
                                       bit equal to 1, it is unable to support
                                       the mesh peering of ES."
                                     Submissi Updated Respons Accept_R #Mot Edit
Resolution Detail
                                     on       (to editor) eStatus ejectDate ion Status
Capital letter: Also solicit CRC
members to recognize this                               Closed   20110317 #78 I
guideline.
Capital letter: Also solicit CRC
members to recognize this                               Closed   20110317 #78 I
guideline.

                                    https://me
                                    ntor.ieee.
counter. The IEs are singular so it org/802.1
will become "the RSN element"       1/dcn/11/
                                    11-11-              Closed   20110317 #70 I
and "the AMPE element". Rest of 0329-01-
comment is accepted.                000s-
                                    seccomre
                                    s-sb2.doc




Capital letter: Also solicit CRC
members to recognize this                               Closed   20110317 #78 I
guideline.


                                     https://me
counter, the heading shall read      ntor.ieee.
                                     org/802.1
"Mesh Peering Management             1/dcn/11/          Closed   20110317 #70 I
frames for authenticated mesh        11-11-
peering exchange."                   0329-01-
                                     000s-
                                     seccomre
                                     https://me
I don't know what this refers to. I ntor.ieee.
can't find "the peer" on line 42 and org/802.1
the closest text to line 42 has      1/dcn/11/          Closed   20110317 #70 I
                                     11-11-
been completely replaced by          0329-01-
accepting CID 2016.                  000s-
                                     seccomre
                                                        Closed   20110317 #78 I
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/          Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
                                                        Closed   20110317 #78 I
                                                  Closed   20110317 #78 I
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
Looking at the latest REVmb, it
seems that this does not need to                  Closed   20110317 #78 I
be in lower case. Keep the current
form for now.




                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
                                     11-11-       Closed   20110317 #70 I
                                     0329-01-
                                     000s-
                                     seccomre
                                     s-sb2.doc
                                       https://me
                                       ntor.ieee.
                                       org/802.1
counter                                1/dcn/11/    Closed   20110317 #70 I
                                       11-11-
                                       0329-01-
                                       000s-
                                       seccomre
                                       https://me
                                       ntor.ieee.
                                       org/802.1
counter                                1/dcn/11/    Closed   20110317 #70 I
                                       11-11-
                                       0329-01-
                                       000s-
                                       seccomre
                                       https://me
                                       ntor.ieee.
                                       org/802.1
ibid                                   1/dcn/11/    Closed   20110317 #70 I
                                       11-11-
                                       0329-01-
                                       000s-
                                       seccomre
                                       https://me
                                       ntor.ieee.
                                       org/802.1
                                       1/dcn/11/    Closed   20110317 #70 I
                                       11-11-
                                       0329-01-
                                       000s-
                                       seccomre
                                       https://me
I just have to note that if I followed ntor.ieee.
this comment the way it is worded org/802.1
there would be an extra "the" in       1/dcn/11/    Closed   20110317 #70 I
                                       11-11-
the sentence-- "the the mesh           0329-01-
STA…"                                  000s-
                                       seccomre
                                       https://me
                                       ntor.ieee.
                                       org/802.1
ggrrrrrrr                              1/dcn/11/    Closed   20110317 #70 I
                                       11-11-
                                       0329-01-
                                       000s-
                                       seccomre
                                       https://me
                                       ntor.ieee.
                                       org/802.1
                                       1/dcn/11/    Closed   20110317 #70 I
                                       11-11-
                                       0329-01-
                                       000s-
                                       seccomre
                                    https://me
                                    ntor.ieee.
HORRIBLE COMMENT! EXPAND org/802.1
"with" to be "the mesh STA with     1/dcn/11/     Closed   20110317 #70 I
                                    11-11-
the largest MAC address"            0329-01-
                                    000s-
                                    seccomre
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/     Closed   20110317 #70 I
                                    11-11-
                                    0329-01-
                                    000s-
                                    seccomre
                                    https://me
horrible comment. Take text         ntor.ieee.
                                    org/802.1
before "and" and after "and" and 1/dcn/11/
                                                  Closed   20110317 #70 I
include it in the comment before 11-11-
the word "with" to provide context. 0329-01-
                                    000s-
                                    seccomre
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/     Closed   20110317 #70 I
                                    11-11-
                                    0329-01-
                                    000s-
                                    seccomre
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/     Closed   20110317 #70 I
                                    11-11-
                                    0329-01-
                                    000s-
                                    seccomre
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/     Closed   20110317 #70 I
                                    11-11-
                                    0329-01-
                                    000s-
                                    seccomre
Looking at the latest REVmb, it
seems that this does not need to                  Closed   20110317 #78 I
be in lower case. Keep the current
form for now.
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
Capital letter: Also solicit CRC
members to recognize this                       Closed   20110317 #78 I
guideline.
                                   https://me
it's page 218! Maybe if you        ntor.ieee.
                                   org/802.1
included subclauses with your      1/dcn/11/    Closed   20110317 #70 I
comments it would be easier to     11-11-
see what you're talking about!     0329-01-
                                   000s-
                                   seccomre

Capital letter: Also solicit CRC
members to recognize this                       Closed   20110317 #78 I
guideline.



make this comment against 11mb                  Closed   20110317 #70 I

                                   https://me
                                   ntor.ieee.
                                   org/802.1
                                   1/dcn/11/    Closed   20110317 #70 I
                                   11-11-
                                   0329-01-
                                   000s-
                                   seccomre
                                   https://me
                                   ntor.ieee.
                                   org/802.1
                                   1/dcn/11/    Closed   20110317 #70 I
                                   11-11-
                                   0329-01-
                                   000s-
                                   seccomre
                                   https://me
                                   ntor.ieee.
                                   org/802.1
                                   1/dcn/11/    Closed   20110317 #70 I
                                   11-11-
                                   0329-01-
                                   000s-
                                   seccomre
                                   https://me
                                   ntor.ieee.
                                   org/802.1
counter, just remove must.         1/dcn/11/    Closed   20110317 #70 I
Sentence is fine without it.       11-11-
                                   0329-01-
                                   000s-
                                   seccomre
                             https://me
                             ntor.ieee.
                             org/802.1
                             1/dcn/11/    Closed   20110317 #70 I
                             11-11-
                             0329-01-
                             000s-
                             seccomre

Thank you for your helpful
                                          Closed   20110317 #78 I
comment!




Thank you for your helpful
                                          Closed   20110317 #78 I
comment!



Thank you for your helpful
                                          Closed   20110317 #78 I
comment!



Thank you for your helpful
                                          Closed   20110317 #78 I
comment!


Thank you for your helpful
                                          Closed   20110317 #78 I
comment!


Thank you for your helpful
                                          Closed   20110317 #78 I
comment!


                                          Closed   20110317 #72 I


Thank you for your helpful
                                          Closed   20110317 #78 I
comment!



Thank you for your helpful
                                          Closed   20110317 #78 I
comment!




Thank you for your helpful
                                          Closed   20110317 #78 I
comment!
Thank you for your helpful
                                                Closed   20110317 #78 I
comment!


Thank you for your helpful
                                                Closed   20110317 #78 I
comment!

Thank you for your helpful
                                                Closed   20110317 #78 I
comment!

Replace "peerMAC" with
"PeerMACAddress" throughout, in                 Closed   20110317 #78 I
order to align with the base
standard.
Thank you for your helpful
                                                Closed   20110317 #78 I
comment!
Replace "peerMAC" with
"PeerMACAddress" throughout, in                 Closed   20110317 #78 I
order to align with the base
standard.
                                  https://me
                                  ntor.ieee.
                                  org/802.1
                                  1/dcn/11/
See document 11-11-0450r0         11-11-        Closed   20110317 #74 I
                                  0450-00-
                                  000s-
                                  resolution-
                                  to-cid-

Thank you for your helpful
                                                Closed   20110317 #78 I
comment!


Thank you for your helpful
                                                Closed   20110317 #78 I
comment!
Also, correct inappropriate
capitalization at the 3rd level
heading title in clause 10.3.
10.3.79: "Mesh Neighbor Offset
Synchronization" -> "Mesh
neighbor offset synchronization"
10.3.80: "Mesh TBTT Adjustment"
-> "Mesh TBTT adjustment"                         Closed   20110317 #78 I
10.3.82: "MBSS Congestion
Control" -> "MBSS congestion
control"
10.3.83: "MBSS Proxy Update" ->
"MBSS proxy update"
10.3.86: "HWMP Mesh Path
Selection" -> "HWMP mesh path
                                                  Closed   20110317 #78 I

Replace "must be" with "shall be".
                                                  Closed   20110317 #78 I
(To be aligned with REVmb
Replace "must be" with "shall be".
                                                  Closed   20110317 #78 I
(To be aligned with REVmb
Replace "must be" with "shall be".
                                                  Closed   20110317 #78 I
(To be aligned with REVmb
Replace "must match" with
"matches" (To be aligned with                     Closed   20110317 #78 I
REVmb D7.02)
Apply the similar change to line
                                                  Closed   20110317 #78 I
26-28 on the same page.

However, compare 9.9 HCF; MCF
                                                  Closed   20110317 #72 I
was already introduced in 9.1.3a

make this comment against 11mb                    Closed   20110317 #70 I
                                     https://me
                                     ntor.ieee.
                                     org/802.1
counter                              1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/    Closed   20110317 #70 I
                                      11-11-
                                      0329-01-
                                      000s-
                                      seccomre
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/    Closed   20110317 #70 I
                                      11-11-
                                      0329-01-
                                      000s-
                                      seccomre
this is not a statement of
permission, it's a description of a                Closed   20110317 #70 I
different way to look at the same
function.
this is not a statement of
permission, it's a description of a                Closed   20110317 #70 I
different way to look at the same
function.
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/    Closed   20110317 #70 I
                                      11-11-
                                      0329-01-
                                      000s-
                                      seccomre
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/    Closed   20110317 #70 I
                                      11-11-
                                      0329-01-
                                      000s-
                                      seccomre
                                      https://me
                                      ntor.ieee.
                                      org/802.1
counter                               1/dcn/11/    Closed   20110317 #70 I
                                      11-11-
                                      0329-01-
                                      000s-
                                      seccomre
                                      https://me
                                      ntor.ieee.
                                      org/802.1
counter                               1/dcn/11/    Closed   20110317 #70 I
                                      11-11-
                                      0329-01-
                                      000s-
                                      seccomre
                              https://me
                              ntor.ieee.
                              org/802.1
                              1/dcn/11/    Closed   20110317 #70 I
                              11-11-
                              0329-01-
                              000s-
                              seccomre
                              https://me
                              ntor.ieee.
                              org/802.1
                              1/dcn/11/    Closed   20110317 #70 I
                              11-11-
                              0329-01-
                              000s-
                              seccomre
                              https://me
                              ntor.ieee.
                              org/802.1
                              1/dcn/11/    Closed   20110317 #70 I
                              11-11-
                              0329-01-
                              000s-
                              seccomre

Replace "can be" with "is".                Closed   20110317 #77 I


                                           Closed   20110317 #77 I

                                           Closed   20110317 #72 I
                              https://me
                              ntor.ieee.
                              org/802.1
                              1/dcn/11/    Closed   20110317 #70 I
                              11-11-
                              0329-01-
                              000s-
                              seccomre
                              https://me
                              ntor.ieee.
                              org/802.1
                              1/dcn/11/    Closed   20110317 #70 I
                              11-11-
                              0329-01-
                              000s-
                              seccomre
                              https://me
                              ntor.ieee.
                              org/802.1
                              1/dcn/11/    Closed   20110317 #70 I
                              11-11-
                              0329-01-
                              000s-
                              seccomre
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/    Closed   20110317 #70 I
                                     11-11-
                                     0329-01-
                                     000s-
                                     seccomre
Replace "In case of infrastructure
BSS operation" with "In
infrastructure BSS operation".                    Closed   20110317 #78 I
Replace "In a mesh BSS
operation" with "In mesh BSS

                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
                                     11-11-       Closed   20110317 #70 M
                                     0329-01-
                                     000s-
                                     seccomre
                                     s-sb2.doc


Replace "ES" with "emergency
service" in sublause 5.2.14.5.12.                 Closed   20110317 #78 I
There are 6 instances.

"PSAP" is defined by TGu.                         Closed   20110317 #78 I

The clause in mention was
reviewed and the task group                       Closed   20110317 #80 I
invites more review from the



                                                  Closed   20110317 #78 I




                                                  Closed   20110317 #78 I
Capital letter: Also solicit CRC
members to recognize this           Closed   20110317 #78 I
guideline.


                                    Closed   20110317 #78 I

Capital letter: Also solicit CRC
members to recognize this           Closed   20110317 #78 I
guideline.
Replace "Synchonization in a
mesh BSS can be maintained by
the default synchronizaion
method, Neighbor Offset
Synchronization method." with       Closed   20110317 #78 I
"Synchronization in a mesh BSS
is maintained by an active
synchronization method. The
default synchronization method is
the Neighbor Offset
                                    Closed   20110317 #78 I

Capital letter: Also solicit CRC
members to recognize this           Closed   20110317 #78 I
guideline.
                                    Closed   20110317 #78 I

                                    Closed   20110317 #78 I

Capital letter: Also solicit CRC
members to recognize this           Closed   20110317 #78 I
guideline.
Replace "can be" with "is".         Closed   20110317 #78 I


                                    Closed   20110317 #78 I


                                    Closed   20110317 #78 I
The mesh gate connects the
MBSS with the DS. Thus, it has a
similar function like the portal.
Accordingly, we were happily and
ruthlessly copying text from the
802.11-2007 ("3.110 portal: The
logical point at which the
integration service is provided."
and in 5.2.5 "A portal is the logical                 Closed   20110317 #78 I
point at which MSDUs from an
integrated non-IEEE-802.11 LAN
enter the IEEE 802.11 DS."). This
definition hasn't changed in
802.11-REVmb/D7.0. Thus, we
believe that the description as a
"logical point" is valid. If
commenter disagrees, the portal
definition in 802.11-2007 should        https://me
                                        ntor.ieee.
                                        org/802.1
See submission 11-11-0429-01-           1/dcn/11/
                                        11-11-        Closed   20110317 #78 I
000s for comment resolution.
                                        0429-01-
                                        000s-
                                        resolution-
                                        to-cid-

                                                      Closed   20110317 #78 I

TDLS is not incorporated in mesh
BSS.
Add "-- Tunneled direct-link setup                    Closed   20110317 #78 I
(TDLS)" after "-- Diirect-link setup
(DLS)".




                                                      Closed   20110317 #78 I




                                                      Closed   20110317 #78 I


                                                      Closed   20110317 #78 I


                                                      Closed   20110317 #78 I
                                      Closed   20110317 #78 I



Replace the sentence as
                                      Closed   20110317 #78 I
proposed by the commenter.



                                      Closed   20110317 #78 M




                                      Closed   20110317 #78 M




Replace "can establish…" with
"establish". Replace "can benefit"    Closed   20110317 #78 I
with "benefits" on line 13.
In 5.2.14.1 replace the last
sentence ". The quantity of certain
mesh-specific mechanisms may
vary among mesh
implementations." with ". The
mesh-specific quantity of certain
mechanisms may vary among             Closed   20110317 #78 I
mesh implementations."


Further, the group believes that it
carefully reviewed the whole draft
for syntactical errors. However,
we request the commenter to
                                      Closed   20110317 #78 I


                                      Closed   20110317 #78 I
Change the sentence to "For
infrastructure BSS and IBSS this
standard provides two
                                      Closed   20110317 #78 I
mechanisms for the support of
applications with QoS
requirements."
In 5.2.6 (QoS BSS: The QoS
network) replace "Because a QoS
STA implements a superset of
STA functionality, as defined in
this standard, the STA may
associate with a non-QoS access
point in a non-QoS BSS, to
provide non-QoS MAC data
service when there is no QoS
BSS with which to associate." with    Closed   20110317 #78 I
Replace "Because a non-mesh
QoS STA implements a superset
of STA functionality, as defined in
this standard, the STA may
associate with a non-QoS access
point in a non-QoS BSS, to
provide non-QoS MAC data
service when there is no QoS
BSS with which to associate. As a
mesh STA does not implement

As in comment.                        Closed   20110317 #78 I
Replace 'To access all the
services of an infrastructure BSS,
a STA becomes “associated.”
These associations are dynamic
and involve the use of the
distribution system service (DSS),
which is described in 5.3.2 (DSS).'
with 'To access all the services of
an infrastructure BSS, a STA
becomes “associated.” These           Closed   20110317 #78 I
associations are dynamic and
involve the use of the distribution
system service (DSS), which is
described in 5.3.2 (DSS).


A mesh STA cannot become
associated as there is no central
entity in a mesh BSS (MBSS).
Instead a mesh STA peers with
other mesh STAs and thereby




Capital letter: Also solicit CRC
members to recognize this             Closed   20110317 #78 I
guideline.
Replace sentence with "A
coordination function that             Closed   20110317 #72 I
combines aspects of the
contention-based and scheduled

The comment proposes better
language. Implement as in the          Closed   20110317 #75 I
comment.


change "A destination mesh
station (STA) that is considered
unreachable as the link to the next
hop of the mesh path to this
destination mesh STA is no longer
                                       Closed   20110317 #77 M
usable."
into "An unreachable destination
mesh station (STA) because the
link to the next hop of the mesh
path to this destination mesh STA
is no longer usable."
The definition defines the peering
as a logical relationship. Mesh
STAs use the wireless link
between them to establish a mesh
peering. Subsequent, they "know
each other." As a logical
relationship, the mesh peering
continues to exist even if the         Closed   20110317 #79 I
wireless link between the mesh
STAs is currently unavailable.
Once the wireless link can be
used again, the mesh STAs
continue to use the logical
relationship. This is different from
traditional 802.11 networks where
The basic idea of 802.11s is that
the MBSS is a self-contained
network. 802.11s tries to reuse as
much 802.11 mechanisms as
possible. Therefore, 802.11s
introduces the mesh gate that is
more similar to the AP than to the
portal. Through an AP an
infrastructure BSS accesses the
DS. Similar, an MBSS access the
DS through a mesh gate. From
DS both, the MBSS and the                          Closed   20110317 #78 I
infrastructure BSS, can connect
with a portal then. So, a mesh
gate does not connect to a non-
802.11 network. It connects to a
DS only. There is text in 5.2.14.4
that explains the relationship
"Whereas the portal integrates the
IEEE 802.11 architecture with a
traditional wired LAN, the mesh
gate integrates the MBSS with the
IEEE 802.11 DS. Once an MBSS



                                                   Closed   20110317 #78 I



                                     https://me
                                     ntor.ieee.
                                     org/802.1
See submission 11-11-0398-00-        1/dcn/11/
                                     11-11-        Closed   20110317 #78 IR
000s for comment resolution.
                                     0398-00-
                                     000s-
                                     resolution-
                                     to-cid-
The more data bit value for group
addressed frames ensures the
correct setting of the bit, if the
mesh STAs change their mesh
power management mode. It is
not trivial to check the correct
operation, if the peer changes its
mesh power mode.
The More Data bit should be valid
for group addressed frames if
there is any peer STA in light or
                                      Closed   20110317 #75 I
deep sleep mode.


During the discussion in 802.11s
Thursday 17.3 AM1, it was
explained that the comment is
requesting to clarify "when there
are more group
addressed MSDUs or MMPDUs to
be transmitted." It was agreed to
change the text to: "when there
are more group
At the discussion on Thursday
AM1, the comment was explained
and the 802.11s group agreed to
change the text:
"The More Data field is set to 1 by
mesh STAs for individually
addressed frames sent to a
neighbor peer mesh STA when
there are more MSDUs or               Closed   20110317 #75 I
MMPDUs to be transmitted to that
mesh STA." to
"The More Data field is set to 1 by
mesh STAs for individually
addressed frames sent to a
neighbor peer mesh STA in light
or deep sleep mode when there
are more MSDUs or MMPDUs are
Replace "For all other values,
                                      Closed   20110317 #78 I
[…]" with "For values 01 and 10,
We carefully checked all
                                      Closed   20110317 #78 I
elements.
TGs editor has actually requested
swapping number assignment
from ANA. (Assign 120 as
MCCAOP Advertsement                             Closed   20110317 #78 I
Overview, and relocate Beacon
Timing to 174). However, this
request has been disagreed by
                                                Closed   20110317 #72 I


                                                Closed   20110317 #72 I

                                                Closed   20110317 #72 M



                                                Closed   20110317 #78 I



Table Table 7-43bj1 has changed.
The group further decided that the
value 0 should be used in case a
protocol is not in use. If this
meaning is not correct, the value
0 is to be reserverd.                           Closed   20110317 #78 I


Thus, in Table 7-43bj6 (Mesh
Peering Protocol Identifier
values), increment all values by 1.
Further introduce the following
                               https://me
                               ntor.ieee.
                               org/802.1
Change "the mesh STA activates 1/dcn/11/
MBCA" to "the mesh STA is      11-11-           Closed   20110317 #73 I
                               0400-02-
using"
                               000s-mac-
                               sync-
                               beacon-
                               resolution-
                               https://me
                                  ntor.ieee.
Change "The B5 to the B23         org/802.1
                                  1/dcn/11/
(taking the B0 as the LSB)" to
                                  11-11-        Closed   20110317 #73 I
"The B5 to the B28 (taking the B0 0400-02-
as the LSB)".                     000s-mac-
                                  sync-
                                  beacon-
                                  resolution-
                                    https://me
                                    ntor.ieee.
                                    org/802.1
Corrected multiple occurrences in   1/dcn/11/    Closed   20110317 #72 I
contribution 11-11-0416-02-000s.    11-11-
                                    0416-02-
                                    000s-
                                    mcca-sb2-
                                    https://me
                                    ntor.ieee.
see contribution 11-11-0416-02-     org/802.1
000s, where multiple occurrences    1/dcn/11/    Closed   20110317 #72 I
                                    11-11-
were corrected.                     0416-02-
                                    000s-
                                    mcca-sb2-
                                    https://me
                                    ntor.ieee.
                                    org/802.1
 Replace sentence as indicated in   1/dcn/11/    Closed   20110317 #72 I
contriubution 11-11-0416r2.         11-11-
                                    0416-02-
                                    000s-
                                    mcca-sb2-
                                                 Closed   20110317 #72 I

                                                 Closed   20110317 #72 I

                                                 Closed   20110317 #72 I


                                                 Closed   20110317 #72 I



                                                 Closed   20110317 #72 I

                                  https://me
                                  ntor.ieee.
                                  org/802.1
 Replace sentence as indicated in 1/dcn/11/
                                                 Closed   20110317 #72 I
contriubution 11-11-0416r2        11-11-
                                  0416-02-
                                  000s-
                                  mcca-sb2-
                                  https://me
                                  ntor.ieee.
                                  org/802.1
 Replace sentence as indicated in 1/dcn/11/
                                                 Closed   20110317 #72 I
contriubution 11-11-0416r2        11-11-
                                  0416-02-
                                  000s-
                                  mcca-sb2-
                                  https://me
                                  ntor.ieee.
                                  org/802.1
 Replace sentence as indicated in 1/dcn/11/
                                                  Closed   20110317 #72 I
contriubution 11-11-0416r2        11-11-
                                  0416-02-
                                  000s-
                                  mcca-sb2-


                                                  Closed   20110317 #72 I




                                                  Closed   20110317 #72 I



                                                  Closed   20110317 #72 I

Change "(0 = non-mesh gate, 1 =
mesh gate)" to "(0 = gate
announcement protocol not
activated, 1 = gate announcement                  Closed   20110317 #77 I
protocol activated)"
also do this change in 7.3.2.112
(RANN element) page 59 line 22
The clause in mention was
reviewed and the task group                       Closed   20110317 #80 I
invites more review from the
                                     https://me
Decided to use the prependix         ntor.ieee.
"MCCA" for all frames. see           org/802.1
contribution 11-11-0416-02-000s,     1/dcn/11/    Closed   20110317 #72 I
                                     11-11-
where the change is                  0416-02-
implemented.                         000s-
                                     mcca-sb2-
                                                  Closed   20110317 #72 I

Replace "Mesh coordination
function (MCF)" with "MCCA                        Closed   20110317 #72 I
initialization"
The solution prevents DTIM
intervals to drift with respect to
each other. This ensures that
MCCAOP reservations can be
selected. The proposed solution,                  Closed   20110317 #72 I
on the other hand, begs the
question of how such a shared
DTIM value would be arrived at,
and requires a mechanism for
distributed decision making.
                                              Closed   20110317 #72 I
                                 https://me
                                 ntor.ieee.
see contribution 11-11-0416-02- org/802.1
000s, where multiple occurrences 1/dcn/11/    Closed   20110317 #72 I
                                 11-11-
were corrected.                  0416-02-
                                 000s-
                                 mcca-sb2-
Delete the last sentence of the
                                              Closed   20110317 #72 I
next paragraph

                                              Closed   20110317 #72 I

                                              Closed   20110317 #72 I

The formal style is consistent with
                                              Closed   20110317 #72 I
other parts of IEEE802.11-2007.

The formal style is consistent with
                                              Closed   20110317 #72 I
other parts of IEEE802.11-2007.


                                              Closed   20110317 #72 I



                                              Closed   20110317 #77 I


The clause in mention was
reviewed and the task group
                                              Closed   20110317 #80 I
invites more review from the
commenter.

                                              Closed   20110317 #77 I


                                              Closed   20110317 #72 I


                                              Closed   20110317 #72 I

                                              Closed   20110317 #72 I


                                              Closed   20110317 #72 I


                                              Closed   20110317 #72 I

                                              Closed   20110317 #72 I
                                                     Closed   20110317 #72 I


                                                     Closed   20110317 #72 I

Add the following text to the end      https://me
                                       ntor.ieee.
of the 11.1.2.3 (Beacon reception)
                                       org/802.1
in the base standard.                  1/dcn/11/
"STAs in an MBSS shall use             11-11-        Closed   20110317 #73 I
                                       0400-02-
information in received Beacon
                                       000s-mac-
frames as described in                 sync-
11C.12.3.2."                           beacon-
                                       resolution-
Add the following sentences to
11.1.3 (Acquiring synchronization,
scanning) in the base standard.
1. Add the following sentence to       https://me
the end of the 5th paragraph in        ntor.ieee.
                                       org/802.1
11.1.3.                                1/dcn/11/
"Note that MLME-JOIN.request           11-11-
primitive is not used to start         0400-02-      Closed   20110317 #73 I
                                       000s-mac-
synchronization in an MBSS. The        sync-
synchronization in an MBSS is          beacon-
described in 11C.12."                  resolution-
                                       text.doc
2. Add the following paragraph
after the 7th paragraph in 11.1.3.
"When scanning MBSSs, the STA
shall process the procedures
Add new subclause 11.1.2.2a   https://me
                              ntor.ieee.
Beacon generation in an MBSS
                                       org/802.1
as follows:                            1/dcn/11/
"11.1.2.2a Beacon generation in        11-11-        Closed   20110317 #73 I
                                       0400-02-
an MBSS
                                       000s-mac-
Beacon generation in an MBSS is        sync-
described in 11C.12.3.1."              beacon-
                                       resolution-
                                       https://me
                                 ntor.ieee.
look at 11.1.1.1. it talks about TSF
                                 org/802.1
for infrastructure networks. The 1/dcn/11/
base is not consistent. Suggest  11-11-              Closed   20110317 #73 I
                                 0400-02-
commenter to provide comment to
                                 000s-mac-
REVmb.                           sync-
                                 beacon-
                                 resolution-
                                      https://me
Add the following sentence to the ntor.ieee.
end of 11.1.1.3. "The             org/802.1
                                  1/dcn/11/
synchronization method in an
                                      11-11-        Closed   20110317 #73 I
MBSS is described in 11C.12.2         0400-02-
(Extensible synchronization           000s-mac-
                                      sync-
framework)."
                                      beacon-
                                      resolution-
Use square brackets for the listed
items here for now. (Publication
editor will be working on the final                 Closed   20110317 #78 I
style)
page 238 line 32, add bracket ")"
as it is missing.
The clause in mention was
reviewed and the task group                         Closed   20110317 #80 I
invites more review from the
Bit 0: 0 (gate role not applicable)                 Closed   20110317 #77 I


Bit 0: 0 (gate role not applicable)                 Closed   20110317 #77 I



Bit 0: 0 (gate role not applicable)                 Closed   20110317 #77 I


The clause in mention was
reviewed and the task group
                                                    Closed   20110317 #80 I
invites more review from the
commenter.
The clause in mention was
reviewed and the task group                         Closed   20110317 #80 I
invites more review from the
The clause in mention was
reviewed and the task group                         Closed   20110317 #80 I
invites more review from the
The clause in mention was
reviewed and the task group                         Closed   20110317 #80 I
invites more review from the
The clause in mention was
reviewed and the task group                         Closed   20110317 #80 I
invites more review from the
The clause in mention was
reviewed and the task group                         Closed   20110317 #80 I
invites more review from the
The clause in mention was
reviewed and the task group                         Closed   20110317 #80 I
invites more review from the
                                   https://me
                                   ntor.ieee.
                                   org/802.1
                                   1/dcn/11/
                                   11-11-        Closed   20110317 #73 I
                                   0400-02-
                                   000s-mac-
                                   sync-
                                   beacon-
                                   resolution-
It is SME's decision to which
neighbor STA to maintain                         Closed   20110317 #73 I
synchronization.
Change paragraph into: "When
dot11MeshActiveSynchronization
Method is 1 (Neighbor Offset        https://me
Synchronization), the mesh STA ntor.ieee.
                                    org/802.1
shall calculate the timing offset   1/dcn/11/
value with respect to the neighbor 11-11-
STA, with which it maintains        0400-02-     Closed   20110317 #73 I
                                    000s-mac-
synchronization. The calculation
                                    sync-
of the timing offset value is based beacon-
on time stamps from the received resolution-
                                    text.doc
Beacon and Probe Response
frames as follows:"
Also, change "neighbor mesh
                                   https://me
                                   ntor.ieee.
                                   org/802.1
                                   1/dcn/11/
                                   11-11-
                                   0400-02-      Closed   20110317 #73 I
                                   000s-mac-
                                   sync-
                                   beacon-
                                   resolution-
                                   text.doc
                                   https://me
                                   ntor.ieee.
                                   org/802.1
                                   1/dcn/11/
Refined text is provided in 11-
                                   11-11-        Closed   20110317 #73 I
11/400r2.                          0400-02-
                                   000s-mac-
                                   sync-
                                   beacon-
                                   resolution-
                                       https://me
                                       ntor.ieee.
                                       org/802.1
                                       1/dcn/11/
                                       11-11-        Closed   20110317 #73 I
                                       0400-02-
                                       000s-mac-
                                       sync-
                                       beacon-
                                       resolution-
As described in Annex D,
dot11MeshNbrOffsetMaxNeighbor
is a capability variable. This is
used to notify the SME of the
hardware capability/limitation in
                                                     Closed   20110317 #73 I
terms of how many neighbor
STAs can be tracked. Using this
information and the result from
scanning, the SME may select to
which neighbor STAs maintain
synchronization.

Many useful functions such as
MBCA, MCCA, and power save
usually relies on clock drift
compensation. Clock drift
compensation works only if mesh
STAs support this function
mutually. If there is a mesh STA
that does not support clock drift
compensation in a mesh BSS, the
mesh STA causes problems at                          Closed   20110317 #73 I
the neighbor mesh STAs. Thus, it
should be safe to define clock drift
compensation as a part of the
defalt synchronization method in
order to facilitate the
interoperability of mesh STAs that
leverage either MBCA, MCCA,
power save support or power
saving.
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/
Add "(a signed integer)" to the
                                      11-11-        Closed   20110317 #73 I
end of the sentence.                  0400-02-
                                      000s-mac-
                                      sync-
                                      beacon-
                                      resolution-
"allowing" is more reader friendly
                                                    Closed   20110317 #73 I
in this context.
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/
Resolution to CID2219 resolve
                                      11-11-        Closed   20110317 #73 I
this problem.                         0400-02-
                                      000s-mac-
                                      sync-
                                      beacon-
                                      resolution-
It is clear that -5 < +3.                           Closed   20110317 #73 I

Change the paragraph and the
lettered item a) and b) as follows:
"When the mesh STA receives a
Beacon frame or a Probe
Response frame from one of the
neighbor STAs with which it
maintains synchronization, the
mesh STA shall operate the         https://me
following clock drift compensation ntor.ieee.
                                      org/802.1
procedure:                            1/dcn/11/
a) If the mesh STA does not have      11-11-
a valid Toffset value obtained        0400-02-      Closed   20110317 #73 I
                                      000s-mac-
from the previous Beacon or           sync-
Probe Response frame reception        beacon-
from the transmitter of the Beacon    resolution-
                                      text.doc
frame or Probe Response frame,
it shall not perform the following
steps.
b) The mesh STA shall calculate
the clock drift amount TClockDrift
by comparing the Toffset obtained
previously for this neighbor STA
and the Toffset obtained from the
It is clock drift adjustment. It is
done through TSF adjustment. No                     Closed   20110317 #73 I
need to change the text here.
                                      https://me
                                      ntor.ieee.
                                      org/802.1
Change the sentence to read "it       1/dcn/11/
shall not perform the following       11-11-        Closed   20110317 #73 I
                                      0400-02-
steps.".
                                      000s-mac-
                                      sync-
                                      beacon-
                                      resolution-
The clock drift is adusted in a
single direction (to be aligned to
the slowest TSF counting). So,
the significant flapping will be                    Closed   20110317 #73 I
avoided although it may introduce
some jitter depeding on the clock
drift compensation                 https://me
                                   ntor.ieee.
                                   org/802.1
Change index "0" to "c", and       1/dcn/11/
change index "1" to "p" throughout 11-11-           Closed   20110317 #73 I
                                   0400-02-
the clause 11C.12.
                                   000s-mac-
                                   sync-
                                   beacon-
                                   resolution-
                                   https://me
                                  ntor.ieee.
                                  org/802.1
                                  1/dcn/11/
Replace "counting frequency" with
                                  11-11-            Closed   20110317 #73 I
"counting".                       0400-02-
                                  000s-mac-
                                  sync-
                                  beacon-
                                  resolution-
It is already described in        https://me
                                      ntor.ieee.
10.3.79.3. It is helpful to have this
                                     org/802.1
kind of sentence in MLME. See        1/dcn/11/
11.1.3 in the base standard.         11-11-
                                     0400-02-       Closed   20110317 #73 I
By the way, "xx.request" shall be
                                     000s-mac-
changed to "xx.request primitive",   sync-
"xx.confirm" shall be changed to     beacon-
                                     resolution-
"xx.confirm primitive". Check for it
                                     text.doc
throughout this clause.              https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
                                     11-11-         Closed   20110317 #73 I
                                     0400-02-
                                     000s-mac-
                                     sync-
                                     beacon-
                                     resolution-
See resolution to CID2190 as
well.
Clause 11.1 of the base standard
describes "Synchronization". This
implies that the beaconing and
synchronizatioon is tightly coupled
for infrastructure BSS and IBSS.
                                 https://me
However, Mesh BSS decouples
                                 ntor.ieee.
beaconing and synchronization.   org/802.1
Thus, it should not be good idea 1/dcn/11/
                                 11-11-
to describe the rationale of mesh
                                 0400-02-           Closed   20110317 #73 I
beaconing and synchronization in 000s-mac-
a separate subclause such as     sync-
                                 beacon-
11C.12.
                                 resolution-
However, it should be reasonable text.doc
to define a new subclause
11.1.2.2a describing beacon
generation in an MBSS, in parallel
with infrastructure BSS and IBSS.
Add the following new subclause
leaving a pointer information.
"11.1.2.2a Beacon generation in
See resolution to CID2225, 2188. https://me
                                  ntor.ieee.
Add the following text to the end
                                      org/802.1
of the 11.1.2.3 (Beacon reception)    1/dcn/11/
in the base standard.                 11-11-        Closed   20110317 #73 I
                                      0400-02-
"STAs in an MBSS shall use
                                      000s-mac-
information in received Beacon        sync-
frames as described in                beacon-
                                      resolution-
11C.12.3.2."                          https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/
                                      11-11-        Closed   20110317 #73 I
                                      0400-02-
                                      000s-mac-
                                      sync-
                                      beacon-
                                      resolution-
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/
                                      11-11-        Closed   20110317 #73 I
                                      0400-02-
                                      000s-mac-
                                      sync-
                                      beacon-
                                      resolution-
Replace
"A mesh STA shall use
information from the Timestamp
field without regard for the BSSID
or Mesh ID, if the mesh STA             https://me
                                        ntor.ieee.
maintains synchronization with
                                        org/802.1
the transmitter of the Beacon           1/dcn/11/
frame, to obtain information            11-11-
necessary for synchronization."
                                        0400-02-      Closed   20110317 #73 I
                                        000s-mac-
with                                    sync-
"A mesh STA shall use                   beacon-
                                        resolution-
information from the Timestamp
                                        text.doc
field without regard for the BSSID
or Mesh ID in order to obtain
information necessary for
synchronization, if the mesh STA
maintains synchronization with   https://me
                                        ntor.ieee.
                                        org/802.1
                                        1/dcn/11/
                                        11-11-        Closed   20110317 #73 I
                                        0400-02-
                                        000s-mac-
                                        sync-
                                        beacon-
                                        resolution-
                                        https://me
                                        ntor.ieee.
                                        org/802.1
                                        1/dcn/11/
                                        11-11-        Closed   20110317 #73 I
                                        0400-02-
                                        000s-mac-
                                        sync-
                                        beacon-
                                        resolution-
                                        https://me
                                        ntor.ieee.
                                        org/802.1
Change "neighbor STA                    1/dcn/11/
identification" to "identifier of the   11-11-        Closed   20110317 #73 I
                                        0400-02-
neighbor STA".
                                        000s-mac-
                                        sync-
                                        beacon-
                                        resolution-
                                        https://me
                                        ntor.ieee.
                                        org/802.1
                                        1/dcn/11/
                                        11-11-        Closed   20110317 #73 I
                                        0400-02-
                                        000s-mac-
                                        sync-
                                        beacon-
                                        resolution-
                                        https://me
                                        ntor.ieee.
Wording:
                                        org/802.1
Change the sentence to read "is         1/dcn/11/
the TBTT calculated when the            11-11-        Closed   20110317 #73 I
                                        0400-02-
latest status number update
                                        000s-mac-
occurs"                                 sync-
                                        beacon-
                                        resolution-
The index do not need to be in
                                                      Closed   20110317 #73 I
increasing order in time.
                                        https://me
                                        ntor.ieee.
                                        org/802.1
                                        1/dcn/11/
                                        11-11-        Closed   20110317 #73 I
                                        0400-02-
                                        000s-mac-
                                        sync-
                                        beacon-
                                        resolution-
                                        https://me
                                        ntor.ieee.
                                        org/802.1
                                        1/dcn/11/
                                        11-11-        Closed   20110317 #73 I
                                        0400-02-
                                        000s-mac-
                                        sync-
                                        beacon-
                                        resolution-
It is clear from the context. It is a
                                                      Closed   20110317 #73 I
arbitrary neighbor STA.
Replace
"is initialized with 0 and
incremented by 1 before
transmitting a frame containing         https://me
the Beacon Timing element when          ntor.ieee.
                                        org/802.1
the mesh STA encountered any of         1/dcn/11/
the following events since it has       11-11-
updated the status number               0400-02-      Closed   20110317 #73 I
                                        000s-mac-
previously:"                            sync-
with                                    beacon-
"is initialized with 0. It is           resolution-
                                        text.doc
incremented by 1 before
transmitting a frame containing
the Beacon Timing element, when
the mesh STA encountered any of
Status number is not a counter. It
is a number given from the                          Closed   20110317 #73 I
counter.

MBCA text structure:
Replace the last paragraph in
11C.12.4.1 with the following text:
"MBCA is composed of beacon
timing advertisement, TBTT
selection, and TBTT adjustment.
When dot11MBCAActivated is
true, the mesh STA advertises the https://me
TBTT and beacon interval of its       ntor.ieee.
                                      org/802.1
neighbor STAs through the             1/dcn/11/
Beacon Timing element as              11-11-
described in 11C.12.4.2 (Beacon       0400-02-      Closed   20110317 #73 I
                                      000s-mac-
timing advertisement). The            sync-
receiver of the Beacon Timing         beacon-
element obtains the beacon            resolution-
                                      text.doc
reception timing of its neighbor
mesh STAs and uses this
information for its TBTT selection
and TBTT adjustment as
described in 11C.12.4.3 (TBTT
selection) and 11C.12.4.4 (TBTT
adjustment). The mesh STA may
also perform additional
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/
                                      11-11-        Closed   20110317 #73 I
                                      0400-02-
                                      000s-mac-
                                      sync-
                                      beacon-
                                      resolution-
"in such case" is more reader
                                                    Closed   20110317 #73 I
friendly in this context.
The intention of this sentence is
that a Beacon Timing element
only includes one tuple. How the
tuples are included in the Beacon
Timing element is described later
                                                   Closed   20110317 #73 I
in this subclause.




                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
                                     11-11-        Closed   20110317 #73 I
                                     0400-02-
                                     000s-mac-
                                     sync-
                                     beacon-
                                     resolution-
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
                                     11-11-        Closed   20110317 #73 I
                                     0400-02-
                                     000s-mac-
                                     sync-
                                     beacon-
                                     resolution-
The sentence is reader friendly
                                                   Closed   20110317 #73 I
enough.
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
                                     11-11-
                                     0400-02-      Closed   20110317 #73 I
                                     000s-mac-
                                     sync-
                                     beacon-
                                     resolution-
                                     text.doc
"524 228" is encouraged by the
style manual. See 15.4.2                           Closed   20110317 #73 I
(Numerical values) in IEEE
Standards Style Manual.
There is no need to do it. It is a
fixed number dervied from the                      Closed   20110317 #73 I
length of the field.
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/
                                      11-11-        Closed   20110317 #73 I
                                      0400-02-
                                      000s-mac-
                                      sync-
                                      beacon-
                                      resolution-
                                      https://me
                                ntor.ieee.
Remove ", using the information org/802.1
                                1/dcn/11/
obtained from the Beacon Timing
                                11-11-              Closed   20110317 #73 I
element from its neighbor mesh  0400-02-
STAs"                           000s-mac-
                                sync-
                                beacon-
                                resolution-
MBCA text structure:
Replace the last paragraph in
11C.12.4.1 with the following text:
"MBCA is composed of beacon
timing advertisement, TBTT
selection, and TBTT adjustment.
When dot11MBCAActivated is
true, the mesh STA advertises the     https://me
TBTT and beacon interval of its       ntor.ieee.
                                      org/802.1
neighbor STAs through the             1/dcn/11/
Beacon Timing element as              11-11-
described in 11C.12.4.2 (Beacon       0400-02-      Closed   20110317 #73 I
                                      000s-mac-
timing advertisement). The            sync-
receiver of the Beacon Timing         beacon-
element obtains the beacon            resolution-
                                      text.doc
reception timing of its neighbor
mesh STAs and uses this
information for its TBTT selection
and TBTT adjustment as
described in 11C.12.4.3 (TBTT
selection) and 11C.12.4.4 (TBTT
adjustment). The mesh STA may
also perform additional
                             https://me
                             ntor.ieee.
                             org/802.1
                             1/dcn/11/
Replace "beacon reception    11-11-
timing" with "beaon timing   0400-02-      Closed   20110317 #73 I
information".                000s-mac-
                             sync-
                             beacon-
                             resolution-
                             text.doc

                             https://me
                             ntor.ieee.
                             org/802.1
                             1/dcn/11/
                             11-11-        Closed   20110317 #73 I
                             0400-02-
                             000s-mac-
                             sync-
                             beacon-
                             resolution-
                             https://me
                             ntor.ieee.
                             org/802.1
                             1/dcn/11/
                             11-11-        Closed   20110317 #73 I
                             0400-02-
                             000s-mac-
                             sync-
                             beacon-
                             resolution-
                             https://me
                             ntor.ieee.
                             org/802.1
                             1/dcn/11/
                             11-11-        Closed   20110317 #73 I
                             0400-02-
                             000s-mac-
                             sync-
                             beacon-
                             resolution-
                             https://me
                             ntor.ieee.
                             org/802.1
                             1/dcn/11/
                             11-11-        Closed   20110317 #73 I
                             0400-02-
                             000s-mac-
                             sync-
                             beacon-
                             resolution-
                                       https://me
                                       ntor.ieee.
                                       org/802.1
                                       1/dcn/11/
                                       11-11-        Closed   20110317 #73 I
                                       0400-02-
                                       000s-mac-
                                       sync-
                                       beacon-
                                       resolution-
The comment is not specific to a
particular issue.
Anyway... As indicated in
resolution to CID2266, the TBTT
scanning procedure is intended                       Closed   20110317 #73 I
for the mesh STAs in deep sleep
mode. It should be necessary for
mesh STAs in deep sleep mode
to collect the up-to-date beacon
information before adjusting
TBTT adjustment should be its
activated as a last resort bailout.
The procedure for proactive TBTT
adjustment is intended to avoid
false positive initiation, which can
cause flapping of TBTT adjustmen                     Closed   20110317 #73 I
among multiple mesh STAs. So, a
mesh STA does not initiate the
procedure unless it recognize that
it really needs to move its TBTT.
From this sense, the described
                                       https://me
                                       ntor.ieee.
The text has been modified to          org/802.1
                                       1/dcn/11/
describe the procedure more
                                       11-11-        Closed   20110317 #73 I
accurately. See submission 11-         0400-02-
11/400r2.                              000s-mac-
                                       sync-
                                       beacon-
                                       resolution-
                                       https://me
                                       ntor.ieee.
                                       org/802.1
                                       1/dcn/11/
                                       11-11-        Closed   20110317 #73 I
                                       0400-02-
                                       000s-mac-
                                       sync-
                                       beacon-
                                       resolution-
As written in this subclause, the
TBTT selection procedure
described in 11C.12.4.3 is
performed during the mesh
discovery process. This means
that beacon timing information are
gathered without establishing         https://me
                                      ntor.ieee.
synchronization with its              org/802.1
neighbors.                            1/dcn/11/
To make it clear, insert the          11-11-
                                      0400-02-      Closed   20110317 #73 I
following paragraph after the first   000s-mac-
paragraph in 11C.2.8 (11C.2           sync-
Establishing or becoming a            beacon-
                                      resolution-
member of a mesh BSS).                text.doc
"When dot11MBCAActivated is
true, the mesh STA shall perform
TBTT selection procedure
described in 11C.12.4.3 (TBTT
selection) using TimeStamp,
Local Time, and Beacon Timing in
the BSSDescription parameter
The comment is not specific to a
                                                    Closed   20110317 #73 I
particular issue.

This process is intended for the https://me
                                 ntor.ieee.
mesh STAs in deep sleep mode.
                                 org/802.1
It should be necessary for mesh 1/dcn/11/
STAs in deep sleep mode to       11-11-
                                 0400-02-           Closed   20110317 #73 I
collect the up-to-date beacon
                                 000s-mac-
information before adjusting its sync-
TBTT. To make this clear, modify beacon-
                                 resolution-
the text in 11C.12.4.4.3 as
                                 text.doc
implemented in 11-11/400r2.
TBTT adjustment should be
activated as a last resort bailout,
and false positive initiation, which
can cause flapping of TBTT
adjustmen among multiple mesh
STAs, should be strictly avoided.
Setting the TBTT Adjusting field in
the Mesh Config element to 1
signals that the mesh STA is                       Closed   20110317 #73 I
already in the process of TBTT
adjustment and it is helpful to
avoid unnecessary (false positive)
initiation of TBTT adjustment at
the other mesh STAs. To leverage
the benefit of this bit setting,
modify the condition to request a
TBTT adjustment to its neighbor
mesh STA, in clause
                                                   Closed   20110317 #72 I

The clause in mention was
reviewed and the task group                        Closed   20110317 #80 I
invites more review from the
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
                                       0447-00-
                                       000s-
                                       peering-
                                       manage
See contribution 11-11/0447r0          ment-
                                                   Closed   20110317 #76 I
and 11-11-0452r1                       reorg.do
                                       c
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
                                       0452-01-
                                       000s-
                                       state-
                                       machine-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0447-00-
                                000s-
                                peering-
                                manage
See contribution 11-11/0447r0   ment-
                                            Closed   20110317 #76 I
and 11-11-0452r1                reorg.do
                                c
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0452-01-
                                000s-
                                state-
                                machine-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0447-00-
                                000s-
                                peering-
                                manage
See contribution 11-11/0447r0   ment-
                                            Closed   20110317 #76 I
and 11-11-0452r1                reorg.do
                                c
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0452-01-
                                000s-
                                state-
                                machine-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0447-00-
                                000s-
                                peering-
                                manage
See contribution 11-11/0447r0   ment-
                                            Closed   20110317 #76 I
and 11-11-0452r1                reorg.do
                                c
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0452-01-
                                000s-
                                state-
                                machine-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0447-00-
                                000s-
                                peering-
                                manage
See contribution 11-11/0447r0   ment-
                                            Closed   20110317 #76 I
and 11-11-0452r1                reorg.do
                                c
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0452-01-
                                000s-
                                state-
                                machine-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0447-00-
                                000s-
                                peering-
                                manage
See contribution 11-11/0447r0   ment-
                                            Closed   20110317 #76 I
and 11-11-0452r1                reorg.do
                                c
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0452-01-
                                000s-
                                state-
                                machine-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0447-00-
                                000s-
                                peering-
                                manage
See contribution 11-11/0447r0   ment-
                                            Closed   20110317 #76 I
and 11-11-0452r1                reorg.do
                                c
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0452-01-
                                000s-
                                state-
                                machine-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0447-00-
                                000s-
                                peering-
                                manage
See contribution 11-11/0447r0   ment-
                                            Closed   20110317 #76 I
and 11-11-0452r1                reorg.do
                                c
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                0452-01-
                                000s-
                                state-
The clause in mention was       machine-
reviewed and the task group
                                            Closed   20110317 #80 I
invites more review from the
commenter.




The clause in mention was
reviewed and the task group
                                            Closed   20110317 #80 I
invites more review from the
commenter.
The clause in mention was
reviewed and the task group
                               Closed   20110317 #80 I
invites more review from the
commenter.




The clause in mention was
reviewed and the task group
                               Closed   20110317 #80 I
invites more review from the
commenter.




                               Closed   20110317 #78 I




The clause in mention was
reviewed and the task group
                               Closed   20110317 #80 I
invites more review from the
commenter.
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/     Closed   20110317 #70 I
                                    11-11-
                                    0329-01-
                                    000s-
                                    seccomre
                                    https://me
                                    ntor.ieee.
                                    org/802.1
See submission 11-11-0425-01-       1/dcn/11/
                                    11-11-        Closed   20110317 #78 I
000s for comment resolution.
                                    0425-01-
                                    000s-
                                    resolution-
                                    to-cid-
This observation is highly
subjective. The comment lacks
instructions which details of the                 Closed   20110317 #78 I
figures do not comply with the
base standard's appearance.
The observation with respect to
Figure 5-6b is highly subjective.   https://me
The comment lacks instructions      ntor.ieee.
which details of the figures do not org/802.1
                                    1/dcn/11/
comply with the base standard's     11-11-
appearance. Also figure 5-6b        0423-00-
                                                  Closed   20110317 #78 R
does not relate to Clause 5.3.2.    000s-
                                    resolution-
Thus, we propose to keep Figure     to-
5-6b unchanged. However,            comment-
submission 11-11-0423-00-000s       cid-
                                    2287.doc
contains a resolution to the
second part of the comment that
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/     Closed   20110317 #70 I
                                    11-11-
                                    0329-01-
                                    000s-
                                    seccomre


                                                  Closed   20110317 #72 I
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/
Submission 11-11-0420-01-000s 11-11-
contains the inclusion of 802.1X in 0420-01-      Closed   20110317 #71 I
                                    000s-
802.11s
                                    adding-
                                    802-1x-
                                    authentic
                                    ation-
Change the paragraph to read:       support-to-

"In a mesh STA when
dot11ESNetwork is false, it is
unable to support the mesh
peering of emergency service and
ESR shall be set to 0. When that
                                                  Closed   20110317 #78 I
mesh STA receives a Mesh
Peering Open frame, that includes
the Interworking element with the
ASRA bit equal to 1, it is unable to
support the mesh peering of
emergency service."
             Edited
Edit Notes
             in Draft


                9.01



                9.01




                9.01




                9.01




                9.01




                9.01




                9.01




                9.01




                9.01
 9.01




 9.01




 9.01




 9.01




 9.01




NC




 9.01
9.01




9.01




9.01




9.01




9.01




9.01




9.01
 9.01




 9.01




 9.01




 9.01




 9.01




 9.01




NC




 9.01
 9.01




 9.01




 9.01




NC




 9.01




 9.01




 9.01




 9.01
9.01




9.01




9.01




9.01




9.01




9.01



9.01



9.01



9.01




9.01




9.01
9.01




9.01



9.01



9.01



9.01



9.01




9.01




9.01



9.01
 9.01




 9.01

 9.01

 9.01

 9.01


 9.01



 9.01



 9.01


NC




 9.01




 9.01
 9.01




 9.01




NC




NC




 9.01




 9.01




 9.01




 9.01
9.01




9.01




9.01




9.01


9.01

9.01




9.01




9.01




9.01
                              9.01




                              9.01




                              9.01



Clause 5 shall not contain
normative language. It
should be written in
declarative language. ->
changed to delarative         9.01
language.
Also, other normative
language in clause 5 is
changed to declarative
language.
                              9.01



                             NC



                             NC




                              9.01




                              9.01
9.01




9.01


9.01




9.01




9.01


9.01


9.01

9.01


9.01


9.01


9.01


9.01
NC




 9.01




 9.01




 9.01




 9.01




 9.01


 9.01


 9.01
                              9.01



                              9.01



per resolution to other CID   9.01

implemented as follows:
"STAs in a mesh BSS
might be sources, sinks or
propagators of traffic;
some mesh STAs might
only propagate traffic for
other STAs. As described      9.01
in 5.2.14.4 (IEEE 802.11
components and mesh
BSS), a mesh BSS might
have interfaces to external
networks and can be
utilized as a backhaul for

                              9.01




                              9.01




                              9.01


                              9.01
                         9.01




                         9.01




Replace "between" with
                         9.01
"among"
                        9.01




Note:
Also, "Mesh Group Key
Handshake" to "mesh
group key handshake".
"Mesh GTK, Mesh         9.01
PMKSA, Mesh TKSA,
Mesh GTKSA" to "mesh
GTK, mesh PMKSA, mesh
TKSA, mesh GTKSA".
 9.01




 9.01




 9.01




NC
                             NC




                              9.01




This resolution conflicts
with 802.11 style guide.
                              9.01
Recommend CRC to
revisit its applicability.
 9.01




 9.01




 9.01

NC
                           NC




                            9.01


                            9.01

Do not leave anything in
                            9.01
this column if it is not


                            9.01




                           NC




                            9.01




                            9.01
9.01




9.01




9.01




9.01

9.01

9.01


9.01



9.01




9.01




9.01
 9.01




 9.01




 9.01



 9.01




 9.01




NC




 9.01




 9.01


 9.01




 9.01
 9.01




 9.01




 9.01


 9.01

 9.01


 9.01



 9.01



 9.01



 9.01




NC



 9.01


 9.01


 9.01

 9.01


 9.01


 9.01

 9.01
9.01


9.01




9.01




9.01




9.01




9.01
 9.01




 9.01




NC


 9.01


 9.01



 9.01




NC




NC



NC



NC



NC



NC



NC
 9.01




NC




 9.01




 9.01




 9.01
 9.01




NC




NC
 9.01




NC




 9.01




NC




 9.01




NC
 9.01




NC




 9.01




 9.01




 9.01




 9.01
9.01




9.01




9.01




9.01
9.01




9.01




9.01




9.01




9.01
 9.01




NC




 9.01




 9.01




NC




 9.01
NC




 9.01




 9.01




NC
NC




 9.01




 9.01




NC




 9.01




NC



NC
9.01




9.01




9.01
9.01




9.01




9.01




9.01




9.01
 9.01




NC




NC




 9.01




 9.01
 9.01




NC




 9.01
 9.01




 9.01



NC




 9.01
9.01




9.01
9.01




9.01
9.01




9.01
 9.01




NC




NC
                            NC




                            NC




Changed as follows:
0 Mesh Link Metric Report
1 HWMP Mesh Path
Selection
2 Gate Announcement
3 Congestion Control
Notification
4 MCCA Setup Request         9.01
5 MCCA Setup Reply
6 MCCA Advertisement
Request
7 MCCA Advertisement
8 MCCA Teardown
9 TBTT Adjustment
Request



                            NC
                               9.01




                               9.01




                              NC




Submission 11-11/423
breaks the context in the
base standard. For that
reason, this resolution is
not implemented.              NC
Recommend CRC to
revisit how to address this
issue and provide an
alternative resolution.




                               9.01




                               9.01
9.01




9.01
                 Must   Categor Subclaus Pag Lin                Issue
CID    Name                                             Topic
                 Be     y         e        e        e           ID




       Struik,          Technic                         Secu
1001             Yes                   8       89               S-SAE
       Rene             al                              rity
       Struik,         Technic            Secu
1002             Yes             8   91          S-SAE
       Rene            al                 rity




       Struik,         Technic            Secu
1003             Yes             8   90          S-SAE
       Rene            al                 rity
       Struik,         Technic            Secu
1004             Yes             8   90          S-SAE
       Rene            al                 rity




       Struik,         Technic            Secu
1005             Yes             8   90          S-SAE
       Rene            al                 rity




       Struik,         Technic            Secu
1006             Yes             8   90          S-SAE
       Rene            al                 rity
       Struik,         Technic              Secu
1007             Yes               8   90          S-SAE
       Rene            al                   rity




       Struik,                              Secu
1008             Yes   Editorial   8   90          S-SAE
       Rene                                 rity




       Struik,         Technic              Secu
1009             Yes               8   90          S-SAE
       Rene            al                   rity
       Struik,         Technic            Secu
1010             Yes             8   89          S-SAE
       Rene            al                 rity




       Struik,         Technic            Secu
1011             Yes             8   89          S-SAE
       Rene            al                 rity
       Struik,         Technic            Secu
1012             Yes             8   88          S-SAE
       Rene            al                 rity
       Struik,         Technic            Secu
1013             Yes             8   87          S-SAE
       Rene            al                 rity




       Struik,         Technic            Secu
1014             Yes             8   87          S-SAE
       Rene            al                 rity
       Struik,         Technic            Secu
1015             Yes             8   87          S-SAE
       Rene            al                 rity




       Struik,         Technic            Secu
1016             Yes             8   87          S-SAE
       Rene            al                 rity




       Struik,         Technic            Secu
1017             Yes             8   86          S-SAE
       Rene            al                 rity
       Struik,         Technic            Secu
1018             Yes             8   86          S-SAE
       Rene            al                 rity




       Struik,         Technic            Secu
1019             Yes             8   86          S-SAE
       Rene            al                 rity
       Struik,         Technic              Secu
1020             Yes               8   86          S-SAE
       Rene            al                   rity




       Struik,                              Secu
1021             Yes   Editorial   8   86          S-SAE
       Rene                                 rity




       Struik,                              Secu
1022             Yes   Editorial   8   86          S-SAE
       Rene                                 rity
       Struik,                              Secu
1023             Yes   Editorial   8   86          S-SAE
       Rene                                 rity




       Struik,         Technic              Secu
1024             Yes                   86          S-SAE
       Rene            al                   rity
       Struik,          Technic                    Secu
1025              Yes               8   84                S-SAE
       Rene             al                         rity




       Chaplin,                                    Gene G-
1026              No    Editorial       127   35
       Clint                                       ral    Editor




       Chaplin,                                    Gene G-
1027              No    Editorial       126   23
       Clint                                       ral    Editor




       Chaplin,                                           M-
1028              No    Editorial       120   5 MAC
       Clint                                              MCCA
       Chaplin,                                           Gene G-
1029              No   Editorial               105   55
       Clint                                              ral  Editor
       Chaplin,                                           Gene G-
1030              No   Editorial               100   62
       Clint                                              ral    Editor


       Chaplin,        Technic                            Gene G-
1031              No                           100   15
       Clint           al                                 ral    Editor




       Chaplin,        Technic                            Secu
1032              No                           84    50          S-SAE
       Clint           al                                 rity




                                                                 S-
       Chaplin,                                           Secu
1033              No   Editorial               83    26          Gener
       Clint                                              rity
                                                                 al




       Chaplin,                                           Gene G-
1034              No   Editorial               53    1
       Clint                                              ral    Editor


       Chaplin,                                           Gene G-
1035              No   Editorial               24    6
       Clint                                              ral    Editor


       Chaplin,                                           Gene G-
1036              No   Editorial               14    46
       Clint                                              ral  Editor
       Chaplin,                                           Gene G-
1037              No   Editorial               12    35
       Clint                                              ral  Editor
       Hiertz,                     9.9a.3.11              Gene G-
1038              No   Editorial               120   2
       Guido                       .2                     ral    Editor
       Hiertz,        Technic                             M-
1039             No             9.9a.3.7   115   51 MAC
       Guido          al                                  MCCA




       Hiertz,        Technic                             M-
1040             No             9.9a.3.7   115   33 MAC
       Guido          al                                  MCCA




       Hiertz,                                            M-
1041             No   General 9.9a.3.3     113   50 MAC
       Guido                                              MCCA




       Hiertz,        Technic                             M-
1042             No                        111   59 MAC
       Guido          al                                  MCCA
       Bahr,           Technic                         Secu S-
1043             Yes             7.3.2.0a    37   62
       Michael         al                              rity   MPM




       Bahr,           Technic                                R-
1044             Yes             7.3.2.0a    37   54 RFI
       Michael         al                                     Proxy




       Bahr,           Technic                                R-
1045             No              7.3.2.112   62   61 RFI
       Michael         al                                     HWMP




       Bahr,           Technic                                R-
1046             Yes             7.3.2.0a    37   52 RFI
       Michael         al                                     HWMP
       Bahr,           Technic                             R-
1047             Yes             7.3.2.0a    37   51 RFI
       Michael         al                                  HWMP




       Bahr,           Technic                             R-
1048             Yes             7.3.2.0a    37   49 RFI
       Michael         al                                  HWMP




       Bahr,           Technic                             M-
1049             No              7.3.2.107   56   44 MAC
       Michael         al                                  MCCA




       Bahr,           Technic                             M-
1050             Yes             7.3.2.0a    37   43 MAC
       Michael         al                                  MCCA
       Bahr,           Technic                                M-
1051             No              7.3.2.105   53   46 MAC
       Michael         al                                     MCCA




                                                              S-
       Bahr,           Technic                         Secu
1052             Yes             7.3.2.0a    37   29          Gener
       Michael         al                              rity
                                                              al




       Bahr,           Technic
1053             Yes             7.3.2.0a    37   25 RFI      R-LM
       Michael         al




                                                              R-
       Bahr,           Technic
1054             No              7.3.2.108   57    1 RFI      MeshG
       Michael         al
                                                              ate
       Bahr,           Technic                                 R-
1055             No                7.4.16.3   82    35 RFI
       Michael         al                                      Proxy




       Bahr,                                             Gene G-
1056             No    Editorial 7.4.16.3     81    59
       Michael                                           ral   Editor



       Bahr,                                             Gene G-
1057             No    Editorial 7.4.16.2     81    35
       Michael                                           ral   Editor



       Bahr,                                             Gene G-
1058             No    Editorial 7.4.16.2     81    20
       Michael                                           ral   Editor




       Bahr,           Technic 11C.10.4                        R-
1059             Yes                          262    5 RFI
       Michael         al          .3                          Proxy




       Bahr,                       11C.10.4                    R-
1060             No    Editorial              264   12 RFI
       Michael                     .4.3                        Proxy
       Bahr,           Technic 11C.10.4                        R-
1061             Yes                          263   55 RFI
       Michael         al          .4.2                        Proxy




       Bahr,                       11C.10.4              Gene G-
1062             No    Editorial              263   53
       Michael                     .4.2                  ral  Editor
       Bahr,                       11C.10.4              Gene G-
1063             No    Editorial              262   21
       Michael                     .3.2                  ral   Editor
       Bahr,                       11C.10.4              Gene G-
1064             No    Editorial              262   60
       Michael                     .3.4                  ral   Editor

       Bahr,                       11C.10.4              Gene G-
1065             No    Editorial              262   45
       Michael                     .3.4                  ral  Editor
       Bahr,                       11C.10.4              Gene G-
1066             No    Editorial              262   42
       Michael                     .3.3                  ral   Editor




       Bahr,           Technic 11C.10.4                        R-
1067             No                           262   25 RFI
       Michael         al          .3.2                        Proxy




       Bahr,                       11C.10.4              Gene G-
1068             No    Editorial              262   24
       Michael                     .3.2                  ral   Editor

       Bahr,                       11C.10.4              Gene G-
1069             No    Editorial              262   18
       Michael                     .3.2                  ral   Editor

       Bahr,                       11C.10.4              Gene G-
1070             No    Editorial              261   44
       Michael                     .2                    ral   Editor
       Bahr,                       11C.10.4              Gene G-
1071             No    Editorial              261   32
       Michael                     .1                    ral   Editor
       Bahr,           Technic                               R-
1072             Yes             7.3.2.113   64    1 RFI
       Michael         al                                    Proxy




       Bahr,                                                 R-
1073             No    Editorial 7.3.2.114   65   19 RFI
       Michael                                               Proxy




       Bahr,                                           Gene G-
1074             No    Editorial 7.3.2.113   65    2
       Michael                                         ral   Editor




       Bahr,           Technic                               R-
1075             Yes             7.3.2.113   64   61 RFI
       Michael         al                                    Proxy




       Bahr,                                           Gene G-
1076             No    Editorial 7.3.2.113   64   21
       Michael                                         ral   Editor


       Bahr,                                           Gene G-
1077             No    Editorial 7.3.2.113   64   19
       Michael                                         ral   Editor
       Bahr,                                              Gene G-
1078             No    Editorial 7.3.2.113     64    18
       Michael                                            ral   Editor

       Bahr,                       11C.9.9.               Gene G-
1079             No    Editorial               243   48
       Michael                     3                      ral   Editor




       Bahr,           Technic                                  R-
1080             Yes               7.3.2.113   64    12 RFI
       Michael         al                                       Proxy




       Bahr,           Technic                                  M-
1081             Yes               9.9a.3.9    117   44 MAC
       Michael         al                                       MCCA
       Bahr,          Technic                             M-
1082             No             9.9a.3.9   117   42 MAC
       Michael        al                                  MCCA




       Bahr,
1083             No   Editorial 9.9a.3.9   117   42 MAC M-BS
       Michael




       Bahr,                                              M-
1084             No   Editorial 9.9a.3.9   117   42 MAC
       Michael                                            MCCA
       Bahr,           Technic                          M-
1085             Yes             9.9a.3   112   1 MAC
       Michael         al                               MCCA




       Bahr,           Technic                          M-
1086             Yes             9.9a.3   112   1 MAC
       Michael         al                               MCCA
       Bahr,           Technic 7.3.2.106                   M-
1087             Yes                        55    16 MAC
       Michael         al        .2                        MCCA




       Bahr,           Technic                             M-
1088             Yes             9.9a.3.8   116   32 MAC
       Michael         al                                  MCCA
       Bahr,           Technic                             M-
1089             Yes             9.9a.3.8   116   32 MAC
       Michael         al                                  MCCA




       Bahr,           Technic 7.3.2.106                   M-
1090             Yes                        56    1 MAC
       Michael         al        .2                        MCCA
       Bahr,           Technic 7.3.2.106                 M-
1091             Yes                       55   16 MAC
       Michael         al      .2                        MCCA
       Bahr,           Technic                             M-
1092             Yes             9.9a.3.8   116   32 MAC
       Michael         al                                  MCCA




       Bahr,           Technic                             M-
1093             Yes             9.9a.3.8   116   32 MAC
       Michael         al                                  MCCA
       Bahr,           Technic                             M-
1094             Yes             9.9a.3.8   117   11 MAC
       Michael         al                                  MCCA




       Bahr,           Technic                             M-
1095             Yes             9.9a.3.8   117   1 MAC
       Michael         al                                  MCCA
       Bahr,           Technic                             M-
1096             Yes             9.9a.3.8   116   61 MAC
       Michael         al                                  MCCA




       Bahr,           Technic                             M-
1097             Yes             9.9a.3.8   116   61 MAC
       Michael         al                                  MCCA
       Bahr,                                               M-
1098             No    Editorial 9.9a.3.8   116   59 MAC
       Michael                                             MCCA




       Bahr,           Technic                             M-
1099             Yes             9.9a.3.8   116   55 MAC
       Michael         al                                  MCCA




       Bahr,                                               M-
1100             No    Editorial 9.9a.3.8   116   59 MAC
       Michael                                             MCCA
       Bahr,          Technic                             M-
1101             No             9.9a.3.2   112   53 MAC
       Michael        al                                  MCCA




       Bahr,                                              M-
1102             No   Editorial 9.9a.3.2   112   54 MAC
       Michael                                            MCCA




       Bahr,          Technic                             M-
1103             No             9.9a.3.1   112   40 MAC
       Michael        al                                  MCCA
       Bahr,          Technic                             M-
1104             No             9.9a.3.1   112   35 MAC
       Michael        al                                  MCCA




       Bahr,                                              M-
1105             No   Editorial 9.9a.3.1   112   31 MAC
       Michael                                            MCCA




       Bahr,                                              M-
1106             No   Editorial 9.9a.3.1   112   17 MAC
       Michael                                            MCCA
       Bahr,                                              M-
1107             No    Editorial 7.4.15.6   77   3 MAC
       Michael                                            MCCA




       Bahr,           Technic                            M-
1108             Yes             7.3.2.0a   37   38 MAC
       Michael         al                                 MCCA
       Bahr,           Technic 7.3.2.106                      M-
1109             Yes                           55    62 MAC
       Michael         al          .2                         MCCA




       Bahr,                       10.3.77.7                  M-
1110             No    Editorial               162   12 MAC
       Michael                     .1                         MCCA




       Bahr,           Technic                                M-
1111             Yes               7.4.15.9    78    47 MAC
       Michael         al                                     MCCA
       Bahr,
1112             No    Editorial 7.4.15.5   76    55 MAC M-CC
       Michael




       Bahr,           Technic                             R-
1113             Yes             7.4.15.3   75    33 RFI
       Michael         al                                  HWMP




       Bahr,           Technic 10.3.76.4
1114             Yes                        156    9 MAC M-BS
       Michael         al        .4




       Bahr,           Technic 10.3.76.4
1115             No                         156    3 MAC M-BS
       Michael         al        .4




       Bahr,           Technic 10.3.76.4
1116             No                         155   65 MAC M-BS
       Michael         al        .3
       Bahr,           Technic 10.3.76.4
1117             No                            155   65 MAC M-BS
       Michael         al          .3




       Bahr,           Technic 10.3.76.4
1118             Yes                           155   50 MAC M-BS
       Michael         al          .2




       Bahr,           Technic 10.3.76.4
1119             Yes                           155   49 MAC M-BS
       Michael         al          .2




       Bahr,                       10.3.76.4
1120             No    Editorial               155   46 MAC M-BS
       Michael                     .2
       Bahr,          Technic 10.3.76.4
1121             No                           155   20 MAC M-BS
       Michael        al          .1




       Bahr,                      10.3.76.3
1122             No   Editorial               155   11 MAC M-BS
       Michael                    .4




       Bahr,          Technic 10.3.76.3
1123             No                           155   10 MAC M-BS
       Michael        al          .4
       Bahr,           Technic 10.3.76.3
1124             Yes                           154   57 MAC M-BS
       Michael         al          .2




       Bahr,                       10.3.76.3
1125             No    Editorial               154   34 MAC M-BS
       Michael                     .1




       Bahr,                       10.3.76.2
1126             No    Editorial               154   27 MAC M-BS
       Michael                     .4




       Bahr,           Technic 10.3.76.2
1127             Yes                           154   16 MAC M-BS
       Michael         al          .3
       Bahr,           Technic 10.3.76.2
1128             Yes                           154   12 MAC M-BS
       Michael         al          .3




       Bahr,                       10.3.76.2
1129             No    Editorial               153   44 MAC M-BS
       Michael                     .1




       Bahr,                       10.3.76.1
1130             No    Editorial               153   36 MAC M-BS
       Michael                     .4




       Bahr,           Technic 10.3.76.1
1131             Yes                           153   34 MAC M-BS
       Michael         al          .4
       Bahr,                       10.3.76.1
1132             No    Editorial               153   28 MAC M-BS
       Michael                     .3




       Bahr,                       10.3.76.1
1133             No    Editorial               153   27 MAC M-BS
       Michael                     .3




       Bahr,           Technic 10.3.76.1
1134             Yes                           153   12 MAC M-BS
       Michael         al          .2




       Bahr,                       10.3.76.1
1135             No    Editorial               152   54 MAC M-BS
       Michael                     .1
       Bahr,                       10.3.76.0
1136             No    Editorial               152   45 MAC M-BS
       Michael                     a




       Bahr,           Technic
1137             No                7.3.2.103   51    8 MAC M-BS
       Michael         al




       Bahr,           Technic
1138             Yes               7.3.2.103   52    21 MAC M-BS
       Michael         al




       Bahr,
1139             No    Editorial 7.3.2.103     52    16 MAC M-BS
       Michael
       Bahr,           Technic
1140             Yes             7.3.2.103   52   15 MAC M-BS
       Michael         al




       Bahr,           Technic
1141             Yes             7.3.2.103   52   13 MAC M-BS
       Michael         al
       Bahr,
1142             No    Editorial 7.3.2.103   52   13 MAC M-BS
       Michael




       Bahr,           Technic
1143             Yes             7.3.2.103   52   12 MAC M-BS
       Michael         al




       Bahr,
1144             No    Editorial 7.3.2.103   51   56 MAC M-BS
       Michael




       Bahr,
1145             No    Editorial 7.3.2.103   51   54 MAC M-BS
       Michael
       Bahr,
1146             No    Editorial 7.3.2.103   51   53 MAC M-BS
       Michael




       Bahr,
1147             No    Editorial 7.3.2.103   51   49 MAC M-BS
       Michael




       Bahr,           Technic
1148             Yes             7.3.2.103   51   49 MAC M-BS
       Michael         al




       Bahr,           Technic
1149             Yes             7.3.2.103   51   43 MAC M-BS
       Michael         al
       Bahr,           Technic
1150             Yes             7.3.2.103   51   42 MAC M-BS
       Michael         al




       Bahr,           Technic
1151             Yes             7.3.2.103   51   38 MAC M-BS
       Michael         al




       Bahr,           Technic
1152             Yes             7.3.2.103   51   38 MAC M-BS
       Michael         al




       Bahr,
1153             No    Editorial 7.3.2.103   51   25 MAC M-BS
       Michael
       Bahr,
1154             No    Editorial 7.3.2.103   51    5 MAC M-BS
       Michael




       Bahr,           Technic 11C.12.4
1155             Yes                         270   27 MAC M-BS
       Michael         al       .2.4




       Bahr,           Technic 11C.12.4
1156             Yes                         270   7 MAC M-BS
       Michael         al       .2.3
       Bahr,           Technic 11C.12.4
1157             No                       269   1 MAC M-BS
       Michael         al      .2.1




       Bahr,           Technic 11C.12.4
1158             No                       268   61 MAC M-BS
       Michael         al      .2.1




       Bahr,           Technic 11C.12.4
1159             Yes                      268   61 MAC M-BS
       Michael         al      .2.1
       Bahr,                      11C.12.4
1160             No   Editorial              269   32 MAC M-BS
       Michael                    .2.2




       Bahr,                      11C.12.4
1161             No   Editorial              270   24 MAC M-BS
       Michael                    .2.3




       Bahr,                      11C.12.4
1162             No   Editorial              270   23 MAC M-BS
       Michael                    .2.3




       Bahr,                      11C.12.4
1163             No   Editorial              270   23 MAC M-BS
       Michael                    .2.3
       Bahr,          Technic 11C.12.4
1164             No                          270   23 MAC M-BS
       Michael        al          .2.3




       Bahr,                      11C.12.4
1165             No   Editorial              270   17 MAC M-BS
       Michael                    .2.3




       Bahr,          Technic 11C.12.4
1166             No                          270   16 MAC M-BS
       Michael        al          .2.3




       Bahr,                      11C.12.4
1167             No   Editorial              270   15 MAC M-BS
       Michael                    .2.3
       Bahr,                      11C.12.4
1168             No   Editorial              270   7 MAC M-BS
       Michael                    .2.3




       Bahr,                      11C.12.4
1169             No   Editorial              270   7 MAC M-BS
       Michael                    .2.3




       Bahr,                      11C.12.4
1170             No   Editorial              270   62 MAC M-BS
       Michael                    .2.4




       Bahr,                      11C.12.4
1171             No   Editorial              270   52 MAC M-BS
       Michael                    .2.4
       Bahr,                       11C.12.4
1172             No    Editorial              270   54 MAC M-BS
       Michael                     .2.4




       Bahr,                       11C.12.4
1173             No    Editorial              270   54 MAC M-BS
       Michael                     .2.4




       Bahr,           Technic 11C.12.4
1174             Yes                          270   48 MAC M-BS
       Michael         al          .2.4




       Bahr,           Technic 11C.12.4
1175             Yes                          270   47 MAC M-BS
       Michael         al          .2.4
       Bahr,           Technic 11C.12.4
1176             No                           270   47 MAC M-BS
       Michael         al          .2.4




       Bahr,           Technic 11C.12.4
1177             Yes                          270   42 MAC M-BS
       Michael         al          .2.4




       Bahr,                       11C.12.4
1178             No    Editorial              270   37 MAC M-BS
       Michael                     .2.4
       Bahr,           Technic 11C.12.4
1179             No                       269   30 MAC M-BS
       Michael         al      .2.2




       Bahr,           Technic 11C.12.4
1180             Yes                      269   26 MAC M-BS
       Michael         al      .2.2




       Bahr,           Technic 11C.12.4
1181             No                       270   32 MAC M-BS
       Michael         al      .2.4




       Bahr,           Technic 11C.12.4
1182             Yes                      270   30 MAC M-BS
       Michael         al      .2.4
       Bahr,                      11C.12.4
1183             No   Editorial              271   20 MAC M-BS
       Michael                    .3




       Bahr,                      11C.12.4
1184             No   Editorial              271   10 MAC M-BS
       Michael                    .3




       Bahr,          Technic 11C.12.4
1185             No                          271   11 MAC M-BS
       Michael        al          .3
       Bahr,          Technic 11C.12.4
1186             No                      271   9 MAC M-BS
       Michael        al          .3




       Bahr,          Technic 11C.12.4
1187             No                      271   9 MAC M-BS
       Michael        al          .3




       Bahr,          Technic 11C.12.4
1188             No                      271   6 MAC M-BS
       Michael        al          .3




       Bahr,
1189             No   Editorial          34    43 MAC M-BS
       Michael
       Bahr,           Technic 11C.12.4
1190             Yes                         271   60 MAC M-BS
       Michael         al       .4.2




       Bahr,
1191             No    Editorial 7.4.15.12   80    37 MAC M-BS
       Michael




       Bahr,                                            Gene G-
1192             No    Editorial 7.4.15.12   80    20
       Michael                                          ral   Editor




       Bahr,
1193             No    Editorial 7.4.15.12   80    36 MAC M-BS
       Michael
       Bahr,
1194             No    Editorial 7.4.15.12   80    35 MAC M-BS
       Michael




       Bahr,
1195             No    Editorial 7.4.15.11   79    62 MAC M-BS
       Michael




       Bahr,                                            Gene G-
1196             No    Editorial 7.4.15.11   79    47
       Michael                                          ral   Editor




       Bahr,           Technic 11C.12.4
1197             Yes                         271   54 MAC M-BS
       Michael         al       .4.2
       Bahr,                       11C.12.4
1198             No    Editorial              271   49 MAC M-BS
       Michael                     .4.2




       Bahr,                       11C.12.4
1199             No    Editorial              271   49 MAC M-BS
       Michael                     .4.2




       Bahr,                       11C.12.4
1200             No    Editorial              271   48 MAC M-BS
       Michael                     .4.2




       Bahr,           Technic 11C.12.4
1201             Yes                          271   48 MAC M-BS
       Michael         al          .4.2
       Bahr,                       11C.12.4
1202             No    Editorial              271   48 MAC M-BS
       Michael                     .4.2




       Bahr,                       11C.12.4
1203             No    Editorial              271   45 MAC M-BS
       Michael                     .4.2




       Bahr,           Technic 11C.12.4
1204             Yes                          271   39 MAC M-BS
       Michael         al          .4.1




       Bahr,           Technic 11C.12.4
1205             No                           271   39 MAC M-BS
       Michael         al          .4.1
       Bahr,                       11C.12.4
1206             No    Editorial              271   39 MAC M-BS
       Michael                     .4.1




       Bahr,                       11C.12.4
1207             No    Editorial              271   38 MAC M-BS
       Michael                     .4.1




       Bahr,           Technic 11C.12.4
1208             Yes                          271   34 MAC M-BS
       Michael         al          .4.1




       Bahr,                       11C.12.4
1209             No    Editorial              271   30 MAC M-BS
       Michael                     .4.1
       Bahr,                      11C.12.4
1210             No   Editorial              271   29 MAC M-BS
       Michael                    .4.1




       Bahr,                      11C.12.4
1211             No   Editorial              271   29 MAC M-BS
       Michael                    .4.1




       Bahr,                      11C.12.4
1212             No   Editorial              271   26 MAC M-BS
       Michael                    .4
       Bahr,           Technic 11C.12.4
1213             Yes                          272   36 MAC M-BS
       Michael         al          .4.3




       Bahr,                       11C.12.4
1214             No    Editorial              272   34 MAC M-BS
       Michael                     .4.3
       Bahr,           Technic 11C.12.4
1215             No                           272   34 MAC M-BS
       Michael         al          .4.3




       Bahr,           Technic 11C.12.4
1216             Yes                          272   30 MAC M-BS
       Michael         al          .4.3




       Bahr,                       11C.12.4
1217             No    Editorial              272   27 MAC M-BS
       Michael                     .4.3
       Bahr,           Technic 11C.12.4
1218             No                           272   26 MAC M-BS
       Michael         al          .4.3




       Bahr,                       11C.12.4
1219             No    Editorial              272   22 MAC M-BS
       Michael                     .4.3




       Bahr,           Technic 11C.12.4
1220             Yes                          272   19 MAC M-BS
       Michael         al          .4.3
       Bahr,                      11C.12.4
1221             No   Editorial              272   18 MAC M-BS
       Michael                    .4.3




       Bahr,                      11C.12.4
1222             No   Editorial              272   18 MAC M-BS
       Michael                    .4.3




       Bahr,
1223             No   Editorial 11C.13.6     276   1 MAC M-PM
       Michael




       Bahr,
1224             No   Editorial 11C.13.6     275   60 MAC M-PM
       Michael
       Bahr,           Technic 11C.12.4
1225             Yes                          272   11 MAC M-BS
       Michael         al          .4.3




       Bahr,           Technic 11C.12.4
1226             Yes                          272   11 MAC M-BS
       Michael         al          .4.3




       Bahr,                       11C.12.4
1227             No    Editorial              272   1 MAC M-BS
       Michael                     .4.3




       Bahr,           Technic 11C.12.4
1228             Yes                          272   10 MAC M-BS
       Michael         al          .4.3
       Bahr,                       11C.12.4
1229             No    Editorial              272   7 MAC M-BS
       Michael                     .4.3




       Bahr,           Technic 11C.12.4
1230             Yes                          272   6 MAC M-BS
       Michael         al          .4.3
       Bahr,           Technic 11C.12.4
1231             Yes                      272   43 MAC M-BS
       Michael         al      .5




       Bahr,           Technic 11C.12.4
1232             Yes                      272   44 MAC M-BS
       Michael         al      .5
       Bahr,           Technic 11C.12.4
1233             No                           272   43 MAC M-BS
       Michael         al          .5




       Bahr,           Technic
1234             Yes               D.3        304   33 MAC M-BS
       Michael         al




       Bahr,                       11C.12.4
1235             No    Editorial              273   1 MAC M-BS
       Michael                     .6
       Bahr,                       11C.12.4
1236             No    Editorial              272   56 MAC M-BS
       Michael                     .6




       Bahr,           Technic 11C.12.4
1237             Yes                          272   56 MAC M-BS
       Michael         al          .6
       Bahr,           Technic 11C.12.4
1238             Yes                      272   59 MAC M-BS
       Michael         al       .6




       Bahr,
1239             No    Editorial D.3      303   5 MAC M-BS
       Michael




       Bahr,
1240             No    Editorial D.3      303   55 MAC M-BS
       Michael
       Bahr,
1241             No    Editorial D.3   303   40 MAC M-BS
       Michael




       Bahr,           Technic
1242             Yes             D.3   303   31 MAC M-BS
       Michael         al




       Bahr,
1243             No    Editorial D.3   303   8 MAC M-BS
       Michael




       Bahr,
1244             No    Editorial D.3   303   9 MAC M-BS
       Michael
       Bahr,                      11C.12.4
1245             No   Editorial              268   44 MAC M-BS
       Michael                    .1




       Bahr,                      11C.12.4
1246             No   Editorial              268   39 MAC M-BS
       Michael                    .1




       Bahr,                      11C.12.4
1247             No   Editorial              268   39 MAC M-BS
       Michael                    .1




       Bahr,                      11C.12.4
1248             No   Editorial              268   34 MAC M-BS
       Michael                    .1




       Bahr,                                            Gene G-
1249             No   Editorial 11C.2.8      196   52
       Michael                                          ral   Editor
       Bahr,           Technic 11C.12.4
1250             Yes                          269   54 MAC M-BS
       Michael         al          .2.3




       Bahr,                       11C.12.4
1251             No    Editorial              269   46 MAC M-BS
       Michael                     .2.3
       Bahr,           Technic 7.3.2.96.
1252             No                           46    53 MAC M-BS
       Michael         al          9




       Bahr,           Technic 7.3.2.96.
1253             Yes                          46    48 MAC M-BS
       Michael         al          9




       Bahr,           Technic 11C.12.4
1254             Yes                          269   28 MAC M-BS
       Michael         al          .2.2




       Bahr,                       11C.12.4
1255             Yes   Editorial              269   26 MAC M-BS
       Michael                     .2.2
       Bahr,           Technic 11C.12.4
1256             Yes                      269   22 MAC M-BS
       Michael         al      .2.2




       Bahr,           Technic 11C.12.4
1257             No                       269   16 MAC M-BS
       Michael         al      .2.2




       Bahr,           Technic 11C.12.3
1258             Yes                      268   9 MAC M-BS
       Michael         al      .2
       Bahr,           Technic 11C.12.2
1259             Yes                          267   7 MAC M-BS
       Michael         al          .2.3




       Bahr,                       11C.12.2
1260             No    Editorial              267   2 MAC M-BS
       Michael                     .2.2




       Bahr,                       11C.12.2
1261             No    Editorial              267   1 MAC M-BS
       Michael                     .2.2
       Bahr,           Technic 10.3.75.4
1262             Yes                           150   56 MAC M-BS
       Michael         al          .2




       Bahr,                       10.3.75.4
1263             No    Editorial               151   8 MAC M-BS
       Michael                     .2




       Bahr,                       11C.12.2
1264             No    Editorial               266   34 MAC M-BS
       Michael                     .2.2
       Bahr,                       11C.12.2
1265             No    Editorial               266   37 MAC M-BS
       Michael                     .2.2




                                                                 G-
       Bahr,                       10.3.10.1              Gene
1266             No    Editorial               137   36          Discov
       Michael                     .3                     ral
                                                                 ery




       Bahr,           Technic 11C.12.2
1267             Yes                           266   22 MAC M-BS
       Michael         al          .2.1




       Bahr,           Technic 10.3.10.1
1268             Yes                           137   42 MAC M-BS
       Michael         al          .3
       Bahr,                       10.3.75.1
1269             No    Editorial               149   17 MAC M-BS
       Michael                     .3




       Bahr,           Technic 11C.12.2
1270             Yes                           266   16 MAC M-BS
       Michael         al          .2.1
       Bahr,           Technic 11C.12.2
1271             Yes                       266        MAC M-BS
       Michael         al      .1




       Bahr,           Technic 7.3.2.96.              Gene G-
1272             No                        44    56
       Michael         al      5                      ral   Frame




       Bahr,           Technic 7.3.2.96.              Gene G-
1273             No                        44    47
       Michael         al      5                      ral   Frame




       Bahr,           Technic 7.3.2.96.
1274             Yes                       44    30 MAC M-BS
       Michael         al      5
       Bahr,                       11C.12.2
1275             No    Editorial              265   62 MAC M-BS
       Michael                     .1




       Bahr,                       11C.12.2
1276             No    Editorial              265   60 MAC M-BS
       Michael                     .1




       Bahr,           Technic
1277             Yes               11C.12.1   265   46 MAC M-BS
       Michael         al




       Bahr,           Technic
1278             Yes               11C.12.1   265   43 MAC M-BS
       Michael         al
       Bahr,
1279             Yes   Editorial 11C.12.1     265   40 MAC M-BS
       Michael




       Bahr,                       11C.12.2
1280             Yes   Editorial              266   27 MAC M-BS
       Michael                     .2.1




       Bahr,           Technic
1281             Yes               11.1.1     184   22 MAC M-BS
       Michael         al




       Bahr,           Technic
1282             Yes               11.1.0a    184   19 MAC M-BS
       Michael         al
       Bahr,           Technic                         Gene G-
1283             No              7.2.2.2     26   36
       Michael         al                              ral   Frame




       Bahr,           Technic                         Gene G-
1284             No                   9.22 121    22
       Michael         al                              ral   Frame




       Bahr,                                           Gene G-
1285             No    Editorial 7.1.3.6.3   22
       Michael                                         ral   Frame




                                                             R-
       Bahr,           Technic
1286             Yes             5.2.13.4    9    16 RFI     MeshG
       Michael         al
                                                             ate
       Sakoda,                                                R-
1287              No   Editorial Y.6        325   36 RFI
       Kazuyuki                                               HWMP




       Sakoda,         Technic                         Gene
1288              No             D.3        290   10          G-MIB
       Kazuyuki        al                              ral




       Sakoda,         Technic
1289              No             A.4.23.1   288   46 RFI      R-LM
       Kazuyuki        al




       Sakoda,         Technic 11C.13.1
1290              No                        281    2 MAC M-PM
       Kazuyuki        al        1
       Sakoda,                     11C.13.1
1291              No   Editorial              280   35 MAC M-PM
       Kazuyuki                    0.3




       Sakoda,                     11C.13.1
1292              No   Editorial              279   59 MAC M-PM
       Kazuyuki                    0.2




       Sakoda,                     11C.13.1
1293              No   Editorial              279   10 MAC M-PM
       Kazuyuki                    0.1




       Sakoda,                     11C.13.9
1294              No   Editorial              278   28 MAC M-PM
       Kazuyuki                    .4
       Sakoda,                     11C.13.9
1295              No   Editorial              278   24 MAC M-PM
       Kazuyuki                    .3




       Sakoda,                     11C.13.9
1296              No   Editorial              278   11 MAC M-PM
       Kazuyuki                    .3




       Sakoda,                     11C.13.9
1297              No   Editorial              278   1 MAC M-PM
       Kazuyuki                    .3




       Sakoda,         Technic 11C.13.9
1298              No                          277   58 MAC M-PM
       Kazuyuki        al          .2




       Sakoda,                     11C.13.9
1299              No   Editorial              277   27 MAC M-PM
       Kazuyuki                    .1
       Sakoda,
1300              No   Editorial 11C.13.8   276   59 MAC M-PM
       Kazuyuki




       Sakoda,
1301              No   Editorial 11C.13.7   276   37 MAC M-PM
       Kazuyuki




       Sakoda,
1302              No   Editorial 11C.13.7   276   34 MAC M-PM
       Kazuyuki




       Sakoda,
1303              No   Editorial 11C.13.7   276   9 MAC M-PM
       Kazuyuki




       Sakoda,
1304              No   Editorial 11C.13.6   275   60 MAC M-PM
       Kazuyuki
       Sakoda,
1305              No   Editorial 11C.13.5     275   54 MAC M-PM
       Kazuyuki




       Sakoda,                     11C.13.4
1306              No   Editorial              275   36 MAC M-PM
       Kazuyuki                    .3




       Sakoda,
1307              No   Editorial 11C.13.3     274   48 MAC M-PM
       Kazuyuki




       Sakoda,
1308              No   Editorial 11C.13.3     274   43 MAC M-PM
       Kazuyuki
       Sakoda,
1309              No   Editorial 11C.13.2   273   49 MAC M-PM
       Kazuyuki




       Sakoda,
1310              No   Editorial 11C.13.2   273   41 MAC M-PM
       Kazuyuki




       Sakoda,
1311              No   Editorial 11C.13.1   273   19 MAC M-PM
       Kazuyuki




       Sakoda,         Technic 11C.12.4
1312              No                        270   17 MAC M-BS
       Kazuyuki        al       .2.3
       Sakoda,                     11C.12.2
1313              No   Editorial              266    5 MAC M-BS
       Kazuyuki                    .1




       Sakoda,         Technic
1314              No               11C.11.2   264   54 MAC M-CC
       Kazuyuki        al




       Sakoda,                     11C.10.3                  R-
1315              No   Editorial              260   54 RFI
       Kazuyuki                    .3                        FWD
                                                             R-
       Sakoda,                     11C.10.3
1316              No   Editorial              260   50 RFI   MeshG
       Kazuyuki                    .2
                                                             ate




                                                             R-
       Sakoda,                     11C.10.3
1317              No   Editorial              260   31 RFI   MeshG
       Kazuyuki                    .2
                                                             ate




                                                             R-
       Sakoda,
1318              No   Editorial 11C.10.3     260   14 RFI   MeshG
       Kazuyuki
                                                             ate
       Sakoda,         Technic
1319              No             11C.8     225    1 RFI     R-LM
       Kazuyuki        al




       Sakoda,         Technic
1320              No             11C.7.3   224   55 RFI     R-LM
       Kazuyuki        al




       Sakoda,         Technic                        Gene G-
1321              No                 11.3 185    36
       Kazuyuki        al                             ral   Base
       Sakoda,         Technic 10.3.79.2                  R-
1322              No                       171   29 RFI
       Kazuyuki        al      .2                         Proxy




       Sakoda,         Technic 10.3.77.8                  M-
1323              No                       163   24 MAC
       Kazuyuki        al      .2                         MCCA




       Sakoda,         Technic 10.3.77.4                  M-
1324              No                       159   42 MAC
       Kazuyuki        al      .2                         MCCA




       Sakoda,         Technic 10.3.76.2
1325              No                       153   51 MAC M-BS
       Kazuyuki        al      .2
       Sakoda,         Technic 10.3.73.2                  Secu S-
1326              No                           145   20
       Kazuyuki        al          .2                     rity   MPM




       Sakoda,                                                   R-
1327              No   Editorial 9.22.3        128   27 RFI
       Kazuyuki                                                  FWD




       Sakoda,                     9.22.2.4.                     R-
1328              No   Editorial               127   31 RFI
       Kazuyuki                    2                             FWD




       Sakoda,                     9.22.2.4.                     R-
1329              No   Editorial               127   26 RFI
       Kazuyuki                    2                             FWD




       Sakoda,                     9.22.2.3.                     R-
1330              No   Editorial               126   40 RFI
       Kazuyuki                    2                             FWD
       Sakoda,                     9.22.2.3.                  R-
1331              No   Editorial               126   16 RFI
       Kazuyuki                    1                          FWD




       Sakoda,                     9.22.2.3.                  R-
1332              No   Editorial               126    1 RFI
       Kazuyuki                    1                          FWD




       Sakoda,                     9.22.2.3.                  R-
1333              No   Editorial               125   49 RFI
       Kazuyuki                    1                          FWD




       Sakoda,                     9.22.2.2.                  R-
1334              No   Editorial               125   31 RFI
       Kazuyuki                    2                          FWD
       Sakoda,                     9.22.2.2.                  R-
1335              No   Editorial               125   23 RFI
       Kazuyuki                    2                          FWD




       Sakoda,                     9.22.2.2.                  R-
1336              No   Editorial               125    9 RFI
       Kazuyuki                    2                          FWD




       Sakoda,                     9.22.2.2.                  R-
1337              No   Editorial               124   61 RFI
       Kazuyuki                    2                          FWD




       Sakoda,                     9.22.2.2.                  R-
1338              No   Editorial               124   42 RFI
       Kazuyuki                    2                          FWD
       Sakoda,                     9.22.2.2.                  R-
1339              No   Editorial               124   40 RFI
       Kazuyuki                    2                          FWD
       Sakoda,         Technic 9.22.2.2.                  R-
1340              No                       124   21 RFI
       Kazuyuki        al      2                          FWD
       Sakoda,                     9.22.2.2.                  R-
1341              No   Editorial               123   42 RFI
       Kazuyuki                    1                          FWD




       Sakoda,                     9.22.2.2.                  R-
1342              No   Editorial               123   34 RFI
       Kazuyuki                    1                          FWD




       Sakoda,                     9.22.2.2.                  R-
1343              No   Editorial               123   29 RFI
       Kazuyuki                    1                          FWD
       Sakoda,         Technic 9.22.2.2.                   R-
1344              No                        123   26 RFI
       Kazuyuki        al       1                          FWD




       Sakoda,                                             R-
1345              No   Editorial 9.22.2.1   122   47 RFI
       Kazuyuki                                            FWD




       Sakoda,                                             R-
1346              No   Editorial 9.22.2.1   122   41 RFI
       Kazuyuki                                            FWD




       Sakoda,                                             R-
1347              No   Editorial 9.22.2.1   122   34 RFI
       Kazuyuki                                            FWD
       Sakoda,                                             R-
1348              No   General                      RFI
       Kazuyuki                                            FWD




       Sakoda,                                             R-
1349              No   Editorial 9.22.2.1   121   60 RFI
       Kazuyuki                                            FWD




       Sakoda,         Technic                             R-
1350              No             9.22.2.1   121   58 RFI
       Kazuyuki        al                                  FWD




       Sakoda,                                             R-
1351              No   Editorial 9.22.2.1   121   56 RFI
       Kazuyuki                                            FWD
       Sakoda,                                              R-
1352              No   Editorial 9.22.2.1    121   44 RFI
       Kazuyuki                                             FWD




       Sakoda,                                              R-
1353              No   Editorial 9.22.1      121   27 RFI
       Kazuyuki                                             FWD




                                                            M-
       Sakoda,         Technic
1354              No             9.9.1.2     111   37 MAC Gener
       Kazuyuki        al
                                                            al




       Sakoda,         Technic
1355              No             7.3.2.103   52    12 MAC M-BS
       Kazuyuki        al
       Sakoda,         Technic 7.3.2.96.                 Gene G-
1356              No                           43   17
       Kazuyuki        al          2                     ral    Frame




       Sakoda,         Technic                           Gene G-
1357              No               7.2.2.2     26   36
       Kazuyuki        al                                ral    Frame




                                                                S-
       Sakoda,         Technic 5.2.13.5.                 Secu
1358              No                           10   47          Gener
       Kazuyuki        al          3                     rity
                                                                al




                                                                G-
       Sakoda,                                           Gene
1359              No   Editorial         3.1   4    8           Gener
       Kazuyuki                                          ral
                                                                al




       Sakoda,
1360              No   Editorial         3.1   3    33 MAC M-PM
       Kazuyuki
       Sakoda,
1361              No   Editorial         3.1   3    21 MAC M-PM
       Kazuyuki




       Sakoda,
1362              No   Editorial         3.1   3    13 MAC M-PM
       Kazuyuki



       Sakoda,                                           Gene G-
1363              No   Editorial frontmtter    4    35
       Kazuyuki                                          ral    Editor




                                                                G-
       Mccann,         Technic                           Gene
1364              No               7.3.2.90    42   1           Emerg
       Stephen         al                                ral
                                                                ency
                                                            G-
       Mccann,        Technic                        Gene
1365             No             11.23.6   190   66          Emerg
       Stephen        al                             ral
                                                            ency




                                                            G-
       Mccann,        Technic                        Gene
1366             No             W.4.4     320   57          Emerg
       Stephen        al                             ral
                                                            ency




                                                            G-
       Mccann,        Technic 5.2.13.5.              Gene
1367             No                       12    49          Emerg
       Stephen        al        12                   ral
                                                            ency
                                                                             Resolutio
Comment                                    Proposed Change
                                                                             n Status
(TR) Clause 8.2a.5: It is unclear how
the SAE protocol deals with
unexpected messages (e.g., random
key confirm message injected right
before the "proper" one, etc.). From the
SAE state machine depicted in Fig. 8-
3a (Clause 8.2a.8.1, p. 94), it seems
that any unexpected message received
along partial execution of the protocol    Suggested remedy: Clarify intended
results in aborting the protocol entirely. behavior w.r.t. unexpected         Disagree
Is this really the desired behavior? Or, messages more clearly.
does one allow ignoring non-
conforming messages pending receipt
of a conforming one? (If not, one may
create another DoS attack, by injecting
a spurious message in the message
flow causing aborted protocol and
requirement to generate a "fresh"
Commit message, thereby burning up
precious computing cycles.) Suggested
(TR) Clause 8.2a.6, p. 91: The DoS
attack countermeasure described
seems to be incomplete. It is unclear
how precisely the Anti-clogging token is
statelessly bound to the sender of the
Commit message, nor under which
conditions the counter in the SAE state
machine is decremented. Moreover,
could a device store more than one
(Commit message, device) pairs with          Suggested remedy: Provide a more
the same device id (if so, this suggests complete specification of how to
allowing two initiated, but incomplete   counter DoS attacks, tackling as a       Principle
password-based key agreement                 minimum the issues highlighted
protocols with that entity). It is unclear   above.
(or I somehow missed this) how one
includes the Anti-clogging token in a
subsequent Commit message.
Moreover, since the size of the Commit
message is not known (l. 38-39)
"suggests" but does not mandate it not
to exceed 256 octets), it is not clear
how one could format frames
appropriately (true - l. 50-52 do suggest
(T) Clause 8.2a.5.4, p. 90, l. 34: the
mapping function F, first introduced in
Clause 8.2a.4.1.1, p. 87, l. 9-11 for
ECC groups (F(x,y):=x), resp. Clause
8.2a.4.2.1, p. 88, l. 41-43 for FFC
groups (F(x):=x) might as well be
defined consistently and uniformly, as      Suggested remedy: define the
the identity function. After all, the key K mapping function to be the identity
                                                                                  Disagree
cannot be computed by operating on x- function throughout, as motivated
coordinates only, as would normally be above.
the case with ephemeral Diffie-
Hellmann, since now K is a linear
combination of two points, rather than a
scalar multiple of one, as would have
been the case with ephemeral DH.
Suggested remedy: define the mapping
function to be the identity function
(TR) Clause 8.2a.5.4, p. 90, l. 10-17:
The "public key validation" checks
performed for FCC groups and ECC
groups should provide similar
assurances, but do not: for FFC
                                             Suggested remedy: Remove the
groups, one checks that the Commit-
                                             inconsistency in the specification, as Principle
element object has the proper order r,
                                             outlined above.
but for ECC groups, one only checks
that the point is on the curve (the
corresponding check for FFC groups
would be simply to check for the
interval [1,p-1]). Suggested remedy:
(TR) Clause 8.2a.5.4, p. 90, l. 15:
Replace "the element shall be less than
the prime, p," by "the element shall be
an integer greater than zero (0) and
less than the prime p". Moreover, the
check that the point (x,y) satisfies the
curve equation introduced first in
Clause 8.2a.4.1.1, p. 86, l. 46 is only
valid for points different from the so-
                                             Suggested remedy: Implement
called "point of infinity". Hence, one                                              Agree
                                             accordingly.
should check that the received object
Commit-element is unequal to the point
of infinity and, if so, additionally check
that it satisfies the Weierstrass
equation (since then it can be written as
(x,y)). This then establishes that the
point is on the curve and unequal to the
point of infinity. One should also check
that the point has the proper order r by
checking that scalar-op(r, Commit-
(TR) Clause 8.2a.5.4, p. 90, l. 12:
Replace "the scalar operation of the
element and the order of the group, r
shall be equal to one (1)" by "the scalar Suggested remedy: Implement
operation of the order r of the group     accordingly. Note RS: the scalar
and the element shall be equal to 1          operation is a mapping from Z x        Principle
(mod p)". Suggested remedy:                  GF(p) to GF(p) and not from GF(p) x
Implement accordingly. Note RS: the          Z to GF(p).
scalar operation is a mapping from Z x
GF(p) to GF(p) and not from GF(p) x Z
to GF(p).
(TR) Clause 8.2a.5.4, p. 90, l. 12: The
current interval check is unclearly
defined. Replace "shall be between one
                                            Suggested remedy: Implement
(1) and the prime" by "shall be greater                                         Agree
                                            accordingly.
than zero (0) and less than the prime
number p". Suggested remedy:
Implement accordingly.




(E) Clause 8.2a.5.4, p. 90, l. 10:
Replace "the order, r, of the negotiated
group scalar validation" by "the order r    Suggested remedy: Implement
                                                                                Principle
of the negotiated group, scalar             accordingly.
validation". Suggested remedy:
Implement accordingly.




(TR) Clause 8.2.a.5.4, p. 90: The
protocol described seems to be
equivalent to ephemeral ECDH, since
the computed key K (8.2a.5.4, p. 90, l.
26-27) is equal to (rndA * rndB)
G(pwd), or - in the notation of the draft
specficiation - scalar-op(rand, scalar-
op(rand-peer, PWE)). If so, one could       Suggested remedy: Replace the
just exchange ephemeral DK                  protocol in question by the
exponents and does not need to              elementary ephemeral ECDH
                                                                                Disagree
exchange the commit-scalar values           protocol with base point G(pwd) =
that are now necessary to "unblind" the PWE and simplify message flows
Commit-element contributions received accordingly, as outlined above.
from the other party involved in the
password-based key agreement
scheme. It is unclear why one does not
implement the ECDH protocol above,
since it is semantically equivalent.
Suggested remedy: Replace the
protocol in question by the elementary
(TR) Clause 8.2a.5, p. 89: It is unclear
whether the password-based key
agreement scheme carry a protocol
serial number, so that messages from
the same protocol run can be easily          Suggested remedy: Introduce a
matched (and inadvertent mix-ups due protocol serial number and filtering
to late receipt of a message from an old on this number, so as to try and        Disagree
protocol run can be avoided). The            avoid clashing protocol runs, as
protocol instance variables introduced       suggested above.
in Clause 8.2a.5.2 do not make this
clear (to me) either. Suggested remedy:
Introduce a protocol serial number and
filtering on this number, so as to try and
(TR) Clause 8.2a.5.2, p. 89, l. 54-55: It
is unclear whether one shall generate a
"fresh" rand and mask value at each
protocol invocation or whether these
can be reused, e.g., after somehow
protocol is aborted due to receipt of
spurious unexpected message during           Suggested remedy: Please clarify.   Agree
execution of password-based key
agreement scheme. In particular, can
one reuse ephemeral public keys or
SHALL these be generated at random
at every invocation? This obviously has
impact on cryptographic properties and
(TR) Clause 8.2.a.4.2.2, p. 88, l. 62 - p.
89, l. 19: The procedure for mapping a
password to a point in an FCC group
and that for mapping a password to a
point in an ECC group seem
inconsistent: with FCC groups, the
pseudo-code suggests checking that
the value PWE does not have an order
that divides the co-factor h:=(p-1)/r,       Suggested remedy: Please
whereas with ECC groups, this check is implement accordingly or explain
not prescribed. Shouldn't one make     carefully why this is not necessary   Principle
sure that the resulting point is a point of somehow (I may have missed
the subgroup of order r here? This          something here).
seems to be confirmed by the
specification of the SAE protocol in
Clause 8.2a.5, where the commit-scalar
value is taken mod r in Clause 8.2a.5.3
and where the order of the Commit-
element object is checked to be a
divisor of r in Clause 8.2a.5.4.
Suggested remedy: Please implement
(TR) Clause 8.2a.4.1.2, p. 87: The
procedure for mapping a password to a
point on the curve does not check
whether the resulting point is on the
subgroup of order r, nor whether the
resulting point happens to be the point
of infinity. While this check is not
necessary for curves with co-factor h=1 Suggested remedy: Check whether
(since every point is in the subgroup   the password-derived point lies in a
then), as seems assumed according to subgroup of order r. Alternatively,
the Note in Clause 8.2a.4.1.1, p. 86, l. stipulate clearly and in one location
51-54, the Note in Clause 8.2a.4, l. 22- in the draft specification that one Principle
26, seems to suggest more flexibility    uses only curves with co-factor h=1
w.r.t. curve choice and consider this to (and use SHALL notation here), so
be a "policy issue". Moreover, the SAE as to avoid ambiguity here.
protocol in Clause 8.2a.5 assumes that
the point has order r (via the commit-
scalar value taken mod r in Clause
8.2a.5.3). Suggested remedy: Check
whether the password-derived point lies
in a subgroup of order r. Alternatively,
stipulate clearly and in one location in
the draft specification that one uses
(T) Clause 8.2a.4.1.2, p. 87: The
procedure for mapping a password to a
point on the curve has non-
deterministic running time, due to "trial-
                                             Suggested remedy: Replace the
and-error" approach. Why not replace
                                             procedure by one with deterministic
this with the deterministic method for                                             Principle
                                             running-time, e.g., using the
mapping a a value to a curve as
                                             technique referenced.
introduced, e.g., in the Crypto 2010
paper by Icart, Coron, et al (also IACR
ePrint 2009-340)? Suggested remedy:
Replace the procedure by one with
(TR) Clause 8.2a.4.1.2, p. 87, l. 32-65:
the pseudo-code does not determine a
specific value for the y-coordinate (l.
                                              Suggested remedy: Replace l. 47
47), but nevertheless performs a check
                                              as follows: "if the equation y2= x3+a
on this y-coordinate (l. 48). Suggested
                                              x + b (mod p)" has a solution y"; add
remedy: Replace l. 47 as follows: "if                                                    Agree
                                              as first subsequent step (right after l.
the equation y2= x3+a x + b (mod p)"
                                              49): determine a solution y to the
has a solution y"; add as first
                                              equation y2 = x3+a x + b (mod p)".
subsequent step (right after l. 49):
determine a solution y to the equation
y2 = x3+a x + b (mod p)".


(TR) Clause 8.2a.4.1, p. 87, l. 9-11:
The mapping function F seems to be a
projection function instead. Moreover, it
is unclear what the output of this
                                              Suggested remedy: Clarify.                 Agree
mapping function F is on the "point of
infinity" - or is this identity element
excluded from the definition?
Suggested remedy: Clarify.


(T) Clause 8.2a.4.1, p. 86, l. 56 till p.
87, l. 7: These paragraphs have some
undefined notions (such as X+Y, qG)
and do not stipulate that the operation
                                              Suggested remedy Replace these
is actually a group (and, thereby, is
                                              paragraphs by "The points of the
associative [which is a prerequisite for
                                              curve form an additive group under
the recursive definition in l. 37-39 on
                                              the binary operator elem-op, which
the same page]). Moreover, the inverse
                                              maps two points X and Y on the             Disagree
of an element is not necessarily a
                                              curve to a third point Z on the curve,
different element (example: elements of
                                              with as identity element the point of
order 2). Suggested remedy Replace
                                              infinity. The inverse of a point X on
these paragraphs by "The points of the
                                              the curve is denoted by inverse(X)."
curve form an additive group under the
binary operator elem-op, which maps
two points X and Y on the curve to a
third point Z on the curve, with as
identity element the point of infinity. The
(T) Clause 8.2a.4.1, p. 86, l. 46: This     Suggested remedy: change this
paragraph would benefit from a more         paragraph accordingly, e.g., by
precise definition of terms and a           replacing this by the following text:
reference to literature on elliptic curves. "(Prime) ECC groups used by SAE
Suggested remedy: change this               are defined by the six-tuple
paragraph accordingly, e.g., by             (p,a,b,G,r,h), where p is a prime
replacing this by the following text:       number, where a and b are
"(Prime) ECC groups used by SAE are coefficients defining the curve
defined by the six-tuple (p,a,b,G,r,h),     equation y2= x3+ax + b (mod p),
where p is a prime number, where a          where G:=(x, y) is a fixed point
and b are coefficients defining the         satisfying this curve equation, where
curve equation y2= x3+ax + b (mod p), r is the order of this point G, and              Agree
where G:=(x, y) is a fixed point            where h is the so-called co-factor.
satisfying this curve equation, where r     Elements in ECC groups are those
is the order of this point G, and where h pairs (x,y) satisfying the curve
is the so-called co-factor. Elements in     equation above and the so-called
ECC groups are those pairs (x,y)            "point of infinity". Elements in an
satisfying the curve equation above and ECC group are usually referred to
the so-called "point of infinity".          as points on the curve. The points of
Elements in an ECC group are usually        the curve form an additive group".
referred to as points on the curve. The     Note RS: Apart from more precision,
points of the curve form an additive        this also includes the point of infinity
group". Note RS: Apart from more            as element of the prime ECC group,



(TR) Clause 8.2a.4, p. 86, l. 38:
Replace "The specific definition of elem-
op(Y,Y)" by "The specific definition of     Suggested remedy: Change
                                                                                       Agree
elem-op(X,Y)", so as to make this           accordingly.
complete. Suggested remedy: Change
accordingly.
(TR) Clause 8.2a.4, p. 86, l. 36-37: The
scalar multiple scalar-op(x,Y) is *not*
the same as an x-fold iteration of elem-
                                            Suggested remedy: Replace the first
op(Y,Y): as an example, if x=2, one has
                                            two sentences by the following text:
2Y = Y+Y (i.e., it is a 1-fold iteration,
                                            "scalar-op(x,Y) can be defined
rather than a 2-fold iteration, of elem-
                                            recursively as follows:
op(Y,Y)). Moreover, the formula does
                                            scalar(0,Y):=O, where O is the
not specify the scalar multiple with
                                            identity element of the group in
scalar zero. Suggested remedy:                                                      Principle
                                            question; for x>0, scalar(x,Y):=elem-
Replace the first two sentences by the
                                            op(scalar-op(x-1,Y),Y)." Note RS: It
following text: "scalar-op(x,Y) can be
                                            seems prudent to introduce the
defined recursively as follows:
                                            identity element O in the preceding
scalar(0,Y):=O, where O is the identity
                                            paragraph, so as not to bury this
element of the group in question; for
                                            inside the definition of an operand.
x>0, scalar(x,Y):=elem-op(scalar-op(x-
1,Y),Y)." Note RS: It seems prudent to
introduce the identity element O in the
preceding paragraph, so as not to bury



(E) Clause 8.2a.4, p. 86, l. 34: Add the
following sentence: "The FFC and ECC
groups are indeed groups under the          Suggested remedy: Change
                                                                                    Disagree
binary operator elem-op thus defined."      accordingly.
Suggested remedy: Change
accordingly.




(E) Clause 8.2a.4, p. 86, l. 33: Replace
"takes and element and a scalar and is
denoted" by "takes an element Y and a Suggested remedy: Change
                                                                                    Agree
scalar x and maps this to a third           accordingly.
element denoted by". Suggested
remedy: Change accordingly.
(E) Clause 8.2a.4, p. 86, l. 33: Replace
"takes two elements and is denoted" by
"takes two elements X and Y and maps Suggested remedy: Change
                                                                   Agree
this to a third element denoted by".       accordingly.
Suggested remedy: Change
accordingly.




(TR) Clause 8.2a.4, p. 86, l. 19: The
256-bit prime curve P-256 is not
defined in RFC 2409, but in RFC 5903,
Section 3.1 (256-bit Random ECP
Group). While the paragraph refers to
the IANA repository related to RFC
2409, this leaves some unclarity, since Suggested remedy: Change   Disagree
the curve in question is specified in   accordingly.
RFC 5903 (and coincides with the P-
256 curve in FIPS Pub 186-2 or
secp256r1 in SEC2-v2) and the
reference to the IANA registry is not
provided. Why not refer to the relevant
RFC 5903 or equivalent FIPS Pub 186-
(TR) Clause 8.2a.1, p. 84 ff.: The stated
purpose of 802.11s is as follows:
"Purpose: The IEEE 802.11 standard
provides a four-address frame format
for exchanging data packets between
stations for the purpose of creating a      Suggested remedy: Introduce
Wireless Distribution System (WDS),     certificate-based public-key key
but does not define how to configure or agreement scheme as well, so as to
use a WDS. The purpose of this          reap scalability and simplicity of user
amendment is to provide a protocol for interface benefits pointed out above.
auto-configuring paths between         Alternatively, please explain
stations over self-configuring multi-hop carefully why that approach was not Disagree
topologies in a WDS to support both      considered. Same remark for an
broadcast/multicast and unicast trafficover-the-air scheme for shooting in
in a Mesh using the four-address frame passwords, so as to bootstrap the
format or an extension." It is unclear password-based key agreement
how a password-based authentication         scheme.
scheme furthers this purpose, since it
(1) seems to assume a user interface
that allows provision of password
string; (2) seems to require set-up of
passwords for each pair of devices that
wish to communicate (thereby, not
"modulo-4 294 967 296" Because you
are using spaces for the separateors,
the phrase here is really ambiguous;        Make clearer                          Principle
does the modulo apply only to the "4",
or to the entire 10 digit number?
"modulo-4 294 967 296" Because you
are using spaces for the separateors,
the phrase here is really ambiguous;        Make clearer                          Principle
does the modulo apply only to the "4",
or to the entire 10 digit number?

"then the STA shall send the CTS
frame after SIFS, without regard for the
NAV and the RAV, and without
resetting, its NAV" This sentence loses
                                            Make clearer.                         Agree
me. Should there not be a comma
between "resetting" and "its", or is
something else trying to be
communicated?
"robe Response"                          "probe Response"                         Principle

"Nothing"                                "the Nothing state"                      Agree

                                         "transitions back to the Nothing
                                         state" "Nothing" should be italicised.
"transitions back to Nothing"            Also, any place in this section a        Agree
                                         state is mentioned, it should be
                                         appended with the word "state"




How about a reference to something       Add a reference to information about
                                                                                  Disagree
about Dragonfly?                         Dragonfly




"dot11RSNAConfigPasswordValueTabl "dot11RSNAConfigPasswordValueT
                                                                                  Agree
ee"                                      able"




"in7.3.2.104.2"                          "in 7.3.2.104.2"                         Agree

"modulo-4 294 967 296" Because you
are using spaces for the separateors,
the phrase here is really ambiguous;     Make clearer                             Principle
does the modulo apply only to the "4",
or to the entire 10 digit number?
"one more"                               "one or more"                            Agree

"in11C.10"                               "in 11C.10"                              Agree

"a RTS"                                  "an RTS"                                 Agree
5.2.13.3 defines the mesh STA. It
states "a mesh STA does not
                                          Remove requirement 4) or state that
implement the following subset of the
                                          how to retrieve this knowledge is out Principle
QoS functionality:" Consequently, a
                                          of scope of this document.
mesh STA cannot know neighboring
"HCCA times."




5.2.13.3 defines the mesh STA. It
states "a mesh STA does not
                                          Remove requirement 4) or state that
implement the following subset of the
                                          how to retrieve this knowledge is out Principle
QoS functionality:" Consequently, a
                                          of scope of this document.
mesh STA cannot know neighboring
"HCCA times."




The sentence "If a mesh STA adjusts
its TBTT, e.g., in response to a TBTT
Adjustment Request, it shall adjust the
MCCAOP reservations accordingly by        Add an editorial note that explains
modifying the MCCAOP Offset of each the basic idea behind this                  Principle
MCCAOP reservation." implies that the adjustment
absolute point in time of an MCCAOP
reservation remains the same. Maybe
we should add an editorial note here.

The EDCAF of an MCCA mesh STA             Add "EDCA TXOPs of a mesh STA
should not access the WM during an        that has dot11MCCAActivated true
MCCAOP. Thus, the EDCAF needs to          shall not                             Agree
be limited from accessing the WM. This extend across any of its tracked
behavior is similar to a FH PHY EDCA      MCCA reservations." to the end of
The MIC element is actually extensible. "Yes" in column Extensible         Agree




The PXU element is actually extensible. "Yes" in column Extensible         Agree




Destination External Address is not    Change number of octets in figure
                                                                           Agree
always present                         into "0 or 6"




The PERR element is actually
                                       "Yes" in column Extensible          Agree
extensible.
The PREP element is actually
                                      "Yes" in column Extensible          Agree
extensible.




The PREQ element is actually
                                      "Yes" in column Extensible          Agree
extensible.




                                      Change number of octets in figure
MCCAOP Owner is not always present.                                       Agree
                                      into "0 or 6"




The MCCAOP Teardown element is not
                                      delete "Yes" in column Extensible   Agree
extensible.
                                            Change number of octets in figure 7-
MCCAOP Reservation field is not             95o146 MCCAOP Setup Reply
                                                                                   Agree
always present.                             element format below MCCAOP
                                            Reservation into "0 or 5"




The Mesh Peering Management
element is not extensible, because the
                                            delete "Yes" in column Extensible      Agree
existence of the Peer Link ID is inferred
from the length field.




The Link Metric Report is actually
extensible, because the length of the
metric field is fixed in an MBSS and
known to the mesh STA. It is only set to "Yes" in column Extensible                Disagree
variable in 7.3.2.98, because different
link metrics with different lengths can
be used in different MBSSs.




lines 1-44:
The GANN element should provide
                                            as in comment                          Principle
some means for selecting between
different mesh gates.
                                        change "Proxy Update Confirmation
                                        frame allows inclusion of multiple
                                        Proxy Update elements." into "The
element type is wrong. missing articles Proxy Update Confirmation frame      Principle
                                        allows the inclusion of multiple
                                        Proxy Update Confirmation
                                        elements."




                                        - make order just "4"
I think it is not necessary to have a '- replace entry in column Notes with Disagree
separate order for each PXUC element. "One or more Proxy Update
                                        Confirmation elements"
                                        change "Proxy Update frame allows
                                        inclusion of multiple Proxy Update
missing article                         elements." into "The Proxy Update    Agree
                                        frame allows the inclusion of
                                        multiple Proxy Update elements."
                                        - make order just "4"
I think it is not necessary to have a   '- replace entry in column Notes with Disagree
separate order for each PXU element.    "One or more Proxy Update
                                        elements"


whole clause: The concept of the PXU
sequence number seems to be a little    as in comment                        Principle
bit crude. Needs improvement.




                                        Change "MAC address of the
The value has to be described from the recipient of the PXU" into "MAC
                                                                             Agree
originator of the PXUC.                 address of the originator of the
                                        PXUC"
A destination mesh STA cannot contain
                                         Correct this.                          Principle
multiple PXUC elements.




                                         ... is transmitted in a Proxy Update
better use indefinite article                                                   Agree
                                         Confirmation frame ...
                                         ... is transmitted in a Proxy Update
better use indefinite article                                                   Agree
                                         frame ...
use name of subfield instead of bit2
                                         as in comment                          Principle
(numbers might change).

missing article                          Effect of receipt of a PXU             Agree

comma too many                           delete comma after Number              Agree


A multi-hop action frame is not
propagated. Propagated means that
the recipient processes the frame, may change "propagated" into
                                                                                Principle
change its content, and retransmits this "transmitted"
(modified) frame. PREQ is an example
for this.


missing article                          ... has a large number of ...          Agree

                                         change "However, the standard
wording                                  allows other usage of the PXU          Agree
                                         element." into "However, the
                                         standard also allows other usages of
                                         Proxy mesh gates and source mesh
plural makes it more general                                                    Agree
                                         STAs of ...
                                         change "the external STAs' MAC
wrong use of apostrophe                  addresses" into "MAC addresses of Agree
                                         the external STAs"
                                           - make field Proxy MAC address the
lines 1-65:
                                           originator MAC address.
It should be possible to include proxy
                                           - include a flag in the Flags subfield,
information where the originator of the
                                           that indicates whether the originator
PXU is the proxy and proxy information                                               Principle
                                           is the proxy or a different proxy
where a different mesh gate than the
                                           MAC address is given in the proxy
originator is the proxy in the same PXU
                                           information field.
element in a byte efficient way.
                                           - include a proxy MAC address i




                                           change into "PXU Recipient MAC
The field name "Destination Mesh STA
                                           Address" and change description in Principle
Address" is confusing.
                                           lines 39-40 accordingly.




                                           change "proxied by the mesh gate"
be more specific with terminology                                                    Agree
                                           into "proxied by the proxy mesh




                                           change "otherwise" into "if the proxy
otherwise is not defined                                                             Agree
                                           information is to be added"




There is only one field called Number of
                                           fields --> field                          Agree
Proxy Information.
                                           change "that proxies external
                                           stations specified by Proxy
wording                                    Information fields in the Proxy           Agree
                                           Update element" into "that proxies
                                           the external stations specified in the
                                           Proxy Information fields of the Proxy
                                          change "the MAC address of the
be more specific with terminology         mesh gate" into "the MAC address   Disagree
                                          of the proxy mesh gate"
proxy mesh STA                            proxy mesh gate                    Agree



lines 12-15:
The concept of the PXU sequence
                                          as in comment                      Principle
number seems to be a little bit crude.
Needs improvement.




lines 44 and 48:
                                          delete "adjust the Reports
The reports are the wrong place for the
                                          accordingly by" and correct        Principle
adjustment. The tracked reservations
                                          grammar (two occurences).
need to be updated.
lines 42-49:
The need for adjustments depends on
the time base that is used for tracking   as in comment                        Principle
the reservations. The shall should be
as vague as possible in this respect.




                                          - Change heading into "Interaction
                                          with time synchronization and
                                          MBCA"
lines 42-49:                              - Make the two sentences separate
TBTT adjustment is part of MBCA, not      paragraphs because they deal with    Disagree
time synchronization.                     different mechanisms.
                                          - Swap the two sentences so that
                                          the order corresponds with the
                                          heading.




This clause fits better behind 9.9a.3.10 Move clause behind 9.9a.3.10          Agree
whole clause: The whole clause of
MCCA needs improvement. Especially
the concept for the MCCAOP
Advertisements is not clear. Right now,
                                          Improve clause on MCCA. Provide a
different levels (set of tracked
                                          description of the concept of MCCA
reservations, advertisement, MCCAOP                                            Principle
                                          advertisements and define and use
Advertisements element) are mixed
                                          corresponding terminology.
together and not clearly distinguished.
This leads to gaps in the specification
and to confusion with the reader /
implementor.




whole clause: What happens if some
MCCAOP Advertisements elements are
lost (not received)? How can a mesh
                                          Specify.                             Principle
STA know whether it received the
complete set of tracked reservations of
its neighbor?
                                              Include an Advertisements
                                              Sequence Number into the MCCA
whole clause, also related to 9.9a.3.8:
                                              Information field of the MCCAOP
How do I know that two MCCAOP
                                              Advertisements element. Same
Advertisements elements belong to the
                                              Advertisements Sequence Number        Principle
same advertisement, that is that they
                                              means same point of time of tracked
represent the tracked reservations at
                                              reservations, different sequence
the same point in time?
                                              number means different
                                              advertisements.




whole clause, also related to clause
7.3.2.106: It is not possible to do a
                                              Provide a mechanism for partial
partial advertisement of MCCAOP
                                              MCCAOP advertisements. Include a
reservations. This is especially useful, if                                         Principle
                                              Partial subfield in the MCCA
there are many tracked MCCAOP
                                              Information field.
reservations and only new reservations
are to be advertised.
whole clause, also related to clause
7.3.2.106: What is the mapping
between tracked reservations and       Define the mapping.              Principle
MCCAOP Advertisements elements? I
assume it can be arbitrary?




lines 1-3:
What are "MCCAOP Advertisements
carried in the MCCAOP Advertisements
element"? An MCCAOP
Advertisements element carries only
                                       Clarify and provide a complete
MCCAOP reservations, but does an
                                       description of the concept of    Principle
"Advertisement Identifier" identify
                                       MCCAOP advertisements.
MCCAOP reservations in an MCCAOP
Advertisements element? The
"Advertisement Identifier", however,
looks also like an index of multiple
MCCAOP Advertisements elements
whole clause. The names of the
subfields "Last Advertisement" and
"Advertisement Identifier" are
confusing. What is an Advertisement?
Is it the same as an MCCAOP
Advertisement element? Or is an
Advertisement the set of all MCCAOP
Advertisements elements that are used - Change subfield "Last
to describe all tracked reservations  Advertisement" into "Last
existing at a certain point of time? From Advertisements Element"
the description of the subfields, it      - change subfield "Advertisement
sounds like a mechanism that allows         Identifier" into "Advertisements     Principle
fragmentation of a set of MCCAOP            Element Index"
reservations over multiple MCCAOP           - specify and describe the concept
Advertisements elements.                    of MCCAOP advertisements fully
"Advertisement identifier" would be the and define corresponding terminolo
index starting at 0 and increasing by 1,
and "Last Advertisement" would
indicate the last index. However, then it
wouldn't be the "Last Advertisement"
and the "Advertisement Identifier", it
would be the "Last Advertisements
Element" and the "Advertisements
whole clause, also related to clause
                                        Specify the advertisement of torn
9.9a.3.10: How are torn down                                                 Principle
                                        down reservations.
MCCAOP reservations advertised?




Terminology is confusing: What is an
                                        provide a clear conceptual idea of
advertisement, whats the difference
                                        the advertisement of MCCAOP
between an advertisement and an
                                        reservations and provide the         Principle
MCCAOP Advertisements element?
                                        corresponding terminology and use
And how does it relate to the tracked
                                        it consistently.
reservations?
                                           replace "shall advertise all MCCAOP
It should actually advertise all tracked   Advertisements elements" with
                                                                                 agree
reservations.                              "shall advertise all tracked
                                           MCCAOP reservations"




lines 1-5:
There are up to 7 last advertisement       swap values of Last Advertisement
                                                                                 Principle
elements and only one that is not the      subfield.
last one.
lines 61-65:
To which one(s) of the 8 MCCAOP
                                          Specify. Be more precise.   Principle
Advertisements elements should this
specification applied?.




lines 61-63:
The Last Advertisement subfield should
be set to 0, because it wouldn't be the   as in comment               Principle
last element if there were more than 8
possible.
"in a number MCCAOP
                                         "in multiple MCCAOP
Advertisements" needs editorial                                                  Agree
                                         Advertisements"
improvement.




The Last Advertisement subfield should
be set to 1, because it is the last      as in comment                           Principle
element.




Make the two cases (all MCCAOP
                                         insert line break before "If the mesh
reservations in a single element or in
                                         STA reports the tracked                 Agree
multiple elements) separate
                                         reservations in a number ..."
paragraphs.
Beacon and Probe Response contain a change "of neighboring mesh STAs
Mesh Configuration element, MCCAOP with the MCCA Enabled subfield of
Advertisments not. What is meant to be the Mesh Capability field in the
said? A list of frames from neighbor        Mesh Configuration element equal    Principle
mesh STAs that contain MCCAOP               to 1" with "from neighboring mesh
advertisements, or that these neighbor STAs with dot11MCCAActivated
mesh STAs have MCCA activated?              being true"




                                            ... frames from neighboring mesh
use "receive from" instead "receive of"                                         Agree
                                            STAs ...




Why is the sentence "The DA field of
the individually addressed frame in this
context might not be set to an individual
address, if the frame uses 4 address or Delete commented sentence               Agree
6 address format." here? I doesn't
seem to be necessary and almost to be
a tautology.
The overlap of MCCAOP reservations
can be verified with any DTIM interval.
The benefit of this kind of DTIM interval Rephrase sentence accordingly.        Principle
is, that the overlap does not change
between DTIM intervals.




verb missing                              with n being a non-negative integer   Agree




MCCAOP Setup Request is a general
                                          lower case for "setup request"        Agree
term.
All MCCA-related information elements
are called MCCAOP yyy element.
Which is logical, because they setup
MCCAOPs. The corresponding frames
are sometimes called MCCA yyy frame,
sometimes MCCAOP yyy frame. A
                                         provide consistent naming of
consistent use of MCCA / MCCAOP in
                                         MCCA(OP) frames throughout the        Principle
the names of the frames is beneficial.
                                         draft.
Calling frames MCCA yyy might help in
easily distinguishing elements and
frames, but calling both elements and
frames MCCAOP yyy makes it possible
to use generic terms such as MCCAOP
setup request.




The MCCAOP Setup Reply is 4 or 9. It - make total length "4 or 9"
                                                                               Agree
is not extensible.                       - delete "Yes" in column Extensible
lines 62-65:
Strange values of Last Advertisement
                                               Swap values.                           Principle
subfield: 0 is true and 1 is false (if it is
the last element -->0, ...)




It's an MCCAOP Advertisement
                                               This primitive requests that the MAC
Request. If it's the request but not the
                                               entity sends out an MCCAOP
frame, not upper case for                                                             Agree
                                               Advertisements Request frame to
advertisements request. Spelling
                                               the peer MAC entity.
mistakes.




                                               - Change "MCCA Advertisements
The MCCAOP Advertisements frame
                                               element" into "MCCAOP
has to be able to carry multiple MCCA
                                               Advertisements element"
Advertisements elements (which is                                                     Agree
                                               - insert in column Notes: "One or
actually an MCCAOP Advertisements
                                               more MCCAOP Advertisements
element).
                                               elements (7.3.2.106 (...)).
I don't think it is necessary to have a     make order just "3", delete
different order number for each of the      "Repeated N times (N is a number
                                                                                  Disagree
possible multiple Congestion                of Congestion Notification element
Notification elements.                      contained in the frame)."




The content of the note is not              Make the note a normal paragraph
                                                                                  Agree
explanatory, it is required (normative).    by deleting "Note-"




11C.12.4 says that the beacon timing
element is only present if the status
                                            change "When the Status Code is
code is 78, but not if the status code is
                                            set to non-zero value," into "When    Agree
1 (which is also non-zero).
                                            the Status Code is 78,"
Furthermore, the status code is not set,
a value is received from the SME.




                                            Change "This primitive initiates
                                            transmission of a response to the
                                            specific peer MAC entity that
                                            requested the TBTT adjustment."
frames are transmitted                      into "This primitive initiates the    Agree
                                            transmission of a TBTT Adjustment
                                            Response frame to the specific peer
                                            MAC entity that requested the TBTT
                                            adjustment."




                                            change "as a response to" into "as
There is only a specific response                                                 Agree
                                            response to"
be more specific                            of a mesh STA                          Agree




lines 50-52:
11C.12.4 says that the beacon timing
                                            change "Present only when Status
element is only present if the status
                                            Code is set to non-zero value." into
code is 78, but not if the status code is                                          Agree
                                            "Present only when Status Code is
1 (which is also non-zero).
                                            78."
Furthermore, the status code is not set,
a value is received from the SME.




lines 49-52:                                Replace "Beacon Timing element"
There might be multiple Beacon Timing with "A set of Beacon Timing                 Agree
elements.                                   elements"




What is a "result response"?                keep only result, delete response.     Disagree
be more specific                          to the mesh STA               Agree




Last sentence needs thorough editorial make sentence legible. Correct
                                                                        Principle
overhaul (words missing, t missing)       spelling mistakes.




The result of the receipt is the
generation of the primitive. The SME is
                                          delete "of the results"       Agree
notified about the reception of the
frame.
lines 57-59:                             Replace "Beacon Timing element"
There might be multiple Beacon Timing with "A set of Beacon Timing         Agree
elements.                                elements"




missing article                          ... to adjust the TBTT.           Agree




There is only one result                 results --> result                Agree




                                         Change "in the TBTT Adjustment
Its the frame, not the TBTT Adjustment
                                         Response response" into "in the   Agree
Response response.
                                         TBTT Adjustment Response frame"
lines 12-16:                            Replace "Beacon Timing element"
There might be multiple Beacon Timing with "A set of Beacon Timing        Agree
elements.                               elements"




There is only one result                results --> result                Agree




There is only one result                results --> result                Agree




There might be multiple Beacon Timing
                                        Beacon Timing elements.           Agree
elements.
                                      change "of peer entity's TBTT" into
wrong use of apostrophe                                                     Disagree
                                      "of the TBTT of the peer entity"




"to be sent" is not correct           is sent                               Principle




lines 12-15:                          Replace "Beacon Timing element"
There might be multiple Beacon Timing with "A set of Beacon Timing          Agree
elements.                             elements"




be is not correct                     change "be" into "is"                 Principle
request goes with "of" or "from"          change into "of its neighboring ..."     Principle




                                          insert a field "Beacon Timing
                                          Information Count" that contains the
                                          number of Beacon Timing
Make the Beacon Timing element
                                          Information fields contained in the      Disagree
extensible
                                          Beacon Timing element. Insert
                                          "Yes" in column Extensible in table 7-
                                          26 for the Beacon Timing element.




unit of Neighbor Beacon Interval
                                          Add unit.                                Principle
subfield is missing.




lines 16-18:                              Change "are contained in this field,
The cause is not that we want to          in order to represent the time in
represent the TBTT in units of 256 us,    units of 256 us." into "are contained
                                                                                   Agree
the cause is that only 2 octets are to be in this subfield representing the
used for the TBTT. Neighbor Last          TBTT in units of 256 us." (with the
Beacon Time is a subfield.                correct character for micro)
                                        insert "from the corresponding
It is unclear which beacon frame is
                                        neighbor STA" after "Beacon frame" Principle
used.
                                        before the comma.




the reception time is used in the
Neighbor offset protocol, a specific
synchronization protocol, for
expressing the times of neighbors in
                                        delete "latest reception time of the
the local TSF. Not necessarily needed                                          Principle
                                        Beacon frame and"
here to be mentioned because the
mesh BSS might use a different
synchronization protocol than the
Neighbor Offset protocol.
                                           Change "measured in the mesh
                                           STA's local TSF timer" into
wrong use of apostrophe                                                          Agree
                                           "measured in the local TSF timer of
                                           the mesh STA"




The field name "Neighbor Last Beacon
Time" is ambiguous. Is it the time, the
mesh STA received a beacon from the
                                           rename "Neighbor Last Beacon
neighbor, or is it the TBTT of the
                                           Time subfield" into "Neighbor Last    Principle
neighbor? It is actually the latter, and
                                           TBTT subfield"
this should be reflected in the field
name in order to have self-explanatory
names.




It is not so obvious what "this element" Change "this element" into "the
                                                                                 Agree
is.                                        Beacon Timing element"




                                           ... multiple Beacon Timing
plural missing                                                                   Agree
                                           Information fields ...
                                        change "contains a neighbor STA's
                                        beacon timing information" into
wrong use of apostrophe                                                          Agree
                                        "contains the beacon timing
                                        information of a neighbor STA"




missing article                         ... if a successive tuple ...            Agree




There are not more reports, there are
only more Beacon Timing elements of     rename "More Report" into "More
                                                                                 Principle
the same report. Use self-explanatory   Beacon Timing Elements"
field names.




                                        Change "The Report Number is set
                                        to 0 in the first or only tuple of the
The beacon timing information tuple     beacon timing information" into "The
does not contain a Report Number        Report Number is set to 0 in the         Agree
subfield.                               Beacon Timing element for the first
                                        or only tuple of beacon timing
                                        information"
The Report Number subfield is not the
number of the report (that would be the
Report Status subfield) but the index       rename "Report Number subfield"
                                                                                      Principle
number of the beacon timing                 into "Index Number subfield"
information tuple. Use self-explanatory
field names.




                                            - delete "the last 4 digits (4 LSBs)
                                            of"
This is the only usage of the status        - insert "is an unsigned integer"
number, and it is with 4 bits, so it is     --> resulting text is: "The Report
                                                                                      Principle
very likely that the status number itself   Status subfield is an unsigned
will be only 4 bits.                        integer. It is set to the status number
                                            of the beacon timing information
                                            set."




The Report Status subfield does not
                                            - rename the "Report Status
contain a status. It contains a status
                                            subfield" into "Status Number             Agree
number. Use self-explanatory field
                                            subfield"
names.




                                            - rename the "Report Control field"
The Report Control field contains           into "Element Control field"
information that controls the               - change "to signal the status of the
                                                                                      Principle
interpretation of the Beacon Timing         beacon timing information tuple" into
element.                                    "to signal information about the
                                            beacon timing information tuple"
missing article                          in an IBSS                       Agree




lines 27-65:
What happens if some Beacon Timing       Clarify and provide a complete
                                                                          Disagree
elements are lost (not received at the   specification
reciever)?




lines 7-17:
Assume that the Beacon Timing
element with index 0 contains 50
Beacon Timing Information fields. Now,
a new beacon timing information          Clarify and provide a complete
                                                                          Principle
appears and is included in this Beacon specification
Timing element with index 0. What
happens to the now 51st beacon timing
information, that existed already but
does not fit into this Beacon Timing
This paragraph does not provide any
specification or information that
pertains to maintaining the status
                                         delete this paragraph.               Disagree
number. Its information should be
contained somewhere else in more
appropriate clauses.




                                         improve specification contained in
item b) is difficult to understand                                            Principle
                                         item b)




The condition is not that the mesh STA
observes the range violation, but when delete "It observes that"              Principle
the range violation exists.
                           change "of corresponding STA's
wrong use of apostrophe    TBTTs" into "of the TBTTS of the   Agree
                           corresponding STAs"




inform is the wrong verb   change informed into transmitted   Agree




missing article            of the Request element             Agree




in or at the order?        decide                             Principle
                                      insert "all" between "containing
all tuples need to be transmitted.                                           Disagree
                                      successive"




                                      remove "the in front of "new beacon
one the too many                                                             Agree
                                      timing information"




                                      change "can advertise the tuple with
There can be more than one tuple with a smaller index number" into "can
                                                                             Agree
smaller index number.                 advertise tuples with smaller index
                                      number"




inform is the wrong verb              use announce instead                   Agree
What is "newly updated"?               delete newly                             Disagree




                                       remove "the" in front of
two articles to many                   - newly updated                          Agree
                                       - beacon timing




                                       - define the matching: If x matches y
                                       - the result is that it indicates that
                                       the beacon has been received by
lines 62-65:
                                       the neighbor mesh STA
Wording of last sentence needs to be                                            Disagree
                                       - delete the last part (which means
simplified and improved.
                                       ...) because it is duplicated, and by
                                       the way, what is an incorrect beacon
                                       frame recepti




unnecessary comma                      delete comma after successfully          Agree
                                           change "neighbor mesh STAs'
                                           Beacon Timing elements" into "the
wrong use of apostrophe                                                         Principle
                                           Beacon Timing elements of the
                                           neighbor mesh STAs"




lines 54-56:
                                           replace the commented text by "of
"of which the Neighbor STA ID subfield
                                           the mesh STA."
matches either the 7 LSBs of the
                                           insert "(taking the I/G bit as the   Agree
assigned AID or the 7 LSBs of its MAC
                                           MSB)" in line 62 after "MAC
address (taking the I/G bit as the MSB)"
                                           address"
duplicates text that follows.




lines 48-50:
                                           Specify                              Disagree
What has to be done, if the MSB is 1?




a reported TBTT (beacon transmission
                                           avoid term "beacon reception
time) cannot be the beacon reception                                            Disagree
                                           timing"
timing.
What does "shall recognize the                 Use correct verb or explain
                                                                                      Principle
reported TBTT" mean?                           recognize




lines 42-45:
The note does not make so much
sense. Firstly, it is incomplete, because
the Report Control field with all its fields
is necessary to detect missing beacon
                                               delete paragraph containing the
information. Secondly, the mesh STA                                                   Principle
                                               note.
will retrieve all other beacon timing
elements already after the first beacon
timing element of a new status number,
because the status number had
changes.

                                               Change "When a mesh STA
                                               receives a Beacon frame containing
                                               Beacon Timing element that
                                               indicates only a subset of the
                                               beacon timing information set is
improve wording                                                                       Disagree
                                               contained" into "When a mesh STA
                                               receives a Beacon frame containing
                                               a Beacon Timing element that
                                               contains only a subset of the beacon
                                               timing information set"
valid beacon timing information is not
contained in the Beacon Timing
element, because this could be read
                                           Change "shall be contained" into
has being required to implement the                                              Principle
                                           "shall be included"
Beacon Timing element as data type
for storing the beacon timing
information in the implementation.



                                           Include a new clause 11C.12.4.x
                                           "Beacon timing information" which
                                           defines all terminology used within
lines 26-38:
                                           MBCA, especially beacon timing
Definition of terminology for MBCA
                                           information, beacon timing            Principle
needs improvement and better
                                           information set, beacon timing
structure.
                                           information tuple.
                                           Remove commented lines from
                                           clause 11C.12.4.2.2




lines 32-34:
This sentence (last sentence of this
paragraph) is more of a general nature. Move this to the general clause of
                                                                                 Disagree
In any way, it does not belong to the      MBCA.
procedures done in lieu of the reception
of a beacon timing element.



How can a mesh STA obtain the
beacon reception timing from a beacon
timing element? The fields in the
beacon timing information of the
                                           change "beacon reception timing"
beacon timing element are the
                                           into "TBTT" or what it actually       Disagree
Neighbor STA ID, the Neighbor Last
                                           means.
Beacon Time which indicates a TBTT,
and the Neighbor Beacon Interval. But I
guess, it is the beacon timing
information stored at this neighbor
This paragraph is specific to MCCA, not Move this paragraph to MCCA
                                                                               Disagree
MBCA.                                 specification.




                                      Change "The mesh STA shall also
                                      collect the beacon timing information
                                      contained in the Beacon Timing
                                      element from its neighbor STAs to
                                      find out the TBTT and beacon
                                      interval of STAs in 2 hop range." into
lines 10-12:
                                      "The mesh STA shall also collect the Agree
wording, missing article
                                      beacon timing information contained
                                      in the Beacon Timing elements
                                      received from its neighbor mesh
                                      STAs in order to obtain the TBTT
                                      and beacon interval of STAs in its 2
                                      hop range."




only mesh STAs can sent the Beacon    make the "neighbor STAs" to
                                                                               Disagree
Timing element                        "neighbor mesh STAs"
only mesh STAs can do the mesh            make the "neighbor STAs" to
                                                                                Disagree
discovery.                                "neighbor mesh STAs"




The TBTT and beacon interval are not
                                          change "through discovery process
obtained through the Mesh Discovery
                                          (see 11C.2 (...))" into "during the   Agree
process. They are obtained by
                                          mesh discovery process"
procedures of the base standard.




                                          Change "using the information
                                          obtained from the Beacon Timing
There are multiple beacon timing          element from its neighbor mesh
elements received. The mesh STA           STAs" into "using the information     Disagree
uses also the received beacons.           obtained from Beacon frames and
                                          Beacon Timing elements received
                                          from its neighbor mesh STAs"




Status Code 78: It is a TBTT
adjustment request. It is a mesh STA, a
non-mesh STA cannot perform this.         Change into "The TBTT adjustment
Appropriate TBTT sounds like "Please      request has not been successful
                                                                                Agree
see if you have this TBTT" and the        because the mesh STA could not
answer 78 sounds like "Sorry, I couldn't find an alternative TBTT."
find that TBTT you where asking for in
my cupboard."
lines 60-65:
                                          Provide clear specification when
Need a clear specification (conditions)                                            Disagree
                                          which status code is used.
when which status code is used.




                                          Change "When the number of
                                          beacon timing information exceeds
                                          50, multiple Beacon Timing
                                          elements are present. The elements
lines 37-39:
                                          are present in the order of Report
Do not use absolute numbers that
                                          Number field value in the Report         Disagree
might change (50 beacon timing
                                          Control field of the Beacon Timing
information)
                                          element." into "When multiple
                                          Beacon Timing elements are
                                          present, they are in the order of the
                                          value of the Report Number field of
lines 20-24:
It is sufficient to say "one or more
Beacon Timing elements". How the          Replace Notes of order 4 with "One

beacon timing elements are                or more Beacon Timing elements."         Disagree

constructed should be given in the        Delete "to (N_Info+3)" in Order

corresponding clause where the TBTT
Adjustment Response frame is




                                          delete "(i.e., when the request is not
explanation of status code is already
                                          successful due to the neighbor           Disagree
given in table 7-23
                                          constraint)"
                                        The Beacon Timing element is
                                        defined in 7.3.2.103 (Beacon Timing
divide sentence into two                                                        Agree
                                        element). It is only present if the
                                        Status ...




                                        Change "When the number of
                                        beacon timing information exceeds
                                        50, multiple Beacon Timing
                                        elements are present. The elements
lines 62-65:
                                        are present in the order of Report
Do not use absolute numbers that
                                        Number field value in the Report        Disagree
might change (50 beacon timing
                                        Control field of the Beacon Timing
information)
                                        element." into "When multiple
                                        Beacon Timing elements are
                                        present, they are in the order of the
                                        value of the Report Number field of
lines 47-51:
It is sufficient to say "one or more
Beacon Timing elements". How the        Replace Notes of order 3 with "One

beacon timing elements are              or more Beacon Timing elements."        Disagree

constructed should be given in the      Delete "to (N_Info+2)" in Order

corresponding clause where the TBTT
Adjustment Request frame is




lines 54-56:
first determine an alternative TBTT, and change sentence, actually the whole
                                                                                Principle
only if one is found, the TBTT          paragraph, according to comment.
adjustment procedure is started.
                                           Change "The TBTT Adjustment
                                           Request frame may be transmitted
                                           only if the recipient of the frame is a
                                           peer mesh STA and the recipient of
                                           the frame sets MBCA Enabled
                                           subfield in the Mesh Capability field
lines 49-52:
                                           of the Mesh Configuration element
Wording of last sentence needs to be                                                 Agree
                                           to 1." into "The TBTT Adjustment
simplified.
                                           Request frame may be transmitted if
                                           the recipient is a peer mesh STA
                                           and has set the MBCA Enabled
                                           subfield in the Mesh Capability field
                                           of the Mesh Configuration element
                                           to 1."


                                           change "in order to request that the
                                           neighbor mesh STA adjusts its
                                           TBTT" into "in order to request this
                                           neighbor mesh STA to adjust its
Improve wording, be more specific                                                    Principle
                                           TBTT"
                                           delete comma before this text
                                           (comma between "timing" and "in
                                           order to")


The text "TBTT appears last at a
particular collision timing" needs to be
improved. A TBTT does not appear           Improve text.                             Principle
(and says "Hello world!") and what is a
particular collision timing?

When beacon frames collide, the stored
TBTTs might be the same. "appears
last" cannot be used in such a situation
                                           Provide working selection criteria.       Principle
as a selection criteria. Furthermore, a
timing is a point in time, no sequential
ordering such as is possible.
be more specific with the mesh STA        ... to the neighbor mesh STA of
                                                                                Agree
whose is for persons, not for things      which the ...




lines 45-47:
The meaning of it in "it may transmit" is Change "it" into "the mesh STA        Agree
already almost two lines away.




When beacon frames collide, the stored
TBTTs might be the same. "later"
                                          Provide working selection criteria.   Principle
cannot be used in such a situation as a
selection criteria.




In a periodic environment, which the
                                          define "appears later"                Principle
TBTT is, later is the same as earlier.
The mesh STA does already know the
                                          delete "it discovers that"           Agree
TBTTs. No discovery needed.




- beacon frames do collide or do not
                                          - delete "may"
collide
                                          '- use plural "Beacon frames" (two   Agree
'- a single beacon frame cannot collide
                                          occurences)
repeatedly




"the mesh STA shall also verify if the
neighbor peer mesh STA received its
Beacon frame as described in
11C.12.4.2.4 (Receiver's procedure)"      Specify a working procedure.         Principle
this is not possible for every beacon
due to incomplete beacon information
in the Beacon Timing element, possible
timeouts in the beacon timing

lines 30-33:
                                          Rewrite sentence in such a way,
"Verify" has a little enforcement
                                          that the mesh STA checks whether
component, but the mesh STA cannot
                                          it (the mesh STA) does transmit
enforce anything at its neighbors,                                             Principle
                                          beacons during the beacon times of
especially, it cannot enforce that mesh
                                          the mesh STAs in its 2hop
STAs in its 2 hop neighborhood do not
                                          neighborhood.
transmit beacons at its TBTTs.
The first sentence doesn't make so
much sence. Firstly, one cannot            Delete the first sentence except the
monitor a Beacon Timing element. It        condition so that the remaining text
can only be processed. Secondly, that      reads:
                                                                                  Agree
the mesh STA shall process the             "When dot11MBCAActivated is true,
received Beacon Timing elements is         the mesh STA shall verify that other
already written in some earlier clause of ..."
11C.12.4.




                                           change "shall keep on monitoring"
informal language                                                                 Agree
                                           into "shall continuously monitor"




lines 26-65:
Clause 11C.12.4.4.1 and 11C.12.4.4.2
cannot be distinguished by a proactive Collapse clauses 11C.12.4.4.1/2
                                                                                  Disagree
and a reactive adjustment. In fact, they into one.
differ by which mesh STA is performing
the TBTT adjustment.
lines 36-38:
Why and how can the Report Status
subfield in the Report Control field in
the Beacon Timing element be used to
                                          Provide working mechanism if there
distinguish a large TSF jitter from a                                          Principle
                                          is a problem.
TBTT adjustment? I think this is not
possible, because there are also other
things than the TBTT adjustment that
change the status number.




a lost of Beacon frame                    a loss of Beacon frames              Agree
There is no slower direction. Time is       Use correct terminology and
                                                                                        Principle
constant and the same.                      wording.




                                            Change
                                            "Upon completion of the TBTT
                                            adjustment, the mesh STA shall
                                            change the TBTT Adjusting field in
                                            the Mesh Configuration element to
lines 30-32:                                0, and update the Report Status
The Report Status subfield in the           subfield in the Report Control field in
Report Control field in the Beacon          the Beacon Timing element as
                                                                                        Agree
Timing element is the wrong place for       described in 11C.12.4.2.1
the update of the status number, and it (Maintenance of the status
is not described in 11C.12.4.2.1.       number)."
                                            into
                                            "Upon completion of the TBTT
                                            adjustment, the mesh STA shall
                                            update the status number as
                                            described in 11C.12.4.2.1
                                            (Maintenance of the status number)




It's better to use the alternative timing   change "until its TBTT is set to the
(which does not cause beacon                timing that does not cause beacon
                                                                                        Agree
collision) as the end condition for the     collision" into "until its TBTT is set to
repeated TBTT adjustment.                   the alternative TBTT"
If the TBTT is adjusted to an alternative
                                            change "may repeat" into "shall
TBTT, the adjustment procedure should                                             Agree
                                            repeat"
not stop halfway through.




lines 22-24:
                                            If dot11MCCAActivated ist true, the
The condition has to come as the first                                            Agree
                                            mesh STA shall adjust ...
part of the sentence.




The beacon timing element is the            change the TBTT information in the
wrong place for doing the adjustment of beacon timing information that is         Principle
the TBTT information.                       stored at the mesh STA
The calculation of the TBTT of the
neighbors from the reception time of a    delete reference to 11C.12.4.2.2       Disagree
beacon is of no interest here.




neighbor STA's TBTT information
- singular, should be multiple neighbor   TBTT information of the neighbor
                                                                                 Agree
STAs                                      STAs
- do not use apostrophe




                                          When a mesh STA expects to
                                          receive a group addressed frame
                                          and CCA is IDLE for the duration of
                                          the PHY specific Group Delivery Idle
lines 1-3:
                                          Time, the receiving mesh STA may       Agree
word order
                                          assume that no more frames
                                          destined to group addresses will be
                                          transmitted and may return to Doze
                                          state.




missing space in DTIMPeriod               DTIM period                            Agree
The text says "try to assure that the
alternative TBTT does not cause
beacon collision" What is if it cannot     Specify.                           Principle
assure that the alternative TBTT does
not cause beacon collision?




What does "collect new beacon timing
information from its neighbor STAs at      Clarify. Specify. Change text
                                                                              Principle
least for its beacon period" mean?         accordingly.
beacon period is a time duration.




Be more specific about the type of the
                                           TBTT adjustment procedure          Principle
adjustment




lines 10-13:
Having item b) here is like starting the
engine in the car and than to decide
where to go or whether to go at all.       Move item b) into 11C.12.4.4.1/2   Principle
The decision for the alternative TBTT
has to be done before the adjustment
procedure is startet.
The text reads that the TBTT Adjusting
                                             Delete "to avoid beacon collision",
field is set to 1 in order to avoid beacon                                         Principle
                                             delete comma before "in order to"
collision. That does not work.




"prior to and during" means always.
During the TBTT adjustment procedure Delete "Prior to and"                         Principle
is sufficient.
lines 43-54:
Unlucky text and unlucky
specifications.
There are several issues:
- beacon reception timings are actually
TBTTs. Reception timings are not
known.
- beacon frames can be sent across
reported TBTTs, but this does not help
with the hidden node problem for          Rewrite the clause and consider the
beacon reception.                         issues of the comment.                Disagree
- the apostroph is usually only used      neighbors' --> of the neighbors
with living things (humans), with dead
things only as an exception
- what are non-essential beacon
reception timings?
- the text talks about timings that are
only from neighbor peer mesh STAs,
but the text uses neighbor mesh STA
only, which might be a larger set of
mesh STAs




How do I know the neighbor's beacon
reception timing? I might know its
                                          Correct this.                         Disagree
TBTT, but not its beacon reception
timing.
Mmmh. But I am allowed to send
beacons in order to disturb the beacons Correct this.                                   Disagree
of my neighbors?




lines 33-46:
The average duration of the last 16
received beacons is not expected, it is
known. How can I compute something             Provide a correct description of
that happened at a neighbour but not at dot11MeshAverageBeaconFrameDu
                                                                         Principle
the mesh STA? How about if different ration. If it is neighbor-specific,
neighbours have quite different beacon remove it from the MIB.
reception times due to different data
rates? If it is neighbor specific, it should
not be in the MIB.




                                               "NOTE--Delayed beacon
                                               transmissions allow mesh STAs to
                                               discover Beacon frames that are
                                               transmitted from multiple mesh
lines 1-3:
                                               STAs with TBTTs close to each            Agree
wording
                                               other. It is recommended to set
                                               dot11MeshDelayedBeaconTxMaxD
                                               elay to a time longer than the typical
                                               duration of Beacon frames."
All beacon transmissions are delayed   Change heading into "Delayed
                                                                            Agree
randomly, not just a single one.       beacon transmissions"




                                       Make the delayed beacon
Clause 11C.12.4.6 makes also much      transmissions independent from the
sense without the MBCA mechanisms      MBCA mechanism based on the
described in the previous subclauses of Beacon Timing element as
11C.12.4. The delayed beacon           described in clauses 11C.12.4.1-4:
transmissions can be independently     - move clause 11C.12.4.6 up so that Disagree
controlled from MBCA                   it becomes clause 11C.12.5
(dot11MeshDelayedBeaconTxInterval = - remove all references to MBCA in
0 switches it off independent from     the description of
dot11MeshMBCAActivated                 dot11MeshDelayedBeacon_X
                                       parameters in D.3
lines 59-65:
paragraph is not easily understandable. Clarify. Provide easily to understand
Lots of guessing, especially about the   specification of delayed beacon        Principle
meaning of                               transmissions.
dot11MeshDelayedBeaconTxInterval.




lines 5-9:                               "This attribute specifies the
"This attribute shall specify the        minimum delay from a TBTT of
minimum delay time from a TBTT for       delayed beacon transmissions for
                                                                                Agree
the delayed beacon transmission, for     the purpose of MBCA. The value is
MBCA purpose. The value is               expressed in units of
expressed in units of microseconds."     microseconds."




lines 55-57:                             "This attribute specifies the
"This attribute shall specify the        maximum delay from a TBTT of
maximum delay time from a TBTT for       delayed beacon transmissions for
                                                                                Agree
the delayed beacon transmission, for     the purpose of MBCA. The value is
MBCA purpose. The value is               expressed in units of
expressed in units of microseconds."     microseconds."
lines 40.42:
                                             "This attribute specifies the interval
"This attribute shall specify the interval
                                             of the delay of beacon transmissions
of the delayed beacon transmission, for
                                             for the purpose of MBCA. The value Principle
MBCA purpose. The value 0 indicates
                                             0 indicates that the delayed beacon
that the delayed beacon transmission is
                                             transmission is disabled."
disabled."




lines 31-43:
An interval is a time duration and needs provide a unit of time                       Principle
a unit of time.




"This attribute shall specify ..." - Shall
requires some action that has to be          "This attribute specifies ..." in all
                                                                                      Agree
done. It is not used with "specify",         occurences in D.3
multiple occurences.




missing article                              The Beacon Timing element is ...         Agree
lines 44-47:
                                         - change "shall activate" into "shall
- Activated does not mean to Activate
                                         use"
something. that has been done already.                                           Principle
                                         - and shall set the MBCA Enabled
- repeat shall
                                         subfield
- missing article




                                         change "cannot be received" into
wording                                                                          Agree
                                         "might not be received"




                                         "from the so-called hidden node
missing article                                                                  Agree
                                         problem"




The MBCA as specified is not capable
of resolving hidden node problems of
                                         change "to resolve" into "to mitigate" Agree
beacons, it can only mitigate these
hidden node problems.




missing article                          using the START primitve                Agree
                                           Delete
                                           dot11MeshBeaconTimingReportMax
                                           Num from draft:
The maximum number of Beacon
                                           - delete first sentence of this
Timing Information fields contained in a
                                           paragraph.
Beacon Timing element is limited by
                                           - delete " and                    Disagree
the max IE size of 257 octets. An
                                           dot11MeshBeaconTimingReportMax
MLME parameter or a value of 50 is not
                                           Num" from line 52.
necessary for this.
                                           - delete
                                           dot11MeshBeaconTimingReportMax
                                           Num from Annex D.




lines 46-48:
First sentence needs to be improved.
                                           Make first sentence legible.      Principle
What are "MBSS, IBSS, and
infrastructure BSS Beacon frames"?
                                         Change "The TBTT Adjusting
                                         subfield is set to 1 while the TBTT
                                         adjusting procedure is on going to
                                         notify that the mesh STA's TBTT is
                                         shifting intentionally, and is set to 0
lines 53-56:                             otherwise. (See 11C.12.4.4.3
There is no unintentional TBTT           (Adjustment procedure).)" into "The Principle
Adjustment procedure.                    TBTT Adjusting subfield is set to 1 in
                                         order to notify that the TBTT
                                         adjustment procedure is ongoing,
                                         and is set to 0 otherwise. (See
                                         11C.12.4.4.3 (Adjustment
                                         procedure).)"




The MBCA Enabled subfield is not set
to 1 when MBCA is activated. It is set to Change "activated" into "used"           Disagree
1 when MBCA is used.




Why only 16 s? The largest possible
beacon interval is 2^26 us (=67,1 s).    don't give an absolute time value         Principle
How about lost beacons?




lines 26-38:
The beacon timing information is         make the paragraphs a separate
something different than the calculation clause ("Beacon timing                    Principle
of the neighbor STA's TBTT (the          information").
heading of the clause).
lines 22-24:
Whether the mesh STA stores the
TBTT as 64 bits or as an "abbreviated        remove paragraph.                 Disagree
TBTT" is an implementation specific
detail.




lines 16-20:
                                             add time basis (TSF timer of
The time basis (transmitter or receiver)                                       Disagree
                                             recipient or transmitter)
has to be given clearly.




lines 9-24:
Clause 11C.12.3.2 tells me one thing
and its details: certain information can
be used from any received beacon,            Specify the actions to be taken
                                                                               Disagree
other information only from beacons          when receiving a beacon.
where there is a peering with the
transmitter. Is that all what I have to do
when a mesh STA receives a beacon?
lines 7-54:
The beauty of the Neighbor Offset
protocol is its simplicity due to its
restriction to a single link or in other
words, its per neighbor scope, i.e. each
neighbor is considered completely
independent. No chain reactions in the
multihop environment. By the way, this
property of independet neighbor offsets
                                              Remove clause 11C.12.2.2.3.           Disagree
is the main reason, that the Neighbor
Offset protocol is acceptable as the
mandatory default synchronization
protocol.
The clock drift adjustment which is
proposed in 11C.12.2.2.3, however,
breaks this property. It will lead to chain
reactions in the complete mesh BSS.
The goal of the Neighbor Offset
protocol is to know the TSF timer of the




lines 2-5:
                                              Move last two sentences into clause
The last two sentences are of general                                               Disagree
                                              11C.12.2.2.1 General
content.




first sentence of paragraph is                Remove first sentence. Check
description of mentioned MLME-SAP             10.3.75 whether it contains this      Disagree
interface and does not belong here.           information.
MLME-
                                           add parameter peerMAC to MLME-
MeshNeighborOffsetMeasure.confirm
                                           MeshNeighborOffsetMeasure.confir Principle
cannot be bound to the corresponding
                                           m
request.




                                           - write the negative and positive
write the negative and positive values     values in "valid range" (see
of the valid range. The implementer has 10.3.16.2.2 of 11mb D4.0 as an
                                                                                   Principle
to think of a correct representation in its editorial example)
code.                                      - remove ", expressed in twos
                                           complement"



                                           Reduce commented text to:
                                           "The mesh STA shall update the
                                           timing offset value with respect to
                                           the neighbor mesh STA based on
lines 34-65:                           time stamps from the
clause 11C.12.2.2.2 contains very good received Beacon and Probe
explanations of the timing offset      Response frames. The unit of the            Disagree
calculations, but most of them are         timing offset value is microseconds.
actually implementation specific.          The mesh STA shall
                                           keep the timing offset value that has
                                           been calculated from the latest
                                           Beacon or Probe Response frame
                                           received from each
It is obvious, that this is for the
Neighbor Offset protocol, and it is
                                          Remove "When
specified somewhere in the draft, that
                                          dot11MeshActiveSynchronizationPr
the Neighbor Offset protocol is used                                              Disagree
                                          otocol is 0 (Neighbor Offset
when
                                          Protocol),", make "the" into "The".
dot11MeshActiveSynchronizationProto
col is 0.


                                          make 3 dashes:
                                          - after an MLME-RESET.request
                                          primitive
lines 36-44:
                                          - before an MLME-JOIN.request           Disagree
put all cases into list.
                                          primitive
                                          - before an MLME-
                                          MeshNeighborOffsetSync.request
                                          primitive



lines 22-24:
This text is the description of the       Remove paragraph. Check 10.3.75
                                                                                  Disagree
corresponding MLME SAP interface,         whether it contains this information.
belongs to clause 10.3.




lines 42-44:
The MLME-MeshNeighborOffsetSync           Provide a general MLME-Interface
is specific to a specific synchronization that starts the TSF in the MBSS / on
protocol. Although the Neighbor Offset the mesh STA and that can be used Principle
Protocol is the default synchronization   with any synchronization protocol of
protocol, an MBSS might use a             the extensible framework.
different one.
"This primitive is generated by the SME "This primitive is generated by the
to order the maintenance of the           SME to start the Neighbor Offset
                                                                                  Agree
Neighbor Offset Synchronization with      Protocol with the specified neighbor
the specified neighbor mesh STA."         mesh STA."




lines 16-20:                              What has to be achieved with the
The text "The mesh STA should             Neighbor Offset protocol?
maintain synchronization with up to the - TSF in an MBSS
dot11MeshNbrOffsetMaxNeighbor             - this means, at least all (neighbor)
neighbor mesh STAs that are in the        peer mesh STA should be
same the MBSS. Additionally, the mesh synchronized
STA should maintain synchronization       - since beacons do not care about
with up to the                            peerings, it would be useful to be
dot11MeshNbrOffsetMaxNeighbor             able to be synchronized with all
neighbor STAs that are outside of the     mesh STAs of an MBSS
MBSS." in its current form provides       - synchronization with STAs outside
ambiguities and some problems:            the MBSS is optional and an             Disagree
- dot11MeshNbrOffsetMaxNeighbor is        additional benefit. This can be
used twice, for the neighbor mesh STA treated more open to
of the same MBSS as well as the           implementation.
neighbor STAs outside the MBSS.           Proposed changes:
- synchronization seems to be optional * Change text into:
in the neighbor offset protocol (should   "The mesh STA shall maintain
maintain synchronization), but the TSF synchronization with all neighbor
has to be used in the MBSS.               mesh STAs that are in the same
- all mesh STAs of an MBSS have to        MBSS. Additionally, the mesh STA
use the same TSF, in this case the        should maintain synchronization
Neighbor Offset protocol. So, a mesh      with neighbor STAs that are outside
                                            Change "Although a mesh STA may
                                            include multiple implementations of
                                            the synchronisation protocol, all the
                                            mesh STAs in an MBSS shall use
lines 3-5:                                  the same synchronisation protocol."
Restriction to only a single                into "Although a mesh STA may
                                                                                     Principle
Synchronization Protocol in use is          include multiple implementations of
missing. Some editorial things.             synchronisation protocols, only one
                                            synchronization protocol shall be
                                            used by a mesh STA at a time and
                                            all mesh STAs in an MBSS shall use
                                            the same synchronisation protocol."



                                            Change "... is specified by the
                                            Vendor Specific element that is
                                            present in the frame." into "... is
There might be more than one Vendor
                                            specified by a Vendor Specific           Agree
Specific element in the frame.
                                            element that is present in the
                                            frame." Also do this change in
                                            clauses 7.3.2.96.2 to 7.3.2.96.7.




                                            Change "... in the Vendor Specific
There might be more than one Vendor
                                            element)" into "... in a Vendor
Specific element in the frame. Full stop                                             Agree
                                            Specific element.)" Also do this
is missing at the end of the sentence.
                                            change in Tables 7-43br to 7-43bw.




                                            Change "... indicates the
                                            synchronization protocol that is ..."
A BSS uses a timing synchronization
                                            into "... indicates the timing           Principle
function, not a synchronization protocol.
                                            synchronization function that is ...",
                                            check throughout draft as well.
                                          Change "However, to accommodate
                                          various application needs, the
                                          framework allows flexibility to
lines 62-64:
                                          integrate future synchronization
Too many parts of the sentence in front
                                          protocols for MBSSs." into "The         Disagree
of subject. Flexibility is provided not
                                          framework allows to integrate other
allowed.
                                          synchronization protocols for
                                          MBSSs in order to accommodate
                                          various application needs."




There can be only exactly one default.    change into "as the default"            Agree




                                          Change the last sentence of the
                                          paragraph "Mesh STAs receiving a
What does "accept the timing              Beacon frame may accept the timing
information" mean"? Does it mean "I       information depending on their
believe that it is your TSF timer." or    active synchronization protocol." into Principle
does it mean "I make it to my TSF         "Mesh STAs receiving a Beacon
timer."?                                  frame use the timing information
                                          according to their active timing
                                          synchronization function."


The "active synchronziation protocol" is - change "active synchronization
actually the "active timing              protocol" into "active timing
synchronization function". A reference    synchronization function"
                                                                                  Principle
is missing to the clause where the        ' do the change from
reader can learn something about the      "synchronization protocol" to "timing
active in front of TSF.                   synchronization function" throughout
                                          the draft.
                                            - move 11C.12.1 to 11.1.1.3
lines 40-50:                                - change title into "TSF for an
This paragraph is a very general text of MBSS"
                                                                                     Principle
the TSF for an MBSS and should be           - remove last paragraph (lines 49-
moved to 11.1.1.3                           50) because they are implicit if this
                                            clause is in 11.1.




                                            make it a separate clause
lines 27-31:
                                            "Initialization of the TSF timer". The
This paragraph about the initialization
                                            last sentence needs to be moved          Disagree
of the TSF timer of a mesh STA is not
                                            somewhere else (TSF timer
general but very specific.
                                            adjustment).




IEEE 802.11mb D4.0 defines in 11.1.1
clauses with "TSF for {infrastructure
                                            provide clause 11.1.1.3 "TSF for an
networks | an IBSS}". The                                                            Principle
                                            MBSS"
corresponding clause for an MBSS is
missing.




lines 19-21:
An uncited definition in IEEE 802.11
says: "A Timing Synchronization
                                            Align these. Preferably use the
Function (TSF) keeps the timers for all
                                            timing synchronization function
STAs in the same BSS synchronized.
                                            terminology and define the               Disagree
All
                                            synchronization protocol(s) of 11s
STAs maintain a local TSF timer." This
                                            as the TSF in an MBSS
is also applicable for the mesh BSS,
but it is somehow different from the text
defined in 11s.
MSDU Length in A-MSDU (addition of
Mesh Config to byte numbers in frame).
                                         Check this.                               Principle
Is 2304 the correct number of bytes in
figure 7-17c?




whole clause: Is the Mesh Control in     If it is not in the MSDU, text needs to
                                                                                   Principle
the MSDU or in the frame?                be adopted that it is in the frame




Mesh Flags field, Mesh TTL field, Mesh Mesh Flags subfield, Mesh TTL
Sequence Number field, and Mesh          subfield, Mesh Sequence Number
                                                                                   Agree
Address Extension field are actually     subfield, Mesh Address Extension
subfields of the Mesh Control field.     subfield throughout the draft.




lines 16-63:
Figure 5-6b should also show the case,
                                         as in comment                             Principle
where just a separate and single mesh
AP is shown: (Mesh Gate - DS - AP)
It is not clear why only proactive PREQ
                                             Suggest to add more informative
mechanism has this informative text.
                                             text on other proactive path
Discuss if it is still needed, or if it is                                            Principle
                                             discovery mechanism. Otherwise,
better to describe other proactive path
                                             the subclause should be removed.
discovery mechanisms in this annex.




Errors in the TGs MIB is reported by
the WG editor. Some of the numbers           Modify the error so that the collision
                                                                                      Principle
are collided with other amendments           is resolved.
and TGs internally.




Looking at the subclause 11C.7.3, the
MP11 (Link metric reporting) sounds          Change the status to be "MP1:O".         Disagree
like an optional feature.




"if the MCCAOP responder operates in
light or deep sleep mode for the
MCCAOP owner."
This sounds contradicting with "the
                                             Clarify with an accurate text.           Principle
mesh STA shall be in
active mode or light sleep mode
towards the neighbor peer mesh STAs
with which it has established
MCCAOPs" in line 62-65 page 280.
"During the mesh peer service period,
the transmitter of the mesh peer
service period and peer mesh STA
shall operate in Awake state."
                                           As in comment.              Agree
should read
"During the mesh peer service period,
the owner and the recipient of the mesh
peer service period shall operate in
Awake state."



Remove unnecessary line feed.              As in comment.              Agree




"and may contain one or more TXOPs"
is redundant here. Also, it should be
                                           As in comment.              Principle
stated that the peer service periods can
be established bi-directionally.




The description format in this subclause
should be aligned with 11C.13.9.3.
However, there are many missing
description for the deep sleep mode,
compared with the descriptions for the     Clean up the description.   Principle
light sleep mode in 11C.13.9.3. For
instance, description such as line 16-21
for light sleep mode is missing for the
deep sleep mode.
"A mesh STA in light or deep sleep
mode may receive peer trigger frames
when its Mesh Awake Window is active
as described in 11C.13.7 (Mesh Awake Clean up the description.                 Principle
Window)."
This sentence sounds like a duplicated
description as the previous paragraph.
"DTIM Beacon and group addressed
transmissions from its peer mesh STA"
should read "DTIM Beacon and group       As in comment.                        Agree
addressed frame transmissions from its
neighbor peer mesh STA"

"for the duration of the Mesh Awake      Replace
Window and the duration of its group     "for the duration of the Mesh Awake
addressed frame transmissions,           Window and the duration of its
whichever occurs later."                 group addressed frame
However, looking at 11C.13.7, the        transmissions, whichever occurs       Disagree
Mesh Awake Window will be extended       later."
when the group addressed frame           with
transmission occurs. This means that     "until the end of the Mesh Awake
"the duration of its group addressed     Window."
frame transmissions" here is something Apply the same change to the line

"when they do not have a mesh peer
service period ongoing." What is "they" Clarify.                               Principle
here?




In figure 11C-6, "Awake Window"
                                         As in comment.                        Agree
should read "Mesh Awake Window".
"if the conditions defined in 11C.13.9.3
(Operation in light sleep mode),
11C.13.9.4 (Operation in deep sleep
mode), and 11C.13.10 (Mesh peer            Clarify.                                Principle
service periods) are met;"
However, it is not clear what is these
"conditions" are.




"The first Mesh Data or QoS Null frame
that a peer mesh STA transmits at
active the Mesh Awake Window is a
                                           Change the text accordingly.            Principle
peer trigger frame." This sentence
should be placed under 11C.13.10
(Peer service period).

                                           Add "If the Mesh Awake Window
It should be stated that the Mesh
                                           element is not contained in the
Awake Window is zero when the Mesh
                                           Beacon frame, the Mesh Awake            Principle
Awake Window element is not included
                                           Window period is zero." to the end
in the beacon frame.
                                           of the paragraph.

"A mesh STA in light or deep sleep         Change the cited text to "A mesh
mode shall be in Awake state when its      STA shall be in Awake state when
Mesh Awake Window is active." I            its Mesh Awake Window is active."
believe that all mesh STA (including       Mesh Awake Window for Active            Principle
active mode mesh STA) shall be in          mode mesh STA is not clearly
Awake state when its Mesh Awake            specified. It might be a good idea to
Window is active.                          clarify explicitly.



                                           Change to "After transmitting
"After a DTIM" is vague.                                                           Agree
                                           beacon containing DTIM,
There is no description to code AID           Add a reference to 7.3.2.6 (TIM
                                                                                     Principle
equals to 0.                                  element).




The paragraph starting from line 36 and
40 does not talk about the transition to
a lower activity level. These                 Change the text accordingly.           Principle
descriptions should belong to other
subclause.


"The non-peer mesh power mode is
indicated by the Power Management
field in the Frame Control field in
Beacon and Probe Response frames.
The non-peer mesh power mode is also
indicated with the Power Management
field in the Frame Control field in group
addressed Mesh Data frames.
The non-peer mesh STAs may send               Rewrite the text here in conjunction
                                                                                     Principle
Probe Request and Mesh Peering                with the modification in 11C.13.2.
Open Request frames only during the
Mesh Awake Window of the mesh STA
that has the Power Management field
set to 1."
I think the mesh power mode is indicatd
by the combination of the Power
Management field and Power Save
Level field. But the text says something
different. Also, "the meshNon-peer has
The subclause 11C.13.3 STA that
mesh power modes should be 4th level
subclause under 11C.13.2 (link-specific Change the clause strucutre and
mesh power modes).                                                                   Principle
                                        modify the text accordingly
Also, 11C.13.2 is a little bit difficult to
understand. It may require text
refinement.
                                              Change to "The used mesh power
                                              mode is indicated by the Power
"The used mesh power mode shall be
                                              Management field in the Frame
indicated by the Power Management
                                              Control field and the Mesh Power
field and Mesh Power Save Level field."
                                              Save Level subfield in the QoS          Principle
The utilization of this "shall" is
                                              Control field." Alternatively, remove
inappropriate. Also, the text needs to
                                              the cited sentence as similar
be more precise.
                                              sentence exists in line 63 of page
                                              273.
"The mesh power modes of mesh                 Also check other usage of "shall" in
peerings are independent and a mesh
                                              Change to "A mesh STA may have
STA may have
                                              different mesh power modes for          Agree
different mesh power modes for each
                                              each mesh peering."
mesh peering." This description is
redundant.



"Operation in light or in deep sleep
mode is optional." This is abrupt. Some As in comment.                                Principle
more informative text should be here.



                                              Specify how to signal the beacon
The sentence reads: "This standard
                                              timing information when a specific
does not impose mesh STAs to inform
                                              TBTT is deleted from the beacon
fragmented beacon timing information
                                              timing information set explicitly, so
set sequentially in its Beacon frames.
                                              that the receiving mesh STAs can
This implies that the mesh STA can
                                              obtain that deleted TBTT
advertise the tuple with a smaller index
                                              information.                            Principle
number more frequently, which is
                                              It should be a good idea to report
useful to notify the new beacon timing
                                              the fragmented beacon timing
information efficiently."
                                              information set sequentially at least
If this is the case, it is not clear how to
                                              once, when a particular TBTT is
signal the deleted TBTT using the
                                              removed from the beacon timing
Beacon Timing element.
                                              information set.
                                              Check the "shall" in clause 11C.12
                                              and other clauses and change the
                                              description accordingly. Particularly
There are some misleading utilization         in 11C.12, following should be
of "shall". For instance, "all the mesh       reexamined.
STAs in an MBSS shall use the same            "all the mesh STAs in an MBSS
                                                                                      Principle
synchronisation protocol." This is not        shall use" line 5 page 266,
actionable. These descriptions shall be "shall keep the Toffset value" line 51
corrected.                              page 266,
                                              "shall look for " line 12 page 271,
                                              line 10 page 272,
                                              "shall verify" line 31 page 271,




The congestion control signalling is
modified without having enough
justification (such as simulation results).
The benefit of the proposed method            As in comment.                          Disagree
needs to be shown. Otherwise, the
newly proposed scheme should be
removed.




This subclause contains many
dupliations with 9.22 and it is very
unclear what is intended to be
                                              As in comment.                          Principle
described here. Serious refinement is
necessary. Probably 11C.10.3.3 should
be removed.
                                         Refine the text here. Also, it should
                                         be reasonable to do the following:
                                         1. the mesh gate investigate if the
"An address unknown to the proxy
                                         destination is really not reachable
mesh gate: The mesh gate forwards
                                         from this mesh gate via external
the MSDU to the DS. Furthermore, the
                                         network (detailed procedure is
mesh gate forwards the MSDU
                                         beyound the scope of the TGs).          Principle
according to the procedures for frame
                                         2. if the mesh gate concludes that
forwarding to non-MBSS STAs." It
                                         the destination is not reachable,
seems that the description is
                                         discard the MSDU and send back a
redundant.
                                         PERR notification to the SA (source
                                         STA) of the MSDU. Optionally, the
                                         mesh gate may forward the MSDU

This subclause contains many
dupliations with 9.22 and it is very
                                         Provide a better text with better
unclear what is intended to be                                                   Principle
                                         readability.
described here. Serious refinement is
necessary.

11C.10.3 (Data forwarding behavior of
a proxy mesh gate) contains many
duplicated description as in 9.22 Mesh
forwarding framework. 11C.10.3 should
                                         It is recommended to move most of
be coupled with 9.22 and eliminate the                                           Principle
                                         the description in 11C.10.3 to 9.22.
ambiguity.
Frame forwarding is not a part of
MLME. It should be more related to
MAC services (which shall be
described under clause 9).
It is not clear which value shall be
contained in the Link Metric Report
frames, when Airtime Link Metric is
activated.
                                            Specify what shall be contained in
Also, it is not clear how the link metric
                                            the Link Metric Report frame.
is calculated for a specific directional                                         Principle
                                            Specify how the directional link
link. Does the metric value is
                                            metric is calculated and is used.
asynmetric in case of Airtime link
metric? how the directional metric value
is calculated and adopted as a link
metric?




                                            Specify when to use this reporting
                                            scheme when the default path
It is not clear when the link metric
                                            selection protocol (HWMP) and the    Disagree
reporting is used.
                                            default path metric (Aritime Lnk
                                            Metirc) is used.




In the base standard (REVmb D4.0),
subclause 11.3.0a talks about the
                                            1) Add "Self-protected Action"or
authentication, association, and frame
                                            "Mesh Peering Open/Confirm/Close
classes. I think TGs needs to amend
                                            frames" to Class 2 frames entry.
this part as well. At least, Mesh Peering
                                            2) Add some pointer information on
Management frames should be defined
                                            mesh peering for mesh BSS in
as class 2 frames (not sure if it is the                                         Principle
                                            11.3.0a.
case for Mesh Group Key
                                            3) Also, delete ", or Mesh Peering
Inform/Acknowledge frames).Also,
                                            Management frames," in subclause
there is no description on mesh peering
                                            10.3.4.1.3 and in subclause
establishment in this subclause. The
                                            10.3.5.1.3.
omission causes architectural flaw.
Need to add pointer information for
MBSSProxyUpdate.confirm primitive        Add "StatusCode" in its argument
does not have ReasonCode in its          and enumerate the ReasonCode              Principle
argument.                                explicitly in the table in 10.3.79.2.3.




The ResultCode of
MCCAADVERTISEMENT.confirm                Add TIMEOUT.                              Disagree
primitive does not contain TIMEOUT.




The ResultCode of
MCCASETUP.confirm primitive does         Add TIMEOUT.                              Agree
not contain TIMEOUT.




MeshTBTTAdjustment.confirm primitive
does not have ReasonCode in its
                                         Replace "Status Code" with
argument. The argument "Status Code"
                                         "ReasonCode" and enumerate the
should be replaced by "ReasonCode"                                                 Principle
                                         ReasonCode explicitly in the table in
and represents all confirm cases,
                                         10.3.76.2.3.
including valid status code range, and
TIMEOUT.
The ResultCode of
MeshPeeringManagement.confirm              Add TIMEOUT.                           Agree
primitive does not contain TIMEOUT.




It is very unclear what is meant by this
paragraph. Serious refinement is           Make a serious rewrite here and
                                                                                  Agree
needed. Also, this clause should be        11C.10.3.
merged with 11C.10.3.2.




                                           Add description on Address 2 thru 4.
There is no description how to se          OR remove the last sentence in the
                                                                                  Principle
Address 2 thru 4.                          first and the second paragraph of
                                           the subclause.



"(with Address Extension Mode set to
01),"
should read
                                           As in comment.                         Principle
"(with Address Extension Mode subfield
in the Mesh Flags field in the Mesh
Control field set to 01 (binary)"

                                           Change
                                           "If the frame is not discarded, the
                                           mesh STA may detect duplicate
The duplicate detection is performed
                                           MSDUs ..."
only when the MSDU is extracted by                                                Principle
                                           to
the frame reception.
                                           "If the frame is not discarded and
                                           one or more MSDUs are collected
                                           by the frame reception, the mesh
                                           STA may detect duplicate MSDUs
"the Mesh TTL field in the Mesh
Control"
should read                               As in comment.   Agree
"the Mesh TTL field in the Mesh Control
field"

"If the MSDU is received from the DS
and Address 1 (RA/DA) is a group
address, the source mesh STA,
which is a proxy mesh gate, shall
transmit the MSDU using a proxied
group addressed Mesh Data frame
(with Address Extension Mode to 01)
(see row "Mesh Data (proxied, group
addressed)" in Table 9-13
(Valid address field usage for Mesh
Data and Multihop Action frames))."
                                          As in comment.   Principle
should read
"If the MSDU is received from the DS
via a proxy and Address 1 (RA/DA) is a
group address, the source mesh STA,
which is a proxy mesh gate, shall
transmit the MSDU using a proxied
group addressed Mesh Data frame
(with Address Extension Mode subfield
in the Mesh Flags field in the Mesh
Control field to 01 (binary)) (see row
"Mesh Data (proxied, group

"with Address Extension Mode set to
00"
should read
                                          As in comment.   Principle
"with Address Extension Mode subfield
in the Mesh Flags field in the Mesh
Control field set to 00 (binary)"


"mesh data frame" should be "Mesh
Data frame". Moreover, it is not clear
what this paragraph is trying to          As in comment.   Principle
describe. It may be better to remove
the entire paragraph here.
"... in the forwarding information (mesh
STA address) or proxy information
(external address),"
should read                                As in comment.                         Principle
"... in the forwarding information (mesh
STA address) or in the proxy
information (external address),"

                                           If they are HWMP specific operation,
The lifetime or precursor list update
                                           explicitly state so, or move the
seems to be path selection protocol                                               Disagree
                                           description under HWMP subclause
specific actions.
                                           (somewhere in 11C.9)



"... the mesh STA shall check the
Address Extension Mode field ... "
should read                                As in comment.                         Agree
"... the mesh STA shall check the
Address Extension Mode subfield ..."



                                           If they are HWMP specific operation,
The lifetime or precursor list update
                                           explicitly state so, or move the
seems to be path selection protocol                                               Disagree
                                           description under HWMP subclause
specific actions.
                                           (somewhere in 11C.9)
                                            Change
                                            "d) If the frame is not discarded and
                                            one or more MSDUs are collected
                                            by the frame reception, the mesh
                                            STA may detect duplicate MSDUs
                                            referring the Mesh Sequence
                                            Number in the corresponding Mesh
                                            Control field and discard them (see
Procedures described from line 40           9.22.2.5 (Detection of duplicate
page 124 is activated only when the         MSDUs/MMPDUs))."
MSDU is collected and the MSDU is           to
                                            "If the frame is not discarded and      Principle
not discarded by the duplicate
detection. It should be explicitly stated   one or more MSDUs are collected
here.                                       by the frame reception, the mesh
                                            STA may detect duplicate MSDUs
                                            referring the Mesh Sequence
                                            Number in the corresponding Mesh
                                            Control field and discard them (see
                                            9.22.2.5 (Detection of duplicate
                                            MSDUs/MMPDUs)). When the
                                            MSDU is not discarded the mesh
                                            STA shall process the following
                                            procedures."
                                        Change the bullet and sub-bullets as
                                        follows:
                                        "b) The mesh STA shall check to
                                        see whether the Address 3 field is
                                        known; if it is an unknown address,
                                        the mesh STA shall take actions
                                        dependeding on the
"b) The mesh STA shall check to see      dot11MeshForwarding and the
whether the Address 3 field is known; if active path selection protocol. If
it is an unknown address, the mesh       dot11MeshFowrading is false, the
STA may perform any of the following    mesh STA shall silently discard the
three actions:"                         frame. If dot11MeshFowrading is        Disagree
It seems that the actions depend on the true, the active path selection
dot11MeshForwarding and active path protocol specific actions are taken.
selection protocol. The text needs to be When HWMP is used, the following
refined here.                            actions are taken:
                                        1) trigger a path discovery
                                        procedure as describe in 11C.9.XX.
                                        2) when the Address 3 is still
                                        unknown destination address even
                                        after the path discovery procedure,
                                        inform the Mesh STA specified in
                                        Address 2 that the destination is
"MSDUs that are either sent by a mesh
STA (as a consequence of a MA-
UNITDATA.request with an
individual destination address) and
destined to an address that is different
from the mesh STA at the end of a
mesh path or received from the DS with
an individual destination address shall
be transmitted using the
proxied individually addressed Mesh
Data format frame (with Address
Extension Mode set to 10), where the        As in comment.                       Principle
Mesh Address Extension subfield in the
Mesh Control field carries the
addresses of the end stations, as
specified in row "Mesh Data (proxied,
individually addressed)" of Table 9-13
(Valid address field usage for
Mesh Data and Multihop Action
frames)."
should read
"MSDUs that are either destined to an
address that is different from the mesh
The sentence "--see 11C.9.8.4
(Forwarding information))" implies that
                                            Apply the same changes to where
the forwarding information is path
                                            11C.9.8.4 (Forwarding information)
selection protocol specific. If it is the                                        Principle
                                            is cited as reference in subclause
case, it should be stated so. If not,
                                            9.22.
general forwarding information should
be described under the subclause
11C.7 (Mesh path selection and metric

"Address Extension Mode set to 00"
should read
"Address Extension Mode subfield in         As in comment.                       Principle
the Mesh Flags field in the Mesh
Control field set to 00 (binary)"
It should be stated that the forwarding
information shall be available prior to
transmitting frames. Describe what is     Add some description as a first
                                                                            Disagree
necessary if the forwarding information paragraph of this subclause.
is not available when a mesh STA
receives the MSDU to send out.




"Address 3 corresponds to the mesh
source of the group addressed Mesh
Data frame."
should read                               As in comment.                    Principle
"Address 3 corresponds to the source
mesh STA of the group addressed
Mesh Data frame."




"... or a mesh STA that receives an
MSDU/MMPDU ..."
should read                               As in comment.                    Disagree
"... or a proxy mesh gate that receives
an MSDU/MMPDU ..."




"... or a mesh STA that receives an
MSDU/MMPDU ..."
should read                               As in comment.                    Disagree
"... or a proxy mesh gate that receives
an MSDU/MMPDU ..."
"... by a proxy mesh gate and by the
source mesh STA."
should read                              As in comment.                 Principle
"... by a proxy mesh gate and by a
source mesh STA."




                                         Insert "(see 11C.10.3 and
Add a reference information to a proxy
                                         11C.10.4)" to the end of the   Principle
mesh gate.
                                         paragraph.




"When the Extension Mode subfield
equals 3 (binary: 11),"
should read                              As in comment.                 Principle
"When the Address Extension Mode
subfield equals 2 (binary: 10),"

"Address 3 and Address 4 correspond
to the destination and source end
stations of a mesh path. The Address
Extension Mode indicates the presence
of an optional Mesh Address Extension
subfield in the Mesh Control field."
should read                              As in comment.                 Principle
"Address 3 and Address 4 correspond
to the destination end station and
source end station of a mesh path. The
Address Extension Mode subfield in the
Mesh Flags field in the Mesh Control
field indicates the presence of an
optional Mesh Address Extension field
"... along with the corresponding value
of the Address Extension Mode field."
should read
"... along with the corresponding value    As in comment.                         Principle
of the Address Extension Mode subfield
in the Mesh Flags field in the Mesh
Control field."
It should be reader friendly to state
something like "Mesh forwarding
utilizes forwarding information (see
11C.9.) that is established by mesh
path selection (see 11C.7 Mesh path
selection and metric framework). The       As in comment.                         Principle
forwarding information may be updated
as a consequence of mesh forwarding.
Detals on the forwarding information
constructed by the Hybrid Wireless
Mesh Protocol (HWMP) are described
Backoff after every single group
                                           Please consider the possibility to
addressed frame transmission sounds
                                           transmit multiple group addressed
like very heavy and resource
                                           frames in the same EDCA TXOP as
consuming operation. Is the backoff
                                           in infrasrtucture network. Mesh
really needed after every transmitted                                             Disagree
                                           operation can be more efficient than
group addressed frame? In mesh BSS,
                                           IBSS. Also, random backoff does
it is very likely that there are many
                                           not help minimizing collisions in a
small size broadcast traffic, regardless
                                           hidden node scenario.
of management or data, and it could be
useful to have Last Beacon Time field
The Neighbor more efficient delivery       Consider a way to express the
can only express the time up to 16.777 beacon timing even if the neighbor
seconds. However, the maximum              STA uses the maximum beacon
beacon interval is 65,535 TU and is        interval. Maybe it is a good idea to
larger than the maximum value in the       signal the unit of the Neighbor Last
                                                                                  Principle
Neighbor Last Beacon Time field. Thus, Beacon Time field and change the
it is possible that the current Neighbor   unit of the Neighbor Last Beacon
Last Beacon Time field can not report      Time field accordingly. This also
the beacon timing even if the mesh         requires changes in clause 11C.12.4
STA recognizes the TBTT of its             (MBCA).
                                            Consider to use Active Path
Active Path Selection Protocol Identifier
                                            Selection Protocol Identifier value
value zero is assigned for HWMP.
                                            zero as a null protocol
However it should be more self
                                            represenatation. If this change is
explaining and consistent with other                                                 Principle
                                            adopted, apply the same change to
identifier value assignment that the
                                            Active Pathselection Metric Identifier
Active Path Selection Protocol Identifier
                                            and Synchronization Protocol
value zero represents null protocol.
                                            Identifier.




The MSDU size is 0-2304. However,
                                            Change the figure to specify the
the figure indicates that the "Mesh                                                  Principle
                                            MSDU size is 0-2304.
Control+MSDU" is 0-2304.




                                            Discuss if it is a reasonable way to
TGs draft D8.0 does not define any          go, once again. It is believed that AS
means to use AS (Authentication             utilization in mesh can be difficult     Disagree
Server) that provides the authorization     and complicated. However it seems
upon successful authentication.             that it can be done using multihop
                                            action frame framework.
"mesh peering: A logical relationship
between two mesh stations (STAs) that
has been established with the Mesh          Change the definition to read "A
Peering Management protocol." This          logical relationship between two
sentence is actually wrong. The mesh        mesh stations (STAs) that has been Agree
peering protocol can be other than          established with the active mesh
Mesh Peering Management protocol.           peering protocol.".
The mesh peering protocol is specified
by the Mesh Peering Protocol Identifier
in thesleep mode: A mesh element.
"light Mesh Configuration power mode Change the definition to read "A
in which the mesh station (STA)             mesh power mode in which the
operates in the Awake or Doze state,        mesh station (STA) operates either
                                                                                     Agree
and is expected to receive beacons          in the Awake state or in the Doze
from the peer mesh STA." should be          state, and is expected to receive
refined.                                    beacons from its peer mesh STA."
"deep sleep mode: A mesh power            Change the definition to read "A
mode in which the mesh station (STA)      mesh power mode in which the
operates in the Awake or Doze state,      mesh station (STA) operates either
                                                                                   Agree
and is not expected to receive beacons in the Awake state or in the Doze
from the peer mesh STA." should be        state, and is not expected to receive
refined.                                  beacons from its peer mesh STA."
"active mode: A link-specific mesh
power mode in which the mesh station Change the definition to read "A
(STA) operates in the Awake state."       mesh power mode in which the
                                                                                   Agree
This sentence is not aligned with other mesh station (STA) always operates
mesh power mode definition, such as       in the Awake state."
deep sleep mode or light sleep mode.
The line feed pitch is not aligned with
                                          correct the style.                       Agree
other lines.
                                          Change the paragraph to:


                                          "Bit 5 is the Additional Step
                                          Required for Access (ASRA) field. It
                                          is set to 1 by the AP to indicate that
                                          the
                                          network requires a further step for
                                          access. It is set to 0 whenever
                                          dot11RSNAEnabled is true. For
This paragraph can be simplified re-
                                          more
using some of the 802.11u emergency                                                Agree
                                          information, refer to Network
support terminology.
                                          Authentication Type Information in
                                          7.3.4.5. For a mesh STA the ASRA
                                          field
                                          is used as an emergency indicator,
                                          A mesh STA that receives a Mesh
                                          Peering Open frame that includes
                                          the
                                          Interworking element, with the
                                          ASRA field equal to 1, allows access
                                        Add the following sentence:
A simple statement could be made
                                        "In an MBSS, if location capability is
about MSTAs which do have location                                               Agree
                                        supported, the MSTA shall report its
capability.
                                        location for ES."




                                        Change the 1st 2 sentences of
                                        paragraph 4 as follows:

The first sentence of this paragraph
                                        In an infrastructure BSS and an
(Oops, from 11u I think) can be mis-
                                        MBSS, when an ES association is          Principle
interpreted as providing no access to
                                        used, the IEEE 802.11 infrastructure
users with an emergency call.
                                        and mesh network should be
                                        designed to restrict access to ES
                                        only (or alternatively prioritise the
                                        ES to the highest level of access.)
                                        Change the paragraph as follows:


                                        Depending on regulations, ES
                                        support may be mandated over the
                                        mesh network. In this case
                                        the Beacon and Probe Response
This paragraph can be simplified re-    frames should inform whether a
using some of the 802.11u emergency mesh STA supports ES, advertising Agree
support terminology.                to other mesh STAs that peering for
                                        ES is possible. If a mesh STA
                                        subsequently requires ES, an
                                        emergency indication is then set
                                        within the Mesh Peering Open
                                        frame. Mesh STAs that support ES,
                                        accept peering from other mesh
                                        STAs requiring ES, transferring
                                      Submissi Updated       Respons Accept_R #Mot Edit
Resolution Detail
                                      on          (to editor) eStatus   ejectDate ion   Status




                                      https://m
Reject. The protocol instance
                                      entor.iee
behiavior in the state machine
                                      e.org/80
(8.2a.8.6.2) specifically says what
                                      2.11/dcn/
to do with every possible payload
                                      11/11-11-
received in every possible state.
                                      0057-01-
Generally the offending frame is                             Closed     20110120 #40 I
                                      000s-
dropped, an error counter
                                      security-
incremented, possibly frames are
                                      comment
(re)sent, and possibly a
                                      s-1st-
retransmission timer is set. See
                                      recirc.do
8.2a.8.6.2
                                      cx
Counter. The note in 8.2a.6
                                        https://m
explains how one can statelessly
                                        entor.iee
bind a token to a MAC address.
                                        e.org/80
Being a statelessly bound token
                                        2.11/dcn/
there is no pairs to store for each
                                        11/11-11-
(Commit message, device). The
                                        0057-01-
Anti-clogging token is encode in a                  Closed   20110120 #40 I
                                        000s-
Commit Message per 8.2a.7.4,
                                        security-
just like it says in 8.2a.6. The text
                                        comment
around the state machine counter
                                        s-1st-
will be made more explicit in
                                        recirc.do
hopes of addressing this
                                        cx
comment.




                                        https://m
Reject. Defining a function to be
                                        entor.iee
the identity function always would
                                        e.org/80
be somewhat pointless. K is not
                                        2.11/dcn/
computed by operating on x-
                                        11/11-11-
coordinates only, but after K is
                                        0057-01-
computed (using scalar-op and                       Closed   20110120 #40 I
                                        000s-
element-op operations) its x-
                                        security-
coordinate is obtained to use in a
                                        comment
KDF (which cannot be passed a
                                        s-1st-
complex data structure like a
                                        recirc.do
point).
                                        cx
                                  https://me
                                  ntor.ieee.
                                  org/802.1
                                  1/dcn/11/
                                  11-11-
Resolved by documents 11-         0228-02-                          #61,
                                                Closed   20110210          I
11/0057r1 and 11-11/0228r2.       000s-                             #67a
                                  addition-
                                  security-
                                  comment-
                                  resolution.
                                  doc




                                  https://m
                                  entor.iee
                                  e.org/80
                                  2.11/dcn/
                                  11/11-11-
                                  0057-01-
Accept                                          Closed   20110120 #40 I
                                  000s-
                                  security-
                                  comment
                                  s-1st-
                                  recirc.do
                                  cx




                                  https://m
                                  entor.iee
                                  e.org/80
                                  2.11/dcn/
Counter. Say "shall be equal to    11/11-11-
one (1) modulo the prime." instead 0057-01-     Closed   20110120 #40 I
of "shall be equal to 1 (mod p)".  000s-
                                  security-
                                  comment
                                  s-1st-
                                  recirc.do
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
                                      11/11-11-
duplicate of 1005                     0057-01-    Closed   20110120 #40 I
                                      000s-
                                      security-
                                      comment
                                      s-1st-
                                      recirc.do
                                      https://m
                                      entor.iee
                                      e.org/80
counter, I think "r" should be        2.11/dcn/
bracketed by commas but will          11/11-11-
defer to the editor. The suggested 0057-01-       Closed   20110120 #40 I
addition of a comma between        000s-
"group" and "scalar" is accepted.     security-
                                      comment
                                      s-1st-
                                      recirc.do




                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
reject. Accepting this comment
                                      11/11-11-
would require notification of
                                      0057-01-
potentially essential patents being               Closed   20110120 #40 I
                                      000s-
required to implement the
                                      security-
standard.
                                      comment
                                      s-1st-
                                      recirc.do
                                      cx
                                    https://m
                                    entor.iee
Reject. As mentioned in the state   e.org/80
machine, there can only be 1        2.11/dcn/
active protocol instance in         11/11-11-
committed or confirmed. And         0057-01-
                                                Closed   20110120 #40 I
there can only be 1 protocol        000s-
instance in accepted. Receipt of    security-
"old" messages is handled by the comment
state machine.                      s-1st-
                                    recirc.do
                                    cx

                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
                                    0057-01-
Accept                                          Closed   20110120 #40 I
                                    000s-
                                    security-
                                    comment
                                    s-1st-
                                    recirc.do
                                    cx
                                  https://m
                                  entor.iee
                                  e.org/80
                                  2.11/dcn/
Counter. Make informative note in 11/11-11-
8.2a.4.1.1 normative specifying   0057-01-
                                              Closed   20110120 #40 I
odd prime curves with a co-factor 000s-
= 1.                              security-
                                  comment
                                  s-1st-
                                  recirc.do
                                  cx
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
Counter. Make informative note in 11/11-11-
8.2a.4.1.1 normative specifying     0057-01-
                                                  Closed   20110120 #40 I
odd prime curves with a co-factor 000s-
=1                                  security-
                                    comment
                                    s-1st-
                                    recirc.do
                                    cx




                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
Counter. Add note about               11/11-11-
probability of finding a point on the 0057-01-    Closed   20110120 #40 I
curve to text describing technique. 000s-
                                    security-
                                    comment
                                    s-1st-
                                    recirc.do
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
Accept                              0057-01-    Closed   20110120 #40 I
                                    000s-
                                    security-
                                    comment
                                    s-1st-
                                    recirc.do
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
Accept                              0057-01-    Closed   20110120 #40 I
                                    000s-
                                    security-
                                    comment
                                    s-1st-
                                    recirc.do



                                    https://m
                                    entor.iee
                                    e.org/80
Reject. This removes information    2.11/dcn/
about what this "binary operator"   11/11-11-
is, namely point addition. The      0057-01-
                                                Closed   20110120 #40 I
suggested remedy does not           000s-
define the notation in complains    security-
about.                              comment
                                    s-1st-
                                    recirc.do
                                    cx
         https://m
         entor.iee
         e.org/80
         2.11/dcn/
         11/11-11-
         0057-01-
accept               Closed   20110120 #40 I
         000s-
         security-
         comment
         s-1st-
         recirc.do
         cx




         https://m
         entor.iee
         e.org/80
         2.11/dcn/
         11/11-11-
accept   0057-01-    Closed   20110120 #40 I
         000s-
         security-
         comment
         s-1st-
         recirc.do
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
couter. Just say it's successive
                                       0057-01-
iterations. The recursive definition               Closed   20110120 #40 I
                                       000s-
is correct.
                                       security-
                                       comment
                                       s-1st-
                                       recirc.do
                                       cx




                                       https://m
                                       entor.iee
                                       e.org/80
reject. This does not seem to add 2.11/dcn/
anything to the draft and may     11/11-11-
become a target for future             0057-01-    Closed   20110120 #40 I
comments-- e.g. "'the groups are       000s-
indeed groups'? Well indeed!"          security-
                                       comment
                                       s-1st-
                                       recirc.do
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
accept                                 0057-01-    Closed   20110120 #40 I
                                       000s-
                                       security-
                                       comment
                                       s-1st-
                                       recirc.do
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
accept                              0057-01-     Closed   20110120 #40 I
                                    000s-
                                    security-
                                    comment
                                    s-1st-
                                    recirc.do

Reject. The IANA registry does      https://m
not define curves, it provides a 1:1 entor.iee
mapping between a curve             e.org/80
(defined somewhere else) and a      2.11/dcn/
unique number. We use the           11/11-11-
unique number here to identify the 0057-01-
                                                 Closed   20110120 #40 I
curve. This makes maintanence of 000s-
the amendment (and 802.11           security-
standard) much easier. RFC 5903 comment
or FIPS Pub 186-2 does not          s-1st-
provide such a convenient           recirc.do
mapping.                            cx
                                     https://m
                                     entor.iee
                                     e.org/80
Reject. It is too late to add new    2.11/dcn/
key exchange protocols to the        11/11-11-
draft. There is nothing in the draft 0057-01-
                                                 Closed   20110120 #40 I
that requires set-up of passwords 000s-
for each pair of devices that wish   security-
to communicate.                      comment
                                     s-1st-
                                     recirc.do
                                     cx




Change "modulo-4 294 967 296"
to "modulo 2^32". 32 is                          Closed   20110120 #47 I
superscript.


Change "modulo-4 294 967 296"
to "modulo 2^32". 32 is                          Closed   20110120 #47 I
superscript.

                                     https://m
                                     entor.iee
                                     e.org/80
                                     2.11/dcn/
Remove comma between
                                     11/11-11-
"resetting" and "its", as proposed               Closed   20110120 #41 I
                                     0179-01-
by commenter.
                                     000s-
                                     mcca-
                                     comment
                                     s-
change to "Probe Response"                  Closed   20110120 #47 I

                                            Closed   20110120 #47 I



Scan the name of states and
                                            Closed   20110120 #47 I
apend "state" if necessary.


                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
Reject. There aren't any yet.   0057-01-    Closed   20110120 #40 I
                                000s-
                                security-
                                comment
                                s-1st-
                                recirc.do
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
accept                          0057-01-    Closed   20110120 #40 I
                                000s-
                                security-
                                comment
                                s-1st-
                                recirc.do
                                            Closed   20110120 #47 I


Change "modulo-4 294 967 296"
to "modulo 2^32". 32 is                     Closed   20110120 #47 I
superscript.


                                            Closed   20110120 #47 I

                                            Closed   20110120 #47 I

                                            Closed   20110120 #47 I
                                      https://m
Replace "3) The reservation does
                                      entor.iee
not overlap with known HCCA
                                      e.org/80
times of neighbor APs." with "3)
                                      2.11/dcn/
The reservation does not overlap
                                      11/11-11-
with known HCCA times of                          Closed   20110120 #41 I
                                      0179-01-
neighbor APs. How the mesh STA
                                      000s-
obtains knowledge about HCCA
                                      mcca-
times of neighbor APs is beyond
                                      comment
the scope of this standard."
                                      s-
                                      https://m
Replace "4) The reservation does
                                      entor.iee
not overlap with known HCCA
                                      e.org/80
times of neighbor APs" with "4)
                                      2.11/dcn/
The reservation does not overlap
                                      11/11-11-
with known HCCA times of                          Closed   20110120 #41 I
                                      0179-01-
neighbor APs. How the mesh STA
                                      000s-
obtains knowledge about HCCA
                                      mcca-
times of neighbor APs is beyond
                                      comment
the scope of this standard. "
                                      s-
                                      https://m
                                      entor.iee
Add the following informative
                                      e.org/80
following line 52. "NOTE: By
                                      2.11/dcn/
modifying the offsets of the
                                      11/11-11-
reservations, the starting times of               Closed   20110120 #41 I
                                      0179-01-
its MCCAOPs do not change as a
                                      000s-
consequence of the TBTT
                                      mcca-
adjustment."
                                      comment
                                      s-
                                      https://m
                                      entor.iee
                                      e.org/80    Closed   20110120 #41 I
                                      2.11/dcn/
                                      11/11-11-
         https://m
         entor.iee
         e.org/80
         2.11/dcn/
         11/11-11-
accept   0057-01-      Closed   20110120 #40 I
         000s-
         security-
         comment
         s-1st-
         recirc.do
         https://m
         entor.iee
         e.org/80
         2.11/dcn/
         11/11-11-
         0188-00-
                       Closed   20110120 #50 I
         000s-rfi-
         proxy-
         comment-
         resolutio
         ns-
         spreadsh
         https://me
         ntor.ieee.
         org/802.1
         1/dcn/11/
         11-11-        Closed   20110210 #64 I
         0230-01-
         000s-rfi-
         comment-
         resolution-
         eindhove
         https://me
         ntor.ieee.
         org/802.1
         1/dcn/11/
         11-11-        Closed   20110210 #64 I
         0230-01-
         000s-rfi-
         comment-
         resolution-
         eindhove
                                https://me
                                ntor.ieee.
                                org/802.1
                                1/dcn/11/
                                11-11-        Closed   20110210 #64 I
                                0230-01-
                                000s-rfi-
                                comment-
                                resolution-
                                eindhove
                                https://me
                                ntor.ieee.
                                org/802.1
                                1/dcn/11/
                                11-11-        Closed   20110210 #64 I
                                0230-01-
                                000s-rfi-
                                comment-
                                resolution-
                                eindhove
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
Make this change in Figure 7-   11/11-11-
                                              Closed   20110120 #41 I
95o150                          0179-01-
                                000s-
                                mcca-
                                comment
                                s-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                              Closed   20110120 #41 I
                                0179-01-
                                000s-
                                mcca-
                                comment
                                s-
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
                                                 Closed   20110120 #41 I
                                    0179-01-
                                    000s-
                                    mcca-
                                    comment
                                    s-
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
accept                              0057-01-     Closed   20110120 #40 I
                                    000s-
                                    security-
                                    comment
                                    s-1st-
                                    recirc.do
                                    https://m
                                    entor.iee
                                    e.org/80
Although this is the case, it is
                                    2.11/dcn/
better to mark the Link Metric
                                    11/11-11-
Report element as not extensible.                Closed   20110120 #48 I
                                    0183-01-
This simplifies processing of the
                                    000s-
Link Metric Report element.
                                    mesh-
                                    link-
                                    reporting-
The proposed change is useful,    https://me
                                  ntor.ieee.
and the commenter is invited to
                                  org/802.1
provide some proposed text for    1/dcn/11/
review. However, we do not see it 11-11-         Closed   20110210 #64 I
                                  0230-01-
necessary right now, that the CRC
                                  000s-rfi-
provides a resolution.            comment-
No changes to existing text.      resolution-
                                  eindhove
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
Text is actually at page 82 lines 7-
                                       0188-00-
8. Apply proposed changes to                       Closed   20110120 #50 I
                                       000s-rfi-
these lines.
                                       proxy-
                                       comment-
                                       resolutio
                                       ns-
                                       spreadsh
Looking at 7.4.10.4 (PSMP frame
format) in the base standard                       Closed   20110120 #47 I
(REVmb D4.0), it should be better
to repeat the order here.


                                                   Closed   20110120 #47 I



Looking at 7.4.10.4 (PSMP frame
format) in the base standard                       Closed   20110120 #47 I
(REVmb D4.0), it should be better
to repeat the order here.
The proposed change is useful,    https://me
                                  ntor.ieee.
and the commenter is invited to
                                  org/802.1
provide some proposed text for    1/dcn/11/
review. However, we do not see it 11-11-           Closed   20110210 #64 I
                                  0230-01-
necessary right now, that the CRC
                                  000s-rfi-
provides a resolution.            comment-
No changes to existing text.      resolution-
                                  eindhove
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
                                       0188-00-
                                                   Closed   20110120 #50 I
                                       000s-rfi-
                                       proxy-
                                       comment-
                                       resolutio
                                       ns-
                                       spreadsh
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
Same issue with PXU element.          11/11-11-
                                                  Closed   20110120 #49 I
changes in doc 11-proxy               0189-00-
                                      000s-rfi-
                                      proxy-
                                      comment-
                                      resolutio

                                                  Closed   20110120 #47 I

                                                  Closed   20110120 #47 I

Change "bit 2 of the Flags
subfield" to "the Lifetime subfield               Closed   20110120 #47 I
in the Flags subfield".
                                                  Closed   20110120 #47 I

                                                  Closed   20110120 #47 I

Delete sentence "As the Proxy     https://me
                                  ntor.ieee.
Update frame is a Multihop Action
                                  org/802.1
frame, the PXU element can be     1/dcn/11/
propagated beyond the neighbor 11-11-             Closed   20110210 #64 I
                                  0230-01-
mesh STAs." (lines 24-25, page
                                  000s-rfi-
262, D8.0)                        comment-
Already done in D8.01 by doc 11- resolution-
                                  eindhove
11/188
                                                  Closed   20110120 #47 I



                                                  Closed   20110120 #47 I



                                                  Closed   20110120 #47 I


                                                  Closed   20110120 #47 I
                          https://m
                          entor.iee
                          e.org/80
                          2.11/dcn/
                          11/11-11-
changes in doc 11-proxy               Closed   20110120 #49 I
                          0189-00-
                          000s-rfi-
                          proxy-
                          comment-
                          resolutio
                          https://m
                          entor.iee
                          e.org/80
                          2.11/dcn/
                          11/11-11-
changes in doc 11-proxy               Closed   20110120 #49 I
                          0189-00-
                          000s-rfi-
                          proxy-
                          comment-
                          resolutio

                                      Closed   20110120 #47 I

                          https://m
                          entor.iee
                          e.org/80
                          2.11/dcn/
                          11/11-11-
                          0188-00-
                                      Closed   20110120 #50 R
                          000s-rfi-
                          proxy-
                          comment-
                          resolutio
                          ns-
                          spreadsh
                                      Closed   20110120 #47 I




                                      Closed   20110120 #47 IR
It is clear from the context. No
need to duplicate "proxy" here.                     Closed   20110120 #47 I
See resolution to CID1077 as
                                                    Closed   20110120 #47 I

The proposed change is useful,    https://me
                                  ntor.ieee.
and the commenter is invited to
                                  org/802.1
provide some proposed text for    1/dcn/11/
review. However, we do not see it 11-11-            Closed   20110210 #64 I
                                  0230-01-
necessary right now, that the CRC
                                  000s-rfi-
provides a resolution.            comment-
No changes to existing text.      resolution-
                                  eindhove
Change the paragraph to "If a
mesh STA adjusts its TBTT, e.g.,
in response to a TBTT Adjustment
Request, it shall adjust the
reservations
                                       https://m
by modifying the MCCAOP Offset
                                       entor.iee
of each of the tracked MCCAOP
                                       e.org/80
reservations. If a mesh
                                       2.11/dcn/
STA adjusts its timing offset value
                                       11/11-11-
with respect to a neighbor mesh
                                       0179-01-     Closed   20110120 #41 I
STA, as specified in 11C.12.2.2
                                       000s-
(Neighbor Offset Protocol), it shall
                                       mcca-
adjust the reservations by
                                       comment
modifying the MCCAOP Offset of
                                       s-
each of the tracked MCCAOP
                                       excell.xls
reservations for which this
neighbor mesh STA is the owner.
In either case, a mesh STA’s
MCCAOP Advertisements shall
always
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
000s, 11-11-0217-02-000s, and  oc
                               https://me        Closed   20110210 #62 I
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               https://m
                               1/dcn/11/
                                    entor.iee
wording:                            e.org/80
MBCA is a part of a                  2.11/dcn/
synchronization function. It should 11/11-11-
                                                 Closed   20110120 #44 I
be better to state "interaction with 0100-02-
time synchronization" in this       000s-m-
context.                            bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
                                                 Closed   20110120 #41 I
                                    0179-01-
                                    000s-
                                    mcca-
                                    comment
                                    s-
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
000s, 11-11-0217-02-000s, and  oc
                               https://me   Closed   20110210 #62 I
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
                               oc
000s, 11-11-0217-02-000s, and
                               https://me   Closed   20110210 #62 I
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
000s, 11-11-0217-02-000s, and  oc
                               https://me   Closed   20110210 #62 I
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
                               oc
000s, 11-11-0217-02-000s, and
                               https://me   Closed   20110210 #62 MR
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
000s, 11-11-0217-02-000s, and  oc
                               https://me          Closed   20110210 #62 MR
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                                      https://m
Replace paragraph with the            entor.iee
following "The Advertisement          e.org/80
Identifier subfield is a 3-bit        2.11/dcn/
unsigned integer. It identifies the   11/11-11-
MCCAOP Advertisements                 0179-01-     Closed   20110120 #41 I
element, except when the              000s-
Advertisement Identifier subfield     mcca-
equals 7 and the Last                 comment
Advertisement subfield equals 1." s-
                                      excell.xls
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
                               formats.d
                               oc
See submissions 11-11-0216-03-
                               https://me
000s, 11-11-0217-02-000s, and  ntor.ieee.
                                            Closed   20110210 #62 I
11-11-0231-01-000s for comment org/802.1
                               1/dcn/11/
resolution.
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0231-01-
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
000s, 11-11-0217-02-000s, and  oc
                               https://me   Closed   20110210 #62 MR
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
                               oc
000s, 11-11-0217-02-000s, and
                               https://me   Closed   20110210 #62 MR
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                            Closed   20110120 #41 I
                                0179-01-
                                000s-
                                mcca-
                                comment
                                s-
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
                               oc
000s, 11-11-0217-02-000s, and
                               https://me   Closed   20110210 #62 MR
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
000s, 11-11-0217-02-000s, and  oc
                               https://me   Closed   20110210 #62 MR
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
                               oc
000s, 11-11-0217-02-000s, and
                               https://me   Closed   20110210 #62 MR
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                            Closed   20110120 #41 I
                                0179-01-
                                000s-
                                mcca-
                                comment
                                s-
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
                               oc
000s, 11-11-0217-02-000s, and
                               https://me   Closed   20110210 #62 MR
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               https://m
                               1/dcn/11/
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                            Closed   20110120 #41 I
                                0179-01-
                                000s-
                                mcca-
                                comment
                                s-
                              https://m
                              entor.iee
                              e.org/80
change to "from neighboring   2.11/dcn/
mesh STAs with                11/11-11-
                                          Closed   20110120 #41 I
dot11MCCAActivated equal to   0179-01-
true"                         000s-
                              mcca-
                              comment
                              s-
                              https://m
                              entor.iee
                              e.org/80
                              2.11/dcn/
                              11/11-11-
                                          Closed   20110120 #41 I
                              0179-01-
                              000s-
                              mcca-
                              comment
                              s-
                              https://m
                              entor.iee
                              e.org/80
                              2.11/dcn/
                              11/11-11-
                                          Closed   20110120 #41 I
                              0179-01-
                              000s-
                              mcca-
                              comment
                              s-
Change note to "The DTIM
                                     https://m
has been chosen to ensure that       entor.iee
the starting times of the            e.org/80
reservations do not change           2.11/dcn/
relative to each other between       11/11-11-
consecutive DTIM intervals. The      0179-01-     Closed   20110120 #41 I
restriction that n be less than or   000s-
equal to 18 has been chosen to       mcca-
be compatible with the maximum       comment
DTIM interval and so that the        s-
range of the MCCAOP Offset in        excell.xls
the reservation, see 7.3.2.104.2
(MCCAOP Reservation field), is
                                     https://m
                                     entor.iee
                                     e.org/80
                                     2.11/dcn/
                                     11/11-11-
                                                  Closed   20110120 #41 I
                                     0179-01-
                                     000s-
                                     mcca-
                                     comment
                                     s-
                                     https://m
                                     entor.iee
                                     e.org/80
                                     2.11/dcn/
                                     11/11-11-
                                                  Closed   20110120 #41 I
                                     0179-01-
                                     000s-
                                     mcca-
                                     comment
                                     s-
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
000s, 11-11-0217-02-000s, and  oc
                               https://me   Closed   20110210 #62 I
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               https://m
                               1/dcn/11/
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                            Closed   20110120 #41 I
                                0179-01-
                                000s-
                                mcca-
                                comment
                                s-
                               https://me
                               ntor.ieee.
                               org/802.1
                               1/dcn/11/
                               11-11-
                               0216-03-
                               000s-
                               mccaop-
                               advertise
                               ments-
                               frame-
See submissions 11-11-0216-03- formats.d
000s, 11-11-0217-02-000s, and  oc
                               https://me      Closed   20110210 #62 I
11-11-0231-01-000s for comment ntor.ieee.
resolution.                    org/802.1
                               1/dcn/11/
                               11-11-
                               0217-02-
                               000s-
                               clause-9-
                               9a-3-8-
                               rewrite.do
                               cx
                               https://me
                               ntor.ieee.
                               org/802.1
                               https://m
                               1/dcn/11/
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
Change first sentence in Clause
                                   11/11-11-
10.3.77.7.1 to become as                       Closed   20110120 #41 I
                                   0179-01-
indicated in the proposed change
                                   000s-
                                   mcca-
                                   comment
                                   s-
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
                                               Closed   20110120 #41 I
                                   0179-01-
                                   000s-
                                   mcca-
                                   comment
                                   s-
See resolutions to CIDs 1056 and
1058. Furthermore, see table 8-
118 in Draft P802.11-                            Closed   20110210 #66 I
REVmb/D7.0. The latter contains
order numbers for repated
                                   https://me
                                   ntor.ieee.
                                   org/802.1
                                   1/dcn/11/
                                   11-11-        Closed   20110210 #64 I
                                   0230-01-
                                   000s-rfi-
                                   comment-
                                   resolution-
                                   eindhove
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
MLME:                                            Closed   20110120 #44 I
                                   0100-02-
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
wording:                                         Closed   20110120 #44 I
                                   0100-02-
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
wording:                                         Closed   20110120 #44 I
                                   0100-02-
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
wording:                                    Closed   20110120 #44 I
                                0100-02-
                                000s-m-
                                bs-
                                comment-
                                resolutio
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
MLME:                                       Closed   20110120 #44 I
                                0100-02-
                                000s-m-
                                bs-
                                comment-
                                resolutio
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
wording:                                    Closed   20110120 #44 I
                                0100-02-
                                000s-m-
                                bs-
                                comment-
                                resolutio
                                https://m
                                entor.iee
wording:                        e.org/80
Looking at 10.3.6.4.2 and       2.11/dcn/
10.3.4.4.2 of the REVmb D4.0,   11/11-11-
                                            Closed   20110120 #44 I
"result response" seems to be an 0100-02-
appropriate description in this  000s-m-
context.                        bs-
                                comment-
                                resolutio
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
wording:                                     Closed   20110120 #44 I
                                0100-02-
                                000s-m-
                                bs-
                                comment-
                                resolutio
wording:
Change "The mesh STA received https://m
this primitive subsequently   entor.iee
processes the TBTT adjustment   e.org/80
described in 11C.12.4.4.3       2.11/dcn/
(Adjustment procedure), and     11/11-11-
responds with MLME-          0100-02-
MeshTBTTAdjustmen.response." 000s-m-         Closed   20110120 #44 I
to                           bs-
"The mesh STA received this      comment-
primitive subsequently processes resolutio
the TBTT adjustment procedure    n-
described in 11C.12.4.4.3       text.doc
(Adjustment procedure), and
responds with the MLME-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
wording:                                     Closed   20110120 #44 I
                                0100-02-
                                000s-m-
                                bs-
                                comment-
                                resolutio
           https://m
           entor.iee
           e.org/80
           2.11/dcn/
           11/11-11-
wording:               Closed   20110120 #44 I
           0100-02-
           000s-m-
           bs-
           comment-
           resolutio
           https://m
           entor.iee
           e.org/80
           2.11/dcn/
           11/11-11-
wording:               Closed   20110120 #44 I
           0100-02-
           000s-m-
           bs-
           comment-
           resolutio
           https://m
           entor.iee
           e.org/80
           2.11/dcn/
           11/11-11-
wording:               Closed   20110120 #44 I
           0100-02-
           000s-m-
           bs-
           comment-
           resolutio
           https://m
           entor.iee
           e.org/80
           2.11/dcn/
           11/11-11-
wording:               Closed   20110120 #44 I
           0100-02-
           000s-m-
           bs-
           comment-
           resolutio
           https://m
           entor.iee
           e.org/80
           2.11/dcn/
           11/11-11-
wording:               Closed   20110120 #44 I
           0100-02-
           000s-m-
           bs-
           comment-
           resolutio
           https://m
           entor.iee
           e.org/80
           2.11/dcn/
           11/11-11-
wording:               Closed   20110120 #44 I
           0100-02-
           000s-m-
           bs-
           comment-
           resolutio
           https://m
           entor.iee
           e.org/80
           2.11/dcn/
           11/11-11-
wording:               Closed   20110120 #44 I
           0100-02-
           000s-m-
           bs-
           comment-
           resolutio
           https://m
           entor.iee
           e.org/80
           2.11/dcn/
           11/11-11-
wording:               Closed   20110120 #44 I
           0100-02-
           000s-m-
           bs-
           comment-
           resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
wording:                            2.11/dcn/
However, change "of peer entity's 11/11-11-
                                                Closed   20110120 #44 I
TBTT" into "of the peer entity's  0100-02-
TBTT"                               000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
wording:                            11/11-11-
                                                Closed   20110120 #44 I
change "to be sent" to "be sent".   0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                        Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
wording:                            https://m
Change                              entor.iee
"This primitive requests that a     e.org/80
TBTT Adjustment Request frame       2.11/dcn/
be sent to the specified peer mesh 11/11-11-
                                                Closed   20110120 #44 I
STA."                               0100-02-
to                                  000s-m-
"This primitive requests            bs-
transmission of a TBTT              comment-
Adjustment Request frame."          resolutio
                                     https://m
wording:
                                     entor.iee
change
                                     e.org/80
"a mesh STA requests TBTT
                                     2.11/dcn/
adjustment to its neighboring peer
                                     11/11-11-
mesh STA."                                       Closed   20110120 #44 I
                                     0100-02-
to
                                     000s-m-
"a mesh STA requests its
                                     bs-
neighbor peer mesh STA of TBTT
                                     comment-
adjustment."
                                     resolutio
                                     https://m
                                     entor.iee
                                     e.org/80
                                     2.11/dcn/
BT element extension:
                                     11/11-11-
It is not required to make the                   Closed   20110120 #44 I
                                     0100-02-
Beacon Timing element etensible.
                                     000s-m-
                                     bs-
                                     comment-
                                     resolutio
                                     https://m
                                     entor.iee
                                     e.org/80
omission:
                                     2.11/dcn/
Add the following sentence to the
                                     11/11-11-
end of the paragraph:                            Closed   20110120 #44 I
                                     0100-02-
"The unit of the Neighbor Beacon
                                     000s-m-
Interval subfield is TU."
                                     bs-
                                     comment-
                                     resolutio
wording:                             https://m
Change                               entor.iee
"are contained in this field, in     e.org/80
order to represent the time in units 2.11/dcn/
of 256 us."                          11/11-11-
                                                 Closed   20110120 #44 I
into                                 0100-02-
"are contained in this subfield      000s-m-
representing the TBTT in units of    bs-
256 us." (with the correct           comment-
character for micro)                 resolutio
                                     https://m
                                     entor.iee
                                     e.org/80
                                     2.11/dcn/
wording: the cited text will be      11/11-11-
                                                 Closed   20110120 #44 I
removed per CID1141.                 0100-02-
                                     000s-m-
                                     bs-
                                     comment-
                                     resolutio
wording:
1. Replace
"The TBTT is calculated from the
latest reception time of the
Beacon frame and values in the
Timestamp field and the Beacon      https://m
interval field of the Beacon frame, entor.iee
as described in 11C.12.4.2.2        e.org/80
(Calculation of neighbor STA’s       2.11/dcn/
TBTT)."                              11/11-11-
with                             0100-02-
"When the active synchronization 000s-m-         Closed   20110120 #44 I
protocol is the Neighbor Offset  bs-
Protocol, the TBTT is calculated     comment-
as described in 11C.12.4.2.2         resolutio
(Calculation of neighbor STA’s       n-
TBTT)."                              text.doc
2. In 11C.12.4.2.2 (Calculation of
neighbor STA’s TBTT), line 26
page 269, replace
"The mesh STA shall keep the
abbreviated TBTT together with
the ..."
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
wording:                                    Closed   20110120 #44 I
                                0100-02-
                                000s-m-
                                bs-
                                comment-
                                resolutio
                                https://m
                                entor.iee
                                e.org/80
BT element naming:              2.11/dcn/
rename "Neighbor Last Beacon    11/11-11-
                                            Closed   20110120 #44 I
Time" subfield into "Neighbor   0100-02-
TBTT" subfield throughout.      000s-m-
                                bs-
                                comment-
                                resolutio
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
wording:                                    Closed   20110120 #44 I
                                0100-02-
                                000s-m-
                                bs-
                                comment-
                                resolutio
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
wording:                                    Closed   20110120 #44 I
                                0100-02-
                                000s-m-
                                bs-
                                comment-
                                resolutio
                                 https://m
                                 entor.iee
                                 e.org/80
                                 2.11/dcn/
                                 11/11-11-
wording:                                     Closed   20110120 #44 I
                                 0100-02-
                                 000s-m-
                                 bs-
                                 comment-
                                 resolutio
                                 https://m
                                 entor.iee
                                 e.org/80
                                 2.11/dcn/
                                 11/11-11-
wording:                                     Closed   20110120 #44 I
                                 0100-02-
                                 000s-m-
                                 bs-
                                 comment-
                                 resolutio
                                 https://m
                                 entor.iee
                                 e.org/80
BT element naming:               2.11/dcn/
rename "More Report" subfield    11/11-11-
                                             Closed   20110120 #44 I
into "More Beacon Timing         0100-02-
Elements" subfield throughout.   000s-m-
                                 bs-
                                 comment-
                                 resolutio
                                 https://m
                                 entor.iee
                                 e.org/80
                                 2.11/dcn/
                                 11/11-11-
wording:                                     Closed   20110120 #44 I
                                 0100-02-
                                 000s-m-
                                 bs-
                                 comment-
                                 resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
BT element naming:                    2.11/dcn/
rename "Report Number" subfield 11/11-11-
                                                  Closed   20110120 #44 I
into "Beacon Timing Element     0100-02-
Number" subfield throughout.          000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
Status Number definition:             2.11/dcn/
Changed the status number to be 11/11-11-
                                                  Closed   20110120 #44 I
given by a modulo-16 counter.   0100-02-
See submission 11-11-100.             000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
                                      11/11-11-
BT element naming:                                Closed   20110120 #44 I
                                      0100-02-
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
wording:
                                      e.org/80
Change
                                      2.11/dcn/
"to signal the status of the beacon
                                      11/11-11-
timing information tuple"                         Closed   20110120 #44 I
                                      0100-02-
into
                                      000s-m-
"to signal information about the
                                      bs-
beacon timing information tuple"
                                      comment-
                                      resolutio
                                        https://m
                                        entor.iee
                                        e.org/80
                                        2.11/dcn/
                                        11/11-11-
wording:                                            Closed   20110120 #44 I
                                        0100-02-
                                        000s-m-
                                        bs-
                                        comment-
                                        resolutio
wording:
When a part of the entire beacon
timing information set is lost at the
receiver, it may transmit a probe
request frame to retrieve the
information. The guideline is           https://m
described as "When a mesh STA entor.iee
receives a Beacon frame       e.org/80
containing Beacon Timing                2.11/dcn/
element that indicates only a           11/11-11-
subset                                  0100-02-
                                                    Closed   20110120 #44 I
of the beacon timing information        000s-m-
set is contained, the mesh STA          bs-
may transmit a Probe Request            comment-
frame                                   resolutio
containing a Beacon Timing              n-
element ID in its Request               text.doc
Information element to the
transmitter of the Beacon
Timing element, in order to
request the rest of the beacon
timing information."
BT element procedure:                   https://m
The combination of the tuples are entor.iee
updated when there is a change in e.org/80
the beacon timing information           2.11/dcn/
(when status number is updated). 11/11-11-
                                                    Closed   20110120 #44 I
Add "The mesh STA may update            0100-02-
the combination of the tuples only 000s-m-
when the status number described bs-
in 11C.12.4.2.1 is updated." at the comment-
beginning of the paragaraph.            resolutio
wording:
It does provide specification. "The
mesh STA shall set the 4 LSBs of https://m
the status number to the Report  entor.iee
Status subfield in the Report         e.org/80
Control                               2.11/dcn/
field in the Beacon Timing            11/11-11-
element."                            0100-02-
                                                  Closed   20110120 #44 I
"The Report Status subfield in the 000s-m-
Report Control field facilitates the bs-
detection of the changes in the       comment-
beacon timing information set by   resolutio
the receiving mesh STA." this text n-
is provided to explain what this   text.doc
information is for, to make it
reader friendly. Operation of the
receiver is described in
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
wording:
                                      11/11-11-
The sentence is refined. See                      Closed   20110120 #44 I
                                      0100-02-
submission 11-11-100.
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
wording:
                                      11/11-11-
The sentence is refined. See                      Closed   20110120 #44 I
                                      0100-02-
submission 11-11-100.
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                          https://m
                          entor.iee
                          e.org/80
                          2.11/dcn/
                          11/11-11-
wording:                              Closed   20110120 #44 I
                          0100-02-
                          000s-m-
                          bs-
                          comment-
                          resolutio
                          https://m
                          entor.iee
                          e.org/80
                          2.11/dcn/
                          11/11-11-
wording:                              Closed   20110120 #44 I
                          0100-02-
                          000s-m-
                          bs-
                          comment-
                          resolutio
                          https://m
                          entor.iee
                          e.org/80
                          2.11/dcn/
                          11/11-11-
wording:                              Closed   20110120 #44 I
                          0100-02-
                          000s-m-
                          bs-
                          comment-
                          resolutio
                          https://m
                          entor.iee
                          e.org/80
                          2.11/dcn/
wording:                  11/11-11-
                                      Closed   20110120 #44 I
Replace "at" with "in".   0100-02-
                          000s-m-
                          bs-
                          comment-
                          resolutio
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
wording:
                                       11/11-11-
it is clear from the description "so               Closed   20110120 #44 I
                                       0100-02-
that all tuples are informed".
                                       000s-m-
                                       bs-
                                       comment-
                                       resolutio
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
wording:                                           Closed   20110120 #44 I
                                       0100-02-
                                       000s-m-
                                       bs-
                                       comment-
                                       resolutio
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
wording:                                           Closed   20110120 #44 I
                                       0100-02-
                                       000s-m-
                                       bs-
                                       comment-
                                       resolutio
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
wording:                                           Closed   20110120 #44 I
                                       0100-02-
                                       000s-m-
                                       bs-
                                       comment-
                                       resolutio
wording:                              https://m
As described, "newly updated" is      entor.iee
"(i.e., the beacon timing             e.org/80
information that causes an update 2.11/dcn/
of the status number as described 11/11-11-
in 11C.12.4.2.1 (Maintenance of       0100-02-    Closed   20110120 #44 I
the                                   000s-m-
status number))".                     bs-
It is a bit vague, but "updated" is   comment-
misleading in this context because resolutio
beacon timing information is          n-
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
                                      11/11-11-
wording:                                          Closed   20110120 #44 I
                                      0100-02-
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
wording:                          2.11/dcn/
The matching conditions are clear 11/11-11-
                                                  Closed   20110120 #44 I
from the description. No need to 0100-02-
change the text.                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
                                      11/11-11-
wording:                                          Closed   20110120 #44 I
                                      0100-02-
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                       https://m
                                       entor.iee
                                       e.org/80
wording:                               2.11/dcn/
change to "the Beacon Timing           11/11-11-
                                                   Closed   20110120 #44 I
elements received from its             0100-02-
neighbor mesh STAs"                    000s-m-
                                       bs-
                                       comment-
                                       resolutio
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
wording:                                           Closed   20110120 #44 I
                                       0100-02-
                                       000s-m-
                                       bs-
                                       comment-
                                       resolutio
                                       https://m
                                       entor.iee
                                       e.org/80
wording:
                                       2.11/dcn/
If the MSB is 1, the mesh STA
                                       11/11-11-
does not count them as essential                   Closed   20110120 #44 I
                                       0100-02-
beacon reception timing. It is clear
                                       000s-m-
from the context.
                                       bs-
                                       comment-
                                       resolutio
                                       https://m
wording:                               entor.iee
Information obtained from the          e.org/80
Beacon Timing element is not the 2.11/dcn/
neighbor STA's TBTT. It is       11/11-11-
                                                   Closed   20110120 #44 I
actually beacon reception timing       0100-02-
at the neighbor STA. The beacon 000s-m-
might be transmitted from       bs-
neighbor or 2 hop neighbors.           comment-
                                       resolutio
wording:
Cited paragraph is replaced with     https://m
the following text. "A mesh STA      entor.iee
that receives the Beacon Timing   e.org/80
element shall record the reported 2.11/dcn/
TBTT and its successive TBTTs 11/11-11-
as neighbor’s essential beacon     0100-02-
reception timing if the MSB of the 000s-m-       Closed   20110120 #44 I
Neighbor STA ID field in the       bs-
corresponding Beacon Timing          comment-
Information field is 0. The         resolutio
essential beacon reception timing n-
is used to control the transmission text.doc
of frames as described in
11C.12.4.5 (Frame transmission
BT element procedure:
                                     https://m
NOTE is changed as follows:
                                     entor.iee
"NOTE1—The Report Control field
                                     e.org/80
in the Beacon Timing element
                                     2.11/dcn/
facilitates the detection of the
                                     11/11-11-
missing beacon timing
                                     0100-02-
information.                                     Closed   20110120 #44 I
                                     000s-m-
NOTE2—Once entire beacon
                                     bs-
timing information set is obtained
                                     comment-
with a particular Status Number,
                                     resolutio
the mesh STA do not need to
                                     n-
retrieve beacon timing information
                                     text.doc
as long as the Status Number
                                     https://m
                                     entor.iee
                                     e.org/80
wording:                             2.11/dcn/
The original text is more direct     11/11-11-
                                                 Closed   20110120 #44 I
and accurate than the proposed       0100-02-
text.                                000s-m-
                                     bs-
                                     comment-
                                     resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
wording: (beacon timing
                                    2.11/dcn/
inforamtion)
                                    11/11-11-
The cieted text is removed in the                 Closed   20110120 #44 I
                                    0100-02-
proposed text. See submission 1-
                                    000s-m-
11-100.
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
wording: (beacon timing
                                    entor.iee
inforamtion)
                                    e.org/80
A new subclause "Beacon timing
                                    2.11/dcn/
information" is created. The new
                                    11/11-11-
clause defines the beacon timing                  Closed   20110120 #44 I
                                    0100-02-
information, the beacon timing
                                    000s-m-
information set, and a tuple of
                                    bs-
beacon information set. See
                                    comment-
submission 11-11-100.
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
wording:                            2.11/dcn/
Cited text fit with the contex of the 11/11-11-
                                                  Closed   20110120 #44 I
entire description. No need to        0100-02-
change the text.                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
wording:                            entor.iee
Information obtained from the       e.org/80
Beacon Timing element is not the 2.11/dcn/
neighbor STA's TBTT. It is       11/11-11-
                                                  Closed   20110120 #44 I
actually beacon reception timing    0100-02-
at the neighbor STA. The beacon 000s-m-
might be transmitted from       bs-
neighbor or 2 hop neighbors.        comment-
                                    resolutio
                                       https://m
                                       entor.iee
wording:
                                       e.org/80
This operation actually relates to
                                       2.11/dcn/
both MCCA and MBCA. Same
                                       11/11-11-
kind of description is present in                  Closed   20110120 #44 I
                                       0100-02-
MCCA subclause. It is more
                                       000s-m-
reader friendly to leave the text in
                                       bs-
MBCA clause as well.
                                       comment-
                                       resolutio
wording:
Change                                 https://m
"The mesh STA shall also collect       entor.iee
the beacon timing information          e.org/80
contained in the Beacon Timing    2.11/dcn/
element from its neighbor STAs to 11/11-11-
find out the TBTT and beacon      0100-02-
interval of STAs in 2 hop range."                  Closed   20110120 #44 I
                                       000s-m-
into                                   bs-
"The mesh STA shall also collect       comment-
the beacon timing information          resolutio
contained in the Beacon Timing         n-
elements received from its             text.doc
neighbor mesh STAs in order to
obtain the TBTT and beacon
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
wording:
                                       11/11-11-
It is clear from the context. No                   Closed   20110120 #44 I
                                       0100-02-
need to specify "mesh STA" here.
                                       000s-m-
                                       bs-
                                       comment-
                                       resolutio
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
wording:
                                   11/11-11-
MBCA is also applicable to non                 Closed   20110120 #44 I
                                   0100-02-
mesh beacons.
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
wording:                                       Closed   20110120 #44 I
                                   0100-02-
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                   https://m
                                   entor.iee
                                   e.org/80
wording:
                                   2.11/dcn/
The proposed text "using the
                                   11/11-11-
information obtained from Beacon               Closed   20110120 #44 I
                                   0100-02-
frames" is vague and duplicates
                                   000s-m-
with the Beacon Timing element.
                                   bs-
                                   comment-
                                   resolutio
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
wording:                                       Closed   20110120 #44 I
                                   0100-02-
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
status code:
                                      11/11-11-
It is clearly described in page 271               Closed   20110120 #44 I
                                      0100-02-
line 60-65.
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
wording:
                                      11/11-11-
50 beacon timing information is a
                                      0100-02-    Closed   20110120 #44 I
fixed value. As the Beacon Timing
                                      000s-m-
element is not extensible.
                                      bs-
                                      comment-
                                      resolutio
                                      n-


Looking at 7.4.10.4 (PSMP frame
format) in the base standard
                                                  Closed   20110120 #47 I
(REVmb D4.0), it should be better
to repeat the order here.


                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
wording:
                                      11/11-11-
it should be reader friendly to                   Closed   20110120 #44 I
                                      0100-02-
state what it means here.
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                        Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
wording:
                                    11/11-11-
50 beacon timing information is a
                                    0100-02-    Closed   20110120 #44 I
fixed value. As the Beacon Timing
                                    000s-m-
element is not extensible.
                                    bs-
                                    comment-
                                    resolutio
                                    n-


Looking at 7.4.10.4 (PSMP frame
format) in the base standard
                                                Closed   20110120 #47 I
(REVmb D4.0), it should be better
to repeat the order here.


                                    https://m
                                    entor.iee
TBTT adjustment: (scannning and e.org/80
adjustment)                     2.11/dcn/
The clause describing TBTT          11/11-11-
                                                Closed   20110120 #44 I
adjustment has been updated per 0100-02-
comment. See submission 11-11- 000s-m-
100                                 bs-
                                    comment-
                                    resolutio
wording:
Change                               https://m
"The TBTT Adjustment Request         entor.iee
frame may be transmitted only if     e.org/80
the recipient of the frame is a peer 2.11/dcn/
mesh STA and the recipient of the 11/11-11-
frame sets MBCA Enabled              0100-02-
subfield in the Mesh Capability                   Closed   20110120 #44 I
                                     000s-m-
field of the Mesh Configuration      bs-
element to 1."                       comment-
into                                 resolutio
"The TBTT Adjustment Request         n-
frame may be transmitted if the      text.doc
recipient is a peer mesh STA and
has set the MBCA Enabled
                                     https://m
wording:                             entor.iee
change                               e.org/80
", in order to request that the      2.11/dcn/
neighbor mesh STA adjusts its        11/11-11-
                                                  Closed   20110120 #44 I
TBTT"                                0100-02-
into                                 000s-m-
"in order to request this neighbor   bs-
mesh STA to adjust its TBTT"         comment-
                                     resolutio
                                     https://me
                                     ntor.ieee.
                                     org/802.1
Submission 802.11-11/0220r2
                                     1/dcn/11/
provides resolutions to this         11-11-       Closed   20110210 #60 I
comment.                             0220-02-
                                     000s-m-
                                     bs-
                                     comment-
                                     https://me
                                     ntor.ieee.
                                     org/802.1
Submission 802.11-11/0220r2
                                     1/dcn/11/
provides resolutions to this         11-11-       Closed   20110210 #60 I
comment.                             0220-02-
                                     000s-m-
                                     bs-
                                     comment-
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                         Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                         Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://me
                                    ntor.ieee.
                                    org/802.1
Submission 802.11-11/0220r2
                                    1/dcn/11/
provides resolutions to this        11-11-       Closed   20110210 #60 I
comment.                            0220-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    https://m
wording:                            entor.iee
Replace                             e.org/80
"its TBTT appears later than that   2.11/dcn/
of colliding STA,"                  11/11-11-
                                                 Closed   20110120 #44 I
with                                0100-02-
"its TBTT appears later than that   000s-m-
of colliding STA at the time of     bs-
collision,"                         comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                          Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                          Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://me
                                    ntor.ieee.
                                    org/802.1
Submission 802.11-11/0220r2         1/dcn/11/
provides resolutions to this        11-11-        Closed   20110210 #60 I
                                    0220-02-
comment.                            000s-m-
                                    bs-
                                    comment-
                                    resolution-
                                    https://m
TBTT adjustment:
                                    entor.iee
The sentence is changed to read
                                    e.org/80
"When dot11MBCAActivated is
                                    2.11/dcn/
true, the mesh STA shall check if
                                    11/11-11-
it does not transmit Beacon                       Closed   20110120 #44 I
                                    0100-02-
frames during the beacon
                                    000s-m-
transmissions of other STAs
                                    bs-
withing its 2 hop rage by parsing
                                    comment-
the Beacon Timing element."
                                    resolutio
                                     https://m
TBTT adjustment:
                                     entor.iee
The sentence is changed to read
                                     e.org/80
"When dot11MBCAActivated is
                                     2.11/dcn/
true, the mesh STA shall check if
                                     11/11-11-
it does not transmit Beacon                      Closed   20110120 #44 I
                                     0100-02-
frames during the beacon
                                     000s-m-
transmissions of other STAs
                                     bs-
withing its 2 hop rage by parsing
                                     comment-
the Beacon Timing element."
                                     resolutio
                                     https://m
                                     entor.iee
                                     e.org/80
                                     2.11/dcn/
                                     11/11-11-
wording:                                         Closed   20110120 #44 I
                                     0100-02-
                                     000s-m-
                                     bs-
                                     comment-
                                     resolutio
wording:                             https://m
Proactive/Reactive adjustment are entor.iee
different. Proative adjustment is    e.org/80
triggered by its own observation,    2.11/dcn/
whereas reactive adjustment is       11/11-11-
                                                 Closed   20110120 #44 I
triggered by a TBTT adjustment       0100-02-
request from its peer. In order to   000s-m-
provide that there are 2 cases to    bs-
operate TBTT adjustment, it          comment-
should be better to have 2 distinct resolutio
Report Status subfield:
Although the Report Status
subfield is updated per the update
of the beacon timing information
as well as the completion of the
TBTT adjustment, it is still helpful   https://m
for mesh STAs in deep sleep            entor.iee
mode that do not listen to             e.org/80
neighbor peer mesh STA's               2.11/dcn/
beacons. It is true that the           11/11-11-
neighbor mesh STA may                  0100-02-
misinterpret the update of the                     Closed   20110120 #44 I
                                       000s-m-
Report Status field. However, it       bs-
only occurs when the neighbor          comment-
peer mesh STA observes large           resolutio
TSF jitter. Also, the effect of the    n-
misinterpretation is limited and       text.doc
only affect to the safe side. If it
happens, the neighbor peer mesh
STA do not operate the clock drift
compensation and (usually) try to
listen to the next beacon to see if
the clock drift is large. The
                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
                                       11/11-11-
wording:                                           Closed   20110120 #44 I
                                       0100-02-
                                       000s-m-
                                       bs-
                                       comment-
                                       resolutio
                                   https://m
                                   entor.iee
                                   e.org/80
TBTT adjustment:
                                   2.11/dcn/
Change "Since the TBTT is
                                   11/11-11-
adjusted in slower direction" to               Closed   20110120 #44 I
                                   0100-02-
"Since the TBTT is adjusted by
                                   000s-m-
slowing its TSF".
                                   bs-
                                   comment-
                                   resolutio



                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
                                   0100-02-
wording:                                       Closed   20110120 #44 I
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                   n-
                                   text.doc



                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
wording:                                       Closed   20110120 #44 I
                                   0100-02-
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                        Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
wording:
                                    https://m
Replace
                                    entor.iee
"The mesh STA shall adjust the
                                    e.org/80
MCCAOP reservations
                                    2.11/dcn/
accordingly by modifying the
                                    11/11-11-
MCCAOP Offset of each
                                    0100-02-
MCCAOP reservation, when                        Closed   20110120 #44 I
                                    000s-m-
dot11MCCAActivated is true."
                                    bs-
with
                                    comment-
"When dot11MCCAActivated is
                                    resolutio
true, the mesh STA shall adjust
                                    n-
the MCCAOP reservations
                                    text.doc
accordingly by modifying the
                                    https://m
                                    entor.iee
wording:
                                    e.org/80
Replace
                                    2.11/dcn/
"that are contained in the Beacon
                                    11/11-11-
Timing element,"                                Closed   20110120 #44 I
                                    0100-02-
with
                                    000s-m-
"that are to be contained in the
                                    bs-
Beacon Timing element,"
                                    comment-
                                    resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
wording:
                                      11/11-11-
This refrence is helpful to specify                 Closed   20110120 #44 I
                                      0100-02-
what the TBTT information is.
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
wording:
                                      e.org/80
replace
                                      2.11/dcn/
"the neighbor STA’s TBTT
                                      11/11-11-
information"                                        Closed   20110120 #44 I
                                      0100-02-
with
                                      000s-m-
"TBTT information of the neighbor
                                      bs-
STAs"
                                      comment-
                                      resolutio
The commenter provides better
language for the sentence,            https://me
change the sentence starting on       ntor.ieee.
                                      org/802.1
line 1 of the page 276 to read:
                                      1/dcn/11/
"When a mesh STA expects to           11-11-
receive a group addressed frame       0128-01-      Closed   20110120 #43 I
                                      000s-m-
and CCA is IDLE for the duration
                                      pm-
of the PHY specific Group             comment-
Delivery Idle Time, the receiving     resolution-
                                      text.doc
mesh STA may assume that no
more frames destined to group
                                      https://me
                                      ntor.ieee.
                                      org/802.1
                                      1/dcn/11/
                                      11-11-        Closed   20110120 #43 I
                                      0128-01-
                                      000s-m-
                                      pm-
                                      comment-
                                 https://m
                                 entor.iee
TBTT adjustment: (scannning and e.org/80
adjustment)                     2.11/dcn/
The clause describing TBTT       11/11-11-
                                             Closed   20110120 #44 I
adjustment has been updated per 0100-02-
comment. See submission 11-11- 000s-m-
100                              bs-
                                 comment-
                                 resolutio
                                 https://m
                                 entor.iee
TBTT adjustment: (scannning and e.org/80
adjustment)                     2.11/dcn/
The clause describing TBTT      11/11-11-
                                             Closed   20110120 #44 I
adjustment has been updated per 0100-02-
comment. See submission 11-11- 000s-m-
100                              bs-
                                 comment-
                                 resolutio
wording:                         https://m
Change "11C.12.4.4.1 Proactive   entor.iee
adjustment" to "11C.12.4.4.1     e.org/80
Proactive TBTT adjustment"       2.11/dcn/
Change "11C.12.4.4.2 Reactive    11/11-11-
                                             Closed   20110120 #44 I
adjustment" to "11C.12.4.4.2     0100-02-
Reactive TBTT adjustment"        000s-m-
Change "11C.12.4.4.3 Adjustment bs-
procedure" to "11C.12.4.4.3 TBTT comment-
adjustment procedure"            resolutio
                                 https://m
                                 entor.iee
TBTT adjustment: (scannning and e.org/80
adjustment)                     2.11/dcn/
The clause describing TBTT       11/11-11-
                                             Closed   20110120 #44 I
adjustment has been updated per 0100-02-
comment. See submission 11-11- 000s-m-
100                              bs-
                                 comment-
                                 resolutio
                                     https://m
wording:
                                     entor.iee
Replace
                                     e.org/80
", in order to announce that it is
                                     2.11/dcn/
adjusting its TBTT to avoid
                                     11/11-11-
beacon collision."                               Closed   20110120 #44 I
                                     0100-02-
with
                                     000s-m-
"in order to announce that the
                                     bs-
TBTT adjustment procedure is
                                     comment-
ongoing."
                                     resolutio
                                     https://m
                                     entor.iee
TBTT adjustment: (scannning and e.org/80
adjustment)                     2.11/dcn/
The clause describing TBTT      11/11-11-
                                                 Closed   20110120 #44 I
adjustment has been updated per 0100-02-
comment. See submission 11-11- 000s-m-
100                                  bs-
                                     comment-
                                     resolutio
wording:
Change
"When dot11MBCAActivated is
true, the mesh STA should not
extend its transmissions, other
than Beacon                        https://m
frames, across its neighbors’      entor.iee
beacon reception timing that are   e.org/80
recognized as neighbor’s           2.11/dcn/
essential beacon                   11/11-11-
reception timing (see 11C.12.4.2.4 0100-02-
(Receiver’s procedure)), in order 000s-m-      Closed   20110120 #44 I
to assist the proper Beacon frame bs-
reception at its neighbor mesh    comment-
STAs. This operation helps in      resolutio
reducing the hidden STA            n-
interference with                  text.doc
beacon reception at its neighbor
mesh STA. When both
dot11MBCAActivated and
dot11MCCAActivated
are true, the mesh STA shall not
extend its transmissions, other
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
BT element procedure:              11/11-11-
                                               Closed   20110120 #44 I
see resolution to CID1231          0100-02-
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
                                   https://m
wording:
                                   entor.iee
Beacon frames can be sent
                                   e.org/80
across reported TBTTs. This is
                                   2.11/dcn/
because the valid beacon frames
                                   11/11-11-
are also reported in the Beacon                Closed   20110120 #44 I
                                   0100-02-
Timing element. If beacon
                                   000s-m-
collision is found, the TBTT is
                                   bs-
adjusted as described in
                                   comment-
11C.12.4.4 TBTT adjustment.
                                   resolutio
                                   https://m
MIB:                               entor.iee
Change the MIB description to      e.org/80
"This attribute specifies the      2.11/dcn/
average duration of the last 16    11/11-11-
                                               Closed   20110120 #44 I
Beacon frames of other mesh        0100-02-
STAs received by this mesh STA. 000s-m-
The value is expressed in units of bs-
microseconds."                     comment-
                                   resolutio
wording:
Change
"NOTE—Delayed beacon
transmission allows mesh STAs to
discover Beacon frames             https://m
transmitted from multiple mesh     entor.iee
STAs of which TBTTs are set        e.org/80
nearly at the same time. It is     2.11/dcn/
recommended to set                 11/11-11-
dot11MeshDelayedBeaconTxMax 0100-02-
                                               Closed   20110120 #44 I
Delay to a longer time than the 000s-m-
typical duration of Beacon frames. bs-
to                                 comment-
"NOTE—Delayed beacon               resolutio
transmissions allow mesh STAs to n-
discover Beacon frames that are text.doc
transmitted from multiple mesh
STAs with TBTTs close to each
other. It is recommended to set
dot11MeshDelayedBeaconTxMax
                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
                                   11/11-11-
wording:                                       Closed   20110120 #44 I
                                   0100-02-
                                   000s-m-
                                   bs-
                                   comment-
                                   resolutio
Delayed beacon transmission:
The reason why the attribute of
the delayed beacon transmission
is controled by MIB variable
(dot11MeshDelayedBeaconTxInte
rval) is that we may want to leave https://m
some flexibility for the           entor.iee
implementation of the delayed      e.org/80
beacon transmission. Delayed       2.11/dcn/
beacon transmission causes         11/11-11-
some inefficiency in terms of      0100-02-
                                               Closed   20110120 #44 I
power save. The neighbor mesh      000s-m-
STAs need to wait for the beacon bs-
reception which is delayed. In   comment-
case STAs are very static in the   resolutio
deployment scenario and the        n-
STAs are keen to save power, the text.doc
delayed beacon transmission is
not useful. MIB variables for
delayed beacon transmission
allows STAs to control the
attribute to meet the deployment
wording:
The sentence is changed to read
"When                             https://m
dot11MeshDelayedBeaconTxInter entor.iee
val is set to non-zero value, the e.org/80
mesh STA shall delay its Beacon   2.11/dcn/
frame transmission from TBTT,     11/11-11-
once every                    0100-02-
                                              Closed   20110120 #44 I
dot11MeshDelayedBeaconTxInter 000s-m-
val. When the mesh STA        bs-
transmits a Beacon frame with     comment-
delay from its TBTT, the delay    resolutio
time shall be randomly selected   n-
between                           text.doc
dot11MeshDelayedBeaconTxMin
Delay and
dot11MeshDelayedBeaconTxMax
                                  https://m
                                  entor.iee
                                  e.org/80
                                  2.11/dcn/
                                  11/11-11-
wording:                                      Closed   20110120 #44 I
                                  0100-02-
                                  000s-m-
                                  bs-
                                  comment-
                                  resolutio
                                  https://m
                                  entor.iee
                                  e.org/80
                                  2.11/dcn/
                                  11/11-11-
wording:                                      Closed   20110120 #44 I
                                  0100-02-
                                  000s-m-
                                  bs-
                                  comment-
                                  resolutio
                                    https://m
wording:                            entor.iee
Change to                           e.org/80
"This attribute specifies the       2.11/dcn/
interval of the delayed beacon      11/11-11-
                                                Closed   20110120 #44 I
transmissions for the purpose of    0100-02-
MBCA. The value 0 indicates that 000s-m-
the delayed beacon transmission bs-
is disabled."                       comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
omission:                           2.11/dcn/
Add "The value is expressed in      11/11-11-
                                                Closed   20110120 #44 I
units of Beacon Interval." to the   0100-02-
end of the paragraph.               000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
wording:                            2.11/dcn/
Remove "shall" from the             11/11-11-
                                                Closed   20110120 #44 I
description in the MIB in clause    0100-02-
D.3 throughout.                     000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                        Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
wording:
                                    entor.iee
"activate" is the recommended
                                    e.org/80
term from ARC study. See page
                                    2.11/dcn/
14 in 11-09-0533-00-0arc-
                                    11/11-11-
recomendation-re-mib-types-and-                 Closed   20110120 #44 I
                                    0100-02-
usage.ppt.
                                    000s-m-
Replace "and set the MBCA
                                    bs-
Enabled subfield" with "and shall
                                    comment-
set the MBCA Enabled subfield"
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                        Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                        Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
wording:                                        Closed   20110120 #44 I
                                    0100-02-
                                    000s-m-
                                    bs-
                                    comment-
                                    resolutio

                                                Closed   20110120 #47 I
wording:
1) Change
"The maximum number of Beacon
Timing Information fields
contained in a Beacon Timing
element is limited to          https://m
dot11MeshBeaconTimingReportM entor.iee
axNum for Beacon frames, or to e.org/80
50 for other frames."                2.11/dcn/
to                            11/11-11-
"The maximum number of Beacon 0100-02-
Timing Information fields                        Closed   20110120 #44 I
                              000s-m-
contained in a Beacon Timing         bs-
element is limited to          comment-
dot11MeshBeaconTimingReportM resolutio
axNum for Beacon frames, or is n-
limited by the maximum               text.doc
information element size for other
frames."
2)
dot11MeshBeaconTimingReportM
axNum is defined to control the
beacon bloat. Some
wording:
Change
"The Beacon Timing element           https://m
reports on MBSS, IBSS, and       entor.iee
infrastructure BSS Beacon frames e.org/80
that are received from the       2.11/dcn/
neighbor STAs with which the         11/11-11-
mesh STA maintains                   0100-02-
                                                 Closed   20110120 #44 I
synchronization on the operating     000s-m-
channel."                            bs-
to                                   comment-
"The Beacon Timing element           resolutio
reports on timing information of     n-
the Beacon frames that are           text.doc
received from the neighbor STAs
with which the mesh STA
maintains synchronization on the
wording:
Change                                  https://m
"The TBTT Adjusting subfield is         entor.iee
set to 1 while the TBTT adjusting       e.org/80
procedure is on going to notify         2.11/dcn/
that the mesh STA's TBTT is             11/11-11-
shifting intentionally, and is set to   0100-02-
                                                     Closed   20110120 #44 I
0 otherwise. (See 11C.12.4.4.3          000s-m-
(Adjustment procedure).)"               bs-
into                                    comment-
"The TBTT Adjusting subfield is         resolutio
set to 1 when the TBTT                  n-
adjustment procedure is ongoing, text.doc
and is set to 0 otherwise. (See
                                        https://m
                                        entor.iee
                                        e.org/80
wording: "activate" is the
                                        2.11/dcn/
recommended term from ARC
                                        11/11-11-
study. See page 14 in 11-09-0533-                    Closed   20110120 #44 I
                                        0100-02-
00-0arc-recomendation-re-mib-
                                        000s-m-
types-and-usage.ppt
                                        bs-
                                        comment-
                                        resolutio
                                        https://me
                                        ntor.ieee.
                                        org/802.1
Submission 802.11-11/0220r2
                                        1/dcn/11/
provides resolutions to this            11-11-       Closed   20110210 #60 I
comment.                                0220-02-
                                        000s-m-
                                        bs-
                                        comment-
                                        https://m
                                        entor.iee
                                        e.org/80
wording: (beacon timing
                                        2.11/dcn/
inforamtion)
                                        11/11-11-
A new subclause "Beacon timing                       Closed   20110120 #44 I
                                        0100-02-
information" is created. See
                                        000s-m-
submission 11-11-100.
                                        bs-
                                        comment-
                                        resolutio
                                     https://m
wording: (beacon timing              entor.iee
inforamtion)                         e.org/80
Storing abbreviated TBTT is the      2.11/dcn/
minimum requirement to a mesh        11/11-11-
                                                 Closed   20110120 #44 I
STA. It does not preclude the        0100-02-
implementation storing entire 64     000s-m-
bits. There is no need to change     bs-
the text.                            comment-
                                     resolutio
wording:
"When a Beacon frame is
received from one of its neighbor
STAs with which the mesh STA
                                     https://m
maintains
                                     entor.iee
synchronization, the mesh STA
                                     e.org/80
shall calculate the TBTT of the
                                     2.11/dcn/
received Beacon frame as follows:
                                     11/11-11-
TTBTT = Tr – (Tt modulo
                                     0100-02-
                                                 Closed   20110120 #44 I
                                     000s-m-
where
                                     bs-
TTBTT is the calculated TBTT
                                     comment-
Tr is the frame reception time
                                     resolutio
measured in the receiving mesh
                                     n-
STA’s TSF timer
                                     text.doc
Tt is the value in the Timestamp
field in the received frame
TBeaconInterval is the value in
the Beacon interval field in the
received frame"
wording:
                                     https://m
11C.12.3.2 (Beacon reception for
                                     entor.iee
mesh STA) is trying to provide the
                                     e.org/80
same level text as 11.1.2.3
                                     2.11/dcn/
(Beacon reception) in the base
                                     11/11-11-
standard REVmb D4.0. 11.1.2.3
                                     0100-02-
(Beacon reception) in the base                   Closed   20110120 #44 I
                                     000s-m-
standard only talks about which
                                     bs-
information shall be taken from
                                     comment-
the received beacon frame and
                                     resolutio
does not specify the specific
                                     n-
actions. Actions taken after
                                     text.doc
receiving beacons vary, and they
Clock drift:                           https://me
                                       ntor.ieee.
Neighbor Offset protocol is            org/802.1
designed according to the              1/dcn/11/
consensus bulit on a long              11-11-
                                       0101-04-
discussion. It should be                             Closed   20110210 #60 I
                                       000s-m-
reasonable to keep the current         bs-
functions as a set of Neighbor         comment-
                                       resolution-
Offset protocol. See strawpoll
                                       overview.
result in 11-11/101r4.                 ppt




                                       https://m
                                       entor.iee
                                       e.org/80
wording:
                                       2.11/dcn/
The cited text is talking about the
                                       11/11-11-
T_offset value. It should be more                    Closed   20110120 #44 I
                                       0100-02-
reader friendly to describe it after
                                       000s-m-
explaining what T_offset is about.
                                       bs-
                                       comment-
                                       resolutio
wording:                               https://m
Looking at 11.1.3.0a (General),        entor.iee
11.1.3.3 (Initializing a BSS), etc, in e.org/80
the base standard (REVmb D4.0), 2.11/dcn/
this kind of description is present    11/11-11-
                                                     Closed   20110120 #44 I
in clause explaining MLME.             0100-02-
Actually, the cited text is helpful in 000s-m-
explaining MLME procedure. The bs-
paragraph should remain here for comment-
the better readability.                resolutio
MLME:                                https://m
Add parameter peerMAC to             entor.iee
- MLME-                              e.org/80
MeshNeighborOffsetMeasure.conf 2.11/dcn/
irm                                  11/11-11-
                                                 Closed   20110120 #44 M
- MLME-                              0100-02-
MeshNeighborOffsetSyncStart.co 000s-m-
nfirm                                bs-
- MLME-                              comment-
MeshNeighborOffsetSyncStop.co resolutio
                              https://m
                                     entor.iee
                                     e.org/80
MLME:
                                     2.11/dcn/
Change the valid range to "–2^63
                                     11/11-11-
to (2^63– 1)" Apply the same                     Closed   20110120 #44 I
                                     0100-02-
change in 10.3.75.4.4.
                                     000s-m-
See submission 11-11-100.
                                     bs-
                                     comment-
                                     resolutio

                                     https://m
                                     entor.iee
wording:                             e.org/80
The cited text is intended to        2.11/dcn/
provide a clear explaination of the 11/11-11-
timing offset value without          0100-02-
                                                 Closed   20110120 #44 I
ambiguity. It does not hurt          000s-m-
anything if such text is provided.   bs-
Proposed text causes ambiguity of comment-
the operation.                       resolutio
                                     n-
                                     text.doc
                                      https://m
                                      entor.iee
wording:                              e.org/80
The cited text is intended to         2.11/dcn/
provide a clear explaination of the 11/11-11-
                                                  Closed   20110120 #44 I
procedure. It does not hurt         0100-02-
anything if such text is provided     000s-m-
here.                                 bs-
                                      comment-
                                      resolutio


These dashed items are parallel
condition. It should be better to
leave the condition "after an                     Closed   20110120 #47 I
MLME-RESET.request primitive"
in line.


wording:                              https://m
Looking at 11.1.3.0a (General),       entor.iee
11.1.3.3 (Initializing a BSS), etc, in e.org/80
the base standard (REVmb D4.0), 2.11/dcn/
this kind of description is present   11/11-11-
                                                  Closed   20110120 #44 I
in clause explaining MLME.            0100-02-
Actually, the cited text is helpful in 000s-m-
explaining MLME procedure. The bs-
paragraph should remain here for comment-
the better readability.               resolutio
                                      https://m
                                      entor.iee
extensible framework:
                                      e.org/80
The condition for generating
                                      2.11/dcn/
MLME-START.request is modified
                                      11/11-11-
to satisfy the commenter's                        Closed   20110120 #44 I
                                      0100-02-
concern. Submission11-11-100
                                      000s-m-
provides a resolution to this
                                      bs-
comment.
                                      comment-
                                      resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
                                      11/11-11-
wording:                                          Closed   20110120 #44 I
                                      0100-02-
                                      000s-m-
                                      bs-
                                      comment-
                                      resolutio



MIB:
What has to be achieved with the
Neighbor Offset protocol is as
follows:                              https://m
1) A mesh STA shall maintain          entor.iee
sync with neghbor peer mesh           e.org/80
STA.                                  2.11/dcn/
2) A mesh STA should maintain         11/11-11-
sync with non-peer mesh STA that 0100-02-
                                                  Closed   20110120 #44 I
belongs to the same MBSS.             000s-m-
3) Additionally a mesh STA should bs-
maintain sync with mesh STAs          comment-
that belong to different MBSSs.       resolutio
The cited text is clear enough to     n-
explain this operation.               text.doc
dot11MeshNbrOffsetMaxNeighbor
is defined as a capability variable
which is useful.
wording:
Change                              https://m
"Although a mesh STA may            entor.iee
include multiple implementations    e.org/80
of the synchronisation protocol, all 2.11/dcn/
the mesh STAs in an MBSS shall 11/11-11-
use the same synchronisation        0100-02-
                                                 Closed   20110120 #44 I
protocol."                          000s-m-
into                                bs-
"Although a mesh STA may            comment-
include multiple implementations    resolutio
of synchronisation protocols, only n-
one synchronization protocol shall text.doc
be used by a mesh STA at a time
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
Do not forget to apply the same
                                    11/11-11-
changes in subclauses under                      Closed   20110120 #42 I
                                    0163-01-
7.3.2.96 throughout.
                                    000s-xls-
                                    to-frame-
                                    format-
                                    comment
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
Do not forget to apply the same
                                    11/11-11-
changes in subclauses under                      Closed   20110120 #42 I
                                    0163-01-
7.3.2.96 throughout.
                                    000s-xls-
                                    to-frame-
                                    format-
                                    comment
                                    https://me
                                    ntor.ieee.
                                    org/802.1
Submission 802.11-11/0220r2
                                    1/dcn/11/
provides resolutions to this        11-11-       Closed   20110210 #60 I
comment.                            0220-02-
                                    000s-m-
                                    bs-
                                    comment-
                                     https://m
                                     entor.iee
                                     e.org/80
wording:
                                     2.11/dcn/
Looking at the context of the
                                     11/11-11-
paragraph, it seems that the                      Closed   20110120 #44 I
                                     0100-02-
original text fits better than the
                                     000s-m-
proposed text.
                                     bs-
                                     comment-
                                     resolutio
                                     https://m
                                     entor.iee
                                     e.org/80
                                     2.11/dcn/
                                     11/11-11-
wording:                                          Closed   20110120 #44 I
                                     0100-02-
                                     000s-m-
                                     bs-
                                     comment-
                                     resolutio
wording:                             https://m
Change                               entor.iee
"Mesh STAs receiving a Beacon        e.org/80
frame may accept the timing          2.11/dcn/
information depending on their       11/11-11-
active synchronization protocol."    0100-02-     Closed   20110120 #44 I
into                                 000s-m-
"Mesh STAs receiving a Beacon        bs-
frame may use the timing             comment-
information in the Beacon frame      resolutio
depending on their active            n-
                                     https://me
                                     ntor.ieee.
                                     org/802.1
Submission 802.11-11/0220r2
                                     1/dcn/11/
provides resolutions to this         11-11-       Closed   20110210 #60 I
comment.                             0220-02-
                                     000s-m-
                                     bs-
                                     comment-
                                      https://m
                                      entor.iee
                                      e.org/80
doc struture:
                                      2.11/dcn/
The cited text is moved to
                                      11/11-11-
11.1.1.3. Submission 11-11-100                    Closed   20110120 #44 I
                                      0100-02-
provides a resolution to this
                                      000s-m-
comment.
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
wording:
                                      entor.iee
"A mesh STA that utilizes the
                                      e.org/80
Neighbor Offset Protocol may
                                      2.11/dcn/
start its TSF timer independently
                                      11/11-11-
of other mesh STAs." This is the                  Closed   20110120 #44 I
                                      0100-02-
only description concerning the
                                      000s-m-
initialization of the TSF timer. No
                                      bs-
need to create a subclause to
                                      comment-
describe this.
                                      resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
doc struture:
                                      2.11/dcn/
The cited text is moved to
                                      11/11-11-
11.1.1.3. Submission 11-11-100                    Closed   20110120 #44 I
                                      0100-02-
provides a resolution to this
                                      000s-m-
comment.
                                      bs-
                                      comment-
                                      resolutio
                                      https://m
doc struture:
                                      entor.iee
"A Timing Synchronization
                                      e.org/80
Function (TSF) keeps the timers
                                      2.11/dcn/
for all STAs in the same BSS
                                      11/11-11-
synchronized." is not applicable to               Closed   20110120 #44 I
                                      0100-02-
mesh STAs, as each mesh STA
                                      000s-m-
maintains its own TSF timer and
                                      bs-
there will be multiple TSF timer
                                      comment-
value in a mesh BSS.
                                      resolutio
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
See submission 11-11-0162-00-       11/11-11-
                                                 Closed   20110120 #42 I
000s for resolution.                0163-01-
                                    000s-xls-
                                    to-frame-
                                    format-
                                    comment
                                    https://m
                                    entor.iee
                                    e.org/80
                                    2.11/dcn/
                                    11/11-11-
See resolution to CID 1283.                      Closed   20110120 #42 I
                                    0163-01-
                                    000s-xls-
                                    to-frame-
                                    format-
                                    comment
Replace all occurences of "Mesh     https://m
Flags field" with "Mesh Flags       entor.iee
subfield", and replace all          e.org/80
occurences of "Mesh TTL field"      2.11/dcn/
with "Mesh TTL subfield", and       11/11-11-
replace all occurences of "Mesh     0163-01-     Closed   20110120 #42 I
Sequence Number field" with         000s-xls-
"Mesh Sequence Number               to-frame-
subfield", and replace all          format-
occurences of "Mesh Address         comment
Extension field" with "Mesh         s.xls
                                   https://me
                                   ntor.ieee.
Resolved in submission             org/802.1
https://mentor.ieee.org/802.11/dcn 1/dcn/11/
                                   11-11-        Closed   20110210 #66 I
/11/11-11-0232-00-000s-
                                   0232-00-
resolution-to-cid-1286.doc         000s-
                                   resolution-
                                   to-cid-
                                  https://me
                                  ntor.ieee.
Informative text for RANN mode org/802.1
                                  1/dcn/11/
added. Resolved in submission 11- 11-11-           Closed   20110210 #65 I
11-0233-00-000s.                  0233-00-
                                  000s-
                                  informativ
                                  e-annex-
                                     https://m
                                     entor.iee
                                     e.org/80
                                     2.11/dcn/
Update Subclause D.3 as              11/11-11-
                                                   Closed   20110120 #46 I
indicated in 11-11/182r0.            0182-00-
                                     000s-
                                     resolutio
                                     ns-to-mib-
                                     conflicts.
The text of 11C.7.3 states that      https://m
“Each peer mesh STA may              entor.iee
request a link metric report from a e.org/80
neighbor peer mesh STA”. This        2.11/dcn/
implies that the peer mesh STA       11/11-11-
must have implemented the Link       0183-01-      Closed   20110120 #48 I
metric reporting functionality. In   000s-
fact, it is stated that “A mesh STA mesh-
receiving a Mesh Link Metric         link-
Report element with the Request      reporting-
subfield of the Flags field equal to changes.
                                     https://me
                                     ntor.ieee.
                                     org/802.1
Change the text to read: if the      1/dcn/11/
MCCAOP responder operates in         11-11-
                                     0128-01-      Closed   20110120 #43 I
light sleep mode for the             000s-m-
MCCAOP owner."                       pm-
                                     comment-
                                     resolution-
                                     text.doc
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
                                     11-11-
                                     0128-01-      Closed   20110120 #43 I
                                     000s-m-
                                     pm-
                                     comment-
                                     resolution-
                                     text.doc
                                     https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
                                     11-11-        Closed   20110120 #43 I
                                     0128-01-
                                     000s-m-
                                     pm-
                                     comment-
Remove the redundant: "and may       https://me
                                     ntor.ieee.
contain one or more TXOPs"
                                     org/802.1
Add to page 279, line 18: " Two      1/dcn/11/
mesh peer service periods may        11-11-        Closed   20110120 #43 I
                                     0128-01-
be initiated with a peer trigger
                                     000s-m-
frame to enable both the             pm-
transmitter and the receiver to be   comment-
                                     resolution-
an owner of sentence:"A mesh
Change the the mesh peer
STA in light or deep sleep mode
may receive peer trigger frames
when its Mesh Awake Window is
active as described in 11C.13.7     https://me
(Mesh Awake Window)." to: "If a     ntor.ieee.
mesh STA receives a peer trigger org/802.1
                                    1/dcn/11/
frame initiating a mesh peer        11-11-
service period from a peer mesh 0128-01-           Closed   20110120 #43 I
STA in deep sleep for the link, the 000s-m-
                                    pm-
mesh STA shall remain in Awake
                                    comment-
state until the mesh peer service resolution-
period is terminated as defined in text.doc
11C.13.10.4 (Termination of a
mesh peer service period). The
mesh STA may return to Doze
state after its Mesh Awake
Window if no peer trigger frame is
                                    https://me
                                    ntor.ieee.
                                    org/802.1
The comment resolution to
                                    1/dcn/11/
CID1294 is providing better text to 11-11-       Closed   20110120 #43 I
describe the sentence.              0128-01-
                                    000s-m-
                                    pm-
                                    comment-
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/
                                    11-11-       Closed   20110120 #43 I
                                    0128-01-
                                    000s-m-
                                    pm-
                                    comment-
The mesh awake window may           https://me
terminate before all group          ntor.ieee.
addressed frames are transmitted. org/802.1
                                    1/dcn/11/
There is rule to increase the       11-11-
duration of the mesh Awake          0128-01-     Closed   20110120 #43 I
Window, but if the group            000s-m-
                                    pm-
addressed frames transmission       comment-
continues after the mesh Awake resolution-
Window, the mesh STA shall stay text.doc
Awake tothe sentence:"when they https://me
Replace transmit the group
                                    ntor.ieee.
do not have a mesh peer service     org/802.1
period ongoing." with:" when the    1/dcn/11/
                                    11-11-       Closed   20110120 #43 I
active STA does not operate as
                                    0128-01-
owner in peer service period with   000s-m-
the peer mesh STA."                 pm-
                                    comment-
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/
                                    11-11-       Closed   20110120 #43 I
                                    0128-01-
                                    000s-m-
                                    pm-
                                    comment-
Change the text:"... if the
conditions definedin 11C.13.9.3
(Operation in light sleep mode),    https://me
11C.13.9.4 (Operation in deep       ntor.ieee.
                                    org/802.1
sleep mode), and 11C.13.10          1/dcn/11/
(Mesh peer service periods) are     11-11-
met; otherwise, the mesh STA        0128-01-      Closed   20110120 #43 I
                                    000s-m-
shall buffer frames."               pm-
To:"... if the mesh STA is in       comment-
Awake state as defined in           resolution-
                                    text.doc
11C.13.9.3 (Operation in light
sleep mode), 11C.13.9.4
(Operation in deep sleep mode),
                                    https://me
                                    ntor.ieee.
                                    org/802.1
The sentence is deleted from
                                    1/dcn/11/
11C.13.7. The sentence is not       11-11-        Closed   20110120 #43 I
needed in 11C.13.10.                0128-01-
                                    000s-m-
                                    pm-
                                    comment-
                                    https://me
                                    ntor.ieee.
                                    org/802.1
The sentence is added to end of     1/dcn/11/
                                    11-11-        Closed   20110120 #43 I
the line 20.
                                    0128-01-
                                    000s-m-
                                    pm-
                                    comment-
Change the sentence: "A mesh        https://me
                                    ntor.ieee.
STA in light or deep sleep mode
                                    org/802.1
shall be in Awake state when its 1/dcn/11/
Mesh Awake Window is active." to 11-11-           Closed   20110120 #43 I
                                    0128-01-
" A mesh STA in active, light sleep
                                    000s-m-
or deep sleep mode shall be in      pm-
Awake state when its Mesh           comment-
                                    resolution-
Awake Window is active."            https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/
                                    11-11-        Closed   20110120 #43 I
                                    0128-01-
                                    000s-m-
                                    pm-
                                    comment-
                                      https://me
                                      ntor.ieee.
Add to the line 54 in page 275:       org/802.1
"The TIM element is handled as        1/dcn/11/
                                      11-11-        Closed   20110120 #43 I
described in 7.3.2.6 (TIM
                                      0128-01-
element)."                            000s-m-
                                      pm-
                                      comment-
The discussion of the peer mesh       https://me
                                      ntor.ieee.
STA in deep sleep mode does not
                                      org/802.1
concern transition to lower power 1/dcn/11/
mode. Remove:"mesh STA is in          11-11-        Closed   20110120 #43 I
                                      0128-01-
deep sleep mode for a link or the".
                                      000s-m-
The remaining sentence is in hte pm-
scope of transition to lower activity comment-
                                      resolution-
mode.




                                 https://me
                                 ntor.ieee.
                                 org/802.1
Add to line 54 at page 274 the   1/dcn/11/
following text: "The non-peer    11-11-
                                 0128-01-           Closed   20110120 #43 I
mesh power mode is set to active 000s-m-
or deep sleep mode."             pm-
                                 comment-
                                 resolution-
                                 text.doc




                                 https://me
                                 ntor.ieee.
The clause structure is enhanced org/802.1
to include four levels of        1/dcn/11/
                                 11-11-             Closed   20110120 #43 I
subsections.
                                 0128-01-
                                 000s-m-
                                 pm-
                                 comment-
                                    https://me
                                    ntor.ieee.
                                    org/802.1
Change the text to read:"The        1/dcn/11/
Power Management field and          11-11-
                                    0128-01-      Closed   20110120 #43 I
Mesh Power Save Level indicate      000s-m-
the mesh power mode in use."        pm-
                                    comment-
                                    resolution-
                                    text.doc
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/
                                    11-11-        Closed   20110120 #43 I
                                    0128-01-
                                    000s-m-
                                    pm-
                                    comment-
                                    https://me
                                    ntor.ieee.
                                    org/802.1
The delete the sentence. PICS       1/dcn/11/
                                    11-11-        Closed   20110120 #43 I
provides the same information.
                                    0128-01-
                                    000s-m-
                                    pm-
                                    comment-
BT element procedure:
Change the sentence to read "       https://m
When the status number is           entor.iee
updated, the mesh STA shall         e.org/80
include the tuple of beacon timing 2.11/dcn/
information indexed as 0 in the    11/11-11-
Beacon Timing element in the        0100-02-
                                                  Closed   20110120 #44 I
subsequent Beacon frame.            000s-m-
Successive tuples shall be          bs-
transmitted in ascending order of   comment-
the index number in the             resolutio
successive Beacon frames."          n-
When the TBTT is deleted,           text.doc
neighbor mesh STAs can obtain
                                   https://me
                                   ntor.ieee.
                                   org/802.1
                                   1/dcn/11/
Submission 802.11-11/0220r2        11-11-
provides resolutions to this       0220-02-      Closed   20110210 #60 I
comment.                           000s-m-
                                   bs-
                                   comment-
                                   resolution-
                                   text.doc



                                   https://m
                                   entor.iee
                                   e.org/80
                                   2.11/dcn/
In document 11-11/116r0            11/11-11-
“Performance Results for           0166-00-
Extended Congestion Notification 000s-
                                                 Closed   20110120 #51 I
IE” it is shown that this added IE performa
can help to improve the            nce-
performance                        results-
                                   for-
                                   extended-
                                   congesti
                                   on-
                                   notificati
                                   https://me
Serious refinement done. 9.22
                                   ntor.ieee.
deals with everything inside the   org/802.1
MBSS, 11C.10.3 deals with          1/dcn/11/
                                   11-11-        Closed   20110210 #63 I
everything that crosses the DS-
                                   0229-02-
MBSS border.                       000s-rfi-
text provided in 11-11/229         forwardin
                                   g-
Only first part of commented
paragraph has been kept. Second
part has been deleted. The clause https://me
on forwarding to non-MBSS STAs ntor.ieee.
                                    org/802.1
has been rewriten.                  1/dcn/11/
to 1. - this is implicitly assumed  11-11-
and expected.                       0229-02-     Closed   20110210 #63 I
                                    000s-rfi-
to 2. - expected behaviour is still forwardin
to forward it to the DS. Now, mesh g-
gate may sent PERR to mesh          resolution
                                    s.doc
source.
text changes are provided in doc
11-11/229
                                    https://me
Serious refinement done. 9.22
                                    ntor.ieee.
deals with everything inside the    org/802.1
MBSS, 11C.10.3 deals with           1/dcn/11/
                                    11-11-       Closed   20110210 #63 I
everything that crosses the DS-
                                    0229-02-
MBSS border.                        000s-rfi-
text provided in 11-11/229          forwardin
                                    g-
                                    https://me
                                    ntor.ieee.
Serious refinement done. 9.22       org/802.1
deals with everything inside the    1/dcn/11/
MBSS, 11C.10.3 deals with           11-11-
                                    0229-02-     Closed   20110210 #63 I
everything that crosses the DS-     000s-rfi-
MBSS border.                        forwardin
text provided in 11-11/229          g-
                                    resolution
                                    s.doc
11C.7.3 page 224, line 61 states
that the Link Metric Report frame
contains "link metric value for the
                                      https://m
corresponding link"; second part
                                      entor.iee
of comment: after “Upon reception
                                      e.org/80
of a Mesh Link Metric Report
                                      2.11/dcn/
frames, a peer mesh STA may
                                      11/11-11-
update its local link metric
                                      0183-01-
information using the link metric                  Closed   20110120 #48 I
                                      000s-
information received.” (page 224,
                                      mesh-
lines 64-65) add “The procedure
                                      link-
to update the local link metric
                                      reporting-
information with the link metric
                                      changes.
information received by a
                                      doc
neighbor peer mesh STA is
outside the scope of the
standard”. The method used to
The use the airtime link metric is
calculateof the link metric           https://m
reporting is not mandatory when       entor.iee
the default path selection protocol e.org/80
HWMP and the default path metric 2.11/dcn/
Airtime is used. Here as well as in 11/11-11-
                                                   Closed   20110120 #48 I
other path selection protocols, the 0183-01-
link metric reporting may be used. 000s-
The determination when to use         mesh-
the link metric reporting is          link-
considered to be implementation       reporting-
Add the following immediately
after the heading "11.3 STA
authentication and association" in
IEEE 802.11-2007: "A STA for
which dot11MeshActivated is true
uses the Mesh Peering
Management framework (11C.3)                       Closed   20110210 #66 I
and does not keep this state
variable. Instead this STA uses a
Mesh peering instance controller
that manages states and state
variables similar to the ones
described in this clause."
                                https://m
                                entor.iee
                                e.org/80
add ResultCode with SUCCESS,    2.11/dcn/
INVALID_PARAMETERS,             11/11-11-
                                            Closed   20110120 #49 I
TIME_OUT,                       0189-00-
UNSPECIFIED_FAILURE             000s-rfi-
                                proxy-
                                comment-
                                resolutio
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
The resultcode contains
                                11/11-11-
Advertisement_TIMEOUT as a                  Closed   20110120 #41 I
                                0179-01-
result code
                                000s-
                                mcca-
                                comment
                                s-
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
                                            Closed   20110120 #41 I
                                0179-01-
                                000s-
                                mcca-
                                comment
                                s-
                                https://m
                                entor.iee
                                e.org/80
MLME:                           2.11/dcn/
The "Status Code" is replaced   11/11-11-
                                            Closed   20110120 #44 I
with "ReasonCode". See          0100-02-
submission 11-11-100.           000s-m-
                                bs-
                                comment-
                                resolutio
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
                                      11/11-11-
accept                                0057-01-    Closed   20110120 #40 I
                                      000s-
                                      security-
                                      comment
                                      s-1st-
                                      recirc.do
Serious rewrite done and in       https://me
                                  ntor.ieee.
11C.10.3. 9.22.3 is now about the
                                  org/802.1
case where a source end STA       1/dcn/11/
which is a mesh STA inside the    11-11-          Closed   20110210 #63 I
                                  0229-02-
MBSS cannot find a path to the
                                  000s-rfi-
destination and forwards the      forwardin
frame to the known mesh gates. g-
                                  resolution
text provided in 11-11/229        https://me
                                  ntor.ieee.
added description similar to mesh org/802.1
data frames. contains now         1/dcn/11/
                                  11-11-          Closed   20110210 #63 I
address 1 through 4. Text
                                  0229-02-
provided in doc 11-11/229.        000s-rfi-
                                  forwardin
                                  g-
Did not include Mesh Flags field in
                                  https://me
                                    ntor.ieee.
order to avoid very long chain
                                    org/802.1
pointer: "with the Address          1/dcn/11/
Extension Mode subfield in the      11-11-        Closed   20110210 #63 I
                                    0229-02-
Mesh Control field set to 01
                                    000s-rfi-
(binary)". Also done for other      forwardin
occurrances. Text has moved.        g-
                                    resolution
Changes provided in doc 11-         https://me
                                    ntor.ieee.
insert after "discarded" and before org/802.1
                                    1/dcn/11/
the comma "and one or more          11-11-
MSDUs are collected from the        0229-02-      Closed   20110210 #63 I
frame"                              000s-rfi-
                                    forwardin
implemented in 11-11/229            g-
                                    resolution
                                    s.doc
                                    https://me
as in comment
                                    ntor.ieee.
also insert "field" after "Mesh     org/802.1
Control" on page 228 line 31 in     1/dcn/11/
                                    11-11-       Closed   20110210 #63 I
clause 11C.9.2 Terminology
                                    0229-02-
(D8.0)                              000s-rfi-
implemented in 11-11/229            forwardin
                                    g-




                                    https://me
                                    ntor.ieee.
                                    org/802.1
commented paragraph has been        1/dcn/11/
moved to 11C.10.3.3 and             11-11-
                                    0229-02-     Closed   20110210 #63 I
substantially changed.              000s-rfi-
text provided in doc 11-11/229      forwardin
                                    g-
                                    resolution
                                    s.doc




Did not include Mesh Flags field in https://me
                                    ntor.ieee.
order to avoid very long chain
                                    org/802.1
pointer: "with the Address          1/dcn/11/
Extension Mode subfield in the      11-11-       Closed   20110210 #63 I
                                    0229-02-
Mesh Control field set to 01
                                    000s-rfi-
(binary)". Also done for other      forwardin
occurrances. Text has moved.        g-
                                    resolution
Changes provided in doc 11-         https://me
                                    ntor.ieee.
                                    org/802.1
paragraph removed, done in doc      1/dcn/11/
                                    11-11-       Closed   20110210 #63 I
11-11/229
                                    0229-02-
                                    000s-rfi-
                                    forwardin
                                    g-
                                     https://me
                                     ntor.ieee.
                                     org/802.1
paragraph with commented text
                                     1/dcn/11/
has been deleted. done in doc 11- 11-11-          Closed   20110210 #63 I
11/229                               0229-02-
                                     000s-rfi-
                                     forwardin
                                     g-
The parts of the forwarding          https://me
                                     ntor.ieee.
information such as lifetime or
                                     org/802.1
precursor list are generic. The      1/dcn/11/
forwarding rules can be applied to 11-11-         Closed   20110210 #63 I
                                     0229-02-
every routing protocol. However,
                                     000s-rfi-
one might assume generic values forwardin
such as infinity for lifetime or any g-
                                     resolution
for precursor.                       https://me
                                     ntor.ieee.
                                     org/802.1
                                     1/dcn/11/
implemented in doc 11-11/229         11-11-       Closed   20110210 #63 I
                                     0229-02-
                                     000s-rfi-
                                     forwardin
                                     g-
The parts of the forwarding          https://me
                                     ntor.ieee.
information such as lifetime or
                                     org/802.1
precursor list are generic. The      1/dcn/11/
forwarding rules can be applied to 11-11-         Closed   20110210 #63 I
                                     0229-02-
every routing protocol. However,
                                     000s-rfi-
one might assume generic values forwardin
such as infinity for lifetime or any g-
                                     resolution
for precursor.
- item d) becomes separate
paragraph.                        https://me
- Did not include "When the       ntor.ieee.
MSDU is not discarded ..."        org/802.1
                                  1/dcn/11/
because this is implicit.         11-11-
- removed "and one or more        0229-02-     Closed   20110210 #63 I
MSDUs are collected from the      000s-rfi-
                                  forwardin
frame" in line 60                 g-
'- changes implemented in doc 11- resolution
11/229                            s.doc
nevertheless, added references
for HWMP as example.
implemented in doc 11-11/229.
The 3 choices really only depend
on the availability (usually called
"knowledge of the destination
address") of a path to the mesh
destination. Although such rules    https://me
as proposed by the commenter        ntor.ieee.
                                    org/802.1
are possible, they are not          1/dcn/11/
intended. The intention is that any 11-11-
path selection protocol has these 0229-02-       Closed   20110210 #63 I
                                    000s-rfi-
3 choices, because each one         forwardin
stresses a certain aspect or        g-
behaviour:                          resolution
                                    s.doc
item 1) assumes that this is a
malicious frame, if it were not,
there would be a path
item 2) assumes that the path just
timed out or got deleted due to
some broken link, so the frame is
alright, I just need to find a new
path, and the intermediate node
The MA-UNITDATA.request is still
there, because this indicates that
the mesh STA is the source end
STA for this kind of data frames.
Did not include Mesh Flags field in https://me
                                     ntor.ieee.
order to avoid very long chain       org/802.1
pointer: "with the Address           1/dcn/11/
Extension Mode subfield in the       11-11-
                                     0229-02-     Closed   20110210 #63 I
Mesh Control field set to 01         000s-rfi-
(binary)"                            forwardin
moved the part on the MSDUs          g-
                                     resolution
received from the DS to              s.doc
11C.10.3.3
some text changes
all changes implemented in doc
11-11/229




                                    https://me
general forwarding information is   ntor.ieee.
now in the new section 9.22.2       org/802.1
                                    1/dcn/11/
Forwarding information. 11C.9.8.4 11-11-
                                                  Closed   20110210 #63 I
now only contains addtions to the 0229-02-
forwarding info by HWMP.            000s-rfi-
                                    forwardin
implemented in doc 11-11/229        g-
                                    resolution
Did not include Mesh Flags field in https://me
                                    ntor.ieee.
order to avoid very long chain
                                    org/802.1
pointer: "with the Address          1/dcn/11/
Extension Mode subfield in the      11-11-        Closed   20110210 #63 I
                                    0229-02-
Mesh Control field set to 01
                                    000s-rfi-
(binary)". Also done for other      forwardin
occurrances. Text has moved.        g-
                                    resolution
Changes provided in doc 11-
We do not consider it necessary
to specify the different ways of
                                    https://me
finding the forwarding info at what
                                    ntor.ieee.
time. Instead, the description in   org/802.1
9.22.2.2.1 assumes a function       1/dcn/11/
                                    11-11-
get_nexthop_from_forwarding_info
                                    0229-02-       Closed   20110210 #63 I
( mesh_DA) which will return the 000s-rfi-
MAC address of the next hop if it forwardin
                                    g-
exists (i.e. if it is stored in the
                                    resolution
forwarding information or if it can s.doc
be computed/ determined
somehow. The latter would be the
                                      https://me
"Address 3 corresponds to the         ntor.ieee.
                                      org/802.1
mesh source address (mesh SA)
                                      1/dcn/11/
of the group addressed Mesh           11-11-       Closed   20110210 #63 I
Data frame."                          0229-02-
                                      000s-rfi-
done in 11-11/229
                                      forwardin
                                      g-
The mesh STA of the comment
covers two different situations:
1) forwarding via an intermediate
mesh STA, or in other words,     https://me
concatenated mesh paths (the via ntor.ieee.
                                 org/802.1
mesh STA is in address 3 and the 1/dcn/11/
final destination mesh STA is in 11-11-
address 5)                       0229-02-          Closed   20110210 #63 I
                                 000s-rfi-
2) forwarding at a proxy mesh    forwardin
gate into an external network.   g-
Case 1) also includes cases      resolution
                                 s.doc
where the mesh STA is not a
proxy mesh gate. Since a proxy
mesh gate is also a mesh STA,
mesh STA is used as the more
added missing case where              https://me
                                      ntor.ieee.
MSDU/MMPDU received from
                                      org/802.1
mesh path and forwarded on            1/dcn/11/
different mesh path. Therefore,       11-11-
                                      0229-02-     Closed   20110210 #63 I
again, mesh STA is the more
                                      000s-rfi-
general term covering all cases       forwardin
(see also CID 1346)                   g-
                                      resolution
changes implemented in doc 11-
                                      s.doc
11/229
                                     https://me
                                     ntor.ieee.
                                     org/802.1
"… by proxy mesh gates and by
                                     1/dcn/11/
source mesh STAs."                   11-11-       Closed   20110210 #63 I
implemented in doc 11-11/229         0229-02-
                                     000s-rfi-
                                     forwardin
                                     g-
This paragraph is only describing
what the meaning of the different
                                    https://me
addresses is. References to the
                                    ntor.ieee.
forwarding at proxy mesh gates      org/802.1
and to the description of the proxy 1/dcn/11/
                                    11-11-
information would be overloading
                                    0229-02-      Closed   20110210 #63 I
this paragraph.                     000s-rfi-
However, a reference to Figure 9- forwardin
                                    g-
38 would be helpful. Is added in
                                    resolution
doc 11-11/229.                      s.doc
Also made the last sentence more
generic. Is implemented in doc 11-
                                   https://me
                                   ntor.ieee.
Values are corrected. Changed      org/802.1
the layout ("… equals 10           1/dcn/11/
                                                  Closed   20110210 #63 I
(binary)"). Implemented in doc 11- 11-11-
                                   0229-02-
11/229                             000s-rfi-
                                   forwardin
                                   g-



changes implemented in doc 11-     https://me
11/229.                            ntor.ieee.
First sentence changed as          org/802.1
                                   1/dcn/11/
commenter suggested.               11-11-
Second sentence does not include 0229-02-         Closed   20110210 #63 I
Mesh Flags field in order to avoid 000s-rfi-
                                   forwardin
very long chain pointer: "with the g-
Address Extension Mode subfield resolution
in the Mesh Control field"         s.doc
changes implemented in doc 11-    https://me
                                  ntor.ieee.
11/229.
                                  org/802.1
field is no a subfield. Did not   1/dcn/11/
include Mesh Flags field in order 11-11-          Closed   20110210 #63 I
                                  0229-02-
to avoid very long chain pointer:
                                  000s-rfi-
"Address Extension Mode subfield forwardin
in the Mesh Control field"        g-

                                   https://me
                                   ntor.ieee.
                                   org/802.1
added all the information          1/dcn/11/
contained in the suggested text in 11-11-
                                   0229-02-       Closed   20110210 #63 I
different places throughout 9.22. 000s-rfi-
Implemented in doc 11-11/229       forwardin
                                   g-
                                   resolution
                                   s.doc


The point is well taken. However,
there is no description how many
group addressed frames can be
buffered, how long they may be
buffered, and which protective                    Closed   20110210 #66 I
mechanism is to be used when
multiple (naturally
unacknowledged) group
addressed frames are transmitted
in a burst.
                                    https://me
                                    ntor.ieee.
                                    org/802.1
                                    1/dcn/11/
Submission 802.11-11/0220r2         11-11-
provides resolutions to this        0220-02-      Closed   20110210 #60 I
comment.                            000s-m-
                                    bs-
                                    comment-
                                    resolution-
                                    text.doc
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
See submission 11-11-0162-00-   11/11-11-
                                             Closed   20110120 #42 I
000s for resolution.            0163-01-
                                000s-xls-
                                to-frame-
                                format-
                                comment
                                https://m
                                entor.iee
                                e.org/80
                                2.11/dcn/
                                11/11-11-
See resolution to CID 1283.                  Closed   20110120 #42 I
                                0163-01-
                                000s-xls-
                                to-frame-
                                format-
                                comment

The clause in mention was
reviewed and the task group
                                             Closed   20110210 #67 I
invites more review from the
commenter.




                                             Closed   20110210 #66 I




                                https://me
                                ntor.ieee.
                                org/802.1
                                1/dcn/11/
                                11-11-       Closed   20110120 #43 I
                                0128-01-
                                000s-m-
                                pm-
                                comment-
                                       https://me
                                       ntor.ieee.
                                       org/802.1
                                       1/dcn/11/
                                       11-11-       Closed   20110120 #43 I
                                       0128-01-
                                       000s-m-
                                       pm-
                                       comment-
                                       https://me
                                       ntor.ieee.
                                       org/802.1
                                       1/dcn/11/
                                       11-11-       Closed   20110120 #43 I
                                       0128-01-
                                       000s-m-
                                       pm-
                                       comment-
                                                    Closed   20110120 #47 I




                                       https://m
                                       entor.iee
                                       e.org/80
                                       2.11/dcn/
Replace "," with "." in "[…] is used
                                       11/11-11-
as an emergency indicator, A                        Closed   20110120 #45 I
                                       0187-00-
mesh STA […]"
                                       000s-es-
                                       comment-
                                       resolutio
                                       n.xls
                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
Add to the end of page 190.           11/11-11-   Closed   20110120 #45 I
                                      0187-00-
                                      000s-es-
                                      comment-
                                      resolutio
                                      n.xls
                                      https://m
Change the first two sentences of
                                      entor.iee
paragraph 4 as follows: "When an
                                      e.org/80
ES association is used, an
                                      2.11/dcn/
infrastructure BSS or an MBSS
                                      11/11-11-   Closed   20110120 #45 I
should be designed to restrict
                                      0187-00-
access to ES only (or alternatively
                                      000s-es-
prioritise the ES to the highest
                                      comment-
level of access.)"
                                      resolutio
                                      n.xls



                                      https://m
                                      entor.iee
                                      e.org/80
                                      2.11/dcn/
                                      11/11-11-
                                                  Closed   20110120 #45 I
                                      0187-00-
                                      000s-es-
                                      comment-
                                      resolutio
                                      n.xls
             Edited
Edit Notes
             in Draft




             NC
 8.01




NC
The resolution is amended
                            8.03
on Feb 10.




                            8.01




                            8.01
 8.01




 8.01




NC
NC




 8.01
8.01
8.01




8.01
 8.01




 8.01




NC
8.01




8.01
 8.01




NC




 8.01
 8.01




NC
                           NC




done throughout the text    8.01




done throughout the text    8.01




                            8.01
                            8.01

                            8.01



                            8.01




                           NC




                            8.01




                            8.01



done throughout the text    8.01



                            8.01

                            8.01

                            8.01
8.01




8.01




8.01




8.01
8.01




8.01




8.03




8.03
8.03




8.03




8.01




8.01
 8.01




 8.01




NC




NC
 8.01




NC




 8.01




NC




NC




 8.01
8.01




8.01

8.01


8.01


8.01

8.01




8.01




8.01



8.01



8.01


8.01
                               8.01




                               8.01




                               8.01




Conflicts with the
resolution to CID79. Do not
open the closed issue         NC
again. The comment
should be rejected.




                               8.01



The text is changed per
                               8.01
other resolution
NC


 8.01




NC




 8.01
 8.03




NC




 8.01
8.03




8.03
                         8.03




changes in item d) are
                         8.03
implemented by editor
changes in item d) are
                         8.03
implemented by editor




                         8.01
8.03
changes in item d) are
                         8.03
implemented by editor




changes in item d) are
                         8.03
implemented by editor
                         8.01




changes in item d) are
                         8.03
implemented by editor
changes in item d) are
                         8.03
implemented by editor




changes in item d) are
                         8.03
implemented by editor
                         8.01




changes in item d) are
                         8.03
implemented by editor




                         8.01
8.01




8.01




8.01
8.01




8.01




8.01
8.03




8.01
8.03




8.01




8.01
NC




 8.03




 8.01




 8.01




 8.01
 8.01




 8.01




 8.01




NC
8.01




8.01




8.01
8.01




8.01




8.01




8.01
8.01




8.01




8.01




8.01
NC




 8.01




 8.01




 8.01
 8.01




NC




 8.01




 8.01
8.01




8.01
8.01




8.01




8.01




8.01
8.01




8.01




8.01




8.01
8.01




8.01




8.01




8.01
 8.01




NC




 8.01
NC




 8.01




 8.01
8.01




8.01




8.01




8.01
NC




 8.01




 8.01




 8.01
NC




 8.01




NC




 8.01
 8.01




 8.01




NC




NC
 8.01




 8.01




NC
 8.01




 8.01




NC




NC
NC




 8.01




NC
NC




 8.01




NC




 8.01
NC




NC




NC




NC
 8.01




NC




NC




 8.01
8.01




8.01




8.03




8.03
8.01




8.01




8.03




8.01
8.01




8.01




8.03




8.01
 8.01




 8.01




NC
8.01




8.01
8.01




8.01




8.01
8.01




8.01




8.01
NC




 8.01




 8.01




 8.01
8.01




8.01




8.01




8.01
8.01




8.01
 8.01




NC
NC




 8.01




 8.01
 8.01




NC
8.01




8.01




8.01
8.01




8.01




8.01




8.01
8.01




8.01




8.01




8.01




8.01
NC




 8.01
 8.01




NC




 8.03




 8.01
NC




NC




NC
NC




NC




NC
In submission 11-11/100,
peerMAC is missing in
some of the argument of
the primitive, although
                            8.01
peerMAC presents in the
table. Argument peerMAC
is added to resolve this
inconsistency.




                            8.01




                           NC
NC




NC




NC




 8.01
 8.01




NC
8.01




8.01




8.01




8.03
NC




 8.01




 8.01




 8.03
 8.01




NC




 8.01




NC
8.01




8.01




8.01




8.03
 8.03




 8.01




NC




 8.01
8.01




8.01




8.01




8.01
 8.01




 8.01




NC




 8.01




 8.01
8.01




8.01




8.01




8.01




8.01
8.01




8.01




8.01




8.01
8.01




8.01




8.01




8.01
 8.03




NC




 8.03
8.03




8.03




8.03
 8.01




NC




 8.03
 8.01




NC




 8.01




 8.01
8.01




8.03




8.03




8.03




8.03
8.03




8.03




8.03




8.03
 8.03




NC




 8.03




NC
8.03
8.03
8.03




8.03




8.03
 8.03




 8.03




NC




 8.03
8.03




8.03




8.03




8.03
 8.03




 8.03




NC




 8.03
 8.01




 8.01




NC




 8.03




 8.01
8.01




8.01




8.01




8.01
8.01




8.01




8.01
                Must   Categor Subclaus Pag                    Issue
CID Name                                          Line Topic
                Be     y         e          e                  ID




      Strutt,                    11C.4.3.               Securi S-
  1             No     General              194    62
      Guenael                    4.1                    ty     MPM




      Strutt,                    11C.4.3.               Securi S-
  2             No     General              194    45
      Guenael                    3.2                    ty     MPM




      Strutt,                    11C.4.3.               Securi S-
  3             No     General              194    35
      Guenael                    3.2                    ty     MPM




      Strutt,                    11C.4.3.               Securi S-
  4             No     General              194    29
      Guenael                    3.2                    ty     MPM




      Strutt,                    11C.3.2.               Securi S-
  5             No     General              190    43
      Guenael                    2                      ty     MPM
     Strutt,                   11C.4.3.              Securi S-
6              No    General              194   21
     Guenael                   3.1                   ty       MPM




     Strutt,                                         Securi
7              No    General 11C.4                            S-Edit
     Guenael                                         ty




     Bahr,           Technic                         Gener
8              Yes             W.4        309    8            G-PH
     Michael         al                              al




     Bahr,           Technic                         Gener
9              Yes             8.1.6      81     7            G-PH
     Michael         al                              al




     Bahr,           Technic                         Gener
10             Yes             7.3.2.90   39    44            G-PH
     Michael         al                              al
     Bahr,           Technic 5.2.13.5.                Gener
11             Yes                         12    28           G-PH
     Michael         al        12                     al




     Bahr,           Technic                          Gener
12             No              10.3.35     133   18           G-PH
     Michael         al                               al




     Bahr,           Technic                          Gener
13             No              10.3.15     130   40           G-PH
     Michael         al                               al




     Bahr,           Technic                          Gener
14             No              7.4.7.6     65    27           G-PH
     Michael         al                               al




     Bahr,           Technic                          Gener
15             No              7.3.2.101   47     1           G-PH
     Michael         al                               al




     Bahr,           Technic                          Gener
16             No              7.3.2.53    38    51           G-PH
     Michael         al                               al
     Bahr,                                           Gener G-
17             No    Editorial 7.3.2.20a   37   45
     Michael                                         al      Editor




     Bahr,           Technic                         Gener
18             No              7.3.2.20a   37   45           G-PH
     Michael         al                              al




     Bahr,           Technic                         Gener
19             No              7.3.2.20    37   18           G-PH
     Michael         al                              al




                                                             G-
     Bahr,           Technic                         Gener
20             Yes             7.3.4.3     64   26           Emerg
     Michael         al                              al
                                                             ency
     Bahr,           Technic                         Gener
21             No              5.2.9       7    43           G-PH
     Michael         al                              al




     Bahr,           Technic                         Gener
22             No              D          279    1           G-PH
     Michael         al                              al

     Bahr,           Technic                         Gener
23             No              A          271    1           G-PH
     Michael         al                              al




     Bahr,           Technic                         Gener
24             Yes             11C.13     262   51           G-PH
     Michael         al                              al




     Bahr,           Technic                         Gener
25             Yes             11C.12.4   258   14           G-PH
     Michael         al                              al
     Bahr,           Technic
26             Yes             11C.12.4   258   14 MAC       M-BS
     Michael         al




     Bahr,           Technic                         Gener
27             Yes             11C.12     255   32           G-PH
     Michael         al                              al




     Bahr,           Technic
28             Yes             11C.11     254   51 MAC       M-CC
     Michael         al




     Bahr,           Technic                                 R-
29             Yes             11C.10.3   250   50 RFI
     Michael         al                                      Proxy
                                                             R-
     Bahr,           Technic
30             Yes             11C.10.2   248   51 RFI       Mesh
     Michael         al
                                                             Gate




                                                             R-
     Bahr,           Technic
31             Yes             11C.10.2   248   51 RFI       Mesh
     Michael         al
                                                             Gate




                                                             R-
     Bahr,           Technic
32             Yes             11C.10.1   248   28 RFI       Mesh
     Michael         al
                                                             Gate




     Bahr,           Technic                         Gener
33             No              11C.9      217    4           G-PH
     Michael         al                              al




     Bahr,           Technic                         Gener
34             No              11C.7      214   58           G-PH
     Michael         al                              al
     Bahr,          Technic                      Gener
35             No             11C.5   203    1           G-PH
     Michael        al                           al




     Bahr,          Technic                      Gener
36             No             11C.4   191    1           G-PH
     Michael        al                           al




     Bahr,          Technic                      Gener
37             No             11C.3   188    6           G-PH
     Michael        al                           al




                                                         G-
     Bahr,          Technic                      Gener
38             No             11C.2   185   24           Discov
     Michael        al                           al
                                                         ery
     Bahr,           Technic
39             Yes               11C.1    185    15 MAC       M-CS
     Michael         al




     Bahr,           Technic                          Gener
40             Yes                  11.23 182     5           G-PH
     Michael         al                               al




     Bahr,                                            Gener G-
41             No    Editorial      11.19 181    48
     Michael                                          al      Editor



     Bahr,                                            Gener G-
42             No    Editorial 11.9a      180    54
     Michael                                          al      Editor




     Bahr,           Technic                          Gener
43             No                11.9a.3.3 181    7           G-PH
     Michael         al                               al




     Bahr,           Technic                          Gener
44             No                11.9.7.2a 178   59           G-PH
     Michael         al                               al
     Bahr,           Technic                           Gener
45             Yes                    10.3 126     5           G-PH
     Michael         al                                al




     Bahr,           Technic                                   R-
46             Yes                    9.22 118    24 RFI
     Michael         al                                        FWD




     Bahr,           Technic                                   M-
47             Yes             9.9a         108   44 MAC
     Michael         al                                        MCCA




     Bahr,           Technic                           Gener
48             Yes                    7.4   64    34           G-PH
     Michael         al                                al
     Bahr,           Technic                            Gener
49             Yes               7.3.2       35     1           G-PH
     Michael         al                                 al




     Bahr,           Technic                            Gener
50             No                7.3.1       31     1           G-PH
     Michael         al                                 al




     Bahr,           Technic                                    M-
51             Yes               9.9a.3.8    113   36 MAC
     Michael         al                                         MCCA




     Bahr,           Technic                                    M-
52             Yes               7.4.15.10   76    46 MAC
     Michael         al                                         MCCA




     Bahr,           Technic                                    M-
53             Yes               7.3.2.106   52     5 MAC
     Michael         al                                         MCCA




     Bahr,                       9.22.2.3.                      R-
54             Yes   Editorial               123   32 RFI
     Michael                     2                              FWD
     Bahr,           Technic 9.22.2.3.                      R-
55             No                            123   31 RFI
     Michael         al          2                          FWD




     Bahr,           Technic 9.22.2.3.                      R-
56             No                            123   31 RFI
     Michael         al          2                          FWD




     Bahr,           Technic 9.22.2.3.                      R-
57             Yes                           123   25 RFI
     Michael         al          2                          FWD




     Bahr,                       9.22.2.3.                  R-
58             No    Editorial               123   19 RFI
     Michael                     2                          FWD




     Bahr,                       9.22.2.2.                  R-
59             No    Editorial               121    7 RFI
     Michael                     1                          FWD




     Bahr,           Technic 9.22.2.3.                      R-
60             Yes                           122   62 RFI
     Michael         al          1                          FWD
     Bahr,           Technic 9.22.2.3.                      R-
61             Yes                           122   38 RFI
     Michael         al          1                          FWD




     Bahr,                       9.22.2.2.                  R-
62             Yes   Editorial               122    1 RFI
     Michael                     2                          FWD




     Bahr,           Technic 9.22.2.2.                      R-
63             Yes                           121   45 RFI
     Michael         al          2                          FWD




     Bahr,           Technic 9.22.2.2.                      R-
64             Yes                           121   58 RFI
     Michael         al          2                          FWD
     Bahr,           Technic 9.22.2.2.                   R-
65             Yes                        121   37 RFI
     Michael         al        2                         FWD




     Bahr,           Technic 9.22.2.2.                   R-
66             Yes                        121   32 RFI
     Michael         al        2                         FWD




     Bahr,           Technic                             R-
67             Yes             9.22.2.1   119   61 RFI
     Michael         al                                  FWD




     Bahr,           Technic                             R-
68             Yes             9.22.2.1   119   34 RFI
     Michael         al                                  FWD




     Bahr,           Technic                             R-
69             Yes             9.22.2.1   118   62 RFI
     Michael         al                                  FWD




     Bahr,           Technic                             R-
70             No              9.22.2.1   118   65 RFI
     Michael         al                                  FWD




     Bahr,           Technic                             R-
71             Yes             9.22.2.1   118   64 RFI
     Michael         al                                  FWD
     Bahr,                                               R-
72             No    Editorial 9.22.2.1   118   59 RFI
     Michael                                             FWD




     Bahr,                                               R-
73             Yes   Editorial 9.22.2.1   118   58 RFI
     Michael                                             FWD




     Bahr,           Technic                             R-
74             Yes             9.22.2.1   118   57 RFI
     Michael         al                                  FWD


     Bahr,           Technic                             R-
75             Yes             9.22.2.1   118   51 RFI
     Michael         al                                  FWD


     Bahr,           Technic                             R-
76             Yes             9.22.2.1   118   49 RFI
     Michael         al                                  FWD
     Bahr,           Technic                              R-
77             Yes             9.22.1     118   29 RFI
     Michael         al                                   FWD




     Bahr,           Technic                         Gener G-
78             Yes             7.4.16.2   79    23
     Michael         al                              al   Frame




     Bahr,           Technic                              R-
79             Yes             7.4.16.2   78    62 RFI
     Michael         al                                   Proxy




     Bahr,                                           Gener G-
80             No    Editorial 7.4.16.1   78    57
     Michael                                         al   Editor




     Bahr,           Technic                              R-
81             Yes             7.4.15.4   73    51 RFI
     Michael         al                                   HWMP




     Bahr,           Technic
82             No              7.4.15.2   72    58 RFI    R-LM
     Michael         al
     Bahr,                                           Gener G-
83             No    Editorial 7.3.1.11    33   13
     Michael                                         al   Editor




     Bahr,           Technic                              R-
84             Yes             7.3.2.110   56   32 RFI
     Michael         al                                   HWMP




     Bahr,           Technic
85             Yes             7.3.2.99    46   10 MAC    M-CC
     Michael         al
     Bahr,           Technic                             R-
86             Yes             7.3.2.112   60   58 RFI
     Michael         al                                  HWMP




     Bahr,           Technic                             R-
87             No              7.3.2.110   58   26 RFI
     Michael         al                                  HWMP




     Bahr,                                               R-
88             No    Editorial 7.3.2.110   57   39 RFI
     Michael                                             HWMP




                                                         R-
     Bahr,           Technic
89             Yes             7.3.2.108   54   46 RFI   Mesh
     Michael         al
                                                         Gate




                                                         R-
     Bahr,           Technic
90             Yes             7.3.2.108   54   42 RFI   Mesh
     Michael         al
                                                         Gate
     Bahr,           Technic
91             Yes             7.3.1.7   32   12 MAC   M-CS
     Michael         al
     Bahr,           Technic
92             Yes             7.3.1.7   32   10 MAC     M-CS
     Michael         al




     Bahr,           Technic                             R-
93             Yes             7.3.1.7   31   58 RFI
     Michael         al                                  HWMP




     Bahr,           Technic                       Securi S-
94             Yes             7.3.1.7   31   35
     Michael         al                            ty    MPM
     Bahr,           Technic                           Securi S-
95             Yes               7.3.1.7    31    52
     Michael         al                                ty    MPM




     Bahr,                       11C.4.4.              Securi S-
96             No    Editorial              200   19
     Michael                     5                     ty    MPM




     Bahr,                                             Gener G-
97             No    Editorial 7.3.1.7      31    58
     Michael                                           al    Editor




     Bahr,           Technic
98             Yes               7.2.3.9    28    64 MAC     M-QoS
     Michael         al
     Bahr,           Technic
99             Yes             7.2.3.1   27   25 MAC   M-QoS
     Michael         al
      Bahr,           Technic
100             Yes             7.2.3.1    27   21 MAC    M-QoS
      Michael         al




      Bahr,                                          Gener G-
101             No    Editorial 7.2.3.0a   26   17
      Michael                                        al   Editor

      Bahr,                                          Gener G-
102             No    Editorial 7.2.3.0a   26   17
      Michael                                        al   Editor

      Bahr,                                          Gener G-
103             No    Editorial 7.2.3.0a   25   55
      Michael                                        al   Editor

      Bahr,                                          Gener G-
104             No    Editorial 7.2.3.0a   26    5
      Michael                                        al   Editor

      Bahr,                                          Gener G-
105             No    Editorial 7.2.3.0a   26    4
      Michael                                        al   Editor

      Bahr,                                          Gener G-
106             No    Editorial 7.2.2.2    25   20
      Michael                                        al   Editor
      Bahr,           Technic                         Gener G-
107             Yes             7.2.2.1     24   55
      Michael         al                              al   Frame


      Bahr,                                           Gener G-
108             No    Editorial 7.2.2.1     24   54
      Michael                                         al   Editor

      Bahr,                                           Gener G-
109             No    Editorial 7.2.1.4     23   51
      Michael                                         al   Editor

      Bahr,                                           Gener G-
110             No    Editorial 7.1.3.6.3   23   31
      Michael                                         al   Editor

      Bahr,           Technic                         Gener G-
111             No              7.1.3.6.3   23    8
      Michael         al                              al   Frame




      Bahr,                                           Gener G-
112             No    Editorial 7.1.3.6.3   21   57
      Michael                                         al   Frame




      Bahr,                                           Gener G-
113             No    Editorial 7.1.3.6.3   22   28
      Michael                                         al   Editor

      Bahr,           Technic                         Gener G-
114             No              7.1.3.6.3   21   62
      Michael         al                              al   Frame


      Bahr,                                           Gener G-
115             No    Editorial 7.1.3.6.3   21   56
      Michael                                         al   Editor


      Bahr,           Technic                         Gener G-
116             No              7.1.3.6.3   21   53
      Michael         al                              al   Editor


      Bahr,           Technic                         Gener G-
117             Yes             7.1.3.6.3   21   49
      Michael         al                              al   Frame
      Bahr,           Technic                           Gener G-
118             Yes               7.1.3.6.3   21   43
      Michael         al                                al   Frame




      Bahr,           Technic                           Gener G-
119             Yes               7.1.3.6.3   21   40
      Michael         al                                al   Frame




      Bahr,           Technic                           Gener G-
120             Yes               7.1.3.6.3   21   37
      Michael         al                                al   Frame




      Bahr,           Technic                           Gener G-
121             Yes               7.1.3.6.2   21   28
      Michael         al                                al   Frame


      Bahr,                       7.1.3.5.1             Gener G-
122             No    Editorial               21    1
      Michael                     1                     al   Editor

      Bahr,                       7.1.3.5.1             Gener G-
123             No    Editorial               20   64
      Michael                     1                     al   Editor

      Bahr,                                             Gener G-
124             No    Editorial 7.1.3.5.9     20   48
      Michael                                           al   Editor




      Bahr,           Technic 7.1.3.5.0
125             No                            18   15 MAC    M-QoS
      Michael         al          a
      Bahr,           Technic                         Gener G-
126             No              7.1.3.1.7   17   65
      Michael         al                              al   Frame




      Bahr,           Technic
127             Yes             7.1.3.1.6   17   49 MAC    M-PM
      Michael         al
      Bahr,           Technic                           Gener G-
128             Yes             7.1.2
      Michael         al                                al       Frame




      Bahr,           Technic                           Gener G-
129             No                      5.6
      Michael         al                                al       Base




                                                                 S-
      Bahr,           Technic                           Securi
130             Yes             5.4.3.2       13   54            Gener
      Michael         al                                ty
                                                                 al
                                                                 S-
      Bahr,           Technic                           Securi
131             Yes               5.4.3.1     13    1            Gener
      Michael         al                                ty
                                                                 al




                                                                 G-
      Bahr,           Technic 5.2.13.5.                 Gener
132             Yes                           12   34            Emerg
      Michael         al          12                    al
                                                                 ency




                                                                 R-
      Bahr,           Technic 5.2.13.5.
133             Yes                           11   53 RFI        Mesh
      Michael         al          10
                                                                 Gate




                                                                 R-
      Bahr,           Technic 5.2.13.5.
134             Yes                           11   50 RFI        Mesh
      Michael         al          10
                                                                 Gate




      Bahr,                       5.2.13.5.             Gener G-
135             No    Editorial               11   50
      Michael                     10                    al       Editor
      Bahr,           Technic 5.2.13.5.
136             Yes                           11   33 RFI       R-LM
      Michael         al          9




      Bahr,           Technic                           Gener G-
137             Yes               5.2.13.3    8    31
      Michael         al                                al      Base




      Bahr,                                             Gener G-
138             No    Editorial 5.2.13.2      8    23
      Michael                                           al      Editor


      Bahr,                                             Gener G-
139             No    Editorial         3.3   5    35
      Michael                                           al      Editor




      Bahr,           Technic
140             Yes                     3.1   3    62 MAC       M-PM
      Michael         al




      Bahr,           Technic                           Gener
141             Yes                     3.1   3    24           G-Def
      Michael         al                                al
      Bahr,           Technic                           Gener
142             Yes                    3.1    3    15           G-Def
      Michael         al                                al




      Bahr,           Technic 11C.12.4                          M-
143             Yes                          260   64 MAC
      Michael         al          .3                            MCCA




      Bahr,           Technic                                   M-
144             Yes                    3.2    5    21 MAC
      Michael         al                                        MCCA




      Bahr,                                             Gener G-
145             No    Editorial        3.2    5    26
      Michael                                           al      Editor




      Bahr,           Technic                           Gener G-
146             Yes                    3.2    5    11
      Michael         al                                al      Editor
      Bahr,           Technic                         R-
147             Yes               3.1   4   51 RFI
      Michael         al                              FWD




      Bahr,
148             No    Editorial   3.1   3   60 MAC    M-PM
      Michael




      Bahr,           Technic
149             Yes               3.1   4   45 MAC    M-PM
      Michael         al




      Bahr,                                      Gener G-
150             No    Editorial   3.1   4   33
      Michael                                    al   Editor

      Bahr,                                      Gener G-
151             No    Editorial   3.1   4    6
      Michael                                    al   Editor




      Bahr,           Technic
152             No                3.1   4    5 MAC    M-PM
      Michael         al
      Bahr,           Technic                    Gener
153             Yes               3.1   3   49           G-Def
      Michael         al                         al




      Bahr,
154             No    Editorial   3.1   3   18 MAC       M-PM
      Michael




      Bahr,           Technic                    Gener
155             Yes               3.1   2   39           G-Def
      Michael         al                         al
                                                                  G-
      Bahr,                                              Gener
156             Yes   General                  4    36            Gener
      Michael                                            al
                                                                  al




      Strutt,                     10.3.79.3              Gener G-
157             No    Editorial               163   33
      Guenael                     .4                     al       Editor




                                                                  S-
      Strutt,                                            Securi
158             No    General 8.2a.8.1        91    37            Gener
      Guenael                                            ty
                                                                  al




      Strutt,                                            Securi S-
159             No    Editorial 11C.4.1       191   21
      Guenael                                            ty       MPM
                                                           G-
      Hiertz,                                      Gener
160             No   Editorial                             Gener
      Guido                                        al
                                                           al




      Hiertz,                    9.9a.3.10                 M-
161             No   Editorial               115   MAC
      Guido                      .2                        MCCA




      Hiertz,                    9.9a.3.10                 M-
162             No   Editorial               115   MAC
      Guido                      .2                        MCCA




      Hiertz,                    9.9a.3.10                 M-
163             No   Editorial               115   MAC
      Guido                      .2                        MCCA




      Hiertz,                    9.9a.3.10                 M-
164             No   Editorial               115   MAC
      Guido                      .2                        MCCA




      Hiertz,                    9.9a.3.10                 M-
165             No   Editorial               115   MAC
      Guido                      .2                        MCCA
      Hiertz,                                         M-
166             No   Editorial 9.9a.3.8   113   MAC
      Guido                                           MCCA




      Hiertz,                                         M-
167             No   Editorial 9.9a.3.8   113   MAC
      Guido                                           MCCA




      Hiertz,        Technic                          M-
168             No             9.9a.3.7   113   MAC
      Guido          al                               MCCA




      Hiertz,        Technic                          M-
169             No             9.9a.3.7   113   MAC
      Guido          al                               MCCA
      Hiertz,        Technic                          M-
170             No             9.9a.3.7   113   MAC
      Guido          al                               MCCA




      Hiertz,        Technic                          M-
171             No             9.9a.3.7   113   MAC
      Guido          al                               MCCA




      Hiertz,        Technic                          M-
172             No             9.9a.3.7   113   MAC
      Guido          al                               MCCA




      Hiertz,        Technic                          M-
173             No             9.9a.3.7   112   MAC
      Guido          al                               MCCA




      Hiertz,        Technic                          M-
174             No             9.9a.3.7   113   MAC
      Guido          al                               MCCA
      Hiertz,        Technic                          M-
175             No             9.9a.3.7   112   MAC
      Guido          al                               MCCA




      Hiertz,        Technic                          M-
176             No             9.9a.3.7   112   MAC
      Guido          al                               MCCA




      Hiertz,        Technic                          M-
177             No             9.9a.3.6   112   MAC
      Guido          al                               MCCA
      Hiertz,                                         M-
178             No   Editorial 9.9a.3.5   111   MAC
      Guido                                           MCCA




      Hiertz,                                         M-
179             No   Editorial 9.9a.3.5   111   MAC
      Guido                                           MCCA




      Hiertz,        Technic                          M-
180             No             9.9a.3.3   110   MAC
      Guido          al                               MCCA




      Hiertz,        Technic                          M-
181             No             9.1.3.0a   107   MAC
      Guido          al                               MCCA
      Hiertz,        Technic 9.9a.3.11                          M-
182             No                           115        MAC
      Guido          al          .1                             MCCA




      Hiertz,        Technic                            Gener
183             No                     3.1    4    17           G-Def
      Guido          al                                 al




      Hiertz,                                           Gener
184             No   Editorial         3.1    3    38           G-Def
      Guido                                             al




      Hiertz,                                           Gener
185             No   Editorial         3.1    3    19           G-Def
      Guido                                             al



      Hiertz,                                           Gener
186             No   Editorial         3.1    2    52           G-Def
      Guido                                             al




      Hiertz,        Technic                                    M-
187             No               9.9a.3.1    109        MAC
      Guido          al                                         MCCA
      Strutt,                                                R-
188             No   General 7.3.2.110    58    15 RFI
      Guenael                                                HWMP




      Strutt,        Technic 10.3.78.1                       M-
189             No                        150   54 MAC
      Guenael        al        .2                            MCCA




      Strutt,        Technic 10.3.78.1                       M-
190             No                        150   51 MAC
      Guenael        al        .2                            MCCA




      Zuniga,        Technic                                 R-
191             No                  9.22 118    22 RFI
      Juan           al                                      FWD




                                                             G-
      Zuniga,                                        Gener
192             No   General          1    1     1           Gener
      Juan                                           al
                                                             al
      Montemur                                                G-
                       Technic                        Gener
193 ro,          Yes             11.23.6   182   55           Emerg
                       al                             al
      Michael                                                 ency




      Turner,          Technic                        Gener G-
194              Yes                       108   44
      Michelle         al                             al      Editor




      Sakoda,                                                 R-
195              No    Editorial Y.6       314   29 RFI
      Kazuyuki                                                HWMP




      Sakoda,                                         Gener G-
196              No    Editorial Y.3       310   52
      Kazuyuki                                        al      Editor


      Sakoda,                                         Gener G-
197              No    Editorial Y.1       310   11
      Kazuyuki                                        al      Frame


      Sakoda,                                         Gener G-
198              No    Editorial A.4.23    274   59
      Kazuyuki                                        al      Editor


      Sakoda,                                         Gener G-
199              No    Editorial A.4.4.1   272   43
      Kazuyuki                                        al      Editor


      Sakoda,                                         Gener G-
200              No    Editorial A.4.3     272   24
      Kazuyuki                                        al      Editor
      Sakoda,                                           Gener G-
201              No   Editorial 11C.13.1     263    1
      Kazuyuki                                          al   Editor


      Sakoda,         Technic 11C.12.4                  Gener G-
202              No                          260   64
      Kazuyuki        al          .3                    al   Editor



      Sakoda,                                           Gener G-
203              No   Editorial 11C.12       255   32
      Kazuyuki                                          al   Editor




      Sakoda,
204              No   Editorial 11C.11.2     255    1 MAC    M-CC
      Kazuyuki




      Sakoda,
205              No   Editorial 11C.11.1     254   60 MAC    M-CC
      Kazuyuki




      Sakoda,                     11C.10.4                   R-
206              No   Editorial              252   48 RFI
      Kazuyuki                    .3.2                       Proxy
      Sakoda,                     11C.10.4                  R-
207              No   Editorial              252   38 RFI
      Kazuyuki                    .3                        Proxy




      Sakoda,                     11C.10.4                  R-
208              No   Editorial              252   21 RFI
      Kazuyuki                    .1                        Proxy




                                                            R-
      Sakoda,                     11C.10.3
209              No   Editorial              251   25 RFI   Mesh
      Kazuyuki                    .3
                                                            Gate




                                                            R-
      Sakoda,         Technic 11C.10.3
210              No                          251   20 RFI   Mesh
      Kazuyuki        al          .2
                                                            Gate




                                                            R-
      Sakoda,                     11C.10.3
211              No   Editorial              251    1 RFI   Mesh
      Kazuyuki                    .2
                                                            Gate
                                                            R-
      Sakoda,
212              No   Editorial 11C.10.3     250   50 RFI   Mesh
      Kazuyuki
                                                            Gate




                                                            R-
      Sakoda,                     11C.10.2
213              No   Editorial              250   43 RFI   Mesh
      Kazuyuki                    .4.3
                                                            Gate




                                                            R-
      Sakoda,         Technic 11C.10.2
214              No                          250   33 RFI   Mesh
      Kazuyuki        al          .4.2
                                                            Gate




                                                            R-
      Sakoda,                     10C.10.2
215              No   Editorial              249   48 RFI   Mesh
      Kazuyuki                    .3
                                                            Gate




                                                            R-
      Sakoda,                     10C.10.2
216              No   Editorial              249   38 RFI   Mesh
      Kazuyuki                    .3
                                                            Gate
                                                            R-
      Sakoda,                     10C.10.2
217              No   Editorial              249   10 RFI   Mesh
      Kazuyuki                    .3
                                                            Gate




                                                            R-
      Sakoda,         Technic 10C.10.2
218              No                          249    3 RFI   Mesh
      Kazuyuki        al          .3
                                                            Gate




      Sakoda,                                               R-
219              No   Editorial 11C.10.1     248   50 RFI
      Kazuyuki                                              Proxy




                                                            R-
      Sakoda,
220              No   Editorial 11C.10.1     248   46 RFI   Mesh
      Kazuyuki
                                                            Gate




                                                            R-
      Sakoda,
221              No   Editorial 11C.10.1     248   46 RFI   Mesh
      Kazuyuki
                                                            Gate
                                                           R-
      Sakoda,
222              No   Editorial 11C.10.1   248   35 RFI    Mesh
      Kazuyuki
                                                           Gate




                                                           R-
      Sakoda,
223              No   Editorial 11C.10.1   248   21 RFI    Mesh
      Kazuyuki
                                                           Gate




      Sakoda,                                              R-
224              No   Editorial 11C.9.2    219   38 RFI
      Kazuyuki                                             HWMP




      Sakoda,                                              R-
225              No   Editorial 11C.9.2    217   57 RFI
      Kazuyuki                                             HWMP




      Sakoda,                                         Gener G-
226              No   Editorial 11C.9      217    4
      Kazuyuki                                        al   Editor
      Sakoda,                                           Gener G-
227              No   Editorial 11C.8        216   48
      Kazuyuki                                          al       Editor


      Sakoda,                                           Gener G-
228              No   Editorial 11C.8        215   60
      Kazuyuki                                          al       Editor


      Sakoda,                                           Gener G-
229              No   Editorial 11C.7.3      215   48
      Kazuyuki                                          al       Editor



      Sakoda,                                           Gener G-
230              No   Editorial 11C.7.2      215   21
      Kazuyuki                                          al       Editor




                                                                 S-
      Sakoda,                                           Securi
231              No   Editorial 11C.5.1      203   16            Gener
      Kazuyuki                                          ty
                                                                 al




      Sakoda,                                           Gener G-
232              No   Editorial 11C.4.4      195   11
      Kazuyuki                                          al       Editor




      Sakoda,                     11C.3.2.              Gener G-
233              No   Editorial              190   63
      Kazuyuki                    3                     al       Editor
      Sakoda,                     11C.3.2.               Gener G-
234              No   Editorial               190   52
      Kazuyuki                    3                      al   Editor


      Sakoda,                     11C.3.2.               Gener G-
235              No   Editorial               189   47
      Kazuyuki                    1                      al   Editor




      Sakoda,                     11.1.3.2.              Gener G-
236              No   Editorial               177   28
      Kazuyuki                    1                      al   Editor




      Sakoda,         Technic
237              No               10.3.82     169   27 RFI    R-LM
      Kazuyuki        al




      Sakoda,                     10.3.78.1              Gener G-
238              No   Editorial               150   52
      Kazuyuki                    .2                     al   Editor
                                                              R-
      Sakoda,         Technic
239              No               9.22.3      125    9 RFI    Mesh
      Kazuyuki        al
                                                              Gate




      Sakoda,                     9.22.2.3.                   R-
240              No   Editorial               123   31 RFI
      Kazuyuki                    2                           FWD




      Sakoda,         Technic 9.22.2.2.                       R-
241              No                           121   41 RFI
      Kazuyuki        al          2                           FWD



      Sakoda,         Technic 9.22.2.2.                       R-
242              No                           120   27 RFI
      Kazuyuki        al          2                           FWD




      Sakoda,                                                 R-
243              No   Editorial 9.22.1        118   30 RFI
      Kazuyuki                                                FWD




      Sakoda,                                            Gener G-
244              No   Editorial 9.13.3.4a 118       15
      Kazuyuki                                           al   Editor
      Sakoda,                     9.9a.3.11                  M-
245              No   Editorial               116   2 MAC
      Kazuyuki                    .1                         MCCA




      Sakoda,         Technic                                M-
246              No               9.9a.3.7    112   63 MAC
      Kazuyuki        al                                     MCCA




      Sakoda,                                                M-
247              No   Editorial 9.9a.3.1      109   43 MAC
      Kazuyuki                                               MCCA
      Sakoda,         Technic                                  M-
248              No             9.9a.3.1   109   33 MAC
      Kazuyuki        al                                       MCCA




      Sakoda,         Technic
249              No             9.9.1.2    108   37 MAC        M-QoS
      Kazuyuki        al




      Sakoda,         Technic                         Securi
250              No             8.2a.5.5   88    40            S-SAE
      Kazuyuki        al                              ty




      Sakoda,         Technic                         Securi
251              No             8.2a.5.4   88    28            S-SAE
      Kazuyuki        al                              ty




      Sakoda,         Technic 8.2a.4.2.               Securi
252              No                        86    27            S-SAE
      Kazuyuki        al        2                     ty
      Sakoda,                     8.2a.4.1.             Securi
253              No   Editorial               85   11            S-SAE
      Kazuyuki                    2                     ty




      Sakoda,                     8.2a.4.1.             Gener G-
254              No   Editorial               84   52
      Kazuyuki                    1                     al       Editor




      Sakoda,                                           Gener G-
255              No   Editorial 7.4.14        66    7
      Kazuyuki                                          al       Editor


      Sakoda,                     7.3.2.96.             Gener G-
256              No   Editorial               42   40
      Kazuyuki                    5                     al       Editor


      Sakoda,                                           Gener G-
257              No   Editorial 7.1.3.6.3     23   38
      Kazuyuki                                          al       Editor


      Sakoda,                                           Gener G-
258              No   Editorial 7.1.3.6.3     22   35
      Kazuyuki                                          al       Editor
      Sakoda,         Technic                                    R-
259              No               7.3.2.113   62    1 RFI
      Kazuyuki        al                                         Proxy




      Sakoda,                                           Gener G-
260              No   Editorial 7.3.2.112     60   32
      Kazuyuki                                          al       Editor




      Sakoda,         Technic 7.3.2.96.                 Gener G-
261              No                           41   17
      Kazuyuki        al          2                     al       Frame




                                                                 G-
      Sakoda,         Technic 5.2.13.5.                 Gener
262              No                           12   28            Emerg
      Kazuyuki        al          12                    al
                                                                 ency




      Sakoda,                     5.2.13.5.             Gener G-
263              No   Editorial               11   29
      Kazuyuki                    9                     al       Editor



                                                                 S-
      Sakoda,         Technic 5.2.13.5.                 Securi
264              No                           10   37            Gener
      Kazuyuki        al          3                     ty
                                                                 al



      Sakoda,                                           Gener G-
265              No   Editorial 5.2.13.4      9    51
      Kazuyuki                                          al       Editor
                                                                 G-
      Sakoda,                                           Gener
266              No    General          2     2     1            Gener
      Kazuyuki                                          al
                                                                 al



                                                                 S-
      Housley,         Technic 11C.3.2.                 Securi
267              No                          189   23            Gener
      Russell          al          1                    ty
                                                                 al


      Rosdahl,                                          Gener
268              Yes   General         3.1    4    26            G-Def
      Jon                                               al




      Rosdahl,         Technic                          Gener
269              Yes                   3.1    4    33            G-Def
      Jon              al                               al




      Rosdahl,         Technic                          Gener
270              Yes                   3.1    4    42            G-Def
      Jon              al                               al




      Rosdahl,                                          Gener
271              Yes   Editorial       3.1    4    62            G-Def
      Jon                                               al
      Rosdahl,         Technic                           Gener
272              Yes                     3.1   3     1           G-Def
      Jon              al                                al




                                                         Gener G-
273 shi, yang No       Editorial 5.2.13.4      8    48
                                                         al      Base




                                   5.2.13.5.             Gener G-
274 shi, yang No       Editorial               11   17
                                   8                     al      Frame
      Odman,                                           Gener G-
275            Yes   Editorial 7.2.3.0a     25    25
      Knut                                             al   Frame




      Odman,                     11C.12.4
276            No    Editorial              258   50 MAC    M-BS
      Knut                       .2.1




      Odman,         Technic 11C.12.4
277            Yes                          262   45 MAC    M-BS
      Knut           al          .6
      Odman,         Technic 11C.12.4
278            Yes                      261   22 MAC   M-BS
      Knut           al     .4.2
      Odman,         Technic 11.1.3.2.              Gener G-
279            Yes                       177   27
      Knut           al      1                      al   Editor
      Odman,         Technic                                 R-
280            Yes             9.22.2.5   124   42 RFI
      Knut           al                                      FWD




      Odman,         Technic                         Gener
281            Yes             5.2.13.4    8    64           G-Def
      Knut           al                              al
                                  5.2.13.5.
      Seibert,        Technic
282              No               4 and       10   52 MAC        M-BS
      Cristina        al
                                  others




      Dentenee
      r,                          8.2a.8.6.             Securi
283              No   Editorial               97   58            S-SAE
      Theodoru                    2e                    ty
      s




      Dentenee
      r,              Technic 8.2a.8.6.                 Securi
284              No                           96   54            S-SAE
      Theodoru        al          2c                    ty
      s
      Dentenee
      r,              Technic 8.2a.8.6.             Securi
285              No                       96   54            S-SAE
      Theodoru        al      2c                    ty
      s




      Dentenee
      r,              Technic 8.2a.8.6.             Securi
286              No                       96   27            S-SAE
      Theodoru        al      2c                    ty
      s




      Dentenee
      r,              Technic 8.2a.8.6.             Securi
287              No                       96    2            S-SAE
      Theodoru        al      2b                    ty
      s




      Dentenee
      r,              Technic 8.2a.8.6.             Securi
288              No                       96    2            S-SAE
      Theodoru        al      2b                    ty
      s




      Dentenee
      r,              Technic 8.2a.8.6.             Securi
289              No                       95   56            S-SAE
      Theodoru        al      2b                    ty
      s
      Dentenee
      r,              Technic                        Securi
290              No             8.2a.5.5   88   43            S-SAE
      Theodoru        al                             ty
      s




      Dentenee
      r,                                             Securi
291              No   Editorial 8.2a.5.5   88   40            S-SAE
      Theodoru                                       ty
      s




      Dentenee
      r,              Technic                        Securi
292              No             8.2a.5.4   88   31            S-SAE
      Theodoru        al                             ty
      s




      Dentenee
      r,                                             Securi
293              No   Editorial 8.2a.5.4   88   28            S-SAE
      Theodoru                                       ty
      s




      Dentenee
      r,                                             Securi
294              No   Editorial 8.2a.5.2   87   56            S-SAE
      Theodoru                                       ty
      s
      Dentenee
      r,                                                   Securi
295              No   Editorial 8.2a.5.2         87   34            S-SAE
      Theodoru                                             ty
      s




      Dentenee
      r,              Technic 8.2a.5.1/                    Securi
296              No                              87   19            S-SAE
      Theodoru        al          2                        ty
      s




      Dentenee
      r,              Technic                              Securi
297              No               8.2a.5.1       87    6            S-SAE
      Theodoru        al                                   ty
      s




      Dentenee
      r,                          8.2a.4.1.                Securi
298              No   Editorial                  85   13            S-SAE
      Theodoru                    2                        ty
      s




      Methley,        Technic
299              No               5.2.6          7    31 MAC        M-QoS
      Steven          al




      Dentenee
                                                           Gener G-
300 r,       No       Editorial              1   1     1
    Theodoru                                               al       Editor
      s
      Dentenee
      r,               Technic                              Gener G-
301              No                          1    1
      Theodoru         al                                   al      Editor
      s




      Mccann,          Technic                              Securi S-
302              No                10.3.73.1 138       49
      Stephen          al                                   ty      MPM




      Mccann,                      10.3.73.1                Gener G-
303              No    Editorial                 136   63
      Stephen                      .2                       al      Editor




                                                                    G-
      Mccann,          Technic                              Gener
304              Yes               11.23.6       182   64           Emerg
      Stephen          al                                   al
                                                                    ency
                                                            G-
      Mccann,         Technic 5.2.13.5.             Gener
305             Yes                       12   35           Emerg
      Stephen         al      12                    al
                                                            ency
    Benvenist
                               7.3.2.96.
306 e,          No   General               31   45 RFI   R-LM
                               3
    Mathilde
    Benvenist                         M-
307 e,          Yes   General   MAC   Gener
    Mathilde                          al
                                                                                Resolutio
Comment                                     Proposed Change
                                                                                n Status

"which shall be set according
to the local state of localLinkID." Why
the obfuscation? Is it set to the
                                            Let us know!                        Principle
LocalLinkID? If yes, say so. If not, say
what it's set to!




"and other information from Mesh
Configuration element". "the" is            Please let me know what the other
                                                                                Principle
missing. And why do I have to guess         information is.
what the other information is?



"shall verify": what matters here is the
result of the verification. Just say what
the verification is (A==B) and the
                                            don't verify. Act!                  Principle
outcome (If TRUE, this, if false, THAT).
Saying "shall verify" does not help.
Many instances of this


"if it contains a mismatched instance
identifier" It would help if we learned
what a mismatched identifier was.           Specify!                            Principle
Matched to what?




"shall be closed properly." not helpful     Remove "properly". It's improper.   Principle
"Mesh Peering Management element
shall contain the Local Link ID field and
Peer link ID field " - Way over-            Delete                                Principle
specified. Totally redundant and
obvious.


"I have an uneasy feeling about the
normative-ness of the mesh peering
management section. "In other cases,        We need to review the clause in
the mesh STA shall" is vague -- one         such a way that normative-ness
needs to track what the previous cases becomes concentrated and non-
                                                                                  Disagree
are, can't we list them for clarity?   redundant. Fuzzy requirements
"mesh peering establishment attempt         should be described as
shall be terminated" is unnecessarily       expectations in the overview.
vague (terminating attempts?). Isn't it
the state machine instance that is
whole clause W.4: The specification of Check the specification of the
emergency services is a complex             emergency service procedures.
mechanism in a wireless mesh BSS. It Look at completeness and proper        Unresolv
is possible that it contains some flaws working and functionality in a WLAN able
and misspecifications that will have an mesh environment. Check against
impact on the functionality and the         the requirments for the emergency
proper working of a WLAN mesh BSS. services.
whole clause 8.1.6: The specification of Check the specification of the
emergency services is a complex             emergency service procedures.
mechanism in a wireless mesh BSS. It Look at completeness and proper        Unresolv
is possible that it contains some flaws working and functionality in a WLAN able
and misspecifications that will have an mesh environment. Check against
impact on the functionality and the         the requirments for the emergency
proper working of a WLAN mesh BSS. services.
whole clause 7.3.2.90: The         Check the specification of the
specification of the Internworking          Interworking element, especially in
element, especially for emergency           the context of emergency services.
                                                                                  Unresolv
services, is a complex mechanism in a Look at completeness and proper
                                                                                  able
wireless mesh BSS. It is possible that it working and functionality in a WLAN
contains some flaws and                     mesh environment. Check against
misspecifications that will have an         the requirments for the emergency
impact on the functionality and the         services.
whole clause 5.2.13.5.12: The            Check the specification of the
specification of emergency services is   emergency service procedures.
a complex mechanism in a wireless         Look at completeness and proper     Unresolv
mesh BSS. It is possible that it contains working and functionality in a WLAN able
some flaws and misspecifications that mesh environment. Check against
will have an impact on the functionality the requirments for the emergency
and the proper working of a WLAN         services.
whole clause 10.3.35: The channel        Check the definition of the channel
switching in a WLAN mesh network is      switch procedures. Look at
not so easy as in an infrastructure        completeness and proper working     Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh    able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
whole clause 10.3.15: The channel       Check the definition of the channel
switching in a WLAN mesh network is switch procedures. Look at
not so easy as in an infrastructure        completeness and proper working     Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh    able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
whole clause 7.4.7.6: The channel       Check the definition of the channel
switching in a WLAN mesh network is switch procedures. Look at
not so easy as in an infrastructure        completeness and proper working     Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh    able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
whole clause 7.3.2.101: The channel     Check the definition of the channel
switching in a WLAN mesh network is switch procedures. Look at
not so easy as in an infrastructure        completeness and proper working     Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh    able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
whole clause 7.3.2.53: The channel      Check the definition of the channel
switching in a WLAN mesh network is switch procedures. Look at
not so easy as in an infrastructure      completeness and proper working       Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh    able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
                                          Insert editorial note that states from
Where does clause 7.3.2.20a come
                                          which amendment after 11mb the           Disagree
from (which amendment)?
                                          clause 7.3.2.20a comes from.


whole clause 7.3.2.20a: The channel       Check the definition of the channel
switching in a WLAN mesh network is       switch procedures. Look at
not so easy as in an infrastructure        completeness and proper working         Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh        able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
whole clause 7.3.2.20: The channel      Check the definition of the channel
switching in a WLAN mesh network is switch procedures. Look at
not so easy as in an infrastructure        completeness and proper working         Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh        able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
The inserted text did not understand
the usage of the venue name
information and reduced the scope ot      The provision of venue name
the venue name information:             information has to be at BSS level,
- the usage is to "provide zero or more not at STA level:
venue names associated with the         - remove clause 7.3.4 from the 11s
BSS". The inserted text, however,         draft, because no changes are            Agree
wants to provide venue names              necessary. The MBSS is also an
associated with a STA. But a STA is       BSS, so it is included in the text
not a BSS, its only part of the BSS.      from 11u.
- the scope is the BSS, so for 11u this
is at least the infrastructure BSS as
well as the IBSS. The insertion of
"infrastructure " before BSS excludes
There are several clauses and
paragraphs in different places of the
11s draft D7.0, that provide adaptions
of mesh functionality to 11n (High
Throughput STAs). However, it seems Check whether the adaption of 11n
that it is likely that something has been functionality to 11s mesh   Unresolv
missed, because 11n had been an           functionality is sufficient and      able
802.11 amendment much thicker than        complete. Fill gaps if necessary.
11s. And adapting a cellular single hop
system with a central access point
(many to 1) to a peer to peer system
with multiple neighbors (1 to many)
It is still possible that the ASN.1                                            Unresolv
                                          Check for completeness.
encoding for MBSS is not complete.                                             able

It is still possible that the PICS                                             Unresolv
                                          Check for completeness.
proforma is not complete.                                                      able

The clause on power save received         Check the specification of power
some improvements during the last         save and related frame and IE
comment resolutions. However, it is still specifications and related
                                                                               Unresolv
likely that there are some errors or      informative clauses thoroughly for
                                                                               able
flaws in the specification of the power   correctness, completeness and that
save mechanisms because it is a           it works together with the other
rather complex mechanism with             mechanisms of 11s, especially
dependencies11C.12.4: A mesh
whole clause to several other             synchronization and beaconing,
                                          Check the mesh collision avoidance
beacon collision avoidance mechanism mechanism and related frame and
is a rather complex thing in a                                                 Unresolv
                                     IE specifications thoroughly for
distributed wireless mesh network, and correctness, completeness and           able
it is very likely that it still contains flaws consistency.
and inconsistencies.
whole clause 11C.12.4: The current
                                          Consider a different mechanism
procedure for changing the TBTT by
                                          than TSF adjustment for changing        Disagree
adjusting the TSF might not be a good
                                          the TBTT.
choice in a distributed mesh network.




whole clause 11C.12: The clause on        Check the clause on
synchronization and beaconing             synchronization and beaconing
changed a lot. In general, it is an       thoroughly for correctness,
improvement in the description and        completeness, and efficient working
                                                                                  Unresolv
definition. However, it is very likely that without any deadlock or wrong
                                                                                  able
there are still errors and flaws in the   results. Do these checks with all the
definition of the procedures for          mechanisms in mind that rely on
synchronization and beaconing. The        synchronization and beaconing,
correctness has to be validated with      especially with MCCA and power
other mechanisms such as MCCA and save. more flexibility of the intra-
whole clause 11C.11: Even as a simple provide
and very lean intra-mesh congestion   mesh congestion control scheme,
control mechanism, it could provide       but keep the rather lean concept of
some more flexibility for the use in      congestion control notification.
                                          Check the clause on intra-mesh          Principle
different congestion control schemes.
Furthermore, the intra-mesh               congestion control and the
congestion control specification might    corresponding frame and IE
still contain some flaws.                 definitions for completeness,
                                          correctness, and consistency.
whole clause 11C.10.3: Eventually, the
clause on the forwarding behaviour of     Check the clause on the proxy
proxies got a good distribution of        mesh gate forwarding throroughly
content between the proxy mesh gate       for correctness, completeness, and
forwarding clause and the mesh STA        consistency as well as correct
                                                                                  Disagree
forwarding clause. However, the           distribution of functionality and
change happened under time pressure, specifications between this clause
so it is rather likely that there are some and the mesh forwarding clause
flaws and inconsistencies in the text.    9.22.
Furthermore, it might be incomplete
whole clause 11C.10.2: The clause on Check the clause on the gate
the gate announcement protocol       announcement protocol thoroughly
received several changes during the                                                Unresolv
                                            for proper scope (is mesh gate too
last comment resolution. It has                                                    able
                                            broad?) and proper procedures and
improved, but it has to be checked          proper working.
whether all flaws and inconsistencies
whole clause 11C.10.2: The change
                                            re-establish the intended behaviour
from mesh portal to mesh gate, and
                                            of the gate announcement protocol.
from connecting to external networks to
                                            Add additional requirements to the
connecting to the DS broke the
                                            mesh gate in order to enable the
intention of the portal announcement
                                            gate announcement protocol. (mesh Principle
protocol, which is now called gate
                                            gate connected to portal through a
announcement protocol. The intention
                                            single DS). Maybe, think about a
is to announce 802.1D ports, so that
                                            more specific name for the GANN
they are known in the MBSS and
                                            protocol.
measures can be taken to avoid
                                            Make the rules for interworking with
The clause mixes mesh gates with
                                            the DS, especially for the gate
802.1D ports which are not necessarily
                                            announcement protocol, more
the same sets of mesh STAs. (an
                                            specialized, so that there is a
802.1D port is a mesh gate but not
                                            distinction between the cases          Principle
every mesh gate is an 802.1D port).
                                            where a mesh gate is directly
This has consequences to configuring
                                            connected to an 802.1D port by the
the gate announcement protocol at a
                                            DS or where it is not. The former
mesh gate.
                                            requires the use of the gate
whole clause 11C.9: The clause on the announcement protocol, the later
hybrid wireless mesh protocol (HWMP)
improved a lot compared to earlier          Check the clause on HWMP
versions. However, it is very likely that   thoroughly for completeness,
during the last comment resolutions         consistency and correctness. Also
some improvements have not been             check that the changes from the
                                                                                   Unresolv
done throughout the complete clause,        last comment resolution rounds
                                                                                   able
meaning, that the improvement has           have been implemented
been done in one place but not all other consistently and look out for missed
places dependent on this have been       changes or necessary follow up
changed as well. Furthermore, it might changes.
be the case that some errors,
incorrectnesses and flaws have been
whole clause 11C.7: The section on the
mesh path selection and metric              Check the clause on the mesh path
                                                                                   Unresolv
framework received some good                selection and metric framework
                                                                                   able
overhaul. However, a thorough check         thoroughly.
is still necessary.
whole clause 11C.5: The clauses on
mesh peering are very important since
they decide whether a mesh STA can           Check the clauses on mesh peering Unresolv
successfully connect to a mesh BSS.          thoroughly for correct behaviour.     able
However, it might be still possible that
there are some flaws despite the
conscious work on these clauses so
whole clause 11C.4: The clauses on
mesh peering are very important since
they decide whether a mesh STA can           Check the clauses on mesh peering Unresolv
successfully connect to a mesh BSS.          thoroughly for correct behaviour.     able
However, it might be still possible that
there are some flaws despite the
conscious work on these clauses so
whole clause 11C.3: The clauses on
mesh peering are very important since
they decide whether a mesh STA can           Check the clauses on mesh peering Unresolv
successfully connect to a mesh BSS.          thoroughly for correct behaviour.     able
However, it might be still possible that
there are some flaws despite the
conscious work on these clauses so
                                      Check the clause on mesh
whole clause 11C.2: The clause on the discovery thoroughly. Look
mesh discovery improved a lot         especially for proper algorithmic
compared with previous sections. It is
                                     processing during the mesh
much more formalized and algorithmic discovery process. There must not
now. However, the mesh discovery     be any uncertainties on how to
process is a complex process,         proceed at any point during the      Unresolv
especially with checking and matching mesh discovery process.
                                                                           able
of all the required and optional      Furthermore, check thoroughly if all
capabilities. So, it is rather likely that   necessary capabilities are
this section still contains functional       considered during the mesh
errors and flaws that might lead to          discovery. Check whether they are
deadlock or wrong decisions about            required or optional or if they are
candidate peer neighbors.                    not necessary to be checked.
                                             Especially, the joining of a mesh
The requirement of
"dot11SpectrumManagementRequired
                                        Define the requirement in such a
shall be true" makes it impossible to
                                        way, that it is possible to use 11s on
implement 11s on 802.11 devices that                                             Disagree
                                        devices that have only older PHYs
implement only an older PHY (e.g.
                                        implemented.
11b), for instance, because they are
application specific.




whole clause 11.23: The use of the      Check the definition of the
Interworking capability and element     Interworking capability and element
and the emergency services is a         and emergency service procedures.
                                                                                 Unresolv
complex mechanism in a wireless         Look at completeness and proper
                                                                                 able
mesh BSS. It is possible that it contains working and functionality in a WLAN
some flaws and misspecifications that   mesh environment. Check against
will have an impact on the functionality the requirments for the Interworking
and the proper working of a WLAN        element mesh STA starts an MBSS
                                        When a and the emergency
grammar (3rd person)                    or becomes a member of an MBSS Agree
                                        ...

                                        Insert editorial note that states from
Where does clause 11.9a come from
                                        which amendment after 11mb the           Disagree
(which amendment)?
                                        clause 11.9a comes from.


whole clause 11.9a.3.3: The channel     Check the definition of the channel
switching in a WLAN mesh network is     switch procedures. Look at
not so easy as in an infrastructure        completeness and proper working       Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh      able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
whole clause 11.9.7.2a: The channel     Check the definition of the channel
switching in a WLAN mesh network is switch procedures. Look at
not so easy as in an infrastructure        completeness and proper working       Unresolv
network. Therefore, it is very likely that and functionality in a WLAN mesh      able
the described mechanism will still have environment. Check against the
problems in a distributed wireless mesh requirments for the channel switch.
environment.
                                            Check the definition of the MLME
whole clause 10.3: The MLME SAP
                                            SAP interfaces. Look at
interfaces look much more complete
                                            completeness and on reducing to
and pretty nice than in previous
                                            the minimum amount of MLME SAP
versions. However, the MLME SAP                                                     Unresolv
                                            interfaces. Check whether the
interfaces of such a complex thing as a                                             able
                                            description of the MLME SAP
mesh BSS are complex as well. It is
                                            interfaces is correct and complete,
rather likely that something is missing
                                            and that it actually supports the
or should be arranged in a better way.
                                            mechanisms of the MLME as well
whole clause 9.22: The section on the       as the mesh functionality defined in
                                            Check the clause on mesh
mesh forwarding received a lot of           forwarding and addressing
changes, and it can be doubted that all thoroughly for correct definitions,
flaws are removed by this. The clause descriptions, correct behaviour and
                                                                                    Principle
will have been improved, but a              completeness. Especially the
thorough check is needed. Especially        subclauses on frame addressing
the subclauses on addressing have           and forwarding need to be checked
very likely some errors.                    thoroughly. Furthermore, all the
                                            possible cases for addressing have
                                            Check the definition of MCCA
                                            thoroughly. Focus is on proper and
whole clause 9.9a: The section on
                                            practical-efficient working of the
MCCA improved since the last letter
                                            mechanism in a distributed
ballot. However, since MCCA is a
                                            environment of a wireless mesh
rather complex mechanism, it is still
                                            network. Also do not forget that        Unresolv
very likely that this section contains
                                            MCCA has dependencies on other          able
errors and flaws that impact proper
                                            mechanisms of 11s, especially time
working and functionality. Especially, it
                                            synchronization and beaconing.
might be the case, that it is not able to
                                            Check MCCA also with respect to
handle all possible configurations.
                                            this. Make sure that MCCA can
                                            handle all possible configurations in
                                            Check the definition of the action
                                            frames thoroughly. Consider
whole clause 7.4: The definition of
                                            dependencies between the different
action frames of such a complex
                                            subconcepts of 11s. Check for
concept as a WLAN mesh network
                                            inconsistencies between clause 7.4 Unresolv
contains very likely some flaws that will
                                            and the corresponding clauses,     able
have an impact on the functionality and
                                            especially 11C. Also make sure that
proper working of the WLAN mesh
                                            the definition of the different
network.
                                            categories of the action frames
                                            actually can do the things they are
whole clause 7.3.2: The definition of     Check the definition of information
information elements of such a            elements thoroughly. Consider
complex concept as a WLAN mesh            dependencies between the different Unresolv
network contains very likely some flaws subconcepts of 11s. Check for            able
that will have an impact on the           inconsistencies between clause
functionality and proper working of the   7.3.2 and the corresponding
WLAN mesh network.                        clauses that contains the procedural
whole clause 7.3.1: The definition of     Check the definition of fields that
non-IE fields of such a complex           are not information elements
concept as a WLAN mesh network            thoroughly. Consider dependencies
                                                                                 Unresolv
contains very likely some flaws that will between the different subconcepts
                                                                                 able
have an impact on the functionality and of 11s. Check for inconsistencies
proper working of the WLAN mesh           between clause 7.3.1 and the
network.                                  corresponding clauses that contains
                                    the procedural description.
Several short comings of the MCCAOP Improve the support for partial
Advertisements procedure have been advertisements and large sets of
resolved. However, the support of         MCCAOP reservations by
                                                                                 Disagree
partial advertisements and large sets of integrating the concepts for the
MCCAOP reservations is still not         announcement of MCCAOP
sufficient.                               reservations as given in 11-10/815
                                    and 11-10/814.
Several short comings of the MCCAOP Improve the support for partial
Advertisements frame format               advertisements and multiple
specification have been resolved.         MCCAOP Advertisements elements
However, the support of partial           by integrating the concepts for the    Disagree

advertisements and multiple MCCAOP announcement of MCCAOP
Advertisements elements is still not      reservations as given in 11-10/815
sufficient.                            and 11-10/814.
The MCCAOP Advertisements element
                                       Make the MCCAOP Advertisements
is not flexible enough to accommodate
                                       element more flexible. Change the
all possible settings of MCCAOP
                                       corresponding text in 9.9a.3.8     Disagree
reservations.Furthermore, the support
                                       accordingly. See 11-10/815 and 11-
of partial advertisements is still not
                                       10/814 for a suitable solution.
sufficient.



"via a frame stting Address 2" is bad
English. The meaning is not easy to       improve and make eligible.             Principle
understand.
dot11MeshForwarding is a truth value. replace "is 1" by " is true"                    Agree




we do not use MIB variables from
                                             dot1Mesh... --> dot11Mesh...             Agree
802.1.



b) is confusing and slightly wrong.
What is the frame reception? If it is just
one frame, than this won't work and
won't help in eliminating broadcast          rewrite paragraph b) accordingly.        Principle
storms. Furthermore, it is not sufficient
to compare the mesh SN, it has to be
considered together with the mesh
source address.




spellling                                    "... of an individually addressed ..."   Agree




                                             make dot11MeshTTL normal font.
dot11... are not in typewriter                                                        Principle
                                             check the whole document.




make it clearer that it is an external       Insert between "external" and "STA"
                                                                                      Agree
source station.                              the word "source"
need to check if DA = broadcast is
covered by 9.22.2.2 individually         check this and amend if necessary. Principle
addressed mesh frames.




The attempt to combined A-MSDUs
                                         Rethink wording and distinction
and traditional MSDUs by the term "one
                                         between A-MSDU and traditional       Principle
or more MSDUs collected from the
                                         MSDU.
frame" is a little bit confusing.




Should state that Address 5 is not
mesh STA. Text seems not to cover all rewrite accordingly.                    Principle
possible combinations.



                                         * remove If one or more MSDUs are
The decrement of the TTL is              collected,"
independent of collecting more than      * check the original submission that Principle
one MSDU.                                introduced these changes.
                                        change into "the mesh STA may
                                        detect duplicate MSDUs by
One has to consider Mesh SN and         referring Address 4 and the Mesh
                                                                              Principle
mesh source.                            Sequence Number in the
                                        corresponding Mesh Control field
                                        and discard them (...)"



Case A is for broken links. Case B is
                                        Change Case A to B.                   Agree
for missing forwarding info.



                                        * Replace "mesh STA collocated
                                      with a portal (STA 1)" with "mesh
There are mesh STAs collocated with a gate collocated with a portal (STA
portal or with an AP. Should be mesh 1)"                                      Disagree
gate something.                         * replace "mesh STA collocated
                                        with an AP (STA 2)" with "mesh
                                        gate collocated with an AP (STA 2)"
There cannot be an MMPDU received       Remove MMPDU from the proxy
from the outside of the MBSS. Proxying case in lines 34, 35 and 42 and        Disagree
of MMPDUs (Multihop Action frames) is check the other parts of the
not possible.                           document.
Not the individually addressed Mesh     Change first sentence of note into:
Data fres only use mesh STA             "The forwarding of individually
addresses in fields Address 1,2,3, and addressed Mesh Data frames uses Disagree
4. This is not true. The forwarding uses only mesh STA addresses in fields
only addresses 1-4.                     Address 1, Address 2, Address 3,
                                        and Address 4."



Is a mesh STA that is collocated with   remove "or a mesh STA that is
                                                                              Principle
one or more APs a mesh gate?            collocated with one or more APs"




                                        "any knowledge of the addresses of
Here, these are end stations.           the source and destination end        Disagree
                                        stations,"
                                        move "in the Mesh Control field"
word order                              right after "of optional address          Principle
                                        fields" (ask native speaker)




There is only one optional Address
extension field but multiple optional   remove "extension"                        Principle
address fields.




                                        replace "end station" with "mesh
end station is not always true.                                                   Disagree
                                        STA"

The Mesh Control field is always        * Start the last sentence with "If they
present. Addresses 5 and 6 are not      are present, Address 5 ..."               Disagree
always present.                         * remove "if it is present"

                                        Insert "of data frames" between "in
Address 4 is in the MAC header only
                                        the MAC header" and "if both ToDS Disagree
for data frames.
                                        and FromDS fields are 1"
                                         insert new definition "mesh
mesh forwarding should also be           forwarding: forwarding of MSDUs
                                         and MMPDUs across paths                Disagree
defined in the list definition.
                                         determined by the mesh path
                                         selection in an MBSS at the link

                                         Add the general format (text and
The current specifications of the        table) of the Multihop Action frame
Multihop Action frames allow to place    to 7.4.16.1 (Category, Multihop
the Mesh Control anywhere in the         Action, Mesh Control, elements). In
                                                                                Principle
Action field. However, there should be   7.1.3.6.3 Mesh Control field,
a general rule, where the Mesh Control reference 7.4.16.1 for placement of
is located in any Multihop Action frame. Mesh Control in Multihop Action
                                         frames.



                                         Change first sentence into: "The
                                         Proxy Update frame is used to
The Proxy Update has more uses than inform the recipient about new,
                                                                                Principle
stated here.                             updated, or deleted proxy
                                         information and is transmitted using
                                         individual addresses."


each requires singular                   "... with each frame format are ..."   Agree


                                         Insert a new second sentence
There is no statement how the HWMP       saying this. Presumably, include a
Mesh Path Selecction frame is sent       reference to the clause where the      Principle
(individually and/or group addressed).   addressing (individually/group) is
                                         defined.


Do we really need a Mesh Link Metric
                                         Decide. If only one frame type, than
Request frame, or can we just use the
                                         change accordingly (Mesh Action
Mesh Link Metric Report frame for
                                         field values, frame type description, Principle
request and response (Mesh Link
                                         MLME-interfaces, Link Metric
Metric Report element not present /
                                         Reporting section).
present)?
                                         * for code 13: change "Mesh Action"
In 11mb, the Meaning of category         to "Mesh" in column "Meaning"
codes of Action frames is without        * for code 14: change "Multihop        Agree
action.                                  Action" to "Multihop" in column
                                         "Meaning"




                                         Add for PREQ, PREP, PERR, PXU,
There is no statement about the          and PXUC element corresponding
management frames that contain the       sentence:
PREQ, PREP, PERR, PXU, and PXUC "The PXXX element is transmitted                Principle
element. See RANN element as an          in an {HWMP Mesh Path Selection
example.                                 frame (reference)}."




The Congestion Notification element is
                                         Provide some more flexibility to the
even for a simple and general
                                         Congestion Notification element and Principle
congestion control mechanism to
                                         the congestion control
inflexible.
The Reason Code (RC) subfield
indicates the validity of the Reason
Code field of 2 octets. If we can omit    Define the RC bit in such a way that
the Reason Code field when it is          it indicates the presence of the       Principle
invalid, we might save enough space       Reason Code field.
for additional unreachable destinations
in the PERR element.



                                          Check this, and if it is not needed
We might not need the USN bit.            remove it and every related now not Disagree
                                          needed anymore mechanism.




The previous interworking and HWMP
                                          replace "the request" with "this
elements do not specify the element                                              Agree
                                          element"
name here.




The GANN is not in the beacon             remove " or in a Beacon frame (see
                                                                                 Agree
anymore.                                  7.2.3.1 (Beacon frame format))."




                                          * The Gate Announcement (GANN)
This is not the intended use. Here, a     element is used for announcing the
mesh AP would also send the GANN.      presence of a mesh gate connected
The real intention is to send the GANN to a portal by a single DS in the
                                                                         Principle
if the mesh STA is a mesh gate that is MBSS.
directly connected to a portal through    * Check this throughout the 11s
its DS.                                   draft
                               remove reason code 66 "MESH-
Reason code "MESH-CHANNEL-
                               CHANNEL-SWITCH-
SWITCH-UNSPECIFIED" is never                                  Principle
                               UNSPECIFIED" from Table 7-22
used.
                               and renumber accordingly.
                                  remove reason code 65 "MESH-
Reason code "MESH-CHANNEL-        CHANNEL-SWITCH-
SWITCH-REGULATORY-                REGULATORY-REQUIREMENTS" Principle
REQUIREMENTS" is never used.      from Table 7-22 and renumber
                                  accordingly




                                  remove reason code 61 "MESH-
Reason code "MESH-PATH-ERROR-     PATH-ERROR-UNSPECIFIED"
                                                                  Principle
UNSPECIFIED" is never used.       from Table 7-22 and renumber
                                  accordingly.




                                  remove reason code 53 "MESH-
Reason code "MESH-MAX-PEERS" is
                                  MAX-PEERS" from Table 7-22 and Principle
never used.
                                  renumber accordingly
                                      remove reason code 59 "MESH-
Reason code "MESH-INCONSISTENT- INCONSISTENT-PARAMETERS"
                                                                        Principle
PARAMETERS" is never used.            from Table 7-22 and renumber
                                      accordingly.




                                      "The reason code of the Mesh
missing word                                                            Principle
                                      Peering Close frame ..."




grammar                               "... sends a PERR ..."            Agree




                                      remove " and dot11MeshActivated
It has to be possible to change the
                                      is false" from line 22 EDCA       Disagree
EDCA parameters in an MBSS.
                                      Parameter Set
It has to be possible to change and to   remove ", and dot11MeshActivated
indicate the QoS parameters in an        is false," from line 24 QoS        Disagree
MBSS.                                    Capability
                                        remove ", and dot11MeshActivated
It has to be possible to change the
                                        is false," from line 23 EDCA          Disagree
EDCA parameters in an MBSS.
                                        Parameter Set




grammar                                 "except Multihop Action frames"       Agree



copy and paste error from 11mb          management frames                     Agree


SA in Figure 7-18 is in 11mb without
                                        remove brackets from SA               Principle
brackets.

                                        "of group addressed frames in an
grammar                                                                       Agree
                                        MBSS are"

not only more details, but all the details remove "More" and make "details"
                                                                              Agree
are defined in 9.22.2.3                 upper case.


missing article                         "of the Mesh Control field"           Agree
The Mesh Control field is not optional
according to the bits and pieces in 7.1. remove "optionally"                       Agree
A mesh data frame has a Mesh Control
field.
                                           "For data frames of subtype QoS
grammar                                                                            Agree
                                           Data that are transmitted ..."


grammar                                    either "in an MBSS" or "in MBSSs"       Principle


missing article, e2e should be lower       "of the end-to-end 802
                                                                                   Agree
case.                                      communication"

There are non-zero values that are
                                           insert "non-reserved" between "non-
reserved, so there is no Mesh Address                                              Agree
                                           zero" and "value"
Extension field
It's a decision based on many things, to
name this number Mesh TTL. IPv4 and
most of the existing routing protocols
called this field TTL. IPv6 calls it Hop   Change TTL to hop limit or leave it
                                                                                   Principle
Limit (or something similar, but not       as is.
Time to Live). On the other hand, we
have spend quite some time to educate
the IEEE 802.11 community about the
meaning of TTL. brackets and starting
The sentence in
                                           Remove brackets and make it a
with "see 9.22.2" is important enough                                              Agree
                                           separate sentence.
to be without brackets.
The Mesh Address Extension also
                                           add at the end "and 4 addresses in
allows 4 addresses in Multihop Action                                              Agree
                                           Multihop Action"
frames.

"Mesh Control processing" sounds           "... to control the processing of the
                                                                                   Principle
strange                                    Mesh Control field"


"from 6 to 18 octets" sounds like as that name possible values 6, 12, or 18
                                                                                   Principle
7 is also a valid value.                   octets explicity.

                                           Change sentence into "In the
The Multihop Action frame always           Multihop Action frame, the Mesh
                                           Control field is located as specified   Principle
contains the Mesh Control field.
                                           in 7.4.16 (Multihop Action frame
                                           details)."
Line 32 indicates, that only the first
                                            Change "(or a fragment thereof)"
fragment of a fragmented Mesh Data                                                    Disagree
                                            into "(or the first fragment thereof)"
frame contains the Mesh Control field.


Line 32 indicates, that only the first
                                            Change "(or a fragment thereof)"
fragment of a fragmented Mesh Data                                                    Disagree
                                            into "(or the first fragment thereof)"
frame contains the Mesh Control field.

                                            * Change sentence into "In Mesh
                                            Data frames, the Mesh Control field
                                            is prepended to the MSDU and
                                            located as follows:"
The mesh data frame always contains
                                            * extend definition of Mesh Data          Principle
the Mesh Control field.
                                            frame to having the Mesh Control
                                            field present as indicated by the
                                            Mesh Control Present subfield of
                                            the QoS Control field.


Strictly speaking, the Mesh Control field change "as a part of data" into "as a
                                                                                      Disagree
is not part of data.                        part of the frame body"



missing article                             "The use of the RSPI subfield ..."        Agree

                                            "The Receiver Service Period
The field length of one bit is written as
                                            Initiated (RSPI) subfield is 1 bit in     Agree
number.
                                            length."
                                            "... sets the Mesh Control Present
missing article                                                                       Agree
                                            subfield ..."

                                            Change the first sentence of the
                                            paragraph into: "The QoS Control
The QoS-related information varies not
                                            field is a 16-bit field that identifies
only by frame (sub)type, but also by
                                            the TC or TS to which the frame
BSS type. Furthermore, it is not only
                                            belongs and various other QoS-            Principle
QoS-related information, but also
                                            related, aggregation, and mesh-
aggregation information and mesh-
                                            related information about the frame
related information.
                                            that varies by frame type and
                                            subtype and type of BSS."
The language of the text of 7.1.3.17 in
11mb D4.0 indicates some temporal
and procedural meaning - first, there    Change editiorial instruction in such
are all cases for individually addressed a way that the first sentence
frames where it is possible to set the   (individually addressed frames) of
More Data field to 1, then there is the    the new 11s paragraph of 7.1.3.1.7
default case "The More Data field is set is inserted as a new paragraph in
to 0 in all other directed frames." at the 7.1.3.1.7 right before "The More
                                                                                    Principle
end. After that, the rules for group       Data field is set to 0 in all other
addressed frames are described.            directed frames.". The second
The editorial instruction would include    sentence (group addressed frames)
the individually addressed mesh data       of the new 11s paragraph of
frames after the default setting to 0,     7.1.3.17 is inserted as a new
which could be understood as a             paragraph at the end of 7.1.3.1.7.
contradiction, if one doesn't read far
enough.




This paragraph on the meaning of the
power management field in an MBSS is
confusing and incomplete.
* The text says that it has to be looked
at together with the Mesh Power Save       provide a clear, well-structured
Level subfield, but the remainder of the description of the use of the power
text gets unique information by just       management field in an MBSS.
                                                                                    Principle
looking at the Power Management field. Describe every possible
* What is with peer mesh STAs, value       constellation, and it should be easily
1, and group addressed frames?             seen that every case is considered.
* It's difficult to see the change from
group addressed to individually
addressed frames.
                                         * Change second paragraph of
                                         7.1.2
                                         "The Frame Body field is of variable
                                         size. The maximum frame body size
                                         is determined by the maximum
                                         MSDU size (2304 octets) or the
                                         maximum A-MSDU size (3839 or
                                         7935 octets, depending upon the
                                         STA's capability), plus any
The second paragraph of clause 7.1.2     overhead from security
"General frame format" needs to be       encapsulation."
                                         into                                    Agree
extended with the new mesh control
field.                                   "The Frame Body field is of variable
                                         size. The maximum frame body size
                                         is determined by the maximum
                                         MSDU size (2304 octets) or the
                                         maximum A-MSDU size (3839 or
                                         7935 octets, depending upon the
                                         STA's capability), plus the length of
                                         the Mesh Control field(s) (6, 12, or
                                         18 octets) if present, plus any
                                         overhead from security
                                         encapsulation."
Clause 5.6 discusses the differences
between ESS and IBSS. 11ad adds its add differences of MBSS to ESS
PBSS to this section. It is necessary, to and IBSS to clause 5.6, if             Principle
add the differences of the MBSS to this necessary.
section as well?

                                         change new 2nd paragraph (lines
                                         54-56) into: "When the
As stated in the previous clause, "A
                                         deauthentication service is
STA may be authenticated with many
                                         terminating an SAE authentication
other STAs at any given instant." The
                                         any PTKSA or GTKSA related to           Principle
destruction of PTKSA andGTKSA
                                         this SAE authentication shall be
needs to be specific to the terminated
                                         destroyed. If PMK caching is not
SAE authentication.
                                         enabled, deauthentication also
                                         destroys any PMKSA created as a
                                         result of this successful SAE
Clause 5.4.3.1 talks about
authentication in infrastructure BSS,
                                            Include necessary text for
IBSS, with APs, in RSNA, and RSN.                                                  Principle
                                            authentication in MBSS.
But never about association in an
MBSS. Forgotten or not necessary?




The last sentence in clause 5.2.13.5.12
                                            remove last sentence from
is already to detailed and to normative                                            Principle
                                            5.2.13.5.12
for clause 5.




The need for proper congirugation if
                                            * replace "multiple mesh gates" with
multiple mesh gates are connected to
                                            the right spezialization to multiple
the mesh BSS is, again, only relevant
                                            mesh gates that are connected to a
for mesh gates that are connected to a
                                            portal by a single DS.
portal by a single DS. It is not
                                            * remove sentence "The                 Principle
necessary between two "Mesh APs".
                                            mechanisms and frames utilized to
Furthermore, this configuration is out of
                                            manage the configuration are
scope of 11s, it is part of 802.1D. So,
                                            defined for the mesh BSS."
there are no mechanisms and frames
defined that can be utilized to manage
"a mesh gate announces its presence
in the mesh BSS using the GATE
Announcement element." Mmmh. A
mesh gate might be just collocated with
                                            The rules for sending a Gate
an AP functionality. So does it really to
                                            announcement need review. It
send a Gate Announcement? Is this the
                                            should be restricted to mesh gates     Principle
case the Gate Announcement has
                                            connected to a portal by a single
been introduced? I think the Gate
                                            DS.
Announcement was actually designed
for mesh gates that are connected to a
DS that is connected to a portal,
because there might be problems if

grammar                                     "A mesh gate announces its ..."        Agree
"Link metrics are used to determine a
mesh path to the destination" This         Change commented sentence into
won't work. The path selection protocol "The path selection protocol uses
is used to determine a mesh path to the link metrics in the determination and Principle
destination. The path selection protocol assessment of a mesh path to the
uses the link metric in order to assess destination."
possible paths.

This makes MBSS impossible, because Define mesh STA similar to clause
only mesh STAs can join an MBSS, but 3.1 as a STA that implements the
                                                                              Disagree
only a STA which has joined an MBSS mesh facility. Say something that it
is a mesh STA ...                          belongs to a mesh BSS.



different numbers                          "Within a mesh BSS, ..."           Agree

The abbreviation AODV is used only
once, and that is in a paragraph where Remove AODV from list of
it is spelled out and introduced two                                          Agree
                                       abbreviations in clause 3.3.
lines before (page 217, lines 15-19). It
is not necessary to list it as an




"power save mode" is not defined. It is
                                           Replace "power save mode" with
used in 11mb, but not defined. So what                                        Principle
                                           "the Doze state".
does this mean here?




                                           Define "end station". Remember
"end station" is not defined.              that are source and destination end Disagree
                                           stations in the 11s draft text.
                                          Add definition "neighbor mesh STA:
                                          A mesh STA that is in direct
Definition of "neighbor mesh STA" is
                                          communication range of a mesh            Disagree
missing.
                                          STA over a single instance of the
                                          wireless medium.


A restriction of the DTIM interval to 6
                                          Provide a flexible restriction of the
values which increase exponentially is
                                          DTIM interval or remove this             Principle
not flexible enough for anticipated
                                          paragraph.
usages.

                                          Add at the end fo the definition of
The definition of MCCAOP is too           MCF coordinated cahnnel access
global. Should be restricted to MBSS,     opportunity (MCCAOP): "Both are
                                                                                   Principle
or even better, to MCCA-capable mesh mesh STAs with
STAs.                                     dot11MCCAActivated set to true in
                                          an MBSS."




methods is singular                       method                                   Principle




                                          Change "8.4.2.6 CF Parameter Set
                                          element", "9.4.2 CFP structure and
                                          timing", "10.2.1.4 TIM types", and
The term is already wrongly used in       "dot11CFPPeriod OBJECT-TYPE"
                                                                                   Principle
IEEE 802.11mb for 8 times.                according to the IEEE 802.11s
                                          definition of DTIM interval, i.e. find
                                          new terminology for DTIM interval in
                                          these places.
The definition of precursor mesh STA is Change definition of precursor
a little confusing: A neighbor peer mesh mesh STA into: "A neighbor peer
STA on the mesh path to the               mesh STA, that identifies the mesh Disagree
destination mesh STA cannot be the        STA as the next hop mesh STA on
precursor mesh STA! The mesh path         the mesh path to the destination
would only start at the mesh STA of       mesh STA."




The defined term is not repeated in the remove "mesh peer service period
                                                                                 Agree
definition.                               is a"




What is the difference between a mesh
                                          remove definition of "peer service
peer service period and a peer service                                           Agree
                                          period (PSP)"
period?




The comma after low-entropy seems to
                                          remove "," after "low-entropy"         Agree
be wrong.


semi-colon is the wrong symbol.           replace ";" with ":" after "defined"   Agree


                                          (1) change in definition of mesh
                                          power mode "per peering" into "per
The mesh power mode is defined as         mesh link"
per peering, but the specific definitions (2) delete "link specific" from
of the three mesh power modes are link definitions of active mode, deep          Principle
specific. This is a contradiction. Mesh   sleep mode, and light sleep mode.
link specific is actually right.          This makes these definitions also
                                          more legible.
The mesh peering management
                                             Change definition of mesh link into:
protocol establishes mesh peerings,
                                             "A link from one mesh station (STA)
not mesh links. The mesh link is a link                                              Agree
                                             to a neighbor mesh STA that have a
between two mesh STAs that have a
                                             mesh peering with each other."
mesh peering with each other.




                                             (1) change end of definition of deep
                                             sleep mode into: "... in the Awake or
                                             the
This is lines 18-20 and 27-28.
                                             Doze state and the mesh STA is not
The definitions of deep sleep mode and
                                             expected to receive the beacons
light sleep mode should use the same
                                             from its neighbor peer mesh STAs."
words except for the difference
                                             (2) change end of definition of light   Principle
between them.
                                             sleep mode into: "... in the Awake or
"from the peer mesh STA" is to specific
                                             the
and might not work.
                                             Doze state and the mesh STA is
                                             expected to receive the beacons
                                             from its neighbor peer mesh STAs."




In the alternative BSS definition, the set
of STAs is not well defined. The
alternative BSS definition that is for the (1) delete "as neighbor STA" from
MBSS is either a set of STAs with the line 39
same mesh profile or a single STA.           (2) answer the question of the
What is the neighbor STA doing here?         comment on the necessity of             Principle
Another question: If two mesh STAs           peerings and change alternative
are in range, have the same mesh             BSS definition accordingly.
profile, and they are the only mesh
STAs in the world that have this mesh
profile, but they have no peering with
                                               insert:
                                               Major contributions were received
This is line iv of the frontmatter.
                                               from the following individuals:
The list of people that provided major
                                               Editor's Note: A three column list of Agree
contribution is missing.
                                               those who provided major
                                               contributions will be added during
                                               sponsor ballot at this point.
                                               I believe that it should be "that
                                               received"
"received"?                                    And add a space between "in" and     Agree
                                               "11C.11"

"Each instance of the protocol is
identified by the peer MAC address. "
I'll admit to not having read the details
of all this, but I find it strange that each
instance of the protocol can be fully
identified with that piece of information,
when Peer management requires
(11C.4.2)
-- The sender's MAC address is the
                                               Check for veracity                   Principle
same as the peerMAC of the mesh
peering instance, and;
-- The receiver's MAC address is the
same as the localMAC of the mesh
peering instance, and;
-- The value of the Local Link ID field is
the same as the peerLinkID of the
mesh peering instance, and;
-- The value of the Peer Link ID field is
the same as the localLinkID using a
"mesh peering close can" is of the
verb as a noun. "closure" or "close
event" or "close action" might be better.
You may want to check the rest of the          don't use "close can"                Principle
text for the same issue. You may want
to use "tear-down" as used in the
following paragraph.
The content checking system of the
                                         Oh well ... If IEEE SA would put less
IEEE SA is overly strict when checking
                                         "intelligence" in the comment
XLS sheets that are uploaded. It does
                                         upload system I'd be more than
not accept number ranges ("52-53") in
                                         happy ... At least, we are humans         Unresolv
the line number column. However, with
                                         who are resolving the comments.           able
Framemaker, the line numbers are
                                         Right? It's not the online system
often not exact. Furthermore, if one
                                         that resolves the comment
doesn't add line numbers, one cannot
                                         automatically, is it?
submit the same comments that might
occur in different locations ...         Replace "In case the reservation
                                         was for group addressed frames, it
                                         stop advertising ..." with "In case the
Line 52-53: stop -> stops                                                          Principle
                                         reservation was for group
                                         addressed frames, it stops
                                         advertising ..."
                                         Replace "In case the reservation
                                         was for individually addressed
                                         frames, it stop advertising ..." with
Line 49-50: stop -> stops                                                          Principle
                                         "In case the reservation was for
                                         individually addressed frames, it
                                         stops advertising ..."
                                         Replace "In case the reservation
                                         was for group addressed frames, it
                                         stop advertising ..." with "In case the
Line 40-41: stop -> stops                                                          Principle
                                         reservation was for group
                                         addressed frames, it stops
                                         advertising ..."
                                         Replace "In case the reservation
                                         was for individually addressed
                                         frames, it stop advertising ..." with
Line 37-38: stop -> stops                                                          Principle
                                         "In case the reservation was for
                                         individually addressed frames, it
                                         stops advertising ..."

Line 23-24: I would propose to use the Replace "There are also other
word "tear down" whenever a mesh       conditions that trigger the MCCAOP
STA signals that it stops a reservation. owner and responder to delete a
                                                                                   Agree
The term "delete" should be used when reservation." with "There are also
the mesh STA deletes an entry from its other conditions that trigger the
internal reservation table.            MCCAOP owner and responder to
                                         tear down a reservation."
                                  Replace "If the mesh STA reports
                                  the tracked reservations in a
                                  number MCCAOP Advertisements
                                  elements,
                                  it shall act as follows. If the number
                                  of MCCAOP Advertisement
                                  elements exceeds 8, it shall set the
                                  Last Advertisement subfield of the
                                  MCCA Information field in the
                                  MCCAOP Advertisements element
                                  to 1 and the Advertisement Identifier
Page 113-114: Conditional list.   subfield of the MCCA Information           Principle
                                  field in the MCCAOP
                                  Advertisements
                                  element to 7. If the number of
                                  MCCAOP Advertisements elements
                                  used is between 1 and 8, it shall
                                  number
                                  these MCCAOP Advertisements
                                  elements consecutively, and set the
                                  Last Advertisement subfield to 0 for
                                  the MCCAOP Advertisements
                                  element with the highest value for



                                  Replace "... its shall set the ..." with
Line 58-59: its -> it                                                        Agree
                                  "... it shall set the ..."




                                  Replace "If not all of the conditions
Line 23-24: Wrong reference.      in e) ..." with "If not all of the         Principle
                                  conditions in d) ..."



                                  Replace "If the condition in e4 is
                                  satisfied and the condition in e5 ..."
Line 19-20: Wrong reference.      with "If the condition in d)4) is          Principle
                                  satisfied and the condition in d)5)
                                  ..."
                                              Replace "If the condition in e4 ..."
Line 15-16: Wrong reference.                                                          Principle
                                              with "If the condition in d)4) ..."



                                              Replace "If one of the conditions in
                                              e1-e3 is not satisfied and both
                                              conditions e4 and e5..." with "If one
Line 9: Wrong reference.                                                              Principle
                                              of the conditions in d)1), d)2), or
                                              d)3) is not satisfied and both
                                              conditions d)4) and d)5) ..."



                                              Replace "If not all of the conditions
Line 5: Wrong reference.                      in e) ..." with "If not all of the      Principle
                                              conditions in d) ..."



                                              Replace "If the conditions in e) ..."
                                              with "If the conditions in d) are
Line 62-63: Wrong reference.                  satisfied and the MCCAOP request Principle
                                              is intended for individual addressed
                                              transmissions,..."

                                              Replace "If the conditions in e) are
                                              satisfied and the MCCAOP request
Line 1-4: This is a little bit strange. The
                                              is intended for group addressed
MCCAOP owner transmits an
                                              transmissions, the responder shall
MCCAOP Setup Request to the group
                                              include the reservation into its
address. A group addressed setup
                                              MCCAOP advertisements only after
cannot be acknowledged. The group of
                                              the MCCAOP advertisements from          Disagree
MCCA capable mesh STAs that this
                                              the MCCAOP owner is received."
MCCAOP affects then have to wait for
                                              with "If the conditions in d) are
another announcement of this
                                              satisfied and the MCCAOP request
MCCAOP before they start to advertise
                                              is intended for group addressed
this MCCAOP on their own?
                                              transmissions, the responder shall
                                              include the reservation into its
Line 54-57: This rule is too strict. When
multiple BSSs overlap, neighboring
APs do not care about their neighbors'
beacon frames/transmissions. They           Replace "3) The reservation does
neither stop to transmit nor do they        not overlap with known Beacon
terminate TXOPs early to allow for an       transmission times or HCCA times
                                                                                 Agree
undelayed beacon frame transmission. of neighbor APs" with "3) The
We shouldn't put much burden on an   reservation does not overlap with
MCCA mesh STA. Since HCCA TXOPs HCCA times of neighbor HCs"
are scheduled, the MCCA capable
mesh STA should respect those.
However, there is no need to further
Line 35-37: This rule is too strict. When
multiple BSSs overlap, neighboring
APs do not care about their neighbors'
beacon frames/transmissions. They           Replace "4) The reservation does
neither stop to transmit nor do they        not overlap with known Beacon
terminate TXOPs early to allow for an       transmission times or HCCA times
                                                                                 Agree
undelayed beacon frame transmission. of neighbor APs." with "4) The
We shouldn't put much burden on an   reservation does not overlap with
MCCA mesh STA. Since HCCA TXOPs HCCA times of neighbor HCs."
are scheduled, the MCCA capable
mesh STA should respect those.
However, there is no need to further




                                            Please clarify which MAF Limit is
                                            meant. The mesh STA's own MAF
Line 5: "... to exceed the MAF Limit."      Limit? Its neighbors' MAF Limits?
                                                                                 Principle
Which MAF Limit?                            All MAF Limits it knows about? The
                                            following sentence provides the
                                            necessary hint.
                                         Replace "... STAs.The ..." with "...
Line 53: Missing space.                                                         Agree
                                         STAs. The ..."




                                         Should be "... MCCAOP re-
Line 44-45: Wrong hyphenation.                                                  Principle
                                         servations ..."




Line 20-22: Does the sentence "... and
terminated when the MCCAOP               Add something about an implicit
reservation is torn down." mean that     MCCAOP tear down based on a            Principle
the MCCOP tear down must be              time out.
explicit?




                                         Replace "The HCF shall be
                                         implemented in all QoS STAs
                                         except mesh STAs." with "The HCF
Line 10-11: Add clarification.                                                  Agree
                                         shall be implemented in all QoS
                                         STAs except mesh STAs. Instead,
                                         mesh STAs implement the MCF."
Line 62: EDCA introduces the concept
of virtual collisions. With virtual
collisions, the highest priority EDCAF    Add a concept that allows to add
gains priority over lower priority        MSDUs of lower priority EDCAFs to
EDCAFs in case they have the same         an MCCAOP that a higher priority        Disagree
slot counter. The lower priority EDCAF EDCAF initiated but did not fill for
defers and observes a virtual collision. the MCCAOP's full duration.
However, EDCA has no mechanism
that allows to add lower priority MSDUs
Line 17-21: The of a higher priority
in case a TXOP mesh gate connects to Delete "A mesh STA that operates
the DS. A mesh STA may collocate          in the mesh BSS (MBSS) may
with a mesh gate. However, a mesh         provide the distribution services for
                                                                                  Agree
STA itself does not attach to the DS.     other mesh
Thus, a mesh STA does not provide         STAs."
and DS services.
                                          Replace "... or a group addressed
                                          data frame that has FromDS set to
                                          1 and ToDS set to 0 that is
Line 38-40: Replace "from" with "by."     transmitted from a mesh STA." with Agree
                                          "... or a group addressed data frame
                                          that has FromDS set to 1 and ToDS
                                          set to 0 that is transmitted by a
                                          Replace "... is not expected to
Line 19-20: Remove "the."                 receive the beacons from ..." with      Agree
                                          "... is not expected to receive
                                          beacons from ..."
                                          Replace "... mesh gates in the
                                          different mesh basic service sets
Line 50-53: Remove "the."                 (MBSSs), ..." with "... mesh gates in Agree
                                          different mesh basic service sets
                                          (MBSSs), ..."
Line 36-37: The sentence "NOTE1--         "NOTE1-- The DTIM interval of the
The DTIM interval of the form 2n * 100 form 2^n * 100 TU has been chosen
TU has been chosen so as to facilitate so as to facilitate the verification Agree
the verification that MCCAOP           that MCCAOP reservations do not
reservations do not overlap." misses a overlap."
"^". The interval should a power of 2.
                                          We created the Mesh Path
                                          Selection Action frame so that it
                                          could have all the elements we
                                          wanted to pack in there. This whole
The PREQ has a "per target" field. That business of having variable length
makes processing over complicated.      elements is a twisted attempt at           Disagree
Same comment for PERR.                    saving not-precious-at-all bits
                                          during events that occur
                                          sporadically anyway. It increases
                                          the implementation complexity to a
                                          whole new dimension. Just remove


There are two i