OpenAccess seeks to interconnect its IP network with other Internet providers on a settlement-free basis when such interconnection are of mutual benefit to both parties.

Due to historical and business reasons, OpenAccess uses AS36696 as its primary ASN for peering and all peers are required to also accept prefixes and AS paths for AS13831 and AS17129.

OpenAccess does not require formal contracts for peering arrangements, but the following guidelines apply.

General Guidelines

1. Meeting the requirements of this document does not require OpenAccess to establish a peering relationship.
2. A network (ASN) that is a BGP transit customer of OpenAccess or a partner network for any dedicated IP services may not simultaneously be a settlement-free peer of that same network.
   
3. All peers must supply an operational contact that is available on a 24x7 basis such as a Network Operations Center or equivalent. Both voice and e-mail contact information is required.
4. Peers should provide a looking glass and/or traceroute server at each interconnection point to assist in troubleshooting.
   
5. Peer must agree to actively cooperate to resolve security incidents, denial of service attacks, and other operational problems.
6. A good faith effort should be made to communicate information regarding network maintenance that will affect traffic exchange.

Technical and Routing Requirements

1. Peers must not utilize any form of gateway of last resort or default route that is directed at OpenAccess.
2. Neither party shall modify, sell or provide the next-hop to a third party.
   
3. All announcements are to be consistent, in terms of prefix aggregation properties, across all interconnect locations.
4. Peers are expected to filter their clients to reject both unauthorized BGP announcements, aggregate prefixes announced as well as filter their prefixes to deny IP datagrams with invalid source addresses.
5. Use of the Internet Routing Registry is encouraged. OpenAccess reserves the right to make entries into the IRR on behalf of the peer if needed.
   

Suspension and Termination

1. OpenAccess reserves the right to suspend peering for an indefinite period of time should any form of network abuse be verified to take place via the peering interconnect.
2. Recurring incidents of network abuse and/or slow responses on curing an incident will result in termination of the peering relationship.
3. OpenAccess reserves the right to terminate the peering relation for any reason with 30 days notice.
   

The definition of network abuse includes but is not limited to:

• Denial of Service attacks
  
• Unsolicited Bulk Email sources
• Setting default-route to OpenAccess