Policies & Requirements

Disclaimer

ix42 is an information directory and community-driven overlay network. ix42 ONLY collects and publishes information. We DO NOT actually operate or manage the Internet Exchange Points (IXPs) or Route Servers (RS) listed on this website.

The listed RSes are voluntarily operated by independent participants within the respective IXPs. The underlying IXP operators bear no responsibility or liability for the operation, traffic, or any issues arising from the use of ix42 services. By connecting to any listed RS, you acknowledge and agree to this.

General Policies

The primary purpose of ix42 is to facilitate dn42 traffic exchange over existing IANA IXPs.
Traffic exchanged MUST be strictly dn42 and associated network traffic. Do NOT route public IANA network traffic over ix42 peering sessions.
Connected networks must adhere to these rules. Failure to comply can result in immediate disconnection by the respective RS operators.
ix42 does not manage, coordinate, or get involved in relationships between connected members and will not act as a third party in any agreement, mediation, or dispute.
The peering fabric may not be used in a manner that disrupts anyone's business or infrastructure.

Peering Requirements

You must have a valid dn42 ASN.
The peering candidate must provide a 24-hour contact point, kept updated in the dn42 registry.
Only announce prefixes you are authorized to announce (registered in the dn42 registry).
Members are allowed to use multiple ASNs as long as they share a common contact point.
For a peer established through a tunnel, the Round-Trip Time between the peer and the RS should ideally not exceed 40ms.

Technical Requirements

Establish BGP sessions using the configured IPs. Only BGPv4 / MP-BGP is allowed as a routing protocol.
IPv4 and IPv6 should be configured in separate BGP sessions or using MP-BGP depending on the RS setup.
Do not point default routes to the RS.
Do not use the RS as a next-hop gateway. The next-hop should remain the original peer's IP.
The use of MD5 and/or GTSM (TTL security) to secure BGP sessions is recommended if supported by the RS.