1. Layered Standards Architectures
Chapter 2
Panko’s Business Data Networks and Telecommunications, 5th edition Copyright 2005 Prentice-Hall

2. Standards
Def: Rules of operation that allow two hardware or software processes to work together
Standards govern the exchange of messages:
Semantics (meanings of messages)
Syntax (structure of messages)
Timing (when stations may transmit, etc.)

3. Figure 2-2: Hypertext Transfer Protocol (HTTP) Interactions1.
HTTP Request Message
Asking for a File
Browser
Webserver
Application
Client PC
Webserver 2.
HTTP Response Message
Delivering the File

4. Figure 2-1: How Standards Govern Interactions, Continued
Message Syntax (Organization)
Cannot be freely structured like human sentences
Rigidly structured
In HTTP, lines of text (Figure 2-3)
Most lines are of the form “Keyword: Information”

5. Figure 2-3: Syntax of HTTP Request and Response Messages
HTTP Request Message
GET /reports/project1/final.htm HTTP/1.1[CRLF]
Host: voyager.cba.Hawaii.edu[CRLF]

6. Figure 2-3: Syntax of HTTP Request and Response Messages, Continued
HTTP Response Message
HTTP/ OK[CRLF]
Date: Tuesday, 20-MAR :32:15 GMT[CRLF]
Server: name of server software[CRLF]
MIME-version: 1.0[CRLF]
Content-type: text/plain[CRLF]
[CRLF]
File to be downloaded

7. Figure 2-1: How Standards Govern Interactions, Continued
Message Syntax (Organization)
General Message Organization (Figure 2-4)
Primary components
Data Field (content to be delivered)
Header (everything before the data field)
Trailer (everything after the data field)
Header and trailer are further divided into fields

8. Figure 2-4: General Message Organization
Trailer
Data Field
Header
Other
Header
Field
Address
Field
Message with
all three parts

9. Figure 2-4: General Message Organization, Continued
Data Field
Header
Other
Header
Field
Address
Field
Message without
a trailer
Usually only data link
layer messages have trailers

10. Figure 2-4: General Message Organization, Continued
Header
Message with
only a header
e.g.
TCP supervisory
messages are
pure headers
Other
Header
Field
Address
Field

11. Figure 2-1: How Standards Govern Interactions, Continued
Message Timing Constraints
When may a process transmit? At any time? Only when some event happens?
Turn-taking in conversations
In client/server computing, server cannot respond unless it receives a request
Many more complex examples exist (for instance, in TCP later in this chapter)

12. Connection-Oriented and Connectionless Protocols

13. Figure 2-5: Connectionless and Connection-Oriented Protocols
Message 1 (Seq. Num = A1)
Message 2 (Seq. Num = A2)
Close Connection
Connection-Oriented
Protocol
Open Connection A B
Message 3 (Seq. Num B1)
Message
(No Sequence Number)
Connectionless Protocol A B

14. Webserver Application
Figure 2-5: Connectionless and Connection-Oriented Protocols, Continued
Client PC
Browser
Webserver
Webserver Application
HTTP Request
No Openings
No Closings

15. Figure 2-6: Transmission Control Protocol (TCP) Session
Client PC
Transport Process
Webserver
Transport Process
1. SYN (Open)
Open
(3)
2. SYN, ACK (1) (Acknowledgment of 1)
3. ACK (2)
TCP 3-Way Connection Open

16. Figure 2-6: Transmission Control Protocol (TCP) Session, Continued
Client PC
Transport Process
Webserver
Transport Process
4. Data = HTTP Request
Carry
HTTP
Req &
Resp
(4)
5. ACK (4)
6. Data = HTTP Response
7. ACK (6)
Request-Response
Cycle for Data Transfer

17. Figure 2-6: Transmission Control Protocol (TCP) Session, Continued
Client PC
Transport Process
Webserver
Transport Process
8. Data = HTTP Request (Error)
9. Data = HTTP Request (No ACK so Retransmit)
Carry
HTTP
Req &
Resp
(4)
10. ACK (9)
11. Data = HTTP Response
12. ACK (11)
Error Handling

18. Figure 2-6: Transmission Control Protocol (TCP) Session, Continued
If acknowledgements are not sent by the receiver, the sender retransmits the TCP segment
This gives reliability
Note: An ACK may be combined with the next message if the next message is sent quickly enough

19. Figure 2-6: Transmission Control Protocol (TCP) Session, Continued
Client PC
Transport Process
Webserver
Transport Process
13. FIN (Close)
14. ACK (13)
Close
(4)
15. FIN
16. ACK (15)
4-Way Close

20. The TCP/IP-OSI Hybrid Standards Architecture

