Download
1 / 3
30 likes | 140 Vues
This document presents an analysis of the default Management Frame QoS (MFQ) policy to streamline configuration processes. The key focus is on the prioritization of management frames based on their action categories. Specifically, management frames not associated with action or action no-ack subtypes are assigned AC_VO priority, while exceptions exist for six action frames listed in the provided spreadsheet. Additionally, a default priority of AC_BE is proposed for Broadcast Probe Requests. This framework aims to standardize management frame handling and facilitate efficient network management.
E N D
Default Management Frame QoS Policy Date: 2010-07-14 Authors: Slide 1 Santosh Pandey, Cisco Systems
Motivation • Reducing Management Frame QoS (MFQ) policy configuration by providing a default MFQ policy
Default MFQ Policy • Refer to submission 11-10-0097-06-00ae-management-frame-analysis.xls • The Default priority is defined as: • Management frames which do not belong to action or action no ack subtype are assigned AC_VO priority • The priority is defined for an entire action category (see the “Group Priority” column in xls sheet) and is followed for both action and action no ack subtype • There are 6 action frames whose priority are exception to the group priority (see ones marked in red in “Proposed Priority” column in the xls sheet). • Broadcast Probe Request (with broadcast address as destination address) is proposed to have a default priority of AC_BE • In all we will have default priority as such • AC_VO priority for all mgmt subtype frames except ones supporting action frames (Action and Action no Ack) • Categories with one default AC each • 6 exceptions to the above rules
