On Dec 28, 2016, at 5:34 PM, Randy Bush wrote:
>> An alternative multi-vendor approach is to use 1 vendor per stack layer,
>> but alternate layer to layer. That is; Vendor A edge router, Vendor B
>> firewall, Vendor A/C switches, Vendor D anti-SPAM software, etc. This
>> doesn't address the bug i
> An alternative multi-vendor approach is to use 1 vendor per stack layer,
> but alternate layer to layer. That is; Vendor A edge router, Vendor B
> firewall, Vendor A/C switches, Vendor D anti-SPAM software, etc. This
> doesn't address the bug impact issue as well as it alleviates the vendor
> "ow
On Wed, Dec 28, 2016 at 1:39 PM, Chris Grundemann
wrote:
> On Tue, Dec 27, 2016 at 3:10 PM, Leo Bicknell wrote:
>
> > 2 Vendor
> >
> > Can be implemented multiple ways, for instance 1 vendor per site
> > alternating sites, or gear deployed in pairs with one from each vendor
> > up and down the s
On Tue, Dec 27, 2016 at 3:10 PM, Leo Bicknell wrote:
> 2 Vendor
>
> Can be implemented multiple ways, for instance 1 vendor per site
> alternating sites, or gear deployed in pairs with one from each vendor
> up and down the stack.
>
An alternative multi-vendor approach is to use 1 vendor per sta
Over the holiday I am taking the opportunity to catch up on some editing.
This session, from October, is a series of very informative presentations
on the latest in network security practice and IPv6 deployment. I'm afraid
the 3rd presentation is in Romanian, but the slides are in English!
joly p
5 matches
Mail list logo
