Well-known author and independent consultant Jeff Doyle joins Bill Koss of networking startup Plexxi as first time guests on the Packet Pushers podcast. Ethan Banks hosts, and Greg Ferro plays the role of in-house opinion-maker, trend-setter, and fashion icon.
What We Discuss
- Let’s define SDN (again), because the definition has been shifting around as different vendors get into the mix.
- Is Cisco’s push towards network programmability changing how customers perceive SDN?
- If SDN ends up as merely fancy change management or service provisioning, is that really disruptive?
- Assuming MPLS is overly complex for a data center deployment, does that point to an Openflow use-case?
- Why can’t the network function like the other technology in an IT department?
- There’s many pieces that must be put into place before SDN can start disrupting the status quo.
- The importance of analytics engines as arbiters between network infrastructure (here’s what I have) and applications (here’s what I need).
- What’s the relevance of legacy protocols like BGP and OSPF if we’re trying to reinvent the network to be software defined?
- Risk aversion has resulted in 20 years of network inertia & fragility. How does that change to open the door to SDN approaches?
- Teetering mountains of complicated code has built the network of today, but you can push it over with simple human error. And that’s bad.
- Is it reasonable to expect large networking companies to provide SDN leadership?
- Centralized or distributed controllers? Which is a better fit for SDN and why?
- If you look at spending, it’s not all about cloud providers. It’s about the enterprise. So why so much focus on the cloudy corner cases?
- If a bold new software defined network design gains favor, what does that mean for Ethernet fabrics and related technologies such as TRILL, DCB, 802.1BR, and SPB?