[AusNOG] Google Bi-Lat Peering

[Phillip Grasso]

try avoid making assumptions about how any of the large content shops will
route your traffic. There are some rules of thumb that doesn't always apply
but a safe bet.

1). deprefer path if its problematic (in terms of packet loss), either
congested or link problems along the path. Does the path have the capacity
to handle the volume..., remember the path may not be as obvious as you
think, especially when CDN's come into play.
2). Expect typical* economic factors to play, generally peers before
transit paths, local paths before longhaul. (please note #1).
3). reliability of routing information, e.g. bilateral generally before
multilateral (consider #1).
4). longest prefix, then bgp rules might apply after that.

What do you mean stripping duplicate AS's? you can pad as many asn as you
want, I don't think that will change most traffic direction decisions from
most large content provider.


*typical for the content player not isp.

On Tue, 11 Feb 2020 at 09:55, Joseph Goldman <joe at apcs.com.au> wrote:

> Hi List,
>
>   Just after some info regarding Google bi-lat peering, how they
> determine best path and downstream networks.
>
>   I've submitted a ticket but thought people on list may have the info
> on-hand in the mean-time.
>
>   Will Google accept downstream networks also, or only networks that are
> origin from the peering AS?
>
>   If the downstream network is on a different IX participating in route
> server peering that google is also on, will Google prefer the bi-lat
> peering even if the AS path is longer?
>   I'm assuming no - should/would prepending work in this situation (in a
> perfect world, yes) or would Google be stripping duplicate AS's? (I've
> heard of some networks doing this)
>
>   We are trying to shift some traffic (google specifically) for a
> downstream customer and just want to know what level of re-engineering
> advertisements we are in for.
>
> Thanks,
> Joe
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20200216/c46c1a4c/attachment.html>