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.
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.
The Internet didn't become usable until Netscape because that gave the average person a user interface that was intuitive, simple, friendly - this made it accessible.
The Internet is literally a network of networks.
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.
Pretty much everything on the web uses those two things: C and UNIX. The browsers are written in C. The UNIX kernel - that pretty much the entire Internet runs on - is written in C.
The big deal about the Internet design was you could have an arbitrary large number of networks so that they would all work together.
TV and the press have always functioned according to the same sets of rules and technical standards. But the Internet is based on software. And anybody can write a new piece of software on the Internet that years later a billion people are using.
I really enjoy computer networking.
Now, if someone tries to monopolize the Web, for example pushes proprietary variations on network protocols, then that would make me unhappy.
World Wide Web: Proposal for a HyperText Project
This coined the term “World Wide Web”. The co-author of the document was Robert A Caillau.
All this stuff was done via FTP but the web has put a really nice user interface on it.
The routers get involved in this and they know that on the path between this router and that router a certain percentage of the bandwidth is reserved to these things and a certain percentage of it is allowed on a first come first served basis.
I started with CB radio, ham radio, and eventually went into computers. And I was just fascinated with it. And back then, when I was in school, computer hacking was encouraged. It was an encouraged activity. In fact, I remember one of the projects my teacher gave me was writing a log-in simulator.
The next Internet could be in the making somewhere in someone's lab.
I also administer the Internet Assigned Names Authority, which is the central coordinator for the Internet address space, domain names and Internet protocol conventions essential to the use and operation of the Internet.
It's incredibly hard to program a network from scratch for 24 hours.
It doesn't matter if it's a wireless or wired network. I think network management can be introduced that is equally sensible.
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.
I go back to when we met with the late Steve Jobs. He couldn't understand why we didn't put Wi-Fi in every cable set box. And I literally went home and said, 'Tell me again - what's Wi-Fi?'
Berners-Lee started the World Wide Web as a set of protocols for transferring, linking and addressing documents to send over the Net. Without the global reach and open technical standards of the Internet, the Web could never have proliferated as it did.
When I helped to develop the open standards that computers use to communicate with one another across the Net, I hoped for but could not predict how it would blossom and how much human ingenuity it would unleash.
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.
The ARPAnet was the first transcontinental, high-speed computer network.
TCP implementations will follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others.