swinog July 2026

swinog@lists.swinog.ch

2 participants
2 discussions

SwiNOG #42 - 20/21.10.2026 - Save the Date
by Simon Ryf 06 Jul '26

06 Jul '26

Dear SwiNOG community, We’re working hard to make the second event this year possible. Location: Enter Technikwelt Solothurn Timetable: 20.10 12:00 - 13:30 Lunch & Networking 20.10 13:30 - 17:30 Presentations 20.10 18:00 - 21:00 Dinner & Networking + Museum Visit — 21.10 09:00 - 12:00 Presentations 21.10 12:00 - 13:30 Lunch & Networking 21.10 16:30 - 16:00 1:1 Meetings We’re still working on the details, please allow us some more time to finalise them. Further info will be available soon - we’ll keep you posted. — 13.07.2026 Call for Papers start 20.07.2026 Registration opens 20 & 21.10.2026 Meeting Day — Please save the date. Greetings Simon SwiNOG Core Team

1 0

RTBH Support Across the Industry
by James Bensley 03 Jul '26

03 Jul '26

Dear Community, We see that RTBH is not as effective as it could be, for various reason, just a few include: * Not all networks support RTBH. * Networks that do support RTBH implement it differently to each other. * There is no one place where one can easily find the info for how to use RTBH with a given network. * Operators have different ideas about how / when / where / why someone should / shouldn’t use RTBH. To this end, we have created the first of two surveys. This first one is quantitative and captures how networks have implemented RTBH and provides (1) a public repository which anyone can use to look-up the RTBH details for their peers/upstreams, and (2) an insight into the (mis-)alignment of RTBH implementations across the industry. Please take the time to fill out the short survey for your own network (even if you don’t support RTBH!), and if you can, please fill it out for other networks where you know how they have implemented RTBH (e.g., peers you use RTBH with): https://docs.google.com/forms/d/e/1FAIpQLScg2Bvr_14onOtZRdoK2SNd0kCHFtqsdw-… (^ No login required) The data ends up in this public repository (you can of course make a pull request directly if you want): https://remotely-triggered-black-hole.github.io/rtbh/ The second survey we are working on will be qualitative, to gather information from the industry community on why you do / don’t support RTBH, when do you use it, how do you think the routing should be secured, etc. The long term goal is to use the data from both surveys as input in to a community effort to improve RTBH alignment across the industry and improve it’s effectiveness for all (e.g. maybe we produce a new BCOP for implementing RTBH, or usage guidelines for blackholing, or maybe a new RFC is required to secure the filtering; regardless, the first step is to gather data about the status quo and review that data to get a baseline of where we are at today). Any questions, please let me know, and thank you for your time and help, it is appreciated. With kind regards, James.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog July 2026