ISO/IEC 10747:1994/Amd 1:1996

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

• Status: Published
• Publication Date: 10-Jul-1996
• ICS: 35.100.30 - Network layer
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6/WG 7 - Network, transport and future network
• Current Stage: 6060 - International Standard published
• Start Date: 11-Jul-1996
• Completion Date: 30-Oct-2025

Relations

• Amends: ISO/IEC 10747:1994 - 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
• Effective Date: 06-Jun-2022
• Child: ISO/IEC 10747:1994 - 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
• Effective Date: 15-Apr-2008

Overview

ISO/IEC 10747:1994/Amd 1:1996 is an amendment to the ISO/IEC 10747 International Standard that governs the Protocol for exchange of inter-domain routeing information among intermediate systems to support forwarding of ISO 8473 PDUs. Amendment 1 adds formal Implementation Conformance Statement (ICS) proformas - structured templates suppliers must complete to declare and prove conformance for management information and related OSI management roles.

Key topics and requirements

• Scope of the amendment: introduces normative annexes (Annexes L, M, N and O) that provide proformas for management conformance statements:
  • MCS (Management Conformance Summary) - Annex L
  • MICS (Management Information Conformance Statement) - Annex M
  • MOCS (Managed Object Conformance Statement) - Annex N
  • MRCS (Managed Relationship Conformance Statement) - Annex O
• Conformance structure:
  • Conformance is split into protocol implementation (subclause 12.1) and management information implementation (subclause 12.2). These are independent.
  • Static conformance: supplier must declare manager and/or agent role support and meet minimum requirements for those roles.
  • Dynamic conformance: implementations claiming dynamic conformance must support specified procedures and semantic elements for items claimed.
• Role-specific requirements:
  • Manager role: must implement at least one management operation, notification or action on the managed objects specified by the standard (tables referenced in Annex L).
  • Agent role: must support one or more instances of the IDRP config managed object and the Adjacent BIS managed object and at least one name binding per supported managed object.
• Proforma rules: Any MCS/MICS/MOCS/MRCS must be technically identical to the proformas in the annexes - preserving table numbering and index items (pagination/headers may differ).
• Technical references:
  • ASN.1 / BER transfer syntax required for referenced abstract data types: joint-iso-ccitt asn1(1) basicEncoding(1) (ISO/IEC 8825).
  • Conformance testing and ICS guidance reference ISO/IEC 9646 series and ITU-T/ISO guidance (X.724 / ISO/IEC 10165-6, X.291, X.296).

Applications and who uses it

• Network equipment vendors implementing inter-domain routing protocols for OSI-based networks (IDRP / ISO 8473).
• Software developers building protocol stacks, management agents or network management systems that must declare conformance.
• Test labs and certification bodies performing conformance testing and interoperability assessments.
• Network architects and operations teams who need precise conformance documentation for procurement, integration and compliance.

Related standards (brief)

• ISO/IEC 8825 (ASN.1 / BER)
• ISO/IEC 9646 series (conformance testing methodology)
• ITU-T Rec. X.724 / ISO/IEC 10165-6 (ICS proforma completion guidance)
• ISO 8473 (connectionless-mode network protocol supported by IDRP)

Keywords: ISO/IEC 10747, IDRP, ISO 8473, inter-domain routing, implementation conformance statement, MCS, MICS, ASN.1, BER, OSI management, conformance testing.

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 Standards
summarized in the following tables. For each International Standard that the supplier of the implementation claims

