This document sets forth Entanet's policy for settlement-free interconnection (the "Policy"), also known as "peering". Entanet updates this policy from time to time and maintains the current version on the Entanet peering web site at http://www.as8468.net/.Definitions
Section 1 of the Policy lists the requirements that an Internet Network requesting peering (the "Requester") must satisfy in order to qualify for settlement-free peering. For the purposes of this policy, an Internet Network must be a single Autonomous System Number (ASN). A company with more than one ASN will have each ASN considered separately.
Section 2 of the policy lists the operational requirements that must be met by the Requester.
Section 3 outlines the process by which peering will be established.
This Policy applies to all requests for settlement-free interconnection with the Entanet Internet Network either by dedicated connections ("private peering") or by multi-party network access points ("public peering").
1. Peering Requirements
1.1 Public Peering:
1.1.1 Network Scope: Requester shall have the ability to interconnect with Entanet in a minimum of two geographically diverse peering locations where Entanet has a peering point of presence.
1.1.2 Minimum utilization: The peering Requester must have a minimum aggregate of 5 Mbps and a maximum of 200 Mbps on any single peering exchange.
1.1.3 Minimum # of routes: Peering Requester must carry minimum of 1 unique route in Interconnect routers, and announce consistent routes using BGP4 at all peering locations. Entanet will not permit routes longer than a /24 from its peers.
1.1.4 Existing IP Transit Customers of Entanet are not generally eligible for peering.
1.2 Private Peering:
1.2.1 Network Scope: The Requester must operate an Internet network in either:
(a) two cities in Europe,
(b) one city in the Americas, &/or
(c) Pacific Rim
1.2.2 Network Capacity: The Requester must have a backbone with a minimum two 1G, OC-12 or STM-4 between any two backbone cities.
1.2.3 Minimum Interconnect: Requester shall have the ability to interconnect with Entanet in a minimum of two geographically diverse peering locations where Entanet has a peering point of presence. The peering Requester must have the ability to interconnect directly at a minimum GigE (1000 Mbps) or greater capacity levels at each point of interconnection.
1.2.4 Minimum # of routes: Peering Requester must carry full customer routes in Interconnect routers, and announce consistent routes using BGP4 at all peering locations. Entanet will not permit routes longer than a /24 from its peers.
1.2.5 Existing IP Transit Customers of Entanet are not generally eligible for peering.
2. Operational Requirements
2.1. The Requester must operate a 24x7 NOC or an equivalent support system that responds to reported issues within 24 hours and can resolve abuse, security, or routing issues within 48 hours.
2.2. The Requester must operate a network with sufficient redundancy and capacity that the failure of a single node will not significantly affect performance.
2.3 The ratio of the aggregate amount of traffic exchanged between the Requester and the Entanet with which it seeks to interconnect shall be roughly balanced and shall not exceed bidirectional ratio of 2:1.
2.4 Hot-potato routing is implied (i.e. we will not send or honour MEDs).
2.5 MD5 passwords are not required for BGP sessions.
2.6. The Requester shall not point default into or transit the other Network where that network has not advertised a route for the destination in question.
2.7. The Requester shall monitor the usage of all interconnection links. If the utilization of any single link should exceed 90% for a period of at least one hour for three consecutive days, the Networks shall work together to increase capacity or to reroute traffic in order to reduce utilization.
2.8. The Requester shall be responsible for communicating with its customers with respect to its Internet Network and the services, including Internet connectivity.
2.9 Interconnection Requester must provide 48 hours notice to Entanet NOC for scheduled maintenance. Said maintenance windows to be between 02:00hrs and 05:00hrs of local time.
2.10 Joint quarterly capacity planning reviews for interconnection augmentation to accommodate traffic growth and minimise the possibility of latency or packet loss between both networks.
2.11 Peers who are unable to maintain the minimums listed in sections 1 & 2 may be given 30 days written notice to remedy the situation
3. Peering Process
3.1. The Requester and Entanet must enter into a bilateral Peering Agreement.
3.2. The requirements set forth in Section 1 of this policy must be met at the time the request for settlement-free peering with Entanet is made. All requirements in this Policy must continue be met in order for the Requester to remain eligible for peering.
3.3 Entanet may require a trial peering connection spanning a minimum of one month with the Requester to measure accurately the traffic ratios between the Requester and Entanet. A successful trial does not guarantee that Entanet will peer with this Requester.
3.4. All requests for settlement-free peering must be submitted via e-mail to firstname.lastname@example.org. The e-mail should include:
3.5. Entanet reserves the right to grant or refuse peering to a Requestor, whether or not they would otherwise meet these requirements.