Agenda, from E-Mail Notice

September 2008 doc.: IEEE 802.11-08/0979r3

IEEE P802.11 Wireless LANs

TGv Teleconference and Ad-Hoc Minutes August, September 2008

Date: 2008-09-02

Author(s): Name Affiliation Address Phone email Dorothy 1332 Crossman Ave Aruba Networks +1-630-363-1389 dstanley@arubanetwo Stanley Sunnyvale, CA 94089 rks.com

Abstract This document contains the meeting notes from the TGv teleconference held August 12 th, August 26th, 2008, September 2nd, and the ad-hoc meeting held August 18-20, 2008.

Submission page 1 Dorothy Stanley (Aruba Networks) September 2008 doc.: IEEE 802.11-08/0979r3

August 12, 2008 Teleconference

Agenda, from e-mail notice:

1. Call to Order, Patent Notification 2. Editor Update 3. Comment Resolution - Multicast Diagnostics, TIM Broadcast 4. Ad-Hoc meeting planning 5. Adjourn

Please review the documents at the following links prior to the call:

- IEEE Patent Policy - http://standards.ieee.org/board/pat/pat-slideset.ppt - Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html - Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf - Ethics - http://www.ieee.org/portal/cms_docs/about/CoE_poster.pdf

Notes – Tuesday, August 12th, 2008

Attendees: Alex Ashley, Emily Qi, Dorothy Stanley, Allan Thomson, Qi Wang

1. Chair called meeting to order: 12:05 Eastern

Chair called attention to the patent policy slides. Are there any questions on the slides? None

Chair asked: Are there any patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) that the participant believes may be essential for the use of that standard? None brought forward

Any additions to the proposed agenda? No changes proposed.

2. Editor’s report.

Emily is working on incorporating the editorial comments, and is targeting to have Draft 3.01 with all of the editorial comment resolutions incorporated, in time for the ad-hoc meeting next week.

3. Comment resolutions

Alex reviewed the Multicast Diagnostics comments, see https://mentor.ieee.org/802.11/file/08/11-08-0889-01-000v-lb133-comments-multicast-diagnostics.xls https://mentor.ieee.org/802.11/file/08/11-08-0954-00-000v-proposed-resolution-to-lb133-cid-17.doc

• CID 17- agree with proposed resolution • CID 18 - agree with proposed resolution • CID 48 - agree with proposed resolution • CID 52 - agree with proposed resolution • CID53, 1281 - agree with proposed resolution, minor grammar fix, move text as indicated in comment. • CID 79 - agree with proposed resolution • CIDs 335, 336 – Need clarification from the commenter, Alex to ping Bill. Post meeting update: comments withdrawn by the commenter. • CID 379 - agree with proposed resolution Submission page 2 Dorothy Stanley (Aruba Networks) September 2008 doc.: IEEE 802.11-08/0979r3

• CID 380, 382, 743, 744 – Discussion on whether the multicast diagnostic should requested/reported as part of the Measurement Request/Report (802.11-2007) or Radio Measurement Request/Report. Only difference is number of repetitions in the request. Agreed to change to “accept”, indicate Radio Resource measurement throughout, check if additional text needed in clause 11 re: number of repetitions. • CID 381 - agree with proposed resolution • CID 595 - agree with proposed resolution • CID 596 - agree with proposed resolution • CID 613 – Change to “accept” • CID 634 - agree with proposed resolution • CID 719 - agree with proposed resolution • CID 720 - agree with proposed resolution • CID 721 - agree with proposed resolution • CID 722 - agree with proposed resolution • CID 723 - agree with proposed resolution • CID 724 – Change to “accept”, make sure category 380 comments are consistent • CID 725 - agree with proposed resolution • CID 726 - agree with proposed resolution • CID 1221 - agree with proposed resolution • CID 1258 – Defer for now, and discuss at the ad-hoc. Alex proposes to “accept” as spec includes signalling that enables the feature to be supported. • CID 1301 - agree with proposed resolution • CID 1397 - agree with proposed resolution Alex will upload a revised spreadsheet, incorporating the agreed changes. Have 3 CIDs remaining, 335, 336 and 1258. Post meeting update: 335 and 336 withdrawn by the commenter.

