<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style></style></head><body lang=DE link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1>Hi Erik,<o:p></o:p><o:p> </o:p>This is a vital topic! You focused a bit on the Dutch community. However, I think it is globally significant.<o:p></o:p><o:p> </o:p>We at DE-CIX are very active in reacting to abusive peers on our IXPs. We have disconnected peers who were (repeatedly) not obeying the law or the DE-CIX Terms and Conditions. I gave a talk about what DE-CIX does in this regard during RIPE75 (<a href="https://ripe75.ripe.net/archives/video/103/">https://ripe75.ripe.net/archives/video/103/</a>).<o:p></o:p><o:p> </o:p>Disclaimer: I am not a lawyer.<o:p></o:p><o:p> </o:p>The European telecommunication law does not allow IXPs to look into peers' traffic on the application level (for a good reason, I believe). So, we do not know if a peer hosts malware or is sending out spam only. DE-CIX is only allowed to look into the operational data (e.g., Route or ASN hijacks) or behavior (e.g., unwanted traffic due to static routes on the Peering LAN). Based on this information, DE-CIX is acting.<o:p></o:p><o:p> </o:p>I am highlighting this because I see issues if IXPs (or carriers and transit providers) are used as central infrastructure to filter data due to information they cannot verify or generate. Just think about the central DNS filtering and censoring discussion we had on a European level to stop certain abusive and harmful Internet services from being accessible.<o:p></o:p><o:p> </o:p>Best regards,<o:p></o:p>Thomas<o:p></o:p><o:p> </o:p>-- <o:p></o:p>Dr. Thomas King<o:p></o:p>Chief Technology Officer (CTO)<o:p></o:p><o:p> </o:p>DE-CIX Management GmbH | Lindleystraße 12 | 60314 Frankfurt am Main | Germany | <a href="http://www.de-cix.net">www.de-cix.net</a> |<o:p></o:p>Phone +49 69 1730902 87 | Mobile +49 175 1161428 | Fax +49 69 4056 2716 | <a href="mailto:thomas.king@de-cix.net">thomas.king@de-cix.net</a> |<o:p></o:p>Geschaeftsfuehrer Harald A. Summa and Sebastian Seifert | Registergericht AG Koeln HRB 51135<o:p></o:p><o:p> </o:p>DE-CIX 25th anniversary: Without you the Internet would not be the same!<o:p></o:p>Join us on the journey at <a href="https://withoutyou.de-cix.net">https://withoutyou.de-cix.net</a><o:p></o:p><o:p> </o:p><o:p> </o:p><o:p> </o:p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'>From: connect-wg <<a href="mailto:connect-wg-bounces@ripe.net">connect-wg-bounces@ripe.net</a>> On Behalf Of Erik Bais Sent: Tuesday, 18 May 2021 21:52 To: <a href="mailto:connect-wg@ripe.net">connect-wg@ripe.net</a>; <a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a> Subject: [connect-wg] Input request for system on how to approach abuse filtering on Route Servers - bad hosters<o:p></o:p></div></div><o:p> </o:p>Hi, <o:p></o:p><o:p> </o:p>As I asked during the Connect WG today, there are discussions currently going on in the Dutch network community to see if there is a way to get a cleaner feed from routeservers on internet exchanges. ( by default ) <o:p></o:p><o:p> </o:p>As you may know there is an Dutch Anti Abuse Network initiative ( AAN ) – abuse.nl <o:p></o:p><o:p> </o:p>The companies associated with AAN setup and all signed a manifest ( in Dutch - <a href="https://www.abuse.nl/manifest/">https://www.abuse.nl/manifest/</a> ) that states that we will all do our best to provide a better and cleaner internet. <o:p></o:p><o:p> </o:p>As members of the member organisation of the largest Internet Exchange, AMS-IX, we like to start with the discussion on asking the AMS-IX to filter certain AS numbers from the default routeserver view. <o:p></o:p>The issue is that even if you don’t peer with certain networks directly, the change is very real that you will receive or that the other network receive your prefixes and that you may not want to peer with those networks. <o:p></o:p><o:p> </o:p>What we like to have is an independent way of generating a list with badhosts ( say a top 50 ) .. ( and with our Dutch infrastructure we have a couple on the Dutch infrastructure as well.. ) <o:p></o:p><o:p> </o:p>A couple years ago there was the list of HostExploit .. or one could have a look at the drop-list of SH .. <o:p></o:p>Personally I would like a proper model that one can explain why a certain network is listed on a certain list with a clear method explaining of what kind of abuse is noted in the said network. <o:p></o:p><o:p> </o:p>Topics that should be included on the rating for the list : <o:p></o:p><o:p> </o:p><ul style='margin-top:0cm' type=disc><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'>Phishing (hosting sites / domain registrations ) <o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'>Malware hosting ( binaries and C&C’s ) <o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'>DDOS traffic ( number of amplification devices in the network compared to the number of IP address ratio )<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'>Login attacks / excessive port scanning <o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'>Hosting of Child exploitation content <o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'>Infected websites / Zeus Botnets <o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'>Etc<o:p></o:p></li></ul><o:p> </o:p>So yeah, something similar as the Top 50 of HostExploit ranking .. but HostExploit stopped producing these lists in 2014. <o:p></o:p><o:p> </o:p>By filtering a top 50 of badness hosters on the Routeservers would remove the cheap IXP option for network connectivity at the better Internet Exchanges and provide a way to remove any DDOS traffic via BGP null-routing via Transits.<o:p></o:p>And companies that would still want to peer with a certain network, can still do so by direct peering setup via the IXP infra. <o:p></o:p><o:p> </o:p>And it will not bring the IXP in a position where it will be asked on why they are still offering services to certain parties .. as that might become legally difficult especially in a membership organisation. <o:p></o:p><o:p> </o:p>So we don’t mind if we take their money as long as are not forced to peer with them via the routeservers. <o:p></o:p><o:p> </o:p>Your constructive feedback is highly appreciated. <o:p></o:p><o:p> </o:p>Regards,<o:p></o:p>Erik Bais<o:p></o:p>A2B Internet <o:p></o:p><o:p> </o:p></div></body></html>