ISO/IEC 10164-13:1995/Amd 1:1997

Information technology — Open Systems Interconnection — Systems Management: Summarization Function — Amendment 1: Implementation conformance statement proformas

Technologies de l'information — Interconnexion de systèmes ouverts (OSI)— Gestion des systèmes: Fonction de récapitulation — Amendement 1: Formulaires de déclaration de conformité d'instance

General Information

• Status: Published
• Publication Date: 19-Mar-1997
• ICS: 35.100.70 - Application layer
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 6060 - International Standard published
• Start Date: 20-Mar-1997
• Completion Date: 14-Feb-2026

Relations

• Amends: ISO/IEC 10164-13:1995 - Information technology — Open Systems Interconnection — Systems Management: Summarization Function
• Effective Date: 28-Dec-2008
• Child: ISO/IEC 10164-13:1995 - Information technology — Open Systems Interconnection — Systems Management: Summarization Function
• Effective Date: 15-Apr-2008

Overview

ISO/IEC 10164-13:1995/Amd 1:1997 is an amendment to the OSI (Open Systems Interconnection) Systems Management specification focusing on the Summarization Function. Amendment 1 provides standardized implementation conformance statement (ICS/MCS/MICS/MOCS) proformas and guidance to help implementers declare which parts of the summarization function they support. The document organizes proformas, instructions, and conformance rules to enable consistent declaration and testing of implementations.

Key Topics

• Implementation conformance statement proformas: Standardized templates (MCS, MICS, MOCS) to record implementation details and declared conformance.
• Conformance model: Clause 13 addresses conformance, including static and dynamic conformance and the specific requirements for management implementation conformance statements.
• Managed object class proformas (MOCS): Annexes provide MOCS proformas for a variety of scanner types and scan records (e.g., heterogeneous, buffered, simple, mean, mean-variance, min-max, percentile, dynamic simple scanners, scan report records).
• Structure and guidance: Annex materials include instructions for completing proformas, symbol/abbreviation lists, table formats, identification of implementations, packages, and a management conformance summary.
• Elements documented per proforma: Statements of conformance, attributes, notifications, actions, parameters, and package membership for each managed object class.

Applications

• Network and systems management: Helps vendors and integrators implement and document OSI-based summarization functions used in monitoring, telemetry and aggregated metrics.
• Interoperability and testing: Standardized ICS/MOCS/MICS proformas enable consistent conformance declarations used by test labs and certification schemes to verify compatibility between management systems and managed devices.
• Product documentation and procurement: Manufacturers and suppliers can provide clear conformance statements for procurement, regulatory or contractual compliance.
• Implementation guidance: Provides a template-driven approach for engineering teams to capture supported features and options of the summarization function for internal QA and release control.

Who uses this standard

• Firmware and network equipment vendors implementing OSI Systems Management summarization features
• Systems management software developers and integrators
• Conformance test laboratories and certification bodies
• Standards engineers, technical writers, and procurement teams requiring formal conformance evidence

Related standards

• Other parts of the ISO/IEC 10164 series and OSI Systems Management recommendations address complementary management functions and conformance frameworks (see ISO/IEC catalog for related parts).

By standardizing implementation conformance statement proformas and detailing proformas for multiple managed object classes, ISO/IEC 10164-13:1995/Amd 1:1997 supports consistent documentation, testing, and interoperability of OSI summarization implementations.

Standards Content (Sample)

ISO/IEC
INTERNATIONAL
STANDARD
First edition
1995-06-01
AMENDMENT 1
1997-04-O 1
Information technology - Open Systems
Interconnection - Systems Management:
Summarization Function
AMENDMENT 1: Implementation
conformance statement proformas
Technologies de I’informa tion - In terconnexion de syst&mes
ouverts (03) Gestion-syst&mes: Fonction de r&urn6
AMENDEMENT I: Proformes de dkclaration de conformit de mise en
euvre
Reference number
ISO/lEC 10164-I 3:1995/Amd.l :I 997(E)

