Unicast IPv4
Multicast
IPv6
Never via route servers
We require peers to have a peering db entry and adequately maintain the entry to reflect current information.
We expect peers to provide us contact details via Peeringdb (either telephonic or email based) where we can address peering related issues. Such contact points should be monitored and responded to in a timely fashion.
We ask our peers to reciprocate with shortest exit (‘hot potato’) routing.
We ask peers to avoid excessive pre‐pending and de-aggregation where possible.
We expect peers to honour the ‘no-export’ BGP community sent by us.
Peers must agree never to statically route, or otherwise cause traffic, to flow towards any prefix we do not explicitly announce via BGP.
ZANOG will only peer via eBGP on public ASN’s, on public address space (we will not peer over RFC1918 address space or to a private ASN).
We expect peers to maintain a route set in a route registry of their choice, and have it listed in peeringdb, by which we will generate filters from
We expect the RPKI signing of all transmitted prefixes.
We expect peers to only announce prefixes that are legitimately assigned to them or their customers.
We expect peers to have sufficient capacity on their peering links to avoid congestion and reserve the right to de-peer any party who is consistently running congested peering circuits.
ok
2024-06-26T04:47:55Z
