F09-LI: Yes
Rationale
Architectural Yes with an explicit optional packet scheduler. RFC 9300 section 9 gives the client-side ITR distribution choice when the eligible best-priority RLOCs have zero weights. Section 12 makes its flow-hash selection algorithm optional. Select two reachable locators for the same destination EID and alternate successive useful UDP packets between them over distinct provisioned paths. Both paths carry the same communication while it is active. Keeping the outer UDP source port constant preserves the separate per-flow source-port recommendation. This supplies the previously missing scheduler policy at the architectural capability level, using the same optional-policy standard already applied to IP F09.
Assessment method
Normative policy analysis and explicit architectural witness; no execution
Source context
RFC 9300 sections 9 and 12; optional-policy parity with F09-IP
Outstanding qualification
This optional deployment policy is now explicit in the LI profile; it is not the flow-hashed behavior observed in lispers.net a61c30b. No existing implementation is asserted to expose this policy, and no traffic test, performance gain or independent interoperability result was produced. Two RLOCs alone do not prove distinct physical routes. Reordering and path MTU differences remain deployment concerns. Selection is at the ITR, not autonomous endpoint control; F20/F23 and all other verdicts are unchanged.
Public sources
- https://www.rfc-editor.org/rfc/rfc9300.html#section-9
- https://www.rfc-editor.org/rfc/rfc9300.html#section-12
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round412.html
- round412-evidence.json