Purpose
ZANOG follows industry best practices when building and operating network infrastructure.
This peering policy outlines the expectations and requirements for networks wishing to peer with ZANOG.
Our goal is to ensure stable, scalable, and mutually beneficial interconnection for all parties.
Peering Policy
ZANOG maintains an Open Peering Policy and will peer with any network that meets the technical and operational requirements outlined below.
Mandatory Requirements
PeeringDB
Peers must maintain a complete and up-to-date PeeringDB profile.
Dual-Stack Peering
Both IPv4 and IPv6 peering sessions must be configured and established across all available IXP connections where both networks are present.
Consistent Prefix Advertisement
Prefixes must be consistently advertised across all IXPs within the same metropolitan or regional area where both networks maintain connectivity. This ensures balanced traffic flow and improves resilience during maintenance or outages.
Adequate Capacity
Peers must ensure sufficient available capacity on all peering links to avoid congestion.
IPv6 Support
IPv6 support is required.
IPv6 is now considered standard practice for modern network operations. All peers must support and establish both IPv4 and IPv6 peering sessions.
PeeringDB
ZANOG uses PeeringDB as the authoritative source for establishing peering sessions.
Peers must maintain an accurate and up-to-date PeeringDB profile including:
• Peering IP addresses
• Maximum prefix limits
• AS-SET information for filtering
• Operational contact details
Routing Security
Peers are expected to maintain accurate routing information.
- Prefixes should have valid IRR route/route6 objects registered in an Internet Routing Registry.
• Prefixes should have valid ROAs published via the Resource Public Key Infrastructure (RPKI).
• ZANOG may implement RPKI origin validation and IRR-based filtering.
Prefix Filtering
ZANOG applies prefix filtering based on IRR data and/or AS-SET information published by peers.
Maximum prefix limits are configured based on values published in PeeringDB. Peers must ensure their AS-SET and maximum prefix values remain accurate and updated as their routing table grows.
Content Distribution
ZANOG hosts various content caches within its ASN and makes this content available at no cost to all peers across IXPs where both the content and ZANOG are present.
ZANOG peers with the route servers at all IXPs where it is present.
However, prefixes learned via bilateral peering sessions are the only prefixes announced to caches hosted within the ZANOG ASN. Peers will therefore only receive cached content if bilateral sessions are established.
Route server peering is supported for general reachability, but bilateral sessions are required to receive cache-originated traffic.
Operational Contact
Peers must provide valid operational contact details via their PeeringDB profile.
Networks are encouraged to maintain:
• A Network Operations Centre (NOC) contact
• A monitored email address for peering issues
• Accurate contact information listed in PeeringDB
Operational communication regarding peering issues will primarily take place using the contact information published in PeeringDB.
Redundancy and Capacity
Multiple Internet Exchange Points (IXPs), and multiple connections to IXPs where available, are strongly recommended.
This ensures sufficient capacity and redundancy in the event of failures, maintenance, or congestion affecting any single exchange or interconnection.
Maximum prefix limits are configured based on values published in PeeringDB. Peers must ensure their AS-SET and maximum prefix values remain accurate and updated as their routing table grows.
Capacity Management
Peers should maintain sufficient capacity on peering interconnections to ensure a high-quality exchange of traffic.
Where sustained congestion is observed, ZANOG may adjust routing preferences or traffic engineering policies until additional capacity is deployed. ZANOG will make reasonable efforts to communicate with peers to resolve congestion in a timely manner.
Policy Compliance Disclaimer
Peers are expected to maintain compliance with all mandatory requirements outlined in this policy. ZANOG reserves the right to terminate or suspend peering sessions if these requirements are not met or are no longer maintained. ZANOG will make reasonable efforts to notify peers in advance of any termination or suspension.