Profile |  Login

Technical Requirements for Interconnection

 

This document lists the common technical requirements for interconnection between two networks, that have agreed to interconnect. The document covers both Public Interconnection over an Internet Exchange Point, and Private Interconnections. Private interconnection, also referred to as PNIs, are direct point to point circuit between two end networks setup for the purpose of exchanging traffic. 

Ethernet is the most common method for both Public and Private Interconnection today (in 2019), and the Layer 2 part of this document is based on it. Additionally, IXPs requirements for their participants are detailed separately in Euro-IX BCP 1, and only a sub-set applicable to private interconnects is covered in this document. 

The layer 3 part of the document focuses on IP version 4 (IPv4) and IP version 6 (IPv6) unicast traffic, as the most common type of traffic exchanged today. The document doesn’t cover Multicast traffic exchange.

 

Physical Connection


Ethernet MAC Layer

0x0800 – IPv4

0x0806 – ARP

0x86dd – IPv6

ARP

IPv6 Neighbour solicitations and advertisements
 

Examples of other link-local protocols are: IRDP, ICMP redirects, IEEE802 Spanning Tree, Vendor proprietary discovery protocols (e.g. CDP, EDP), Interior routing protocol broadcasts (e.g. OSPF, ISIS, IGRP, EIGRP), BOOTP/DHCP, PIM-SM, PIM-DM, DVMRP. These should be disabled on the interconnection facing interfaces. 

 

IP Address

Private interconnection is recommended to use /31 or /30 for IPv4 link-local addresses, and /127 or /64 for IPv6 link-local addresses. IPv6 site-local addresses shall not be used. rDNS should be configured with mutual agreement. 

 

Routing

 

Forwarding Requirements:

Traffic on interconnection interfaces shall forwarded only to routes being advertised across the interconnection. Any kind of static shouldn’t be done. 

 

Looking Glass and non-routing devices: 

When a BGP speaker is collecting routing information for analysis and not for immediate routing decisions, the BGP speaker may use a private AS number and should not advertise any routes.

 

Optional Requirements: 

These are evolving requirements, and may be required by some peers, and will be increasingly more important in coming years.