Document Organization Discussion

Slides:



Advertisements
Similar presentations
June 2005 doc.: IEEE /0593r0 July 2005 Summary Presentation Proposal L:19 Siemens Proposal for WLAN Mesh Networking Date: Authors:
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
TGn Sync Atlanta Presentation on Confirmation
VTS SG Montréal Closing Report
IEEE White Space Radio Contribution Title
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
Legacy OFDM Transmission on several Antennas
TGs September 2005 Mid-week Report
TGp Closing Report Date: Authors: July 2005 Month Year
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
Motion to accept Draft p 2.0
TGs January Final Report
3GPP liaison report July 2006
[place presentation subject title text here]
Descriptive Language Usage in TGv
[place presentation subject title text here]
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Quick Beacon Impacts on LB 92
Self-organizing and Auto-configuring Mesh Networks
[place presentation subject title text here]
JTC1 Ad Hoc Mid-week Report
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
TGs San Diego Closing Report
ADS Study Group Mid-week Report
IEEE P Wireless RANs Date:
TGu-changes-from-d0-01-to-d0-02
Number of Encoder as a function of MCS
LB73 Noise and Location Categories
Document Structure Discussion
Proposal for QAP Available Admission capacity
TGy draft 2.0 with changebars from draft 1.0
TGs January Final Report
TGv Redline D0.10 Insert and Deletion
WNG Closing Report, May Authors: May 2008 Date: May 2007
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGp Closing Report Date: Authors: March 2007 Month Year
November Opening Report
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
3GPP2 Liaison Report Date: Authors: May 2006 May 2006
May 2005 CAPWAP AHC Closing Report
Liaison Report From Date: Authors: Month Year
Beamforming and Link Adaptation Motions
Draft P802.11s D1.03 WordConversion
Document Structure Discussion
January Opening Report
Proposed Changes for LB81 Comments
Motion to go to Letter Ballot
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
Document Structure Discussion
TGp Closing Report Date: Authors: November 2006 Month Year
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Summary of Unresolved MAC Comments for 2/28 TGs Telecon
TGr Proposed Draft Revision Notice
TGs March Mid-Week Report
WNG SC Closing Report Date: Authors: July 2006 July 2006
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

Document Organization Discussion June 2006 doc.: IEEE 802.11-06/826r3 June 2006 Document Organization Discussion Date: 2006-06-14 Authors: Name Address Company Phone Email W. Steven Conner 2111 NE 25th Ave, Hillsboro, OR 97124 Intel +1-503-264-8036 w.steven.conner@intel.com Notice: This document has been prepared to assist IEEE 802.11. 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 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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 <stuart.kerry@philips.com> 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. W. Steven Conner, Intel Corp. Donald Eastlake 3rd, Motorola

Current Organization of the TGs Draft June 2006 doc.: IEEE 802.11-06/826r3 June 2006 Current Organization of the TGs Draft 3 Definitions 4 Abbreviations and Acronyms 5 General Description 7 Frame Formats 11A WLAN Mesh Services 11A.1 Use of Mesh Identifier 11A.2 Single and Multiple Radio Devices 11A.3 Mesh Topology Discovery and Formation 11A.4 Mesh Path Selection and Forwarding 11A.5 Security 11A.6 Optimizations to EDCA for Mesh Points 11A.7 Intra-Mesh Congestion Control 11A.8 Multi-Channel MAC Using Common Channel Framework (Optional) 11A.9 Mesh Deterministic Access (Optional) 11A.10 Interworking Support in a WLAN Mesh 11A.11 Configuration and Management (DFS) 11A.12 Mesh Beaconing and Synchronization 11A.13 Power Management in a Mesh (Optional) 11A.14 Layer Management (Informative) Annex P WLAN Mesh Annex W. Steven Conner, Intel Corp. Donald Eastlake 3rd, Motorola

