F28-BL: No
Rationale
Babel selects feasible routes using routing information and local policy. The selected IPv6/Babel composition exposes ordinary destination-based forwarding, not a sender interface to select or exclude downstream intermediaries. Selecting a local next hop or adjusting administrative route metrics does not enforce an endpoint-chosen path beyond that hop.
Assessment method
Primary specification and pinned code review; no runtime experiment
Source context
Babel route selection, LISP RLOC selection and RPL source routing
Outstanding qualification
RFC 8966 section 3.6 permits routing policy and implementation choices, but does not define an endpoint path-selection contract. The fixed aggregate hierarchy used for the separate G01 witness likewise does not supply such an interface. No source-routing extension, tunnel chain or application path-control service is selected. This does not deny administrator traffic engineering or automatic route recovery.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round513.html
- round513-sources.json