|
7184
|
|
|
V
|
There are multiple instances of "Handshake" (after PeerKey, TPK, 4-Way, (SMK), (STK), Mesh Group Key, SMK, (TPK), TDLS Setup, the, STK,
PTK, TPK Security Protocol, GTK
|
Change all instances to "handshake", and adjust the surrounding words too if uppercase
|
REVISED (EDITOR: 2016-01-29 10:57:06Z) - Change "Message " to "message ", except where syntax requires initial cap.
Make changes as specified, except:
do not change case of preceeding: "Peer Key" or "PeerKey"
do not change when indicating an AKM enumeration
do not change "TPK Handshake Key"
|
EDITOR
|
Terminology
|
|
EDITOR: 2016-01-29 10:59:33Z - Made speculative edits. Changes as requested also implied changing "Message " to "message ", which was a
far bigger job than changing "Handshake".
Another candidate change for consistency is to change "Supplicant" to "supplicant". I didn't make that change, because at some point I have to stop pulling on this thread or the whole jumper will dissappear in a puff of editing smoke.
|
|
7242
|
2908.03
|
C.3
|
J
|
It says "Time-out"
|
Change to "Timeout"
|
REJECTED (EDITOR: 2016-02-04 10:32:44Z) - This is an automatically inserted hyphen.
|
EDITOR
|
Editorials rejected
|
|
|
|
7251
|
|
|
J
|
It says "Awake Window"
|
Change to "awake window"
|
REJECTED (EDITOR: 2016-02-09 10:21:15Z) - The commenter doesn't indicate why "Awake Window" is incorrect, or where it is incorrect.
The proposed change is incorrect, because it would result in the incorrect "awake window element" and "Maximum awake window Duration field".
|
EDITOR
|
Editorials rejected
|
|
EDITOR: 2016-02-12 10:09:27Z - Mark R intends to bring a submission - similar to 7250.
EDITOR: 2016-02-09 10:21:08Z- Changed to "Rejected."
|
|
7269
|
548.08
|
8.3.4.2
|
A
|
"PHY-TXHEADEREND" is missing from Table 8-2---PHY-SAP inter-(sub)layer service primitives
|
Add a row for this, with an X in the Indication column
|
ACCEPTED (EDITOR: 2016-01-29 15:40:36Z)
|
EDITOR
|
PHY SAP
|
|
Adding content is not editorial. Changed to "PHY SAP".
|
|
7270
|
|
|
J
|
Characteristics should not be called "asomething" (or otherwise have the name of the PHY in the middle) since they are used by the MAC,
which is supposed to be common for all PHYs
|
Delete "DMG" from aDMGPPMinListeningTime, aDMGDWSValidPeriod, aDMGDetectionThres and arguably also aCWminDMGIBSS, aMinPPDUDurationForDMGMeasurement
|
REJECTED (EDITOR: 2016-01-29 11:17:06Z) - "DMG" is a qualifier used in both the name of the PHY and the STA - "a DMG STA". It is entirely
appropriate that DMG-specific characteristics are labelled thus.
|
EDITOR
|
Terminology
|
|
|
|
7326
|
|
|
J
|
Something has gone horribly wrong around here
|
Make it right
|
REJECTED (EDITOR: 2016-01-28 11:25:36Z) - 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
|
Editorials rejected
|
|
|
|
7327
|
563.01
|
9
|
J
|
"The UTF-8 format is defined in IETF RFC 3629." is superfluous
|
Delete the 2 instances of this sentence
|
REJECTED (EDITOR: 2016-01-29 15:44:44Z) - The cited sentence is not incorrect, and it is informative.
|
EDITOR
|
Editorials rejected
|
|
|
|
7374
|
|
|
V
|
It says "integral"
|
Delete when preceding "multiple", otherwise change to "integer"
|
REVISED (EDITOR: 2016-01-28 10:23:41Z) - Change all "integral" to "integer", except at 3581.57.
In reply to the commenter one of "integral" or "integer" may be necessary before "multiple" to make it clear that fractional multiples are not allowed, for example the text at 680.01 needs this qualification.
|
EDITOR
|
Editorials objected to
|
|
|
|
7409
|
2240.60
|
16.2.5
|
J
|
"by the MAC" in a PHY clause
|
Move to a MAC clause
|
REJECTED (EDITOR: 2016-02-02 13:19:29Z) - This is descriptive text - i.e., describing the purpose of the primitive. It does not contain
any normative requirements for the MAC. Its presence here is appropriate.
|
EDITOR
|
Editorials rejected
|
|
|
|
7410
|
2209.41
|
|
J
|
"is issued to the MAC" -- it can't be issued to anything else
|
Delete "to the MAC" in all cases
|
REJECTED (EDITOR: 2016-01-28 10:01:00Z) - The cited text is not incorrect and may aid the reader.
|
EDITOR
|
Editorials rejected
|
|
|
|
7482
|
|
|
V
|
Per the resolution of CID 6126, "over the air" is too informal and "over the WM" is to be used. How about "on the air", "on-the-air", "the
air interface"?
|
Change "on the air"/"on-the-air" to "over the WM" (about 17 instances) and "air interface" to "WM" (about 13 instances)
|
REVISED (EDITOR: 2016-01-28 12:19:57Z) - Change all "on the air" to "on the WM",
except change to "over the WM" at 1634.13.
Change all "on-the-air" to "over-the-WM".
Change all "at the air interface" to "on the WM".
|
EDITOR
|
Terminology
|
|
|
|
7490
|
|
|
A
|
Some instances of "backoff time" should be "backoff timer"
|
Change at 1272.56, 1273.25, 1290.64, 1291.28, 1291.29,
|
ACCEPTED (EDITOR: 2016-01-28 14:02:12Z)
|
EDITOR
|
Terminology
|
|
|
|
7522
|
27.63
|
3.2
|
J
|
We don't define STA for any other PHY
|
Delete the definition of DMG STA (and also DMG AP and maybe DMG BSS)
|
REJECTED (EDITOR: 2016-01-29 13:55:56Z) - DMG as a qualifier applies to more than just the PHY. It is defined by reference to the frequencies
it operates in, but that does not limit the qualifier only to the PHY layer.
|
EDITOR
|
Editorials rejected
|
|
|
|
7582
|
|
|
J
|
"is IDLE", "indicates IDLE" etc. when not referring to the STATE argument should be lowercase. Ditto "BUSY"
|
. In D4.0 (possibly some fixed in CR): a PHY-CCA.indication primitive that is BUSYLowercase at 1279.8, 2200.8, 1293.2, 1364.44, 1364.50,
2259.6, 2217.21.5, 2217.56, 2241.62, 2244.55, 2302.25. Consider adding "medium" or "channel" where absent
|
REJECTED (EDITOR: 2016-01-29 11:22:46Z) - Comment does not indicate valid locations in the balloted draft.
|
EDITOR
|
Editorials rejected
|
|
EDITOR: 2016-01-29 11:23:24Z - Note to commenter, please do not provide references to previous versions of the draft. You can hardly expect
the editors to want to do additional work that you can and should have done yourself.
|
|
7637
|
1951.01
|
12.5.3.4.4
|
J
|
This subclause keeps switching between "receiver" and "recipient"
|
Pick one and stick to it
|
REJECTED (EDITOR: 2016-02-04 10:25:33Z) - Both terms are equally valid and used commonly in the draft. There is no need to avoid use of
one of them.
|
EDITOR
|
Editorials rejected
|
|
|
|
7638
|
1959.22
|
12.5.5.4.4
|
J
|
This subclause keeps switching between "receiver" and "recipient"
|
Pick one and stick to it
|
REJECTED (EDITOR: 2016-02-04 10:26:17Z) - Both terms are equally valid and used commonly in the draft. There is no need to avoid use of
one of them.
|
EDITOR
|
Editorials rejected
|
|
|
|
7639
|
|
|
J
|
This spec keeps switching between "receiver" and "recipient"
|
Pick one and stick to it, at least within a subclause and siblings/cousins/children
|
REJECTED (EDITOR: 2016-01-28 10:14:48Z) - These terms are used as synonyms with roughly equally frequency. Their intended use is clear.
|
EDITOR
|
Editorials rejected
|
|
EDITOR: 2016-01-28 10:13:06Z - There are 593 "receiver" and 417 "recipient".
|
|
7652
|
1766.49
|
11.24.6.3
|
V
|
Move "The responding STA's selection of the format and bandwidth in the FTM Format and Bandwidth field should be the same as that requested
by the initiating STA. The responding STA shall not choose a bandwidth wider than requested. The responding STA shall not choose a VHT format if HT-mixed or non-HT format was requested. The responding STA shall not choose an HT format if non-HT format was
requested." to the "If the request was successful" below
|
As it says in the comment
|
REVISED (EDITOR: 2016-02-04 10:08:41Z) - Move the para to become the new first list item at 1767.01.
|
EDITOR
|
Frame Formats
|
|
Agree with commenter, but not editorial.
|
|
7663
|
716.28
|
9.4.1.53
|
J
|
It says "Transmitting STA does not support 160MHz PPDUs and transmitting STA does notsupport 80+80 MHz PPDUs."
|
Change to "Transmitting STA does notsupport 80+80 or 160 MHz PPDUs."
|
REJECTED (EDITOR: 2016-02-09 10:31:50Z) - The cited text is correct.
|
EDITOR
|
Editorials rejected
|
|
EDITOR: 2016-02-09 10:31:36Z - Updated resolution. Was previously: "The cited text is correct, and similar text is used elsewhere in this
table."
|
|
7673
|
715.20
|
9.4.1.53
|
J
|
It says "The Dynamic Extended NSS BW field, combined with the Channel Width field,Supported Channel Width Set field and the Supported VHT-MCS
and NSS Setfield indicates whether 80+80 MHz and 160 MHz operation is supported.In addition, the Dynamic Extended NSS BW Support field, combined with theSupported VHT-MCS and NSS Set field indicates extensions to the maximumNSS supported for each bandwidth
of operation. "
|
Change to "The value of this field, combined with the Channel Width field,Supported Channel Width Set field and the Supported VHT-MCS and
NSS Setfield, indicates whether 80+80 MHz and 160 MHz operation is supported.In addition, the value of this field, combined with theSupported VHT-MCS and NSS Set field, indicates extensions to the maximumNSS supported for each bandwidth of operation. "
|
REJECTED (EDITOR: 2016-02-01 16:41:34Z) - The comment does not indicate why the cited text is wrong - i.e., there is no rationale for the
change.
|
EDITOR
|
Editorials rejected
|
|
|
|
7736
|
|
|
J
|
There are two instances of " usingthe hash algorithm defined for/by the negotiated AKM in Table 9-132" and one of "is the hash algorithm
defined by the negotiated AKM specified in Table 9-132" compared with eight of " using the hash algorithm defined by the AKM in Table 9-132"
|
Change the three to "using/is the hash algorithm defined by the AKM in Table 9-132" too
|
REJECTED (EDITOR: 2016-01-28 11:32:09Z) - The cited text is correct, no change is necessary.
|
EDITOR
|
Editorials rejected
|
|
|
|
7737
|
|
|
J
|
There are 5 "hash function"s and 16 "hash algorithms"
|
Change the 5 to "hash algorithm"s
|
REJECTED (EDITOR: 2016-01-28 11:32:40Z) - Both terms are correct.
|
EDITOR
|
Editorials rejected
|
|
|
|
7754
|
|
|
J
|
There are 7 instances of "used by the MAC"
|
Delete "by the MAC" in all except the ones in Clause 17. At 199.55 also delete "entity that is being reset" and 556.19 also delete "sublayer"
|
REJECTED (EDITOR: 2016-01-29 11:19:31Z) - The cited text is not incorrect.
|
EDITOR
|
Editorials rejected
|
|
|
|
7758
|
|
|
J
|
3 instances of " the received status of up to 64 entries, where each entry representsan MSDU or an A-MSDU"
|
Change each to "the received status of up to 64 MPDUs, where each MPDU contains an MSDU or A-MSDU"
|
REJECTED (EDITOR: 2016-01-29 11:03:01Z) - The text as specified is correct. In the three cited locations there is a 1:1 mapping between
entries and "MSDU or an A-MSDU".
|
EDITOR
|
Editorials rejected
|
|
|
|
7800
|
|
|
J
|
Various editorial issues were raised in yellow stuff in 14/1104
|
Address these editorial issues
|
REJECTED (EDITOR: 2016-01-29 10:10:06Z) - 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
|
Editorials rejected
|
|
|
|
7801
|
32.06
|
3.2
|
J
|
"This format is represented at the PHY data service access point (SAP) by the TXVECTOR/RXVECTOR FORMAT parameter being equal to HT_GF."
is superfluous (not done for other cases)
|
Delete the cited sentence
|
REJECTED (EDITOR: 2016-01-29 14:03:33Z) - The cited sentence is not incorrect. There are at least two other occurrences of similar language,
so "not done for other cases" is not correct.
|
EDITOR
|
Editorials rejected
|
|
|
|
7802
|
32.12
|
3.2
|
J
|
"This format is represented at the PHY data service access point (SAP) by the TXVECTOR/RXVECTOR FORMAT parameter being equal to HT_MF."
is superfluous (not done for other cases)
|
Delete the cited sentence
|
REJECTED (EDITOR: 2016-01-29 14:04:50Z) - The cited sentence is not incorrect. There are at least two other occurrences of similar language,
so "not done for other cases" is not correct.
|
EDITOR
|
Editorials rejected
|
|
|
|
7810
|
109.50
|
4.6
|
V
|
4.6 should talk about "non-802.11" not "wired", when considering other address spaces.
|
Replace "wired LAN" with "non-IEEE Std 802.11 LAN" (2 occurences in 4.6, one in 4.7)
|
REVISED (EDITOR: 2016-01-29 14:24:54Z) - Change 3 cited occurrences of "wired LAN" to "non-IEEE-Std-802.11 LAN".
|
EDITOR
|
Terminology
|
|
EDITOR: 2016-01-29 14:20:54Z - This is arguably non-editorial, so moved to "Terminology".
|