F09-IP: Yes
Rationale
The column now explicitly selects optional per-packet unicast next-hop rotation over multiple provisioned routes, as documented in RFC 2991 section 2. Packets of the same communication can use concurrent paths. Flow-hashed ECMP alone would not establish this result. Reordering and unequal path MTUs are limitations; no endpoint path control or performance gain is claimed.
Assessment method
Documentary analysis; no protocol execution
Source context
Primary specification / explicit selected policy
Outstanding qualification
Bind a router implementation with per-packet scheduling and verify packets of one communication traverse both paths. Measure reordering/MTU consequences; do not substitute flow-hashed ECMP.