NM Interoperability Technical Exchange Session 3: Emerging Technologies Dr. Stephen Bush, GE Research Mr. Morris Hornik, DoD CIO

Topics of Interest SDN and applications Security Emerging Technologies Cloud Networks Tactical/waveforms Security Emerging Technologies

Supply-Chain counter-fitting – HW and SW lineage Architectures need to account for emerging technologies, and should be the baseline for how things are engineered, deployed, maintained and managed. SDN Architectures Supply-Chain counter-fitting – HW and SW lineage Commercial vs DoD Financial industry has tighter security relationships/architectures to protect financial networks

SDN can establish coalition networks Better provisioning DRS built software routers, used in Blue-Force tracking network SDN in tactical Benefits – dumb, small devices: size, weight and power Disadvantages – vulnerability, management complexity Challenges – do we know if the network is doing what it is supposed to be doing? Diversity and redundancy – how critical is it in the tactical – increases footprint, power, vulnerability (space shuttle example of 5 identical processors) Opinion – SDN is premature Recommend early investigation, testing to understand how SDN is applied, verified and secured

Good about SDN Understanding Risk Defining Cost Evolution on how networking and NM is done Retooling of staff Size, weight and power May need new tools/languages to enable humans effectively manage Understanding Risk Defining Cost

Standards and enforcement of standards Trusted Platform Spec Cognitive Radios Is SDN an enabler of cognitive networking? Evolved Packet Core Standards and enforcement of standards Trusted Platform Spec Reference Implementation Helps with interpretations of specifications Need to make specs

How many times has a packet been access/encrypted How many times has a packet been access/encrypted? A ‘smart’ packet with code running may capture access/modification info. SDN and MANET Content-Aware routing MPLS and SDN? SDN is not able to control network interface? SDN may not scale? Networked Soldier Avoid information overload Automated decision making for data flow Attractive target ‘big data’ problem QOS and QOE are important

Company called Embrane Policy based management How smart should the network be to keep things simple for the networked soldier Company called Embrane Evolution of SDN, new capabilities Policy based management SDN and other IT Drivers Analytics and Business Intelligence Big Data Driven by need to rationalize IT costs, handling massive data volumes, mobile operations

Volumes of data /Cloud/Data Processing & Filtering/ Data Shaping are now needed for DoD – 100G transport Patterns (data that is compressible also lends to better analysis) Agile, localized standards (vice enterprise-wide standards) may be more effective and timely Is this risky? Customers willing to give data? Interactions/interfaces can evolve (instead of designing/specifying it completely upfront) Smarts centralized initially, but pushed out (decentralized) over time Instead of grand network solution that does everything, let the components do what they need to do, their way; but a centralized solution that pulls it all together to work with independent components

Decentralized mgmt pitfalls Too many data interfaces/relationships to manage Trouble-shooting is not trivial Knowing your network and knowing what ‘normal’ is Deception Techniques that will make our networks safer What can we do to make enemies see our network differently than what it is+ What is the value of doing this? CS and Neuroscience – biological system is compromised – risk management is more crucial