ISO/IEC 15802-4:1994

Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 4: System load protocol

Defines a protocol to load the memory of data processing equipment installed on IEEE 802 networks. Discusses the LS in only as much detail as is necessary to define the loading protocol. Provides the PICS proforma for the System Load Protocol in compliance with the relevant requirements, and in accordance with the relevant guidance, given in ISO/IEC 9646-2.

Technologies de l'information — Télécommunications et échange d'informations entre systèmes —Réseaux de zones locales et métropolitaines — Spécifications communes — Partie 4: Protocole de charge de système

General Information

• Status: Withdrawn
• Publication Date: 14-Dec-1994
• Withdrawal Date: 14-Dec-1994
• ICS: 35.110 - Networking
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6/WG 1 - Physical and data link layers
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 27-Apr-2009
• Completion Date: 30-Oct-2025

Relations

• Consolidated By: ISO 2342:2003 - Slotted headless screws with shank
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD
15802-4
ANSIIIEEE
Std 802.1 E
First edition
1994-05-16
Information technology -
Telecommunications and information
exchange between Systems - Local and
metropolitan area networks - Common
specifications -
Part 4:
System load protocol
T~kcommunications et khange
Technologies de I’information -
d ’informations entre systemes - R&eaux de zones locales et
m&opolitaines - Spkifications communes -
Partie 4: Protocole de Charge de Systeme
Reference number
llSO/IEC 15802-4: 1994(Ei)
ANSI/IEEE
Std 802.1E, 1994 edition
Abstract: Services and protocol elements that permit the downloading of memory images to data
processing equipment attached to IEEE 802 Local and Metropolitan Area Networks are defined.
The protocol makes use of the group addressing capabilities inherent in LAN/MAN technologies to
permit simultaneous loading of the same memory image to multiple destination Systems. The stan-
dard includes the specification of managed objects that permit the Operation of the load protocol to
be remotely managed.
Keywords: local area networks, management; metropolitan area networks, management; System
load protocol
Corrected Edition
In the first printing of this edition, the fifth line of the title on page one of the Standard was mis-
rather than “Specific requirements- “.
printed. lt should have read “Common specifications-”
That error has been corrected in this printing.
The Institute of Electrical and Electronics Engineers, Inc.
345 East 47th Street, New York, NY 10017-2394, USA
Second Printing
Corrected Edition
March 1995
Copyrigh t 0 1994 by the Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 1994. Printed in the United States of America.
ISBN 1-55937-341-5
No part of this publication may be reproduced in any form, in an electronie re trieval System of o thetwise,
withou t the Prior
written Permission of the publisher.
May 16, 1994
SH16535
ISO/IEC 15802-4 : 1994
ANSMEEE Std 802.1 E, 1994 Edition
(incorporating ANSVIEEE Std 802.1 E-l 990 and
ANSVIEEE Std 802.1 m-l 993)
Information technology-
Telecommunications and information
exchange between systems-
Local and metropolitan area networks-
Common specifications-
Part 4: System load protocol
Sponsor
Technical Committee on Computer Communications
of the
IEEE Computer Society
Adopted as an International Standard by the
International Organization for Standardization
and by the
International Electrotechnical Commission
- American National Standard
Published by
The Institute of Electrical and Electronics Engineers, Inc.

International Standard ISO/IEC 15802-4: 1994
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized System for worldwide standardization. National bodies that are members
of ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, govemmental
and non-govemmental, in liaison with ISO and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a joint technical committee, ISOLIEC
JTC 1. Draft International Standards adopted by the joint technical committee are circulated to national
bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national
bodies casting a vote.
In 1993, ANWIEEE Std 802.1E-1990 was adopted by ISO/IEC JTC 1, as draft International Standard
ISOLIEC DIS 15802-3 (renumbered as ISO/IEC 15802-4). A further revision was subsequently approved by
ISO/IEC JTC 1 in the form of this new edition, which is published as International Standard ISO/IEC
15802-4: 1994.
International Organization for StandardizationBnternational Electrotechnical Commission
Case postale 56 l CH-121 1 Geneve 20 l Switzerland

