E.G. File Transfer: CS420/520 Axel Krings Sequence 2

Chapter 2
CS420/520 Axel Krings
Page 1
Sequence 2
Need For Protocol Architecture

E.g. File transfer
Source must activate comms. Path or inform network
of destination
Source must check destination is prepared to receive
File transfer application on source must check
destination file management system will accept and
store file for his user
May need file format translation
Task broken into subtasks

Implemented separately in layers in stack
Functions needed in both systems
Peer layers communicate
Page 2
Sequence 2
Simplified Network
Architecture, e.g., file transfer
Page 3
Sequence 2
Key Elements of a Protocol

Syntax
Data formats
Signal levels
Semantics
Control information
Error handling
Timing
Speed matching
Sequencing
Page 4
Sequence 2
Standardized Protocol
Architectures
Required for devices to communicate
Vendors have more marketable products
Customers can insist on standards based
equipment
Two standards:
OSI Reference model
Never lived up to early promises
TCP/IP protocol suite

Most widely used
Also: IBM Systems Network Architecture (SNA)

Page 5
Sequence 2
TCP/IP Protocol Architecture

developed by US Defense Advanced Research
Project Agency (DARPA)
for ARPANET packet switched network
used by the global Internet
protocol suite comprises a large collection of
standardized protocols
Page 6
Sequence 2
TCP/IP Layers
this is not an official model but a working one
Application layer
Host-to-host, or transport layer
Internet layer
Network access layer
Physical layer
Page 7
Sequence 2
Physical Layer
concerned with physical interface between
computer and network
concerned with issues like:
characteristics of transmission medium
signal levels
data rates
other related matters
Page 8
Sequence 2
Network Access Layer

exchange of data between an end system and
attached network
concerned with issues like :
destination address provision
invoking specific services like priority
access to & routing data across a network link
between two attached systems
allows layers above to ignore link specifics
Page 9
Sequence 2
Internet Layer
routing functions across multiple networks

for systems attached to different networks
using IP protocol
implemented in end systems and routers
routers connect two networks and relays data
between them
Page 10
Sequence 2
Transport Layer
common layer shared by all applications

provides reliable delivery of data
in same order as sent
commonly uses TCP
Page 11
Sequence 2
Application Layer
provide support for user applications, e.g., ftp,
email
need a separate module for each type of
application
Page 12
Sequence 2
Operation of TCP and IP

Host A
Host B
App X
Port
(service access point)
App Y
Logical connection
(TCP connection)
TCP
App Y
App X
IP
Network Access
Protocol #1
Physical
TCP
Global internet
address
IP
Network Access
Protocol #2
Subnetwork attachment
point address
Router
Logical connection
(e.g., virtual circuit)
Physical
IP
NAP 1
Network 1
NAP 2
Physical Physical
Network 2
Page 13
Sequence 2
Figure 2.1 TCP/IP Concepts
Addressing Requirements
two levels of addressing required
each host on a subnet needs a unique global
network address
its IP address
each application on a (multi-tasking) host needs

a unique address within the host
known as a port
Page 14
Sequence 2
Protocol Data Units (PDU)

At each layer
protocols are used to communicate
control information is added to user data
Transport layer may fragment user data

Each fragment has a transport header added
Destination SAP (service access point)
Sequence number
Error detection code
This gives a transport protocol data unit
Page 15
Sequence 2
Protocol Data Units
Page 16
Sequence 2
Operation of TCP/IP
User data
Application
byte stream
TCP
segment
TCP
header
IP
datagram
IP
header
Network-level
packet
Network
header
Page 17
Sequence 2
Figure 2.2 Protocol Data Units (PDUs) in the TCP/IP Architecture
TCP
Usual transport layer is Transmission Control Protocol
Reliable connection
RFC 793 from 1981
Connection
Temporary logical association between entities in different
systems
TCP PDU
Called TCP segment
Includes source and destination port (c.f. SAP)
Identify respective users (applications)
Connection refers to pair of ports
TCP tracks segments between entities on each

connection
Page 18
Sequence 2
TCP Header
Bit:
31
16
Source Port
Destination Port
20 octets
Sequence Number
Acknowledgement Number
Header
length Reserved
Flags
Checksum
Window
Urgent Pointer
Options + Padding
Page 19
Sequence 2
(a) TCP Header
User
Datagram Protocol
0
16
(UDP)
8 octets
Bit:
Source Port
Destination Port
Segment Length
Checksum
31
an alternative to TCP
no guaranteed delivery (...it is a datagram)
UDP Header
no preservation of (b)
sequence
no protection against duplication
minimum Figure
overhead
2.3 TCP and UDP Headers
adds port addressing to IP
Page 20
Sequence 2
10
Bit:
31
16
Source Port
Destination Port
20 octets
Sequence Number
Acknowledgement Number
Header
length Reserved
Flags
Window
Checksum
Urgent Pointer
Options + Padding
UDP Header
(a) TCP Header
31
16
8 octets
Bit:
Source Port
Destination Port
Segment Length
Checksum
(b) UDP Header
21 and UDP Headers