Comments on Current Organization June 2006 doc.: IEEE 802.11-06/826r3 June 2006 Comments on Current Organization Currently, all WLAN Mesh protocol descriptions are in a single major section of the document (11A) Some of the functions described here are closely related to similar functions in the base standard E.g., new versions of discovery, association, link security, beaconing, synchronization, power save functions, which are currently specified in the base std for BSS and IBSS modes E.g., new MAC protocols that build on and are tightly coupled to EDCA in the base standard (MDA and CCF) Other functions described here are unique to mesh and only loosely coupled to the base standard E.g. path selection and forwarding, mesh interworking, congestion control are new functions not included in the base standard W. Steven Conner, Intel Corp. Donald Eastlake 3rd, Motorola

June 2006 doc.: IEEE 802.11-06/826r3 June 2006 Document Organization Conventions Typically Used by Other TG Amendments Functionality that is closely related to existing functions in the base standard integrated into existing sections Functionality that is new/unique to the TG goes in its own major section of the document Is this the right approach for TGs? Pros: Consistency with the base standard and other TG amendments May be helpful for non-TGs reviewers to understand what parts of the draft are closely related to existing functions/other amendments Cons: Makes the “mesh specification” less cohesive W. Steven Conner, Intel Corp. Donald Eastlake 3rd, Motorola

June 2006 doc.: IEEE 802.11-06/826r3 June 2006 Possible Re-Organization of the TGs Draft to more closely conform to base standard 3 Definitions 4 Abbreviations and Acronyms 5 General Description 7 Frame Formats 11A WLAN Mesh Services 11A.1 Use of Mesh Identifier  Merge with Clause 5 General Description 11A.2 Single and Multiple Radio Devices  Merge with Clause 5 General Description 11A.3 Mesh Topology Discovery and Formation  Merge with Clause 11.8 Association 11A.4 Mesh Path Selection and Forwarding  Keep in standalone Mesh Clause 11A.5 Security  Merge link security with Clause 8 Security 11A.6 Optimizations to EDCA for Mesh Points  Merge with Clause 9.9.1 EDCA 11A.7 Intra-Mesh Congestion Control  Keep in standalone Mesh Clause 11A.8 Multi-Channel MAC Using Common Channel Framework (Optional) New section in Clause 9 MAC Sublayer 11A.9 Mesh Deterministic Access (Optional)  New section in Clause 9 MAC Sublayer 11A.10 Interworking Support in a WLAN Mesh  Keep in standalone Mesh Clause 11A.11 Configuration and Management (DFS)  Merge with Clause 11.10 DFS procedures 11A.12 Mesh Beaconing and Synchronization  Merge with Clause 11.1 Synchronization and Beacon Generation 11A.13 Power Management in a Mesh (Optional)  Merge with Clause 11.2 Power Management 11A.14 Layer Management (Informative)  Merge with Clause 10 Layer Management Annex P WLAN Mesh Annex W. Steven Conner, Intel Corp. Donald Eastlake 3rd, Motorola

June 2006 doc.: IEEE 802.11-06/826r3 June 2006 Possible Re-Organization of the TGs Draft to more closely conform to base standard 3 Definitions 4 Abbreviations and Acronyms 5 General Description Frame Formats Security 8.x Mesh Link Security MAC Sublayer 9.9.1.x Optimizations to EDCA for Mesh Points 9.x Mesh Multi-Channel MAC Using Common Channel Framework 9.x Mesh Deterministic Access Layer Management 10.x Mesh Layer Management MLME 11.1.x Mesh Synchronization 11.1.x Mesh Beacon Generation 11.2.x Mesh Power Management 11.8.x Mesh Association and Link Maintenance (Mesh Topology Discovery/Formation) 11.10.x Mesh DFS procedures 11A WLAN Mesh Services 11A.4 Mesh Path Selection and Forwarding 11A.7 Intra-Mesh Congestion Control 11A.10 Interworking Support in a WLAN Mesh Annex P WLAN Mesh Annex W. Steven Conner, Intel Corp. Donald Eastlake 3rd, Motorola

Discussion Looking for feedback on document organization June 2006 doc.: IEEE 802.11-06/826r3 June 2006 Discussion Looking for feedback on document organization Should TGs evolve the document organization to more closely conform to the base standard and other amendments prior to going to letter ballot? W. Steven Conner, Intel Corp. Donald Eastlake 3rd, Motorola