Extension Switch Operator

Technical Requirements

An Extension Switch Operator is a 3rd party that connects switching infrastructure they manage via a circuit that they control to an assigned port at IX-Denver / IX-West core infrastructure.  There are a few minimum rules we would like to enforce for safety of all members and operators as well as for future considerations.

  • For the most part all ‘basic technical info’ rules apply – ESO must not send bpdus, and limit l2 garbage on uplink to IX-Denver core infrastructure, ESO should also apply this methodology to remote member facing ports.
  • Extension switch operator should filter private IPv4 aka bogon sources in the data plane at edge ports (at minimum RFC1918, RFC6598, documentation net, and link local sources) and if possible the extension operator should filter the equivalent in IPv6 ranges (except link local).
  • Extension switch operator brings their own extension switch and access circuit infrastructure to meet IX-Denver at a suitable agreed upon core switch location and port(s).
  • The extension switch operator is expected to monitor the capacity of any extension links to core IX-West / IX-Denver locations and upgrade capacity when necessary, IX-West / IX-Denver will begin recommending upgrades to the extension switch operator if peak utilization is over 70% of line rate on a monthly basis.
  • Extension operator must provide MAC address and public ASN information for remote members to which it allocates IP addressing.
  • Layer 2 MTU between core IX-Denver infrastructure, extension infrastructure, and edge ports to remote members must be 9000 < bytes.
  • Ports between IX-Denver and an extension switch operator should be configured as a trunk port and the extension switch operator should hand off 1 VLAN tag per remote peer network.
  • Extension operators must be able to filter broadcast, multicast and unknown unicast (BUM) traffic to a 5-10% level of line rate on any uplink ports to the connected IX-Denver core infrastructure, and the ESO should enforce similar filtering on remote member facing ports, extension operators must send only legitimate BUM type traffic to IX-Denver.