One other multi-cast diagnostic text change is proposed, not related to any submitted comment, please review https://mentor.ieee.org/802.11/file/08/11-08-0963-01-000v-all-groups-multicast-diagnostics- request.ppt . We’ll discuss in Hawaii.

Discussion on Proxy ARP category CID 1322. - need to check the RFC, confirm if ARP request frames are always broadcast, and response frames are unicast – Alex. - Add text to clarify that the translation table is kept only for associated stations.

4. Agenda for August 18-19-20 Ad-hoc meeting, Santa Clara

We discussed the agenda for next week’s ad-hoc meeting, see below for the planned times. We will adjust further as needed. Known ad-hoc attendees to date are Emily, Allan, Dorothy, Qi, Moo-Ryong, and Ganesh.

Monday AM – Location, FBMS Monday PM – Timing Measurement, STA Statistics, TCLAS, Roaming Management Tuesday AM – Channel Usage, TFS, Sleep Mode Tuesday PM – General, Diagnostics Wednesday AM – Traffic Generation Wednesday PM – Virtual AP

August 26th con call – Collocated Interference, TIM Broadcast

5. Adjourn at 13:45 Eastern.

August 18-20, 2008 Ad-hoc

Monday AM – Location, FBMS Monday PM – Timing Measurement, STA Statistics, TCLAS, Roaming Management Tuesday AM – Channel Usage, TFS, Sleep Mode Tuesday PM – General, Diagnostics Wednesday AM – Traffic Generation Wednesday PM – Virtual AP

Notes – Monday, August 18th, 2008

Attendees: Emily Qi, Dorothy Stanley, Allan Thomson, Ganesh Venkatesan, Qi Wang

1. Chair called meeting to order: 9:45am Pacific

Allan reviewed the Location comments, see https://mentor.ieee.org/802.11/file/08/11-08-0897-00-000v-lb133-comments-location.xls and https://mentor.ieee.org/802.11/file/08/11-08-0946-00-000v-normative-changes-location-d3.doc .

• CID 601, 1303- agree with proposed resolution, include resolution text • CID 602 - agree with proposed resolution • CID 327 - agree with proposed resolution • CID 328, 1304 - agree with proposed resolution, include reference • CID 1215 - agree with proposed resolution • CID 137, 312 - agree with proposed resolution • CID 143 – Change to decline, add reason – ES bits indicate only location. • CID 612 - agree with proposed resolution • CID 1302, 144, 76 – Discussion: How is error data populated? Is configurated, must be converted to this, we don’t specify how. Agree with proposed resolution, minor edits to include full field names. • CID 636 – Fixed in Draft 3.01. • CID 274, 347, 23, 662 – agree with proposed resolution • CID 325 - agree with proposed resolution, minor change to the reason. Submission page 4 Dorothy Stanley (Aruba Networks) September 2008 doc.: IEEE 802.11-08/0979r3

• CID 203 – Change to counter, length is “16” • CID 115 - agree with proposed resolution, add that reference is corrected. • CID 663 – Agree with proposed resolution • CID 664, 666, 665, 1230 - agree with proposed resolution • CID 668 - agree with proposed resolution, minor change to included text, added note to editor. • CID 669, 670, 187, 119, 686, 687, 1233 - agree with proposed resolution • CID 690 - agree with proposed resolution, also Event, Diagnostics and TIM Broadcast. • CID 716, 717, 718 - agree with proposed resolution • CID 1249 - agree with proposed resolution, some wording changes. • CID 1250, 1251, 1252, 1253 - agree with proposed resolution • CID120 - agree with proposed resolution, edits to text in 946r1 • CID 1254 – Defer – Henry and Allan to investigate further, public action filtering concern. • CID 55, 1270, 1255 - agree with proposed resolution • Clause 12, 15, 17 and 20 – comments have been agreed with reviewers, except for CIDs 263, 259, 266, 262, 264, 265, 260, leave those as deferred • CID 1260, 1259, 1261, 1262, 1263, 286, 597, 598, 599, 600, 138, 139, 145, 1393 - agree with proposed resolution • CID 1367 – Defer, Qi to check with commenter.

