Peering Policy

 

 

Peering Policy

This document outlines the guidelines and requirements that NationalNet uses to determine whether a network qualifies for peering. NationalNet reserves the right to modify this document at any time without notice.

 

 

1. Internet Peering Requirements

 

• 1. Both parties shall operate an experienced Network Operations Center manned 24 hours a day, 7 days a week. Should network issues arise, there should be an escalation procedure in place to allow for the timely resolution of issues.

 

• 2. Potential peering partners must have a strict filtering policy in place to prevent route leaks.

 

• 3. Should you plan network maintenance, notification should be provided in a timely manner.

 

• 4. Both parties will be responsible for abiding by the others AUP and TOS. In the event of a Denial of Service attack, both parties should have qualified engineers in place and every effort should be made to cooperate in order to mitigate the attack as quickly as possible.

   

2. Technical & Routing Requirements

 

• 1. Both parties should maintain sufficient connectivity and capacity to enable saturation free delivery of traffic. It is expected that both parties will act proactively to establish additional capacity to accommodate traffic growth and have the ability to monitor traffic growth in order to be proactive.

 

• 2. Neither party shall point default "route of last resort"; add a static route; or otherwise send traffic to the other party for a route not advertised via BGP.

 

• 3. Neither party shall modify, sell, or provide the next-hop to a third party.

 

• 4. Under no circumstances shall the interconnection partner be a simultaneous peer and transit customer. This is strictly forbidden.

 

• 5. Generally, NationalNet will not peer with downstream transit customers of existing peering partners, however under some circumstances we may alter this decision you may contact us for further evaluation.

 

Please Contact Us should you wish to peer with us.