RFC 8325: Mapping Diffserv to IEEE 802.11

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc8325.html

Published

2018-02-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust Legal Provisions (BCP 78/79); no-redistribution; short excerpts and locators only

Source notes citing this source

• RFC 8325 maps CS5 signaling to User Priority 5 (the Video access category, AC_VI), not to the Voice access category. in context
• RFC 8325 maps EF (46) to IEEE 802.11 User Priority 6, placing voice in the Voice access category (AC_VO). in context
• RFC 8325's summary table maps CS3 (the Broadcast Video class) to UP 4 in AC_VI. in context
• RFC 8325 recommends mapping signaling traffic marked CS5 to UP 5 in the Video Access Category (AC_VI). in context
• RFC 8325 says packets from wireless clients requesting CS6 or CS7 should be mapped to UP 0 rather than UP 7, and the client OS should re-mark them to DSCP 0. in context
• RFC 8325 maps EF (DSCP 46) to 802.11 UP 6, placing voice in the Voice Access Category (AC_VO). in context
• RFC 8325 says the default practice of copying the top three DSCP bits into the 802.11 UP produces inconsistent mappings, including putting voice in AC_VI rather than AC_VO. in context
• RFC 8325 recommends mapping VOICE-ADMIT (DSCP 44) to UP 6 as well. in context

Cite this source record

APA

WarmTransfer. (2018, February 1). RFC 8325: Mapping Diffserv to IEEE 802.11. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-8325-diffserv-to-80211

BibTeX

@misc{warmtransfer-rfc-8325-diffserv-to-80211,
  title  = {RFC 8325: Mapping Diffserv to IEEE 802.11},
  author = {{WarmTransfer}},
  year   = {2018},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-8325-diffserv-to-80211},
  note   = {IETF / RFC Editor, accessed 2026-09-24}
}