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

["Neil J. McRae" <[e-mail]>]

I would be deploying automation to take care of network problems/issues/whatever whether I worked at BT or I was the admin of a network with four and a half nodes.

We have the world and his wife automating and innovating on top of -our- internet platform and we are still encouraging behaviours like it was 1992 (I'd say like mission control in the 60s but I think they had more automation back then!) 

oh well if we just want to be the dumb pipe providers! 

> On 20 Nov 2016, at 18:34, 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.
> 
> 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 see these quite similar to TXT records in DNS. and so, I do think that
> at some point after this has been implemented, we'll need to document
> widely adopted structures in a BCP.
> 
> -gaurab
> 
> 
>