This Policy applies to all requests for settlement-free interconnection with the IPTP Networks 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 IPTP Networks in a minimum of two geographically diverse peering locations where IPTP Networks has a peering point of presence.
1.1.2 Minimum utilization: The peering Candidate must have a minimum aggregate of 10 Mbps and a maximum of 10000 Mbps on any single peering exchange.
1.1.3 Minimum # of routes: Peering Candidate must carry minimum of 10 unique routes in Interconnect routers, and announce consistent routes using BGP4 at all peering locations. IPTP Networks will not permit the routes longer than a /24 from its peers.
1.1.4 Existing IP Transit Customers of IPTP Networks and/or Customers of peering partners of IPTP Networks are not eligible for peering.
1.2 Private peering:
1.2.1 Network Capacity: The Requester must have a backbone with a minimum two OC-48’s between any two backbone cities.
1.2.2 Minimum Interconnect: Requester shall have the ability to interconnect with IPTP Networks in a minimum of two geographically diverse peering locations where IPTP Networks has a peering point of presence. The peering Candidate must have the ability to interconnect directly at a minimum GigE (1000 Mbps) or greater capacity levels at each point of interconnection with a minimum utilization of 25%.
1.2.3 Minimum # of routes: Peering Candidate must carry full customer routes (minimum of 1000 unique routes) in Interconnect routers, and announce consistent routes using BGP4 at all peering locations. IPTP Networks will not permit the routes longer than a /24 from its peers.
1.2.4 Existing IP Transit Customers of IPTP Networks and/or Customers of peering partners of IPTP Networks are not eligible for peering.
2. Operational Requirements
2.1. Each Network 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. Each Network 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 IPTP Network with which it seeks to interconnect shall be roughly balanced and shall not exceed bidirectional ratio of 8:1.
2.4 Hot-potato routing is implied (i.e. we will not send or honor MEDs).
2.5 MD5 passwords are not required but supported for all BGP sessions.
2.6. Neither Network shall point default into or transit the other Network where that network has not advertised a route for the destination in question.
2.7. Each Network shall monitor the usage of all interconnection links. If the utilization of any single link should exceed 70% 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. Each Network shall be responsible for communicating with its customers with respect to its Internet Network and the services, including Internet connectivity, each provides to its respective customers.
2.9 Interconnection Candidate must provide 48 hours notice to IPTP Networks Network Control Center 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 minimize 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 will be given 30 days written notice to remedy the situation
IPTP Networks reserves the right to grant or refuse peering to a requestor, whether or not they would otherwise meet these requirements.
