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

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

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

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

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

I'd argue that, even when someone has no interest to use the Shutdown Communications sent by others, they can benefit and save time by using the feature to inform their customers or peers of shutdown reasons. Sending and receiving are two separate considerations. Kind regards, Job > On 19

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

Neil J. McRae wrote: > I just wish I thought we had the luxury of lazy operations like this! there are more places in heaven and earth, Neil, including many places where automation makes no sense and many other places where unstructured text would be a useful tool in the operator's box. Just

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

On Sat, Nov 19, 2016 at 05:23:15PM +, Neil J. McRae wrote: > It's a wonderfully useless solution when it could be a wonderfully > useful solution - it's just more operational noise that we already > have and we will start filtering like everything else. What's really useless is hyperbole

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

It's a wonderfully useless solution when it could be a wonderfully useful solution - it's just more operational noise that we already have and we will start filtering like everything else. Neil. > On 19 Nov 2016, at 16:58, Marco Marzetti wrote: > > Robert, > > This is

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

Robert, This is a wonderful easy to use solution to send informational messages to your neighbor for a very specific case (sesssion shutdown) It is so easy that i wonder why we're discussing for so lo long. Changing operational patterns or having well-formatted messages is out of the scope and

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

On Sat, Nov 19, 2016 at 05:07:50PM +0100, Robert Raszuk wrote: > If you think this is too much then let's support new message type (for > example Advisory) which will be able to be sent ahead of planned admin > shutdown with all details necessary and be done. "Shutdown" and "advisory"-style

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

> On Nov 19, 2016, at 10:10 AM, Robert Raszuk wrote: > > > Leave alone that this all makes sense to be sent well before the planned > admin shutdown so the other side is first aware of it and can manually or > automatically take users off that peering. > > But looks like

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

Leave alone that this all makes sense to be sent well before the planned admin shutdown so the other side is first aware of it and can manually or automatically take users off that peering. But looks like we are light years away from such basic thing here On Sat, Nov 19, 2016 at 3:59 PM,

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

> On Nov 19, 2016, at 9:59 AM, Neil J. McRae wrote: > > We shouldn't be encouraging folks to build networks that for routine events > we then require more manual intervention when it's unwarranted. > > Why does it need to be free format? Part of the motivation I had for

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

We shouldn't be encouraging folks to build networks that for routine events we then require more manual intervention when it's unwarranted. Why does it need to be free format? How many reasons or signals does one need to send in a message like this? Just thinking whilst I wait for the till to

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

Robert Raszuk wrote: > Just to be clear: I am also OK with free form text with the few well > known and easy to machine parse keywords (in it). the field should either be fully structured or free-form, and the explicit intent of this draft is free form, utf8. Having a half-way house is in

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

Marco, Just to be clear: I am also OK with free form text with the few well known and easy to machine parse keywords (in it). Of course provided that we either forget about new length field in subcode 2 which would update 4271 or we do it in new subcode all together. Thx, R. On Sat, Nov 19,

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

Robert, So you're suggesting to include recommendation for the formatting? That could help (as long as it's not mandatory). Regards On Sat, Nov 19, 2016 at 2:51 PM, Neil J. McRae wrote: > I personally think this is a really bad idea but understand why some might > want this

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

I personally think this is a really bad idea but understand why some might want this - and we've had similar drafts in the past- in my view we shouldn't be moving more towards more human related randomness in system level messages - have a set of status numbers or something that can be

Re: [GROW] Fw: New Version Notification for draft-sriram-opsec-urpf-improvements-00.txt

Siriam, I wasn't at the meeting, so pardon me if you've already discussed that there. So you are suggesting that every customers can send packets that other customer's IPs in the source field? Is that correct? Anyway: Have you considered the additional burden on routers to handle that? And what

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

On Fri, Nov 18, 2016 at 08:01:30PM +, Jakob Heitz (jheitz) wrote: > Not necessary. You can already send whatever you want. In iOS-XR, it just > hexdumps it all. The only thing that will change is that it will print it in > UTF8 as well. It will still hexdump. If you want no hexdump, then we