to the VHT-SIG-A “If indicates an unsupported mode, the PHY shall set issue PHY_RXSTART.ind (RXVECTOR) then PHY shall issue the error condition 4122 Adrian 267.57 22.3.21 The PMD interface is 1. Add a new PMD Rejected. inadequate to receive an request: MU PPDU. Precedence in Clause with 18 (802.11a) and For the PMD to parameters MCS, Clause 20 (802.11n) demodulate a symbol START_STS, is that the PMD has and extract the NUM_STS (Add to appropriate user's data table 22-62 and new the information from requires that it subclauses 22.6.5.x). the signal field, e.g. understand which of the 2. Update 22.3.21 and Rate or MCS. No STS to demodulate, figure 22-28 showing new PMD request is and which user-specific generation of this necessary. MCS to expect. primitive in "Setup PSDU RX". However, this information is held in the signal fields, which are comprehended only in the PLCP. Discussion: The purpose of an architecture is and conquer” by dividing a behaviour into smaller pieces with “divide – well, documented interfaces, the individual pieces are simpler. The implication of this resolution is that we have two receive state machines: A State machine that is in the PLCP it interfaces between the PMD and MAC-SAP it’s operation is described in text and figures A machine in the PMD It interfaces between the PLCP and the hardware it’s operation is not described anywhere it is of more-or-less equivalent complexity to the PLCP state machine because it is required to detect the different types of signal field in order to decode their contents, which are used to determine how to interpret the rest of the packet. Such an implication is an indictment of our architecture i.e., it has failed to provide the necessary – simplifications.
to “If the VHT-SIG-A indicates an unsupported mode, the PHY shall set issue PHY_RXSTART.ind (RXVECTOR) then PHY shall issue the error condition 4122 Adrian 267.57 22.3.21 The PMD interface is inadequate to receive an MU PPDU. For the PMD to demodulate a symbol and extract the appropriate user's data requires that it understand which of the STS to demodulate, and which user-specific MCS to expect. However, this information is held in the signal fields, which are comprehended only in the PLCP. 1. Add a new PMD request: with parameters MCS, START_STS, NUM_STS (Add to table 22-62 and new subclauses 22.6.5.x). 2. Update 22.3.21 and figure 22-28 showing generation of this primitive in "Setup PSDU RX". Rejected. Precedence in Clause 18 (802.11a) and Clause 20 (802.11n) is that the PMD has the information from the signal field, e.g. Rate or MCS. No new PMD request is necessary. Discussion: The purpose of an architecture is “divide and conquer” – by dividing a behaviour into smaller pieces with well, documented interfaces, the individual pieces are simpler. The implication of this resolution is that we have two receive state machines: A State machine that is in the PLCP it interfaces between the PMD and MAC-SAP it’s operation is described in text and figures A machine in the PMD It interfaces between the PLCP and the hardware it’s operation is not described anywhere it is of more-or-less equivalent complexity to the PLCP state machine because it is required to detect the different types of signal field in order to decode their contents, which are used to determine how to interpret the rest of the packet. Such an implication is an indictment of our architecture – i.e., it has failed to provide the necessary simplifications.
11-12-0503-00-00ac-lb187-clause-22-3-21-pmd-comment-resolutions.docx