changed. Similar observations on P16L23, P19L39, P23L5. BSS, and 0-8191 for S1G BSS". response frame carried in S1G PPDU, it is not necessary to modify the valid range of the AID field. 2035 Typo Remove "(" Accepted- Agree in principle. 2036 Typo Remove "(" Accepted- Agree in principle. 2037 Typo Remove "(" Accepted- Agree in principle. 2038 RPS element can also be included in the beacon or short probe response change "if such element was present in the Beacon or Probe Response" to "if such element was present in the (short) Beacon or (short) Probe Response" Revised- RPS element is dynamically controlled by the MAC sub-layer. There is no interaction with MLME. TGah editor to make changes in under the heading for CID 2038. 2666 From the current description it is not clear how long is the RAW valid for and how many consecutive BIs is the RPS IE to be included in the Beacon and Probe Response frames. Is it just for one BI immediately following the receipt of the MLME-RPS.request or does it persist till another MLME-RPS.request is received? If the RAW is persistent, does the MLME need to update/remove the PRAW information in the RPS IE? Please clarify. Revised- RPS element is dynamically controlled by the MAC There is no interaction with MLME. TGah editor to make changes shown in under the heading for CID 2038. 1031 The heading should reflect properly the name of the primitive. Uppercase everything before ".request" Revised- Segment Count element is dynamically controlled by the MAC sub-layer. There is no interaction with MLME. TGah editor to make changes shown in under the heading for CID 1031. 2039 Segment Count element can also be included in the short beacon or short probe response change "if such element was present in the Beacon or Probe Response" to "if such element was present in the (short) Beacon or (short) Probe Response" Revised- Segment Count element is dynamically controlled by the MAC sub-layer. There is no interaction with MLME.
6.3.107.2 MLME-TWTTEARDOWN.request 6.3.107.2.1 Function This primitive requests that a TWT Teardown frame be sent to the AP with which the non-AP STA is associated. 6.3.107.2.2 Semantics of the service primitive The primitive parameters are as follows: MLME-TWTTEARDOWN.request( PeerSTAAddress, TWTFlow (#1018) ) Name Type Valid range Description PeerSTAAddress MAC Address Any valid individual MAC Address Specifies the address of the peer MAC entity with which to perform the TWT Teardown procedure. TWTFlow As defined in 8.6.24.9 (TWT Teardown frame format) As defined in 8.6.24.9 (TWT Teardown format) Specifies the proposed service parameters for the TWT Teardown. 6.3.107.2.3 When generated This primitive is generated by the SME to request that a TWT Teardown be sent to the AP with which the STA is associated. 6.3.107.2.4 Effect of receipt On receipt of this primitive, the MLME constructs a TWT Teardown frame(#100). The STA then attempts to transmit this to the AP with which it is associated. 6.3.107.3 MLME-TWTTEARDOWN.indication 6.3.107.3.1 Function This primitive indicates that a TWT Teardown frame was received from a non-AP STA. 6.3.107.3.2 Semantics of the service primitive The primitive parameters are as follows: MLME-TWTTEARDOWN.indication( PeerSTAAddress, TWTFlow (#1018) ) Name Type Valid range Description PeerSTAAddress MAC Address Any valid individual MAC Address Specifies the address of the peer MAC entity with which to perform the TWT Teardown procedure. TWTFlow As defined in 8.6.24.9 (TWT Teardown frame format) As defined in 8.6.24.9 (TWT Teardown frame format) Specifies the proposed service parameters for the TWT Teardown.
6.3.111 Flow Suspend operation 6.3.111.1 General The following MLME primitives support the signaling of a flow suspend operation. 6.3.111.2 MLME-FLOWSUSPEND.request 6.3.111.2.1 Function This primitive requests that a Flow Suspend frame be sent to a peer entity. 6.3.111.2.2 Semantics of the service primitive The primitive parameters are as follows: MLME-FLOWSUSPEND.request( PeerSTAAddress, SuspendDuration (#1018) ) Name Type Valid range Description PeerSTAAddress MAC Address Any valid individual MAC Address Specifies the address of the peer MAC entity with which to perform the flow suspend operation. SuspendDuration As defined in 8.6.26.2 (Flow Suspend As defined in 8.6.26.2 (Flow Suspend frame) Specifies the proposed service parameters for the Flow Suspend operation. 6.3.111.2.3 When generated This primitive is generated by the SME to request that a Flow Suspend frame be sent to the peer entity. 6.3.111.2.4 Effect of receipt On receipt of this primitive, the MLME constructs a Flow Suspend frame(#100). The STA then attempts to transmit this to the peer entity. 6.3.111.3 MLME-FLOWSUSPEND.indication 6.3.111.3.1 Function This primitive indicates that a Flow Suspend was received from a peer entity. 6.3.111.3.2 Semantics of the service primitive The primitive parameters are as follows: MLME-FLOWSUSPEND.indication( PeerSTAAddress, SuspendDuration (#1018) ) Name Type Valid range Description PeerSTAAddress MACAddress Any valid individual MAC Address The address of the peer MAC entity from which a Flow Suspend frame was received.