The encyclopedia · Software & IT · Technical decision · 1988–1990
SNMP won network management by making everything one tiny UDP request
The IETF chose an almost too-simple protocol — get, set, trap over UDP — and it became the standard for managing networks.
IETF
the move
As networks grew in the late 1980s, operators had no common way to check a router's status or change its configuration. The Internet community's rival proposals, built around the OSI management framework, were judged unimplementable on the hardware of the day.
The SNMP designers made simplicity the whole point. A manager sends a tiny UDP packet to port 161 asking for a named object, and the agent answers with its value; traps push urgent events back. There is no connection, no heavy encoding and almost nothing to install.
RFC 1157, published in May 1990, described the protocol, and vendors implemented it quickly because the bar was so low. SNMP became the de facto standard for managing network equipment and remains in every router, switch and printer.
why it works
- The OSI-style alternatives were too heavy for 1980s hardware
- A few operations over UDP were trivial to implement
- MIBs gave every device one uniform tree of named values
- Shipping in every router made it the default before rivals arrived
what transfers
When the heavyweight standard cannot be implemented, an intentionally minimal one wins by being easy enough that every vendor ships it.
what came after
SNMPv2 and SNMPv3 added better security while keeping the same simple model, and the protocol is still the universal interface for monitoring network gear. Newer streaming telemetry handles scale, but SNMP's core design outlived every competitor it faced.
references
spotted an error? The archive wants to know.