Peering policy

Member must:

  1. Have registered AS number (autonomous system) and at least one IP prefix.
  2. Maintain a complete and current https://peeringdb.com profile.
  3. Use on the connection interface only those IP addresses and network masks, which were provided by 1-IX. And only those MAC addresses, which were reported to 1-IX.
  4. Announce BGP prefixes in accordance with routing policy in RIPE, ARIN or RADB databases. In addition, maintain complete and current AS-SET objects. In addition, maintain complete and current ROA objects for the RPKI protocol.
  5. Only announce prefixes with its own next-hop IP address
  6. Forward traffic only to BGP prefixes received from the connection interface to 1-IX. Do not use a static route on the connection to 1-IX, or otherwise send traffic to 1-IX through any route not received via BGP.
  7. Not redistribute Peering LAN networks of the traffic exchange point (185.1.213.0/24,185.1.254.0/24,2001:7f8:115::0/64, 2001:7f8:115:1::0/24) beyond the member’s router.
  8. Transmit only Ethernet frames of types: 0x0800 – IPv4, 0x0806 – ARP, 0x86dd – IPv6, 0x8100 – IEEE 802.1q .
  9. Address Ethernet frames only to MAC addresses received on the connection interface to 1-IX or to the broadcast address of ARP packets, or to the multicast address of the ICMPv6 Neighbor Discovery protocol.
  10. On the interfaces connecting to 1-IX, disable all link-local protocols, Proxy ARP, Ip directed broadcast, ip redirects.
    Examples of prohibited protocols:
    STP, RSTP, MSTP, PVSP, PVST+
    CDP, VTP, DTP, PAGP, LLDP, UDLD, EDP, ELRP, ERPS, EAPS
    MRP, MVPR, MMRP, GARP, GVRP
    BOOTP, DHCP
    ICMPv6 ND-RA, IRDP, ICMP Redirects
    OSPF, ISIS, IGRP, EIGRP
    PIM-SM, PIM-DM, DVMRP.