RTBH Support Across the Industry

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============5822504507320113680==
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg=pgp-sha512;
 boundary="------d8296c11139ee76c8e0288bd84fd052898ec5620f6d373157d852eb4030956d1";
 charset=utf-8

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------d8296c11139ee76c8e0288bd84fd052898ec5620f6d373157d852eb4030956d1
Content-Type: multipart/mixed;boundary=---------------------5b64c785fb86c41d2f2b6bb82a5d9e93

-----------------------5b64c785fb86c41d2f2b6bb82a5d9e93
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

Dear Community,

RTBH is not as effective as it could be, for various reason, just a few in=
clude:

* 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 sh=
ould / shouldn't use RTBH.

To this end, below is the first of two surveys. This first one is quantita=
tive and captures how networks have implemented RTBH and provides (1) a pu=
blic 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 impl=
ementations across the industry.

Please take the time to fill out the short survey for your own network (ev=
en if you don't support RTBH!), and if you can, please fill it out for oth=
er networks where you know how they have implemented RTBH (e.g., peers you=
 use RTBH with): https://docs.google.com/forms/d/e/1FAIpQLScg2Bvr_14onOtZR=
doK2SNd0kCHFtqsdw-elsO5miUAO-3zzg/viewform

(^ 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.githu=
b.io/rtbh/

The second survey will be qualitative, to gather information from the indu=
stry 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 c=
ommunity effort to improve RTBH alignment across the industry and improve =
it's effectiveness for all (e.g. maybe 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 abo=
ut the status quo and review that data to get a baseline of where we are a=
t today).

Any questions, please let me know, and thank you for your time and help, i=
t is appreciated.

With kind regards,
James
-----------------------5b64c785fb86c41d2f2b6bb82a5d9e93--

--------d8296c11139ee76c8e0288bd84fd052898ec5620f6d373157d852eb4030956d1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsG5BAEBCgBtBYJqZwttCRCoEx+igX+A+0UUAAAAAAAcACBzYWx0QG5vdGF0
aW9ucy5vcGVucGdwanMub3JnC2GDLbDDCBxr+rRkwF03VmoIAX2wpYqgn6HL
1LJ+jc4WIQQ+k2NZBObfK8Tl7sKoEx+igX+A+wAAkOQQAKGu5PnbdmK6tpZO
k2ncip9lkS5jtXAlOJEAoBnsN2pF+qJSPh0oIHFVJeqxuPs/3/vqmkTxiZD1
FsofBiLWg6V96l/69M3BClzbZeiuZvyRekH4qlQYZBMSiJ/Xe+cK57mWBiSr
BJsik5cjwf6MFk7TGnHRT+XuLiCym65H4L1BUKssun9zqtKcYdC9EAc2mUoa
wQVBIBVOIpTI+dKls9zV5/cAHP3IOnCkba14nV82cD13h5SPLtCvKvGgzjpu
30ztqlZfW4vi+p6gqna0wiGz1IIWpztYN+setmxvC7BYShswjZQvATU2jiSb
9FEcXaFkcHe3Wr9xLSwqW9E0uiGxN0Tm68YYBv1o2Eq2GeoHBSKdc0XjaLeX
aYG7Z/klOTKNVH/OZI4Z8B2hzs9S/YBo1WE5lvych3L7VRn5NURtzuO/REXg
pOao0Nn9BZIIL1SzACLjZ2azrReRi9F6hEpW8fB1tulak9C5EyGX5cNRFgTS
SjdVM92AfFINwnG6vj0vHQLz05wST/lU76v0YuCCb6F7xVmsOdZ5DywRFC0h
5fH1kKNjnoh6E9KpDJ+J2d8zupLL93JvX+wHzHiSRCwULD4fZf1bUZKUsXq6
k7WmBRPDcZlujpAftzc8I9ReWs1Wxwoml3y0Nj1YpCOnWaDndVT8g+pEILfE
ZereWiap
=je2x
-----END PGP SIGNATURE-----


--------d8296c11139ee76c8e0288bd84fd052898ec5620f6d373157d852eb4030956d1--


--===============5822504507320113680==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/[email protected]/message/LOWUU7RHOKTYKVGWRHNXQJ3GSJYN3HLE/
--===============5822504507320113680==--