Network Design Quotes

One of my bosses happened to be one of the early architects of some of the ways Internet providers work. He taught me how the cables connect, how the telecom providers work... I learned how to make my own Ethernet cables, all the way up to running a small business.

One thing that I can tell you that we have not done very well is to build in broadcast capability into the network, and we don't take advantage of broadcast radio.

I'm not an economist; I'm a hacker who has spent his career exploring and repairing large networks.

It's incredibly hard to program a network from scratch for 24 hours.

I would say that in general, Cisco is a very strong research and development organization.

The last thing I would ever do is try to become a network programmer.

In a world of dumb terminals and telephones, networks had to be smart. But in a world of smart terminals, networks have to be dumb.

By placing intelligence at the edges rather than control in the middle of the network, the Internet has created a platform for innovation.

My main interest is in trying to find radically different kinds of neural nets.

The idea that hardware on networks should just be caches for movable process descriptions and the processes themselves goes back quite a ways. There's a real sense in which MS and Apple never understood networking or operating systems (or what objects really are), and when they decided to beef up their OSs, they went to (different) very old bad mainframe models of OS design to try to adapt to personal computers.

An attitude of only taking what you need was built into the protocols of the Internet itself.

I am instinctively a network infrastructure plumber.

Fragmentation is like classful addressing - an interesting early architectural error that shows how much experimentation was going on while IP was being designed.