Mesh Frame Formats Date: Authors: May 2007 March 2007

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0300r1 Submission May 2007 Guenael Strutt, MotorolaSlide 1 LB93 Unresolved RFI Comments Notice: This document has been prepared to.
Advertisements

Doc.: IEEE /0186r0 Submission January 2007 Guenael Strutt, MotorolaSlide 1 RFI London Update Notice: This document has been prepared to assist.
Coexistence Motions for LB84 Comment Resolution
LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
TGn Sync Atlanta Presentation on Confirmation
TGn LB97 Frame Format Ad Hoc
Motions Date: Authors: January 2006
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Mesh Frame Formats Date: Authors: June 2007 March 2007
Waveform Generator Source Code
TGn LB97 Frame Format Ad Hoc
Review of Extensible Path Selection Framework
Mesh Frame Types & Subtypes
[ Policies and Procedure Summary]
Mesh Frame Formats Date: Authors: July 2007 March 2007
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
3GPP liaison report July 2006
[place presentation subject title text here]
Descriptive Language Usage in TGv
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
TGn Frame Format Ad Hoc Status and Motions
CID 186, 206 and 211 resolution Date: Authors: January 2007
TGp Closing Report Date: Authors: March 2006 Month Year
March 2007 doc.: IEEE /0389r0 March 2007
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
Mesh Frame Formats Date: Authors: May 2007 March 2007
ADS Study Group Mid-week Report
Mesh Frame Formats Date: Authors: May 2007 March 2007
Protection Assurance Method
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
Extended Channel Switch Announcements
Proposal for QAP Available Admission capacity
PHY Ad Hoc September Opening Report
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D1.04-D1.0 Insert and Deletion
TGv Redline D0.10 Insert and Deletion
TGn LB84 – Frame Format Ad Hoc Status and Motions
LB93 Unresolved RFI Comments
Suggested comment resolution on ATIM window parameter
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Mesh Frame Formats Date: Authors: June 2007 March 2007
TGr Proposed Draft Revision Notice
Off-channel selection
[ Policies and Procedure Summary]
Beamforming and Link Adaptation Motions
CID 186, 206 and 211 resolution Date: Authors: January 2007
Link Metric Comment Resolution
TGn LB84 – Frame Format Ad Hoc Status and Motions
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
Mesh Frame Formats Date: Authors: May 2007 March 2007
Mesh Frame Formats Date: Authors: July 2007 March 2007
TGu Motions Date: Authors: May 2006 May 2006
Beamforming and Link Adaptation Motions for LB 84 Comment Resolutions
MAC Address Spoofing in Mesh
TGn LB84 – Frame Format Ad Hoc Motions
TGp Closing Report Date: Authors: November 2006 Month Year
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

Mesh Frame Formats Date: 2007-05-14 Authors: May 2007 March 2007 doc.: IEEE 802.11-07/0550r3 May 2007 Mesh Frame Formats Date: 2007-05-14 Authors: 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>. Guenael Strutt, Motorola et al. Guenael Strutt, Motorola et al.

March 2007 doc.: IEEE 802.11-07/0550r3 May 2007 Abstract Many comments were raised during LB93 about the definition of new frame format types and subtypes in D1.00. This presentation identifies possible resolutions to comments classified under the General identifiers G11. Ideally, mesh frames should be compatible with frames and features from other task groups, e.g. TGn, TGv, TGw. This presentation addresses all of the above Guenael Strutt, Motorola et al. Guenael Strutt, Motorola et al.