ISO/lEC 1016413 : 199YAmd.l: 1997 (E)
Contents
Page
Subclause 2.1 .
1)
Subclause 2.2 .
2)
Subclause 3.3 .
3)
.................................................................................................................................................
Subclause 3.7
4)
Subclause 3.9 .
5)
............................................................
39 . Implementation conformance statement proforma definitions
Clause 4 .
6)
........................................................................................................................................................
Clause 13
7)
13 Conformance .
..............................................................................................................................
13.1 Static conformance
13.2 Dynamic conformance .
..................................................
13.3 Management implementation conformance statement requirements
New annexes .
8)
........................................................................................................................................
Annex B - MCS proforma
B.l Introduction .
........................................................................................................
B.l.l Purpose and structure
................................ 4
Instructions for completing the MCS proforma to produce an MCS
B.1.2
.....................................................................................
B.1.3 Symbols, abbreviations and terms
......................................................................................................................
B.1.4 Table format
...................................................................................................
B .2 Identification of the implementation
Date of statement .
B.2.1
.................................................................................
B.2.2 Identification of the implementation
Contact .
B.2.3
B.3 Identification of the Recommendation 1 International Standard in which the management
.........................................................................................................................
information is defined
...................................................................................
Technical corrigenda implemented
B.3.1
Amendments implemented .
B.3.2
..................................................................................................
B.4 Management conformance summary
.......................................................................................................................................
Annex C - MICS proforma
C. 1 Introduction .
.................................................
C.2 Instructions for completing the MICS proforma to produce a MICS
.......................................................................................................
Symbols, abbreviations and terms
C.3
................................................................ 11
C.4 Statement of conformance to the management information
..........................................................................................................................
c.4.1 Attributes
........................................................................
C.4.2 Create and delete management operations
Notifications .
c.4.3
..............................................................................................................................
c.4.4 Actions
.........................................................................................................................
c.4.5 Parameters
....................................................
Annex D - MOCS proforma for “Heterogeneous scanner” managed object class
D. 1 Introduction .
............................
D.l.1 Instructions for completing the MOCS proforma to produce a MOCS
..................................................................................... 26
D.1.2 Symbols, abbreviations and terms
0 ISO/IEC 1997
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm, without permission in writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland
ii
ISO/IEC 1016443 : 199YAmd.l: 1997 (E)
0 ISO/IEC
......................................................................
D.2 Statement of conformance to the managed object class
D.3 Packages .
............................................................................................................................................
D.4 Attributes
D.5 Notifications .
................................................................................................................................................
D.6 Actions
D.7 Parameters .
..............................................................
Annex E - MOCS proforma for “Buffered scanner” managed object class
E.l .
Introduction
............................ 34
E.l.l Instructions for completing the MOCS proforma to produce a MOCS
E.1.2 Symbols, abbreviations and terms .
...................................................................... 34
E.2 Statement of conformance to the managed object class
E.3 Packages .
E.4 Attributes .
........................................................................................................................................
E.5 Notifications
E.6 Actions .
E.7 Parameters .
................................................................. 41
Annex F - MOCS proforma for “Simple scanner” managed object class
F.l Introduction .
F.l.l Instructions for completing the MOCS proforma to produce a MOCS .
F.1.2 Symbols, abbreviations and terms .
...................................................................... 41
F.2 Statement of conformance to the managed object class
F.3 Packages .
............................................................................................................................................ 42
F.4 Attributes
F.5 Notifications .
F.6 Actions .
F.7 Parameters .
.................................................................. 47
Annex G - MOCS proforma for “Mean scanner” managed object class
G. 1 Introduction .
............................ 47
G.l.l Instructions for completing the MOCS proforma to produce a MOCS
G.1.2 Symbols, abbreviations and terms .
G.2 Statement of conformance to the managed object class .
G.3 Packages .
G.4 Attributes .
G. 5 Notifications .
................................................................................................................................................
G.6 Actions
G.7 Parameters .
.................................................... 53
Annex H - MOCS proforma for “Mean variance scanner” managed object class
.........................................................................................................................................
H. 1 Introduction
............................ 53
H.l.1 Instructions for completing the MOCS proforma to produce a MOCS
H.1.2 Symbols, abbreviations and terms .
...................................................................... 53
H.2 Statement of conformance to the managed object class
H.3 Packages .
H.4 Attributes .
H.5 Notifications .
H.6 Actions .
...........................................................................................................................................
H.7 Parameters
.............................................................. 58
Annex I - MOCS proforma for “Min max scanner” managed object class
I.1 Introduction .
............................ 58
1.1.1 Instructions for completing the MOCS proforma to produce a MOCS
1.1.2 Symbols, abbreviations and terms .
Statement of conformance to the managed object class . 58
I.2
I.3 Packages .
............................................................................................................................................
I.4 Attributes
. . .
@ ISOIIEC
ISO/IEC 10164-13 : 199YAmd.l : 1997 (E)
I.5 Notifications . 62
I.6 Actions . 62
I.7 Parameters . 62
............................................................. 63
Annex J - MOCS proforma for “Percentile scanner” managed object class
J.l Introduction . 63
J.l.l Instructions for completing the MOCS proforma to produce a MOCS . 63
5.1.2 Symbols, abbreviations and terms . 63
J.2 Statement of conformance to the managed object class . 63
J.3 Packages . 64
............................................................................................................................................ 65
5.4 Attributes
J.5 Notifications . 67
J.6 Actions . 67
........................................................................................................................................... 67
J.7 Parameters
Annex IS - MOCS proforma for “Dynamic simple scanner” managed object class . 68
K. 1 Introduction . 68
K.l.1 Instructions for completing the MOCS proforma to produce a MOCS . 68
K.1.2 Symbols, abbreviations and terms . 68
K.2 Statement of conformance to the managed object class . 68
..............................................................................................................................................
K.3 Packages 69
K.4 Attributes . 69
K.5 Notifications . 70
K.6 Actions . 70
K.7 Parameters . 71
Annex L - MOCS proforma for “Buffered scan report record” managed object class . 72
L.l
Introduction . 72
L.l.l Instructions for completing the MOCS proforma to produce a MOCS . 72
L.1.2 Symbols, abbreviations and terms . 72
L.2 Statement of conformance to the managed object class . 72
L.3 Packages . 73
L.4 Attributes . 74
Annex M - MOCS proforma for “Scan report record” managed object class
.......................................................... 76
M. 1 Introduction . 76
M.l.1 Instructions for completing the MOCS proforma to produce a MOCS . 76
M.1.2 Symbols, abbreviations and terms . 76
M.2 Statement of conformance to the managed object class .
M.3 Packages . 77
M.4 Attributes .
Annex N - MOCS proforma for “Statistical report record” managed object class . 80
N. 1 Introduction .
N.l.l Instructions for completing the MOCS proforma to produce a MOCS . 80
N.1.2 Symbols, abbreviations and terms .
N.2 Statement of conformance to the managed object class . 80
N.3 Packages .
N.4 Attributes . 82
Annex 0 - MRCS proforma for name binding .
0.1 Introduction . 84
0.1.1 Symbols, abbreviations and terms . 84
0.2 Instructions for completing the MRCS proforrna for name binding to produce a MRCS .
0.3 Statement of conformance to the name binding . 84
iv
0 ISOIIEC ISO/IEC 1016443 : 199YAmd.l: 1997 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form
the specialized system for worldwide standardization. National bodies that are members of IS0 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. IS0 and IEC technical committees collaborate in fields of mutual interest.
Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the
work.
In the field of information technology, IS0 and IEC have established a joint technical committee, ISO/IEC 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.
Amendment 1 to International Standard ISO/IEC 10164- 13: 1995 was prepared by Joint Technical Committee
ISOIIEC JTC 1, Information technology, Subcommittee SC 21, Open systems interconnection, data management and
open distributed processing, in collaboration with ITU-T. The identical text is published as ITU-T Rec. X.738/Amd. 1.

0 ISO/IEC
ISO/IEC 10164-13 : 199YAmd.l : 1997 (E)
Introduction
ITU-T Rec. X.738 1 ISO/IEC 10164-13 provides many possible options for implementors to choose from in the
development of a product. This means that an Operations System (OS) product from one vendor needing to interwork
with an OS product from another vendor must be developed to some common and explicit agreement both developers
use concerning the actual options to be developed in their software products for X.738-based messages. This amendment
provides a means to specify message options in such a way that the later documentation of actual options chosen for a
product can be more explicit. The result is that the time to carry out interoperability tests between an OS from one
vendor and an OS from another vendor may be reduced because product developers can be provided with more explicit
message specification.
vi
ISO/IEC 10164-13 : 199YAmd.l : 1997 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION -
SYSTEMS MANAGEMENT: SUMMARIZATION FUNCTION
AMENDMENT 1
Implementation conformance statement proformas
Subclause 2.1
1)
Add the following reference:
cc
-
ITU-T Recommendation X.724 (1993) i ISO/IEC 10165-6: 1994, Information technology - Open Systems
Interconnection - Structure of management information: Requirements and guidelines for implementation
conformance statement proformas associated with OSI management . ‘) ‘)
Subclause 2.2
2)
Add the following references:
-
CCITT Recommendation X.291 (1992), OSI conformance testing methodology and framework for
protocol Recommendations for CCITT applications -Abstract test suite spec@ation.
ISO/IEC 9646-2: 1994, Information technology - Open Systems Interconnection - Conformance testing
methodology andfiamework - Part 2: Abstract test suite speczjication.
-
ITU-T Recommendation X.296 (1995), OSI conformance testing methodology and j?amework for
protocol Recommendations for ITU-T applications - Implementation conformance statements.
ISO/IEC 9646-7: 1995, Information technology -
Open Systems Interconnection - Conformance testing
methodology andfiamework - Part 7: Implementation Conformance Statements. ”
Subclause 3.3
3)
Insert the following terms:
“e) Managed Object Conformance Statement (MOCS);
f) Management Information Conformance Statement (MICS);
k) MICS proforma;
1) MOCS proforma.”
“dependent conformance and d): “general conformance ”.
Delete items c):
ReIabeI the list items and re-arrange the list in alphabetic order.
Subclause 3.7
4)
Add the following terms:
“b) PICS proforma;
c) protocol implementation conformance statement.”
Replace the dash “-” of the term “alarm” with “a) “.
ITU-T Rec. X.738 (1993)/Amd.l (1996 E)
ISO/IEC 10164-13 : 1995/Amd.l : 1997 (E)
Subclause 3.9
5)
Add the following new subclause, immediately after 3.8:
Cb
39 . Implementation conformance statement proforma definitions
This Recommendation 1 International Standard makes use of the following terms defined in ITU-T Rec. X.724 (
ISO/IEC 10165-6:
a) Management Conformance Summary (MCS);
b) Managed Relationship Conformance Statement (MRCS);
c) MCS proforma;
d) MRCS proforma.”
The subclauses which follow the new subclause 3.9 should be renumbered accordingly.
Clause 4
6)
Insert the following abbreviations in the existing list of abbreviations, by alphabetical order:
Implementation Conformance Statement
“ICS
MCS Management Conformance Summary
Management Information Conformance Statement
MICS
MIDS Management Information Definition Statement
Managed Relationship Conformance Statement”
MRCS
Clause 13
7)
RepZace clause I3 by the following:
13 Conformance
International Standard shall with the
Implementations claiming to conform to this Recommendation comply
conformance requirements as defined in the following subclauses.
13.1 Static conformance
The implementation shall c onform to the requirements of this Recommendation 1 International Standard in the manager
role, the agent role, or both roles. A claim of conformance to at least one role shall be made in Table B. 1.
If a claim of conformance is made for support in the manager role, the implementation shall support at least one
management operation or notification or action of the managed objects specified by this Recommendation 1 International
Standard. The conformance requirements in the manager role for those management operations and notifications and
actions are identified in Table B.3 and further tables referenced by Annex B.
If a claim of conformance is made for support in the agent role, the implementation shall support one or more instances
of the managed object classes identified in Table B.4 and further tables referenced by Annex B.
The implementation shall support the transfer syntax derived from the encoding rules specified in CCITT Rec. X.209 1
ISO/IEC 8825 named Cjoint-iso-ccitt asnl( 1) basicEncoding( 1)) for the abstract data types referenced by the definitions
for which support is claimed.
ITU-T Rec. X.738 (1993)/Amd.l (1996 E)
ISO/IEC 10164-13 : 199WAmd.l : 1997 (E)
Dynamic conformance
13.2
Implementations claiming to conform to this Recommendation 1 International Standard shall support the elements of
procedure and definitions of semantics
corresponding to the defini tions for which support i s claimed.
13.3 Management implementation conformance statement requirements
Any MCS proforma, MICS proforma, MOCS proforma, and MRCS proforma which conforms to this Recommendation 1
International Standard shall be technically identical to the proformas specified in Annex B through Annex 0 preserving
table numbering and the index numbers of items, and differing only in pagination and page headers.
The supplier of an implementation which is claimed to conform to this Recommendation 1 International Standard shall
complete a copy of the Management Conformance Summary (MCS) provided in Annex B as part of the conformance
requirements together with any other ICS proformas referenced as applicable from that MCS. A ICS which conforms to
this Recommendation 1 International Standard shall:
-
describe an implementation which conforms to this Recommendation I International Standard;
-
have been completed in accordance with the instructions for completion given in ITU-T Rec. X.724 I
ISO/IEC 10 165-6;
-
include the information necessary to uniquely identify both the supplier and the implementation.
Claims of conformance to the management information defined in this Recommendation I International Standard in
managed object classes defined elsewhere shall include the requirements of the MIDS proforma in the MOCS proforma
for the managed object class.”
New annexes
8)
Add the following new annexes immediately after Annex A:
ITU-T Rec. X.738 (1993)/Amd.l (1996 E) 3

