Participant Info

  • LocationRO
  • Network ASNs39107
  • IX-F IDs37

Implementation of MANRS Actions

  • Action 1: Filtering of Route Announcements InterLAN-IX filters prefixes based on IRR database (ASN/AS-SET) and RPKI information. Additional filters are also in place, such as first-hop validation.
  • Action 2-1: Offer assistance to its members to maintain accurate routing information in an appropriate repository (IRR and/or RPKI) We provide on demand support for our members.
  • Action 2-2: Offer assistance in implementing MANRS ISP Actions for the members InterLAN organizes regular workshops on technical topics and among the topics presented and debated we have MANRS as well as other topics of interest to the InterLAN community such as IRR, RIPE Database, RPKI, PeeringDB, RIPE Atlas, IXP Manager etc.InterLAN is hosting the RONOG event. RONOG (Romanian Network Operators Group) is a platform for people to share ideas in an informal way, focusing on technical aspects which can affect the Internet. We encourage all the networks in our region to participate in RONOG event dedicated to all network operators to engage and take part and act for the Internet resilience.The RONOG project is open for our local and regional community of networks implementing best security practices available today and encouraging all networks to join this community. Throughout all editions, the RONOG event intensely promoted and debated the MANRS project and its importance for all network operators that actively contribute to ensuring a safer and more stable Internet.
  • Action 2-3: Indicate MANRS participation on the member list and the website We are currently using IXP Manager and each MANRS-compliant member is stated as such on this application.
  • Action 2-4: Provide incentives linked to MANRS readiness During the workshops organized by InterLAN we offered different prizes to those participants who submitted the signed ROAs and RPKI validation and we offered technical support for the rest of the attendees to help them sign ROA and RPKI validation.
  • Action 3: Protect the peering platform There are specific rules and filters that do not allow traffic that is unnecessary. Below is a list with the services that are not allowed: a. ICMP redirect b. IEEE802 STP c. IRDP - (Internet router discovery protocol) d. BOOT/DHCP e. DVMRP f. UDLD g. L2 keepalive h. ICMPv6 ND-RA i. Trunking protocols: VTP, DTP j. Proprietary protocols, including but not limited to: CDP, EDP k. Rounting protocols: OSPF, ISIS, IGRP, EIGRP, RIP l. IGMP should not be enabled on IEX VLAN m. xSTP should not be enabled on the port connected in InterLAN infrastructure
  • Action 4: Facilitate global operational communication and coordination between network operators We are using several mailing lists in order to communicate with our members.
  • Action 5: Provide monitoring and debugging tools to the members A Looking Glass is available internally for our peers. From there one can inspect his own prefixes and prefixes from other peers. It contains all the relevant information, including reasons why a prefix is filtered to ease the debugging of potential issues. Other monitoring and debugging tools available include sFlow and MRTG.

Why InterLAN Internet Exchange Supports MANRS