ISO/IEC 10742:1994/Amd 2:1996
(Amendment)Information technology — Telecommunications and information exchange between systems — Elements of management information related to OSI Data Link Layer standards — Amendment 2: Implementation conformance statement proformas
Information technology — Telecommunications and information exchange between systems — Elements of management information related to OSI Data Link Layer standards — Amendment 2: Implementation conformance statement proformas
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Éléments de l'information de gestion liés aux normes de la couche de liaison de données OSI — Amendement 2: Proformes de déclaration de conformité de mise en oeuvre
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
10742
STANDARD
First edition
1994-08-o 1
AMENDMENT 2
1996-07-I 5
Information technology -
Telecommunications and information
exchange between systems - Elements of
management information related to OSI
Data Link Layer standards
AMENDMENT 2: Implementation conformance
statement proformas
T&l&ommunications et khange
Technologies de I’in forma tion -
d ‘information en tre sys t&mes - &men ts d ‘information de ges tion
concernant les normes de la couche de liaison de donnkes OSI
AMENDEMENTZ: Proformes de dklaration de conformit de mise en
euvre
Reference number
lSO/IEC 10742:1994/Amd.2:1996(E)
---------------------- Page: 1 ----------------------
ISOIIEC 10742 : 1994/Amd. 2 : 1996(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 2 to International Standard ISO/IEC 10742 : 1994 was prepared by Joint
Technical Committee ISO/IEC JTC 1, 1~$3nnation technology, Subcommittee SC 6,
Telecommunications and information exchange between systems.
This Amendment is also published by ITU-T as Rec. X.282/Amd. 2 but not as identical
text.
0 ISO/IEC 1996
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-12 11 Geneve l Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
OISOAEC ISO/IEC 10742 : 1994/Amd. 2 : 1996(E)
- Telecommunications and information exchange between systems
Information technology
- Elements of management information related to OS1 Data Link Layer standards
AMENDMENT 2:
Implementation conformance statement proformas
Page 1
“Scope “.
Add the following as the last paragraph of Clause 1
Annexes E, F, G and H, which are integral parts of this International Standard provide ICS proformas associated with Data
link layer management information.
Add the following reference to subclause 2. I.
-
ITU-T Recommendation X.724 (1993) 1 ISO/IEC 10165-6: 1994, information technoZo,oy - Open Systems
Structure of management information: Requirements and guidelines for implementation
Interconnection -
conformance statement proformas associated with 0511 management .
Page 2
Add the foZEowing references to subclause 2.2:
-
CCITT Recommendation X.209 (1988), Specijcation of basic encoding rules for abstract syntax notation
one (ASN. 1).
ISO/IEC 8825: 1990, Information technology - Open Svstems Interconnection - Specification of Basic
Encoding Rules for Abstract Syntax Notation One (ASN. i).
CCITT Recommendation X.290 (1991), OSI conformance testing methodology and framework for protocol
”
Recommendations for CCITT applications - General concepts.
ISO/IEC 9646- 1: 1994, Information technology - Open Systems Interconnection - Conformance testing
methodology andframework - Part I: General concepts.
CCITT Recommendation X.29 1 (1992), OSI conformance testing methodology and framework for protocol
Recommendations for CCITT applications -Abstract test suite specification.
ISOLEC 9646-2: 1994, Information technology - Open Systems Interconnection - Conformance testing
methodology andframework - Part 2: Abstract Test Suite specification.
NOTE - ISO/IEC 9646-l : 1994 and ISO/IEC 9646-2: 1994 supersede ISOAEC 9646-l : 199 1 and ISO/IEC 9646-2:
1991 respectively. However, when this International Standard was under development, the previous editions were
valid and this International Standard is therefore based on these editions, which are listed below.
ISOIIEC 9646-l : 1991, Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts.
ISO5EC 9646-2: 199 1, Information technology - Open Systems Interconnection - Co1zformance
methodology and framework - Part 2: Abstract test suite specification.
ITU-T Recommendation X.296 (1995), OSI conformance testing methodology and framework for protocol
Recommendations for ITU-T applications - Implementation Co)?formance Statements.
---------------------- Page: 3 ----------------------
ISO/IEC 10742 : 1994/Amd. 2 : 1996(E) OISOAIX
ISO/IEC 9646-7: 1995, Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation conformance statements.
Page 4
Add the following abbreviations to clause 4:
MCS management conformance summary
management information conformance statement
MICS
MOCS managed object conformance statement
MRCS managed relationship conformance statement
Page 33
Replace clause 7 with the following:
7
Conformance
Implementations claiming to conform to this International Standard shall comply with the conformance requirements
defined in the following subclauses.
71 Conformance requirements to this International Standard
.
7.1.1 Static conformance
The implementation shall conform to the requirements of this International Standard in . the manager role, the agent role, or
ndard.
both . roles. A claim of conformance to at least one role shall be made in Table E. 1 of thi s International Sta
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 International Standard. The
conformance requirements in the manager role for those management operations, notifications and actions are identified in
Table E.3 and further tables referenced by Annex E.
If a claim of conformance is made for support in the agent role, the implementation shall support one or more instances of
the data link subsystem managed object class and the data link sef7irice access point managed object class identified in Table
E.4 of this International Standard and further tables referenced by Annex E.
If a claim of conformance is made for support in the agent role, the implementation shall support at least one name binding
identified in Table E.7 of this International Standard for each supported managed object.
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.
7.1.2 Dynamic conformance
Implementations claiming to conform to this International Standard shall support the elements of procedure and definitions
of semantics corresponding to the definitions for which support is claimed.
2
---------------------- Page: 4 ----------------------
0ISOA.E ISO/IEC 10742 : 1994/Amd. 2 : 1996(E)
7.1.3 Management implementation conformance statement requirements
Any MCS proforma, MICS proforma, MOCS proforma, and MRCS proforma which conform to this International Standard
shall be technically identical to the proformas specified in Annexes E, F, G and H 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 International Standard shall complete a copy of the
management conformance summary @KS) provided in Annex E as part of the conformance requirements together with
any other ICS proformas referenced as applicable from that MCS.
Any MCS, MICS, MOCS, and MRCS which conform to
this International Standard shall:
-
describe an implementation which conforms to this International Standard;
-
have been completed in accordance with the instructions for completion given in ITU-T Rec. X.724 1
ISO/IEC 10 165-6;
-
include the information necessary to uniquely identify both the supplier and the implementation.
72 . Protocol specific conformance requirements
The supplier of an implementation which is claimed to conform to this International Standard shall support at least one
protocol identified in Table E.2 of this International Standard.
7.2.1 Conformance to the IS0 7776
An implementation claming conformance to ISO/IEC 7776 in the agent role as a managed implementation shall:
conform to ITU-T Recommendation X.282 1 ISO/IEC 10742 as defined in 7.1;
a)
support the 1APBDLE MO, the sLPPM MO and sLPConnection MO.
b)
7.2.2 Conformance to the ISO/IEC 8802-2 connectionless-mode LLC
An implementation claming conformance to ISO/IEC 8802-2 connectionless-mode LLC in the agent role as a managed
implementation shall:
conform to ITU-T Recommendation X.282 1 ISO/IEC 10742 as defined in 7.1;
a>
support the 1LCDLE MO and at least one class derived from the 1LCCLPM MO.
b)
7.2.3 Conformance to the ISO/IEC 8802-2 connection-mode LLC
An implementation claming conformance to ISO/IEC 8802-2 connection-mode LLC in the agent role as a managed
implementation shall:
conform to ITU-T Recommendation X.282 1 ISO/IEC 10742 as defined in 7.1;
a)
support the 1LCDLE MO and at least one class derived from the 1LCCOPM MO.
W
7.2.4 Conformance to the IS0 8802 MAC
An implementation claming conformance to IS0 8802 MAC in the agent role as a managed implementation shall:
conform to ITU-T Recommendation X.282 I ISO/IEC 10742 as defined in 7.1;
a>
support the mACDLE MO and at least one class derived from the mAC MO.
b)
11
Page 60
Add the following annexes after Annex D.
---------------------- Page: 5 ----------------------
ISO/IEC 10742 : 1994/Amd. 2 : 1996(E) OISO5EC
Annex E
(normative)
MCS proforma’ )
El . Introduction
E.l.l 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 supplier of an
by the
implementation becomes the MCS.
E.1.2 Instructions for completing the MCS proforma to produce an MCS2 )
The supplier of the implementation shall enter an explicit statement in each of the provided. Specific instruction is
provided in the text which precedes each table.
E.1.3 Symbols, abbreviations and terms
For all annexes of this International Standard, the following common notations, defined in CCITT Rec. X.291 1 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
1 - ‘c ’, ‘m ’, and ‘0’ are prefixed by a ‘c:’ when nested under a conditional or optional item of the same table;
options among a set of status
2 - ‘0’ may be suffixed ‘.N’ (where N i .s a unique number) for mutually excl usive or selectable
bY
items with the same values of N)
values. Support of at least one of the choices (from the is required.
For all annexes of this International Standard, the following common notations, defined in CCITT Rec. X.29 1 1 ISOKIEC
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;
Ig the item is ignored (i.e. processed syntactically but not semantically).
’ ) Users of this 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 fo
r completing the MCS proforrna are specified in ITU-T Rec.X.724 1 ISO/IEC 10165-6 .
4
---------------------- Page: 6 ----------------------
OISOAlX ISO/IEC 10742 : 1994/Amd. 2 : 1996(E)
Identification of the implementation
E2 .
E.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
E.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.
E.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.
E3 Identification of the 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 International
Standard which specifies the management information to which conformance is claimed, in the box below.
International Standard to which conformance is claimed
E.3.1 Technical corrigenda implemented
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified International Standard, in the box below.
5
---------------------- Page: 7 ----------------------
OISOAEC
ISOlIEC 10742 : 1994/Amd. 2 : 1996(E)
E.3.2 Amendments implemented
numbers of implemented amendments to the
The supplier of the implementation shall state the titles and reference
identified International Standard, in the box below.
E4 . Management conformance summary
The supplier of implementation shall state the capabilities and features supported and provide summary of conformance
claims to Recommendations 1 International Standards using the tables in this annex.
The supplier of the implementation shall specifjr the roles that are supported, in Table E. 1
Table E.l - Roles
,
support Additional information
Status
Index Roles supported
0.1
1 Manager role support
0.1
Agent role support
2
The supplier of the implementation shall specify the protocols that are supported, in Table E.2
Table E.2 - Protocol
Additional information
Status support
Protocol supported
Index
1
IS0 7776 support
0.2
2
IS0 8802-2 (CL mode) support
0.2
3 IS0 8802-2 (CO mode) support
0.2
4 ISO/IEC 8802 MAC support
cl
cl: if E.2/2a or E.2/3a then m else -
The supplier of the implementation shall speci@ support for management information in the manager role, in Table E-3.
Table E.3 - Manager role minimum conformance requirement
Additional information
Status support
Item
cl
1 Operations on managed objects
Cl
2 Attribute value change notification for EWMA metric monitor managed object
cl
3 Object creation notification for EWMA metric monitor managed object
cl
4 Object deletion notification for EWMA metric monitor managed object
cl
5 Quality of service alarm notification for EWMA metric monitor managed object
cl
State change notification for EWMA metric monitor managed object
6
c2
Object creation notification for LAPB data link entity managed object
7
c2
Object deletion notification for LAPB data link entity managed object
8
c2
9 State change notification for LAPB data link entity managed object
c3
10 Object creation notification for LLC data link entity managed object
c3
11 Object deletion notification for LLC data link entity managed object
c3
State change notification for LLC data link entity managed object
12
c4
13 Object creation notification for MAC data link entity managed object
c4
Object deletion notification for MAC data link entity managed object
14
c4
15 State change notification for MAC data link entity managed object
c2
Deactivate action for SLP connection managed object
16
c2
17 Communications alarm notification for SLP connection managed object
c2
18 Object creation notification for SLP connection managed object
c2
19 Object deletion notification for SLP connection managed object
c2
20 Object creation notification for SLP connection IV managed object
6
---------------------- Page: 8 ----------------------
OISOAEC ISO/IEC 10742 : 1994/Amd. 2 : 1996(E)
Table E.3 (concluded) - Manager role minimum conformance requirement
Item Status support Additional information
21 Object deletion notification for SLP connection IV managed object c2
22 Activate action for SLP protocol machine managed object c2
23 Deactivate action for SLP protocol machine managed object c2
24 Object creation notification for SLP protocol managed object c2
25 Object deletion notification for SLP protocol managed object c2
State change notification for SLP protocol machine managed object
26 c2
cl: if E.l/la then 0.3 else -
c2: if E. l/la and E.2/la then 0.3 else -
c3: if E.l/la and (E.2/2a or E.2/3a) then 0.3 else -
c4: if El/la and E.2/4a then 0.3 else -
The supplier of the implementation shall specify support for management information in the agent role, in Table E.4
Table E.4 - Agent role minimum conformance requirement
Status support Additional information
Index Item
m
1 Data link subsystem managed object
2 Data link service access point managed object m
3 LAPB data link entity managed object C5
4 LAPB single link protocol machine managed object c5
5 LAPB single link protocol connection managed object c5
c6
6 LAPB single link protocol connection initial values managed object
c7
7 MAC data link entity managed object
c8
8 MAC managed object
9 LLC data link managed object c9
10 LLC connectionless protocol machine managed object cl0
il LLC connection-mode protocol machine managed object cl1
c5: if E. 1/2a and E.2/la then m else -
c6: if E. 1/2a and E.2/la then o else -
c7: if E. 1/2a and E.2/4a then m else -
c8: if E. 1/2a and E.2/4a then o else -
c9: if E. 1/2a and E2/2a or G.2/3a then m else -
~10: if E. 1/2a and E.2/2a then o else -
cl 1: if E. 1/2a and E.2/3a then o else -
Table ES - Logging of event records
Status support Additional information
Index
cl2
1 Does the implementation support logging of event records in agent role?
~12: if E. 1/2a then o else -
NOTE - Conformance to this International Standard does not require conformance to CCIT.T Rec. X.735 1 ISOLIEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the International
Standards summarized in the following tables. For each 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.
7.
---------------------- Page: 9 ----------------------
OISO/IK
ISOlIEC 10742 : 1994/Amd. 2 : 1996(E)
In tables E.6, E.7 and E.8, 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 E.6 - MOCS support summary
Support Table Additional
Description Constraints Status
Index Identification of the Table numbers of
numbers of information
and values
document that includes the MOCS proforma
MOCS
MOCS proforma
-
dLSAP m
1 “ISO/IEC 10742” G.1 -G.4
-
datalinksubsystem m
2 “ISO/IEC 10742” G.5 - G.8
-
0
“ISO/IEC 10742” G.9 - G.14 eWMAMetricMonitor
3
-
cl3
” I SO/I EC 10742” G.15 - G.20 IAPBDLE
4
-
cl4
“ISO/IEC 10742” G.21 ILCCLPM
5
-
ILCCOPM cl5
“ISO/IEC 10742” G.22
6
-
cl6
“ISO/IEC 10742” G.23 - G.28 ILCDLE
7
,
-
mAC cl7
8 “ISO/IEC 10742” G.29
-
mACDLE cl8
9 “ISO/IEC 10742” G.30 - G.35
-
0
resourceTypeld
10 ” ISOA EC 10742” G.36 - G.39
-
cl9
” ISO/I EC 10742” G.40 - G.47 sLPConnection
11
-
c20
“ISO/IEC 10742” G.48 - G.53 sLPConnectionlVM0
12
-
c21
“ISO/IEC 10742” G.54 - G.60 sLPPM
13
-
objectCreationRecord c22
14 ‘ISO/IEC 10164-l” Table C. 1 - C.4
-
objectDeletionRecord c22
15 “ISO/IEC 10164-l” Table C.5 - C.8
Table C.9 - C.12 attributeValueChangeRecord - c23
16 ‘ISO/IEC 10164-l”
-
c24
Table C. 1 - C.4 rstateChangeRecord
17 “ISO/IEC 10164-2”
-
~25
Table C.l - C.4 alarmRecord
18 ‘ISO/IEC 10164-4”
~13: if E.4/3a then m else -
~14: if E.4/10a then m else -
cl5 if E.4/11a then m else -
~16: if E.4/9a then m else -
~17: if E.4/8a then m else -
~18: if E.4/7a then m else -
~19: if E.4/5a then m else -
~20: if E.4/6a then m else -
c2 1: if E.4/4a then m else -
~22: if E.6/4a or E.6/5a or E.6/6a or E.6/7a or E.6/8a or E.6/9a or E.6/1 la or E.6/12a or E6/13a then m else -
~23: if E.6/4a then m else -
~24: if E.6/4a or E.6/5a or E.6/6a or E.6/7a or E.6/8a or E6/9a or E6/13a then m else -
~25: ifE.6/4a or E.6/1 la then m else -
---------------------- Page: 10 ----------------------
OISOAEIC ISO/IEC 10742 : 1994/Amd. 2 : 1996(E)
Table E.7 - MRCS support summary
Index Identification of the Table numbers Description Constraints and values Status Support Table numbers Additional
document that includes the of MRCS of MRCS information
M RCS proforma proforma
-
1 “ISO/IEC 10742” Table H. l/l dLSAP-datalinkEntity- 0.4
Management
-
2 ” I SO/I EC 10742” Table H. l/2 “CCITT Rec. X.723 (1993) 1 0.4
ISO/IEC 10165-5 : 1993 ”:
sap1 -communicationsEntity
-
3 “ISO/IEC 10742” Table H. l/3 datalinkEntity- 0.5
datalinksubsystem-
Management
--
4 “ISO/IEC 10742” Table H. l/4 “CCITT Rec. X.723 (1993) 1 0.5
I SO/I EC 10165-5 : 1993 ”:
communicationsEntity-
subsystem
--
“CCITT Rec. X.723 (1993) 1
5 “ISO/IEC 10742” Table H. l/5 m
ISO/IEC 10165-5 : 1993 ”:
subsystem-system
--
6 “ISO/IEC 10742” Table H. l/6 eWMAMetricMonitor- c26
ILCDLE-Management
-
7 “ISO/IEC 10742” Table HI7 eWMAMetricMonitor- c26
mACDLE-Management
-
8 “ISO/IEC 10742” Table H. l/8 ILCCLPM-ILCDLE- c27
Management
-
9 “ISO/IEC 10742” Table H. l/9 “CCITT Rec. X.723 (1993) 1 c27
ISO/IEC 10165-5 : 1993 ”:
clProtocolMachine-entity
-
10 “ISO/IEC 10742” Table H. l/l0 ILCCOPM-ILCDLE- c28
Management
-
11 “ISO/IEC 10742” Table H. l/l 1 “CCITT Rec. X.723 (1993) I c29
ISO/IEC 10165-5 : 1993 ”:
coProtocolMachine-entity
-
mAC-mACDLE-Automatic c30
12 “ISO/IEC 10742” Table H. l/l2
-
13 “ISO/IEC 10742” Table H. l/l 3 mAC-mACDLE-Management c30
-
14 “ISO/IEC 10742” Table H. l/l4 resourceTypeld-ILCDLE- c31
Automatic
-
15 “ISO/IEC 10742” Table H. l/l 5 resourceTypeld-mACDLE- c31
Automatic
16 “ISO/IEC 10742” Table H. l/16 sLPConnection-sLPPM- c32
Automatic
--
17 “ISO/IEC 10742” Table H. l/l 7 sLPConnection-sLPPM- c32
Management
18 “ISO/IEC 10742” Table H. l/l 8 “CCITT Rec. X.723 (1993) I c32
ISO/IEC 10165-5 : 1993 ”:
SinglePeerConnection-
coProtocolMachine
“ISO/IEC 10742” Table H. l/l 9 sLPConnectionIVMO- c33
19
sLPPM-Management
-
sLPPM-IAPBDLE- c34
20 “ISO/IEC 10742” Table H. l/20
Management
c35
21 “ISO/IEC 10164-6” Table D. l/l logRecord-log
~26: if E.6/3a then 0.6 else -
~27: if E.6/4a then 0.7 else -
~28: if E.6/5a then 0.9 else -
~29: if E.6/6a then 0.9, if E.6/13a then o. 10, if E.6/6a and E.6/13a then 0.9 and o. 10 else -
~30: if E.6/8a then o. 11 else -
c3 1: if E.6/10a then o. 12 else -
~32: if E.6/1 la then 0.13 else -
~33: if E.6/12a then m else -
~34: if E.6/13a then 0.10 else -
~35: if E.6/14a or E.6/15a or E.6/16a or E.6/17a or E.6/18a then m else -
---------------------- Page: 11 ----------------------
ISOIIEC 10742 : 1994/Amd. 2 : 1996(E)
Table E.8 - MICS support summary
Index Identification of the Table numbers Description Constraints and Status support Table numbers of Additional
document that includes of MICS values MICS information
the MICS proforma proforma
-
“ISO/IEC 10742” Table F.l to management c36
1
F.23 operations
-
” I SO/l EC 10742” Table F.24 notifications c37
2
-
3 “ISO/IEC 10742” Table F.25 actions c38
~36: if E.3/la then m else -
~37: if E.3l2a or E.3/3a or E.3/4a or E.3/5a or E.3/6a or E.3/7a or E3/8a or E.3/9a or E.3/10a or E.Ylla or E.3/12a or
E.3113a or E.3/14a E.3115 or E.3/17a or E.3/18a or E.3/19a or E.3/20a or E.3/2la or E.3/24a or E.3/25a or E.3/26a then m
else -
~38: if E.3/16a or E.3/22a or E.3/23a then m else -
10
---------------------- Page: 12 ----------------------
OISOAIK ISO/IEC 10742 : 19941Amd. 2 : 1996(E)
Annex F
(normative)
MICS proforma ’)
Fl . 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 International Standard, to provide
conformance information in a standard form.
F2 . Instructions for completing the MICS proforma 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 1 ISO/IEC 10165-6. In addition to the general guidance given in KU-T Rec. X.724 1 ISO/IEC 101656. The
supplier of the implementation shall state which items are supported in tables below and if necessary, provide additional
information.
F3 . Symbols, abbreviations and terms
The MICS proforma contained in this Annex is comprised of information in tabular form, in accordance with CCITT Rec.
X.291 1 ISO/IEC 9646-2.
The notations used in the Status and Support columns are specified in F. 1.3.
F4 . Statement of conformance to the management information
F.4.1 Attributes
The specifier of a manager role implementation that claims to support management operations on the attributes specified in
this International Standard shall import a copy of the following tables and complete them.
F.4.1.1 The Data Link Service Access Point managed object
Table F.l - dLSAP Attribute support
Set Set by by create create Get Get Replace Replace Add Add Remove Remove Set Set to to
default default
Index Index Attribute Attribute template template label label Value Value of of object object Constraints Constraints and and Status Status Suppor Suppor Status Status Suppor Suppor Status Status Suppor Suppor Status Status Suppor Suppor Status Status Suppor Suppor Status Status Suppor Suppor Additional Additional
identifier identifier for for values values t t t t t t t t t t t t information information
attribute attribute
1 1 ““Rec. Rec. X.721 X.721 j j ISO/IEC ISO/IEC (2 (2 9 9 3 3 2 2 7 7 50) 50) SET SET OF OF cl cl 0.14 0.14
10165-2 10165-2 : : 19921992 ””: : ObjectClass ObjectClass
allomorphs allomorphs
2 2 ““Rec. Rec. X.721 X.721 I I ISO/IEC ISO/IEC (2 (2 9 9 3 3 2 2 7 7 63) 63) OBJECT OBJECT cl cl 0.14 0.14
10165-2 10165-2 : : 19921992 ””: : IDENTIFIER IDENTIFIER
nameBinding nameBinding
cl cl 0.14 0.14
3 3 ““Rec. Rec. X.72 X.72 1 1 j j ISO/IEC ISO/IEC (2 (2 9 9 3 3 2 2 7 7 65) 65) ObjectClass ObjectClass
10165-2 10165-2 : : 19921992 ””: :
objectClass objectClass
0.14 0.14
4 4 ““Rec. Rec. X.721 X.721 j j ISO/IEC ISO/IEC (2 (2 9 9 3 3 2 2 7 7 66) 66) SET SET OF OF OBJECT OBJECT cl cl
10165-2 10165-2 : : 19921992 ””: : IDENTIFIER IDENTIFIER
, .packages packages . _
” Users of this International Standard may freely reproduce the PICS profonna in this Annex so that it can be used for its intended purpose, and may fiwther
publish the completed PICS.
11
---------------------- Page: 13 ----------------------
ISO/IEC 10742 : 1994/Amd. 2 : 1996(E)
Table F.1 (concluded) - dLSAP Attribute support
Set to
Set by create Get Replace Add Remove
default
I I I I
1
Value of object Constraints and Status Suppor Status Status Suppor Status Suppor Additional
ttribute template label
t t t information
identifier for values
attribute
0.14
5 “CCITT Rec. X.723 (2 9 3 5 7 8) INTEGER
(1993) I ISO/IEC 10165-
5 : 1993":
saplAddress
(2 9 3 5 7 10) GraphicString cl 0.14
6 “CCITT Rec. X.723
(1993) I ISO/IEC 10165-
5 : 1993":
sapld
0.14
7 “CCITT Rec. X.723 (29357 15) SETOF
(1993) I ISO/IEC 10165- Object Instance
5 : 1993":
userEntitvNames
I I
~ ~~~
cl: if F.l7/la then 0.14 e Ise -
F.4.1.2 The Data Link Subsystem managed object
Table F.2 - datalinksubsystem Attribute support
Set to
Set by create Get Replace Add Remove
default
Status Suppor Status Suppor Status Suppor Status Suppor Status Suppor Status Suppor Additional
Index bttribute template label klue of object IConstraints and
,I. .-A 4 + + + i t infnrmatinn
L L II ll"' I I lUCl"l I
1 1 1 1
identifier for ~IIU~:S
attribute
0.14
1 “Rec. X.721 I ISO/IEC (2 9 3 2 7 50) SET OF
10165-2 : 1992 ”: IObjectClass 1
I I I I I I I I I I I I I I I
allomorphs I I I I I
! ! 1 I I I I I I I
I
0.14
2 I “Rec. X.721 I ISO/IEC I (2 9 3 2 7 63) I OBJECT
10165-2 : 1992 ”: IDENTIFIER
nameBinding
3 “Rec. X.721 I ISO/IEC (2 9 3 2 7 65) ObjectClass 0.14
10165-2 : 1992 ”:
objectClass
4 “Rec. X. 721 I ISO/IEC (2 9 3 2 7 66) SET OF OBJECT 0.14
90165-2 : 1992 ”: IDENTIFIER
5 “CCITT Rec. X.723 I (2 9 3 5 7 11) GraphicString - 0.14
(1993) j ISO/IEC 10165-
I I
5 : 1993 ”:
I I I I
puosyswrw
F.4.1.3 The EWMA Metric Monitor managed object
Table F.3 - eWMAMetricMonitor Attribute support
Set to
Replace Add Remove
Set by create Get
default
Index Attribute template lab
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.