Proposed Resolution of General Comments on Frame Formats (11-07/799) March 2007 doc.: IEEE 802.11-07/0550r3 May 2007 Proposed Resolution of General Comments on Frame Formats (11-07/799) CIDs in General Category G11: Need clarification on compatibility of mesh data frame type with existing data subtypes 1672, 2235, 3467, 3601, 4468, 4893 Clarification of extended frame type vs. mesh management frame type vs. using existing frame types 42, 1234, 1582, 2011, 2012, 2013, 2024, 2031, 2055, 2278, 3674, 3675, 3676, 3722, 3723, 3724, 3760, 3761, 3764, 3765, 4470, 4471, 4770 Mesh Management Frame and Mesh Action Data Unit needs clarification 6, 312, 313, 316, 317, 318, 319, 324, 1937, 1939, 2057, 2619, 2900, 3535, 3747, 4018, 4081, 4197, 4894, 4939, 5197 Incomplete frame descriptions 1805, 1936, 3605, 3666 Action encapsulation frame needs clarification 3547 Guenael Strutt, Motorola et al. Guenael Strutt, Motorola et al.

Proposed Management Frames for Mesh March 2007 doc.: IEEE 802.11-07/0550r3 May 2007 Proposed Management Frames for Mesh Action frame SUBTYPE MAC HEADER PAYLOAD MGMT 00 ACTION 1101 ADDR1 RA=DA ADDR2 TA=SA BSSID 00 CATEGORY X ACTION Y Fields/IEs related to this Category/Action TYPE ACTION FIELD Path Request Peer Link Open Mesh Channel Switch Link Metric Report Portal Announcement etc. FIXED LENGTH TYPE SUBTYPE MAC HEADER PAYLOAD MGMT 00 MH ACTION 1111 ADDR1 RA ADDR2 TA ADDR3 DA ADDR4 SA TTL CATEGORY X ACTION Y Fields/IEs related to this Category/Action MULTIHOP INFO FIELD ACTION FIELD Multihop Action frame Mesh Key Holder Security Establishment PMK-MA Delivery Push etc. Guenael Strutt, Motorola et al. Guenael Strutt, Motorola et al.

Proposed Data Frames for Mesh March 2007 doc.: IEEE 802.11-07/0550r3 May 2007 Proposed Data Frames for Mesh Reuse existing data types/subtypes with ToDS/FromDS bits set to 1/1: Mesh data frames are only exchanged between peer MPs with an established mesh link Assures forward compatibility with data frame changes that other task groups might come with – e.g. TGn aggregation. Compatibility with legacy/non-standard implementations No incompatibilities with legacy BSS/IBSS STA or AP implementations since they use different values for ToDS/FromDS Some non-standard WDS implementations may automatically attempt to communicate with any nearby device discovered sending 4-address broadcast/multicast data frames (so-called “Lazy WDS” scheme) MPs ignore 4-address data frames transmitted by legacy/non-standard WDS devices, since they do not establish a mesh link Guenael Strutt, Motorola et al. Guenael Strutt, Motorola et al.

Second contribution (11-07/800): Reorganization of Action Types March 2007 doc.: IEEE 802.11-07/0550r3 May 2007 Second contribution (11-07/800): Reorganization of Action Types Category Action(s) Mesh PLM Peer Link Open Peer Link Confirm Peer Link Close Mesh HWMP Path Request Path Reply Path Error Root Announcement Mesh Security Mesh Key Holder Security Establishment PMK-MA delivery push PMK-MA confirm PMK-MA request PMK-MA delivery pull PMK-MA delete Mesh EAP encapsulation Etc… … Guenael Strutt, Motorola et al. Guenael Strutt, Motorola et al.

May 2007 Motion #1 Moved, to accept the submission contained in document 11-07/799r1 to resolve the CIDs listed on slide 3 of 11-07/550r4, and instruct the editor to incorporate the changes into the draft Guenael Strutt, Motorola et al.

May 2007 Motion #2 Moved, to accept the submission contained in document 11-07/800r1, and instruct the editor to incorporate the changes into the draft Guenael Strutt, Motorola et al.

References doc.: IEEE 802.11-07-0023r23 (Issue Identifier G11) March 2007 doc.: IEEE 802.11-07/0550r3 May 2007 References doc.: IEEE 802.11-07-0023r23 (Issue Identifier G11) Guenael Strutt, Motorola et al. Guenael Strutt, Motorola et al.