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-e... (^ 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