TUSIX – Rules & Policies
The Tucson Internet Exchange (TUSIX) has a few rules and policies to ensure the exchange fabric’s short- and long-term health.
- Peering is bilateral except for the exchange route servers. There is no Multi-Lateral Peering Agreement (MPLA).
- There are only three ethertypes allowed: 0x0800 (IPv4), 0x0806 (ARP) and 0x86dd (IPv6).
- Participants must use BGP-4 or its successor and must set NEXT_HOP_SELF if advertising routes are from other TUSIX participants.
- Participants may not point default or use another participant’s or TUSIX’s resources without permission.
- Broadcast ARP and multicast ICMPv6 Neighbor Discovery packets are the only permitted non-unicast traffic. Per-neighbor timeouts that result in flooded (broadcast/multicast) packets should be set to 4 hours or as close to that as possible in the case of vendor limitations. Short timeouts may result in quarantine.
- Participants must be responsive to other participants and TUSIX administrators to protect the short- and long-term health of the exchange fabric. Urgent issues may result in the suspension of a participant to protect the fabric. For non-urgent issues, if a participant is unresponsive to concerns raised by a TUSIX administrator, a TUSIX administrator will notify the non-responding participant via their PeeringDB and TUSIX contact emails of their need to respond in order to avoid suspension from the TUSIX. The length of time to determine if a participant is unresponsive, and time to suspension, will depend on the severity of the matter, each not to exceed two weeks.
- Participants must not allow TUSIX subnets to propagate externally from their network and should minimize internal propagation as much as possible. If a participant’s network beyond their TUSIX edge router(s) can reach the TUSIX subnet addresses, ACLs will be requested in order to prevent this from happening.
- Participants may not sniff traffic between other participants.
- Participant ACLs must not violate neighbor discovery norms, since doing so will result in excess flooded packets on the community fabric and burden for TUSIX administrators.
- For IPv4, this means that a participant’s router must be configured to receive and respond to ARP packets from all TUSIX participants, even those that are not direct peers.
- For IPv6, this means that participant routers must receive and respond to ICMPv6 neighbor solicitation packets from both fe80::/10 and all TUSIX participant addresses, including those that are not direct peers, directed toward fe80::/10, ff02::1:ff00:0/104, and the participant’s unicast TUSIX assignments.
Press Release Policy
If your organization plans to release press releases specifically mentioning the Tucson Internet Exchange, please coordinate with TUSIX administrators as a courtesy before contacting the media. Emailing firstname.lastname@example.org is the best method of contact. In addition, please keep in mind that TUSIX participation does not grant organizations any rights to use other participants’ names, logos or other information.
Join the Exchange
With every participant and every connection, TUSIX grows stronger. Join TUSIX to contribute to faster and more reliable networks for all users. Together, we work towards our shared goal of improved internet connectivity.