F38-HP: Yes
Rationale
Select independently administered DiffServ policies in the IP forwarding layer carrying HIP control and ESP-protected user traffic. Domain/interface owners classify, police and shape traffic and enforce local service-class resource priorities. ESP payload decryption is unnecessary for classification of the visible transport aggregate.
Assessment method
Primary RFC review and explicit optional IP transport policy selection
Source context
HIP/Babel specifications and RFC 7567/2475
Outstanding qualification
Optional transport policy with actual conditioning/enforcement selected, not marking alone. Compatible inter-domain agreements remain necessary. This does not provide application reservation, global QoS or new cryptographic authorization.
Public sources
- https://www.rfc-editor.org/rfc/rfc2475.html#section-2.3
- https://www.rfc-editor.org/rfc/rfc7401.html
- https://www.rfc-editor.org/rfc/rfc7402.html#section-3
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round682.html