ISO/IEC 10164-13 : 1995/Amd.l : 1997 (E)
Annex B
MCS proforma ’)
(This annex forms an integral part of this Recommendation I
International Standard)
Bl . Introduction
B.1.1 Purpose and structure
ier that identifies an implementation and
The Management Conformance Summary (MCS) is a statement by a suppl
the implementation claims conformance to any of the listed set of documents that
provides information on whether
specify conformance requirements to OS1 management.
The MCS proforma is a document, in the form of a questionnaire that when completed by the supplier of an
implementation becomes the MCS.
B.1.2 Instructions for completing the MCS proforma to produce an MCS2)
statement in each of the boxes provided. Specific instruction
The supplier of the implementation shall enter an explicit is
provided in the text which precedes each table.
B.1.3 Symbols, abbreviations and terms
For all annexes of this Recommendation ( International Standard, the following common notations, defined in CCITT
Rec. X.291 and ISO/IEC 9646-2 and ITU-T Rec. X.296 1 ISO/IEC 9646-7 are used for the Status column:
m Mandatory;
0 Optional;
C Conditional;
X Prohibited;
-
Not applicable or out of scope.
NOTES
‘c ’, ‘m ’, and ‘0’ are prefixed by a ‘c:’ when nested under a conditional or optional item of the same table.
2 ‘0’ may be suffixed by ‘.N’ (where N is a unique number) for mutually exclusive or selectable options among a set of
status values. Support of at least one of the choices (from the items with the same values of N) is required.
For all annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 and ISO/IEC 9646-2 and ITU-T Rec. X.296 1 ISO/IEC 9646-7 are used for the Support column:
Y Implemented;
N Not implemented;
-
No answer required;
The item is ignored (i.e. processed syntactically but not semantically).
k
B.1.4 Table format
Some of the tables in this Recommendation I International Standard have been split because the information is too wide
to fit on the page. Where this occurs, the index number of the first block of columns are the index numbers of the
corresponding rows of the remaining blocks of columns. A complete table reconstructed from the constituent parts
should have the following layout:
Index First block of columns
Second block of columns Etc.
In this Recommendation I International Standard the constituent parts of the table appear consecutively, starting with the
first block of columns.
*) Copyright release for MCS proforma
Users of this Recommendation 1 International Standard may freely reproduce the MCS proforma in this annex so that it can be
used for its intended purpose, and may further publish the completed MCS.
2, Instructions for completing the MCS proforma are specified in ITU-T Rec. X.724 1 ISO/IEC 10 165-6.
ITU-T Rec. X.738 (1993)/Amd.l (1996 E)
ISO/IEC 10164-13 : 199YAmd.l : 1997 (E)
When a table with sub-rows is too wide to fit on a page, the continuation tables(s) have been constructed with index
numbers identical to the index numbers in the corresponding rows of the first table, and with sub-index numbers
corresponding to the sub-rows within each indexed row. For example, if Table X.1 has 2 rows and the continuation of
Table X.1 has 2 sub-rows for each row, the tables are presented as follows.
Table X.1 - Title
support
l
Index G
A B C D E F
-
1 a b
-
2 a b
Table X.1 (continued) - Title
H I J
Index Subindex K L
i
1 1.1 h
j
1.2 h i
j
2 2.1 h i
j
2.2 h i
j
A complete table reconstructed from the constituent parts should have the following layout:
support
I I
Index A B C D E F G Subindex H
I J K L
1 a b - 1.1 h i
j
1.2 h i
j
2 a b - 2.1 h i
j
2.2 h i
j
References made to cells within tables shall be interpreted as references within reconstructed tabled. In the example,
above, the reference X. l/id corresponds to the blank cell in the column G for row with Index 1, and X.1/1.2b
corresponds to the blank cell in column L for row with Sub-index 1.2.
B2 . Identification of the implementation
B.2.1 Date of statement
The supplier of the implementation shall enter the date of this statement in the box below. Use the format
DD-MM-YYYY.
Date of statement
ITU-T Rec. X.738 (1993)/Amd.l (1996 E)

ISO/IEC 10164-13 : 1995/Amd.l : 1997 (E)
B.2.2 Identification of the implementation
The supplier of the implementation shall enter information necessary to uniquely identify the implementation and the
system(s) in which it may reside, in the box below.
B.2.3 Contact
The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the
content of the MCS, in the box below.
,
B3 . Identification of the Recommendation 1 International Standard in which the management
information is defined
The supplier of the implementation shall enter the title, reference number and date of the publication of the
Recommendation ) International Standard which specifies the management information to which conformance is
claimed, in the box below.
Recommendation / International Standard to which conformance is claimed
B.3.1 Technical corrigenda implemented
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified Recommendation 1 International Standard, in the box below.
B.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the
identified Recommendation 1 International Standard, in the box below.
B4 . Management conformance summary
The supplier of implementation shall state the capabilities and features supported and provide summary of conformance
claims to Recommendations I International Standards using the tables in this annex.
The supplier of the implementation shall specify the roles that are supported, in Table B. 1.
6 ITU-T Rec. X.738 (1993)/Amd.l (1996 E)

