MAC beaconing sync comment resolution overview September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 MAC beaconing sync comment resolution overview Date: 2010-02-17 Authors: Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Abstract Summary of the suggested resolution text (11-10/222r0) September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Abstract Summary of the suggested resolution text (11-10/222r0) How the comments are resolved BT element ambiguity and limitation Control bits in the Mesh Config element Wordsmith Other open comments on M-BS category Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Summary of 11-10/222 Clean up the description on synchronization. September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Summary of 11-10/222 Clean up the description on synchronization. Clarify the detailed operation for MBCA. Provide the missing descriptions. Consolidate the control bits in Mesh Config element with respect to the MBCA. Add the partial beacon timing advertisement method. This also clarifies how to advertise more than 50 beacon timing information. Add the status number announcement in the beacon timing element to facilitate the detection of the changes in the beacon timing information. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

How the comments are resolved September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 How the comments are resolved CID2718 (BT element ambiguity) Provide more accurate information when it is present. Especially when present in Probe Response frame is not provided. CID2009 (BT element limitation) The Beacon Timing element can only hold beacon information of dot11MeshBeaconTimingReportMaxNum neighbors, and a maximum of 51 due to the length restriction of IEs. How is the case of (dot11MeshBeaconTimingReportMaxNum+n) and 52 or more neighbors handled? Adhoc group agrees to define the partial report method on BT element to leave more flexibility on the beacon timing reporting. @PM2 Mon in LA.  11-10/222 provides clear text to describe the BT element conditions.  11-10/222 adds the partial beacon timing advertisement method. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

How the comments are resolved September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 How the comments are resolved CID2032, 2049 (Control bits in the Mesh Config element) There is confusion with TBTT selection and TSF adjustments and corresponding bits in Mesh Capability field. The text describes the conditions for the selection of the TBTT and the procedure for adjusting the TSF. We should review these control bits in Mesh Capability field… Adhoc group agrees to make TSF Adjustment as mandatory and remove the control bit on it. @PM2 Mon.  11-10/222 further consolidates the control bit in the Mesh Configuration element. The new text provides clear text on the TSF adjustment. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Some more… CID2014 (wordsmith) CID 2715, 2741 (wordsmith) September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Some more… CID2014 (wordsmith) The neighbor mesh STA's TSF timer value is not translated, it is actually the neighbor mesh STA's TSF timer value. The own TSF timer value will be translated. CID 2715, 2741 (wordsmith) Complains the ambiguity of the descriptions. CID2721 (wordsmith) Complains about the incompleteness of MBCA Needs some more work.  11-10/222 provides detailed description to address commenter’s concern. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

How the comments are resolved September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 How the comments are resolved CID2050, 2258 (Placeholder comments) These comments are not specific to a particular issue. Request to review the synchronization and related mechanisms.  11-10/222 is provided through the careful review of the entire synchronization framework. It is believed that the new text addresses commenter’s concern. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Other open comments on M-BS category September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Other open comments on M-BS category CID2521 MLME-STARTBEACONING can be merged with MLME-START with small changes. This will save lots of redundant text and will make it more consistent for BSS, IBSS and MBSS CID2638 The primitive title "Start Beaconing" is vague and could be confusing. CID2522 Fix typo in subclause 10.3.78.2. Adhoc group agrees to reuse MLME-START primitive. @PM2 Mon in LA.  will be resolved by the resolution text 11-10/135r0. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Other open comments on M-BS category September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Other open comments on M-BS category CID2519 Suggest to add Beacon Timing report element in BSS description in the SCAN primitive.  suggest to accept in principle. It should be present actually.  will be resolved by the resolution text 11-10/136r0. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Summary All M-BS category comments are examined and 3 resolution texts are available to close rest of the comments 11-10/135 (Extension of MLME-START Primitives for MBSS) 11-10/136 (Inclusion of Beacon Timing element in BSSDescription) 11-10/222 (MAC beaconing sync comment resolution text) Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Comments? Questions? February 2010 September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Comments? Questions? Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola