The encyclopedia · Software & IT · Technical decision · 1987–1998
OSPF became enterprise routing's standard by sharing the whole map
The IETF's OSPF gives every router a full network map and shortest paths; its open, scalable design made it the standard interior routing protocol.
IETF
The solution
In the 1980s, routing inside networks used distance-vector protocols that exchanged summaries of routes, which converged slowly and struggled as networks grew. Link-state routing, born on the ARPANET, offered a more robust model.
OSPF, developed by the IETF and standardized as RFC 2328 in 1998, is a link-state protocol: every router floods link-state advertisements so each holds an identical topology database, then computes its own shortest-path tree. Areas contain the computation, and exchanges can be authenticated.
Because OSPF was an open standard with multiple interoperable implementations, it became the default interior gateway protocol across enterprise, campus and service-provider networks and is core to every serious networking curriculum, while proprietary alternatives stayed confined to single-vendor shops.
Why it worked
- Complete topology knowledge eliminated loops and sped convergence.
- Areas let OSPF scale to thousands of routers.
- An open IETF standard meant multi-vendor interoperability.
- Authentication and equal-cost multipath answered operational needs.
What can be applied
The standard that wins is the one no vendor owns: OSPF beat proprietary rivals in enterprise networks because any vendor could implement it and no customer was locked in.
Aftermath
OSPF remains the most widely deployed interior gateway protocol, supported by every major router vendor, with OSPFv3 extending it to IPv6; RFC 2328's design has outlasted every proprietary rival and still anchors enterprise networks.
Sources
spotted an error? The archive wants to know.