primitive:" -- OK, and how can the MLME determine the to deliver to the SME? 56 11.46 This "Estimated Delete "Entities Revise TGax – 0 Throughput" is outside the scope editor to make intended to be useful of this standard that changes as shown for controlling traffic might control the in 11-17/1192r3 decisions. It does traffic steering that are marked specify how a STA can decision of a device with CID 56 slight – inform another STA of benefitby being modifications to the traffic estimates but I able to predict the wording have been am not convinced that throughput that made to reduce the this is of any use for might be obtained expressed level of what it supposed to through a link with certainty of the address. By stating at a STA. Those statements as L51 and L53 that same entities also opposed to the these outside entities need to know what wholesale deletion "need to know the the current proposed by the current estimates" we estimate of commenter, based are open to questions throughput is for on the fact that of accuracy and 'how network selection existing systems do to use'. I suggest that purposes (by use parameters these statements are comparing an similar to those removed. estimated listed to make the throughout with decisions described existing in the cited text. throughout)." The commenter intends to bring a related presentation. 55 11.46 Huge paragraph at "If the MLME is Revise TGax – P2049 L13 is in fact incapable of editor to make quite simple", but is determining a value changes as shown repeated for each for the in 11-17/1192r3 parameter and hence that are marked becomes diffivult to or with CID 55 comprehend. If the MLME is incapable of determining a vale for parameter for any access category, it simply returns a 0. If then the MLME the AverageMSDU shall return a value size in the of for the value of that parameter for that access primitive is -1, then category in the the corresponding the primitive. If the primitive is 0. If the or AverageMSDU size is
primitive:" -- OK, and how can the MLME determine the to deliver to the SME? 56 11.46 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. 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)." The commenter intends to bring a related presentation. Revise – TGax editor to make changes as shown in 11-17/1192r3 that are marked with CID 56 – 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. 55 11.46 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 "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 Revise – TGax editor to make changes as shown in 11-17/1192r3 that are marked with CID 55
11-17-1192-03-000m-cr-esp.docx