21. Figure 2-7: TCP/IP-OSI Architecture
Layer
Specific Purpose
General Purpose
Application (5)
Application-application interworking
Transport (4)
Host-host communication
Transmission across an internet
Internet (3)
Packet delivery across an internet
Data Link (2)
Frame delivery across a network
Transmission across a single network (LAN or WAN)
Physical (1)
Device-device connection

22. Figure 2-7: TCP/IP-OSI Architecture, Continued
Physical and Data Link Layer Standards Govern Communication Through a Single Network
LAN or WAN

23. Figure 2-7: TCP/IP-OSI Architecture, Continued
Physical Layer
Physical layer standards govern transmission between adjacent devices connected by a transmission medium
Host A
Physical Link
A-X1
Switch X1

24. Figure 2-7: TCP/IP-OSI Architecture, Continued
Data Link Layer
Data link layer standards govern the transmission of frames across a single network—typically by sending them through several switches along the data link
Data link layer standards also govern frame organization, timing constraints, and reliability

25. Figure 2-8: Physical and Data Link Layer Standards
3 Physical Link
1 Data Link
2 Switches
Host A
Switch
Data Link
A-R1
Switch
Physical Link
A-X1
Server
Station
Switch X1
Physical
Link
X1-X2
Physical
Link
X2-R1
Mobile Client
Station
Switch X2
Router R1

26. Figure 2-7: TCP/IP-OSI Architecture, Continued
Internet and Transport Layers
An internet is a group of networks connected by routers so that any application on any host on any network can communicate with any application on any other host on any other network
Internet and transport layer standards govern communication across an internet composed of two or more single networks

27. Figure 2-7: TCP/IP-OSI Architecture, Continued
Internet Layer
Internet layer standards govern the transmission of packets across an internet— typically by sending them through several routers along the route
Internet layer standards also govern packet organization, timing constraints, and reliability

28. Figure 2-9: Internet and Data Link Layer Standards
Host A
Data Link A-R1 R1
Network X
Network Y
3 Data Links: One per Network
1 Route per Internet
Data
Link
R1-R2
Network Z
Route A-B R2
Host B
Data Link R2-B

29. Figure 2-9: Internet and Data Link Layer Standards, Continued
Frame X
Details in
Network X
Packet
Data Link
A-R1
Switch
Host A
Switch
Frame X Destination Addresses:
Packet: Host B (Destination Host)
Frame: Router R1
Server
Station
Switch X1
Mobile Client
Station
Switch X2
Route
A-B
Router R1
Network X

30. Figure 2-9: Internet and Data Link Layer Standards, Continued
Details in
Network Y To
Network X
Route
A-B
Router R1
Frame Y
Data Link
R1-R2
Packet
Frame Y Destination Addresses:
Packet: Host B (Destination Host)
Frame: Router R2 To
Network Z
Router R2
Network Y

31. Figure 2-9: Internet and Data Link Layer Standards, Continued
Details in
Network Z
Packet
Data Link
R2-B
Frame Z
Switch Z1
Host B
Switch
Router R2
Frame Z Destination Addresses:
Packet: Host B (Destination Host)
Frame: Host B
Switch Z2
Mobile Client
Stations
Switch X2
Router
Network Z

32. Frames and Packets
In an internet with hosts separated by N networks, there will be:
2 hosts
One route (between the two hosts)
N frames (one in each network)
N-1 routers (change frames between each pair of networks)

33. Figure 2-7: TCP/IP-OSI Architecture, Continued
Transport Layer
Transport layer standards govern aspects of end-to-end communication between two end hosts that are not handled by the data link layer
These standards also allow hosts to work together even if the two computers are from different vendors and have different internal designs

34. Figure 2-10: Internet and Transport Layer Standards
end-to-end (host-to-host)
TCP is connection-oriented, reliable
Server
Client PC
Internet Layer
(usually IP)
hop-by-hop (host-router or router-router)
connectionless, unreliable
Router 1
Router 2
Router 3

35. Figure 2-7: TCP/IP-OSI Architecture, Continued
Application Layer
The application layer governs how two applications work with each other, even if they are from different vendors

36. Transport and Application Layer Standards
App A
App B
App C
App D
Application Layer
(App B – App C)
Transport Layer
end-to-end (host-to-host)
(Client PC – Server)
Client PC
Server
Most hosts are multitasking machines
that run multiple applications simultaneously.
Hosts need to communicate; So do pairs of applications

37. Standards Layers: Recap
Application (5)
Transport (4)
Internet (3)
Data Link (2)
Physical (1)

38. Figure 2-11: Why Layer?
Breaking up large tasks into smaller tasks and assigning tasks to different individuals is common in all fields
Specialization in standards design (EEs for physical layer, application specialists for application layer, etc.)
Simplification in standards design for individual standards
If you change a standard at one layer, you do not have to change standards at other layers

39. Day 4 Start Here

