CH 11
CH 11
11.1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
11-1 FRAMING
11.2
Figure 11.1 A frame in a character-oriented protocol
11.3
Figure 11.2 Byte stuffing and unstuffing
11.4
Note
11.5
Figure 11.3 A frame in a bit-oriented protocol
11.6
Note
11.7
Figure 11.4 Bit stuffing and unstuffing
11.8
11-2 FLOW AND ERROR CONTROL
11.9
Note
11.10
Note
11.11
11-3 PROTOCOLS
Now let us see how the data link layer can combine
framing, flow control, and error control to achieve the
delivery of data from one node to another. The
protocols are normally implemented in software by
using one of the common programming languages. To
make our discussions language-free, we have written
in pseudocode a version of each protocol that
concentrates mostly on the procedure instead of
delving into the details of language rules.
11.12
11.13
11.14
11.15
Design of Stop-and-Wait Protocol
11.16
11.17
11.18
Note
11.19
Note
11.20
Note
11.21
Example 11.3
11.22
Figure 11.11 Flow diagram for Example 11.3
11.23
Example 11.4
Solution
The bandwidth-delay product is
11.24
Example 11.4 (continued)
The system can send 20,000 bits during the time it takes
for the data to go from the sender to the receiver and then
back again. However, the system sends only 1000 bits. We
can say that the link utilization is only 1000/20,000, or 5
percent. For this reason, for a link with a high bandwidth
or long delay, the use of Stop-and-Wait ARQ wastes the
capacity of the link.
11.25
POINT-TO-POINT PROTOCOL (PPP)
11.26
11.27
11.28