The difference between SDN and standardization
Lori MacVittie, senior product manager of emerging technologies at F5 Networks, takes a look at which came first, SDN or standardization, on a blog on the company site. The adoption of SDN is mostly needed to address a variety of operational issues within a network. However, MacVittie explains that although standardization is key to address these issues, SDN is just one way to gain standardization.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
In fact, she writes that SDN really only helps with standardization in the upper levels of the stack. MacVittie adds a diagram explaining the functions that still need to be standardized in Layers 4 through 7, writing that there can sometimes be upward of 20 vendors present in these layers within one network. At the end of the day, bringing functions together is done through standardization -- which includes SDN as just one way that standardization can be achieved.
Check out MacVittie's full post exploring SDN and standardization in layers 4-7.
SDN and NFV growth will happen, but not right away
In a post on Adva Optical's Technically Speaking blog, communications industry analyst Gary Kim looks at SDN and network functions virtualization (NFV) and explains why the adoption of both will happen, but not overnight. As with any "open" approach, it will take time for full interoperability to occur across device and software domains, no matter how simple the approach is. Several issues are also preventing the immediate adoption of SDN, such as a lack of standards for integration, approaches that require "rip and replace," and confusion in the overlap between SDN and NFV.
In fact, Kim added that although SDN and NFV very clearly overlap, it's hard to say whether they're complimentary to one another.
Take a look at Kim's breakdown of the eventual adoption of both SDN and NFV.
Why SDN and communications are a great match
In a blog post on the No Jitter site, Eric Krapf, program and co-chair for Enterprise Connect events, looked at SDN's recent adoption in the world of communications, citing the Microsoft Lync SDN application programming interface (API) as an example of what can be done even before the full SDN architecture arrives. The benefits of SDN in communications are clear, particularly having a real-time server with the ability to influence network resource allocation to ensure quality.
He adds that Microsoft partner Aruba uses the Lync API for a more specific use case; the company uses the API to identify Lync media flows across an Aruba infrastructure. The bigger picture for SDN in communications will extend beyond Lync and will benefit communication users best when it's more commonly deployed and standards are in place, allowing it to talk to any communications server.
Check out Krapf's full outline of SDN's current role in communications.
The benefits of Hyper-V network virtualization
On the Altaro blog, which looks specifically at topics pertaining to Hyper-V and Windows administrators, Nirmal Sharma, who works as an independent systems architect, outlines eight benefits of implementing Hyper-V network virtualization.
Sharma's eight points include benefits such as "bring your own IP address," network topology, cross-subnet live migration, and easier moves of services to a cloud.
Take a look at all of Sharma's eight benefits of Hyper-V network virtualization.