I mentioned in my previous post that one of the things that struck me at this year’s Future:NET, in part because of how powerfully simply it was stated, is that networks are all about policy and availability. Note that this is different than the split between connectivity and security, because routing policy isn’t always about security, and availability has to be about more than just connectivity. We covered the policy part in some detail in that last post, but what happens when you combine the two? What is the result of having a single policy, available everywhere you operate?

Chris Grundemann - Headshot

Chris Grundemann

Creative BizTech & TechBiz Consultant

By submitting my data I agree to be contacted