New Challenges for Network Engineers

Terry Slattery
Principal Architect

NFV and SDN are not the only factors that are forcing changes on network engineers; new protocols are coming, too.

“May you live in interesting times.”

The old Chinese proverb rings true as the current set of changes sweep through the networking industry. Not only are we learning about NFV and SDN, there are new transport protocols that will require new education and new troubleshooting tools. I became aware of the new protocols when reading about WebRTC (browser-based real-time collaboration – video in the browser). (See “Speeding Up the Internet” for a related post about speeding up the Internet.)

Wait! New transport protocols? What’s wrong with TCP and UDP? Well, there are several things that could be improved. Instead of repeating them here, you can read about them in RFC4960, Stream Control Transmission Protocol, Section 1.1. And these problems don’t include the impact of bufferbloat on TCP throughput.

UDP has its own problems. Software developers have to build message handling, fragmentation and reassembly, and congestion control into their applications. That’s a lot of work and a lot of code to include in each application.

The new protocols are the Stream Control Transmission Protocol (SCTP—see RFC4960), SPeeDY (SPDY—see “SPDY: An experimental protocol for a faster web”), and Quick UDP Internet Connections (QUIC—see “QUIC, a multiplexed stream transport over UDP”). SCTP was created to transport PSTN signaling over IP networks without the problems of TCP. SPDY was created, primarily by Google developers, to improve the performance of HTTP on the wire. It performs HTTP multi-stream compression and encryption with SSL/TLS over TCP. QUIC is a successor to SPDY that uses UDP as its transport in order to avoid some of the problems inherent in TCP. According to Google, about half of all Chrome browser interactions with the Google search engine are using QUIC. Another interesting tidbit about QUIC is that using UDP allows its congestion control mechanisms to be developed outside the OS kernel. Making changes to kernel networking code is nearly impossible, so moving the task into user space code allows researchers to easily deploy new technologies without requiring an OS upgrade. This is very cool.

These new protocols are good. They address many of the problems and inefficiencies of traditional protocols. We will need to understand how these new protocols work and how to troubleshoot them, just as we had to understand TCP’s windowing functionality over long fat pipes in order to achieve high throughput flows.

There are other changes that these protocols bring. Firewalls and load balancers will need to understand and handle the new protocols. Stateful firewalls, in particular, will need to be modified to handle QUIC, which runs over UDP and can start a connection between a client and server in one or two round-trip times. The encryption and compression of data on the wire will require that network analysis tools be updated to understand and decode the new protocols. Tools that sniff packets on the wire, like Wireshark and Application Performance Management systems, will need to adapt to the new protocols. I’m sure we’ll also need new troubleshooting tools to supplement the existing tools.

Leave a Reply


Nick Kelly

Cybersecurity Engineer, Cisco

Nick has over 20 years of experience in Security Operations and Security Sales. He is an avid student of cybersecurity and regularly engages with the Infosec community at events like BSides, RVASec, Derbycon and more. The son of an FBI forensics director, Nick holds a B.S. in Criminal Justice and is one of Cisco’s Fire Jumper Elite members. When he’s not working, he writes cyberpunk and punches aliens on his Playstation.


Virgilio “BONG” dela Cruz Jr.

CCDP, CCNA V, CCNP, Cisco IPS Express Security for AM/EE
Field Solutions Architect, Tech Data

Virgilio “Bong” has sixteen years of professional experience in IT industry from academe, technical and customer support, pre-sales, post sales, project management, training and enablement. He has worked in Cisco Technical Assistance Center (TAC) as a member of the WAN and LAN Switching team. Bong now works for Tech Data as the Field Solutions Architect with a focus on Cisco Security and holds a few Cisco certifications including Fire Jumper Elite.


John Cavanaugh

CCIE #1066, CCDE #20070002, CCAr
Chief Technology Officer, Practice Lead Security Services, NetCraftsmen

John is our CTO and the practice lead for a talented team of consultants focused on designing and delivering scalable and secure infrastructure solutions to customers across multiple industry verticals and technologies. Previously he has held several positions including Executive Director/Chief Architect for Global Network Services at JPMorgan Chase. In that capacity, he led a team managing network architecture and services.  Prior to his role at JPMorgan Chase, John was a Distinguished Engineer at Cisco working across a number of verticals including Higher Education, Finance, Retail, Government, and Health Care.

He is an expert in working with groups to identify business needs, and align technology strategies to enable business strategies, building in agility and scalability to allow for future changes. John is experienced in the architecture and design of highly available, secure, network infrastructure and data centers, and has worked on projects worldwide. He has worked in both the business and regulatory environments for the design and deployment of complex IT infrastructures.