Physical Interface Specifications

The following types/speeds of Ethernet interfaces are available:

if/cecable typewavelengthDistanceinput (dbm)output (dbm)
TXUTP cat5eN/A100mN/An/A
SXMutimode Fiber 62.5/125 OM1 850nm275m0….-21~-3
LXSingleMode Fiber310nmTbd-3……..-25-3

Ethernet Specifications

Framing & Ethertypes

The PS-IX infrastructure offers ports that implement the Ethernet standard (IEEE 802.3-2012 / Ethernet II).

The members’ ports are, by default, in “access” mode, which means that only untagged Ethernet Frames are allowed. 802.1q-tagged frames can be supported, if necessary (e.g., for private peerings).

Allowed ethertypes are: IPv4 (0x0800), IPv6 (0x06dd), ARP (0x0806) and 802.3ad – LACP (0x8809). Traffic with any other ethertype may be dropped without notice.

Maximum Transmission Unit (MTU)

The allowed L2 payload (L3 MTU) for PS-IX is 9000 bytes. Frames exceeding this payload may be dropped without further notice.

Link Aggregation (link-bundling, ether-channel, port-channel)

Links of the same speed, on the same device, can be bundled into a single logical interface. Bundling can be configured statically or dynamically through LACP (802.3ad).

In both cases, per-flow load-balancing is implemented (source/destination IP addresses & ports).

Port Speed/Duplex

For copper ports, PS-IX explicitly configures speed and full-duplex on its side; and auto-negotiation is enabled (so that these settings are advertised to the members). Members can explicitly configure speed/full-duplex, or rely on auto-negotiation, or do both (explicitly configure speed/full-duplex and keep auto-negotiation active) — the latter is the safest option, than suggested.

Public Peering LAN Specifications


The public peering LAN address space is:


IPv6: 2a07:8780:6e::/64

Members are assigned one IPv4 and one IPv6 address per physical port or bundle in order to connect their router on the public peering LAN. Under certain circumstances, a second IPv4 and a second IPv6 address can be assigned for redundancy.

Members are not allowed to use IPs other that the ones assigned to them on the ports connecting to PS-IX. Proxy-ARP is not allowed on the PS-IX ports; and NAT is not allowed on the PS-IX IPs.

Members are not allowed to redistribute the peering LAN address space into their eBGP and announce it to other AS.

MAC addresses

MAC address policy and MAC address change

For each assigned PS-IX IP address, members need to specify a single corresponding MAC address. Based in this correlation, PS-IX statically configures the provided MAC addresses on the relevant ports (static mac learning and layer2 access lists that drop traffic sourced from other MAC addresses).

In case of hardware replacement (router, port, card etc), the member need to contact PS-IX personnel in order to explicitly allow the new MAC. To facilitate the transition, both old and new MAC can be permitted for a limited period of time. Please note that, after a MAC change, the other members’ ARP tables need to be updated. This process relies on appropriate ARP/gARP messages between the replaced equipment and the equipment of each of the member’s peers. If, for any reason, this process fails for a peer,significant downtime might occur. In order to resolve such a problem, the member will need to communicate directly with the affected peer(s) — PS-IX is unable to trigger such an ARP update.

Traffic Limitations

Members are not allowed to advertise spoofed or private address space and AS numbers.

Multicast is not allowed on the public peering LAN .