* |
Each peer must establish and maintain links to facilitate mutually acceptable performance and shall be liable in most cases for half the costs of the interconnect |
* |
All BGP sessions require MD5 passwords |
* |
Each peer must operate a 24x7 Network Operations Centre or Monitoring Centre or provide a mechanism to report and action faults 24x7 |
* |
Each peer must set next hop to be itself and must not set a route of last resort pointing to AS5413 |
* |
Each peer shall advertise consistent route announcements at all public peering points |
* |
Each peer shall have a total minimum busy hour traffic exchange of 100mb |
* |
Each peer shall provide a backup session over a public exchange to protect against service interruption on single private interconnect |
* |
Hot-potato routing is implied, (we will choose our exit best for AS5413, we will not normally honour meds) |
* |
AS5413 will 'set community none' on all received routes (including routes received with no-export/no-advertise) |
* |
Each peer shall assist with quarterly capacity planning reviews to accommodate traffic growth and ensure least latency and packet loss path |
* |
Willingness to enter into a Bilateral Interconnect Agreement and Non-Disclosure Agreement with AS5413 |
* |
Each peer will maintain accurate prefix and routing information in a publicly accessible Internet Routing Registry (IRR). |
* |
Each peer and AS5413 shall announce only their infrastructure and own customer routes |
* |
AS5413 will prefer the private interconnect for best path. Daisy Communications expects the peer to do the same unless agreed otherwise |