ISO/IEC 10164-13 : 199YAmd.l : 1997 (E)
Table B.l - Roles
Index Roles supported status Additional information
support
1 Manager role support 0.1
2 Agent role support 0.1
The supplier of the implementation shall specie support for the systems management functional units in Table B.2.
Table B.2 - Systems management functional units
Manager
Agent
Status
Index Capability support status support Additional information
1 Scan stimulation functional unit cl c2
2 Summarization event reporting functional cl c2
unit
cl: if B.l/la then o else -
c2: if B. 1/2a then o else -
The supplier of the implementation shall specify support for management information in the manager role, in Table B.3.
Table B.3 - Manager role minimum conformance requirement
Index Item status support
Additional information
1 Operations on managed objects c3
2 Buffered scan report notification c4
3 Scan report notification c4
c4
4 Statistical report notification
c5
5 Activate dynamic simple scan report action
6 Activate scan report action C5
7 Activate statistical report action c5
8 Report buffer action c5
c3
9 Object creation notification from at least one
summarization managed objects
c3
10 Object deletion notification from at least one
summarization managed objects
c3
11 Attribute value change notification from at
least summarization managed objects
c3
12 State change notification from at least one
summarization managed objects
c3: if B. l/l a then 0.2 else -
c4:
if B.2/2a then 0.3 else (if B. l/l a then 0.2 else -)
c5:
if B.2/1 a then 0.4 else (if B. l/l a then 0.2 else -)
The supplier of the implementation shall specie support for management information in the agent role, in Table B.4.
ITU-T Rec. X.738 (1993)/Amd.l (1996 E) 7

ISO/IEC 10164-13 : 1995/Amd.l : 1997 (E)
Table B.4 - Agent role minimum conformance requirement
status status
Index Index Item Item support support Additional Additional information information
1 1 Heterogeneous Heterogeneous scanner scanner managed managed object object c6 c6
2 2 Buffered Buffered scanner scanner managed managed object object c6 c6
3 3 Simple Simple scanner scanner managed managed object object c6 c6
4 4 c6 c6
Mean Mean scanner scanner managed managed object object
I I I I
c6 c6
5 5 Mean Mean variance variance scanner scanner managed managed object object
6 6 Min max scanner managed object c6 c6
Min max scanner managed object
c6 c6
7 7 Percentile Percentile scanner scanner managed managed object object
c6 c6
8 8 Dynamic Dynamic simple simple scanner scanner managed managed object object
c6: c6:
if if B.l/2a B.l/2a then then 0.5 0.5 else else - -
Table B.5 - Logging of event records
Additional information
Index Status support
1 Does the implementation support logging of c7
event records in agent role?
c7: if B.l/2a then o else -
I I
NOTE 1 - Conformance to this Recommendation 1 International Standard does not require conformance to CCITT
Rec. X.735 1 ISOLIEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the Recommendation 1
International Standards summarized in Tables B.6 to B.9. For each Recommendation I International Standard that the
supplier of the implementation claims conformance to, the corresponding conformance statement(s) shall be completed,
or referenced by, the MCS. The supplier of the implementation shall complete the Support, Table numbers and
Additional information columns.
In Tables B.6 to B.9, the Status column is used to indicate whether the supplier of the implementation is required to
complete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tables
or referenced items and are not changed by the value of the MCS Status column. Similarly, the Support column is used
by the supplier of the implementation to indicate completion of the referenced tables or referenced items.
NOTE 2 - Conformance to the MAPDUs defined in this Recommendation 1 International Standard can be claimed by
completing the corresponding tables in the MICS and MOCS annexes of the referenced Recommendation 1 International Standard.
Table B.6 - PICS support summary
Identification of the
Table
Table
document that Constraints
numbers Additional
Index
Description Status support numbers
includes the PICS
of PIGS and values information
of PIGS
proforma
proforma
-
1 CCITT Rec. X.730 1
Annex E Systems Oa)
ISOLIEC 10164-l
all tables management
application
context
a>
The supplier of implementation shall indicate the application contexts supported.
8 ITU-T Rec. X.738 (1993)/Amd.l (1996 E)

ISO/IEC 10164-13 : 1995/Amd.l : 1997 (E)
Table B.7 - MOCS support summary
Identification of the Table
Table
Constraints Additional
document that numbers
number
Description
Index Status Support
includes the MOCS of MOCS and values information
of MOCS
proforma proforma
-
1 Annex C obj ectcreation c8
CCITT Rec. X.730 1
obj ectDeletion
ISO/IEC 10 164- 1 all tables
attributevalue
Change records
-
2 CCITT Rec. X.73 1 1 Annex C statechange c8
Record
ISO/IEC 10 164-2 all tables
I
-
3 ITU-T Rec. X.738 1 Annex D heterogeneous c9
all tables Scanner
ISO/IEC 10 164- 13
bufferedscanner - cl0
4 ITU-T Rec. X.738 1 Annex E
all tables
ISO/IEC 10164-13
-
Annex F simplescanner cl1
5 ITU-T Rec. X.738 I
ISO/IEC 10164-13 all tables
-
6 ITU-T Rec. X.738 I Annex G meanscanner cl2
all tables
ISO/IEC 10164-13
-
meanvariance cl3
7 ITU-T Rec. X.738 I Annex H
ISO/IEC 10164-13 all tables Scanner
-
8 ITU-T Rec. X.738 I Annex I minMaxScanner cl4
all tables
ISO/IEC 10164-13
percentilescanner - cl5
9 ITU-T Rec. X.738 I Annex J
ISO/IEC 10164-13 all tables
-
10 ITU-T Rec. X.738 I Annex K dynamicsimple cl6
all tables Scanner
ISO/IEC 10164-13
-
Annex L bufferedscan cl7
11 ITU-T Rec. X.738 I
ISO/IEC 10164-13 all tables ReportRecord
scanReportRecord -
12 ITU-T Rec. X.738 I Annex M cl8
ISO/IEC 10164-13 all tables
-
StatisticalReport cl9
13 ITU-T Rec. X.738 I Annex N
all tables Record
ISO/IEC 10164-13
c8: if (B.4/la or B.4/2a or B.4/3a or B.4/4a or B.4/5a or B.4/6a or B.4/7a) and B.5/la then m else -
c9: if B.4/1a then m else -
cl 0: if B.4/2a then m else -
cl 1: if B.4/3a then m else -
~12: if B.4/4a then m else -
~13: if B.4/5a then m else -
~14: if B.4/6a then m else -
cl 5: if B.4/7a then m else -
cl 6: if B.4/8a then m else -
cl 7: if B. 1/2a and B.4/2a and B.5/la then m else -
cl 8: if B. 1/2a and (B.4/1 a or B.4/3a) and B.50 a then m else -
~19: if B.l/2a and (B4/4a or B.4/5a or B.4/6a or B.4/7a) and B.5/la then m else -
ITU-T Rec. X.738 (1993)/Amd.l (1996 E)

