|
DataMuseum.dkPresents historical artifacts from the history of: CP/M |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about CP/M Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 48512 (0xbd80)
Types: RcTekst
Names: »99109973.WP«
└─⟦7fab0c8ae⟧ Bits:30005866/disk3.imd Dokumenter i RcTekst format (RCSL 99-1-*)
└─⟦this⟧ »99109973.WP«
╱04002d4e0c00060000000003014831600000000000000000000000000000000000000000000000002a34414b555f69737d8791ffffffffff04╱
↲
╞ __________________________↲
╞ RCSL No.:╞ 991 09973↲
╞ Edition:╞ December 1984↲
╞ Authors: ╞ Ejvind Lynning (ed.)↲
╞ ╞ John Svensson↲
╞ ╞ Peter Holm↲
╞ ╞ Jesper A. Tågholt↲
↲
↲
↲
↲
FOR INTERNAL USE↲
↲
↲
↲
↲
________________________________________________________________________↲
↲
Title:↲
↲
┆06┆RCLLC↲
┆06┆Protocol for Logical Link Control↲
┆06┆in RC Local Area Networks↲
↲
↲
________________________________________________________________________↲
════════════════════════════════════════════════════════════════════════
↓
┆06┆i↲
↲
↲
↲
┆a1┆TABLE OF CONTENTS PAGE↲
╱04002d4e0c0006000000000301483160000000000000000000000000000000000000000000000000050a11191e464b555f69737dffffffff04╱
╱04002d4e0c00060000000003014831600000000000000000000000000000000000000000000000002a34414b555f69737d8791ffffffffff04╱
↓
↲
↲
1.╞ INTRODUCTION ................................................... 1↲
↲
2.╞ FUNDAMENTAL CONCEPTS ........................................... 3↲
↲
3.╞ SERVICE INTERFACES ............................................. 5↲
╞ 3.1╞ MAC Service ...............................................╞ 5↲
╞ 3.2╞ RCLLC Services ............................................╞ 6↲
╞ ╞ 3.2.1╞ SAP Activation and Deactivation ....................╞ 6↲
╞ ╞ ╞ 3.2.1.1╞ ACTIVATE.request ...........................╞ 6↲
╞ ╞ ╞ 3.2.1.2╞ ACTIVATE.confirm ...........................╞ 7↲
╞ ╞ ╞ 3.2.1.3╞ DEACTIVATE.request .........................╞ 7↲
╞ ╞ ╞ 3.2.1.4╞ DEACTIVATE.confirm .........................╞ 8↲
╞ ╞ 3.2.2╞ Loop-back Test Service .............................╞ 8↲
╞ ╞ ╞ 3.2.2.1╞ TEST.request ...............................╞ 8↲
╞ ╞ ╞ 3.2.2.2╞ TEST.confirm ...............................╞ 9↲
╞ ╞ ╞ 3.2.2.3╞ TEST.indication ............................╞ 9↲
╞ ╞ 3.2.3╞ Type 1 Service .....................................╞ 10↲
╞ ╞ ╞ 3.2.3.1 UDATA.request ..............................╞ 10↲
╞ ╞ ╞ 3.2.3.2╞ UDATA.indication ...........................╞ 11↲
╞ ╞ 3.2.4╞ Client Network Service .............................╞ 11↲
╞ ╞ ╞ 3.2.4.1╞ CONNECT.indication .........................╞ 12↲
╞ ╞ ╞ 3.2.4.2╞ DISCONNECT.indication ......................╞ 13↲
╞ ╞ ╞ 3.2.4.3╞ DISCONNECT.acknowledge .....................╞ 13↲
╞ ╞ ╞ 3.2.4.4╞ DATA.request ...............................╞ 13↲
╞ ╞ ╞ 3.2.4.5 DATA.confirm ............................... 14↲
╞ ╞ ╞ 3.2.4.6╞ DATA.indication ............................╞ 14↲
↲
4.╞ RCLLC PROCEDURES ............................................... 15↲
╞ 4.1╞ Type 1 Procedures .........................................╞ 15↲
╞ ╞ 4.1.1╞ Unacknowledged Data Transfer .......................╞ 15↲
╞ ╞ 4.1.2╞ Loop-back Test Procedure ...........................╞ 16↲
╞ ╞ 4.1.3╞ Station Identification Exchange ....................╞ 16↲
╞ 4.2╞ Procedures for Client Network Service .....................╞ 17↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆06┆ii↲
↲
↲
↲
┆a1┆TABLE OF CONTENTS (cont.) PAGE↲
↲
↲
5. RCLLC PROTOCOL ELEMENTS ........................................ 23↲
╞ 5.1╞ Type 1 Protocol Elements .................................. 25↲
╞ ╞ 5.1.1╞ UI (Unnumbered Information) ........................╞ 25↲
╞ ╞ 5.1.2 XID (eXchange IDentification) ......................╞ 26↲
╞ ╞ 5.1.3╞ TEST ...............................................╞ 26↲
╞ 5.2╞ Protocol Elements for Client Network Service ..............╞ 26↲
╞ ╞ 5.2.1╞ ACTIVE_SAP .........................................╞ 26↲
╞ ╞ 5.2.2╞ RESET ..............................................╞ 27↲
╞ ╞ 5.2.3╞ RACK ...............................................╞ 28↲
╞ ╞ 5.2.4╞ DATA ...............................................╞ 28↲
╞ ╞ 5.2.5╞ ACK ................................................╞ 28↲
↲
↲
┆a1┆APPENDICES↲
↲
A. References .....................................................╞ 30↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆RCLLC Protocol┆05┆Page ┆0b┆↲
┆a1┆1. INTRODUCTION↲
↲
This document is the reference definition of the protocol for logical ↓
link control in an RC local area network, the ┆a1┆RCLLC protocol┆e1┆. The ↓
protocol applies to the intercommunication between those stations ↓
attached to such a local area network which are RC products. It does not ↓
rule out the attachment of other manufacturers' products to the same ↓
network, nor the cooperation between RC products and such other ↓
products.↲
↲
In order to place the protocol in proper context, a description of the ↓
service provided by the RCLLC layer and of the behavior of RCLLC ↓
entities is also given. The description of the RCLLC service is to be ↓
understood in an abstract sense and should not be interpreted as a ↓
prescription for an implementation. In particular,↲
↲
╞ - ┆84┆some of the service primitives may be statically implemented, i.e. ↓
┆19┆┆86┆┄┄as initializations, which may not require any interaction between ↓
┆19┆┆86┆┄┄entities;↲
╞ - ┆84┆some stations may offer only a subset of the complete RCLLC ↓
┆19┆┆86┆┄┄service.↲
↲
The protocol and service defined in this document form an extension to ↓
the proposed ISO LLC type 1 protocol and service (ref. 1), viz.:↲
↲
╞ - ┆84┆all frames which are valid according to the RCLLC protocol are ↓
┆19┆┆86┆┄┄also valid ISO LLC type 1 frames;↲
╞ - ┆84┆RCLLC adds protocol functions and interface service functionality ↓
┆19┆┆86┆┄┄to ISO LLC type 1 in a fashion which one might choose to consider ↓
┆19┆┆86┆┄┄as a sublayer added on top of an LLC type 1 sublayer.↲
↲
The services of LLC type 1 are data transfer on connectionless data ↓
links, allowing multiple independent clients within each station, plus ↓
facilities for point-to-point loop back test traffic.↲
↲
The essential service of the RCLLC layer, which constitutes an extension ↓
to the type 1 service, is called ┆a1┆client network service┆e1┆. This service ↓
comprises the dynamic configuration, maintenance and supervision of ↓
┆8c┆┆83┆┆c8┆↓
multiple independent networks of clients. Connection-based data transfer ↓
with sequence control and retransmission to avoid loss of or damage to ↓
data is performed between any pair of clients belonging to the same ↓
client network.↲
↲
Two types of client networks are foreseen and specifically catered for ↓
in the protocol design:↲
↲
1) ┆84┆IMC networks (refs. 3,4) which may involve a wide variety of RC ↓
┆19┆┆83┆┄┄products. The (RCLLC) clients in an IMC network are the IMC nodes;↲
2) ┆84┆CCP/M DR NET (ref. 5) networks in which the stations are RC750 ↓
┆19┆┆83┆┄┄Personal Computers. Each of these may also contain an IMC node and ↓
┆19┆┆83┆┄┄thus belong to two client networks.↲
↲
Like the ISO LLC protocol the RCLLC protocol assumes that the services ↓
of a Medium Access Control layer are available. The services of this ↓
layer are defined so as to be independent of the actual medium. In ↓
addition to transmission of frames to a specific station a multicast ↓
function must be provided.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆2. FUNDAMENTAL CONCEPTS↲
↲
The following terms are used in this document with their standard ↓
meaning as defined in the ISO model for Open Systems Interconnection ↓
(ref. 2): station, layer, entity, peer, protocol, service primitive, ↓
data link, connection.↲
↲
Further concepts and terminology which are not necessarily found in the ↓
ISO model, but used in the present document, are defined in the ↓
following:↲
↲
An ┆a1┆RCLLC station┆e1┆ is a station which is attached to the local area ↓
network and hosts an RCLLC entity that communicates with peer entities ↓
in other RCLLC stations according to the RCLLC protocol. A station which ↓
supports only the LLC type 1 protocol and not the full RCLLC protocol is ↓
not considered an RCLLC station. Until the RCLLC protocol is adopted by ↓
other manufacturers, an RCLLC station will be the same as an RC product ↓
attached to the network.↲
↲
The ┆a1┆M┆e1┆edium ┆a1┆A┆e1┆ccess ┆a1┆C┆e1┆ontrol (MAC) layer is the only protocol layer between ↓
the RCLLC layer and the physical network. Each RCLLC station contains ↓
precisely one MAC entity and one RCLLC entity. The ┆a1┆station address┆e1┆ is a ↓
unique address which identifies the station within the local area ↓
network. It follows that the station address is also a unique address of ↓
the RCLLC entity.↲
↲
The data units that are transmitted among RCLLC entities using the MAC ↓
service are called ┆a1┆RCLLC protocol elements┆e1┆.↲
↲
A ┆a1┆client┆e1┆ is an RCLLC-user, i.e. an entity making use of the RCLLC ↓
service and located in the layer above the RCLLC layer.↲
↲
An RCLLC ┆a1┆S┆e1┆ervice ┆a1┆A┆e1┆ccess ┆a1┆P┆e1┆oint (SAP) is the (logical) point at which a ↓
client accesses the RCLLC service. Within an RCLLC station each SAP is ↓
assigned a ┆a1┆local SAP address┆e1┆ in the range 1..63. The ┆a1┆complete SAP ↓
┆19┆┄┄┆84┆address┆e1┆ is the pair (station address, local SAP address) which uniquely ↓
identifies a SAP within the local area network.↲
↲
┆8c┆┆83┆┆c8┆↓
A SAP can be ┆a1┆inactive┆e1┆, in which case it is effectively unknown to the ↓
RCLLC layer so that all data and control information addressed to it is ↓
discarded; or it can be ┆a1┆active┆e1┆. An active SAP can be used to obtain ↓
either type 1 service or client network service, but not both.↲
↲
The RCLLC layer maintains a number of logical ┆a1┆client networks┆e1┆. A client ↓
network has a ┆a1┆network number┆e1┆ (within the local area network), which must ↓
be in the range 1..63, and comprises all active SAPs within RCLLC ↓
stations on the local area network whose local SAP addresses are equal ↓
to this number, and for which client network service has been requested.↲
↲
For all RC local area networks client network number 1 is assigned to an ↓
IMC network, i.e. the IMC nodes in the RCLLC stations of a local area ↓
network will all access the RCLLC service using a local SAP address of ↓
1. Similarly, client network number 2 is used for DR NET.↲
↲
Associated with each client network within a local area network is a ↓
multicast address which delimits the RCLLC stations that take part in ↓
the client network from all other stations on the network; i.e. a frame ↓
which is transmitted on the local area network with this multicast ↓
address should be received by (the MAC entity within) a station if and ↓
only if the station is an RCLLC station containing a SAP belonging to ↓
the client network.↲
↲
Each SAP belonging to a client network has an associated ┆a1┆SAP mask┆e1┆. The ↓
SAP mask is a 16-bit word. Two SAP masks ┆a1┆match┆e1┆ if at least one bit ↓
position contains a one in both masks, i.e. if a logical AND-operation ↓
yields a non-zero result. The RCLLC layer will maintain connections ↓
between all pairs of SAPs belonging to the same client network whose ↓
masks match.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆3. SERVICE INTERFACES↲
↲
The MAC layer is the foundation on which the RCLLC layer is built, and ↓
its service is therefore described briefly.↲
↲
The description of the RCLLC layer goes into much more detail, because ↓
there is a very direct relationship between the RCLLC service as it ↓
appears in the individual service primitives and the elements and ↓
procedures which constitute the RCLLC protocol. The description of the ↓
RCLLC service also forms a point of reference for the definition of ↓
protocols for services to be built on top of the RCLLC layer.↲
↲
↲
┆a1┆3.1 MAC Services↲
↲
The function performed by the MAC layer is to accept from an RCLLC ↓
entity a MAC service data unit, to transmit it to one, several ↓
(multicast), or all stations in the network, and in the receiving ↓
station(s) to deliver the unit to the destination RCLLC entity(ies).↲
↲
In the case of a CSMA/CD type network the MAC service includes retrans┄↓
mission following a detected collision.↲
↲
There is no guarantee that a MAC service data unit which is transmitted ↓
from one station on a network is received at the destination station(s).↲
↲
Each MAC entity is sensitive to its station address and possibly one or ↓
more multicast addresses, i.e. addresses of groups of stations to which ↓
the station belongs. Only MAC service data units transmitted with one of ↓
these addresses or the broadcast address (if applicable) will be ↓
received by the MAC entity.↲
↲
Padding of frames containing MAC service data units in order to reach a ↓
minimum size required by the type of physical network in question is ↓
performed by the MAC layer. The padding is removed again before ↓
delivery.↲
↲
┆8c┆┆83┆┆bc┆↓
A network dependent maximum size for MAC service data units is also ↓
enforced by the MAC layer, i.e. data units exceeding the maximum size ↓
will not be transmitted, and the receiver part of a MAC entity will ↓
discard all incoming frames that would yield a data unit longer than the ↓
maximum size.↲
↲
The RCLLC layer uses the MAC service by transmitting each RCLLC protocol ↓
element as a MAC service data unit.↲
↲
↲
┆a1┆3.2 RCLLC Services↲
↲
The RCLLC services are obtained by a client through an active SAP. A SAP ↓
can be used either for type 1 service or for client network service, but ↓
not for both. The loop-back test facility is available regardless of the ↓
choice of type 1 or client network service.↲
↲
↲
┆a1┆3.2.1 SAP Activation and Deactivation↲
↲
There are four primitives to request activation and deactivation of a ↓
SAP and to confirm the processing of these requests. They are described ↓
in the following subsections.↲
↲
↲
┆a1┆3.2.1.1 ACTIVATE.request↲
↲
The primitive which requests the activation of a SAP is passed from a ↓
client to the RCLLC entity.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆specifies the local SAP address of the SAP to be ↓
┆19┆┆93┆┄┄activated.↲
service_type╞ ┆84┆specifies whether type 1 service or client network ↓
┆19┆┆93┆┄┄service is requested; the following two parameters ↓
┆19┆┆93┆┄┄are only present if client network service is ↓
┆19┆┆93┆┄┄requested.↲
┆8c┆┆83┆┆c8┆↓
SAP_mask╞ ┆84┆specifies the SAP mask used to prevent establishment ↓
┆19┆┆93┆┄┄of undesired connections, cf. section 4.↲
client_info╞ ┆84┆is a data unit which is transmitted and passed to the ↓
┆19┆┆93┆┄┄remote client in the CONNECT_indication primitive ↓
┆19┆┆93┆┄┄whenever a connection is established between the ↓
┆19┆┆93┆┄┄activated SAP and a remote SAP.↲
↲
↲
┆0e┆↓
┆a1┆3.2.1.2 ACTIVATE.confirm↲
↲
The primitive which is issued in response to an ACTIVATE.request ↓
primitive is passed from the RCLLC entity to the requesting client.↲
┆0f┆↓
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆is the local SAP address of the SAP in question as ↓
┆19┆┆93┆┄┄specified in the request.↲
result╞ ┆84┆indicates whether the SAP was successfully activated.↲
↲
When a SAP has been activated for type 1 service UDATA.request primi┄↓
tives may be issued requesting the transmission of data.↲
↲
When a SAP has been activated for client network service, the RCLLC ↓
layer will automatically begin to establish the appropriate connections. ↓
As each connection is established, the client will be informed by means ↓
of a CONNECT.indication primitive and may subsequently request trans┄↓
mission of data by issuing DATA.request primitives.↲
↲
In either case, once a SAP has been activated, the client may issue the ↓
TEST.request primitive to request a loop-back test.↲
↲
↲
┆a1┆3.2.1.3 DEACTIVATE.request↲
↲
The primitive which requests the deactivation of a SAP is passed from a ↓
client to the RCLLC entity.↲
↲
┆8c┆┆83┆┆bc┆↓
┆0e┆↓
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆specifies the local SAP address of the SAP to be ↓
┆19┆┆93┆┄┄deactivated.↲
┆0f┆↓
↲
↲
┆a1┆3.2.1.4 DEACTIVATE.confirm↲
↲
The primitive which is issued in response to a DEACTIVATE.request primi┄↓
tive is passed from the RCLLC entity to the requesting client.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆is the local SAP address of the SAP in question as ↓
┆19┆┆93┆┄┄specified in the request.↲
↲
↲
┆a1┆3.2.2 Loop-back Test Service↲
↲
The loop-back test facility allows a client to request a test of the ↓
transmission path between the local RCLLC entity and one or more remote ↓
RCLLC entities without requiring the participation of any remote ↓
client(s). This is done by transmitting a TEST protocol element ↓
(command) to the specified RCLLC entity/entities to which it/each of ↓
them must respond by transmitting a TEST protocol element (response) ↲
addressed to the requesting client (SAP).↲
↲
Notice: No indication is given if the responding protocol element fails ↓
to arrive from any or all of the RCLLC entities addressed in the ↓
TEST.request primitive.↲
↲
↲
┆a1┆3.2.2.1 TEST.request↲
↲
The primitive, which requests that one or more transmission paths be ↓
tested, is passed from a client to the RCLLC entity.↲
↲
┆8c┆┆83┆┆bc┆↓
┆0e┆↓
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ is the local SAP address.↲
┆0f┆↓
rem_addr╞ ┆84┆is the station address of the remote RCLLC entity; a ↓
┆19┆┆93┆┄┄multicast or broadcast address may be used in place ↓
┆19┆┆93┆┄┄of a specific station address to request testing of ↓
┆19┆┆93┆┄┄multiple transmission paths.↲
tdu╞ ╞ ┆84┆test data unit, transmitted in the information field ↓
┆19┆┆93┆┄┄of the exchanged protocl elements.↲
↲
↲
↲
┆a1┆3.2.2.2 TEST.confirm↲
↲
The primitive, which confirms that the transmission path between the ↓
local RCLLC entity and one remote RCLLC entity has been tested as ↓
requested by a previous TEST.request primitive, is passed from the RCLLC ↓
entity to the client.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ is the local SAP address.↲
rem_addr╞ is the station address of the remote RCLLC entity.↲
result╞ ┆84┆indicates how the test went, e.g. 'no problems', 'too ↓
┆19┆┆93┆┄┄many collisions', or 'received protocol element was ↓
┆19┆┆93┆┄┄damaged'.↲
↲
↲
┆a1┆3.2.2.3 TEST.indication↲
↲
The primitive, which indicates that a TEST protocol element addressed to ↓
the local SAP has been received, is passed from the RCLLC entity to the ↓
client.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
dest_addr╞ ┆84┆is the destination address of the received protocol ↓
┆19┆┆93┆┄┄element, consisting of↲
┆8c┆┆83┆┆c8┆↓
╞ ╞ 1) ┆84┆the local station address, or a multicast address ↓
┆19┆┆96┆┄┄to which the station is sensitive, or the ↓
┆19┆┆96┆┄┄broadcast address, and↲
╞ ╞ 2) the local SAP address.↲
src_addr╞ ┆84┆is the complete address of the source SAP or RCLLC ↓
┆19┆┆93┆┄┄entity, consisting of↲
╞ ╞ 1) station address, and↲
╞ ╞ 2) ┆84┆source SAP address or null address indicating the ↓
┆19┆┆96┆┄┄protocol element originated from the remote RCLLC ↓
┆19┆┆96┆┄┄entity.↲
↲
Note that a TEST.request primitive issued by a client in an RCLLC ↓
station does not cause this primitive to be generated in remote RCLLC ↓
station(s), as the protocol element (TEST command) which is transmitted ↓
in this case is not addressed to a SAP, but to one or more remote RCLLC ↓
entities.↲
↲
↲
┆a1┆3.2.3 Type 1 Service↲
↲
Type 1 service comprises unacknowledged connectionless data transfer ↓
between SAPs.↲
↲
↲
┆a1┆3.2.3.1 UDATA.request↲
↲
The primitive, which requests transmission of an RCLLC service data ↓
unit, is passed from a client to the RCLLC entity.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ is the local SAP address.↲
dest_addr╞ ┆84┆is the complete address of the destination SAP(s), ↓
┆19┆┆93┆┄┄where the station address may be a multicast address ↓
┆19┆┆93┆┄┄or the broadcast address.↲
l_sdu╞ is the service data unit to be transmitted.↲
service_class╞ ┆84┆specifies the priority desired for the data unit ↓
┆19┆┆93┆┄┄transfer; its effect is unspecified.↲
↲
↲
┆8c┆┆83┆┆e0┆↓
┆0e┆↓
┆a1┆┆a1┆3.2.3.2 UDATA.indication↲
↲
The primitive, which is used to deliver a received RCLLC service data ↓
unit, is passed from the RCLLC entity to the client.↲
┆0f┆↓
↲
┆a1┆Parameters┆e1┆:↲
↲
dest_addr╞ ┆84┆is the complete address of the destination SAP(s), ↓
┆19┆┆93┆┄┄where the station address may be a multicast address ↓
┆19┆┆93┆┄┄or the broadcast address.↲
src_addr╞ is the complete address of the source SAP.↲
l_sdu╞ is the received service data unit.↲
↲
↲
┆a1┆3.2.4 Client Network Service↲
↲
The RCLLC layer automatically establishes and maintains a connection ↓
between each pair of SAPs belonging to the same client network, except ↓
when the connection is excluded because the SAP masks do not match.↲
↲
When a SAP is activated, connections will be established to those remote ↓
SAPs which were already active. The (local) client will receive a ↓
CONNECT.indication primitive for each connection when it has been ↓
established. Similarly the remote clients will each receive a ↓
CONNECT.indication primitive.↲
↲
When a connection has been established, both clients may request the ↓
transmission of RCLLC service data units by issuing DATA.request ↓
primitives. A received data unit is passed to the client at the ↓
destination SAP by means of a DATA.indication primitive.↲
↲
The order in which RCLLC service data units are passed to the RCLLC ↓
layer for transmission on a connection is preserved to the point of ↓
delivery. RCLLC service data units are delivered free of transmission ↓
errors.↲
↲
When a SAP is deactivated, either because of a request or because the ↓
station in which it exists ceases to operate or is reinitialized, the ↓
┆8c┆┆83┆┆c8┆↓
RCLLC layer will detect the event and remove the connections in which ↓
the SAP took part. Each of the clients at the remote end of such a ↓
connection will be notified by means of a DISCONNECT.indication ↓
primitive.↲
↲
There is no guarantee that all service data units passed to the RCLLC ↓
layer for transmission will have been delivered before a connection is ↓
removed.↲
↲
When an RCLLC entity has removed (one end-point of) a connection and ↓
passed the indication to the client it will not establish a new ↓
connection to the same remote SAP until the client has acknowledged the ↓
removal of the connection by issuing a DISCONNECT.acknowledge primitive. ↓
This procedure is significant when a connection is removed because of a ↓
temporary malfunction or the reinitialization of a station. It allows ↓
the client to gracefully terminate any activity associated with the ↓
connection before it is reestablished.↲
↲
Details about the six primitives used in conjunction with client network ↓
service are given in the following subsections.↲
↲
↲
┆a1┆3.2.4.1 CONNECT.indication↲
↲
The primitive, which indicates that a connection has been established, ↓
is passed from the RCLLC entity to the client.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆is the local SAP address, i.e. the client network ↓
┆19┆┆93┆┄┄number.↲
rem_addr╞ is the station address of the remote SAP.↲
client_info╞ ┆84┆is the data unit passed to the RCLLC layer when the ↓
┆19┆┆93┆┄┄remote SAP was activated.↲
↲
After receiving the primitive the client may issue DATA.request ↓
primitives on the connection, and should expect DATA.indication ↓
primitives to arrive.↲
↲
↲
┆8c┆┆83┆┆e0┆↓
┆a1┆3.2.4.2 DISCONNECT.indication↲
↲
The primitive, which indicates that a connection has been removed, is ↓
passed from the RCLLC entity to the client.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆is the local SAP address, i.e. the client network ↓
┆19┆┆93┆┄┄number.↲
rem_addr╞ is the station address of the remote SAP.↲
reason╞ specifies why the connection was removed.↲
↲
The client should acknowledge receipt of the primitive by issuing a ↓
DISCONNECT.acknowledge primitive. A new connection to the same remote ↓
SAP will not be established until this has been done.↲
↲
↲
┆a1┆3.2.4.3 DISCONNECT.acknowledge↲
↲
The primitive, which acknowledges the removal of a connection, is passed ↓
from a client to the RCLLC entity.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆is the local SAP address, i.e. the client network ↓
┆19┆┆93┆┄┄number.↲
rem_addr╞ is the station address of the remote SAP.↲
↲
After receiving the primitive the RCLLC entity may establish a new ↓
connection to the same remote SAP.↲
↲
↲
┆a1┆3.2.4.4 DATA.request↲
↲
The primitive, which requests that an RCLLC service unit be transmitted ↓
on a connection, is passed from a client to the RCLLC entity.↲
↲
┆8c┆┆83┆┆bc┆↓
┆0e┆↓
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆is the local SAP address, i.e. the client network ↓
┆19┆┆93┆┄┄number.↲
┆0f┆↓
dest_addr╞ is the station address of the remote SAP.↲
l_sdu╞ is the service data unit to be transmitted.↲
↲
↲
┆a1┆3.2.4.5 DATA.confirm↲
↲
The primitive, which indicates that an RCLLC service data unit ↓
previously passed in a DATA.request primitive has been transmitted on a ↓
connection, is passed from the RCLLC entity to the requesting client.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆is the local SAP address, i.e. the client network ↓
┆19┆┆93┆┄┄number.↲
dest_addr╞ is the station address of the remote SAP.↲
result╞ ┆84┆indicates how the transmission went, e.g. 'no ↓
┆19┆┆93┆┄┄problems' or 'too many collisions'.↲
↲
The primitive may confirm that the data unit has been transmitted and ↓
acknowledged, but not that it has been delivered to and received by the ↓
remote client.↲
↲
↲
┆a1┆3.2.4.6 DATA.indication↲
↲
The primitive, which is used to deliver an RCLLC service unit received ↓
on a connection, is passed from the RCLLC entity to the client.↲
↲
┆a1┆Parameters┆e1┆:↲
↲
l_SAP_addr╞ ┆84┆is the local SAP address, i.e. the client network ↓
┆19┆┆93┆┄┄number.↲
dest_addr╞ is the station address of the remote SAP.↲
l_sdu╞ is the received service data unit.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆4. RCLLC PROCEDURES↲
↲
The description of RCLLC procedures falls in two parts: 1) the type 1 ↓
procedures which are in conformance with (ref. 1), and 2) the procedures ↓
for client network service which constitute a functional extension to ↓
the type 1 procedures.↲
↲
In general, an RCLLC protocol element may be a ┆a1┆command┆e1┆ protocol element ↓
or a ┆a1┆response┆e1┆ protocol element. As a protocol element is transmitted ↓
using the services of the MAC layer it may be addressed to one or ↓
several stations, using an individual, multicast, or broadcast station ↓
address. Within each addressed station an RCLLC protocol element is ↓
addressed either to the RCLLC entity as such or to a specific SAP.↲
↲
↲
┆a1┆4.1 Type 1 Procedures↲
↲
This section contains a general description of the type 1 procedures. ↓
Details not covered in the general description are given in conjunction ↓
with the individual protocol elements in section 5.↲
↲
↲
┆a1┆4.1.1 Unacknowledged Data Transfer↲
↲
This subsection applies to data transfer between active SAPs for which ↓
type 1 service has been requested.↲
↲
Unacknowledged connectionless data transfer as requested by the ↓
UDATA.request primitive is accomplished by transmission of a UI protocol ↓
element containing the service data unit passed as a parameter of the ↓
primitive. This may occur at any time while the source SAP is active.↲
↲
When a UI protocol element is correctly received, the service data unit ↓
which it contains is passed to the client by means of a UDATA.indication ↓
primitive. There is no associated acknowledgement or sequence checking. ↓
Notice that a UI protocol element which is found to be in error by the ↓
receiving MAC or RCLLC entity is simply discarded. Buffer shortage in ↓
the receiving RCLLC entity may also cause a UI protocol element to be ↓
discarded.↲
↲
↲
┆8c┆┆83┆┆ec┆↓
┆a1┆4.1.2 Loop-back Test Procedure↲
↲
An RCLLC entity will initiate the loop-back test procedure upon receipt ↓
of a TEST.request primitve from a client. It does so by transmitting a ↓
TEST command protocol element with the poll bit set to 1 and addressed ↓
as specified in the request. The information field of the TEST command ↓
will contain the specified test data unit. Notice that multi- or broad-↓
casting may be used to test several transmission paths using one command ↓
protocol element.↲
↲
For each TEST response protocol element which is subsequently received ↓
correctly, with or without an information field, the client is informed ↓
by means of a TEST.confirm primitive.↲
↲
An RCLLC entity will not transmit a TEST command protocol element, ↓
except when directed by a TEST.request primitive.↲
↲
When an RCLLC entity correctly receives a TEST command protocol element ↓
addressed to itself or to an active SAP, with the poll bit set to 1, it ↓
will respond by transmitting a TEST response protocol element addressed ↓
to the source RCLLC entity or SAP. The received information is copied to ↓
the response protocol element. If the information field could not be ↓
held in the receive buffer(s) of the RCLLC entity due to overlength, the ↓
response protocol element will contain an empty information field. In ↓
the case when the received TEST command protocol element is addressed to ↓
a SAP, the client will be informed by means of a TEST.indication ↓
primitive. Notice that the source station in this case will not be an ↓
RCLLC station.↲
↲
A TEST command protocol element received with poll bit set to 0 is ↓
discarded.↲
↲
↲
┆a1┆4.1.3 Station Identification Exchange↲
↲
Type 1 station identification exchange is not supported as part of the ↓
RCLLC service interface, and an RCLLC entity will not, therefore, ↓
transmit XID command protocol elements. It will, however, answer ↓
┆8c┆┆83┆┆c8┆↓
politely when an XID protocol element addressed to itself or to an ↓
active SAP is correctly received. Observe that the source station in ↓
this case will not be an RCLLC station.↲
↲
↲
┆a1┆4.2 Procedures for Client Network Service↲
↲
This section contains a general description of the procedures for client ↓
network service. Details not covered in the general description are ↓
given in conjunction with the individual protocol elements in section 5.↲
↲
Client networks are supervised by the RCLLC layer. The protocol element ↓
ACTIVE_SAP plays a central role in this respect. Whenever a SAP ↓
belonging to a client network is active the RCLLC entity serving the SAP ↓
will regularly transmit this protocol element to its peer entities using ↓
the multicast address for the client network. An RCLLC receiving the ↓
ACTIVE_SAP protocol element will discard it unless the included SAP ↓
mask matches the mask of the local SAP belonging to the same client ↓
network.↲
↲
This procedure serves to make a SAP known throughout the client network ↓
so that all desired connections to the SAP may be established. Notice ↓
that the SAP remains unknown to all stations where its mask does not ↓
match the local SAP mask.↲
↲
Moreover, the procedure allows RCLLC entities to supervise the liveness ↓
of all existing connections. When the ACTIVE_SAP protocol element fails ↓
to arrive from a SAP to which a connection exists, for a sufficiently ↓
long period of time, this will be taken to indicate that the SAP is no ↓
longer active, and the RCLLC entity will therefore remove its end of the ↓
connection.↲
↲
All protocol elements other than ACTIVE_SAP are transmitted using ↓
individual station address.↲
↲
The rigorous description of the procedures for establishment and ↓
supervision of connections which is given in the following is based on a ↓
state, two timers and a retransmission counter maintained by an RCLLC ↓
┆8c┆┆83┆┆c8┆↓
entity for each connection in which it takes part, i.e. for each remote ↓
SAP it knows. The following connection states exist: UNKNOWN, RESETTING, ↓
DATA, DISCONNECTING. The timers are:↲
↲
╞ - ┆84┆the acknowledgement timer which runs when an acknowledgement, i.e. ↓
┆19┆┆86┆┄┄a RACK or ACK protocol element is expected,↲
╞ - ┆84┆the SAP alive timer which runs whenever the remote SAP is known ↓
┆19┆┆86┆┄┄and is restarted each time an ACTIVE_SAP protocol element is ↓
┆19┆┆86┆┄┄received.↲
↲
In addition to the state, timers, and retransmission counter an RCLLC ↓
entity maintains for each connection two sequence counters for data ↓
units, N(S): the number of the data unit to transmit, and N(R): the ↓
number of the next data unit to be received.↲
↲
The following events may cause the state of a connection to change:↲
↲
PE_new_SAP╞ ┆84┆An ACTIVE_SAP protocol element is received from the ↓
┆19┆┆93┆┄┄remote SAP indicating it has become active, possibly ↓
┆19┆┆93┆┄┄by reinitialization, see subsection 5.2.1.↲
↲
PE_rack╞ ┆84┆A RACK or RESET protocol element is received from the ↓
┆19┆┆93┆┄┄remote SAP when RACK is expected.↲
↲
PE_reset╞ ┆84┆A RESET protocol element is received from the remote ↓
┆19┆┆93┆┄┄SAP, except when RACK is expected.↲
↲
give_up╞ ┆84┆The RCLLC entity gives up the connection when the ↓
┆19┆┆93┆┄┄retransmission counter is exhausted, or when the SAP ↓
┆19┆┆93┆┄┄alive timer runs out.↲
↲
SP_dack╞ ┆84┆An expected DISCONNECT.acknowledge service primitive ↓
┆19┆┆93┆┄┄is received from the client.↲
↲
An overview of the state changes caused by events and the associated ↓
actions, i.e. protocol elements and service primitives that are ↓
generated, is given in figure 1. Note that the figure and the ↓
description which follows apply to a single connection, in fact to each ↓
end-point separately.↲
↲
┆8c┆┆83┆┆e0┆↓
┆0e┆↓
╱04002d4e0c0006000000000201483100000000000000000000000000000000000000000000000000070d1a222a383f44474b555f69737dff04╱
╱04002d4e0c0006000000000301483160000000000000000000000000000000000000000000000000050a11191e464b555f69737dffffffff04╱
↓
╞ ╞ ╞ ┆a1┆╞ ╞ _↲
╞ ╞ ╞ !╞ ╞ !↲
╞ ╞ ╞ ! UNKNOWN╞ !<---------------------------!↲
╞ ╞ ╞ ┆a1┆!╞ ╞ !┆e1┆╞ ╞ ╞ ╞ !↲
╞ ╞ ╞ !╞ !╞ ╞ ╞ ╞ ╞ !↲
╞ ╞ PE_new_SAP╞ ! !╞ PE_reset╞ ╞ ╞ ╞ !↲
╞ ----------------------! !------------------------╞ ╞ !↲
╞ ! <RESET>╞ ╞ ╞ <RACK>╞ ╞ !╞ ╞ !↲
╞ ! <CONNECT_indication>╞ ╞ <CONNECT_indication>╞ !╞ ╞ !↲
╞ !╞ ╞ ╞ ╞ ╞ ╞ !╞ ╞ !↲
┆a1┆╞ v╞ ┆e1┆╞ ╞ ╞ ╞ ┆a1┆╞ v╞ ┆e1┆╞ !↲
!╞ ╞ !╞ PE_rack╞ ╞ !╞ ╞ !╞ !↲
! RESETTING╞ !----------------------------------------->! DATA !╞ !↲
┆a1┆!╞ ╞ !┆e1┆╞ ╞ ╞ ╞ ┆a1┆!╞ ╞ !┆e1┆╞ !↲
! !╞ PE_new_SAP╞ ╞ PE_new_SAP╞ ! ! !╞ ╞ !↲
! !----------------------> <----------------------! ! !╞ ╞ !↲
!╞ ╞ ╞ ╞ !╞ ╞ ! !╞ ╞ !↲
!╞ ╞ ╞ ╞ !╞ PE_reset╞ ! !╞ ╞ !↲
!╞ ╞ ╞ ╞ !<--------------------------! !╞ ╞ !↲
!╞ ╞ ╞ ╞ !╞ ╞ ╞ !╞ ╞ !↲
!╞ ╞ give_up╞ ╞ !╞ give_up╞ ╞ !╞ ╞ !↲
!---------------------------->!<------------------------------!╞ ╞ !↲
╞ ╞ ╞ ╞ !╞ ╞ ╞ ╞ ╞ !↲
╞ ╞ ╞ ╞ !<DISCONNECT_indication>╞ ╞ ╞ !↲
╞ ╞ ╞ ╞ !╞ ╞ ╞ ╞ ╞ !↲
╞ ╞ ╞ ┆a1┆╞ v╞ ┆e1┆╞ ╞ ╞ ╞ !↲
╞ ╞ ╞ !╞ ╞ ! SP_dack╞ ╞ ╞ ╞ !↲
╞ ╞ ╞ ! DISCONNECTING╞ !-----------------------------↲
╞ ╞ ╞ ┆a1┆!╞ ╞ !↲
╱04002d4e0c0006000000000301483100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
╱04002d4e0c0006000000000201483100000000000000000000000000000000000000000000000000070d1a222a383f44474b555f69737dff04╱
↓
↲
Figure 1: State graph for a connection.↲
┆0f┆↓
↲
A general procedure applies to the transmission of protocol elements for ↓
which an acknowledgement is required in the form of a protocol element ↓
transmitted in the opposite direction, viz. RESET and DATA which are ↓
acknowledged by RACK and ACK, respectively. ┆a1┆Initiating┆e1┆ the ┆a1┆transmission┆e1┆ ↓
of one of these elements means: initializing the retransmission counter, ↓
starting the acknowledgement timer, and actually transmitting the ↓
protocol element. When the acknowledging protocol element arrives, the ↓
transmission is considered successfully completed, and the timer is ↓
stopped. If, on the other hand, the acknowledgement timer expires, the ↓
retransmission counter is decremented, and if it was exhausted, i.e. ↓
became zero, the connection is given up (give_up event). Otherwise, the ↓
timer is restarted and the protocol element retransmitted.↲
↲
There is never more than one outstanding protocol element requiring ↓
acknowledgement, i.e. transmission of a RESET or DATA protocol element ↓
┆8c┆┆83┆┆c0┆↓
is not initiated until transmission of the previous element is ↓
completed. For this reason a DATA.request primitive containing an RCLLC ↓
service data unit for transmission on a connection may be accepted while ↓
an unacknowledged protocol element is outstanding, but it will then be ↓
queued (by the RCLLC entity) for transmission rather than processed ↓
immediately.↲
↲
The remaining part of this section contains a discussion of the meaning ↓
of each state of a connection (end-point) and the procedures followed by ↓
an RCLLC entity in each state.↲
↲
UNKNOWN↲
↲
The RCLLC entity has no knowledge of the remote SAP, but is ready to ↓
establish a connection. No service primitives are accepted and all ↓
protocol elements except ACTIVE_SAP and RESET are discarded.↲
↲
A received ACTIVE_SAP protocol element (with matching SAP mask) consti┄↓
tutes a PE_new_SAP event. It causes the RCLLC entity to establish a ↓
connection to the remote SAP by starting the SAP alive timer, initiating ↓
the transmission of a RESET protocol element, resetting the sequence ↓
counters, passing a CONNECT.indication primitive to the client, and ↓
changing the connection state to RESETTING.↲
↲
A received RESET protocol element constitutes a PE_reset event indi┄↓
cating that the local SAP has become known to the remote RCLLC entity ↓
and caused it to establish a connection. The local RCLLC entity will ↓
establish its end of the connection by starting the SAP alive timer, ↓
transmitting a RACK protocol element to acknowledge RESET, resetting the ↓
sequence counters, passing a CONNECT.indication primitive to the client, ↓
and changing the connection state to DATA.↲
↲
RESETTING↲
↲
The RCLLC entity has established the connection by initiating the trans┄↓
mission of a RESET protocol element. The state is used to wait for the ↓
acknowledging RACK protocol element after which data may be transmitted ↓
in both directions.↲
↲
┆8c┆┆83┆┆d4┆↓
DATA.request primitives are accepted (queued). DISCONNECT.acknowledge ↓
primitives are discarded.↲
↲
A received RESET or RACK protocol element constitutes a PE_rack event ↓
and causes the RCLLC entity to change the connection state to DATA. ↓
RESET, which may occur if RESET protocol elements are transmitted in ↓
both directions simultaneously, is answered with RACK.↲
↲
Received DATA or ACK protocol elements are discarded.↲
↲
If a PE_new_SAP event occurs (cf. subsection 5.2.1), or if the ↓
connection is given up, either because the SAP alive timer expires or ↓
because the RESET protocol element is retransmitted to exhaustion, the ↓
RCLLC entity will pass a DISCONNECT.indication primitive to the client ↓
and change the connection state to DISCONNECTING.↲
↲
DATA↲
↲
The connection has been completely established through the exchange of ↓
RESET and RACK protocol elements. In this state RCLLC service data units ↓
are transferred between the two SAPs through the exchange of DATA and ↓
ACK protocol elements between the RCLLC entities.↲
↲
Each DATA.request primitive received from the client causes initiation ↓
of the transmission of a DATA protocol element containing the service ↓
data unit passed as a parameter of the primitive. The sequence number of ↓
the protocol element is set equal to the value of N(S), and subsequently ↓
N(S) is incremented modulo 2. Initiation of the transmission of the ↓
protocol element takes place: either when an ACK or RACK protocol ↓
element is received marking the successful completion of a previous ↓
transmission provided a non-empty queue of service data units are ↓
awaiting transmission; or immediately upon receipt of the DATA.request ↓
primitive if there is no outstanding protocol element awaiting ↓
acknowledgement.↲
↲
When a DATA protocol element is received, its sequence number is ↓
compared to the value of N(R). If they are equal the received service ↓
data unit is passed to the client by means of a DATA.indication primi┄↓
┆8c┆┆83┆┆c8┆↓
tive, and N(R) is incremented modulo 2. Otherwise, the service data unit ↓
is discarded. In both cases an ACK protocol element with sequence number ↓
equal to that of the DATA protocol element is transmitted to the remote ↓
SAP in order to acknowledge receipt.↲
↲
If a RACK protocol element or a DISCONNECT.acknowledge service primitive ↲
is received, it is discarded.↲
↲
If a PE_new_SAP event occurs (cf. subsection 5.2.1), if a RESET protocol ↓
element is received, or if the connection is given up, either because ↓
the SAP alive timer expires or because a DATA protocol element is re┄↓
transmitted to exhaustion, the RCLLC entity will pass a ↓
DISCONNECT.indication primitive to the client and change the connection ↓
state to DISCONNECTING.↲
↲
DISCONNECTING↲
↲
The connection has been disconnected as seen from the point of view of ↓
the RCLLC layer. This state allows the client to decide when it will ↓
accept the connection to be reestablished.↲
↲
All received protocol elements and service primitives are discarded ↓
except the DISCONNECT.acknowledge primitve. When this primitive is ↓
received the connection state is changed to UNKNOWN.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆5. RCLLC PROTOCOL ELEMENTS↲
↲
All RCLLC protocol elements conform to the syntax for LLC type 1 ↓
protocol elements ("protocol data units"). This is achieved by defining ↓
the formats of all the protocol elements used in the procedures oriented ↓
toward client network service to be instances of type 1 UI (Unnumbered ↓
Information) commands.↲
↲
The following conventions apply to the figures in this section: the ↓
octets of a protocol element are shown in the order they are transmitted ↓
downward on the page, and the bits within an octet similarly from left ↓
to right. The least significant bit position within an octet, the ↓
contents of which is transmitted first, is numbered 0, and so forth.↲
↲
The general format for type 1 protocol elements consists of a three-↓
octet link control header followed by an information field:↲
↲
╱04002d4e0c00060000000002014831000000000000000000000000000000000000000000000000000b0f2f37414b555f69737d8791ffffff04╱
╱04002d4e0c0006000000000301483100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
↓
bit no.╞ ┆a1┆ 0 1 2 3 4 5 6 7 ↲
octet no. 0╞ ┆a1┆! 0 ! 0 ! DSAP╞ !↲
╞ 1╞ ┆a1┆!C/R! 0 ! SSAP╞ !↲
╞ 2╞ ┆a1┆! Control╞ !↲
╞ 3╞ !╞ !↲
╞ ╞ ! Type 1 Information╞ !↲
╱04002d4e0c00060000000003014831000000000000000000000000000000000000000000000000000b0f2f37414b555f69737d8791ffffff04╱
╱04002d4e0c00060000000002014831000000000000000000000000000000000000000000000000000b0f2f37414b555f69737d8791ffffff04╱
↓
╞ ╞ ┆a1┆!╞ !↲
↲
The DSAP field contains the local SAP address of the destination SAP and ↓
the SSAP field the local SAP address of the source SAP.↲
↲
If the DSAP field contains 0 (all bits 0) the protocol element is ↓
interpreted as addressed to the destination RCLLC (or other LLC type 1) ↓
entity rather than to a client.↲
↲
If the DSAP field does not contain all 0 bits, its contents taken as a ↓
binary number in the range 1..63 is interpreted as the address of an ↓
individual SAP.↲
↲
A C/R bit with value 0 indicates a command protocol element, and one ↓
with value 1 a response protocol element. The UI protocol element, and ↓
thus all protocol elements for client network service can only be ↓
transmitted as commands, i.e. with the C/R bit set to 0.↲
↲
┆8c┆┆83┆┆d4┆↓
Bit 0 of octet 0 and bit 1 of octet 1 must always be 0.↲
↲
If the SSAP field contains 0 (all bits 0), the protocol element is ↓
interpreted as originating from the source RCLLC (or other LLC type 1) ↓
entity rather than from a client. Otherwise, the contents of the SSAP ↓
field is interpreted as a binary number in the range 1..63.↲
↲
Bit 4 of octet 2 (the Control field) is the Poll/Final bit. When this ↓
bit is set to 1 (Poll) in a command, a response is requested. The ↓
response should contain the same coding of the Control field; i.e., bit ↓
4 (Final) should also be set in the response. The Poll bit must not be ↓
set in a UI protocol element; thus this bit is 0 in all protocol ↓
elements for client network service.↲
↲
The SSAP field of a response protocol element always contains the same ↓
value as the DSAP field of the command protocol element to which it ↓
corresponds, and vice versa.↲
↲
The remaining bits of the Control field specify the type of protocol ↓
element in question, viz.:↲
↲
11000000╞ ╞ UI, Unnumbered Information↲
1111X101╞ ╞ XID, eXchange IDentification↲
1100X111╞ ╞ TEST↲
↲
The use of the Type 1 Information field depends on the type of protocol ↓
element, and is described for each element type in section 5.1.↲
↲
The protocol elements for client network service are UI commands ↓
addressed to an individual SAP with three extra octets of RCLLC header ↓
in addition to the LLC type 1 header. Source and destination SAPs have ↓
the same local address which is equal to the client network number, ↓
Netno. The format is as shown below:↲
↲
┆8c┆┆83┆┆98┆↓
┆0e┆↓
╱04002d4e0c00060000000002014831000000000000000000000000000000000000000000000000000b0f292f37414b555f69737d8791ffff04╱
╱04002d4e0c00060000000003014831000000000000000000000000000000000000000000000000000b0f2f37414b555f69737d8791ffffff04╱
↓
bit no.╞ ┆a1┆ 0 1 2 3 4 5 6 7 ↲
octet no. 0╞ ┆a1┆! 0 0 ! Netno╞ !↲
╞ 1╞ ┆a1┆! 0 0 ! Netno╞ !┆e1┆ type 1↲
╞ 2╞ ┆a1┆! 1 1 0 0 0 0 0 0╞ !┆e1┆ header RCLLC↲
╞ 3╞ ┆a1┆! Function╞ !┆e1┆ header↲
╞ 4╞ ┆a1┆! Param 0╞ !↲
╞ 5╞ ┆a1┆! Param 1╞ !↲
╞ 6╞ !╞ !↲
╞ ╞ ! Information╞ !↲
╱04002d4e0c00060000000003014831000000000000000000000000000000000000000000000000000b0f292f37414b555f69737d8791ffff04╱
╱04002d4e0c00060000000002014831000000000000000000000000000000000000000000000000000b0f292f37414b555f69737d8791ffff04╱
↓
╞ ╞ ┆a1┆!╞ !↲
┆0f┆↓
↲
The value in the Function field specifies the type of protocol element, ↓
viz.:↲
↲
00000000 (binary 0) ACTIVE_SAP↲
10000000 (binary 1) RESET↲
01000000 (binary 2) RACK↲
11000000 (binary 3) DATA↲
00100000 (binary 4) ACK↲
↲
The use of the Param 0 and 1 fields and of the Information field depends ↓
on the type of protocol element, and is described for each element type ↓
in section 5.2.↲
↲
↲
┆a1┆5.1 Type 1 Protocol Elements↲
↲
This section specifies the encoding of the Type 1 Information field of ↓
protocol elements used in conjunction with type 1 procedures.↲
↲
↲
┆a1┆5.1.1 UI (Unnumbered Information)↲
↲
The UI protocol element may only be transmitted as a command, i.e. the ↓
C/R bit must be 1.↲
↲
When the protocol element is used for type 1 service the Type 1 ↓
Information field is used to hold an RCLLC service data unit.↲
↲
┆8c┆┆83┆┆b0┆↓
┆0e┆↓
┆a1┆5.1.2 XID (eXchange IDentification)↲
↲
The Type 1 Information field in a received XID command is ignored. In an ↓
XID response protocol element transmitted by an RCLLC entity three ↓
octets, numbers 6 through 8, are encoded as follows:↲
┆0f┆↓
↲
╱04002d4e0c00060000000002014831000000000000000000000000000000000000000000000000000b0f28414b555f69737d8791ffffffff04╱
╱04002d4e0c00060000000003014831000000000000000000000000000000000000000000000000000b0f292f37414b555f69737d8791ffff04╱
↓
bit no.╞ ┆a1┆ 0 1 2 3 4 5 6 7 ↲
octet no. 6╞ ┆a1┆! 1 0 0 0 0 0 0 1╞ !↲
╞ 7╞ ┆a1┆! 1 0 0 0 0 0 0 0╞ !┆e1┆↲
╱04002d4e0c00060000000003014831000000000000000000000000000000000000000000000000000b0f282f37414b555f69737d8791ffff04╱
╱04002d4e0c00060000000002014831000000000000000000000000000000000000000000000000000b0f28414b555f69737d8791ffffffff04╱
↓
╞ 8╞ ┆a1┆! 0 0 0 0 0 0 0 0╞ !↲
↲
↲
┆a1┆5.1.3 TEST↲
↲
The Type 1 Information field is used to hold a test data unit. The ↓
associated procedure is described in subsection 4.1.2.↲
↲
↲
┆a1┆5.2 Protocol Elements for Client Network Service↲
↲
In order to facilitate speedy access to status information associated ↓
with connections, each RCLLC entity will assign to each connection an ↓
index in the range 0..255. When a connection is established the assigned ↓
indices are exchanged between the two RCLLC entities. Subsequent DATA ↓
and ACK protocol elements each contain the index assigned to the ↓
connection by the receiver of the element.↲
↲
↲
┆a1┆5.2.1 ACTIVE_SAP↲
↲
An RCLLC entity transmits this protocol element periodically for each ↓
active SAP it serves which belongs to a client network. It is ↓
transmitted using the multicast address for the client network in ↓
question so that all relevant RCLLC entities will receive it. The ↓
frequency with which the protocol element is transmitted depends on the ↓
implementation.↲
↲
The first word of the Information field contains the SAP mask of the ↓
active SAP. Unless the mask matches that of the local SAP at the ↓
receiving RCLLC entity the protocol element is discarded.↲
↲
┆8c┆┆83┆┆e0┆↓
The Param 1 field contains a sequence number in the range 0..254. The ↓
first 255 ACTIVE_SAP protocol elements transmitted after activation of a ↓
SAP will have sequence numbers 0, 1, 2,.. 254. In all subsequent ↓
ACTIVE_SAP protocol elements the sequence number will also be 254. This ↓
procedure allows the receiving RCLLC entity to detect when a SAP is ↓
deactivated and swiftly reactivated, possibly because of station re┄↓
initialization.↲
↲
When an ACTIVE_SAP protocol element is received from a previously ↓
unknown SAP a PE_new_SAP event is generated (cf. section 4.2). The same ↓
is the case if the sequence number is less than the sequence number ↓
found in the last received ACTIVE_SAP or RESET protocol element from the ↓
same SAP. However, when the sequence number are equal or ascending, the ↓
protocol element is only taken to indicate that the SAP is still active. ↓
In the latter case the SAP alive timer is restarted.↲
↲
The Information field from the third byte onwards contains the ↓
client_info passed from the client when the SAP was activated.↲
↲
↲
┆a1┆5.2.2 RESET↲
↲
This protocol element is transmitted in conjunction with establishment ↓
of a connection.↲
↲
The Param 0 field contains the index assigned to the connection by the ↓
sending RCLLC entity.↲
↲
The Param 1 field contains the sequence number to be included in the ↓
next ACTIVE_SAP protocol element to be transmitted from the sender.↲
↲
The Information field contains the client_info passed from the client ↓
when the SAP was activated.↲
↲
↲
┆8c┆┆83┆┆a4┆↓
┆0e┆↓
┆a1┆5.2.3 RACK↲
↲
This protocol element is transmitted to acknowledge receipt of a RESET ↓
protocol element in conjunction with establishment of a connection.↲
┆0f┆↓
↲
The Param 0 field contains the index assigned to the connection by the ↓
sending RCLLC entity.↲
↲
The Param 1 field contains the index assigned to the connection by the ↓
receiver as indicated in the RESET protocol element being acknowledged.↲
↲
The Information field is empty.↲
↲
↲
┆a1┆5┆a1┆.2.4 DATA↲
↲
This protocol element is transmitted to carry an RCLLC service data unit ↓
from the source SAP to the destination SAP.↲
↲
The Param 0 field contains the sequence number of the element, cf. ↓
section 4.2. The sequence number, which can only be 0 or 1 is placed in ↓
bit 0. The remaining bits are all 0.↲
↲
The Param 1 field contains the index assigned to the connection at the ↓
destination RCLLC entity.↲
↲
The Information field contains the RCLLC service data unit.↲
↲
↲
┆a1┆5.3.5 ACK↲
↲
This protocol element is transmitted to acknowledge receipt of a DATA ↓
protocol element on a connection.↲
↲
The Param 0 field contains the sequence number of the element being ↓
acknowledged.↲
↲
┆8c┆┆83┆┆bc┆↓
The Param 1 field contains the index assigned to the connection at the ↓
destination RCLLC entity, i.e. the sender of the DATA element.↲
↲
The Information field is empty.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆A. REFERENCES↲
↲
(ref.1)╞ ISO/DP 8802/2 (TC 97/SC 6 N2925)↲
╞ Local Area Networks - Logical Link Control - Draft E↲
↲
(ref.2)╞ ISO/DIS 7498↲
╞ Data Processing - Open Systems Interconnection↲
╞ Basic Reference Model↲
╞ Feb. 4, 1982↲
↲
(ref.3)╞ RCSL No. 42-i1982:↲
╞ Distributed System Architecture, Report↲
↲
(ref.4)╞ RCSL No. 42-i1983:↲
╞ DSA Inter Module Communication,↲
╞ Functional Description↲
↲
(ref.5)╞ DR Soft/Net, Network Operating System,↲
╞ System Guide↲
╞ Digital Research, 1984.↲
┆1a┆┆1a┆╞ System G
0x0000…0020 (0,) 00 00 00 00 00 00 00 00 42 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 4e 00 00 00 ┆ B N ┆
0x0020…0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
0x0040…0047 00 00 00 00 00 00 00 ┆ ┆
0x0047…0080 Params {
0x0047…0080 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1` ┆
0x0047…0080 00 00 00 00 00 00 00 00 2a 34 41 4b 55 5f 69 73 7d 87 91 ff ff ff ff ff 04 ┆ *4AKU_iså ┆
0x0047…0080 }
0x0080…00a0 0d 0a 09 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 0d 0a 09 ┆ __________________________ ┆
0x00a0…00c0 52 43 53 4c 20 4e 6f 2e 3a 09 39 39 31 20 30 39 39 37 33 0d 0a 09 45 64 69 74 69 6f 6e 3a 09 44 ┆RCSL No.: 991 09973 Edition: D┆
0x00c0…00e0 65 63 65 6d 62 65 72 20 31 39 38 34 0d 0a 09 41 75 74 68 6f 72 73 3a 20 09 45 6a 76 69 6e 64 20 ┆ecember 1984 Authors: Ejvind ┆
0x00e0…0100 4c 79 6e 6e 69 6e 67 20 28 65 64 2e 29 0d 0a 09 09 4a 6f 68 6e 20 53 76 65 6e 73 73 6f 6e 0d 0a ┆Lynning (ed.) John Svensson ┆
0x0100…0120 09 09 50 65 74 65 72 20 48 6f 6c 6d 0d 0a 09 09 4a 65 73 70 65 72 20 41 2e 20 54 7d 67 68 6f 6c ┆ Peter Holm Jesper A. Tåghol┆
0x0120…0140 74 0d 0a 0d 0a 0d 0a 0d 0a 0d 0a 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 46 4f 52 20 49 4e ┆t FOR IN┆
0x0140…0160 54 45 52 4e 41 4c 20 55 53 45 0d 0a 0d 0a 0d 0a 0d 0a 0d 0a 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f ┆TERNAL USE ____________┆
0x0160…0180 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f ┆________________________________┆
0x0180…01a0 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 0d 0a 0d 0a ┆____________________________ ┆
0x01a0…01c0 54 69 74 6c 65 3a 0d 0a 0d 0a 06 52 43 4c 4c 43 0d 0a 06 50 72 6f 74 6f 63 6f 6c 20 66 6f 72 20 ┆Title: RCLLC Protocol for ┆
0x01c0…01e0 4c 6f 67 69 63 61 6c 20 4c 69 6e 6b 20 43 6f 6e 74 72 6f 6c 0d 0a 06 69 6e 20 52 43 20 4c 6f 63 ┆Logical Link Control in RC Loc┆
0x01e0…0200 61 6c 20 41 72 65 61 20 4e 65 74 77 6f 72 6b 73 0d 0a 0d 0a 0d 0a 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f ┆al Area Networks __________┆
0x0200…0220 (1,) 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f ┆________________________________┆
0x0220…0240 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 5f 0d 0a ┆______________________________ ┆
0x0240…0243 FormFeed {
0x0240…0243 0c 82 c4 ┆ ┆
0x0240…0243 }
0x0243…0260 0a 06 69 0d 0a 0d 0a 0d 0a 0d 0a a1 54 41 42 4c 45 20 4f 46 20 43 4f 4e 54 45 4e 54 53 ┆ i TABLE OF CONTENTS┆
0x0260…0280 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ┆ ┆
0x0280…0299 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 50 41 47 45 0d 0a ┆ PAGE ┆
0x0299…02d2 Params {
0x0299…02d2 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1` ┆
0x0299…02d2 00 00 00 00 00 00 00 00 05 0a 11 19 1e 46 4b 55 5f 69 73 7d ff ff ff ff 04 ┆ FKU_iså ┆
0x0299…02d2 }
0x02d2…030b Params {
0x02d2…030b 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1` ┆
0x02d2…030b 00 00 00 00 00 00 00 00 2a 34 41 4b 55 5f 69 73 7d 87 91 ff ff ff ff ff 04 ┆ *4AKU_iså ┆
0x02d2…030b }
0x030b…0320 0a 0d 0a 0d 0a 31 2e 09 49 4e 54 52 4f 44 55 43 54 49 4f 4e 20 ┆ 1. INTRODUCTION ┆
0x0320…0340 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆................................┆
0x0340…0360 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 20 20 20 31 0d 0a 0d 0a 32 2e 09 46 55 ┆................... 1 2. FU┆
0x0360…0380 4e 44 41 4d 45 4e 54 41 4c 20 43 4f 4e 43 45 50 54 53 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆NDAMENTAL CONCEPTS .............┆
0x0380…03a0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 20 20 ┆.............................. ┆
0x03a0…03c0 20 33 0d 0a 0d 0a 33 2e 09 53 45 52 56 49 43 45 20 49 4e 54 45 52 46 41 43 45 53 20 2e 2e 2e 2e ┆ 3 3. SERVICE INTERFACES ....┆
0x03c0…03e0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆................................┆
0x03e0…0400 2e 2e 2e 2e 2e 2e 2e 2e 2e 20 20 20 35 0d 0a 09 33 2e 31 09 4d 41 43 20 53 65 72 76 69 63 65 20 ┆......... 5 3.1 MAC Service ┆
0x0400…0420 (2,) 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆................................┆
0x0420…0440 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 35 0d 0a 09 33 2e 32 09 52 43 4c 4c 43 20 ┆............... 5 3.2 RCLLC ┆
0x0440…0460 53 65 72 76 69 63 65 73 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆Services .......................┆
0x0460…0480 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 36 0d 0a 09 09 33 2e 32 ┆..................... 6 3.2┆
0x0480…04a0 2e 31 09 53 41 50 20 41 63 74 69 76 61 74 69 6f 6e 20 61 6e 64 20 44 65 61 63 74 69 76 61 74 69 ┆.1 SAP Activation and Deactivati┆
0x04a0…04c0 6f 6e 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 36 0d 0a 09 09 09 ┆on .................... 6 ┆
0x04c0…04e0 33 2e 32 2e 31 2e 31 09 41 43 54 49 56 41 54 45 2e 72 65 71 75 65 73 74 20 2e 2e 2e 2e 2e 2e 2e ┆3.2.1.1 ACTIVATE.request .......┆
0x04e0…0500 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 36 0d 0a 09 09 09 33 2e 32 ┆.................... 6 3.2┆
0x0500…0520 2e 31 2e 32 09 41 43 54 49 56 41 54 45 2e 63 6f 6e 66 69 72 6d 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆.1.2 ACTIVATE.confirm ..........┆
0x0520…0540 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 37 0d 0a 09 09 09 33 2e 32 2e 31 2e ┆................. 7 3.2.1.┆
0x0540…0560 33 09 44 45 41 43 54 49 56 41 54 45 2e 72 65 71 75 65 73 74 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆3 DEACTIVATE.request ...........┆
0x0560…0580 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 37 0d 0a 09 09 09 33 2e 32 2e 31 2e 34 09 44 ┆.............. 7 3.2.1.4 D┆
0x0580…05a0 45 41 43 54 49 56 41 54 45 2e 63 6f 6e 66 69 72 6d 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆EACTIVATE.confirm ..............┆
0x05a0…05c0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 38 0d 0a 09 09 33 2e 32 2e 32 09 4c 6f 6f 70 2d 62 61 ┆........... 8 3.2.2 Loop-ba┆
0x05c0…05e0 63 6b 20 54 65 73 74 20 53 65 72 76 69 63 65 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ck Test Service ................┆
0x05e0…0600 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 38 0d 0a 09 09 09 33 2e 32 2e 32 2e 31 09 54 45 ┆............. 8 3.2.2.1 TE┆
0x0600…0620 (3,) 53 54 2e 72 65 71 75 65 73 74 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ST.request .....................┆
0x0620…0640 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 20 38 0d 0a 09 09 09 33 2e 32 2e 32 2e 32 09 54 45 53 54 2e ┆.......... 8 3.2.2.2 TEST.┆
0x0640…0660 63 6f 6e 66 69 72 6d 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆confirm ........................┆
0x0660…0680 2e 2e 2e 2e 2e 2e 2e 09 20 20 39 0d 0a 09 09 09 33 2e 32 2e 32 2e 33 09 54 45 53 54 2e 69 6e 64 ┆....... 9 3.2.2.3 TEST.ind┆
0x0680…06a0 69 63 61 74 69 6f 6e 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ication ........................┆
0x06a0…06c0 2e 2e 2e 2e 09 20 20 39 0d 0a 09 09 33 2e 32 2e 33 09 54 79 70 65 20 31 20 53 65 72 76 69 63 65 ┆.... 9 3.2.3 Type 1 Service┆
0x06c0…06e0 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ ...............................┆
0x06e0…0700 2e 2e 2e 2e 2e 2e 09 20 31 30 0d 0a 09 09 09 33 2e 32 2e 33 2e 31 20 55 44 41 54 41 2e 72 65 71 ┆...... 10 3.2.3.1 UDATA.req┆
0x0700…0720 75 65 73 74 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆uest ...........................┆
0x0720…0740 2e 2e 2e 09 20 31 30 0d 0a 09 09 09 33 2e 32 2e 33 2e 32 09 55 44 41 54 41 2e 69 6e 64 69 63 61 ┆... 10 3.2.3.2 UDATA.indica┆
0x0740…0760 74 69 6f 6e 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆tion ...........................┆
0x0760…0780 09 20 31 31 0d 0a 09 09 33 2e 32 2e 34 09 43 6c 69 65 6e 74 20 4e 65 74 77 6f 72 6b 20 53 65 72 ┆ 11 3.2.4 Client Network Ser┆
0x0780…07a0 76 69 63 65 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆vice ...........................┆
0x07a0…07c0 2e 2e 09 20 31 31 0d 0a 09 09 09 33 2e 32 2e 34 2e 31 09 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 ┆.. 11 3.2.4.1 CONNECT.indic┆
0x07c0…07e0 61 74 69 6f 6e 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 ┆ation ......................... ┆
0x07e0…0800 20 31 32 0d 0a 09 09 09 33 2e 32 2e 34 2e 32 09 44 49 53 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 ┆ 12 3.2.4.2 DISCONNECT.indic┆
0x0800…0820 (4,) 61 74 69 6f 6e 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 31 33 ┆ation ...................... 13┆
0x0820…0840 0d 0a 09 09 09 33 2e 32 2e 34 2e 33 09 44 49 53 43 4f 4e 4e 45 43 54 2e 61 63 6b 6e 6f 77 6c 65 ┆ 3.2.4.3 DISCONNECT.acknowle┆
0x0840…0860 64 67 65 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 31 33 0d 0a 09 ┆dge ..................... 13 ┆
0x0860…0880 09 09 33 2e 32 2e 34 2e 34 09 44 41 54 41 2e 72 65 71 75 65 73 74 20 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ 3.2.4.4 DATA.request .........┆
0x0880…08a0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 31 33 0d 0a 09 09 09 33 ┆...................... 13 3┆
0x08a0…08c0 2e 32 2e 34 2e 35 20 44 41 54 41 2e 63 6f 6e 66 69 72 6d 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆.2.4.5 DATA.confirm ............┆
0x08c0…08e0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 20 20 31 34 0d 0a 09 09 09 33 2e 32 2e ┆................... 14 3.2.┆
0x08e0…0900 34 2e 36 09 44 41 54 41 2e 69 6e 64 69 63 61 74 69 6f 6e 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆4.6 DATA.indication ............┆
0x0900…0920 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 31 34 0d 0a 0d 0a 34 2e 09 52 43 4c 4c 43 ┆................ 14 4. RCLLC┆
0x0920…0940 20 50 52 4f 43 45 44 55 52 45 53 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ PROCEDURES ....................┆
0x0940…0960 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 20 20 31 35 0d ┆........................... 15 ┆
0x0960…0980 0a 09 34 2e 31 09 54 79 70 65 20 31 20 50 72 6f 63 65 64 75 72 65 73 20 2e 2e 2e 2e 2e 2e 2e 2e ┆ 4.1 Type 1 Procedures ........┆
0x0980…09a0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆................................┆
0x09a0…09c0 2e 09 20 31 35 0d 0a 09 09 34 2e 31 2e 31 09 55 6e 61 63 6b 6e 6f 77 6c 65 64 67 65 64 20 44 61 ┆. 15 4.1.1 Unacknowledged Da┆
0x09c0…09e0 74 61 20 54 72 61 6e 73 66 65 72 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ta Transfer ....................┆
0x09e0…0a00 2e 2e 2e 09 20 31 35 0d 0a 09 09 34 2e 31 2e 32 09 4c 6f 6f 70 2d 62 61 63 6b 20 54 65 73 74 20 ┆... 15 4.1.2 Loop-back Test ┆
0x0a00…0a20 (5,) 50 72 6f 63 65 64 75 72 65 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆Procedure ......................┆
0x0a20…0a40 2e 2e 2e 2e 2e 09 20 31 36 0d 0a 09 09 34 2e 31 2e 33 09 53 74 61 74 69 6f 6e 20 49 64 65 6e 74 ┆..... 16 4.1.3 Station Ident┆
0x0a40…0a60 69 66 69 63 61 74 69 6f 6e 20 45 78 63 68 61 6e 67 65 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ification Exchange .............┆
0x0a60…0a80 2e 2e 2e 2e 2e 2e 2e 09 20 31 36 0d 0a 09 34 2e 32 09 50 72 6f 63 65 64 75 72 65 73 20 66 6f 72 ┆....... 16 4.2 Procedures for┆
0x0a80…0aa0 20 43 6c 69 65 6e 74 20 4e 65 74 77 6f 72 6b 20 53 65 72 76 69 63 65 20 2e 2e 2e 2e 2e 2e 2e 2e ┆ Client Network Service ........┆
0x0aa0…0ab5 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 31 37 0d 0a 0d 0a ┆............. 17 ┆
0x0ab5…0ab8 FormFeed {
0x0ab5…0ab8 0c 83 ec ┆ ┆
0x0ab5…0ab8 }
0x0ab8…0ac0 0a 06 69 69 0d 0a 0d 0a ┆ ii ┆
0x0ac0…0ae0 0d 0a 0d 0a a1 54 41 42 4c 45 20 4f 46 20 43 4f 4e 54 45 4e 54 53 20 28 63 6f 6e 74 2e 29 20 20 ┆ TABLE OF CONTENTS (cont.) ┆
0x0ae0…0b00 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ┆ ┆
0x0b00…0b20 20 20 20 20 20 20 20 20 20 50 41 47 45 0d 0a 0d 0a 0d 0a 35 2e 20 20 52 43 4c 4c 43 20 50 52 4f ┆ PAGE 5. RCLLC PRO┆
0x0b20…0b40 54 4f 43 4f 4c 20 45 4c 45 4d 45 4e 54 53 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆TOCOL ELEMENTS .................┆
0x0b40…0b60 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 20 20 32 33 0d 0a 09 35 2e ┆....................... 23 5.┆
0x0b60…0b80 31 09 54 79 70 65 20 31 20 50 72 6f 74 6f 63 6f 6c 20 45 6c 65 6d 65 6e 74 73 20 2e 2e 2e 2e 2e ┆1 Type 1 Protocol Elements .....┆
0x0b80…0ba0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 20 20 32 ┆............................. 2┆
0x0ba0…0bc0 35 0d 0a 09 09 35 2e 31 2e 31 09 55 49 20 28 55 6e 6e 75 6d 62 65 72 65 64 20 49 6e 66 6f 72 6d ┆5 5.1.1 UI (Unnumbered Inform┆
0x0bc0…0be0 61 74 69 6f 6e 29 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 ┆ation) ........................ ┆
0x0be0…0c00 20 32 35 0d 0a 09 09 35 2e 31 2e 32 20 20 58 49 44 20 28 65 58 63 68 61 6e 67 65 20 49 44 65 6e ┆ 25 5.1.2 XID (eXchange IDen┆
0x0c00…0c20 (6,) 74 69 66 69 63 61 74 69 6f 6e 29 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆tification) ....................┆
0x0c20…0c40 2e 2e 09 20 32 36 0d 0a 09 09 35 2e 31 2e 33 09 54 45 53 54 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆.. 26 5.1.3 TEST ...........┆
0x0c40…0c60 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆................................┆
0x0c60…0c80 2e 2e 2e 2e 09 20 32 36 0d 0a 09 35 2e 32 09 50 72 6f 74 6f 63 6f 6c 20 45 6c 65 6d 65 6e 74 73 ┆.... 26 5.2 Protocol Elements┆
0x0c80…0ca0 20 66 6f 72 20 43 6c 69 65 6e 74 20 4e 65 74 77 6f 72 6b 20 53 65 72 76 69 63 65 20 2e 2e 2e 2e ┆ for Client Network Service ....┆
0x0ca0…0cc0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 32 36 0d 0a 09 09 35 2e 32 2e 31 09 41 43 54 49 56 45 5f 53 ┆.......... 26 5.2.1 ACTIVE_S┆
0x0cc0…0ce0 41 50 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆AP .............................┆
0x0ce0…0d00 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 32 36 0d 0a 09 09 35 2e 32 2e 32 09 52 45 53 45 54 20 ┆............ 26 5.2.2 RESET ┆
0x0d00…0d20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆................................┆
0x0d20…0d40 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 32 37 0d 0a 09 09 35 2e 32 2e 33 09 52 41 43 4b ┆.............. 27 5.2.3 RACK┆
0x0d40…0d60 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ ...............................┆
0x0d60…0d80 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 32 38 0d 0a 09 09 35 2e 32 2e 34 09 44 41 ┆................ 28 5.2.4 DA┆
0x0d80…0da0 54 41 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆TA .............................┆
0x0da0…0dc0 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 32 38 0d 0a 09 09 35 2e 32 2e 35 09 ┆.................. 28 5.2.5 ┆
0x0dc0…0de0 41 43 4b 20 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆ACK ............................┆
0x0de0…0e00 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 32 38 0d 0a 0d 0a 0d 0a a1 41 ┆.................... 28 A┆
0x0e00…0e20 (7,) 50 50 45 4e 44 49 43 45 53 0d 0a 0d 0a 41 2e 20 20 52 65 66 65 72 65 6e 63 65 73 20 2e 2e 2e 2e ┆PPENDICES A. References ....┆
0x0e20…0e40 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e ┆................................┆
0x0e40…0e57 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 2e 09 20 33 30 0d 0a ┆................. 30 ┆
0x0e57…0e5a FormFeed {
0x0e57…0e5a 0c 82 94 ┆ ┆
0x0e57…0e5a }
0x0e5a…0e60 0a 14 b3 52 43 4c ┆ RCL┆
0x0e60…0e80 4c 43 20 50 72 6f 74 6f 63 6f 6c 05 50 61 67 65 20 0b 0d 0a a1 31 2e 20 20 20 20 20 49 4e 54 52 ┆LC Protocol Page 1. INTR┆
0x0e80…0ea0 4f 44 55 43 54 49 4f 4e 0d 0a 0d 0a 54 68 69 73 20 64 6f 63 75 6d 65 6e 74 20 69 73 20 74 68 65 ┆ODUCTION This document is the┆
0x0ea0…0ec0 20 72 65 66 65 72 65 6e 63 65 20 64 65 66 69 6e 69 74 69 6f 6e 20 6f 66 20 74 68 65 20 70 72 6f ┆ reference definition of the pro┆
0x0ec0…0ee0 74 6f 63 6f 6c 20 66 6f 72 20 6c 6f 67 69 63 61 6c 20 0a 6c 69 6e 6b 20 63 6f 6e 74 72 6f 6c 20 ┆tocol for logical link control ┆
0x0ee0…0f00 69 6e 20 61 6e 20 52 43 20 6c 6f 63 61 6c 20 61 72 65 61 20 6e 65 74 77 6f 72 6b 2c 20 74 68 65 ┆in an RC local area network, the┆
0x0f00…0f20 20 a1 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c e1 2e 20 54 68 65 20 0a 70 72 6f 74 6f 63 6f 6c ┆ RCLLC protocol . The protocol┆
0x0f20…0f40 20 61 70 70 6c 69 65 73 20 74 6f 20 74 68 65 20 69 6e 74 65 72 63 6f 6d 6d 75 6e 69 63 61 74 69 ┆ applies to the intercommunicati┆
0x0f40…0f60 6f 6e 20 62 65 74 77 65 65 6e 20 74 68 6f 73 65 20 73 74 61 74 69 6f 6e 73 20 0a 61 74 74 61 63 ┆on between those stations attac┆
0x0f60…0f80 68 65 64 20 74 6f 20 73 75 63 68 20 61 20 6c 6f 63 61 6c 20 61 72 65 61 20 6e 65 74 77 6f 72 6b ┆hed to such a local area network┆
0x0f80…0fa0 20 77 68 69 63 68 20 61 72 65 20 52 43 20 70 72 6f 64 75 63 74 73 2e 20 49 74 20 64 6f 65 73 20 ┆ which are RC products. It does ┆
0x0fa0…0fc0 6e 6f 74 20 0a 72 75 6c 65 20 6f 75 74 20 74 68 65 20 61 74 74 61 63 68 6d 65 6e 74 20 6f 66 20 ┆not rule out the attachment of ┆
0x0fc0…0fe0 6f 74 68 65 72 20 6d 61 6e 75 66 61 63 74 75 72 65 72 73 27 20 70 72 6f 64 75 63 74 73 20 74 6f ┆other manufacturers' products to┆
0x0fe0…1000 20 74 68 65 20 73 61 6d 65 20 0a 6e 65 74 77 6f 72 6b 2c 20 6e 6f 72 20 74 68 65 20 63 6f 6f 70 ┆ the same network, nor the coop┆
0x1000…1020 (8,) 65 72 61 74 69 6f 6e 20 62 65 74 77 65 65 6e 20 52 43 20 70 72 6f 64 75 63 74 73 20 61 6e 64 20 ┆eration between RC products and ┆
0x1020…1040 73 75 63 68 20 6f 74 68 65 72 20 0a 70 72 6f 64 75 63 74 73 2e 0d 0a 0d 0a 49 6e 20 6f 72 64 65 ┆such other products. In orde┆
0x1040…1060 72 20 74 6f 20 70 6c 61 63 65 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 69 6e 20 70 72 6f 70 65 ┆r to place the protocol in prope┆
0x1060…1080 72 20 63 6f 6e 74 65 78 74 2c 20 61 20 64 65 73 63 72 69 70 74 69 6f 6e 20 6f 66 20 74 68 65 20 ┆r context, a description of the ┆
0x1080…10a0 0a 73 65 72 76 69 63 65 20 70 72 6f 76 69 64 65 64 20 62 79 20 74 68 65 20 52 43 4c 4c 43 20 6c ┆ service provided by the RCLLC l┆
0x10a0…10c0 61 79 65 72 20 61 6e 64 20 6f 66 20 74 68 65 20 62 65 68 61 76 69 6f 72 20 6f 66 20 52 43 4c 4c ┆ayer and of the behavior of RCLL┆
0x10c0…10e0 43 20 0a 65 6e 74 69 74 69 65 73 20 69 73 20 61 6c 73 6f 20 67 69 76 65 6e 2e 20 54 68 65 20 64 ┆C entities is also given. The d┆
0x10e0…1100 65 73 63 72 69 70 74 69 6f 6e 20 6f 66 20 74 68 65 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 ┆escription of the RCLLC service ┆
0x1100…1120 69 73 20 74 6f 20 62 65 20 0a 75 6e 64 65 72 73 74 6f 6f 64 20 69 6e 20 61 6e 20 61 62 73 74 72 ┆is to be understood in an abstr┆
0x1120…1140 61 63 74 20 73 65 6e 73 65 20 61 6e 64 20 73 68 6f 75 6c 64 20 6e 6f 74 20 62 65 20 69 6e 74 65 ┆act sense and should not be inte┆
0x1140…1160 72 70 72 65 74 65 64 20 61 73 20 61 20 0a 70 72 65 73 63 72 69 70 74 69 6f 6e 20 66 6f 72 20 61 ┆rpreted as a prescription for a┆
0x1160…1180 6e 20 69 6d 70 6c 65 6d 65 6e 74 61 74 69 6f 6e 2e 20 49 6e 20 70 61 72 74 69 63 75 6c 61 72 2c ┆n implementation. In particular,┆
0x1180…11a0 0d 0a 0d 0a 09 2d 20 84 73 6f 6d 65 20 6f 66 20 74 68 65 20 73 65 72 76 69 63 65 20 70 72 69 6d ┆ - some of the service prim┆
0x11a0…11c0 69 74 69 76 65 73 20 6d 61 79 20 62 65 20 73 74 61 74 69 63 61 6c 6c 79 20 69 6d 70 6c 65 6d 65 ┆itives may be statically impleme┆
0x11c0…11e0 6e 74 65 64 2c 20 69 2e 65 2e 20 0a 19 86 80 80 61 73 20 69 6e 69 74 69 61 6c 69 7a 61 74 69 6f ┆nted, i.e. as initializatio┆
0x11e0…1200 6e 73 2c 20 77 68 69 63 68 20 6d 61 79 20 6e 6f 74 20 72 65 71 75 69 72 65 20 61 6e 79 20 69 6e ┆ns, which may not require any in┆
0x1200…1220 (9,) 74 65 72 61 63 74 69 6f 6e 20 62 65 74 77 65 65 6e 20 0a 19 86 80 80 65 6e 74 69 74 69 65 73 3b ┆teraction between entities;┆
0x1220…1240 0d 0a 09 2d 20 84 73 6f 6d 65 20 73 74 61 74 69 6f 6e 73 20 6d 61 79 20 6f 66 66 65 72 20 6f 6e ┆ - some stations may offer on┆
0x1240…1260 6c 79 20 61 20 73 75 62 73 65 74 20 6f 66 20 74 68 65 20 63 6f 6d 70 6c 65 74 65 20 52 43 4c 4c ┆ly a subset of the complete RCLL┆
0x1260…1280 43 20 0a 19 86 80 80 73 65 72 76 69 63 65 2e 0d 0a 0d 0a 54 68 65 20 70 72 6f 74 6f 63 6f 6c 20 ┆C service. The protocol ┆
0x1280…12a0 61 6e 64 20 73 65 72 76 69 63 65 20 64 65 66 69 6e 65 64 20 69 6e 20 74 68 69 73 20 64 6f 63 75 ┆and service defined in this docu┆
0x12a0…12c0 6d 65 6e 74 20 66 6f 72 6d 20 61 6e 20 65 78 74 65 6e 73 69 6f 6e 20 74 6f 20 0a 74 68 65 20 70 ┆ment form an extension to the p┆
0x12c0…12e0 72 6f 70 6f 73 65 64 20 49 53 4f 20 4c 4c 43 20 74 79 70 65 20 31 20 70 72 6f 74 6f 63 6f 6c 20 ┆roposed ISO LLC type 1 protocol ┆
0x12e0…1300 61 6e 64 20 73 65 72 76 69 63 65 20 28 72 65 66 2e 20 31 29 2c 20 76 69 7a 2e 3a 0d 0a 0d 0a 09 ┆and service (ref. 1), viz.: ┆
0x1300…1320 2d 20 84 61 6c 6c 20 66 72 61 6d 65 73 20 77 68 69 63 68 20 61 72 65 20 76 61 6c 69 64 20 61 63 ┆- all frames which are valid ac┆
0x1320…1340 63 6f 72 64 69 6e 67 20 74 6f 20 74 68 65 20 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c 20 61 72 ┆cording to the RCLLC protocol ar┆
0x1340…1360 65 20 0a 19 86 80 80 61 6c 73 6f 20 76 61 6c 69 64 20 49 53 4f 20 4c 4c 43 20 74 79 70 65 20 31 ┆e also valid ISO LLC type 1┆
0x1360…1380 20 66 72 61 6d 65 73 3b 0d 0a 09 2d 20 84 52 43 4c 4c 43 20 61 64 64 73 20 70 72 6f 74 6f 63 6f ┆ frames; - RCLLC adds protoco┆
0x1380…13a0 6c 20 66 75 6e 63 74 69 6f 6e 73 20 61 6e 64 20 69 6e 74 65 72 66 61 63 65 20 73 65 72 76 69 63 ┆l functions and interface servic┆
0x13a0…13c0 65 20 66 75 6e 63 74 69 6f 6e 61 6c 69 74 79 20 0a 19 86 80 80 74 6f 20 49 53 4f 20 4c 4c 43 20 ┆e functionality to ISO LLC ┆
0x13c0…13e0 74 79 70 65 20 31 20 69 6e 20 61 20 66 61 73 68 69 6f 6e 20 77 68 69 63 68 20 6f 6e 65 20 6d 69 ┆type 1 in a fashion which one mi┆
0x13e0…1400 67 68 74 20 63 68 6f 6f 73 65 20 74 6f 20 63 6f 6e 73 69 64 65 72 20 0a 19 86 80 80 61 73 20 61 ┆ght choose to consider as a┆
0x1400…1420 (10,) 20 73 75 62 6c 61 79 65 72 20 61 64 64 65 64 20 6f 6e 20 74 6f 70 20 6f 66 20 61 6e 20 4c 4c 43 ┆ sublayer added on top of an LLC┆
0x1420…1440 20 74 79 70 65 20 31 20 73 75 62 6c 61 79 65 72 2e 0d 0a 0d 0a 54 68 65 20 73 65 72 76 69 63 65 ┆ type 1 sublayer. The service┆
0x1440…1460 73 20 6f 66 20 4c 4c 43 20 74 79 70 65 20 31 20 61 72 65 20 64 61 74 61 20 74 72 61 6e 73 66 65 ┆s of LLC type 1 are data transfe┆
0x1460…1480 72 20 6f 6e 20 63 6f 6e 6e 65 63 74 69 6f 6e 6c 65 73 73 20 64 61 74 61 20 0a 6c 69 6e 6b 73 2c ┆r on connectionless data links,┆
0x1480…14a0 20 61 6c 6c 6f 77 69 6e 67 20 6d 75 6c 74 69 70 6c 65 20 69 6e 64 65 70 65 6e 64 65 6e 74 20 63 ┆ allowing multiple independent c┆
0x14a0…14c0 6c 69 65 6e 74 73 20 77 69 74 68 69 6e 20 65 61 63 68 20 73 74 61 74 69 6f 6e 2c 20 70 6c 75 73 ┆lients within each station, plus┆
0x14c0…14e0 20 0a 66 61 63 69 6c 69 74 69 65 73 20 66 6f 72 20 70 6f 69 6e 74 2d 74 6f 2d 70 6f 69 6e 74 20 ┆ facilities for point-to-point ┆
0x14e0…1500 6c 6f 6f 70 20 62 61 63 6b 20 74 65 73 74 20 74 72 61 66 66 69 63 2e 0d 0a 0d 0a 54 68 65 20 65 ┆loop back test traffic. The e┆
0x1500…1520 73 73 65 6e 74 69 61 6c 20 73 65 72 76 69 63 65 20 6f 66 20 74 68 65 20 52 43 4c 4c 43 20 6c 61 ┆ssential service of the RCLLC la┆
0x1520…1540 79 65 72 2c 20 77 68 69 63 68 20 63 6f 6e 73 74 69 74 75 74 65 73 20 61 6e 20 65 78 74 65 6e 73 ┆yer, which constitutes an extens┆
0x1540…1560 69 6f 6e 20 0a 74 6f 20 74 68 65 20 74 79 70 65 20 31 20 73 65 72 76 69 63 65 2c 20 69 73 20 63 ┆ion to the type 1 service, is c┆
0x1560…1580 61 6c 6c 65 64 20 a1 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 73 65 72 76 69 63 65 e1 2e 20 ┆alled client network service . ┆
0x1580…15a0 54 68 69 73 20 73 65 72 76 69 63 65 20 0a 63 6f 6d 70 72 69 73 65 73 20 74 68 65 20 64 79 6e 61 ┆This service comprises the dyna┆
0x15a0…15c0 6d 69 63 20 63 6f 6e 66 69 67 75 72 61 74 69 6f 6e 2c 20 6d 61 69 6e 74 65 6e 61 6e 63 65 20 61 ┆mic configuration, maintenance a┆
0x15c0…15e0 6e 64 20 73 75 70 65 72 76 69 73 69 6f 6e 20 6f 66 20 0a 8c 83 c8 0a 6d 75 6c 74 69 70 6c 65 20 ┆nd supervision of multiple ┆
0x15e0…1600 69 6e 64 65 70 65 6e 64 65 6e 74 20 6e 65 74 77 6f 72 6b 73 20 6f 66 20 63 6c 69 65 6e 74 73 2e ┆independent networks of clients.┆
0x1600…1620 (11,) 20 43 6f 6e 6e 65 63 74 69 6f 6e 2d 62 61 73 65 64 20 64 61 74 61 20 74 72 61 6e 73 66 65 72 20 ┆ Connection-based data transfer ┆
0x1620…1640 0a 77 69 74 68 20 73 65 71 75 65 6e 63 65 20 63 6f 6e 74 72 6f 6c 20 61 6e 64 20 72 65 74 72 61 ┆ with sequence control and retra┆
0x1640…1660 6e 73 6d 69 73 73 69 6f 6e 20 74 6f 20 61 76 6f 69 64 20 6c 6f 73 73 20 6f 66 20 6f 72 20 64 61 ┆nsmission to avoid loss of or da┆
0x1660…1680 6d 61 67 65 20 74 6f 20 0a 64 61 74 61 20 69 73 20 70 65 72 66 6f 72 6d 65 64 20 62 65 74 77 65 ┆mage to data is performed betwe┆
0x1680…16a0 65 6e 20 61 6e 79 20 70 61 69 72 20 6f 66 20 63 6c 69 65 6e 74 73 20 62 65 6c 6f 6e 67 69 6e 67 ┆en any pair of clients belonging┆
0x16a0…16c0 20 74 6f 20 74 68 65 20 73 61 6d 65 20 0a 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 2e 0d 0a 0d ┆ to the same client network. ┆
0x16c0…16e0 0a 54 77 6f 20 74 79 70 65 73 20 6f 66 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 73 20 61 72 ┆ Two types of client networks ar┆
0x16e0…1700 65 20 66 6f 72 65 73 65 65 6e 20 61 6e 64 20 73 70 65 63 69 66 69 63 61 6c 6c 79 20 63 61 74 65 ┆e foreseen and specifically cate┆
0x1700…1720 72 65 64 20 66 6f 72 20 0a 69 6e 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 64 65 73 69 67 6e 3a ┆red for in the protocol design:┆
0x1720…1740 0d 0a 0d 0a 31 29 20 84 49 4d 43 20 6e 65 74 77 6f 72 6b 73 20 28 72 65 66 73 2e 20 33 2c 34 29 ┆ 1) IMC networks (refs. 3,4)┆
0x1740…1760 20 77 68 69 63 68 20 6d 61 79 20 69 6e 76 6f 6c 76 65 20 61 20 77 69 64 65 20 76 61 72 69 65 74 ┆ which may involve a wide variet┆
0x1760…1780 79 20 6f 66 20 52 43 20 0a 19 83 80 80 70 72 6f 64 75 63 74 73 2e 20 54 68 65 20 28 52 43 4c 4c ┆y of RC products. The (RCLL┆
0x1780…17a0 43 29 20 63 6c 69 65 6e 74 73 20 69 6e 20 61 6e 20 49 4d 43 20 6e 65 74 77 6f 72 6b 20 61 72 65 ┆C) clients in an IMC network are┆
0x17a0…17c0 20 74 68 65 20 49 4d 43 20 6e 6f 64 65 73 3b 0d 0a 32 29 20 84 43 43 50 2f 4d 20 44 52 20 4e 45 ┆ the IMC nodes; 2) CCP/M DR NE┆
0x17c0…17e0 54 20 28 72 65 66 2e 20 35 29 20 6e 65 74 77 6f 72 6b 73 20 69 6e 20 77 68 69 63 68 20 74 68 65 ┆T (ref. 5) networks in which the┆
0x17e0…1800 20 73 74 61 74 69 6f 6e 73 20 61 72 65 20 52 43 37 35 30 20 0a 19 83 80 80 50 65 72 73 6f 6e 61 ┆ stations are RC750 Persona┆
0x1800…1820 (12,) 6c 20 43 6f 6d 70 75 74 65 72 73 2e 20 45 61 63 68 20 6f 66 20 74 68 65 73 65 20 6d 61 79 20 61 ┆l Computers. Each of these may a┆
0x1820…1840 6c 73 6f 20 63 6f 6e 74 61 69 6e 20 61 6e 20 49 4d 43 20 6e 6f 64 65 20 61 6e 64 20 0a 19 83 80 ┆lso contain an IMC node and ┆
0x1840…1860 80 74 68 75 73 20 62 65 6c 6f 6e 67 20 74 6f 20 74 77 6f 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f ┆ thus belong to two client netwo┆
0x1860…1880 72 6b 73 2e 0d 0a 0d 0a 4c 69 6b 65 20 74 68 65 20 49 53 4f 20 4c 4c 43 20 70 72 6f 74 6f 63 6f ┆rks. Like the ISO LLC protoco┆
0x1880…18a0 6c 20 74 68 65 20 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c 20 61 73 73 75 6d 65 73 20 74 68 61 ┆l the RCLLC protocol assumes tha┆
0x18a0…18c0 74 20 74 68 65 20 73 65 72 76 69 63 65 73 20 0a 6f 66 20 61 20 4d 65 64 69 75 6d 20 41 63 63 65 ┆t the services of a Medium Acce┆
0x18c0…18e0 73 73 20 43 6f 6e 74 72 6f 6c 20 6c 61 79 65 72 20 61 72 65 20 61 76 61 69 6c 61 62 6c 65 2e 20 ┆ss Control layer are available. ┆
0x18e0…1900 54 68 65 20 73 65 72 76 69 63 65 73 20 6f 66 20 74 68 69 73 20 0a 6c 61 79 65 72 20 61 72 65 20 ┆The services of this layer are ┆
0x1900…1920 64 65 66 69 6e 65 64 20 73 6f 20 61 73 20 74 6f 20 62 65 20 69 6e 64 65 70 65 6e 64 65 6e 74 20 ┆defined so as to be independent ┆
0x1920…1940 6f 66 20 74 68 65 20 61 63 74 75 61 6c 20 6d 65 64 69 75 6d 2e 20 49 6e 20 0a 61 64 64 69 74 69 ┆of the actual medium. In additi┆
0x1940…1960 6f 6e 20 74 6f 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 66 20 66 72 61 6d 65 73 20 74 6f 20 ┆on to transmission of frames to ┆
0x1960…1980 61 20 73 70 65 63 69 66 69 63 20 73 74 61 74 69 6f 6e 20 61 20 6d 75 6c 74 69 63 61 73 74 20 0a ┆a specific station a multicast ┆
0x1980…199c 66 75 6e 63 74 69 6f 6e 20 6d 75 73 74 20 62 65 20 70 72 6f 76 69 64 65 64 2e 0d 0a ┆function must be provided. ┆
0x199c…199f FormFeed {
0x199c…199f 0c 81 e4 ┆ ┆
0x199c…199f }
0x199f…19a0 0a ┆ ┆
0x19a0…19c0 a1 32 2e 20 20 20 20 20 46 55 4e 44 41 4d 45 4e 54 41 4c 20 43 4f 4e 43 45 50 54 53 0d 0a 0d 0a ┆ 2. FUNDAMENTAL CONCEPTS ┆
0x19c0…19e0 54 68 65 20 66 6f 6c 6c 6f 77 69 6e 67 20 74 65 72 6d 73 20 61 72 65 20 75 73 65 64 20 69 6e 20 ┆The following terms are used in ┆
0x19e0…1a00 74 68 69 73 20 64 6f 63 75 6d 65 6e 74 20 77 69 74 68 20 74 68 65 69 72 20 73 74 61 6e 64 61 72 ┆this document with their standar┆
0x1a00…1a20 (13,) 64 20 0a 6d 65 61 6e 69 6e 67 20 61 73 20 64 65 66 69 6e 65 64 20 69 6e 20 74 68 65 20 49 53 4f ┆d meaning as defined in the ISO┆
0x1a20…1a40 20 6d 6f 64 65 6c 20 66 6f 72 20 4f 70 65 6e 20 53 79 73 74 65 6d 73 20 49 6e 74 65 72 63 6f 6e ┆ model for Open Systems Intercon┆
0x1a40…1a60 6e 65 63 74 69 6f 6e 20 0a 28 72 65 66 2e 20 32 29 3a 20 73 74 61 74 69 6f 6e 2c 20 6c 61 79 65 ┆nection (ref. 2): station, laye┆
0x1a60…1a80 72 2c 20 65 6e 74 69 74 79 2c 20 70 65 65 72 2c 20 70 72 6f 74 6f 63 6f 6c 2c 20 73 65 72 76 69 ┆r, entity, peer, protocol, servi┆
0x1a80…1aa0 63 65 20 70 72 69 6d 69 74 69 76 65 2c 20 0a 64 61 74 61 20 6c 69 6e 6b 2c 20 63 6f 6e 6e 65 63 ┆ce primitive, data link, connec┆
0x1aa0…1ac0 74 69 6f 6e 2e 0d 0a 0d 0a 46 75 72 74 68 65 72 20 63 6f 6e 63 65 70 74 73 20 61 6e 64 20 74 65 ┆tion. Further concepts and te┆
0x1ac0…1ae0 72 6d 69 6e 6f 6c 6f 67 79 20 77 68 69 63 68 20 61 72 65 20 6e 6f 74 20 6e 65 63 65 73 73 61 72 ┆rminology which are not necessar┆
0x1ae0…1b00 69 6c 79 20 66 6f 75 6e 64 20 69 6e 20 74 68 65 20 0a 49 53 4f 20 6d 6f 64 65 6c 2c 20 62 75 74 ┆ily found in the ISO model, but┆
0x1b00…1b20 20 75 73 65 64 20 69 6e 20 74 68 65 20 70 72 65 73 65 6e 74 20 64 6f 63 75 6d 65 6e 74 2c 20 61 ┆ used in the present document, a┆
0x1b20…1b40 72 65 20 64 65 66 69 6e 65 64 20 69 6e 20 74 68 65 20 0a 66 6f 6c 6c 6f 77 69 6e 67 3a 0d 0a 0d ┆re defined in the following: ┆
0x1b40…1b60 0a 41 6e 20 a1 52 43 4c 4c 43 20 73 74 61 74 69 6f 6e e1 20 69 73 20 61 20 73 74 61 74 69 6f 6e ┆ An RCLLC station is a station┆
0x1b60…1b80 20 77 68 69 63 68 20 69 73 20 61 74 74 61 63 68 65 64 20 74 6f 20 74 68 65 20 6c 6f 63 61 6c 20 ┆ which is attached to the local ┆
0x1b80…1ba0 61 72 65 61 20 0a 6e 65 74 77 6f 72 6b 20 61 6e 64 20 68 6f 73 74 73 20 61 6e 20 52 43 4c 4c 43 ┆area network and hosts an RCLLC┆
0x1ba0…1bc0 20 65 6e 74 69 74 79 20 74 68 61 74 20 63 6f 6d 6d 75 6e 69 63 61 74 65 73 20 77 69 74 68 20 70 ┆ entity that communicates with p┆
0x1bc0…1be0 65 65 72 20 65 6e 74 69 74 69 65 73 20 0a 69 6e 20 6f 74 68 65 72 20 52 43 4c 4c 43 20 73 74 61 ┆eer entities in other RCLLC sta┆
0x1be0…1c00 74 69 6f 6e 73 20 61 63 63 6f 72 64 69 6e 67 20 74 6f 20 74 68 65 20 52 43 4c 4c 43 20 70 72 6f ┆tions according to the RCLLC pro┆
0x1c00…1c20 (14,) 74 6f 63 6f 6c 2e 20 41 20 73 74 61 74 69 6f 6e 20 77 68 69 63 68 20 0a 73 75 70 70 6f 72 74 73 ┆tocol. A station which supports┆
0x1c20…1c40 20 6f 6e 6c 79 20 74 68 65 20 4c 4c 43 20 74 79 70 65 20 31 20 70 72 6f 74 6f 63 6f 6c 20 61 6e ┆ only the LLC type 1 protocol an┆
0x1c40…1c60 64 20 6e 6f 74 20 74 68 65 20 66 75 6c 6c 20 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c 20 69 73 ┆d not the full RCLLC protocol is┆
0x1c60…1c80 20 0a 6e 6f 74 20 63 6f 6e 73 69 64 65 72 65 64 20 61 6e 20 52 43 4c 4c 43 20 73 74 61 74 69 6f ┆ not considered an RCLLC statio┆
0x1c80…1ca0 6e 2e 20 55 6e 74 69 6c 20 74 68 65 20 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c 20 69 73 20 61 ┆n. Until the RCLLC protocol is a┆
0x1ca0…1cc0 64 6f 70 74 65 64 20 62 79 20 0a 6f 74 68 65 72 20 6d 61 6e 75 66 61 63 74 75 72 65 72 73 2c 20 ┆dopted by other manufacturers, ┆
0x1cc0…1ce0 61 6e 20 52 43 4c 4c 43 20 73 74 61 74 69 6f 6e 20 77 69 6c 6c 20 62 65 20 74 68 65 20 73 61 6d ┆an RCLLC station will be the sam┆
0x1ce0…1d00 65 20 61 73 20 61 6e 20 52 43 20 70 72 6f 64 75 63 74 20 0a 61 74 74 61 63 68 65 64 20 74 6f 20 ┆e as an RC product attached to ┆
0x1d00…1d20 74 68 65 20 6e 65 74 77 6f 72 6b 2e 0d 0a 0d 0a 54 68 65 20 a1 4d e1 65 64 69 75 6d 20 a1 41 e1 ┆the network. The M edium A ┆
0x1d20…1d40 63 63 65 73 73 20 a1 43 e1 6f 6e 74 72 6f 6c 20 28 4d 41 43 29 20 6c 61 79 65 72 20 69 73 20 74 ┆ccess C ontrol (MAC) layer is t┆
0x1d40…1d60 68 65 20 6f 6e 6c 79 20 70 72 6f 74 6f 63 6f 6c 20 6c 61 79 65 72 20 62 65 74 77 65 65 6e 20 0a ┆he only protocol layer between ┆
0x1d60…1d80 74 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 20 61 6e 64 20 74 68 65 20 70 68 79 73 69 63 61 6c ┆the RCLLC layer and the physical┆
0x1d80…1da0 20 6e 65 74 77 6f 72 6b 2e 20 45 61 63 68 20 52 43 4c 4c 43 20 73 74 61 74 69 6f 6e 20 63 6f 6e ┆ network. Each RCLLC station con┆
0x1da0…1dc0 74 61 69 6e 73 20 0a 70 72 65 63 69 73 65 6c 79 20 6f 6e 65 20 4d 41 43 20 65 6e 74 69 74 79 20 ┆tains precisely one MAC entity ┆
0x1dc0…1de0 61 6e 64 20 6f 6e 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 2e 20 54 68 65 20 a1 73 74 61 74 69 ┆and one RCLLC entity. The stati┆
0x1de0…1e00 6f 6e 20 61 64 64 72 65 73 73 e1 20 69 73 20 61 20 0a 75 6e 69 71 75 65 20 61 64 64 72 65 73 73 ┆on address is a unique address┆
0x1e00…1e20 (15,) 20 77 68 69 63 68 20 69 64 65 6e 74 69 66 69 65 73 20 74 68 65 20 73 74 61 74 69 6f 6e 20 77 69 ┆ which identifies the station wi┆
0x1e20…1e40 74 68 69 6e 20 74 68 65 20 6c 6f 63 61 6c 20 61 72 65 61 20 0a 6e 65 74 77 6f 72 6b 2e 20 49 74 ┆thin the local area network. It┆
0x1e40…1e60 20 66 6f 6c 6c 6f 77 73 20 74 68 61 74 20 74 68 65 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 ┆ follows that the station addres┆
0x1e60…1e80 73 20 69 73 20 61 6c 73 6f 20 61 20 75 6e 69 71 75 65 20 61 64 64 72 65 73 73 20 6f 66 20 0a 74 ┆s is also a unique address of t┆
0x1e80…1ea0 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a 54 68 65 20 64 61 74 61 20 75 6e 69 ┆he RCLLC entity. The data uni┆
0x1ea0…1ec0 74 73 20 74 68 61 74 20 61 72 65 20 74 72 61 6e 73 6d 69 74 74 65 64 20 61 6d 6f 6e 67 20 52 43 ┆ts that are transmitted among RC┆
0x1ec0…1ee0 4c 4c 43 20 65 6e 74 69 74 69 65 73 20 75 73 69 6e 67 20 74 68 65 20 4d 41 43 20 0a 73 65 72 76 ┆LLC entities using the MAC serv┆
0x1ee0…1f00 69 63 65 20 61 72 65 20 63 61 6c 6c 65 64 20 a1 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c 20 65 ┆ice are called RCLLC protocol e┆
0x1f00…1f20 6c 65 6d 65 6e 74 73 e1 2e 0d 0a 0d 0a 41 20 a1 63 6c 69 65 6e 74 e1 20 69 73 20 61 6e 20 52 43 ┆lements . A client is an RC┆
0x1f20…1f40 4c 4c 43 2d 75 73 65 72 2c 20 69 2e 65 2e 20 61 6e 20 65 6e 74 69 74 79 20 6d 61 6b 69 6e 67 20 ┆LLC-user, i.e. an entity making ┆
0x1f40…1f60 75 73 65 20 6f 66 20 74 68 65 20 52 43 4c 4c 43 20 0a 73 65 72 76 69 63 65 20 61 6e 64 20 6c 6f ┆use of the RCLLC service and lo┆
0x1f60…1f80 63 61 74 65 64 20 69 6e 20 74 68 65 20 6c 61 79 65 72 20 61 62 6f 76 65 20 74 68 65 20 52 43 4c ┆cated in the layer above the RCL┆
0x1f80…1fa0 4c 43 20 6c 61 79 65 72 2e 0d 0a 0d 0a 41 6e 20 52 43 4c 4c 43 20 a1 53 e1 65 72 76 69 63 65 20 ┆LC layer. An RCLLC S ervice ┆
0x1fa0…1fc0 a1 41 e1 63 63 65 73 73 20 a1 50 e1 6f 69 6e 74 20 28 53 41 50 29 20 69 73 20 74 68 65 20 28 6c ┆ A ccess P oint (SAP) is the (l┆
0x1fc0…1fe0 6f 67 69 63 61 6c 29 20 70 6f 69 6e 74 20 61 74 20 77 68 69 63 68 20 61 20 0a 63 6c 69 65 6e 74 ┆ogical) point at which a client┆
0x1fe0…2000 20 61 63 63 65 73 73 65 73 20 74 68 65 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 2e 20 57 69 74 ┆ accesses the RCLLC service. Wit┆
0x2000…2020 (16,) 68 69 6e 20 61 6e 20 52 43 4c 4c 43 20 73 74 61 74 69 6f 6e 20 65 61 63 68 20 53 41 50 20 69 73 ┆hin an RCLLC station each SAP is┆
0x2020…2040 20 0a 61 73 73 69 67 6e 65 64 20 61 20 a1 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 e1 ┆ assigned a local SAP address ┆
0x2040…2060 20 69 6e 20 74 68 65 20 72 61 6e 67 65 20 31 2e 2e 36 33 2e 20 54 68 65 20 a1 63 6f 6d 70 6c 65 ┆ in the range 1..63. The comple┆
0x2060…2080 74 65 20 53 41 50 20 0a 19 80 80 84 61 64 64 72 65 73 73 e1 20 69 73 20 74 68 65 20 70 61 69 72 ┆te SAP address is the pair┆
0x2080…20a0 20 28 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 2c 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 ┆ (station address, local SAP add┆
0x20a0…20c0 72 65 73 73 29 20 77 68 69 63 68 20 75 6e 69 71 75 65 6c 79 20 0a 69 64 65 6e 74 69 66 69 65 73 ┆ress) which uniquely identifies┆
0x20c0…20e0 20 61 20 53 41 50 20 77 69 74 68 69 6e 20 74 68 65 20 6c 6f 63 61 6c 20 61 72 65 61 20 6e 65 74 ┆ a SAP within the local area net┆
0x20e0…2100 77 6f 72 6b 2e 0d 0a 0d 0a 8c 83 c8 0a 41 20 53 41 50 20 63 61 6e 20 62 65 20 a1 69 6e 61 63 74 ┆work. A SAP can be inact┆
0x2100…2120 69 76 65 e1 2c 20 69 6e 20 77 68 69 63 68 20 63 61 73 65 20 69 74 20 69 73 20 65 66 66 65 63 74 ┆ive , in which case it is effect┆
0x2120…2140 69 76 65 6c 79 20 75 6e 6b 6e 6f 77 6e 20 74 6f 20 74 68 65 20 0a 52 43 4c 4c 43 20 6c 61 79 65 ┆ively unknown to the RCLLC laye┆
0x2140…2160 72 20 73 6f 20 74 68 61 74 20 61 6c 6c 20 64 61 74 61 20 61 6e 64 20 63 6f 6e 74 72 6f 6c 20 69 ┆r so that all data and control i┆
0x2160…2180 6e 66 6f 72 6d 61 74 69 6f 6e 20 61 64 64 72 65 73 73 65 64 20 74 6f 20 69 74 20 69 73 20 0a 64 ┆nformation addressed to it is d┆
0x2180…21a0 69 73 63 61 72 64 65 64 3b 20 6f 72 20 69 74 20 63 61 6e 20 62 65 20 a1 61 63 74 69 76 65 e1 2e ┆iscarded; or it can be active .┆
0x21a0…21c0 20 41 6e 20 61 63 74 69 76 65 20 53 41 50 20 63 61 6e 20 62 65 20 75 73 65 64 20 74 6f 20 6f 62 ┆ An active SAP can be used to ob┆
0x21c0…21e0 74 61 69 6e 20 0a 65 69 74 68 65 72 20 74 79 70 65 20 31 20 73 65 72 76 69 63 65 20 6f 72 20 63 ┆tain either type 1 service or c┆
0x21e0…2200 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 73 65 72 76 69 63 65 2c 20 62 75 74 20 6e 6f 74 20 62 ┆lient network service, but not b┆
0x2200…2220 (17,) 6f 74 68 2e 0d 0a 0d 0a 54 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 20 6d 61 69 6e 74 61 69 6e ┆oth. The RCLLC layer maintain┆
0x2220…2240 73 20 61 20 6e 75 6d 62 65 72 20 6f 66 20 6c 6f 67 69 63 61 6c 20 a1 63 6c 69 65 6e 74 20 6e 65 ┆s a number of logical client ne┆
0x2240…2260 74 77 6f 72 6b 73 e1 2e 20 41 20 63 6c 69 65 6e 74 20 0a 6e 65 74 77 6f 72 6b 20 68 61 73 20 61 ┆tworks . A client network has a┆
0x2260…2280 20 a1 6e 65 74 77 6f 72 6b 20 6e 75 6d 62 65 72 e1 20 28 77 69 74 68 69 6e 20 74 68 65 20 6c 6f ┆ network number (within the lo┆
0x2280…22a0 63 61 6c 20 61 72 65 61 20 6e 65 74 77 6f 72 6b 29 2c 20 77 68 69 63 68 20 6d 75 73 74 20 0a 62 ┆cal area network), which must b┆
0x22a0…22c0 65 20 69 6e 20 74 68 65 20 72 61 6e 67 65 20 31 2e 2e 36 33 2c 20 61 6e 64 20 63 6f 6d 70 72 69 ┆e in the range 1..63, and compri┆
0x22c0…22e0 73 65 73 20 61 6c 6c 20 61 63 74 69 76 65 20 53 41 50 73 20 77 69 74 68 69 6e 20 52 43 4c 4c 43 ┆ses all active SAPs within RCLLC┆
0x22e0…2300 20 0a 73 74 61 74 69 6f 6e 73 20 6f 6e 20 74 68 65 20 6c 6f 63 61 6c 20 61 72 65 61 20 6e 65 74 ┆ stations on the local area net┆
0x2300…2320 77 6f 72 6b 20 77 68 6f 73 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 65 73 20 61 ┆work whose local SAP addresses a┆
0x2320…2340 72 65 20 65 71 75 61 6c 20 0a 74 6f 20 74 68 69 73 20 6e 75 6d 62 65 72 2c 20 61 6e 64 20 66 6f ┆re equal to this number, and fo┆
0x2340…2360 72 20 77 68 69 63 68 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 73 65 72 76 69 63 65 20 68 ┆r which client network service h┆
0x2360…2380 61 73 20 62 65 65 6e 20 72 65 71 75 65 73 74 65 64 2e 0d 0a 0d 0a 46 6f 72 20 61 6c 6c 20 52 43 ┆as been requested. For all RC┆
0x2380…23a0 20 6c 6f 63 61 6c 20 61 72 65 61 20 6e 65 74 77 6f 72 6b 73 20 63 6c 69 65 6e 74 20 6e 65 74 77 ┆ local area networks client netw┆
0x23a0…23c0 6f 72 6b 20 6e 75 6d 62 65 72 20 31 20 69 73 20 61 73 73 69 67 6e 65 64 20 74 6f 20 61 6e 20 0a ┆ork number 1 is assigned to an ┆
0x23c0…23e0 49 4d 43 20 6e 65 74 77 6f 72 6b 2c 20 69 2e 65 2e 20 74 68 65 20 49 4d 43 20 6e 6f 64 65 73 20 ┆IMC network, i.e. the IMC nodes ┆
0x23e0…2400 69 6e 20 74 68 65 20 52 43 4c 4c 43 20 73 74 61 74 69 6f 6e 73 20 6f 66 20 61 20 6c 6f 63 61 6c ┆in the RCLLC stations of a local┆
0x2400…2420 (18,) 20 61 72 65 61 20 0a 6e 65 74 77 6f 72 6b 20 77 69 6c 6c 20 61 6c 6c 20 61 63 63 65 73 73 20 74 ┆ area network will all access t┆
0x2420…2440 68 65 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 75 73 69 6e 67 20 61 20 6c 6f 63 61 6c 20 53 ┆he RCLLC service using a local S┆
0x2440…2460 41 50 20 61 64 64 72 65 73 73 20 6f 66 20 0a 31 2e 20 53 69 6d 69 6c 61 72 6c 79 2c 20 63 6c 69 ┆AP address of 1. Similarly, cli┆
0x2460…2480 65 6e 74 20 6e 65 74 77 6f 72 6b 20 6e 75 6d 62 65 72 20 32 20 69 73 20 75 73 65 64 20 66 6f 72 ┆ent network number 2 is used for┆
0x2480…24a0 20 44 52 20 4e 45 54 2e 0d 0a 0d 0a 41 73 73 6f 63 69 61 74 65 64 20 77 69 74 68 20 65 61 63 68 ┆ DR NET. Associated with each┆
0x24a0…24c0 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 77 69 74 68 69 6e 20 61 20 6c 6f 63 61 6c 20 61 ┆ client network within a local a┆
0x24c0…24e0 72 65 61 20 6e 65 74 77 6f 72 6b 20 69 73 20 61 20 0a 6d 75 6c 74 69 63 61 73 74 20 61 64 64 72 ┆rea network is a multicast addr┆
0x24e0…2500 65 73 73 20 77 68 69 63 68 20 64 65 6c 69 6d 69 74 73 20 74 68 65 20 52 43 4c 4c 43 20 73 74 61 ┆ess which delimits the RCLLC sta┆
0x2500…2520 74 69 6f 6e 73 20 74 68 61 74 20 74 61 6b 65 20 70 61 72 74 20 69 6e 20 0a 74 68 65 20 63 6c 69 ┆tions that take part in the cli┆
0x2520…2540 65 6e 74 20 6e 65 74 77 6f 72 6b 20 66 72 6f 6d 20 61 6c 6c 20 6f 74 68 65 72 20 73 74 61 74 69 ┆ent network from all other stati┆
0x2540…2560 6f 6e 73 20 6f 6e 20 74 68 65 20 6e 65 74 77 6f 72 6b 3b 20 69 2e 65 2e 20 61 20 66 72 61 6d 65 ┆ons on the network; i.e. a frame┆
0x2560…2580 20 0a 77 68 69 63 68 20 69 73 20 74 72 61 6e 73 6d 69 74 74 65 64 20 6f 6e 20 74 68 65 20 6c 6f ┆ which is transmitted on the lo┆
0x2580…25a0 63 61 6c 20 61 72 65 61 20 6e 65 74 77 6f 72 6b 20 77 69 74 68 20 74 68 69 73 20 6d 75 6c 74 69 ┆cal area network with this multi┆
0x25a0…25c0 63 61 73 74 20 0a 61 64 64 72 65 73 73 20 73 68 6f 75 6c 64 20 62 65 20 72 65 63 65 69 76 65 64 ┆cast address should be received┆
0x25c0…25e0 20 62 79 20 28 74 68 65 20 4d 41 43 20 65 6e 74 69 74 79 20 77 69 74 68 69 6e 29 20 61 20 73 74 ┆ by (the MAC entity within) a st┆
0x25e0…2600 61 74 69 6f 6e 20 69 66 20 61 6e 64 20 0a 6f 6e 6c 79 20 69 66 20 74 68 65 20 73 74 61 74 69 6f ┆ation if and only if the statio┆
0x2600…2620 (19,) 6e 20 69 73 20 61 6e 20 52 43 4c 4c 43 20 73 74 61 74 69 6f 6e 20 63 6f 6e 74 61 69 6e 69 6e 67 ┆n is an RCLLC station containing┆
0x2620…2640 20 61 20 53 41 50 20 62 65 6c 6f 6e 67 69 6e 67 20 74 6f 20 0a 74 68 65 20 63 6c 69 65 6e 74 20 ┆ a SAP belonging to the client ┆
0x2640…2660 6e 65 74 77 6f 72 6b 2e 0d 0a 0d 0a 45 61 63 68 20 53 41 50 20 62 65 6c 6f 6e 67 69 6e 67 20 74 ┆network. Each SAP belonging t┆
0x2660…2680 6f 20 61 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 68 61 73 20 61 6e 20 61 73 73 6f 63 69 ┆o a client network has an associ┆
0x2680…26a0 61 74 65 64 20 a1 53 41 50 20 6d 61 73 6b e1 2e 20 54 68 65 20 0a 53 41 50 20 6d 61 73 6b 20 69 ┆ated SAP mask . The SAP mask i┆
0x26a0…26c0 73 20 61 20 31 36 2d 62 69 74 20 77 6f 72 64 2e 20 54 77 6f 20 53 41 50 20 6d 61 73 6b 73 20 a1 ┆s a 16-bit word. Two SAP masks ┆
0x26c0…26e0 6d 61 74 63 68 e1 20 69 66 20 61 74 20 6c 65 61 73 74 20 6f 6e 65 20 62 69 74 20 0a 70 6f 73 69 ┆match if at least one bit posi┆
0x26e0…2700 74 69 6f 6e 20 63 6f 6e 74 61 69 6e 73 20 61 20 6f 6e 65 20 69 6e 20 62 6f 74 68 20 6d 61 73 6b ┆tion contains a one in both mask┆
0x2700…2720 73 2c 20 69 2e 65 2e 20 69 66 20 61 20 6c 6f 67 69 63 61 6c 20 41 4e 44 2d 6f 70 65 72 61 74 69 ┆s, i.e. if a logical AND-operati┆
0x2720…2740 6f 6e 20 0a 79 69 65 6c 64 73 20 61 20 6e 6f 6e 2d 7a 65 72 6f 20 72 65 73 75 6c 74 2e 20 54 68 ┆on yields a non-zero result. Th┆
0x2740…2760 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 20 77 69 6c 6c 20 6d 61 69 6e 74 61 69 6e 20 63 6f 6e 6e ┆e RCLLC layer will maintain conn┆
0x2760…2780 65 63 74 69 6f 6e 73 20 0a 62 65 74 77 65 65 6e 20 61 6c 6c 20 70 61 69 72 73 20 6f 66 20 53 41 ┆ections between all pairs of SA┆
0x2780…27a0 50 73 20 62 65 6c 6f 6e 67 69 6e 67 20 74 6f 20 74 68 65 20 73 61 6d 65 20 63 6c 69 65 6e 74 20 ┆Ps belonging to the same client ┆
0x27a0…27bd 6e 65 74 77 6f 72 6b 20 77 68 6f 73 65 20 0a 6d 61 73 6b 73 20 6d 61 74 63 68 2e 0d 0a ┆network whose masks match. ┆
0x27bd…27c0 FormFeed {
0x27bd…27c0 0c 82 e8 ┆ ┆
0x27bd…27c0 }
0x27c0…27e0 0a a1 33 2e 20 20 20 20 20 53 45 52 56 49 43 45 20 49 4e 54 45 52 46 41 43 45 53 0d 0a 0d 0a 54 ┆ 3. SERVICE INTERFACES T┆
0x27e0…2800 68 65 20 4d 41 43 20 6c 61 79 65 72 20 69 73 20 74 68 65 20 66 6f 75 6e 64 61 74 69 6f 6e 20 6f ┆he MAC layer is the foundation o┆
0x2800…2820 (20,) 6e 20 77 68 69 63 68 20 74 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 20 69 73 20 62 75 69 6c 74 ┆n which the RCLLC layer is built┆
0x2820…2840 2c 20 61 6e 64 20 0a 69 74 73 20 73 65 72 76 69 63 65 20 69 73 20 74 68 65 72 65 66 6f 72 65 20 ┆, and its service is therefore ┆
0x2840…2860 64 65 73 63 72 69 62 65 64 20 62 72 69 65 66 6c 79 2e 0d 0a 0d 0a 54 68 65 20 64 65 73 63 72 69 ┆described briefly. The descri┆
0x2860…2880 70 74 69 6f 6e 20 6f 66 20 74 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 20 67 6f 65 73 20 69 6e ┆ption of the RCLLC layer goes in┆
0x2880…28a0 74 6f 20 6d 75 63 68 20 6d 6f 72 65 20 64 65 74 61 69 6c 2c 20 62 65 63 61 75 73 65 20 0a 74 68 ┆to much more detail, because th┆
0x28a0…28c0 65 72 65 20 69 73 20 61 20 76 65 72 79 20 64 69 72 65 63 74 20 72 65 6c 61 74 69 6f 6e 73 68 69 ┆ere is a very direct relationshi┆
0x28c0…28e0 70 20 62 65 74 77 65 65 6e 20 74 68 65 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 61 73 20 69 ┆p between the RCLLC service as i┆
0x28e0…2900 74 20 0a 61 70 70 65 61 72 73 20 69 6e 20 74 68 65 20 69 6e 64 69 76 69 64 75 61 6c 20 73 65 72 ┆t appears in the individual ser┆
0x2900…2920 76 69 63 65 20 70 72 69 6d 69 74 69 76 65 73 20 61 6e 64 20 74 68 65 20 65 6c 65 6d 65 6e 74 73 ┆vice primitives and the elements┆
0x2920…2940 20 61 6e 64 20 0a 70 72 6f 63 65 64 75 72 65 73 20 77 68 69 63 68 20 63 6f 6e 73 74 69 74 75 74 ┆ and procedures which constitut┆
0x2940…2960 65 20 74 68 65 20 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c 2e 20 54 68 65 20 64 65 73 63 72 69 ┆e the RCLLC protocol. The descri┆
0x2960…2980 70 74 69 6f 6e 20 6f 66 20 74 68 65 20 0a 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 61 6c 73 6f ┆ption of the RCLLC service also┆
0x2980…29a0 20 66 6f 72 6d 73 20 61 20 70 6f 69 6e 74 20 6f 66 20 72 65 66 65 72 65 6e 63 65 20 66 6f 72 20 ┆ forms a point of reference for ┆
0x29a0…29c0 74 68 65 20 64 65 66 69 6e 69 74 69 6f 6e 20 6f 66 20 0a 70 72 6f 74 6f 63 6f 6c 73 20 66 6f 72 ┆the definition of protocols for┆
0x29c0…29e0 20 73 65 72 76 69 63 65 73 20 74 6f 20 62 65 20 62 75 69 6c 74 20 6f 6e 20 74 6f 70 20 6f 66 20 ┆ services to be built on top of ┆
0x29e0…2a00 74 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 2e 0d 0a 0d 0a 0d 0a a1 33 2e 31 20 20 20 20 4d 41 ┆the RCLLC layer. 3.1 MA┆
0x2a00…2a20 (21,) 43 20 53 65 72 76 69 63 65 73 0d 0a 0d 0a 54 68 65 20 66 75 6e 63 74 69 6f 6e 20 70 65 72 66 6f ┆C Services The function perfo┆
0x2a20…2a40 72 6d 65 64 20 62 79 20 74 68 65 20 4d 41 43 20 6c 61 79 65 72 20 69 73 20 74 6f 20 61 63 63 65 ┆rmed by the MAC layer is to acce┆
0x2a40…2a60 70 74 20 66 72 6f 6d 20 61 6e 20 52 43 4c 4c 43 20 0a 65 6e 74 69 74 79 20 61 20 4d 41 43 20 73 ┆pt from an RCLLC entity a MAC s┆
0x2a60…2a80 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 2c 20 74 6f 20 74 72 61 6e 73 6d 69 74 20 69 74 ┆ervice data unit, to transmit it┆
0x2a80…2aa0 20 74 6f 20 6f 6e 65 2c 20 73 65 76 65 72 61 6c 20 0a 28 6d 75 6c 74 69 63 61 73 74 29 2c 20 6f ┆ to one, several (multicast), o┆
0x2aa0…2ac0 72 20 61 6c 6c 20 73 74 61 74 69 6f 6e 73 20 69 6e 20 74 68 65 20 6e 65 74 77 6f 72 6b 2c 20 61 ┆r all stations in the network, a┆
0x2ac0…2ae0 6e 64 20 69 6e 20 74 68 65 20 72 65 63 65 69 76 69 6e 67 20 0a 73 74 61 74 69 6f 6e 28 73 29 20 ┆nd in the receiving station(s) ┆
0x2ae0…2b00 74 6f 20 64 65 6c 69 76 65 72 20 74 68 65 20 75 6e 69 74 20 74 6f 20 74 68 65 20 64 65 73 74 69 ┆to deliver the unit to the desti┆
0x2b00…2b20 6e 61 74 69 6f 6e 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 28 69 65 73 29 2e 0d 0a 0d 0a 49 6e 20 ┆nation RCLLC entity(ies). In ┆
0x2b20…2b40 74 68 65 20 63 61 73 65 20 6f 66 20 61 20 43 53 4d 41 2f 43 44 20 74 79 70 65 20 6e 65 74 77 6f ┆the case of a CSMA/CD type netwo┆
0x2b40…2b60 72 6b 20 74 68 65 20 4d 41 43 20 73 65 72 76 69 63 65 20 69 6e 63 6c 75 64 65 73 20 72 65 74 72 ┆rk the MAC service includes retr┆
0x2b60…2b80 61 6e 73 80 0a 6d 69 73 73 69 6f 6e 20 66 6f 6c 6c 6f 77 69 6e 67 20 61 20 64 65 74 65 63 74 65 ┆ans mission following a detecte┆
0x2b80…2ba0 64 20 63 6f 6c 6c 69 73 69 6f 6e 2e 0d 0a 0d 0a 54 68 65 72 65 20 69 73 20 6e 6f 20 67 75 61 72 ┆d collision. There is no guar┆
0x2ba0…2bc0 61 6e 74 65 65 20 74 68 61 74 20 61 20 4d 41 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e ┆antee that a MAC service data un┆
0x2bc0…2be0 69 74 20 77 68 69 63 68 20 69 73 20 74 72 61 6e 73 6d 69 74 74 65 64 20 0a 66 72 6f 6d 20 6f 6e ┆it which is transmitted from on┆
0x2be0…2c00 65 20 73 74 61 74 69 6f 6e 20 6f 6e 20 61 20 6e 65 74 77 6f 72 6b 20 69 73 20 72 65 63 65 69 76 ┆e station on a network is receiv┆
0x2c00…2c20 (22,) 65 64 20 61 74 20 74 68 65 20 64 65 73 74 69 6e 61 74 69 6f 6e 20 73 74 61 74 69 6f 6e 28 73 29 ┆ed at the destination station(s)┆
0x2c20…2c40 2e 0d 0a 0d 0a 45 61 63 68 20 4d 41 43 20 65 6e 74 69 74 79 20 69 73 20 73 65 6e 73 69 74 69 76 ┆. Each MAC entity is sensitiv┆
0x2c40…2c60 65 20 74 6f 20 69 74 73 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 20 61 6e 64 20 70 6f 73 ┆e to its station address and pos┆
0x2c60…2c80 73 69 62 6c 79 20 6f 6e 65 20 6f 72 20 0a 6d 6f 72 65 20 6d 75 6c 74 69 63 61 73 74 20 61 64 64 ┆sibly one or more multicast add┆
0x2c80…2ca0 72 65 73 73 65 73 2c 20 69 2e 65 2e 20 61 64 64 72 65 73 73 65 73 20 6f 66 20 67 72 6f 75 70 73 ┆resses, i.e. addresses of groups┆
0x2ca0…2cc0 20 6f 66 20 73 74 61 74 69 6f 6e 73 20 74 6f 20 77 68 69 63 68 20 0a 74 68 65 20 73 74 61 74 69 ┆ of stations to which the stati┆
0x2cc0…2ce0 6f 6e 20 62 65 6c 6f 6e 67 73 2e 20 4f 6e 6c 79 20 4d 41 43 20 73 65 72 76 69 63 65 20 64 61 74 ┆on belongs. Only MAC service dat┆
0x2ce0…2d00 61 20 75 6e 69 74 73 20 74 72 61 6e 73 6d 69 74 74 65 64 20 77 69 74 68 20 6f 6e 65 20 6f 66 20 ┆a units transmitted with one of ┆
0x2d00…2d20 0a 74 68 65 73 65 20 61 64 64 72 65 73 73 65 73 20 6f 72 20 74 68 65 20 62 72 6f 61 64 63 61 73 ┆ these addresses or the broadcas┆
0x2d20…2d40 74 20 61 64 64 72 65 73 73 20 28 69 66 20 61 70 70 6c 69 63 61 62 6c 65 29 20 77 69 6c 6c 20 62 ┆t address (if applicable) will b┆
0x2d40…2d60 65 20 0a 72 65 63 65 69 76 65 64 20 62 79 20 74 68 65 20 4d 41 43 20 65 6e 74 69 74 79 2e 0d 0a ┆e received by the MAC entity. ┆
0x2d60…2d80 0d 0a 50 61 64 64 69 6e 67 20 6f 66 20 66 72 61 6d 65 73 20 63 6f 6e 74 61 69 6e 69 6e 67 20 4d ┆ Padding of frames containing M┆
0x2d80…2da0 41 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 73 20 69 6e 20 6f 72 64 65 72 20 74 ┆AC service data units in order t┆
0x2da0…2dc0 6f 20 72 65 61 63 68 20 61 20 0a 6d 69 6e 69 6d 75 6d 20 73 69 7a 65 20 72 65 71 75 69 72 65 64 ┆o reach a minimum size required┆
0x2dc0…2de0 20 62 79 20 74 68 65 20 74 79 70 65 20 6f 66 20 70 68 79 73 69 63 61 6c 20 6e 65 74 77 6f 72 6b ┆ by the type of physical network┆
0x2de0…2e00 20 69 6e 20 71 75 65 73 74 69 6f 6e 20 69 73 20 0a 70 65 72 66 6f 72 6d 65 64 20 62 79 20 74 68 ┆ in question is performed by th┆
0x2e00…2e20 (23,) 65 20 4d 41 43 20 6c 61 79 65 72 2e 20 54 68 65 20 70 61 64 64 69 6e 67 20 69 73 20 72 65 6d 6f ┆e MAC layer. The padding is remo┆
0x2e20…2e40 76 65 64 20 61 67 61 69 6e 20 62 65 66 6f 72 65 20 0a 64 65 6c 69 76 65 72 79 2e 0d 0a 0d 0a 8c ┆ved again before delivery. ┆
0x2e40…2e60 83 bc 0a 41 20 6e 65 74 77 6f 72 6b 20 64 65 70 65 6e 64 65 6e 74 20 6d 61 78 69 6d 75 6d 20 73 ┆ A network dependent maximum s┆
0x2e60…2e80 69 7a 65 20 66 6f 72 20 4d 41 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 73 20 69 ┆ize for MAC service data units i┆
0x2e80…2ea0 73 20 61 6c 73 6f 20 0a 65 6e 66 6f 72 63 65 64 20 62 79 20 74 68 65 20 4d 41 43 20 6c 61 79 65 ┆s also enforced by the MAC laye┆
0x2ea0…2ec0 72 2c 20 69 2e 65 2e 20 64 61 74 61 20 75 6e 69 74 73 20 65 78 63 65 65 64 69 6e 67 20 74 68 65 ┆r, i.e. data units exceeding the┆
0x2ec0…2ee0 20 6d 61 78 69 6d 75 6d 20 73 69 7a 65 20 0a 77 69 6c 6c 20 6e 6f 74 20 62 65 20 74 72 61 6e 73 ┆ maximum size will not be trans┆
0x2ee0…2f00 6d 69 74 74 65 64 2c 20 61 6e 64 20 74 68 65 20 72 65 63 65 69 76 65 72 20 70 61 72 74 20 6f 66 ┆mitted, and the receiver part of┆
0x2f00…2f20 20 61 20 4d 41 43 20 65 6e 74 69 74 79 20 77 69 6c 6c 20 0a 64 69 73 63 61 72 64 20 61 6c 6c 20 ┆ a MAC entity will discard all ┆
0x2f20…2f40 69 6e 63 6f 6d 69 6e 67 20 66 72 61 6d 65 73 20 74 68 61 74 20 77 6f 75 6c 64 20 79 69 65 6c 64 ┆incoming frames that would yield┆
0x2f40…2f60 20 61 20 64 61 74 61 20 75 6e 69 74 20 6c 6f 6e 67 65 72 20 74 68 61 6e 20 74 68 65 20 0a 6d 61 ┆ a data unit longer than the ma┆
0x2f60…2f80 78 69 6d 75 6d 20 73 69 7a 65 2e 0d 0a 0d 0a 54 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 20 75 ┆ximum size. The RCLLC layer u┆
0x2f80…2fa0 73 65 73 20 74 68 65 20 4d 41 43 20 73 65 72 76 69 63 65 20 62 79 20 74 72 61 6e 73 6d 69 74 74 ┆ses the MAC service by transmitt┆
0x2fa0…2fc0 69 6e 67 20 65 61 63 68 20 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c 20 0a 65 6c 65 6d 65 6e 74 ┆ing each RCLLC protocol element┆
0x2fc0…2fe0 20 61 73 20 61 20 4d 41 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 2e 0d 0a 0d 0a ┆ as a MAC service data unit. ┆
0x2fe0…3000 0d 0a a1 33 2e 32 20 20 20 20 52 43 4c 4c 43 20 53 65 72 76 69 63 65 73 0d 0a 0d 0a 54 68 65 20 ┆ 3.2 RCLLC Services The ┆
0x3000…3020 (24,) 52 43 4c 4c 43 20 73 65 72 76 69 63 65 73 20 61 72 65 20 6f 62 74 61 69 6e 65 64 20 62 79 20 61 ┆RCLLC services are obtained by a┆
0x3020…3040 20 63 6c 69 65 6e 74 20 74 68 72 6f 75 67 68 20 61 6e 20 61 63 74 69 76 65 20 53 41 50 2e 20 41 ┆ client through an active SAP. A┆
0x3040…3060 20 53 41 50 20 0a 63 61 6e 20 62 65 20 75 73 65 64 20 65 69 74 68 65 72 20 66 6f 72 20 74 79 70 ┆ SAP can be used either for typ┆
0x3060…3080 65 20 31 20 73 65 72 76 69 63 65 20 6f 72 20 66 6f 72 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 ┆e 1 service or for client networ┆
0x3080…30a0 6b 20 73 65 72 76 69 63 65 2c 20 62 75 74 20 0a 6e 6f 74 20 66 6f 72 20 62 6f 74 68 2e 20 54 68 ┆k service, but not for both. Th┆
0x30a0…30c0 65 20 6c 6f 6f 70 2d 62 61 63 6b 20 74 65 73 74 20 66 61 63 69 6c 69 74 79 20 69 73 20 61 76 61 ┆e loop-back test facility is ava┆
0x30c0…30e0 69 6c 61 62 6c 65 20 72 65 67 61 72 64 6c 65 73 73 20 6f 66 20 74 68 65 20 0a 63 68 6f 69 63 65 ┆ilable regardless of the choice┆
0x30e0…3100 20 6f 66 20 74 79 70 65 20 31 20 6f 72 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 73 65 72 ┆ of type 1 or client network ser┆
0x3100…3120 76 69 63 65 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 31 20 20 53 41 50 20 41 63 74 69 76 61 74 69 6f ┆vice. 3.2.1 SAP Activatio┆
0x3120…3140 6e 20 61 6e 64 20 44 65 61 63 74 69 76 61 74 69 6f 6e 0d 0a 0d 0a 54 68 65 72 65 20 61 72 65 20 ┆n and Deactivation There are ┆
0x3140…3160 66 6f 75 72 20 70 72 69 6d 69 74 69 76 65 73 20 74 6f 20 72 65 71 75 65 73 74 20 61 63 74 69 76 ┆four primitives to request activ┆
0x3160…3180 61 74 69 6f 6e 20 61 6e 64 20 64 65 61 63 74 69 76 61 74 69 6f 6e 20 6f 66 20 61 20 0a 53 41 50 ┆ation and deactivation of a SAP┆
0x3180…31a0 20 61 6e 64 20 74 6f 20 63 6f 6e 66 69 72 6d 20 74 68 65 20 70 72 6f 63 65 73 73 69 6e 67 20 6f ┆ and to confirm the processing o┆
0x31a0…31c0 66 20 74 68 65 73 65 20 72 65 71 75 65 73 74 73 2e 20 54 68 65 79 20 61 72 65 20 64 65 73 63 72 ┆f these requests. They are descr┆
0x31c0…31e0 69 62 65 64 20 0a 69 6e 20 74 68 65 20 66 6f 6c 6c 6f 77 69 6e 67 20 73 75 62 73 65 63 74 69 6f ┆ibed in the following subsectio┆
0x31e0…3200 6e 73 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 31 2e 31 20 20 41 43 54 49 56 41 54 45 2e 72 65 71 75 ┆ns. 3.2.1.1 ACTIVATE.requ┆
0x3200…3220 (25,) 65 73 74 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 20 77 68 69 63 68 20 72 65 71 75 65 ┆est The primitive which reque┆
0x3220…3240 73 74 73 20 74 68 65 20 61 63 74 69 76 61 74 69 6f 6e 20 6f 66 20 61 20 53 41 50 20 69 73 20 70 ┆sts the activation of a SAP is p┆
0x3240…3260 61 73 73 65 64 20 66 72 6f 6d 20 61 20 0a 63 6c 69 65 6e 74 20 74 6f 20 74 68 65 20 52 43 4c 4c ┆assed from a client to the RCLL┆
0x3260…3280 43 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 e1 3a 0d 0a 0d 0a 6c 5f ┆C entity. Parameters : l_┆
0x3280…32a0 53 41 50 5f 61 64 64 72 09 84 73 70 65 63 69 66 69 65 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 ┆SAP_addr specifies the local SA┆
0x32a0…32c0 50 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 53 41 50 20 74 6f 20 62 65 20 0a 19 93 80 80 ┆P address of the SAP to be ┆
0x32c0…32e0 61 63 74 69 76 61 74 65 64 2e 0d 0a 73 65 72 76 69 63 65 5f 74 79 70 65 09 84 73 70 65 63 69 66 ┆activated. service_type specif┆
0x32e0…3300 69 65 73 20 77 68 65 74 68 65 72 20 74 79 70 65 20 31 20 73 65 72 76 69 63 65 20 6f 72 20 63 6c ┆ies whether type 1 service or cl┆
0x3300…3320 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 0a 19 93 80 80 73 65 72 76 69 63 65 20 69 73 20 72 65 71 ┆ient network service is req┆
0x3320…3340 75 65 73 74 65 64 3b 20 74 68 65 20 66 6f 6c 6c 6f 77 69 6e 67 20 74 77 6f 20 70 61 72 61 6d 65 ┆uested; the following two parame┆
0x3340…3360 74 65 72 73 20 0a 19 93 80 80 61 72 65 20 6f 6e 6c 79 20 70 72 65 73 65 6e 74 20 69 66 20 63 6c ┆ters are only present if cl┆
0x3360…3380 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 73 65 72 76 69 63 65 20 69 73 20 0a 19 93 80 80 72 65 71 ┆ient network service is req┆
0x3380…33a0 75 65 73 74 65 64 2e 0d 0a 8c 83 c8 0a 53 41 50 5f 6d 61 73 6b 09 84 73 70 65 63 69 66 69 65 73 ┆uested. SAP_mask specifies┆
0x33a0…33c0 20 74 68 65 20 53 41 50 20 6d 61 73 6b 20 75 73 65 64 20 74 6f 20 70 72 65 76 65 6e 74 20 65 73 ┆ the SAP mask used to prevent es┆
0x33c0…33e0 74 61 62 6c 69 73 68 6d 65 6e 74 20 0a 19 93 80 80 6f 66 20 75 6e 64 65 73 69 72 65 64 20 63 6f ┆tablishment of undesired co┆
0x33e0…3400 6e 6e 65 63 74 69 6f 6e 73 2c 20 63 66 2e 20 73 65 63 74 69 6f 6e 20 34 2e 0d 0a 63 6c 69 65 6e ┆nnections, cf. section 4. clien┆
0x3400…3420 (26,) 74 5f 69 6e 66 6f 09 84 69 73 20 61 20 64 61 74 61 20 75 6e 69 74 20 77 68 69 63 68 20 69 73 20 ┆t_info is a data unit which is ┆
0x3420…3440 74 72 61 6e 73 6d 69 74 74 65 64 20 61 6e 64 20 70 61 73 73 65 64 20 74 6f 20 74 68 65 20 0a 19 ┆transmitted and passed to the ┆
0x3440…3460 93 80 80 72 65 6d 6f 74 65 20 63 6c 69 65 6e 74 20 69 6e 20 74 68 65 20 43 4f 4e 4e 45 43 54 5f ┆ remote client in the CONNECT_┆
0x3460…3480 69 6e 64 69 63 61 74 69 6f 6e 20 70 72 69 6d 69 74 69 76 65 20 0a 19 93 80 80 77 68 65 6e 65 76 ┆indication primitive whenev┆
0x3480…34a0 65 72 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 69 73 20 65 73 74 61 62 6c 69 73 68 65 64 20 62 ┆er a connection is established b┆
0x34a0…34c0 65 74 77 65 65 6e 20 74 68 65 20 0a 19 93 80 80 61 63 74 69 76 61 74 65 64 20 53 41 50 20 61 6e ┆etween the activated SAP an┆
0x34c0…34e0 64 20 61 20 72 65 6d 6f 74 65 20 53 41 50 2e 0d 0a 0d 0a 0d 0a 0e 0a a1 33 2e 32 2e 31 2e 32 20 ┆d a remote SAP. 3.2.1.2 ┆
0x34e0…3500 20 41 43 54 49 56 41 54 45 2e 63 6f 6e 66 69 72 6d 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 ┆ ACTIVATE.confirm The primiti┆
0x3500…3520 76 65 20 77 68 69 63 68 20 69 73 20 69 73 73 75 65 64 20 69 6e 20 72 65 73 70 6f 6e 73 65 20 74 ┆ve which is issued in response t┆
0x3520…3540 6f 20 61 6e 20 41 43 54 49 56 41 54 45 2e 72 65 71 75 65 73 74 20 0a 70 72 69 6d 69 74 69 76 65 ┆o an ACTIVATE.request primitive┆
0x3540…3560 20 69 73 20 70 61 73 73 65 64 20 66 72 6f 6d 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 ┆ is passed from the RCLLC entity┆
0x3560…3580 20 74 6f 20 74 68 65 20 72 65 71 75 65 73 74 69 6e 67 20 63 6c 69 65 6e 74 2e 0d 0a 0f 0a 0d 0a ┆ to the requesting client. ┆
0x3580…35a0 a1 50 61 72 61 6d 65 74 65 72 73 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 84 69 73 20 ┆ Parameters : l_SAP_addr is ┆
0x35a0…35c0 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 53 41 50 ┆the local SAP address of the SAP┆
0x35c0…35e0 20 69 6e 20 71 75 65 73 74 69 6f 6e 20 61 73 20 0a 19 93 80 80 73 70 65 63 69 66 69 65 64 20 69 ┆ in question as specified i┆
0x35e0…3600 6e 20 74 68 65 20 72 65 71 75 65 73 74 2e 0d 0a 72 65 73 75 6c 74 09 84 69 6e 64 69 63 61 74 65 ┆n the request. result indicate┆
0x3600…3620 (27,) 73 20 77 68 65 74 68 65 72 20 74 68 65 20 53 41 50 20 77 61 73 20 73 75 63 63 65 73 73 66 75 6c ┆s whether the SAP was successful┆
0x3620…3640 6c 79 20 61 63 74 69 76 61 74 65 64 2e 0d 0a 0d 0a 57 68 65 6e 20 61 20 53 41 50 20 68 61 73 20 ┆ly activated. When a SAP has ┆
0x3640…3660 62 65 65 6e 20 61 63 74 69 76 61 74 65 64 20 66 6f 72 20 74 79 70 65 20 31 20 73 65 72 76 69 63 ┆been activated for type 1 servic┆
0x3660…3680 65 20 55 44 41 54 41 2e 72 65 71 75 65 73 74 20 70 72 69 6d 69 80 0a 74 69 76 65 73 20 6d 61 79 ┆e UDATA.request primi tives may┆
0x3680…36a0 20 62 65 20 69 73 73 75 65 64 20 72 65 71 75 65 73 74 69 6e 67 20 74 68 65 20 74 72 61 6e 73 6d ┆ be issued requesting the transm┆
0x36a0…36c0 69 73 73 69 6f 6e 20 6f 66 20 64 61 74 61 2e 0d 0a 0d 0a 57 68 65 6e 20 61 20 53 41 50 20 68 61 ┆ission of data. When a SAP ha┆
0x36c0…36e0 73 20 62 65 65 6e 20 61 63 74 69 76 61 74 65 64 20 66 6f 72 20 63 6c 69 65 6e 74 20 6e 65 74 77 ┆s been activated for client netw┆
0x36e0…3700 6f 72 6b 20 73 65 72 76 69 63 65 2c 20 74 68 65 20 52 43 4c 4c 43 20 0a 6c 61 79 65 72 20 77 69 ┆ork service, the RCLLC layer wi┆
0x3700…3720 6c 6c 20 61 75 74 6f 6d 61 74 69 63 61 6c 6c 79 20 62 65 67 69 6e 20 74 6f 20 65 73 74 61 62 6c ┆ll automatically begin to establ┆
0x3720…3740 69 73 68 20 74 68 65 20 61 70 70 72 6f 70 72 69 61 74 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 73 2e ┆ish the appropriate connections.┆
0x3740…3760 20 0a 41 73 20 65 61 63 68 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 69 73 20 65 73 74 61 62 6c 69 73 ┆ As each connection is establis┆
0x3760…3780 68 65 64 2c 20 74 68 65 20 63 6c 69 65 6e 74 20 77 69 6c 6c 20 62 65 20 69 6e 66 6f 72 6d 65 64 ┆hed, the client will be informed┆
0x3780…37a0 20 62 79 20 6d 65 61 6e 73 20 0a 6f 66 20 61 20 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 61 74 69 ┆ by means of a CONNECT.indicati┆
0x37a0…37c0 6f 6e 20 70 72 69 6d 69 74 69 76 65 20 61 6e 64 20 6d 61 79 20 73 75 62 73 65 71 75 65 6e 74 6c ┆on primitive and may subsequentl┆
0x37c0…37e0 79 20 72 65 71 75 65 73 74 20 74 72 61 6e 73 80 0a 6d 69 73 73 69 6f 6e 20 6f 66 20 64 61 74 61 ┆y request trans mission of data┆
0x37e0…3800 20 62 79 20 69 73 73 75 69 6e 67 20 44 41 54 41 2e 72 65 71 75 65 73 74 20 70 72 69 6d 69 74 69 ┆ by issuing DATA.request primiti┆
0x3800…3820 (28,) 76 65 73 2e 0d 0a 0d 0a 49 6e 20 65 69 74 68 65 72 20 63 61 73 65 2c 20 6f 6e 63 65 20 61 20 53 ┆ves. In either case, once a S┆
0x3820…3840 41 50 20 68 61 73 20 62 65 65 6e 20 61 63 74 69 76 61 74 65 64 2c 20 74 68 65 20 63 6c 69 65 6e ┆AP has been activated, the clien┆
0x3840…3860 74 20 6d 61 79 20 69 73 73 75 65 20 74 68 65 20 0a 54 45 53 54 2e 72 65 71 75 65 73 74 20 70 72 ┆t may issue the TEST.request pr┆
0x3860…3880 69 6d 69 74 69 76 65 20 74 6f 20 72 65 71 75 65 73 74 20 61 20 6c 6f 6f 70 2d 62 61 63 6b 20 74 ┆imitive to request a loop-back t┆
0x3880…38a0 65 73 74 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 31 2e 33 20 20 44 45 41 43 54 49 56 41 54 45 2e 72 ┆est. 3.2.1.3 DEACTIVATE.r┆
0x38a0…38c0 65 71 75 65 73 74 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 20 77 68 69 63 68 20 72 65 ┆equest The primitive which re┆
0x38c0…38e0 71 75 65 73 74 73 20 74 68 65 20 64 65 61 63 74 69 76 61 74 69 6f 6e 20 6f 66 20 61 20 53 41 50 ┆quests the deactivation of a SAP┆
0x38e0…3900 20 69 73 20 70 61 73 73 65 64 20 66 72 6f 6d 20 61 20 0a 63 6c 69 65 6e 74 20 74 6f 20 74 68 65 ┆ is passed from a client to the┆
0x3900…3920 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a 8c 83 bc 0a 0e 0a a1 50 61 72 61 6d 65 74 ┆ RCLLC entity. Paramet┆
0x3920…3940 65 72 73 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 84 73 70 65 63 69 66 69 65 73 20 74 ┆ers : l_SAP_addr specifies t┆
0x3940…3960 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 53 41 50 20 ┆he local SAP address of the SAP ┆
0x3960…3980 74 6f 20 62 65 20 0a 19 93 80 80 64 65 61 63 74 69 76 61 74 65 64 2e 0d 0a 0f 0a 0d 0a 0d 0a a1 ┆to be deactivated. ┆
0x3980…39a0 33 2e 32 2e 31 2e 34 20 20 44 45 41 43 54 49 56 41 54 45 2e 63 6f 6e 66 69 72 6d 0d 0a 0d 0a 54 ┆3.2.1.4 DEACTIVATE.confirm T┆
0x39a0…39c0 68 65 20 70 72 69 6d 69 74 69 76 65 20 77 68 69 63 68 20 69 73 20 69 73 73 75 65 64 20 69 6e 20 ┆he primitive which is issued in ┆
0x39c0…39e0 72 65 73 70 6f 6e 73 65 20 74 6f 20 61 20 44 45 41 43 54 49 56 41 54 45 2e 72 65 71 75 65 73 74 ┆response to a DEACTIVATE.request┆
0x39e0…3a00 20 70 72 69 6d 69 80 0a 74 69 76 65 20 69 73 20 70 61 73 73 65 64 20 66 72 6f 6d 20 74 68 65 20 ┆ primi tive is passed from the ┆
0x3a00…3a20 (29,) 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 74 6f 20 74 68 65 20 72 65 71 75 65 73 74 69 6e 67 20 63 ┆RCLLC entity to the requesting c┆
0x3a20…3a40 6c 69 65 6e 74 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 ┆lient. Parameters : l_SAP┆
0x3a40…3a60 5f 61 64 64 72 09 84 69 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 20 ┆_addr is the local SAP address ┆
0x3a60…3a80 6f 66 20 74 68 65 20 53 41 50 20 69 6e 20 71 75 65 73 74 69 6f 6e 20 61 73 20 0a 19 93 80 80 73 ┆of the SAP in question as s┆
0x3a80…3aa0 70 65 63 69 66 69 65 64 20 69 6e 20 74 68 65 20 72 65 71 75 65 73 74 2e 0d 0a 0d 0a 0d 0a a1 33 ┆pecified in the request. 3┆
0x3aa0…3ac0 2e 32 2e 32 20 20 4c 6f 6f 70 2d 62 61 63 6b 20 54 65 73 74 20 53 65 72 76 69 63 65 0d 0a 0d 0a ┆.2.2 Loop-back Test Service ┆
0x3ac0…3ae0 54 68 65 20 6c 6f 6f 70 2d 62 61 63 6b 20 74 65 73 74 20 66 61 63 69 6c 69 74 79 20 61 6c 6c 6f ┆The loop-back test facility allo┆
0x3ae0…3b00 77 73 20 61 20 63 6c 69 65 6e 74 20 74 6f 20 72 65 71 75 65 73 74 20 61 20 74 65 73 74 20 6f 66 ┆ws a client to request a test of┆
0x3b00…3b20 20 74 68 65 20 0a 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 70 61 74 68 20 62 65 74 77 65 65 6e 20 ┆ the transmission path between ┆
0x3b20…3b40 74 68 65 20 6c 6f 63 61 6c 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 61 6e 64 20 6f 6e 65 20 6f ┆the local RCLLC entity and one o┆
0x3b40…3b60 72 20 6d 6f 72 65 20 72 65 6d 6f 74 65 20 0a 52 43 4c 4c 43 20 65 6e 74 69 74 69 65 73 20 77 69 ┆r more remote RCLLC entities wi┆
0x3b60…3b80 74 68 6f 75 74 20 72 65 71 75 69 72 69 6e 67 20 74 68 65 20 70 61 72 74 69 63 69 70 61 74 69 6f ┆thout requiring the participatio┆
0x3b80…3ba0 6e 20 6f 66 20 61 6e 79 20 72 65 6d 6f 74 65 20 0a 63 6c 69 65 6e 74 28 73 29 2e 20 54 68 69 73 ┆n of any remote client(s). This┆
0x3ba0…3bc0 20 69 73 20 64 6f 6e 65 20 62 79 20 74 72 61 6e 73 6d 69 74 74 69 6e 67 20 61 20 54 45 53 54 20 ┆ is done by transmitting a TEST ┆
0x3bc0…3be0 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 0a 28 63 6f 6d 6d 61 6e 64 29 20 74 6f 20 74 ┆protocol element (command) to t┆
0x3be0…3c00 68 65 20 73 70 65 63 69 66 69 65 64 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 2f 65 6e 74 69 74 69 ┆he specified RCLLC entity/entiti┆
0x3c00…3c20 (30,) 65 73 20 74 6f 20 77 68 69 63 68 20 69 74 2f 65 61 63 68 20 6f 66 20 0a 74 68 65 6d 20 6d 75 73 ┆es to which it/each of them mus┆
0x3c20…3c40 74 20 72 65 73 70 6f 6e 64 20 62 79 20 74 72 61 6e 73 6d 69 74 74 69 6e 67 20 61 20 54 45 53 54 ┆t respond by transmitting a TEST┆
0x3c40…3c60 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 28 72 65 73 70 6f 6e 73 65 29 20 0d 0a 61 ┆ protocol element (response) a┆
0x3c60…3c80 64 64 72 65 73 73 65 64 20 74 6f 20 74 68 65 20 72 65 71 75 65 73 74 69 6e 67 20 63 6c 69 65 6e ┆ddressed to the requesting clien┆
0x3c80…3ca0 74 20 28 53 41 50 29 2e 0d 0a 0d 0a 4e 6f 74 69 63 65 3a 20 4e 6f 20 69 6e 64 69 63 61 74 69 6f ┆t (SAP). Notice: No indicatio┆
0x3ca0…3cc0 6e 20 69 73 20 67 69 76 65 6e 20 69 66 20 74 68 65 20 72 65 73 70 6f 6e 64 69 6e 67 20 70 72 6f ┆n is given if the responding pro┆
0x3cc0…3ce0 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 66 61 69 6c 73 20 0a 74 6f 20 61 72 72 69 76 65 20 66 ┆tocol element fails to arrive f┆
0x3ce0…3d00 72 6f 6d 20 61 6e 79 20 6f 72 20 61 6c 6c 20 6f 66 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 ┆rom any or all of the RCLLC enti┆
0x3d00…3d20 74 69 65 73 20 61 64 64 72 65 73 73 65 64 20 69 6e 20 74 68 65 20 0a 54 45 53 54 2e 72 65 71 75 ┆ties addressed in the TEST.requ┆
0x3d20…3d40 65 73 74 20 70 72 69 6d 69 74 69 76 65 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 32 2e 31 20 20 54 45 ┆est primitive. 3.2.2.1 TE┆
0x3d40…3d60 53 54 2e 72 65 71 75 65 73 74 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 ┆ST.request The primitive, whi┆
0x3d60…3d80 63 68 20 72 65 71 75 65 73 74 73 20 74 68 61 74 20 6f 6e 65 20 6f 72 20 6d 6f 72 65 20 74 72 61 ┆ch requests that one or more tra┆
0x3d80…3da0 6e 73 6d 69 73 73 69 6f 6e 20 70 61 74 68 73 20 62 65 20 0a 74 65 73 74 65 64 2c 20 69 73 20 70 ┆nsmission paths be tested, is p┆
0x3da0…3dc0 61 73 73 65 64 20 66 72 6f 6d 20 61 20 63 6c 69 65 6e 74 20 74 6f 20 74 68 65 20 52 43 4c 4c 43 ┆assed from a client to the RCLLC┆
0x3dc0…3de0 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a 8c 83 bc 0a 0e 0a a1 50 61 72 61 6d 65 74 65 72 73 e1 3a 0d ┆ entity. Parameters : ┆
0x3de0…3e00 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 69 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 ┆ l_SAP_addr is the local SAP a┆
0x3e00…3e20 (31,) 64 64 72 65 73 73 2e 0d 0a 0f 0a 72 65 6d 5f 61 64 64 72 09 84 69 73 20 74 68 65 20 73 74 61 74 ┆ddress. rem_addr is the stat┆
0x3e20…3e40 69 6f 6e 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 72 65 6d 6f 74 65 20 52 43 4c 4c 43 20 ┆ion address of the remote RCLLC ┆
0x3e40…3e60 65 6e 74 69 74 79 3b 20 61 20 20 0a 19 93 80 80 6d 75 6c 74 69 63 61 73 74 20 6f 72 20 62 72 6f ┆entity; a multicast or bro┆
0x3e60…3e80 61 64 63 61 73 74 20 61 64 64 72 65 73 73 20 6d 61 79 20 62 65 20 75 73 65 64 20 69 6e 20 70 6c ┆adcast address may be used in pl┆
0x3e80…3ea0 61 63 65 20 0a 19 93 80 80 6f 66 20 61 20 73 70 65 63 69 66 69 63 20 73 74 61 74 69 6f 6e 20 61 ┆ace of a specific station a┆
0x3ea0…3ec0 64 64 72 65 73 73 20 74 6f 20 72 65 71 75 65 73 74 20 74 65 73 74 69 6e 67 20 6f 66 20 0a 19 93 ┆ddress to request testing of ┆
0x3ec0…3ee0 80 80 6d 75 6c 74 69 70 6c 65 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 70 61 74 68 73 2e 0d 0a ┆ multiple transmission paths. ┆
0x3ee0…3f00 74 64 75 09 09 84 74 65 73 74 20 64 61 74 61 20 75 6e 69 74 2c 20 74 72 61 6e 73 6d 69 74 74 65 ┆tdu test data unit, transmitte┆
0x3f00…3f20 64 20 69 6e 20 74 68 65 20 69 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 0a 19 93 80 80 ┆d in the information field ┆
0x3f20…3f40 6f 66 20 74 68 65 20 65 78 63 68 61 6e 67 65 64 20 70 72 6f 74 6f 63 6c 20 65 6c 65 6d 65 6e 74 ┆of the exchanged protocl element┆
0x3f40…3f60 73 2e 0d 0a 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 32 2e 32 20 20 54 45 53 54 2e 63 6f 6e 66 69 72 6d ┆s. 3.2.2.2 TEST.confirm┆
0x3f60…3f80 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 63 68 20 63 6f 6e 66 69 72 6d ┆ The primitive, which confirm┆
0x3f80…3fa0 73 20 74 68 61 74 20 74 68 65 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 70 61 74 68 20 62 65 74 ┆s that the transmission path bet┆
0x3fa0…3fc0 77 65 65 6e 20 74 68 65 20 0a 6c 6f 63 61 6c 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 61 6e 64 ┆ween the local RCLLC entity and┆
0x3fc0…3fe0 20 6f 6e 65 20 72 65 6d 6f 74 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 68 61 73 20 62 65 65 ┆ one remote RCLLC entity has bee┆
0x3fe0…4000 6e 20 74 65 73 74 65 64 20 61 73 20 0a 72 65 71 75 65 73 74 65 64 20 62 79 20 61 20 70 72 65 76 ┆n tested as requested by a prev┆
0x4000…4020 (32,) 69 6f 75 73 20 54 45 53 54 2e 72 65 71 75 65 73 74 20 70 72 69 6d 69 74 69 76 65 2c 20 69 73 20 ┆ious TEST.request primitive, is ┆
0x4020…4040 70 61 73 73 65 64 20 66 72 6f 6d 20 74 68 65 20 52 43 4c 4c 43 20 0a 65 6e 74 69 74 79 20 74 6f ┆passed from the RCLLC entity to┆
0x4040…4060 20 74 68 65 20 63 6c 69 65 6e 74 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 e1 3a 0d 0a 0d ┆ the client. Parameters : ┆
0x4060…4080 0a 6c 5f 53 41 50 5f 61 64 64 72 09 69 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 ┆ l_SAP_addr is the local SAP add┆
0x4080…40a0 72 65 73 73 2e 0d 0a 72 65 6d 5f 61 64 64 72 09 69 73 20 74 68 65 20 73 74 61 74 69 6f 6e 20 61 ┆ress. rem_addr is the station a┆
0x40a0…40c0 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 72 65 6d 6f 74 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 ┆ddress of the remote RCLLC entit┆
0x40c0…40e0 79 2e 0d 0a 72 65 73 75 6c 74 09 84 69 6e 64 69 63 61 74 65 73 20 68 6f 77 20 74 68 65 20 74 65 ┆y. result indicates how the te┆
0x40e0…4100 73 74 20 77 65 6e 74 2c 20 65 2e 67 2e 20 27 6e 6f 20 70 72 6f 62 6c 65 6d 73 27 2c 20 27 74 6f ┆st went, e.g. 'no problems', 'to┆
0x4100…4120 6f 20 0a 19 93 80 80 6d 61 6e 79 20 63 6f 6c 6c 69 73 69 6f 6e 73 27 2c 20 6f 72 20 27 72 65 63 ┆o many collisions', or 'rec┆
0x4120…4140 65 69 76 65 64 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 77 61 73 20 0a 19 93 80 80 ┆eived protocol element was ┆
0x4140…4160 64 61 6d 61 67 65 64 27 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 32 2e 33 20 20 54 45 53 54 2e 69 6e ┆damaged'. 3.2.2.3 TEST.in┆
0x4160…4180 64 69 63 61 74 69 6f 6e 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 63 68 ┆dication The primitive, which┆
0x4180…41a0 20 69 6e 64 69 63 61 74 65 73 20 74 68 61 74 20 61 20 54 45 53 54 20 70 72 6f 74 6f 63 6f 6c 20 ┆ indicates that a TEST protocol ┆
0x41a0…41c0 65 6c 65 6d 65 6e 74 20 61 64 64 72 65 73 73 65 64 20 74 6f 20 0a 74 68 65 20 6c 6f 63 61 6c 20 ┆element addressed to the local ┆
0x41c0…41e0 53 41 50 20 68 61 73 20 62 65 65 6e 20 72 65 63 65 69 76 65 64 2c 20 69 73 20 70 61 73 73 65 64 ┆SAP has been received, is passed┆
0x41e0…4200 20 66 72 6f 6d 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 74 6f 20 74 68 65 20 0a 63 ┆ from the RCLLC entity to the c┆
0x4200…4220 (33,) 6c 69 65 6e 74 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 e1 3a 0d 0a 0d 0a 64 65 73 74 5f ┆lient. Parameters : dest_┆
0x4220…4240 61 64 64 72 09 84 69 73 20 74 68 65 20 64 65 73 74 69 6e 61 74 69 6f 6e 20 61 64 64 72 65 73 73 ┆addr is the destination address┆
0x4240…4260 20 6f 66 20 74 68 65 20 72 65 63 65 69 76 65 64 20 70 72 6f 74 6f 63 6f 6c 20 0a 19 93 80 80 65 ┆ of the received protocol e┆
0x4260…4280 6c 65 6d 65 6e 74 2c 20 63 6f 6e 73 69 73 74 69 6e 67 20 6f 66 0d 0a 8c 83 c8 0a 09 09 31 29 20 ┆lement, consisting of 1) ┆
0x4280…42a0 84 74 68 65 20 6c 6f 63 61 6c 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 2c 20 6f 72 20 61 ┆ the local station address, or a┆
0x42a0…42c0 20 6d 75 6c 74 69 63 61 73 74 20 61 64 64 72 65 73 73 20 0a 19 96 80 80 74 6f 20 77 68 69 63 68 ┆ multicast address to which┆
0x42c0…42e0 20 74 68 65 20 73 74 61 74 69 6f 6e 20 69 73 20 73 65 6e 73 69 74 69 76 65 2c 20 6f 72 20 74 68 ┆ the station is sensitive, or th┆
0x42e0…4300 65 20 0a 19 96 80 80 62 72 6f 61 64 63 61 73 74 20 61 64 64 72 65 73 73 2c 20 61 6e 64 0d 0a 09 ┆e broadcast address, and ┆
0x4300…4320 09 32 29 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 2e 0d 0a 73 72 63 5f ┆ 2) the local SAP address. src_┆
0x4320…4340 61 64 64 72 09 84 69 73 20 74 68 65 20 63 6f 6d 70 6c 65 74 65 20 61 64 64 72 65 73 73 20 6f 66 ┆addr is the complete address of┆
0x4340…4360 20 74 68 65 20 73 6f 75 72 63 65 20 53 41 50 20 6f 72 20 52 43 4c 4c 43 20 0a 19 93 80 80 65 6e ┆ the source SAP or RCLLC en┆
0x4360…4380 74 69 74 79 2c 20 63 6f 6e 73 69 73 74 69 6e 67 20 6f 66 0d 0a 09 09 31 29 20 73 74 61 74 69 6f ┆tity, consisting of 1) statio┆
0x4380…43a0 6e 20 61 64 64 72 65 73 73 2c 20 61 6e 64 0d 0a 09 09 32 29 20 84 73 6f 75 72 63 65 20 53 41 50 ┆n address, and 2) source SAP┆
0x43a0…43c0 20 61 64 64 72 65 73 73 20 6f 72 20 6e 75 6c 6c 20 61 64 64 72 65 73 73 20 69 6e 64 69 63 61 74 ┆ address or null address indicat┆
0x43c0…43e0 69 6e 67 20 74 68 65 20 0a 19 96 80 80 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 6f 72 ┆ing the protocol element or┆
0x43e0…4400 69 67 69 6e 61 74 65 64 20 66 72 6f 6d 20 74 68 65 20 72 65 6d 6f 74 65 20 52 43 4c 4c 43 20 0a ┆iginated from the remote RCLLC ┆
0x4400…4420 (34,) 19 96 80 80 65 6e 74 69 74 79 2e 0d 0a 0d 0a 4e 6f 74 65 20 74 68 61 74 20 61 20 54 45 53 54 2e ┆ entity. Note that a TEST.┆
0x4420…4440 72 65 71 75 65 73 74 20 70 72 69 6d 69 74 69 76 65 20 69 73 73 75 65 64 20 62 79 20 61 20 63 6c ┆request primitive issued by a cl┆
0x4440…4460 69 65 6e 74 20 69 6e 20 61 6e 20 52 43 4c 4c 43 20 0a 73 74 61 74 69 6f 6e 20 64 6f 65 73 20 6e ┆ient in an RCLLC station does n┆
0x4460…4480 6f 74 20 63 61 75 73 65 20 74 68 69 73 20 70 72 69 6d 69 74 69 76 65 20 74 6f 20 62 65 20 67 65 ┆ot cause this primitive to be ge┆
0x4480…44a0 6e 65 72 61 74 65 64 20 69 6e 20 72 65 6d 6f 74 65 20 52 43 4c 4c 43 20 0a 73 74 61 74 69 6f 6e ┆nerated in remote RCLLC station┆
0x44a0…44c0 28 73 29 2c 20 61 73 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 28 54 45 ┆(s), as the protocol element (TE┆
0x44c0…44e0 53 54 20 63 6f 6d 6d 61 6e 64 29 20 77 68 69 63 68 20 69 73 20 74 72 61 6e 73 6d 69 74 74 65 64 ┆ST command) which is transmitted┆
0x44e0…4500 20 0a 69 6e 20 74 68 69 73 20 63 61 73 65 20 69 73 20 6e 6f 74 20 61 64 64 72 65 73 73 65 64 20 ┆ in this case is not addressed ┆
0x4500…4520 74 6f 20 61 20 53 41 50 2c 20 62 75 74 20 74 6f 20 6f 6e 65 20 6f 72 20 6d 6f 72 65 20 72 65 6d ┆to a SAP, but to one or more rem┆
0x4520…4540 6f 74 65 20 52 43 4c 4c 43 20 0a 65 6e 74 69 74 69 65 73 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 33 ┆ote RCLLC entities. 3.2.3┆
0x4540…4560 20 20 54 79 70 65 20 31 20 53 65 72 76 69 63 65 0d 0a 0d 0a 54 79 70 65 20 31 20 73 65 72 76 69 ┆ Type 1 Service Type 1 servi┆
0x4560…4580 63 65 20 63 6f 6d 70 72 69 73 65 73 20 75 6e 61 63 6b 6e 6f 77 6c 65 64 67 65 64 20 63 6f 6e 6e ┆ce comprises unacknowledged conn┆
0x4580…45a0 65 63 74 69 6f 6e 6c 65 73 73 20 64 61 74 61 20 74 72 61 6e 73 66 65 72 20 0a 62 65 74 77 65 65 ┆ectionless data transfer betwee┆
0x45a0…45c0 6e 20 53 41 50 73 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 33 2e 31 20 20 55 44 41 54 41 2e 72 65 71 ┆n SAPs. 3.2.3.1 UDATA.req┆
0x45c0…45e0 75 65 73 74 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 63 68 20 72 65 71 ┆uest The primitive, which req┆
0x45e0…4600 75 65 73 74 73 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 66 20 61 6e 20 52 43 4c 4c 43 20 73 ┆uests transmission of an RCLLC s┆
0x4600…4620 (35,) 65 72 76 69 63 65 20 64 61 74 61 20 0a 75 6e 69 74 2c 20 69 73 20 70 61 73 73 65 64 20 66 72 6f ┆ervice data unit, is passed fro┆
0x4620…4640 6d 20 61 20 63 6c 69 65 6e 74 20 74 6f 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 2e 0d ┆m a client to the RCLLC entity. ┆
0x4640…4660 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 69 ┆ Parameters : l_SAP_addr i┆
0x4660…4680 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 2e 0d 0a 64 65 73 74 5f 61 ┆s the local SAP address. dest_a┆
0x4680…46a0 64 64 72 09 84 69 73 20 74 68 65 20 63 6f 6d 70 6c 65 74 65 20 61 64 64 72 65 73 73 20 6f 66 20 ┆ddr is the complete address of ┆
0x46a0…46c0 74 68 65 20 64 65 73 74 69 6e 61 74 69 6f 6e 20 53 41 50 28 73 29 2c 20 0a 19 93 80 80 77 68 65 ┆the destination SAP(s), whe┆
0x46c0…46e0 72 65 20 74 68 65 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 20 6d 61 79 20 62 65 20 61 20 ┆re the station address may be a ┆
0x46e0…4700 6d 75 6c 74 69 63 61 73 74 20 61 64 64 72 65 73 73 20 0a 19 93 80 80 6f 72 20 74 68 65 20 62 72 ┆multicast address or the br┆
0x4700…4720 6f 61 64 63 61 73 74 20 61 64 64 72 65 73 73 2e 0d 0a 6c 5f 73 64 75 09 69 73 20 74 68 65 20 73 ┆oadcast address. l_sdu is the s┆
0x4720…4740 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 20 74 6f 20 62 65 20 74 72 61 6e 73 6d 69 74 74 ┆ervice data unit to be transmitt┆
0x4740…4760 65 64 2e 0d 0a 73 65 72 76 69 63 65 5f 63 6c 61 73 73 09 84 73 70 65 63 69 66 69 65 73 20 74 68 ┆ed. service_class specifies th┆
0x4760…4780 65 20 70 72 69 6f 72 69 74 79 20 64 65 73 69 72 65 64 20 66 6f 72 20 74 68 65 20 64 61 74 61 20 ┆e priority desired for the data ┆
0x4780…47a0 75 6e 69 74 20 0a 19 93 80 80 74 72 61 6e 73 66 65 72 3b 20 69 74 73 20 65 66 66 65 63 74 20 69 ┆unit transfer; its effect i┆
0x47a0…47c0 73 20 75 6e 73 70 65 63 69 66 69 65 64 2e 0d 0a 0d 0a 0d 0a 8c 83 e0 0a 0e 0a a1 a1 33 2e 32 2e ┆s unspecified. 3.2.┆
0x47c0…47e0 33 2e 32 20 20 55 44 41 54 41 2e 69 6e 64 69 63 61 74 69 6f 6e 0d 0a 0d 0a 54 68 65 20 70 72 69 ┆3.2 UDATA.indication The pri┆
0x47e0…4800 6d 69 74 69 76 65 2c 20 77 68 69 63 68 20 69 73 20 75 73 65 64 20 74 6f 20 64 65 6c 69 76 65 72 ┆mitive, which is used to deliver┆
0x4800…4820 (36,) 20 61 20 72 65 63 65 69 76 65 64 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 0a ┆ a received RCLLC service data ┆
0x4820…4840 75 6e 69 74 2c 20 69 73 20 70 61 73 73 65 64 20 66 72 6f 6d 20 74 68 65 20 52 43 4c 4c 43 20 65 ┆unit, is passed from the RCLLC e┆
0x4840…4860 6e 74 69 74 79 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 2e 0d 0a 0f 0a 0d 0a a1 50 61 72 61 6d ┆ntity to the client. Param┆
0x4860…4880 65 74 65 72 73 e1 3a 0d 0a 0d 0a 64 65 73 74 5f 61 64 64 72 09 84 69 73 20 74 68 65 20 63 6f 6d ┆eters : dest_addr is the com┆
0x4880…48a0 70 6c 65 74 65 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 64 65 73 74 69 6e 61 74 69 6f 6e ┆plete address of the destination┆
0x48a0…48c0 20 53 41 50 28 73 29 2c 20 0a 19 93 80 80 77 68 65 72 65 20 74 68 65 20 73 74 61 74 69 6f 6e 20 ┆ SAP(s), where the station ┆
0x48c0…48e0 61 64 64 72 65 73 73 20 6d 61 79 20 62 65 20 61 20 6d 75 6c 74 69 63 61 73 74 20 61 64 64 72 65 ┆address may be a multicast addre┆
0x48e0…4900 73 73 20 0a 19 93 80 80 6f 72 20 74 68 65 20 62 72 6f 61 64 63 61 73 74 20 61 64 64 72 65 73 73 ┆ss or the broadcast address┆
0x4900…4920 2e 0d 0a 73 72 63 5f 61 64 64 72 09 69 73 20 74 68 65 20 63 6f 6d 70 6c 65 74 65 20 61 64 64 72 ┆. src_addr is the complete addr┆
0x4920…4940 65 73 73 20 6f 66 20 74 68 65 20 73 6f 75 72 63 65 20 53 41 50 2e 0d 0a 6c 5f 73 64 75 09 69 73 ┆ess of the source SAP. l_sdu is┆
0x4940…4960 20 74 68 65 20 72 65 63 65 69 76 65 64 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 2e ┆ the received service data unit.┆
0x4960…4980 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 34 20 20 43 6c 69 65 6e 74 20 4e 65 74 77 6f 72 6b 20 53 65 72 ┆ 3.2.4 Client Network Ser┆
0x4980…49a0 76 69 63 65 0d 0a 0d 0a 54 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 20 61 75 74 6f 6d 61 74 69 ┆vice The RCLLC layer automati┆
0x49a0…49c0 63 61 6c 6c 79 20 65 73 74 61 62 6c 69 73 68 65 73 20 61 6e 64 20 6d 61 69 6e 74 61 69 6e 73 20 ┆cally establishes and maintains ┆
0x49c0…49e0 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 0a 62 65 74 77 65 65 6e 20 65 61 63 68 20 70 61 69 72 20 ┆a connection between each pair ┆
0x49e0…4a00 6f 66 20 53 41 50 73 20 62 65 6c 6f 6e 67 69 6e 67 20 74 6f 20 74 68 65 20 73 61 6d 65 20 63 6c ┆of SAPs belonging to the same cl┆
0x4a00…4a20 (37,) 69 65 6e 74 20 6e 65 74 77 6f 72 6b 2c 20 65 78 63 65 70 74 20 0a 77 68 65 6e 20 74 68 65 20 63 ┆ient network, except when the c┆
0x4a20…4a40 6f 6e 6e 65 63 74 69 6f 6e 20 69 73 20 65 78 63 6c 75 64 65 64 20 62 65 63 61 75 73 65 20 74 68 ┆onnection is excluded because th┆
0x4a40…4a60 65 20 53 41 50 20 6d 61 73 6b 73 20 64 6f 20 6e 6f 74 20 6d 61 74 63 68 2e 0d 0a 0d 0a 57 68 65 ┆e SAP masks do not match. Whe┆
0x4a60…4a80 6e 20 61 20 53 41 50 20 69 73 20 61 63 74 69 76 61 74 65 64 2c 20 63 6f 6e 6e 65 63 74 69 6f 6e ┆n a SAP is activated, connection┆
0x4a80…4aa0 73 20 77 69 6c 6c 20 62 65 20 65 73 74 61 62 6c 69 73 68 65 64 20 74 6f 20 74 68 6f 73 65 20 72 ┆s will be established to those r┆
0x4aa0…4ac0 65 6d 6f 74 65 20 0a 53 41 50 73 20 77 68 69 63 68 20 77 65 72 65 20 61 6c 72 65 61 64 79 20 61 ┆emote SAPs which were already a┆
0x4ac0…4ae0 63 74 69 76 65 2e 20 54 68 65 20 28 6c 6f 63 61 6c 29 20 63 6c 69 65 6e 74 20 77 69 6c 6c 20 72 ┆ctive. The (local) client will r┆
0x4ae0…4b00 65 63 65 69 76 65 20 61 20 0a 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 61 74 69 6f 6e 20 70 72 69 ┆eceive a CONNECT.indication pri┆
0x4b00…4b20 6d 69 74 69 76 65 20 66 6f 72 20 65 61 63 68 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 77 68 65 6e 20 ┆mitive for each connection when ┆
0x4b20…4b40 69 74 20 68 61 73 20 62 65 65 6e 20 0a 65 73 74 61 62 6c 69 73 68 65 64 2e 20 53 69 6d 69 6c 61 ┆it has been established. Simila┆
0x4b40…4b60 72 6c 79 20 74 68 65 20 72 65 6d 6f 74 65 20 63 6c 69 65 6e 74 73 20 77 69 6c 6c 20 65 61 63 68 ┆rly the remote clients will each┆
0x4b60…4b80 20 72 65 63 65 69 76 65 20 61 20 0a 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 61 74 69 6f 6e 20 70 ┆ receive a CONNECT.indication p┆
0x4b80…4ba0 72 69 6d 69 74 69 76 65 2e 0d 0a 0d 0a 57 68 65 6e 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 68 ┆rimitive. When a connection h┆
0x4ba0…4bc0 61 73 20 62 65 65 6e 20 65 73 74 61 62 6c 69 73 68 65 64 2c 20 62 6f 74 68 20 63 6c 69 65 6e 74 ┆as been established, both client┆
0x4bc0…4be0 73 20 6d 61 79 20 72 65 71 75 65 73 74 20 74 68 65 20 0a 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 ┆s may request the transmission ┆
0x4be0…4c00 6f 66 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 73 20 62 79 20 69 ┆of RCLLC service data units by i┆
0x4c00…4c20 (38,) 73 73 75 69 6e 67 20 44 41 54 41 2e 72 65 71 75 65 73 74 20 0a 70 72 69 6d 69 74 69 76 65 73 2e ┆ssuing DATA.request primitives.┆
0x4c20…4c40 20 41 20 72 65 63 65 69 76 65 64 20 64 61 74 61 20 75 6e 69 74 20 69 73 20 70 61 73 73 65 64 20 ┆ A received data unit is passed ┆
0x4c40…4c60 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 20 61 74 20 74 68 65 20 0a 64 65 73 74 69 6e 61 74 69 6f ┆to the client at the destinatio┆
0x4c60…4c80 6e 20 53 41 50 20 62 79 20 6d 65 61 6e 73 20 6f 66 20 61 20 44 41 54 41 2e 69 6e 64 69 63 61 74 ┆n SAP by means of a DATA.indicat┆
0x4c80…4ca0 69 6f 6e 20 70 72 69 6d 69 74 69 76 65 2e 0d 0a 0d 0a 54 68 65 20 6f 72 64 65 72 20 69 6e 20 77 ┆ion primitive. The order in w┆
0x4ca0…4cc0 68 69 63 68 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 73 20 61 72 ┆hich RCLLC service data units ar┆
0x4cc0…4ce0 65 20 70 61 73 73 65 64 20 74 6f 20 74 68 65 20 52 43 4c 4c 43 20 0a 6c 61 79 65 72 20 66 6f 72 ┆e passed to the RCLLC layer for┆
0x4ce0…4d00 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 6e 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 69 73 ┆ transmission on a connection is┆
0x4d00…4d20 20 70 72 65 73 65 72 76 65 64 20 74 6f 20 74 68 65 20 70 6f 69 6e 74 20 6f 66 20 0a 64 65 6c 69 ┆ preserved to the point of deli┆
0x4d20…4d40 76 65 72 79 2e 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 73 20 61 ┆very. RCLLC service data units a┆
0x4d40…4d60 72 65 20 64 65 6c 69 76 65 72 65 64 20 66 72 65 65 20 6f 66 20 74 72 61 6e 73 6d 69 73 73 69 6f ┆re delivered free of transmissio┆
0x4d60…4d80 6e 20 0a 65 72 72 6f 72 73 2e 0d 0a 0d 0a 57 68 65 6e 20 61 20 53 41 50 20 69 73 20 64 65 61 63 ┆n errors. When a SAP is deac┆
0x4d80…4da0 74 69 76 61 74 65 64 2c 20 65 69 74 68 65 72 20 62 65 63 61 75 73 65 20 6f 66 20 61 20 72 65 71 ┆tivated, either because of a req┆
0x4da0…4dc0 75 65 73 74 20 6f 72 20 62 65 63 61 75 73 65 20 74 68 65 20 0a 73 74 61 74 69 6f 6e 20 69 6e 20 ┆uest or because the station in ┆
0x4dc0…4de0 77 68 69 63 68 20 69 74 20 65 78 69 73 74 73 20 63 65 61 73 65 73 20 74 6f 20 6f 70 65 72 61 74 ┆which it exists ceases to operat┆
0x4de0…4e00 65 20 6f 72 20 69 73 20 72 65 69 6e 69 74 69 61 6c 69 7a 65 64 2c 20 74 68 65 20 0a 8c 83 c8 0a ┆e or is reinitialized, the ┆
0x4e00…4e20 (39,) 52 43 4c 4c 43 20 6c 61 79 65 72 20 77 69 6c 6c 20 64 65 74 65 63 74 20 74 68 65 20 65 76 65 6e ┆RCLLC layer will detect the even┆
0x4e20…4e40 74 20 61 6e 64 20 72 65 6d 6f 76 65 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 73 20 69 6e 20 ┆t and remove the connections in ┆
0x4e40…4e60 77 68 69 63 68 20 0a 74 68 65 20 53 41 50 20 74 6f 6f 6b 20 70 61 72 74 2e 20 45 61 63 68 20 6f ┆which the SAP took part. Each o┆
0x4e60…4e80 66 20 74 68 65 20 63 6c 69 65 6e 74 73 20 61 74 20 74 68 65 20 72 65 6d 6f 74 65 20 65 6e 64 20 ┆f the clients at the remote end ┆
0x4e80…4ea0 6f 66 20 73 75 63 68 20 61 20 0a 63 6f 6e 6e 65 63 74 69 6f 6e 20 77 69 6c 6c 20 62 65 20 6e 6f ┆of such a connection will be no┆
0x4ea0…4ec0 74 69 66 69 65 64 20 62 79 20 6d 65 61 6e 73 20 6f 66 20 61 20 44 49 53 43 4f 4e 4e 45 43 54 2e ┆tified by means of a DISCONNECT.┆
0x4ec0…4ee0 69 6e 64 69 63 61 74 69 6f 6e 20 0a 70 72 69 6d 69 74 69 76 65 2e 0d 0a 0d 0a 54 68 65 72 65 20 ┆indication primitive. There ┆
0x4ee0…4f00 69 73 20 6e 6f 20 67 75 61 72 61 6e 74 65 65 20 74 68 61 74 20 61 6c 6c 20 73 65 72 76 69 63 65 ┆is no guarantee that all service┆
0x4f00…4f20 20 64 61 74 61 20 75 6e 69 74 73 20 70 61 73 73 65 64 20 74 6f 20 74 68 65 20 52 43 4c 4c 43 20 ┆ data units passed to the RCLLC ┆
0x4f20…4f40 0a 6c 61 79 65 72 20 66 6f 72 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 77 69 6c 6c 20 68 61 76 ┆ layer for transmission will hav┆
0x4f40…4f60 65 20 62 65 65 6e 20 64 65 6c 69 76 65 72 65 64 20 62 65 66 6f 72 65 20 61 20 63 6f 6e 6e 65 63 ┆e been delivered before a connec┆
0x4f60…4f80 74 69 6f 6e 20 69 73 20 0a 72 65 6d 6f 76 65 64 2e 0d 0a 0d 0a 57 68 65 6e 20 61 6e 20 52 43 4c ┆tion is removed. When an RCL┆
0x4f80…4fa0 4c 43 20 65 6e 74 69 74 79 20 68 61 73 20 72 65 6d 6f 76 65 64 20 28 6f 6e 65 20 65 6e 64 2d 70 ┆LC entity has removed (one end-p┆
0x4fa0…4fc0 6f 69 6e 74 20 6f 66 29 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 61 6e 64 20 0a 70 61 73 73 65 ┆oint of) a connection and passe┆
0x4fc0…4fe0 64 20 74 68 65 20 69 6e 64 69 63 61 74 69 6f 6e 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 20 69 ┆d the indication to the client i┆
0x4fe0…5000 74 20 77 69 6c 6c 20 6e 6f 74 20 65 73 74 61 62 6c 69 73 68 20 61 20 6e 65 77 20 0a 63 6f 6e 6e ┆t will not establish a new conn┆
0x5000…5020 (40,) 65 63 74 69 6f 6e 20 74 6f 20 74 68 65 20 73 61 6d 65 20 72 65 6d 6f 74 65 20 53 41 50 20 75 6e ┆ection to the same remote SAP un┆
0x5020…5040 74 69 6c 20 74 68 65 20 63 6c 69 65 6e 74 20 68 61 73 20 61 63 6b 6e 6f 77 6c 65 64 67 65 64 20 ┆til the client has acknowledged ┆
0x5040…5060 74 68 65 20 0a 72 65 6d 6f 76 61 6c 20 6f 66 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 62 ┆the removal of the connection b┆
0x5060…5080 79 20 69 73 73 75 69 6e 67 20 61 20 44 49 53 43 4f 4e 4e 45 43 54 2e 61 63 6b 6e 6f 77 6c 65 64 ┆y issuing a DISCONNECT.acknowled┆
0x5080…50a0 67 65 20 70 72 69 6d 69 74 69 76 65 2e 20 0a 54 68 69 73 20 70 72 6f 63 65 64 75 72 65 20 69 73 ┆ge primitive. This procedure is┆
0x50a0…50c0 20 73 69 67 6e 69 66 69 63 61 6e 74 20 77 68 65 6e 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 69 ┆ significant when a connection i┆
0x50c0…50e0 73 20 72 65 6d 6f 76 65 64 20 62 65 63 61 75 73 65 20 6f 66 20 61 20 0a 74 65 6d 70 6f 72 61 72 ┆s removed because of a temporar┆
0x50e0…5100 79 20 6d 61 6c 66 75 6e 63 74 69 6f 6e 20 6f 72 20 74 68 65 20 72 65 69 6e 69 74 69 61 6c 69 7a ┆y malfunction or the reinitializ┆
0x5100…5120 61 74 69 6f 6e 20 6f 66 20 61 20 73 74 61 74 69 6f 6e 2e 20 49 74 20 61 6c 6c 6f 77 73 20 0a 74 ┆ation of a station. It allows t┆
0x5120…5140 68 65 20 63 6c 69 65 6e 74 20 74 6f 20 67 72 61 63 65 66 75 6c 6c 79 20 74 65 72 6d 69 6e 61 74 ┆he client to gracefully terminat┆
0x5140…5160 65 20 61 6e 79 20 61 63 74 69 76 69 74 79 20 61 73 73 6f 63 69 61 74 65 64 20 77 69 74 68 20 74 ┆e any activity associated with t┆
0x5160…5180 68 65 20 0a 63 6f 6e 6e 65 63 74 69 6f 6e 20 62 65 66 6f 72 65 20 69 74 20 69 73 20 72 65 65 73 ┆he connection before it is rees┆
0x5180…51a0 74 61 62 6c 69 73 68 65 64 2e 0d 0a 0d 0a 44 65 74 61 69 6c 73 20 61 62 6f 75 74 20 74 68 65 20 ┆tablished. Details about the ┆
0x51a0…51c0 73 69 78 20 70 72 69 6d 69 74 69 76 65 73 20 75 73 65 64 20 69 6e 20 63 6f 6e 6a 75 6e 63 74 69 ┆six primitives used in conjuncti┆
0x51c0…51e0 6f 6e 20 77 69 74 68 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 0a 73 65 72 76 69 63 65 20 ┆on with client network service ┆
0x51e0…5200 61 72 65 20 67 69 76 65 6e 20 69 6e 20 74 68 65 20 66 6f 6c 6c 6f 77 69 6e 67 20 73 75 62 73 65 ┆are given in the following subse┆
0x5200…5220 (41,) 63 74 69 6f 6e 73 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 34 2e 31 20 20 43 4f 4e 4e 45 43 54 2e 69 ┆ctions. 3.2.4.1 CONNECT.i┆
0x5220…5240 6e 64 69 63 61 74 69 6f 6e 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 63 ┆ndication The primitive, whic┆
0x5240…5260 68 20 69 6e 64 69 63 61 74 65 73 20 74 68 61 74 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 68 61 ┆h indicates that a connection ha┆
0x5260…5280 73 20 62 65 65 6e 20 65 73 74 61 62 6c 69 73 68 65 64 2c 20 0a 69 73 20 70 61 73 73 65 64 20 66 ┆s been established, is passed f┆
0x5280…52a0 72 6f 6d 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 74 6f 20 74 68 65 20 63 6c 69 65 ┆rom the RCLLC entity to the clie┆
0x52a0…52c0 6e 74 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 ┆nt. Parameters : l_SAP_ad┆
0x52c0…52e0 64 72 09 84 69 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 2c 20 69 2e ┆dr is the local SAP address, i.┆
0x52e0…5300 65 2e 20 74 68 65 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 0a 19 93 80 80 6e 75 6d 62 65 ┆e. the client network numbe┆
0x5300…5320 72 2e 0d 0a 72 65 6d 5f 61 64 64 72 09 69 73 20 74 68 65 20 73 74 61 74 69 6f 6e 20 61 64 64 72 ┆r. rem_addr is the station addr┆
0x5320…5340 65 73 73 20 6f 66 20 74 68 65 20 72 65 6d 6f 74 65 20 53 41 50 2e 0d 0a 63 6c 69 65 6e 74 5f 69 ┆ess of the remote SAP. client_i┆
0x5340…5360 6e 66 6f 09 84 69 73 20 74 68 65 20 64 61 74 61 20 75 6e 69 74 20 70 61 73 73 65 64 20 74 6f 20 ┆nfo is the data unit passed to ┆
0x5360…5380 74 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 20 77 68 65 6e 20 74 68 65 20 0a 19 93 80 80 72 65 ┆the RCLLC layer when the re┆
0x5380…53a0 6d 6f 74 65 20 53 41 50 20 77 61 73 20 61 63 74 69 76 61 74 65 64 2e 0d 0a 0d 0a 41 66 74 65 72 ┆mote SAP was activated. After┆
0x53a0…53c0 20 72 65 63 65 69 76 69 6e 67 20 74 68 65 20 70 72 69 6d 69 74 69 76 65 20 74 68 65 20 63 6c 69 ┆ receiving the primitive the cli┆
0x53c0…53e0 65 6e 74 20 6d 61 79 20 69 73 73 75 65 20 44 41 54 41 2e 72 65 71 75 65 73 74 20 0a 70 72 69 6d ┆ent may issue DATA.request prim┆
0x53e0…5400 69 74 69 76 65 73 20 6f 6e 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 2c 20 61 6e 64 20 73 68 ┆itives on the connection, and sh┆
0x5400…5420 (42,) 6f 75 6c 64 20 65 78 70 65 63 74 20 44 41 54 41 2e 69 6e 64 69 63 61 74 69 6f 6e 20 0a 70 72 69 ┆ould expect DATA.indication pri┆
0x5420…5440 6d 69 74 69 76 65 73 20 74 6f 20 61 72 72 69 76 65 2e 0d 0a 0d 0a 0d 0a 8c 83 e0 0a a1 33 2e 32 ┆mitives to arrive. 3.2┆
0x5440…5460 2e 34 2e 32 20 20 44 49 53 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 61 74 69 6f 6e 0d 0a 0d 0a 54 ┆.4.2 DISCONNECT.indication T┆
0x5460…5480 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 63 68 20 69 6e 64 69 63 61 74 65 73 20 74 68 ┆he primitive, which indicates th┆
0x5480…54a0 61 74 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 68 61 73 20 62 65 65 6e 20 72 65 6d 6f 76 65 64 ┆at a connection has been removed┆
0x54a0…54c0 2c 20 69 73 20 0a 70 61 73 73 65 64 20 66 72 6f 6d 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 ┆, is passed from the RCLLC enti┆
0x54c0…54e0 74 79 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 ┆ty to the client. Parameters┆
0x54e0…5500 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 84 69 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 ┆ : l_SAP_addr is the local S┆
0x5500…5520 41 50 20 61 64 64 72 65 73 73 2c 20 69 2e 65 2e 20 74 68 65 20 63 6c 69 65 6e 74 20 6e 65 74 77 ┆AP address, i.e. the client netw┆
0x5520…5540 6f 72 6b 20 0a 19 93 80 80 6e 75 6d 62 65 72 2e 0d 0a 72 65 6d 5f 61 64 64 72 09 69 73 20 74 68 ┆ork number. rem_addr is th┆
0x5540…5560 65 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 72 65 6d 6f 74 65 20 ┆e station address of the remote ┆
0x5560…5580 53 41 50 2e 0d 0a 72 65 61 73 6f 6e 09 73 70 65 63 69 66 69 65 73 20 77 68 79 20 74 68 65 20 63 ┆SAP. reason specifies why the c┆
0x5580…55a0 6f 6e 6e 65 63 74 69 6f 6e 20 77 61 73 20 72 65 6d 6f 76 65 64 2e 0d 0a 0d 0a 54 68 65 20 63 6c ┆onnection was removed. The cl┆
0x55a0…55c0 69 65 6e 74 20 73 68 6f 75 6c 64 20 61 63 6b 6e 6f 77 6c 65 64 67 65 20 72 65 63 65 69 70 74 20 ┆ient should acknowledge receipt ┆
0x55c0…55e0 6f 66 20 74 68 65 20 70 72 69 6d 69 74 69 76 65 20 62 79 20 69 73 73 75 69 6e 67 20 61 20 0a 44 ┆of the primitive by issuing a D┆
0x55e0…5600 49 53 43 4f 4e 4e 45 43 54 2e 61 63 6b 6e 6f 77 6c 65 64 67 65 20 70 72 69 6d 69 74 69 76 65 2e ┆ISCONNECT.acknowledge primitive.┆
0x5600…5620 (43,) 20 41 20 6e 65 77 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 74 6f 20 74 68 65 20 73 61 6d 65 20 72 65 ┆ A new connection to the same re┆
0x5620…5640 6d 6f 74 65 20 0a 53 41 50 20 77 69 6c 6c 20 6e 6f 74 20 62 65 20 65 73 74 61 62 6c 69 73 68 65 ┆mote SAP will not be establishe┆
0x5640…5660 64 20 75 6e 74 69 6c 20 74 68 69 73 20 68 61 73 20 62 65 65 6e 20 64 6f 6e 65 2e 0d 0a 0d 0a 0d ┆d until this has been done. ┆
0x5660…5680 0a a1 33 2e 32 2e 34 2e 33 20 20 44 49 53 43 4f 4e 4e 45 43 54 2e 61 63 6b 6e 6f 77 6c 65 64 67 ┆ 3.2.4.3 DISCONNECT.acknowledg┆
0x5680…56a0 65 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 63 68 20 61 63 6b 6e 6f 77 ┆e The primitive, which acknow┆
0x56a0…56c0 6c 65 64 67 65 73 20 74 68 65 20 72 65 6d 6f 76 61 6c 20 6f 66 20 61 20 63 6f 6e 6e 65 63 74 69 ┆ledges the removal of a connecti┆
0x56c0…56e0 6f 6e 2c 20 69 73 20 70 61 73 73 65 64 20 0a 66 72 6f 6d 20 61 20 63 6c 69 65 6e 74 20 74 6f 20 ┆on, is passed from a client to ┆
0x56e0…5700 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 ┆the RCLLC entity. Parameters┆
0x5700…5720 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 84 69 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 ┆ : l_SAP_addr is the local S┆
0x5720…5740 41 50 20 61 64 64 72 65 73 73 2c 20 69 2e 65 2e 20 74 68 65 20 63 6c 69 65 6e 74 20 6e 65 74 77 ┆AP address, i.e. the client netw┆
0x5740…5760 6f 72 6b 20 0a 19 93 80 80 6e 75 6d 62 65 72 2e 0d 0a 72 65 6d 5f 61 64 64 72 09 69 73 20 74 68 ┆ork number. rem_addr is th┆
0x5760…5780 65 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 72 65 6d 6f 74 65 20 ┆e station address of the remote ┆
0x5780…57a0 53 41 50 2e 0d 0a 0d 0a 41 66 74 65 72 20 72 65 63 65 69 76 69 6e 67 20 74 68 65 20 70 72 69 6d ┆SAP. After receiving the prim┆
0x57a0…57c0 69 74 69 76 65 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 6d 61 79 20 65 73 74 61 62 ┆itive the RCLLC entity may estab┆
0x57c0…57e0 6c 69 73 68 20 61 20 6e 65 77 20 0a 63 6f 6e 6e 65 63 74 69 6f 6e 20 74 6f 20 74 68 65 20 73 61 ┆lish a new connection to the sa┆
0x57e0…5800 6d 65 20 72 65 6d 6f 74 65 20 53 41 50 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 34 2e 34 20 20 44 41 ┆me remote SAP. 3.2.4.4 DA┆
0x5800…5820 (44,) 54 41 2e 72 65 71 75 65 73 74 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 ┆TA.request The primitive, whi┆
0x5820…5840 63 68 20 72 65 71 75 65 73 74 73 20 74 68 61 74 20 61 6e 20 52 43 4c 4c 43 20 73 65 72 76 69 63 ┆ch requests that an RCLLC servic┆
0x5840…5860 65 20 75 6e 69 74 20 62 65 20 74 72 61 6e 73 6d 69 74 74 65 64 20 0a 6f 6e 20 61 20 63 6f 6e 6e ┆e unit be transmitted on a conn┆
0x5860…5880 65 63 74 69 6f 6e 2c 20 69 73 20 70 61 73 73 65 64 20 66 72 6f 6d 20 61 20 63 6c 69 65 6e 74 20 ┆ection, is passed from a client ┆
0x5880…58a0 74 6f 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a 8c 83 bc 0a 0e 0a a1 50 ┆to the RCLLC entity. P┆
0x58a0…58c0 61 72 61 6d 65 74 65 72 73 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 84 69 73 20 74 68 ┆arameters : l_SAP_addr is th┆
0x58c0…58e0 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 64 72 65 73 73 2c 20 69 2e 65 2e 20 74 68 65 20 63 6c ┆e local SAP address, i.e. the cl┆
0x58e0…5900 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 0a 19 93 80 80 6e 75 6d 62 65 72 2e 0d 0a 0f 0a 64 65 73 ┆ient network number. des┆
0x5900…5920 74 5f 61 64 64 72 09 69 73 20 74 68 65 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 20 6f 66 ┆t_addr is the station address of┆
0x5920…5940 20 74 68 65 20 72 65 6d 6f 74 65 20 53 41 50 2e 0d 0a 6c 5f 73 64 75 09 69 73 20 74 68 65 20 73 ┆ the remote SAP. l_sdu is the s┆
0x5940…5960 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 20 74 6f 20 62 65 20 74 72 61 6e 73 6d 69 74 74 ┆ervice data unit to be transmitt┆
0x5960…5980 65 64 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 34 2e 35 20 20 44 41 54 41 2e 63 6f 6e 66 69 72 6d 0d ┆ed. 3.2.4.5 DATA.confirm ┆
0x5980…59a0 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 63 68 20 69 6e 64 69 63 61 74 65 ┆ The primitive, which indicate┆
0x59a0…59c0 73 20 74 68 61 74 20 61 6e 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 ┆s that an RCLLC service data uni┆
0x59c0…59e0 74 20 0a 70 72 65 76 69 6f 75 73 6c 79 20 70 61 73 73 65 64 20 69 6e 20 61 20 44 41 54 41 2e 72 ┆t previously passed in a DATA.r┆
0x59e0…5a00 65 71 75 65 73 74 20 70 72 69 6d 69 74 69 76 65 20 68 61 73 20 62 65 65 6e 20 74 72 61 6e 73 6d ┆equest primitive has been transm┆
0x5a00…5a20 (45,) 69 74 74 65 64 20 6f 6e 20 61 20 0a 63 6f 6e 6e 65 63 74 69 6f 6e 2c 20 69 73 20 70 61 73 73 65 ┆itted on a connection, is passe┆
0x5a20…5a40 64 20 66 72 6f 6d 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 74 6f 20 74 68 65 20 72 ┆d from the RCLLC entity to the r┆
0x5a40…5a60 65 71 75 65 73 74 69 6e 67 20 63 6c 69 65 6e 74 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 ┆equesting client. Parameters┆
0x5a60…5a80 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 84 69 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 ┆ : l_SAP_addr is the local S┆
0x5a80…5aa0 41 50 20 61 64 64 72 65 73 73 2c 20 69 2e 65 2e 20 74 68 65 20 63 6c 69 65 6e 74 20 6e 65 74 77 ┆AP address, i.e. the client netw┆
0x5aa0…5ac0 6f 72 6b 20 0a 19 93 80 80 6e 75 6d 62 65 72 2e 0d 0a 64 65 73 74 5f 61 64 64 72 09 69 73 20 74 ┆ork number. dest_addr is t┆
0x5ac0…5ae0 68 65 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 72 65 6d 6f 74 65 ┆he station address of the remote┆
0x5ae0…5b00 20 53 41 50 2e 0d 0a 72 65 73 75 6c 74 09 84 69 6e 64 69 63 61 74 65 73 20 68 6f 77 20 74 68 65 ┆ SAP. result indicates how the┆
0x5b00…5b20 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 77 65 6e 74 2c 20 65 2e 67 2e 20 27 6e 6f 20 0a 19 93 ┆ transmission went, e.g. 'no ┆
0x5b20…5b40 80 80 70 72 6f 62 6c 65 6d 73 27 20 6f 72 20 27 74 6f 6f 20 6d 61 6e 79 20 63 6f 6c 6c 69 73 69 ┆ problems' or 'too many collisi┆
0x5b40…5b60 6f 6e 73 27 2e 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 20 6d 61 79 20 63 6f 6e 66 69 ┆ons'. The primitive may confi┆
0x5b60…5b80 72 6d 20 74 68 61 74 20 74 68 65 20 64 61 74 61 20 75 6e 69 74 20 68 61 73 20 62 65 65 6e 20 74 ┆rm that the data unit has been t┆
0x5b80…5ba0 72 61 6e 73 6d 69 74 74 65 64 20 61 6e 64 20 0a 61 63 6b 6e 6f 77 6c 65 64 67 65 64 2c 20 62 75 ┆ransmitted and acknowledged, bu┆
0x5ba0…5bc0 74 20 6e 6f 74 20 74 68 61 74 20 69 74 20 68 61 73 20 62 65 65 6e 20 64 65 6c 69 76 65 72 65 64 ┆t not that it has been delivered┆
0x5bc0…5be0 20 74 6f 20 61 6e 64 20 72 65 63 65 69 76 65 64 20 62 79 20 74 68 65 20 0a 72 65 6d 6f 74 65 20 ┆ to and received by the remote ┆
0x5be0…5c00 63 6c 69 65 6e 74 2e 0d 0a 0d 0a 0d 0a a1 33 2e 32 2e 34 2e 36 20 20 44 41 54 41 2e 69 6e 64 69 ┆client. 3.2.4.6 DATA.indi┆
0x5c00…5c20 (46,) 63 61 74 69 6f 6e 0d 0a 0d 0a 54 68 65 20 70 72 69 6d 69 74 69 76 65 2c 20 77 68 69 63 68 20 69 ┆cation The primitive, which i┆
0x5c20…5c40 73 20 75 73 65 64 20 74 6f 20 64 65 6c 69 76 65 72 20 61 6e 20 52 43 4c 4c 43 20 73 65 72 76 69 ┆s used to deliver an RCLLC servi┆
0x5c40…5c60 63 65 20 75 6e 69 74 20 72 65 63 65 69 76 65 64 20 0a 6f 6e 20 61 20 63 6f 6e 6e 65 63 74 69 6f ┆ce unit received on a connectio┆
0x5c60…5c80 6e 2c 20 69 73 20 70 61 73 73 65 64 20 66 72 6f 6d 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 ┆n, is passed from the RCLLC enti┆
0x5c80…5ca0 74 79 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 2e 0d 0a 0d 0a a1 50 61 72 61 6d 65 74 65 72 73 ┆ty to the client. Parameters┆
0x5ca0…5cc0 e1 3a 0d 0a 0d 0a 6c 5f 53 41 50 5f 61 64 64 72 09 84 69 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 ┆ : l_SAP_addr is the local S┆
0x5cc0…5ce0 41 50 20 61 64 64 72 65 73 73 2c 20 69 2e 65 2e 20 74 68 65 20 63 6c 69 65 6e 74 20 6e 65 74 77 ┆AP address, i.e. the client netw┆
0x5ce0…5d00 6f 72 6b 20 0a 19 93 80 80 6e 75 6d 62 65 72 2e 0d 0a 64 65 73 74 5f 61 64 64 72 09 69 73 20 74 ┆ork number. dest_addr is t┆
0x5d00…5d20 68 65 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 72 65 6d 6f 74 65 ┆he station address of the remote┆
0x5d20…5d40 20 53 41 50 2e 0d 0a 6c 5f 73 64 75 09 69 73 20 74 68 65 20 72 65 63 65 69 76 65 64 20 73 65 72 ┆ SAP. l_sdu is the received ser┆
0x5d40…5d51 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 2e 0d 0a ┆vice data unit. ┆
0x5d51…5d54 FormFeed {
0x5d51…5d54 0c 83 c8 ┆ ┆
0x5d51…5d54 }
0x5d54…5d60 0a a1 34 2e 20 20 20 20 20 52 43 4c ┆ 4. RCL┆
0x5d60…5d80 4c 43 20 50 52 4f 43 45 44 55 52 45 53 0d 0a 0d 0a 54 68 65 20 64 65 73 63 72 69 70 74 69 6f 6e ┆LC PROCEDURES The description┆
0x5d80…5da0 20 6f 66 20 52 43 4c 4c 43 20 70 72 6f 63 65 64 75 72 65 73 20 66 61 6c 6c 73 20 69 6e 20 74 77 ┆ of RCLLC procedures falls in tw┆
0x5da0…5dc0 6f 20 70 61 72 74 73 3a 20 31 29 20 74 68 65 20 74 79 70 65 20 31 20 0a 70 72 6f 63 65 64 75 72 ┆o parts: 1) the type 1 procedur┆
0x5dc0…5de0 65 73 20 77 68 69 63 68 20 61 72 65 20 69 6e 20 63 6f 6e 66 6f 72 6d 61 6e 63 65 20 77 69 74 68 ┆es which are in conformance with┆
0x5de0…5e00 20 28 72 65 66 2e 20 31 29 2c 20 61 6e 64 20 32 29 20 74 68 65 20 70 72 6f 63 65 64 75 72 65 73 ┆ (ref. 1), and 2) the procedures┆
0x5e00…5e20 (47,) 20 0a 66 6f 72 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 73 65 72 76 69 63 65 20 77 68 69 ┆ for client network service whi┆
0x5e20…5e40 63 68 20 63 6f 6e 73 74 69 74 75 74 65 20 61 20 66 75 6e 63 74 69 6f 6e 61 6c 20 65 78 74 65 6e ┆ch constitute a functional exten┆
0x5e40…5e60 73 69 6f 6e 20 74 6f 20 0a 74 68 65 20 74 79 70 65 20 31 20 70 72 6f 63 65 64 75 72 65 73 2e 0d ┆sion to the type 1 procedures. ┆
0x5e60…5e80 0a 0d 0a 49 6e 20 67 65 6e 65 72 61 6c 2c 20 61 6e 20 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c ┆ In general, an RCLLC protocol┆
0x5e80…5ea0 20 65 6c 65 6d 65 6e 74 20 6d 61 79 20 62 65 20 61 20 a1 63 6f 6d 6d 61 6e 64 e1 20 70 72 6f 74 ┆ element may be a command prot┆
0x5ea0…5ec0 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 0a 6f 72 20 61 20 a1 72 65 73 70 6f 6e 73 65 e1 20 70 72 ┆ocol element or a response pr┆
0x5ec0…5ee0 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 2e 20 41 73 20 61 20 70 72 6f 74 6f 63 6f 6c 20 65 6c ┆otocol element. As a protocol el┆
0x5ee0…5f00 65 6d 65 6e 74 20 69 73 20 74 72 61 6e 73 6d 69 74 74 65 64 20 0a 75 73 69 6e 67 20 74 68 65 20 ┆ement is transmitted using the ┆
0x5f00…5f20 73 65 72 76 69 63 65 73 20 6f 66 20 74 68 65 20 4d 41 43 20 6c 61 79 65 72 20 69 74 20 6d 61 79 ┆services of the MAC layer it may┆
0x5f20…5f40 20 62 65 20 61 64 64 72 65 73 73 65 64 20 74 6f 20 6f 6e 65 20 6f 72 20 0a 73 65 76 65 72 61 6c ┆ be addressed to one or several┆
0x5f40…5f60 20 73 74 61 74 69 6f 6e 73 2c 20 75 73 69 6e 67 20 61 6e 20 69 6e 64 69 76 69 64 75 61 6c 2c 20 ┆ stations, using an individual, ┆
0x5f60…5f80 6d 75 6c 74 69 63 61 73 74 2c 20 6f 72 20 62 72 6f 61 64 63 61 73 74 20 73 74 61 74 69 6f 6e 20 ┆multicast, or broadcast station ┆
0x5f80…5fa0 0a 61 64 64 72 65 73 73 2e 20 57 69 74 68 69 6e 20 65 61 63 68 20 61 64 64 72 65 73 73 65 64 20 ┆ address. Within each addressed ┆
0x5fa0…5fc0 73 74 61 74 69 6f 6e 20 61 6e 20 52 43 4c 4c 43 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e ┆station an RCLLC protocol elemen┆
0x5fc0…5fe0 74 20 69 73 20 0a 61 64 64 72 65 73 73 65 64 20 65 69 74 68 65 72 20 74 6f 20 74 68 65 20 52 43 ┆t is addressed either to the RC┆
0x5fe0…6000 4c 4c 43 20 65 6e 74 69 74 79 20 61 73 20 73 75 63 68 20 6f 72 20 74 6f 20 61 20 73 70 65 63 69 ┆LLC entity as such or to a speci┆
0x6000…6020 (48,) 66 69 63 20 53 41 50 2e 0d 0a 0d 0a 0d 0a a1 34 2e 31 20 20 20 20 54 79 70 65 20 31 20 50 72 6f ┆fic SAP. 4.1 Type 1 Pro┆
0x6020…6040 63 65 64 75 72 65 73 0d 0a 0d 0a 54 68 69 73 20 73 65 63 74 69 6f 6e 20 63 6f 6e 74 61 69 6e 73 ┆cedures This section contains┆
0x6040…6060 20 61 20 67 65 6e 65 72 61 6c 20 64 65 73 63 72 69 70 74 69 6f 6e 20 6f 66 20 74 68 65 20 74 79 ┆ a general description of the ty┆
0x6060…6080 70 65 20 31 20 70 72 6f 63 65 64 75 72 65 73 2e 20 0a 44 65 74 61 69 6c 73 20 6e 6f 74 20 63 6f ┆pe 1 procedures. Details not co┆
0x6080…60a0 76 65 72 65 64 20 69 6e 20 74 68 65 20 67 65 6e 65 72 61 6c 20 64 65 73 63 72 69 70 74 69 6f 6e ┆vered in the general description┆
0x60a0…60c0 20 61 72 65 20 67 69 76 65 6e 20 69 6e 20 63 6f 6e 6a 75 6e 63 74 69 6f 6e 20 0a 77 69 74 68 20 ┆ are given in conjunction with ┆
0x60c0…60e0 74 68 65 20 69 6e 64 69 76 69 64 75 61 6c 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 ┆the individual protocol elements┆
0x60e0…6100 20 69 6e 20 73 65 63 74 69 6f 6e 20 35 2e 0d 0a 0d 0a 0d 0a a1 34 2e 31 2e 31 20 20 55 6e 61 63 ┆ in section 5. 4.1.1 Unac┆
0x6100…6120 6b 6e 6f 77 6c 65 64 67 65 64 20 44 61 74 61 20 54 72 61 6e 73 66 65 72 0d 0a 0d 0a 54 68 69 73 ┆knowledged Data Transfer This┆
0x6120…6140 20 73 75 62 73 65 63 74 69 6f 6e 20 61 70 70 6c 69 65 73 20 74 6f 20 64 61 74 61 20 74 72 61 6e ┆ subsection applies to data tran┆
0x6140…6160 73 66 65 72 20 62 65 74 77 65 65 6e 20 61 63 74 69 76 65 20 53 41 50 73 20 66 6f 72 20 77 68 69 ┆sfer between active SAPs for whi┆
0x6160…6180 63 68 20 0a 74 79 70 65 20 31 20 73 65 72 76 69 63 65 20 68 61 73 20 62 65 65 6e 20 72 65 71 75 ┆ch type 1 service has been requ┆
0x6180…61a0 65 73 74 65 64 2e 0d 0a 0d 0a 55 6e 61 63 6b 6e 6f 77 6c 65 64 67 65 64 20 63 6f 6e 6e 65 63 74 ┆ested. Unacknowledged connect┆
0x61a0…61c0 69 6f 6e 6c 65 73 73 20 64 61 74 61 20 74 72 61 6e 73 66 65 72 20 61 73 20 72 65 71 75 65 73 74 ┆ionless data transfer as request┆
0x61c0…61e0 65 64 20 62 79 20 74 68 65 20 0a 55 44 41 54 41 2e 72 65 71 75 65 73 74 20 70 72 69 6d 69 74 69 ┆ed by the UDATA.request primiti┆
0x61e0…6200 76 65 20 69 73 20 61 63 63 6f 6d 70 6c 69 73 68 65 64 20 62 79 20 74 72 61 6e 73 6d 69 73 73 69 ┆ve is accomplished by transmissi┆
0x6200…6220 (49,) 6f 6e 20 6f 66 20 61 20 55 49 20 70 72 6f 74 6f 63 6f 6c 20 0a 65 6c 65 6d 65 6e 74 20 63 6f 6e ┆on of a UI protocol element con┆
0x6220…6240 74 61 69 6e 69 6e 67 20 74 68 65 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 20 70 61 ┆taining the service data unit pa┆
0x6240…6260 73 73 65 64 20 61 73 20 61 20 70 61 72 61 6d 65 74 65 72 20 6f 66 20 74 68 65 20 0a 70 72 69 6d ┆ssed as a parameter of the prim┆
0x6260…6280 69 74 69 76 65 2e 20 54 68 69 73 20 6d 61 79 20 6f 63 63 75 72 20 61 74 20 61 6e 79 20 74 69 6d ┆itive. This may occur at any tim┆
0x6280…62a0 65 20 77 68 69 6c 65 20 74 68 65 20 73 6f 75 72 63 65 20 53 41 50 20 69 73 20 61 63 74 69 76 65 ┆e while the source SAP is active┆
0x62a0…62c0 2e 0d 0a 0d 0a 57 68 65 6e 20 61 20 55 49 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 ┆. When a UI protocol element ┆
0x62c0…62e0 69 73 20 63 6f 72 72 65 63 74 6c 79 20 72 65 63 65 69 76 65 64 2c 20 74 68 65 20 73 65 72 76 69 ┆is correctly received, the servi┆
0x62e0…6300 63 65 20 64 61 74 61 20 75 6e 69 74 20 0a 77 68 69 63 68 20 69 74 20 63 6f 6e 74 61 69 6e 73 20 ┆ce data unit which it contains ┆
0x6300…6320 69 73 20 70 61 73 73 65 64 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 20 62 79 20 6d 65 61 6e 73 ┆is passed to the client by means┆
0x6320…6340 20 6f 66 20 61 20 55 44 41 54 41 2e 69 6e 64 69 63 61 74 69 6f 6e 20 0a 70 72 69 6d 69 74 69 76 ┆ of a UDATA.indication primitiv┆
0x6340…6360 65 2e 20 54 68 65 72 65 20 69 73 20 6e 6f 20 61 73 73 6f 63 69 61 74 65 64 20 61 63 6b 6e 6f 77 ┆e. There is no associated acknow┆
0x6360…6380 6c 65 64 67 65 6d 65 6e 74 20 6f 72 20 73 65 71 75 65 6e 63 65 20 63 68 65 63 6b 69 6e 67 2e 20 ┆ledgement or sequence checking. ┆
0x6380…63a0 0a 4e 6f 74 69 63 65 20 74 68 61 74 20 61 20 55 49 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 ┆ Notice that a UI protocol eleme┆
0x63a0…63c0 6e 74 20 77 68 69 63 68 20 69 73 20 66 6f 75 6e 64 20 74 6f 20 62 65 20 69 6e 20 65 72 72 6f 72 ┆nt which is found to be in error┆
0x63c0…63e0 20 62 79 20 74 68 65 20 0a 72 65 63 65 69 76 69 6e 67 20 4d 41 43 20 6f 72 20 52 43 4c 4c 43 20 ┆ by the receiving MAC or RCLLC ┆
0x63e0…6400 65 6e 74 69 74 79 20 69 73 20 73 69 6d 70 6c 79 20 64 69 73 63 61 72 64 65 64 2e 20 42 75 66 66 ┆entity is simply discarded. Buff┆
0x6400…6420 (50,) 65 72 20 73 68 6f 72 74 61 67 65 20 69 6e 20 0a 74 68 65 20 72 65 63 65 69 76 69 6e 67 20 52 43 ┆er shortage in the receiving RC┆
0x6420…6440 4c 4c 43 20 65 6e 74 69 74 79 20 6d 61 79 20 61 6c 73 6f 20 63 61 75 73 65 20 61 20 55 49 20 70 ┆LLC entity may also cause a UI p┆
0x6440…6460 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 74 6f 20 62 65 20 0a 64 69 73 63 61 72 64 65 64 ┆rotocol element to be discarded┆
0x6460…6480 2e 0d 0a 0d 0a 0d 0a 8c 83 ec 0a a1 34 2e 31 2e 32 20 20 4c 6f 6f 70 2d 62 61 63 6b 20 54 65 73 ┆. 4.1.2 Loop-back Tes┆
0x6480…64a0 74 20 50 72 6f 63 65 64 75 72 65 0d 0a 0d 0a 41 6e 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 77 ┆t Procedure An RCLLC entity w┆
0x64a0…64c0 69 6c 6c 20 69 6e 69 74 69 61 74 65 20 74 68 65 20 6c 6f 6f 70 2d 62 61 63 6b 20 74 65 73 74 20 ┆ill initiate the loop-back test ┆
0x64c0…64e0 70 72 6f 63 65 64 75 72 65 20 75 70 6f 6e 20 72 65 63 65 69 70 74 20 0a 6f 66 20 61 20 54 45 53 ┆procedure upon receipt of a TES┆
0x64e0…6500 54 2e 72 65 71 75 65 73 74 20 70 72 69 6d 69 74 76 65 20 66 72 6f 6d 20 61 20 63 6c 69 65 6e 74 ┆T.request primitve from a client┆
0x6500…6520 2e 20 49 74 20 64 6f 65 73 20 73 6f 20 62 79 20 74 72 61 6e 73 6d 69 74 74 69 6e 67 20 61 20 0a ┆. It does so by transmitting a ┆
0x6520…6540 54 45 53 54 20 63 6f 6d 6d 61 6e 64 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 77 69 ┆TEST command protocol element wi┆
0x6540…6560 74 68 20 74 68 65 20 70 6f 6c 6c 20 62 69 74 20 73 65 74 20 74 6f 20 31 20 61 6e 64 20 61 64 64 ┆th the poll bit set to 1 and add┆
0x6560…6580 72 65 73 73 65 64 20 0a 61 73 20 73 70 65 63 69 66 69 65 64 20 69 6e 20 74 68 65 20 72 65 71 75 ┆ressed as specified in the requ┆
0x6580…65a0 65 73 74 2e 20 54 68 65 20 69 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 6f 66 20 74 68 ┆est. The information field of th┆
0x65a0…65c0 65 20 54 45 53 54 20 63 6f 6d 6d 61 6e 64 20 0a 77 69 6c 6c 20 63 6f 6e 74 61 69 6e 20 74 68 65 ┆e TEST command will contain the┆
0x65c0…65e0 20 73 70 65 63 69 66 69 65 64 20 74 65 73 74 20 64 61 74 61 20 75 6e 69 74 2e 20 4e 6f 74 69 63 ┆ specified test data unit. Notic┆
0x65e0…6600 65 20 74 68 61 74 20 6d 75 6c 74 69 2d 20 6f 72 20 62 72 6f 61 64 2d 0a 63 61 73 74 69 6e 67 20 ┆e that multi- or broad- casting ┆
0x6600…6620 (51,) 6d 61 79 20 62 65 20 75 73 65 64 20 74 6f 20 74 65 73 74 20 73 65 76 65 72 61 6c 20 74 72 61 6e ┆may be used to test several tran┆
0x6620…6640 73 6d 69 73 73 69 6f 6e 20 70 61 74 68 73 20 75 73 69 6e 67 20 6f 6e 65 20 63 6f 6d 6d 61 6e 64 ┆smission paths using one command┆
0x6640…6660 20 0a 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 2e 0d 0a 0d 0a 46 6f 72 20 65 61 63 68 20 ┆ protocol element. For each ┆
0x6660…6680 54 45 53 54 20 72 65 73 70 6f 6e 73 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 77 ┆TEST response protocol element w┆
0x6680…66a0 68 69 63 68 20 69 73 20 73 75 62 73 65 71 75 65 6e 74 6c 79 20 72 65 63 65 69 76 65 64 20 0a 63 ┆hich is subsequently received c┆
0x66a0…66c0 6f 72 72 65 63 74 6c 79 2c 20 77 69 74 68 20 6f 72 20 77 69 74 68 6f 75 74 20 61 6e 20 69 6e 66 ┆orrectly, with or without an inf┆
0x66c0…66e0 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 2c 20 74 68 65 20 63 6c 69 65 6e 74 20 69 73 20 69 6e ┆ormation field, the client is in┆
0x66e0…6700 66 6f 72 6d 65 64 20 0a 62 79 20 6d 65 61 6e 73 20 6f 66 20 61 20 54 45 53 54 2e 63 6f 6e 66 69 ┆formed by means of a TEST.confi┆
0x6700…6720 72 6d 20 70 72 69 6d 69 74 69 76 65 2e 0d 0a 0d 0a 41 6e 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 ┆rm primitive. An RCLLC entity┆
0x6720…6740 20 77 69 6c 6c 20 6e 6f 74 20 74 72 61 6e 73 6d 69 74 20 61 20 54 45 53 54 20 63 6f 6d 6d 61 6e ┆ will not transmit a TEST comman┆
0x6740…6760 64 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 2c 20 0a 65 78 63 65 70 74 20 77 68 65 6e ┆d protocol element, except when┆
0x6760…6780 20 64 69 72 65 63 74 65 64 20 62 79 20 61 20 54 45 53 54 2e 72 65 71 75 65 73 74 20 70 72 69 6d ┆ directed by a TEST.request prim┆
0x6780…67a0 69 74 69 76 65 2e 0d 0a 0d 0a 57 68 65 6e 20 61 6e 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 63 ┆itive. When an RCLLC entity c┆
0x67a0…67c0 6f 72 72 65 63 74 6c 79 20 72 65 63 65 69 76 65 73 20 61 20 54 45 53 54 20 63 6f 6d 6d 61 6e 64 ┆orrectly receives a TEST command┆
0x67c0…67e0 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 0a 61 64 64 72 65 73 73 65 64 20 74 6f 20 ┆ protocol element addressed to ┆
0x67e0…6800 69 74 73 65 6c 66 20 6f 72 20 74 6f 20 61 6e 20 61 63 74 69 76 65 20 53 41 50 2c 20 77 69 74 68 ┆itself or to an active SAP, with┆
0x6800…6820 (52,) 20 74 68 65 20 70 6f 6c 6c 20 62 69 74 20 73 65 74 20 74 6f 20 31 2c 20 69 74 20 0a 77 69 6c 6c ┆ the poll bit set to 1, it will┆
0x6820…6840 20 72 65 73 70 6f 6e 64 20 62 79 20 74 72 61 6e 73 6d 69 74 74 69 6e 67 20 61 20 54 45 53 54 20 ┆ respond by transmitting a TEST ┆
0x6840…6860 72 65 73 70 6f 6e 73 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 61 64 64 72 65 73 ┆response protocol element addres┆
0x6860…6880 73 65 64 20 0a 74 6f 20 74 68 65 20 73 6f 75 72 63 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 ┆sed to the source RCLLC entity ┆
0x6880…68a0 6f 72 20 53 41 50 2e 20 54 68 65 20 72 65 63 65 69 76 65 64 20 69 6e 66 6f 72 6d 61 74 69 6f 6e ┆or SAP. The received information┆
0x68a0…68c0 20 69 73 20 63 6f 70 69 65 64 20 74 6f 20 0a 74 68 65 20 72 65 73 70 6f 6e 73 65 20 70 72 6f 74 ┆ is copied to the response prot┆
0x68c0…68e0 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 2e 20 49 66 20 74 68 65 20 69 6e 66 6f 72 6d 61 74 69 6f 6e ┆ocol element. If the information┆
0x68e0…6900 20 66 69 65 6c 64 20 63 6f 75 6c 64 20 6e 6f 74 20 62 65 20 0a 68 65 6c 64 20 69 6e 20 74 68 65 ┆ field could not be held in the┆
0x6900…6920 20 72 65 63 65 69 76 65 20 62 75 66 66 65 72 28 73 29 20 6f 66 20 74 68 65 20 52 43 4c 4c 43 20 ┆ receive buffer(s) of the RCLLC ┆
0x6920…6940 65 6e 74 69 74 79 20 64 75 65 20 74 6f 20 6f 76 65 72 6c 65 6e 67 74 68 2c 20 74 68 65 20 0a 72 ┆entity due to overlength, the r┆
0x6940…6960 65 73 70 6f 6e 73 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 77 69 6c 6c 20 63 6f ┆esponse protocol element will co┆
0x6960…6980 6e 74 61 69 6e 20 61 6e 20 65 6d 70 74 79 20 69 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 ┆ntain an empty information field┆
0x6980…69a0 2e 20 49 6e 20 0a 74 68 65 20 63 61 73 65 20 77 68 65 6e 20 74 68 65 20 72 65 63 65 69 76 65 64 ┆. In the case when the received┆
0x69a0…69c0 20 54 45 53 54 20 63 6f 6d 6d 61 6e 64 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 ┆ TEST command protocol element i┆
0x69c0…69e0 73 20 61 64 64 72 65 73 73 65 64 20 74 6f 20 0a 61 20 53 41 50 2c 20 74 68 65 20 63 6c 69 65 6e ┆s addressed to a SAP, the clien┆
0x69e0…6a00 74 20 77 69 6c 6c 20 62 65 20 69 6e 66 6f 72 6d 65 64 20 62 79 20 6d 65 61 6e 73 20 6f 66 20 61 ┆t will be informed by means of a┆
0x6a00…6a20 (53,) 20 54 45 53 54 2e 69 6e 64 69 63 61 74 69 6f 6e 20 0a 70 72 69 6d 69 74 69 76 65 2e 20 4e 6f 74 ┆ TEST.indication primitive. Not┆
0x6a20…6a40 69 63 65 20 74 68 61 74 20 74 68 65 20 73 6f 75 72 63 65 20 73 74 61 74 69 6f 6e 20 69 6e 20 74 ┆ice that the source station in t┆
0x6a40…6a60 68 69 73 20 63 61 73 65 20 77 69 6c 6c 20 6e 6f 74 20 62 65 20 61 6e 20 0a 52 43 4c 4c 43 20 73 ┆his case will not be an RCLLC s┆
0x6a60…6a80 74 61 74 69 6f 6e 2e 0d 0a 0d 0a 41 20 54 45 53 54 20 63 6f 6d 6d 61 6e 64 20 70 72 6f 74 6f 63 ┆tation. A TEST command protoc┆
0x6a80…6aa0 6f 6c 20 65 6c 65 6d 65 6e 74 20 72 65 63 65 69 76 65 64 20 77 69 74 68 20 70 6f 6c 6c 20 62 69 ┆ol element received with poll bi┆
0x6aa0…6ac0 74 20 73 65 74 20 74 6f 20 30 20 69 73 20 0a 64 69 73 63 61 72 64 65 64 2e 0d 0a 0d 0a 0d 0a a1 ┆t set to 0 is discarded. ┆
0x6ac0…6ae0 34 2e 31 2e 33 20 20 53 74 61 74 69 6f 6e 20 49 64 65 6e 74 69 66 69 63 61 74 69 6f 6e 20 45 78 ┆4.1.3 Station Identification Ex┆
0x6ae0…6b00 63 68 61 6e 67 65 0d 0a 0d 0a 54 79 70 65 20 31 20 73 74 61 74 69 6f 6e 20 69 64 65 6e 74 69 66 ┆change Type 1 station identif┆
0x6b00…6b20 69 63 61 74 69 6f 6e 20 65 78 63 68 61 6e 67 65 20 69 73 20 6e 6f 74 20 73 75 70 70 6f 72 74 65 ┆ication exchange is not supporte┆
0x6b20…6b40 64 20 61 73 20 70 61 72 74 20 6f 66 20 74 68 65 20 0a 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 ┆d as part of the RCLLC service ┆
0x6b40…6b60 69 6e 74 65 72 66 61 63 65 2c 20 61 6e 64 20 61 6e 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 77 ┆interface, and an RCLLC entity w┆
0x6b60…6b80 69 6c 6c 20 6e 6f 74 2c 20 74 68 65 72 65 66 6f 72 65 2c 20 0a 74 72 61 6e 73 6d 69 74 20 58 49 ┆ill not, therefore, transmit XI┆
0x6b80…6ba0 44 20 63 6f 6d 6d 61 6e 64 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 2e 20 49 74 20 ┆D command protocol elements. It ┆
0x6ba0…6bc0 77 69 6c 6c 2c 20 68 6f 77 65 76 65 72 2c 20 61 6e 73 77 65 72 20 0a 8c 83 c8 0a 70 6f 6c 69 74 ┆will, however, answer polit┆
0x6bc0…6be0 65 6c 79 20 77 68 65 6e 20 61 6e 20 58 49 44 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 ┆ely when an XID protocol element┆
0x6be0…6c00 20 61 64 64 72 65 73 73 65 64 20 74 6f 20 69 74 73 65 6c 66 20 6f 72 20 74 6f 20 61 6e 20 0a 61 ┆ addressed to itself or to an a┆
0x6c00…6c20 (54,) 63 74 69 76 65 20 53 41 50 20 69 73 20 63 6f 72 72 65 63 74 6c 79 20 72 65 63 65 69 76 65 64 2e ┆ctive SAP is correctly received.┆
0x6c20…6c40 20 4f 62 73 65 72 76 65 20 74 68 61 74 20 74 68 65 20 73 6f 75 72 63 65 20 73 74 61 74 69 6f 6e ┆ Observe that the source station┆
0x6c40…6c60 20 69 6e 20 0a 74 68 69 73 20 63 61 73 65 20 77 69 6c 6c 20 6e 6f 74 20 62 65 20 61 6e 20 52 43 ┆ in this case will not be an RC┆
0x6c60…6c80 4c 4c 43 20 73 74 61 74 69 6f 6e 2e 0d 0a 0d 0a 0d 0a a1 34 2e 32 20 20 20 20 50 72 6f 63 65 64 ┆LLC station. 4.2 Proced┆
0x6c80…6ca0 75 72 65 73 20 66 6f 72 20 43 6c 69 65 6e 74 20 4e 65 74 77 6f 72 6b 20 53 65 72 76 69 63 65 0d ┆ures for Client Network Service ┆
0x6ca0…6cc0 0a 0d 0a 54 68 69 73 20 73 65 63 74 69 6f 6e 20 63 6f 6e 74 61 69 6e 73 20 61 20 67 65 6e 65 72 ┆ This section contains a gener┆
0x6cc0…6ce0 61 6c 20 64 65 73 63 72 69 70 74 69 6f 6e 20 6f 66 20 74 68 65 20 70 72 6f 63 65 64 75 72 65 73 ┆al description of the procedures┆
0x6ce0…6d00 20 66 6f 72 20 63 6c 69 65 6e 74 20 0a 6e 65 74 77 6f 72 6b 20 73 65 72 76 69 63 65 2e 20 44 65 ┆ for client network service. De┆
0x6d00…6d20 74 61 69 6c 73 20 6e 6f 74 20 63 6f 76 65 72 65 64 20 69 6e 20 74 68 65 20 67 65 6e 65 72 61 6c ┆tails not covered in the general┆
0x6d20…6d40 20 64 65 73 63 72 69 70 74 69 6f 6e 20 61 72 65 20 0a 67 69 76 65 6e 20 69 6e 20 63 6f 6e 6a 75 ┆ description are given in conju┆
0x6d40…6d60 6e 63 74 69 6f 6e 20 77 69 74 68 20 74 68 65 20 69 6e 64 69 76 69 64 75 61 6c 20 70 72 6f 74 6f ┆nction with the individual proto┆
0x6d60…6d80 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 69 6e 20 73 65 63 74 69 6f 6e 20 35 2e 0d 0a 0d 0a 43 6c ┆col elements in section 5. Cl┆
0x6d80…6da0 69 65 6e 74 20 6e 65 74 77 6f 72 6b 73 20 61 72 65 20 73 75 70 65 72 76 69 73 65 64 20 62 79 20 ┆ient networks are supervised by ┆
0x6da0…6dc0 74 68 65 20 52 43 4c 4c 43 20 6c 61 79 65 72 2e 20 54 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c ┆the RCLLC layer. The protocol el┆
0x6dc0…6de0 65 6d 65 6e 74 20 0a 41 43 54 49 56 45 5f 53 41 50 20 70 6c 61 79 73 20 61 20 63 65 6e 74 72 61 ┆ement ACTIVE_SAP plays a centra┆
0x6de0…6e00 6c 20 72 6f 6c 65 20 69 6e 20 74 68 69 73 20 72 65 73 70 65 63 74 2e 20 57 68 65 6e 65 76 65 72 ┆l role in this respect. Whenever┆
0x6e00…6e20 (55,) 20 61 20 53 41 50 20 0a 62 65 6c 6f 6e 67 69 6e 67 20 74 6f 20 61 20 63 6c 69 65 6e 74 20 6e 65 ┆ a SAP belonging to a client ne┆
0x6e20…6e40 74 77 6f 72 6b 20 69 73 20 61 63 74 69 76 65 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 ┆twork is active the RCLLC entity┆
0x6e40…6e60 20 73 65 72 76 69 6e 67 20 74 68 65 20 53 41 50 20 0a 77 69 6c 6c 20 72 65 67 75 6c 61 72 6c 79 ┆ serving the SAP will regularly┆
0x6e60…6e80 20 74 72 61 6e 73 6d 69 74 20 74 68 69 73 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 ┆ transmit this protocol element ┆
0x6e80…6ea0 74 6f 20 69 74 73 20 70 65 65 72 20 65 6e 74 69 74 69 65 73 20 75 73 69 6e 67 20 0a 74 68 65 20 ┆to its peer entities using the ┆
0x6ea0…6ec0 6d 75 6c 74 69 63 61 73 74 20 61 64 64 72 65 73 73 20 66 6f 72 20 74 68 65 20 63 6c 69 65 6e 74 ┆multicast address for the client┆
0x6ec0…6ee0 20 6e 65 74 77 6f 72 6b 2e 20 41 6e 20 52 43 4c 4c 43 20 72 65 63 65 69 76 69 6e 67 20 74 68 65 ┆ network. An RCLLC receiving the┆
0x6ee0…6f00 20 0a 41 43 54 49 56 45 5f 53 41 50 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 77 69 ┆ ACTIVE_SAP protocol element wi┆
0x6f00…6f20 6c 6c 20 64 69 73 63 61 72 64 20 69 74 20 75 6e 6c 65 73 73 20 74 68 65 20 69 6e 63 6c 75 64 65 ┆ll discard it unless the include┆
0x6f20…6f40 64 20 53 41 50 20 0a 6d 61 73 6b 20 6d 61 74 63 68 65 73 20 74 68 65 20 6d 61 73 6b 20 6f 66 20 ┆d SAP mask matches the mask of ┆
0x6f40…6f60 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 62 65 6c 6f 6e 67 69 6e 67 20 74 6f 20 74 68 65 20 73 ┆the local SAP belonging to the s┆
0x6f60…6f80 61 6d 65 20 63 6c 69 65 6e 74 20 0a 6e 65 74 77 6f 72 6b 2e 0d 0a 0d 0a 54 68 69 73 20 70 72 6f ┆ame client network. This pro┆
0x6f80…6fa0 63 65 64 75 72 65 20 73 65 72 76 65 73 20 74 6f 20 6d 61 6b 65 20 61 20 53 41 50 20 6b 6e 6f 77 ┆cedure serves to make a SAP know┆
0x6fa0…6fc0 6e 20 74 68 72 6f 75 67 68 6f 75 74 20 74 68 65 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 ┆n throughout the client network ┆
0x6fc0…6fe0 0a 73 6f 20 74 68 61 74 20 61 6c 6c 20 64 65 73 69 72 65 64 20 63 6f 6e 6e 65 63 74 69 6f 6e 73 ┆ so that all desired connections┆
0x6fe0…7000 20 74 6f 20 74 68 65 20 53 41 50 20 6d 61 79 20 62 65 20 65 73 74 61 62 6c 69 73 68 65 64 2e 20 ┆ to the SAP may be established. ┆
0x7000…7020 (56,) 4e 6f 74 69 63 65 20 0a 74 68 61 74 20 74 68 65 20 53 41 50 20 72 65 6d 61 69 6e 73 20 75 6e 6b ┆Notice that the SAP remains unk┆
0x7020…7040 6e 6f 77 6e 20 74 6f 20 61 6c 6c 20 73 74 61 74 69 6f 6e 73 20 77 68 65 72 65 20 69 74 73 20 6d ┆nown to all stations where its m┆
0x7040…7060 61 73 6b 20 64 6f 65 73 20 6e 6f 74 20 0a 6d 61 74 63 68 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 ┆ask does not match the local SA┆
0x7060…7080 50 20 6d 61 73 6b 2e 0d 0a 0d 0a 4d 6f 72 65 6f 76 65 72 2c 20 74 68 65 20 70 72 6f 63 65 64 75 ┆P mask. Moreover, the procedu┆
0x7080…70a0 72 65 20 61 6c 6c 6f 77 73 20 52 43 4c 4c 43 20 65 6e 74 69 74 69 65 73 20 74 6f 20 73 75 70 65 ┆re allows RCLLC entities to supe┆
0x70a0…70c0 72 76 69 73 65 20 74 68 65 20 6c 69 76 65 6e 65 73 73 20 0a 6f 66 20 61 6c 6c 20 65 78 69 73 74 ┆rvise the liveness of all exist┆
0x70c0…70e0 69 6e 67 20 63 6f 6e 6e 65 63 74 69 6f 6e 73 2e 20 57 68 65 6e 20 74 68 65 20 41 43 54 49 56 45 ┆ing connections. When the ACTIVE┆
0x70e0…7100 5f 53 41 50 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 66 61 69 6c 73 20 0a 74 6f 20 ┆_SAP protocol element fails to ┆
0x7100…7120 61 72 72 69 76 65 20 66 72 6f 6d 20 61 20 53 41 50 20 74 6f 20 77 68 69 63 68 20 61 20 63 6f 6e ┆arrive from a SAP to which a con┆
0x7120…7140 6e 65 63 74 69 6f 6e 20 65 78 69 73 74 73 2c 20 66 6f 72 20 61 20 73 75 66 66 69 63 69 65 6e 74 ┆nection exists, for a sufficient┆
0x7140…7160 6c 79 20 0a 6c 6f 6e 67 20 70 65 72 69 6f 64 20 6f 66 20 74 69 6d 65 2c 20 74 68 69 73 20 77 69 ┆ly long period of time, this wi┆
0x7160…7180 6c 6c 20 62 65 20 74 61 6b 65 6e 20 74 6f 20 69 6e 64 69 63 61 74 65 20 74 68 61 74 20 74 68 65 ┆ll be taken to indicate that the┆
0x7180…71a0 20 53 41 50 20 69 73 20 6e 6f 20 0a 6c 6f 6e 67 65 72 20 61 63 74 69 76 65 2c 20 61 6e 64 20 74 ┆ SAP is no longer active, and t┆
0x71a0…71c0 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 77 69 6c 6c 20 74 68 65 72 65 66 6f 72 65 20 72 ┆he RCLLC entity will therefore r┆
0x71c0…71e0 65 6d 6f 76 65 20 69 74 73 20 65 6e 64 20 6f 66 20 74 68 65 20 0a 63 6f 6e 6e 65 63 74 69 6f 6e ┆emove its end of the connection┆
0x71e0…7200 2e 0d 0a 0d 0a 41 6c 6c 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 6f 74 68 65 72 ┆. All protocol elements other┆
0x7200…7220 (57,) 20 74 68 61 6e 20 41 43 54 49 56 45 5f 53 41 50 20 61 72 65 20 74 72 61 6e 73 6d 69 74 74 65 64 ┆ than ACTIVE_SAP are transmitted┆
0x7220…7240 20 75 73 69 6e 67 20 0a 69 6e 64 69 76 69 64 75 61 6c 20 73 74 61 74 69 6f 6e 20 61 64 64 72 65 ┆ using individual station addre┆
0x7240…7260 73 73 2e 0d 0a 0d 0a 54 68 65 20 72 69 67 6f 72 6f 75 73 20 64 65 73 63 72 69 70 74 69 6f 6e 20 ┆ss. The rigorous description ┆
0x7260…7280 6f 66 20 74 68 65 20 70 72 6f 63 65 64 75 72 65 73 20 66 6f 72 20 65 73 74 61 62 6c 69 73 68 6d ┆of the procedures for establishm┆
0x7280…72a0 65 6e 74 20 61 6e 64 20 0a 73 75 70 65 72 76 69 73 69 6f 6e 20 6f 66 20 63 6f 6e 6e 65 63 74 69 ┆ent and supervision of connecti┆
0x72a0…72c0 6f 6e 73 20 77 68 69 63 68 20 69 73 20 67 69 76 65 6e 20 69 6e 20 74 68 65 20 66 6f 6c 6c 6f 77 ┆ons which is given in the follow┆
0x72c0…72e0 69 6e 67 20 69 73 20 62 61 73 65 64 20 6f 6e 20 61 20 0a 73 74 61 74 65 2c 20 74 77 6f 20 74 69 ┆ing is based on a state, two ti┆
0x72e0…7300 6d 65 72 73 20 61 6e 64 20 61 20 72 65 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 63 6f 75 6e 74 65 ┆mers and a retransmission counte┆
0x7300…7320 72 20 6d 61 69 6e 74 61 69 6e 65 64 20 62 79 20 61 6e 20 52 43 4c 4c 43 20 0a 8c 83 c8 0a 65 6e ┆r maintained by an RCLLC en┆
0x7320…7340 74 69 74 79 20 66 6f 72 20 65 61 63 68 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 69 6e 20 77 68 69 63 ┆tity for each connection in whic┆
0x7340…7360 68 20 69 74 20 74 61 6b 65 73 20 70 61 72 74 2c 20 69 2e 65 2e 20 66 6f 72 20 65 61 63 68 20 72 ┆h it takes part, i.e. for each r┆
0x7360…7380 65 6d 6f 74 65 20 0a 53 41 50 20 69 74 20 6b 6e 6f 77 73 2e 20 54 68 65 20 66 6f 6c 6c 6f 77 69 ┆emote SAP it knows. The followi┆
0x7380…73a0 6e 67 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 73 74 61 74 65 73 20 65 78 69 73 74 3a 20 55 4e 4b 4e ┆ng connection states exist: UNKN┆
0x73a0…73c0 4f 57 4e 2c 20 52 45 53 45 54 54 49 4e 47 2c 20 0a 44 41 54 41 2c 20 44 49 53 43 4f 4e 4e 45 43 ┆OWN, RESETTING, DATA, DISCONNEC┆
0x73c0…73e0 54 49 4e 47 2e 20 54 68 65 20 74 69 6d 65 72 73 20 61 72 65 3a 0d 0a 0d 0a 09 2d 20 84 74 68 65 ┆TING. The timers are: - the┆
0x73e0…7400 20 61 63 6b 6e 6f 77 6c 65 64 67 65 6d 65 6e 74 20 74 69 6d 65 72 20 77 68 69 63 68 20 72 75 6e ┆ acknowledgement timer which run┆
0x7400…7420 (58,) 73 20 77 68 65 6e 20 61 6e 20 61 63 6b 6e 6f 77 6c 65 64 67 65 6d 65 6e 74 2c 20 69 2e 65 2e 20 ┆s when an acknowledgement, i.e. ┆
0x7420…7440 0a 19 86 80 80 61 20 52 41 43 4b 20 6f 72 20 41 43 4b 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d ┆ a RACK or ACK protocol elem┆
0x7440…7460 65 6e 74 20 69 73 20 65 78 70 65 63 74 65 64 2c 0d 0a 09 2d 20 84 74 68 65 20 53 41 50 20 61 6c ┆ent is expected, - the SAP al┆
0x7460…7480 69 76 65 20 74 69 6d 65 72 20 77 68 69 63 68 20 72 75 6e 73 20 77 68 65 6e 65 76 65 72 20 74 68 ┆ive timer which runs whenever th┆
0x7480…74a0 65 20 72 65 6d 6f 74 65 20 53 41 50 20 69 73 20 6b 6e 6f 77 6e 20 0a 19 86 80 80 61 6e 64 20 69 ┆e remote SAP is known and i┆
0x74a0…74c0 73 20 72 65 73 74 61 72 74 65 64 20 65 61 63 68 20 74 69 6d 65 20 61 6e 20 41 43 54 49 56 45 5f ┆s restarted each time an ACTIVE_┆
0x74c0…74e0 53 41 50 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 0a 19 86 80 80 72 65 63 ┆SAP protocol element is rec┆
0x74e0…7500 65 69 76 65 64 2e 0d 0a 0d 0a 49 6e 20 61 64 64 69 74 69 6f 6e 20 74 6f 20 74 68 65 20 73 74 61 ┆eived. In addition to the sta┆
0x7500…7520 74 65 2c 20 74 69 6d 65 72 73 2c 20 61 6e 64 20 72 65 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 63 ┆te, timers, and retransmission c┆
0x7520…7540 6f 75 6e 74 65 72 20 61 6e 20 52 43 4c 4c 43 20 0a 65 6e 74 69 74 79 20 6d 61 69 6e 74 61 69 6e ┆ounter an RCLLC entity maintain┆
0x7540…7560 73 20 66 6f 72 20 65 61 63 68 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 74 77 6f 20 73 65 71 75 65 6e ┆s for each connection two sequen┆
0x7560…7580 63 65 20 63 6f 75 6e 74 65 72 73 20 66 6f 72 20 64 61 74 61 20 0a 75 6e 69 74 73 2c 20 4e 28 53 ┆ce counters for data units, N(S┆
0x7580…75a0 29 3a 20 74 68 65 20 6e 75 6d 62 65 72 20 6f 66 20 74 68 65 20 64 61 74 61 20 75 6e 69 74 20 74 ┆): the number of the data unit t┆
0x75a0…75c0 6f 20 74 72 61 6e 73 6d 69 74 2c 20 61 6e 64 20 4e 28 52 29 3a 20 74 68 65 20 0a 6e 75 6d 62 65 ┆o transmit, and N(R): the numbe┆
0x75c0…75e0 72 20 6f 66 20 74 68 65 20 6e 65 78 74 20 64 61 74 61 20 75 6e 69 74 20 74 6f 20 62 65 20 72 65 ┆r of the next data unit to be re┆
0x75e0…7600 63 65 69 76 65 64 2e 0d 0a 0d 0a 54 68 65 20 66 6f 6c 6c 6f 77 69 6e 67 20 65 76 65 6e 74 73 20 ┆ceived. The following events ┆
0x7600…7620 (59,) 6d 61 79 20 63 61 75 73 65 20 74 68 65 20 73 74 61 74 65 20 6f 66 20 61 20 63 6f 6e 6e 65 63 74 ┆may cause the state of a connect┆
0x7620…7640 69 6f 6e 20 74 6f 20 63 68 61 6e 67 65 3a 0d 0a 0d 0a 50 45 5f 6e 65 77 5f 53 41 50 09 84 41 6e ┆ion to change: PE_new_SAP An┆
0x7640…7660 20 41 43 54 49 56 45 5f 53 41 50 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 ┆ ACTIVE_SAP protocol element is ┆
0x7660…7680 72 65 63 65 69 76 65 64 20 66 72 6f 6d 20 74 68 65 20 0a 19 93 80 80 72 65 6d 6f 74 65 20 53 41 ┆received from the remote SA┆
0x7680…76a0 50 20 69 6e 64 69 63 61 74 69 6e 67 20 69 74 20 68 61 73 20 62 65 63 6f 6d 65 20 61 63 74 69 76 ┆P indicating it has become activ┆
0x76a0…76c0 65 2c 20 70 6f 73 73 69 62 6c 79 20 0a 19 93 80 80 62 79 20 72 65 69 6e 69 74 69 61 6c 69 7a 61 ┆e, possibly by reinitializa┆
0x76c0…76e0 74 69 6f 6e 2c 20 73 65 65 20 73 75 62 73 65 63 74 69 6f 6e 20 35 2e 32 2e 31 2e 0d 0a 0d 0a 50 ┆tion, see subsection 5.2.1. P┆
0x76e0…7700 45 5f 72 61 63 6b 09 84 41 20 52 41 43 4b 20 6f 72 20 52 45 53 45 54 20 70 72 6f 74 6f 63 6f 6c ┆E_rack A RACK or RESET protocol┆
0x7700…7720 20 65 6c 65 6d 65 6e 74 20 69 73 20 72 65 63 65 69 76 65 64 20 66 72 6f 6d 20 74 68 65 20 0a 19 ┆ element is received from the ┆
0x7720…7740 93 80 80 72 65 6d 6f 74 65 20 53 41 50 20 77 68 65 6e 20 52 41 43 4b 20 69 73 20 65 78 70 65 63 ┆ remote SAP when RACK is expec┆
0x7740…7760 74 65 64 2e 0d 0a 0d 0a 50 45 5f 72 65 73 65 74 09 84 41 20 52 45 53 45 54 20 70 72 6f 74 6f 63 ┆ted. PE_reset A RESET protoc┆
0x7760…7780 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 72 65 63 65 69 76 65 64 20 66 72 6f 6d 20 74 68 65 20 ┆ol element is received from the ┆
0x7780…77a0 72 65 6d 6f 74 65 20 0a 19 93 80 80 53 41 50 2c 20 65 78 63 65 70 74 20 77 68 65 6e 20 52 41 43 ┆remote SAP, except when RAC┆
0x77a0…77c0 4b 20 69 73 20 65 78 70 65 63 74 65 64 2e 0d 0a 0d 0a 67 69 76 65 5f 75 70 09 84 54 68 65 20 52 ┆K is expected. give_up The R┆
0x77c0…77e0 43 4c 4c 43 20 65 6e 74 69 74 79 20 67 69 76 65 73 20 75 70 20 74 68 65 20 63 6f 6e 6e 65 63 74 ┆CLLC entity gives up the connect┆
0x77e0…7800 69 6f 6e 20 77 68 65 6e 20 74 68 65 20 0a 19 93 80 80 72 65 74 72 61 6e 73 6d 69 73 73 69 6f 6e ┆ion when the retransmission┆
0x7800…7820 (60,) 20 63 6f 75 6e 74 65 72 20 69 73 20 65 78 68 61 75 73 74 65 64 2c 20 6f 72 20 77 68 65 6e 20 74 ┆ counter is exhausted, or when t┆
0x7820…7840 68 65 20 53 41 50 20 0a 19 93 80 80 61 6c 69 76 65 20 74 69 6d 65 72 20 72 75 6e 73 20 6f 75 74 ┆he SAP alive timer runs out┆
0x7840…7860 2e 0d 0a 0d 0a 53 50 5f 64 61 63 6b 09 84 41 6e 20 65 78 70 65 63 74 65 64 20 44 49 53 43 4f 4e ┆. SP_dack An expected DISCON┆
0x7860…7880 4e 45 43 54 2e 61 63 6b 6e 6f 77 6c 65 64 67 65 20 73 65 72 76 69 63 65 20 70 72 69 6d 69 74 69 ┆NECT.acknowledge service primiti┆
0x7880…78a0 76 65 20 0a 19 93 80 80 69 73 20 72 65 63 65 69 76 65 64 20 66 72 6f 6d 20 74 68 65 20 63 6c 69 ┆ve is received from the cli┆
0x78a0…78c0 65 6e 74 2e 0d 0a 0d 0a 41 6e 20 6f 76 65 72 76 69 65 77 20 6f 66 20 74 68 65 20 73 74 61 74 65 ┆ent. An overview of the state┆
0x78c0…78e0 20 63 68 61 6e 67 65 73 20 63 61 75 73 65 64 20 62 79 20 65 76 65 6e 74 73 20 61 6e 64 20 74 68 ┆ changes caused by events and th┆
0x78e0…7900 65 20 61 73 73 6f 63 69 61 74 65 64 20 0a 61 63 74 69 6f 6e 73 2c 20 69 2e 65 2e 20 70 72 6f 74 ┆e associated actions, i.e. prot┆
0x7900…7920 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 61 6e 64 20 73 65 72 76 69 63 65 20 70 72 69 6d 69 74 ┆ocol elements and service primit┆
0x7920…7940 69 76 65 73 20 74 68 61 74 20 61 72 65 20 0a 67 65 6e 65 72 61 74 65 64 2c 20 69 73 20 67 69 76 ┆ives that are generated, is giv┆
0x7940…7960 65 6e 20 69 6e 20 66 69 67 75 72 65 20 31 2e 20 4e 6f 74 65 20 74 68 61 74 20 74 68 65 20 66 69 ┆en in figure 1. Note that the fi┆
0x7960…7980 67 75 72 65 20 61 6e 64 20 74 68 65 20 0a 64 65 73 63 72 69 70 74 69 6f 6e 20 77 68 69 63 68 20 ┆gure and the description which ┆
0x7980…79a0 66 6f 6c 6c 6f 77 73 20 61 70 70 6c 79 20 74 6f 20 61 20 73 69 6e 67 6c 65 20 63 6f 6e 6e 65 63 ┆follows apply to a single connec┆
0x79a0…79c0 74 69 6f 6e 2c 20 69 6e 20 66 61 63 74 20 74 6f 20 65 61 63 68 20 0a 65 6e 64 2d 70 6f 69 6e 74 ┆tion, in fact to each end-point┆
0x79c0…79d6 20 73 65 70 61 72 61 74 65 6c 79 2e 0d 0a 0d 0a 8c 83 e0 0a 0e 0a ┆ separately. ┆
0x79d6…7a0f Params {
0x79d6…7a0f 04 00 2d 4e 0c 00 06 00 00 00 00 02 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0x79d6…7a0f 00 00 00 00 00 00 00 00 07 0d 1a 22 2a 38 3f 44 47 4b 55 5f 69 73 7d ff 04 ┆ "*8?DGKU_iså ┆
0x79d6…7a0f }
0x7a0f…7a48 Params {
0x7a0f…7a48 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1` ┆
0x7a0f…7a48 00 00 00 00 00 00 00 00 05 0a 11 19 1e 46 4b 55 5f 69 73 7d ff ff ff ff 04 ┆ FKU_iså ┆
0x7a0f…7a48 }
0x7a48…7a60 0a 09 09 09 a1 09 09 5f 0d 0a 09 09 09 21 09 09 21 0d 0a 09 09 09 21 20 ┆ _ ! ! ! ┆
0x7a60…7a80 20 20 20 55 4e 4b 4e 4f 57 4e 09 21 3c 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d ┆ UNKNOWN !<-------------------┆
0x7a80…7aa0 2d 2d 2d 2d 2d 2d 2d 2d 21 0d 0a 09 09 09 a1 21 09 09 21 e1 09 09 09 09 21 0d 0a 09 09 09 20 20 ┆--------! ! ! ! ┆
0x7aa0…7ac0 20 21 09 20 20 20 20 20 21 09 09 09 09 09 21 0d 0a 09 09 50 45 5f 6e 65 77 5f 53 41 50 09 20 20 ┆ ! ! ! PE_new_SAP ┆
0x7ac0…7ae0 20 21 20 20 20 20 20 20 20 20 20 21 09 20 20 20 20 20 50 45 5f 72 65 73 65 74 09 09 09 09 21 0d ┆ ! ! PE_reset ! ┆
0x7ae0…7b00 0a 09 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 21 20 20 20 20 20 20 20 ┆ ----------------------! ┆
0x7b00…7b20 20 20 21 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 09 09 21 0d 0a ┆ !------------------------ ! ┆
0x7b20…7b40 09 21 20 20 20 3c 52 45 53 45 54 3e 09 09 09 3c 52 41 43 4b 3e 09 09 21 09 09 21 0d 0a 09 21 20 ┆ ! <RESET> <RACK> ! ! ! ┆
0x7b40…7b60 20 20 3c 43 4f 4e 4e 45 43 54 5f 69 6e 64 69 63 61 74 69 6f 6e 3e 09 09 3c 43 4f 4e 4e 45 43 54 ┆ <CONNECT_indication> <CONNECT┆
0x7b60…7b80 5f 69 6e 64 69 63 61 74 69 6f 6e 3e 09 21 09 09 21 0d 0a 09 21 09 09 09 09 09 09 21 09 09 21 0d ┆_indication> ! ! ! ! ! ┆
0x7b80…7ba0 0a a1 09 76 09 20 e1 09 09 09 09 a1 09 76 09 20 e1 09 21 0d 0a 21 09 09 21 09 20 20 20 20 20 50 ┆ v v ! ! ! P┆
0x7ba0…7bc0 45 5f 72 61 63 6b 09 09 21 09 09 21 09 21 0d 0a 21 20 52 45 53 45 54 54 49 4e 47 09 21 2d 2d 2d ┆E_rack ! ! ! ! RESETTING !---┆
0x7bc0…7be0 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d ┆--------------------------------┆
0x7be0…7c00 2d 2d 2d 2d 2d 2d 3e 21 20 20 20 44 41 54 41 20 20 20 20 21 09 21 0d 0a a1 21 09 09 21 e1 09 09 ┆------>! DATA ! ! ! ! ┆
0x7c00…7c20 (62,) 09 09 a1 21 09 09 21 e1 09 21 0d 0a 20 20 20 21 20 20 20 20 20 21 09 20 20 20 20 20 50 45 5f 6e ┆ ! ! ! ! ! PE_n┆
0x7c20…7c40 65 77 5f 53 41 50 09 09 50 45 5f 6e 65 77 5f 53 41 50 09 20 20 21 20 20 20 21 20 20 20 21 09 09 ┆ew_SAP PE_new_SAP ! ! ! ┆
0x7c40…7c60 21 0d 0a 20 20 20 21 20 20 20 20 20 21 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d ┆! ! !-------------------┆
0x7c60…7c80 2d 2d 2d 3e 20 3c 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 21 20 20 20 ┆---> <----------------------! ┆
0x7c80…7ca0 21 20 20 20 21 09 09 21 0d 0a 20 20 20 21 09 09 09 09 21 09 09 20 20 20 20 20 20 21 20 20 20 21 ┆! ! ! ! ! ! !┆
0x7ca0…7cc0 09 09 21 0d 0a 20 20 20 21 09 09 09 09 21 09 20 20 50 45 5f 72 65 73 65 74 09 20 20 20 20 20 20 ┆ ! ! ! PE_reset ┆
0x7cc0…7ce0 21 20 20 20 21 09 09 21 0d 0a 20 20 20 21 09 09 09 09 21 3c 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d ┆! ! ! ! !<------------┆
0x7ce0…7d00 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 21 20 20 20 21 09 09 21 0d 0a 20 20 20 21 09 09 09 09 ┆--------------! ! ! ! ┆
0x7d00…7d20 21 09 09 09 20 20 20 21 09 09 21 0d 0a 20 20 20 21 09 09 20 20 67 69 76 65 5f 75 70 09 09 21 09 ┆! ! ! ! give_up ! ┆
0x7d20…7d40 20 20 20 20 67 69 76 65 5f 75 70 09 09 20 20 20 21 09 09 21 0d 0a 20 20 20 21 2d 2d 2d 2d 2d 2d ┆ give_up ! ! !------┆
0x7d40…7d60 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 3e 21 3c 2d 2d 2d 2d 2d 2d 2d ┆---------------------->!<-------┆
0x7d60…7d80 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 21 09 09 21 0d 0a 09 09 09 ┆-----------------------! ! ┆
0x7d80…7da0 09 21 09 09 09 09 09 21 0d 0a 09 09 09 09 21 3c 44 49 53 43 4f 4e 4e 45 43 54 5f 69 6e 64 69 63 ┆ ! ! !<DISCONNECT_indic┆
0x7da0…7dc0 61 74 69 6f 6e 3e 09 09 09 21 0d 0a 09 09 09 09 21 09 09 09 09 09 21 0d 0a 09 09 09 a1 09 76 09 ┆ation> ! ! ! v ┆
0x7dc0…7de0 20 e1 09 09 09 09 21 0d 0a 09 09 09 21 09 09 21 20 20 20 20 20 53 50 5f 64 61 63 6b 09 09 09 09 ┆ ! ! ! SP_dack ┆
0x7de0…7e00 21 0d 0a 09 09 09 21 20 44 49 53 43 4f 4e 4e 45 43 54 49 4e 47 09 21 2d 2d 2d 2d 2d 2d 2d 2d 2d ┆! ! DISCONNECTING !---------┆
0x7e00…7e20 (63,) 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 0d 0a 09 09 09 a1 21 09 09 21 0d 0a ┆-------------------- ! ! ┆
0x7e20…7e59 Params {
0x7e20…7e59 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0x7e20…7e59 00 00 00 00 00 00 00 00 05 0f 19 23 2d 37 41 4b 55 5f 69 73 7d 87 91 ff 04 ┆ #-7AKU_iså ┆
0x7e20…7e59 }
0x7e59…7e92 Params {
0x7e59…7e92 04 00 2d 4e 0c 00 06 00 00 00 00 02 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0x7e59…7e92 00 00 00 00 00 00 00 00 07 0d 1a 22 2a 38 3f 44 47 4b 55 5f 69 73 7d ff 04 ┆ "*8?DGKU_iså ┆
0x7e59…7e92 }
0x7e92…7ea0 0a 0d 0a 46 69 67 75 72 65 20 31 3a 20 53 ┆ Figure 1: S┆
0x7ea0…7ec0 74 61 74 65 20 67 72 61 70 68 20 66 6f 72 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 2e 0d 0a 0f 0a ┆tate graph for a connection. ┆
0x7ec0…7ee0 0d 0a 41 20 67 65 6e 65 72 61 6c 20 70 72 6f 63 65 64 75 72 65 20 61 70 70 6c 69 65 73 20 74 6f ┆ A general procedure applies to┆
0x7ee0…7f00 20 74 68 65 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 66 20 70 72 6f 74 6f 63 6f 6c 20 65 6c ┆ the transmission of protocol el┆
0x7f00…7f20 65 6d 65 6e 74 73 20 66 6f 72 20 0a 77 68 69 63 68 20 61 6e 20 61 63 6b 6e 6f 77 6c 65 64 67 65 ┆ements for which an acknowledge┆
0x7f20…7f40 6d 65 6e 74 20 69 73 20 72 65 71 75 69 72 65 64 20 69 6e 20 74 68 65 20 66 6f 72 6d 20 6f 66 20 ┆ment is required in the form of ┆
0x7f40…7f60 61 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 0a 74 72 61 6e 73 6d 69 74 74 65 64 20 ┆a protocol element transmitted ┆
0x7f60…7f80 69 6e 20 74 68 65 20 6f 70 70 6f 73 69 74 65 20 64 69 72 65 63 74 69 6f 6e 2c 20 76 69 7a 2e 20 ┆in the opposite direction, viz. ┆
0x7f80…7fa0 52 45 53 45 54 20 61 6e 64 20 44 41 54 41 20 77 68 69 63 68 20 61 72 65 20 0a 61 63 6b 6e 6f 77 ┆RESET and DATA which are acknow┆
0x7fa0…7fc0 6c 65 64 67 65 64 20 62 79 20 52 41 43 4b 20 61 6e 64 20 41 43 4b 2c 20 72 65 73 70 65 63 74 69 ┆ledged by RACK and ACK, respecti┆
0x7fc0…7fe0 76 65 6c 79 2e 20 a1 49 6e 69 74 69 61 74 69 6e 67 e1 20 74 68 65 20 a1 74 72 61 6e 73 6d 69 73 ┆vely. Initiating the transmis┆
0x7fe0…8000 73 69 6f 6e e1 20 0a 6f 66 20 6f 6e 65 20 6f 66 20 74 68 65 73 65 20 65 6c 65 6d 65 6e 74 73 20 ┆sion of one of these elements ┆
0x8000…8020 (64,) 6d 65 61 6e 73 3a 20 69 6e 69 74 69 61 6c 69 7a 69 6e 67 20 74 68 65 20 72 65 74 72 61 6e 73 6d ┆means: initializing the retransm┆
0x8020…8040 69 73 73 69 6f 6e 20 63 6f 75 6e 74 65 72 2c 20 0a 73 74 61 72 74 69 6e 67 20 74 68 65 20 61 63 ┆ission counter, starting the ac┆
0x8040…8060 6b 6e 6f 77 6c 65 64 67 65 6d 65 6e 74 20 74 69 6d 65 72 2c 20 61 6e 64 20 61 63 74 75 61 6c 6c ┆knowledgement timer, and actuall┆
0x8060…8080 79 20 74 72 61 6e 73 6d 69 74 74 69 6e 67 20 74 68 65 20 0a 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 ┆y transmitting the protocol ele┆
0x8080…80a0 6d 65 6e 74 2e 20 57 68 65 6e 20 74 68 65 20 61 63 6b 6e 6f 77 6c 65 64 67 69 6e 67 20 70 72 6f ┆ment. When the acknowledging pro┆
0x80a0…80c0 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 61 72 72 69 76 65 73 2c 20 74 68 65 20 0a 74 72 61 6e ┆tocol element arrives, the tran┆
0x80c0…80e0 73 6d 69 73 73 69 6f 6e 20 69 73 20 63 6f 6e 73 69 64 65 72 65 64 20 73 75 63 63 65 73 73 66 75 ┆smission is considered successfu┆
0x80e0…8100 6c 6c 79 20 63 6f 6d 70 6c 65 74 65 64 2c 20 61 6e 64 20 74 68 65 20 74 69 6d 65 72 20 69 73 20 ┆lly completed, and the timer is ┆
0x8100…8120 0a 73 74 6f 70 70 65 64 2e 20 49 66 2c 20 6f 6e 20 74 68 65 20 6f 74 68 65 72 20 68 61 6e 64 2c ┆ stopped. If, on the other hand,┆
0x8120…8140 20 74 68 65 20 61 63 6b 6e 6f 77 6c 65 64 67 65 6d 65 6e 74 20 74 69 6d 65 72 20 65 78 70 69 72 ┆ the acknowledgement timer expir┆
0x8140…8160 65 73 2c 20 74 68 65 20 0a 72 65 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 63 6f 75 6e 74 65 72 20 ┆es, the retransmission counter ┆
0x8160…8180 69 73 20 64 65 63 72 65 6d 65 6e 74 65 64 2c 20 61 6e 64 20 69 66 20 69 74 20 77 61 73 20 65 78 ┆is decremented, and if it was ex┆
0x8180…81a0 68 61 75 73 74 65 64 2c 20 69 2e 65 2e 20 0a 62 65 63 61 6d 65 20 7a 65 72 6f 2c 20 74 68 65 20 ┆hausted, i.e. became zero, the ┆
0x81a0…81c0 63 6f 6e 6e 65 63 74 69 6f 6e 20 69 73 20 67 69 76 65 6e 20 75 70 20 28 67 69 76 65 5f 75 70 20 ┆connection is given up (give_up ┆
0x81c0…81e0 65 76 65 6e 74 29 2e 20 4f 74 68 65 72 77 69 73 65 2c 20 74 68 65 20 0a 74 69 6d 65 72 20 69 73 ┆event). Otherwise, the timer is┆
0x81e0…8200 20 72 65 73 74 61 72 74 65 64 20 61 6e 64 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d ┆ restarted and the protocol elem┆
0x8200…8220 (65,) 65 6e 74 20 72 65 74 72 61 6e 73 6d 69 74 74 65 64 2e 0d 0a 0d 0a 54 68 65 72 65 20 69 73 20 6e ┆ent retransmitted. There is n┆
0x8220…8240 65 76 65 72 20 6d 6f 72 65 20 74 68 61 6e 20 6f 6e 65 20 6f 75 74 73 74 61 6e 64 69 6e 67 20 70 ┆ever more than one outstanding p┆
0x8240…8260 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 72 65 71 75 69 72 69 6e 67 20 0a 61 63 6b 6e 6f ┆rotocol element requiring ackno┆
0x8260…8280 77 6c 65 64 67 65 6d 65 6e 74 2c 20 69 2e 65 2e 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 66 ┆wledgement, i.e. transmission of┆
0x8280…82a0 20 61 20 52 45 53 45 54 20 6f 72 20 44 41 54 41 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e ┆ a RESET or DATA protocol elemen┆
0x82a0…82c0 74 20 0a 8c 83 c0 0a 69 73 20 6e 6f 74 20 69 6e 69 74 69 61 74 65 64 20 75 6e 74 69 6c 20 74 72 ┆t is not initiated until tr┆
0x82c0…82e0 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 66 20 74 68 65 20 70 72 65 76 69 6f 75 73 20 65 6c 65 6d 65 ┆ansmission of the previous eleme┆
0x82e0…8300 6e 74 20 69 73 20 0a 63 6f 6d 70 6c 65 74 65 64 2e 20 46 6f 72 20 74 68 69 73 20 72 65 61 73 6f ┆nt is completed. For this reaso┆
0x8300…8320 6e 20 61 20 44 41 54 41 2e 72 65 71 75 65 73 74 20 70 72 69 6d 69 74 69 76 65 20 63 6f 6e 74 61 ┆n a DATA.request primitive conta┆
0x8320…8340 69 6e 69 6e 67 20 61 6e 20 52 43 4c 4c 43 20 0a 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 ┆ining an RCLLC service data uni┆
0x8340…8360 74 20 66 6f 72 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 6e 20 61 20 63 6f 6e 6e 65 63 74 69 ┆t for transmission on a connecti┆
0x8360…8380 6f 6e 20 6d 61 79 20 62 65 20 61 63 63 65 70 74 65 64 20 77 68 69 6c 65 20 0a 61 6e 20 75 6e 61 ┆on may be accepted while an una┆
0x8380…83a0 63 6b 6e 6f 77 6c 65 64 67 65 64 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 ┆cknowledged protocol element is ┆
0x83a0…83c0 6f 75 74 73 74 61 6e 64 69 6e 67 2c 20 62 75 74 20 69 74 20 77 69 6c 6c 20 74 68 65 6e 20 62 65 ┆outstanding, but it will then be┆
0x83c0…83e0 20 0a 71 75 65 75 65 64 20 28 62 79 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 29 20 66 ┆ queued (by the RCLLC entity) f┆
0x83e0…8400 6f 72 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 72 61 74 68 65 72 20 74 68 61 6e 20 70 72 6f 63 ┆or transmission rather than proc┆
0x8400…8420 (66,) 65 73 73 65 64 20 0a 69 6d 6d 65 64 69 61 74 65 6c 79 2e 0d 0a 0d 0a 54 68 65 20 72 65 6d 61 69 ┆essed immediately. The remai┆
0x8420…8440 6e 69 6e 67 20 70 61 72 74 20 6f 66 20 74 68 69 73 20 73 65 63 74 69 6f 6e 20 63 6f 6e 74 61 69 ┆ning part of this section contai┆
0x8440…8460 6e 73 20 61 20 64 69 73 63 75 73 73 69 6f 6e 20 6f 66 20 74 68 65 20 6d 65 61 6e 69 6e 67 20 0a ┆ns a discussion of the meaning ┆
0x8460…8480 6f 66 20 65 61 63 68 20 73 74 61 74 65 20 6f 66 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 28 65 ┆of each state of a connection (e┆
0x8480…84a0 6e 64 2d 70 6f 69 6e 74 29 20 61 6e 64 20 74 68 65 20 70 72 6f 63 65 64 75 72 65 73 20 66 6f 6c ┆nd-point) and the procedures fol┆
0x84a0…84c0 6c 6f 77 65 64 20 62 79 20 0a 61 6e 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 69 6e 20 65 61 63 ┆lowed by an RCLLC entity in eac┆
0x84c0…84e0 68 20 73 74 61 74 65 2e 0d 0a 0d 0a 55 4e 4b 4e 4f 57 4e 0d 0a 0d 0a 54 68 65 20 52 43 4c 4c 43 ┆h state. UNKNOWN The RCLLC┆
0x84e0…8500 20 65 6e 74 69 74 79 20 68 61 73 20 6e 6f 20 6b 6e 6f 77 6c 65 64 67 65 20 6f 66 20 74 68 65 20 ┆ entity has no knowledge of the ┆
0x8500…8520 72 65 6d 6f 74 65 20 53 41 50 2c 20 62 75 74 20 69 73 20 72 65 61 64 79 20 74 6f 20 0a 65 73 74 ┆remote SAP, but is ready to est┆
0x8520…8540 61 62 6c 69 73 68 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 2e 20 4e 6f 20 73 65 72 76 69 63 65 20 ┆ablish a connection. No service ┆
0x8540…8560 70 72 69 6d 69 74 69 76 65 73 20 61 72 65 20 61 63 63 65 70 74 65 64 20 61 6e 64 20 61 6c 6c 20 ┆primitives are accepted and all ┆
0x8560…8580 0a 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 65 78 63 65 70 74 20 41 43 54 49 56 45 ┆ protocol elements except ACTIVE┆
0x8580…85a0 5f 53 41 50 20 61 6e 64 20 52 45 53 45 54 20 61 72 65 20 64 69 73 63 61 72 64 65 64 2e 0d 0a 0d ┆_SAP and RESET are discarded. ┆
0x85a0…85c0 0a 41 20 72 65 63 65 69 76 65 64 20 41 43 54 49 56 45 5f 53 41 50 20 70 72 6f 74 6f 63 6f 6c 20 ┆ A received ACTIVE_SAP protocol ┆
0x85c0…85e0 65 6c 65 6d 65 6e 74 20 28 77 69 74 68 20 6d 61 74 63 68 69 6e 67 20 53 41 50 20 6d 61 73 6b 29 ┆element (with matching SAP mask)┆
0x85e0…8600 20 63 6f 6e 73 74 69 80 0a 74 75 74 65 73 20 61 20 50 45 5f 6e 65 77 5f 53 41 50 20 65 76 65 6e ┆ consti tutes a PE_new_SAP even┆
0x8600…8620 (67,) 74 2e 20 49 74 20 63 61 75 73 65 73 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 74 6f ┆t. It causes the RCLLC entity to┆
0x8620…8640 20 65 73 74 61 62 6c 69 73 68 20 61 20 0a 63 6f 6e 6e 65 63 74 69 6f 6e 20 74 6f 20 74 68 65 20 ┆ establish a connection to the ┆
0x8640…8660 72 65 6d 6f 74 65 20 53 41 50 20 62 79 20 73 74 61 72 74 69 6e 67 20 74 68 65 20 53 41 50 20 61 ┆remote SAP by starting the SAP a┆
0x8660…8680 6c 69 76 65 20 74 69 6d 65 72 2c 20 69 6e 69 74 69 61 74 69 6e 67 20 0a 74 68 65 20 74 72 61 6e ┆live timer, initiating the tran┆
0x8680…86a0 73 6d 69 73 73 69 6f 6e 20 6f 66 20 61 20 52 45 53 45 54 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 ┆smission of a RESET protocol ele┆
0x86a0…86c0 6d 65 6e 74 2c 20 72 65 73 65 74 74 69 6e 67 20 74 68 65 20 73 65 71 75 65 6e 63 65 20 0a 63 6f ┆ment, resetting the sequence co┆
0x86c0…86e0 75 6e 74 65 72 73 2c 20 70 61 73 73 69 6e 67 20 61 20 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 61 ┆unters, passing a CONNECT.indica┆
0x86e0…8700 74 69 6f 6e 20 70 72 69 6d 69 74 69 76 65 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 2c 20 61 6e ┆tion primitive to the client, an┆
0x8700…8720 64 20 0a 63 68 61 6e 67 69 6e 67 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 73 74 61 74 65 ┆d changing the connection state┆
0x8720…8740 20 74 6f 20 52 45 53 45 54 54 49 4e 47 2e 0d 0a 0d 0a 41 20 72 65 63 65 69 76 65 64 20 52 45 53 ┆ to RESETTING. A received RES┆
0x8740…8760 45 54 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 63 6f 6e 73 74 69 74 75 74 65 73 20 ┆ET protocol element constitutes ┆
0x8760…8780 61 20 50 45 5f 72 65 73 65 74 20 65 76 65 6e 74 20 69 6e 64 69 80 0a 63 61 74 69 6e 67 20 74 68 ┆a PE_reset event indi cating th┆
0x8780…87a0 61 74 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 68 61 73 20 62 65 63 6f 6d 65 20 6b 6e 6f 77 ┆at the local SAP has become know┆
0x87a0…87c0 6e 20 74 6f 20 74 68 65 20 72 65 6d 6f 74 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 0a 61 6e ┆n to the remote RCLLC entity an┆
0x87c0…87e0 64 20 63 61 75 73 65 64 20 69 74 20 74 6f 20 65 73 74 61 62 6c 69 73 68 20 61 20 63 6f 6e 6e 65 ┆d caused it to establish a conne┆
0x87e0…8800 63 74 69 6f 6e 2e 20 54 68 65 20 6c 6f 63 61 6c 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 77 69 ┆ction. The local RCLLC entity wi┆
0x8800…8820 (68,) 6c 6c 20 0a 65 73 74 61 62 6c 69 73 68 20 69 74 73 20 65 6e 64 20 6f 66 20 74 68 65 20 63 6f 6e ┆ll establish its end of the con┆
0x8820…8840 6e 65 63 74 69 6f 6e 20 62 79 20 73 74 61 72 74 69 6e 67 20 74 68 65 20 53 41 50 20 61 6c 69 76 ┆nection by starting the SAP aliv┆
0x8840…8860 65 20 74 69 6d 65 72 2c 20 0a 74 72 61 6e 73 6d 69 74 74 69 6e 67 20 61 20 52 41 43 4b 20 70 72 ┆e timer, transmitting a RACK pr┆
0x8860…8880 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 74 6f 20 61 63 6b 6e 6f 77 6c 65 64 67 65 20 52 45 ┆otocol element to acknowledge RE┆
0x8880…88a0 53 45 54 2c 20 72 65 73 65 74 74 69 6e 67 20 74 68 65 20 0a 73 65 71 75 65 6e 63 65 20 63 6f 75 ┆SET, resetting the sequence cou┆
0x88a0…88c0 6e 74 65 72 73 2c 20 70 61 73 73 69 6e 67 20 61 20 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 61 74 ┆nters, passing a CONNECT.indicat┆
0x88c0…88e0 69 6f 6e 20 70 72 69 6d 69 74 69 76 65 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 2c 20 0a 61 6e ┆ion primitive to the client, an┆
0x88e0…8900 64 20 63 68 61 6e 67 69 6e 67 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 73 74 61 74 65 20 ┆d changing the connection state ┆
0x8900…8920 74 6f 20 44 41 54 41 2e 0d 0a 0d 0a 52 45 53 45 54 54 49 4e 47 0d 0a 0d 0a 54 68 65 20 52 43 4c ┆to DATA. RESETTING The RCL┆
0x8920…8940 4c 43 20 65 6e 74 69 74 79 20 68 61 73 20 65 73 74 61 62 6c 69 73 68 65 64 20 74 68 65 20 63 6f ┆LC entity has established the co┆
0x8940…8960 6e 6e 65 63 74 69 6f 6e 20 62 79 20 69 6e 69 74 69 61 74 69 6e 67 20 74 68 65 20 74 72 61 6e 73 ┆nnection by initiating the trans┆
0x8960…8980 80 0a 6d 69 73 73 69 6f 6e 20 6f 66 20 61 20 52 45 53 45 54 20 70 72 6f 74 6f 63 6f 6c 20 65 6c ┆ mission of a RESET protocol el┆
0x8980…89a0 65 6d 65 6e 74 2e 20 54 68 65 20 73 74 61 74 65 20 69 73 20 75 73 65 64 20 74 6f 20 77 61 69 74 ┆ement. The state is used to wait┆
0x89a0…89c0 20 66 6f 72 20 74 68 65 20 0a 61 63 6b 6e 6f 77 6c 65 64 67 69 6e 67 20 52 41 43 4b 20 70 72 6f ┆ for the acknowledging RACK pro┆
0x89c0…89e0 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 61 66 74 65 72 20 77 68 69 63 68 20 64 61 74 61 20 6d ┆tocol element after which data m┆
0x89e0…8a00 61 79 20 62 65 20 74 72 61 6e 73 6d 69 74 74 65 64 20 0a 69 6e 20 62 6f 74 68 20 64 69 72 65 63 ┆ay be transmitted in both direc┆
0x8a00…8a20 (69,) 74 69 6f 6e 73 2e 0d 0a 0d 0a 8c 83 d4 0a 44 41 54 41 2e 72 65 71 75 65 73 74 20 70 72 69 6d 69 ┆tions. DATA.request primi┆
0x8a20…8a40 74 69 76 65 73 20 61 72 65 20 61 63 63 65 70 74 65 64 20 28 71 75 65 75 65 64 29 2e 20 44 49 53 ┆tives are accepted (queued). DIS┆
0x8a40…8a60 43 4f 4e 4e 45 43 54 2e 61 63 6b 6e 6f 77 6c 65 64 67 65 20 0a 70 72 69 6d 69 74 69 76 65 73 20 ┆CONNECT.acknowledge primitives ┆
0x8a60…8a80 61 72 65 20 64 69 73 63 61 72 64 65 64 2e 0d 0a 0d 0a 41 20 72 65 63 65 69 76 65 64 20 52 45 53 ┆are discarded. A received RES┆
0x8a80…8aa0 45 54 20 6f 72 20 52 41 43 4b 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 63 6f 6e 73 ┆ET or RACK protocol element cons┆
0x8aa0…8ac0 74 69 74 75 74 65 73 20 61 20 50 45 5f 72 61 63 6b 20 65 76 65 6e 74 20 0a 61 6e 64 20 63 61 75 ┆titutes a PE_rack event and cau┆
0x8ac0…8ae0 73 65 73 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 74 6f 20 63 68 61 6e 67 65 20 74 ┆ses the RCLLC entity to change t┆
0x8ae0…8b00 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 73 74 61 74 65 20 74 6f 20 44 41 54 41 2e 20 0a 52 45 ┆he connection state to DATA. RE┆
0x8b00…8b20 53 45 54 2c 20 77 68 69 63 68 20 6d 61 79 20 6f 63 63 75 72 20 69 66 20 52 45 53 45 54 20 70 72 ┆SET, which may occur if RESET pr┆
0x8b20…8b40 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 61 72 65 20 74 72 61 6e 73 6d 69 74 74 65 64 20 ┆otocol elements are transmitted ┆
0x8b40…8b60 69 6e 20 0a 62 6f 74 68 20 64 69 72 65 63 74 69 6f 6e 73 20 73 69 6d 75 6c 74 61 6e 65 6f 75 73 ┆in both directions simultaneous┆
0x8b60…8b80 6c 79 2c 20 69 73 20 61 6e 73 77 65 72 65 64 20 77 69 74 68 20 52 41 43 4b 2e 0d 0a 0d 0a 52 65 ┆ly, is answered with RACK. Re┆
0x8b80…8ba0 63 65 69 76 65 64 20 44 41 54 41 20 6f 72 20 41 43 4b 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d ┆ceived DATA or ACK protocol elem┆
0x8ba0…8bc0 65 6e 74 73 20 61 72 65 20 64 69 73 63 61 72 64 65 64 2e 0d 0a 0d 0a 49 66 20 61 20 50 45 5f 6e ┆ents are discarded. If a PE_n┆
0x8bc0…8be0 65 77 5f 53 41 50 20 65 76 65 6e 74 20 6f 63 63 75 72 73 20 28 63 66 2e 20 73 75 62 73 65 63 74 ┆ew_SAP event occurs (cf. subsect┆
0x8be0…8c00 69 6f 6e 20 35 2e 32 2e 31 29 2c 20 6f 72 20 69 66 20 74 68 65 20 0a 63 6f 6e 6e 65 63 74 69 6f ┆ion 5.2.1), or if the connectio┆
0x8c00…8c20 (70,) 6e 20 69 73 20 67 69 76 65 6e 20 75 70 2c 20 65 69 74 68 65 72 20 62 65 63 61 75 73 65 20 74 68 ┆n is given up, either because th┆
0x8c20…8c40 65 20 53 41 50 20 61 6c 69 76 65 20 74 69 6d 65 72 20 65 78 70 69 72 65 73 20 6f 72 20 0a 62 65 ┆e SAP alive timer expires or be┆
0x8c40…8c60 63 61 75 73 65 20 74 68 65 20 52 45 53 45 54 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 ┆cause the RESET protocol element┆
0x8c60…8c80 20 69 73 20 72 65 74 72 61 6e 73 6d 69 74 74 65 64 20 74 6f 20 65 78 68 61 75 73 74 69 6f 6e 2c ┆ is retransmitted to exhaustion,┆
0x8c80…8ca0 20 74 68 65 20 0a 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 77 69 6c 6c 20 70 61 73 73 20 61 20 44 ┆ the RCLLC entity will pass a D┆
0x8ca0…8cc0 49 53 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 61 74 69 6f 6e 20 70 72 69 6d 69 74 69 76 65 20 74 ┆ISCONNECT.indication primitive t┆
0x8cc0…8ce0 6f 20 74 68 65 20 63 6c 69 65 6e 74 20 0a 61 6e 64 20 63 68 61 6e 67 65 20 74 68 65 20 63 6f 6e ┆o the client and change the con┆
0x8ce0…8d00 6e 65 63 74 69 6f 6e 20 73 74 61 74 65 20 74 6f 20 44 49 53 43 4f 4e 4e 45 43 54 49 4e 47 2e 0d ┆nection state to DISCONNECTING. ┆
0x8d00…8d20 0a 0d 0a 44 41 54 41 0d 0a 0d 0a 54 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 68 61 73 20 62 65 ┆ DATA The connection has be┆
0x8d20…8d40 65 6e 20 63 6f 6d 70 6c 65 74 65 6c 79 20 65 73 74 61 62 6c 69 73 68 65 64 20 74 68 72 6f 75 67 ┆en completely established throug┆
0x8d40…8d60 68 20 74 68 65 20 65 78 63 68 61 6e 67 65 20 6f 66 20 0a 52 45 53 45 54 20 61 6e 64 20 52 41 43 ┆h the exchange of RESET and RAC┆
0x8d60…8d80 4b 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 2e 20 49 6e 20 74 68 69 73 20 73 74 61 ┆K protocol elements. In this sta┆
0x8d80…8da0 74 65 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 74 73 20 0a 61 72 65 ┆te RCLLC service data units are┆
0x8da0…8dc0 20 74 72 61 6e 73 66 65 72 72 65 64 20 62 65 74 77 65 65 6e 20 74 68 65 20 74 77 6f 20 53 41 50 ┆ transferred between the two SAP┆
0x8dc0…8de0 73 20 74 68 72 6f 75 67 68 20 74 68 65 20 65 78 63 68 61 6e 67 65 20 6f 66 20 44 41 54 41 20 61 ┆s through the exchange of DATA a┆
0x8de0…8e00 6e 64 20 0a 41 43 4b 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 62 65 74 77 65 65 ┆nd ACK protocol elements betwee┆
0x8e00…8e20 (71,) 6e 20 74 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 69 65 73 2e 0d 0a 0d 0a 45 61 63 68 20 44 41 ┆n the RCLLC entities. Each DA┆
0x8e20…8e40 54 41 2e 72 65 71 75 65 73 74 20 70 72 69 6d 69 74 69 76 65 20 72 65 63 65 69 76 65 64 20 66 72 ┆TA.request primitive received fr┆
0x8e40…8e60 6f 6d 20 74 68 65 20 63 6c 69 65 6e 74 20 63 61 75 73 65 73 20 69 6e 69 74 69 61 74 69 6f 6e 20 ┆om the client causes initiation ┆
0x8e60…8e80 0a 6f 66 20 74 68 65 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 66 20 61 20 44 41 54 41 20 70 ┆ of the transmission of a DATA p┆
0x8e80…8ea0 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 63 6f 6e 74 61 69 6e 69 6e 67 20 74 68 65 20 73 ┆rotocol element containing the s┆
0x8ea0…8ec0 65 72 76 69 63 65 20 0a 64 61 74 61 20 75 6e 69 74 20 70 61 73 73 65 64 20 61 73 20 61 20 70 61 ┆ervice data unit passed as a pa┆
0x8ec0…8ee0 72 61 6d 65 74 65 72 20 6f 66 20 74 68 65 20 70 72 69 6d 69 74 69 76 65 2e 20 54 68 65 20 73 65 ┆rameter of the primitive. The se┆
0x8ee0…8f00 71 75 65 6e 63 65 20 6e 75 6d 62 65 72 20 6f 66 20 0a 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 ┆quence number of the protocol e┆
0x8f00…8f20 6c 65 6d 65 6e 74 20 69 73 20 73 65 74 20 65 71 75 61 6c 20 74 6f 20 74 68 65 20 76 61 6c 75 65 ┆lement is set equal to the value┆
0x8f20…8f40 20 6f 66 20 4e 28 53 29 2c 20 61 6e 64 20 73 75 62 73 65 71 75 65 6e 74 6c 79 20 0a 4e 28 53 29 ┆ of N(S), and subsequently N(S)┆
0x8f40…8f60 20 69 73 20 69 6e 63 72 65 6d 65 6e 74 65 64 20 6d 6f 64 75 6c 6f 20 32 2e 20 49 6e 69 74 69 61 ┆ is incremented modulo 2. Initia┆
0x8f60…8f80 74 69 6f 6e 20 6f 66 20 74 68 65 20 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 6f 66 20 74 68 65 20 ┆tion of the transmission of the ┆
0x8f80…8fa0 0a 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 74 61 6b 65 73 20 70 6c 61 63 65 3a 20 65 ┆ protocol element takes place: e┆
0x8fa0…8fc0 69 74 68 65 72 20 77 68 65 6e 20 61 6e 20 41 43 4b 20 6f 72 20 52 41 43 4b 20 70 72 6f 74 6f 63 ┆ither when an ACK or RACK protoc┆
0x8fc0…8fe0 6f 6c 20 0a 65 6c 65 6d 65 6e 74 20 69 73 20 72 65 63 65 69 76 65 64 20 6d 61 72 6b 69 6e 67 20 ┆ol element is received marking ┆
0x8fe0…9000 74 68 65 20 73 75 63 63 65 73 73 66 75 6c 20 63 6f 6d 70 6c 65 74 69 6f 6e 20 6f 66 20 61 20 70 ┆the successful completion of a p┆
0x9000…9020 (72,) 72 65 76 69 6f 75 73 20 0a 74 72 61 6e 73 6d 69 73 73 69 6f 6e 20 70 72 6f 76 69 64 65 64 20 61 ┆revious transmission provided a┆
0x9020…9040 20 6e 6f 6e 2d 65 6d 70 74 79 20 71 75 65 75 65 20 6f 66 20 73 65 72 76 69 63 65 20 64 61 74 61 ┆ non-empty queue of service data┆
0x9040…9060 20 75 6e 69 74 73 20 61 72 65 20 0a 61 77 61 69 74 69 6e 67 20 74 72 61 6e 73 6d 69 73 73 69 6f ┆ units are awaiting transmissio┆
0x9060…9080 6e 3b 20 6f 72 20 69 6d 6d 65 64 69 61 74 65 6c 79 20 75 70 6f 6e 20 72 65 63 65 69 70 74 20 6f ┆n; or immediately upon receipt o┆
0x9080…90a0 66 20 74 68 65 20 44 41 54 41 2e 72 65 71 75 65 73 74 20 0a 70 72 69 6d 69 74 69 76 65 20 69 66 ┆f the DATA.request primitive if┆
0x90a0…90c0 20 74 68 65 72 65 20 69 73 20 6e 6f 20 6f 75 74 73 74 61 6e 64 69 6e 67 20 70 72 6f 74 6f 63 6f ┆ there is no outstanding protoco┆
0x90c0…90e0 6c 20 65 6c 65 6d 65 6e 74 20 61 77 61 69 74 69 6e 67 20 0a 61 63 6b 6e 6f 77 6c 65 64 67 65 6d ┆l element awaiting acknowledgem┆
0x90e0…9100 65 6e 74 2e 0d 0a 0d 0a 57 68 65 6e 20 61 20 44 41 54 41 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 ┆ent. When a DATA protocol ele┆
0x9100…9120 6d 65 6e 74 20 69 73 20 72 65 63 65 69 76 65 64 2c 20 69 74 73 20 73 65 71 75 65 6e 63 65 20 6e ┆ment is received, its sequence n┆
0x9120…9140 75 6d 62 65 72 20 69 73 20 0a 63 6f 6d 70 61 72 65 64 20 74 6f 20 74 68 65 20 76 61 6c 75 65 20 ┆umber is compared to the value ┆
0x9140…9160 6f 66 20 4e 28 52 29 2e 20 49 66 20 74 68 65 79 20 61 72 65 20 65 71 75 61 6c 20 74 68 65 20 72 ┆of N(R). If they are equal the r┆
0x9160…9180 65 63 65 69 76 65 64 20 73 65 72 76 69 63 65 20 0a 64 61 74 61 20 75 6e 69 74 20 69 73 20 70 61 ┆eceived service data unit is pa┆
0x9180…91a0 73 73 65 64 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 20 62 79 20 6d 65 61 6e 73 20 6f 66 20 61 ┆ssed to the client by means of a┆
0x91a0…91c0 20 44 41 54 41 2e 69 6e 64 69 63 61 74 69 6f 6e 20 70 72 69 6d 69 80 0a 8c 83 c8 0a 74 69 76 65 ┆ DATA.indication primi tive┆
0x91c0…91e0 2c 20 61 6e 64 20 4e 28 52 29 20 69 73 20 69 6e 63 72 65 6d 65 6e 74 65 64 20 6d 6f 64 75 6c 6f ┆, and N(R) is incremented modulo┆
0x91e0…9200 20 32 2e 20 4f 74 68 65 72 77 69 73 65 2c 20 74 68 65 20 73 65 72 76 69 63 65 20 64 61 74 61 20 ┆ 2. Otherwise, the service data ┆
0x9200…9220 (73,) 75 6e 69 74 20 0a 69 73 20 64 69 73 63 61 72 64 65 64 2e 20 49 6e 20 62 6f 74 68 20 63 61 73 65 ┆unit is discarded. In both case┆
0x9220…9240 73 20 61 6e 20 41 43 4b 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 77 69 74 68 20 73 ┆s an ACK protocol element with s┆
0x9240…9260 65 71 75 65 6e 63 65 20 6e 75 6d 62 65 72 20 0a 65 71 75 61 6c 20 74 6f 20 74 68 61 74 20 6f 66 ┆equence number equal to that of┆
0x9260…9280 20 74 68 65 20 44 41 54 41 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 74 72 ┆ the DATA protocol element is tr┆
0x9280…92a0 61 6e 73 6d 69 74 74 65 64 20 74 6f 20 74 68 65 20 72 65 6d 6f 74 65 20 0a 53 41 50 20 69 6e 20 ┆ansmitted to the remote SAP in ┆
0x92a0…92c0 6f 72 64 65 72 20 74 6f 20 61 63 6b 6e 6f 77 6c 65 64 67 65 20 72 65 63 65 69 70 74 2e 0d 0a 0d ┆order to acknowledge receipt. ┆
0x92c0…92e0 0a 49 66 20 61 20 52 41 43 4b 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 6f 72 20 61 ┆ If a RACK protocol element or a┆
0x92e0…9300 20 44 49 53 43 4f 4e 4e 45 43 54 2e 61 63 6b 6e 6f 77 6c 65 64 67 65 20 73 65 72 76 69 63 65 20 ┆ DISCONNECT.acknowledge service ┆
0x9300…9320 70 72 69 6d 69 74 69 76 65 20 0d 0a 69 73 20 72 65 63 65 69 76 65 64 2c 20 69 74 20 69 73 20 64 ┆primitive is received, it is d┆
0x9320…9340 69 73 63 61 72 64 65 64 2e 0d 0a 0d 0a 49 66 20 61 20 50 45 5f 6e 65 77 5f 53 41 50 20 65 76 65 ┆iscarded. If a PE_new_SAP eve┆
0x9340…9360 6e 74 20 6f 63 63 75 72 73 20 28 63 66 2e 20 73 75 62 73 65 63 74 69 6f 6e 20 35 2e 32 2e 31 29 ┆nt occurs (cf. subsection 5.2.1)┆
0x9360…9380 2c 20 69 66 20 61 20 52 45 53 45 54 20 70 72 6f 74 6f 63 6f 6c 20 0a 65 6c 65 6d 65 6e 74 20 69 ┆, if a RESET protocol element i┆
0x9380…93a0 73 20 72 65 63 65 69 76 65 64 2c 20 6f 72 20 69 66 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e ┆s received, or if the connection┆
0x93a0…93c0 20 69 73 20 67 69 76 65 6e 20 75 70 2c 20 65 69 74 68 65 72 20 62 65 63 61 75 73 65 20 0a 74 68 ┆ is given up, either because th┆
0x93c0…93e0 65 20 53 41 50 20 61 6c 69 76 65 20 74 69 6d 65 72 20 65 78 70 69 72 65 73 20 6f 72 20 62 65 63 ┆e SAP alive timer expires or bec┆
0x93e0…9400 61 75 73 65 20 61 20 44 41 54 41 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 ┆ause a DATA protocol element is ┆
0x9400…9420 (74,) 72 65 80 0a 74 72 61 6e 73 6d 69 74 74 65 64 20 74 6f 20 65 78 68 61 75 73 74 69 6f 6e 2c 20 74 ┆re transmitted to exhaustion, t┆
0x9420…9440 68 65 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 77 69 6c 6c 20 70 61 73 73 20 61 20 0a 44 49 53 ┆he RCLLC entity will pass a DIS┆
0x9440…9460 43 4f 4e 4e 45 43 54 2e 69 6e 64 69 63 61 74 69 6f 6e 20 70 72 69 6d 69 74 69 76 65 20 74 6f 20 ┆CONNECT.indication primitive to ┆
0x9460…9480 74 68 65 20 63 6c 69 65 6e 74 20 61 6e 64 20 63 68 61 6e 67 65 20 74 68 65 20 63 6f 6e 6e 65 63 ┆the client and change the connec┆
0x9480…94a0 74 69 6f 6e 20 0a 73 74 61 74 65 20 74 6f 20 44 49 53 43 4f 4e 4e 45 43 54 49 4e 47 2e 0d 0a 0d ┆tion state to DISCONNECTING. ┆
0x94a0…94c0 0a 44 49 53 43 4f 4e 4e 45 43 54 49 4e 47 0d 0a 0d 0a 54 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e ┆ DISCONNECTING The connection┆
0x94c0…94e0 20 68 61 73 20 62 65 65 6e 20 64 69 73 63 6f 6e 6e 65 63 74 65 64 20 61 73 20 73 65 65 6e 20 66 ┆ has been disconnected as seen f┆
0x94e0…9500 72 6f 6d 20 74 68 65 20 70 6f 69 6e 74 20 6f 66 20 76 69 65 77 20 6f 66 20 0a 74 68 65 20 52 43 ┆rom the point of view of the RC┆
0x9500…9520 4c 4c 43 20 6c 61 79 65 72 2e 20 54 68 69 73 20 73 74 61 74 65 20 61 6c 6c 6f 77 73 20 74 68 65 ┆LLC layer. This state allows the┆
0x9520…9540 20 63 6c 69 65 6e 74 20 74 6f 20 64 65 63 69 64 65 20 77 68 65 6e 20 69 74 20 77 69 6c 6c 20 0a ┆ client to decide when it will ┆
0x9540…9560 61 63 63 65 70 74 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 74 6f 20 62 65 20 72 65 65 73 ┆accept the connection to be rees┆
0x9560…9580 74 61 62 6c 69 73 68 65 64 2e 0d 0a 0d 0a 41 6c 6c 20 72 65 63 65 69 76 65 64 20 70 72 6f 74 6f ┆tablished. All received proto┆
0x9580…95a0 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 61 6e 64 20 73 65 72 76 69 63 65 20 70 72 69 6d 69 74 69 ┆col elements and service primiti┆
0x95a0…95c0 76 65 73 20 61 72 65 20 64 69 73 63 61 72 64 65 64 20 0a 65 78 63 65 70 74 20 74 68 65 20 44 49 ┆ves are discarded except the DI┆
0x95c0…95e0 53 43 4f 4e 4e 45 43 54 2e 61 63 6b 6e 6f 77 6c 65 64 67 65 20 70 72 69 6d 69 74 76 65 2e 20 57 ┆SCONNECT.acknowledge primitve. W┆
0x95e0…9600 68 65 6e 20 74 68 69 73 20 70 72 69 6d 69 74 69 76 65 20 69 73 20 0a 72 65 63 65 69 76 65 64 20 ┆hen this primitive is received ┆
0x9600…9620 (75,) 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 73 74 61 74 65 20 69 73 20 63 68 61 6e 67 65 64 20 ┆the connection state is changed ┆
0x9620…962d 74 6f 20 55 4e 4b 4e 4f 57 4e 2e 0d 0a ┆to UNKNOWN. ┆
0x962d…9630 FormFeed {
0x962d…9630 0c 82 a0 ┆ ┆
0x962d…9630 }
0x9630…9640 0a a1 35 2e 20 20 20 20 20 52 43 4c 4c 43 20 50 ┆ 5. RCLLC P┆
0x9640…9660 52 4f 54 4f 43 4f 4c 20 45 4c 45 4d 45 4e 54 53 0d 0a 0d 0a 41 6c 6c 20 52 43 4c 4c 43 20 70 72 ┆ROTOCOL ELEMENTS All RCLLC pr┆
0x9660…9680 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 63 6f 6e 66 6f 72 6d 20 74 6f 20 74 68 65 20 73 ┆otocol elements conform to the s┆
0x9680…96a0 79 6e 74 61 78 20 66 6f 72 20 4c 4c 43 20 74 79 70 65 20 31 20 0a 70 72 6f 74 6f 63 6f 6c 20 65 ┆yntax for LLC type 1 protocol e┆
0x96a0…96c0 6c 65 6d 65 6e 74 73 20 28 22 70 72 6f 74 6f 63 6f 6c 20 64 61 74 61 20 75 6e 69 74 73 22 29 2e ┆lements ("protocol data units").┆
0x96c0…96e0 20 54 68 69 73 20 69 73 20 61 63 68 69 65 76 65 64 20 62 79 20 64 65 66 69 6e 69 6e 67 20 0a 74 ┆ This is achieved by defining t┆
0x96e0…9700 68 65 20 66 6f 72 6d 61 74 73 20 6f 66 20 61 6c 6c 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 ┆he formats of all the protocol e┆
0x9700…9720 6c 65 6d 65 6e 74 73 20 75 73 65 64 20 69 6e 20 74 68 65 20 70 72 6f 63 65 64 75 72 65 73 20 6f ┆lements used in the procedures o┆
0x9720…9740 72 69 65 6e 74 65 64 20 0a 74 6f 77 61 72 64 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 73 ┆riented toward client network s┆
0x9740…9760 65 72 76 69 63 65 20 74 6f 20 62 65 20 69 6e 73 74 61 6e 63 65 73 20 6f 66 20 74 79 70 65 20 31 ┆ervice to be instances of type 1┆
0x9760…9780 20 55 49 20 28 55 6e 6e 75 6d 62 65 72 65 64 20 0a 49 6e 66 6f 72 6d 61 74 69 6f 6e 29 20 63 6f ┆ UI (Unnumbered Information) co┆
0x9780…97a0 6d 6d 61 6e 64 73 2e 0d 0a 0d 0a 54 68 65 20 66 6f 6c 6c 6f 77 69 6e 67 20 63 6f 6e 76 65 6e 74 ┆mmands. The following convent┆
0x97a0…97c0 69 6f 6e 73 20 61 70 70 6c 79 20 74 6f 20 74 68 65 20 66 69 67 75 72 65 73 20 69 6e 20 74 68 69 ┆ions apply to the figures in thi┆
0x97c0…97e0 73 20 73 65 63 74 69 6f 6e 3a 20 74 68 65 20 0a 6f 63 74 65 74 73 20 6f 66 20 61 20 70 72 6f 74 ┆s section: the octets of a prot┆
0x97e0…9800 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 61 72 65 20 73 68 6f 77 6e 20 69 6e 20 74 68 65 20 6f 72 ┆ocol element are shown in the or┆
0x9800…9820 (76,) 64 65 72 20 74 68 65 79 20 61 72 65 20 74 72 61 6e 73 6d 69 74 74 65 64 20 0a 64 6f 77 6e 77 61 ┆der they are transmitted downwa┆
0x9820…9840 72 64 20 6f 6e 20 74 68 65 20 70 61 67 65 2c 20 61 6e 64 20 74 68 65 20 62 69 74 73 20 77 69 74 ┆rd on the page, and the bits wit┆
0x9840…9860 68 69 6e 20 61 6e 20 6f 63 74 65 74 20 73 69 6d 69 6c 61 72 6c 79 20 66 72 6f 6d 20 6c 65 66 74 ┆hin an octet similarly from left┆
0x9860…9880 20 0a 74 6f 20 72 69 67 68 74 2e 20 54 68 65 20 6c 65 61 73 74 20 73 69 67 6e 69 66 69 63 61 6e ┆ to right. The least significan┆
0x9880…98a0 74 20 62 69 74 20 70 6f 73 69 74 69 6f 6e 20 77 69 74 68 69 6e 20 61 6e 20 6f 63 74 65 74 2c 20 ┆t bit position within an octet, ┆
0x98a0…98c0 74 68 65 20 0a 63 6f 6e 74 65 6e 74 73 20 6f 66 20 77 68 69 63 68 20 69 73 20 74 72 61 6e 73 6d ┆the contents of which is transm┆
0x98c0…98e0 69 74 74 65 64 20 66 69 72 73 74 2c 20 69 73 20 6e 75 6d 62 65 72 65 64 20 30 2c 20 61 6e 64 20 ┆itted first, is numbered 0, and ┆
0x98e0…9900 73 6f 20 66 6f 72 74 68 2e 0d 0a 0d 0a 54 68 65 20 67 65 6e 65 72 61 6c 20 66 6f 72 6d 61 74 20 ┆so forth. The general format ┆
0x9900…9920 66 6f 72 20 74 79 70 65 20 31 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 63 6f 6e ┆for type 1 protocol elements con┆
0x9920…9940 73 69 73 74 73 20 6f 66 20 61 20 74 68 72 65 65 2d 0a 6f 63 74 65 74 20 6c 69 6e 6b 20 63 6f 6e ┆sists of a three- octet link con┆
0x9940…9960 74 72 6f 6c 20 68 65 61 64 65 72 20 66 6f 6c 6c 6f 77 65 64 20 62 79 20 61 6e 20 69 6e 66 6f 72 ┆trol header followed by an infor┆
0x9960…9971 6d 61 74 69 6f 6e 20 66 69 65 6c 64 3a 0d 0a 0d 0a ┆mation field: ┆
0x9971…99aa Params {
0x9971…99aa 04 00 2d 4e 0c 00 06 00 00 00 00 02 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0x9971…99aa 00 00 00 00 00 00 00 00 0b 0f 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff ff 04 ┆ /7AKU_iså ┆
0x9971…99aa }
0x99aa…99e3 Params {
0x99aa…99e3 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0x99aa…99e3 00 00 00 00 00 00 00 00 05 0f 19 23 2d 37 41 4b 55 5f 69 73 7d 87 91 ff 04 ┆ #-7AKU_iså ┆
0x99aa…99e3 }
0x99e3…9a00 0a 20 20 20 20 20 62 69 74 20 6e 6f 2e 09 a1 20 20 30 20 20 20 31 20 20 20 32 20 20 20 ┆ bit no. 0 1 2 ┆
0x9a00…9a20 (77,) 33 20 20 20 34 20 20 20 35 20 20 20 36 20 20 20 37 20 20 0d 0a 6f 63 74 65 74 20 6e 6f 2e 20 30 ┆3 4 5 6 7 octet no. 0┆
0x9a20…9a40 09 a1 21 20 30 20 21 20 30 20 21 20 20 20 20 20 20 20 20 20 44 53 41 50 09 21 0d 0a 09 31 09 a1 ┆ ! 0 ! 0 ! DSAP ! 1 ┆
0x9a40…9a60 21 43 2f 52 21 20 30 20 21 20 20 20 20 20 20 20 20 20 53 53 41 50 09 21 0d 0a 09 32 09 a1 21 20 ┆!C/R! 0 ! SSAP ! 2 ! ┆
0x9a60…9a80 20 20 20 20 20 20 20 20 20 43 6f 6e 74 72 6f 6c 09 21 0d 0a 09 33 09 21 09 21 0d 0a 09 09 21 20 ┆ Control ! 3 ! ! ! ┆
0x9a80…9a9b 20 20 20 20 20 54 79 70 65 20 31 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 09 21 0d 0a ┆ Type 1 Information ! ┆
0x9a9b…9ad4 Params {
0x9a9b…9ad4 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0x9a9b…9ad4 00 00 00 00 00 00 00 00 0b 0f 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff ff 04 ┆ /7AKU_iså ┆
0x9a9b…9ad4 }
0x9ad4…9b0d Params {
0x9ad4…9b0d 04 00 2d 4e 0c 00 06 00 00 00 00 02 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0x9ad4…9b0d 00 00 00 00 00 00 00 00 0b 0f 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff ff 04 ┆ /7AKU_iså ┆
0x9ad4…9b0d }
0x9b0d…9b20 0a 09 09 a1 21 09 21 0d 0a 0d 0a 54 68 65 20 44 53 41 50 ┆ ! ! The DSAP┆
0x9b20…9b40 20 66 69 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 64 ┆ field contains the local SAP ad┆
0x9b40…9b60 64 72 65 73 73 20 6f 66 20 74 68 65 20 64 65 73 74 69 6e 61 74 69 6f 6e 20 53 41 50 20 61 6e 64 ┆dress of the destination SAP and┆
0x9b60…9b80 20 0a 74 68 65 20 53 53 41 50 20 66 69 65 6c 64 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 ┆ the SSAP field the local SAP a┆
0x9b80…9ba0 64 64 72 65 73 73 20 6f 66 20 74 68 65 20 73 6f 75 72 63 65 20 53 41 50 2e 0d 0a 0d 0a 49 66 20 ┆ddress of the source SAP. If ┆
0x9ba0…9bc0 74 68 65 20 44 53 41 50 20 66 69 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 30 20 28 61 6c 6c 20 62 ┆the DSAP field contains 0 (all b┆
0x9bc0…9be0 69 74 73 20 30 29 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 0a ┆its 0) the protocol element is ┆
0x9be0…9c00 69 6e 74 65 72 70 72 65 74 65 64 20 61 73 20 61 64 64 72 65 73 73 65 64 20 74 6f 20 74 68 65 20 ┆interpreted as addressed to the ┆
0x9c00…9c20 (78,) 64 65 73 74 69 6e 61 74 69 6f 6e 20 52 43 4c 4c 43 20 28 6f 72 20 6f 74 68 65 72 20 4c 4c 43 20 ┆destination RCLLC (or other LLC ┆
0x9c20…9c40 74 79 70 65 20 31 29 20 0a 65 6e 74 69 74 79 20 72 61 74 68 65 72 20 74 68 61 6e 20 74 6f 20 61 ┆type 1) entity rather than to a┆
0x9c40…9c60 20 63 6c 69 65 6e 74 2e 0d 0a 0d 0a 49 66 20 74 68 65 20 44 53 41 50 20 66 69 65 6c 64 20 64 6f ┆ client. If the DSAP field do┆
0x9c60…9c80 65 73 20 6e 6f 74 20 63 6f 6e 74 61 69 6e 20 61 6c 6c 20 30 20 62 69 74 73 2c 20 69 74 73 20 63 ┆es not contain all 0 bits, its c┆
0x9c80…9ca0 6f 6e 74 65 6e 74 73 20 74 61 6b 65 6e 20 61 73 20 61 20 0a 62 69 6e 61 72 79 20 6e 75 6d 62 65 ┆ontents taken as a binary numbe┆
0x9ca0…9cc0 72 20 69 6e 20 74 68 65 20 72 61 6e 67 65 20 31 2e 2e 36 33 20 69 73 20 69 6e 74 65 72 70 72 65 ┆r in the range 1..63 is interpre┆
0x9cc0…9ce0 74 65 64 20 61 73 20 74 68 65 20 61 64 64 72 65 73 73 20 6f 66 20 61 6e 20 0a 69 6e 64 69 76 69 ┆ted as the address of an indivi┆
0x9ce0…9d00 64 75 61 6c 20 53 41 50 2e 0d 0a 0d 0a 41 20 43 2f 52 20 62 69 74 20 77 69 74 68 20 76 61 6c 75 ┆dual SAP. A C/R bit with valu┆
0x9d00…9d20 65 20 30 20 69 6e 64 69 63 61 74 65 73 20 61 20 63 6f 6d 6d 61 6e 64 20 70 72 6f 74 6f 63 6f 6c ┆e 0 indicates a command protocol┆
0x9d20…9d40 20 65 6c 65 6d 65 6e 74 2c 20 61 6e 64 20 6f 6e 65 20 0a 77 69 74 68 20 76 61 6c 75 65 20 31 20 ┆ element, and one with value 1 ┆
0x9d40…9d60 61 20 72 65 73 70 6f 6e 73 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 2e 20 54 68 65 ┆a response protocol element. The┆
0x9d60…9d80 20 55 49 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 2c 20 61 6e 64 20 0a 74 68 75 73 20 ┆ UI protocol element, and thus ┆
0x9d80…9da0 61 6c 6c 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 66 6f 72 20 63 6c 69 65 6e 74 ┆all protocol elements for client┆
0x9da0…9dc0 20 6e 65 74 77 6f 72 6b 20 73 65 72 76 69 63 65 20 63 61 6e 20 6f 6e 6c 79 20 62 65 20 0a 74 72 ┆ network service can only be tr┆
0x9dc0…9de0 61 6e 73 6d 69 74 74 65 64 20 61 73 20 63 6f 6d 6d 61 6e 64 73 2c 20 69 2e 65 2e 20 77 69 74 68 ┆ansmitted as commands, i.e. with┆
0x9de0…9e00 20 74 68 65 20 43 2f 52 20 62 69 74 20 73 65 74 20 74 6f 20 30 2e 0d 0a 0d 0a 8c 83 d4 0a 42 69 ┆ the C/R bit set to 0. Bi┆
0x9e00…9e20 (79,) 74 20 30 20 6f 66 20 6f 63 74 65 74 20 30 20 61 6e 64 20 62 69 74 20 31 20 6f 66 20 6f 63 74 65 ┆t 0 of octet 0 and bit 1 of octe┆
0x9e20…9e40 74 20 31 20 6d 75 73 74 20 61 6c 77 61 79 73 20 62 65 20 30 2e 0d 0a 0d 0a 49 66 20 74 68 65 20 ┆t 1 must always be 0. If the ┆
0x9e40…9e60 53 53 41 50 20 66 69 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 30 20 28 61 6c 6c 20 62 69 74 73 20 ┆SSAP field contains 0 (all bits ┆
0x9e60…9e80 30 29 2c 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 0a 69 6e 74 ┆0), the protocol element is int┆
0x9e80…9ea0 65 72 70 72 65 74 65 64 20 61 73 20 6f 72 69 67 69 6e 61 74 69 6e 67 20 66 72 6f 6d 20 74 68 65 ┆erpreted as originating from the┆
0x9ea0…9ec0 20 73 6f 75 72 63 65 20 52 43 4c 4c 43 20 28 6f 72 20 6f 74 68 65 72 20 4c 4c 43 20 74 79 70 65 ┆ source RCLLC (or other LLC type┆
0x9ec0…9ee0 20 31 29 20 0a 65 6e 74 69 74 79 20 72 61 74 68 65 72 20 74 68 61 6e 20 66 72 6f 6d 20 61 20 63 ┆ 1) entity rather than from a c┆
0x9ee0…9f00 6c 69 65 6e 74 2e 20 4f 74 68 65 72 77 69 73 65 2c 20 74 68 65 20 63 6f 6e 74 65 6e 74 73 20 6f ┆lient. Otherwise, the contents o┆
0x9f00…9f20 66 20 74 68 65 20 53 53 41 50 20 0a 66 69 65 6c 64 20 69 73 20 69 6e 74 65 72 70 72 65 74 65 64 ┆f the SSAP field is interpreted┆
0x9f20…9f40 20 61 73 20 61 20 62 69 6e 61 72 79 20 6e 75 6d 62 65 72 20 69 6e 20 74 68 65 20 72 61 6e 67 65 ┆ as a binary number in the range┆
0x9f40…9f60 20 31 2e 2e 36 33 2e 0d 0a 0d 0a 42 69 74 20 34 20 6f 66 20 6f 63 74 65 74 20 32 20 28 74 68 65 ┆ 1..63. Bit 4 of octet 2 (the┆
0x9f60…9f80 20 43 6f 6e 74 72 6f 6c 20 66 69 65 6c 64 29 20 69 73 20 74 68 65 20 50 6f 6c 6c 2f 46 69 6e 61 ┆ Control field) is the Poll/Fina┆
0x9f80…9fa0 6c 20 62 69 74 2e 20 57 68 65 6e 20 74 68 69 73 20 0a 62 69 74 20 69 73 20 73 65 74 20 74 6f 20 ┆l bit. When this bit is set to ┆
0x9fa0…9fc0 31 20 28 50 6f 6c 6c 29 20 69 6e 20 61 20 63 6f 6d 6d 61 6e 64 2c 20 61 20 72 65 73 70 6f 6e 73 ┆1 (Poll) in a command, a respons┆
0x9fc0…9fe0 65 20 69 73 20 72 65 71 75 65 73 74 65 64 2e 20 54 68 65 20 0a 72 65 73 70 6f 6e 73 65 20 73 68 ┆e is requested. The response sh┆
0x9fe0…a000 6f 75 6c 64 20 63 6f 6e 74 61 69 6e 20 74 68 65 20 73 61 6d 65 20 63 6f 64 69 6e 67 20 6f 66 20 ┆ould contain the same coding of ┆
0xa000…a020 (80,) 74 68 65 20 43 6f 6e 74 72 6f 6c 20 66 69 65 6c 64 3b 20 69 2e 65 2e 2c 20 62 69 74 20 0a 34 20 ┆the Control field; i.e., bit 4 ┆
0xa020…a040 28 46 69 6e 61 6c 29 20 73 68 6f 75 6c 64 20 61 6c 73 6f 20 62 65 20 73 65 74 20 69 6e 20 74 68 ┆(Final) should also be set in th┆
0xa040…a060 65 20 72 65 73 70 6f 6e 73 65 2e 20 54 68 65 20 50 6f 6c 6c 20 62 69 74 20 6d 75 73 74 20 6e 6f ┆e response. The Poll bit must no┆
0xa060…a080 74 20 62 65 20 0a 73 65 74 20 69 6e 20 61 20 55 49 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 ┆t be set in a UI protocol eleme┆
0xa080…a0a0 6e 74 3b 20 74 68 75 73 20 74 68 69 73 20 62 69 74 20 69 73 20 30 20 69 6e 20 61 6c 6c 20 70 72 ┆nt; thus this bit is 0 in all pr┆
0xa0a0…a0c0 6f 74 6f 63 6f 6c 20 0a 65 6c 65 6d 65 6e 74 73 20 66 6f 72 20 63 6c 69 65 6e 74 20 6e 65 74 77 ┆otocol elements for client netw┆
0xa0c0…a0e0 6f 72 6b 20 73 65 72 76 69 63 65 2e 0d 0a 0d 0a 54 68 65 20 53 53 41 50 20 66 69 65 6c 64 20 6f ┆ork service. The SSAP field o┆
0xa0e0…a100 66 20 61 20 72 65 73 70 6f 6e 73 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 61 6c ┆f a response protocol element al┆
0xa100…a120 77 61 79 73 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 73 61 6d 65 20 0a 76 61 6c 75 65 20 61 73 ┆ways contains the same value as┆
0xa120…a140 20 74 68 65 20 44 53 41 50 20 66 69 65 6c 64 20 6f 66 20 74 68 65 20 63 6f 6d 6d 61 6e 64 20 70 ┆ the DSAP field of the command p┆
0xa140…a160 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 74 6f 20 77 68 69 63 68 20 69 74 20 0a 63 6f 72 ┆rotocol element to which it cor┆
0xa160…a180 72 65 73 70 6f 6e 64 73 2c 20 61 6e 64 20 76 69 63 65 20 76 65 72 73 61 2e 0d 0a 0d 0a 54 68 65 ┆responds, and vice versa. The┆
0xa180…a1a0 20 72 65 6d 61 69 6e 69 6e 67 20 62 69 74 73 20 6f 66 20 74 68 65 20 43 6f 6e 74 72 6f 6c 20 66 ┆ remaining bits of the Control f┆
0xa1a0…a1c0 69 65 6c 64 20 73 70 65 63 69 66 79 20 74 68 65 20 74 79 70 65 20 6f 66 20 70 72 6f 74 6f 63 6f ┆ield specify the type of protoco┆
0xa1c0…a1e0 6c 20 0a 65 6c 65 6d 65 6e 74 20 69 6e 20 71 75 65 73 74 69 6f 6e 2c 20 76 69 7a 2e 3a 0d 0a 0d ┆l element in question, viz.: ┆
0xa1e0…a200 0a 31 31 30 30 30 30 30 30 09 09 55 49 2c 20 55 6e 6e 75 6d 62 65 72 65 64 20 49 6e 66 6f 72 6d ┆ 11000000 UI, Unnumbered Inform┆
0xa200…a220 (81,) 61 74 69 6f 6e 0d 0a 31 31 31 31 58 31 30 31 09 09 58 49 44 2c 20 65 58 63 68 61 6e 67 65 20 49 ┆ation 1111X101 XID, eXchange I┆
0xa220…a240 44 65 6e 74 69 66 69 63 61 74 69 6f 6e 0d 0a 31 31 30 30 58 31 31 31 09 09 54 45 53 54 0d 0a 0d ┆Dentification 1100X111 TEST ┆
0xa240…a260 0a 54 68 65 20 75 73 65 20 6f 66 20 74 68 65 20 54 79 70 65 20 31 20 49 6e 66 6f 72 6d 61 74 69 ┆ The use of the Type 1 Informati┆
0xa260…a280 6f 6e 20 66 69 65 6c 64 20 64 65 70 65 6e 64 73 20 6f 6e 20 74 68 65 20 74 79 70 65 20 6f 66 20 ┆on field depends on the type of ┆
0xa280…a2a0 70 72 6f 74 6f 63 6f 6c 20 0a 65 6c 65 6d 65 6e 74 2c 20 61 6e 64 20 69 73 20 64 65 73 63 72 69 ┆protocol element, and is descri┆
0xa2a0…a2c0 62 65 64 20 66 6f 72 20 65 61 63 68 20 65 6c 65 6d 65 6e 74 20 74 79 70 65 20 69 6e 20 73 65 63 ┆bed for each element type in sec┆
0xa2c0…a2e0 74 69 6f 6e 20 35 2e 31 2e 0d 0a 0d 0a 54 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e ┆tion 5.1. The protocol elemen┆
0xa2e0…a300 74 73 20 66 6f 72 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 73 65 72 76 69 63 65 20 61 72 ┆ts for client network service ar┆
0xa300…a320 65 20 55 49 20 63 6f 6d 6d 61 6e 64 73 20 0a 61 64 64 72 65 73 73 65 64 20 74 6f 20 61 6e 20 69 ┆e UI commands addressed to an i┆
0xa320…a340 6e 64 69 76 69 64 75 61 6c 20 53 41 50 20 77 69 74 68 20 74 68 72 65 65 20 65 78 74 72 61 20 6f ┆ndividual SAP with three extra o┆
0xa340…a360 63 74 65 74 73 20 6f 66 20 52 43 4c 4c 43 20 68 65 61 64 65 72 20 0a 69 6e 20 61 64 64 69 74 69 ┆ctets of RCLLC header in additi┆
0xa360…a380 6f 6e 20 74 6f 20 74 68 65 20 4c 4c 43 20 74 79 70 65 20 31 20 68 65 61 64 65 72 2e 20 53 6f 75 ┆on to the LLC type 1 header. Sou┆
0xa380…a3a0 72 63 65 20 61 6e 64 20 64 65 73 74 69 6e 61 74 69 6f 6e 20 53 41 50 73 20 68 61 76 65 20 0a 74 ┆rce and destination SAPs have t┆
0xa3a0…a3c0 68 65 20 73 61 6d 65 20 6c 6f 63 61 6c 20 61 64 64 72 65 73 73 20 77 68 69 63 68 20 69 73 20 65 ┆he same local address which is e┆
0xa3c0…a3e0 71 75 61 6c 20 74 6f 20 74 68 65 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 6e 75 6d 62 65 ┆qual to the client network numbe┆
0xa3e0…a400 72 2c 20 0a 4e 65 74 6e 6f 2e 20 54 68 65 20 66 6f 72 6d 61 74 20 69 73 20 61 73 20 73 68 6f 77 ┆r, Netno. The format is as show┆
0xa400…a412 (82,) 6e 20 62 65 6c 6f 77 3a 0d 0a 0d 0a 8c 83 98 0a 0e 0a ┆n below: ┆
0xa412…a44b Params {
0xa412…a44b 04 00 2d 4e 0c 00 06 00 00 00 00 02 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0xa412…a44b 00 00 00 00 00 00 00 00 0b 0f 29 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff 04 ┆ )/7AKU_iså ┆
0xa412…a44b }
0xa44b…a484 Params {
0xa44b…a484 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0xa44b…a484 00 00 00 00 00 00 00 00 0b 0f 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff ff 04 ┆ /7AKU_iså ┆
0xa44b…a484 }
0xa484…a4a0 0a 20 20 20 20 20 62 69 74 20 6e 6f 2e 09 a1 20 20 30 20 20 31 20 20 20 32 20 20 33 ┆ bit no. 0 1 2 3┆
0xa4a0…a4c0 20 20 34 20 20 35 20 20 36 20 20 37 20 20 0d 0a 6f 63 74 65 74 20 6e 6f 2e 20 30 09 a1 21 20 30 ┆ 4 5 6 7 octet no. 0 ! 0┆
0xa4c0…a4e0 20 20 30 20 21 20 20 20 20 20 20 4e 65 74 6e 6f 09 21 0d 0a 09 31 09 a1 21 20 30 20 20 30 20 21 ┆ 0 ! Netno ! 1 ! 0 0 !┆
0xa4e0…a500 20 20 20 20 20 20 4e 65 74 6e 6f 09 21 e1 20 20 74 79 70 65 20 31 0d 0a 09 32 09 a1 21 20 31 20 ┆ Netno ! type 1 2 ! 1 ┆
0xa500…a520 20 31 20 20 20 30 20 20 30 20 20 30 20 20 30 20 20 30 20 20 30 09 21 e1 20 20 68 65 61 64 65 72 ┆ 1 0 0 0 0 0 0 ! header┆
0xa520…a540 20 20 20 20 20 52 43 4c 4c 43 0d 0a 09 33 09 a1 21 20 20 20 20 20 20 20 20 46 75 6e 63 74 69 6f ┆ RCLLC 3 ! Functio┆
0xa540…a560 6e 09 21 e1 20 20 20 20 20 20 20 20 20 20 20 20 20 68 65 61 64 65 72 0d 0a 09 34 09 a1 21 20 20 ┆n ! header 4 ! ┆
0xa560…a580 20 20 20 20 20 20 50 61 72 61 6d 20 30 09 21 0d 0a 09 35 09 a1 21 20 20 20 20 20 20 20 20 50 61 ┆ Param 0 ! 5 ! Pa┆
0xa580…a5a0 72 61 6d 20 31 09 21 0d 0a 09 36 09 21 09 21 0d 0a 09 09 21 20 20 20 20 20 20 20 49 6e 66 6f 72 ┆ram 1 ! 6 ! ! ! Infor┆
0xa5a0…a5aa 6d 61 74 69 6f 6e 09 21 0d 0a ┆mation ! ┆
0xa5aa…a5e3 Params {
0xa5aa…a5e3 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0xa5aa…a5e3 00 00 00 00 00 00 00 00 0b 0f 29 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff 04 ┆ )/7AKU_iså ┆
0xa5aa…a5e3 }
0xa5e3…a61c Params {
0xa5e3…a61c 04 00 2d 4e 0c 00 06 00 00 00 00 02 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0xa5e3…a61c 00 00 00 00 00 00 00 00 0b 0f 29 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff 04 ┆ )/7AKU_iså ┆
0xa5e3…a61c }
0xa61c…a620 0a 09 09 a1 ┆ ┆
0xa620…a640 21 09 21 0d 0a 0f 0a 0d 0a 54 68 65 20 76 61 6c 75 65 20 69 6e 20 74 68 65 20 46 75 6e 63 74 69 ┆! ! The value in the Functi┆
0xa640…a660 6f 6e 20 66 69 65 6c 64 20 73 70 65 63 69 66 69 65 73 20 74 68 65 20 74 79 70 65 20 6f 66 20 70 ┆on field specifies the type of p┆
0xa660…a680 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 2c 20 0a 76 69 7a 2e 3a 0d 0a 0d 0a 30 30 30 30 30 ┆rotocol element, viz.: 00000┆
0xa680…a6a0 30 30 30 20 28 62 69 6e 61 72 79 20 30 29 20 20 20 41 43 54 49 56 45 5f 53 41 50 0d 0a 31 30 30 ┆000 (binary 0) ACTIVE_SAP 100┆
0xa6a0…a6c0 30 30 30 30 30 20 28 62 69 6e 61 72 79 20 31 29 20 20 20 52 45 53 45 54 0d 0a 30 31 30 30 30 30 ┆00000 (binary 1) RESET 010000┆
0xa6c0…a6e0 30 30 20 28 62 69 6e 61 72 79 20 32 29 20 20 20 52 41 43 4b 0d 0a 31 31 30 30 30 30 30 30 20 28 ┆00 (binary 2) RACK 11000000 (┆
0xa6e0…a700 62 69 6e 61 72 79 20 33 29 20 20 20 44 41 54 41 0d 0a 30 30 31 30 30 30 30 30 20 28 62 69 6e 61 ┆binary 3) DATA 00100000 (bina┆
0xa700…a720 72 79 20 34 29 20 20 20 41 43 4b 0d 0a 0d 0a 54 68 65 20 75 73 65 20 6f 66 20 74 68 65 20 50 61 ┆ry 4) ACK The use of the Pa┆
0xa720…a740 72 61 6d 20 30 20 61 6e 64 20 31 20 66 69 65 6c 64 73 20 61 6e 64 20 6f 66 20 74 68 65 20 49 6e ┆ram 0 and 1 fields and of the In┆
0xa740…a760 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 64 65 70 65 6e 64 73 20 0a 6f 6e 20 74 68 65 20 ┆formation field depends on the ┆
0xa760…a780 74 79 70 65 20 6f 66 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 2c 20 61 6e 64 20 69 73 ┆type of protocol element, and is┆
0xa780…a7a0 20 64 65 73 63 72 69 62 65 64 20 66 6f 72 20 65 61 63 68 20 65 6c 65 6d 65 6e 74 20 74 79 70 65 ┆ described for each element type┆
0xa7a0…a7c0 20 0a 69 6e 20 73 65 63 74 69 6f 6e 20 35 2e 32 2e 0d 0a 0d 0a 0d 0a a1 35 2e 31 20 20 20 20 54 ┆ in section 5.2. 5.1 T┆
0xa7c0…a7e0 79 70 65 20 31 20 50 72 6f 74 6f 63 6f 6c 20 45 6c 65 6d 65 6e 74 73 0d 0a 0d 0a 54 68 69 73 20 ┆ype 1 Protocol Elements This ┆
0xa7e0…a800 73 65 63 74 69 6f 6e 20 73 70 65 63 69 66 69 65 73 20 74 68 65 20 65 6e 63 6f 64 69 6e 67 20 6f ┆section specifies the encoding o┆
0xa800…a820 (84,) 66 20 74 68 65 20 54 79 70 65 20 31 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 6f ┆f the Type 1 Information field o┆
0xa820…a840 66 20 0a 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 75 73 65 64 20 69 6e 20 63 6f 6e ┆f protocol elements used in con┆
0xa840…a860 6a 75 6e 63 74 69 6f 6e 20 77 69 74 68 20 74 79 70 65 20 31 20 70 72 6f 63 65 64 75 72 65 73 2e ┆junction with type 1 procedures.┆
0xa860…a880 0d 0a 0d 0a 0d 0a a1 35 2e 31 2e 31 20 20 55 49 20 28 55 6e 6e 75 6d 62 65 72 65 64 20 49 6e 66 ┆ 5.1.1 UI (Unnumbered Inf┆
0xa880…a8a0 6f 72 6d 61 74 69 6f 6e 29 0d 0a 0d 0a 54 68 65 20 55 49 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 ┆ormation) The UI protocol ele┆
0xa8a0…a8c0 6d 65 6e 74 20 6d 61 79 20 6f 6e 6c 79 20 62 65 20 74 72 61 6e 73 6d 69 74 74 65 64 20 61 73 20 ┆ment may only be transmitted as ┆
0xa8c0…a8e0 61 20 63 6f 6d 6d 61 6e 64 2c 20 69 2e 65 2e 20 74 68 65 20 0a 43 2f 52 20 62 69 74 20 6d 75 73 ┆a command, i.e. the C/R bit mus┆
0xa8e0…a900 74 20 62 65 20 31 2e 0d 0a 0d 0a 57 68 65 6e 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 ┆t be 1. When the protocol ele┆
0xa900…a920 6d 65 6e 74 20 69 73 20 75 73 65 64 20 66 6f 72 20 74 79 70 65 20 31 20 73 65 72 76 69 63 65 20 ┆ment is used for type 1 service ┆
0xa920…a940 74 68 65 20 54 79 70 65 20 31 20 0a 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 69 73 ┆the Type 1 Information field is┆
0xa940…a960 20 75 73 65 64 20 74 6f 20 68 6f 6c 64 20 61 6e 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 ┆ used to hold an RCLLC service d┆
0xa960…a980 61 74 61 20 75 6e 69 74 2e 0d 0a 0d 0a 8c 83 b0 0a 0e 0a a1 35 2e 31 2e 32 20 20 58 49 44 20 28 ┆ata unit. 5.1.2 XID (┆
0xa980…a9a0 65 58 63 68 61 6e 67 65 20 49 44 65 6e 74 69 66 69 63 61 74 69 6f 6e 29 0d 0a 0d 0a 54 68 65 20 ┆eXchange IDentification) The ┆
0xa9a0…a9c0 54 79 70 65 20 31 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 69 6e 20 61 20 72 65 ┆Type 1 Information field in a re┆
0xa9c0…a9e0 63 65 69 76 65 64 20 58 49 44 20 63 6f 6d 6d 61 6e 64 20 69 73 20 69 67 6e 6f 72 65 64 2e 20 49 ┆ceived XID command is ignored. I┆
0xa9e0…aa00 6e 20 61 6e 20 0a 58 49 44 20 72 65 73 70 6f 6e 73 65 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d ┆n an XID response protocol elem┆
0xaa00…aa20 (85,) 65 6e 74 20 74 72 61 6e 73 6d 69 74 74 65 64 20 62 79 20 61 6e 20 52 43 4c 4c 43 20 65 6e 74 69 ┆ent transmitted by an RCLLC enti┆
0xaa20…aa40 74 79 20 74 68 72 65 65 20 0a 6f 63 74 65 74 73 2c 20 6e 75 6d 62 65 72 73 20 36 20 74 68 72 6f ┆ty three octets, numbers 6 thro┆
0xaa40…aa60 75 67 68 20 38 2c 20 61 72 65 20 65 6e 63 6f 64 65 64 20 61 73 20 66 6f 6c 6c 6f 77 73 3a 0d 0a ┆ugh 8, are encoded as follows: ┆
0xaa60…aa64 0f 0a 0d 0a ┆ ┆
0xaa64…aa9d Params {
0xaa64…aa9d 04 00 2d 4e 0c 00 06 00 00 00 00 02 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0xaa64…aa9d 00 00 00 00 00 00 00 00 0b 0f 28 41 4b 55 5f 69 73 7d 87 91 ff ff ff ff 04 ┆ (AKU_iså ┆
0xaa64…aa9d }
0xaa9d…aad6 Params {
0xaa9d…aad6 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0xaa9d…aad6 00 00 00 00 00 00 00 00 0b 0f 29 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff 04 ┆ )/7AKU_iså ┆
0xaa9d…aad6 }
0xaad6…aae0 0a 20 20 20 20 20 62 69 74 20 ┆ bit ┆
0xaae0…ab00 6e 6f 2e 09 a1 20 20 30 20 20 31 20 20 32 20 20 33 20 20 34 20 20 35 20 20 36 20 20 37 20 20 0d ┆no. 0 1 2 3 4 5 6 7 ┆
0xab00…ab20 0a 6f 63 74 65 74 20 6e 6f 2e 20 36 09 a1 21 20 31 20 20 30 20 20 30 20 20 30 20 20 30 20 20 30 ┆ octet no. 6 ! 1 0 0 0 0 0┆
0xab20…ab40 20 20 30 20 20 31 09 21 0d 0a 09 37 09 a1 21 20 31 20 20 30 20 20 30 20 20 30 20 20 30 20 20 30 ┆ 0 1 ! 7 ! 1 0 0 0 0 0┆
0xab40…ab4b 20 20 30 20 20 30 09 21 e1 0d 0a ┆ 0 0 ! ┆
0xab4b…ab84 Params {
0xab4b…ab84 04 00 2d 4e 0c 00 06 00 00 00 00 03 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0xab4b…ab84 00 00 00 00 00 00 00 00 0b 0f 28 2f 37 41 4b 55 5f 69 73 7d 87 91 ff ff 04 ┆ (/7AKU_iså ┆
0xab4b…ab84 }
0xab84…abbd Params {
0xab84…abbd 04 00 2d 4e 0c 00 06 00 00 00 00 02 01 48 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ -N H1 ┆
0xab84…abbd 00 00 00 00 00 00 00 00 0b 0f 28 41 4b 55 5f 69 73 7d 87 91 ff ff ff ff 04 ┆ (AKU_iså ┆
0xab84…abbd }
0xabbd…abc0 0a 09 38 ┆ 8┆
0xabc0…abe0 09 a1 21 20 30 20 20 30 20 20 30 20 20 30 20 20 30 20 20 30 20 20 30 20 20 30 09 21 0d 0a 0d 0a ┆ ! 0 0 0 0 0 0 0 0 ! ┆
0xabe0…ac00 0d 0a a1 35 2e 31 2e 33 20 20 54 45 53 54 0d 0a 0d 0a 54 68 65 20 54 79 70 65 20 31 20 49 6e 66 ┆ 5.1.3 TEST The Type 1 Inf┆
0xac00…ac20 (86,) 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 69 73 20 75 73 65 64 20 74 6f 20 68 6f 6c 64 20 61 ┆ormation field is used to hold a┆
0xac20…ac40 20 74 65 73 74 20 64 61 74 61 20 75 6e 69 74 2e 20 54 68 65 20 0a 61 73 73 6f 63 69 61 74 65 64 ┆ test data unit. The associated┆
0xac40…ac60 20 70 72 6f 63 65 64 75 72 65 20 69 73 20 64 65 73 63 72 69 62 65 64 20 69 6e 20 73 75 62 73 65 ┆ procedure is described in subse┆
0xac60…ac80 63 74 69 6f 6e 20 34 2e 31 2e 32 2e 0d 0a 0d 0a 0d 0a a1 35 2e 32 20 20 20 20 50 72 6f 74 6f 63 ┆ction 4.1.2. 5.2 Protoc┆
0xac80…aca0 6f 6c 20 45 6c 65 6d 65 6e 74 73 20 66 6f 72 20 43 6c 69 65 6e 74 20 4e 65 74 77 6f 72 6b 20 53 ┆ol Elements for Client Network S┆
0xaca0…acc0 65 72 76 69 63 65 0d 0a 0d 0a 49 6e 20 6f 72 64 65 72 20 74 6f 20 66 61 63 69 6c 69 74 61 74 65 ┆ervice In order to facilitate┆
0xacc0…ace0 20 73 70 65 65 64 79 20 61 63 63 65 73 73 20 74 6f 20 73 74 61 74 75 73 20 69 6e 66 6f 72 6d 61 ┆ speedy access to status informa┆
0xace0…ad00 74 69 6f 6e 20 61 73 73 6f 63 69 61 74 65 64 20 0a 77 69 74 68 20 63 6f 6e 6e 65 63 74 69 6f 6e ┆tion associated with connection┆
0xad00…ad20 73 2c 20 65 61 63 68 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 77 69 6c 6c 20 61 73 73 69 67 6e ┆s, each RCLLC entity will assign┆
0xad20…ad40 20 74 6f 20 65 61 63 68 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 61 6e 20 0a 69 6e 64 65 78 20 69 6e ┆ to each connection an index in┆
0xad40…ad60 20 74 68 65 20 72 61 6e 67 65 20 30 2e 2e 32 35 35 2e 20 57 68 65 6e 20 61 20 63 6f 6e 6e 65 63 ┆ the range 0..255. When a connec┆
0xad60…ad80 74 69 6f 6e 20 69 73 20 65 73 74 61 62 6c 69 73 68 65 64 20 74 68 65 20 61 73 73 69 67 6e 65 64 ┆tion is established the assigned┆
0xad80…ada0 20 0a 69 6e 64 69 63 65 73 20 61 72 65 20 65 78 63 68 61 6e 67 65 64 20 62 65 74 77 65 65 6e 20 ┆ indices are exchanged between ┆
0xada0…adc0 74 68 65 20 74 77 6f 20 52 43 4c 4c 43 20 65 6e 74 69 74 69 65 73 2e 20 53 75 62 73 65 71 75 65 ┆the two RCLLC entities. Subseque┆
0xadc0…ade0 6e 74 20 44 41 54 41 20 0a 61 6e 64 20 41 43 4b 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e ┆nt DATA and ACK protocol elemen┆
0xade0…ae00 74 73 20 65 61 63 68 20 63 6f 6e 74 61 69 6e 20 74 68 65 20 69 6e 64 65 78 20 61 73 73 69 67 6e ┆ts each contain the index assign┆
0xae00…ae20 (87,) 65 64 20 74 6f 20 74 68 65 20 0a 63 6f 6e 6e 65 63 74 69 6f 6e 20 62 79 20 74 68 65 20 72 65 63 ┆ed to the connection by the rec┆
0xae20…ae40 65 69 76 65 72 20 6f 66 20 74 68 65 20 65 6c 65 6d 65 6e 74 2e 0d 0a 0d 0a 0d 0a a1 35 2e 32 2e ┆eiver of the element. 5.2.┆
0xae40…ae60 31 20 20 41 43 54 49 56 45 5f 53 41 50 0d 0a 0d 0a 41 6e 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 ┆1 ACTIVE_SAP An RCLLC entity┆
0xae60…ae80 20 74 72 61 6e 73 6d 69 74 73 20 74 68 69 73 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 ┆ transmits this protocol element┆
0xae80…aea0 20 70 65 72 69 6f 64 69 63 61 6c 6c 79 20 66 6f 72 20 65 61 63 68 20 0a 61 63 74 69 76 65 20 53 ┆ periodically for each active S┆
0xaea0…aec0 41 50 20 69 74 20 73 65 72 76 65 73 20 77 68 69 63 68 20 62 65 6c 6f 6e 67 73 20 74 6f 20 61 20 ┆AP it serves which belongs to a ┆
0xaec0…aee0 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 2e 20 49 74 20 69 73 20 0a 74 72 61 6e 73 6d 69 74 74 ┆client network. It is transmitt┆
0xaee0…af00 65 64 20 75 73 69 6e 67 20 74 68 65 20 6d 75 6c 74 69 63 61 73 74 20 61 64 64 72 65 73 73 20 66 ┆ed using the multicast address f┆
0xaf00…af20 6f 72 20 74 68 65 20 63 6c 69 65 6e 74 20 6e 65 74 77 6f 72 6b 20 69 6e 20 0a 71 75 65 73 74 69 ┆or the client network in questi┆
0xaf20…af40 6f 6e 20 73 6f 20 74 68 61 74 20 61 6c 6c 20 72 65 6c 65 76 61 6e 74 20 52 43 4c 4c 43 20 65 6e ┆on so that all relevant RCLLC en┆
0xaf40…af60 74 69 74 69 65 73 20 77 69 6c 6c 20 72 65 63 65 69 76 65 20 69 74 2e 20 54 68 65 20 0a 66 72 65 ┆tities will receive it. The fre┆
0xaf60…af80 71 75 65 6e 63 79 20 77 69 74 68 20 77 68 69 63 68 20 74 68 65 20 70 72 6f 74 6f 63 6f 6c 20 65 ┆quency with which the protocol e┆
0xaf80…afa0 6c 65 6d 65 6e 74 20 69 73 20 74 72 61 6e 73 6d 69 74 74 65 64 20 64 65 70 65 6e 64 73 20 6f 6e ┆lement is transmitted depends on┆
0xafa0…afc0 20 74 68 65 20 0a 69 6d 70 6c 65 6d 65 6e 74 61 74 69 6f 6e 2e 0d 0a 0d 0a 54 68 65 20 66 69 72 ┆ the implementation. The fir┆
0xafc0…afe0 73 74 20 77 6f 72 64 20 6f 66 20 74 68 65 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 ┆st word of the Information field┆
0xafe0…b000 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 53 41 50 20 6d 61 73 6b 20 6f 66 20 74 68 65 20 0a 61 ┆ contains the SAP mask of the a┆
0xb000…b020 (88,) 63 74 69 76 65 20 53 41 50 2e 20 55 6e 6c 65 73 73 20 74 68 65 20 6d 61 73 6b 20 6d 61 74 63 68 ┆ctive SAP. Unless the mask match┆
0xb020…b040 65 73 20 74 68 61 74 20 6f 66 20 74 68 65 20 6c 6f 63 61 6c 20 53 41 50 20 61 74 20 74 68 65 20 ┆es that of the local SAP at the ┆
0xb040…b060 0a 72 65 63 65 69 76 69 6e 67 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 20 74 68 65 20 70 72 6f 74 ┆ receiving RCLLC entity the prot┆
0xb060…b080 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 64 69 73 63 61 72 64 65 64 2e 0d 0a 0d 0a 8c 83 ┆ocol element is discarded. ┆
0xb080…b0a0 e0 0a 54 68 65 20 50 61 72 61 6d 20 31 20 66 69 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 61 20 73 ┆ The Param 1 field contains a s┆
0xb0a0…b0c0 65 71 75 65 6e 63 65 20 6e 75 6d 62 65 72 20 69 6e 20 74 68 65 20 72 61 6e 67 65 20 30 2e 2e 32 ┆equence number in the range 0..2┆
0xb0c0…b0e0 35 34 2e 20 54 68 65 20 0a 66 69 72 73 74 20 32 35 35 20 41 43 54 49 56 45 5f 53 41 50 20 70 72 ┆54. The first 255 ACTIVE_SAP pr┆
0xb0e0…b100 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 74 72 61 6e 73 6d 69 74 74 65 64 20 61 66 74 65 ┆otocol elements transmitted afte┆
0xb100…b120 72 20 61 63 74 69 76 61 74 69 6f 6e 20 6f 66 20 61 20 0a 53 41 50 20 77 69 6c 6c 20 68 61 76 65 ┆r activation of a SAP will have┆
0xb120…b140 20 73 65 71 75 65 6e 63 65 20 6e 75 6d 62 65 72 73 20 30 2c 20 31 2c 20 32 2c 2e 2e 20 32 35 34 ┆ sequence numbers 0, 1, 2,.. 254┆
0xb140…b160 2e 20 49 6e 20 61 6c 6c 20 73 75 62 73 65 71 75 65 6e 74 20 0a 41 43 54 49 56 45 5f 53 41 50 20 ┆. In all subsequent ACTIVE_SAP ┆
0xb160…b180 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 73 20 74 68 65 20 73 65 71 75 65 6e 63 65 20 6e ┆protocol elements the sequence n┆
0xb180…b1a0 75 6d 62 65 72 20 77 69 6c 6c 20 61 6c 73 6f 20 62 65 20 32 35 34 2e 20 54 68 69 73 20 0a 70 72 ┆umber will also be 254. This pr┆
0xb1a0…b1c0 6f 63 65 64 75 72 65 20 61 6c 6c 6f 77 73 20 74 68 65 20 72 65 63 65 69 76 69 6e 67 20 52 43 4c ┆ocedure allows the receiving RCL┆
0xb1c0…b1e0 4c 43 20 65 6e 74 69 74 79 20 74 6f 20 64 65 74 65 63 74 20 77 68 65 6e 20 61 20 53 41 50 20 69 ┆LC entity to detect when a SAP i┆
0xb1e0…b200 73 20 0a 64 65 61 63 74 69 76 61 74 65 64 20 61 6e 64 20 73 77 69 66 74 6c 79 20 72 65 61 63 74 ┆s deactivated and swiftly react┆
0xb200…b220 (89,) 69 76 61 74 65 64 2c 20 70 6f 73 73 69 62 6c 79 20 62 65 63 61 75 73 65 20 6f 66 20 73 74 61 74 ┆ivated, possibly because of stat┆
0xb220…b240 69 6f 6e 20 72 65 80 0a 69 6e 69 74 69 61 6c 69 7a 61 74 69 6f 6e 2e 0d 0a 0d 0a 57 68 65 6e 20 ┆ion re initialization. When ┆
0xb240…b260 61 6e 20 41 43 54 49 56 45 5f 53 41 50 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 ┆an ACTIVE_SAP protocol element i┆
0xb260…b280 73 20 72 65 63 65 69 76 65 64 20 66 72 6f 6d 20 61 20 70 72 65 76 69 6f 75 73 6c 79 20 0a 75 6e ┆s received from a previously un┆
0xb280…b2a0 6b 6e 6f 77 6e 20 53 41 50 20 61 20 50 45 5f 6e 65 77 5f 53 41 50 20 65 76 65 6e 74 20 69 73 20 ┆known SAP a PE_new_SAP event is ┆
0xb2a0…b2c0 67 65 6e 65 72 61 74 65 64 20 28 63 66 2e 20 73 65 63 74 69 6f 6e 20 34 2e 32 29 2e 20 54 68 65 ┆generated (cf. section 4.2). The┆
0xb2c0…b2e0 20 73 61 6d 65 20 0a 69 73 20 74 68 65 20 63 61 73 65 20 69 66 20 74 68 65 20 73 65 71 75 65 6e ┆ same is the case if the sequen┆
0xb2e0…b300 63 65 20 6e 75 6d 62 65 72 20 69 73 20 6c 65 73 73 20 74 68 61 6e 20 74 68 65 20 73 65 71 75 65 ┆ce number is less than the seque┆
0xb300…b320 6e 63 65 20 6e 75 6d 62 65 72 20 0a 66 6f 75 6e 64 20 69 6e 20 74 68 65 20 6c 61 73 74 20 72 65 ┆nce number found in the last re┆
0xb320…b340 63 65 69 76 65 64 20 41 43 54 49 56 45 5f 53 41 50 20 6f 72 20 52 45 53 45 54 20 70 72 6f 74 6f ┆ceived ACTIVE_SAP or RESET proto┆
0xb340…b360 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 66 72 6f 6d 20 74 68 65 20 0a 73 61 6d 65 20 53 41 50 2e 20 ┆col element from the same SAP. ┆
0xb360…b380 48 6f 77 65 76 65 72 2c 20 77 68 65 6e 20 74 68 65 20 73 65 71 75 65 6e 63 65 20 6e 75 6d 62 65 ┆However, when the sequence numbe┆
0xb380…b3a0 72 20 61 72 65 20 65 71 75 61 6c 20 6f 72 20 61 73 63 65 6e 64 69 6e 67 2c 20 74 68 65 20 0a 70 ┆r are equal or ascending, the p┆
0xb3a0…b3c0 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 6f 6e 6c 79 20 74 61 6b 65 6e 20 74 6f ┆rotocol element is only taken to┆
0xb3c0…b3e0 20 69 6e 64 69 63 61 74 65 20 74 68 61 74 20 74 68 65 20 53 41 50 20 69 73 20 73 74 69 6c 6c 20 ┆ indicate that the SAP is still ┆
0xb3e0…b400 61 63 74 69 76 65 2e 20 0a 49 6e 20 74 68 65 20 6c 61 74 74 65 72 20 63 61 73 65 20 74 68 65 20 ┆active. In the latter case the ┆
0xb400…b420 (90,) 53 41 50 20 61 6c 69 76 65 20 74 69 6d 65 72 20 69 73 20 72 65 73 74 61 72 74 65 64 2e 0d 0a 0d ┆SAP alive timer is restarted. ┆
0xb420…b440 0a 54 68 65 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 66 72 6f 6d 20 74 68 65 20 ┆ The Information field from the ┆
0xb440…b460 74 68 69 72 64 20 62 79 74 65 20 6f 6e 77 61 72 64 73 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 ┆third byte onwards contains the ┆
0xb460…b480 0a 63 6c 69 65 6e 74 5f 69 6e 66 6f 20 70 61 73 73 65 64 20 66 72 6f 6d 20 74 68 65 20 63 6c 69 ┆ client_info passed from the cli┆
0xb480…b4a0 65 6e 74 20 77 68 65 6e 20 74 68 65 20 53 41 50 20 77 61 73 20 61 63 74 69 76 61 74 65 64 2e 0d ┆ent when the SAP was activated. ┆
0xb4a0…b4c0 0a 0d 0a 0d 0a a1 35 2e 32 2e 32 20 20 52 45 53 45 54 0d 0a 0d 0a 54 68 69 73 20 70 72 6f 74 6f ┆ 5.2.2 RESET This proto┆
0xb4c0…b4e0 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 74 72 61 6e 73 6d 69 74 74 65 64 20 69 6e 20 63 6f ┆col element is transmitted in co┆
0xb4e0…b500 6e 6a 75 6e 63 74 69 6f 6e 20 77 69 74 68 20 65 73 74 61 62 6c 69 73 68 6d 65 6e 74 20 0a 6f 66 ┆njunction with establishment of┆
0xb500…b520 20 61 20 63 6f 6e 6e 65 63 74 69 6f 6e 2e 0d 0a 0d 0a 54 68 65 20 50 61 72 61 6d 20 30 20 66 69 ┆ a connection. The Param 0 fi┆
0xb520…b540 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 69 6e 64 65 78 20 61 73 73 69 67 6e 65 64 20 ┆eld contains the index assigned ┆
0xb540…b560 74 6f 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 62 79 20 74 68 65 20 0a 73 65 6e 64 69 6e ┆to the connection by the sendin┆
0xb560…b580 67 20 52 43 4c 4c 43 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a 54 68 65 20 50 61 72 61 6d 20 31 20 66 ┆g RCLLC entity. The Param 1 f┆
0xb580…b5a0 69 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 73 65 71 75 65 6e 63 65 20 6e 75 6d 62 65 ┆ield contains the sequence numbe┆
0xb5a0…b5c0 72 20 74 6f 20 62 65 20 69 6e 63 6c 75 64 65 64 20 69 6e 20 74 68 65 20 0a 6e 65 78 74 20 41 43 ┆r to be included in the next AC┆
0xb5c0…b5e0 54 49 56 45 5f 53 41 50 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 74 6f 20 62 65 20 ┆TIVE_SAP protocol element to be ┆
0xb5e0…b600 74 72 61 6e 73 6d 69 74 74 65 64 20 66 72 6f 6d 20 74 68 65 20 73 65 6e 64 65 72 2e 0d 0a 0d 0a ┆transmitted from the sender. ┆
0xb600…b620 (91,) 54 68 65 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 74 ┆The Information field contains t┆
0xb620…b640 68 65 20 63 6c 69 65 6e 74 5f 69 6e 66 6f 20 70 61 73 73 65 64 20 66 72 6f 6d 20 74 68 65 20 63 ┆he client_info passed from the c┆
0xb640…b660 6c 69 65 6e 74 20 0a 77 68 65 6e 20 74 68 65 20 53 41 50 20 77 61 73 20 61 63 74 69 76 61 74 65 ┆lient when the SAP was activate┆
0xb660…b680 64 2e 0d 0a 0d 0a 0d 0a 8c 83 a4 0a 0e 0a a1 35 2e 32 2e 33 20 20 52 41 43 4b 0d 0a 0d 0a 54 68 ┆d. 5.2.3 RACK Th┆
0xb680…b6a0 69 73 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 74 72 61 6e 73 6d 69 74 74 ┆is protocol element is transmitt┆
0xb6a0…b6c0 65 64 20 74 6f 20 61 63 6b 6e 6f 77 6c 65 64 67 65 20 72 65 63 65 69 70 74 20 6f 66 20 61 20 52 ┆ed to acknowledge receipt of a R┆
0xb6c0…b6e0 45 53 45 54 20 0a 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 6e 20 63 6f 6e 6a 75 6e ┆ESET protocol element in conjun┆
0xb6e0…b700 63 74 69 6f 6e 20 77 69 74 68 20 65 73 74 61 62 6c 69 73 68 6d 65 6e 74 20 6f 66 20 61 20 63 6f ┆ction with establishment of a co┆
0xb700…b720 6e 6e 65 63 74 69 6f 6e 2e 0d 0a 0f 0a 0d 0a 54 68 65 20 50 61 72 61 6d 20 30 20 66 69 65 6c 64 ┆nnection. The Param 0 field┆
0xb720…b740 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 69 6e 64 65 78 20 61 73 73 69 67 6e 65 64 20 74 6f 20 ┆ contains the index assigned to ┆
0xb740…b760 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 62 79 20 74 68 65 20 0a 73 65 6e 64 69 6e 67 20 52 ┆the connection by the sending R┆
0xb760…b780 43 4c 4c 43 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a 54 68 65 20 50 61 72 61 6d 20 31 20 66 69 65 6c ┆CLLC entity. The Param 1 fiel┆
0xb780…b7a0 64 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 69 6e 64 65 78 20 61 73 73 69 67 6e 65 64 20 74 6f ┆d contains the index assigned to┆
0xb7a0…b7c0 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f 6e 20 62 79 20 74 68 65 20 0a 72 65 63 65 69 76 65 72 ┆ the connection by the receiver┆
0xb7c0…b7e0 20 61 73 20 69 6e 64 69 63 61 74 65 64 20 69 6e 20 74 68 65 20 52 45 53 45 54 20 70 72 6f 74 6f ┆ as indicated in the RESET proto┆
0xb7e0…b800 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 62 65 69 6e 67 20 61 63 6b 6e 6f 77 6c 65 64 67 65 64 2e 0d ┆col element being acknowledged. ┆
0xb800…b820 (92,) 0a 0d 0a 54 68 65 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c 64 20 69 73 20 65 6d 70 74 ┆ The Information field is empt┆
0xb820…b840 79 2e 0d 0a 0d 0a 0d 0a a1 35 a1 2e 32 2e 34 20 20 44 41 54 41 0d 0a 0d 0a 54 68 69 73 20 70 72 ┆y. 5 .2.4 DATA This pr┆
0xb840…b860 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 74 72 61 6e 73 6d 69 74 74 65 64 20 74 6f ┆otocol element is transmitted to┆
0xb860…b880 20 63 61 72 72 79 20 61 6e 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 61 74 61 20 75 6e 69 ┆ carry an RCLLC service data uni┆
0xb880…b8a0 74 20 0a 66 72 6f 6d 20 74 68 65 20 73 6f 75 72 63 65 20 53 41 50 20 74 6f 20 74 68 65 20 64 65 ┆t from the source SAP to the de┆
0xb8a0…b8c0 73 74 69 6e 61 74 69 6f 6e 20 53 41 50 2e 0d 0a 0d 0a 54 68 65 20 50 61 72 61 6d 20 30 20 66 69 ┆stination SAP. The Param 0 fi┆
0xb8c0…b8e0 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 73 65 71 75 65 6e 63 65 20 6e 75 6d 62 65 72 ┆eld contains the sequence number┆
0xb8e0…b900 20 6f 66 20 74 68 65 20 65 6c 65 6d 65 6e 74 2c 20 63 66 2e 20 0a 73 65 63 74 69 6f 6e 20 34 2e ┆ of the element, cf. section 4.┆
0xb900…b920 32 2e 20 54 68 65 20 73 65 71 75 65 6e 63 65 20 6e 75 6d 62 65 72 2c 20 77 68 69 63 68 20 63 61 ┆2. The sequence number, which ca┆
0xb920…b940 6e 20 6f 6e 6c 79 20 62 65 20 30 20 6f 72 20 31 20 69 73 20 70 6c 61 63 65 64 20 69 6e 20 0a 62 ┆n only be 0 or 1 is placed in b┆
0xb940…b960 69 74 20 30 2e 20 54 68 65 20 72 65 6d 61 69 6e 69 6e 67 20 62 69 74 73 20 61 72 65 20 61 6c 6c ┆it 0. The remaining bits are all┆
0xb960…b980 20 30 2e 0d 0a 0d 0a 54 68 65 20 50 61 72 61 6d 20 31 20 66 69 65 6c 64 20 63 6f 6e 74 61 69 6e ┆ 0. The Param 1 field contain┆
0xb980…b9a0 73 20 74 68 65 20 69 6e 64 65 78 20 61 73 73 69 67 6e 65 64 20 74 6f 20 74 68 65 20 63 6f 6e 6e ┆s the index assigned to the conn┆
0xb9a0…b9c0 65 63 74 69 6f 6e 20 61 74 20 74 68 65 20 0a 64 65 73 74 69 6e 61 74 69 6f 6e 20 52 43 4c 4c 43 ┆ection at the destination RCLLC┆
0xb9c0…b9e0 20 65 6e 74 69 74 79 2e 0d 0a 0d 0a 54 68 65 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c ┆ entity. The Information fiel┆
0xb9e0…ba00 64 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 20 52 43 4c 4c 43 20 73 65 72 76 69 63 65 20 64 61 74 ┆d contains the RCLLC service dat┆
0xba00…ba20 (93,) 61 20 75 6e 69 74 2e 0d 0a 0d 0a 0d 0a a1 35 2e 33 2e 35 20 20 41 43 4b 0d 0a 0d 0a 54 68 69 73 ┆a unit. 5.3.5 ACK This┆
0xba20…ba40 20 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 69 73 20 74 72 61 6e 73 6d 69 74 74 65 64 ┆ protocol element is transmitted┆
0xba40…ba60 20 74 6f 20 61 63 6b 6e 6f 77 6c 65 64 67 65 20 72 65 63 65 69 70 74 20 6f 66 20 61 20 44 41 54 ┆ to acknowledge receipt of a DAT┆
0xba60…ba80 41 20 0a 70 72 6f 74 6f 63 6f 6c 20 65 6c 65 6d 65 6e 74 20 6f 6e 20 61 20 63 6f 6e 6e 65 63 74 ┆A protocol element on a connect┆
0xba80…baa0 69 6f 6e 2e 0d 0a 0d 0a 54 68 65 20 50 61 72 61 6d 20 30 20 66 69 65 6c 64 20 63 6f 6e 74 61 69 ┆ion. The Param 0 field contai┆
0xbaa0…bac0 6e 73 20 74 68 65 20 73 65 71 75 65 6e 63 65 20 6e 75 6d 62 65 72 20 6f 66 20 74 68 65 20 65 6c ┆ns the sequence number of the el┆
0xbac0…bae0 65 6d 65 6e 74 20 62 65 69 6e 67 20 0a 61 63 6b 6e 6f 77 6c 65 64 67 65 64 2e 0d 0a 0d 0a 8c 83 ┆ement being acknowledged. ┆
0xbae0…bb00 bc 0a 54 68 65 20 50 61 72 61 6d 20 31 20 66 69 65 6c 64 20 63 6f 6e 74 61 69 6e 73 20 74 68 65 ┆ The Param 1 field contains the┆
0xbb00…bb20 20 69 6e 64 65 78 20 61 73 73 69 67 6e 65 64 20 74 6f 20 74 68 65 20 63 6f 6e 6e 65 63 74 69 6f ┆ index assigned to the connectio┆
0xbb20…bb40 6e 20 61 74 20 74 68 65 20 0a 64 65 73 74 69 6e 61 74 69 6f 6e 20 52 43 4c 4c 43 20 65 6e 74 69 ┆n at the destination RCLLC enti┆
0xbb40…bb60 74 79 2c 20 69 2e 65 2e 20 74 68 65 20 73 65 6e 64 65 72 20 6f 66 20 74 68 65 20 44 41 54 41 20 ┆ty, i.e. the sender of the DATA ┆
0xbb60…bb80 65 6c 65 6d 65 6e 74 2e 0d 0a 0d 0a 54 68 65 20 49 6e 66 6f 72 6d 61 74 69 6f 6e 20 66 69 65 6c ┆element. The Information fiel┆
0xbb80…bb8d 64 20 69 73 20 65 6d 70 74 79 2e 0d 0a ┆d is empty. ┆
0xbb8d…bb90 FormFeed {
0xbb8d…bb90 0c 80 b0 ┆ ┆
0xbb8d…bb90 }
0xbb90…bba0 0a a1 41 2e 20 20 20 20 20 52 45 46 45 52 45 4e ┆ A. REFEREN┆
0xbba0…bbc0 43 45 53 0d 0a 0d 0a 28 72 65 66 2e 31 29 09 49 53 4f 2f 44 50 20 38 38 30 32 2f 32 20 20 28 54 ┆CES (ref.1) ISO/DP 8802/2 (T┆
0xbbc0…bbe0 43 20 39 37 2f 53 43 20 36 20 4e 32 39 32 35 29 0d 0a 09 4c 6f 63 61 6c 20 41 72 65 61 20 4e 65 ┆C 97/SC 6 N2925) Local Area Ne┆
0xbbe0…bc00 74 77 6f 72 6b 73 20 2d 20 4c 6f 67 69 63 61 6c 20 4c 69 6e 6b 20 43 6f 6e 74 72 6f 6c 20 2d 20 ┆tworks - Logical Link Control - ┆
0xbc00…bc20 (94,) 44 72 61 66 74 20 45 0d 0a 0d 0a 28 72 65 66 2e 32 29 09 49 53 4f 2f 44 49 53 20 37 34 39 38 0d ┆Draft E (ref.2) ISO/DIS 7498 ┆
0xbc20…bc40 0a 09 44 61 74 61 20 50 72 6f 63 65 73 73 69 6e 67 20 2d 20 4f 70 65 6e 20 53 79 73 74 65 6d 73 ┆ Data Processing - Open Systems┆
0xbc40…bc60 20 49 6e 74 65 72 63 6f 6e 6e 65 63 74 69 6f 6e 0d 0a 09 42 61 73 69 63 20 52 65 66 65 72 65 6e ┆ Interconnection Basic Referen┆
0xbc60…bc80 63 65 20 4d 6f 64 65 6c 0d 0a 09 46 65 62 2e 20 34 2c 20 31 39 38 32 0d 0a 0d 0a 28 72 65 66 2e ┆ce Model Feb. 4, 1982 (ref.┆
0xbc80…bca0 33 29 09 52 43 53 4c 20 4e 6f 2e 20 34 32 2d 69 31 39 38 32 3a 0d 0a 09 44 69 73 74 72 69 62 75 ┆3) RCSL No. 42-i1982: Distribu┆
0xbca0…bcc0 74 65 64 20 53 79 73 74 65 6d 20 41 72 63 68 69 74 65 63 74 75 72 65 2c 20 52 65 70 6f 72 74 0d ┆ted System Architecture, Report ┆
0xbcc0…bce0 0a 0d 0a 28 72 65 66 2e 34 29 09 52 43 53 4c 20 4e 6f 2e 20 34 32 2d 69 31 39 38 33 3a 0d 0a 09 ┆ (ref.4) RCSL No. 42-i1983: ┆
0xbce0…bd00 44 53 41 20 49 6e 74 65 72 20 4d 6f 64 75 6c 65 20 43 6f 6d 6d 75 6e 69 63 61 74 69 6f 6e 2c 0d ┆DSA Inter Module Communication, ┆
0xbd00…bd20 0a 09 46 75 6e 63 74 69 6f 6e 61 6c 20 44 65 73 63 72 69 70 74 69 6f 6e 0d 0a 0d 0a 28 72 65 66 ┆ Functional Description (ref┆
0xbd20…bd40 2e 35 29 09 44 52 20 53 6f 66 74 2f 4e 65 74 2c 20 4e 65 74 77 6f 72 6b 20 4f 70 65 72 61 74 69 ┆.5) DR Soft/Net, Network Operati┆
0xbd40…bd60 6e 67 20 53 79 73 74 65 6d 2c 0d 0a 09 53 79 73 74 65 6d 20 47 75 69 64 65 0d 0a 09 44 69 67 69 ┆ng System, System Guide Digi┆
0xbd60…bd80 74 61 6c 20 52 65 73 65 61 72 63 68 2c 20 31 39 38 34 2e 0d 0a 1a 1a 09 53 79 73 74 65 6d 20 47 ┆tal Research, 1984. System G┆