Overview
The Hyper Group Network Internet Exchange (HNIX) is a virtual IXP that operates for non-commercial, neutral BGP learning and experimental platforms which operates as a collaborative effort. We currently only support IPv6 traffic and peering. The following guidelines are established to ensure the overall well-being of the exchange fabric, both in the short and long term.
Peering
Peering is bilateral, except for the mandatory route server. 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 HNIX participants.
Participants are prohibited from pointing to default or utilizing another participant's or HNIX's
resources without permission.
Join
As this project is community and experimental-based, we are not able to provide any SLA guarantee. We will try our best to provide best-effort support which to ensure minimum downtime to the IX route servers.
We welcome everyone or entity to join our IX. We currently only accept tunneling access with the below technology:
- Generic Routing Encapsulation IPv4, L2 (GRETAP) [Most Preferred]
- Generic Routing Encapsulation IPv6, L2 (IP6GRETAP)
- Virtual eXtensible Local Area Network (VXLAN) [Least Preferred]
Data rate and bandwidth may be limited due to ISP connectivity and internet quality on both sides. We will try our best to provide better bandwidth support. If possible, we will provide multiple PoPs and connect those PoPs via VPLS (Virtual Private LAN Service). Latency depends on the location of the PoPs.
We have limited the routes propagated for each participant. Currently, 200 routes are allowed for each participant. If exceeded, the connection will be reset by our RS. This limitation will be changed depending on the scale of the network and peers.
Exit
Participants can proactively email our IX support team which is no longer active on our IX. We will remove the members which not provisioned or whose no route has been propagated for a long time (normally in a month).
Transit
IX natively does not support transit services. However, we will try to establish transit services with AS216324.
Ethertypes
Only the mentioned types are allowed: 0x0806 (ARP), and 0x86dd (IPv6)
Traffic Types
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.
ACL and Norms
Participant ACLs/Prefix-list must adhere to neighbor discovery norms.
For IPv6, routers must respond to ICMPv6 neighbor solicitation packets from "SUBNET" and all HNIX
participant addresses.
Traffic Monitoring
Participants are prohibited from sniffing traffic between other participants.
Subnet Propagation
Participants must not allow HNIX subnets to propagate externally and should minimize internal propagation. ACLs/Prefix lists are requested to prevent unintended reachability.
Responsiveness
Participants must be responsive to other participants and HNIX administrators. Urgent issues may result in suspension to protect the fabric. Non-urgent issues will be communicated via PeeringDB and contact emails mentioned below, with a response time not exceeding two weeks.
Our contacts are as follows:
- Support Contact: [email protected]
- NOC Contact: [email protected]
- NOC Contact: [email protected]
HNIX participation does not grant rights to use other participants' names, logos, or information.