At the root of John Boyd’s “OODA loop” methodology, there is the notion that we need to acknowledge and work with levels of “uncertainty”—gaps that result when applying established models to new and changing contexts[i]. Unfortunately, the networking community—desperate for operational stability—largely ignores these mismatches, designing network and security architectures as if they can dictate how applications are deployed.
What’s the next digital frontier? It’s Digital Cohesion, a future in which applications we use often self-assemble to deliver compelling mega services that enhance our lives. Today, if I need a ride to the airport I might order a ride on Uber. Or if I want dinner delivered to my home I might order a meal through doordash. In doing so, I am using applications manually. In the future, these services will act autonomously, and deploy based on my situation, need, and location, as well as my history and feedback from other services or devices I’ve used. I will no longer need to call such services, as they will automatically appear and serve when needed.
Few who have watched the film of the same name will forget the compelling scene towards the end where the group of captured slaves are asked to identify Spartacus from amongst them and one by one they memorably stand to each proclaim ’I’m Spartacus.’
Bear with me as I somewhat tenuously (for now) draw a parallel between that scene and the claims and cries of IT and Networking vendors as they all clamour to shout ‘I’m Open’
It seems as though ever since I was a young lad, vendors in the IT community have positioned themselves as “open”. It could be argued of course that no one would ever claim they are closed and proprietary so the word open became almost the default or ‘safe harbour’ position.