Summary

This document describes the peering policies for Icolo.io (AS328162).

Policy Statement

icolo.io has an open peering policy, all networks matching the following technical requirements are welcome to peer with us.

Our preference is to setup multiple peering sessions for redundancy wherever and whenever possible, and to use md5 authentication on all peers.

icolo.io will also peer with route servers on all IXPs where we are present. In general, peering sessions with AS328162 will advertise all AS328162:AS-SET-ICOLO (in AFRINIC IRR database) routes.

Peering Requirements (General)

• To be eligible for peering, each candidate must:
• Use a registered public autonomous system (AS) number;
• Publish valid contact information via PeeringDB;
• Maintain valid AS and prefix records with a public Internet Routing Registry (IRR);
• Highly recommended to use RPKI validation;
• Be able to use TCP MD5 authentication on Peer connections; and
• Comply with MANRS
• A peer may only send toward us traffic intended for a destination network we advertise. The use of static or default routes toward us is not permitted.
• Peers must ensure that their policies in PeeringDB (e.g. maximum prefix count) are kept accurate.
• The following features are encouraged but not required:
• RFC 7999—BLACKHOLE community
• RFC 8326—Graceful BGP session shutdown

Operations

Icolo will review it's peering policy periodically and reserves the right to modify this policy at any time and without notice. We may also filter any routes which we determine should not be advertised to AS328162 over the agreed upon peering session. We will by default filter any bogon prefixes (i.e. IP space allocated by RFCs 1918, 5735, and 6598) and default routes.