Twitter
Midwest Internet Exchange

M-IX Peering Requirements

Midwest Internet Exchange Peering Requirements:
1. The peering candidate must be a registered entity in its local jurisdiction.
2. The peering candidate must provide M-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. Single members are allowed to use multiple ASN’s as long as they share a common contact point.
6. M-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.
7. Peering parties are encouraged to aggregate routes where ever possible.
8. Only prefixes registered to the Member or for which the member has a signed LOA on file may be announced.
9. The minimum prefix announced should be /24 for IPv4 and /48 for IPv6.
10. Members must be listed and provide updated contact information on PeeringDB.com
11. 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 M-IX approval.
5. The use of MD5 and/or BTSH to secure BGP sessions is recommended.

%d bloggers like this: