The Register® — Biting the hand that feeds IT

Feeds

Ethernet at 40: Its daddy reveals its turbulent youth

Bob Metcalfe: How Token Ring and 'IBM's arrogance' nearly sank Big Blue

SaaS data loss: The problem you didn’t know you had

Feature When Bob Metcalfe, the prime mover behind the invention of Ethernet, recently visited the site of that invention, Xerox's Palo Alto Research Center (PARC), The Reg had the opportunity to sit down with him to discuss the history of Ethernet, its advantages over Token Ring, and IBM's perfidy.

Metcalfe was in town to promote a two-day Ethernet Innovation Summit that will commence on May 22 at Silicon Valley's Computer History Museum in celebration of Ethernet's 40th anniversary.

"As you know," Metcalfe told us, "something like Ethernet is not actually invented in a single day. But if there were a day, it would be May 22nd, [1973]."

The Reg asked what had happend on that day. "I wrote a memo," he said, "and in that memo named it and outlined its general operation." Ethernet, however, was not the original name of what has now become the world's networking standard.

"Prior to that we'd been calling it the 'Alto ALOHA Network,' Alto being the PC that we were building, and the ALOHA Network being a packet radio network at the University of Hawaii whose design we admired," Metcalfe said.

"But then on that day we realized that we were going to network things other than Altos," he said, "and Ethernet had by then progressed so that it was barely resembling ALOHA. So we changed it to Ethernet."

The term ALOHA, by the way, was a rather contrived acronym that stood for Abramson's Logic of Hiring Access, named after its University of Hawaii developer, Norm Abramson.

Bob Metcalfe

Ethernet daddy Bob Metcalfe
(source: University of Texas at Austin)

Metcalfe remains more than a little sensitive about just how much Ethernet owes to ALOHA. "Over the years people have said that Ethernet is just ALOHA network," he told us. "I wrote a preface to my own book in which I put a paragraph explaining how Ethernet was just like ALOHA network except – and then there was like 20 'excepts,' one of which was that the ALOHA network was not a LAN; it was a WAN. It was to connect the Hawaiian Islands over a distance of 200 miles, and it ran at 4800 bits per second." Ethernet first ran at 2.94 megabits per second.

There were other differences, as well. Ethernet, for example, operated within a mile, so its propagation time was five milliseconds; ALOHA's 200-mile range, of course, operated at much longer time scales. "The parametric values all changed, and therefore the operation of the network changed," Metcalfe told us – and he said that he provided more than enough examples in his preface to prove his point.

"When I reread that paragraph," he said of his protestations, "I can see whoever wrote that paragraph was fed up with that accusation."

But his fervent attempt to separate Ethernet from ALOHA wasn't entirely successful – even at PARC. During our interview in the center's cafeteria, Metcalfe caught sight of a man at a corner table whom he identified as being PARC's "artificial-intelligence guru," Danny Bobrow, whose office was next to Metcalfe's in the early 70s. Metcalfe, who last visted PARC in 1975, told Bobrow about Ethernet's 40th birthday, and the AI guru said, "And it all came out of ALOHA, eh?"

Metcalfe turned to us; "See? See?" he said, then turned back to Babrow. "I'll have to send you my book," he laughed.

But he's still a bit miffed. "Norm Abramson, my good friend from the University of Hawaii," he said, "I've seen his presentations and he takes credit for Ethernet, Wi-Fi, and everything else."

That said, "There's plenty of credit to go around," he admitted.

Metcalfe had worked on the ARPANET both in graduate school and at PARC, and when he arrived at PARC, researcher Charles Simonyi was working to create a LAN within the buiding called SIGNET. "His idea was to mimic the ARPANET," Metcalfe said, "and put packet switches all over the building."

Since Metcalfe was "the real networking guy," he told us, Simony was given the boot and he was given the SIGNET project. "By the way, SIGNET is short for Simonyi's Infinitely Glorious Network, named after himself," Metcalfe informed us.

Don't feel sorry for Simonyi being removed from his LAN project, however. He and PARC colleague Butler Lampson went on to develop a WYSIWYG text editor for the Alto called Bravo. It was transformed into Microsoft Word and Simonyi got rich.

"He now has his own three-engine jet and his own helicopter, and he's a billionaire," Metcalfe said. "Maybe I should have written Bravo and he should have done the network."

We asked Metcalfe what the main usage-model requirements that his work on Ethernet were intended to solve. "No one wrote a requirements document," he said, "this is a research center."

What PARC wanted to do was create a LAN to link the Altos that it planned to put on its researchers' desks to replace the 300-bits-per-second Texas Instruments Silent 700s they had at the time, a "revolutionary" change, according to Metcalfe.

