Technical Requirements
- A fully redundant network with sufficient capacity to exchange traffic without congestion
- Peer has a public routable Autonomous System Number (ASN)
- MD5 is not supported
ASN details
- Xyberdata manages AS5536 and other ASNs as described in AS-SET AFRINIC::AS-XYBERDATA
Routing policy
- Peer has at least one public routable /24 prefix
- Xyberdata overwrites received Multi Exit Discriminators (MED)
- Xyberdata prefers to receive BGP community tags from peers to indicate route origination
- Unless specifically agreed upon beforehand, peers are expected to announce consistent routes
- In general, Xyberdata advertises all Xyberdata routes, with some regional specifics as appropriate
- All prefixes must be properly ROA signed
- Xyberdata applies well known BGP community 'No-Export' to all egress/ingress peer routes
- Neither party shall attempt to establish a static route, a route of last resort, or otherwise to the other party
Operational requirements
- A fully staffed 24x7 Network Operations Center (NOC)
- Peers are expected to have a complete and up-to-date profile on PeeringDB
Physical connection requirements
- The locations where you can connect with Xyberdata are listed on PeeringDB
- Peering consists of two connections to two Xyberdata edge routers from the peer edge routers
- Peer may choose not to deploy redundant devices at their end