April 2016

Overview

IFN's Network Openness Policy encourages cooperation in interconnecting with Internet networks where technically feasible at reasonable rates and terms for the purpose of exchanging traffic.

IFN will engage selectively in settlement-free peering with a willing interconnected network or public exchange when peering is beneficial to IFN's purposes.

This Peering Policy provides guidelines for IFN's settlement-free peering. Meeting or exceeding all of the peering requirements does not guarantee IFN will enter into a peering relationship with an Applicant. IFN reserves the right to grant or refuse peering to an Applicant. It is within IFN's sole discretion to modify, replace or discontinue this policy, or any peering relationship granted under the Policy, at any time. IFN can provision network peering connections at speeds from 1 Gbps Ethernet to 10 Gbps Ethernet, and is capable of IPv4 and IPv6 peering. Peering with IFN does not convey access privileges to, nor automatically provide for traffic exchange with, any of the other private networks with which IFN connects; traffic is exchanged with those networks only in accordance with the policies of those other networks.

Peering Requirements

  • Routes must be contained in a single Autonomous System Number (ASN) per network to be shared.
  • An Internet Network must be a single Autonomous System Number. • Routing protocol must be BGP-4.
  • The average amount of bandwidth exchanged monthly in each direction aggregated across all interconnection links between the Peer and IFN's network shall generally equal or exceed 500 Mbps for private peers and 3 Gbps for public exchanges.
  • IFN will peer only at the following POP locations:
    • 1. 575 or 535 Scherer’s Court Columbus, OH
    • 2. 5707 N West St. Lima, OH
    • 3. 3842 Albon Rd. Monclova, OH 43542
  • Peer must abide by the following routing policy:
    • 1. Peer must use the same peering AS at each interconnection point and must announce a consistent set of routes at each point, unless otherwise mutually agreed.
    • 2. No transit or third party routes are to be announced; all routes exchanged must be peer's and peer's customers' routes.
    • 3. Peer must filter route announcements from its customers by prefix.
    • 4. Neither party shall abuse the peering relationship by engaging in activities such as but not limited to: pointing a default route at the other or otherwise forwarding traffic for destinations not explicitly advertised, resetting next-hop, selling or giving next-hop to others.

Operational Peering Requirements

  • The Peer must operate a fully functional 24x7 Network Operations Center.
  • The Peer must be, in IFN's sole judgment, operationally staffed to be an effective peering partner.
  • The Peer must be responsive to unsolicited email and network abuse complaints, as well as routing, security and interconnection issues, providing knowledgeable staff within a two-hour period after notice.
  • The Peer must establish and maintain traffic exchange links of a sufficient robustness, aggregate capacity, and geographic dispersion, in IFN's sole judgment, to facilitate mutually acceptable performance across the interconnect links.
  • Each Internet Network must set next hop to be itself, the advertising router of the network. Each Internet Network will propagate such routes to its transit customers with its own router as next hop.
  • Each Internet Network shall implement "shortest exit routing" and advertise routes consistent with that policy, unless both Internet Networks mutually agree otherwise based on special circumstances.
  • Each Internet Network will restrict its advertisements to non-transit routes originating within the range for which peering is established and will not propagate the received route announcements outside such range.
  • Each Internet Network must operate a fully redundant network, capable of handling a simultaneous single-node outage in each network without significantly affecting the performance of the traffic being exchanged. The Peer must use a dynamic routing protocol for their internal gateway connectivity routing.

General Policy Guidelines

  • Settlement free peering means that IP traffic will flow between the two peering organizations' networks without a transfer of funds between the two organizations.
  • Peer must agree to enter into a Mutual Non-Disclosure Agreement and an Interconnection Agreement.
  • All requirements of the Peering Policy must continue to be met to continue a peering interconnection with IFN's network. Status under this policy will be evaluated periodically. In the case of a change in ownership or control of an Internet network with which IFN has an interconnection agreement, the relationship will be evaluated within 30 days of such change.
  • IFN will continue to monitor the development of the Internet and traffic conditions and make appropriate changes in this policy as the Internet continues to evolve. IFN reserves the right to modify this Policy at any time.
  • All requests for settlement-free or regional interconnection peering must be submitted to peering@ifnetwork.biz