Blog
SRv6 technology related blogs posted by SRv6 TEK Innovations Principal Network Architect Gyan Mishra to help facilitate discussion topics on SRv6 technology and how it is an industry wide network disrupter.
Log in to write a post or join the discussion.
316 posts
-
The Pizza Box Ascendancy: Engineering High-Density 1RU/2RU Non-Blocking Switches
π° Silicon Efficiency: Processing Terabit-Scale SRv6 Pipelines on Merchant Silicon
-
Monolithic Failure: The Financial and Operational Risks of Chassis Routers
π° Deconstructing the Giant: Replacing Single-Vendor Chassis with Resilient SRv6 Grids
-
DPUs in the AI Era: Orchestrating East-West Traffic for GPU Clusters
π° Unleashing AI Scale: Optimizing GPU Cluster Latency via DPU-Assisted SRv6
-
Orchestrating the DPU Control Plane: Canonical MAAS and OpenStack Ironic
π° Automated Provisioning: Orchestrating Dual-Plane Bare-Metal Nodes with SRv6 Profiles
-
Storage Disaggregation via DPU: Local NVMe Performance over NVMe-oF
π° Unified Fabric: Merging Storage Disaggregation and SRv6 Transport Networks
-
Physical Hardware Isolation: Enforcing Zero-Trust at the Server Edge
π° Un-Hackable Security: Hardening Edge Firewalls Using Isolated SRv6 Path Enclaves
-
Bare-Metal Deployment Flavor 2: Offloading Type-1 Hypervisors (KVM & ESXi)
π° Reclaiming Lost Power: Offloading Hypervisor SRv6 Encapsulation to Smart Silicon
-
Bare-Metal Deployment Flavor 1: True Native OS with DPU Multi-Tenancy
π° Multi-Tenant Agility: Injecting SRv6 Transport Segments directly onto Bare-Metal Hosts
-
Architecture Anatomy: The DPU as an Independent Mini-Server Pod
π° Silicon Evolution: Running Native SRv6 Pipelines Inside Isolated Server DPUs
-
The Death of the Midplane: Why the Blade Server Market Collapsed
π° The Compute Transformation: Moving from Rigid Blade Chassis to SRv6 Edge Nodes
-
Network and Server Convergence: Managing Server Clusters as One Routing Grid
β‘ The Technical Shift: Collapsing the traditional wall between systems administrators and network engineering teams by extending BGP and SRv6 down to individual DPU enclaves.
-
The PINS Initiative: Integrating P4 with SONiC and SAI Control Planes
β‘ The Technical Shift: Exploring the P4 Integrated Network Stack (PINS) project, which models the standard SAI pipeline as a P4 program to allow remote P4Runtime orchestration.
-
Next-Generation SRv6: Network-Wide Programmatic Policy Injection
β‘ The Technical Shift: Using Segment Routing over IPv6 (SRv6) to embed explicit service paths, traffic engineering policies, and compute instructions right into standard IPv6 headers.
-
High-Performance User-Space Networking: The Role of DPDK
β‘ The Technical Shift: How the Data Plane Development Kit (DPDK) bypasses the standard Linux kernel network stack to talk directly to network hardware from user-space applications.
-
The Host-Side Pipeline: eBPF vs. P4 for Internal Kernel Packet Processing
β‘ The Technical Shift: Comparing eBPF (running inside the Linux kernel) with P4 (running on hardware ASICs) for programmable network control.
-
The Hybrid Switch: Combining P4 Switching with Marvell OCTEON DPUs
β‘ The Technical Shift: Technical tear-down of hybrid switches (like Asterfusion) that couple an Intel Tofino or Broadcom switch chip with Marvell OCTEON processors on one internal bus.
-
Control Plane Interfacing: Comparing P4Runtime with Traditional SDK APIs
β‘ The Technical Shift: Architectural comparison of P4Runtime (a runtime control API) against traditional vendor Software Development Kit (SDK) binary interfaces.
-
Hardcoded Optimization: Using Scale Profiles and UFT Over Custom Coding
β‘ The Technical Shift: How fixed-function chips optimize resources via Unified Forwarding Tables (UFT) and Scale Profiles (e.g., L2-heavy vs. L3-heavy templates).
-
Broadcom's Counter-Strategy: Network Programming Language (NPL) Deep Dive
β‘ The Technical Shift: Architecture review of Broadcom's Network Programming Language (NPL) designed to optimize their programmable Trident chips.
-
The ASIC Oligopoly: How P4 Support Democratized Chip Architectures
β‘ The Technical Shift: Tracking how P4 moved from an Intel Tofino-exclusive feature to a language supported across Broadcom, Cisco Silicon One, Nokia FP, and Juniper families.