160 likes | 283 Views
Chapter Objectives. After completing this chapter you will be able to: Describe the history of TCP/IP Describe the history of the Internet Outline the different functions of the Internet organisations (IAB, IETF, IRTF, IANA) Describe Request for Comments (RFCs) Outline the OSI 7-layer model
E N D
Chapter Objectives After completing this chapter you will be able to: • Describe the history of TCP/IP • Describe the history of the Internet • Outline the different functions of the Internet organisations (IAB, IETF, IRTF, IANA) • Describe Request for Comments (RFCs) • Outline the OSI 7-layer model • Outline the TCP/IP protocol stack
History of TCP/IP • 1969: ARPANET went into operation • four packet-switched nodes at three different sites • connected together via 56 kbit/s circuits • using the Network Control Protocol (NCP) • funded by the U.S. Department of Defence • 1974: TCP/IP designed by Vinton G. Cerf and Robert E. Kahn • 1979: IP version 4 documented
History of TCP/IP (Contd) • 1979: the Internet Control and Configuration Board (ICCB) formed • 1979: BSD Unix with TCP/IP supplied to Universities • 1980: ARPA started converting machines to TCP/IP • 1983: mandate that all computers connected to ARPANET use TCP/IP • 1983 ARPANET split into two separate networks, • ARPANET for further research • MILNET for the military
History of the Internet • 1985: the ARPANET was heavily used and congested • 1986: NSFNET developed to replace ARPANET • universities and research organisations connected to regional networks • regional networks connected to a main backbone • six nationally funded super-computer centres connected to backbone • The original links were 56 kbit/s. • 1988: Links upgraded to T1 (1.544 Mbit/s) • The NSFNET T1 backbone connected a total of 13 sites • 1991: NSF decided to move the backbone to a private company • 1993: New Internet backbone, ANSNET, with T3 (45 Mbit/s) links • 1993: Final NSF solicitations
Today'sInternet • Distributed architecture operated by commercial Network Service Providers (NSPs) • Connected together at Network Access Points (NAPs) • high-speed switch to which a number of routers can be connected for the purpose of traffic exchange • allows Internet traffic from the customers of one provider to reach the customers of another provider. • ISPs provide Internet services to end customers • Connection point between a customer and an ISP is called a point of presence (POP) • ISP networks exchange information with each other by connecting to NSPs that are connected to NAPs, or by connecting directly to NAPs
vBNS Backbone Network Map Seattle R Ameritech NAP Boston Cleveland R National Center for Atmospheric Research Chicago New York City R R R R Sprint NAP R R Perryman, MD R Pittsburgh Supercomputing Center San Francisco R Denver R R National Center for Supercomputing Applications R Washington, DC R Los Angeles MFS NAP R R R Atlanta San Diego Supercomputer Center R DS-3 OC-3C OC-12C OC-48 R Houston Router ATM Switch NAP R
Internet Architecture Board (IAB) Organisation The IAB organisation The IAB Board IRTF IETF IRSG IESG Working groups Research groups
Active IETF Working Groups • Applications • Internet • Operations and Management • Routing • Security • Transport • User services • General
Internet Research Task Force • Active IRTF Research Groups • End-to-End • Information Infrastructure Architecture • Internet Resource Discovery • Network Management • Reliable Multicast • Routing • Secure Multicast • Services Management
Internet Assigned Number Authority (IANA) IANA ARIN American Registry for Internet Numbers RIPE Reseaux IP Europeen APNIC Asia Pacific Network Information Centre
RFC Standards Track Process Draft Paper IESG recommends promotion to proposed standard. RFC publishes as RFC. Otherwise it is sent back to the IETF work group. RFC Spec Proposed Standard Review by IETF and IESG not to exceed two years Implementation and test for a minimum of 6 months Draft Standard Evaluation of implementation for a minimum of 4 months Standard
Important RFCs STD Number RFC Number Name 1 2500 Internet Official Protocol Standards 2 1700 Assigned Numbers 3 1122 1123 Requirements for Internet hosts 4* 1812 Requirements for IP Version 4 Routers www.rfc-editor.org/rfc.html
APPLICATION PRESENTATION SESSION TRANSPORT NETWORK DATA LINK PHYSICAL OSI 7- Layer Model Interfaces directly with application programs running on the devices. Provides code conversion and data reformatting. Co-ordinates interaction between end-to-end application processes. Provides end-to-end data integrity and quality of service. Switches and routes information to the appropriate network device. Transfers units of information to the other end of the physical link. Transmits/Receives on the network medium
OSI 7- Layer Model and Internetworking Devices SYSTEM B SYSTEM A Data Data A A P Data P Data Data Data S S T Data T Data Router Data Data N N Bridge/Switch Data Data D D Repeater 101100011110101010010 101100011110101010010
Internet Protocol Suite and OSI Reference Model APPLICATION APPLICATION (FTP, TELNET, SNMP, DNS, SMTP ) PRESENTATION SESSION TRANSPORT TRANSPORT (TCP or UDP) NETWORK INTERNET PROTOCOL (IP) ICMP, IGMP ARP, RARP DATA LINK NETWORK INTERFACE (LAN - ETH, TR, FDDI) (WAN - Serial lines, FR, ATM) PHYSICAL
TCP/IP Protocol Stack Based on Data Flow Application Layer Telnet, FTP, TFTP,HTTP,SNMP,SMTP, and so on Port Number BGP RIP Transport Layer OSPF EGP TCP UDP ICMP IGMP Protocol Number Internet Layer ARP IP RARP Type code Data Link Layer Ethernet, Token Ring, PPP, and so on