ISO/IEC 10164-7:1992/Amd 1:1995
(Amendment)Information technology — Open Systems Interconnection — Systems Management: Security alarm reporting function — Amendment 1: Implementation conformance statement proformas
Information technology — Open Systems Interconnection — Systems Management: Security alarm reporting function — Amendment 1: Implementation conformance statement proformas
Contains tables, which document the mandatory and optional management information specific to the Security Alarm Reporting Function. This amendment will be used by Profile specifiers, for example, those developing International Standardized Profiles (ISPs), to specify an explicit subset of capability, which will afford interoperability between implementations.
Technologies de l'information — Interconnexion de systèmes ouverts — Gestion-système: Fonction de compte rendu d'alarme de sécurité — Amendement 1: Formulaires de déclaration de conformité d'instance
General Information
Relations
Buy Standard
Standards Content (Sample)
ISO/IEC
INTERNATIONAL
10164-7
STANDARD
First edition
1992-05-I 5
AMENDMENT 1
1995-l 2-l 5
Information technology - Open Systems
Interconnection - Systems Management:
Security alarm reporting function
AMENDMENT 1: Implementation
conformance statement proformas
In terconnexion de sys t&mes ouverts
Technologies de /‘information -
(OS/) - Gestion-systemes: Fonction de rapport d’alarme de s&wit6
AMENDEMENT I: Proformes de dklaration de conformit de mise
en cwvre
Reference number
ISO/IEC 10164-7:1992/Amd.l:1995(E)
---------------------- Page: 1 ----------------------
ISWIEC 101647: 1992/Amd.l: 1995(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-7: 1992 was prepared by Joint Technical Committee
ISO/IEC 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.736/Amd. 1.
0 ISO/IEC 1995
All rights reserved. Unless otherwise specified, no part of this publication may be repro-
duced or utilized in any form or by any means, electronic or mechanical, including photo-
copying 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
---------------------- Page: 2 ----------------------
0 ISO/IEC ISO/IEC 10164-7:1992/Amd.l: 1995(E)
Introduction
This amendment includes tables, which document the mandatory and optional management information specific to the
Security Alarm Reporting Function. This amendment will be used by Profile specifiers, for example, those developing
International Standardized Profiles (ISPs), to specify an explicit subset of capability, which will afford interoperability
between implementations. The tables also include a column for equipment vendors to state the capability of their
products in terms of the Profiles or base specification. The table structures comply with the Guidelines for
Implementation Conformance Statement Proformas specified in ITU-T Recommendation X.724 I ISO/IEC 101656.
. . .
111
---------------------- Page: 3 ----------------------
This page intentionally left blank
---------------------- Page: 4 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION -
SYSTEMS MANAGEMENT: SECURITY ALARM REPORTING FUNCTION
AMENDMENT 1
(to Rec. X.736 I ISO/IEC 10164-7)
IMPLEMENTATION CONFORMANCE STATEMENT PROFORMAS
Add the following footnote to the first list item in 2. I:
1)
“I) as amended by ITU-T Rec. X.70Kor.2 I ISO/IEC 10040Kor.2”
Add the following reference to 2. I:
2)
66
- ITU-T Recommendation X.724 (1993) I ISO/IEC 101656:1994, Information technology - Open Systems
Interconnection - Structure of management information: Requirements and guidelines for implementation
conformance statement proformas associated with OSI management.”
Add the following references to 2.2:
3)
- CCITT Recommendation X.291 (1992), OSI conformance testing methodology and framework for
protocol Recommendations for CCITT applications -Abstract test suite specification.
Open Systems Interconnection - Conformance testing
ISO/IEC 9646-2: 199 1, Information technology -
methodology and framework - Part 2: Abstract test suite specification.
-
ITU-T Recommendation X.2963), OH conformance testing methodology and framework for protocol
Recommendations for ITU-T applications - Implementation conformance statements.
- Open Systems Interconnection - Conformance testing
ISO/IEC 9646-7.3), Information technology
methodology and framework - Part 7: Implementation conformance statements.”
And then add the following footnote:
3, Presently at the stage of draft.
Apply the following changes to 3.4:
4)
Replace “dependent conformance” with “managed object conformance statement (MOCS)“.
Replace “general conformance” with “management information conformance statement (MICS)“.
Relabel items e) and f) as g) and h) and insert the following new items:
“e) MICS proforma;
f) MOCS proforma;”
Apply the following change to 3.7:
Replace “system conformance statement” with the following:
“a) PICS proforma;
b) protocol implementation conformance statement;
c) system conformance statement.”
Renumber 3.8 as 3.9 and insert the following new subclause:
ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 5 ----------------------
ISO./IEC 10164-7 : 1992/Amd.l : 1995 (E)
66’
38 a Implementation conformance statement proforma definitions
This Recommendation I International Standard makes use of the following terms defined in ITU-T Rec. X.724 I
ISOLIEC 10165-6:
a) Managed Relationship Conformance Statement (MRCS);
b) Management Conformance Summary (MCS);
c) Management Information Definition Statement (MIDS) proforma;
d) MCS proforma;
e) MRCS proforma.”
Add the following abbreviations to clause 4:
“ICS Implementation Conformance Statement
MCS Management Conformance Summary
MICS Management Information Conformance Statement
MIDS Management Information Definition Statement
MOCS Managed Object Conformance Statement
MRCS Managed Relationship Conformance Statement
PICS Protocol Implementation Conformance Statement”
Replace clause 13 with the following:
66
13 Conformance
.ons claiming to conform to this Recommendatio n I International Sta ndard shall comply with the
Implementati
conformance requirements as d .efined in the following subclauses.
13.1 Static conformance
The implementation shall conform to the requirements of this Recommendation I 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 A. 1.
If a claim of conformance is made for support in the manager role, the implementation shall support at least one of the
notifications or at least one of the management operations specified in this Recommendation I International Standard.
The conformance requirements in the manager role for those management operations and notifications are identified in
Table A.3 and further tables referenced by Annex A.
If a claim of conformance is made for support in the agent role, the implementation shall support at least one of the
notifications specified in this Recommendation I International Standard. The conformance requirements in the agent role
are identified in Table A.4 and further tables referenced by Annex A.
The implementation shall support the transfer syntax derived from the encoding rules specified in CCITT Rec. X.209 1
ISO/IEC 8825 named (joint-iso-ccitt asnl(1) basicEncoding( 1)) for the abstract data types referenced by the definitions
for which support is claimed.
NOTE - Prior to the publication of this amendment, this Recommendation I International Standard identified general and dependent
conformance classes. A claim of conformance similar to general conformance class can be made by stating support in the manager role, the agent role,
or both roles, for the security alarm reporting functional unit in Table A.2. A claim of conformance similar to dependent conformance class can be
made by stating support for at least one of the items in Tables A.3 or A.4.
13.2 Dynamic conformance
Implementations claiming to conform to this Recommendation I International Standard shall support the elements of
procedure and definitions of semantics corresponding to the definitions for which support is claimed.
13.3 Management implementation conformance statement requirements
Any MCS proforma, MICS proforma, and MOCS proforma which conforms to this Recommendation I International
Standard shall be technically identical to the proformas specified in Annexes A, B and C preserving table numbering and
the index numbers of items, and differing only in pagination and page headers.
2 ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 6 ----------------------
ISO/IEC 10164-7 : 199WAmd.l : 1995 (E)
The supplier of an implementation which is claimed to conform to this Recommendation I International Standard shall
complete a copy of the Management Conformance Summary (MCS) provided in Annex A as part of the conformance
requirements together with any other ICS proformas referenced as applicable from that MCS. An ICS which conforms to
this Recommendation I 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 10165-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 for the
managed object class.”
Add the following annexes:
9
ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 7 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
Annex A
MCS proforma5)
(This annex forms an integral part of this Recommendation I International Standard)
A.1 Introduction
A.l.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 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.
A.1.2 Instructions for completing the MCS proforma to produce a 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.
A.l.3 Symbols, abbreviations and terms
For all annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISO/IEC 9646-2 and ITU-T Rec. X.296 I ISO/IEC 9646-7, are used for the Status column:
m Mandatory;
0 Optional;
C Conditional;
Prohibited;
X
-
Not applicable or out of scope.
NOTES
1 ‘C’, ‘m’, and ‘0’ are prefixed by “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 selectable options among a set of status values.
Support of at least one of the choices (from the items with the same value of N) is required.
For all annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISO/IEC 9646-2 and ITU-T Rec. X.296 I 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).
Ig
A.l.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.
5, Users of this Recommendation I 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. Instructions for the MCS proforma are specified in
ITU-T Rec. X.724 I ISO/IEC 101656.
4 ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 8 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
When a table with sub-rows is too wide to fit on a page, the continuation table(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
1 a b -
2 a b -
Table X.1 (concluded) - Title
J K L
Index Sub-index H I
1 1.1 h i
j
1.2 h i
j
2 2.1 h i
j
h i
2.2
j
A complete table reconstructed from the constituent parts should have the following layout:
Index A B C D E F G Sub-index H I J K L
a 1.1 h i
1 b -
j
h i
1.2
j
i
2 a b - 2.1 h
j
2.2 h i
j
References made to cells within tables shall be interpreted as references within reconstructed tables. In the example,
above, the reference X. l/id corresponds with the blank cell in column G for row with Index 1, and X. l/l .2b corresponds
with the blank cell in column L for row with Sub-index 1.2.
A.2 Identification of the implementation
A.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
I
I
ITU-T Rec. X.736 (1992)/Amd.l(1995 E) 5
---------------------- Page: 9 ----------------------
ISOLEC 10164-a : 1992/Amd.l : 1995 (E)
A.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.
A.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 or any referenced conformance statement, in the box below.
A3 . Identification of the Recommendations I International Standards 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
Recommendations I International Standards which specify the management information to which conformance is
claimed, in the box below.
Recommendations I International Standards to which conformance is claimed
I I
A.3.1 Technical corrigenda implemented
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified Recommendations I International Standards, in the box below.
A.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the
identified Recommendations I International Standards, in the box below.
6 ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 10 ----------------------
ISOAEC 10164-7 : 1992/Amd.l : 1995 (E)
A.4 Management conformance summary
The supplier of the implementation shall state the capabilities and features supported and provide a 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 A. 1.
Table A.1 - Roles
Index Roles supported Status Support Additional information
1 Manager role support 0.1
2 Agent role support 0.1
The supplier of the implementation shall specify support for the systems management functional unit, in Table A.2.
Table A.2 - Systems management functional unit
Manager Agent
Index Systems management functional unit name Status Support Status Support Additional information
cl c2
1 security alarm reporting functional unit
cl: if A. l/la then o else -.
c2: if A. 1/2a then o else -.
The supplier of the implementation shall specify support for management information in the manager role, in Table A.3.
Table A.3 - Manager role minimum conformance requirement
Index Item Status support Additional information
c3
1 Integrity violation notification
c3
2 Operational violation notification
c3
3 Physical violation notification
c3
4 Security service or mechanism violation notification
c3
5 Time domain violation notification
c4
6 Operations on managed objects
c3: if A.2/la then m else (if A.l/la then 0.2 else -).
c4: if A.2/la then m else (if A.l/la then 0.2 else -).
NOTE - Manager role minimum conformance requires support for at least one of the items identified in this table. Support for the
functional unit identified in Table A.2 mandates support for some of those items. Conditions c3 and c4 express both of these
requirements.
The supplier of the implementation shall specify support for management information in the agent role, in Table A.4.
ITU-T Rec. X.736 (1992)/Amd.l(1995 E) 7
---------------------- Page: 11 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
Table A.4 - Agent role minimum conformance requirement
Index Item Status support Table reference Additional information
c5
1 Integrity violation notification
C5
2 Operational violation notification
3 Physical violation notification c5
4 c5
Security service or mechanism violation
notification
c5
5 Time domain violation notification
-
6 Security alarm record managed object class c6
if A.20 b then m else (if A. 1/2a then 0.3 else -).
c5:
c6: if A.l/2a and A.5/la then m else -.
NOTES
1 Condition c6 makes it mandatory, if logging is supported, to support the event log records associated with the notifications
supported.
2 The Table reference column in this table is the notification reference of the MOCS supplied by the supplier of the managed
object which claims to import the notification from this Recommendation I International Standard.
Table A.5 - Logging of event records
c7: if A.l/2a then o else -.
I
I
NOTE 1 - Conformance to this Recommendation I International Standard does not require conformance to CCITI’
Rec. X.735 I ISO/IEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the Recommendations
I International Standards summarized in the Tables A.6 to A.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 A.6 to A.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.
Table A.6 - PICS support summary
Table
Table
Identification of the
numbers Constraints Additional
Index document that includes of pIcs Description Status Support numbers
information
and values
of PIGS
the PICS proforma
proforma
1 OBJECT
CCITI’ Rec. X.730 I Annex E SM application context
ISO/IEC 10164-l 1 all tables 1 IDENTIFIER
I I Iml I I I
NOTE 2 - Conformance to the MAPDUs defined in this Recommendation I International Standard can be claimed by
completing the corresponding tables in the MICS and MOCS annexes of the referenced Recommendations I International Standards.
8 ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 12 ----------------------
ISO/IEC 10164-7 : 1992lAmd.l : 1995 (E)
Table A.7 - MOCS support summary
Table
Table
Identification of the
Constraints
numbers
Status Support numbers of Additiona1
Description
Index document that includes
information
and values
of MOCS
MOCS
the MOCS proforma
proforma
- C8
1 CCITT Rec. X.736 I Annex C securityAlarmRecord
all tables
ISO/IEC 10 164-7
I I
c8: if A.4/6a then m else -.
Table A.8 - MRCS support summary
Table
Table
Identification of the
Additional
Constraints
numbers
Status Support numbers
Description
Index document that includes of MRCS
information
and values
of MRCS
the MRCS proforma
proforma
Item logRecord-log name - c9
1 CCITI Rec. X.735 I
binding
ISO/IEC 10164-6 D. l/l
c9: if A.5/la then o else -.
Table A.9 - MICS support summary
Table
Table
Identification of the
Additional
Constraints
numbers
Description Status Support numbers
Index document that includes of MICS
information
and values
of MICS
the MICS proforma
proforma
-
cl0
Table B. 1 notifications
1 CCITI Rec. X.736 I
ISO/IEC 10164-7
-
cl1
2 CCITI’ Rec. X.736 I Tables B.2 management
and B.3 operations
ISO/IEC 10164-7
~10: if A.3lla or A.3/2a or A.3/3a or A.3/4a or A.3/5a then m else -.
cll: if A.3/6a then m else -.
9
ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 13 ----------------------
ISW’IEC 10164-7 : 1992/Amd.l : 1995 (E)
Annex B
MICS proforma@
(This annex forms an integral part of this Recommendation I International Standard)
Bl . Introduction
The purpose of this MICS proforma is to provide a mechanism for a supplier of an implementation which claims
conformance, in the manager role, to management information specified in this Recommendation 1 International
Standard, to provide conformance information in a standard form.
B2 . Instructions for completing the MICS proformma to produce a MICS
The MICS proforma contained in this annex is comprised of information in tabular form, in accordance with ITU-T
Rec. X.724 I ISO/‘IEc 101656. In addition to the general guidance given in ITU-T Rec. X.724 1 ISW’IEC lO16.56:, the
Additional information column shall be used to identify the object classes for which the management operations arz
supported. The supplier of the implementation shall state which items are supported in the tables below and if necessary,
provide additional information.
B3 0 terms
The following abbreviations are used throughout the MICS proforma:
dmi-att joint-iso-ccitt ms(9) smi(3) part2f2) attribute(7)
dmi-not joint-iso-ccitt ms(9) smi(3) parQ(2) notification( 10)
The notations used for the Status and Support columns are specified in A. 1.3.
B4 . Statement of conformance to the
B.4.1 Notifications
The specifier of a manager role implementation that claims to support the notifications specified in this Recommendation
1 International Standard shall import a copy of Table B. 1 and complete it,
cl: if A.3/la then m else -.
c2: if A.3/2a then m else -.
c3: if A.3/3a then m else -.
c4: if A.3/4a then m else -.
c5: if A.3/5a then m else -.
(continued)
@ Users of this Recommendation I International Standard may freely reproduce the MICS proforma in this annex so that it can be
used for its intended purpose, and may further publish the completed MICS.
10 ITU-T Rec. X.736 (1992)/Amd.l (1995 E)
---------------------- Page: 14 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
Table B.l (continued) - Notification support
Value of object
identifier for the
Additional
Index Sub-index Notification field name label Constraints and values
attribute type
Status “PPO’ information
associated with
the field
1.1 securityAlarmCause (dmi-att 2 1) OBJECT IDENTIFIER m
m
1.2 SecurityAlarmSeverity (dmi-att 23) ENUMERATED 0 to 4
-
1.3 securityAlarmDetector (dmi-att 22) m
-
1.3.1 mechanism OBJECT IDENTIFIER m
- -
1.3.2 object m
- -
1.3.2.1 distinguishedName m
- -
nonSpecificForm m
1.3.2.2
- -
m
1.3.2.3 1ocalDistinguishedName
-
1.3.3 application OBJECT IDENTIFIER m
-
1.4 serviceuser ( dmi-att 25 } m
-
1.4.1 identifier OBJECT IDENTIFIER m
- -
1.4.2 details m
-
m
1.5 serviceprovider (dmi-att 24)
-
1.51 identifier OBJECT IDENTIFIER m
- -
1.5.2 details m
m
1.6 notificationIdentifier (dmi-att 16) INTEGER
-
1.7 correlatedNotifications (dmi-att 12) m
- -
1.7.1 correlatedNotifications m
- -
1.7.2 m
sourceObjectInst
- -
m
1.7.2.1 distinguishedName
- -
1.7.2.2 nonSpecificForm m
-
-
m
1.7.2.3 1ocalDistinguishedName
-
1.8 additionalText (dmi-att 7) m
1.9 addi tionalInformation (dmi-att 6) required for some objects m
2.1 securityAlarmCause (dmi-att 2 1) OBJECT IDENTIFIER m
2.2 ENUMERATED 0 to 4 m
SecurityAlarmSeverity (dmi-att 23)
-
2.3 securityAlarmDetector (dmi-att 22) m
-
2.3.1 mechanism OBJECT IDENTIFIER m
- -
2.3.2 object m
- -
m
2.3.2.1 distinguishedName
- -
2.3.2.2 nonSpecificForm m
(continued)
ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
11
---------------------- Page: 15 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
Table B.l (continued) - Notification support
Value of object
identifier for the
Additional
Index Sub-index Notification field name label attribute type Constraints and values
Status SuPPort information
associated with
the field
- -
2 2.3.2.3 1ocalDistinguishedName m
I I I
I
-
2.3.3 application 1 OBJECTIDENTIFIER 1 m
I I
2.4 serviceuser {dmi-att 25) 1 - m
I
I I I
-
m
2.4.1 identifier I OBJECT IDENTIFIER /
I
I
2.4.2 details m
I I
I
-
2.5 serviceprovider (dmi-att 24) m
I
I I I
-
m
2.5.1 1 identifier I OBJECTIDENTIFIER I
I
2.5.2 details m
I
I I
2.6 notificationIdentifier (dmi-att 16) / INTEGER m
I I I
I
-
2.7 correlatedNotifications (dmi-att 12) / m
I
I I I
2.7.1 correlatedNotifications m
I I
I
m
2.7.2 sourceObjectInst
I I
I
2.7.2.1 distinguishedName m
I I I
m
I I
2.7.2.3 1ocalDistinguishedName
I
2.8 additionalText
I
2.9 additionalInformation
I
securityAlarmCause
I
securityAlarmSeverity
3.2
I
securityAlarmDetector
I
mechanism
I
object
3.3.2
I
3.3.2.1 distinguishedName
I
3.3.2.2 nonSpecificForm
I
3.3.2.3 1ocalDistinguishedName
I
application
I
serviceuser
I
identifier
I
(continued)
---------------------- Page: 16 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
_ Table B.l (continued) - Notification support
Value of object
identifier for the
Additional
Index Sub-index Notification field name label attribute type Constraints and values
Status “PPort information
associated with
the field
.
I
4
3
3.9 additionallnformation (dmi-att 6) required for some objects
m
4
(continued)
ITU-T Rec. X.736 (1992)fAm
---------------------- Page: 17 ----------------------
ISOAEC 10164-7 : 1992/Amd.l : 1995 (E)
Table B.1 (concluded) - Notification support
Value of object
identifier for the
Additional
Index Sub-index Notification field name label attribute type Constraints and values
Status SuPPort information
associated with
the field
-
4.8 additionalText (dmi-att 7) m
addi tionalInformation { dmi-att 6) required for some objects m
4.9
OBJECT IDENTIFIER m
5.1 securityAlarmCause (dmi-att 2 1)
5.2 securityAlarmSeverity ( dmi-att 23 } ENUMERATED 0 to 4 m
-
5.3 securityAlarmDetector (dmi-att 22) m
-
mechanism OBJECT IDENTIFIER m
5.3.1
- -
m
5.3.2 object
- -
5.3.2.1 distinguishedName m
- -
5.3.2.2 nonSpecificForm m
- -
5.3.2.3 1ocalDistinguishedName m
-
OBJECT IDENTIFIER
5.3.3 application m
-
5.4 serviceuser ( dmi-att 25 } m
-
5.4.1 identifier OBJECT IDENTIFIER m
- -
5.4.2 details m
-
5.5 serviceprovider (dmi-att 24) m
-
5.5.1 identifier OBJECT IDENTIFIER m
-
-
5.5.2 details m
5.6 notificationIdentifier (dmi-att 16)
INTEGER m
-
5.7 correlatedNotifications (dmi-att 12) m
- -
5.7.1 correlatedNotifications m
-
-
5.7.2 sourceObjectInst m
-
-
5.7.2.1 distinguishedName
m
- -
5.7.2.2 nonSpecificForm m
- -
5.7.2.3 1ocalDistinguishedName m
-
5.8 additionalText (dmi-att 7)
m
additionalInformation
5.9 (dmi-att 6) required for some objects m
14 ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 18 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
B.4.2 Attributes
The specifier of a manager role implementation that claims to support management operations on the attributes specified
in this Recommendation I International Standard shall import a copy of Table B.2 and complete it.
Table B.2 - Attribute support
Attribute template label identifier for the Constraints and values
15
ITU-T Rec. X.736 (1992)/Amd.l(1995 E)
---------------------- Page: 19 ----------------------
ISO/IEC 10164-7 : 1992/Amd.l : 1995 (E)
Table B.2 (concluded) - Attribute support
Replace 1 Add I Remove 1 Set to default 1
r
Additional information 1
I Index [ Status 1 Support 1 Status 1 Support 1 Status I Support 1 Status 1 Support I
- - - -
L
t
-
-
1
- -
2
I I
I I
I
- - -
-
3
I I I I
- - -
-
I I I
14 I I I I I
-
- -
15 I I I I
I - I I I
- - - -
6
-
- -
7
- -
8
-
- -
19 I - I
I I I
- - -
10
- -
- -
11
- -
-
12
I I I I I
-
I 13 I - I I I I - I I - I
I I
I
- -
14
I - I I I
-
...
NORME
lSO/CEI
10164-7
INTERNATIONALE
Première édition
1992-05-I 5
AMENDEMENT 1
1995-I 2-l 5
Technologies de l’information -
Interconnexion de systèmes ouverts
(OSI) - Gestion-systèmes: Fonction de
signalisation des alarmes de sécurité
AMENDEMENT 1: Formulaires de déclaration
de conformité d’instance
Information technology - Open Sys tems In terconnection - Sys tems
Management: Security alarm reporting function
AMENDMENT 1: Implementation conformance statement proformas
Numéro de référence
ISO/CEI 10164-7:1992/Amd.l:1995(F)
---------------------- Page: 1 ----------------------
ISOKEI 10164-7:1992/Amd.l:1995(F)
Avant-propos
LIS0 (Organisation internationale de normalisation) et la CE1 (Commission
électrotechnique internationale) forment ensemble un système consacré à la
normalisation internationale considérée comme un tout. Les organismes nationaux
membres de I’ISO ou de la CE1 participent au développement de Normes inter-
nationales par l’intermédiaire des comités techniques créés par l’organisation
concernée afin de s’occuper des différents domaines particuliers de l’activité
technique. Les comités techniques de I’ISO et de la CE1 collaborent dans des
domaines d’intérêt commun. D’autres organisations internationales, gouverne-
mentales ou non gouvernementales, en liaison avec I’ISO et la CE1 participent
également aux travaux.
Dans le domaine des technologies de l’information, 1’ISO et la CE1 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
approbation, avant leur acceptation comme Normes internationales. Les Normes
qui requièrent
internationales sont approuvées conformément aux procédures
l’approbation de 75 % au moins des organismes nationaux votants.
L’Amendement 1 à la Norme internationale ISOKEI 10164-7: 1992 a été élaboré par
le comité technique mixte ISOKEI JTC 1, Technologies de Z’information, sous-
comité SC 21, Interconnexion des systèmes ouverts, gestion des données et
traitement distribué ouvert, en collaboration avec I’UIT-T. Le texte identique est
publié en tant que Recommandation UIT-T X736/Amd. 1.
0 ISOKEI 1995
Droits de reproduction r&ervé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.
ISOKEI Copyright Office l Case postale 56 l CH- 1211 Genève 20 l Suisse
Version française tin5e en 1996
Imprimé en Suisse
ii
---------------------- Page: 2 ----------------------
@ ISOKEI ISOKEI 10164-7: 1992/Amd.l: 1995(F)
Introduction
Le présent amendement contient les tableaux qui indiquent les informations de gestion obligatoires et facultatives
propres à la fonction de signalisation des alarmes de sécurité. Il sera utilisé par les spécificateurs de profils, par exemple
ceux qui élaborent des profils normalisés internationaux (ISP) (international standardized profiles), quand ils spécifient
un sous-ensemble explicite de capacités afin d’assurer l’interopérabilité des applications. Les tableaux comportent
aussi une colonne dans laquelle les fournisseurs d’équipements indiqueront les capacités de leurs produits en termes de
profils ou de spécifications de base. La structure des tableaux est conforme aux lignes directrices contenues dans la
Rec. UIT-T X.724 I ISOKEI 10165-6 pour l’établissement des formulaires de d&laration de conformité des instances de
protocole.
---------------------- Page: 3 ----------------------
Page blanche
---------------------- Page: 4 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
NORME INTERNATIONALE
RECOMMANDATION UIT-T
TECHNOLOGIES DE L’INFORMATION - INTERCONNEXION DE SYSTÈMES
OUVERTS (OSI) - GESTION-SYSTÈMES: FONCTION DE SIGNALISATION
DES ALARMES DE SÉCURITÉ .
AMENDEMENT 1
(à la Rec. UIT-T X.736 1 ISOKEI 10164-7)
FORMULAIRES DE DÉCLARATION DE CONFORMITÉ D’INSTANCE
Au paragraphe 2.1, ajouter la note de bas de page suivante au premier élément de la liste:
1)
«l) Tel que modifiée par la Rec. UIT-T X.701Kor.2 I ISOKEI 10040/Cor.2.»
Au paragraphe 2.1, ajouter la référence suivante:
2)
«- Recommandation UIT-T X.724 (1993) I ISOKEI 10165.6:1994, Technologie 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 de protocole associés à la
gestion OSI. »
Au paragraphe 2.2, ajouter les références suivantes:
3)
«- Recommandation X.291 du CCITT (1992), Cadre général et méthodologie des tests de conformité
d’interconnexion des systèmes ouverts pour les Recommandations sur les protocoles pour les applications
de I’UIT-T - Spécifïcation de suites de tests abstraite.
ISOKEI 9646-2: 199 1, 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.2963), Cad re général et méthodologie des tests de conformité OSI pour les
Recommandations sur les protocoles pour les applications de I’UIT-T - Déclarations de conformité
d’instance.
ISOKEI 9646-73), Technologies de 1 ‘information - Interconnexion de systèmes
ouverts - Méthodologie
générale et procédures - Partie 7: Déclarations de conformité des instances. »
Ensuite, ajouter la note de bas de page suivante:
«3) Actuellement à Mat de projet.»
Au paragraphe 3.4, faire les modifications suivantes:
4)
Remplacer «conformité induite» par «déclaration de conformité d’objet géré (MOCS)».
Remplacer «conformite générale» par «déclaration de conformité d’information de gestion @KS)».
Les points e) etf) deviennent les points g) et h). Insérer les nouveaux points suivants:
«e) formulaire MICS;
f) formulaire MOCS;»
Au paragraphe 3.7, faire les modifications suivantes:
5)
Remplacer «déclaration de conformité du syst&me» par:
«a) formulaire PICS;
b) déclaration de conformité d’instance de protocole;
c) déclaration de conformité du système.»
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
1
---------------------- Page: 5 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
Le paragraphe 3.8 devient 3.9. Insérer le nouveau paragraphe suivant:
6)
u3.8 Définition des formulaires de déclaration de conformité d’instance
La présente Recommandation I Norme internationale utilise les termes suivants définis par la Rec. UIT-T X.724 I
ISOKEI 10165-6:
a) déclaration de conformité de relation gérée (MRCS);
b) récapitulatif de conformité de gestion (MCS);
c) formulaire de déclaration de définition d’information de gestion (MIDS);
d) formulaire MCS;
e) formulaire MRCS .»
A l’article 4, ajouter les abréviations suivantes:
7)
«ICS Déclaration de conformité d’instance (implementation confonnance statement)
MCS Récapitulatif de conformité de gestion (management conformance summary)
M.ICS 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)
MOCS Déclaration de conformité d’objet géré (managed abject conformance statement)
MRCS Déclaration de conformité de relation gérée (managed relationship conformance statement)
Déclaration de conformité d’instance de protocole (protocol implementation conformance
PICS
statement)»
Remplacer l’article 13 par ce qui suit:
8)
Conformité
«13
I Norme internationale doivent satisfaire aux
Les instances qui se veulent conformes a la présente Recommandation
prescriptions de conformité définies aux paragraphes suivants.
13.1 Conformité statique
L’instance doit satisfaire aux prescriptions de conformité de la présente Recommandation 1 Norme internationale dans
son rôle de gestionnaire, son rôle d’agent, ou dans les deux rôles. Une déclaration de conformité à l’un des rôles au moins
sera faite au Tableau A. 1.
Si une déclaration de conformité est faite pour la prise en charge du rôle de gestionnaire, l’instance doit prendre
en charge l’une au moins des notifications ou l’une au moins des opérations de gestion spécifiées dans la presente
Recommandation I Norme internationale. Les prescriptions de conformité du rôle de gestionnaire à ces opérations et
notifications de gestion sont identifiés au Tableau A.3 et dans d’autres tableaux référencés dans 1’Annexe A.
Si une déclaration de conformité est faite pour la prise en charge du rôle d’agent, l’instance doit prendre en charge l’une
au moins des notifications spécifiées dans la présente Recommandation I Norme internationale. Les prescriptions de
conformité du rôle d’agent sont identifiés au Tableau A.4 et dans d’autres tableaux référencés dans 1’Annexe A.
L’instance doit prendre en charge la syntaxe de transfert obtenue à partir des règles de codage specifiées dans la
Rec. X.209 du CCITT I ISOKEI 8825 appelée {joint-iso-ccitt asnl( 1) basicEncoding( 1)) pour les types abstraits de
données référencés par les définitions que l’instance veut prendre en charge.
NOTE - Avant publication du présent amendement, la présente Recommandation I Norme internationale identifiait des
classes de conformite générale et induite. Une declaration de conformité semblable à celle de la classe de conformité générale peut
être faite en declarant la prise en charge par le rôle de gestionnaire, le rôle d’agent ou par les deux rôles, de l’unit6 fonctionnelle de
rapport d’alarme de securite du Tableau A.2. Une déclaration de conformité semblable à celle de la classe de conformité induite peut
être faite en declarant la prise en charge de l’un au moins des élements des Tableaux A.3 ou A.4.
2 Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
---------------------- Page: 6 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
13.2 Conformité dynamique
Les instances qui se veulent conformes à la présente Recommandation I Norme internationale doivent prendre en charge
les éléments de procédure et les définitions sémantiques correspondant aux définitions qu’elles veulent prendre en
charge.
13.3 Prescriptions de déclaration de conformité d’information de gestion
Un formulaire MCS, MICS ou MOCS conforme à la présente Recommandation l Norme internationale doit être
identique, dans son texte, aux formulaires correspondants spécifiés dans les Annexes A, B, ou C, doit conserver la
numérotation des tableaux et les numéros d’index des différents éléments et ne peut différer de ces formulaires que par la
pagination et les en-têtes de page.
Le fournisseur d’une instance qui se veut conforme à la présente Recommandation I Norme internationale doit compléter
un formulaire récapitulatif de conformité de gestion (MCS) fourni dans I’Annexe A, ce qui fait partie des prescriptions
de conformité, de même que tout autre formulaire ICS referencé qui est applicable d’après le MCS. Un ICS qui se veut
conforme à la présente Recommandation I Norme internationale:
-
decrit une instance conforme à la présente Recommandation I Norme internationale;
-
est rempli conformément aux instructions données à cet effet dans la Rec. UIT-T X.724 I
ISOKEI 101656;
-
contient les renseignements nécessaires pour identifier sans ambiguïté le fournisseur et l’instance.
Les déclarations de conformité d’information de gestion définies dans la présente Recommandation I Norme
internationale pour des classes d’objets gérés définies par ailleurs comprennent les prescriptions MIDS, tels que les
spécifie le formulaire MOCS pour la classe des objets gérés.»
Ajouter les annexes suivantes:
9
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
3
---------------------- Page: 7 ----------------------
ISOKEI 10164-7 : 199WAmd.l: 1995 (F)
Annexe A
Formulaire MCW
(Cette annexe fait partie intégrante de la présente Recommandation I Norme internationale)
Al l Introduction
A.l.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 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.
A.l.2 Instructions for completing the MCS proforma to produce a 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.
Symbols, abbreviations and terms
A.l.3
For a11 annexes of this Recommendation 1 International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISO/IEC 9646-2 and ITU-T Rec. X.296 I ISO/IEC 9646-7, are used for the Status column:
m Mandatory;
Optional;
0
C Conditional;
X Prohibited;
-
Not applicable or out of scope.
NOTES
1 ‘c’, ‘m’, and ‘0’ are prefixed by “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 selectable options among a set of status values.
Support of at least one of the choices (from the items with the same value of N) is required.
For a11 annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISOAEC 9646-2 and ITU-T Rec. X.296 I ISOAEC 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).
Ig
A.14 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:
.
First block of columns Second block of columns Etc.
Index
In this Recommendation I International Standard the constituent parts of the table appear consecutively, starting with the
first block of columns.
3 Les utilisateurs de la presente Recommandation I Norme internationale sont autorisés a reproduire le formulaire MCS de la
présente annexe pour utiliser celui-ci conformement à son objet. Ils sont également autorises à publier le formulaire une fois
celui-ci complété. Les instructions pour le formulaire MCS sont spécifiées dans la Rec. UIT-T X.724 I ISO/CEI 101656.
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
4
---------------------- Page: 8 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
When a table with sub-rows is too wide to fit on a page, the continuation table(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
1 a b -
2 a b -
Table X.1 (concluded) - Title
Index Sub-index H 1 J K L
1 1.1 h i j
,
1.2 h i j
I 1
2 2.1 h i j
1 2.2
l I
I I h I i I j I
A complete table reconstructed from the constituent parts should have the following layout:
I Support I
,
Index A B C D E F G Sub-index H 1 J K L
1 a b - 1.1
h i j
.
1.2 h i j
r
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 tables. In the example,
above, the reference X. l/ld corresponds with the blank ce11 in column G for row with Index 1, and X. 1/1.2b corresponds
with the blank ce11 in column L for row with Sub-index 1.2.
A2 0 Identification of the implementation
A.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
I
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
5
---------------------- Page: 9 ----------------------
ISOKEI 10164-7 : 199VAmd.l: 1995 (F)
A.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.
Contact
A.2.3
The supplier of the implementation shah provide information on whom to contact if there are any queries conceming the
content of the MCS or any referenced conformance statement, in the box below.
A3 0 Identification of the Recommendations I International Standards 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
Recommendations I International Standards which specify the management information to which conformance is
claimed, in the box below.
Recommendations I International Standards to which conformance is claimed
A.3.1 Technicai corrigenda implemented
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified Recommendations I International Standards, in the box below.
A.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the
identified Recommendations I International Standards, in the box below.
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
6
---------------------- Page: 10 ----------------------
ISO/CEI 10164-7 : 1992/Amd.l: 1995 (F)
Management conformance summary
A.4
The supplier of the implementation shall state the capabilities and features supported and provide a 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 A. 1.
Table A.1 - Roles
Index Roles supported Status Support Additional information
1 Manager role support 0.1
Agent role support 0.1
2
The supplier of the implementation shah specify support for the systems management functional unit, in Table A.2.
Table A.2 - Systems management functionai unit
Manager Agent
I I I
Status Support Additional information
Index Systems management functional unit name Status Support
1 security alarm reporting functional unit cl c2
I I I I I
I I I
cl: if A.l/la then o else -.
c2: if A. 1/2a then o else -.
The supplier of the implementation shall specify support for management information in the manager role, in Table A.3.
Table A.3 - Manager role minimum conformance requirement
Item Status support Additional information
Index
Integrity violation notification c3
1
c3
2 Operational violation notification
c3
3 Physical violation notification
c3
4 Security service or mechanism violation notification
c3
Time domain violation notification
5
c4
6 Operations on managed abjects
c3: if AZla then m else (if A.l/la then 0.2 else -).
c4: if A.Ula then m else (if A.l/la then 0.2 else -).
NOTE - Manager role minimum conformance requires support for at least one of the items identified in this table. Support for the
functional unit identified in Table A.2 mandates support for some of those items. Conditions c3 and c4 express both of these
requirements.
The supplier of the implementation shall specify support for management information in the agent role, in Table A.4.
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
---------------------- Page: 11 ----------------------
ISOKEI 10164-7 : 1992lAmd.l: 1995 (F)
Table A.4 - Agent role minimum conformance requirement
Item
Index Status Table reference Additional information
Support
1 Integrity violation notification CS
2 Operational violation notification C5
3 Physical violation notification C5
Security service or mechanism violation c5
4
notification
5 Time domain violation notification c5
-
c6
6 Security alarm record managed abject class
c5: if A.2/lb then m else (if A.l/2a then 0.3 else -).
c6: if A. 1/2a and A.5/la then m else -.
NOTES
1 Condition c6 makes it mandatory, if logging is supported, to support the event log records associated with the notifications
supported.
2 The Table reference column in this table is the notification reference of the MOCS supplied by the supplier of the managd
abject which claims to import the notification from this Recommendation I International Standard.
Table A.5 - Logging of event records
Addi tional
Index Status Support
information
Does the implementation support logging of event records in agent role? c7
1
\
c7: if A. 1/2a then o else -.
I I
NOTE 1 - Conformance to this Recommendation I International Standard does not require conformance to CCITI’
Rec. X.735 I ISO/IEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the Recommendations
I International Standards summarized in the Tables A.6 to A.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 A.6 to A.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.
Table A.6 - PICS support summary
Table
Identification of the Table
Addi tional
numbers Constraints
of pIcs Description
Index document that includes Status Support numbers
and values information
the PICS proforma of PICS
proforma
r
1 CCITT Rec. X.730 I Annex E SM application context
ISO/IEC 10164-l II=E,1 m 1 1 1 1
a11 tables
I I
NOTE 2 - Conformance to the MAPDUs defined in this Recommendation I International Standard cari be claimed by
completing the corresponding tables in the MICS and MOCS annexes of the referenced Recommendations I International Standards.
8 Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
---------------------- Page: 12 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
Table A.7 - MOCS support summary
Table
Table
Identification of the
numbers Constraints
Status Support numbers of Additiona
Description
Index document that includes of MOCS
information
and values
MOCS
the MOCS proforma
proforma
- C8
CCITT Rec. X.736 I Annex C securityAlarmRecord
1
a11 tables
ISO/IEC 10164-7
c8: if A.4/6a then m else -.
Table A.8 - MRCS support summary
I I
Table
Table
ification of the
Ident
Constraints Additional
numbers
I
Description Status Support numbers
Index document J----- that includes of MRCS
information
and values
of MRCS
the MRCS proforma
proforma
CCITT Rec. X.735 I Item logRecord-log name - c9
D. 111 binding
ISO/IEC 10164-6
c9: if A.5/la then o else -.
I
Table A.9 - MICS support summary
.
Table
Table
Identification of the
Constraints Additional
numbers
Description Status Support numbers
Index document that includes of MICS
and values information
the MICS proforma of MICS
proforma
CCITI’ Rec. X.736 I Table B. 1 notifications cl0
1
ISO/IEC 10164-7
CCITT Rec. X.736 1 Tables B.2 management cl1
ISO/IEC 10164-7 and B.3 operations
l2 I I l I l l I I I
if A.3/la or A.3/2a or A,3/3a or A.3/4a or A.3/5a then m else -.
if A.3/6a then m else -.
Rec. UIT-T X.736 (1992)/Amd.l(1995 F) 9
---------------------- Page: 13 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
Annexe B
Formulaire MICW
(Cette annexe fait partie intégrante de la présente Recommandation I Norme internationale)
Bl . Introduction
The purpose of this MICS proforma is to provide a mechanism for a supplier of an implementation which claims
conformance, in the manager role, to management information specified in this Recommendation I International
Standard, to provide conformance information in a standard form.
Instructions for completing the MICS proforma to produce a MICS
B2 l
The MICS proforma contained in this annex is comprised of information in tabular form, in accordance with ITU-T
Rec. X.724 I ISOBIEC 10165-6. In addition to the general guidance given in ITU-T Rec. X.724 I ISO/IEC 101656, the
Additional information column shah be used to identify the abject classes for which the management operations are
supported. The supplier of the implementation shah state which items are supported in the tables below and if necessary,
provide additional information.
B3 0 Symbols, abbreviations and terms
The following abbreviations are used throughout the MICS proforma:
dmi-att joint-iso-ccitt ms(9) smi(3) part2(2) attribute(7)
dmi-not joint-iso-ccitt ms(9) smi(3) part2(2) notification( 10)
The notations used for the Status and Support columns are specified in A. 1.3.
B4 l Statement of conformance to the management information
B.4.1 Notifications
The specifier of a manager role implementation that claims to support the notifications specified in this Recommendation
I International Standard shall import a copy of Table B. 1 and complete it.
Table B.1 - Notification support
I
I SUPp0I-t
Value of abject
Constraints Non- Addi tional
Index Notification type template label identifier for the S tatus Confirmed
and values confirmed information
notification type
1 integrityviolation (dmi-not 5) cl
2 0perationalViolation (dmi-not 8) c2
(dmi-not 9)
3 physicalViolation c3
I
4 securityServiceOrMechan.ism (dmi-not 13) c4
5 timeDomainViolation (dmi-not 55) c5
1
cl: if A.3/1a then m else -.
c2: if A.3/2a then m else -.
c3: if A.3/3a then m else -.
c4: if A.3/4a then m else -.
c5: if A.3/5a then m else -.
(continued)
@ Les utilisateurs de la presente Recommandation I Norme internationale sont autorises a reproduire le formulaire MICS de la
présente annexe pour utiliser celui-ci conformement à son objet.
10 Rec. UIT-T X.736 (1992)Amd.l(1995 F)
---------------------- Page: 14 ----------------------
ISOKEI 10164-7 : 1992fAmd.l: 1995 (F)
Table B.1 (continued) - Notification support
Value of abject
identifier for the
Index Sub-index Notification field name label attribute type Constraints and values Status Support i~!oditi~~~a
associated with
the field
1 1.1 securityAlarmCause (dmi-att 2 1) OBJECT IDENTIFIER m
1.2 securityAlarmSeverity ( dmi-att 23 ) ENUMERATED 0 to 4 m
securityAlarmDetector { dmi-att 22) m
1.3
1.3.1 mechanism OBJECT IDENTIFIER m
m
1.3.2 abject
m
1.3.2.1 distinguishedName
,
m
nonSpecificForm
1.3.2.2
1
m
1.3.2.3 1ocalDistinguishedName
application OBJECT IDENTIFIER m
1.3.3
( dmi-att 25 ) m
1.4 serviceuser
,
1.4.1 identifier OBJECT IDENTIFIER m
m
1.4.2 details
(dmi-att 24) m
1.5 serviceprovider
1.51 identifier OBJECT IDENTIFIER m
1 s.2 details m
notificationIdentifier (dmi-att 16) m
1.6 INTEGER
(dmi-att 12) m
1.7 correlatedNotifications
m
1.7.1 correlatedNotifications
m
sourceObjectInst
1.7.2
m
1.7.2.1 distinguishedName
m
1.7.2.2 nonSpecificForm
m
1.7.2.3 1ocalDistinguishedName
additionalText (dmi-att 7) m
1.8
1.9 additionalInformation (dmi-att 6) required for some abjects m
( dmi-att 2 1) OBJECT IDENTIFIER m
2 2.1 securityAlarmCause
m
2.2 securityAla.rmSeverity ( dmi-att 23) ENUMERATED 0 to 4
(dmi-att 22)
2.3 securityAlarmDetector m
2.3.1 mechanism OBJECT IDENTIFIER m
m
abject
2.3.2
m
2.3.2.1 distinguishedName
m
2.3.2.2 nonSpecificForm
(continued)
Rec. UIT-T X.736 (1992)fAmd.l(1995 F) 11
---------------------- Page: 15 ----------------------
SOKEI 10164-7 : 199WAmd.l: 1995 (F)
Table B.l (continued) - Notification support
Value of abject
identifier for the
Index Sub-index Notification field name label attribute type Constraints and values Status Support i~~iti~~a~
associated with
the field
2 2.3.2.3 1ocalDistinguishedName m
2.3.3 application OBJECT IDENTIFIER m
r
(dmi-att 25) m
2.4 serviceuser
2.4.1 identifier OBJECT IDENTIFIER m
1
2.4.2 details m
serviceprovider (dmi-att 24) m
2.5
2.5.1 identifier OBJECT IDENTIFIER m
r
2.5.2 details m
1
1
2.6 notification.Identifier : (dmi-att 16) INTEGER k m
,
correlatedNotifications (dmi-att 12) m
2.7 -
2.7.1 correlatedNotifications m
I
2.7.2 sourceObjectInst m
L 1
2.7.2.1 distinguishedName m
L
nonSpecifïcForm m
2.7.2.2
2.7.2.3 1ocalDistinguishedName m
2.8 additionalText (dmi-att 7) m
L
(dmi-att 6) m
2.9 additionalInformation required for some abjects
3 3.1 securityAlarmCause (dmi-att 21) OBJECT IDENTIFIER m
3.2 securityAlarmSeverity ( dmi-att 23 ) ENUMERATED 0 to 4 m
securityAlarmDetector (dmi-att 22) m
3.3
r
3.3.1 mechanism OBJECT IDENTIFIER m
-
3.3.2 abject m
I
3.3.2.1 distinguishedName m
3.3.2.2 nonSpecificForm m
3.3.2.3 1ocalDistinguishedName m
L
application OBJECT IDENTIFIER m
3.3.3
3.4 serviceuser ( dmi-att 25) m
3.4.1 identifier OBJECT IDENTIFIER m
3.4.2 details m
3.5 serviceprovider (dmi-att 24) m
3.5.1 identifier OBJECT IDENTIFIER m
r
details m
3.5.2
(continued)
12 Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
---------------------- Page: 16 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
Table B.l (continued) - Notification support
Value of abject
identifier for the
Index Sub-index Notification field name label attribute type Constraints and values Status Support A:!d:::
associated with
the field
n
...
NORME
lSO/CEI
10164-7
INTERNATIONALE
Première édition
1992-05-I 5
AMENDEMENT 1
1995-I 2-l 5
Technologies de l’information -
Interconnexion de systèmes ouverts
(OSI) - Gestion-systèmes: Fonction de
signalisation des alarmes de sécurité
AMENDEMENT 1: Formulaires de déclaration
de conformité d’instance
Information technology - Open Sys tems In terconnection - Sys tems
Management: Security alarm reporting function
AMENDMENT 1: Implementation conformance statement proformas
Numéro de référence
ISO/CEI 10164-7:1992/Amd.l:1995(F)
---------------------- Page: 1 ----------------------
ISOKEI 10164-7:1992/Amd.l:1995(F)
Avant-propos
LIS0 (Organisation internationale de normalisation) et la CE1 (Commission
électrotechnique internationale) forment ensemble un système consacré à la
normalisation internationale considérée comme un tout. Les organismes nationaux
membres de I’ISO ou de la CE1 participent au développement de Normes inter-
nationales par l’intermédiaire des comités techniques créés par l’organisation
concernée afin de s’occuper des différents domaines particuliers de l’activité
technique. Les comités techniques de I’ISO et de la CE1 collaborent dans des
domaines d’intérêt commun. D’autres organisations internationales, gouverne-
mentales ou non gouvernementales, en liaison avec I’ISO et la CE1 participent
également aux travaux.
Dans le domaine des technologies de l’information, 1’ISO et la CE1 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
approbation, avant leur acceptation comme Normes internationales. Les Normes
qui requièrent
internationales sont approuvées conformément aux procédures
l’approbation de 75 % au moins des organismes nationaux votants.
L’Amendement 1 à la Norme internationale ISOKEI 10164-7: 1992 a été élaboré par
le comité technique mixte ISOKEI JTC 1, Technologies de Z’information, sous-
comité SC 21, Interconnexion des systèmes ouverts, gestion des données et
traitement distribué ouvert, en collaboration avec I’UIT-T. Le texte identique est
publié en tant que Recommandation UIT-T X736/Amd. 1.
0 ISOKEI 1995
Droits de reproduction r&ervé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.
ISOKEI Copyright Office l Case postale 56 l CH- 1211 Genève 20 l Suisse
Version française tin5e en 1996
Imprimé en Suisse
ii
---------------------- Page: 2 ----------------------
@ ISOKEI ISOKEI 10164-7: 1992/Amd.l: 1995(F)
Introduction
Le présent amendement contient les tableaux qui indiquent les informations de gestion obligatoires et facultatives
propres à la fonction de signalisation des alarmes de sécurité. Il sera utilisé par les spécificateurs de profils, par exemple
ceux qui élaborent des profils normalisés internationaux (ISP) (international standardized profiles), quand ils spécifient
un sous-ensemble explicite de capacités afin d’assurer l’interopérabilité des applications. Les tableaux comportent
aussi une colonne dans laquelle les fournisseurs d’équipements indiqueront les capacités de leurs produits en termes de
profils ou de spécifications de base. La structure des tableaux est conforme aux lignes directrices contenues dans la
Rec. UIT-T X.724 I ISOKEI 10165-6 pour l’établissement des formulaires de d&laration de conformité des instances de
protocole.
---------------------- Page: 3 ----------------------
Page blanche
---------------------- Page: 4 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
NORME INTERNATIONALE
RECOMMANDATION UIT-T
TECHNOLOGIES DE L’INFORMATION - INTERCONNEXION DE SYSTÈMES
OUVERTS (OSI) - GESTION-SYSTÈMES: FONCTION DE SIGNALISATION
DES ALARMES DE SÉCURITÉ .
AMENDEMENT 1
(à la Rec. UIT-T X.736 1 ISOKEI 10164-7)
FORMULAIRES DE DÉCLARATION DE CONFORMITÉ D’INSTANCE
Au paragraphe 2.1, ajouter la note de bas de page suivante au premier élément de la liste:
1)
«l) Tel que modifiée par la Rec. UIT-T X.701Kor.2 I ISOKEI 10040/Cor.2.»
Au paragraphe 2.1, ajouter la référence suivante:
2)
«- Recommandation UIT-T X.724 (1993) I ISOKEI 10165.6:1994, Technologie 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 de protocole associés à la
gestion OSI. »
Au paragraphe 2.2, ajouter les références suivantes:
3)
«- Recommandation X.291 du CCITT (1992), Cadre général et méthodologie des tests de conformité
d’interconnexion des systèmes ouverts pour les Recommandations sur les protocoles pour les applications
de I’UIT-T - Spécifïcation de suites de tests abstraite.
ISOKEI 9646-2: 199 1, 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.2963), Cad re général et méthodologie des tests de conformité OSI pour les
Recommandations sur les protocoles pour les applications de I’UIT-T - Déclarations de conformité
d’instance.
ISOKEI 9646-73), Technologies de 1 ‘information - Interconnexion de systèmes
ouverts - Méthodologie
générale et procédures - Partie 7: Déclarations de conformité des instances. »
Ensuite, ajouter la note de bas de page suivante:
«3) Actuellement à Mat de projet.»
Au paragraphe 3.4, faire les modifications suivantes:
4)
Remplacer «conformité induite» par «déclaration de conformité d’objet géré (MOCS)».
Remplacer «conformite générale» par «déclaration de conformité d’information de gestion @KS)».
Les points e) etf) deviennent les points g) et h). Insérer les nouveaux points suivants:
«e) formulaire MICS;
f) formulaire MOCS;»
Au paragraphe 3.7, faire les modifications suivantes:
5)
Remplacer «déclaration de conformité du syst&me» par:
«a) formulaire PICS;
b) déclaration de conformité d’instance de protocole;
c) déclaration de conformité du système.»
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
1
---------------------- Page: 5 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
Le paragraphe 3.8 devient 3.9. Insérer le nouveau paragraphe suivant:
6)
u3.8 Définition des formulaires de déclaration de conformité d’instance
La présente Recommandation I Norme internationale utilise les termes suivants définis par la Rec. UIT-T X.724 I
ISOKEI 10165-6:
a) déclaration de conformité de relation gérée (MRCS);
b) récapitulatif de conformité de gestion (MCS);
c) formulaire de déclaration de définition d’information de gestion (MIDS);
d) formulaire MCS;
e) formulaire MRCS .»
A l’article 4, ajouter les abréviations suivantes:
7)
«ICS Déclaration de conformité d’instance (implementation confonnance statement)
MCS Récapitulatif de conformité de gestion (management conformance summary)
M.ICS 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)
MOCS Déclaration de conformité d’objet géré (managed abject conformance statement)
MRCS Déclaration de conformité de relation gérée (managed relationship conformance statement)
Déclaration de conformité d’instance de protocole (protocol implementation conformance
PICS
statement)»
Remplacer l’article 13 par ce qui suit:
8)
Conformité
«13
I Norme internationale doivent satisfaire aux
Les instances qui se veulent conformes a la présente Recommandation
prescriptions de conformité définies aux paragraphes suivants.
13.1 Conformité statique
L’instance doit satisfaire aux prescriptions de conformité de la présente Recommandation 1 Norme internationale dans
son rôle de gestionnaire, son rôle d’agent, ou dans les deux rôles. Une déclaration de conformité à l’un des rôles au moins
sera faite au Tableau A. 1.
Si une déclaration de conformité est faite pour la prise en charge du rôle de gestionnaire, l’instance doit prendre
en charge l’une au moins des notifications ou l’une au moins des opérations de gestion spécifiées dans la presente
Recommandation I Norme internationale. Les prescriptions de conformité du rôle de gestionnaire à ces opérations et
notifications de gestion sont identifiés au Tableau A.3 et dans d’autres tableaux référencés dans 1’Annexe A.
Si une déclaration de conformité est faite pour la prise en charge du rôle d’agent, l’instance doit prendre en charge l’une
au moins des notifications spécifiées dans la présente Recommandation I Norme internationale. Les prescriptions de
conformité du rôle d’agent sont identifiés au Tableau A.4 et dans d’autres tableaux référencés dans 1’Annexe A.
L’instance doit prendre en charge la syntaxe de transfert obtenue à partir des règles de codage specifiées dans la
Rec. X.209 du CCITT I ISOKEI 8825 appelée {joint-iso-ccitt asnl( 1) basicEncoding( 1)) pour les types abstraits de
données référencés par les définitions que l’instance veut prendre en charge.
NOTE - Avant publication du présent amendement, la présente Recommandation I Norme internationale identifiait des
classes de conformite générale et induite. Une declaration de conformité semblable à celle de la classe de conformité générale peut
être faite en declarant la prise en charge par le rôle de gestionnaire, le rôle d’agent ou par les deux rôles, de l’unit6 fonctionnelle de
rapport d’alarme de securite du Tableau A.2. Une déclaration de conformité semblable à celle de la classe de conformité induite peut
être faite en declarant la prise en charge de l’un au moins des élements des Tableaux A.3 ou A.4.
2 Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
---------------------- Page: 6 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
13.2 Conformité dynamique
Les instances qui se veulent conformes à la présente Recommandation I Norme internationale doivent prendre en charge
les éléments de procédure et les définitions sémantiques correspondant aux définitions qu’elles veulent prendre en
charge.
13.3 Prescriptions de déclaration de conformité d’information de gestion
Un formulaire MCS, MICS ou MOCS conforme à la présente Recommandation l Norme internationale doit être
identique, dans son texte, aux formulaires correspondants spécifiés dans les Annexes A, B, ou C, doit conserver la
numérotation des tableaux et les numéros d’index des différents éléments et ne peut différer de ces formulaires que par la
pagination et les en-têtes de page.
Le fournisseur d’une instance qui se veut conforme à la présente Recommandation I Norme internationale doit compléter
un formulaire récapitulatif de conformité de gestion (MCS) fourni dans I’Annexe A, ce qui fait partie des prescriptions
de conformité, de même que tout autre formulaire ICS referencé qui est applicable d’après le MCS. Un ICS qui se veut
conforme à la présente Recommandation I Norme internationale:
-
decrit une instance conforme à la présente Recommandation I Norme internationale;
-
est rempli conformément aux instructions données à cet effet dans la Rec. UIT-T X.724 I
ISOKEI 101656;
-
contient les renseignements nécessaires pour identifier sans ambiguïté le fournisseur et l’instance.
Les déclarations de conformité d’information de gestion définies dans la présente Recommandation I Norme
internationale pour des classes d’objets gérés définies par ailleurs comprennent les prescriptions MIDS, tels que les
spécifie le formulaire MOCS pour la classe des objets gérés.»
Ajouter les annexes suivantes:
9
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
3
---------------------- Page: 7 ----------------------
ISOKEI 10164-7 : 199WAmd.l: 1995 (F)
Annexe A
Formulaire MCW
(Cette annexe fait partie intégrante de la présente Recommandation I Norme internationale)
Al l Introduction
A.l.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 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.
A.l.2 Instructions for completing the MCS proforma to produce a 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.
Symbols, abbreviations and terms
A.l.3
For a11 annexes of this Recommendation 1 International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISO/IEC 9646-2 and ITU-T Rec. X.296 I ISO/IEC 9646-7, are used for the Status column:
m Mandatory;
Optional;
0
C Conditional;
X Prohibited;
-
Not applicable or out of scope.
NOTES
1 ‘c’, ‘m’, and ‘0’ are prefixed by “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 selectable options among a set of status values.
Support of at least one of the choices (from the items with the same value of N) is required.
For a11 annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISOAEC 9646-2 and ITU-T Rec. X.296 I ISOAEC 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).
Ig
A.14 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:
.
First block of columns Second block of columns Etc.
Index
In this Recommendation I International Standard the constituent parts of the table appear consecutively, starting with the
first block of columns.
3 Les utilisateurs de la presente Recommandation I Norme internationale sont autorisés a reproduire le formulaire MCS de la
présente annexe pour utiliser celui-ci conformement à son objet. Ils sont également autorises à publier le formulaire une fois
celui-ci complété. Les instructions pour le formulaire MCS sont spécifiées dans la Rec. UIT-T X.724 I ISO/CEI 101656.
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
4
---------------------- Page: 8 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
When a table with sub-rows is too wide to fit on a page, the continuation table(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
1 a b -
2 a b -
Table X.1 (concluded) - Title
Index Sub-index H 1 J K L
1 1.1 h i j
,
1.2 h i j
I 1
2 2.1 h i j
1 2.2
l I
I I h I i I j I
A complete table reconstructed from the constituent parts should have the following layout:
I Support I
,
Index A B C D E F G Sub-index H 1 J K L
1 a b - 1.1
h i j
.
1.2 h i j
r
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 tables. In the example,
above, the reference X. l/ld corresponds with the blank ce11 in column G for row with Index 1, and X. 1/1.2b corresponds
with the blank ce11 in column L for row with Sub-index 1.2.
A2 0 Identification of the implementation
A.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
I
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
5
---------------------- Page: 9 ----------------------
ISOKEI 10164-7 : 199VAmd.l: 1995 (F)
A.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.
Contact
A.2.3
The supplier of the implementation shah provide information on whom to contact if there are any queries conceming the
content of the MCS or any referenced conformance statement, in the box below.
A3 0 Identification of the Recommendations I International Standards 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
Recommendations I International Standards which specify the management information to which conformance is
claimed, in the box below.
Recommendations I International Standards to which conformance is claimed
A.3.1 Technicai corrigenda implemented
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified Recommendations I International Standards, in the box below.
A.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the
identified Recommendations I International Standards, in the box below.
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
6
---------------------- Page: 10 ----------------------
ISO/CEI 10164-7 : 1992/Amd.l: 1995 (F)
Management conformance summary
A.4
The supplier of the implementation shall state the capabilities and features supported and provide a 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 A. 1.
Table A.1 - Roles
Index Roles supported Status Support Additional information
1 Manager role support 0.1
Agent role support 0.1
2
The supplier of the implementation shah specify support for the systems management functional unit, in Table A.2.
Table A.2 - Systems management functionai unit
Manager Agent
I I I
Status Support Additional information
Index Systems management functional unit name Status Support
1 security alarm reporting functional unit cl c2
I I I I I
I I I
cl: if A.l/la then o else -.
c2: if A. 1/2a then o else -.
The supplier of the implementation shall specify support for management information in the manager role, in Table A.3.
Table A.3 - Manager role minimum conformance requirement
Item Status support Additional information
Index
Integrity violation notification c3
1
c3
2 Operational violation notification
c3
3 Physical violation notification
c3
4 Security service or mechanism violation notification
c3
Time domain violation notification
5
c4
6 Operations on managed abjects
c3: if AZla then m else (if A.l/la then 0.2 else -).
c4: if A.Ula then m else (if A.l/la then 0.2 else -).
NOTE - Manager role minimum conformance requires support for at least one of the items identified in this table. Support for the
functional unit identified in Table A.2 mandates support for some of those items. Conditions c3 and c4 express both of these
requirements.
The supplier of the implementation shall specify support for management information in the agent role, in Table A.4.
Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
---------------------- Page: 11 ----------------------
ISOKEI 10164-7 : 1992lAmd.l: 1995 (F)
Table A.4 - Agent role minimum conformance requirement
Item
Index Status Table reference Additional information
Support
1 Integrity violation notification CS
2 Operational violation notification C5
3 Physical violation notification C5
Security service or mechanism violation c5
4
notification
5 Time domain violation notification c5
-
c6
6 Security alarm record managed abject class
c5: if A.2/lb then m else (if A.l/2a then 0.3 else -).
c6: if A. 1/2a and A.5/la then m else -.
NOTES
1 Condition c6 makes it mandatory, if logging is supported, to support the event log records associated with the notifications
supported.
2 The Table reference column in this table is the notification reference of the MOCS supplied by the supplier of the managd
abject which claims to import the notification from this Recommendation I International Standard.
Table A.5 - Logging of event records
Addi tional
Index Status Support
information
Does the implementation support logging of event records in agent role? c7
1
\
c7: if A. 1/2a then o else -.
I I
NOTE 1 - Conformance to this Recommendation I International Standard does not require conformance to CCITI’
Rec. X.735 I ISO/IEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the Recommendations
I International Standards summarized in the Tables A.6 to A.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 A.6 to A.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.
Table A.6 - PICS support summary
Table
Identification of the Table
Addi tional
numbers Constraints
of pIcs Description
Index document that includes Status Support numbers
and values information
the PICS proforma of PICS
proforma
r
1 CCITT Rec. X.730 I Annex E SM application context
ISO/IEC 10164-l II=E,1 m 1 1 1 1
a11 tables
I I
NOTE 2 - Conformance to the MAPDUs defined in this Recommendation I International Standard cari be claimed by
completing the corresponding tables in the MICS and MOCS annexes of the referenced Recommendations I International Standards.
8 Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
---------------------- Page: 12 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
Table A.7 - MOCS support summary
Table
Table
Identification of the
numbers Constraints
Status Support numbers of Additiona
Description
Index document that includes of MOCS
information
and values
MOCS
the MOCS proforma
proforma
- C8
CCITT Rec. X.736 I Annex C securityAlarmRecord
1
a11 tables
ISO/IEC 10164-7
c8: if A.4/6a then m else -.
Table A.8 - MRCS support summary
I I
Table
Table
ification of the
Ident
Constraints Additional
numbers
I
Description Status Support numbers
Index document J----- that includes of MRCS
information
and values
of MRCS
the MRCS proforma
proforma
CCITT Rec. X.735 I Item logRecord-log name - c9
D. 111 binding
ISO/IEC 10164-6
c9: if A.5/la then o else -.
I
Table A.9 - MICS support summary
.
Table
Table
Identification of the
Constraints Additional
numbers
Description Status Support numbers
Index document that includes of MICS
and values information
the MICS proforma of MICS
proforma
CCITI’ Rec. X.736 I Table B. 1 notifications cl0
1
ISO/IEC 10164-7
CCITT Rec. X.736 1 Tables B.2 management cl1
ISO/IEC 10164-7 and B.3 operations
l2 I I l I l l I I I
if A.3/la or A.3/2a or A,3/3a or A.3/4a or A.3/5a then m else -.
if A.3/6a then m else -.
Rec. UIT-T X.736 (1992)/Amd.l(1995 F) 9
---------------------- Page: 13 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
Annexe B
Formulaire MICW
(Cette annexe fait partie intégrante de la présente Recommandation I Norme internationale)
Bl . Introduction
The purpose of this MICS proforma is to provide a mechanism for a supplier of an implementation which claims
conformance, in the manager role, to management information specified in this Recommendation I International
Standard, to provide conformance information in a standard form.
Instructions for completing the MICS proforma to produce a MICS
B2 l
The MICS proforma contained in this annex is comprised of information in tabular form, in accordance with ITU-T
Rec. X.724 I ISOBIEC 10165-6. In addition to the general guidance given in ITU-T Rec. X.724 I ISO/IEC 101656, the
Additional information column shah be used to identify the abject classes for which the management operations are
supported. The supplier of the implementation shah state which items are supported in the tables below and if necessary,
provide additional information.
B3 0 Symbols, abbreviations and terms
The following abbreviations are used throughout the MICS proforma:
dmi-att joint-iso-ccitt ms(9) smi(3) part2(2) attribute(7)
dmi-not joint-iso-ccitt ms(9) smi(3) part2(2) notification( 10)
The notations used for the Status and Support columns are specified in A. 1.3.
B4 l Statement of conformance to the management information
B.4.1 Notifications
The specifier of a manager role implementation that claims to support the notifications specified in this Recommendation
I International Standard shall import a copy of Table B. 1 and complete it.
Table B.1 - Notification support
I
I SUPp0I-t
Value of abject
Constraints Non- Addi tional
Index Notification type template label identifier for the S tatus Confirmed
and values confirmed information
notification type
1 integrityviolation (dmi-not 5) cl
2 0perationalViolation (dmi-not 8) c2
(dmi-not 9)
3 physicalViolation c3
I
4 securityServiceOrMechan.ism (dmi-not 13) c4
5 timeDomainViolation (dmi-not 55) c5
1
cl: if A.3/1a then m else -.
c2: if A.3/2a then m else -.
c3: if A.3/3a then m else -.
c4: if A.3/4a then m else -.
c5: if A.3/5a then m else -.
(continued)
@ Les utilisateurs de la presente Recommandation I Norme internationale sont autorises a reproduire le formulaire MICS de la
présente annexe pour utiliser celui-ci conformement à son objet.
10 Rec. UIT-T X.736 (1992)Amd.l(1995 F)
---------------------- Page: 14 ----------------------
ISOKEI 10164-7 : 1992fAmd.l: 1995 (F)
Table B.1 (continued) - Notification support
Value of abject
identifier for the
Index Sub-index Notification field name label attribute type Constraints and values Status Support i~!oditi~~~a
associated with
the field
1 1.1 securityAlarmCause (dmi-att 2 1) OBJECT IDENTIFIER m
1.2 securityAlarmSeverity ( dmi-att 23 ) ENUMERATED 0 to 4 m
securityAlarmDetector { dmi-att 22) m
1.3
1.3.1 mechanism OBJECT IDENTIFIER m
m
1.3.2 abject
m
1.3.2.1 distinguishedName
,
m
nonSpecificForm
1.3.2.2
1
m
1.3.2.3 1ocalDistinguishedName
application OBJECT IDENTIFIER m
1.3.3
( dmi-att 25 ) m
1.4 serviceuser
,
1.4.1 identifier OBJECT IDENTIFIER m
m
1.4.2 details
(dmi-att 24) m
1.5 serviceprovider
1.51 identifier OBJECT IDENTIFIER m
1 s.2 details m
notificationIdentifier (dmi-att 16) m
1.6 INTEGER
(dmi-att 12) m
1.7 correlatedNotifications
m
1.7.1 correlatedNotifications
m
sourceObjectInst
1.7.2
m
1.7.2.1 distinguishedName
m
1.7.2.2 nonSpecificForm
m
1.7.2.3 1ocalDistinguishedName
additionalText (dmi-att 7) m
1.8
1.9 additionalInformation (dmi-att 6) required for some abjects m
( dmi-att 2 1) OBJECT IDENTIFIER m
2 2.1 securityAlarmCause
m
2.2 securityAla.rmSeverity ( dmi-att 23) ENUMERATED 0 to 4
(dmi-att 22)
2.3 securityAlarmDetector m
2.3.1 mechanism OBJECT IDENTIFIER m
m
abject
2.3.2
m
2.3.2.1 distinguishedName
m
2.3.2.2 nonSpecificForm
(continued)
Rec. UIT-T X.736 (1992)fAmd.l(1995 F) 11
---------------------- Page: 15 ----------------------
SOKEI 10164-7 : 199WAmd.l: 1995 (F)
Table B.l (continued) - Notification support
Value of abject
identifier for the
Index Sub-index Notification field name label attribute type Constraints and values Status Support i~~iti~~a~
associated with
the field
2 2.3.2.3 1ocalDistinguishedName m
2.3.3 application OBJECT IDENTIFIER m
r
(dmi-att 25) m
2.4 serviceuser
2.4.1 identifier OBJECT IDENTIFIER m
1
2.4.2 details m
serviceprovider (dmi-att 24) m
2.5
2.5.1 identifier OBJECT IDENTIFIER m
r
2.5.2 details m
1
1
2.6 notification.Identifier : (dmi-att 16) INTEGER k m
,
correlatedNotifications (dmi-att 12) m
2.7 -
2.7.1 correlatedNotifications m
I
2.7.2 sourceObjectInst m
L 1
2.7.2.1 distinguishedName m
L
nonSpecifïcForm m
2.7.2.2
2.7.2.3 1ocalDistinguishedName m
2.8 additionalText (dmi-att 7) m
L
(dmi-att 6) m
2.9 additionalInformation required for some abjects
3 3.1 securityAlarmCause (dmi-att 21) OBJECT IDENTIFIER m
3.2 securityAlarmSeverity ( dmi-att 23 ) ENUMERATED 0 to 4 m
securityAlarmDetector (dmi-att 22) m
3.3
r
3.3.1 mechanism OBJECT IDENTIFIER m
-
3.3.2 abject m
I
3.3.2.1 distinguishedName m
3.3.2.2 nonSpecificForm m
3.3.2.3 1ocalDistinguishedName m
L
application OBJECT IDENTIFIER m
3.3.3
3.4 serviceuser ( dmi-att 25) m
3.4.1 identifier OBJECT IDENTIFIER m
3.4.2 details m
3.5 serviceprovider (dmi-att 24) m
3.5.1 identifier OBJECT IDENTIFIER m
r
details m
3.5.2
(continued)
12 Rec. UIT-T X.736 (1992)/Amd.l(1995 F)
---------------------- Page: 16 ----------------------
ISOKEI 10164-7 : 1992/Amd.l: 1995 (F)
Table B.l (continued) - Notification support
Value of abject
identifier for the
Index Sub-index Notification field name label attribute type Constraints and values Status Support A:!d:::
associated with
the field
n
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.