-
Notifications
You must be signed in to change notification settings - Fork 0
Route Server BGP Community usage
This Euro-IX Large BGP Community standard list does not try to force IXPs to use all filters or options described below, that is entirely up to the IXPs themselves. However, we do ask that when an IXP does provide a service to its peers in the form of Large BGP Communities we would appreciate it if this list was respected as this will make it much easier for us, the IXP community, but also for our peers to understand what information is trying to be conveyed. When you do not see any community for what you need, then please use the reserved IXP free ranges for speedy deployment, but it would also be wise to start discussing your new community in the EURO-IX mailing list, or at the EURO-IX forums so that we can assign more permanent number for all to use.
Currently the community ranges are divided into 2 distinct ranges, namely 0-999 are for action communities, and 1000-1999 are meant for informational communities. Alternative implementations could use boundaries defined by multiples of binary prefixes.
The first 32b part of the community should ALWAYS contain the Route Server's AS number.
For example ECIX's Route Servers would all use 9033:*:*
Priorities: regarding the priority an integer determines the evaluation order in the route server configuration. Where 0 is the highest priority. For example a no export community has a prio of 0 and a export is also on there with prio 1, then the no export will have presdence.
There is three values in regards to stripping the community before export: "strip recommended", "strip yes", "strip no".
*:*:0 is seen as a wildcard unless stated otherwise.
For example, 9033:0:0 means do not send my route to any peer, while 9033:0:4200000000 only means do not send this prefix to AS 4200000000.
Range of communities to advertise to route server to take some kind of action with the announced prefixes to peers. (e.g. suppress prefixes to a particular peer in some way.)
| Range | Description | Notes | Strip on export | Priority |
|---|---|---|---|---|
| RS:0:PEERAS | Do not advertise to PEERAS | recoomended | 0 (highest) | |
| RS:1:PEERAS | Advertise to PEERAS | Reccomended | Only useful in combination with RS:1:0 | |
| RS:2:ms | Do not announce to peers higher than ms | recommended | ms = Latency of peer in ms |
| Range | Description | Notes |
|---|---|---|
| RS:101:PEERAS | Prepend to PEERAS once | |
| RS:102:PEERAS | Prepend to PEERAS twice | |
| RS:103:PEERAS | Prepend to PEERAS three times | |
| RS:111:ms | Prepend once to peers higher than ms | |
| RS:112:ms | Prepend twice to peers higher than ms | |
| RS:113:ms | Prepend three times to peers higher than ms |
Free to use Action communities
Range of communities which can be set by the Route Server to give additional information to the advertised prefix (e.g. what the Route Server thinks the RPKI status is of this prefix is)
| Range | Description | Notes | Strip on import |
|---|---|---|---|
| RS:1000:1 | RPKI VALID | RS checked prefix RPKI and is VALID | strip yes |
| RS:1000:2 | RPKI UNKNOWN | RS checked prefix and is UNKNOWN | strip yes |
| RS:1000:3 | RPKI NOT CHECKED | strip yes | |
| RS:1000:4-* | RPKI INVALID because of $REASON | strip yes | |
| RS:1001:1 | IRRDB VALID | Prefix exists in IRRDB | strip yes |
| RS:1001:2 | IRRDB NOT CHECKED | Prefix was not checked in IRRDB | strip yes |
| RS:1001:3 | MORE SPECIFIC THAN IRRDB | Prefix does not exist in IRRDB, but a less specific valid entry exists | strip yes |
| RS:1001:4 | IRRDB Prefix not found in AS-SET or aut-num | Prefix was not found in the peer's as-set | strip yes |
| RS:1001:5 | IRRDB INVALID ORIGIN AS | Origin AS not in peer AS-SET * | strip yes |
| RS:1001:6 | IRRDB INVALID PREFIX FOR ORIGIN AS | Prefix not found in origin AS * | strip yes |
| RS:1002:1-* | TRACER (RS #) | IXP assigned ID for route server instance | strip no |
| RS:1003:ms | measured RTT for advertising peer | IXP measured round trip time for peer in ms | strip yes |
| RS:1004:$peerAS | Incoming Peer AS | Use Autonomous System Number of the incoming member for that route | strip yes |
| RS:1005:1 | AS Object, Route Object and Organization NOT from the same region. | meant as a transitioning mechanism until full RPKI deployment | strip yes |
| RS:1005:2 | AS Object, Route Object and Organization from within the same region. | meant as a transitioning mechanism until full RPKI deployment (match) | strip yes |
| RS:1005:3 | AS Object, Route Object and Organization from within the same region Not checked | meant as a transitioning mechanism until full RPKI deployment (match) | strip yes |
Prefixes which have these communities are not expected to be advertised to anyone by the route server, the route server has filtered them. It may still be useful to tag a route which is filtered so that you can see why a route was filtered. for example in BIRD you can still show the filtered routes with show route filtered all.
| Range | Description | Notes |
|---|---|---|
| RS:1101:1 | Prefix length too long | |
| RS:1101:2 | Prefix length too short | |
| RS:1101:3 | Bogon Prefix | |
| RS:1101:4 | Bogon AS | |
| RS:1101:5 | AS path too long | |
| RS:1101:6 | AS path too short | |
| RS:1101:7 | as-path.first != peeras | |
| RS:1101:8 | next hop IP != peer IP | |
| RS:1101:9 | transit-free ASN in AS-Path | |
| RS:1101:10 | ||
| RS:? | ToDo add reasons from other filtering |
| Range | Description | Notes |
|---|---|---|
| RS:1102:1 | Advertising peer declines prefix | Advertising peer does not want you to receive prefix |
| RS:1102:2 | You declined prefix from advertising peer | You do not want to receive prefix from advertising peer |
| RS:1102:3 | maximum number of BGP communities exceeded |
Free to use informational communities