[External] Re: BGP Community - AS0 is de-facto "no-export-to" marker - Any ASN reserved to "export-only-to"?'

Mark Tinka mark.tinka at seacom.com
Wed Sep 30 09:43:13 UTC 2020

On 11/Sep/20 20:58, Hunter Fuller wrote:

> Hey Mark, I am here. At 10364 we have 7 network people, 3 of whom have
> an understanding of BGP deeper than surface level. We have 3 peers and
> 2 transit providers total.
> When we go to implement external-facing BGP policy, the #1 concern is
> "What are most people doing?". When we turn up a session with a peer
> or provider (which we will be doing much more frequently in the near
> future), it would be really wonderful if they could say "We support
> RFCXXXX-style communities" and we would know what that means. And if
> RFCXXXX exists then we will implement it when it's needed, just like
> we do no-export. I don't spend all day on BGP and so I like to defer
> to people who have learned from the "school of hard knocks" where
> possible.
> The last thing we want to do is to have a nonstandard or
> difficult-to-understand policy or configuration, because there are
> only 3 total people who could possibly understand it, and all of us
> have many, many other job responsibilities so we basically have to
> "page it back in" every time we go to look at it. The ideal situation
> is that we can google "RFCXXXX-compliant config" and get something
> that helps us get in line with best practices as smoothly as possible.

So if your peer or provider sent you a link to a web site where they 
published all of their support BGP communities, you'd find that onerous 
to deploy across them?


More information about the NANOG mailing list