ISO/IEC 10747 : 19941Amd. 1 : 1996(E)
OISOAEC
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 L.5, L.6, and L.7, 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 L.5 - MOCS support summary
Index Identification of the Table numbers of Description Constraints and Status Support Table numbers of Additional
document that includes the MOCS proforma values MOCS
information
MOCS proforma
-
1 “ISO/IEC 10747” Table N.l - N.7 idrpconfig m
2 “ISO/IEC 10747” Table N.8 - N. 13 m
adjacentBlS
c3
3 “ISO/IEC 10737 ” Table F.44 - F.47 communicationlnformation -
Record
c3
4 “ISO/IEC 10164-4” Table C. 1 - C.4 alarmRecord
c3: if L.4/la then m else -
Table L.6 - MRCS support summary
Constraints and values Status Support Table numbers ofAdditional
Index Identification of the Table numbers Description
MRCS
document that includes the of MRCS
information
MRCS proforma proforma
idrpconfig-networkEntity m
1 “lSO/IEC 10747” Table 0.1 /I
m
2 “ISO/IEC 10747” Table 0.112 adjacentBlS-idrpconfig
-
3 “ISO/IEC 10164-6 ” Table D. l/l logRecord-log c4
c4: if L.4/la then o else -
Table L.7 - MICS support summary
Additional
Index Identification of the Table numbers Description Constraints and Status support Table numbers of
information
document that includes of MICS values MICS
the MICS proforma proforma
‘I I SO/I EC 10747” Table M.l to management C5
M.3 operations
“ISO/IEC 10747” Table M.4 notifications c6
c7
3 ” ISO/I EC 10747” Table M.5 actions
c5: if L.2/la then m else -
c6: if L.2/2a or L.2/3a then m else -
c7: if L.2/4a or L.2/5a or L.2/6a or L.2/7a then m else -

ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
OISOLIIT
Annex M
(normative)
1)
roform a
MICS p
M.l 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.
M.2
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 / ISO/IEC 101656, In addition to the general guidance given in ITU-T Rec. X.724 1 ISO/IEC 10165-6. The
supplier of the implementation shall state which items are supported in tables below and if necessary, provide additional
information.
M.3 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 L. 1.3.
M.4
Statement of conformance to the management information
M.4.1 Attributes
The supplier 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.
intended purpose, and may tirther publish
I’ Users of this International Standard may freely reproduce the PICS proforma in this Annex so that it can be used for its
the completed PICS.
ISOIIEC 10747 : 1994/Amd. 1 : 1996(E)
oIsoAEc
M.4. 1.1 IDRP config managed object
ribute suaoort
Table M.l - idrpconfig Att
- ----- --t-I--- -
Get Replace Add Remove Set to
Set by
create
default
I I
Stat Supp Stat Supp Stat Supp Stat Supp Stat Supp Stat Supp Additional
Index Attribute template label Value of object Constraints and
identifier for values us oft us Ott us oft us oft us oft us
Ort information
attribute
1 “Rec. X.721 j ISO/IEC (2 9 3 2 7 50) SET OF
cl 0.2
ObjectClass
101652 1992”:
allomorphs
authenticationTypeCode (2 13 0 3 7 1) ENUMERATED cl 0.2
capacity (2 13 0 3 7 7) INTEGER - 0.2
externalBlSNeighbor (2 13 0 3 7 9) SET OF OCTET cl 0.2 0.2
STRING
holdTime (2 13 0 3 7 IO} INTEGER - 0.2
6 idrpconfig ID
(2 13 0 3 7 50) OCTET STRING cl 0.2
7 internalBlS
(2 13037 12) SETOFOCTET cl 0.2 0.2
STRING
internalsystems (2 13 0 3 7 13) SEQUENCE cl
0.2 0.2
intralS (2 13037 14)
SETOFOCTET cl 0.2 0.2
STRING
IocE-pense (2 13 0 3 7 24) INTEGER
- 0.2
IocalRDl (2 13 0 3 7 22) OCTET STRING
cl 0.2 0.2
IocalSNPA (2 13 0 3 7 23) SET OF SET OF
cl 0.2 0.2
OCTET STR I N‘G
maxCPUOverloadTimer (2 13 0 3 7 25)
SEQUENCE - 0.2
maxPDULocal
(21303726) INTEGER - 0.2
maxRIBIntegrityCheck
(2 13 0 3 7 28) INTEGER - 0.2
maxRIBIntegrityTimer
(2 13 0 3 7 29) SEQUENCE - 0.2
minRDOriginationTimer
(2 13 0 3 7 30) SEQUENCE - 0.2
multiExit
(2 13 0 3 7 32) BOOLEAN Cl 0.2 0.2
“Rec. -.721 j ISO/IEC (2 9 3 2 7 63) OBJECT cl 0.2
10165-2 : 1992”. IDENTIFIER
nameBinding
“Rec. -.721 j ISO/IEC (2 9 3 2 7 65) ObjectClass
cl 0.2
10165-2 : 1992”:
objectClass
“Rec. -.721 j ISO/IEC
(2 9 3 2 7 66) SET OF OBJECT cl 0.2
IDENTIFIER
10165-2 : 1992”:
packages
priority (2 1303734) INTEGER - 0.2
rdLRE
(2 1303736) INTEGER - 0.2
rdTransitDelay
(2 13 0 3 7 37) INTEGER - 0.2
rdcconfig
(2 1303735) SETOF cl 0.2 0.2
SEQUENCE
retransmissionTime (2 13 0 3 7 38) INTEGER - 0.2
ri bAttsSet (2 13 0 3 7 39) SEQUENCE - 0.2
routeserver (2 13 0 3 7 40) BOOLEAN cl 0.2 0.2
version (2 13 0 3 7 46) INTEGER - 0.2
cl: if M.4/la then 0.2 else -
ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
OISOBEC
M.4.1.2 Adjacent BIS managed object
Table M.2 - adjacentBlS Attribute support
1 sti; 1 Get 1 Replace 1 Add- I Remove 1 :zazt (
ttri bute template label
“Rec. X.721 I ISO/IEC (2 9 3 2 7 50) SET OF 0.2
10165-2 : 1992”: ObjectClass
allomorphs
bisNegotiatedVersion (2 13 0 3 7 2) INTEGER - 0.2
bisNet (2 130373) OCTETSTRING - 0.2
bisPeerSNPAs (2 130374) SETOFSETOF - 0.2
OCTET STRING
5 bisRDC (2 130375) SETOFOCTET - 0.2 0.2 0.2
STRING
6 bisRDl (2 130376) OCTETSTRING - 0.2 0.2 0.2
7 closeWaitDelayTimer (2 13 0 3 7 8) SEQUENCE - 0.2
8 holdTimer (2 13 0 3 7 11) SEQUENCE - 0.2
9 keepAliveTimer (2 13 0 3 7 16) SEQUENCE - 0.2
10 keepAIivesSinceLastUpdate (2 13 0 3 7 15) INTEGER 0.2
11 IastAckRecv (2 13037 17) INTEGER - 0.2
12 IastAckSent (2 13 0 3 7 18) INTEGER - 0.2
I
13 IastPriorSeqNo (2 13 0 3 7 49) INTEGER - 0.2 0.2
14 IastSeqNoRecv (2 13 0 3 7 19) INTEGER - 0.2
15 IastSeqNoSent (2 13 0 3 7 20) INTEGER - 0.2
16 IistenForOPEN (2 1303721) BOOLEAN - 0.2
17 maxPDUPeer (2 13 0 3 7 27) INTEGER - 0.2
18 minRouteAdvertisementlnte (2 13 0 3 7 48) INTEGER 0.2
rval
minRouteAdvertisementTim (2 13 0 3 7 31) SEQUENCE - 0.2
er
“Rec. X.721 I ISO/IEC (2 9 3 2 7 63) OBJECT - 0.2
10165-2 : 1992”: IDENTIFIER
nameBinding
21 “Rec. X.721 I ISO/IEC (2 9 3 2 7 65) ObjectClass - 0.2
10165-2 : 1992”:
objectClass
22 OutstandingPDUs (2 13 0 3 7 33) INTEGER - 0.2
23 “Rec. X.721 I ISO/IEC (2 9 3 2 7 66) SET OF OBJECT - 0.2
10165-2 : 1992”: IDENTIFIER
packages
24 state (2 13 0 3 7 41) ENUMERATED - 0.2
25 totalBlSPDUsln (2 13 0 3 7 42) INTEGER - 0.2
26 totalBlSPDUsOut (2 1303743) INTEGER - 0.2
27 updatesln (2 13 0 3 7 44) INTEGER - 0.2
28 updatesout (2 1303745) INTEGER - 0.2
M.4.2 Attribute groups
The supplier of a manager role implementation that claims to support management operations on the attribute groups
specified in this International Standard shall import a copy of the following tables and complete them.
ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
OISOAEC
M.4.2.1 Adjacent BIS managed object
Table M.3 - adjacentBE Attribute group support
Get Set to
I
default
Status Support Status Support Additional
Value of object Constraints and values
Index Attribute group template
dentifier for
label information
attribute group
0.2
“CCITT Rec. X.723 (1993) 1 [2 9 3 5 8 0) keepAlivesSinceLastUpdate
lSO/IEC 101655 : 1993”:
totalBlSPDUsln
counters
totaIBISPDUsOut
updatesln
updatesout
0.2
2 “Rec. X.721 j ISO/IEC (29328 I} state
101652 : 1992”:
state .
T
M.4.3 Create and delete management operations
The supplier of a manager role implementation that claims to support the create or delete management operations on the
managed objects specified in this International Standard shall import a copy of the following tables and complete them.
M.4.3.1 IDRP config managed object
Table M.4 - Create and delete support
Status support Additional information
Operation Constraints and values
Index
0.2
idrpconfig MO
1 Create support
-
-
Create with reference object
1.1
0.2
Delete support idrpconfig MO
M.4.3 Notifications
specified in this International
The supplier of a manager role implementation that claims to support the notifications
Standard shall import a copy of this table and complete it.
Table MS - Notification support
C
L support
r
C;;z-aints and Stat $ppAdditional
,dditional Subindex Notification field Value of
‘alue of Zonstraint :onf
Wkzation type template
object V us
z name label
bject I and met lo information
iformation
identifier of
lentifier for falues n led
attribute
otification
type
/Pe
associated
with field
Information c2
1.1 Alarmlnfo
Rec. X.721 1 ISO/IEC
Syntax
0165-2 : 1992”:
SEQUENCE
:ommunicationsAlarm
c:m
probablecause
1.1.1
1 28e 3 2 7 CHocE
a
OBJECT c:m
globalValue
1.1.1.1
IDENTIFIER
I
c:m
INTEGER
1.1.1.2 localValue
1.1.2 specificProblems 1 27p 3 2 7 SET OF CHOICE c:m
c:m
OBJECT
1.1.2.1 OBJECT
IDENTIFIER
IDENTIFIER
INTEGER c:m
1.1.2.2 INTEGER
I t
I
1.1.3 perceivedseverity \ 27p
3 2 7 ENUMERATED c:m
1.1.4 backedUpStatus
\ :P 3 2 7 BooLEAN c:m
1.1.5 backUpObject (2 9
3 2 7 Object Instance c:m
1.1.6 trendlndication k 20,”
3 2 7 ENUMERATED c:m
0lS0m
ISO/IEC 10747 : 1994/Amd. 1 : 1996(E)
Table MS (concluded) - Notification support
1upport
Subindex Notification field ‘Value of C;;z-aints and Stat f;ppAdditional
:onl ,dditional
jex Mikation type template ‘alue of :onstraint
g name label object V us
1 bject and net
information
iformation
identifier of
led
Ientifier for alues
attribute
otification
type
fw
associated
with field
;; 3 2 7 SEQUENCE c:m
1.1.7 thresholdlnfo
Attributeld c:m
1.1.7.1 triggeredThreshold -
c:m
1.1.7.2 observedValue CHOICE
c:m
1.1.7.2.1 integer INTEGER
1.1.7.2.2 real REAL c:m
1.1.7.3 thresholdLevel - CHOICE c:m
I I
...