1 chapter 16 protocols and protocol layering. 2 protocol agreement about communication specifies ...

1

Chapter 16Chapter 16

Protocols and

Protocol Layering

2

ProtocolProtocol

Agreement about communicationSpecifies

Format of messages (syntax)Meaning of messages (semantics)Rules for exchangeProcedure for handling problems

3

Need for ProtocolsNeed for Protocols

Hardware is low levelMany problems can occur

Bits corrupted or destroyedEntire packet lostPacket duplicatedPackets delivered out of order

4

Need for Protocols (continued)

Need for Protocols (continued)

Need mechanisms to distinguish amongMultiple computers on a networkMultiple applications on a computerMultiple copies of a single application on a

computer

5

Set of ProtocolsSet of Protocols

Work togetherEach protocol solves part of communication

problemKnown as

Protocol suiteProtocol family

Designed in layers

6

Plan for Protocol DesignPlan for Protocol Design

Intended for protocol designersDivides protocols into layersEach layer devoted to one subproblemExample: ISO 7-layer reference model

7

Illustration of the 7-Layer Model

Illustration of the 7-Layer Model

Defined earlyNow somewhat datedDoes not include internet layer!

8

ISO LayersISO Layers

Layer 1: PhysicalUnderlying hardware

Layer 2: Data Link (media access)Hardware frame definitions

Layer 3: NetworkPacket forwarding

Layer 4: TransportReliability

9

ISO Layers (continued)ISO Layers (continued)

Layer 5: SessionLogin and passwords

Layer 6: PresentationData representation

Layer 7: ApplicationServices for common applications

10

TCP/IP protocol suiteTCP/IP protocol suite

11

Layers and Protocol Software

Layers and Protocol Software

Protocol software follows layering modelOne software module per layerModules cooperateIncoming or outgoing data passes from one

module to anotherEntire set of modules known as stack

12

Illustration of StacksIllustration of Stacks

13

Layers and Packet Headers

Layers and Packet Headers

Each layerPrepends header to outgoing packetRemoves header from incoming packet

14

Example of encapsulationExample of encapsulation

15

Scientific Layering Principle

Scientific Layering Principle

Software implementing layer N at the destination receives exactly the message sent by software implementing layer N at the source

16

Illustration of Layering Principle

Illustration of Layering Principle

17

Protocol TechniquesProtocol Techniques

For bit corruptionParityChecksumCRC

For out-of-order deliverySequence numbers

DuplicationSequence numbers

18

Protocol Techniques (continued)

Protocol Techniques (continued)

For lost packetsPositive acknowledgement and retransmission

For replay (excessive delay)Unique message ID

For data overrunFlow control

19

Flow ControlFlow ControlNeeded because

Sending computer system faster than receiving computer

Sending application faster than receiving application

Related to bufferingTwo forms

Stop-and-goSliding window

20

Stop-And-Go Flow ControlStop-And-Go Flow Control

Sending SideTransmits one packetWaits for signal from receiver

Receiving sideReceives and consumes packetsTransmits signal to sender

Inefficient

21

Sliding Window Flow Control

Sliding Window Flow Control

Receiving sideEstablishes multiple buffers and informs sender

Sending sideTransmits packets for all available buffersOnly waits if no signal arrives before

transmissionReceiving side

Sends signals as packets arrive

22

Illustration of SlidingWindow on Sending Side

Illustration of SlidingWindow on Sending Side

Window tells how many packets can be sentWindow moves as acknowledgements arrive

23

PerformancePerformance

Stop-and-goSlowUseful only in special cases

Sliding windowFastNeeded in high-speed network

24

Comparison of Flow Control

Comparison of Flow Control

25

Why Sliding Window?Why Sliding Window?

SimultaneouslyIncrease throughputControl flow

Speedup

Tw = min(B, TG * W)where

B is underlying hardware bandwidthTW is sliding window throughputTG is stop-and-go throughputW is the window size

26

CongestionCongestion

Fundamental problem in networksCaused by traffic, not hardware failureAnalogous to congestion on a highwayPrinciple cause of delay

27

Illustration of ArchitectureThat Can Experience

Congestion

Illustration of ArchitectureThat Can Experience

Congestion

Multiple sourcesBottleneck

Dealing with CongestionDealing with Congestion

Congestion results in filled buffers in packet switches => packets will be discarded => retransmission => more packets…..

SolutionsIncreasing buffer spaceReducing the amount of packets in the network

Packet switches inform senders, or Senders use packet loss as an indication

28

29

Congestion and LossCongestion and Loss

Modern network hardware works well; most packet loss results from congestion, not from hardware failure