Network Architecture: CSE 6315

Network Layered Architecture

Ketema Adere (PhD)

Assistant Professor of Computer Science & Engineering,
Network Science Research Group, ASTU,
Email: ketem2006@[Link]/
[Link]@[Link]
Office: Building/Room: 508/ 09
1
 Computer Network - Architecture
• Network Architecture comprises of
– Layers
• Layered approach to reduce the design complexity
• Each layer performs a well defined function
• Each layer will offer certain services to the higher
layers, shielding those layers from the details of actual
implementation of services offered
– Protocols
• set of rules that govern the data exchange by the peer
entities
• Defines the format and meaning of data transferred
between computers at a given layer
• Sender and receiver must use the same format
2
 Computer Network - Architecture
 Network Architecture is a combination of hardware and
software that sends data from one location to another.
– Each software package uses the services of another software
package.
– At the lowest layer, a signal, or a set of signals, is sent from the
source computer to the destination computer.
– We use the concept of layers in our daily life.
– Example: the task of sending an e-mail from one point in the
world to another can be broken into several tasks, each
performed by a separate software package.

3
 Layered Tasks
 Example: consider two friends who communicate through postal mail
 The process of sending a letter to a friend would be complex if there
were no services available from the post office.

4
Reference Model

5
 OSI REFERENCE MODEL

 Deals with connecting open

systems.

 Describe standards for inter-

computer communication.

 The OSI model has seven layers.

6
 Why a Layered Network Model?
 To provide well-defined interfaces b/n adjacent
layers
• A change in one layer doesn’t have an effect on the
other layers.
• Interface must remain the same
 Allows a structured development of network
software.

• Reduces complexity
• Standardizes interfaces
• Facilitates modular engineering
• Ensures interoperable technology
• Accelerates evolution
• Simplifies learning
7
 Network Layering Design

• Networks are organized as stack of layers

• Layers are built one above other

• Function of each layer is different

• Each layer provides services to higher layer

• Hides lower details from upper layers

• Layers are built independently

Page 8
 Design Issues of Layers
• Identify sender and receiver
– Multiple machines
– Multiple processes
– Addressing
• Rules of data transfer
– Simplex
– Duplex
– Number of logical channels
– Separate channels for separate purpose
• Data
• Control information

Page 9
 Design Issues of Layers(cont …)
• Error control
– Error detection code
– Error correction code
– Notification of error
• Flow control
– Protecting slow receiver from a fast sender
– Pre-decided transmission rate
– Feedback from receiver
– Situation analysis by sender

10
 Design Issues of Layers(cont …)
• Order of messages
– In sequence
– Out of sequence
– Numbering
– Reassembly
• Size of message
– Unrestricted size
– Restriction on size
– Fragmentation and reassembly
– Impact of overheads on transmission efficiency

Page 11
 Design Issues of Layers(cont …)
• Multiplexing
– Demultiplexing
– Utilization of common resources
– Physical layer multiplexing
– Logical channel multiplexing
• Tunnels
• Path selection
– Multiple paths
– Routing
– Cost of path
– Quality of path
– Security concerns

Page 12
 OSI REFERENCE MODEL
 The principles that were applied to arrive at
these seven layers can be:-

13
 . . . CONTINUED

1. A layer should be created where a

different abstraction is needed.

2. The function of each layer should

be chosen with an eye toward
defining internationally
standardized protocols.

14
 . . . CONTINUED

3. Each layer should perform a well-

defined function.

4. The layer boundaries should be

chosen to minimize the information
flow across the interfaces.

15
 . . . CONTINUED

5. The number of layers should be

large enough that distinct functions
need not be thrown together in the
same layer.

16
Layer

Application Protocol
7 APPLICATION APPLICATION

Presentation Protocol
6 PRESENTATION PRESENTATION

Session Protocol
5 SESSION SESSION

Transport Protocol
4 TRANSPORT TRANSPORT

Network Protocol
3 NETWORK NETWORK

Data Link Protocol

2 DATA LINK DATA LINK

