1065 Emily Qi "The Data PPDU Duration Target field is 8 bits in length and is an unsigned integer that indicates the expected target duration of PPDUs". How to derive "the expected target duration of PPDUs"? If it is not specified, how do we know the estimated throughput from different AP vendors are comparable? Specify it. Revise - TGmd editor to make changes as shown in that are marked with CID 1065. These changes note that the algorithm to determine this value is beyond the scope of the standard and explain that because the STA transmitting the value of the field is the same STA that would be transmitting the PPDUs, it would be expected that that STA could maintain the promised duration value by modifying transmission parameters as needed for that purpose. 1149 Fischer 11.44 "When an primitive is received at the MLME, the MLME can use the parameters provided in the primitive plus the following information to create estimates of throughput per access category to deliver to the SME in the parameter of the primitive:" -- OK, and how can the MLME determine the to deliver to the SME? CCCID259 Add an equivalent para for Revise – TGmd editor to make changes as shown in that are marked with CID 1149. These changes effect the requested change and add a new MIB variable for Outbound and split the functionality of STAs, allowing them to support any combination of ESP Inbound, ESP Outbound. EstimatedThroughput
1150 Fischer 11.44 This "Estimated Throughput" is intended to be useful for controlling traffic decisions. It does specify how a STA can inform another STA of traffic estimates but I am not convinced that this is of any use for what it supposed to address. By stating at L51 and L53 that these outside entities "need to know the current estimates" we are open to questions of accuracy and 'how to use'. I suggest that these statements are removed. CCCID56 Delete "Entities outside the scope of this standard that might control the traffic steering decision of a device benefitby being able to predict the throughput that might be obtained through a link with a STA. Those same entities also need to know what the current estimate of throughput is for network selection purposes (by comparing an estimated throughout with existing throughout)." Revise – TGmd editor to make changes as shown in that are marked with CID 1150 – slight modifications to the wording have been made to reduce the expressed level of certainty of the statements as opposed to the wholesale deletion proposed by the commenter, based on the fact that existing systems do use parameters similar to those listed to make the decisions described in the cited text. 1151 Fischer 11.44 Huge paragraph at P2049 L13 is in fact quite simple", but is repeated for each parameter and hence becomes diffivult to comprehend. If the MLME is incapable of determining a vale for it simply returns a 0. If the AverageMSDU size in the primitive is -1, then the corresponding the primitive is 0. If the AverageMSDU size is 0, then the correspondoing EstimatedThroughput is calculated using any size but recommends 1500B. Can we try to write it simpler? CCCID55 "If the MLME is incapable of determining a value for the or parameter for any access category, then the MLME shall return a value of 0 for the value of that parameter for that access category in the primitive. If the or parameter for an access category is equal to -1 in the primitive, the STA shall include a value of 0 in the respective or Revise – TGmd editor to make changes as shown in that are marked with CID 1151. These changes break up the paragraph, but do not make the other changes suggested.
measurements, there is no reason why we need to stick to +/- 5dB we should be making a target of 1dB. As many will know I have been advocating the DSC mechanism that uses the Beacon RSSI. As such an algorithm for determining the Beacon RSSI has been presented that accounts for a mobile STA, missed beacons etc. but uses the Beacon RSSI to adjust effective CCA thresheld. This is a good use for Beacon RSSI but even if DSC is adopted there is still no need to have this seperate Clause. CCCID54 experts did not agree that a more accurate value was possible and useful output is generated in real systems with an accuracy estimated to be about 5dB. Commenter can review equation R-2 of Annex R.7 P3801 to see where RSSI is used, noting that in the earliest implementations, a simple comparison of RSSI is often employed rather than a calculation such as is described in R.7. 1153 Fischer "The Estimated Air Time Fraction subfield is 8 bits in length and contains an unsigned integer that represents the predicted percentage of time, linearly scaled with 255 representing 100%, that a new STA joining the BSS will be allocated for that contain only MPDUs with the Type subfield equal to Data of the corresponding access category for that STA." "Allocated"? So the STA is using HCCA, or EDCA Admission Control? What scheme is in use here that we have allocation of BW to specific STAs, and traffic? In addition, what is %, the fraction of all traffic or fraction of just that AC traffic? This is unclear, but why have this for every AC and how is this to be interpreted? Also Replace cited with "The Estimated Air Time Fraction subfield is 8 bits in length and contains an unsigned integer that represents the predicted percentage of time, linearly scaled with 255 representing 100%, not used by PPDUs that contain only MPDUs with the Type subfield equal to Data, of the corresponding access category." Revise – TGmd editor to make changes as shown in that are marked with CID 1153. These changes improve the wording, similar to the requested changes.
unclear how an AP would even measure this. I am generally unhappy with this, I might make a presentation. CCCID31 1154 Fischer "The Estimated Air Time Fraction subfield is 8 bits in length and contains an unsigned integer that represents the predicted percentage of time, linearly scaled with 255 representing 100%, that a new STA joining the BSS will be allocated for PPDUs carrying Data of the corresponding AC for that STA." -- if you look at R.7 it turns out that this is exactly the time for the PPDUs, not including any contention/IFS time. This is a very subtle point (and differs from e.g. admission control) CCCID212 Change the cited text to "The Estimated Air Time Fraction subfield is 8 bits in length and contains an unsigned integer that represents the predicted percentage of air time (so not including interframe space), linearly scaled with 255 representing 100%, that a new STA joining the BSS will be allocated for PPDUs carrying Data of the corresponding AC for that STA (so not including any Management or Control frames)." Revise – TGmd editor to make changes as in 11-17/1192r21 that are marked with CID 1154. These changes add a "beyond the scope of this standard" language that says the computation should include efficiency scaling. 1155 Fischer R.7 The equation for PPDU_Dur extremely pedantically accounts for symbol rounding ... and then completely fails to account for delimiters. It also includes the PHY header but not the PHY trailer (e.g. signal extension) CCCID213 At the end of the referenced subclause add a "NOTE---The equations do not account for e.g. A-MPDU delimiters and signal extension." Revise – TGmd editor to make changes as shown in that are marked with CID 1155, which adds a minimum delimiter count of 4 octets to the PPDUDur equation, and adds a note that indicates that signal extension is not accounted for.
1156 Fischer R.7 The equation for PPDU_Dur assumes A-MSDUs can be included in A-MPDUs, but this will only happen if both sides support it CCCID214 At the end of the referenced subclause add a "NOTE---The equations above assume that are included in Revise – TGmd editor to make changes as shown in that are marked with CID 1156, which qualifies the definitions of A_MSDU_BTX and A_MSDU_BRX to account for the case of no A-MSDU aggregation. 1157 Fischer R.7 PPDU_Dur "is the expected duration of a single PPDU, in seconds". DPDUR "is the Data PPDU duration target of the transmitter of the PPDUs containing MPDUs with the Type subfield equal to Data, in seconds". Given the equation, PPDU_Dur is also only for PPDUs with Data MPDUs. So PPDU_Dur is the same thing as DPDUR CCCID215 Delete the definition of PPDU_Dur and then change PPDU_Dur to throughout the referenced subclause Revise – TGmd editor to make changes as shown in that are marked with CID 1157 which makes a reference to the Data PPDU Duration Target subfield of the ESP element, while noting that the two terms cited by the commenter, PPDU_Dur and DPDUR are not the same thing. DPDUR is the target duration, but PPDU_Dur is the actual duration which can be limited at high data rates by aggregation limits, for example. 1158 Fischer R.7 "Note that some of the parameters of Equation (R-2) have values that are AC dependent." -- er, which? None of them have any dependency on the AC CCCID216 Delete the cited sentence Accept
1159 Fischer R.7 It is claimed that one can determine and for each AC of a current or potential link to another STA Equation (R-1)", but Equation (R-1) refers to EST_AirtimeFraction, which is defined as " the estimated portion of airtime that is available for outbound transmissions", so does not work for inbound traffic CCCID217 Delete and" in R.7. At the end of R.7 add a para "The mechanism by which ESP STAs determine values for is outside the scope of the standard." Revise – TGmd editor to make changes as shown in that are marked with CID 1159, which generally agree with the nature of the comment, but resolve it by adding language for Inbound describing a method for estimating the inbound traffic. 1160 Fischer R.7 The equation for PPDU_Dur extremely pedantically accounts for symbol rounding ... and then completely fails to account for delimiters. It also includes the PHY header but not the PHY trailer (e.g. signal extension) CCCID251 Add the overhead (delimiter and rounding) for MPDUs in an Also add a term for the PHY trailer Revise – TGmd editor to make changes as shown in that are marked with CID 1160, which adds a minimum delimiter count of 4 octets to the PPDUDur equation, and adds a note that indicates that signal extension is not accounted for. 1368 Mark RISON R.7 "Note that some of the parameters of Equation (R-2) have values that are AC dependent." -- none of them do Delete the cited text in the referenced location Accept 5