BGP communities
InterIX provides BGP community filtering mechanism to peers
InterIX route server peers are able to manipulate outbound routing policies via an in-band mechanism using BGP communities.
Available options
- Do not announce a prefix to a certain peer: 0:peer-as
- Announce a prefix to a certain peer: 56584:peer-as
- Do not announce a prefix to any peer: 0:56584

Large BGP communities
For destination peers employing a 32-bit ASN, you can use the large BGP community as follows:
- Do not announce a prefix to a certain peer: 56584:0:peer-as
- Announce a prefix to a certain peer: 56584:1:peer-as
- Do not announce a prefix to any peer: 56584:0:0

Route target extended BGP community
- do not announce a prefix to a certain peer: RT:0:peer-as
- announce a prefix to a certain peer: RT:56584:peer-as
- do not announce a prefix to any peer: RT:56584:0

AS path prepending
InterIX route server peers are able to add one or more AS numbers to the left side of the AS path and advertise it only to a certain member(s) by using below large BGP communities:
- prepend with one AS number to a certain peer: 56584:101:peer-as
- prepend with two AS numbers to a certain peer: 56584:102:peer-as
- prepend with three AS numbers to a certain peer: 56584:103:peer-as
