[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Last-call DoS/DoS Attack BCOP

Subject: Last-call DoS/DoS Attack BCOP
From: jtk at cymru.com (John Kristoff)
Date: Wed, 25 Mar 2015 07:50:15 -0500
In-reply-to: <[email protected]>
References: <CAC1-dtns9BDpVCLr+jnFsaGrNAcR7pzQZFesdu2PfgjeMubMdg@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]> <20150323182142.364b56df@localhost> <[email protected]> <CAL9jLaZP5MD00cmwrS-nnVDgZ3dnCDari4AM5477Tm3rEofX4Q@mail.gmail.com> <[email protected]>

On Wed, 25 Mar 2015 08:27:14 -0400
Rob Seastrom <rs at seastrom.com> wrote:

> John's statement was in the context of general advice to be included
> in a BCOP document and I felt compelled to say "whoa there".

My intent was for it to be taken as a DDoS mitigation response option,
not as a general practice.

John

Follow-Ups:
- Last-call DoS/DoS Attack BCOP
  - From: morrowc.lists at gmail.com (Christopher Morrow)

References:
- Last-call DoS/DoS Attack BCOP
  - From: yardiel at gmail.com (Yardiel D. Fuentes)
- Last-call DoS/DoS Attack BCOP
  - From: jtk at cymru.com (John Kristoff)
- Last-call DoS/DoS Attack BCOP
  - From: rs at seastrom.com (Rob Seastrom)
- Last-call DoS/DoS Attack BCOP
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- Last-call DoS/DoS Attack BCOP
  - From: rs at seastrom.com (Rob Seastrom)

Prev by Date: Last-call DoS/DoS Attack BCOP
Next by Date: Last-call DoS/DoS Attack BCOP
Previous by thread: Last-call DoS/DoS Attack BCOP
Next by thread: Last-call DoS/DoS Attack BCOP
Index(es):
- Date
- Thread