MCT-IX Connection Policy

Version: 1.0
Date: 10/1/2025

• Any organization holding a valid Autonomous System Number (ASN) and operating IP networks (e.g., ISPs, content providers, enterprises, cloud networks) may apply to connect.
• Participants must be able to establish BGP sessions with the Exchange route servers or with other members directly.
• All applicants must agree to abide by this policy and the Exchange’s Terms of Service.

• Port Types: Connections are available on Ethernet interfaces [1G, 10G, 100G — customize as needed].
• Cabling: The Exchange, in coordination with the data center, will provide the cross-connect from the Exchange switch fabric to a patch panel in the participant’s rack or cabinet. Participants are responsible for ordering and maintaining the patch within their own space, but the Exchange will manage all cabling inside the shared switching environment.
• Addressing: IPv4 and IPv6 addresses will be assigned from the Exchange’s LAN allocation. IPv6 participation is strongly encouraged.
• Protocols:
  • Only Ethernet, ARP, IPv4, IPv6, ICMP, and BGP are permitted on the Exchange LAN.
  • No proxy ARP, gratuitous ARP, or unauthorized multicast/broadcast traffic is allowed.

• The Exchange operates route servers to simplify multilateral peering.
• Use of the route servers is strongly encouraged but not mandatory.
• Participants may choose to:
  • Peer with the route servers to gain immediate multilateral visibility.
  • Establish bilateral peering sessions directly with other members.
• The Exchange may enforce route filtering, IRR/RPKI validation, and prefix limits on its route servers to ensure stability and security.

• Participants must maintain current technical contact details with the Exchange.
• Participants are responsible for securing their own equipment and BGP sessions (e.g., use of max-prefix limits, RPKI validation is recommended).
• The Exchange reserves the right to disconnect any participant that negatively impacts the stability of the shared fabric.
• The Exchange may conduct periodic maintenance; participants will be notified in advance whenever possible.

• Use of the Exchange fabric for transit services, tunneling, or carrying traffic not explicitly exchanged between members.
• Use of the Exchange LAN for unicast traffic between a participant’s own ports.
• Announcing prefixes not legitimately assigned or authorized for use by the participant.
• Activities that compromise security, stability, or neutrality of the Exchange.

• The Exchange may temporarily disable or permanently revoke a participant’s connection for violation of this policy.
• Violations will be communicated to the participant’s designated contact, with reasonable time provided to remediate, unless immediate disconnection is required to protect the Exchange.

This Connection Policy may be revised by MCT-IX. Participants will be notified of any changes with reasonable notice.