API VERSA OU, under AS210464, offers peering services through Internet Exchange Points (IXPs) without transit. This policy outlines the terms and conditions governing peering relationships, ensuring efficient and mutually beneficial connectivity over IXPs.
2) Peering Terms
Peering will only occur over a mutually agreed upon IXP. No transit services are offered under this policy, and API VERSA OU will not provide connectivity to any third-party networks.
Both parties agree to exchange only mutually agreed upon prefixes.
Peering is strictly settlement-free unless otherwise agreed upon.
3) Routing Policy
API VERSA OU will advertise only its own prefixes and those of its downstream customers that have explicit consent.
API VERSA OU expects the peer to advertise only the prefixes that belong to them or their downstream customers.
API VERSA OU supports both IPv4 and IPv6 routes over peering sessions.
API VERSA OU uses AS-SETs for proper filtering and expects peers to maintain up-to-date AS-SET information on PeeringDB.
4) Traffic and Prefix Limits
Peering partners are expected to exchange traffic solely for their own networks and their directly connected customers.
API VERSA OU reserves the right to apply maximum prefix limits to prevent route leaks or misconfigurations.
5) Network and Operational Requirements
The peer must operate a professionally managed, 24x7x365 network operations center (NOC).
The peer must have an up-to-date PeeringDB entry, including accurate technical and operational contacts.
The peer must maintain appropriate measures to ensure network security and prevent abuse, including filtering for bogon or private IP space routes.
Traffic exchange must be balanced within reasonable expectations, with no overwhelming asymmetric traffic from one side unless agreed upon in advance.
6) Blackholing and Route Filtering
API VERSA OU supports the use of blackholing for DoS/DDoS mitigation using standard BGP community tags.
Both parties must apply appropriate filtering to avoid route leaks, including rejecting prefixes longer than /24 for IPv4 and /48 for IPv6 unless explicitly agreed upon.
7) Termination of Peering
Either party may terminate peering with written notice at any time. Immediate termination can occur in case of policy violations or security threats.
API VERSA OU reserves the right to suspend or terminate the peering relationship if the peer’s network is used for illegal activities or violates any applicable laws and regulations.
8) No Reselling
Peers are prohibited from reselling or offering the peering connection as a transit service to third parties. Peering is for the direct exchange of traffic between API VERSA OU and the peer only.
9) Technical Details
API VERSA OU will maintain a BGP session with peers over the IXP.
API VERSA OU prefers the use of MD5 authentication for BGP sessions, and peers are encouraged to enable it.
Peers must maintain redundancy and not create single points of failure within the IXP environment.
10) Amendments and Revisions
API VERSA OU reserves the right to amend this Peering Policy at any time. Peers will be notified of significant changes that affect the relationship.
Continued peering after changes to this policy implies acceptance of the updated Peering Policy.
11) Dispute Resolution
Any disputes regarding peering shall be handled through direct communication between the network operators. If unresolved, API VERSA OU reserves the right to escalate to a governing legal framework.
12) Governing Law
This Policy is governed by the laws of Estonia, and any disputes will be resolved in the courts of Estonia.