Escolar Documentos
Profissional Documentos
Cultura Documentos
Overview
Example:
Sending a letter . .
Protocol
Reference Models
Edited by Ted E. Lee Copyright 2008 Ted E. Lee
6
Details
Edited by Ted E. Lee Copyright 2008 Ted E. Lee
7
how to use interface to Layer 4 content requirement for receiving Layer 5 User doesnt see beyond Layer 5 Source and destination layers of similar levels dont see whats going on between themselves Analogous to using telephone: You need to know
how to use telephone & receivers telephone number message content to send receiver The rest can be ignored
like foreign diplomacy of 17th century
Source-destination communication:
10
11
Protocols defining the electrical, mechanical, and procedural specifications for data transmission e.g., RS232-C specification for serial transmission Reliability of physical layer; error detection & control for point-to-point connections (next adjacent node) e.g., pre-determined frame layouts in an installed NIC.
2. Data link
12
Data Link Layer: Framing with counts A character stream separated by frame counts
(a) Without errors (b) With one error.
14
The OSI Reference Model 3. Network: Choosing, starting, and terminating end-to-end
network connections along data route for a series of independent packets (connection-less) --transparently!
4. Transport:
Reliability between systems; error detection and control Ensures all of the packets are arriving in the proper order (connection-oriented, sequence numbers for packets) differentiates between applications at each end of a connection (e.g., Telnet and WWW sessions)
15
7. Application
HTTP DNS (Domain Name Service) resolves a domain name to IP a specific IP address. FTP, Telnet
16
Data Format
Enabling Technology
17
18
TCP/IP Suite
19
A Critique of the OSI Model and Protocols A Critique of the TCP/IP Reference Model
21
Bad timing:
The TCP/IP protocols were already in widespread use by research universities by the time the OSI protocols appeared.
Choice of 7 layers was more political than technical Two of the top layers (session and presentation) are nearly empty, whereas two other ones (data link and network) are overfull. Too complex to follow
TCP/IP was thought of as part of UNIX (felt comfortable in academia) Considered as product of Europeans
Problems
Service, interface, and protocol not distinguished Not a general model Network access layer is not really a layer No mention of physical and data link layers Minor protocols deeply entrenched, hard to replace
23
Hybrid Model
24
25