Route Prefix Advertisement Control by Standard and Large BGP Community
With immediate effect, HKIX route servers support route prefix advertisement control by standard and large BGP community.
HKIX participants can use below standard BGP community to control BGP prefix advertisement, targets for 2-Byte AS number ($Peer-AS).
| Send prefix to all | 4635:4635 |
| Send prefix to $Peer-AS only | 4635:$Peer-AS |
| Do not send prefix to all | 0:4635 |
| Do not send prefix to $Peer-AS | 0:$Peer-AS |
- If there is none of BGP community, a prefix will be sent to all by default.
- Please use either Standard BGP Community or Large BGP Community for route prefix advertisement control, but do not use both at the same time.
- Please set only one type of above BGP community, while $Peer-AS can be multiple (for example 4635:65501 & 4635:65502 to announce a prefix only to AS65501 and AS65502, or 0:65501 & 0:65502 to announce a prefix to all but not to AS65501 and AS65502).
HKIX participants can use below large BGP community to control BGP prefix advertisement, targets for 4-Byte and 2-Byte AS number ($Peer-AS).
| Send prefix to all | 4635:1:0 |
| Send prefix to $Peer-AS only | 4635:1:$Peer-AS |
| Do not send prefix to all | 4635:0:0 |
| Do not send prefix to $Peer-AS | 4635:0:$Peer-AS |
- If there is none of BGP community, a prefix will be sent to all by default.
- Please use either Standard BGP Community or Large BGP Community for route prefix advertisement control, but do not use both at the same time.
- Please set only one type of above BGP community, while $Peer-AS can be multiple (for example 4635:1:234567 & 4635:1:65501 to announce a prefix only to AS234567 and AS65501, or 4635:0:234567 & 4635:0:65501 to announce a prefix to all but not to AS234567 and AS65501).
|
