On 12 Jul 2019, at 13:33, MIXP announcements wrote:

The MIXP has two route servers. When a participant peers with the route server, No traffic will be exchanged with the route servers themselves, or their ASN. They just facilitate the exchange of BGP updates.

We highly recommend that you set up session to either one

you should peer with *both*

to enable prefixes and traffic exchange from any other participant who also has a session to the route server, if your peering policy is open.

Please set up sessions to the following:

Route Server 1: ASN: 37324 IPv4 Neighbour: 196.223.0.201 IPv6 Neighbour: 2001:43f8:270:d0d0::201

Route Server 2: ASN: 37324 IPv4 Neighbour: 196.223.0.202 IPv6 Neighbour: 2001:43f8:270:d0d0::202

if you have an open peering policy - like most of you do - then this is almost a no-brainer. it means that you can get quickly and easily peered with existing and new peers that you might have missed out. which makes your peering more effective. which makes your network better. if you are super-lazy, it also means that you can then not have to worry about setting up direct bilateral sessions and filtering your peers at the MIXP, because the BGP-RS service that the IXP provides will do this. i don’t encourage that, but, i do know that this has become a trend globally..

one of the improvements that is being discussed and will likely get implemented is the ability to look into the route filtering that the BGP-RS does as well, so that you can see what is, and is not being used by your peer networks.

Route Collector ASN: 327821 IPv4: 196.223.0.199 IPv6: 2001:43f8:270:d0d0::199

For any additional support, please contact peering@mixp.org

imho, peering with the BGP-RC should be mandatory, since this is a no-risk event, to the peering network, and the debugging opportunities that it offers are fantastic! and consider that it’s also a great marketing tool; any peer that is serious about connecting to your IX, will ask for a dump of the potential routes (if they they won’t get all) and the looking glass/route collector combination is the way to get this.

here’s the looking glass now: https://lg.mixp.org. if you are one of the networks who has a BGP session down, please fix this. if you know someone who works at a network who has a session down/not advertising anything, can you have a word with them to fix this. as i explained, if you are going to be serious about improving your internet environment for investment, then it really does need to be a group effort..

also, please take a minute to check that you are registered for a peeringdb.com account, and that your network appears here, and that it is listed as a MIXP peer: https://www.peeringdb.com/ix/1508

if you have a marketing team - and you all do - then you know why marketing is necessary. well, this is *technical marketing*. that is needed when you want to speak to peering co-ordinators at other networks. i can tell you that if you don’t have an up-to-date peeringdb entry, no-one at afpif is going to want to meet with you :-)

—n.