LillIX

Policy

Règles techniques et opérationnelles applicables aux réseaux souhaitant se connecter à LillIX.

Disclaimer / Foreword


The below document displays a set of strict common rules that any network willing to connect to the LILLIX has to follow. Failure to comply with any rules may result in a deny to connect to LILLIX.

Those rules are to be agreed by any LILLIX candidate network before actually joining the Exchange.

General terms



  • The candidate shall be a public or privately held company officially registered in its home country's trade and/or industry authority.

  • The candidate shall run an Internet related business.

  • The candidate shall provide LILLIX with a 24 hours/24 and 7 days/7 operational contact.

  • LILLIX does not manage, coordinate nor take part in relationships between connected members, and will therefore not act as third party in peering agreements between its members.

  • LILLIX must never be used to harm or disrupt other parties' business and infrastructures.

  • The LILLIX service does not include any collocation, housing nor hosting features.

  • Members' cabling shall always be labelled clearly, displaying the owner's name.

Routing and AS restrictions



  • Only BGPv4 is allowed and mandatory as a routing protocol.

  • The peering party should have a registered public ASN.

  • The same member is allowed to use multiple ASNs as long as there is one single common NOC contact.

  • LILLIX only accepts peering traffic from its members: no charged peering traffic, no next-hop rewrite hack, no default routes nor statics.

  • Peering parties should always send aggregated routes when possible.

  • Only RIR registered prefixes shall be announced by members.

  • The minimum IPv4 prefix to be announced is /24, and /48 for IPv6.

Link layer restrictions


The only accepted L2 frames should be IPv4 (0x0800), IPv6 (0x86dd), and ARP (0x0806).

The following protocols are explicitly forbidden: discovery protocols, L2 resiliency protocols, VTP/GVRP, ICMP redirect, BootP/DHCP. Multicast protocols PIM SM/DM/SDM and IGMP are LILLIX specials.

Physical ports and capacity



  • There should be one cable per member. No shared cable is allowed as LILLIX switches run MAC filtering.

  • LILLIX can ask applicants to provide bandwidth justification whenever necessary.

  • Ethernet aggregation and port bandwidth upgrades are possible subject to LILLIX approval.