5 ms·
"Probing just 30% of the top prefixes is likely not enough for their use case. Probing is also an after the fact approach. Fastly needs a solution which will gi
by bogomipz 11y ago
"Probing just 30% of the top prefixes is likely not enough for their use case. Probing is also an after the fact approach. Fastly needs a solution which will give best possible path from first packet."
That's not how BGP works. There's no such thing as getting the best path from the first packet in terms of latency. There's nothing in BGP that tell you about the path in terms of latency or performance. The only "best" that BGP gives you is AS path length between you and the destination. It tells you nothing about congestion/packet loss upstream. The only way to get that is out of band probing, like taking latency measurements and pref'ing routes. There is no approach beyond "after the fact"
There is nothing in this article that talks about optimization of routes.
- amazon_not 11y ago> That's not how BGP works. Of course not. I only stated what Fastly needs, I did not make a statement about how BGP works. By having full BGP feeds from all transit providers the nodes can use the AS paths as part of the heuristics to determine the best possible path (with the available information) from first packet. Obviously the heuristics will also use after the fact probe information to tune the model. The point is that the solution proposed by the grandparent is not better than the one described in the article. > There is nothing in this article that talks about optimization of routes. No, they talk about route selection.
- scurvy 11y agoWhat you're talking about works OK in a single colo or datacenter model, but it doesn't map to the PoP model. It's the PoP model that's driving them to do this. In their PoPs they've got local peers and exchanges that will handle the bulk of their traffic. The leftover stuff is only local and probably minor. They can definitely find that with flow data and optimize across a pair of default routes (basically building their own routing table). It's a pretty common practice when all you deploy is PoPs. Why do you care about a full BGP feed when you're only handling 4-10% of the Internet in a given PoP? AS path length doesn't tell you anything about a route's performance. It's a hint and only a hint.
- amazon_not 11y ago> What you're talking about works OK in a single colo or datacenter model, but it doesn't map to the PoP model. It's the PoP model that's driving them to do this Could you please explain how the PoP model in this case differs from the colo/DC model? Outside the US Fastly's PoP cover multiple countries or whole continents.