side of the power spectrum, pro- cessors implement various power-down (sleep) modes that are also typically disabled, most often through boot time configuration. On multithreaded processors, incremental gains from enabling additional processor threads can vary depending on the application. Careful benchmarking can establish any potential gains or losses due to cache pollution. Networking stacks CU, DU, and RU implementations require networking stack support for termination and for- warding of U-Plane and C-Plane traffic but also for Management and OAM operations. These stacks can be supported by the Linux (kernel) implementation, specialized open-source or third party solutions, such as7,8 or a combination thereof where performance-critical pieces are optimized independently from remainder components. Features Target networking features that are expected to be supported by cell-site type of products include L2 protocol support: 802.1q (VLAN), 802. lad (QinQ), QoS/traffic prioritization, Link Aggregation, MPLS, Jumbo Frame support (9KByte). IP protocol support: Access Control Lists (ACL), IPv4/IPv6, IPSec, UDP, GTP, ingress policing based on traffic type (e.g., Control Plane policing), DiffServ. Routing and Management: Command Line Interface (CLI), Simple Network Management Protocol (SNMP) v2 and v3, Segment Routing, Border Gateway Protocol (BGP), NETCONF/YANG, Secure Copy Protocol, Syslog, Network Timing Protocol, Dynamic Host Configuration Protocol (DHCP) and DHCP relay, Network Layer Reachability Information, Ethernet Operation and Maintenance (OAM). Security TS 33.210 directs that the base station platform shall support network layer security protocols defined by IETF IPsec security protocols specified in RFC-4301 and in RFC-2401. Details of Open Radio Access Network (O-RAN) Systems Architecture and Design platform specific IPsec implementation are unique per implementation, some aspects COV- ered in later chapters. The minimum requirements of IPsec are listed below. ESP shall be supported according to RFC-430