doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK1 Measurement Comment Resolution Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. Date:

doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK2 Abstract This document is to provide comment resolution for TGv Internal Review comment 257, 258, 259, 260, 261 and 263. The normative text for this comment resolution is 07/2126r0.

doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK3 CID 257,258 Comments –Dot11RetryCount, dot11MultipleRetryCount, dot11FrameDuplicateCount, dot11RTSFailureCount and dot11ACKFailureCount correspond to the group identity of 1. But, dot11FailedCount and dot11FCSErrorCount correspond to the group identity of 0. If Triggered Reporting has consist of dot11FailedCount Threshold and dot 11RetryCount Threshold, which value is set to the group identity? It seems that STA Counters Trigger in Figure v1 should be divided into two categories according to the Group Identity. –It seems that the size of STA Counter Trigger Condition field should be 1 byte, when I compare the Reporting Reason field in Figure v9.

doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK4 CID 257,258 Resolutions –Change Figure v1, Figure v2 and Figure v8 –Insert the following into lines 14 – 16, page 3 “When the group identity of the triggered STA Statistics request is set to 0, B2 – B6 in the STA Counter Trigger Condition field shall be set to 0. And, when the group identity of the triggered STA Statistics request is set to 1, B0 and B1 in the STA Counter Trigger Condition field shall be set to 0.”

doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK5 CID 259,260,261 Comments –Please change the size of RSNA Trigger Condition field to 1 byte. –As the dot11RSNAStatesTKIPHdrErros is modified in the TGW ( w-lb88-comment-resolution), please also exchange it to dot11RSNAStatsRobustMgmtCCMPReplays. Also, please include the dot11RSNATKIPICVErrors, dot11RSNAStatsCCMPDecryptErrors, dot11RSNAStatsCCMPReplays, dot11RSNSStatsTKIPReplays. –Please the size of Reporting Reason field for RSNA Counters change from 2 bytes to 1 bytes.

doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK6 CID 259,260,261 Resolutions –Change Figure v5, Figure v6, Figure v7, Figure v10 and Table 31b –Delete lines 4 – 6, page 7 –Insert the following into lines 10 – 25, page 7 The dot11RSNAStatsRobustMgmtCCMPReplays Threshold field contains a value representing the number of discarded MPDUs to be used as the threshold value for the dot11RSNAStatsRobustMgmtCCMPReplays. This field is present when the dot11RSNAStatsRobustMgmtCCMPReplays bit-field in the RSNA Trigger Condition field is set to 1. The dot11RSNAStatsTKIPICVErrors Threshold field contains a value representing the number of discarded MPDUs to be used as the threshold value for the dot11RSNAStatsTKIPICVErrors. This field is present when the dot11RSNAStatsTKIPICVErrors bit-field in the RSNA Trigger Condition field is set to 1. The dot11RSNAStatsTKIPReplays Threshold field contains a value representing the number of discarded MPDUs to be used as the threshold value for the dot11RSNAStatsTKIPReplays. This field is present when the dot11RSNAStatsTKIPReplays bit-field in the RSNA Trigger Condition field is set to 1. The dot11RSNAStatsCCMPDecryptErrors Threshold field contains a value representing the number of discarded MPDUs to be used as the threshold value for the dot11RSNAStatsCCMPDecryptErrors. This field is present when the dot11RSNAStatsCCMPDecryptErrors bit-field in the RSNA Trigger Condition field is set to 1. The dot11RSNAStatsCCMPReplays Threshold field contains a value representing the number of discarded MPDUs to be used as the threshold value for the dot11RSNAStatsCCMPReplays. This field is present when the dot11RSNAStatsCCMPReplays bit-field in the RSNA Trigger Condition field is set to 1.

doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK7 CID 263 Comments –It seems that Triggered Statistic Request/Report should also support the QoS STA Counters.

doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK8 CID 263 Resolutions –Insert page 4 and page 5 –Insert Figure v9

doc.: IEEE /2175r0 Submission July 2007 Yongho SEOK9 Motion Move to modify the TGv draft 0.13 according to the normative text in document v-measurement-comment- resolution.doc Mover: Seconder: Result: