1. 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

2. 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

3. A Brief Summary of the Evolution of the Internet 1945 Memex Conceived 1945 WWW Created 1989 Mosaic Created 1993 A Mathematical Theory of Communication 1948 Packet Switching Invented 1964 Silicon Chip 1958 First Vast Computer Network Envisioned 1962 ARPANET 1969 TCP/IP Created 1972 Internet Named and Goes TCP/IP 1984 Hypertext Invented 1965 Age of eCommerce Begins 1995

4. The Ever-changing Internet Different colors based on IP address http://research.lumeta.com/ches/map

5. 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.

6. 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.

7. 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.

8. TCP/IP protokolu kopa

9. TCP/IP un ISO OSI modelis

10. TCP/IP un Internets RFC 1-3542 http://www.faqs.org/rfcs/ RIPE, ARIN, APNIC ICANN

11. 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...

12. IPv4 pakete: RFC 791 (1981)

13. Type of Service (TOS) Precedence DiffServ – QoS mehānisms IP telefonija (VoIP) Video Streaming etc.

14. IP paketes fragmentēšana

15. Protokoli

16. 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

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

18. Q1Q1 Q2Q2 Q3Q3 Q4Q4 2007 Q1Q1 Q2Q2 Q3Q3 Q4Q4 2004 Q1Q1 Q2Q2 Q3Q3 Q4Q4 2003 Q1Q1 Q2Q2 Q3Q3 Q4Q4 2000 Q1Q1 Q2Q2 Q3Q3 Q4Q4 2001 Q1Q1 Q2Q2 Q3Q3 Q4Q4 2002 Q1Q1 Q2Q2 Q3Q3 Q4Q4 2005 Q1Q1 Q2Q2 Q3Q3 Q4Q4 2006 IPv6 Timeline Consumer adoption <= Dur. 5+ yrs. Consumer adoption <= Dur. 5+ yrs. => => Early adopter Early adopter Appl. Porting <= Duration 3+ yrs. Appl. Porting <= Duration 3+ yrs. => => Enterprise adopt. Enterprise adopt. adoption <= Dur. 3+ yrs. ISP ISP => =>