Public Peering

Ports, IPv4 and IPv6

All ports on the LU-CIX public exchange infrastructure are Ethernet and are available at the following speeds:
100M (FE) - 100BASE-TX
1G (GE) – 1000BASE-SX, 1000BASE-LX, 1000BASE-T
10G (10GE) – 10GBASE-SR, 10GBASE-LR

Additionally LU-CIX is able to aggregate FE, GE and 10G ports to provide higher bandwidth trunks.

Members can use ports for unicast IPv4 and IPv6 or multicast IPv4:
IPv4 and IPv6 unicast is available on the main peering VLAN
IPv4 multicast is run on a separate VLAN

Membership requirements

LU-CIX ASBL 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 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.

Motivation

Members' use of the LU-CIX network shall at all times conform to the relevant standards.

Physical Connection / Interface settings

100BASE-TX and 1000BASE-T Ethernet interfaces attached to LU-CIX ports must be explicitly configured with speed, duplex other configuration settings, i.e. they should not be auto-sensing.

MAC Layer

Ethernet framing

The LU-CIX infrastructure is based on the Ethernet II (or “DIX Ethernet”) standard. This means that LLC/SNAP encapsulation (802.2) is not permitted.

Ethertypes

Frames forwarded to LU-CIX ports must have one of the following Ethertypes:
0x0800 - IPv4
0x0806 - ARP
0x86dd - IPv6

One MAC address per port

Frames forwarded to an individual LU-CIX port shall all have the same source MAC address.

No proxy ARP

Use of proxy ARP on the router's interface to the Exchange is not allowed.

Unicast only

Frames forwarded to LU-CIX ports shall not be addressed to a multicast or broadcast MAC destination address except as follows:
broadcast ARP packets
multicast ICMPv6 Neighbour Discovery packets. This DOES NOT include Router Discovery packets.
multicast is only allowed on the separated Multicast VLAN

No link-local traffic

Traffic for link-local protocols shall not be forwarded to LU-CIX ports.

Link-local protocols include, but are not limited to, the following list:
IRDP
ICMP redirects
IEEE 802 Spanning Tree
Vendor proprietary protocols. These include, but are not limited to:
- Discovery protocols: CDP, EDP - VLAN/trunking protocols: VTP, DTP
Interior routing protocol broadcasts (e.g. OSPF, ISIS, IGRP, EIGRP)
BOOTP/DHCP
PIM-SM
PIM-DM
DVMRP
ICMPv6 ND-RA
UDLD
L2 Keepalives
The following link-local protocols are exceptions and are allowed:
ARP
IPv6 ND

IP Layer

No directed broadcast

IP packets addressed to LU-CIX peering LAN's directed broadcast address shall not be automatically forwarded to LU-CIX ports.

IP addressing

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 in the 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.

Routing

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.

Forwarding

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