1 / 20

802.11 Arc Standing Committee

This document provides the agenda, working documents, and meeting goals for the IEEE P802.11 Architecture Committee meeting held in Nov 2008. It includes discussions on MAC block diagrams and future session planning.

chowell
Download Presentation

802.11 Arc Standing Committee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 802.11 Arc Standing Committee Authors: Date: 2008-11-10 David Bagby, Calypso Ventures, Inc.

  2. Abstract Agenda, working document and report for ARC SC, Nov 2008, Dallas David Bagby, Calypso Ventures, Inc.

  3. IEEE P802.11 Architecture Committee Agenda, working document & report. Nov 2008 sessions. David Bagby, Calypso Ventures, Inc.

  4. Arc Agenda – Nov 2008 • Admin • Attendance • Policies • Meeting goals • Short recap of work from telecons • Continue work on MAC block diagrams • Future session planning David Bagby, Calypso Ventures, Inc.

  5. Attendance • Reminder to attendees to sign in for .11 attendance credit David Bagby, Calypso Ventures, Inc.

  6. IP policy • A SC is covered by the WG IP policy announcements. • Even though we don’t have to read the policy to SC attendees, all attendees are reminded that the policies are in effect and apply to SC sessions. David Bagby, Calypso Ventures, Inc.

  7. Arc SC – Meeting Goals Short recap of Telecons since last session. Continuation of MAC block diagram work David Bagby, Calypso Ventures, Inc.

  8. Discussion Topic Ground Rules • We are exploring - • Small group, open, honest dialog • Session is not oriented toward being a tutorial, • Participation requires familiarity with 2007 contents. David Bagby, Calypso Ventures, Inc.

  9. MAC block diagram working documents • Doc 08/949r3 • Doc 08/1298r0 David Bagby, Calypso Ventures, Inc.

  10. Session Summary • Reviewed work from telecons • Updated working docs to reflect consensus resulting in doc revisions • 08/949r4 • 08/1298r1 • Laid out next steps for model refinements • Continued MAC model discussion & refinement David Bagby, Calypso Ventures, Inc.

  11. Planning for Jan • Will have 2 conf calls before Jan sessions • Tues, 13:00-14:00 ET • 12/16 • 1/13 • Next F2F session in Jan 2009 in los Angeles David Bagby, Calypso Ventures, Inc.

  12. Relevant Documents • 08/9494r4 – updated historical record of diagrams as they have evolved • 08/1298r1 – MAC diagram working document. • 08/1256r2 – this report • 08/1426r0 – minutes for Nov Arc session David Bagby, Calypso Ventures, Inc.

  13. Background material: Session notes • Notes are points informally captured during SC discussions - they are not minutes. David Bagby, Calypso Ventures, Inc.

  14. Notes: Tues Am 1 • How much complexity in diagrams considering the goals? • Tentative Proposal: 5-7 “blocks” on a diagram page; 2 levels - 1 top, 1 of drill down; approx one page text per diagram page. • Seemed a good 1st cut goal • Don’t want clause references to drive explanatory level of detail. • 2007 vs. 1999 doc target shift – implications • We still agree 2007 is right target doc; diagrams to date are 1999 async data centric; more work to do for 2007. David Bagby, Calypso Ventures, Inc.

  15. Notes Tues AM1 • Scope of MAC arc doc functionality • Probable 2 categories • Included functionality • Done and in doc • Work still to be done in doc • Ignored within doc • Not felt to be important by SC participants for goals • Generally considered obsolete • Low ROI on effort required to include David Bagby, Calypso Ventures, Inc.

  16. Notes Tues AM1 • Driving message sequences • A Subset of 1999 was initial set • Were items left out ok to continue to ignore? • Or do we need to include some? • Included to date: • Basic async data slow • Leaving out: • PCF – supplanted by TGe in 2007 • Orig PHY related control stuff (FH, DS, IR phys, 1997 regulatory stuff). • What of (Delta 2007-1999) needs to be added? • Which big chucks of functionality? • Driving sequences to use? • Look ahead exercise (to be done later) • Diagrams “mostly ok” for post 2007 active TG impacts? David Bagby, Calypso Ventures, Inc.

  17. Notes Tues AM1 • Misc to-do • Enhance intro text in doc • Purpose explanation • Useful framework to understand/discuss changes proposed by Task Groups • Intro to overall mac functionality before dive into standard itself David Bagby, Calypso Ventures, Inc.

  18. Thurs AM2 notes • Driving sequences to try to get (2007-1999) impacts • Probable useful order for exercise? • Simple data missing ack • Finish Data flows cases, missing ack cases • Power saving impacts • Security • WEP • TGi • QOS sequences • Queuing in common • One or both schedulers? • EDCA 1st then HCCA • TGh • (management frame sequences => time bounds handled in what block(s)) • PHY control (rf pwr etc) David Bagby, Calypso Ventures, Inc.

  19. Thurs AM2 notes • MIB variable mess • Temporal relation of mib value change vs. action • Control • Internal interfaces • External interfaces David Bagby, Calypso Ventures, Inc.

  20. Thurs AM2 notes • Discussion: initial consideration of QOS addition to diagrams. • Re QOS impacts – where is logical queuing put for retry? Block 3 or 5? • Many or one thing at a time from 3 to 5? • Does 5 have any data store? • Is there flow control between 3/5? • What happens if we think of QOS as multiple instances of some part (maybe all) of the top level diagram? • Is it a virtual STA? (collisions happen at the common medium). • Prob less than the “sta”… Partition by state for medium access? (where is that in current diagram?) David Bagby, Calypso Ventures, Inc.

More Related