[174795] in North American Network Operators' Group

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

Re: AWS EC2 us-west-2 reboot

daemon@ATHENA.MIT.EDU (Jared Mauch)
Wed Oct 1 17:19:48 2014

X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAB2RJyh+SzH2sdLeST3CoZ48-U-ZKon-vNa_aQ+dfFj1q+jNUQ@mail.gmail.com>
Date: Wed, 1 Oct 2014 17:18:49 -0400
To: Todd Underwood <toddunder@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org


> On Oct 1, 2014, at 4:59 PM, Todd Underwood <toddunder@gmail.com> =
wrote:
>=20
> this is kind of incident handling 101 and shouldn't be surprising to =
anyone.

There=E2=80=99s always people who feel =E2=80=9Cleft out of the loop=E2=80=
=9D when these things occur.  I=E2=80=99ve found
there=E2=80=99s no one location for centralized data after many years of =
doing this from the
ASN.1/ILMI days to present.  It requires being professional and engaging =
when most people
just want to consume the derived data.

Having found a few of these issues myself over the years, the best bugs =
are the ones
where the advisory comes out after the fixed software is broadly =
available and
deployed.  Nothing will be perfect as people always like their legacy =
system
that requires no work, but in reality, there is no such thing.

- Jared=

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