40. Review Questions Three things standards are concerned with
Semantics, syntax, timing
Connection-oriented vs. connectionless
List the 5 layers of the TCP/IP hybrid model
Additional 2 in the OSI model
What is the highest layer of operation for a switch, router, access point
What are Physical layer standards concerned with?
Data link layer standards?
Internet Layer?
Transport Layer?
Application Layer?

41. Syntax Examples

42. Octet Octets Field lengths may be measured in octets
An octet is a group of eight bits
In computer science, an octet is called a byte
Octet

43. Figure 2-12: Ethernet Frame
Preamble (7 octets) …
Start of Frame Delimiter
(1 octet)
Destination Ethernet Address (48 bits)
Source Ethernet Address (48 bits)
Length (2 octets) Length of Data Field …

44. Figure 2-12: Ethernet Frame, Continued
Data Field
(variable
length)
LLC Subheader
(usually 7 octets)
Usually
IP Packet
PAD (added if data field < 46 octets)
Frame Check Sequence (32 bits)

45. Figure 2-12: Ethernet Frame, Continued
Frame Check Sequence (32 bits)
Sender computes the frame check sequence field value based on contents of other fields
Receiver recomputes the field value
If the values match, there have been no errors
If the values do not match, there is an error
The receiver simply discards the frame
Unreliable: error detection but not error correction

46. Figure 2-14: Internet Protocol (IP) Packet
Bit 0
Bit 31
Version
(4 bits)
Header
Length
(4 bits)
Diff-Serv
(8 bits)
Total Length
(16 bits)
Identification
(16 bits)
Flags
(3 bits)
Fragment Offset
(13 bits)
Time to Live
(8 bits)
Protocol
(8 bits)
Header Checksum (16 bits)
Source Address (32 bits)
Destination Address (32 bits)
Options (if any)
Padding
(to 32-bit boundary)
Data Field
(dozens, hundreds, or thousands of bits)
Often contains a TCP segment

47. Figure 2-14: Internet Protocol (IP) Packet, Continued
Bit 0
Bit 31
Version
(4 bits)
Header
Length
(4 bits)
Diff-Serv
(8 bits)
Total Length
(16 bits)
Identification
(16 bits)
Flags
(3 bits)
Fragment Offset
(13 bits)
Time to Live
(8 bits)
Protocol
(8 bits)
Header Checksum (16 bits)
Version is Bits 0-3
Header length is Bits 4-7
Diff Serv is Bits 8-15
Total Length is Bits 16-31
Identification is Bits 32-47
Time to live is Bits 48-55
These fields
are discussed in
Chapter 8

48. Vertical Communication

49. Figure 2-15: Layered Communication on the Source Host
Application
Process
HTTP
Message
Transport
Process
HTTP
Message
TCP
Hdr
Encapsulation of HTTP Message
in Data Field of TCP Segment

50. Figure 2-15: Layered Communication on the Source Host, Continued
When a layer process (N) creates a message, it passes it down to the next-lower-layer process (N-1) immediately
The receiving process (N-1) will encapsulate the Layer N message, that is, place it in the data field of its own (N-1) message

51. Figure 2-15: Layered Communication on the Source Host, Continued
Transport
Process
HTTP
Message
TCP
Hdr
Internet
Process
HTTP
Message
TCP
Hdr IP
Hdr
Encapsulation of TCP Segment
in Data Field of IP Packet

52. Figure 2-15: Layered Communication on the Source Host, Continued
Internet
Process
HTTP
Message
TCP
Hdr IP
Hdr
Data Link
Process
Eth
Trlr
HTTP
Message
TCP
Hdr IP
Hdr
Eth
Hdr
Encapsulation of IP Packet
in Data Field of Ethernet Frame

53. Figure 2-15: Layered Communication on the Source Host, Continued
Data Link
Process
Eth
Trlr
HTTP
Message
TCP
Hdr IP
Hdr
Eth
Hdr
Physical
Process

54. Figure 2-15: Layered Communication on the Source Host, Continued
The following is the final frame for a
an HTTP message on an Ethernet LAN
Eth
Trlr
HTTP
Message
TCP
Hdr IP
Hdr
Eth
Hdr L2 L5 L4 L3 L2

55. Figure 2-15: Layered Communication on the Source Host, Continued
The following is the final frame for a
an SMTP ( ) message on PPP telephone modem connection
PPP
Trlr
SMTP
Message
TCP
Hdr IP
Hdr
PPP
Hdr L2 L5 L4 L3 L2
Note: HTTP is NOT the application layer message, as it is in webservice.
PPP replaces Ethernet.

56. Figure 2-15: Layered Communication on the Source Host, Continued
The following is the final frame
for a packet carrying a supervisory TCP segment:
Eth
Trlr
TCP
Hdr IP
Hdr
Eth
Hdr L2 L4 L3 L2
Supervisory TCP segments are initiated by the Transport layer process (Layer 4), so Layer 5 is not involved.
TCP supervisory messages consist entirely of headers. The header carries supervisory information, so no TCP data field exists in supervisory TCP messages.

