Differentiated Services (DiffServ) is a quality-of-service architecture that classifies IP traffic into a small set of per-hop behaviors so each router along a path can prioritize packets independently, without tracking per-flow state. Encoded in the IP header’s DSCP field, it lets networks give latency-sensitive or business-critical traffic better handling than best-effort traffic.
Key takeaways
- DiffServ sorts traffic into a small set of per-hop behaviors, not flows.
- The DSCP field in the IP header carries each packet’s classification.
- Routers act on DSCP locally – no per-flow signaling or reservation.
- IETF standardized DiffServ in RFC 2474 and RFC 2475 back in 1998.
- Versa’s CoS forwarding-class model applies DiffServ-style classification.
On this page: Why it mattersHow it worksTypesDiffServ & VersaFAQ
Why is DiffServ important?
Networks carry traffic with very different tolerances for delay, jitter, and loss: a voice call degrades within milliseconds of added latency, while a bulk file transfer barely notices. When a link congests, something has to lose first, and without a QoS scheme routers treat every packet the same, letting low-priority traffic starve high-priority traffic or vice versa at random.
DiffServ matters because it solved this at Internet scale. An earlier proposal, Integrated Services (IntServ), required routers to track reservation state for every flow – a design that does not scale past a campus network. DiffServ instead sorts traffic into a handful of coarse classes marked directly in the packet, so core routers make fast, stateless decisions. That scalability is why DiffServ, not IntServ, became the QoS model underneath enterprise WANs, service-provider backbones, and SD-WAN class-of-service features today.
What is DiffServ?
DiffServ works by marking, not signaling. At the edge of a DiffServ domain, an ingress device inspects each packet and writes a 6-bit Differentiated Services Code Point (DSCP) into the IP header’s former Type of Service byte. That DSCP value maps to a per-hop behavior (PHB) – a queuing and forwarding treatment, such as low-latency scheduling or a defined drop priority – that every downstream router applies independently based only on the marking it sees.
Because classification happens once, at the edge, and enforcement is local at each hop, DiffServ avoids the per-flow state and signaling overhead that made IntServ impractical. Operators define a small number of forwarding classes – commonly four to eight – and configure schedulers, queues, and drop policies (such as weighted random early detection) that route each marking to the right queue and share bandwidth during congestion. Rewrite rules can also remark packets crossing a domain boundary, keeping policy consistent along the path.
Types of DiffServ per-hop behaviors
The IETF defined a small set of standard PHB groups that most DiffServ deployments use. Default (Best-Effort) is DSCP 0, the fallback for traffic with no special treatment. Class Selector (CS) provides eight backward-compatible classes mapping to the older IP Precedence field, used for coarse priority ordering. Assured Forwarding (AF) defines four classes, each with three drop-precedence levels, giving relatively reliable delivery to important-but-not-real-time traffic such as business applications. Expedited Forwarding (EF) is the premium class: strict low-latency, low-jitter, low-loss treatment reserved for traffic like voice, where even small queuing delay is noticeable.
DiffServ & Versa
Versa’s Class of Service (CoS) feature on Versa Operating System (VOS) devices implements DiffServ-style classification end to end. Ingress traffic is classified into forwarding classes by QoS profiles and policies, and rewrite rules mark or remark the DSCP (and IEEE 802.1p) bits on outbound headers so downstream hops see a consistent classification. On egress, schedulers and scheduler maps assign each forwarding class to its own interface queue, with drop profiles for handling congestion – the same mark-then-forward model DiffServ defines.
DSCP also appears elsewhere in the VOS policy stack: NPU policy-based forwarding can match and set DSCP values in hardware ACL rules, and security policy rules can match traffic by DSCP as part of firewall policy. Together these let a Versa SD-WAN fabric carry a DiffServ marking from a branch LAN, across the WAN overlay, to the destination with consistent per-hop treatment at every device.
Frequently asked questions
What is the DSCP field?
DSCP (Differentiated Services Code Point) is a 6-bit field in the IP header – repurposing the old Type of Service byte – that carries a packet’s DiffServ classification. Routers read this value to select which per-hop behavior to apply to that packet.
How is DiffServ different from IntServ?
IntServ reserves resources per individual flow using signaling (RSVP), which requires every router to track per-flow state – impractical at large scale. DiffServ instead marks packets with a class at the edge and lets each router apply a stateless, local per-hop behavior based on that marking.
What are per-hop behaviors (PHBs)?
A per-hop behavior is the forwarding treatment a router applies to packets carrying a given DSCP value – for example, strict low-latency queuing for Expedited Forwarding traffic. PHBs are defined per router hop, not end to end, which is what makes DiffServ scale.
Does DiffServ guarantee bandwidth or latency?
Not by itself. DiffServ provides differentiated, better-than-best-effort treatment for marked traffic, but hard guarantees depend on how operators provision classes, queues, and scheduling across every hop in the path – DiffServ is the marking and forwarding model, not a reservation protocol.
How does Versa use DiffServ?
Versa VOS devices classify ingress traffic into forwarding classes, apply DSCP-based rewrite rules, and schedule egress queues per class – the same classify-mark-forward model DiffServ defines. DSCP values are also usable as match criteria in NPU ACL and security policy rules.
More on DiffServ
If you want to learn more, these are sources we trust.
| RFC 2475: An Architecture for Differentiated Services | RFC 2474: Definition of the DS Field |
|---|---|
| The original IETF architecture document defining the DiffServ model of edge classification and per-hop forwarding behavior. | The companion RFC that defines the 6-bit DSCP field and the code points routers use to select a per-hop behavior. |
Related terms
If you’re reading about DiffServ, these are worth looking at next.
| SD-WAN | Wide Area Network | Network |
|---|---|---|
| The traffic-steering fabric that applies DiffServ-style classification when choosing paths and shaping traffic across links. | The transport links – broadband, MPLS, wireless – whose limited capacity is exactly what DiffServ prioritization manages. | The VOS object that groups interfaces for management, including the CoS and DSCP rewrite settings applied to their egress traffic. |