Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Searchable, convenient, complete TCP/IP information.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
      9  TCP/IP Network Interface Layer (OSI Data Link Layer) Protocols
           9  TCP/IP Serial Line Internet Protocol (SLIP) and Point-to-Point Protocol (PPP)
                9  Point-to-Point Protocol (PPP)
                     9  PPP Feature Protocols

Previous Topic/Section
PPP Encryption Control Protocol (ECP) and Encryption Algorithms
Previous Page
Pages in Current Topic/Section
12
3
Next Page
PPP Bandwidth Allocation Protocol (BAP) and Bandwidth Allocation Control Protocol (BACP)
Next Topic/Section

PPP Multilink Protocol (MP/MLP/MLPPP)
(Page 3 of 3)

PPP Multilink Protocol Setup and Configuration

To use MP, both devices must have it implemented as part of their PPP software and must negotiate its use. This is done by LCP as part of the negotiation of basic link parameters in the Link Establishment phase (just like Link Quality Reporting). Three new configuration options are defined to be negotiated to enable MP:

  • Multilink Maximum Received Reconstructed Unit: Provides the basic indication that the device starting the negotiation supports MP and wants to use it. The option contains a value specifying the maximum size of PPP frame it supports. If the device receiving this option does not support MP it must respond with a Configure-Reject LCP message.

  • Multilink Short Sequence Number Header Format: Allows devices to negotiate use of a shorter sequence number field for MP frames, for efficiency. (See the topic on MP frames for more.)

  • Endpoint Discriminator: Uniquely identifies the system; used to allow devices to determine which links go to which other devices.

Before MP can be used, a successful negotiation of at least the Multilink Maximum Received Reconstructed Unit option must be performed on each of the links between the two devices. Once this is done and an LCP link exists for each of the physical links, a virtual bundle is made of the LCP links and MP is enabled.

PPP Multilink Protocol Operation

As mentioned above, MP basically sits between the network layer and the regular PPP links and acts as a “middleman”. Here is what it does for each “direction” of communication:

  • Transmission: MP accepts datagrams received from any of the network layer protocols configured using appropriate NCPs. It first encapsulates them into a modified version of the regular PPP frame. It then takes that frame and decides how to transmit it over the multiple physical links. Typically, this is done by dividing the frame into fragments that are evenly spread out over the set of links. These are then encapsulated and sent over the physical links. However, an alternate strategy can also be implemented as well, such as alternating full-sized frames between the links. Also, smaller frames are typically not fragmented, nor are control frames such as those used for link configuration.

  • Reception: MP takes the fragments received from all physical links and reassembles them into the original PPP frame. That frame is then processed like any PPP frame, by looking at its Protocol field and passing it to the appropriate network layer protocol.

The fragments used in MP are similar in concept to IP fragments, but of course these are different protocols running at different layers. To PPP or MP, an IP fragment is just an IP datagram like any other.

The fragmenting of data in MP introduces a number of complexities that the protocol must handle. For example, since fragments are being sent roughly concurrently, we need to identify them with a sequence number to facilitate reassembly. We also need some control information to identify the first and last fragments. A special frame format is used for MP fragments to carry this extra information, which I describe in the section on PPP frame formats. That topic also contains more information about how fragmenting is accomplished, as well as an illustration that demonstrates how it works.

Related Information: I also recommend reading the next topic, which describes two protocols defined after MP to better control how it works: BAP and BACP.



Previous Topic/Section
PPP Encryption Control Protocol (ECP) and Encryption Algorithms
Previous Page
Pages in Current Topic/Section
12
3
Next Page
PPP Bandwidth Allocation Protocol (BAP) and Bandwidth Allocation Control Protocol (BACP)
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.