The Largest Romanian Interconnection Platform

interlan

2018-07-12 - Technical Regulations

I. Recommendations

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.

II. Obligations

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)
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

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-bit in the case of IPv4, and 96-bit 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

Accepted (large):
39107:0:ASN – don’t advertise to peer with ASN
39107:1:ASN – advertise to peer with ASN
39107:0:0 – don’t advertise to any ASN
39107:1:0 – advertise to all ASN

Accepted:
39107:ASN – advertise only to peer with ASN
0:0 – don’t advertise to any ASN
0:ASN – don’t advertise to peer with ASN

0: communities have precedence over 39107: communities

Sent:
39107:100 – Members
39107:200 – Partners
39107:300 – Bucharest
39107:400 – Romania except Bucharest
39107:500 – International (outside Romania)
39107:600 – Content provider
39107:650 – Not content provider
39107:700 – Another IX
39107:ASN – ASN specific community – all routes are marked by this style of community

2018-03-18 - InterLAN joins the AS112 project by providing an anycast instance to respond DNS queries

The AS112 project is a group of name server operators in an autonomous system running anycasts instances of name servers that respond to reverse DNS queries for private addresses and private networks sent to the Internet. The distributed sink for queries sent to non-unique IP addresses helps reduce the load on the authoritative servers due to this kind of ambiguous queries by their nature which can not be answered corectly. It is named after the Autonomous System Number (ASN) that has been assigned to it.

InterLAN is one of the volunteer operators participating in the AS112 project. Anycasts prefixes of this project are advertised in InterLAN platform by a dedicated server that has peering sessions with Exchange Route Servers, this way the service is automatically available to network operators connected to these RSs.
More details about this project and how it works can be found here:

https://www.as112.net/
https://www.ripe.net/analyse/dns/as112
https://tools.ietf.org/html/rfc7534
https://en.wikipedia.org/wiki/Blackhole_server

2018-03-07 - On 6 and 7 March 2018, InterLAN attends CEE Peering Days in Berlin

On 6 and 7 March 2018, the annual international conference CEE Peering Days takes place in Berlin, Germany. Experts, engineers, peering managers, internet service providers, and data center operators from Central and Eastern Europe are participating in the event. The first edition of this conference took place in 2013, with over 200 participants each year with the support of the most important organizations in european community.

The conference program includes two days of technical workshops and presentations on various topics of general interest, as well as bilateral meetings.

InterLAN attendees had discussions with others on various on-going partnerships as well as business opportunities.

More details can be found on the event website: www.peeringdays.eu.

2018-03-06 - The Romanian Fiber Optic Conference conference on Smart Connexions of Tommorow takes place on 6 March

The Romanian Fiber Optic Conference is the most anticipated event of the Romanian industry and this year is held on March 6 at the Radisson Blu Hotel in the capital. The event will be structured in two sections and will include presentations and debates on national themes of common interest.

According to its stated purpose, this year’s Smart Connexions of Tommorow edition aims to be a catalyst for ideas and an environment conducive to the exchange of experiences, the chosen theme being an argument in favor of forecasts for the future, helping the target make business decisions favorable to their business.

The delegation of Interlan Association participates in the event, the members of the delegation having several talks with other attendees. More details about the event can be found at http://afor.ro/ro/home/rfoc.html.

2018-02-27 - InterLAN representatives participate to international conference APRICOT 2018 and SANOG 31 Meeting

Between 24-28 February 2018, an InterLAN delegation attends the international conference APRICOT 2018 and the SANOG 31 Meeting, which are held simultaneously in Kathmandu, Nepal.

APRICOT 2018

APRICOT 2018 (Asia Pacific Regional Internet Conference on Operational Technologies) is the largest Asia Pacific Internet conference with an attendance of more than 700 engineers, researchers, operators and service providers, and various policy community representatives from over 50 countries.

SANOG 31 (South Asian Network Operators Group) is a forum on operational issues and technologies of interest to data operators in the South Asian region.

APNIC 45 (Asia Pacific Regional Internet Registry) and APIX 17 (Asia Pacific Internet ExchangeAssociation) are also taking part in the event.

InterLAN representatives had several interventions:

In the Peering Forum: IXP Session, Eric Băleanu made a short presentation of InterLAN Internet Exchange (video).
In the NOG BoF session, Cristian Copcea spoke about the challenges InterLAN faced as host of RONOG (video).
In the Network Operations session, Cristian Copcea presented the TVX project and the video stream management application developed by InterLAN (video).
In the NOG Reports session, Eric Băleanu presented a report of RONOG editions so far (video).

Various discussions were held with other attendees on ongoing and future partnerships.

More details about this event can be found on its official website.

 

2018-02-26 - Bollywood and Mooz Dance TV channels are available via multicast stream on the InterLAN TVX platform

The Bollywood TV and Mooz Dance TV channels have become available via multicast streaming on the InterLAN TVX platform:
Bollywood HD, Bollywood Film TV, Bollywood Classic TV, Bollywood TV, Mooz Dance HD, Mooz Dance TV.

Other TV Channels are availabile on the same platform:
Antena 1 HD, Antena 1, Antena 3 HD, Antena 3, Antena Stars HD, Antena Stars, Happy Channel HD, Happy Channel, ZU TV HD, ZU TV, Rock TV HD, Rock TV, Kiss TV HD, Kiss TV, Magic TV HD, Magic TV, Bucuresti TV HD, Bucuresti TV, Cinethronix TV, Columna TV, Travel Mix, Valea Prahovei TV, Orizont TV, Telestar 1 TV, Tradiții TV.

The complete list of TV channels available on InterLAN TVX Platform can be found here.

2018-01-11 - InterLAN supports Euro-IX Fellowship Program in 2018

InterLAN supports the Euro-IX Fellowship Program in 2018. This program provides financial assistance to Internet Exchanges in difficulty in order to increase the Euro-IX membership.

Interlan Association is a full member of Euro-IX since 2008 and is supporting the Fellowship program since 2016.

You can find more details about this program here.

Feedback from fellows can be found here.

2018-01-09 - Antena TV Group connects to InterLAN

Antena TV Group connects to InterLAN on a 10G port.

2017-12-22 - Facebook raises interconnection capacity to InterLAN Internet Exchange at 80 Gbps

Facebook raises interconnection capacity to InterLAN Internet Exchange platform at 80 Gbps amid steady growth in aggregated traffic. Facebook is the most popular social platform in Romania and users of Internet service providers connected to InterLAN have improved experience when accessing the application due to high data transfer speeds and lower response times.

2017-12-12 - Interlan Association donates funds for KINIX

Interlan Association supports the KINIX – Kinshasa Internet Exchange Point with funds to restore the equipment affected by the fire in the KINIX premises. The purpose of the donation is to aid in restoring the electrical network destroyed by the fire.