AS328112 Peering Policy
- 1
We peer openly.
- 2We support both public and private peering.
- 3We do not require a minimum amount of traffic to peer.
- 4We do not consider traffic ratios to peer.
- 5While not mandatory, we encourage peering in multiple, mutual locations.
- 6We do not require a contract to peer.
- 7We do not support contracts for public peering.
- 8We can support contracts for private peering if required by our peering partner.
- 9We do not peer with our IP Transit or Internet Access customers.
- 10We may not peer with networks that are customers of our customers.
- 11We announce only AllWorldIT routes and AllWorldIT customer routes.
- 12
We announce routes consistently across all peering sessions, barring any customer-induced traffic engineering implementations.
- 13We do not provide any kind of global IP Transit or Internet Access across peering sessions.
- 14We do not provide access to AllWorldIT on-net services or CDNs across peering sessions.
- 15
We generally peer with route servers.
- 16
We generally peer with route collectors.
- 17We exchange both IPv4 and IPv6 routes.
- 18
We do prefix-based filtering based on IRR records and automated AS_PATH-based filtering for peer routes using RPSL.
- 19
We set “max-prefix” values for route control based on the peers PeeringDB entry.
- 20We do not accept (or announce) private or reserved IP address space, we do not accept (or announce) private AS numbers.
- 21We do not accept (or announce) IPv4 routes smaller than a /24 or IPv6 routes smaller than a /64.
- 22We encourage our peers to set “max-prefix” values for route control in order to reduce administrative overhead and speed up improvement in routing quality enabled by peering. However, we understand each network employs its own policy in this regard, and we shall respect it.
- 23We perform a strict and extensive combination of prefix, AS_PATH, and “max-prefix” based filtering on all BGP sessions with our downstream customers. As such, our peers are guaranteed of good, clean routing when they peer with AllWorldIT.
- 24We filter (and drop) traffic sourced from or destined to any private or reserved IP address space, in either direction of the peering session.
- 25We do not accept any routes from route collectors.
- 26
Peers are not permitted to point static routes toward our routers (including default route), doing so will result in your ASN being dropped from our edge.
- 27We do not accept customer routes from peers.
- 28We only configure private BGP sessions for IPv4 and IPv6. We do not accept peering requests for IPv4 only.
- 29
Private BGP sessions with excessive flapping, or which have been offline without notification, will be removed.