BRENNEN

Industries / Technology / Telecommunications / Networking equipment

Network software

This work writes the software that runs network gear: the operating systems on routers and switches, the protocols they use to share routes, and the tools operators use to configure and watch them.

6

Milestones achieved, from 1988 to 2023.

1

To watch for: announced, not yet confirmed outside.

2

Open deliverables. Nobody has shipped them.

The road

AchievedWatch forOpen

Achieved

  1. 1988

    A shared way to watch

    SNMP, the Simple Network Management Protocol, was published as RFC 1067 in August 1988 by J. Case (University of Tennessee), M. Fedor (NYSERNet), M. Schoffstall (Rensselaer Polytechnic Institute) and J. Davin (Proteon). It let one management station read counters and status from devices of any make. A 2002 workshop of the Internet Architecture Board found SNMP "widely deployed for basic monitoring," but that "router equipment is usually not fully configurable via SNMP"; operators changed settings by typing commands into each vendor's own command line.

    Lessonwatching networks was standardized long before configuring them.

    rfc-editor.orgrfc-editor.org

    Credit

    Case, Fedor, Schoffstall and Davin; the IETF

  2. 1989

    Routes between networks

    BGP, the Border Gateway Protocol, was published as RFC 1105 in June 1989 by K. Lougheed of cisco Systems and Y. Rekhter of IBM's T.J. Watson Research Center. Networks run by different organizations, called autonomous systems, use it to tell each other which addresses they can reach and through which other networks. At the time it ran on cisco routers and the NSFNET backbone, the US research network. BGP is still how networks share routes: Huston's count of 1,050,000 IPv4 entries in January 2026 is a count of BGP routes.

    rfc-editor.orgpotaroo.net

    Credit

    Kirk Lougheed (Cisco) and Yakov Rekhter (IBM)

  3. 2006

    Configuration gets a protocol

    The 2002 workshop recommended, "with strong consensus from both protocol developers and operators," that the IETF work on standard configuration. NETCONF, published as RFC 4741 in December 2006 and edited by R. Enns of Juniper Networks, gave a standard way to install, change and delete a device's configuration, written in XML. YANG, RFC 6020 of October 2010, edited by M. Bjorklund of Tail-f Systems, is a language for describing that configuration and state data.

    LessonOpenConfig, a working group of network operators, now writes vendor-neutral YANG models but carries them over newer protocols such as gNMI, which it says "replace traditional management protocols like SNMP and NETCONF"; the data models outlasted the protocol built for them.

    rfc-editor.orgrfc-editor.orgopenconfig.net

    Credit

    the IETF; Rob Enns; Martin Bjorklund

  4. 2013

    Software steers a backbone

    In software-defined networking (SDN), switches keep forwarding packets while central software, rather than each switch, decides their tables. Google's B4 paper, peer reviewed at the SIGCOMM 2013 conference, described its private network between data centers, run this way through the OpenFlow protocol on switches built from bought-in chips. After three years in production B4 carried more traffic than Google's public-facing network, and its central traffic planning ran many links close to full, where such links are usually run well below capacity so that failures can be hidden.

    LessonGoogle layered the central planning on top of ordinary routing with BGP, which gave it what the paper calls a "big red button" to switch the new system off.

    cseweb.ucsd.edu

    Credit

    Sushant Jain, Alok Kumar, Amin Vahdat and colleagues at Google

  5. 2016

    An open switch operating system

    Microsoft built SONiC (Software for Open Networking in the Cloud), a Linux-based operating system for switches in its Azure data centers, and published it openly; the project's GitHub repositories date from February and March 2016. On 14 April 2022 it moved to the Linux Foundation, which said it ran on over 100 switch models from several makers. Alibaba Cloud said it had "widely deployed SONiC-based whitebox switches," and eBay said it "deploys SONiC at scale."

    github.comlinuxfoundation.org

    Credit

    Microsoft Azure Networking (Dave Maltz); the Linux Foundation

  6. 2023

    A programmable chip line ends

    P4, proposed in a paper first posted in December 2013 by Pat Bosshart, Nick McKeown, Jennifer Rexford, Amin Vahdat, George Varghese and others, is a language for telling a switch how to read and handle packets, so that a new protocol need not wait for a new chip. Barefoot Networks' Tofino chips ran P4 programs at full speed, and Intel bought Barefoot in 2019. In January 2023 Intel's chief executive, Pat Gelsinger, said Intel would "end future investments in our network switching product line" while supporting existing customers. Nick McKeown, then general manager of Intel's Network and Edge Group, wrote that one in four papers at SIGCOMM 2022 built on P4 in some way.

    Lessonthe language outlived the chips; Cisco's G300 switch chip of 2026 is programmable in P4.

    arxiv.orgtomshardware.comgroups.google.comheise.de

    Credit

    Barefoot Networks and Intel

