545 171.2 10.2.1.4 In the second sentence, Replace Revised – "do11ShortBeaconInterval" shall be "do11ShortBeaconInterval" by Agree with the commenter. However, this issue has already been addressed by comment resolutions in doc 820r1. 550 170.42 10.2.1.2 The last sentence of 10.2.1.2 says that Replace "Extended Accepted – a non-TIM support field is included in Capabilities element" by Extended Capabilities element. Though, "S1G Capabilities element". TGah editor to make the subclause 8.4.2.170k specifies that a changes proposed by the non-TIM support field is included in commenter. S1G Capabilities element. 846 160.8 9.32n.3 in order benefit fully from relays there define a mechiansim to allow Rejected – should be a mechanism (in addition to AP to enable multiple relay the TXOP sharing decribed in 9.32n.3) STAs to operate at the same The commenter does not to allow AP to enable multiple Relay time (excluding TXOP identify an to be solved STA to communicate with associated sharing operation described and the proposed resolution STAs at the same time in the 9.32n.3) does not provide enough details to evaluate its feasibility. 858 164.14 9.32r Due to the potentially high number of Specify a mechanism to Rejected – channels and channel widths (which indicate APs preferred means a narrow band channel may operating channels and in principle with the overlap with wider band channel) in channel widhts to ensure commenter. However, 11ah there should be a mechanism for robust BSS operation in case comment resolution for CIDs AP to indicate the preferred channel(s) AP may have change 863 and 866 (in doc 779r0) where it moves when current channel channel fast due to OBSS or include the S1G Operation becomes available. Channel switching other unexpected element which indicates such announcement may not reach the long interference- information (Channel Width, sleepers Primary Channel Number, etc). Discussion: None.
545 171.2 10.2.1.4 In the second sentence, "do11ShortBeaconInterval" shall be Replace "do11ShortBeaconInterval" by Revised – Agree with the commenter. However, this issue has already been addressed by comment resolutions in doc 820r1. 550 170.42 10.2.1.2 The last sentence of 10.2.1.2 says that a non-TIM support field is included in Extended Capabilities element. Though, subclause 8.4.2.170k specifies that a non-TIM support field is included in S1G Capabilities element. Replace "Extended Capabilities element" by "S1G Capabilities element". Accepted – TGah editor to make the changes proposed by the commenter. 846 160.8 9.32n.3 in order benefit fully from relays there should be a mechanism (in addition to the TXOP sharing decribed in 9.32n.3) to allow AP to enable multiple Relay STA to communicate with associated STAs at the same time define a mechiansim to allow AP to enable multiple relay STAs to operate at the same time (excluding TXOP sharing operation described in the 9.32n.3) Rejected – The commenter does not identify an to be solved and the proposed resolution does not provide enough details to evaluate its feasibility. 858 164.14 9.32r Due to the potentially high number of channels and channel widths (which means a narrow band channel may overlap with wider band channel) in 11ah there should be a mechanism for AP to indicate the preferred channel(s) where it moves when current channel becomes available. Channel switching announcement may not reach the long sleepers Specify a mechanism to indicate APs preferred operating channels and channel widhts to ensure robust BSS operation in case AP may have change channel fast due to OBSS or other unexpected interference- Rejected – in principle with the commenter. However, comment resolution for CIDs 863 and 866 (in doc 779r0) include the S1G Operation element which indicates such information (Channel Width, Primary Channel Number, etc). Discussion: None.
11-13-1106-00-00ah-cc9-resolution-cids-112-497-544-545-550-605-606-628-657-846-858.docx