|
6712
|
|
|
V
|
Do not allow "A-MPDU" and "A-MSDU" to span lines (i.e. make the hyphen always non-break).
|
As it say in the comment
|
REVISED (EDITOR: 2015-09-16 01:46:57Z) - Make changes under CID 6712 in https://mentor.ieee.org/802.11/dcn/15/11-15-1010-10-000m-revmc-sb0-stephens-resolutions-part-2.doc.
This addresses hyphenation of the most frequent 30 hyphenated terms.
|
EDITOR
|
|
5278
|
586.09
|
8.2.4.6.3
|
J
|
"For a VHT STA:" implies that this is something done by another entity for the STA, while it actually is done in the STA.
|
On lines 9 and 15 replace "For a" with "In a".
|
REJECTED (EDITOR: 2015-09-16 02:04:11Z) - "In a" doesn't work here. The frame is not "in" a STA, but is transmitted or received by the
STA. "For a" is unambigous.
|
EDITOR
|
|
5352
|
788.09
|
8.4.2.21.10
|
V
|
"a LCI subelement Length of 0": the Length field is not 0, though its value might be.
|
Replace "subelement Length of" with "subelement Length value of" throughout the draft.
|
REVISED (EDITOR: 2015-05-26 13:58:52Z) - Replace: "indicated by a LCI subelement Length of 0 and no following fields"
by
"indicated by the Length field of the LCI subelement being set to 0 and there being no following subelements"
|
EDITOR
|
|
5309
|
738.34
|
8.4.2.20.6
|
J
|
"The Subelement ID field values ... are shown in": but the value of this field is what is in the field at the time it is in a transmitted
frame, not a list of possible values it might have.
|
Replace "The Subelement ID field values" with "The eligible Subelement ID field values".
|
REJECTED (EDITOR: 2015-09-16 01:58:11Z) - The table defines the interpretation of all possible values of this field, including defining
which values are reserved. So the limitation to "eligible" by the proposed change is incorrect.
|
EDITOR
|
|
5493
|
1536.37
|
10.1.3.8
|
V
|
"A STA that has a value of true for
dot11MultiBSSIDActivated is defined as a STA that supports the Multiple BSSID capability. A STA for which dot11MultiBSSIDActivated is true shall set the Multiple BSSID field of the Extended Capabilities element to 1.": a station has a value of true? So some
stations are false? And the STA somehow holds the value true for an attribute? And multiple BSSID capability (note that the name of a capability does not take initial caps) is the definition of a STA that holds a true value for a specific attribute? And another
STA has a dot11 attribute that is true for it. And that STA apparently has stored somewhere an element in which it sets the values of the element's fields. Where did all this fanciful writing come from?
|
Replace:
"A STA that has a value of true for
dot11MultiBSSIDActivated is defined as a STA that supports the Multiple BSSID capability. A STA for which dot11MultiBSSIDActivated is true shall set the Multiple BSSID field of the Extended Capabilities element to 1."
With:
"A STA whose dot11MultiBSSIDActivated value is true shall be multiple BSSID capable and shall set to 1 the Multiple BSSID field of the Extended Capabilities elements that it transmits."
|
REVISED (EDITOR: 2015-05-28 10:36:04Z) - Replace "A STA that has a value of true for
dot11MultiBSSIDActivated is defined as a STA that supports the Multiple BSSID capability. A STA for which dot11MultiBSSIDActivated is true shall set the Multiple BSSID field of the Extended Capabilities element to 1."
With:
"A STA in which dot11MultiBSSIDActivated is true is defined as a STA that supports the Multiple BSSID capability. The STA shall set to 1 the Multiple BSSID field of the Extended Capabilities elements that it transmits."
|
EDITOR
|
|
5073
|
1082.28
|
8.4.5.5
|
V
|
The letters representing variable values should be italics
|
As in comment
|
REVISED (EDITOR: 2015-08-13 15:05:13Z) - Change variables to italic within 8.4.6.5, and check that the appropriate IEEE paragraph styles
are applied.
|
EDITOR
|
|
6697
|
|
|
V
|
Sometimes "SIFS" is used in equations, sometimes "aSIFSTime" (probably other pairs too).
|
Use aSIFSTime where SIFS is used, throughout
|
REVISED (EDITOR: 2015-08-18 09:17:05Z)
Globally replace "+ SIFS Time" with "+ aSIFSTime"
Globally replace "+ SIFS" with "+ aSIFSTime"
(excluding 1457.50, 1464.25, 1257.42, )
Replace SIFS with aSIFSTime at 1258.16, 1464.32 (2x), 1534.37.
|
EDITOR
|
|
5387
|
1020.40
|
8.4.2.137
|
J
|
"The BSSID field specifies", here and on line 45: "band indicated by the Channel Number and Band ID fields.", on line 44: "Beacon Interval
field specifies": it is not fields that specify and indicate, but their contents.
|
Replace "The BSSID field specifies" with "The value of the BSSID field specifies". On this line and line 45 replace "indicated by the"
with "indicated by the values of the". And on line 44 replace "Beacon Interval" with "value of the Beacon Interval".
|
REJECTED (EDITOR: 2015-04-28 10:06:59Z) - According to the convention stated in subclause 1.4, it is not necessary to add "value of" when
referring to the contents of a field.
|
EDITOR
|
|
6154
|
3.01
|
1.5
|
J
|
From Guido Hiertz:This clause uses upright font for quantity symbols. This seems to comply with IEEE 260. Other equations in 802.11REVmc/D4.0
use upright font for quantity symbols. This is inconsistent.
|
I propose that no changes are applied to this clause. However, this clause should refer to IEEE Std 260.1-2004 to explain basic principles
of mathematical notations.
|
REJECTED (EDITOR: 2015-06-16 12:28:16Z) - The comment fails to identify a specific issue to be addressed. It fails to identify changes
in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.
|
EDITOR
|
|
5293
|
729.59
|
8.4.2.16
|
A
|
This is a simple list, so there is no need for semicolons.
|
Replace the first sentence of the paragraph with:
"The TPC Report element is included in TPC Report frames (see 8.6.2.5 (TPC Report frame format)), Link Measurement Report frames (8.6.7.5 (Link Measurement Report frame format)), Beacon frames (8.3.3.2 (Beacon frame format)) and Probe Response frames (8.3.3.10
(Probe Response frame format))."
|
ACCEPTED (EDITOR: 2015-09-16 01:34:45Z)
|
EDITOR
|