Policy

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.

The content and scope is prone to be updated in the future, LILLIX users are therefore to ensure of the lastest version in use at https://www.lillix.fr/peering-policy/ based on the revision number displayed at the bottom of the page.

• 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.

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

• LILLIX doesn’t manage, coordinate nor take part in relationships between connected members, and will therefore not act as 3rd party in peering agreements between its members.

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

• LILLIX administration reserves itself the right to interrupt the connectivity (temporarily or definitely) of any of his members if one of the following events was to happen:

  • Disrespect of any or all of the hereby mentioned rules.
  • Maintenance purposes.
  • Statutory obligation from a regulatory authority.
  • Any unforeseen issue that would require LILLIX to interrupt connectivity for the sake of his members.

• The LILLIX service doesn’t include any collocation, housing nor hosting features.

• LILLIX is not responsible of any loss of revenue or any operational issues generated by any disruption in the LILLIX‘s service continuity. The service is provided as is, without any explicit or implied warranty.

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

• Only BGPv4 is allowed and mandatory as a routing protocol.
• The peering party should have a registered public ASN (Autonomous System Number � ranging from 1 to 64511). This ASN should be registered within any of the RIPE NCC, LACNIC, AfriNIC, ARIN & APNIC routing registries.
• As a remark, the same Member is allowed to use multiple ASNs long as there is one single common NOC contact.
• LILLIX only accepts peering traffic from his members, implying:
  • 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 (RIPE NCC, ARIN, APNIC) registered prefixes shall be announced by members.
• The minimum IPv4 prefix to be announced is /24, it is /48 for IPv6.

• The only accepted L2 Frames should be of the below EtherType: IPv4 (0x0800), IPv6 (0x86dd), ARP (0x0806).
• The below listed protocol are explicitly forbidden:
  • No discovery protocol (CDP, EDP, IRDP).
  • No L2 resiliency protocol (VRRP, HSRP or such).
  • No VTP, GVRP.
  • No ICMP redirect.
  • No BootP/DHCP.
  • Please note the below exceptions which are LILLIX Specials:
    • multicast protocols PIM SM/DM/SDM, IGMP.

  LILLIX keeps the right to update the above list whenever it is required.

• There should be one cable (FiberOptics or Copper) per member, no shared cable is allowed as LILLIX switches run MAC filtering.
• LILLIX keeps the right to ask applicants to provide bandwidth justification whenever felt necessary.
• 802.3d Ethernet aggregation is possible, as much as port bandwidth upgrade, and is subject to LILLIX‘s approval.