Settlement-Free Peering Policy

For Autonomous System 25525

October 29, 2007

This Peering Policy describes the criteria that REASONNET IP NETWORKS has established for engaging in settlement-free peering relationships for connections with its AS25525 network.  REASONNET IP NETWORKS may modify this Peering Policy at any time. This Peering Policy seeks to establish transparent rules for peering connections between REASONNET IP NETWORKS AS25525 and other IP networks where such exchanges offer equitable benefits and are cost-effective.

Please keep in mind that this policy is only a guideline. Therefore, REASONNET IP NETWORKS may refuse or agree to setup peering without any justification, and might even shutdown active peering sessions provided a prior 24 hours notice is issued.

REASONNET IP NETWORKS wants to provide best possible connections towards other networks shorter routes don.t always mean best routes. Therefore once a peering has been established the peering relationship will be reviewed periodically to ensure joint capacity planning and to ensure that all peering criteria are still met.

REASONNET IP NETWORKS conducts periodic internal reviews of its Peering Policy to ensure that the criteria and eligibility requirements for peering eligibility are consistent with REASONNET IP NETWORKS. network growth and expansion and business needs.   This Peering Policy will be revised on a regular basis to reflect this analysis.  Existing peering partners may be asked at times to re-qualify for continued peering.

I.                      Definitions

Peering is the exchange of IP traffic between two interconnected IP networks.  This exchange is strictly limited to traffic destined for the other network.  Traffic is exchanged on a bilateral basis between peering routers and is governed by BGP-4 peering sessions.

Transit indicates a settlement based customer/provider relationship between networks, where one network uses the other network to provide upstream connectivity.

Route announcement The means by which two peering partners notify each other of address information in order for the peering partners to exchange Internet traffic. The current means is by the BGP-4 protocol.

Network A network or Autonomous System (AS) is defined as a group of connected Internet Protocol (IP) routers that are under one administrative control.

Applicant: A company with a Network applying for settlement free peering with REASONNET IP NETWORKS AS25525.

RIPN: REASONNET IP NETWORKS (AS25525)

II.        General Conditions & Requirements

It is within RIPN sole discretion to modify, replace, or discontinue this policy at any time. Any such decision made by RIPN concerning such Policy will be final, binding, and conclusive.

The Applicant must not be a RIPN IP-transit customer in the past 12 months, or a customer route.

Neither party will apply port, service, or other charges to the other party.

The Applicant shall make available a twenty-four hour, seven-day-a-week (.24x7.) contact for peering issues.

The Applicant shall operate a twenty-four hour, seven-day-a-week (.24x7.) Network Operations Center (NOC) under its sole control.

III.       Traffic Requirements

1.      Public Peering

A.      The total 95%tile traffic volume at all peering connection shall average at least 25 Mbps. Traffic volumes shall the sum of both direction; inbound and outbound on a weekly averaged basis.

B.       Each peering connection speed shall be at least 1GBps.

C.      The weekly aggregated 95th percentile traffic ratio shall not exceed 4:1.  The applicant must be able to maintain this ratio without employing permanent traffic manipulation, including AS prepending.

2.      Private Peering

A.      The total 95%tile traffic volume at all peering connection shall average at least 150 Mbps. Traffic volumes shall the sum of both direction; inbound and outbound on a weekly averaged basis.

IV.               Routing Requirements

Each Applicant shall meet the following requirements with respect to routing:

A.      The Applicant shall register routes and routing policy with RIPE, APNIC or ARIN.

B.      The Applicant shall not establish a route of last resort also known as a default route, directed to RIPN.

C.      Both the Applicant and RIPN shall announce only customer routes, and will not announce any routes from any of its peers.

D.      The Applicant shall support Classless Internet Domain Routing (.CIDR.) exchanged at edge routers using BGP-4.  The routes advertised shall be sufficiently aggregated routes. Both parties may agree to operate any later routing protocol that may be defined.

E.      RIPN may require the Applicant to filter routes at the Applicant.s network edge, i.e. listen to the routes that the Applicant.s customers have pre-registered so that such customers do not announce routes that are not pre-registered.

F.      The Applicant must filter its BGP customer.s routes by prefix or AS to ensure that these customers do not announce unauthorized Internet routes.

G.      The Applicant will announce consistent routing announcements to RIPN.  Consistent announcements require that all routes be announced at all peering sites with the same aggregation properties.

H.      RIPN doesn.t honour meds or other attributes that are at the Applicants control, so called hot-potato routing is applied through the RIPN backbone.