Feeds

Ethernet — a networking protocol name for the ages

Michelson, Morley, and Metcalfe

Boost IT visibility and business value

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.”

The essential guide to IT transformation

Next page: Into the ether

More from The Register

next story
The Return of BSOD: Does ANYONE trust Microsoft patches?
Sysadmins, you're either fighting fires or seen as incompetents now
Microsoft: Azure isn't ready for biz-critical apps … yet
Microsoft will move its own IT to the cloud to avoid $200m server bill
Oracle reveals 32-core, 10 BEEELLION-transistor SPARC M7
New chip scales to 1024 cores, 8192 threads 64 TB RAM, at speeds over 3.6GHz
Docker kicks KVM's butt in IBM tests
Big Blue finds containers are speedy, but may not have much room to improve
US regulators OK sale of IBM's x86 server biz to Lenovo
Now all that remains is for gov't offices to ban the boxes
Gartner's Special Report: Should you believe the hype?
Enough hot air to carry a balloon to the Moon
Flash could be CHEAPER than SAS DISK? Come off it, NetApp
Stats analysis reckons we'll hit that point in just three years
Nimble's latest mutants GORGE themselves on unlucky forerunners
Crossing Sandy Bridges without stopping for breath
prev story

Whitepapers

5 things you didn’t know about cloud backup
IT departments are embracing cloud backup, but there’s a lot you need to know before choosing a service provider. Learn all the critical things you need to know.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Build a business case: developing custom apps
Learn how to maximize the value of custom applications by accelerating and simplifying their development.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.