Technical Information

Physical

1.1 It is recommended that Ethernet and FastEthernet interfaces are configured with duplex, speed and other configurations and not be auto-sensing. GigE and higher speed interfaces shall be configured to be auto negotiating.

MAC Layer

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

0x0800 – IPv4

0x0806 – ARP

0x86dd – IPv6

2.2 Frames forwarded from attached customer device(s) to a member interface on the JED-IX Peering LAN(s) shall all have the same source MAC address.

2.2.1 A member interface delivered over a link-aggregated port shall be treated as a single ingress port for the purposes of clause 2.2.

2.3 Frames forwarded to a member interface which is part of the JEDIX peering LAN(s) shall not be addressed to a multicast or broadcast MAC destination address except as follows:

• broadcast ARP packets
• multicast IPv6 Neighbour Solicitation packets
• where a member interface is a member of the JEDIX multicast VLAN, in which case frames may be forwarded which are destined to multicast group addresses

2.4 Traffic for link-local protocols shall not be forwarded to member interfaces which are part of the JEDIX peering LAN(s) except for the following:

• ARP
• IPv6 Neighbour solicitations and advertisements
• Link local protocols includes but is not limited to:

IRDP

ICMP redirects

IEEE802 Spanning Tree

Vendor proprietary discovery protocols (e.g. CDP, EDP)

Interior routing protocol broadcasts (e.g. OSPF, ISIS, IGRP, EIGRP)

BOOTP/DHCP

PIM-SM

PIM-DM

DVMRP

IP Layer

3.1 Member interfaces connected to JEDIX peering LAN ports shall only use IP addresses and netmasks (prefix lengths) assigned to them by JEDIX. In particular:

• IPv6 addresses (link & global scope) shall be explicitly configured and not auto-configured.
• IPv6 site-local addresses shall not be used.

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

Routing

4.1 All exchange of routes across the JEDIX network shall be via BGP4

4.2 AS numbers used in BGP-4 sessions across the JEDIX network shall not be from ranges reserved for private use. The only exception to this is when a BGP speaker is collecting routing information for analysis and not for immediate routing decisions. In this case the BGP speaker may use a private AS number. If it does so it shall not advertise any routes.

4.4 IP address space assigned to the JEDIX peering LANs shall not be advertised to other networks without explicit permission of JED-IX.

4.5 All routes advertised across the JEDIX network shall point to the router advertising it UNLESS agreement has been made in advance in writing by JEDIX and the two members involved. (For the avoidance of doubt) The JEDIX route servers are not routers and shall advertise routes pointing to the advertising router.

4.6 All routes to be advertised in a peering session across JEDIX shall be registered in the RIPE or other public routing registry.

4.7 Members may use more than one ASN for their JEDIX peering provided that each ASN presented shares the same NOC and peering contact details.

Forwarding

5.1 Traffic on member interfaces connected to the JEDIX peering LAN(s) shall only be forwarded to a JEDIX Member when permission has been given by the receiving Member either:

5.1.1 by advertising a route across the JEDIX network, or

5.1.2 explicitly in writing.

5.2 Traffic shall not be routinely exchanged between two member interfaces connected to the JEDIX peering LAN(s) and owned by the same JEDIX Member.