Model Scope and Limitations

The lapb process model implements the data link level procedures as specified in Section 2 of the X.25 Recommendation, with the following limitations:

  • Interframe fill by means of eight-bit flag sequences is not modeled explicitly. Instead, if the lapb process model has not sent a regular LAPB packet within a certain period of time (defined by the “max idle time” process model attribute), it transmits a special LINK_ALIVE packet to indicate to the remote end that the data link is still functioning. (These packets are otherwise ignored by the model.) If a lapb process does not receive any kind of packet from the data link in this length of time, this indicates to the model that an idle channel condition has occurred, and the appropriate recovery procedure is initiated.
  • Because there are no interframe fill sequences, no synchronization between processes occurs; likewise, no explicit bit stuffing is performed on the data in the LAPB packets.
  • Flow control of the packet layer is not specified as part of the process interface; instead, packets arriving from the network layer are queued until the transmitter is available. (Note that command frames are never queued by the process, but are sent directly to the transmitter.)
  • The “busy” condition is not modeled (the lapb process currently uses subqueues of infinite length). As a result, no RNR packets will be transmitted, and so the “remote busy” condition is not modeled either.
  • The LAP (Link Access Protocol) procedure specified in Section 2.6–2.7 of the X.25 Recommendation is not supported; most modern X.25 implementations use only LAPB.