IEEE P802.11 Wireless LANs SB0 resolution to misc comments Date: 2015-12-07 Author(s): Name Affiliation Address Phone email Zander Lei Institute for Infocomm Research (I2R) 1 Fusionopolis Way #21-01 Connexis Singapore 138632 +65 6408 2436 leizd@i2r.a-star.edu.sg Interpretation of a Motion to Adopt A motion to approve this submission means that the editing instructions and any changed or added material are actioned in the TGah Draft. This introduction is not part of the adopted material. Editing inst ructions formatted like this are intended to be copied into the TGah Draft (i.e. they are instructions to the 802.11 editor on how to merge the text with the baseline documents). TGah Editor: Editing instructions preceded by “TGah Editor” are instructions to the TGah editor to modify existing material in the TGah draft. As a result of adopting the changes, the TGah editor will execute the instructions rather than copy them to the TGah Draft. Clause 8.4.2.6 and 8.6.5 (4 CIDs) Pg. Ln Comment Proposed Change Resolution The number of different ways of encoding a block is completely over the top. Assuming these are all mandatory modes, it adds unnecessary complexity to what are supposed to be simple devices. Delete the "inverse bitmap" bit and related behaviour. Delete the ADE mode and related behaviour. Rejected. 11ah needs to support very different use cases, e.g., sensors and data offloading. TIM has to be encoded efficiently in different scenarios where the adopted TIM Hierarchical Structure allowing 4 modes to address the issue effiecintly. Details can be found in 11-12/388r2. In addtion, “inverse bitmap” increases marginal complexity and ADE mode is not a mandatory mode. I 0
132 BAT ADDBA Request 133 BAT ADDBA Response 134 BAT DELBA 134135-255 Reserved Instruction to TGah editor: Please replace 8.6.5.2 (ADDBA Request frame format) of TGah D5.0 with the following: 8.6.5.2 ADDBA Request frame format Change the 1st three paragraphs of sub-clause 8.6.5.2: An ADDBA Request frame is sent by an originator of block ack to another STA. There are three types of ADDBA Request frame, i.e. basic ADDBA Request frame, NDP ADDBA Request frame, and BAT ADDBA Request frame, and they share the same frame format. The Action field of an ADDBA Request frame contains the information shown in Table 8-287 (ADDBA Request frame Action field format). The Category field is defined in 8.4.1.11 (Action field). The Block Ack Action field is different for a different type of ADDBA Request frame. It is set to 0, 128, or 132 to represent an ADDBA Request frame, an NDP ADDBA Request frame, or a BAT ADDBA Request frame respectively. The field value and meaning for each value is described in 8.6.5.1 (General). Instruction to TGah editor: Please make the following changes in the clauses 8.6.5.3 (ADDBA Response frame format) of TGah D5.0: 8.6.5.3 ADDBA Response frame format Change the third paragraph of sub-clause 8.6.5.3: Change the 1st three paragraphs of sub-clause 8.6.5.2: The Block Ack Action field is set to 1, 129, or 133 (representing ADDBA response). The meaning for each value is described in 8.6.5.1 (General). The ADDBA Response frame is sent in response to an ADDBA Response frame. There are three types of ADDBA Response frame, i.e. basic ADDBA Response frame, NDP ADDBA Response frame, and BAT ADDBA Response frame, and they share the same frame format. The Action field of an ADDBA Response frame contains the information shown in Table 8-288 (ADDBA Response frame Action field format).