In general, 10VPN maintains an open peering policy. If a network shares a common POP with 10VPN (either via IX or dedicated cross-connect) then 10VPN will peer in that location. Peering in multiple common POPs, while not required, is encouraged. 10VPN requires that all peers adhere to the following:
- Only advertise prefixes for the networks for which you operate
- Do not point static or default routes towards 10VPN unless explicitly granted permission
- Use IRR or RPKI filtering whenever possible
- Maintain a NOC reachable by email or phone
10VPN strongly encourages the use of IRRDB to describe a networks routing policy and valid prefixes. 10VPN operates several IRR AS-SETs:
- AS-10VPN-RESEARCH - This ASSET is available in the RIPE database and describes the members of our research network
- AS-10VPN-PEERS - This ASSET is available in the RIPE database and includes all networks that 10VPN Research expects to peer with. We will include IX ASSETs when available.
- AS-10VPN-TRANSIT - This ASSET is available in the RIPE database and describes all networks that 10VPN purchases transit from.
- AS-10VPN - This ASSET is available in ARIN and describes all the members of our production network.
- AS-10VPN-CUST - This ASSET (available in ARIN) contains all our customer networks (networks we provide transit to).