Editing IEEE 802.2 (section)

===LSAP values===
Although the LSAP fields are 8 bits long, the low-order bit is reserved for special purposes, leaving only 128 values available for most purposes.

The low-order bit of the DSAP indicates whether it contains an individual or a group address:
* If the low-order bit is 0, the remaining 7 bits of the DSAP specify an individual address, which refers to a single local service access point (LSAP) to which the packet should be delivered.
* If the low-order bit is 1, the remaining 7 bits of the DSAP specify a group address, which refers to a group of LSAPs to which the packet should be delivered.

The low-order bit of the SSAP indicates whether the packet is a command or response packet:
* If it's 0, the packet is a command packet.
* If it's 1, the packet is a response packet.
The remaining 7 bits of the SSAP specify the LSAP (always an individual address) from which the packet was transmitted.

LSAP numbers are globally assigned by the IEEE to uniquely identify well established international standards.

{| class="wikitable"
|+ Individual LSAP addresses
|-
!colspan="2"| Value
!rowspan="2"| Meaning
|-
! Dec !! Hex
|-
| 0 || 00 || Null LSAP<ref name="rfc1700">{{cite IETF| title = Assigned Numbers | rfc = 1700 | sectionname = IEEE 802 NUMBERS OF INTEREST | page = 165 | last1 = Postel | first1 = J. | author-link1 = Jon Postel| last2 = Reynolds | first2 = J. | author-link2 = Joyce K. Reynolds | date = October 1994}}</ref><ref name= "LAN_tech">{{cite book | title = LAN Technologies Explained | surname1 = Miller | given1 = Philip | surname2 = Cummins | given2 = Michael | isbn = 1-55558-234-6 | publisher = Digital Press | year = 2000 | page = [https://archive.org/details/lantechnologiese0000mill/page/506 506] | url = https://archive.org/details/lantechnologiese0000mill/page/506 }}</ref>
|-
| 2 || 02 || Individual [[Logical link control|LLC Sublayer]] Mgt<ref name="rfc1700" /><ref name="LAN_tech" />
|-
| 4 || 04 || [[Systems Network Architecture|SNA]] Path Control (individual)<ref name="rfc1700" /><ref name="LAN_tech" />
|-
| 6 || 06 || Reserved for DoD [[Internet Protocol|IP]]<ref name="rfc1700" />
|-
| 14 || 0E || ProWay-LAN<ref name="rfc1700" /><ref name="LAN_tech" />
|-
| 24 || 18 || [[Texas Instruments]]<ref name="LAN_tech" />
|-
| 66 || 42 || IEEE 802.1 Bridge Spanning Tree Protocol<ref name="LAN_tech" />
|-
| 78 || 4E || EIA-RS 511<ref name="rfc1700" /><ref name="LAN_tech" />
|-
| 94 || 5E || ISI IP<ref name="rfc1700" />
|-
| 126 || 7E || ISO 8208 ([[X.25]] over IEEE 802.2 Type LLC)<ref name="LAN_tech" />
|-
| 128 || 80 || Xerox Network Systems (XNS)<ref name="LAN_tech" />
|-
| 130 || 82 || BACnet/Ethernet<ref>{{Citation | url = https://www.ashrae.org/resources--publications/bookstore/standard-135 | title = The BACnet Standard—Standard 135-2012 | publisher = Ashrae}}.</ref>
|-
| 134 || 86 || Nestar<ref name="LAN_tech" />
|-
| 142 || 8E || ProWay-LAN (IEC 955)<ref name="rfc1700" /><ref name="LAN_tech" />
|-
| 152 || 98 || ARPANET Address Resolution Protocol (ARP)<ref name="LAN_tech" />
|-
| 166 || A6 || RDE (route determination entity)
|-
| 170 || AA || [[Subnetwork Access Protocol|SNAP]] Extension Used<ref name="rfc1700" /><ref name="LAN_tech" />
|-
| 188 || BC || [[Banyan VINES]]<ref name="LAN_tech" />
|-
| 224 || E0 || [[Novell NetWare]]<ref name="LAN_tech" />
|-
| 240 || F0 || [[IBM]] [[NetBIOS]]<ref name="LAN_tech" />
|-
| 244 || F4 || [[IBM]] LAN Management (individual)<ref name="LAN_tech" />
|-
| 248 || F8 || [[IBM]] Remote Program Load (RPL)<ref name="LAN_tech" />
|-
| 250 || FA || Ungermann-Bass<ref name="LAN_tech" />
|-
| 254 || FE || OSI [[Connectionless-mode Network Service]]:<ref name="LAN_tech" /> CLNP,<ref>{{Citation | url = https://datatracker.ietf.org/doc/html/rfc994 | publisher = IETF | series = RFC | number = 994 | title = Final Text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service}}.</ref> ISIS,<ref>{{Cite web|title=ISO/IEC 10589:2002|url=https://www.iso.org/cms/render/live/en/sites/isoorg/contents/data/standard/03/09/30932.html|access-date=2020-12-18|website=ISO|language=en}}</ref> ESIS<ref>{{Cite web|title=ISO 9542:1988|url=https://www.iso.org/cms/render/live/en/sites/isoorg/contents/data/standard/01/72/17285.html|access-date=2020-12-18|website=ISO|language=en}}</ref>
|}

{| class="wikitable"
|+ Group DSAP addresses (not valid for SSAP)
|-
!colspan="2"| Value
!rowspan="2"| Meaning
|-
! Dec !! Hex
|-
| 3 || 03 || Group [[Logical link control|LLC Sublayer]] Mgt<ref name="rfc1700" /><ref name="LAN_tech" />
|-
| 5 || 05 || [[Systems Network Architecture|SNA]] Path Control (group)<ref name="LAN_tech" />
|-
| 245 || F5 || [[IBM]] LAN Management (group)<ref name="LAN_tech" />
|-
| 255 || FF || Global DSAP (broadcast to all)<ref name="rfc1700" /><ref name="LAN_tech" />
|}

The protocols or families of protocols which have assigned one or more SAPs may operate directly on top of 802.2 LLC.  Other protocols may use the [[Subnetwork Access Protocol]] (SNAP) with IEEE 802.2 which is indicated by the hexadecimal value 0xAA (or 0xAB, if the source of a response) in SSAP and DSAP.  The SNAP extension allows using [[EtherType]] values or private protocol ID spaces in all [[IEEE 802]] networks. It can be used both in datagram and in connection-oriented network services.

[[Ethernet]] ([[IEEE 802.3]]) networks are an exception; the IEEE 802.3x-1997 standard explicitly allowed using of the [[Ethernet II framing]], where the 16-bit field after the MAC addresses does not carry the length of the frame followed by the IEEE 802.2 LLC header, but the [[EtherType]] value followed by the upper layer data. With this framing only datagram services are supported on the [[data link layer]].