Hi, On Thu, Jul 12, 2018 at 02:20:42AM +0300, Saku Ytti wrote: > Of course this cannot happen, because you can't just randomly kill > people new breaking default configs. Which is another issue I think > vendors should address, so that they could evolve out-of-the-box > defaults over time. I think this would be quite easily solvable, if > in configurations you could declare which standards version you want > to use, and if nothing is declared, it'll use what ever standard the > image defaults to. This way Juniper could keep introducing new > standard config versions, and people could choose to stay in any > specific standard version as long as they want. Keeping backward > compatibility while allowing more sensible defaults.
*like*
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
