Metraipolis › archive › dc_dae650b30dba

Resource versus Responsiveness: Benchmarking SDN Controller Runtimes for a Moving-Target-Defense Control Plane at Scale — arXiv:2609.35585

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.35585
License (as archived)
CC0-1.0
Archived
2026-10-07T23:02:24.898Z
SHA-256 of the archived text
3297f84cd0335dc4b368f3c54570012d30f4692f203abac1c613ca5966c1bb24
Stable URL of this page
https://metraipolis.com/documento/dc_dae650b30dba

How to cite

Resource versus Responsiveness: Benchmarking SDN Controller Runtimes for a Moving-Target-Defense Control Plane at Scale — arXiv:2609.35585 — arXiv (en), https://arxiv.org/abs/2609.35585 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_dae650b30dba (Metraipolis archive dc_dae650b30dba, sha256 3297f84cd0335dc4b368f3c54570012d30f4692f203abac1c613ca5966c1bb24)
BibTeX
@misc{dcdae650b30dba,
  title = {Resource versus Responsiveness: Benchmarking SDN Controller Runtimes for a Moving-Target-Defense Control Plane at Scale — arXiv:2609.35585},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.35585},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_dae650b30dba; sha256 3297f84cd0335dc4b368f3c54570012d30f4692f203abac1c613ca5966c1bb24},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.35585. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Network Moving Target Defense (MTD) built on Software-Defined Networking (SDN) continuously rotates host-facing addresses to invalidate an attacker's reconnaissance. Each rotation creates a burst of control-plane mutations, while new connections may simultaneously require reactive flow installation. Yet SDN controller runtime is usually treated as an implementation detail in the MTD literature. We show that it materially affects performance. We port the same Continuity-Preserving Address Mutation (CPAM) logic to three widely used controllers: Ryu (single-threaded cooperative Python), OpenDaylight, and ONOS (both multi-threaded JVM), and evaluate them on an identical 500-host campus fabric using an RFC 8456-aligned methodology with ten runs per controller. All three provide near-zero loss, sub-millisecond jitter, and preserve established sessions, but their control-plane behavior differs sharply. OpenDaylight and ONOS keep reactive latency low and stable, whereas Ryu serializes reactive flow installation behind periodic rotation work, increasing reactive RTT by about 100x and causing a small number of setup-time failures. Ryu uses far less memory, while ONOS achieves OpenDaylight-class reactive latency with the lowest CPU utilization of the three and a smaller live heap than OpenDaylight. These results expose distinct resource-versus-responsiveness operating points and show that controller selection should be treated as a first-class design decision in SDN-based MTD.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-29 in cs.NI).
Categorie arXiv: Networking and Internet Architecture (cs.NI).
Pagina del lavoro: https://arxiv.org/abs/2609.35585 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-07T22:39:52.981Z dalla pagina https://arxiv.org/catchup/cs.NI/2026-09-29?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).