Requirement for connected members
LU-CIX ASBL connected members have to warrant that they meet, and will continue to meet, the following requirements:
- Be a recognised legal entity,
- Have an ASN (Autonomous System Number) assigned by one of the Regional Internet Registries (or their predecessors),
- Present to LU-CIX an Autonomous System (AS) that is visible from the LU-CIX transit router,
- Use BGP-4 for peerings.
Allowed Traffic Types on Unicast Peering VLANs
To ensure smooth operation of the LU-CIX infrastructure, LU-CIX imposes a set of restrictions on what kind of traffic is allowed on the public peering fabric. A summary of those restrictions is detailed hereafter.
Members' use of the LU-CIX network shall at all times conform to the relevant standards.
Members can use ports for unicast IPv4 and IPv6:
IPv4 and IPv6 unicast is available on the main peering VLAN.
No directed broadcast
IP packets addressed to LU-CIX peering LAN's directed broadcast address shall not be automatically forwarded to LU-CIX ports.
No-export of LU-CIX peering LAN.
IP address space assigned to LU-CIX peering LAN shall not be advertised to other networks without explicit permission of LU-CIX.
All routes advertised across the LU-CIX network shall point to the router advertising it unless an agreement has been made in advance in writing by LU-CIX and the members involved.
All routes to be advertised in a peering session across LU-CIX shall be registered with RIPE or other public routing registry. Members may use more than one ASN for their LU-CIX peering provided that each ASN presented shares the same NOC and peering contact details.
All exchange of routes across the LU-CIX network shall be via BGP4(+):
- AS numbers used in BGP4(+) sessions across the LU-CIX network shall not be from range reserved for private use,
- All routes advertised shall be aggregated as far as possible.
Traffic shall only be forwarded to a LU-CIX member when permission has been given by the receiving member either:
- By advertising a route across the LU-CIX network or explicitly in writing,
- Traffic shall not be routinely exchanged between two LU-CIX ports owned by the same LU-CIX member.