WOLFE PEERING POLICY
This document sets forth Wolfe’s policy for settlement-free interconnection (the “Policy”), also known as “peering”. Wolfe updates this policy from time to time and maintains the current version on the Wolfe web site at http://www.wolfe.net/peering-policy/.
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 3 of the policy lists the operational requirements that must be met by both Wolfe and the Requester. Section 4 outlines the process by which peering will be established.
This Policy applies to all requests for settlement-free interconnection with the Wolfe Internet Network either by dedicated connections (“private peering”) or by multi-party network access points (“public peering”).
1. Public Peering:
- Network Scope: Requester shall have the ability to interconnect with Wolfe in a minimum of three geographically diverse peering locations where Wolfe has a peering point of presence.
- Minimum utilization: The peering Candidate must have a minimum aggregate of 500Mbps on any single peering exchange.
- Minimum # of routes: Peering Candidate must carry minimum of 50 unique routes in Interconnect routers, and announce consistent routes using BGP4 at all peering locations. Wolfe will not permit the routes longer than a /24 from its peers.
- Existing IP Transit Customers of Wolfe are not eligible for peering.
2. Private peering:
- Network Scope: The Requester must operate an Internet network in:
Four cities spanning three time zones in the US (Seattle, Los Angeles, Chicago, Atlanta, Newark, or New York)
- Network Capacity: The Requester must have a backbone with a minimum two 10 GigE’s between any two backbone cities.
- Minimum Interconnect: Requester shall have the ability to interconnect with Wolfe in a minimum of two geographically diverse peering locations where Wolfe has a peering point of presence. The peering Candidate must have the ability to interconnect directly at a minimum GigE (1000Mbps) or greater capacity levels at each point of interconnection with a minimum utilization of 25%.
- Minimum # of routes: Peering Candidate must carry full customer routes (minimum of 1200 unique routes) in Interconnect routers, and announce consistent routes using BGP4 at all peering locations. Wolfe will not permit the routes longer than a /24 from its peers.
Existing IP Transit Customers of Wolfe are not eligible for peering.
3. Operational Requirements
- 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.
- Each Network must operate a network with sufficient redundancy and capacity that the failure of a single node will not significantly affect performance.
The ratio of the aggregate amount of traffic exchanged between the Requester and the Wolfe with which it seeks to interconnect shall be roughly balanced and shall not exceed bidirectional ratio of 2:1.
- Hot-potato routing is implied. However Wolfe will honor and send MED values.
- MD5 passwords are required for all BGP sessions.
- Neither Network shall point default into or transit the other Network where that network has not advertised a route for the destination in question.
- Each Network 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.
- 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.
- Interconnection Candidate must provide 48 hours notice to Wolfe NOC for scheduled maintenance. Said maintenance windows to be between 02:00hrs and 05:00hrs of local time.
4. Peering Process
- The Requester and Wolfe must enter into a bilateral Peering Agreement.
- The requirements set forth in Section 1 of this policy must be met at the time the request for settlement-free peering with Wolfe is made. All requirements in this Policy must continue be met in order for the Requester to remain eligible for peering.
- Wolfe may require a trial peering connection spanning a minimum of one month with the perspective candidate to measure accurately the traffic ratios between the candidate and Wolfe. A successful trial does not guarantee that Wolfe will peer with this candidate.
- All requests for settlement-free peering must be submitted via e-mail to email@example.com. The e-mail should include:
- the Requester’s complete contact information (name, phone, email)
- the Requester’s ASN
- a list of suggested interconnection points
- a traceroute showing the current path taken to www.wolfe.net
- an IP address Wolfe can traceroute to for testing purposes
- Wolfe reserves the right to grant or refuse peering to a requestor, whether or not they would otherwise meet these requirements.