Network Architecture Quotes

In the earliest days, this was a project I worked on with great passion because I wanted to solve the Defense Department's problem: it did not want proprietary networking and it didn't want to be confined to a single network technology.

I started in time-sharing and networking with packet switching, which was the precursor to what became the Internet. Time-shared use on packet-switch networks, when you think about it, is the cloud.

The Internet was developed in large part by U.S. government research funding to develop new communications networks, starting with a network created by the Department of Defense.

The big deal about the Internet design was you could have an arbitrary large number of networks so that they would all work together.

I really enjoy computer networking.

World makers, social network makers, ask one question first: 'How can I do it?'

The Internet wasn't useful until some basic infrastructure was built.

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

The next Internet could be in the making somewhere in someone's lab.

It doesn't matter if it's a wireless or wired network. I think network management can be introduced that is equally sensible.

The bottom-up, loosely-coupled, bilateral and multi-stakeholder practices that have created the network of networks we call the Internet allow for a broad range of business models.

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

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

The idea was that you could grow a system like the Internet one network at a time and then interconnect them. In some sense, the most important thing was the invention of the architecture protocols that enabled the Internet.

Infrastructure web services had to happen.

What makes a great standalone piece of hardware is not the same thing as what makes a great networking device. One can work as an essentially closed system. The other is absolutely dependent on its openness.

The remarkable social impact and economic success of the Internet is in many ways directly attributable to the architectural characteristics that were part of its design. The Internet was designed with no gatekeepers over new content or services.

Rebuilding a network is a slow, brick-by-brick process. It's not just creating a hit show - it's building shows to back up that hit show; it's creating an identity of success so that people want their shows on your network.

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

So as I look at transitioning to the communication platforms of the future, I see that the beauty of Internet protocols is you get the separation of the layers between service and technology.

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.

Unlike 4G and previous generations of technology, 5G is very different. It is not just about radio. In fact, it stands across the full network from mobile access to cloud core, from software-defined networking to all forms of backhaul, front haul, IP routing, fixed networks, software, and more.

The ARPAnet was the first transcontinental, high-speed computer network.

At MIT, I had the good fortune for seven years to teach network theory, which is basic to many disciplines, to one-third of the undergraduate student body. It was an experiment to see how high we could bring their level of understanding, and it exceeded all of my expectations.

The basic technical protocols that have enabled the Internet to work in such a globally interconnected way are developed and shared openly by a community of engineers.