Community Structure

​

AS134555 supports the use of Large BGP Communities (RFC8092) for granular control over routing policies. The community format follows the model defined in RFC8195, and is defined as follows:

 

<Encoo ASN>:<Function Field>:<Upstream ASN>

 

Encoo ASN:

 

This is the Autonomous System Number (ASN) of Encoo Pty Ltd. In all communities, this field will be 134555.

 

​

Function Field:

 

This is a three-digit code that defines the specific action to be taken when a route carrying this community is received.

 

The function codes are:

• 101: Prepend once to the specified ASN

• 102: Prepend twice to the specified ASN

• 103: Prepend three times to the specified ASN

• 0: No export to the specified ASN

Upstream ASN:

 

This is the ASN of the upstream provider to whom the action defined by the function field applies. If this field is 0, it means that the action applies to all upstream providers.

 

Examples of Use
 

Here are examples of how these communities could be used:

 

• Community 134555:101:4826 - This community would result in AS134555 prepending its ASN once when advertising routes to Vocus (ASN 4826).

• Community 134555:102:4826 - This community would result in AS134555 prepending its ASN twice when advertising routes to Vocus (ASN 4826).

• Community 134555:103:4826 - This community would result in AS134555 prepending its ASN three times when advertising routes to Vocus (ASN 4826).

• Community 134555:0:4826 - This community would prevent AS134555 from exporting routes to Vocus (ASN 4826).

 

If a route carries multiple communities, all applicable actions will be applied to the route.

​

​

​