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
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)
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
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.
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:
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.
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)
Page 60
Add the following annexes after Annex D.
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 .
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.
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
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
IS0 7776 support
0.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 th
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.