The Knot in the Network
In Computer Networking, the basic unit of science is the ‘node.’ All computers and chips, anything that sends or receives traffic, is a node. Nodes are connected by links. Networks consist of nodes and links. Some nodes are routers, some are hosts.
The origin of the word is the Latin nodus, “knot”—the thing you tie in a rope. Trace it further back to its Indo-European root ned-, “to bind or tie,” which also produced Latin nectere, “to bind,” which gives us connect, annex, and nexus; and through the Germanic line it produced the English word net. “Network node” is therefore very nearly a redundancy—the knot of the knotted thing!
For most of its career the word named distinguished points in continuous things, such as where orbits cross in astronomy. But for Computer Networking, the decisive precedent is electrical. In 1845 Gustav Kirchhoff, still a student at Königsberg, published the two circuit laws every engineering student now learns; the current law—what flows into a junction flows out—is known in German as the Knotenregel, the knot rule, because a junction where conductor branches meet is a Knoten, a knot. Electrical engineering was calling its junctions knots a century before anyone switched a packet.
Königsberg, fittingly, is also where network mathematics comes from: Leonhard Euler’s 1736 analysis of the city’s seven bridges is the conventional origin of graph theory, the abstraction (a graph = points joined by lines) by which orbits, stems, circuits, and telephone exchanges become the same object. The word graph itself came later, coined by the mathematician James Joseph Sylvester in 1878; mathematicians tend to say vertex, engineers say node, and they mean the same thing.
Computer networking inherited both lineages at once. Paul Baran’s 1964 RAND studies, On Distributed Communications, asked whether a web of switching nodes with redundant links could survive the loss of many of them. (Spoiler: YES).
When the ARPANET went live in 1969, its design split the graph world into two: a communication subnet built of Interface Message Processors were called the “nodes,” with UCLA’s IMP as node number one—versus the timesharing computers that actually served users, the “hosts.” That division of labor is why the network’s very first Request for Comments, RFC 1 of April 1969, is titled simply “Host Software.”
The standards later fixed the usage into law. RFC 8200, the current IPv6 specification, defines a node as a device that implements the protocol, a router as a node that forwards packets not addressed to itself, and a host as any node that is not a router. So in IETF terms every host is a node, and routers are the nodes that aren’t hosts.
The IEEE, meanwhile, preserves the older topological sense: the 802 LAN standards largely avoid node for end systems, preferring station, while IEEE glossary usage keeps the graph-theoretic meaning — an endpoint of a link, or a junction common to several. The definitions differ because they draw different graphs: to Ethernet, a switch is a node; to IP, the whole switched segment collapses into a single link and the switch vanishes.
Two thousand years of usage agree on the essential point. To call something a node is to make a relational claim: a node is not a kind of thing but a kind of position. A device becomes a node the moment it is tied into something larger, and ceases to be one the moment it is cut loose. The Romans would have found nothing strange here — a nodus was always a place where separate strands are made to hold. We did not stretch the word to fit our machines; we finally built the thing the word was waiting for.