Connection Policies
Requirements for peering at FOUNTAIN-IX
01
AS Number Requirement
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)
02
NOC Contact
The peering member must provide Fountain-IX with a NOC contact
03
BGP Protocol
The peering member must use BGPv4 or its successor and must set NEXT_HOP_SELF, when advertising routes
04
Allowed Ethertypes
The only ethertypes allowed are IPv4 (Ethertype 0x0800), IPv6 (Ethertype 0x86DD), and ARP (Ethertype 0x0806)
05
Prefix Registration
The peering member is only allowed to announce prefixes registered to the member and contains appropriate IRR
06
Minimum Prefix Length
The minimum prefixes announced should be /24 for IPv4 and /48 for IPv6. Members are additionally encouraged to aggregate prefixes, when ever possible.
07
Non-Unicast Traffic
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 hours
08
Route Propagation
The peering member should not propagate Fountain-IX prefixes, externally and minimize, internally
09
Resource Usage
The peering member may not point default route or use another member's or Fountain-IX's resources without permission
10
Physical Presence
The peering member must be present at the facility to peer over Fountain-IX