11-15/1010
|
5025
|
MAC
|
Frame formats 8.4
|
"While associated with an AP or PCP, a STA overrid
|
Move to clause 10 somewhere relevant.
|
|
11-15/1010
|
5026
|
MAC
|
Frame formats 8.4
|
"expected to communicate" - passive voice is consi
|
Reword to avoid the passive voice and remove any e
|
|
11-15/1010
|
5027
|
MAC
|
Frame formats 8.4
|
"The Relay Capabilities element is not used in an
|
Remove cited sentence or move to clause 9 or 10.
|
|
11-15/1010
|
5029
|
MAC
|
Frame formats 8.4
|
"Relay Usability" -- this is a poor choice of fiel
|
Globally change to "Relay Client".
|
|
11-15/1010
|
5038
|
EDITOR
|
General
|
The "Action field format" tables are inconsistent
|
Recommend that this be discussed and see if a simp
|
|
11-15/1010
|
5041
|
MAC
|
Frame formats 8.4
|
"DSE Registered Location Element Body field" -- ha
|
Replace "Element Body" with "Information" in this
|
|
11-15/1010
|
5048
|
GEN
|
GEN Assigned Adrian Stephens
|
There are MIB variables left that relate to the re
|
Remove (or deprecate) all the *ot11Hopping* object
|
|
11-15/1010
|
5059
|
GEN
|
GEN Assigned Adrian Stephens
|
There are a number of placeholder clauses.
|
The group needs to determine whether to keep the p
|
|
11-15/1010
|
5061
|
MAC
|
Frame formats 8.4
|
The reserved range "4-220" is incorrect.
|
Change to "5-220"
|
|
11-15/1010
|
5070
|
MAC
|
Frame formats 8.4
|
Anything that purports to identify elements using
|
Create an Extended Request element, which contain
|
|
11-15/1010
|
5071
|
MAC
|
Frame formats 8.4
|
"Reserved and shall be set to 0 or 3 otherwise" --
|
Either remove "reserved and" or remove "and shall
|
|
11-15/1010
|
5141
|
MAC
|
HCF
|
"All other channel access functions at the STA sha
|
Add to 9.3.2.1 a statement that the virtual carrie
|
|
11-15/1010
|
5310
|
EDITOR
|
Editorials - assigned
|
"A Yes in the Extensible column": but what is in
|
Replace 'A Yes in the Extensible' with 'A "Yes" in
|
|
11-15/1010
|
5863
|
GEN
|
GEN Assigned Adrian Stephens
|
The document does not correctly include terms of c
|
Detailed requested changes will be provided throug
|
|
11-15/1010
|
6042
|
MAC
|
Frame formats 8.4
|
It is confusing to read about the MCCAOP Setup Req
|
Since the MCCAOP Setup Request element corresponds
|
|
11-15/1010
|
6044
|
MAC
|
Frame formats 8.4
|
The calculation of the value of the Length field i
|
The easiest resolution is to delete the sentence "
|
|
11-15/1010
|
6051
|
GEN
|
GEN Assigned Adrian Stephens
|
The term RSNA-capable is only ever used to refer t
|
Change the definition to (deleting "equipment"), "
|
|
11-15/1010
|
6052
|
GEN
|
GEN Assigned Adrian Stephens
|
The term RSNA-enabled is only ever used to refer t
|
Change the definition to (deleting "equipment"), "
|
|
11-15/1010
|
6088
|
GEN
|
GEN Assigned Adrian Stephens
|
A given DS (and therefore a given ESS) can only ha
|
Change "portals" to "the portal" at 10.61, 11.6, 1
|
|
11-15/1010
|
6098
|
MAC
|
Frame formats 8.4
|
Error in the Reserved values range.
|
Change the Reserved table entry value range from '
|
|
11-15/1010
|
6202
|
MAC
|
Frame formats 8.4
|
The term "an RSN protected frame" is used, but the
|
Change the cited text to "a protected frame"
|
|
11-15/1010
|
6226
|
MAC
|
Frame formats 8.4
|
It is not possible to request elements with an ele
|
Add words to that effect
|
|
11-15/1010
|
6254
|
MAC
|
Frame formats 8.4
|
It says "In a Beacon report or , the Antenna ID al
|
Add something before the comma
|
|
11-15/1010
|
6274
|
GEN
|
GEN Assigned Adrian Stephens
|
There are no 2-param Floor examples
|
Add "For example, Floor (3.3, 2) is 2 and Floor (-
|
|
11-15/1010
|
6297
|
GEN
|
GEN Assigned Adrian Stephens
|
It says "nontransmitted basic service set (BSS) id
|
Delete "Beacon" in the cited text
|
|
11-15/1010
|
6323
|
GEN
|
GEN Assigned Adrian Stephens
|
The definition of "STSL" appears to preclude a dir
|
Add "or PCP" after "AP" at 43.12
|
|
11-15/1010
|
6396
|
GEN
|
GEN Assigned Adrian Stephens
|
"non-high throughput (non-HT) physical layer (PHY)
|
Make definition cover PPDUs sent by pre-HT PHYs an
|
|
11-15/1010
|
6410
|
GEN
|
GEN Assigned Adrian Stephens
|
Use of >> on signed quantities is implementation-d
|
Only use unsigned values with >> (cf. e.g. p. 3511
|
|
11-15/1010
|
6413
|
MAC
|
Frame formats 8.4
|
"The Channel Number field indicates the channel nu
|
Clarify (maybe need to say "of frequency segment 0
|
|
11-15/1010
|
6414
|
MAC
|
Frame formats 8.4
|
"The Operating Class field contains an enumerated
|
Clarify
|
|
11-15/1010
|
6415
|
MAC
|
Frame formats 8.4
|
"The Channel Number field indicates a current oper
|
Clarify (maybe need to say "of frequency segment 0
|
|
11-15/1010
|
6433
|
GEN
|
GEN Assigned Adrian Stephens
|
The terms "transmit power" and "transmit power lev
|
Change "transmit power level" to "transmit power"
|
|
11-15/1010
|
6456
|
GEN
|
GEN Assigned Adrian Stephens
|
"monotonic" (/ly) (increasing, incrementing, etc.)
|
Examine the 45 instances of "monotonic" and replac
|
|
11-15/1010
|
6531
|
GEN
|
GEN Assigned Adrian Stephens
|
The definition of "wireless local area network (WL
|
Delete the definition
|
|
11-15/1010
|
6532
|
MAC
|
Frame formats 8.4
|
"Request subelement" is too generic
|
Change to "FMS Request subelement" throughout
|
|
11-15/1010
|
6533
|
MAC
|
Frame formats 8.4
|
"Status subelement" is too generic
|
Change to "FMS Response subelement" throughout
|
|
11-15/1010
|
6560
|
GEN
|
GEN Assigned Adrian Stephens
|
The term "MMPDU" causes no end of confusion as peo
|
Change "MMPDU" to "MLMEPDU" throughout, defining t
|
|
11-15/1010
|
6565
|
GEN
|
GEN Assigned Adrian Stephens
|
The relationship between PHYs is not clear (e.g. a
|
Clarify the relationship between PHYs, and whether
|
|
11-15/1010
|
6587
|
MAC
|
|
We need to distinguish between an MCS for a specif
|
Introduce the term "HT-MCS" and use that for MCSes
|
|
11-15/1010
|
6610
|
MAC
|
|
The mapping from the RCPI to the RCPI value in MMP
|
Put it all in one common place
|
|
11-15/1010
|
6667
|
GEN
|
GEN Assigned Adrian Stephens
|
Add VHT to the definition of "non-high throughput
|
As it says in the comment
|
|
11-15/1010
|
6668
|
GEN
|
GEN Assigned Adrian Stephens
|
The second half in "directional multi-gigabit (DMG
|
As it says in the comment
|
|
11-15/1010
|
6669
|
GEN
|
GEN Assigned Adrian Stephens
|
Definition of "40 MHz physical layer (PHY) protoco
|
As it says in the comment
|
|
11-15/1010
|
6717
|
GEN
|
GEN Assigned Adrian Stephens
|
Need to make sure >> is only used for logical shif
|
As it says in the comment
|
|
11-15/1010
|
6720
|
GEN
|
GEN Assigned Adrian Stephens
|
Does "non-VHT" imply "non-TVHT"?
|
Clarify
|
|
11-15/1010
|
6737
|
GEN
|
GEN Assigned Adrian Stephens
|
Shouldn't have years for docs which are fully iden
|
As it says in the comment
|
|
11-15/1010
|
6747
|
GEN
|
GEN Assigned Adrian Stephens
|
Does "positive" include 0 (apparently not)?
|
Clarify (perhaps in Subclause 1.4 or 1.5?)
|
|
11-15/1010
|
6756
|
GEN
|
GEN Assigned Adrian Stephens
|
"The RCPI field contains an RCPI value as specifie
|
Make the RCPI value mapping the same for all PHYs,
|
|
11-15/1010
|
6787
|
GEN
|
GEN Assigned Adrian Stephens
|
What is X in the penultimate column of Table 17-2
|
Clarify
|
|
11-15/1010
|
6789
|
GEN
|
GEN Assigned Adrian Stephens
|
Inconsistency about presence/absence of space afte
|
As it says in the comment
|
|
11-15/1010
|
6819
|
GEN
|
GEN Assigned Adrian Stephens
|
"individually addressed bufferable unit (BU): An i
|
As it says in the comment
|
|
11-15/1207
|
6223
|
MAC
|
|
Should there be a minimum fragment size? dot11Fra
|
Add a dot11FragmentationLimit
|
|
11-15/1207
|
6227
|
MAC
|
|
What is a "mesh TKSA"?
|
Change to "mesh PTKSA" throughout
|
|
11-15/1207
|
6234
|
MAC
|
|
Basic rates/MCSes are by definition a property of
|
Delete "BSS" (and fix subsequent capitalisation, w
|
|
11-15/1207
|
6236
|
MAC
|
|
What happens if dot11SupportedDataRatesRxTable doe
|
Remove either the SAP parameters or the MIB variab
|
|
11-15/1207
|
6245
|
MAC
|
|
It's not clear which non-Action frames are robust
|
State explicitly in Clause 11 that Disassoc and De
|
|
11-15/1207
|
6290
|
MAC
|
|
The AID is not 1-2007 for DMG STAs
|
Change the text at 173.20, 180.31, 187.26, 1940.30
|
|
11-15/1207
|
6332
|
MAC
|
Frame formats 8.4
|
It says "default pairwise cipher suite and
defaul
|
Is it referring to the case where the RSNE is trun
|
|
11-15/1207
|
6350
|
MAC
|
|
Does reassociation apply to PCPs?
|
Change the text where it indicates reassociation m
|
|
11-15/1207
|
6357
|
MAC
|
|
What is the difference, if any, between "neighbour
|
Clarify. If "peer" means some kind of peering agr
|
|
11-15/1207
|
6424
|
MAC
|
|
The concept of a "successful transmission" (or "tr
|
Define the concept of a successful transmisison in
|
|
11-15/1207
|
6430
|
MAC
|
|
The material related to DMG has a lot of "TXTIME"s
|
Add an indication of the PHY parameters (especiall
|
|
11-15/1207
|
6432
|
MAC
|
|
The spec often talks of doing things based on the
|
Check the use of each of the 114 instances of "rec
|
|
11-15/1207
|
6443
|
MAC
|
|
Is a frame which was not "correctly received" a fr
|
Deal with the miscreants as they were dealt with u
|
|
11-15/1207
|
6457
|
MAC
|
|
The GCM nonce is missing the priority
|
Add a priority, as for CCM
|
|
11-15/1207
|
6460
|
MAC
|
|
What exactly does "mandatory" mean in the context
|
Add a "NOTE---A STA is not required to include man
|
|
11-15/1207
|
6475
|
MAC
|
|
If in a U-APSD SP an AP ends the SP part-way throu
|
Clarify (see CID 1482)
|
|
11-15/1207
|
6483
|
MAC
|
|
The term "supported rate set" is undefined
|
Change throughout to "operational rate set", excep
|
|
11-15/1207
|
6484
|
MAC
|
|
Sometimes the spec refers to Association Request/R
|
Add "(Re)" where appropriate
|
|
11-15/1207
|
6485
|
MAC
|
|
Introduce the term PPDU Transmission Options to en
|
As it says in the comment
|
|
11-15/1207
|
6488
|
MAC
|
|
Non-HT BA is obsolete, as is HT-delayed BA. Their
|
Mark them all as so (or deprecated -- I can't reme
|
|
11-15/1207
|
6536
|
MAC
|
|
There are a bunch of "*BSS network"s, which seems
|
Delete the "network"s
|
|
11-15/1207
|
6543
|
MAC
|
|
References to "Clause frames" (n = 16, 17, etc
|
Pick one valid term and use it consistently
|
|
11-15/1207
|
6570
|
MAC
|
|
It's a bad idea to say which things X is present i
|
Remove all but a single normative instance of thin
|
|
11-15/1207
|
6572
|
MAC
|
|
The distinctions made in the specification w.r.t.
|
Make the definitions comprehensible. E.g. what do
|
|
11-15/1207
|
6589
|
MAC
|
|
Colons in MAC addresses and suchlike imply bit-rev
|
Change the colons to hyphens, or put an explicit n
|
|
11-15/1207
|
6617
|
MAC
|
|
Do we really have to say "Multiple Vendor Specific
|
Say it once at most
|
|
11-15/1207
|
6624
|
MAC
|
|
When do we say "Address 1/2" and when do we say "T
|
Be consistent
|
|
11-15/1207
|
6671
|
MAC
|
|
The last bullet point of NOTE 2 in Table 8-173--HT
|
As it says in the comment
|
|
11-15/1207
|
6706
|
MAC
|
|
Sometimes spec says "Supported Rates element" but
|
Add "and Extended Supported Rates element" whereve
|
|
11-15/1207
|
6708
|
MAC
|
|
DMG mixes up the operational rate set and the basi
|
Unmix DMG
|
|
11-15/1207
|
6710
|
MAC
|
|
"In an A-MSDU, the Mesh Control field is located i
|
Delete "A-MSDU or" in the cited text
|
|
11-15/1207
|
6765
|
MAC
|
|
One instance of "AES-GCMP" (all others are "AES-GC
|
Change the errant one to "AES-GCM"
|
|
11-15/1207
|
6768
|
MAC
|
|
Constructs like "AP's BSSID" are dubious because t
|
Change to "AP's MAC address" throughout
|
|
11-15/1207
|
6770
|
MAC
|
|
It says "Because the IEEE Std 802.11 null Data fra
|
I think it means a Null frame here
|
|
11-15/1207
|
6774
|
MAC
|
|
"The SME shall generate an MLME-ASSOCIATE.response
|
Change to refer to the field which gives the targe
|
|
11-15/1207
|
6786
|
MAC
|
|
"However, an acknowledgment shall be sent in respo
|
Add "or MMPDU" after "MSDU"
|
|
11-15/1207
|
6791
|
MAC
|
|
References to both 802.1Q-2004 and 2011 in clause
|
As it says in the comment
|
|
11-15/1207
|
6799
|
MAC
|
|
Table 11-8---Integrity and key-wrap algorithms top
|
As it says in the comment
|
|
11-15/1207
|
6811
|
MAC
|
|
"When dot11DMGOptionImplemented is true, dot11Mesh
|
Change as suggested in the comment
|
|
11-15/1207
|
6826
|
MAC
|
|
"The Request element field is described in 8.4.2.1
|
As it says in the comment
|
|