Peering policy

Peers must comply with the following

• A publicly routable ASN
• Publicly routable address space
• ASN record completed in PeeringDB
• 24×7 NOC contact capable of resolving BGP routing issues
• Ability to do BGP between peers (and ideally the route servers — optional)
• Peer contact information must be provided to help enable a response in the event of any issues that may impact the IX or other peers
• Re-advertising the IX peering prefixes is not permitted

Allowed traffic

Ethernet types

• 0x0800 — IPv4
• 0x0806 — ARP
• 0x86DD — IPv6

MAC security

Layer 2 MAC filtering is implemented at EdgeIX to help prevent unauthorised traffic from entering the exchange. Each peering port or bundle is restricted to a single MAC address.

No proxy ARP

Unicast only — except for broadcast ARP and IPv6 Neighbour Discovery.

No link-local traffic

The following protocols are fine:

• ARP
• IPv6 ND

Please assume all others are not allowed.

Community-based prefix filtering

The EdgeIX route server system provides well-known communities to allow members to control the distribution of their prefixes.

Standard communities

Community	Description
0:peer-as	Prevent announcement of a prefix to a peer
24224:peer-as	Announce a route to a certain peer
0:24224	Prevent announcement of a prefix to all peers
24224:24224	Announce a route to all peers

Large communities

Large community	Description
24224:0:peer-as	Prevent announcement of a prefix to a peer
24224:1:peer-as	Announce a route to a certain peer
24224:0:0	Prevent announcement of a prefix to all peers
24224:1:0	Announce a route to all peers

For example, to instruct the route server to distribute a prefix only to AS64111 and AS64222, tag the prefix with 0:24224, 24224:64111 and 24224:64222.

Alternatively, to announce a prefix to all EdgeIX members except AS64333, tag it with community 0:64333.