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.
\nThe official RFC 2475 — An Architecture for Differentiated Services from RFC Editor / Internet Engineering Task Force supports the following bounded statements:
\nKeep 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.
\nThis 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.
\nDSE 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.
\nAn 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.
\nKeep 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.
\nKeep 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.
\n