MDA Comments 1 Date: 2008-05-05 Authors: September, 2008 Feb, 2008 doc.: IEEE 802.11-07/xxxx September, 2008 MDA Comments 1 Date: 2008-05-05 Authors: Dee Denteneer, Philips Liwen Chu, STMicroelectronics

Resolve a number of CIDs on MDA September, 2008 Resolve a number of CIDs on MDA CIDs: 368, 586, 633, 745, 1386, 1387, 1536, 1805, 1806, 1807, 1815, 1882, 338, 339, 587, 589, 591, 1039, 1308, 1485, 387, 1822, 1847 Normative text: IEEE 802.11-08/1104r0; the excell sheet describing the comment resolution is 1105. Dee Denteneer, Philips

September, 2008 CIDs 368, 586, 633, 745, 1386, 1387, 1536, 1805, 1806, 1807, 1815 Minor edits of text requested Some other typos corrected Dee Denteneer, Philips

CID 1882 "All MDA supporting MPs" - this is imprecise September, 2008 CID 1882 "All MDA supporting MPs" - this is imprecise Relate to MIB variable or OTA signalling As suggested Dee Denteneer, Philips

September, 2008 CID 338, 339 "MDAOP setup, MP5: M", this is inconsistent with the statement that MDAOP is an optional feature" Rejected, as “The MDA concept remains optional. However, if implemented MDA has some mandatory parts.” Dee Denteneer, Philips

September, 2008 CID 587, 589, 591, 1039, 1308, 1485 E.g. 1485: “MDAOP" is not adquately defined. Define it to be the last 4 fields in fig s23, or better, create a new fig and rpeat the field definitions” Dee Denteneer, Philips

Figure xx -- MDAOP Reservation field MDAOP Setup Request element September, 2008 CID 587, 589, 591, 1039, 1308, 1485 Remedy: Have introduced a MDAOP field, as suggested, see new Clause 7.3.1.36 MDAOP Duration MDAOP Periodicity MDAOP Offset   1 2 Figure xx -- MDAOP Reservation field Element ID Length MDAOP Reservation ID MDAOP Reservation   Octets: 1 1 4 MDAOP Setup Request element Dee Denteneer, Philips

Figure xx -- MDAOP Reservation field September, 2008 MDAOP Duration MDAOP Periodicity MDAOP Offset   1 2 Figure xx -- MDAOP Reservation field Dee Denteneer, Philips

September, 2008 CIDs: 387, 1822, 1847 “The duration of MDA TXOPs must be determined beforehand, which is not possible.” Section 9.9.1.2 („EDCA TXOPs“) in 802.11-2007 allows a station to transmit multiple frames within a single TXOP. However, the station shall not exceed its TXOPlimit. Thus, the standard already describes a mechanism that requires a station to calculate the frame transmission duration in advance (that is before transmitting the frame). Furthermore, the standard even requires the station to consider the response frame in its calculation as well. Additionally, section 9.9.3.1 („Contention-based admission control procedures“) describes a procedure where a station decides in advance whether it may transmit or not. To do so, the station maintains two counters “admitted_time“ and „used_time.“ Based on these counters and the frame transmission duration that the station predicts, it decides whether it may transmit or not. In summary, 802.11-2007 already describes two different mechanisms that require an STA to calculate the duration of a frame transmission in advance. Therefore, MDA does not require anything particularly new. Dee Denteneer, Philips