MAC beaconing sync comment resolution overview

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0497 r0 Submission May 2008 Allan Thomson, Cisco SystemsSlide 1 D2.0 Location Changes Summary Date: Authors:
Advertisements

Doc.: IEEE /0560r0 Submission May 2009 Allan Thomson, Cisco SystemsSlide 1 Time Features Date: Authors:
Submission doc.: IEEE 11-10/0259r0 March 2013 Jarkko Kneckt (Nokia)Slide 1 CID 266 & CID 281 Date: Authors:
Doc.: IEEE /1468r0 Submission Dec 2008 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE s Mesh Network Date:
Doc.: IEEE /1206r0 Submission Oct 2004 Black, NokiaSlide 1 TGk LB71 Parallel category comment resolution Simon Black (Nokia)
Doc.: IEEE /0786r1 Submission Proposed Resolution to CID 26, 27, 37, 38, 40-47, 49-53, 67-71, 114, 115, 118 and 124 Qian ChenSlide 1 July 2014.
Doc.: IEEE /0100r2 Submission January 2010 Kazuyuki Sakoda, Sony CorporationSlide 1 MAC beaconing sync comment resolution Date: Authors:
Doc.: IEEE /1143r0 Submission November 2009 Kazuyuki Sakoda, Sony CorporationSlide 1 Potential confusion in D3.04 Date: Authors:
Doc.: IEEE /0232r0 Submission February 2009 Meiyuan Zhao, IntelSlide 1 Suggestions to Clean Up Peering Management Frames Date:
Doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 1 Proxy Update Element Revision Date: Authors:
Doc.: IEEE /0590r0 Submission May 2010 Kazuyuki Sakoda, Sony CorporationSlide 1 MAC beaconing sync comment resolution overview Date:
Doc.: IEEE /0537r0 Submission May 2010 Kazuyuki Sakoda, Sony CorporationSlide 1 General frame format comment resolution overview Date:
FILS Reduced Neighbor Report
Time Features Date: Authors: May 2009 Month Year
doc.: IEEE <doc#>
Suggested comment resolution on Power save clause
MCCA Comments Resolution 159 ppt
Multi-band Discovery Assistance
Multi-band Discovery Assistance
Summary of Unresolved General Comments for 2/14 TGs Telecon
Summary of Unresolved General Comments for 2/14 TGs Telecon
Multi-band Discovery Assistance for ay (CR on CID 1771)
Resolutions to orphan comments
FILS Reduced Neighbor Report
CID#102 - Channel Allocation
Remaining issues regarding power save
Remaining issues regarding power save
CR for CID 1105 Date: Authors: January 2019 Month Year
Proposed resolution of CID 3518
Proposed resolution of CID 3518
Overview of Changes to Key Holder Frame Formats
Proposed resolution of CID 3518
QoS STA function applied to Mesh STA
Proposed Resolutions to RFI comments of LB 166 on IEEE s D7.0
AP Power Down Notification
Multi-band Discovery Assistance for ay (CR on CID 1771)
Discovery Assistance for ay
Draft D4.01 status report Date: Authors: February 2010
Channel Allocation March 2008 Authors: Date: Month Year
WUR Synchronization Date: Authors: November 2017 Name
Suggested comment resolution on ATIM window parameter
WAVE without beacons Date: Authors: May 2007 Month Year
Terminology changes in a nutshell …
Common Mesh TSF Issues Date: Authors: September 2007
Proposed Changes for D0.25 Comments
Suggested comment resolution on Power save clause
LB97 Coex: Duplicate DSSS
PLE Comment Resolution
Time Features Date: Authors: May 2009 Month Year
Synchronization related comment resolution
Suggested comment resolution on Mesh DTIM element
MAC beaconing sync comment resolution
Some open questions Date: Authors: January 2010
Overview Suggested Comment Resolution for Mesh Synchronization
MBCA and Beacon Timing element clean up
Clarification on CID3778 and Mesh TIM element
doc.: IEEE <doc#>
Timing Measurement Date: Authors: Jan 2010 November 2007
Resolutions of the Remaining Power Management Comments
Setting of DTIM Interval for MCCA
Proposed resolution of CID 3518
Some feedback from editor
Suggested comment resolution on ATIM window parameter
Congestion Control Comments Resolution
Multi-band comments resolution
Timing Measurement Date: Authors: Jan 2010 November 2007
On the Need for an ai Annex
Summary of Unresolved MAC Comments for 2/28 TGs Telecon
Suggested comment resolution on Power save clause
General discovery comment resolution overview
Presentation transcript:

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