changed. Similar BSS, and 0-8191 for S1G response observations on P16L23, BSS". frame carried in S1G P19L39, P23L5. 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 change "if such element Revised- included in the beacon was present in the Beacon RPS element is or short probe response or Probe Response" to "if dynamically controlled by such element was present the MAC sub-layer. in the (short) Beacon or There is no interaction (short) Probe Response" with MLME. TGah editor to make changes in under the heading for CID 2038. 2666 From the current Please clarify. Revised- description it is not clear RPS element is how long is the RAW valid dynamically controlled by for and how many the MAC There consecutive BIs is the RPS is no interaction with IE to be included in the MLME. Beacon and Probe TGah editor to make Response frames. Is it just changes shown in for one BI immediately under the following the receipt of the heading for CID 2038. 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? 1031 The heading should reflect Uppercase everything Revised- properly the name of the before ".request" Segment Count element primitive. 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 change "if such element Revised- can also be included in the was present in the Beacon Segment Count element short beacon or short probe or Probe Response" to "if is dynamically controlled response such element was present by the MAC sub-layer. in the (short) Beacon or There is no interaction (short) Probe Response" with MLME.
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.
11-14-0518-00-00ah-lb200-mac-mlme-sap-comment-resolution.docx