Midco Peering Policy
Updated Jan 4, 2022
Midco is an Internet service provider offering service in Kansas, Minnesota, North Dakota, South Dakota and Wisconsin to residential and business customers via fiber, HFC and fixed wireless access.
Current information is available from PeeringDB - https://as11232.peeringdb.com.
Midco’s primary ASN is 11232
IRR AS-set object ARIN::AS-MIDCO
IPv4 Prefixes 300, recommend max-prefix of at least 1000. (Best to use value from peeringDB.)
IPv6 Prefixes 15, recommend max-prefix of at least 50. (Best to use value from peeringDB.)
Midco peers with IX provided route servers where they are available.
Midco’s preference to peer directly with any network with more than 500Mbps in the dominant direction rather than via the IX route server.
Midco’s preference is to establish private peering with any network with more than 1Gbps in the dominant direction rather then peering via an IX fabric.
Midco supports 10GE and 100GE peering connections.
Midco prefers 10G-LR and 100G-LR4 optics for peering.
Midco has a selective peering policy. Anyone wishing to peer with Midco at a common location should contact email@example.com. For peering to be mutually beneficial, please confirm that the following requirements are met before requesting a peering connection.
Peering partners are expected to:
- Peer with a globally unique ASN assigned by an RIR.
- Maintain up-to-date network and contact information in peeringDB.
- Maintain an IRR as-set one of the IRR databases mirrored by RADb.
- Maintain IRR route/route6 objects for all announced prefixes.
- Operate a 24x7x365 NOC that will promptly work to resolve any reports of trouble with a peering connection. In this context “trouble” includes but is not limited to – route flaps, max prefix violations, excess traffic, interface flaps, abuse and security incidents.
- Only announce prefixes allocated or assigned by an RIR to the announcing ASN or prefixes delegated to an immediate customer ASN.
- Only route traffic destined to prefixes advertised by Midco via peering connections. In particular, the following are violations of this requirement:
- Sourcing traffic from a prefix not announced to Midco via the peering connection.
- Sending traffic destined to a prefix not announced by Midco over the peering connection.
- Resetting next hop.
- Monitor capacity between the networks and augment before congestion occurs.
It is recommended, but not required for peering partners to:
- Peer with Midco at more than one location.
- Maintain ROAs for all announcements.
- Provide a looking glass or route server.
Midco’s routing policy generally prefers routes learned via private peering (PNI) over those learned via public peering (IX).
Midco generally announces all the routes in the AS-MIDCO as-set at all peering locations but under certain circumstances may announce a subset.
Midco does not recommend the use of MD5 but can support it.
Midco reserves the right to terminate peering sessions at any time for any reason. Under normal circumstances Midco will provide 30 day notification before terminating a peering session but reserves the right to immediately terminate a peering session to protect the integrity of the Midco network.
Midco reserves the right to modify this policy as needed.