ISO/IEC 10747:1994/Amd 1:1996
(Amendment)Information technology — Telecommunications and information exchange between systems — Protocol for exchange of inter-domain routeing information among intermediate systems to support forwarding of ISO 8473 PDUs — Amendment 1: Implementation conformance statement proformas
Information technology — Telecommunications and information exchange between systems — Protocol for exchange of inter-domain routeing information among intermediate systems to support forwarding of ISO 8473 PDUs — Amendment 1: Implementation conformance statement proformas
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Protocole pour échange d'information inter-domaine de routage parmi les systèmes intermédiaires supportant la transmission de PDUs de l'ISO 8473 — Amendement 1: Proformes de déclaration de conformité de mise en oeuvre
General Information
Relations
Standards Content (Sample)
INTERNATIONAL
ISO/IEC
STANDARD
First edition
1994-I o-01
AMENDMENT 1
1996-07-I 5
Information technology -
Telecommunications and information
exchange between systems - Protocol for
exchange of inter-domain routeing
information among intermediate systems to
support forwarding of IS0 8473 PDUs
AMENDMENT 1:
Implementation conformance statement proformas
Technologies de I’informa tion - T&communica Cons et &change
d ‘informa tion en tre sys t&mes - Pro tocole pour &change d ‘informa Con
inter-domaine de routage parmi /es systemes in termkdiaires supportant la
transmission de PDlJs de I’ISO 8473
AMENDEMENT 1: Proformes de dklaration de conformit de mise en
cwvre
Reference number
ISO/I EC 10747: 1994/Amd. 1: 1996(E)
ISO/IEC 10747 : 1994/Amd. 1 : 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 1 to International Standard ISO/IEC 10747 : 1994 was prepared by Joint
Technical Committee ISO/IEC JTC 1, Inforz?zation technology, Subcommittee SC 6,
Telecommunications and information exchange between systems.
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 10747 : 1994/Amd. 1 : 1996(E)
Information technology - Telecommunications and information exchange between systems -
Protocol for exchange of inter-domain routeing information among intermediate systems to
support forwarding of IS0 8473 PDUs
AMENDMENT 1:
Implementation conformance statement proformas
Page 1
“S’cope “.
Add the. following as the last paragraph of Clause I
Annexes L, M, N and 0, which are integral parts of this International Standard provide ICS proformas associated with IDRP
management information.
Add the fi,llowing refirences to clause 2 “Normative References”.
ISOLEC 8825: 1990, Information technologv - Open Systems Interconnection - Specification of Basic
Encoding Rules jtir Abstract Syntax Notation tiOne (ASN. I).
Open Systems Interconnection - Conformance testing
ISOLEC 9646- 1: 1994, Information technologv -
e
methodology and*framework - Part I: General concepts.
ISO/IEC 9646-2: 1994, Infornzation technologv - Open Systems Interconnection - Conformance testing
methodology and,framework - Part 2: Abstract Tkst Suite specification.
NOTE - ISOAEC 9646-l : 1994 and ISO/IEC 9646-2: 1994 supersede ISOIIEC 9646-l : 199 1 and ISOIIEC 9646-2: 199 1
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.
ISOAEC 9646- 1: 199 1, Information technology - Open Systems Interconnection - Conformance testing
,
methodoloa and framework - Part I: General concepts.
ISOIEC 9646-2: 199 1, Information technology - Open Systems Ilzterconnection - Conformance testing
methodoloa undfrumework - Part 2: Abstract test suite spec$kation.
Open Svstems Interconnection - Conformance testing
ISO/IEC 9646-7: 1995, Information technologv - II
w
methodology and framework - Part 7: Implementation Conformance Statements.
Structure of management
Open Systems Interconnection -
ISO/IEC 10 165-6: 1994, Information technology -
ouidelines for implementation conformunce statement proformas associated
information.* Requirements and b
with OSI management.
ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
OISObEC
Page 5
Add the following abbreviations to subclause 4.3 “Other Abbreviations”.
management conformance summary
MCS
MICS management information conformance statement
MOCS managed object conformance statement
MRCS managed relationship conformance statement
Page 74
Add the following after the title “12 Conformance “.
12.1 Conformance for protocol implementation
This subclause specifies the conformance for protocol implementation of IDRP. The supplier of implementation for protocol
implementation shall support the following specification.
NOTE - The conformance for protocol implementation is independent of the conformance for management information
implementation specified in subclause 12.2.
“12.2 “, “12.2-l “, “12.2.2 “, “12.2.3” and “12.2.4” with “12.1.1”, “12.1.2”, “12.1.2.1”,
RepEace title number of “12. I “,
“I 2.1.2.3 ” and “12.1.2.4 “, respectively.
“12.1.2.2”,
Delete “t) ” of subclause 12.1.1 “Static conformance for all BLW’.
Add the following afler subclause 12.1.2.4.4.
12.2 Conformance for management information implementation
implementation of IDRI? The supplier of
This subclause specifies the conformance for management information
implementation for management information implementation shall support the following specification.
NOTE - The conformance for management information implementation is independent of the conformance for protocol
implementation specified in subclause 12.1.
12.2.1 Static conformance
The implementation shall conform to the requirements of this 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 L. 1 of this International Standard.
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
notifications and actions are identified in
conformance requirements in the manager role for those management operations,
Table L.2 and further tables referenced by Annex L.
If a claim of conformance is made for support in the agent role, the implementation shall support one or more instances of
the IDRP config managed object class and the Adjacent BIS managed object class identified in Table L.3 of this International
Standard and further tables referenced by Annex L.
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 L.6 of this International Standard for each supported managed object.
OISOAEC ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
The implementation shall support the transfer syntax derived from the encoding rules specified in CCITT Rec. X.209 1
ISO/IEC 8825 named tjoint-iso-ccitt asnl( 1) basicEncoding( I)} for the abstract data types referenced by the definitions for
which support is claimed.
12.2.2 Dynamic conformance
International Standard shall support the elements of procedure and definitions
Implementations claiming to conform to this
for which support is claimed.
of semantics corresponding to the definitions
12.2.2.1 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 L, M, N, and 0 preserving table numbering and the
index numbers of items, and differing only in pagination and page headers.
The supplier of an implementation which is claimed to conform to this International Standard shall complete a copy of the
management conformance summary (MCS) provided in Annex L as part of the conformance requirements together with any
other ICS proformas referenced as applicable from that MCS. Any MCS, MICS, MOCS and MEKS 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
1016596;
-
include the information necessary to uniquely identify both the supplier and the implementation.
An implementation claming conformance to this International Standard in the agent role as a managed implementation
shall:
-
support the IDRP config MO and the Adjacent BIS MO.
Page 109
Add the following Annexes after Annex K.
ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
OISOLEC
Annex L
(normative)
MCS proform’ )
Ll . Introduction
L.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.
L.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 boxes provided. Specific instruction is
provided in the text which table.
precedes each
L.l.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 sarne table;
2 - ‘0’ may be suffixed by ‘N (where N is a unique number) for mutually exclusive or selectable options among a set of status
values. Support of at least one of the choices (from the items with the same values of N) is required.
For all annexes of this 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 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.
* ) Instructions for completing the MCS proforma are specified in ITU-T Rec.X.724 1 ISOLIEC 10166 .
OISOAEC ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
L.2 Identification of the implementation
Date of statement
L.2.1
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
L.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.
L.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.
L.3 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
L.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.
ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
OISOAEC
L.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the identified
International Standard, in the box below.
L.4 Management conformance summary
The supplier of implementation shall state the capabilities and features supported and provide summary of conformance
claims to International Standards using the tables in this annex.
The supplier of the implementation shall specify the roles that are supported, in Table L. 1
Table L.l - Roles
1 Roles supported
1 index Status 1 Additional information
I Support I I
i -i-Manager role support 0.1
I I I -1
I Agent role support 0.1
I 2 I I I I
The supplier of the implementation shall specify support for management information in the manager role, in Table L.2
Table L.2 - Manager role minimum conformance requirement
I Index I Item Status I Additional information
I Support I I
1 Operations on managed objects Cl
I I I I I I
Cl
I 2 I Communications alarm notification for IDRP config managed object
I I I I
cl
3 Communications information for IDRP config managed object
I I ]
I
cl
Activate action for IDRP config managed object
I I I I I
cl
Deactivate action for IDRP config managed object
I ! 1
I
Cl
I Activate action for Adjacent BIS managed object
I I I I
1 Deactivate action for Adiacent BIS managed obiect I cl
I I I
cl: if L.l/la then 0.2 else -
The supplier of the implementation shall specify support for management information in the agent role, in Table D.4
Table L.3 - Agent role minimum conformance requirement
Index Item Status support Additional information
1 m
IDRP config managed object
m
2 Adjacent BIS managed object
Table L.4 - Logging of event records
Additional information
Index Status support
1 Does the implementation support logging of event records in agent role? c2
c2: if L. 1/2a then o else -
NOTE - Conformance to this International Standard does not require conformance to CCITT Rec. X.735 1 ISO/IEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the International Stan
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.