1. Traffic Participants are encouraged to announce all their routes and accept all routes from InterLAN. For a better and easier connectivity it is recommended that participants perform BGP sessions with InterLAN route-servers. Participants in peering are advised to establish a page on their own website (e.g. website.com/peering), where the peering access procedure is detailed for whoever may be interested.
2. It is recommended that the devices used for interconnection be specialized equipment such as routers or Layer III class switches.
1. The traffic that runs through the InterLAN infrastructure as a result of the exchange of information between participants should not be filtered or altered. The interception or the examination of this traffic will be made with the written approval of InterLAN technical department or at the written request of qualified authorities, according to the law in force.
2. Potential participants are entirely responsible in terms of connectivity with InterLAN POP where the interconnection will take place.
3. InterLAN alone will decide the route to transfer data packets from the partner in the InterLAN network.
4. Traffic participants will not act send illegal traffic or other traffic that hinders InterLAN peering use by other partners (e.g. ARP spoofing, sniffers installation, etc.).
5. Ethernet packets sent to the access ports in InterLAN by the partners will have only the following types:
a. 0x0800 – IPv4
b. 0x0806 – ARP
c. 0x86dd – Ipv6
d. 0x8100 – 802.1q
6. It is forbidden to activate Proxy ARP on the interfaces towards InterLAN.
7. All Ethernet frames representing Internet Exchange traffic sent to an access port in InterLAN will have necessarily the mac address/addresses associated with IPv4 and IPv6 allocated by InterLAN technical department.
8. An IP address used for the interconnection with InterLAN RSes and with the other partners will be assigned to each peering participant. The number of IP addresses assigned to a traffic participant can be altered according to interconnection needs, supported by submitted documents.
The assignment of additional IP addresses is done by the InterLAN technical department in following situations:
a. The need for back up BGP sessions
b. Private BGP sessions operation
c. Simultaneous active sessions of the same traffic partner (identified by ASN)
9. The traffic specific to local protocols should not be sent towards the access ports in InterLAN.
10. The following type of traffic and protocols are not allowed:
a. ICMP redirect
b. IEEE802 STP
c. IRDP – (Internet router discovery protocol)
g. L2 keepalive
h. ICMPv6 ND-RA
i. Trunking protocols: VTP, DTP
j. Proprietary protocols, including but not limited to: CDP, EDP
k. Routing 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
11. The outgoing broadcast traffic of a port should not exceed 20 pps / port / vlan.
12. MAC address numbers:
a. At client ports, only one MAC address is accepted for each IP address assigned as long as the client does not use other services than IX services. If the traffic is originated by more than one MAC address, the port will be disabled for 5 minutes.
b. More than one MAC address is accepted on the client ports depending on the services used (transit, multicast, multiple routers). The limit will be established with the customer, and if the rule is exceeded, the rule from the previous paragraph will apply. The limit may increase with the approval of InterLAN.
13. The routes exchange will be achieved only via BGP IPv4, IPv6 sessions.
14. The maximum length of a prefix announced by participants should not exceed 24-bits in the case of IPv4, and 96-bits in the case of IPv6.
15. All routes announced in InterLAN which originate from traffic participants public ASes must be registered in RIR’s database managing them (route-objects must exist).
16. Each peering participant must have a public ASN and at least one IP address class originated from his own ASN.
17. BGP sessions will announce only own IP address classes or customer’s classes and not those of other providers without their express consent along with InterLAN’s consent.
18. InterLAN’s peering reserved IP address space will be not announced in other networks except with the prior written approval of InterLAN technical department.
19. All routes announced in InterLAN will have set the nexthop to the partner making the announcement, unless the consent of technical department was obtained for the members announcing the routes with nexthop to other partners.
20. The announcement of private address classes (RFC1918) in InterLAN is not permitted.
21. A participant will send traffic to another participant’s port only in case when he has obtained permission from the latter via a route announced through InterLAN route-servers or a private BGP session.
22. The use of static routes is not allowed. All traffic routing decisions through the connection with InterLAN will be taken on the basis of by BGP session received routes.
23. Maintenance works must be notified to the InterLAN technical department at least 48 hours prior to the event, with a declared goal to take all necessary measures to prevent any compatibility and/or connectivity issues of the participants. In case of accidental equipment replacement as result of their failure, it is required to announce immediately, by any means, the InterLAN technical department.
III. BGP communities
39107:39107 – advertise to all peers
39107:ASN – advertise only to peer with ASN
0:0 – don’t advertise prefix
0:ASN – don’t advertise to peer with ASN
0: communities have precedence over 39107: communities
39107:100 – Members
39107:200 – Partners
39107:300 – Bucharest
39107:400 – Romania except Bucharest
39107:500 – International (outside Romania)
39107:600 – Content provider
39107:700 – Another IX
39107:ASN – ASN specific community – all routes are marked by this style of community
InterLAN attends „Enhanced National Cyber Security Services and Capabilities for Interoperability”, the first workshop organized by Romania National Computer Security Incident Response Team at Ramada Hotel, Constanta. The event focuses on the technical development for The National Cybersecurity Services Platform, an open running project. The project aims to ensure the interconnection of CERT-RO and other national cybersecurity capabilities and services with the EU cooperation mechanisms and core service platform, facilitating an efficient information sharing and incident management at the national and European level.
During the workshop more than 40 representatives from the public, private and academic environment will talk about issues related to launching the platform and facilitating technical discussions from the development stage so that the most appropriate solutions are implemented.
InterLAN is hosting the 7th regional RIPE SEE Meeting in Timișoara, Romania. The agenda consists of two days of tutorials, presentations and discussions about security, IPv6, BGP, routing, peering new Technologies, GDPR, data protection.
InterLAN became an authorized RoTLD partner and implemented the .ro domain management system, the application is available here https://registrar.interlan.ro.
RIPE 76 Meeting takes place between 14 and 18 May, in Marseille, France. InterLAN delegates attends RIPE 76 and participates during 5 days of presentations, tutorials, workshops and open discussions.
InterLAN Internet Exchange will host the seventh regional meeting of network operators in Southeast Europe. The regional meeting RIPE SEE 7 will be held from June 18th to 19th in Timişoara, the event being organized by RIPE NCC. Register here. Over the course of the two days, Internet service providers, network operators and other industry stakeholders meet to discuss the policies and procedures for allocating and managing Internet numbering resources as well as other technical issues. Participants have the opportunity to share their own experiences with the use of the latest technologies and have the opportunity for new partnerships with the other present entities, during the presentations and social events organized at the event. More details can be found here.
InterLAN attends the “Ziua Comunicatiilor 2018” conference, which is held at the JW Marriott Hotel and brings together top representatives of public institutions in the telecommunications sector, telecom operators, IT & C companies and other providers of electronic solutions for telecommunications. InterLAN supports together with other telecom associations this year’s edition of “Ziua Comunicatiilor 2018”.
InterLAN attended “DataCenter Forum 2018” at Willbrook Platinum Center. The topics of the conference includes analyzes and debates on the current situation of the local market, both from the perspective of ongoing investments and the challenges that industry is going through.
Between 4-6 May Asociatia Interlan organizes for its members a technical workshop in Mamaia, Constanta. The participants were actively involved and discussed topics such as TVX Platform, RIPE Atlas, Surveillance systems, IXP Manager, Dual stack IPv4 & IPv6, PeeringDB tool and other topics of interest for InterLAN community.
Bunea Telecom becomes a traffic partner in InterLAN Internet Exchange.