Peering policy
Requirements for peering
AS216212 maintains an open peering policy without specific requirements for peering. We however strongly recommend networks to consider peering if:
Upwards of 2Gbps flow between the network and AS216212.
Routing paths could benefit considerably from direct interconnection.
Reliability issues exist between AS216212 carriers and the network's carriers.
Best-practices
When peering with AS216212 we ask you to commit to the following:
If the network and AS216212 share more than one mutual IXP that sessions be provisioned at all mutual IXPs.
Configure sessions for IPv4 and IPv6 (where possible), even if the network currently only uses one of the two protocols.
Establish redundant sessions at IXPs where AS216212 maintains multiple ports for redundancy.
Inbound policy
We will apply the following to routes inbound to AS216212:
Reject IPv4 routes of prefix length greater than /24, and smaller than /8.
Reject IPv6 routes of prefix length greater than /48, and smaller than /16.
Reject RFC1918 prefixes.
Reject RPKI invalid prefixes.
Reject paths with bogon ASNs.
Reject paths with well-known transit ASNs.
Reject paths with unexpected ASNs after the peer ASN (AS set filtering).
Although AS216212 enforces strict outbound policies, we recommend peers apply similar inbound policies to our sessions.
Strict requirements
Peers must meet the following criteria:
Maintain an up-to-date PeeringDB entry accurately reflecting the network's points of interconnection, prefix limits, traffic ratios, geographic scope, and network type.
For networks with a cone larger than one (1), provide us with an AS set to filter on.
Have a publicly routable ASN from a Regional Internet Registry, ideally with a public routing policy published with RPSL.
Have a NOC reachable at least 12/7.