Membership and Pricing

Become a Member Today!

You can join IX-Denver today by simply filling out this application form and then shooting us an email.

Pricing Structure and Member Classifications v1.1:

Member Pricing Structure Summary Table:

IX-Denver Pricing Structure

Directly Connected Members (at 910Telecom or Flexential):

  • Per port pricing is calculated per IX-West / IX-Denver site
  • Primary port fee includes two (2) membership voting rights per connected organization
  • Primary port fee Includes one IPv4 host and one IPv6 host allocation
  • Includes the use of one MAC address and one public ASN on the exchange
  • Includes the use of one ebgp session on IX-West / IX-Denver route server(s) for connected network per IP (one IPv4 session and one IPv6 session per route server).
  • A direct connected member is connected by a wave, dark fiber, or other ‘carrier grade’ equivalent ethernet private infrastructure.

Extension Switch Operators (ESOs):

  • Port pricing is calculated per IX-West / IX-Denver site
  • Primary port fee includes two (2) membership voting rights for ESO’s organization
  • Each remote peer IP host allocation which ESO subscribes to includes one tenth (.1) membership voting right for ESO to utilize per active, assigned organization.
  • Port fee Includes one IPv4 host and one IPv6 host allocation for operator’s network
  • Includes the use of one MAC address and one public ASN on the exchange for operator’s network
  • An extension switch is connected by a transport wave, dark fiber, or other ‘carrier grade’ equivalent ethernet private infrastructure, and is managed by a 3rd party from IX-West.
  • An extension switch operator may permit other 3rd parties to operate an extension off of their infrastructure. It is required that the additional party also conform to IX-West / IX-Denver general technical and specific ESO technical rules.  
    • In this case the ‘primary’ ESO that maintains a customer / member relationship with IX-West / IX-Denver is responsible for recording of remote member MAC addresses, assigning IP address (IPv4+IPv6) from their allocation(s), and requesting services from IX-West / IX-Denver (e.g route server requests) on behalf of downstream ESO.

Remote Members Connected via ESO:

  • $10/mo ($120/yr) per Host IP allocation (IPv4/32+IPv6/128) subscription based model.
  • IP allocations fees are invoiced to the Extension Switch Operator (exceptions can apply)
  • Includes the use of one MAC address and one public ASN on the exchange
  • Includes the use of one ebgp session on IX-West / IX-Denver route server(s) per IP (one IPv4 session and one IPv6 session per route server).
  • Extension Switch Operator is the primary contact for troubleshooting or assistance for the remote network the IP allocation is assigned to.

The focus for IX-Denver is on the value remote members bring to the direct connected members, vs what possible revenue can be generated from remote members.  This structure also provides ESO’s a predictable, non-ambiguous cost structure, and lowers IX-West / IX-Denver touchpoints required with remote members.

Extension Switch Operator (ESO) Technical Rules:

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 as much as possible on uplink to IX-Denver core infrastructure, ESO should also apply this to remote member facing ports.
  • Extension switch operator should filter private IPv4 aka bogon sources in the dataplane 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 of course).
  • 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 from IX-Denver to an extension switch operator should be configured as an access port in the public peering vlan, exceptions can apply (MNVoIP/NP is trunk for our transit).
  • 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 extension member facing ports, extension operators must send only legitimate BUM type traffic to IX-Denver.