Ethernet — a networking protocol name for the ages

Michelson, Morley, and Metcalfe


In the beginning, Ethernet was optional. When Bob Metcalfe and David Boggs cooked up their network protocol at Xerox PARC in the early 1970s, it was meant to connect the research haven’s now famous Alto machines — but only if researchers felt the need. “Each scientist would get a kind of Alto order form,” Metcalfe remembers, “and you had to check a box if you wanted Ethernet.”

Then, one afternoon, with maybe ten Altos on the desks of ten PARC researchers, someone accidentally disconnected a networking cable. When ten people stood up to ask “What happened?,” Metcalfe realized his fledgling network protocol might be a keeper. “From then on,” he says, “Ethernet was not an option.”

More than thirty years later, Metcalfe went looking for a new Ethernet cable, strolling into an everyday American electronics retailer. “The woman at the cash register took me to a twenty-foot-wide wall filled with cables and said ’What color do you want?’”

After Metcalfe brokered an epic Ethernet group handshake between Intel, Xerox, and DEC in the late 1970s and brought his protocol to market through a new company he called 3Com, Ethernet shed its optional status on a global scale, evolving from LAN hardware into mainstay internet plumbing. In 2008, according to IDC, 350 million Ethernet switch ports were pushed out into the world. And that doesn’t include WiFi gear.

Last year, in honor of his Ethernet exploits, Silicon Valley’s Computer History Museum anointed Metcalfe with its annual Fellow Award, and this week, he turned up at the Mountain View geek mecca to reminisce — and, in that inimitably-opinionated Metcalfe way, trumpet his version of the future.

Harvard’s dark little heart

Metcalfe joined the Palo Alto Research Center in 1972, just after some Harvard profs failed his PhD thesis defense. His research focused on, yes, packet communication. And packet communication wasn’t a place where he and Harvard saw eye-to-eye.

When he first arrived at Harvard, Metcalfe offered to plug the venerable university into the Arpanet, a fledgling research network that would one day evolve into the modern interwebs. But Harvard declined.

“Harvard to this day is ambivalent about engineering, in their dark little heart of hearts,” he tells The Reg. “When I said I wanted to get them on the Arpanet, I was behaving like an engineer in a department of applied mathematics, and they said 'No, we’re going to hire a company do it.’”

That company was Bolt, Beranek, and Newman, a major cog in the rise of the Apranet. But the way Metcalfe tells it, BBN promptly hired another grad student to do all the work he was willing to do for free.

So, he went down the road to MIT, his undergraduate alma mater, offering his networking services to their DEC PDP-10 mainframe. MIT said “Yes,” and Metcalfe spent his Harvard career doing research on MIT’s Arpanet IMP (interface message processor). In the end, his Harvard overlords were not amused.

“I was — I still am — naive about politics,” Metcalfe says. “I didn’t really understand the process. The professors should have noticed this, but they didn’t. I showed up for my thesis defense and they gunned me down.”

But a new job was already in place at PARC — the Xerox research center that would give rise to everything from laser printing to the GUI interface — and PARC agreed to let him finish his PhD there. This, Metcalfe says, is the sort of luck that turns a life into history.

“My first stroke of luck was being born to my parents. My second stroke of luck was being given the networking job in a building full of personal computers. This was a problem that had never before occurred in the history of the world. The solution was not as amazing as the luck of getting that assignment.”

Next page: Into the ether

Similar topics


Other stories you might like

  • This startup says it can glue all your networks together in the cloud
    Or some approximation of that

    Multi-cloud networking startup Alkira has decided it wants to be a network-as-a-service (NaaS) provider with the launch of its cloud area networking platform this week.

    The upstart, founded in 2018, claims this platform lets customers automatically stitch together multiple on-prem datacenters, branches, and cloud workloads at the press of a button.

    The subscription is the latest evolution of Alkira’s multi-cloud platform introduced back in 2020. The service integrates with all major public cloud providers – Amazon Web Services, Google Cloud, Microsoft Azure, and Oracle Cloud – and automates the provisioning and management of their network services.

    Continue reading
  • Cisco execs pledge simpler, more integrated networks
    Is this the end of Switchzilla's dashboard creep?

    Cisco Live In his first in-person Cisco Live keynote in two years, CEO Chuck Robbins didn't make any lofty claims about how AI is taking over the network or how the company's latest products would turn networking on its head. Instead, the presentation was all about working with customers to make their lives easier.

    "We need to simplify the things that we do with you. If I think back to eight or ten years ago, I think we've made progress, but we still have more to do," he said, promising to address customers' biggest complaints with the networking giant's various platforms.

    "Everything we find that is inhibiting your experience from being the best that it can be, we're going to tackle," he declared, appealing to customers to share their pain points at the show.

    Continue reading
  • Cloudflare explains how it managed to break the internet
    'Network engineers walked over each other's changes'

    A large chunk of the web (including your own Vulture Central) fell off the internet this morning as content delivery network Cloudflare suffered a self-inflicted outage.

    The incident began at 0627 UTC (2327 Pacific Time) and it took until 0742 UTC (0042 Pacific) before the company managed to bring all its datacenters back online and verify they were working correctly. During this time a variety of sites and services relying on Cloudflare went dark while engineers frantically worked to undo the damage they had wrought short hours previously.

    "The outage," explained Cloudflare, "was caused by a change that was part of a long-running project to increase resilience in our busiest locations."

    Continue reading

Biting the hand that feeds IT © 1998–2022