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

[Job Snijders <[e-mail]>]

Hi Neil,

On Sat, Nov 19, 2016 at 02:17:14PM +0000, Neil J. McRae wrote:
> Free form is inefficient and will drive less useful outcomes. 
> 
> This becomes bloat because immediately I add to my peering policy that
> we will ignore all of these messages because I can't trigger action on
> them -  any message from the network I want to be able to automate
> something from it like an icon on a NOC display or other notification
> -perhaps that auto looks up the NOC phone number (although that's not
> likely these days!), search the recent emails from that AS; gets the
> peering DB record for that AS or a message that says ignore this cease
> for quantum X - 
> 
> Let's not even start about the language challenges this would present.
> Or the sales droids 1-800-Cheap-transit ;) 

You are free to ignore the free form Shutdown Communication, it is your
network. Your choice does not mean that the shutdown communication tool
should not exist for others who do want to use it.

Different networks are at different levels of automation, some might get
there and require more advanced tools, some don't. I dont think the
language challenges are real, with each of your BGP neighbors you'll
already have an agreement what the preferred language for communication
is. If you receive spam in the 128 octets of the Shutdown Communication,
you can consider shutting down the session on your side too.

Job