Foreword to International Standard ISO/IEC 15802-4 : 1994
This Standard is part of a family of Standards for Local and Metropolitan Area Networks. The relationship
between this Standard and the other members of the family is shown below. (The numbers in the figure refer
to ISO Standard numbers.)
8802-2 Logical Link
Data
Link
Layer
8802-3 8802-5 8802-6 8802-7
Medium Medium Medium Medium
Access Access Access Access
------------- ------------. ------------- -------------
-------------
8802-3 8802-5 8802-6 8802-7 Physical
Physical Physical Physical
Physical Layer
This family of Standards deals with the Physical and Data Link layers as defined by the ISO Open Systems
Interconnection Basic Reference Model (ISO 7498 : 1984). The access Standards define five types of
medium access technologies and associated physical media, each appropriate for particular applications or
System objectives. Other types are under investigation.
The Standards defining the access technologies are as follows:
ISO/IEC 8802-3 [ANWIEEE Std 802.3, 1993 Edition], a bus utilizing CSMA/CD as the access
a>
method.
b) ISO/IEC 8802-4 [ANSUIEEE Std 802.4-19901, a bus utilizing token passing as the access method.
ISO/IEC 8802-5 [ANWIEEE Std 802.5-19921, a ring utilizing token passing as the access method.
C>
d) ISO/IEC 8802-6 [ANWIEEE Std 802.6, 1994 Edition], a dual bus utilizing distributed queuing as
the access method. DQDB subnetworks provide a range of telecommunications Services within a
metropolitan area.
ISO 8802-7, a ring utilizing slotted ring as the access method.
e>
ISO 8802-2 [ANWIEEE Std 802.2-19891, Logical Link Controlprotocol, provides for data transfer between
medium access Standards and network layer protocol.
ISO/IEC 10038 [ANWIEEE Std 802.1D, 1993 Edition], Media access control (MAC) bridges, specifies an
architecture and protocol for the interconnection of IEEE 802 LANs below the level of the logical link con-
trol protocol.
ISO/IEC DIS 15802-2 [IEEE Std 802.1B], LAN/MAN Management, defines an Open Systems Interconnec-
tion (OSI) management-compatible architecture, and Service and protocol elements for use in a LAN/MAN
environment for performing remote management.
ISO/IEC 15802-4 [ANSIAEEE Std 802.1E, 1994 Edition], System load protocol, specifies a set of Services
and protocol for those aspects of management concerned with the loading of Systems on IEEE 802 LANs.
The reader of this document is urged to become familiar with the complete family of Standards.

ANWIEEE Std 802.1 E, 1994 Edition
IEEE Standards documents are developed within the Technical Committees of the
IEEE Societies and the Standards Coordinating Committees of the IEEE Standards
Board. Members of the committees serve voluntarily and without compensation.
They are not necessarily members of the Institute. The Standards developed within
IEEE represent a consensus of the broad expertise on the subject within the Institute
as well as those activities outside of IEEE which have expressed an interest in partic-
ipating in the development of the Standard.
Use of an IEEE Standard is wholly voluntary. The existente of an IEEE Standard
does not imply that there are no other ways to produce, test, measure, purchase, mar-
ket, or provide other goods and Services related to the scope of the IEEE Standard.
Furthermore, the viewpoint expressed at the time a Standard is approved and issued is
subject to Change brought about through developments in the state of the art and
comments received from users of the Standard. Every IEEE Standard is subjected to
review at least once every five years for revision or reaffirmation. When a document
is more than five years old, and has not been reaffirmed, it is reasonable to conclude
that its contents, although still of some value, do not wholly reflect the present state
of the art. Users are cautioned to check to determine that they have the latest edition
of any IEEE Standard.
Comments for revision of IEEE Standards are welcome from any interested Party,
regardless of membership affiliation with IEEE. Suggestions for changes in docu-
ments should be in the form of a proposed Change of text, together with appropriate
supporting comments.
Interpretations: Occasionally questions may arise regarding the meaning of portions
of Standards as they relate to specific applications. When the need for interpretations
is brought to the attention of IEEE, the Institute will initiate action to prepare appro-
priate responses. Since IEEE Standards represent a consensus of all concerned inter-
ests, it is important to ensure that any interpretation has also received the concurrence
of a balance of interests. For this reason IEEE and the members of its technical com-
mittees are not able to provide an instant response to interpretation requests except in
those cases where the matter has previously received formal consideration.
Comments on Standards and requests for interpretations should be addressed to:
Secretary, IEEE Standards Board
445 Hoes Lane
P.O. Box 1331
Piscataway, NJ 08855- 133 1
USA
IEEE Standards documents may involve the use of patented technology. Their
approval by the Institute of Electrical and Electronics Engineers does not mean that
using such technology for the purpose of conforming to such Standards is authorized
by the patent owner. It is the Obligation of the user of such technology to obtain all
necessary permissions.
Introduction
(This introduction is not a part of ANSI/IEEE Std 802.1E, 1994 Edition or of ISO/IEC 15802-4 : 1994.)
This Standard is part of a family of Standards for local and metropolitan area networks. The relationship
between the Standard and other members of the family is shown below. (The numbers in the figure refer to
IEEE Standard numbers .)
802.2 LOGICAL LINK
DATA
802.1 BRIDGING
LINK
1 LAYER
I
802.4 802.5
802.6 802.9 802.12
MEDIUM MEDIUM MEDIUM MEDIUM MEDIUM
ACCESS ACCESS ACCESS ACCESS ACCESS
802.4 802.5 802.6 802.9 802.12
PHYSICAL
‘HYSICAL PHYSICAL PHYSICAL PHYSICAL PHYSICAL LAYER
I
* Formerly IEEE Std 802.1A.
This family of Standards deals with the Physical and Data Link layers as defined by the International Organi-
zation for Standardization (ISO) Open Systems Interconnection Basic Reference Model (ISO 7498 : 1984).
The access Standards define several types of medium access technologies and associated physical media,
each appropriate for particular applications or System objectives. Other types are under investigation.
The Standards defining these technologies are as follows:
l IEEE Std 802?: Overview and Architecture. This Standard provides an overview to the
family of IEEE 802 Standards. This document forms part of the 802.1
scope of work.
l ISO/IEC DIS 15802-2
[IEEE Stds 802.1B and 802.1k]: LAN/MAN Management. Defines an Open Systems Interconnection
(OSI) management-compatible architecture, and Services and protocol
elements for use in a LAN/MAN environment for performing remote
management.
l ISO/IEC 10038
[ANWIEEE Std 802. lD]: MAC Bridging. Specifies an architecture and protocol for the inter-
connection of IEEE 802 LANs below the MAC Service boundary.
l ISO/IEC 15802-4
[IEEE Std 802.1E]: System Load Protocol. Specifies a set of Services and protocol for those
aspects of management concerned with the loading of Systems on IEEE
802 LANs.
l ISO 8802-2
Logical Link Control
[ANWIEEE Std 802.21:
?The 802 Architecture and Overview Specification, originally known as IEEE Std 802.1 A, has been renumbered as IEEE Std 802. This
has been done to accommodate recognition of the base Standard in a family of Standards. References to IEEE Std 802.1A should be con-
sidered as references to IEEE Std 802.

l ISO/IEC 8802-3
[ANSUIEEE Std 802.31: CSMAKD Access Method and Physical Layer Specifications
l ISO/IEC 8802-4
[ANSVIEEE Std 802.41: Token Bus Access Method and Physical Layer Specifications
l ISO/IEC 8802-5
[ANSI/IEEE Std 802.51: Token Ring Access Method and Physical Layer Specifications
l ISOAEC 8802-6
[ANSIYIEEE Std 802.61: Distributed Queue Dual Bus Access Method/Physical Layer Specifications
l IEEE Std 802.10: Interoperable LAN/MAN Security, Currently Contains Secure Data Exchange
In addition to the family of Standards, the following is a recommended practice for a common technology:
l IEEE Std 802.7: IEEE Recommended Practice for Broadband Local Area Networks
The following additional working groups have authorized Standards projects under development:
l IEEE 802.9 Integrated Services (1s) LAN Interface at the Medium Access Control (MAC)
and Physical Layers
l IEEE 802.11 Wireless LAN Medium Access Control (MAC)/Physical Layer Specifications
l IEEE 802.12 Demand Priority Access Method and Physical Layer Specifications
The reader of this Standard is urged to become familiar with the complete family of Standards.
Conformance test methodology
An additional Standards series, identified by the number 1802, has been established to identify the conform-
ante test methodology documents for the 802 family of Standards. This makes the correspondence between
the various 802 Standards and their applicable conformance test requirements readily apparent. Thus the
conformance test documents for 802.3 are numbered 1802.3, the conformance test documents for 802.5 will
be 1802.5, and so on. Similarly, ISO will use 18802 to number conformance test Standards for 8802
Standards.
IEEE Std 802.1 E, 1994 Edition
This Standard defines Services and protocol elements that permit the downloading of memory images to data
processing equipment attached to IEEE 802 Local and Metropolitan Area Networks. The protocol makes use
of the group addressing capabilities inherent in LAN/MAN technologies to permit simultaneous loading of
the Same memory image to multiple destination Systems. The Standard includes the specification of managed
objects that permit the Operation of the load protocol to be remotely managed; these specifications, along
with the Protocol Implementation Conformance Statement (PICS) proforma in annex A, were developed as
P802.1m/D4, a Supplement to IEEE Std 802.1E.
This Standard contains state-of-the-art material. The area covered by this Standard is undergoing evolution.
Revisions are anticipated within the next few years to clarify existing material, to correct possible errors, and
to incorporate new related material.
Information on the current revision state of this and IEEE 802 committee working documents are available
other IEEE 802 Standards may be obtainedfrom: from:
Secretary, IEEE Standards Board IEEE Document Distribution Service
PO. Box 1331 AlphaGraphics #35 Attn: P Thrush
445 Hoes Lane 10201 N. 35th Avenue
Piscataway, NJ 08855- 133 1, USA Phoenix, AZ 8505 1, USA

Patticipants
The following is a list of participants in the IEEE Project 802.1 Working Group at the time IEEE Std
802.1 E- 1990 was approved:
William P. Lidinsky, Chair*
Tony Jeffree, Chair, Network Management Task Group*
Fumio Akashi Pat Gonia Daniel Pitt*
Paul D. Amer Richard Graham* Ron L. G. Printe
Charles Arnold Michael A. Grave1 Nigel Ramsden
Floyd Backes* Mogens Hansen Trudy Reusser
Ann B allard Harold Harrington Edouard Rocher
Richard Bantel John Hart* Paul Rosenblum*
Sy Bederman Mike Harvey* John S alter
Amatzia Ben-Artzi Bob Herbst Alan Sarsby
Robert Bledsoe Jack R. Hung Susan Schanning
Kwame Boakye Thomas Hytry Mick Seaman*
Juan Bulnes Jay Israel Gerry Segal*
Fred Burg Ram Kedlaya Rich Seifert*
Peter Carbone Ha1 Keen* Howard Sherry
Alan Chambers* Alan Kirby Wu-Shi Shung
Ken Chapman Kimberly Kirkpatrick M. Soha
Alice Chen Steve Kleiman Dan Stokesberry
Michael Chernick James Kristof* Lennart Swartz
Jade Chien H. Eugene Latham* Kenta Takumi
Jim Corrigan Chao-yu Liang Robin Tasker*
Paul Cowell* Bing Liao* Angus Telfer
Peter Dawe George Lin* Dave Thompson
S tan Degen* Mike Lumpkin Nathan Tobol
Frank Deignan Andy Luque Wendel1 Turner
Desh Deshpande Phillip Magnuson Peter Videcrantz*
Ron Dhondy Bruce McClure Paul Wainright
Kurt Dobbins Tom McGowan Scott Wasson*
Eiji Doi Margaret A. Merrick Daniel Watts
Barbara J. Don Carlos Jim Montrose Alan Weissberger
Walter Eldon Jerry 0’ Keefe Deborah Wilbert
Eldon D. Feist Richard Patti* Igor Zhovnirovsky*
Len Fishler* Roger Pfister* Carolyn Zimmer*
Kevin Flanagan* Thomas L. Phinney Nick Zucchero
David Piscitello
* Voting member of the 802.1 Working Group at the time of approval of this document.
The following persons were on the balloting committee of IEEE Std 802.1E-1990:
Willian B. Adams Ingrid Fromm Randolph Little
William D. Livingston
Hasan S. Alkhatib D. G. Gan
Kit Athul Patrick Gonia Donald Loughry
Willian E. Ayen Michael D. Graebner Andy J. Luque
Eduard0 W. Bergamini Maris Graube Kelly C. McDonald
Peter 1. P. Boulton J. Scott Haugdahl Richard H. Miller
Paul W. Campbell Richard J. Iliff David S. Millman
George S. Carson Raj Jain John E. Montague
Chih-Tsai Chen Tony Jeffree Kinji Mori
Michael H. Coden K. H. Kellermayr Charles Oestereicher
Robert Crowder Samuel Kho Young Oh
Mitchell G. Duncan Thomas M. Kurihara Rafat Pirzada
John E. Emrich Anthony B. Lake Udo W. Pooch
Philip H. Enslow Mike Lawler John P. Riganati
John W. Fendrich Jaiyong Lee Gar-y S. Robinson
Donald A. Fisher William Lidinsky Robert Rosenthal
Harvey A. Freeman E C. Lim Norman Schneidewind
vii
Adarshpal S. Sethi Efstathios D. Sykas Donald F. Weir
D. A. Sheppard Daniel Sze Alan J. Weissberger
Leo Sintonen Nathan Tobol
Earl J. Whitaker
John Spragins L. David Umbaugh
George B. Wright
Carel M. Stillebroer Thomas A. Varetoni Oren Yuen
Fred J. Strauss James T. Vorhies Lixia Zhang
When the IEEE Standards Board approved IEEE Std 802.1E-1990 on May 31, 1990, it had the following
membership:
Marco W. Migliaro, Chair James M. Daly, Vice Chair
Andrew G. Salem, Secretary
Paul L. Borrill Kenneth D. Hendrix Lawrence V. McCall
Fletcher J. Buckley John W. Horch
L. Bruce McClung
Allen L. Clapp Joseph L. Koepfinger*
Donald T. Michael*
James M. Daly Irving Kolodny Stig Nilsson
Stephen R. Dillon Michael L. Lawler
Roy T. Oishi
Donald C. Fleckenstein Donald C. Loughry
Gary S. Robinson
Jay Forster* John E. May, Jr. Terrance R. Whittemore
Thomas L. Hannan Donald W. Zipse <
*Member Emeritus
IEEE Std 802.1E-1990 was approved by the American National Standards Institute (ANSI) on October 12,
1990.
The following is a list of participants in the IEEE Project 802.1 Working Group at the time IEEE Std
802.1m-1993 was approved:
William P. Lidinsky, Chair*
Tony Jeffree, Chair, Network Management Task Group*
Jeanne Haney*
Floyd Backes* Ronald Presti*
Robert Barrett* John Hart* Maurice Qureshi
Amatzia Ben-Artzi Mike Harvey Paul Rosenblum
Anthony Berent* Eli Herscovitz Paul Ruocchio*
Orna Berry* Bonnie Hromis*
Tom Rutt*
Sai Boeker Long Huang Mick Seaman*
Brian Bortz Jan-Olof Jemnemo* Gerry Segal
Laura Bridge* Albert Juandy Rich Seifert
Brian Brown George Kajos Steve Senum
Alan Chambers* Ha1 Keen* Himanshu Shah*
Steve Cooper* Yoav Kluger W. Earl Smith
Paul Cowell* Hans Lackner Robin Tasker*
Andy Davis* Choon Lee Surya Varanasi
Mike Dickerson* George Lin Peter Videcrantz
Len Fishler* Joseph E. Massery Donald G. Vincent
Daryl Francis Alan Oppenheimer* Trevor Warwiek
Bill Futral Richard Patti *
Richard Watson*
Lionel Geretz* David T. Perkins* Bernd Widmann
Brian Phillips*
Richard Gilbert Bert Williams
Harry Gold* John Pickens*
Jerry A. Wyatt*
Andrew Green Venkat Prasad Amnon Yacoby*
Sharam Hakimi* Carolyn Zimmer
* Voting member of the 802.1 Working Group at the time of approval of this document.
. . .
Vlll
The following persons were on the balloting committee of IEEE Std 802.lm-1993:
William B. Adams Lanse M. Leach John P. Riganati
Ian F. Akyildiz Jai Yong Lee Philip T. Robinson
Kit Athul Randolph S. Little Daniel Rosich
William E. Ayen Joseph Loo Floyd E. ROSS
Paul W. Campbell Donald C. Loughry Victor Rozentouler
Anthony L. Carrato Wen-Pai Lu Christoph Ruland
John Cronican Gottfried W. R. Luderer Tom Rutt
Dave Sanford
Robert Crowder William C. McDonald
Ann Miller Donald A. Sheppard
Jose A. Cueto
Dan Shia
Paul Eastman Richard H. Miller
David S. Millman Surindra Singh
John E. Emrich
C. B. Madhab Mishra William R. Smith
Philip H. Enslow
Carel M. Stillebroer
John W. Fendrich W. Melody Moh
John E. Montague Fred J. Strauss
Harold C. Folts
Kinji Mori Efstathiois D. Sykas
Robert Gagliano
Patrick Gonia Alok C. Nigam Hao Tang
Patricia Thaler
Juli0 Gonzalez-Sanz Ellis S. Nolley
Russe11 D. Housley Charles Oestereider Geoffrey 0. Thompson
William J. Hunteman Young Oh Robert Tripi
Richard J. Iliff Thomas L. Phinney Mark-Rene Uchida
Thomas J. Jasinski John Pickens James T. Vorhies
Tony Jeffree Art J. Pina Barry M. Vornbrock
Youngbum Kirn Rafat Pirzada Donald F. Weir
Dae Young Kirn Vikram Punj Raymond Wenig
Kenneth Kung Yang Qianli Earl J. Whitaker
Lak Ming Lam Thad L. D. Regulinski Jerry A. Wyatt
Michael Lawler Francisco J. Restivo Oren Yuen
Alan B. Richstein
The final conditions for approval of IEEE Std 802.1m-1993 were met on September 29, 1993. This Standard
was conditionally approved by the IEEE Standards Board on June 17, 1993, with the following membership:
Wallace S. Read, Chair Donald C. Loughry, Vice Chair
Andrew G. Salem, Secretary
Gilles A. Baril Jim Isaak Don T. Michael*
Jose A. Berrios de la Paz Ben C. Johnson Marco W. Migliaro
Clyde R. Camp Walter J. Karplus L. John Rankine
Donald C. Fleckenstein Lorraine C. Kevra Arthur K. Reilly
Jay Forster* E. G. “Al” Kiener Ronald H. Reimer
David F. Franklin Ivor N. Knight Gary S. Robinson
Ramiro Garcia Joseph L. Koepfinger* Leonard L. Tripp
Donald N. Heirman D. N. “Jim” Logothetis Donald W. Zipse
*Member Emeritus
Also included are the following nonvoting IEEE Standards Board liaisons:
Satish K. Aggarwal
James Beall
Richard B. Engelman
David E. Soffrin
Stanley 1. Warshaw
Kristin M. Dittmann
IEEE Standards Project Editor
IEEE Std 802.1m-1993 was approved by ANSI on February 24, 1994.
ix
Contents
CLAUSE PAGE
1. Overview . 1
2. Scope . 2
3. References . 3
4. Definitions . 4
5. Authority . 4
6. Architecture . 4
7. Service definition . 5
7.1 SYSTEM LOAD.request . 6
-
7.2 SYSTEM LOAD.indication . 6
-
7.3 SYSTEM LOAD.response . 7
-
......................................................................................................... 7
7.4 SYSTEM LOAD.confirm
-
8. Protocol specification .
.................................................................................. 8
8.1 Summary of Protocol Data Units (PDUs)
....................................................................................................................... 9
8.2 LoadRequestPDU
8.3 LoadResponsePDU . 11
...................................................................................................................... 12
8.4 GroupStatusPDU
......................................................................................................... 14
8.5 GroupStatusRequestPDU
.......................................................................................................................... 14
8 6 LoadDataPDU
............................................................................................................... 15
8.7 Elements of Operation
8.8 Use of layer Services .
8.9 ASN. 1 encodings .
.................................................................................. 31
9. System Load Protocol managed Object classes
9.1 Introduction .
.................................................................. 32
9.2 System Load Protocol managed Object definitions
9.3 System Load Protocol managed Object class definitions . 36
...................................................................................................................................... 43
10. Conformance
............................................................................. 43
10.1 Conformance to this International Standard
............................................................................................................ 43
10.2 Claims of conformance
ANNEX
(normative) PICS proforma . 44
Annex A
(normative) Allocation of Object identifier values . 55
Annex B
Annex C (informative) System issues . 58

Information technology-
Telecommunications and information exchange between
systems-
Local and metropolitan area networks-
Common specifications-
Part 4: System load protocol
1. Overview
Stations in a network may, from time to time, require a Portion of their local addressable memory space to be
loaded using information held on a remote Station. In multivendor networks, the Provision of standardized
mechanisms to achieve this functionality is desirable.
In Order to accommodate efficient loading of multiple stations with the same information at the same time, it
is desirable to provide facilities for performing the load process on a multicast basis as well as on a point-to-
Point basis. The System Load Protocol provides both capabilities.
The protocol assumes two types of device in any load Operation:
Loadable Device (LD), which is capable of accepting a load from a Load Server.
a>
b) Load Server (LS), which is capable of providing a load for a Loadable Device.
A load Operation tan be initiated by
An LD requesting data from an LS.
A third Party requesting an LD to accept data by means of a management request, using the Load
b)
Operation specified in clause 9, and specifically in 9.2.1.3, in the description of the Load Operation.
When an LD accepts such a request, it will then request data from an LS in the normal manner.
The loadable data is termed an image. An image is broken down into Groups that, in turn, consist of blocks.
The protocol allows flexibility in the choice of image and block size. It does not state the number of Groups
in an image or the number of octets in a block.
The System Load Protocol relies on IEEE 802.2 Logical Link Control (LLC) Type 1 Services (see ISO 8802-
2 ’) operating over any compatible MAC and Physical Layer.
The System Load Protocol allows the use of IEEE 802.1B LAN/MAN Management [ISO/IEC DIS 15802-21
to manage aspects of its Operation. This use is described in 9.3. In addition, the managed objects have been
defined in such a way that it is also possible to use CMIP (ISO/IEC 9596) as the management protocol, as
described in 9.4.
‘Information on references tan be found in clause 3.

ISO/IEC 15802-4 : 1994
[ANSVIEEE Std 802.1 E, 1994 Edition] LOCAL AND METROPOLITAN AREA NETWORKS:
The System Load Protocol may be used in conjunction with other management protocols. It provides a load
capability not provided by general-purpose management protocols. The general-purpose management proto-
cols provide the capabilities of Parameter manipulation, event reporting, and action invocation that support
and enhance the load facility. For example, a load of one System might be invoked from another System by
means of management intervention.
The following clauses describe
The System Load architecture.
a>
The Services provided by System Load.
b)
The semantics and Syntax of the System Load Protocol, including the state machines that describe
C>
the Operation of the System Load Protocol machine.
d) The semantics of the load-related management objects.
Annex C provides further information regarding the application of the protocol.
To evaluate conformance of a particular implementation, it is necessary to have a Statement of which capa-
bilities and Options have been implemented for a given protocol. Such a Statement is called a Protocol Imple-
mentation Conformance Statement (PICS). Annex A .to this International Standard contains the PICS
proforma for the System Load Protocol.
2. Scope
The System Load Protocol specification defines a protocol to load the memory of data processing equipment
installed on IEEE 802 networks. To this end the specification
Defines the protocol data unit (PDU) formats for loading an end System.
a>
Defines the protocol for loading an end System.
b)
Describes the Services required of the end System being loaded (Loadable Device or LD) to success-
C>
fully complete a Load Operation.
Describes the Services required of the end System providing the load (Load Server or LS) to success-
d)
fully complete a load Operation.
Defines the semantic aspects of managed objects of the LD and LS that permit the manipulation of
e>
the operational Parameters of the LD and LS state machines, announcement of load servers, and the
third-Party initiation of a load.
Defines the Syntax used when performing management operations via the IEEE 802.1B LAN/MAN
Management Protocol (ISO/IEC DIS 15802-2).
Defines the Syntax used when performing management operations via the CMIP Systems Manage-
g>
ment Protocol (ISO/IEC 9596- 1).
The specification discusses the LS in only as much detail as is necessary to define the loading protocol. Man-
agement and LS decisions, such as what to do as a result of LS or LD events or when an LS or Manager
fails, are LS and Manager implementation issues and are beyond the scope of this document.
The protocol is specified to convey images consisting of data (in blocks) of unspecified format. The content
and format of data blocks are application-specific; this Standard does not place any constraints on
The form, content, or meaning of the images that may be conveyed by m.eans of the protocol;
a>
The manner in which data blocks are processed subsequent to their being received by a loadable
b)
device.
This International Standard provides the PICS proforma for the System Load Protocol in compliance with
the relevant requirements, and in accordance with the relevant guidance, given in ISO/IEC 9646-2.
ISO/IEC 15802-4 : 1994
SYSTEM LOAD PROTOCOL [ANSVIEEE Std 802.1 E, 1994 Edition]
3. References
The following Standards contain provisions which, through references in this text, constitute provisions of
this International Standard. At the time of publication, the editions indicated were valid. All Standards are
subject to revision, and Parties to agreements based an this International Standard are encouraged to investi-
gate the possibility of applying the most recent editions of the Standards listed below.
IEEE Std 802- 1990, IEEE Standards for Local and Metropolitan Area Networks: Overview and Architecture
(ANSI).2
IEEE Std 802.1F-1993, IEEE Standards for Local and Metropolitan Area Networks: Common Definitions
and Procedures for IEEE 802 Management Information.
ISO 7495-4 : 1989, Information technology-Open Systems Interconnection-Basic Reference Model-
Part 4: Management framework.3
ISO 8802-2 : 1989 [ANSUIEEE Std 802.2- 19891, Information processing Systems-Local area networks-
Part 2: Logical link control.
ISO/IEC 8824 : 1990, Information technology-Open Systems Interconnection-Specification of Abstract
Syntax Notation One (ASN. 1).
ISO/IEC 8825 : 1990, Information technology-Open Systems Interconnection-Specification of Basic
Encoding Rules for Abstract Syntax Notation One (ASN. 1).
ISO/IEC 9595 : 199 1, Information technology-Open Systems Interconnection-Common management
information Service definition.
ISO/IEC 9596- 1 : 199 1, Information technology-Open Systems Interconnection-Common management
information protocol-Part 1: Specification.
ISO/IEC 9646- 1 : 199 1, Information technology-Open Systems Interconnection-Conformance testing
methodology and framework-Part 1: General concepts.
ISO/IEC 9646-2 : 199 1, Information technology-Open Systems Interconnection-Conformance testing
methodology and framework- Part 2: Abstract test Suite specification.
ISO/IEC 10165-4 : 1992, Information technology-Open Systems Interconnection-Management informa-
information- Part 4: Guidelines for the definition of managed
tion Services -Structure of management
objects.
ISO/IEC TR 10178, Information technology-Telecommunications and information exchange between sys-
tems-The structure and coding of Logical Link Control addresses in Local Area Networks.
ISO/IEC TR 10735, Information technology-Telecommunications and information exchange between sys-
tems-S tandard Group MAC Addresses.
21EEE publications are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, P.O. Box 133 1, Piscataway,
NJ 088551331, USA.
31S0 and ISO/IEC publications are available from the ISO Central Secretariat, 1 rue de Varembe, Case Post ale 56, CH-l 211, Geneve
20, SwitzerlamUSuisse. In the US, they are available from the Sales Department, American National Standards Institute, 11 West 42nd
Street, 13th Floor, New York, NY 10036, USA.

ISO/IEC 15802-4 : 1994
[ANSVIEEE Std 802.1 E, 1994 Edition]
LOCALAND METROPOLITAN AREA NETWORKS:
ISO/IEC DIS 15802-2. .4 [ANWIEEE Std 802.1B-1992 and IEEE Std 802.1k-19931, Draft Standard for
Local and Metropolitan Area Networks: LAN/MAN Management.
4. Definitions
The following terms are used throughout this International Standard in a specialized manner:
4.1 Image: The data structure contained in the Load Server that the Loadable Device wishes to load.
4.2 Loadable Device (LD): A Station on the network that is capable of accepting a load from a Load Server.
4.3 Load Server (LS): A Station on the network that is capable of providing a load for a Loadable Device.
This International Standard uses the following terms defined in ISO/IEC 9646- 1:
PICS proforma
a>
b) protocol implementation conformance Statement (PICS)
static conformance review
C>
Other management-specific terms are defined in IEEE 802.1B LAN/MAN Management (ISO/IEC DIS
15802-2).
5. Authority
In cases where there are discrepancies between the text descriptions, state di .agrams, and the state tables, the
state tables are to be con sidered as the authority.
6. Architecture
This clause contains an overview of the System Load architecture. Figure 1 depicts the architectural
compo-
nents and interfaces. There are three major architectural components involved in System Load:
System Load User (SLU)
a>
b) System Load Entity (SLE)
System Load Layer Management Entity (SL-LME)
C>
A brief description of each of these components follows:
The SLU is a user of System Load Services. The user of these Services may be a provider of load images
(LS) or a requester of load images (LD) or both.
In Order to perform its function, the SLU may be required to communicate with an SLU in another Station.
The SLUs intercommunicate in a peer-to-peer manner, using the communication Services provided by the
SLE. This communication is described in terms of the roles that each SLU and associated SLE plays in a
particular instance of communication, either the role of an LD or an LS. These terms are used for descriptive
purposes only and do not imply System capabilities in any other context. An LD requests to be loaded with
an image. An LS acts on behalf of the requesting LD to provide an image.
4Currently at state of Draft International Standard.
ISO/IEC 15802-4 : 1994
SYSTEM LOAD PROTOCOL [ANSVIEEE Std 802.1 E, 1994 Edition]
The System Load Service is provided by means of the System Load Protocol. Two architectural components
are associated with the Operation of the protocol. These are the SLE and the SL MIB.
-
The SLE performs System Load communication functions on behalf of its SLU.
The SL MIB is a set of managed objects associated with the SLE. It provides the management functions and
-
management information specific to the management of the SLE, allowing it to be managed in a manner
analogous to managing a layer. The managed Object class definitions for the SL-MIB are contained in
clause 9. IEEE 802.1B [ISO/IEC DIS 15802-21 describes how the functionality of these managed objects
may be accessed by means of management protocol.
The SLE makes use of the underlying Services of IEEE 802 LLC Type 1 (ISO 8802-2) in Order to convey
SL PDUs. The use of other Services is not precluded; however, this Standard does not specify any conform-
-
ante-related aspects of the use of any other Services.
The load-specific Services of the SLE are described in clause 7.
P rotocol
Figure l-System Load architecture
7. Service definition
This clause defines the Services provided by the System Load Entity (SLE) to the System Load User (SLU)
at the System Load Service Boundary.
The following primitives are defined for the SLU to request Service from the SLE:
SYSTEM LOAD.request, by which the SLU requests that a load Operation be performed.
-
a>
SYSTEM-LOAD.confirm, by which the SLE confirms the success or failure of the corresponding
b)
request.
SYSTEM LOAD.indication, by which the SLE informs the SLU that an image is required in Order
-
C>
to perform a requested load Operation.
SYSTEM LOAD.response, by which the SLU returns the required image or reason for not provid-
-
d)
ing the image.
The time sequence of these Service primitives is shown in figure 2.
In addition, general-purpose management Services provided by IEEE 802.1B LAN/MAN Management
(ISO/IEC DIS 15802-2) and the CMISKMIP Standards (ISO/IEC 9595 and 9596) support the load facility:
ISO/IEC 15802-4 : 1994
[ANSVIEEE Std 802.1 E, 1994 Edition] LOCALAND METROPOLITAN AREA NETWORKS:
LD System Load LS
Service
SYSTEM-LOAD.req
E SYSTEM LOAD.ind
-
SYSTEM-LOAD.rsp
SYSTEM LOAD.cnf 4
-
Figure 2-Sequence of SYSTEM LOAD primitives
-
of the System Load Service in terms of these primi tives and their associated is for
NOTE-The definition Parameters
construed as placing constraints on the nature of real implernentations.
clarity only, and should not be
7.1 SYSTEM LOAD.request
-
This primitive is the Service request primitive for the System Load Service.
7.1.1 Semantics of the Service primitive
SYSTEMLOAD.request (
load info,
-
load reason
-
- load info specifies information that may be used to determine the image to be loaded.
-
--- load reason specifies the reason that the load is desired. The load reason Parameter shall have one of
-
the following values:
No reason is specified.
Unspecified:
PowerUp: The System or some part of it has had power restored.
The load has been forced remotely via a Systems management action.
Forcedload:
OperationalFailure: An operational failure has occurred resulting in the necessity for a load.
A previous load attempt has failed.
LoadFailure:
Reconfiguration: A configuration Change requiring load has occurred.
Private Reason: An implementation-specific reason.
7.1.2 When generated
This primitive is used by the SLU whenever it needs to have part or all of its System loaded.
7.1.3 Effect of receipt
The effect of this primitive is that the SLE shall request the load from one or more load servers.
7.2 SYSTEM LOAD.indication
-
This primitive is the Service indication primitive for the System Load Service.
ISO/IEC 15802-4 : 1994
[ANSVIEEE Std 802.1 E, 1994 Edition]
SYSTEM LOAD PROTOCOL
7.2 SYSTEM LOAD.indication
-
This primitive is the Service indication primitive for the System Load Service.
7.2.1 Semantics of the Service primitive
SYSTEM-LOAD.indication (
load info,
-
load reason
-
)
- load info specifies information that may be used to determine the image to be loaded. The load info
- -
Parameter shall take the value provided in the corresponding SYSTEMLOAD.request primitive.
- load reason specifies the reason that the load is desired. The loadreason Parameter shall take the
-
value provided in the corresponding SYSTEM-LOAD.request primitive.
7.2.2 When generated
This primitive is generated upon receipt of a LoadRequestPDU by the SLE.
7.2.3 Effect of receipt
The effect of this primitive is that the SLU shall return the required image or reason for not returning the
image in a SYSTEM-LOAD.response primitive.
7.3 SYSTEM LOAD.response
-
This primitive is the Service response primitive for the System Load Service.
7.3.1 Semantics of the Service primitive
(
SYSTEM LOAD.response
-
Status,
image
)
Parameter
Status specifies the success or failure of the load request. The Status shall take one of the
following values:
success: The image is available and supplied.
not-available: The image is not available for the indicated load.
image is the image to be provided by the load; it is not provided if Status is not success.
-
7.3.2 When generated
This primitive is used by the SLU to return the image indicated in the corresponding SYSTEM LOAD.indi-
-
cation primitive.
7.3.3 Effect of receipt
The effect of this primitive is that the SLE shall attempt to perform the load.

ISO/IEC 15802-4 : 1994
[ANSVIEEE Std 802.1 E, 1994 Edition] LOCAL AND METROPOLITAN AREA NETWORKS:
7.4 SYSTEM LOAD.confirm
-
This primitive is the Service confirmation primitive for the System Load Service.
7.4.1 Semantics of the Service primitive
SYSTEM-LOAD.confirm (
Status,
Image
success or failure of the load request. The Status Parameter shall take one of the
- Status specifies the
following values:
success: The load was correctly performed.
noresponse: No server responded to the request.
incomplete: A load was attempted but never successfully completed.
invalid-response: An invalid load response was (were) received with Parameters inconsistent
with the corresponding load request.
- image is the image provided by the load; it is not provided
...