ISO/IEC 10164-13 : 1995/Amd.l : 1997 (E)
Table B.8 - MRCS support summary
Identification of the Table
Table
Additional
numbers Constraints
document that
Description Status Support numbers of
Index
information
includes the MRCS of MRCS and values
MRCS
proforma
proforma
-
c20
1 Annex 0, dynamicSimple
ITU-T Rec. X.738 I
0.1/l Scanner-system
ISO/IEC 10164-13
c21
2 Annex 0, conflictingpackages -
ITU-T Rec. X.738 I
0.112 Scanner-system
ISO/IEC 10164-13
-
c22
logRecord-log
3 Annex D,
CCITT Rec. X.735 I
D.l/l
ISO/IEC 10164-6
if B.4/8a then m else -
~20:
~21: if B.4/la or B.4/2a or B.4/3a or B.4/4a or B.4/5a B.4/6a or B.4/7a then m else -
~22: if B.5/la then m else -
Table B.9 - MICS support summary
Identification of the Table
Table
Additional
Constraints
document that numbers of
Description SWUS SUPPOI? numbers of infomation
Index
and values
includes the MICS MICS
MICS
proforma
proforma
- c23
Table C.l to Management oprations
1 ITU-T Rec. X.738 I
ISO/IEC 10164-13 c.10
-
objectcreation, c24
2 CCITT Rec. X.730 I Table B. 1
objectDeletion and
ISO/IEC 10164-l
attributeValueChange
notifications
-
~25
3 CCITT Rec. X.73 1 I Table B.l statechang
...

NORME ISO/CEI
INTERNATIONALE 10164-13
Première édition
1995-06-01
AMENDEMENT 1
1997-04-01
Technologies de l'information —
Interconnexion de systèmes ouverts
(OSI) — Gestion-systèmes: Fonction de
récapitulation
AMENDEMENT 1: Formulaires de déclaration
de conformité d'instance
Information technology — Open Systems Interconnection — Systems
Management: Summarization Function
AMENDMENT 1: Implementation conformance statement proformas
Numéro de référence
ISO/CEI 10164-13:1995/Amd.1:1997(F)
©
ISO/CEI 1997
ISO/CEI 10164-13:1995/Amd.1:1997(F)
PDF – Exonération de responsabilité
Le présent fichier PDF peut contenir des polices de caractères intégrées. Conformément aux conditions de licence d'Adobe, ce fichier peut
être imprimé ou visualisé, mais ne doit pas être modifié à moins que l'ordinateur employé à cet effet ne bénéficie d'une licence autorisant
l'utilisation de ces polices et que celles-ci y soient installées. Lors du téléchargement de ce fichier, les parties concernées acceptent de fait la
responsabilité de ne pas enfreindre les conditions de licence d'Adobe. Le Secrétariat central de l'ISO décline toute responsabilité en la
matière.
Adobe est une marque déposée d'Adobe Systems Incorporated.
Les détails relatifs aux produits logiciels utilisés pour la création du présent fichier PDF sont disponibles dans la rubrique General Info du
fichier; les paramètres de création PDF ont été optimisés pour l'impression. Toutes les mesures ont été prises pour garantir l'exploitation de
ce fichier par les comités membres de l'ISO. Dans le cas peu probable où surviendrait un problème d'utilisation, veuillez en informer le
Secrétariat central à l'adresse donnée ci-dessous.
© ISO/CEI 1997
Droits de reproduction réservés. Sauf prescription différente, aucune partie de cette publication ne peut être reproduite ni utilisée sous quelque
forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et les microfilms, sans l'accord écrit de l’éditeur.
ISO/CEI Copyright office � Case postale 56 � CH-1211 Genève 20 � Suisse
Version française tirée en 1999
ImpriméenSuisse
ii © ISO/CEI 1997 – Tous droits réservés

ISO/CEI 10164-13:1995/Amd.1:1997(F)
Sommaire
Page
1) Paragraphe 2.1. 1
2) Paragraphe 2.2. 1
3) Paragraphe 3.3. 1
4) Paragraphe 3.7. 2
5) Paragraphe 3.9. 2
3.9 Définition des formulaires de déclaration de conformité d'instance . 2
6) Article 4. 2
7) Article 13. 2
13) Conformité . 2
13.1 Conformité statique. 2
13.2 Conformité dynamique . 3
13.3 Prescriptions de la déclaration de conformité de l'instance de gestion . 3
8) Nouvelles annexes. 3
Annexe B – Formulaire MCS. 4
B.1 Introduction. 4
B.1.1 Purpose and structure. 4
B.1.2 Instructions for completing the MCS proforma to produce an MCS . 4
B.1.3 Symbols, abbreviations and terms. 4
B.1.4 Table format. 4
B.2 Identification of the implementation. 5
B.2.1 Date of statement . 5
B.2.2 Identification of the implementation. 6
B.2.3 Contact . 6
B.3 Identification of the Recommendation | International Standard in which the management
information is defined . 6
B.3.1 Technical corrigenda implemented. 6
B.3.2 Amendments implemented. 6
B.4 Management conformance summary . 6
Annexe C – Formulaire MICS . 11
C.1 Introduction. 11
C.2 Instructions for completing the MICS proforma to produce a MICS . 11
C.3 Symbols, abbreviations and terms. 11
C.4 Statement of conformance to the management information. 11
C.4.1 Attributes . 11
C.4.2 Create and delete management operations. 15
C.4.3 Notifications. 17
C.4.4 Actions . 20
C.4.5 Parameters. 25
Annexe D – Formulaire MOCS pour la classe d'objet géré «Heterogeneous scanner» . 26
D.1 Introduction. 26
D.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 26
D.1.2 Symbols, abbreviations and terms. 26
D.2 Statement of conformance to the managed object class. 26
D.3 Packages. 27
D.4 Attributes . 28
D.5 Notifications. 30
D.6 Actions . 33
D.7 Parameters. 33
© ISO/CEI 1997 – Tous droits réservés iii

ISO/CEI 10164-13:1995/Amd.1:1997(F)
Page
Annexe E – Formulaire MOCS pour la classe d'objet géré «Buffered scanner». 34
E.1 Introduction. 34
E.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 34
E.1.2 Symbols, abbreviations and terms. 34
E.2 Statement of conformance to the managed object class. 34
E.3 Packages. 35
E.4 Attributes . 36
E.5 Notifications. 38
E.6 Actions . 39
E.7 Parameters. 40
Annexe F – Formulaire MOCS pour la classe d'objet géré «Simple scanner». 41
F.1 Introduction. 41
F.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 41
F.1.2 Symbols, abbreviations and terms. 41
F.2 Statement of conformance to the managed object class. 41
F.3 Packages. 42
F.4 Attributes . 43
F.5 Notifications. 45
F.6 Actions . 45
F.7 Parameters. 46
Annexe G – Formulaire MOCS pour la classe d'objet géré «Mean scanner» .47
G.1 Introduction. 47
G.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 47
G.1.2 Symbols, abbreviations and terms. 47
G.2 Statement of conformance to the managed object class. 47
G.3 Packages. 48
G.4 Attributes . 49
G.5 Notifications. 51
G.6 Actions . 52
G.7 Parameters. 52
Annexe H – Formulaire MOCS pour la classe d'objet géré «Mean variance scanner». 53
H.1 Introduction. 53
H.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 53
H.1.2 Symbols, abbreviations and terms. 53
H.2 Statement of conformance to the managed object class. 53
H.3 Packages. 54
H.4 Attributes . 55
H.5 Notifications. 57
H.6 Actions . 57
H.7 Parameters. 57
Annexe I – Formulaire MOCS pour la classe d'objet géré «Min max scanner».58
I.1 Introduction. 58
I.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 58
I.1.2 Symbols, abbreviations and terms. 58
I.2 Statement of conformance to the managed object class. 58
I.3 Packages. 59
I.4 Attributes . 60
I.5 Notifications. 62
I.6 Actions . 62
I.7 Parameters. 62
Annexe J – Formulaire MOCS pour la classe d'objet géré «Percentile scanner». 63
J.1 Introduction. 63
J.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 63
J.1.2 Symbols, abbreviations and terms. 63
iv © ISO/CEI 1997 – Tous droits réservés