Transmission Media
1 PHYSICAL PHYSICAL
17
HOST A HOST B
Data Unit at Each Layer

APPLICATION
Upper
Layer PRESENTATION
Data
SESSION

Segment TRANSPORT

Packet NETWORK

Frame DATA LINK

Bits PHYSICAL

18
 THE PHYSICAL LAYER

 Concerned with transmitting raw

bits over a communication channel.
• How many volts should be used to represent
a 1 and 0.

• How many nanoseconds a bit lasts.

• Whether transmission may proceed

simultaneously in both directions.
19
 . . . CONTINUED

• How the initial connection is established and

how it is torn down.

• How many pins the network connector has

and what each pin is used for.

20
 . . . CONTINUED

 The design issues here largely deal

with:-
• Mechanical

• Electrical and timing interfaces

• The physical transmission medium

21
22
 THE DATA LINK LAYER

 The data link layer transforms the

physical layer, a raw transmission
facility, to reliable link.

 Responsible to deliver a frame

from node-to-node (Hop-to-hop).

23
 SPECIFIC RESPONSIBILITIES

 Framing

 Physical Addressing

 Flow Control

 Error Control

 Access control

24
25
EXAMPLE

26
 THE NETWORK LAYER

 The network layer is responsible for the

source-to-destination delivery of a packet,
possibly across multiple networks.

 It controls the operation of the subnet.

 A key design issue is determining how

packets are routed from source to
destination.

27
 SPECIFIC RESPONSIBILITIES

 Logical addressing (i.e., IP addressing )

 Routing (i.e., selecting a best path in order

to transmit packets from source to
destination host-to-host delivery).

28
EXAMPLE

29
 THE TRANSPORT LAYER

 Provides:-
• Reliable communication (TCP)

• Unreliable communication (UDP)

• Create port number

30
 THE TRANSPORT LAYER

 The basic function of the transport layer is:-

• To accept data from above,

• Split it up into smaller units if need be,

• Pass these to the network layer, and ensure that the

pieces all arrive correctly at the other end.

• Thus, responsible for process-to-process delivery of

the entire message.
31
 SPECIFIC RESPONSIBILITIES

 Service-point addressing.

 Segmentation and reassembly.

 Connection control.

 Flow control.

 Error control.

32
EXAMPLE

33
 THE SESSION LAYER

 Create and maintain sessions

 The session layer allows users on

different machines to establish
sessions between them.

34
 SPECIFIC RESPONSIBILITIES

 Dialog control.

 Synchronization.

35
36
 THE PRESENTATION LAYER

 Generify data, and encryption

services.

 The presentation layer is concerned

with the syntax and semantics of
the information transmitted.

37
 SPECIFIC RESPONSIBILITIES

 Translation.

 Encryption.

 Compression.

38
39
 THE APPLICATION LAYER

 Communicate with network aware

applications.

 The application layer contains a

variety of protocols that are
commonly needed by users.

40
 SPECIFIC RESPONSIBILITIES

 File transfer, access, and

management (FTAM).

 Mail services.

 Hyper Text Transfer Protocol

(HTTP)

 Directory services.

41
 TCP/IP & the Internet

 The modern Internet sits on top of

the TCP/IP technology
 Used as a standard.

 To bridge the gap b/n non-compatible

platforms.

 All computers connected to the Internet

understands TCP/IP.
42
 TCP/IP REFERENCE MODEL

 TCP/IP is the first set protocols

used in the Internet.

 Allows computers to
communicate/share resources across
a network.

43
 TCP/IP REFERENCE MODEL

 The TCP/IP protocol suite, used in

the Internet, was developed prior to
the OSI model.

 The TCP/IP protocol suite is made of

five layers.

44
 TCP/IP REFERENCE MODEL

 The protocols are built on top of

connectionless technology.
 Data sent from one node to another as a
sequence of datagram.

 Each datagram sent independably.

 Datagrams of the same message may follow

different path.
45
 . . . CONTINUED

 Physical
