Fiber Data Exchange / Midwest Internet Exchange Policies
1. This document contains a set of common rules that all networks wishing to connect to the FD-IX fabric must adhere to. Failure to comply with any provision of this agreement can result in immediate disconnection from the FD-IX peering fabric without notice. By connecting to the FD-IX peering fabric you acknowledge that you have read, understand and agree to all the terms contained within.
2. The terms contained within this document are subject to change. By connecting to the FD-IX peering fabric you agree to all future revisions. Revisions will be published and members will be notified via e-mail 30 days in advance.
3. FD-IX does not manage, coordinate or act as an intermediary in relationships between connected members and will not act as a third party in any agreement, mediation or dispute.
4. The FD-IX Peering fabric may not be used in a manner that would disrupt other participant’s business or infrastructure.
5. FD-IX Administration personnel reserve the right to disconnect or otherwise disrupt service to a member under any of the following conditions:
5a. Failure to follow any of the provisions of this agreement.
5b. To perform scheduled or emergency maintenance.
5c. Statutory obligation set forth by a regulating authority.
5d. As part of a request related to an ongoing investigation, warrant or subpoena issued by a recognized law enforcement entity with jurisdiction in an area in which FD-IX, operates.
5e. Any unforeseen issue that would require FD-IX to interrupt connectivity for the sake of its membership.
6. FD-IX is not responsible for any losses incurred as a result of disruption in the continuity of the Peering fabric. The service is provided as is, without any warranties expressed or implied including merchantability or fitness for a particular purpose.
7.FD-IX will schedule any maintenance a minimum of seventy-two (72) hours in advance, unless in case of an emergency.
Allowed Traffic Types on Fiber Data Exchange / Midwest Internet Exchange
The FD-IX NOC reserves the right to disable ports that violate the rules below
Ethernet interfaces attached to FD-IX ports must be set to auto-sensing unless otherwise agreed.
The FD-IX infrastructure is based on the Ethernet II (or DIX Ethernet) standard. This means that LLC/SNAP encapsulation (802.2) is not permitted.
Frames forwarded to FD-IX ports shall have one of the following ethertypes:
• 0x0800 – IPv4
• 0x0806 – ARP
• 0x86dd – IPv6
One MAC address per port
Frames forwarded to an individual FD-IX port shall all have the same source MAC address.
No proxy ARP
Use of proxy ARP on the router’s interface to the Exchange is not allowed.
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.
No link-local traffic
Traffic for link-local protocols shall not be forwarded to FD-IX ports.
Link-local protocols include, but are not limited to, the following list:
• ICMP redirects
• IEEE 802 Spanning Tree
• Vendor proprietary discovery protocols (e.g. CDP, EDP)
• Interior routing protocol broadcasts (e.g. OSPF, ISIS, IGRP, EIGRP)
• ICMPv6 ND-RA
The following link-local protocols are exceptions and are allowed:
• IPv6 ND
No directed broadcast
IP packets addressed to FD-IX peering LAN’s directed broadcast address shall not be automatically forwarded to FD-IX ports.
no-export of FD-IX peering LAN
IP address space assigned to an FD-IX peering LAN shall not be advertised to other networks without explicit permission of FD-IX.
1. The peering candidate must be a registered entity in its local jurisdiction.
2. The peering candidate must provide FD-IX with a 24 hour contact point.
3. Only BGPv4 and BGPv6 are allowed as routing protocols.
4. The Peering candidate must have a registered, Public ASN (Autonomous System Number) issued by a recognized routing registry. (ARIN, RIPE, APNIC, LACNIC, AfriNIC)
5. 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.
6. Peering parties are encouraged to aggregate routes where ever possible.
7. Only prefixes registered to the Member or for which the member has a signed LOA on file may be announced.
8. The minimum prefix announced should be /24 for IPv4 and /48 for IPv6.
9. Members must be listed and provide updated contact information on PeeringDB.com
10. Members are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purposes of filtering.
Midwest Internet Exchange Technical Requirements:
1. The only L2 frame types allowed are 0x0800, 0x86dd and 0x0806.
2. All L2/L3 protocols are forbidden with the exception of IP, NDP and ARP.
3. There is a limit of one MAC address per port. Shared cables are not permitted.
4. Ethernet aggregation is available subject to FD-IXapproval.
5. The use of MD5 and/or BTSH to secure BGP sessions is recommended.