|
7015
|
929.03
|
9.4.2.71.1
|
"may be identified" - "may" in Clause 9
|
Reword to avoid normative verb.
|
REVISED (EDITOR: 2016-02-25 09:35:15Z) - Delete cited sentence.
|
IR
|
EDITOR: 2016-03-02 08:27:41Z- Reviewed. EDITOR_Q: 2016-03-01 18:47:17Z - implemented. The location is 929.03, not 939.01.
The following sentence is deleted: The Antenna Type field does not change based on different modes of operation of the antenna(s), as may be identified by the Antenna ID field (see 9.4.2.40 (Antenna element)).
|
|
7073
|
863.52
|
9.4.2.34
|
"The HC may set the Service Start Time field and the Service Interval field to 0 (unspecified) for nonpowersaving STAs,"
|
Change "may" to "can" and cite the normative text that defines this behaviour.
|
ACCEPTED (EDITOR: 2016-02-25 09:33:32Z)
|
NR
|
EDITOR_A: 2016-03-03 04:00:54Z - reviewed
EDITOR: 2016-03-01 15:34:44Z- Proposed resolution is incomplete. Needs to be revised.
|
|
7111
|
3055.15
|
C.3
|
Regarding dot11LCIAltitude: With the merging of the fraction and integer parts during working group ballot comment resolution, no change was made to the size or range of this variable.
i.e., it no longer necessarily reflect the full range of values possible in the related structures. Also the description citing the "fixed-point" part might be wrong.
|
Adjust at least the range on line 15/16 to reflect the range in Clause 9. Review the other variables in the LCI structure (dot11LCI*) and ensure that the range and description matches
the structure.
|
REVISED (GEN: 2016-02-23 19:54:13Z) Revised.
At 2952.64, change "-2097151..2097151" to "-536870912..536870911"
At 2953.08, delete "This field contains the fixed point Part of Attitude."
|
IR
|
EDITOR: 2016-03-07 10:10:09Z- Review requested. Approved change updates a different MIB variable to the one in the comment.
EDITOR: 2016-03-01 17:29:32Z- Reviewed. EDITOR_A: 2016-02-29 20:37:32Z
|
|
7236
|
2756.22
|
B.4.9
|
It says "Set SERVICE field bits for locked clocks, and length extension (B0, B2, B3, B5, B6, and B7)" but b0, b3, b5 and b7 are now reserved
|
Delete the parenthesis
|
ACCEPTED (EDITOR: 2016-02-25 09:50:34Z)
|
IR
|
EDITOR: 2016-03-01 17:25:19Z- Reviewed. The resolution is too subtle. It states that the parenthesis should be removed. The editor first interpreted this as removing the parentheses.
This was then changed in review to removing the term in parentheses. TGmc, please review and confirm this was the intent.
EDITOR_A: 2016-02-29 19:29:16Z
|
|
7552
|
1960.06
|
12.6
|
What is an "MTKSA"? The term appears in Subclause 12.6 twice, but not in Clause 3, nor is it defined/described in Subclause 12.5.1.1
|
Change both instances to "mesh TKSA" or "mesh PTKSA" (depending on resolution to other comment), with the right case. Also delete "pairwise" before the second
|
REVISED (GEN: 2016-02-25 06:32:05Z) incorporate the changes in 11-16/281r1 (https://mentor.ieee.org/802.11/dcn/16/11-16-0281-01-000m-resolution-of-cid-4859.docx) and remove "pairwise"
in paragraphs 12.6.1.1.9 and 12.6.7
|
MR
|
EDITOR: 2016-03-01 16:51:03Z- Reviewed. Don't see that part of the resolution "remove 'pairwise' in paragraphs 12.6.1.1.9" is correct, as a) the location is imprecise; b) this term doesn't
occur in this subclause.
EDITOR_A: 2016-02-29 22:17:13Z
|
|
7570
|
|
|
All the statements of the form "where KDF-Hash-Length is the key derivation function defined in 12.7.1.7.2 (Key derivation function(KDF)) using the hash algorithm defined by to generate
a key of length Length." is duplication of the specification in 12.7.1.7.2. All that needs to be known is what hash to use
|
Delete the "to generate a key of length Length" at 1915.33, 1917.52, 1919.35, 1995.32, 1995.63, 2066.2, 2138.6, 2138.19,
|
ACCEPTED (GEN: 2016-02-25 11:53:29Z)
|
MR
|
EDITOR_A: 2016-03-05 17:38:07Z - reviewed
EDITOR: 2016-03-01 11:16:25Z- The cited locations did not follow the same pattern. Deleted text at cited locations except:
At 1995.32, did not delete " to generate a key whose length is equal to the length of the hash algorithm’s digest", as I cannot tell how much should be deleted as a purely editorial function.
|
|
7702
|
2313.23
|
18.3.4
|
"is being received at the antenna" -- where else?
|
Delete "at the antenna"
|
REVISED (GEN: 2016-02-24 17:06:20Z) Keeping "at the antenna" is consistent with other places in the document, however the sentence can be clarified as follows:
Change:
"CCA shall report busy at least while a PPDU with energy above the ED threshold is being received at the antenna."
To:
"CCA shall report busy at least while a PPDU is being received at the antenna with energy above the ED threshold."
|
IR
|
EDITOR: 2016-03-01 17:10:42Z- Reviewed. Change made as indicated, but note resolution of similar comment CID 7701 has a different (and better) wording.
EDITOR_A: 2016-02-29 19:46:36Z
|