Top Banner
Internet History w.internetsociety.org/internet/what-internet/history-internet/brief-history- ternet Timeline https://tools.ietf.org/html/rfc2235
27

Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Mar 28, 2015

Download

Documents

Julissa Pascoe
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Internet History

http://www.internetsociety.org/internet/what-internet/history-internet/brief-history-internetHobbes Internet Timeline https://tools.ietf.org/html/rfc2235

Page 2: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

The history of the Internet is the story of people and their ideas, and the projects they worked on.It is not the story of any one person or projectIt is not the story of any single application,

whether electronic mail, remote login, file transfer, the web, video, or machine-to-machine communication

Or even of ICANN or the IANAHowever, many people and projects made

important contributions.This is an attempt at the story

People, ideas, projects, and applications

Page 3: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

The original concept: Survivable networks

Page 4: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Leonard Kleinrock wrote on packet switching conceptsSubsequently convinced Larry Roberts to look

at packet switching as an alternative to circuit switching

His logic:If the strength of a chain is that of its weakest

link,Then the strength of a network is the strength

of its last surviving path

1961:

Page 5: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

J.C.R. Licklider’s (MIT) "Galactic Network" conceptHe envisioned a globally interconnected set of

computers through which everyone could quickly access data and programs from any site.

“Wouldn’t it be cool if one could walk up to a computer

and find the knowledge of the universe at our fingertips?

1962:

Page 6: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Paul Baran at RAND independently suggested that a packet-based network might be a useful way to build a survivable voice network,

Baran was the one that suggested we call them “packets”. We do.

Also 1962:

Page 7: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Roberts and Merrill connected two computers – and found circuit switched analog telephone inadequate for their purposes

1965:

Page 8: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Larry Roberts, DARPA program manager, started research on the concept of packet networking

1967:

Page 9: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Roberts issued an RFP for research, which was soon awarded to BBN

The network BBN developed, called the ARPANET, had its first node with UCLA and Len KleinrockThe second node was at SRI

The first packet to cross the network went from UCLA to SRI – an attempt to log into a computer

1968:

Page 10: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

The RFC Series was originated as a way to share notes among researchers – Steve CrockerThe notes were called “Requests for

Comments” in an attempt to downplay their importance.

Later, vendors would joke that they were “Requirements for Compliance”, e.g., specificationsMany were in fact white papers, thoughts

about what might be – and what might in the end not be - blind alleys…

The ruminations of a a far-flung distributed research laboratory on topics they were just working out

1969:

Page 11: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Synchronous “start/stop” protocol patented 1966

IBM 3780/2780 Binary Synchronous Communication

IBM 3270 Binary Synchronous Communication

HDLC/SDLC development

Context: fledgling communications

Page 12: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Early transmission protocols had crude ways, if any, to identify and recover from errorsMaster/SlavePoll/CallHalf Duplex (two way alternate)

SDLC/HDLC made a giant step forwardFull Duplex (two way simultaneous)Using a sliding window, it could keep data

being transmitted (or retransmitted) in one direction while being acknowledged in the other, and in LAPB, data continuously in transit in both directions.

Sliding Windows

Page 13: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

NCP prototyping and deployment on the ARPANET

ALOHA, a satellite network based on random or semi-random transmission

1970:

Page 14: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

1972Louis Pouzin invented the datagram:

A packet that contains all necessary state within itself and so depends on no external network state

Operating on a best-effort basis – it may be lost, duplicated, or reordered in flight

Page 15: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Robert Kahn demonstrated the fledgling ARPANET at ICCC

The application that he demonstrated: Ray Tomlinson’s electronic mailkiller@application

Original telnet (remote login) specification (RFC 318)John Postel

Also 1972:

Page 16: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Each distinct network would have to stand on its own: No internal changes could be required to any such network to

connect it to the Internet.Communications would be on a best effort basis.

If a packet didn't make it to the final destination, it would shortly be retransmitted from the source.

Black boxes (IMPs) would be used to connect the networks; These would later be called gateways and routers. Gateways retained no per-flow state, thereby keeping them

simple and avoiding complicated adaptation and recovery from various failure modes.

There would be no global operational control. Sites were by definition autonomous. The only protocols they

had to implement were IP and ICMP, and maybe TCP and UDP

Kahn’s Ground Rules

Page 17: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