Allan reviewed the FBMS comments, see https://mentor.ieee.org/802.11/file/08/11-08-0898-00-000v-lb133-comments-fbms.xls .

• CID 106, 197, 1218, 88 – agree with proposed resolution • CID 7 – Change to counter, see CID 1288 • CID 1288, 1336, 672, 673, 674, 30, 676, 675, 31, 78, 350 - agree with proposed resolution • CID 351 – Defer, need to discuss TCLAS length • CID 32, 678, 33 - agree with proposed resolution • CID 352 – Decline, reason codes are specific to FBMS • CID 679 – Change to Counter • CID 80, 35, 680, 352, 45, 694, 695, 696, 697, 168, 698, 699, 700, 701, 702, 703, 84, 86, 704, 1277, 46 - agree with proposed resolution • CID 167 – Diescussion – Informative notes helpful to implementers. Don’t include for other features. Casts FBMS in a negative light. Reword in a neutral way, agreed to text, delete 2nd note. • CID 1276 - agree with proposed resolution • CID 1275 – Agree with commenter’s second approach, to enable station to indicate acceptable range. Allan to generate text. Defer for now. • CID 1340 - agree with proposed resolution • CID 1279 - agree with proposed resolution • CID 190 – Same as CID 1279 • CID 366 – Change to counter, add reference to 9.2.7.2 • CID 367 – Change to counter, add sentences • CID 47, 707 - agree with proposed resolution • CID 1240 - agree with proposed resolution, slight text changes • CID 1241, 127, 708, 709, 710, 183, 59, 184, 1400, 1414 - agree with proposed resolution

Ganesh reviewed the Timing Synchronization proposed text changes, continuing from the Denver meeting discussion. Believe that this text will address all of the timing measurement related comments. See https://mentor.ieee.org/802.11/file/08/11-08-0891-00-000v-timing-measurement.ppt and https://mentor.ieee.org/802.11/file/08/11-08-0842-00-000v-normative-text-for-timing-measurement.doc .

Discussion: - There is an alternate solution that has been proposed for timing measurement, using beacon frames. Ganesh is preparing a presentation describing the alternative, and the issues with it,

including the need for hardware support for statistical processing, and lack of symmetry between non-AP STAs and APs. - The solution in 08-891 uses management action frames rather than public action frames, since the frames are exchanged only between APs and associated stations. - MIB variable definitions need changes to index by MAC address, also need text to describe use of MIB variables. - Are using Time of departure solution for both location and timing measurement. Need text to clarify that the accuracy required for the 2 applications is different. - No additional annex changes are needed. - Next steps, get additional review from commenters, and prepare the corresponding comment resolutions.

Ganesh reviewed the proposed resolutions for the STA Statistics category comments, see: https://mentor.ieee.org/802.11/file/08/11-08-0956-00-000v-lb133-tclas-sta-statistics-resolutions.xls and https://mentor.ieee.org/802.11/file/08/11-08-0966-00-000v-lb133-tclas-sta-statististics-normative-text.doc

• CID 12, 14, 49, 110, 155, 157, 199 - agree with proposed resolution • CID 375 – Change to counter, add a sentence to deal with the case of when the STA trigger limit is greater than that requested by the AP. • CDI 635 – Change to accept • CID 715 – agree with proposed resolution • CID 1222 – Same as CID 199 • CID 1242 – Agree, delete duplicate resolution • CID 1283 - agree with proposed resolution • CID 1243 - agree with proposed resolution, slight wording edits • CID 1297 - agree with proposed resolution, slight wording change • CID 1300 - agree with proposed resolution • CID 1415 – Defer, investigate needed .11n triggers; Have considered adding A-MPDU and A- MPDU measurements previously, not added, since already have MSDU and MPDU triggers.

Ganesh reviewed the proposed resolutions for the TCLAS category comments, see: https://mentor.ieee.org/802.11/file/08/11-08-0956-00-000v-lb133-tclas-sta-statistics-resolutions.xls and https://mentor.ieee.org/802.11/file/08/11-08-0966-00-000v-lb133-tclas-sta-statististics-normative-text.doc

