On-path vs off-path traffic steering, that is the question

Service-level traffic steering in the Internet has been using an indirection-based model for decades now, using the DNS to resolve a name to a locator, often complemented with load balancing techniques. Contrasting this off-path realization, service information as part of the data packet itself may determine the one of possibly many communication endpoints on-path while traversing the network. This paper compares both design choices regardless of the specific decision mechanism used. For this, we assume a compute-aware traffic steering mechanism for both approaches and determine latency penalties through off-path resolution steps as well as distributing scheduling decisions to on-path network ingress points. Lastly, we investigate latency variances and resilience in an AR/VR scenario.