Hello,
I’m looking to make contact with someone at Bell Canada/AS577 who is able to perform BGP prefix filtering facing their on-prem Akamai caches. Normal sales rep and NOC channels are not producing any meaningful results so far.
Thanks in advance!
I’m curious as to why someone would want to do this? My interest is education, not combative.
In previous lives I have had great success simply talking to people at Akamai about where my customers’ traffic was landing, and where would make more sense for it to land. They were always very responsive; the people I used to talk to are no longer there, but I imagine there are replacements, even if you have to hunt a little further than the published noc address. I always took care to describe my problem in terms of clients and content rather than routing policy, which seemed like a better bet than making assumptions about how their content-steering machinery worked.
Asking Akamai seems more likely to succeed than asking a third-party network to modify their BGP export policy for a non-customer, especially when the third-party network is large and, I am guessing, highly-automated and policy-rigid. But it would be interesting to me too to find out if I’m wrong.
Jason, if you are multi-homed you could always try AS_PATH prepending 18717 to the advertisments you send towards 577 (he said, over his shoulder, running away).
Joe
* jabley@hopcount.ca (Joe Abley) [Wed 19 Jun 2019, 17:24 CEST]:
I'm curious as to why someone would want to do this? My interest is education, not combative.
In previous lives I have had great success simply talking to people at Akamai about where my customers' traffic was landing, and where would make more sense for it to land. They were always very responsive; the people I used to talk to are no longer there, but I imagine there are replacements, even if you have to hunt a little further than the published noc address. I always took care to describe my problem in terms of clients and content rather than routing policy, which seemed like a better bet than making assumptions about how their content-steering machinery worked.
Still happy to help out as will be other colleagues lurking on this list.
Asking Akamai seems more likely to succeed than asking a third-party network to modify their BGP export policy for a non-customer, especially when the third-party network is large and, I am guessing, highly-automated and policy-rigid. But it would be interesting to me too to find out if I'm wrong.
It's Akamai making the decision to serve networks from certain clusters so it's not really up to Bell to go against Akamai's request to send their own + customer prefixes for their cluster.
Jason, if you are multi-homed you could always try AS_PATH prepending 18717 to the advertisments you send towards 577 (he said, over his shoulder, running away).
Akamai caches generally ignore AS_paths so that may not help.
-- Niels.
clusters so it's not really up to Bell to go against Akamai's request
to send their own + customer prefixes for their cluster.
Does Akamai mostly rely on the DNS the request was coming from?
Regards
Bjoern
As I recall, yes that is true.
Somethings mentioned here...
I recall that after I deployed my local AANP clusters, that *if* I wanted to bypass local aanp caching, that I would change my dns setting and thus bypass aanp cache, and flow out to inet.
-Aaron