You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 2, 2022. It is now read-only.
It might be useful from a troubleshooting and eyeball optimization perspective to provide more anycast routing information. Currently there are a few communities added to CDN prefixes. Core PoPs run bcg which adds it's own communities, and all CDN nodes add 34553:110 to mark the route as originating from the CDN network instead of elsewhere in AS34553. Should each node add a unique community to indicate which node is making the announcement? What other information could be added that would help with troubleshooting and eyeball optimization?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
It might be useful from a troubleshooting and eyeball optimization perspective to provide more anycast routing information. Currently there are a few communities added to CDN prefixes. Core PoPs run bcg which adds it's own communities, and all CDN nodes add
34553:110
to mark the route as originating from the CDN network instead of elsewhere in AS34553. Should each node add a unique community to indicate which node is making the announcement? What other information could be added that would help with troubleshooting and eyeball optimization?Beta Was this translation helpful? Give feedback.
All reactions