Operational Requirements
- Peer must have an Autonomous System Number (ASN) and at least one publicly-routable IP block (/24 or bigger for IPv4 and /48 or bigger for IPv6) issued by a Regional Internet Registry (RIR).
- Peer must have a Network Operation Center (NOC) or similar capability staffed 24x7 with qualified engineers
- Peer must keep an up to date record in PeeringDB containing at a minimum of all peering locations and an up to date list of contacts.
- Peer must commit to upgrading links or adding peering locations if the any site has a consistent usage of 80% or more of the link speed.
- Peer must agree to establish peering at all mutual locations
Technical Requirements
- Peer must support BGP4 protocol
- Peer must use hot-potato routing on all links
- Peer must support IPv4 and IPv6 peering at all locations (native or dual-stack)
- Peer must not set the link as a gateway of last resort or forward traffic across the link for an unadvertised route.
- Peer must not use link to connect two isolated sites or networks controlled by the same organization.
- Peer must support community-triggered blackholing of traffic including prefixes as small as /24 for IPv4 and /128 for IPv6.
- Peer must not transmit link-local, broadcast, or multicast traffic across the link.