ISO/CEI 10164-13:1995/Amd.1:1997(F)
Page
J.2 Statement of conformance to the managed object class. 63
J.3 Packages. 64
J.4 Attributes . 64
J.5 Notifications. 67
J.6 Actions . 67
J.7 Parameters. 67
Annex K – Formulaire MOCS pour la classe d'objet géré «Dynamic simple scanner» . 68
K.1 Introduction. 68
K.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 68
K.1.2 Symbols, abbreviations and terms. 68
K.2 Statement of conformance to the managed object class. 68
K.3 Packages. 70
K.4 Attributes . 70
K.5 Notifications. 71
K.6 Actions . 71
K.7 Parameters. 72
Annexe L – Formulaire MOCS pour la classe d'objet géré «Buffered scan report record» . 73
L.1 Introduction . 73
L.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 73
L.1.2 Symbols, abbreviations and terms. 73
L.2 Statement of conformance to the managed object class. 73
L.3 Packages. 74
L.4 Attributes . 75
Annexe M – Formulaire MOCS pour la classe d'objet géré «Scan report record» . 77
M.1 Introduction. 77
M.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 77
M.1.2 Symbols, abbreviations and terms. 77
M.2 Statement of conformance to the managed object class. 77
M.3 Packages. 78
M.4 Attributes . 79
Annexe N – Formulaire MOCS pour la classe d'objet géré «Statistical report record» . 81
N.1 Introduction. 81
N.1.1 Instructions for completing the MOCS proforma to produce a MOCS . 81
N.1.2 Symbols, abbreviations and terms. 81
N.2 Statement of conformance to the managed object class. 81
N.3 Packages. 82
N.4 Attributes . 83
Annexe O – Formulaire MRCS pour la corrélation de noms . 85
O.1 Introduction. 85
O.1.1 Symbols, abbreviations and terms. 85
O.2 Instructions for completing the MRCS proforma for name binding to produce a MRCS . 85
O.3 Statement of conformance to the name binding. 85
© ISO/CEI 1997 – Tous droits réservés v

ISO/CEI 10164-13:1995/Amd.1:1997(F)
Avant-propos
L'ISO (Organisation internationale de normalisation) et la CEI (Commission électrotechnique internationale)
forment le système spécialisé de la normalisation mondiale. Les organismes nationaux membres de l'ISO ou de la
CEI participent au développement de Normes internationales par l'intermédiaire des comités techniques créés par
l'organisation concernée afin de s'occuper des domaines particuliers de l'activité technique. Les comités
techniques de l'ISO et de la CEI collaborent dans des domaines d'intérêt commun. D'autres organisations
internationales, gouvernementales et non gouvernementales, en liaison avec l'ISO et la CEI participent également
aux travaux.
Dans le domaine des technologies de l'information, l'ISO et la CEI ont créé un comité technique mixte,
l'ISO/CEI JTC 1. Les projets de Normes internationales adoptés par le comité technique mixte sont soumis aux
organismes nationaux pour vote. Leur publication comme Normes internationales requiert l'approbation de 75 % au
moins des organismes nationaux votants.
L’Amendement 1 à la Norme internationale ISO/CEI 10164-13:1995 a été élaboré par le comité technique mixte
ISO/CEI JTC 1, Technologies de l'information, sous-comité SC 21, Interconnexion des systèmes ouverts, gestion
des données et traitement distribué ouvert, en collaboration avec l'UIT-T. Le texte identique est publié en tant que
Rec. UIT-T X.738/Amd.1.
vi © ISO/CEI 1997 – Tous droits réservés

