ALP-IX Technical Requirements

Scope

These Technical Requirements (TR) define the ways in which you may or may not make use of the ALP-IX services. This document will be regularly reviewed and revised in the light of operational experience to ensure maximum protection of service to ALP-IX members. Subsequent versions of this document are effective after 10 working days of having been posted upon ALP-IX website.

Motivation

Members' use of the ALP-IX network shall at all times conform to the relevant standards as laid out in STD0001 and associated Internet STD documents.

Physical

1.1 Ethernet interfaces attached to ALP-IX ports shall be explicitly configured with duplex, speed and other configuration settings and shall not be auto-sensing.

MAC Layer

2.1 Frames forwarded to ALP-IX ports shall have one of the following ethertypes

2.2 All frames of a service forwarded to an individual ALP-IX port shall have the same source MAC address.

2.3 Frames forwarded to ALP-IX ports shall not be addressed to a multicast or broadcast MAC destination address except as follows:

2.4 Traffic for link-local protocols shall not be forwarded to ALP-IX ports except for the following:

These link-local protocols include but are not limited to the following list

2.5 ARP traffic shall not exceed 20 pps per port/vlan.

IP Layer

3.1 Interfaces connected to ALP-IX ports shall only use IP addresses and netmasks (prefix lengths)assigned to them by ALP-IX. In particular:

3.2 IP packets addressed to ALP-IX peering LAN directed broadcast address shall not be automatically forwarded to ALP-IX ports.

Routing

4.1 All exchange of routes across the ALP-IX network shall be via BGP4(+).

4.2 AS numbers used in BGP4(+) sessions across the ALP-IX network shall not be from range reserved for private use.

4.3 All routes advertised shall be aggregated as far as possible.

4.4 IP address space assigned to ALP-IX peering LAN shall not be advertised to other networks without explicit permission of ALP-IX. All routes advertised across the ALP-IX network shall point to the router advertising it unless an agreement has been made in advance in writing by ALP-IX and the members involved. All routes to be advertised in a peering session across ALP-IX shall be registered in the RIPE or other public routing registry. Members may use more than one ASN for their ALP-IX peering provided that each ASN presented shares the same NOC and peering contact details.

Forwarding

5.1 Traffic shall only be forwarded to a ALP-IX member when permission has been given by the receiving member either:

5.2 Traffic shall not be routinely exchanged between two ALP-IX ports owned by the same ALP-IX member.