5318 Alfred 304.02 9.42f The description of SST Suggest to have Revise generally – operation is quite sparse one subclause agree with commenter, at this point and difficult here that an TGah editor to execute to follow. In my Overview of the proposed changes understanding an SST SST operation found in document AP can setup an SST and SST BSS under all BSS or use the existing setup. Then headings that include BSS to identify the describe that CID 5318. enabled SST channels. from the enabled And then the SST AP SST channnels can signal which are (picked either allowed to be accessed from the BSS during a (short) beacon operation or from interval with the SST the SST element (here) or with operation the RPS element when element) the AP SST STA supports RAW signals the SST (described in 9.22.5.1). channels that are The allowed SST allowed to be channels can also be used every indicated via a TWT (short) beacon element (described in interval by the 9.42a) and can also be SST STA via the periodically setup using SST element as the RPS element described in (a (described in 9.42g.1). I subclause that think SST would really follows this one: benefit from some maybe calling it organization and adding Basic SST references to the operation?) or via subclauses when the the RPS element signaling is provided via as described in other elements. 9.22.5.1. And refer to the signaling with TWT element when these STAs have negotiated TWT operation and to the Periodinc SST operation subclause for the periodic case. Also suggest keeping consistency between the language used in these subclauses. 5319 Alfred 304.63 9.42f DL bit? I think this is DL As in comment. Revise generally – Activity field. I noticed with commenter, TGah some similar editor to execute inconistencies. Please proposed changes check that the field found in document names are inline with the under all elements descriptions. headings that include CID 5319.
5318 Alfred 304.02 9.42f The description of SST operation is quite sparse at this point and difficult to follow. In my understanding an SST AP can setup an SST BSS or use the existing BSS to identify the enabled SST channels. And then the SST AP can signal which are allowed to be accessed during a (short) beacon interval with the SST element (here) or with the RPS element when SST STA supports RAW (described in 9.22.5.1). The allowed SST channels can also be indicated via a TWT element (described in 9.42a) and can also be periodically setup using the RPS element (described in 9.42g.1). I think SST would really benefit from some organization and adding references to the subclauses when the signaling is provided via other elements. Suggest to have one subclause here that an Overview of the SST operation and SST BSS setup. Then describe that from the enabled SST channnels (picked either from the BSS operation or from the SST operation element) the AP signals the SST channels that are allowed to be used every (short) beacon interval by the SST STA via the SST element as described in (a subclause that follows this one: maybe calling it Basic SST operation?) or via the RPS element as described in 9.22.5.1. And refer to the signaling with TWT element when these STAs have negotiated TWT operation and to the Periodinc SST operation subclause for the periodic case. Also suggest keeping consistency between the language used in these subclauses. Revise – generally agree with commenter, TGah editor to execute proposed changes found in document under all headings that include CID 5318. 5319 Alfred 304.63 9.42f DL bit? I think this is DL Activity field. I noticed some similar inconistencies. Please check that the field names are inline with the elements descriptions. As in comment. Revise – generally with commenter, TGah editor to execute proposed changes found in document under all headings that include CID 5319.