... packets.¹

In fact, like most enterprise route control products, we enforce outbound route control by transmitting packets to a destination along the same provider as the one on which the traffic from the destination is received.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... performance²

About a third of the connections employed for measurement can be expected to be routed along their optimal providers

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... table³

We could allow routes to change less frequently than the sampling interval, $T$, (e.g., every $T'>T$ seconds) but since we do not use performance history, this would be equivalent to sampling and updating every $T'$ seconds.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.