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

[Sam Silvester <[e-mail]>]

On Mon, Nov 21, 2016 at 5:04 AM, Gaurab Raj Upadhaya <[e-mail]>
wrote:

> On 11/19/16 9:58 PM, Nick Hilliard wrote:
> > 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.
>

I completely agree with this also. It's a no-brainer to me, I would love
this functionality and I can think of plenty of times on both a sending and
receiving end that this would have been a nice to have thing.


> that sums it up neatly for me. I also think that adding complexity in
> the free form at this stage may limit implementation and the numerous
> ways in which it can be used for automation.
>

I would also recommend no explicit or suggested terms are added in the ID.
Leave it open ended and see how it goes. At the end of the day, it
shouldn't matter to those implementing BGP speaker software, so why mention
it at all in the ID?

I support this proposal, would love to see it make it out the door in terms
of shipping code.

Regards,

Sam