Next Generation SONET/SDH

Chapter 3.4 - Point-To-Point Protocol

3.4   POINT-TO-POINT PROTOCOL

The Point-to-Point protocol (PPP) is a protocol that defines the encapsulation of
LAN IP over the B channels of the integrated services digital network (ISDN).

ISDN is defined in two rates: the basic (BRI) at 144 Kbit/s and the primary rate
(BRI) at 1.544 Mbit/s. The BRI consists of two B channels, each at 64 Kbit/s and of
a subrate D channel at 16 Kbit/s. The B channels are used to transport data or voice.
The D channel is used only to transport maintenance and control messages or user
data. By definition, BRI supports any user-defined mix of voice and data. Thus, the
total bandwidth can be used for high-speed data and video, or for a mix of voice and
data.

Based on this, the encapsulation of IP LAN in PPP falls into two categories: one
that requires bandwidth greater than 64 kbit/s and another that requires bandwidth
lower than 64 kbit/s.

Before any LAN IP is transported over PPP, a step-by-step negotiation takes
place. The main negotiation steps are:

  • The Link Control Protocol (LCP)
  • The Authentication Protocol (AP), consisting of the Password Authentication
    Protocol (PAP) and the Challenge Handshake Authentication Protocol
    (CHAP)
  • The Network Control Protocol (NCP)

Each negotiation step uses specifically defined PPP frames (Figure 3.8).

Figure 3.8 PPP: LCP, Authentication, and NCP frames.

The LCP frame consists of the PPP header (0xFF03), the LCP Protocol field
0xC021), the LCP code field, and the LCP options field. The LCP code conveys
the following messages:

  • Configuration request
  • Configuration acknowledge
  • Configuration nonacknowledge
  • Configuration rejected
  • Echo request (to check quality of service)
  • Echo reply

The LCP negotiated options are:

  • Security option
  • Authentication mode
  • Multilink option

The authentication frame consists of the PPP header (0xFF03), the protocol
field, and the parameters field. The protocol field indicates the type of authentication:

  • Password authentication protocol (PAP)
  • Challenge handshake authentication protocol (CHAP)

The network control protocol (NCP), consists of the PPP header (0xFF03), the
NCP Protocol field, the NCP code field, and the NCP options field.

The NCP protocol filed conveys the following:

  • IP control protocol (IPCP) with hex code 0x8021,
  • Novell IP extended control protocol (IPXCP) with hex code 0x802B
  • Bandwidth allocation control protocol (BACP) with hex code 0xC02D

The NCP code field conveys the following:

  • Configuration request; configuration parameters are network number, IPX
    node, and router alias
  • Configuration acknowledge
  • Configuration nonacknowledge
  • Configuration rejected
  • Termination request; used to interrupt PPP traffic before B channel is disconnected
  • Termination acknowledge

Figure 3.9 PPP frames for IP packets requiring. (A) less than 64 kbit/s. (B) greater than 64kbit/s bandwidth.

When the negotiation is completed, IP traffic that is encapsulated in PPP frames
is routed. When the traffic is lower than 64 kbit/s, the encapsulated IP packet is
routed over one B channel. In this case, the PPP frame consists of the PPP header
(0xFF03), the protocol code field (0x0021), and the IP packet field. When traffic is
greater than 64 kbit/s, the encapsulated IP packet is broken into two pieces, which
are routed over both B channels (B1 and B2). This is called the PPP/multilink protocol
(PPP/MLP). In this case, the frame consists of the PPP header (0xFF31), the
protocol code (0x003D), and the IP fragment field (fragment #1 in B1, and fragment
#2 in B2). Figure 3.9 illustrates the frames for each of the two cases.

 

UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Category: Fiber Optic Couplers
Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.