Link Layer
 Data link

 Network

 Transport

 Application

46
 OSI Model TCP/IP Hierarchy Protocols

7th
Application Layer

6th
Presentation Layer Application Layer

5th
Session Layer

4th
Transport Layer
Transport Layer

3rd
Network Layer
Network Layer

2nd
Link Layer
Link Layer
1st
Physical Layer

47
 Packet Encapsulation

 The data is sent down the protocol

stack
 Each layer adds to the data by
prepending headers

48
 source Encapsulation
message M application
segment Ht M transport
datagram Hn Ht M network
frame Hl Hn Ht M link
physical
link
physical

switch

destination Hn Ht M network
M application Hl Hn Ht M link Hn Ht M
Ht M transport physical
Hn Ht M network
Hl Hn Ht M link router
physical

49
 Encapsulation

A frame check Application

sequence (FCS)
field Presentation
PDU
Upper-Layer Data Session

Transport Segment
TCP Header Upper-Layer Data

Network Packet
IP Header Data

LLC Header Data FCS

Data-Link Frame

MAC Header Data FCS

Physical Bits
0101110101001000010

50
Encapsulation

51
Network Access & Physical Layer

 TCP/IP reference model does not

discuss these layers too much
• the node should connect to the network with
a protocol such that it can send IP packets

52
 Internetwork Layer

• Connectionless, point to point

internetworking protocol (uses the
datagram approach)
• takes care of routing across multiple
networks.

53
 Internetwork Layer

• each packet travels in the network

independently of each other
 they may not arrive (if there is a problem in
the network)
 they may arrive out of order

54
 Transport Layer

• End-to-end data transfer

• Transmission Control Protocol (TCP)
• connection oriented
• reliable delivery of data
• ordering of delivery
• User Datagram Protocol (UDP)
• connectionless service
• delivery is not guaranteed 55
 Application Layer

 Support for user applications

 A separate module for each different
application
• e.g. HTTP, SMTP, FTP

56
 IP (Internet Protocol)

 The core of the TCP/IP protocol

suite
 Two versions co-exist
• v4 – the widely used IP protocol
• v6 – has been standardized in 1996, but still
not widely deployed
 IP (v4) header minimum 20 octets (160
bits) 57
 What does IP Do?
 IP transports datagram (packet) from the source to
destination node.
 Responsible for routing a packet
 Breaks a packet into smaller packets, if required.
 Unreliable service.
 Components of IP packet
 IP header : Contains many fields that are used by
routers to forward the packet, such as: fields that
identify the sender, receiver, and transport protocol
 Payload : Contains information (data) & upper-layer
info.
58
 Need for IPv6
 We have run out of IPv4 address space
 Better QoS: IPv4 has very limited QoS
features
 End-to-end security: IPv4 does not
provide any security
 Better addressing scheme
– Hierarchical
– Efficient for routing
– Easy to implement
 Mobile IP support, etc.

59
 IPv6
 IPv6
• Enhancements over IPv4 for modern
high speed networks
• IPv6 introduces a more streamlined
header format that reduces overhead
processing on intermediate routers and
speeds throughput.
• Support for multimedia data streams
60
Header: from IPv4 to IPv6
Changed Removed

61
 IPv6 Header Format

 New Header Format

 IPv4 headers and IPv6 headers are not
interoperable and IPv6 is not backward
compatible with IPv4.
 Both IPv6 header and addresses are larger than
the IPv4 header and address respectively
62
 IPv6

 Thus, the driving force behind v6

was to increase address space
• 128-bit as compared to 32-bit of v4
 Not backward compatible
• all equipment and software must change

63
 IPv6
 Types of IPv6 Addresses
– Unicast: an identifier for a single interface.
– Multicast: an identifier for a set of
interfaces (typically belonging to different
nodes).
– Anycast: when a packet is sent to an
anycast group, it is only delivered to one of
the group members, thereby limiting the
data flooding that characterizes IPv4
networks.

64
 What is not in IPv6
 Broadcast
