GLV-IX Member requirements
All members of GLV-IX are always required to adhere to all requirements of GLV-IX. Prior to their membership application being approved, new Members must demonstrate, that they will be able to meet these requirements. Members who cease to meet any of these requirements after joining GLV-IX may lose their membership. Operator of internet exchange may amend the requirements and policy from time to time and will publish those changes on the GLV-IX website and notify members. Members agree to comply with any changes within 30 days.
GLV-IX General Requirements
- Member must be located within territory of Latvia.
- Member must be either a Internet Service Provider (ISP), Latvian state institution or municipality, Latvian state-owned company or business entity registered and operating in Latvia and providing services to customers in Latvia.
- The primary means of communication between Members is e-mail.
- Each Member provides and keeps up to date their contact information points:
- A legal/contractual contact point, with an e-mail address that will be used for official communications.
- An administrative contact point, for administrative issues.
- A technical contact point, for technical issues.
- A NOC (Network Operations Centre), with a telephone number for emergencies (in case member is an ISP).
- An appropriate level of insurance relating to equipment located at GLV-IX and staff indemnification is to be maintained by all Members of GLV-IX with respect to GLV-IX, to companies providing services to GLV-IX, and to third parties. Members will not hold operator of GLV-IX liable for any loss whatsoever resulting from the activities of another Member.
- Members must not carry out any illegal activities through GLV-IX.
- Members must ensure that their usage of GLV-IX is not detrimental to the usage of GLV-IX by other Members. Members must also ensure that their usage follows applicable Internet standards as published by the IETF and as documented in the current version of STD 1.
- Members should not routinely use GLV-IX for carrying traffic between their own routers.
- Traffic may only be forwarded from one GLV-IX Member to another if permission has been given by the recipient, either by advertising a route across an GLV-IX or else explicitly in writing.
- Member can install devices necessary for connecting to GLV-IX in GLV-IX rack. The equipment must be mountable in a 19″ rack and powered with 230V AC. Any additional equipment necessary for mounting Member’s devices must be provided by Member. Member equipment can only be installed in positions in rack provided by GLV-IX operator. The only authorized connections from the devices of the Member located in the peering services area are WAN connections and connections with the switching infrastructure.
- Any equipment installed by a Member in GLV-IX rack must be clearly labelled as belonging to the Member. Members must notify GLV-IX of equipment details and value prior to installing or changing any equipment.
- Members must not interfere with equipment owned by others installed at GLV-IX or in the room, rack or cage containing GLV-IX without the explicit permission of the owner.
- Members have a duty of confidentiality to GLV-IX and other GLV-IX Members. Members must not install packet sniffers to monitor traffic passing through GLV-IX.
- Members may not directly connect customers to their equipment housed in any GLV-IX rack.
- Members may not connect equipment to or otherwise provide connectivity to GLV-IX switch infrastructure on behalf of non-Members.
- Member is not allowed to ask for payment or reward for traffic traversing GLV-IX infrastructure.
GLV-IX Technical Requirements
GLV-IX provides connectivity to its infrastructure using switched shared Ethernet LANs.
- All traffic frames destined to a particular GLV-IX physical interface and to GLV-IX peering LANs must have the same source MAC address. Member declares to GLV-IX operator their equipment MAC addresses that will be used for traffic exchange on GLV-IX.
- Physical interfaces of the same speed on the same physical GLV-IX switch may be aggregated together using IEEE 802.3ad link aggregation control protocol, by prior agreement with GLV-IX operator.
- For the purposes of gaining access to multiple GLV-IX peering LANs over the same physical port or link-aggregated group of ports, IEEE 802.1q packet framing may be used by prior agreement with GLV-IX operator. If 802.1q framing is used on a port or port group, then all packets on that port or port group must be configured to use 802.1q framing.
All traffic frames directed to GLV-IX peering LANs must be configured to use IEEE 802.3 Ethernet encapsulation, with one of the following ethertypes:
- 0x0806 – ARP
- 0x0800 – IPv4
- 0x86dd – IPv6
- With the exception of ARP and IPv6 Neighbour Discovery, traffic frames directed towards GLV-IX peering LANs must not be addressed to a broadcast MAC destination.
- Proxy ARP must be disabled on all interfaces connected to GLV-IX peering LANs.
With the exception of ARP and IPv6 Neighbour Discovery, link-local traffic must not be forwarded to GLV-IX peering LANs. Link-local traffic includes, but is not limited to:
- IEEE 802 Spanning Tree
- Vendor-proprietary discovery protocols (e.g. CDP, EDP)
- IPv6 Router Advertisement and Router Solicitation
- IPv4 ICMP redirects and IPv6 redirects
- All interior routing protocol announcements (e.g. RIP, OSPF, IGRP, EIGRP, ISIS)
- Member should use dedicated router (Layer 3) port. In case Member uses Layer 2 transport, the member has to ensure a loop free path without use of Layer 2 loop protection protocols. The path should be seen as equivalent to direct router port connection.
- Members must not configure IPv4 or IPv6 addresses on interfaces connected to GLV-IX peering LANs other than those assigned to them by GLV-IX operator.
- Members must not use and transmit data with source or destination addresses listed in RFCs as prohibited for global internet use (e.g. RFC 1918).
- Members must not use IPv4 or IPv6 addresses on interfaces connected to GLV-IX peering LANs for any purpose other than BGP peering on TCP port 179 and ICMP control traffic necessary for proper network operation, monitoring and diagnostics. These network addresses must not be used for network address translation or any other form of layer 3 traffic proxying.
- IP packets received from an GLV-IX peering LAN with a destination IP address of any GLV-IX peering LAN’s directed broadcast address must be ignored.
- Broadcast traffic forwarded to a particular GLV-IX peering LAN must not exceed 50 packets per second.
- GLV-IX operator reserves the right to disconnect any port which violates any of the requirements listed above.
GLV-IX Peering Policy
- Each Member must have their own Autonomous System number and register the routing policy for their AS in the RIPE routing registry or another public routing registry.
- Unicast peering between Members’ routers across GLV-IX will be via BGP (version 4).
- Each Member must register in advance, in the RIPE routing registry or another public routing registry, all routes to be announced through any peerings at GLV-IX.
- Members shall not generate unnecessary route flap or advertise unnecessarily specific routes in peering sessions with other Members across GLV-IX.
- Members may not advertise routes with a next-hop other than that of their own routers without the prior permission of the advertised party, the advertisee, and GLV-IX operator.
- Each Member may also peer directly via BGP with other Members of GLV-IX, but is not allowed to use static routing or any other routing protocols besides BGP on GLV-IX infrastructure.
- Each Member must peer with the GLV-IX route servers and route collectors. If a Member advertises any routes to another Member, it must also advertise these routes to the GLV-IX route servers and route collectors. Member is responsible to bring up at least one BGP peering connection to each GLV-IX Route Server and announce all prefixes or at least a significant part of his network.
- Member may also advertise their customer prefixes, as long as Member ensures free, unfiltered and high quality connectivity to those prefixes.
- IPv4 and IPv6 address prefixes assigned to GLV-IX must not be advertised to other networks without the explicit permission of GLV-IX operator.
- Member provides GLV-IX operator their AS-SET name (or AS number in case of only single origin AS) that will be announced to GLV-IX Route Servers.
- GLV-IX Route Severs will filter prefixes based on AS-SET, RIPE, IRRDB and RPKI databases and perform additional sanity checks. Member is responsible for maintaining their records in respective databases.