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 Age of eCommerce Begins 1995 Mosaic Created 1993 WWW Created 1989 Internet Named and Goes TCP/IP 1984 TCP/IP Created 1972 ARPANET 1969 Hypertext Invented 1965 Packet Switching Invented 1964 First Vast Computer Network Envisioned 1962 Silicon Chip 1958 A Mathematical Theory of Communication 1948 Memex Conceived 1945 1945

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 RIPE, ARIN, APNIC ICANN 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. Time to Live Source Address Total Length Type of Service Hdr Len Identification Fragment Offset Flg Protocol Header Checksum Destination Address Options...

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

Ping options C:\NET>tracert www.delfi.lv 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 Options: -t Ping the specified host until stopped. To see statistics and continue - type Control-Break; To stop - type Control-C. -a Resolve addresses to hostnames. -n count Number of echo requests to send. -l size Send buffer size. -f Set Don't Fragment flag in packet. -i TTL Time To Live. -v TOS Type Of Service. -r count Record route for count hops. -s count Timestamp for count hops. -j host-list Loose source route along host-list. -k host-list Strict source route along host-list. -w timeout Timeout in milliseconds to wait for each reply. C:\NET> 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 12 ms 12 ms 11 ms 81.198.214.1 2 12 ms 11 ms 12 ms iveta.tkom.lv [195.122.1.65] 3 12 ms 12 ms 11 ms iveta.tkom.lv [195.122.1.65] 4 12 ms 12 ms 12 ms 195.122.6.27 5 12 ms 12 ms 12 ms 195.122.6.102 6 12 ms 16 ms 15 ms 62.85.40.225 7 25 ms 14 ms 12 ms 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

IPv6 Pakete: RFC 1883 (1995) Ver. Traffic Class Flow Label Flow Label Hdr Len Hdr Len Type of Service Total Length Payload Length Next Header Hop Limit Identification Identification Flg Flg Fragment Offset Fragment Offset Source Address Time to Live Protocol Header Checksum Header Checksum Source Address Destination Address FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 Options... Options... Destination Address shaded fields have no equivalent in the other version IPv6 header is twice as long (40 bytes) as IPv4 header without options (20 bytes) 1080:0:0:0:8:800:200C:417A

IPv6 Timeline Q1 Q2 Q3 Q4 2007 2004 2003 2000 2001 2002 2005 2006 Early adopter Appl. Porting <= Duration 3+ yrs. => adoption <= Dur. 3+ yrs. ISP => Consumer adoption <= Dur. 5+ yrs. => Enterprise adopt. <= 3+ yrs. =>