Figure 2.3 Page
TCP
Sequence 2
IP Header
Bit:
Version
IHL
14
DS
20 octets
31
19
ECN
Identification
Time to Live
16
Total Length
Flags
Protocol
Fragment Offset
Header Checksum
Source Address
Destination Address
Options + Padding
(a) IPv4 Header

Bit:
0
Version
Page 22
10
DS
Payload Length
12
Sequence 2
24
16
ECN
31
Flow Label
Next Header
Hop Limit
11
ets
Source Address
20 oct
Time to Live
Protocol
Header Checksum
Source Address
Bit:
Version
Destination
14 Address
16
19
IHL
DS
ECN
Options
+ Padding
20 octets
Identification
Time to Live
31
Total Length
Flags
Fragment Offset
Protocol
Header Checksum
(a)
IPv4
Header
Source
Address
Destination Address
Bit:
10
12
16
Options
+ Padding
Version Header
DS
ECN
IPv6
(a) IPv4 Header
0
Version
Next Header
10
DS
40 octets
12
Hop Limit
24
16
ECN
Payload Length
31
Flow Label
Payload Length
Bit:
24
31
Flow Label
Next Header
Source Address
Hop Limit
40 octets
Source Address
Destination Address
Destination Address
(b) IPv6 Header

(b) IPv6 Header
DS = Differentiated
services
fieldfield
DS = Differentiated
services
ECN = Explicit
congestion
notificationfield
field
ECN = Explicit
congestion
notification
Page 23
Note:
TheDS/ECN
8-bit DS/ECN
Note:
The 8-bit
fields were fields
formerlywere formerly
known
as theas
Type
Serviceof
field
in the IPv4
known
theofType
Service
field in the IPv4
header
and the
Traffic
fieldClass
in the IPv6
header
and
the Class
Traffic
field in the IPv6
header.
header.
Sequence 2
Figure 2.4 IP Headers
Figure 2.4 IP Headers
TCP/IP Applications
have a number of standard TCP/IP applications
such as
Simple Mail Transfer Protocol (SMTP)
File Transfer Protocol (FTP)
Telnet
Page 24
Sequence 2
12
Some TCP/IP Protocols

MIME
BGP
FTP
HTTP
SMTP
TELNET
TCP
SNMP
UDP
ICMP
IGMP
OSPF
RSVP
IP
BGP = Border Gateway Protocol

FTP
= File Transfer Protocol
HTTP = Hypertext Transfer Protocol
ICMP = Internet Control Message Protocol
IGMP = Internet Group Management Protocol
IP
= Internet Protocol
MIME
= Multipurpose
Internet Mail Extension
CS420/520
Axel
Krings
OSPF
RSVP
SMTP
SNMP
TCP
UDP
=
=
=
=
=
=
Open Shortest Path First

Resource ReSerVation Protocol
Simple Mail Transfer Protocol
Simple Network Management Protocol
Transmission Control Protocol
User Datagram Protocol
Page 25
Sequence 2
Figure 2.5 Some Protocols in the TCP/IP Protocol Suite
OSI
Open Systems Interconnection
developed by the International Organization for
Standardization (ISO)
has seven layers
is a theoretical system delivered too late!
TCP/IP is the de facto standard
Page 26
Sequence 2
13
Standardized Protocol
Architectures
Layer 7
(Application)
Total
Communication
Function
Layer N
Decompose
(modularity,
information-hiding)
Service to
Layer N+1
Layer N
entity
Protocol
with peer
Layer N
Service from
Layer N1
Layer 1
(Physical)
OSI-wide standards
(e.g., network management, security)
Page 27
Sequence 2
Figure 2.8 The OSI Architecture as a Framework for Standardization
Application
Provides access to the OSI environment for users and also
provides distributed information services.
OSI Layers
Presentation
Provides independence to the application processes from
differences in data representation (syntax).
Session
Provides the control structure for communication between
applications; establishes, manages, and terminates
connections (sessions) between cooperating applications.
Transport
Provides reliable, transparent transfer of data between end
points; provides end-to-end error recovery and flow control.
Network
Provides upper layers with independence from the data
transmission and switching technologies used to connect
systems; responsible for establishing, maintaining, and
terminating connections.
Data Link
Provides for the reliable transfer of information across the
physical link; sends blocks (frames) with the necessary
synchronization, error control, and flow control.
Physical
Concerned with transmission of unstructured bit stream over
physical medium; deals with the mechanical, electrical,
functional, and procedural characteristics to access the
physical medium.
Page 28
Sequence 2
Figure 2.6 The OSI Layers
14
OSI Layers (1)

Physical
Physical interface between devices
Mechanical
Electrical
Functional
Procedural
Data Link
Means of activating, maintaining and deactivating a
reliable link
Error detection and control
Higher layers may assume error free transmission
Page 29
Sequence 2
OSI Layers (2)

Network
Transport of information
Higher layers do not need to know about underlying technology
Not needed on direct links
Transport
Exchange of data between end systems
Error free
In sequence
No losses
No duplicates
Quality of service
Page 30
Sequence 2
15
OSI Layers (3)

