Fiber Data Exchange / Midwest Internet Exchange Policies

FD-IX is a neutral Internet Exchange enterprise and promotes open peering policies. The mission of FD-IX is to facilitate and promote peering between members on a shared fabric via open peering.

The following peering policies are accepted:


the MEMBER opens peering on simple demand from any member present at the FD-IX.


The MEMBER evaluates every demand before opening the peering.


the MEMBER publishes restrictive objective criteria the other member has to meet in order to establish a peering.

Paid peering:

in case the MEMBERs do not reach an agreement for settlement-free peering, they may arrange for payment. This payment has to be negotiated and carried out between the members.

Bilateral Peering contracts:

FD-IX does not require from the MEMBERS to set-up formal peering agreements for exchanging traffic, however it is not allowed to send data/traffic to another party without acknowledgement of the other party. In case of infringement, FD-IX has the right to immediately disconnect the infringing member.

Information to customers about any restrictions in traffic exchange

The member accepts to keep its customers informed about any restrictions in traffic to or from other members.


Rules for routing and use of private AS numbers:

A member must publish its routing policy and information via, Routing information may not be exchanged through the exchange point with routing protocols that use multicast or broadcast, such as RIP and OSPF. Static routing may not be used to control traffic through the exchange point. Private AS numbers may only be used at an exchange point if they are coordinated and accepted by FD-IX. Routing information that is exported to other destinations on Internet may not contain private AS numbers.

Assistance in correction of problems

A member shall immediately assist in the correction of problems in its own, or in shared equipment.

Section 2

Technical Details
2.1 Ethernet framing

The FD-IX infrastructure is based on the Ethernet standard. This means that LLC/SNAP encapsulation (802.2) is not permitted

Frames forwarded to FD-IX ports must have one of the following ethertypes:

  • 0x0800 – IPv4
  • 0x0806 – ARP
  • 0x86dd – IPv6

2.2 No proxy ARP

Use of proxy ARP on the router’s interface to the Exchange is not allowed.

2.3 Unicast only

Frames forwarded to FD-IX ports shall not be addressed to a multicast or broadcast MAC destination address except as follows:

  • broadcast ARP packets
  • multicast ICMPv6 Neighbour Discovery packets. Please note that this does not include Router Solicitation or Advertisement packets.

2.4 No link-local traffic

Traffic related to link-local protocols shall not be forwarded to FD-IX ports. Link-local protocols include, but are not limited to, the following list:

  • IRDP
  • ICMP redirects
  • IEEE 802 Spanning Tree
  • Vendor proprietary protocols. These include, but are not limited to:
    • Discovery protocols: CDP, EDP, LLDP etc.
    • VLAN/trunking protocols: VTP, DTP
    • Interior routing protocol broadcasts (e.g. OSPF, ISIS, IGRP, EIGRP)
    • PIM-SM
    • PIM-DM
    • DVMRP
    • ICMPv6 ND-RA
    • UDLD
    • L2 Keepalives

The following link-local protocols are exceptions and are allowed:

  • ARP
  • IPv6 ND

2.5 No directed broadcast

IP packets addressed to FD-IX peering LAN’s directed broadcast address shall not be automatically forwarded to FD-IX ports.

2.6 no-export of FD-IX peering LAN

IP address space assigned to FD-IX Peering LANs must not be advertised to other networks without explicit permission of FD-IX.

Using Application layer protocols to unleash malicious actions against other FD-IX customers over FD-IX infrastructure, is forbidden. FD-IX reserves the right to disable a customer’s port in case of complaints of attacks/abuse originating from such customers. The following list includes, but is not limited to:

  • BGP hijacking
  • DNS amplification/flood
  • HTTP flood
  • NTP amplification
  • UDP flood
  • ICMP flood
  • Simple Service Discovery Protocol (SSDP)

The FD-IX Connection Agreement allows for connecting one router to a port sold to a member unless otherwise stated in your connection agreement. Only the customer’s MAC address is allowed on the port; no frames with different source MAC addresses are allowed to enter the platform. L2 ACLs prevent several potentially crippling network loops affecting the switching fabric.

The aim of the FD-IX is to have a network availability of at least 99.99%. FD-IX considers both service interruption as well as deterioration of service as service failure.

Excluded from this definition are service failures due to:

  • Scheduled maintenance
  • Violations of FD-IX regulations by members causing dis-functioning of the exchange
  • Force majeure


  1. Only BGPv4 is allowed as a routing protocol.
  2. The Peering candidate must have a registered, Public ASN (Autonomous System Number) issued by a recognized routing registry. (ARIN, RIPE, APNIC, LACNIC, AfriNIC)
  3. Single members are allowed to use multiple ASN’s as long as they share a common contact point.
  4. FD-IX only accepts peering traffic from its members. Members may not transit charged peering traffic or use next-hop rewrites, default routes or static routes unless specifically given permission. If you are a transit provider you must register with FD_IX to sell transit across the exchange.
  5. Peering parties are encouraged to aggregate routes where ever possible.
  6. Only prefixes registered to the Member, contained in IRR, or for which the member has a signed LOA on file may be announced.
  7. The minimum prefix announced should be /24 for IPv4 and /48 for IPv6.