ISO/CEI 10164-13:1995/Amd.1:1997(F)
Introduction
La Rec. UIT-T X.738 | ISO/CEI 10164-13 offre le plus grand nombre d'options possibles aux réalisateurs qui pourront
ainsi opérer un choix au moment d'élaborer un produit. Autrement dit, le système d'exploitation (OS) d'un constructeur
qui a besoin d'interfonctionner avec l'OS d'un autre constructeur doit être élaboré sur la base d'un accord explicite
commun que les deux concepteurs appliqueront aux options effectives à prévoir dans leur logiciel pour les messages de
type X.738. Cet amendement permet de spécifier les options des messages de façon à expliciter les textes ultérieurs qui
concerneront les options effectivement choisies pour le produit. Il s'ensuit que les délais nécessaires pour procéder aux
tests d'interfonctionnement entre l'OS d'un constructeur et l'OS d'un autre constructeur peuvent être réduits parce que les
concepteurs de produits disposeront d'une spécification plus explicite des messages.
© ISO/CEI 1997 – Tous droits réservés vii

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
NORME INTERNATIONALE
ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
Rec. UIT-T X.738 (1993)/Amd.1 (1996 F)
RECOMMANDATION UIT-T
TECHNOLOGIES DE L'INFORMATION – INTERCONNEXION
DE SYSTÈMES OUVERTS (OSI) – GESTION-SYSTÈMES: FONCTION
DE RÉCAPITULATION
AMENDEMENT 1
Formulaires de déclaration de conformité d'instance
1) Paragraphe 2.1
Ajouter la référence suivante:
«– Recommandation UIT-T X.724 (1993) | ISO/CEI 10165-6:1994, Technologies de l'information –
Interconnexion des systèmes ouverts – Structure de l'information de gestion: spécifications et directives
pour l'établissement des formulaires de déclaration de conformité d'instances associés à la gestion OSI.»
2) Paragraphe 2.2
Ajouter les références suivantes:
«– Recommandation X.291 du CCITT (1992), Cadre général et méthodologie des tests de conformité OSI
pour les Recommandations sur les protocoles pour les applications du CCITT – Spécification des suites
de tests abstraites.
ISO/CEI 9646-2:1994, Technologies de l'information – Interconnexion de systèmes ouverts – Cadre
général et méthodologie des tests de conformité OSI – Partie 2: Spécification des suites de tests
abstraites.
– Recommandation UIT-T X.296 (1995), Cadre général et méthodologie des tests de conformité OSI pour
les Recommandations sur les protocoles pour les applications de l'UIT – Déclarations de conformité
d'instance.
ISO/CEI 9646-7:1995, Technologies de l'information – Interconnexion de systèmes ouverts (OSI) –
Essais de conformité – Méthodologie générale et procédures: Déclarations de conformité des mises en
œuvre.»
3) Paragraphe 3.3
Ajouter les termes suivants:
«e) déclaration de conformité d'objet géré (MOCS, managed object conformance statement);
f) déclaration de conformité d'information de gestion (MICS, management information conformance
statement);
k) formulaire MICS;
l) formulaire MOCS.»
Supprimer les points c): «conformité dépendante» et d): «conformité générale».
Relibeller et remettre par ordre alphabétique la liste des points.
Rec. UIT-T X.738 (1993)/Amd.1 (1996 F) 1

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
4) Paragraphe 3.7
Ajouter les termes suivants:
«b) formulaire PICS;
c) déclaration de conformité d'instance de protocole.»
Remplacer le tiret «–» du terme «alarm» par «a)».
5) Paragraphe 3.9
Introduire le nouveau paragraphe suivant, immédiatement après 3.8:
«3.9 Définition des formulaires de déclaration de conformité d'instance
La présente Recommandation | Norme internationale utilise les termes suivants définis dans la Rec. UIT-T X.724 |
ISO/CEI 10165-6:
a) récapitulatif de conformité de gestion (MCS, management conformance summary);
b) déclaration de conformité de relation gérée (MRCS, managed relationship conformance statement);
c) formulaire MCS;
d) formulaire MRCS.»
Les paragraphes qui suivent le nouveau paragraphe 3.9 doivent être renumérotés en conséquence.
6) Article 4
Insérer les abréviations suivantes, par ordre alphabétique, à l'article 4:
«ICS Déclaration de conformité d'instance (implementation conformance statement)
MCS Récapitulatif de conformité de gestion (management conformance summary)
MICS Déclaration de conformité d'information de gestion (management information conformance
statement)
MIDS Déclaration de définition d'information de gestion (management information definition statement)
MRCS Déclaration de conformité de relation gérée (managed relationship conformance statement)
7) Article 13
Remplacer l’article 13 par:
«13 Conformité
Les réalisations réputées conformes à la présente Recommandation | Norme internationale répondront aux prescriptions
de conformité définies dans les paragraphes qui suivent.
13.1 Conformité statique
La réalisation sera conforme aux prescriptions de la présente Recommandation | Norme internationale dans le rôle de
gestionnaire, dans le rôle d'agent ou dans les deux. Une demande de conformité de l'un de ces rôles au moins sera faite
dans le Tableau B.1.
2 Rec. UIT-T X.738 (1993)/Amd.1 (1996 F)

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
En cas de demande de conformité du rôle de gestionnaire, la réalisation prendra en compte au moins une opération de
gestion, notification ou action des objets gérés spécifiés dans la présente Recommandation | Norme internationale. Les
prescriptions de conformité du rôle de gestionnaire pour ces opérations, notifications et action de gestion sont énoncées
dans le Tableau B.3 et d'autres tableaux mentionnés dans l'Annexe B.
En cas de demande de conformité du rôle d'agent, la réalisation prendra en compte une ou plusieurs instances de classes
d'objets gérés identifiées dans le Tableau B.4 et d'autres tableaux mentionnés dans l'Annexe B.
La réalisation prendra en compte la syntaxe de transfert obtenue à partir des règles de codage spécifiées dans la
Rec. X.209 du CCITT | ISO/CEI 8825, appelées {joint-iso-ccitt asn1(1) basicEncoding(1)}, pour les types de données
abstraites auxquels se rapportent les définitions pour lesquelles la conformité est demandée.
13.2 Conformité dynamique
Les réalisations réputées conformes à la présente Recommandation | Norme internationale prendront en compte les
éléments de procédure et les définitions de sémantique correspondant aux définitions pour lesquelles cette conformité est
demandée.
13.3 Prescriptions de la déclaration de conformité de l'instance de gestion
Tout formulaire MCS, MICS, MOCS et MRCS qui est conforme à la présente Recommandation | Norme internationale
doit être techniquement identique aux formulaires spécifiés dans les Annexes B à O, en respectant le numérotage des
tableaux et les numéros d'ordre de la colonne «Index», et ne s'en écartant que par la pagination et les en-têtes de page.
Le fournisseur d'une réalisation qui est réputée conforme à la présente Recommandation | Norme internationale remplira
un exemplaire du récapitulatif de conformité de gestion (MCS) reproduit dans l'Annexe B dans le cadre des prescriptions
de conformité avec tout autre formulaire ICS qualifié d'applicable par cette déclaration MCS. Un formulaire ICS
conforme à la présente Recommandation | Norme internationale:
– décrit une réalisation qui est conforme à la présente Recommandation | Norme internationale;
– a été rempli conformément aux instructions données à cet effet dans la Rec. UIT-T X.724 |
ISO/CEI 10165-6;
– contient les informations nécessaires pour identifier de manière univoque tant le fournisseur que la
réalisation.
Les revendications de conformité à l'information de gestion définie dans la présente Recommandation | Norme
internationale dans les classes d'objet géré définies dans d'autres documents doivent inclure les prescriptions du
formulaire MIDS dans le formulaire MOCS pour la classe d'objet géré.»
8) Nouvelles annexes
Ajouter les annexes suivantes à la suite de l'Annexe A:
Rec. UIT-T X.738 (1993)/Amd.1 (1996 F) 3

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
Annexe B
1)
Formulaire MCS
(Cette annexe fait partie intégrante de la présente Recommandation | Norme Internationale)
B.1 Introduction
B.1.1 Purpose and structure
The Management Conformance Summary (MCS) is a statement by a supplier that identifies an implementation and
provides information on whether the implementation claims conformance to any of the listed set of documents that
specify conformance requirements to OSI management.
The MCS proforma is a document, in the form of a questionnaire that when completed by the supplier of an
implementation becomes the MCS.
2)
B.1.2 Instructions for completing the MCS proforma to produce an MCS
The supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction is
provided in the text which precedes each table.
B.1.3 Symbols, abbreviations and terms
For all annexes of this Recommendation | International Standard, the following common notations, defined in CCITT
Rec. X.291 and ISO/IEC 9646-2 and ITU-T Rec. X.296 | ISO/IEC 9646-7 are used for the Status column:
m Mandatory;
o Optional;
c Conditional;
x Prohibited;
– Not applicable or out of scope.
NOTES
1 ‘c’, ‘m’, and ‘o’ are prefixed by a ‘c:’ when nested under a conditional or optional item of the same table.
2 ‘o’ may be suffixed by ‘.N’ (where N is a unique number) for mutually exclusive or selectable options among a set of
status values. Support of at least one of the choices (from the items with the same values of N) is required.
For all annexes of this Recommendation | International Standard, the following common notations, defined in CCITT
Rec. X.291 and ISO/IEC 9646-2 and ITU-T Rec. X.296 | ISO/IEC 9646-7 are used for the Support column:
Y Implemented;
N Not implemented;
– No answer required;
Ig The item is ignored (i.e. processed syntactically but not semantically).
B.1.4 Table format
Some of the tables in this Recommendation | International Standard have been split because the information is too wide
to fit on the page. Where this occurs, the index number of the first block of columns are the index numbers of the
corresponding rows of the remaining blocks of columns. A complete table reconstructed from the constituent parts
should have the following layout:
Index First block of columns Second block of columns Etc.
In this Recommendation | International Standard the constituent parts of the table appear consecutively, starting with the
first block of columns.
_______________
1)
Droits de reproduction du formulaire MCS
Les utilisateurs de la présente Recommandation | Norme internationale sont autorisés à reproduire le formulaire MCS de la
présente annexe pour utiliser celui-ci conformément à son objet. Ils sont également autorisés à publier le formulaire une fois
celui-ci complété.
2)
Les instructions pour compléter le formulaire MCS sont spécifiées dans la Rec. UIT-T X.724 | ISO/CEI 10165-6.
4 Rec. UIT-T X.738 (1993)/Amd.1 (1996 F)

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
When a table with sub-rows is too wide to fit on a page, the continuation tables(s) have been constructed with index
numbers identical to the index numbers in the corresponding rows of the first table, and with sub-index numbers
corresponding to the sub-rows within each indexed row. For example, if Table X.1 has 2 rows and the continuation of
Table X.1 has 2 sub-rows for each row, the tables are presented as follows.
Table X.1 – Title
Support
Index A B C D E F G
1a b –
2a b –
Table X.1 (continued) – Title
Index Subindex H I J K L
1 1.1 h i j
1.2 h i j
2 2.1 h i j
2.2 h i j
A complete table reconstructed from the constituent parts should have the following layout:
Support
Index A B C D E F G Subindex H I J K L
1 a b – 1.1 h i j
1.2 h i j
2 a b – 2.1 h i j
2.2 h i j
References made to cells within tables shall be interpreted as references within reconstructed tabled. In the example,
above, the reference X.1/1d corresponds to the blank cell in the column G for row with Index 1, and X.1/1.2b
corresponds to the blank cell in column L for row with Sub-index 1.2.
B.2 Identification of the implementation
B.2.1 Date of statement
The supplier of the implementation shall enter the date of this statement in the box below. Use the format
DD-MM-YYYY.
Date of statement
Rec. UIT-T X.738 (1993)/Amd.1 (1996 F) 5

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
B.2.2 Identification of the implementation
The supplier of the implementation shall enter information necessary to uniquely identify the implementation and the
system(s) in which it may reside, in the box below.
B.2.3 Contact
The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the
content of the MCS, in the box below.
B.3 Identification of the Recommendation | International Standard in which the management
information is defined
The supplier of the implementation shall enter the title, reference number and date of the publication of the
Recommendation | International Standard which specifies the management information to which conformance is
claimed, in the box below.
Recommendation | International Standard to which conformance is claimed
B.3.1 Technical corrigenda implemented
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified Recommendation | International Standard, in the box below.
B.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the
identified Recommendation | International Standard, in the box below.
B.4 Management conformance summary
The supplier of implementation shall state the capabilities and features supported and provide summary of conformance
claims to Recommendations | International Standards using the tables in this annex.
The supplier of the implementation shall specify the roles that are supported, in Table B.1.
6 Rec. UIT-T X.738 (1993)/Amd.1 (1996 F)

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
Table B.1 – Roles
Index Roles supported Status Support Additional information
1 Manager role support o.1
2 Agent role support o.1
The supplier of the implementation shall specify support for the systems management functional units in Table B.2.
Table B.2 – Systems management functional units
Manager Agent
Index Capability Status Support Status Support Additional information
1 Scan stimulation functional unit c1 c2
2 Summarization event reporting functional c1 c2
unit
c1: if B.1/1a then o else –
c2: if B.1/2a then o else –
The supplier of the implementation shall specify support for management information in the manager role, in Table B.3.
Table B.3 – Manager role minimum conformance requirement
Index Item Status Support Additional information
1 Operations on managed objects c3
2 Buffered scan report notification c4
3 Scan report notification c4
4 Statistical report notification c4
5 Activate dynamic simple scan report action c5
6 Activate scan report action c5
7 Activate statistical report action c5
8 Report buffer action c5
9 Object creation notification from at least one c3
summarization managed objects
10 Object deletion notification from at least one c3
summarization managed objects
11 Attribute value change notification from at c3
least summarization managed objects
12 State change notification from at least one c3
summarization managed objects
c3: if B.1/1a then o.2 else –
c4: if B.2/2a then o.3 else (if B.1/1a then o.2 else –)
c5: if B.2/1a then o.4 else (if B.1/1a then o.2 else –)
The supplier of the implementation shall specify support for management information in the agent role, in Table B.4.
Rec. UIT-T X.738 (1993)/Amd.1 (1996 F) 7

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
Table B.4 – Agent role minimum conformance requirement
Index Item Status Support Additional information
1 Heterogeneous scanner managed object c6
2 Buffered scanner managed object c6
3 Simple scanner managed object c6
4 Mean scanner managed object c6
5 Mean variance scanner managed object c6
6 Min max scanner managed object c6
7 Percentile scanner managed object c6
8 Dynamic simple scanner managed object c6
c6: if B.1/2a then o.5 else –
Table B.5 – Logging of event records
Index Status Support Additional information
1 Does the implementation support logging of c7
event records in agent role?
c7: if B.1/2a then o else –
NOTE 1 – Conformance to this Recommendation | International Standard does not require conformance to CCITT
Rec. X.735 | ISO/IEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the Recommendation |
International Standards summarized in Tables B.6 to B.9. For each Recommendation | International Standard that the
supplier of the implementation claims conformance to, the corresponding conformance statement(s) shall be completed,
or referenced by, the MCS. The supplier of the implementation shall complete the Support, Table numbers and
Additional information columns.
In Tables B.6 to B.9, the Status column is used to indicate whether the supplier of the implementation is required to
complete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tables
or referenced items and are not changed by the value of the MCS Status column. Similarly, the Support column is used
by the supplier of the implementation to indicate completion of the referenced tables or referenced items.
NOTE 2 – Conformance to the MAPDUs defined in this Recommendation | International Standard can be claimed by
completing the corresponding tables in the MICS and MOCS annexes of the referenced Recommendation | International Standard.
Table B.6 – PICS support summary
Identification of the Table
Table
document that numbers Constraints Additional
Index Description Status Support numbers
includes the PICS of PICS and values information
of PICS
proforma proforma
a)
1 CCITT Rec. X.730 | Annex E Systems –o
ISO/IEC 10164-1 all tables management
application
context
a)
The supplier of implementation shall indicate the application contexts supported.
8 Rec. UIT-T X.738 (1993)/Amd.1 (1996 F)

