[go: up one dir, main page]

0% found this document useful (0 votes)
54 views30 pages

3.HDLC PPP

Download as pdf or txt
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 30

11-3 HDLC

High-level Data Link Control (HDLC) is a bit -


oriented protocol for communication over point-to-
point and multipoint links. It implements the Stop-
and-Wait protocol we discussed earlier. Although
this protocol is more a theoretical issue than
practical, most of the concept defined in this
protocol is the basis for other practical protocols
such as
PPP, Ethernet, or wireless LANs.
11.1
111.3.1 Transfer Modes

HDLC provides two common transfer modes that


can be used in different configurations: normal
response mode (NRM) and asynchronous balanced
mode (ABM).

11.2
Figure 111.14: Normal response mode

11.3
Figure 111.15: Asynchronous balanced mode

11.4
111.3.2 Framing

To provide the flexibility necessary to support all the


options possible in the modes and configurations
just described, HDLC defines three types of frames:
information frames (I-frames), supervisory frames
(S-frames), and unnumbered frames (U-frames).

11.5
Figure 111.16: HDLC frames

11.6
Figure 111.17: Control field format for the different frame types

11.7
Example 111.5
Figure 111.18 shows how U-frames can be used for
connection establishment and connection release. Node A
asks for a connection with a set asynchronous balanced
mode (SABM) frame; node B gives a positive response with
an unnumbered acknowledgment (UA) frame. After these
two exchanges, data can be transferred between the two
nodes (not shown in the figure). After data transfer, node A
sends a DISC (disconnect) frame to release the connection;
it is confirmed by node B responding with a UA
(unnumbered acknowledgment).

11.8
Figure 111.18: Example of connection and disconnection

11.9
Example 111.6
Figure 111.19 shows two exchanges using piggybacking.
The first is the case where no error has occurred; the second
is the case where an error has occurred and some frames are
discarded.

11.10
Figure 111.19: Example of piggybacking with and without error

11.11
11-4 PPP

One of the most common protocols for point-to-


point access is the Point-to-Point Protocol (PPP).
Today, millions of Internet users who need to
connect their home computers to the server of an
Internet service provider use PPP. To control and
manage the transfer of data, there is a need for a
point-to-point protocol at the data-link layer. PPP is
by far the most common.

11.12
111.4.1 Services

The designers of PPP have included several services


to make it suitable for a point-to-point protocol, but
have ignored some traditional services to make it
simple.

11.13
111.4.2 Framing

PPP uses a character-oriented (or byte-oriented)


frame. Figure 111.20 shows the format of a PPP
frame.

11.14
Figure 111.20: PPP frame format

11.15
111.4.3 Transition Phases

A PPP connection goes through phases which can


be shown in a transition phase diagram (see Figure
111.21).

11.16
Figure 111.21: Transition phases

11.17
111.4.4 Multiplexing

Although PPP is a link-layer protocol, it uses


another set of protocols to establish the link,
authenticate the parties involved, and carry the
network-layer data. Three sets of protocols are
defined to make PPP powerful: the Link Control
Protocol (LCP), two Authentication Protocols (APs),
and several Network Control Protocols (NCPs).

11.18
Figure 111.22: Multiplexing in PPP

11.19
Figure 111.23: LCP packet encapsulated in a frame

11.20
Table 111.1: LCP Packets

11.21
Table 111.2: Common options

11.22
Figure 111.24: PAP packets encapsulated in a PPP frame

11.23
Figure 111.25: CHAP packets encapsulated in a PPP frame

11.24
Figure 111.26: IPCP packet encapsulated in PPP frame

11.25
Table 111.3: Code values for IPCP Packets

11.26
Figure 111.27: IP datagram encapsulated in a PPP frame

11.27
Figure 111.28: Multilink PPP

11.28
Example 111.7
Let us go through the phases followed by a network layer
packet as it is transmitted through a PPP connection. Figure
111.29 shows the steps. For simplicity, we assume
unidirectional movement of data from the user site to the
system site (such as sending an e-mail through an ISP).

11.29
Figure 111.29: An example

11.30

You might also like