Peering through route servers is usually preferred over dedicated BGP sessions, especially for low-volume, low-prefix peers that are already connected to the route servers. This is to avoid unnecessary maintenance and configuration overhead.

Although having a generally open peering policy we still evaluate each request based on its merits and require:

• common sense
• must filter customer prefixes strictly
• must not leak prefixes from non-customer sessions (even if the prefix is from a customer)
• an updated peeringdb entry
• reasonable prefix aggregation
• responsive NOC
• peers IX-link must not be congested
• IPv6 peering, if peer AS is v6 enabled
• must not be our customer, or a customer of a existing peer
• do not send automated emails to our NOC for whatever reason; humans only!