1 / 12

Mesh Frame Formats

Mesh Frame Formats. Authors:. Date: 2007-07-16. 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.

jescie-guerrero
Download Presentation

Mesh Frame Formats

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. Mesh Frame Formats Authors: Date: 2007-07-16 Steven Conner, et al.

  2. 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 is a summary of 11-07/799r6, which addresses all of the above Steven Conner, et al.

  3. 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 Steven Conner, et al.

  4. Background: Frame Types/Subtypes in the current 802.11s Draft D1.05 This contribution eliminates the use of the last reserved 802.11 major frame type (11) Steven Conner, et al.

  5. Mesh Management Frames Overview • Majority of TGs management frames only require 1-hop transmission • Reuse existing Action Frame subtype (1101) for these frames (defined in Clause 7.4) • Some TGs management frames require multihop transmission • Multihop Action Frame subtype (1111) includes Mesh Header for these frames (defined in Clause 7.4b) • Replaces Extended/Mesh Management frame in D1.05 • Allows mesh header insertion as fixed field • Easier hardware decode than IE parsing Note: management frame subtype 0111 remains reserved for use by other task groups July 2007 Slide 5 Steven Conner, et al.

  6. Management Frames for Mesh Action frame MAC HEADER PAYLOAD MGMT 00 ACTION1101 ADDR1RA=DA ADDR2TA=SA BSSID00 CATEGORYX ACTIONY Fields/IEs related to this Category/Action TYPE SUBTYPE ACTION FIELD Path RequestPeer Link OpenMesh Channel SwitchLink Metric ReportPortal Announcementetc. FIXED LENGTH MAC HEADER PAYLOAD MGMT 00 MH ACTION1111 ADDR1RA ADDR2TA ADDR3DA Mesh Header CATEGORYX ACTIONY Fields/IEs related to this Category/Action SUBTYPE Mesh HeaderFIELD ACTION FIELD Multihop Action frame Mesh Key Holder Security EstablishmentPMK-MA Delivery Push etc. Steven Conner, et al.

  7. Multihop Action Frame Details July 2007 MAC HEADER PAYLOAD MGMT 00 Multihop Action1111 ADDR1RA ADDR2TA ADDR3 MeshHeader CATEGORYX ACTIONY Fields/IEs related to this Category/Action ACTION FIELD TYPE SUBTYPE Flags TTL Seq # Address Extension Address Extension Mode Reserved Addr4 Addr4 Addr5 Addr6 - OR - B0 B1 B2 - B7 Applicable for Multihop Action Frames Steven Conner, et al.

  8. Mesh Data Frames overview • Separation from non-mesh device interpretation • Use FromDS = ToDS = 1 • Included if and only if transmitted between peer MPs with an established peer link • Flexibility of broadcast addressing schemes • Addr1 can contain unicast address or multicast address (a separate contribution is being prepared to specify more details here) • Support for loop detection • Mesh header always included in mesh data frames • Compatibility with existing cipher suite designs • Security header (IV/extended IV) always appears directly following MAC header July 2007 Slide 8 Steven Conner, et al.

  9. Mesh Data Frame Format MAC HEADER PAYLOAD TYPE SUBTYPE Data 10 Any XXXX ADDR1RA ADDR2 TA ADDR3 ADDR4 MeshHeader SNAP/LLC… Flags TTL Seq # Address Extension Address Extension Mode Reserved Addr5 Addr6 B0 B1 B2 - B7 Applicable for Data Frames Steven Conner, et al.

  10. Motion • Moved, to adopt the submission contained in document 11-07/799r8 to resolve all of the open CIDs labeled with issue identifier G11 (frame formats) in 11-07/23r37, and instruct the editor to incorporate the changes into the draft Steven Conner, et al.

  11. References • doc.: IEEE 802.11-07-0023r37 (Issue Identifier G11) Steven Conner, et al.

  12. Data Frames for Mesh 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 Steven Conner, et al.

More Related