1. Mesh Frame Formats Date: 2007-06-13 Authors: June 2007 March 2007
doc.: IEEE /0550r3
June 2007
Mesh Frame Formats
Date:
Authors:
Guenael Strutt, Motorola et al.
Guenael Strutt, Motorola et al.

2. March 2007
doc.: IEEE /0550r3
June 2007
Abstract
Many comments were raised during LB93 about the definition of new frame format types and subtypes in D 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.

3. Proposed Resolution of General Comments on Frame Formats (11-07/799)
March 2007
doc.: IEEE /0550r3
June 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.

4. Proposed Management Frames for Mesh
March 2007
doc.: IEEE /0550r3
June 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
Mesh Header
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.

5. Proposed Data Frames for Mesh
March 2007
doc.: IEEE /0550r3
June 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.

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