White-Box Switches: Development, Architecture, and Future Trends

White‑box switches have rapidly evolved in the last thirty years, driven by open‑source organizations such as ONF, the Linux Foundation, OCP, and TIP, offering a decoupled hardware‑software architecture that reduces costs and enables open‑source software development.

Their advantages include customizable hardware and software, programmable data‑plane, containerized deployment, enhanced flexibility, agility, and reduced operational expenses through cloud‑native technologies.

Industry adoption spans chip manufacturers, device vendors, cloud providers, and telecom operators, forming a robust ecosystem that supports both open‑source and commercial initiatives.

Historically, milestones include early Linux adoption (1998), Linux‑based switching (2008), OVS‑based open switches (2010), ONIE and FBOSS development (2013), the first white‑box switch Wedge (2015), and the proliferation of open network operating systems such as SONiC, OpenSwitch, DANOS, and Stratum.

The open‑source ecosystem is organized around projects like OCP (hardware standards), ONF (SDN development), TIP (telecom infrastructure), and ODCC (data‑center collaboration), each contributing to standards, hardware designs, and software stacks.

AT&T defines a four‑layer architecture: Hardware 1 (commercial ASICs), Software 1 (chip interfaces), Hardware 2 (reference designs), and Software 2 (network OS and protocols), highlighting the importance of the software layer.

Programmable networking technologies enable centralized control, dynamic configuration, and API‑driven resource abstraction, while traditional fixed‑function ASICs limit flexibility.

Hardware acceleration using SmartNICs, FPGAs, and CPU‑SmartNIC heterogenous designs offloads intensive processing, reducing latency and CPU load.

Security concerns arise from open boot environments like ONIE, which can be exploited to insert malicious code before the OS loads, making firmware replacement costly.

Overall, white‑box switches combine open hardware standards, programmable data planes, hardware acceleration, and security considerations to build scalable, flexible, and future‑proof network infrastructures.