RFC 8325: Mapping Diffserv to IEEE 802.11

Publisher

IETF / RFC Editor

URL

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

Published

2018-02-01

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

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

Source notes citing this source

• For upstream Wi-Fi traffic, RFC 8325 says client operating systems should use the same DSCP-to-UP mappings as downstream, but packets requesting CS6 or CS7 should be mapped to UP 0 and re-marked to DSCP 0. in context
• RFC 8325 maps EF-marked (telephony) traffic to IEEE 802.11 User Priority 6, which places it in the Voice Access Category (AC_VO). in context
• RFC 8325 identifies a common default of deriving 802.11 UP from the three most significant DSCP bits. Under that default, EF voice (101110) maps to UP 5 and lands in the Video Access Category instead of Voice. 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-b

BibTeX

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