[188576] in North American Network Operators' Group
Re: Best practices for sending network maintenance notifications
daemon@ATHENA.MIT.EDU (Hal Ponton)
Wed Apr 6 15:05:20 2016
X-Original-To: nanog@nanog.org
From: Hal Ponton <hal@buzcom.net>
In-Reply-To: <alpine.BSF.2.00.1604061144160.78400@prime.gushi.org>
Date: Wed, 6 Apr 2016 20:05:14 +0100
To: "Dan Mahoney, System Admin" <danm@prime.gushi.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
I think there was a BCP being worked on. I seem to recall it was being discu=
ssed as a Facebook group. But there's no RFC, at least that I know of.
Regards,
Hal Ponton
Senior Network Engineer
Buzcom / FibreWiFi
Tel: 07429 979 217
Email: hal@buzcom.net
> On 6 Apr 2016, at 19:56, Dan Mahoney, System Admin <danm@prime.gushi.org> w=
rote:
>=20
> All,
>=20
> We recently, at $dayjob, had one of our peers (at Symantec) send out a ne=
twork maint notification, putting 70 addresses in the "To:" field, rather th=
an using BCC or the exchange's mailing list.
>=20
> Naturally, when you mail 30 addresses, of the forms peering@ and noc@ vari=
ous organizations, you're likely to hit at least a few autoresponders and ti=
cket systems...
>=20
> And at least one or two of those autoresponders are of course brainded and=
configured to reply-all. (In this case, Verizon's ServiceNow setup was suc=
h a stupid responder). And that made things fun in our own ticket system, a=
s our RT setup happily created a bunch of tickets.
>=20
> My question for the group -- does anyone know if there's a "best practices=
" for sending maint notifications like this? An RFC sort of thing?
>=20
> While it would define a social protocol, rather than a truly technical one=
, if there's not such a document, it seems like it could useful. And once s=
uch a thing exists, exchanges could of course helpfully point their members A=
T it (for both their humans, and ticket systems, to follow).
>=20
> -Dan
>=20
> --=20
>=20