Session
Control of dialogues between applications
Dialogue discipline
Grouping
Recovery
Presentation
Data formats and coding
Data compression
Encryption
Application
Means for applications to access OSI environment
Page 31
Sequence 2
The OSI Environment
Page 32
Sequence 2
16
OSI
OSI vs TCP/IP
TCP/IP
Application
Presentation
Application
Session
Transport
Transport (host-to-host)
Network
Internet
Data Link
Network
Access
Physical
Physical
Page 33
Sequence 2
Figure 2.7 A Comparison of the OSI and TCP/IP Protocol Architectures
Layer Specific Standards

Service Definition
(Functional description
for internal use)
Addressing
(Service Access Point)
Layer N
Page 34
Protocol Specification
(Precise syntax and
semantics for
interoperability)
Sequence 2
Figure 2.9 Layer-Specific Standards
17
Service Primitives and

Parameters
define services between
adjacent layers using:
primitives to specify
function performed
parameters to pass data
and control info
Service user
Service provider
Service user
Request
Service user
Service provider
Se
Request
Indication
Ind
Response
Confirm
(a) Confirmed Service
Page 35
(b) Nonconfirmed Service
Sequence 2
Figure 2.10 Time Sequence Diagrams for Service Primitives
2.1 Service Primitive Types

Primitive Table
Types
REQUEST
A primitive issued by a service user to invoke some service and to pass the
parameters needed to specify fully the requested service
INDICATION
A primitive issued by a service provider either to

1. indicate that a procedure has been invoked by the peer service user on
the connection and to provide the associated parameters, or
2. notify the service user of a provider-initiated action
RESPONSE
A primitive issued by a service user to acknowledge or complete some

procedure previously invoked by an indication to that user
CONFIRM
A primitive issued by a service provider to acknowledge or complete some

procedure previously invoked by a request by the service user
Page 36
Sequence 2
18
Traditional vs Multimedia
Applications
traditionally Internet dominated by info retrieval
applications
typically using text and image transfer
eg. email, file transfer, web
see increasing growth in multimedia applications

involving massive amounts of data
such as streaming audio and video
Page 37
Sequence 2
Elastic and Inelastic Traffic

elastic traffic
can adjust to delay & throughput changes over a wide
range
eg. traditional data style TCP/IP traffic
some applications more sensitive though
inelastic traffic
does not adapt to such changes
eg. real-time voice & video traffic
need minimum requirements on net arch
Page 38
Sequence 2
19
Multimedia
Technologies
TECHNOLOGIES
Quality of service
Protocols
Communications/networking
Synchronization
Compression
User interface
Computer architecture
Te
xt
So
un
d
G
ra
ph
M ics
ot
io
n
Database
Operating system
MEDIA TYPE
MM e-mail
Collaborative work systems
MM conferencing
Streaming audio/video
VoIP
APPLICATION
Page 39
Sequence 2
Figure 2.11 A Multimedia Taxonomy
20

E.G. File Transfer: CS420/520 Axel Krings Sequence 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E.G. File Transfer: CS420/520 Axel Krings Sequence 2

Uploaded by

Copyright:

Available Formats

Chapter 2

CS420/520 Axel Krings

Need For Protocol Architecture

Task broken into subtasks

CS420/520 Axel Krings

CS420/520 Axel Krings

Key Elements of a Protocol

CS420/520 Axel Krings

TCP/IP protocol suite

Also: IBM Systems Network Architecture (SNA)

TCP/IP Protocol Architecture

CS420/520 Axel Krings

CS420/520 Axel Krings

CS420/520 Axel Krings

Network Access Layer

allows layers above to ignore link specifics

CS420/520 Axel Krings

routing functions across multiple networks

CS420/520 Axel Krings

common layer shared by all applications

CS420/520 Axel Krings

CS420/520 Axel Krings

Operation of TCP and IP

CS420/520 Axel Krings

Figure 2.1 TCP/IP Concepts

each application on a (multi-tasking) host needs

CS420/520 Axel Krings

Protocol Data Units (PDU)

Transport layer may fragment user data

This gives a transport protocol data unit

CS420/520 Axel Krings

Protocol Data Units

CS420/520 Axel Krings

CS420/520 Axel Krings

Figure 2.2 Protocol Data Units (PDUs) in the TCP/IP Architecture

TCP tracks segments between entities on each

CS420/520 Axel Krings

(a) TCP Header

CS420/520 Axel Krings

(a) TCP Header

(b) UDP Header

21 and UDP Headers

CS420/520 Axel Krings

(a) IPv4 Header

(a) IPv4 Header

(b) IPv6 Header

Figure 2.4 IP Headers

Figure 2.4 IP Headers

CS420/520 Axel Krings

Some TCP/IP Protocols

BGP = Border Gateway Protocol

Open Shortest Path First

Figure 2.5 Some Protocols in the TCP/IP Protocol Suite

CS420/520 Axel Krings

CS420/520 Axel Krings

Figure 2.8 The OSI Architecture as a Framework for Standardization

CS420/520 Axel Krings

Figure 2.6 The OSI Layers

OSI Layers (1)

OSI Layers (2)

CS420/520 Axel Krings

OSI Layers (3)

The OSI Environment