The original protocol combined the services of what we today call “TCP” and “IP”.

It worked well for file exchange and remote access to time-sharing systems, But not some other applications, for which

application control was more importantThe 1978-1981 update process:

Separated TCP from IPv4 (RFC 791, 792, 793)Added UDP for applications that needed it

Electronic mail, remote login, and file exchange remained the “killer applications” for two decades or more

1973 and on: Kahn/Cerf and TCP

Page 18: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Development of concepts for a random local area network (one that didn’t cross a legal boundary) by Bob Metcalf

That was experimented with at Xerox PARC (PupNet)

Resulted in the DEC, Intel, and Xerox specification for the Ethernet, 1981

Starting in 1973:

Page 19: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

BBN Telenet: first commercial packet data service

1974:

Page 20: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

January 1, 1983:Cut-over from NCP to TCP/IPv4

1984:Deployment of the Domain name SystemReplaced centrally-managed “hostfile” with a

distributed and recursive system for namingNames originally translated simply to IP

addresses or lists of names of mail servers

Early 1980’s

Page 21: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

And then Al Gore…Circa 1984, the junior

senator from Tennessee started discussing his ideas of an “Information Superhighway”.

He had five NSF-sponsored supercomputer centers, and he wanted to connect universities to them

NSF-funded IP networking experiments:CSNET: an X.25 networkUSAN: a wide area

Ethernet network over satellite

56 KBPS NSFNETOther networks:

NASA Science InternetCYCLADESCERN networksBITNET……Got Money

Page 22: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

The NSFNET grew dramatically, as universities bought routers and connected first to it and then each otherChanged successively from 56 KBPS to T-1 to T-

3States or other agencies built regional

networks that connected to it: NEARNet, BARRNET, PSINET, NYSERNET, and many others

Regional networks

Page 23: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

1990: the ARPANET Core, having become irrelevant after 22

years of operation, was shut down Formation of the IANA at USC/ISIRecognition that IPv4 would eventually run out of

address space – starting work on CIDR and IP Next Generation

Initial formation of Regional Internet RegistriesARIN, RIPE, APNICLACNIC and AfriNIC came later

Succeeding years:Many regional networks in time became commercial

networks.And in turn replaced the NSFNET as the core network

Commercialization of the backbone

Page 24: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

These existed in the 1980’s, interconnecting LANs (subnet and host)SNADECNETAppleTalkXNS Internet Transport

XNS 3COM Ungermann-Bass Banyan Vines Novell Netware

MIT ChaosnetSytek NetBIOSothers

Connection-Oriented and Connectionless OSIAddress (NSAP) identifies

network, subnet, and host

IPv4Originally identified

network, subnet, and host

With CIDR (1992), could aggregate networks to identify service providers

Competing network technologiesThese existed and could interconnect companies

Page 25: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Every 3-5 years, the Internet fundamentally changes in the payload it carries 1970-1990: SMTP, FTP, Network News, telnet 1992: World Wide Web, multicast, experimental voice/video 1995: WWW with multiple sessions in parallel, commercial Voice on IP 2000: Peer to Peer file sharing in various forms 2003: Web 2.0 applications like MySpace, Facebook, BitTorrent File Sharing 2008: Cyberlockers replacing file sharing 1990-present: Rise of video in various forms Lately: Map/Reduce and Hadoop – data center distributed applications Next…

Not that old payloads go away: we add new and sometimes dominant payloads in addition to the old

On the commercial backbone, video is becoming dominant, primarily from Content Providers that colocate with an ISP’s POPs or data centers

In private networks (Smart Grid, Health Care, public and private safety, industrial automation) we see distributed telemetry and distributed control.

Changing applications

Page 26: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

The structurePerhaps 10,000 networks

offering communication or content services to others

Roughly another 50,000 networks interconnected using BGP routing

Billions of users world-wide

The primary service of the network is connectivity. The Internet thrives on

innovation, and fosters it.

Each distinct network is autonomous

Communications is on a best effort basis.

Routers are used to connect the networks;

There is no global operational control.

The Internet in 2013

Kahn’s principles:

Page 27: Http:// Hobbes Internet Timeline //tools.ietf.org/html/rfc2235.

Internet History

http://www.internetsociety.org/internet/what-internet/history-internet/brief-history-internetHobbes Internet Timeline https://tools.ietf.org/html/rfc2235