F28-RI: No
Rationale
The selected IPv6 IoT endpoint is a RPL leaf. In non-storing operation, routers collect routing information and insert the RFC 6554 source route for downward delivery. That infrastructure-selected path does not expose an endpoint interface to choose or exclude downstream intermediaries; selecting a parent or local access alone does not satisfy F28.
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
RPL does contain genuine source routing: the header specifies IPv6 hops inside its routing domain. This verdict does not erase that feature. It distinguishes the selected leaf endpoint role from a router constructing the header; an endpoint acting as a suitably informed RPL router would be a different qualified role. Domain-boundary restrictions and the selected OF0 routing behavior remain unchanged. No added path-selection application is credited.
Public sources
- https://www.rfc-editor.org/rfc/rfc6554.html#section-2
- https://www.rfc-editor.org/rfc/rfc6554.html#section-4.1
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