Watch for

  1. A self-driving network

    HPE says Marvis, an AI system it gained when it bought Juniper Networks in July 2025, now runs across its Aruba, Mist and EdgeConnect product lines, finding and fixing network problems with or without a person approving. HPE's Mittal Parekh said "none of my competitors, not Cisco, has a truly self-driving network," and that ServiceNow had cut about 90% of its helpdesk tickets with HPE's technology.

    Achieved whena customer or an independent party publishes ticket counts from before and after, with how tickets were counted, or an outside test shows faults being fixed without people.

    lightreading.com

    Claimed by

    HPE, October 2026

Open

  1. 01

    Config translation, checked by machine

    A public benchmark of at least 100 router configurations, each translated by an AI agent from Cisco IOS into Juniper Junos, Arista EOS and Nokia SR OS, with each draft checked by Batfish, an open-source configuration analyzer, to show whether the translated network treats the same test traffic the same way as the original. The benchmark records how often each agent succeeds and how often a person had to step in.

    The brief
    Credit · unclaimed
  2. 02

    One scorecard for OpenConfig

    A public scorecard, refreshed monthly, of how fully each major router operating system supports OpenConfig's vendor-neutral models: for each test in OpenConfig's featureprofiles suite, whether each vendor's system passes as written or only with a "deviation," plus independent runs of the whole suite on Nokia's freely downloadable SR Linux container.

    The brief
    Credit · unclaimed

Open 01 · the brief

Config translation, checked by machine

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A public benchmark of at least 100 router configurations, each translated by an AI agent from Cisco IOS into Juniper Junos, Arista EOS and Nokia SR OS, with each draft checked by Batfish, an open-source configuration analyzer, to show whether the translated network treats the same test traffic the same way as the original. The benchmark records how often each agent succeeds and how often a person had to step in.

Why it is still open

Rajdeep Mondal and co-authors at UCLA and Microsoft Research paired GPT-4 with verifiers in 2023 but translated "a single router" from Cisco to Juniper. INTA, from Yunze Wei and co-authors (ICNP 2025), translates Nokia and Cisco configurations into Huawei's with LLM agents. On a dataset collected from industry it reports 98.15% syntactic and view correctness and 84.72% of commands matching reference translations, scores of syntax and wording, not of how the translated network forwards traffic. A benchmark posted in April 2026 compares five models across Cisco NX-OS, Huawei VRP and Arista EOS, but starts from structured intent, not from an existing configuration. NetConfEval (CoNEXT 2024) scores models on turning written requirements into configurations for emulated networks. An October 2026 study by Anastasios Politis scored three free models' first answers on one small network of Cisco routers only. Searches on 20 November 2026 found no public benchmark that checks translations between Cisco, Juniper, Arista and Nokia by the traffic they pass.

arxiv.orgarxiv.orgarxiv.orggithub.comarxiv.org

Built with what exists

Batfish, which reads Cisco, Juniper, Arista, Nokia SR OS, SONiC and FRRouting configurations; a coding agent that runs Batfish after each draft and fixes what it flags, the habit the Note "Checked without being asked" describes in Thinking Machines' Inkling 2 Small; a spreadsheet of results.

github.com

  1. First step

    Write ten Cisco IOS configurations for a small lab network running OSPF and BGP, load them into Batfish, and have one agent translate them to Junos with Batfish feedback, logging every round.

  2. Done looks like

    100 source configurations and 300 translations published, each marked as matching on a stated set of test flows or as failed, with the success rate, prompts per success and human interventions for at least two different AI models.

Open 02 · the brief

One scorecard for OpenConfig

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A public scorecard, refreshed monthly, of how fully each major router operating system supports OpenConfig's vendor-neutral models: for each test in OpenConfig's featureprofiles suite, whether each vendor's system passes as written or only with a "deviation," plus independent runs of the whole suite on Nokia's freely downloadable SR Linux container.

Why it is still open

The project's rules let a test use "CLI instead of OC," meaning the vendor's own commands in place of the shared model, through a deviation set for that device in each test's metadata file, so the record of where vendors fall short sits scattered through the test code and pull requests. A web search on 20 November 2026 found no combined scorecard across vendors.

raw.githubusercontent.com

Built with what exists

The featureprofiles repository and its Ondatra tests; KNE (Kubernetes Network Emulation) to run them on container images, which the project documents for Arista cEOS, Cisco 8000e and XRd, Juniper ncPTX and Nokia SR Linux; a script that reads every test's metadata file and counts deviations per vendor.

raw.githubusercontent.com

  1. First step

    Clone featureprofiles, write a script that counts deviations per vendor across all metadata files, and publish the first table.

  2. Done looks like

    Every featureprofiles test listed with its deviation count per vendor, a full test run on SR Linux with pass and fail per test, both refreshed on a fixed date each month for at least six months, with the scripts published.