Separate Diffserv edge conditioning from core per-hop forwarding

Keep this document to one review outcome: Separate Diffserv edge conditioning from core per-hop forwarding. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 2475 — An Architecture for Differentiated Services from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• A differentiated-services domain’s boundary nodes classify and condition ingress traffic so its DS codepoints select supported per-hop behaviors. The research record locates this support at Section 2.1 (Differentiated Services Domain).
• Both boundary and interior nodes apply a per-hop behavior from the DS codepoint, but traffic-conditioning agreements can require extra metering, marking, shaping, or policing at boundaries. The research record locates this support at Sections 2.1.1 (DS Boundary Nodes and Interior Nodes) and 2.3.3 (Traffic Conditioners).
• Core scalability comes from forwarding behavior aggregates without per-microflow or per-customer state, leaving complex classification and conditioning primarily at network boundaries. The research record locates this support at Sections 1.1 (Overview) and 1.3 (Requirements).

Keep the evidence boundary at these traced claims. They support a review of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

This RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. A correct source interpretation can still be inapplicable to a particular design. Confirm DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Section 2.1 (Differentiated Services Domain), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections 2.1.1 (DS Boundary Nodes and Interior Nodes) and 2.3.3 (Traffic Conditioners), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Sections 1.1 (Overview) and 1.3 (Requirements), which observable configuration, record, or test can confirm applicability here?
• Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?
• Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, observed and expected states, owner, and reason for deviation.

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring before and after the test, and store only sanitized operational evidence.

Verification and evidence

Keep the source locations Section 2.1 (Differentiated Services Domain); Sections 2.1.1 (DS Boundary Nodes and Interior Nodes) and 2.3.3 (Traffic Conditioners); Sections 1.1 (Overview) and 1.3 (Requirements) adjacent to the sanitized artifacts used for comparison. Prefer configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results, with enough identity and timing data for an independent recheck.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• RFC 2475 — An Architecture for Differentiated Services — RFC Editor / Internet Engineering Task Force