TCP/IP History

1970 – ARPANET started using Network Control Protocol

1972 – Telnet was implemented 1973 – FTP was introduced 1974 – TCP was specified 1981 – IP was specified 1983 – ARPANET changed to TCP/IP 1984 – DNS was introduced 1993 – WWW invented

Internet Growth Trends 1977: 111 hosts on Internet 1981: 213 hosts 1983: 562 hosts 1984: 1,000 hosts 1986: 5,000 hosts 1987: 10,000 hosts 1989: 100,000 hosts 1992: 1,000,000 hosts 2001: 150 – 175 million hosts 2002: over 200 million hosts By 2010, about 80% of the planet will be on the Internet

A Brief Summary of the Evolution of the Internet

1945

Memex Conceived

1945

WWWCreated

1989

MosaicCreated

1993

A Mathematical

Theory of Communication

1948

Packet Switching Invented

1964

SiliconChip1958

First Vast ComputerNetwork

Envisioned1962

ARPANET1969

TCP/IPCreated

1972

InternetNamed

and Goes

TCP/IP1984

HypertextInvented

1965

Age ofeCommerce

Begins1995

The Ever-changing Internet

Different colors based on IP addresshttp://research.lumeta.com/ches/map

The Internet Standard Process The Internet Society (ISOC). A group of volunteers

who manages the standards of TCP/IP The Internet Architecture Board (IAB) is the

technical advisory group of ISOC, and responsible for setting standards, publishing RFCs and overseeing the Internet Standards process.

RFCs. A document written by anyone, a standard suggestion, read and tested by the ISOC. Each RFC is assigned a number. A RFC is never updated, but a new RFC is created.

RFC Classifications

Required. Must be implemented on all TCP/IP-based hosts and gateways.

Recommended. It’s encouraged that this is implemented.

Elective. Limited use. Not a general

implementation. Not recommended. Must not be

implemented.

RFC Maturity level

Proposed Standard. Valuable, due to the interest from the community

Draft Standard. Stable and good. Internet Standard. A significant

benefit to the Internet.

TCP/IP protokolu kopa

TCP/IP un ISO OSI modelis

TCP/IP un Internets

RFC 1-3542http://www.faqs.org/rfcs/

RIPE, ARIN, APNICICANN

IPv4 pakete: RFC 791 (1981)

Ver.

Time toLive

Source Address

Total LengthType ofService

HdrLen

Identification FragmentOffsetFlg

Protocol HeaderChecksum

Destination Address

Options...

IPv4 pakete: RFC 791 (1981)

Type of Service (TOS)Precedence

DiffServ – QoS mehānismsIP telefonija (VoIP)Video Streamingetc.

IP paketes fragmentēšana

Protokoli

IP Opcijas

Security - the data field may be encrypted, or made accessible only to a specified user group

Source Routing - If known, the actual route to be followed through the network may be specified as a list of routers

Route Record - records the addresses of the routers visited by the datagram

Stream Identification - allows source to indicate the type of data being carried - samples of speech

Timestamp - the source and intermediate routers add a timestamp to the data

IPv6 Pakete: RFC 1883 (1995)

Ver.

Time toLive

Source Address

Total LengthType ofService

HdrLen

Identification FragmentOffsetFlg

Protocol HeaderChecksum

Destination Address

Options...

Ver. TrafficClass

Source Address

Payload Length NextHeader

HopLimit

Destination Address

HdrLen

Identification FragmentOffsetFlg

HeaderChecksum

Options...

shaded fields have no equivalent in theother version

IPv6 header is twice as long (40 bytes) asIPv4 header without options (20 bytes)

Flow LabelFlow Label

FEDC:BA98:7654:3210:FEDC:BA98:7654:3210

1080:0:0:0:8:800:200C:417A

Q1

Q2

Q3

Q4

2007Q1

Q2

Q3

Q4

2004Q1

Q2

Q3

Q4

2003Q1

Q2

Q3

Q4

2000Q1

Q2

Q3

Q4

2001Q1

Q2

Q3

Q4

2002Q1

Q2

Q3

Q4

2005Q1

Q2

Q3

Q4

2006

IPv6 Timeline

Consumer adoption <= Dur. 5+ yrs.Consumer adoption <= Dur. 5+ yrs. =>=>

Early adopterEarly adopter

Appl. Porting <= Duration 3+ yrs.Appl. Porting <= Duration 3+ yrs. =>=>

Enterprise adopt.Enterprise adopt.<= 3+ yrs. <= 3+ yrs. => =>

adoption <= Dur. 3+ yrs.adoption <= Dur. 3+ yrs. ISPISP =>=>