Download TCP/IP protokolu kopa

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
First Vast
Computer
Network
Silicon Envisioned
Chip
A
1962
Mathematical 1958
Theory of
Communication
Memex
1948
Conceived
1945
1945
Packet
Switching
Invented
1964
Hypertext
Invented
1965
TCP/IP
Created
ARPANET
1972
1969
Mosaic
Created
WWW
Internet Created
1993
Named
1989
and
Goes
TCP/IP
1984
Age of
eCommerce
Begins
1995
The Ever-changing Internet
Different colors based on IP address
http://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 un Internets
RFC 1-3542
http://www.faqs.org/rfcs/
RIPE, ARIN, APNIC
ICANN
TCP/IP protokolu kopa
TCP/IP un ISO OSI modelis
IPv4 pakete: RFC 791 (1981)
Ver.
Hdr
Len
Type of
Service
Identification
Time to
Live
Total Length
Flg
Protocol
Source Address
Destination Address
Options...
Fragment
Offset
Header
Checksum
IPv4 pakete: RFC 791 (1981)
Type of Service (TOS)
Precedence
DiffServ – QoS mehānisms
IP telefonija (VoIP)
Video Streaming
etc.
IP paketes
fragmentēšana
Protokoli
IP Opcijas




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
C:\NET>ping
Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] target_name
Ping options
C:\NET>tracert www.delfi.lv
Tracing route to www.delfi.lv [195.2.123.94]
over a maximum of 30 hops:
1
2
3
4
5
6
7
12
12
12
12
12
12
25
ms
ms
ms
ms
ms
ms
ms
12
11
12
12
12
16
14
ms
ms
ms
ms
ms
ms
ms
11
12
11
12
12
15
12
ms
ms
ms
ms
ms
ms
ms
Options:
-t
-a
-n
-l
-f
-i
-v
-r
-s
-j
-k
-w
count
size
TTL
TOS
count
count
host-list
host-list
timeout
C:\NET>
81.198.214.1
iveta.tkom.lv [195.122.1.65]
iveta.tkom.lv [195.122.1.65]
195.122.6.27
195.122.6.102
62.85.40.225
rev2.delfi.lv [195.2.123.94]
Trace complete.
C:\NET>ping -r 9 www.delfi.lv
Pinging www.delfi.lv [195.2.123.94] with 32 bytes of data:
Reply from 195.2.123.94: bytes=32 time=17ms TTL=58
Route: 62.85.40.227 ->
195.2.123.65 ->
195.2.123.94 ->
62.85.40.225 ->
195.122.6.109 ->
195.122.1.65
Reply from 195.2.123.94: bytes=32 time=21ms TTL=58
Ping the specified host until stopped.
To see statistics and continue - type Control-Break;
To stop - type Control-C.
Resolve addresses to hostnames.
Number of echo requests to send.
Send buffer size.
Set Don't Fragment flag in packet.
Time To Live.
Type Of Service.
Record route for count hops.
Timestamp for count hops.
Loose source route along host-list.
Strict source route along host-list.
Timeout in milliseconds to wait for each reply.
IPv6 Pakete: RFC 1883 (1995)
Ver. Traffic
Class
Payload Length
Flow Label
Next
Header
Hop
Limit
Hdr Type of
Ver. Len
Service
Identification
Time to Protocol
Live
Total Length
Flg
Fragment
Offset
Header
Checksum
Source Address
Source Address
FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
Destination Address
Options...
Destination Address
1080:0:0:0:8:800:200C:417A
shaded fields have no equivalent in the
other version
IPv6 header is twice as long (40 bytes) as
IPv4 header without options (20 bytes)
IPv6 Timeline
2000
2001
2002
2003
2004
2005
2006
2007
Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q
1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
Early adopter
Appl. Porting <= Duration 3+ yrs.=>
ISP adoption <= Dur. 3+ yrs.=>
Consumer adoption <= Dur. 5+ yrs.
=>
Enterprise adopt.<= 3+ yrs.
=>