5318 Alfred 304.02 9.42f The description of SST Suggest to have Revise generally – operation is quite sparse one subclause with commenter, TGah at this point and difficult here that gives editor to execute to follow. In my an Overview of proposed changes understanding an SST the SST found in document AP can setup an SST operation and under all BSS or use the existing SST BSS setup. headings that include BSS to identify the Then describe CID 5318. enabled SST channels. that from the And then the SST AP enabled SST can signal which are channnels allowed to be accessed (picked either during a (short) beacon from the BSS interval with the SST operation or from element (here) or with the SST the RPS element when operation SST STA supports RAW element) the AP (described in 9.22.5.1). signals the SST The allowed SST channels that are channels can also be allowed to be indicated via a TWT used every element (described in (short) beacon 9.42a) and can also be interval by the periodically setup using SST STA via the the RPS element SST element as (described in 9.42g.1). I described in (a think SST would really subclause that benefit from some follows this one: organization and adding maybe calling it references to the Basic SST subclauses when the operation?) or via signaling is provided via the RPS element other elements. 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. 5319 Alfred 304.63 9.42f DL bit? I think this is DL As in comment. Revise generally – Activity field. I noticed agree with commenter, some similar TGah 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 gives 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 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 agree with commenter, TGah editor to execute proposed changes found in document under all headings that include CID 5319.
11-15-0083-01-00ah-lb205-twt-sst-cids-not-grouptwt.docx