As the world waits for the introduction of 5G networks, the industry gears up to address the security challenges that may accompany 5G. The 5G networks would essentially promote the use of a huge number of interconnected devices, a tremendous increase in bandwidth, and collaborative functioning of legacy and new access technologies. Undoubtedly, the upcoming 5G environment would demand the deployment of additional security mechanisms to ensure business continuity. 5G systems are meant to be service-oriented, which is why it is important to address the security challenges appropriately and to focus on instilling stronger security and privacy settings in 5G networks.
There is a great scene in the movie Victor, Victoria, where the character played by James Garner decides it’s time to mix things up a bit. So, he strolls into an old gritty bar wearing a tuxedo, walks up to the bartender, and orders milk. Within minutes, the other men in the bar decide they’ve had enough of this, and they start an intense bar fight. Garner is soon throwing and taking punches, getting tossed across the floor, and loving every minute of it.
Software-defined networking (SDN) started out as an architecture for solving the inefficiencies of Layer 2/3 networks. SDN initially neglected the rest of the Open Systems Interconnection (OSI) stack, but that should change quickly as application delivery controllers (ADCs) and other network services expand their involvement in the SDN industry.
Over the past several years, server virtualization has led to consolidation of physical server resources to reduce cost and enable flexibility by allowing applications to be virtualized and distributed.
A similar trend is underway for networks – traditional networks are now becoming more dynamic to lower cost and reduce vendor lock-in. The two key efforts of note: Software Defined Networking (SDN), which brings standardization through APIs, and Network Function Virtualization (NFV) that allows operators to quickly enable value-added services. The NFV initiative is highly complementary to SDN.
Software Defined Networking (SDN) is a hot topic for carriers and most service providers are somewhere in the process of figuring out how to take advantage of this technology. SDN’s design can help to overcome the network challenges that accompanied the explosive growth of video, mobility and cloud services. Major Tier 1 telecoms across the globe are already implementing capabilities to reduce costs and add more flexibly to their managed services.
Gartner has recently released their application delivery controller (ADC) magic quadrant for 2015.* The Magic Quadrant shows that the landscape for ADC vendors continues to change as complimentary differentiating technologies become an essential part of the ADC solution profile. To understand why the ADC Magic Quadrant is still relevant, it is important to know how the ADC landscape has evolved to where we are today.
Jim Metzler is a Distinguished Research Fellow and Co-Founder of Ashton Metzler & Associates and is a featured guest blogger.
Many people associate NFV exclusively with service providers. That’s understandable because the organizations that are most closely associated with the definition and development of NFV, such as the European Telecommunications Standards Institute (ETSI) and the TM Forum, focus almost exclusively on service providers. The service provider orientation of these organizations shows up in all of their documents.
Last week I spent a few days in sunny (and crowded) San Jose, California at the NFV World Forum. The theme this year was largely about open environments and interoperability, ushered on by the standardization efforts behind NFV, along with the related topics of carrier-grade service assurance and reliability. I was fortunate to speak about how Radware is actively investing in open environments as the architecture becomes common platforms for commercial implementations. Radware is implementing SDN and NFV in network security and application delivery domains to help service providers achieve radical cost reduction while benefitting from the advantages of cloud-based application services.
A couple of years ago the discussion of SDN focused primarily on the fact that SDN separated the network control function from the network forwarding function and that separation of functions might require the introduction of new protocols such as OpenFlow. More recently there has been a lot of discussion about the value of an overlay SDN model vs. an underlay SDN model and the role of specialized hardware in either model. All of these discussions are important and they all are focused on key architectural characteristics of SDN.
Jim Frey is Vice President of Research, Network Management for Enterprise Management Associates (EMA) and is a featured guest blogger.
Network functions virtualization (NFV) is one of the best-accepted and most-understood spinoffs of the SDN craze that has taken root over the past few years. The concept is straightforward: take features and capabilities that are typically implemented in the network and repackage them in forms that can be invoked automatically, without requiring the deployment of new hardware.