ISO/CEI 10164-13 : 1995/Amd.1 : 1997 (F)
Table B.7 – MOCS support summary
Identification of the Table
Table
document that numbers Constraints Additional
number
Index Description Status Support
includes the MOCS of MOCS and values information
of MOCS
proforma proforma
1 CCITT Rec. X.730 | Annex C objectCreation –c8
ISO/IEC 10164-1 all tables objectDeletion
attributeValue
Change records
2 CCITT Rec. X.731 | Annex C stateChange –c8
ISO/IEC 10164-2 all tables Record
3 ITU-T Rec. X.738 | Annex D heterogeneous –c9
ISO/IEC 10164-13 all tables Scanner
4 ITU-T Rec. X.738 | Annex E bufferedScanner – c10
ISO/IEC 10164-13 all tables
5 ITU-T Rec. X.738 | Annex F simpleScanner – c11
ISO/IEC 10164-13 all tables
6 ITU-T Rec. X.738 | Annex G meanScanner – c12
ISO/IEC 10164-13 all tables
7 ITU-T Rec. X.738 | Annex H meanVariance – c13
ISO/IEC 10164-13 all tables Scanner
8 ITU-T Rec. X.738 | Annex I minMaxScanner – c14
ISO/IEC 10164-13 all tables
9 ITU-T Rec. X.738 | Annex J percentileScanner – c15
ISO/IEC 10164-13 all tables
10 ITU-T Rec. X.738 | Annex K dynamicSimple – c16
ISO/IEC 10164-13 all tables Scanner
11 ITU-T Rec. X.738 | Annex L bufferedScan – c17
ISO/IEC 10164-13 all tables ReportRecord
12 ITU-T Rec. X.738 | Annex M scanReportRecord – c18
ISO/IEC 10164-13 all tables
13 ITU-T Rec. X.738 | Annex N statisticalReport – c19
ISO/IEC 10164-13 all tables Record
c8: if (B.4/1a or B.4/2a or B.4/3a or B.4/4a or B.4/5a or B.4/6a or B.4/7a) and B.5/1a then m else –
c9: if B.4/1a then m else –
c10: if B.4/2a then m else –
c11: if B.4/3a then m else –
c12: if B.4/4a then m else –
c13: if B.4/5a then m else –
c14: if B.4/6a then m else –
c15: if B.4/7a then m else –
c16: if B.4/8a then m else –
c17: if B.1/2a and B.4/2a and B.5/1a the
...