– There is no broadcast in IPv6.
– This functionality is taken over by
multicast.
– As a consequence, all 0’s and all 1’s
addresses are legal.
– No fragmentation by intermediate routers
– There are other differences also
– Minimum MTU of 1280 bytes

65
Representation of IPv6 Addresses

Abbreviated IPv6 addresses

66
Transition from IPv4 to IPv6

67
 Transition from IPv4 to IPv6
 Dual Stack: it is relatively easy to write a stack that supports
both IPv4 and IPv6 while sharing most of the code.
 Tunneling: an isolated IPv6 host or network must be able to
use the existing IPv4 infrastructure to carry IPv6 packets.
– Encapsulating IPv6 packets within IPv4, in effect using
IPv4 as a link layer for IPv6.
– Automatic Tunneling and Configured Tunneling
 Proxying and Translation: When an IPv6-only host needs
to access an IPv4-only service , some form of translation is
necessary.
– For example a web proxy: a dual-stack application-layer
proxy
68
 Features of IPv6
 New header format
– IPv6 is not compatible with IPv4, but it is compatible
with the other protocols, including TCP and UDP
– Major improvement of IPv6 is the simplification of the
header
 IPv6 has longer addresses than IPv4.
– 1000 addresses per square meter
 Efficient and hierarchical addressing and routing
infrastructure
 Stateless and stateful (using DHCPv6) address
configuration
 Built-in security (IPSec), ignored if not required
 Better support for QoS
 Extensibility: IPv6 can easily be extended for new
features by adding extension headers
 Jumbograms (packet larger than 64KB) possible 69
Feature IPv4 IPv6
Source and destination address 32 bits /4bytes 128 bits / 32bytes
IPSec Optional Required
Payload ID for QoS in the header No identification Using Flow label field

Fragmentation Both router and the Only supported at the sending

sending hosts hosts
Header checksum included Not included
Resolve IP address to a link layer broadcast ARP Multicast Neighbor Solicitation
address request message
Determine the address of the best ICMP Router ICMPv6 Router Solicitation and
default gateway Discovery(optional) Router Advertisement (required)

Send traffic to all nodes on a Broadcast Link-local scope all-nodes

subnet multicast address

Configure address Manually or DHCP Autoconfiguration

Manage local subnet group (IGMP) Multicast Listener Discovery

membership (MLD) 70
 Key Observations
 Longer Address than IPv4
 Longer but Simpler Header
 Fixed length header, options in payload
 No fragment offset
– Do path discovery
– Sends error message to sender if packet size is
Big
 No checksum
– Assuming reliable networks
– Transport layer already has checksum
 What has not changed
– Almost everything!
– IPv6 is a connectionless datagram delivery service
using end-to-end address identifiers and end-to-
end signalling with TCP and UDP transport 71
 IPv6 Implementation Issues
 Large investment in existing infrastructure
 Interoperability between IPv4 and IPv6
 Interoperability of Applications
 Resistance to change
 Support by OS
 No single owner of the Internet
 Cost of new implementation

72
 TCP

 Transmission Control Protocol

• end to end protocol
• Reliable connection = provides flow and error
control
 In TCP terms, a connection is a
temporary association between entities in
different systems

73
 Cont…

 TCP PDU
• Called “TCP segment”
• Includes source and destination port
 Identify respective users (applications)
 pair of ports (together with the IP addresses)
uniquely identify a connection; such an
identification is necessary in order TCP to
track segments between entities.
74
TCP Header

75
 UDP

 User Datagram Protocol

 Alternative to TCP
• end-to-end protocol
 Not guaranteed delivery

76
 UDP

 No preservation of sequence
 No protection against duplication
 Minimum overhead

77
UDP

78
PDU’s in TCP/IP

79
 Network Devices (Reading Assignment)
 Computer networking devices are the devices
which mediate in a computer network
Amplifier
 Repeater
Hub
Bridge
 Switch
 Router
 L3 Switch
Wireless Access Point(WAP)
 Gateway 80
 THANK YOU!!

Q&A?
81