Exchange Peering Policy
1. The peering member must have a registered, public AS Number issued with the appropriate Regional Internet Registry for your country (RIPE, ARIN, APNIC, LACNIX, AfriNIC)2. The peering member must provide F4 IX with a NOC contact3. The peering member must use BGPv4 or its successor and must set NEXT_HOP_SELF, when advertising routes4. The only ethertypes allowed are IPv4 (Ethertype 0x0800), IPv6 (Ethertype 0x86DD), and ARP (Ethertype 0x0806)5. The peering member is only allowed to announce prefixes registered to the member and contains appropriate IRR6. The minimum prefixes announced should be /24 for IPv4 and /48 for IPv6. Members are additionally encouraged to aggregate prefixes, when ever possible.7. The only non-unicast traffic allowed is broadcast ARP and multicast ICMPv6 Neighbor Discovery packets. Per-neighbor timeouts for broadcast/multicast packets should be set to 4 hours8. The peering member should not propagate F4 IX prefixes, externally and minimize, internally9. The peering member may not point default route or use another member's or F4 IX's resources without permission10. The peering member must be present at the facility to peer over F4 IX
© F4 Networks, LLC