Mesh Frame Format and Addressing Month Year doc.: IEEE 802.11-yy/xxxxr0 July 2007 Mesh Frame Format and Addressing Date: 2007-07-15 Authors: S. Duvurri, et. al. John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 July 2007 Abstract We propose changes to clarify management frame formats when used with mesh networking. S. Duvurri, et. al. John Doe, Some Company

Mesh Data Frames overview July 2007 Mesh Data Frames overview Separation from non-mesh device interpretation Use FromDS = ToDS = 1 Flexibility of broadcast addressing schemes A1 can contain unicast address or multicast address Support for loop detection Mesh header always included Compatibility with existing cipher suite designs Security header (IV/extended IV) always appears directly following MAC header S. Duvurri, et. al.

Data Frame Format FrameControl.ToDS = FrameControl.FromDS = 1 Month Year doc.: IEEE 802.11-yy/xxxxr0 July 2007 Data Frame Format FrameControl.ToDS = FrameControl.FromDS = 1 MAC HEADER PAYLOAD TYPE SUBTYPE Data 10 Any XXXX ADDR1 RA ADDR2 TA ADDR3 DA ADDR4 SA Mesh Header SNAP/LLC… Flags TTL Seq# Address Extension AE MCM Reserved Addr5 Addr6 B0-B1 B2 B3 - B7 AE : Address Extension Mode. MCM : Multi hop Control Mode. Always 1. S. Duvurri, et. al. John Doe, Some Company

Unified Mesh Management Frame Format July 2007 Unified Mesh Management Frame Format MAC HEADER PAYLOAD MGMT 00 Mesh Action ADDR1 RA ADDR2 TA ADDR3 DA Mesh Header CATEGORYX ACTION Y Fields/IEs related to this Category/Action ACTION FIELD TYPE SUBTYPE Flags TTL Seq# Address Extension AE MCM Reserved Addr4 Addr5 Addr6 B0-B1 B2 B3 - B7 AE : Address Extension Mode. MCM : Multi hop Control Mode. S. Duvurri, et. al.

Flexible Management Format July 2007 Flexible Management Format MCM flag defined in Mesh header to indicates the presence of the rest of the mesh header. Single subtype can be used for both 3 addr and 4 addr mesh management purposes MCM always 1 for data frames MCM is 0 for single hop (3 address) mesh management frames MCM is 1 for multi hop (4 address) mesh management frames S. Duvurri, et. al.

Flexible Management Format (2) July 2007 Flexible Management Format (2) Differentiates mesh management early in frame decode Puts all of mesh management under a single subtype Allows mesh header insertion as fixed field Easier hardware decode than IE parsing Same frame subtype used for both single hop and multihop management Same Category/ActionType codepoint could be re-used for multihop simply by setting MCM = 1 Suggest retargeting ALL mesh management frames to use this format Association request S. Duvurri, et. al.

Month Year doc.: IEEE 802.11-yy/xxxxr0 July 2007 Straw Poll Shall the authors generate normative text for this proposal? Yes: No: Abstain: S. Duvurri, et. al. John Doe, Some Company