• CID 337 – Counter, add a new classifier type for fixed IPv6 • CID 338 – Counter, insert Classifier Mask in Type 3, add text saying that the field is reserved. • CID 339, 637, 1305, 1306 - agree with proposed resolution • CID 1307 – Agree with proposed resolution to keep the example; example was added in response to previous comments. Ganesh to confirm that commenter can live with this. Defer for agreement confirmation. • CID 1308 – Agree on “counter”, Ganesh to agree on specific text with the commenter. Defer for agreement confirmation. • CID 1309 – Propose Accept, add anew classifier type 4, don’t restrict to specific protocols.

Agreed to start the Tuesday at 8:00am Pacific, as we will need to finish at 2:30pm on Wednesday.

Meeting Recessed at 5:00pm Pacific.

Attendees: Joe Kwak, Emily Qi, Dorothy Stanley, Allan Thomson, Qi Wang

Dorothy reviewed the General category comments, see https://mentor.ieee.org/802.11/file/08/11-08- 0841-01-000v-lb133-general-comments.xls .

• CID 99, 1310- agree with proposed resolution • CID 100 – declined, while a timeout could be added, the base spec and amendments generally don’t include one, for example Neighbor Report. • CID 183 – already done in FBMS • CID 224, 225, 226 – agree with proposed resolution • CID 235 – accepted, “Request Information” is one item added • Comment category 251 – Defer, management frame priority • CID 326, 329 - agree with proposed resolution • CID 331 – Counter. Channel usage element is deleted, traffic generation retained, as channel usage is not in the Beacon frame. • Comment category 365 – Change to counter, and insert one sentence in 11.20.1 to cover all cases. • CID 269 – Defer – Directed multicast presentation planned again in September • CID 400, Comment category 1274 – AP Collaboration. Proposed decline, with reason updated from prior comments. Would like to find a way forward. Concern with the complexity of the required infrastructure. • Comment category 401 – Discussion – Interpretation of PAR can be argued either way. Propose decline, add more detail on each of the features. Plan one motion for the category, of course motions will be considered as they are brought forward. • CID 1239 – Defer, Qi to propose text, plan to discuss on Aug 26th con call • CID 1257 – Defer, Qi to propose text, plan to discuss on Aug 26th con call • Comment category CID 1347 – Agree, slight wording changes.

Dorothy reviewed the remaining Diagnostics category comments, see https://mentor.ieee.org/802.11/file/08/11-08-0902-01-000v-lb133-diagnostics-text.doc and https://mentor.ieee.org/802.11/file/08/11-08-0901-01-000v-lb133-diagnostics-comments.xls . Most of the comments were reviewed in Denver. Remaining comments:

• CIDs 163, 227 – Deferred, Allan and Peter are the commenters and will propose a solution. Concern that the details requested are similar to ones rejected previously. • CIDs 309, 1229 – Counter, adopt text proposed by the commenter. • CIDs 1246, 1248 – Deferred. Further discussion needed to try to find a way forward. Discussion: See true value of a feature when all devices implement diagnostics. Want to be able to diagnose issues. Diagnostics used only for problems, or once upon association. Entire WNM is optional. Concern about diagnostics not being needed in consumer class devices. How does this benefit home networks? WFA will have a different view. Our job here is to give a recommendation. Implementations can choose to implement specifics or not.

There is one Annex category comment, CID 241. Proposed resolution: Counter, change Change from (CF8 & CF11 & CF13 & CF15):O to (CF8 & CF11 & CF13 & DSE5 & DSE6 & DSE7 & DSE8 & DSE9):O.

Emily reviewed the Channel Usage category comments, see https://mentor.ieee.org/802.11/file/08/11-08- 0985-00-000v-lb133-comments-channelusage.xls . Submission page 7 Dorothy Stanley (Aruba Networks) September 2008 doc.: IEEE 802.11-08/0979r3

