This document provides an introduction to the topics that will be covered in an engineering course on internetworking. It discusses the basics of data networking and how TCP/IP allows different networks to interconnect. It describes the layered architecture of internet protocols and references the ISO 7-layer model. It provides a brief history of the development of the Internet and organizations like ARPA, NSF, IAB, IETF, and RFCs.
This document provides an introduction to the topics that will be covered in an engineering course on internetworking. It discusses the basics of data networking and how TCP/IP allows different networks to interconnect. It describes the layered architecture of internet protocols and references the ISO 7-layer model. It provides a brief history of the development of the Internet and organizations like ARPA, NSF, IAB, IETF, and RFCs.
This document provides an introduction to the topics that will be covered in an engineering course on internetworking. It discusses the basics of data networking and how TCP/IP allows different networks to interconnect. It describes the layered architecture of internet protocols and references the ISO 7-layer model. It provides a brief history of the development of the Internet and organizations like ARPA, NSF, IAB, IETF, and RFCs.
This document provides an introduction to the topics that will be covered in an engineering course on internetworking. It discusses the basics of data networking and how TCP/IP allows different networks to interconnect. It describes the layered architecture of internet protocols and references the ISO 7-layer model. It provides a brief history of the development of the Internet and organizations like ARPA, NSF, IAB, IETF, and RFCs.
Computer Engineering Stevens Institute of Technology Chapter 1
Introduction d i to Internetworking ki Introduction to Internetworking
• Data networking: g sharingg information,, sharingg media.
• Internet becomes a necessity. • Various networks have been setup with various characteristics and for various purposes. • Internetworking connects heterogeneous networks, hides details of network hardware, hardware allows computers to communicate independent of their physical network connections. Internet Technology
• Internet technology gy resulted from Advanced Research Projects Agency (ARPA). • TCP/IP technology particular fits very large scale networks – the th ARPA/NSF IInternet, t t th the TCP/IP IInternet, t t th the global l b l Internet or the Internet all refer to the same network. • TCP/IP C / Internet te et Protocol otoco Suite Su te for o data communications co u cat o s across any set of interconnected networks. (Not necessary pass through the global Internet.) • Networks N i TCP/IP ≠ the k using h global l b l Internet. I Internet Service
• Protocols for communication is what algorithms
g for computing. • Protocols: the syntactic and semantic rules for data communication. i ti • Protocol describes: message format, how to transmit and/or respond espo d messages, essages, how ow to handle a d e eerrors. o s. • Advantages of high-level abstraction: programmers can quickly create new programs; programs will not be restricted i d to a particular i l architecture, hi same code d can be b compiled and run on different machines; applications can communicate between arbitraryy ppair of computers. p Internet Services
• Each internetworkingg service is pprovided byy a separate
p protocol. Examples: – Application level: services for users — www, email, ft telnet, ftp, t l t http htt – Transport level: services for application programs — connectionless co ect o ess pac packet et de delivery ve y services se v ces (U (UDP),), reliable e ab e stream transport service (TCP). Internet Services
• Differences between TCP/IP services and other network
services: – Independent network technology. TCP/IP protocols define the unit of data transmission (datagram) and specify the way to transmit them on particular networks. – Universal interconnection interconnection. TCP/IP internetwork assigns a universal address to each computer (IP address), and each datagram carries the addresses of its source and destination. destination – End-to-end acknowledgements. – Application pp pprotocol standards. Internet History
• 1977-1979,, Advanced research pprojects
j agency g y (ARPA), ( ), ARPANET • 1979-1983, Internet control and configuration board (ICCB) ARPANET bbecomes bbackbone (ICCB), kb off th the Internet. I t t • 1983, Berkeley software distribution of UNIX and TCP/IP – soc socket, et, aan operating ope at g system syste abstraction abst act o allows a ows application programs to access communication protocols. • 1986, NSF, NSFNET, regional networks • 1986, ARPANET tied with NSFNET • 1987, Domain name system (DNS) Internet Architecture Board
• Internet Architecture Board ((IAB)) sets the technical
direction and decides which and when protocols become standard. • IAB formed in 1983 from ICCB. It had several Internet Task Forces. It shifted from ARPA group to an autonomous organization. Volunteers performed much of the work. work • By 1989, commercial production and market place overcame researches and dominated the evolution of Internet. Internet • IAB reorganized with Internet Research Task Force (IRTF) and Internet Engineering Task Force (IETF). Internet Architecture Board
• IETF: concentrates on short-term to medium-term
engineering problems. It is managed by the Internet Engineering Steering Group (IESG), with about ten areas. • IRTF: IRTF coordinates di t researchh activities ti iti related l t d to t Internet I t t architecture in general. It is managed by the Internet Research Steering Group (IRSG). • Internet Society (ISOC), an independent society organized and the new host for the IAB since 1992. Request For Comments
• Internet documentation of pprotocols,, standards and policies
p are posted on-line and can be accessed at no charge. • Internet Request For Comments (RFCs) are documents about b t worksk on the th Internet, I t t proposals l for f new or revised i d protocols and TCP/IP protocol standards. They are edited and approved by IESG. • RFCs have the status of industrial standard. • Internet Drafts (IDs) are preliminary versions of RFC documents. Future Growth and Technology
• Significant g changes: g traffic loads,, traffic ppatterns and services.
• Bandwidth increases, demands increases.
• Distributed Di t ib t d operation ti andd management. t Chapter 10
Protocoll Layering i Multiple Protocols
• Multiple p pprotocols needed to handle different pproblems: – Hardware failure – Routing – Network congestion – Packet delay and loss – Data corruption – Data duplication and out-of-order Layers of Protocols
• The conceptual p organization g of pprotocol software in layers. y (Figure 10.1) Layers of Protocols
• The ppath of a message
g over the IP network. ((Figure g 11.3)) ISO 7-Layer Reference Model
• ISO Reference Model of Openp System
y Interconnection (OSI). (Figure 11.4) – It is a conceptual model, not an implementation guide. – This Thi model d l is i honored h d in ITU X.25 (connection oriented) (connection-oriented) network p implementation. ISO 7-Layer Reference Model
• Physical y Layer y ((layer y 1):) pphysical y interconnection between host computers and network switches. Data unit = raw bits. • Data Link Layer (layer 2): data transfer between host and switch it h – error detection, d t ti ACK.ACK Data D t unitit = frame. f • Network Layer (layer 3): interactions between host and network etwo – data unit, u t, addressing, add ess g, routing, out g, congestion co gest o control. Data unit = packet. • Transport Layer (layer 4): end-to-end reliable data transfer – ensure no noded failure. f il ISO 7-Layer Reference Model
• Session Layer y ((layer y 5): ) remote terminal access – terminal to host interconnection, uni- or bi-directional dialogue control, synch for file transfer. • Presentation P t ti Layer L (l (layer 6): 6) syntax t andd semantics ti conversions for applications – data codecs. • Application pp cat o Layer aye ((layer aye 7): application app cat o programs. p og a s. Inter-Layer Interactions TCP/IP 5-Layer Reference Model
• TCP/IP Reference Model. ((Figure
g 10.5)) TCP/IP 5-Layer Reference Model
• Five conceptual p layers: y four software layer y and one hardware layer. – Network Interface Layer: accepting IP datagrams and transmitting them over specific network. Data unit = frame. – Internet Layer: communications between two machines – datagram formation formation, addressing and routing, routing ICMP control. Data unit = datagram. – Transport Layer: end-to-end communication – flow control, l reliable li bl transfer f (ACK andd ARQ). ARQ) Data D uniti = (transport protocol) packet. – Application pp Layer: y application pp pprograms. g Difference Between ISO and Internet Layering
• Comparisons p are made based on implementations, p , i.e. X.25 for ISO model, Internet for TCP/IP model. • Reliable transfer: – X.25: error detection and handling at all layers. – Internet: consider it as an end-to-end problem at transport layer. Simplifies network interface layer and internet layer – unreliable data link. • Authority and Control: – X.25: network vendor has all the authority and controls on network access and traffic monitoring – routing, flow control internal ACK, reliable transfer – hosts can do little. – Internet: hosts have to participate in most of network protocols. Protocol Layering Principle
• Layering y g pprinciple: p layered y pprotocols are designed g so that layer n at the destination receives exactly the same object sent by layer n at the source. – It allows protocol designer to focus attention on one layer at a time. – Software program at one layer on one host only talks to the software program at the same layer on the other host. • Layering in a TCP/IP internet environment. – Transport layer and Application layer: end-to-end transfer – Internet Layer and Network Interface: hophop-to-hop to hop Protocol Layering Principle
• Layering y g in IP network. ((Figure g 10.7)) Two Important Boundaries in The TCP/IP Model
• Important p boundaries in the TCP/IP Model. (Figure ( g 10.9)) Two Important Boundaries in The TCP/IP Model
• High-level g pprotocol address boundary. y – Application programs and all protocol software from Internet layer upward use only IP addresses. – The network interface layer handles physical addresses. • Operating System Boundary. – Application A li ti programs are outside t id the th operating ti system. t – Protocol software programs are inside the operating system. y • Passing data between lower layers of protocol software is much easier than passing data between th application the li ti layer l andd the th transport t t layer. l Disadvantages of Layering
• Software based on strict layering
y g can be extremelyy inefficient. – Communications only through horizontal directions – th same layer the l talk t lk to t the th same layer l att different diff t hosts. h t – Vertical information exchange is not allowed except passingg data. pass • Optimizations can be made by introducing limited interlayer information exchange.
