CodeHistory.org
FIELD NOTE / 2026.09.214 MIN READ / 6 SOURCES

The Minds Behind Internet Routing Protocols – 7 People Redefining Networking

Seven routing pioneers helped create the protocols that let local networks, autonomous systems, and provider backbones find scalable paths.

Written byTheo MercerEDITOR · CODEHISTORY RESEARCH DESKRESEARCHED / CITED

TL;DR

Internet routing is not one algorithm but a stack of solutions for different scopes. Perlman solved loop-free bridging and contributed to link-state ideas; Rekhter and Lougheed created BGP, with Li helping evolve BGP-4 and CIDR; Oran helped shape IS-IS; Moy defined OSPF; and Rosen helped move provider networks toward MPLS label switching.[1][3][4][5]

Why you should read it anyway

The Internet can survive link failures and policy disagreements because routers continually exchange compressed views of topology and reachability, then choose paths according to protocol rules and local policy. The hardest part is that no single organization controls the whole system. Internal routing wants speed and consistency; inter-domain routing must also represent economic and policy boundaries.

Imagine where Internet Routing Protocols would be without them

Without these routing protocols, packet networks could connect only at much smaller scale or with far more manual configuration. Redundancy would be dangerous because loops could form; autonomous systems would struggle to exchange routes; large providers would lack scalable interior routing and traffic engineering. The Internet’s physical links matter only because routing makes them behave like one reachable system.

Time Estimate of how many years we would be hindered without them for human progress

Editorial counterfactual estimate: 5–10 years. Routing problems appear immediately as networks grow, so alternative algorithms and protocols would have emerged. The likely delay lies in open standardization and scaling: BGP, OSPF, IS-IS, CIDR, and MPLS gave operators shared tools for networks orders of magnitude larger than their predecessors.

The 7 people behind Internet Routing Protocols

1. Radia Perlman

Why they matter: Perlman invented the spanning-tree algorithm that allowed Ethernet bridges to create a loop-free forwarding topology automatically, and she also contributed deeply to link-state routing work at Digital.[5] Her role is foundational because real networks contain redundant links for resilience; routing and bridging protocols must exploit redundancy without creating forwarding loops that amplify traffic indefinitely.

2. Yakov Rekhter

Why they matter: Rekhter co-authored the original BGP specification with Kirk Lougheed in 1989 and later edited BGP-4 with Tony Li.[1][2] BGP changed Internet routing from a relatively simple reachability mechanism into a policy-capable inter-domain protocol that could scale across autonomous systems. Rekhter also helped define CIDR-era address aggregation, tightly linking routing scalability to address allocation.

3. Kirk Lougheed

Why they matter: Lougheed, at Cisco, co-authored RFC 1105 with Rekhter, defining the first Border Gateway Protocol as a mechanism for exchanging reachability information between autonomous systems.[1] His contribution sits at the point where the growing Internet needed routers from different organizations to exchange routes without pretending they belonged to one administrative domain.

4. Tony Li

Why they matter: Li co-edited BGP-4 with Rekhter and co-authored important CIDR work that reduced routing-table growth by allowing address aggregation.[2] BGP-4’s support for classless prefixes became essential as the Internet outgrew classful addressing. Li’s role shows that routing scalability depends on the representation of addresses as much as on the path-selection algorithm.

5. Dave Oran

Why they matter: Oran was a major architect of IS-IS and is associated with the ISO 10589 work that defined the link-state routing protocol later widely used by service providers.[6] His work represents a parallel standards lineage to OSPF: large networks needed robust link-state protocols capable of distributing topology information efficiently and calculating shortest paths under change.

6. John Moy

Why they matter: Moy authored the principal OSPF specifications, including RFC 2328, which defines OSPF Version 2 as a link-state routing protocol for use inside an autonomous system.[3] OSPF introduced areas, link-state advertisements, designated routers, authentication options, and fast topology recalculation into a widely deployed open Internet standard.

7. Eric Rosen

Why they matter: Rosen contributed to early ARPANET routing improvements and later became a principal architect of Multiprotocol Label Switching. RFC 3031, co-authored by Rosen, defines MPLS’s label-based forwarding architecture.[4] His work extends the routing story beyond calculating next hops: large provider networks also needed traffic-engineering and forwarding mechanisms that could map groups of packets onto controlled label-switched paths.

How they each differ from one another

Perlman’s famous contribution concerns loop-free LAN bridging and link-state network design. Rekhter and Lougheed originated BGP; Li helped evolve BGP-4 and CIDR. Oran represents the IS-IS family, while Moy is the central OSPF specification author. Rosen’s later MPLS work introduced label-based forwarding for provider-scale control. These are complementary layers, not competing claims to one invention.

Final Take

Routing is the Internet’s invisible negotiation system. Every packet benefits from decades of work that lets routers discover neighbors, flood topology, summarize prefixes, express organizational policy, recover after failures, and engineer traffic. The people behind routing made a global network possible without requiring a global network operator.

RESEARCH / PROVENANCE

Works Cited

6 SOURCES
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06

CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.

Contribute / Corrections

Improve the record.

Use this moderated submission form to suggest a correction, provide a source, challenge a priority claim or identify a missing contributor. Submissions are treated as research leads, not automatically published comments.

Submit a research lead

Please do not submit confidential material or claims you cannot support.