[178359] in North American Network Operators' Group
Last-call DoS/DoS Attack BCOP
daemon@ATHENA.MIT.EDU (Yardiel D. Fuentes)
Fri Feb 27 11:28:24 2015
X-Original-To: nanog@nanog.org
From: Yardiel D. Fuentes <yardiel@gmail.com>
Date: Fri, 27 Feb 2015 11:16:15 -0500
In-Reply-To: <E62C8F63-8E44-4AA5-8009-D71F1C7DA4B2@gmail.com>
To: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Hello NANOGers,
Following up on the below effort from last year, the DDoS/DoS Attack =
BCOP Draft document is ready for the last call 2-week period. After this =
period and unless notable objections are raised, the current document =
will be ratified as such. The current document can be found in the NANOG =
BCOP site -- link to current document found below:
http://bcop.nanog.org/index.php/BCOP_Drafts
Any additional community-wide comments or feedback in order to ensure =
quality documentation are not only very welcome but encouraged.
Cheers,
Yardiel Fuentes
On Jul 2, 2014, at 6:48 PM, Yardiel D. Fuentes wrote:
>=20
>=20
> OK NANOGers,
>=20
> Some of us got the call to arms from Chris G email below and the NANOG =
BCOP Committee and now we are interested in generating DoS =
attack-related Best Common Practices (BCOP) appeal to serve the entire =
NANOG community.
>=20
> This document, as other BCOP appeals are expected to be as brief as =
possible and to the point in order to keep it practical and useful.
>=20
> The goal is to generate a set of best practices of what to do =
before/during/after a DoS/DDoS attack -- including what seems to have =
worked best and what hasn't. Time dedicated to this effort should =
extensive and participation can be non-real-time given that it can be =
done over email with no need for conference calls if desired.
>=20
> DoS and DDoS attacks have been a topic that have captured high =
interest from NANOGers based on the archived list topics and email =
threads. So, now is your time to help shape a NANOG BCOP Appeal on this =
topic.
>=20
> Please contact me off-list if you want participate by either sharing =
your experience, expertise or opinions towards generating a DoS Attack =
BCOP.
>=20
>=20
> Yardiel Fuentes
> yardiel@gmail.com
> twitter: #techguane
>=20
>=20
>=20
> On Jun 1, 2014, at 5:25 PM, Chris Grundemann wrote:
>=20
>> Hail NANOGers!
>>=20
>> As most of you hopefully know, NANOG now has a BCOP Ad Hoc Committee
>> and we are pushing forward with new BCOPs!
>> http://nanog.org/governance/bcop
>>=20
>> We currently have three BCOPs in active development:
>>=20
>> eBGP configuration, shepherd Bill Armstrong
>> Public Peering Exchange update, shepherd Shawn Hsiao
>> Ethernet OAM, shepherd Mark Calkins
>>=20
>> All three of these nascent BCOPs will be presented in the BCOP Track
>> on Monday: http://nanog.org/meetings/abstract?id=3D2348
>>=20
>> We have also collected a list of Appeals (BCOPs that need to be
>> written): http://bcop.nanog.org/index.php/Appeals
>>=20
>> If you would like to help out with any of these BCOPs (or others yet
>> to be identified) please join the BCOP mailing list and reach out to
>> the shepherd (if applicable of course):
>> http://mailman.nanog.org/mailman/listinfo/bcop
>>=20
>> Our committee is brand new and we are still finding and smoothing
>> wrinkles, etc. We would love your help in any capacity. As a BCOP
>> shepherd or SME or just to point out potential pit falls or room for
>> improvement, with the process, the wiki, a BCOP or anything at all
>> really.
>>=20
>> This is a bottom-up, community led effort and it will only succeed
>> with your help - join us in creating what I believe will be a vital
>> and long-lasting institution!
>>=20
>> Cheers,
>> ~Chris
>>=20
>> --=20
>> @ChrisGrundemann
>> http://chrisgrundemann.com
>=20
