Subscription Requirements and Process

Administrative

• Pricing

  • Port fee as of January 2025 are as follows:

    • 1Gig:  No cost for the first.  Each additional $250/year.  

    • 10Gig:  No cost for the first.  Each additional $500/year.

    • 40Gig:  No cost for the first.  Each additional $1000/year.

    • 100Gig:  $3,000/year per port.

  • Connection to the DACS-IX region local to the connected site is provided at no cost.  Connections to a non-local region require additional backhaul fees.

  • Exemptions to these fees are made on a case-by-case basis and subject to approval.

    • Typically, exemptions are granted to non-profit entities that contribute an in-kind service of equal value to all other participants.

    • Examples of this are ccTLD/gTLD servers, root DNS server operators, or global routing debugging and performance measurement tools with public interfaces.

    • Questions and requests may be sent to info@dacs-ix.com​

• Billing

  • Billing is performed on an annual basis at your turn-up anniversary date.  Monthly billing is available upon request.

  • All pricing is in US dollars.

​

Logistics

• Participants are required to have at least one organization representative subscribed to the DACS-IX mailing list per region.

​

• Correspondence or discussions on the mailing lists are considered confidential to participants, members, and sponsors.

​

• No SLA or service guarantees are implied – all services are considered best effort.

​

• Participants may not spoof ARP or ICMPv6 packets, or sniff traffic between other participants

​

Technical

• Participants must utilize an ASN (Autonomous System Number) that is allocated by an RIR (Regional Internet Registry), such as ARIN.

• Private or reserved ASN’s are not acceptable – as specified by RFC 1930 or RFC 6996.

• For each logical link to exchange, only one source MAC address is allowed to be sourced.

• The only acceptable broadcast protocols are ARP (for IPv4 neighbor discovery) and ICMPv6 Neighbor Discovery (for IPv6 Neighbor Discovery).  All other broadcast traffic (e.g., ICMPv6 RAs, CDP, LLDP, DHCP, or STP) are forbidden.

• All participants are required to establish and maintain BGP session with the route collector in each region they are connected to.  This service is utilized purely for debugging purposes; no routes are reflected back out, and no traffic is exchanged over this peering session.

• Participants must not allow DACS-IX production VLAN subnets to propagate externally from their network and should minimize internal propagation as much as able.  If a participant’s network beyond their DACS-IX connected edge router(s) can reach the regions subnet addresses, ACLs are requested in order to prevent this.

​

• ​Participants may not point any static or default routes towards other participants, or otherwise use another participant’s or provider's resources without permission.

• ​Participants are encouraged to utilize DACS-IX regional route servers, where appropriate for their organization traffic engineering policies.  These peering relationships help facilitate creating immediate value for new members of the exchange.  Peering with the route servers is not required.