[190843] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Cloudflare, dirty networks and politricks

daemon@ATHENA.MIT.EDU (TR Shaw)
Thu Jul 28 19:50:37 2016

X-Original-To: nanog@nanog.org
From: TR Shaw <tshaw@oitc.com>
In-Reply-To: <28E6FC71-F6FF-49B9-B861-3B573372594F@f5.com>
Date: Thu, 28 Jul 2016 19:45:14 -0400
To: Donn Lasher <D.Lasher@f5.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org


> On Jul 28, 2016, at 7:30 PM, Donn Lasher via NANOG <nanog@nanog.org> =
wrote:
>=20
> On 7/28/16, 10:17 AM, "NANOG on behalf of J. Oquendo" =
<nanog-bounces@nanog.org on behalf of joquendo@e-fensive.net> wrote:
>=20
>=20
>> While many are chanting: #NetworkLivesMatter, I have yet
>> to see, read, or hear about any network provider being
>> the first to set precedence by either de-peering, or
>> blocking traffic from Cloudflare. There is a lot of
>> keyboard posturing: "I am mad and I am not going to take
>> it anymore" hooplah but no one is lifting a finger to
>> do anything other than regurgitate "I am mad... This is
>> criminal."
>=20
> (long discussion, was waiting for a place to jump in..)
>=20
> If we want to be accurate about it, Cloudflare doesn=E2=80=99t host =
the DDoS, they protect the website of seller of the product. We =
shouldn=E2=80=99t be de-peering Cloud Flare over sites they protect any =
more than we would de-peer GoDaddy over sites they host, some of which, =
no doubt, sell gray/black market/illegal items/services.
>=20
> If, on the other hand,  you can find a specific network actually =
generating the volumes of DDoS, you should have a conversation about =
de-peering=E2=80=A6.
>=20
> $0.02=E2=80=A6
>=20

It would be nice however if Cloudflare would announce there =
=E2=80=9Cfreebie=E2=80=9D ciders and the IP block that host their paying =
customers. Most of the abuse centers on the free clients.


home help back first fref pref prev next nref lref last post