[179928] in North American Network Operators' Group
Re: Is anyone working on an RFC for standardized maintenance
daemon@ATHENA.MIT.EDU (Bill Woodcock)
Thu May 14 07:55:51 2015
X-Original-To: nanog@nanog.org
From: "Bill Woodcock" <woody@pch.net>
In-Reply-To: <555219EA.1080004@direcpath.com>
Date: Thu, 14 May 2015 13:53:40 +0200
To: Robert Drake <rdrake@direcpath.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Whoo... Yeah, we had a WG on that, back around 2000 or so... The determina=
tion was, as I recall, that it didn't need to be part of SNMP, but it kind o=
f went off the rails in an all-things-to-all-people sort of way. But my mem=
ory is vague. Erik Guttman might remember more clearly. =20
Anyway, the idea is a good one, and if you can keep it constrained to a reas=
onable scope, I think you should find good support.=20
=20
-Bill
> On May 14, 2015, at 06:10, Robert Drake <rdrake@direcpath.com> wrote:
>=20
> Like the "Automated Copyright Notice System" (http://www.acns.net/spec.htm=
l) except I don't think they went through any official standards body beside=
s their own MPAA, or whatever.
>=20
> I get circuits from several vendors and get maintenance notifications from=
them all the time. Each has a different format and each supplies different=
details for their maintenance. Most of the time there are core things that=
everyone wants and it would be nice if it were automatically readable so au=
tomation could be performed (i.e., our NOC gets the email into our ticketing=
system. It is recognized as being part of an existing maintenance due to ma=
intenance id# (or new, whatever) and fields are automatically populated or u=
pdated accordingly.
>=20
> If you're uncomfortable with the phrase "automatically populated according=
ly" for security reasons then you can replace that with "NOC technician veri=
fies all fields are correct and hits update ticket." or whatever.
>=20
> The main fields I think you would need:
>=20
> 1. Company Name
> 2. Maintenance ID
> 3. Start Date
> 4. Expected length
> 5. Circuits impacted (if known or applicable)
> 6. Description/Scope of Work (free form)
> 7. Ticket Number
> 8. Contact
>=20
