F28-IP: Yes
Rationale
IPv4 Loose and Strict Source and Record Route options let the source specify intermediate IP addresses. Loose routing permits other hops between listed addresses; strict routing requires the listed sequence. This is native endpoint path selection in the IPv4 branch of the declared IPv4/IPv6 column.
Assessment method
Primary specification analysis; architectural capability, no runtime test
Source context
Pinned primary specification; selected-composition architectural assessment
Outstanding qualification
RFC 791 section 3.1 and RFC 1812 sections 5.2.4.1 and 5.3.13.4. The witness requires a path whose routers permit source-routed packets; filtering or local policy may prevent use. No authenticated router-identity proof or general public-Internet availability is claimed. IPv6 RH0 is deprecated by RFC 5095 and is not a witness; no Segment Routing extension is silently added.
Public sources
- https://www.rfc-editor.org/rfc/rfc791.html
- https://www.rfc-editor.org/rfc/rfc1812.html
- https://www.rfc-editor.org/rfc/rfc5095.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round464.html
- round464-sources.json