AS31712 - Gigastream plc
Routing Policy

 

Gigastream logo

 

AS Padding

Customers with public AS numbers may pad their AS path to control the desirability of their connections. Customers with an assigned private AS number may not pad their AS path. Gigastream may treat the padding of private AS numbers from customers inconsistently.

Export/No-Export Peer Controls

Customers may manipulate the announcement of their own routes through the tagging of prefixes with the following communities:

Community   Effect

65200:<as>

do not announce to peer

65201:<as>

prepend adverts to peer 1x

65202:<as>

prepend adverts to peer 2x

65203:<as>

prepend adverts to peer 3x

Where <as> should be replaced with the peer ASN or the second part of the route origin community as detailed below. To manipulate route advertisements for all peers at an exchange point use the ASN of the IXP's route collector network. For example to cease announcements across the LINX use 65500:5459 or to cease announcements to all transit providers use 65500:65100.

These communities do not combine correctly. You will see strange behaviour if you attempt to manipulate advertisements to an AS and at an exchange point at which we peer with the same AS. Please contact us through your normal support channels if you need to discuss combining these features.

Gigastream will also accept the well-known community "no-export".

Null Route Prefix - DDOS Mitigation

Customers may associate the community 31712:666 with any prefix of /30 or longer (/32 is preferred) within their agreed prefix list. Gigastream will null route all prefixes heard with this community as early as possible within the network to mitigate the effects of a DDOS attack. You must stop advertising null routed prefixes as soon as reasonably possible.

MED (Multi Exit Discriminator)

Gigastream can accept MEDs from customers to adjust route preference on the network. Please contact us through your normal support channels for more information.

Prefix Length Limitations

Gigastream accepts only those prefixes of length /24 and shorter from peers.

Gigastream will accept any properly registered prefix from a customer but will announce only /24 and shorter prefixes to peers.

Route Origin Communities

Routes announced to customers may have one of the following communities associated with them:

Community   Route Origin

31712:65000

Local route

31712:65010

Customer route

31712:65050

Partial transit route (UK)

31712:65070

Partial transit route (EU)

31712:65100

Full transit route

Local Prefs

All customer routes seen by Gigastream will have a local pref higher than the network default.

Customers may adjust the local pref on routes advertised to Gigastream through the use of the following communities:

Community   Effect

65300

Routes tagged with this community will be de-preferred below all other routes

65350

Routes tagged with this community will be de-preferred below those learnt from peers

65400

Routes tagged with this community will be treated equally to those learnt from peers (and de-preferred below those learnt from customers)

65475

Routes tagged with this community will be preferred over others learnt from customers

Any Questions?

peering@gigastream.net