F38-IP: Yes
Rationale
Select independently administered DiffServ domains. RFC 2475 defines boundary classification and conditioning, including policing and shaping, under domain provisioning policies and inter-domain traffic agreements. Domains can enforce their own access to service classes and resource priorities without imposing one uniform policy across the whole path.
Assessment method
Primary specification and implementation documentation review; no runtime experiment
Source context
RFC 1633, RFC 7567, RFC 2475 or IRATI Ethernet tutorial, as linked
Outstanding qualification
Explicit optional IP-layer DiffServ witness, not universal default Internet service. Service-class admission is not cryptographic peer authorization. Inter-domain agreements must be compatible; no guaranteed global QoS, dynamic application reservation or added stateful firewall is inferred.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round650.html