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
Current Stage
9599 - Withdrawal of International Standard
Start Date
27-Apr-2009
Completion Date
27-Apr-2009
Ref Project

RELATIONS

Effective Date
06-Jun-2022

Buy Standard

Standard
ISO/IEC 15802-4:1994 - Information technology -- Telecommunications and information exchange between systems -- Local and metropolitan area networks -- Common specifications
English language
72 pages
sale 15% off
Preview
sale 15% off
Preview

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
---------------------- Page: 1 ----------------------

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
---------------------- Page: 2 ----------------------
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.
---------------------- Page: 3 ----------------------
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
---------------------- Page: 4 ----------------------
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

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.

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.

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.

---------------------- Page: 5 ----------------------
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.
---------------------- Page: 6 ----------------------
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
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
* 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.
---------------------- Page: 7 ----------------------
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
---------------------- Page: 8 ----------------------
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
---------------------- Page: 9 ----------------------
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
---------------------- Page: 10 ----------------------
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.
---------------------- Page: 11 ----------------------
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

---------------------- Page: 12 ----------------------
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.
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

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.
---------------------- Page: 13 ----------------------
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
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.