"There was a lot of argument if it made any sense to put a computer on every desk," he recalled. "You'd have to have an MIS manager for every desk. What if they broke? Someone would have to come to your office and fix it."

Those objections, he said, "melted away over time." A fast LAN would allow PARC to not only put an Alto on each desk and preserve access to the ARPANET gateway, but it would also solve another problem: providing access to the laser printer that PARC was developing.

"I wrote the operating system for that printer," he told us, "and then we plugged in an Ethernet card. Its requirement was 500 dots per inch, a page per second, 8½ by 11. Five hundred times 500 times 8½ times 11 is about 23 megabits per second. And so the current methods of networking were not going to keep that printer busy."

When we jokingly asked, "Well, what are buffers for?" he responded, "Well, speaking of buffers, each of these Altos has a removable-disk cartridge that could carry two megabytes, which was huge in the day. And so sneakernet was born."

To print, the researchers would put their documents on one of those removable cartridges, remove the cartridge, walk over to the Alto to which the laser printer was connected, plug the cartridge into that Alto, and print it. Sneakernet.

"But I argued," he said, "'Wouldn't it be easier just to hit P?' And they said, 'Well, you'd still have to walk down to get the printout!' So I said, 'Okay, you've got me there'."

But eventually Metcalfe did get the laser printer hooked up to his new LAN, and thanks to the printer's resident fonts and compression schemes, Ethernet's throughput was plenty fast enough to accept print jobs.

That was the genesis of Ethernet: connecting those "revolutionary" desktop PCs, providing access to the ARPANET, and allowing researchers to simply hit P to print. "We were not planning to do the web, or audio, or video," Metcalfe told us. Those came later. Much later.

Steps to Take Before Choosing a Business Continuity Partner

That's not her philosophy

Rand wants everyone to be selfish and only follow their own goals because she doesn't understand that there is a difference between individual goals and the common good. Ethernet is actually a good example why she is wrong.

Ethernet works, because there are strict rules everyone must adhere to. If there is a collision you have to wait a random time. With each collision the timespan of that random number will increase. This rule throttles down stations when the network is full, to share the bandwidth more or less fairly between them.

Now an Any Rand network card would simply ignore the standard and re-transmission the packet right away. That way it will always give the card 100% of the network if it wishes to. However if more people act like this, there will _only_ be collisions. Once there is a collision, both stations will try again at the same time, they will do so until one of them gives up. Instead of sharing the bandwidth fairly between the stations, those few stations ruin the network for everyone.

26
0

twisted Pair...

I know almost everyone says how wonderful twisted pair cabling was, but one of the major advantages of ethernet for us over Token ring was that it didn't require star wiring for every damn device. By and large we weren't installing in purpose built office buildings but in older, often historic buildings with no cable space. Getting permission for a run of thinnet, maybe with a thicknet backbone, or even earlier corvus omninet which was a STP bus, was straightforward, getting permission for vast wodges of twisted pair for TR would have been next to impossible. And then anytime anyone wanted a new device it would have been get the cablers in. Mind you that hasn't changed, because every time we think we've flood wired an office they have a reorg and cram yet more tinier desks in at an even higher density...

A few years on of course the managers all had their own devices on their desk and those pig ugly runs of trunking suddenly weren't a problem any more... Especially if it meant no more engineers crawling round our office with a TDR trying to work out where the break actually was...

19
0

Re: Ethernet is the Ayn Rand network?

Ayn Rand probably wasn't a fascist, but she was certainly a hypocrite for trying to create a moral justification for why her followers had to do what she told them, when she had taught them that morality was obsolete.

13
0

More from The Register

SCO vs. IBM battle resumes over ownership of Unix
Zombie lawsuit back and wants to suck the brains out of Linux
 breaking news
You don't need phone lines or cable for ANYTHING, says Dish
The satellite-dish man can sort you out with phone and broadband over the air too
 breaking news
What's HP got under wraps? Looks awfully flash and tape shaped
What happens in Vegas won't stay there - we've got the details
Microsoft borks botnet takedown in Citadel snafu
Stupid Redmond kicked over our honeypots, wail white hats
IBM's $1bn layoffs latest: Now axe swings in US, Canada - reports
Union claims 121 storage bods canned after dismal sales
NetApp musters muscular cluster bluster for ONTAP busters
Storage array OS overhauled to juggle more nodes, go down on you, er, less
HP adds 'Haswell' Xeon E3s to entry ProLiant servers
Gussies up MicroServer for SMBs, adds baby switches