• CID 63, 64, 186 – agree with proposed resolution • CID 68 – Change to Counter, CID 331 removed channel usage, CID 225 deleted Supported Regulatory classes. • CID 87 – Defer, Brian Hart to bring a presentation. • CID 89, 90 – agree with proposed resolution • CID 91 – Change to decline, algorithm is up to the station • CID 92 – Agree with proposed resolution • CID 93 – Decline, focus is on infrastructure. • CID 94 – agree with proposed resolution • CID 95 – change to decline with proposed resolution, addional reason • CID 96 – Agree with proposed resolution, additional reason. Other mechanisms are layer 3 and above and are not standardized. • CID 165 – Agree with proposed resolution • CID 234 – change to include 3 octet country string. Qi to confirm that Henry agrees. • CID 277 – agree with proposed resolution • CID 357 – Agree, delete last sentence of resolution • CID 603, 688 – Agree with proposed resolution • CID 1231 – Counter, include “IEEE 802.11” • CID 1292, 1293 – agree with proposed resolution

Emily reviewed the Sleep Mode category comments, see https://mentor.ieee.org/802.11/file/08/11-08- 0986-00-000v-lb133-comments-sleepmode.xls .

• CID 19 – agree with proposed resolution • CID 62 – agree with proposed resolution, clarification of exact sentence. • CID 104 – Counter, add additional sentence. • CID 111 – agree with proposed resolution • CID 112 – Decline, algorithm for determining when to enter sleep mode is unspecified, just as it is for existing power save mechanisms. • CID 113, 281 – Include proposed solution 1 in 281, add an additional statement that if TFS is not supported, then sleep mode must not be supported. • CID 114 – See text in 11.2.1, move sleep mode text to the power management section, to follow TIM broadcast. • CID 133 – Decline, Null data frame can be sent even when RSN is enabled, additional explanation of the capability. • CID 135, 136, 150, 169, 170, 171, 172, 185 – Agree with proposed resolution • CID 191 – Defer, name of feature discussion. • CID 279 – Counter, made field mandatory, set to 0 in the Response frame. • CID 280, 282 – Agree with proposed resolution • CID 283 – declined, do not to support delivery of group addressed frames at the sleep interval. • CID 293, 1377 – Decline, new GTK not yet in use, so previous one must be sent • CID 317 – accept, text changes to 11.20.16 • CID 354 – agree with proposed resolution • CID 397 – Defer, need clarification from the commenter. • CID 693 – Defer, need investigation • CID 681, 685, 691, 742, 1381 – Agree with proposed resolution • CID 692 – Change to counter, consolidate sentences.

Agreed to start the Wednesday at 8:00 am Pacific, as we will need to finish at 2:30pm.

Meeting recessed at 5:10pm.

Notes – Wednesday, August 20th, 2008

Attendees: Joe Kwak, Emily Qi, Dorothy Stanley, Allan Thomson, Qi Wang, Fujio Watanabe

We are subject to the IEEE Patent policy. We’ll discuss the event category comments today, as Virtual AP resolutions not completed.

August 26th conference call: Collocated Interference, Virtual AP, any other comments September 2nd conference call: Virtual AP, TIM Broadcast, any other comments

Joe reviewed the Event category comments, see https://mentor.ieee.org/802.11/file/08/11-08-0987-00- 000v-lb133-comments-event.xls.

• CID 330 – Change to counter, describes the type of authentication used in the RSNA • CIDs 606, 607, 608, 609, 610, 611, 644 – agree with proposed resolution • CID 1387 – Change to decline, see p 43, line 32. • CID 1324, 1224 – agree with proposed resolution • CID 1326 – Counter, additional text added to clarify address fileds • CID 200, 1225 – Counter, change from “operating channel” to “peer to peer channel” • CID 201, 1226 – Counter • CID 249 – decline, event vs diagnostics. Uses are somewhat different, “diagnostics” can be interpreted broadly or more narrowly, no functional benefit to making the change • CID 645 – agree with proposed resolution • CIDs 1332, 77, 340, 646, 1227, 1327, 1328 – Defer, Joe to prepare submisstion based on using RFC3339 format and the suggestion in CID 1328 • CID 341 – decline, reason codes specific to transition • CID 1329 – counter, add reason “low RSSI” • CID 647 – agree with proposed resolution • CID 97 – accept commenter’s rewording • CIDs 193, 255, 1405 – decline, add reasons why the TG has kept the syslog event report. Dorothy to provide previous motion results to add to the rationale, and e-mail the commenters. • CID 648, 179, 727, 728, 729 – agree with proposed resolution • CID 180, 181 – counter, added sentence • CID 383, 730, 731, 732 – agree with proposed resolution • CID 107 – counter, add text to clarify when an event is provided, and status is provided