57. Figure 2-16: Decapsulation on the Destination Host
Eth
Trlr
HTTP
Message
TCP
Hdr IP
Hdr
Eth
Hdr
Data Link
Process
Physical
Process

58. Figure 2-16: Decapsulation on the Destination Host, Continued
HTTP
Message
TCP
Hdr IP
Hdr
Internet
Process
Eth
Trlr
HTTP
Message
TCP
Hdr IP
Hdr
Eth
Hdr
Data Link
Process
Decapsulation of IP Packet
from Data Field of Ethernet Frame

59. Figure 2-16: Decapsulation on the Destination Host, Continued
HTTP
Message
TCP
Hdr
Transport
Process
HTTP
Message
TCP
Hdr IP
Hdr
Internet
Process
Decapsulation of TCP Segment
from Data Field of IP Packet

60. Figure 2-16: Decapsulation on the Destination Host, Continued
HTTP
Message
Application
Process
HTTP
Message
TCP
Hdr
Transport
Process
Decapsulation of HTTP Message
from Data Field of TCP Segment

61. Figure 2-17: Layered End-to-End Communication
Routers
Have Three
Layers
---
Each Router
Port
Has Two
Switches
Have Two
Layers
---
Each Switch
Port
Has One
Layer
Source and
Destination
Hosts Have
5 Layers
Int
App DL
Trans
Phy
Source
Host
Switch 1
Switch 2
Router 1
Switch 3
Router 2
Destination
Host

62. Hypertext Transfer Protocol
Figure 2-18: Protocols
Protocols are standards that govern interactions between hardware and software processes at the same layer but on different hosts
Hypertext Transfer Protocol
Int
App DL
Trans
Phy
Source
Host
Switch 1
Switch 2
Router 1
Switch 3
Router 2
Destination
Host

63. Figure 2-18: Protocols, Continued
Hypertext Transfer Protocol
Int
App DL
Trans
Phy
Transmission Control Protocol
Internet Protocol
Source
Host
Switch 1
Switch 2
Router 1
Switch 3
Router 2
Destination
Host

64. OSI, TCP/IP, and Other Standards Architectures

65. Figure 2-19: OSI and TCP/IP
Standards
Agency(ies)
ISO (International
Organization for
Standardization)
ITU-T (International
Telecommunications
Union—
Standards Sector)
IETF (Internet
Engineering Task
Force)

66. Figure 2-19: OSI and TCP/IP, Continued
Dominance
Nearly 100% at
physical and data
link layers
70% to 80% at the
Internet and transport
layers. Also strong
at the application layer
Documents are
Called
Various
Mostly RFCs (requests
for comment)

67. Figure 2-20: The Hybrid TCP/IP-OSI Architecture
Broad Purpose
Application
Application
Application
(Layer 5)
Applications
Presentation
Session
Transport
Transport
Transport (Layer 4)
Internetworking
Internet
Network
Internet (Layer 3)
Use OSI
Standards Here
Data Link
Data Link (Layer 2)
Communication
within a single
LAN or WAN
Physical
Physical (Layer 1)

68. Figure 2-20: The Hybrid TCP/IP-OSI Architecture, Continued
Notes:
The Hybrid TCP/IP-OSI Architecture is used on the Internet and dominates internal corporate networks
OSI standards are used almost universally at the physical and data link layers (which govern communication within individual networks)
TCP/IP is used for 70% to 80% of all corporate traffic at the internet and transport layers and is used heavily at the application layer.

69. Figure 2-21: OSI Session Layer
(Manages a series of transactions)
App 1
App 2
App 3
App 4
Transport Layer
Network or
Internet
Client PC
Server

70. Figure 2-21: OSI Session Layer, Continued
Manages a series of transactions closely
If there is a connection break, only have to retransmit transactions since the last rollback point
TCP/IP Has No Session Layer
The few applications that need to manage transaction series closely provide their own mechanisms
In HTTP, cookies provide continuity across applications

71. Figure 2-22: OSI Presentation Layer
(Transfer Syntax C)
App 2
Internal
Syntax A
App 3
Internal
Syntax B
Presentation standards also include
compression standards and
data formatting standards (jpeg, etc.)

72. Figure 2-22: OSI Presentation Layer, Continued
Transfer syntax
Layer for application standards, such as jpeg
TCP/IP Has No Presentation Layer
MIME at least allows the sender to indicate the format of file delivered in a message

73. Figure 2-23: Other Major Standards Architectures
IPX/SPX
Used by older Novell NetWare file servers
Popular option for newer Novell NetWare file servers
SNA (Systems Network Architecture)
Used by IBM mainframe computers
AppleTalk
Used by Apple Macintoshes