Date: Thu, 28 Mar 2024 15:29:07 +0200 (SAST) Message-ID: <545350592.4349.1711632547181@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4348_324008811.1711632547180" ------=_Part_4348_324008811.1711632547180 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In line with support best operational practice, we've prepared several g= uides to assist peering participants with configuration of their peering de= vices, all of which may be found below. Please report E&O to ops = [@] inx.net.za.
There are two BGP separate route = servers on each peering LAN. It is recommended to always peer with both BGP Route Servers at a location, as sessions to both se= rvers ensure that there is no disruption to the advertisement of your prefi= xes should it be necessary to performance maintenance on a Route Server. &n= bsp;The Route Servers do no= t peer with each other by d= esign, so peering with only one server is an unnecessary risk for your netw= ork!
Each INX peering LAN has a BGP route collector. BGP peering sessio= ns on the route-collectors are done in advance of port turn-up, and set to = passive, so we will automatically respond to, and activate peering sessions= from peers. BGP prefix information gathered via this service, is mad= e available via our integrated = Looking Glass, as a diagnostic tool for the Internet community. &n= bsp;We heartily encourage all peers to peer with the route-collector at eac= h of the INXes that they are present at.
In order to help maintain hygiene across the peering fabric, all peering= participant ports are subjected to a standard layer-2 filtering policy to = limit frames that are considered unwanted at the peering fabric. Belo= w is a list of frames that are filtered (dropped) by default. This li= st is revised as necessary.
INX operates two looking glass services that provide different views of = the INXes to the public. Every INX LAN has a Route Collector that eng= ages in peering with participants on the LAN, and we are able to provide a = view of what peering looks like from the perspective of the INX Route Serve= rs as well. Both these serve useful, and yet separate purposes, and u= sers of the service are encourage to ensure that understand the differences= .
To ensure that your connection to the INX is easy, as well as secure, we= have created a set of templates for the configuration of various types of = hardware in common use at the exchange point.
Although we do filter = specific types of Layer-2 frames, we still encourage peers to keep thei= r ports clean, and may insist on this before moving you out of quarantine.<= /p>
Attacks against the routing system are increasing, and it's not uncommon= in today's Internet world to experience prefix hijacking. The IETF h= as for a while, been woking on an Internet Resource Public Key Infrastructu= re, to help validate routing (BGP) announcements.
Details on RPKI and how this works is best followed up through your RIR.= The RIPE-NCC in particular has excellent resources for you to peruse, and ano= ther excellent set of guidelines is available at https://rpki.re= adthedocs.io. INX runs separate workshops on IRR and RPKI usage, = so look out for our announcements, and join the classes.