F36-IL: No
Rationale
ILNPv6 Locator selection and updates preserve identifier-bound transport across attachments; the selected TCP interface does not request admission against a reserved capacity or delay budget.
Assessment method
Primary RFC review with explicit optional transport mechanisms
Source context
RFC 9300/6741 and RFC 7567/2475
Outstanding qualification
No application-requested reservation protocol is selected. Traffic engineering, TCP reliability, packet marking and operator provisioning do not by themselves meet F36.
Public sources
- https://www.rfc-editor.org/rfc/rfc6741.html#section-3.2
- https://www.rfc-editor.org/rfc/rfc6741.html#section-3.2
- https://www.rfc-editor.org/rfc/rfc1633.html#section-5
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round681.html