It is recommended that Ethernet and Fast Ethernet interfaces are configured with duplex, speed and other configurations not be auto-sensing. GigE and higher speed interfaces shall be configured to be auto negotiating.
Frames forwarded to IXP ports shall have one of the following ether-types
Frames forwarded from attached member device(s) to a member interface on the IXP Peering LAN(s) shall all have the same source MAC address.
Frames forwarded to an interface which is part of the IXP 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 [IXP NAME] multicast VLAN, in which case frames may be forwarded which are destined to multicast group addresses
Interfaces connected to IXP peering LAN ports shall only use IP addresses and netmasks (prefix lengths) assigned to them by IXP NAME. In particular:
IPv6 addresses (link & global scope) shall be explicitly configured and not auto-configured.
IPv6 site-local addresses shall not be used.
All exchange of routes across the IXP network shall be via BGP4
AS numbers used in BGP4 sessions across the IXP 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.
IXP supports good engineering practice and IXP participants are encouraged to aggregate their routes in accordance with Route Aggregation Best Current Practice, from time to time in force.
IP address space assigned to the IXP peering LANs shall not be advertised to other networks without explicit permission of IXP.
All routes advertised across the IXP network shall point to the router advertising it UNLESS agreement has been made in advance in writing by IXP and the two participants involved. (For the avoidance of doubt) The IXP route servers are not routers and shall advertise routes pointing to the advertising router.
All routes to be advertised in a peering session across the IXP shall be registered in a public routing registry.
Participants may use more than one ASN for their IXP peering provided that each ASN presented shares the same NOC and peering contact details.
Traffic on member interfaces connected to the IXP peering LAN(s) shall only be forwarded to an IXP NAME Participant when permission has been given by the receiving Participant either:
by advertising a route across the IXP network, or
explicitly in writing.
Traffic shall not be routinely exchanged between two participant interfaces connected to the IXP peering LAN(s) and owned by the same IXP Participant.