Fujio reviewed Traffic Generation category comment resolutions, see https://mentor.ieee.org/802.11/file/08/11-08-0990-00-000v-lb133-traffic-generation.xls .

• CID 36, 71, 72, 73 – agree with proposed resolution • CID 196, 1217 – counter, slight wording changes • CID 247 – agree with proposed resolution • CID 394 – counter, refer to CID 246 • CID 246 – counter, remove traffic generation element from the neighbour report • CID 740 – counter, subelement reference is removed • CID 741 – accepted • CID 1216 – counter • CID 1359 – counter, change name to “QOS Traffic Capability”

Meeting adjourned at 2:30pm Pacific. Submission page 9 Dorothy Stanley (Aruba Networks) September 2008 doc.: IEEE 802.11-08/0979r3

August 26, 2008 Teleconference

1. Call to Order, Patent Notification 2. Editor Update 3. Comment Resolution – Collocated Interference, Virtual AP, TIM Broadcast, others 4. Adjourn

Attendees: Alex Ashley, Joe Kwak, Emily Qi, Jon Rosdahl, Dorothy Stanley, Allan Thomson, Qi Wang, Menzo Wentink, Jing Zhu

No update.

Jing reviewed the Collocated Interference comments, see https://mentor.ieee.org/802.11/file/08/11-08-0991-00-000v-lb133-co-located-interference-report.xls

• CID 128 – Change to decline, change reference to page 4 from page 23, remove second sentence. Confusion on “measurement”, there is no measurement in collocated interference, only conveying information that is known by the STA; look at context of what is being reported, can be past or present, independent of how information is known. • CID 129 – Change to decline, really referring to text on page 193, not 183. • CID 189 – Counter, delete “or collocated interferers” in 5.2.11.4, change 3.22a definition to “… are known a priori without requiring interference detection, measurement or characterization”, and on page 193, line 21, insert “requiring” similarly. • CIDs 195, 232 – Agree with proposed resolution • CID 231- Counter, keep proposed resolution. • CID 233, 236 - Agree with proposed resolution. • CID 237 – Counter, see CID 189. Submission page 10 Dorothy Stanley (Aruba Networks) September 2008 doc.: IEEE 802.11-08/0979r3

• CID 242 – Change to counter, see CID 189. • CID 267 – Decline, the text defines the frame formats unambiguously. • CIDs 302, 303, 304, 305, 306, 307, 308 – Defer. Discussed solution proposed by Jing. Jon and others to review. Proposed solution is to add one new sentence to 7.3.2.80, and one small change in 11.20.11. • CID 332 – Change to decline. • CID 356, 362, 705, 706, 957, 958 – Change to decline, see CID 332. • CID 604 – Counter, Change from “allows” to “enables” throughout clause 5 text, and change from “receive” to “obtain” and “reporting” to “requests and reports” in the collocated interference section. • CID 1265 – Decline, encoding uses a single octet, not a lot to be gained from using a smaller number of bits. Collocated interference is not a measurement report, see CID 189. • CID 1266 - Agree with proposed resolution. • CID1267 – Accept, add proposed sentence on page 86, line 23, before the last sentence in the paragraph. • CID 1271 – Defer. Intend to accept, need to identify all places where “detect” is used, and replace with “knows”or similar.

Menzo began reviewing the TIM Broadcast comments, see https://mentor.ieee.org/802.11/file/08/11-08- 0967-00-000v-tgv-lb133-tim-broadcast-proposed-comment-resolutions.xls .

• CID 38 – Counter, move the text to 11.2.1.11a from clause 7. • CID 108 – Agree with proposed resolution.

September 2nd con call – Continue with TIM Broadcast, Virtual AP (please contact Qi Wang, [email protected] if you’d like to help prepare resolutions), any other comments.

- Update on Collocated interference comment 1271 – all locations of “detect” - Update on CID 302 and similar: is proposed text change agreeable?

September 2, 2008 Teleconference

