Logical Link Control – IEEE 802.2
The IEEE 802.2 standards for Logical Link Control define a programming interface between that part of the communications software that controls the network interface card (the Media Access Control and Physical Medium Dependent components) and the overlying protocol stack (IP, NetBIOS, NetWare, etc.).
The connection between the network interface card and the rest of the communications system is through a structure called a Service Access Point (SAP, pronounced like the sap from which maple syrup is made. The three letters, when spoken individually, “S”, “A”, “P”, refer to a SQL-based accounting software system, the “SQL Accounting Program”)
The SAP differentiates between communications protocols; there’s a SAP for NetBIOS, another for SNA, another for NetWare, and so on. A programmer can select Type 2 Logical Link Control in which case the frames are given sequence numbers as they pass through the SAP and the 802.2 Logical Link Control layer at the receiver provides an acknowledgement for received frames. This creates a reliable data transfer mechanism at the Data Link Layer. Type 1 Logical Link Control simply provides the differentiation function, with no sequence and acknowledgement process.
This section of the compendium discusses the types of Logical Link Control behavior that you might observe with your protocol analyzer and details how to isolate and describe problems that may occur.
Topics In This Discussion
- Defining “Connection-less” and “Connection-Oriented”
- Type I LLC
- Setting Up a Type II LLC Connection
- Transmitting and Acknowledging
- Data in Type II LLC
- Protocol Analysis Techniques for Type II LLC
- The Bits in the LLC Header
- Type I LLC Commands and Responses
- Type II LLC Commands and Responses
- Viewing LLC with your Protocol Analyzer
- The Rationale for Using a Reliable Data Link