IEEE 802.2

From Wikipedia, the free encyclopedia
Jump to: navigation, search

IEEE 802.2 is the name given to a subsection of the IEEE 802 standard that describes a software component of a computer network. It defines Logical Link Control (LLC), which is the upper portion of the data link layer of the OSI Model. The LLC sublayer presents a uniform interface to the user of the data link service, usually the network layer. Beneath the LLC sublayer is the Media Access Control (MAC) sublayer, which is dependent on the particular medium being used (Ethernet, token ring, FDDI, 802.11, etc.).

The IEEE 802.2 sublayer adds some control information to the message created by the upper layer (typically, the network layer) and passed to the LLC for transmission to the next hop node. The resulting packet is generally referred to as LLC Protocol Data Unit (PDU) and the additional field added by the LLC sublayer for the so-called LLC HEADER. The LLC Header consist of three fields, namely DSAP (Destination Service Access Point), SSAP (Source Service Access Point), and Control.

  • S-SAP is an 8-bit long field that represents the logical address of the network layer entity that has created the message.
  • D-SAP is an 8-bit long field that represents the logical addresses of the network layer entity intended to receive the message.
  • Control field may be either 8 or 16 bit long and, besides defining the packet format, its used to carry some further control information for auxiliary services, such as flow control.

Despite the SAP fields being 8-bit long, some bits have specific significance, so that there is room for only 64 distinguished SAP numbers, which are globally assigned by the IEEE to uniquely identify well established international standards.

IP does not have an assigned SAP number, because only “international standards” could be given globally assigned SAP numbers. Protocols which are not international standards can use a SAP number from the locally administered SAP number space.

The Subnetwork Access Protocol (SNAP) allows EtherType values to be used to specify the protocol being transported atop IEEE 802.2, and also allows vendors to define their own protocol value spaces.

Operational modes[edit]

IEEE 802.2 provides two connectionless and one connection-oriented operational modes:

  • Type 1 is an unacknowledged connectionless mode for a datagram service. It allows for sending frames

The use of multicasts and broadcasts reduce network traffic when the same information needs to be propagated to all stations of the network. However the Type 1 service provides no guarantees regarding the order of the received frames compared to the order in which they have been sent; the sender does not even get an acknowledgment that the frames have been received.

  • Type 2 is a connection-oriented operational mode. Sequence numbering ensures that the frames received are guaranteed to be in the order they have been sent, and no frames are lost.
  • Type 3 is an acknowledged connectionless service. It supports point-to-point communication only .

Each device conforming the IEEE 802.2 standard must support service type 1. Each network node is assigned an LLC Class according to which service types it supports:

LLC
Class
Supported Service Types
1 2 3
I X
II X X
III X X
IV X X X

LLC header[edit]

The 802.2 header includes two eight-bit address fields, called service access points or SAPs in OSI terminology; they are the Destination SAP (DSAP), and the Source SAP (SSAP).

LSAP Values[edit]

The DSAP and SSAP can have the following values:

Value Meaning
Dec Hex
0 00 Null LSAP[1][2]
2 02 Individual LLC Sublayer Mgt[1][2]
3 03 Group LLC Sublayer Mgt[1][2]
4 04 SNA Path Control (individual)[1][2]
5 05 SNA Path Control (group)[2]
6 06 Reserved for DoD IP[1]
14 0E ProWay-LAN[1][2]
24 18 Texas Instruments[2]
66 42 IEEE 802.1 Bridge Spanning Tree Protocol[2]
78 4E EIA-RS 511[1][2]
94 5E ISI IP[1]
126 7E ISO 8208 (X.25 over IEEE 802.2 Type LLC)[2]
128 80 Xerox Network Systems (XNS)[2]
134 86 Nestar[2]
142 8E ProWay-LAN (IEC 955)[1][2]
152 98 ARPANET Address Resolution Protocol (ARP)[2]
166 A6 RDE (route determination entity)
170 AA SNAP Extension Used[1][2]
188 BC Banyan Vines[2]
224 E0 Novell Netware[2]
240 F0 IBM NetBIOS[2]
244 F4 IBM LAN Management (individual)[2]
245 F5 IBM LAN Management (group)[2]
248 F8 IBM Remote Program Load (RPL)[2]
250 FA Ungermann-Bass[2]
254 FE OSI protocols ISO CLNS IS 8473[3][2]
255 FF Global DSAP (cannot be used for SSAP)[1][2]

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, and
  • if it's 1, the packet is a response packet.

The remaining 7 bits of the SSAP specify the LSAP from which the packet was transmitted.

Some protocols, or families of protocols, have one or more SAPs assigned to them; for example, IPv4 has a SAP value of hex 06. Those protocols operate directly on top of 802.2 LLC, which provides both datagram and connection-oriented network services.

The Subnetwork Access Protocol (SNAP) can be used with IEEE 802.2; it allows EtherType values to be used with all IEEE 802 protocols, as well as supporting private protocol ID spaces. When both the DSAP and the SSAP are set to the hexadecimal value 0xAA (or 0xAB, if the low-order bit of the field is set), the SNAP service is requested.

Most IEEE 802 protocols, as well as FDDI, always use 802.2. IEEE 802.3 is an exception; Ethernet originally used Ethernet II framing, with a 2-octet type field containing an EtherType value, and no 802.2 header, but the original IEEE 802.3 specification used a framing wherein the 2-octet field following the 6-octet destination and source MAC addresses contained a frame length, with an 802.2 LLC header following the length field. In IEEE 802.3x-1997, the IEEE Ethernet standard was changed to explicitly allow the use of the 16-bit field after the MAC addresses to be used as a length field or a type field.

There exists an Internet standard, RFC 1042, for encapsulating IP version 4 traffic in IEEE 802.2 frames with LLC/SNAP headers. It is almost never implemented on Ethernet,[4] although it is used on FDDI and on token ring, IEEE 802.11, and other IEEE 802 networks.

IP traffic can not be encapsulated in IEEE 802.2 LLC frames without SNAP because, although there is an LLC protocol type for IP, there is no LLC protocol type for ARP.[citation needed] IP Version 6 can also be transmitted over Ethernet using IEEE 802.2 with LLC/SNAP, but, again, that's almost never used (although LLC/SNAP encapsulation of IPv6 is used on IEEE 802 networks).

Control Field[edit]

Following the destination and source SAP fields is a control field. IEEE 802.2 was conceptually derived from HDLC, and has the same three types of PDUs:

  • Unnumbered format PDUs, or U-format PDUs, with an 8-bit control field, which are intended for connectionless applications;
  • Information transfer format PDUs, or I-format PDUs, with a 16-bit control and sequence numbering field, which are intended to be used in connection-oriented applications;
  • Supervisory format PDUs, or S-format PDUs, with a 16-bit control field, which are intended to be used for supervisory functions at the LLC (Logical Link Control) layer.

Of these three formats, only the U-format is commonly used. The format of a PDU frame is identified by the lower two bits of the first byte of the control field.

References[edit]

  1. ^ a b c d e f g h i j k RFC-1700
  2. ^ a b c d e f g h i j k l m n o p q r s t u v w x Miller, Philip; Cummins, Michael (2000). LAN Technologies Explained. Digital Press. p. 506. ISBN 1555582346. 
  3. ^ Final Text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service
  4. ^ https://lkml.org/lkml/2011/7/27/169

External links[edit]

This article is based on material taken from the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.