+1 on the change Tammy AS36811 Sent from my iPhone
> On Feb 27, 2014, at 1:23, Michael Hallgren <m.hallg...@free.fr> wrote: > > Le 26/02/2014 22:10, sth...@nethelp.no a écrit : >>> We've been asked to make a change the "clear bgp neighbor" command >>> to make the neighbor or "all" argument mandatory. The root cause >>> is the severe impact of "clear bgp neighbor" and the increasing >>> accidental use of this command without a specific neighbor. >>> >>> In general, we avoid changing commands to add mandatory arguments, >>> but my feeling is that the impact and severity of this specific >>> command makes this an acceptable occasion for such a change. >>> >>> I'm looking for feedback about this change. My working assumption >>> is that "clear bgp neighbor" is a sufficiently rare command and >>> would not be used in automation/scripts, so the impact of making >>> the neighbor/all argument mandatory would be minimal. Is this >>> assumption accurate? >> For us, yes. Fully support the idea of requiring an "all" argument. > > +1 > > mh > >> Steinar Haug, AS 2116 >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > ---------- > > This email has been scanned for spam and viruses by Proofpoint Essentials > cloud email security - visit the following URL to report this email as spam: > https://us1.proofpointessentials.com/index01.php?mod_id&mod_option=logitem&mid=6372874&rid=1312411&report=1 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp