Self-evolving network verifiers

📅 2026-08-11
📈 Citations: 0
✨ Influential: 0
📄 PDF
🤖 AI Summary
Traditional symbolic network verifiers rely on manual modeling, which struggles to accommodate vendor-specific implementation discrepancies and protocol evolution. This work proposes the first self-evolving verification framework that treats router software as a trusted oracle and integrates SMT solvers, counterexample-guided inductive synthesis (CEGIS), network emulation, and intelligent code agents within a closed-loop system to automatically extend and correct symbolic models. By shifting the verification focus from manual modeling to systematic testing, the approach autonomously uncovers vendor-specific behaviors. A prototype implementation successfully augmented a 3,000-line SMT-based verifier with support for OSPF areas, BGP route reflection, and L3VPN over EVPN, achieving complete behavioral consistency with the oracle.
📝 Abstract
Symbolic network verifiers can reason about correctness across vast spaces of routing inputs and failures, but only for the protocols and features an expert has encoded by hand. Creating and maintaining a faithful model of the control plane is both difficult and never-ending, since no written source specifies perfectly what a network does: vendor implementations deviate from the RFCs, and behaviour shifts with releases. The burden of constant upkeep ultimately keeps verification out of many networks that need it. We argue that the model should instead evolve automatically to faithfully capture the actual network behaviour. To achieve that, we leverage the only source that specifies it unambiguously: the router software itself. In a counterexample-guided loop, a coding agent proposes extensions to the verifier's symbolic encoding, while a trusted oracle (e.g., emulated routers) supplies the ground-truth routing state. The agent iteratively refines the network model using each disagreement with the oracle. As early evidence, a prototype of this system taught a 3,000-line SMT-based verifier three features it did not support: OSPF areas, BGP route reflection, and L3VPN over EVPN, converging autonomously on models that match the oracle, even noticing vendor-specific behaviour. Automating model growth shifts the hard problem from writing verification systems to systematically testing them; we propose a research agenda for trusting and harnessing automatically evolved verifiers.
Problem

Research questions and friction points this paper is trying to address.

network verification
control plane modeling
protocol implementation
vendor deviation
model maintenance
Innovation

Methods, ideas, or system contributions that make the work stand out.

self-evolving verifier
counterexample-guided loop
symbolic network verification
control plane modeling
router emulation
🔎 Similar Papers