intent-based networking
/ IBN spelled out: I-B-N /
Imagine telling a taxi driver where you want to go and letting them choose the route, versus dictating every turn yourself. Traditional network configuration is dictating every turn: you log into devices and set specific commands, addresses, and rules. Intent-based networking is telling the driver the destination: you state what you want — the intent — in high-level terms, such as these two groups must never communicate, or video calls must always get priority, and the system works out the detailed configuration to make it true and keep it true.
Concretely, an intent-based system takes a declared goal, translates it into concrete device configuration and forwarding rules (often via an SDN controller and its northbound API), pushes that down to the network, and then continuously checks reality against the intent. If the network drifts — a link fails, someone makes a manual change, traffic shifts — the system detects the gap and corrects it, rather than leaving an out-of-date config in place. So there are usually four moving parts: capture the intent, translate it, deploy it, and verify-and-remediate in a loop. It is declarative (say what you want) rather than imperative (say each step), much like infrastructure-as-code tools but aimed at the running network's behaviour.
Why it matters: as networks grow, hand-configuring hundreds of devices is slow and error-prone, and most outages trace back to misconfiguration. Stating intent once and letting software realize and police it reduces that risk and makes the network's purpose, not its low-level commands, the source of truth. Be honest about the limits: the translation from human intent to correct configuration is hard and not magic — an intent system is only as good as its models and its verification, an ambiguous or conflicting intent yields ambiguous results, and most products today automate well-understood policies rather than truly understanding free-form goals.
An admin declares an intent: finance servers may talk only to finance clients, and to nothing else. The system translates this into firewall and access rules across many switches and pushes them out. Weeks later someone mistakenly opens a path from a guest network to a finance server; the system notices the deployed state no longer matches the intent and either alerts or auto-corrects it.
Declare the goal once; the system both realizes it and keeps watching that reality matches.
Intent-based networking is not the network understanding plain English wishes. It automates the translation and verification of well-defined policies; the hard, error-prone step is mapping a human goal to correct configuration, and a vague or conflicting intent gives vague or conflicting results.