Re: [Idr] [GROW] draft-snijders-idr-shutdown-00: Drop a line in the peer's syslog at shutdown

[Robert Raszuk <[e-mail]>]

Nick,

Those who do not automate may not even look at the syslog at all. I  those
cases as Jared said adding it to sh bgp neig may help with the risk of
having the screen scraping parsers broken.

As to what's the point of this discussion ... is to not change format of
NOTFICATION as per 4271 yet define someting even if not structured to be
machine readable.

Thx
R.

On Nov 20, 2016 6:58 AM, "Nick Hilliard" <[e-mail]> wrote:

> Neil J. McRae wrote:
> > I just wish I thought we had the luxury of lazy operations like this!
>
> to clarify my previous email, it's a matter of simple economics:
> automation needs scale to work properly, and in particular, bgp session
> management automation only makes sense for a relatively small number of
> networks worldwide because the cost*risk to return ratio is wrong in
> most cases.  This is particularly the case because of poor availability
> of good tooling.
>
> Regarding the I-D, there are ~55000 asns visible in the dfz, of which
> ~6000-7000 are non-leaf, and probably less than a thousand where bgp
> session automation makes financial sense.  No doubt, as5400/2856 would
> be in the top bracket of these and it would make sense for your tooling
> teams to automate the hell out of nearly everything, which would
> militate against accepting free-form advisory shutdown notices like this
> - but then again, BT is atypical in the general scheme of things.
> Whether you like it or not, the long tail of ASNs would benefit from a
> simple mechanism of this form.
>
> Nick
>
> _______________________________________________
> Idr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/idr
>