Peering Policy

This page outlines the peering policy for connecting with the VONet Mesh Network via the VONet-operated Internet Exchange Point (IXP). This exchange provides a neutral interconnection platform, but this policy applies specifically to peering with VONet itself as a network participant.

1. Policy Overview

VONet is a nonprofit, community-led mesh network that aims to improve local connectivity by enabling efficient, direct routing between community members and other networks.

Through the VONet IXP platform, external networks may establish BGP peering with the VONet Mesh Network, either directly or via the public route servers managed by VONet.

2. General Participation Requirements

To peer with VONet, participants must:

• Operate a network with a valid Autonomous System Number (ASN)
• Be able to establish BGP sessions over IPv4 and/or IPv6
• Hold IP address space allocated by a recognized RIR (e.g. ARIN, RIPE, LACNIC)
• Maintain accurate entries in PeeringDB and a public IRR (Internet Routing Registry)
• Follow Internet routing best practices and community etiquette

Community networks, nonprofits, research institutions, and small ISPs are especially encouraged to peer.

3. Technical Requirements

To peer with VONet:

• Connections must be made via the VONet IXP platform (physical or virtual cross-connects are supported)
• Participants must present a consistent MAC address and clean BGP configuration
• Only BGP is supported; no broadcast traffic, proxy ARP, or dynamic IGPs
• All routing sessions must be established over secure, well-maintained routers
• Tunnel-based remote peering is possible with prior coordination

4. BGP Session Requirements

BGP sessions with VONet (either directly or via the IXP route servers) are subject to:

• Proper route origin validation (only announce prefixes your ASN is authorized to originate)
• IRR registration of all announced prefixes
• RPKI ROAs for announced prefixes
• Respect for max-prefix limits, prefix length constraints, and filtering rules
• No default routes or full tables to VONet route servers

Sessions may be terminated or filtered if these requirements are not met.

5. Routing Security and Filtering

VONet enforces routing security for all peering sessions through:

• RPKI origin validation (using RTR protocol with local validator)
• IRR-based prefix and ASN filtering
• Prefix size filtering (no smaller than /24 IPv4 or /48 IPv6)
• Max-prefix limits to avoid accidental route leaks

Invalid or unregistered routes will be rejected. Peers are responsible for maintaining valid IRR and RPKI records.

6. Route Servers (Optional)

VONet operates route servers at the IXP for networks that wish to peer with VONet and other participants without establishing individual BGP sessions.

• Route servers apply the same security filtering and policies described above
• Next-hop is preserved (VONet does not forward traffic through itself)
• Participation in the route server is optional; bilateral peering is also supported

7. Traffic and Usage Guidelines

While peering with VONet:

• Do not use the IXP as a transit path between unrelated networks
• Traffic should be destined for or originate from VONet or its mesh network participants
• Do not send abusive or unsolicited traffic
• VONet may monitor route and traffic patterns for abuse detection or troubleshooting (but does not inspect payload content)

8. Costs and Access

Peering with VONet is free for qualifying networks. There are no commercial charges.

VONet is a nonprofit and relies on volunteers, donations, and community support to operate. In-kind contributions are welcomed but not required.

9. How to Peer with VONet

To get started:

• Email support@vonet.org with your ASN and a brief description of your network
• Ensure your prefixes are properly registered in an IRR and covered by RPKI ROAs
• Make sure your PeeringDB entry is up to date
• Coordinate your connection via the VONet IXP (physical port or remote tunnel)

Once approved, we will assign an IP address on the IXP LAN and provide BGP session details.

10. Contact

For peering requests or technical questions:

Email: support@vonet.org Website: https://vonet.org PeeringDB: