Context: It seems reasonable that an A-MSDU could be used in this context. Certainly, if the A-MSDU contains only one MSDU (the A-MSDU being used for other purposes), then this seems perfectly fine. ‘wrapper’ It is less clear if the polling non-AP STA was expecting and can handle getting multiple MSDUs contained in an A-MSDU. However, since such a STA has negotiated the use of A-MSDU for transmission to it, and the limits on such use, it seems reasonable that those same limits would be workable for the STA while in power save. Thus, the proposal is to accept this change. Proposed Resolution: ACCEPTED. Can we just use instead? “BU” No proposed resolution, yet: CID Comment Page Clause Proposed Change 7146 Stephens, 134.10 5.1.5.1 A role-specific behaviour is not Determine whether to show a Adrian shown for a DMG relay. role-specific behaviour for a If security on a DMG relay is DMG relay, which would be established for each leg of the similar to a mesh STA. relay, then the data-flow must pass through the controlled port, and therefore be shown in the role-specific behaviour. 7150 Stephens, 3581.01 Annex N Annex N contains terminology Review Annex N and change Adrian that is unique to itself, such as terminology and architecture to WLAN system and ACM_STA. conform to the normative portions The understanding of what a DS of the draft. is has developed and change in the ARC standing committee, resulting in changes to Clause 5. Annex N has been ignored. 7069 Stephens, 854.62 9.4.2.31 " An incoming MSDU that is not Move normative behaviour to Adrian classified to a particular TS may clause 10/11. be classified to another active TS based on the frame classifier for that TS." - normative verb in clause 9
Context: It seems reasonable that an A-MSDU could be used in this context. Certainly, if the A-MSDU contains only one MSDU (the A-MSDU ‘wrapper’ being used for other purposes), then this seems perfectly fine. It is less clear if the polling non-AP STA was expecting and can handle getting multiple MSDUs contained in an A-MSDU. However, since such a STA has negotiated the use of A-MSDU for transmission to it, and the limits on such use, it seems reasonable that those same limits would be workable for the STA while in power save. Thus, the proposal is to accept this change. Proposed Resolution: ACCEPTED. Can we just use “BU” instead? No proposed resolution, yet: CID Page Clause Comment Proposed Change 7146 Stephens, Adrian 134.10 5.1.5.1 A role-specific behaviour is not shown for a DMG relay. If security on a DMG relay is established for each leg of the relay, then the data-flow must pass through the controlled port, and therefore be shown in the role-specific behaviour. Determine whether to show a role-specific behaviour for a DMG relay, which would be similar to a mesh STA. 7150 Stephens, Adrian 3581.01 Annex N Annex N contains terminology that is unique to itself, such as WLAN system and ACM_STA. The understanding of what a DS is has developed and change in the ARC standing committee, resulting in changes to Clause 5. Annex N has been ignored. Review Annex N and change terminology and architecture to conform to the normative portions of the draft. 7069 Stephens, Adrian 854.62 9.4.2.31 " An incoming MSDU that is not classified to a particular TS may be classified to another active TS based on the frame classifier for that TS." - normative verb in clause 9 Move normative behaviour to clause 10/11.
11-16-0290-02-000m-resolutions-for-some-comments-on-11mc-d5-0.docx