The NiceRoute Internet Exchange (NRIX) operates as a collaborative effort, and the following guidelines are established to ensure the overall well-being of the exchange fabric, both in the short and long term.
- Peering is bilateral, except for route servers. There is no Multi-Lateral Peering Agreement (MLPA).
- Participants must utilize BGP-4 or its successor and must set NEXT_HOP_SELF when advertising routes from other NRIX participants.
- Participants are prohibited from pointing default or utilizing another participant's or NRIX's resources without explicit permission.
Only three ethertypes are allowed: 0x0800 (IPv4), 0x0806 (ARP), and 0x86dd (IPv6).
- Only broadcast ARP and multicast ICMPv6 Neighbor Discovery packets are allowed as non-unicast traffic.
- Per-neighbor timeouts leading to flooded packets should be set to 4 hours (or as close as possible) to avoid quarantine.
- Participant ACLs must adhere to neighbor discovery norms.
- For IPv4, routers must respond to ARP packets from all NRIX participants.
- For IPv6, routers must respond to ICMPv6 neighbor solicitation packets from fe80::/10 and all NRIX participant addresses.
Participants must not allow NRIX subnets to propagate externally and should minimize internal propagation. ACLs are requested to prevent unintended reachability.
Participants are prohibited from sniffing traffic between other participants.
Participants must be responsive to other participants and NRIX administrators. Urgent issues may result in suspension to protect the fabric. Non-urgent issues will be communicated via PeeringDB and NRIX contact emails, with a response time not exceeding two weeks.
Contact: [email protected]
- Organizations planning press releases mentioning NRIX should coordinate with administrators before release.
- NRIX participation does not grant rights to use other participants' names, logos, or information.
Note: The Press Release Policy is a courtesy and ensures respectful communication within the NRIX community.