1. Call to Order, Patent Notification 2. Editor Update 3. Comment Resolution – Virtual AP, TIM Broadcast, others 4. Adjourn

Notes – Tuesday, September 2, 2008

Attendees: Alex Ashley, Emily Qi, Jon Rosdahl, Dorothy Stanley, Allan Thomson, Ganesh Venkatesan, Menzo Wentink, Jing Zhu

Draft 3.01 is available and posted on the member’s area of the 802.11 website. It includes resolutions to the LB133 editorial comments.

Emily reviewed the 2 remaining Sleep Mode comments, see https://mentor.ieee.org/802.11/file/08/11-08- 0986-02-000v-lb133-comments-sleepmode.xls .

• CIDs 397 and 693 – Agree with proposed resolution. Emily worked with Bill (the commenter, who agrees with the proposed resolution) to generate the proposed text. Allan to confirm that he agrees; if not, then discuss alternalte text and pull the CIDs from the blanket motion.

Menzo continued reviewing the TIM Broadcast comments, see https://mentor.ieee.org/802.11/file/08/11- 08-0967-00-000v-tgv-lb133-tim-broadcast-proposed-comment-resolutions.xls .

• CIDs 130, 270 – Leave as deferred. Need to investigate whether clock drift variability is a concern. Clocks do differ, but the question is, is the amount of drift predictable. Have to wake up early for the TIM frame, just like today for the Beacon frame. Agree that SSID should not be included for the reason indicated. Submission page 12 Dorothy Stanley (Aruba Networks) September 2008 doc.: IEEE 802.11-08/0979r3

• CID 151 – Agree with proposed resolution. • CID 164 – Change to counter, several changes needed. Menzo to prepare text. Change “A value of 0 indicates…” to “A value of 0 is reserved”, add status code value 4 to table v32. Make similar change to the other fields. In figure, change last fields to optional, change length to 3 or 8. Also impacts resolution of CID 38. Change • CID 38 – to counter, delete the indicated sentence. • CID 175, 176– Agree with proposed resolution. • CID 177 – Add description of the VOIP application to the decline reason. Add description of power save when the interval is 1. • CID 271 – Agree with proposed resolution, slight wording changes. • CID 273 – Defer. Similar proposal was rejected in Denver. Need to discuss reasons, if we want to go down that path again. • CID 323 – Move to Virtual AP category. • CID 355 – Change to decline, status codes are local to TIM Broadcast, similar to CID 354. • CID 370, 371 – Agree with proposed resolution. • CID 372 – Change to accept, since context of the sentence is when TIM frame transmission is active. • CID 373, 374 – Agree with proposed resolution. • CID 711, 712, 713, 713 – Agree with proposed resolution. • CID 1272 – Agree with proposed resolution, add sentence to decline reason. • CID 1273, 1286 – Agree with proposed resolution. • CID 1289 – Accepted, same resolution as CID 151, but applied to 7.2.3.5. • CID 1291 – Agree with proposed resolution, duplicate of CID 151. • CID 1315 – Counter, add text to describe contents of fields: A1 to Broadcast, A2, A3 to transmitted BSSID. Need to address second part of the comment in Multiple BSSID section, add reference here to the applicable CID. • CID 1394 – Agree with proposed resolution, add more descriptive text to the explanation, there seems to be confusion over what is duplicated. • CID 1395 – Counter, delete the indicated sentence. • CID 1396 – Agree with proposed resolution.

Summary of remaining TIM Broadcast comments: Deferred: CIDs 130, 270, 273. Move to “Virtual AP” category: CID 323. CID reference needed for CID 1315.

Jing and Jon gave an update on the remaining Collocated Interference category comments.

The agreed proposed resolution to CID 302 is to incorporate the text changes in https://mentor.ieee.org/802.11/file/08/11-08-1010-00-000v-receiver-indicator-in-co-located-interference- report.doc . These are the changes that Jing proposed on the previous call.

The proposed resolution to CIDs 303 through 308 is “See CID 302”.

For CID 1271, Jing reviewed the text and found 2 additional occurrences of “detect”, and believes that they should remain. The resolution text will be updated with an explanation for each occurrence, see 08- 991-02.

References:

Submission page 14 Dorothy Stanley (Aruba Networks)