ISO/IEC 10589:1992/Amd 1:1996
(Amendment)Information technology — Telecommunications and information exchange between systems — Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473) — Amendment 1: Implementation conformance statement proformas
Information technology — Telecommunications and information exchange between systems — Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473) — Amendment 1: Implementation conformance statement proformas
Technologies de l'information — Communication de données et échange d'informations entre systèmes — Protocole intra-domaine de routage d'un système intermédiaire à un système intermédiaire à utiliser conjointement avec le protocole fournissant le service de réseau en mode sans connexion (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
1992-06-15
AMENDMENT 1
1996-07-15
Information technology -
Telecommunications and information
exchange between systems - Intermediate
system to Intermediate system intra-domain
routeing information exchange protocol for
use in conjunction with the protocol for
providing the connectionless-mode Network
Service (IS0 8473)
AMENDMENT 1:
Implementation conformance statement proformas
Technologies de I’informa tion -
T6l&ommunica tjons et &change
d ’information entre systdmes -
Protocole intra-domaine de routage d ’un
syst&me intermgdiaire 2 un systeme intermkdiaire 9 utiljser conjointement
avec le protocole fournissant le service de r&eau en mode sans
connexion (IS0 84 73)
AMENDEMENT 1: Proformes de dbclaration de conform26 de mise en
owvre
Reference number
&O/l EC 10589: 1992/Amd. 1: 1996(E)
---------------------- Page: 1 ----------------------
ISO/IEC 10589 : 1992/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, ISOKEC 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 10589:1992 was prepared by Joint
Technical Committee ISO/XEC JTC 1, information 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-1211 Geneve 0 Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
OISOAEC ISO/IEC 10589 : 1992/Amd. 1 : 1996(E)
Information technology - Telecommunications and information exchange between systems -
Intermediate system to intermediate system intra-domain routeing information exchange
protocol for use in conjunction with the protocol for providing the connectionless-mode
Network Service (IS0 8473)
AMENDMENT 1:
Implementation conformance statement proformas
Page 1
Add the ,folZowing as the last paragraph of Clause 1 “Scope “.
International Standard provide ICS proformas associated with intra-
Annexes G, M, I and J, which are integral parts of this
domain routeing protocol management information.
Add the following refirences to clause 2 “Normative references ”.
l[SO/IIEC 8825: 1990, Information technology - Open Systems Interconnection - Specification of Basic
Encoding Rules for Abstract Syntax Notation One (ASN. I).
ISO/IEC 9646-1: 1994, In@mation technology - Open Systems Interconnection - Confbrmance testing
- 1
methodologWv and,j?amework - Part I: General concepts.
ISO/IEC 9646-2: 1994, Information technologv - Open Svstems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite spe&?cation.
NOTE - ISO/IEC 9646- 1: 1994 and ISO/IEC 9646-2: 1994 supersede ISOiIEC 9646-l : 199 1 and ISO/IEC 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.
ISO5EC 9646-l : 1991, Information technology - Open Systems Interconnection - Conformance testing
methodology andframework - Part I: General concepts.
technology - open Systems Interconnection - Conformance
ISOJIEX 9646-2: 199 1, Infomzation
2: Abstract test suite specification.
methodology and framework - Part
Open 5ystems Interconnection - Conjbrmance testing
ISO/IEC 9646-7: 1995, Information technology -
.
methodology and. fkamework - Part 7: Implementation Conformance Statements.
ISO/IEC 10165-6: 1994, Information technology - Open Systenzs Interconnection - Structure of nzanagenzent
L ctatement proformas associated
information.- Requirements and guidelines for implementation corzformance
with 05 ’1 management.
---------------------- Page: 3 ----------------------
ISO/IEC 10589 : 1992/Amd. 1 : 1996(E) OISOBZC
Page 4
Add the following abbreviations to subclause 4.4 “Miscellaneous ”:
management conformance summary
MCS
MICS management information conformance statement
MOCS managed object conformance statement
MRCS managed relationship conformance statement
Page 101
.
Add the following after the title “12 Conformance “.
12.1 Conformance for protocol implementation
This subclause specifies the conformance for protocol implementation of intra-domain routeing protocol. 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.
Replace title number of “12.1 ”, “12.1.1 ))) “12.1.2 ”, “12.1.3 ”, “12.1.4 ”, “12.2 ”, “12.2.1 “, “12.2.2 ”, “122.2. I ”, “12.23 “,
“12.2.4 ”, “12.2;4.1 ”, “12.2.4.2 ”, “12.2.4.3” and “12.2.4.4” with “12.1. I “, “12.1.1.1 ”, “12.1.1.2 ”, “12.1.1.3 ”, “12.1.1.4 “,
“12.1.2 ”, “12.1.2.1))) “12.1.2.2 ”, “12.1.2.2.1 ”, “12.1.2.3 ”, “12.1.2.4 ”, “12.1.2.4.1 ”, “12.1.2.4.2 ”, “12.1.2.4.3” and
“12.1.2.4.4 “, respectively.
Delete ‘i)) ” of subclause 12.1.1.2 ”Static conformance requirements for all ~,!i ’$ ‘and , renanle ‘i) ” with ‘j/) “.
Add the following aper subclause 12.1.2.4.4.
12.2 Conformance for management information implementation
This subclause specifies the conformance for management information implementation of intra-domain routeing protocol.
The supplier of 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 G. 1 of this International Standard.
the implementation shall support at least one
If a claim of conformance is made for support in the manager role,
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 and notifications and actions are identified
in Table G.3 and further tables referenced by Annex G.
If a claim of conformance is made for support in the agent role, the implementation shall support one or more instances of
the destination managed object class, the destination area manageci object, the
the adjacency managed object class,
destination system managed object class, the reachable address managed object class and the virtual adjacency managed
object class identified in Table G.4 of this International Standard and further tables referenced by Annex G.
2
---------------------- Page: 4 ----------------------
OISOLEC ISO/IEC 10589 : 1992/Amd. 1 : 1996(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 G.8 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 tjoint-iso-ccitt asnl( 1) basicEncoding( 1)) 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 procedure and definitions
Implementations claiming to conform to this of
for which support is claimed.
of semantics corresponding to the definitions
Management implementation conformance statement requirements
12.2.3
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 G, II, I, and J 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 G 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 ) ISO/IEC
10165-6;
-
include the information necessary to uniquely identify both the supplier and the implementation.
12.2.4 IS level specific conformance requirements
The supplier of an implementation which is claimed to conform to this International Standard shall support at least level 1 IS
identified in Table G.2 of this International Standard.
12.2.4.1 Conformance to level 1 ISs
An implementation claming conformance to the level 1 IS of this International Standard in the agent role as a managed
implementation shall support the adjacency MO and the destination system MO.
12.2.4.2 Conformance to level 2 ISs
An implementation claming conformance to the level 2 IS of this International Standard in the agent role as a managed
system MO, the destination area MO, the virtual
implementation shall support the adjacency MO, the destination
adjacencyM0 and the reachable address MO.
Page 142
Add the following Annexes after Annex F.
---------------------- Page: 5 ----------------------
ISO/IEC 10589 : 1992/Amd. 1 : 1996(E) OISOAIX
Annex G
(normative)
Gl . Introduction
G.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.
G.l.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 precedes each table.
G. 1.3 Symbols, abbreviations and terms
For all remaining 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;
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 remaining annexes of this International Standard, the following common notations, defined in CCITT Rec. X.291 I
ISO/IEC 9646-2 and IT&T Rec. X.296 I 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).
1
) 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 ISO/IEC 10165-6 .
4
---------------------- Page: 6 ----------------------
ISO/IEC 10589 : 1992/Amd. 1 : 1996(E)
OISOLEC
6.2 Identification of the implementation
G.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
G.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.
G.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.
G.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
G.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.
---------------------- Page: 7 ----------------------
ISO/IEC 10589 : 1992/Amd. 1 : 1996(E) OISOBEC
G.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.
G.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 G. 1
Table G.1 - Roles
Status support
Index Roles supported Additional information
1 Manager role support 0.1
2 Agent role SUDDOI~ 0.1
The supplier of the implementation shall specifji the level of IS that are supported, in Table G.2
Table G.2 - Level of IS
Index Status support Additional information
Level supported
1 m
Level 1 IS support
0
I 2 I Level 2 IS SUPPOrt I I I I
The supplier of the implementation shall specie support for management information in the manager role, in Table G. 3.
Table G.3 - Manager role minimum conformance requirement
Index Item I Status I Support I Additional information
I
1 Operations on managed objects cl
1
!
I
Activate action for reachableAddress cl
2
cl
3 Deactivate action reachableAddress
cl
4 State change notification for Adjacency managed object
1
cl
5 Object creation notification for reachableAddress managed
object
cl
6 Object deletion notification for reachableAddress managed
object
cl
7 State change notification for reachableAddress managed object 1
I I I
cl: ifG.l/la then 0.2 else -
The supplier of the implementation shall specify support for management information in the agent role, in Table G.4.
6
---------------------- Page: 8 ----------------------
OISOEC ISO/IEC 10589 : 1992/Amd. 1 : 1996(E)
Table G.4 - Agent role minimum conformance requirement
1 Status 1 Support I Additional information
1 Id n ex em
I It I
m
adjacency managed object
! ! !
I
I destinationArea managed obiect c2 I
I I I
destinationsystem managed object m
! ! !
1
I reachableAddress managed obiect
5 virtualAdjacency managed object
c2: if G.2/2a then m else -
notification, attribute or action table
NOTE - The Table reference column in the above table is the managed object class ,
reference of the MOCS supplied by the supplier of the managed object which claims to import the notification or attribute from this
International Standard.
Table G.5 - Logging of event records
1 Status 1 Support 1 Additional information
Index
c3
I Does the implementation suc>r>ort looaina of event records in agent role? I I I I
c3: if G. 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
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 G.6, G.7, and G.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 G.6 - MOCS support summary
r
Index Identification of the Table numbers of Description Constraints and Status Supbort Table numbers of Additional
document that includes the MOCS proforma values MOCS
information
MOCS proforma
-
1 “ISO/IEC 10589” Table I.1 - 1.6 adjacency m
Table 1.7 - 1.10 virtualAdjacency c4
2 ” ISO/I EC 10589”
-
3 “ISO/IEC 10589” Table I. 11 - I. 14 destinationsystem m
-
4 “ISO/IEC 10589” Table l.15- 1.18 destinationArea c5
reachableAddress c6
5 “ISO/IEC 10589” Table I. 19- 1.24
c7
6 “ISO/IEC 10164-l” Table C.l - C.4 objectCreationRecord
-
7 “ISO/IEC 10164-l” Table C.5 - C.8 objectDeletionRecord c7
-
Table C. 9 - C. 12 StateChangeRecord c8
c4: if G.4/5a then m else -
c5 : if G.4/2a then m else -
6: if G.4/4a then m else -
c7: if G.4/4a and GS/la then m else -
c8: if GS/la then m else -
---------------------- Page: 9 ----------------------
ISO/IEC 10589 : 19921Amd. 1 : 1996(E) OISOBEC
Table G.7 - MRCS support summary
I
Table numbers Description Constraints and values Status Support Table numbers of Additional
Index Identification of the
MRCS
document that includes the of MRCS
information
MRCS proforma proforma
-
adjacency-linkage 0.3
1 “I SO/i EC 10589” Table J. l/l
-
adjacency-linkage- 0.3
2 “ISO/IEC 10589” Table J. l/2
management
J. l/3 VirtualAdjacency-cLNS c9
3 “ISO/IEC 10589” Table
-
4 “ISO/IEC 10589” Table J. l/4 destinationsystem-cLNS m
-
Table J. l/5 destinationArea-cLNS cl0
5 “ISO/IEC 10589”
-
reachableAddress-linkage- cl1
6 ” ISOA EC 10589” Table J. l/6
imported
reachableAddress-linkage- Cl1
7 “ISO/IEC 10589” Table J.l/7
management
-
“ISO/IEC 101646” logRecord-log cl2
8 Table D. 1 /I
.
c9: if G.6/2a then m else -
~10: ifG.6/4a then m else -
cl 1: if G.6/5a then 0.4 else -
~12: G.5/la then o else -
Table G.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 M ICS proforma proforma
-
1 “ISO/IEC 10589” Table H.l to management cl3
H.7 operations
2 “lSO/IEC 10589” Table H.8 notifications cl4
-
actions cl5
3 “ISO/IEC 10589” Table H.9
I
~13: ifG.3/la then m else -
~14: if G.3/4a or G.3/5a or G.3/6a or G.3/7a then m else -
~15: if G.3/2a or G.3/3a then m else -
8
---------------------- Page: 10 ----------------------
ISO/IEC lo589 : 1992/Amd. 1 : 1996(E)
OISOLEC
Annex H
(normative)
1)
MICS proforma
H.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.
Instructions for completing the MICS proforma to produce a MICS
H.2
The MICS proforma contained in this annex is comprised of information in tabular form, in accordance with ITU-T
Rec. X.724 ) ISO/IEC 10165-6. In addition to the general guidance given in ITU-T Rec. X.724 1 ISO/IEC 10165-6, the
Additional information column shall be used to identify the object classes for which the management operations are
supported. The supplier of the implementation shall state which items are supported in tables below and if necessary, provide
additional information.
Symbols, abbreviations and terms
H.3
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 G. 1.3.
H.4 Statement of conformance to the management information
H.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.
H.4.1.1 Adjacency managed object
Table H.4- adjacency managed object Attribute support
Remove Set to
Get Replace Add
default
Stat Supp Stat SuppStat Supp Stat S;upp Stat S;u$pStatu Sup Additional
Index Attribute template label ‘Value of object Constraints and
us ort us oft us ort us us S
identifier for values
port information
cd-tri ht Itn
c4Ll.l I"ULb
I
1 “RPC x 77.1 !3 ISO/IEC (2 9 3 2 7 50) SET OF cl 0.5
I 10165-2 I .-w. I . . a : -
19 2 ”: ObjectClass
=rllnmnrnhc
Ull ”, I IV. y’” IV
I wnp Y 731 I I.cm/lFr. 113 CI ? 7 7 631 IOBJECT
1 cl I I 0.5 I I - I I - I I - I I - I I
---_-
I ’(ji&:\i’:Ll ’g&j?i~ “Lw ” - - - ’ -” IDENTIFIER ’
nameBinding
“Rec. X.721 1 ISO/IEC (2 9 3 2 7 65) ObjectClass cl
0.5
10165-2 : 1992 ”:
objectClass
“Rec. X.721 !3 ISO/IEC (2 9 3 2
7 66) SET OF OBJECT ~1 0.5
IDENTIFIER
I packages 10165-2 : 19 2 ”: 1
5 “ISOIEC 10589 ”: (2 13 0 1 7 77 } GraphicString
-Ai- ,,,,.,I A I IclI lo.5l I - I I - I I - I I - I I
I
dUJdC;~llLylU
(2 13 0 1 7 78) - 0.5
l.SeS.AdjacencySt
6 adjacencystate ” ISOA EC 10589 ”:
7 “ISO/IEC 10589 ”: (2 13 0
1 7 79) ISIS.ANPAAddres - 0.5
S
neighbourSNPAAddress
‘) Users of this International Standard may freely reproduce the PICS proforma in this Annex so that it can be used for its intended purpose, and may fkther publish
the completed PICS.
9
---------------------- Page: 11 ----------------------
OISOAEC
ISO/IEC 10589 : 1992/Amd. 1 : 1996(E)
Table H.1 (concluded) - adjacency managed object Attribute support
[ Set by 1 Get 1 Replace 1 Add 1 Remove 1 Set to 1
create
default
Stat SuppStat SuppStat SuppStat SuppStat SuppStatu Sup Additional
Index Attribute template label
‘Value of object C;;zFints and
us of-t us olt us or-t us art us of-t s
identifier for v
port information
. . .attri bute .
I
- 0.5
8 “ISO/IEC 10589 ”: (2 13 0 17 80) ENUMERATED
nninhhn, trC\/c+nmT\/nfi
1 I lGi$jl IUUUI uy3LGI I I I y p-G ,
I I I I 1 I I I I I I I 1 I
I-l IO.51 I-1 I-1 I-1 I-1 I
g 1 "ISOIIl=C .--~.-- 10589". .---- 1(2 13 0 1 7 8311SET OF 1
c-
-1OCTETSTRING 1
I nninhhnnr tr.~\/ct~mIrlc I I I I I I I I I I I I I
I
I UL.l~, Ivy”“, VJ “.I, I l,U”
“ISO/IEC 10589 ”: (2 13 0 1 7 82) ISIS.AdjacencyUs
- 0.5
age
adjacencyusage
“ISO/IEC
10589 ”: (2 13 0 1 7 84) ISIS.AreaAddress - 0.5
es
areaAddressesOfNeighbour
“ISO/IEC 10589 ”: (2 130 17 85)timer
0.5
holdingTimer
“ISO/IEC 10589 ”:
(2 13 0 1 7 86) ISIS. Intermediate - 0.5
SystemPnonty
priorityOfNeig h bour
cl: if H.6/la then 0.5 else x
H.4.1.2 Virtual adjacency managed object
Table H.2 - virtualAdjacency Attribute support
Get Replace Add Remove Set to
default
Index Attribute template label Stat Supp Stat Supp Stat Supp Stat Supp Stat Supp Stat Supp Additional
Value of object C~;rFints and
us of-t us of-t us ort us ort us oft us
identifier for v
On information
attribute
0.5
1 “Rec. X.721 1 ISO/IEC (2 9 3 2 7 50) SET OF
10165-2 : 1992 ”: ObjectClass -
allomorphs
0.5
2 “Rec. X.721 ISO/IEC (2 9 3 2 7 63) OBJECT
IDENTIFIER -
10165-2 : 19 !J 2 ”:
nameBinding
Q “Des* Y 731 I ICA/Il=I‘ nhiprtPlacc n5
13 Q ? 3 7 fm
3 ll~i~5~ ,:Ll’9t3’2~vl 1LV
AL ” ” L I VW, --Jcr”c”‘uyu
I I nhier.tClacs I I l--l I I I I I I I I I
I I I
-“J--*-‘--- I III I II I 11 11 1 ’
I
A I “RCW Y731 II.cn/lFr. Irc,s177fm lSFTnf=nR-IFcTI - 1 1 t-m 1 - 1 I I-I I-I 1 1
VYVLV 1 -. -
-I ~~j~s/-\i ‘:‘1199~~v’ IL- ~~ ” - - ’ “J ~~NvTi FIER
packages
5 “ISO/IEC 10589: 1992 ”:
(2 13 0 1 7 88) ISIS.NAddress - 0.5
networkEntityTyitle
6 “ISO/IEC 10589: 1992 ”: (2 13 0
1 7 89) ISIS.PathMetric - 0.5
metric
1
H.4.1.3 Destination system managed object
Table H.3 - destinationsystem Attribute support
Replace Add Remove Set to
Get
default
Stat Supp Stat Supp Stat Supp Stat “,u,p Stat S;gp Stat Supp Additional
Index Attribute template label value of object Co;Eaints and
us ort us oft us ort us us us
identifier for v
Oft information
attribute
1 “Rec. X.72 1 1 ISO/IEC (2 9 3
2 7 50) SET OF - 0.5
10165-2 : 1992 ”: ObjectClass
allomorphs
.
L “Rec. X.721 !3 ISO/IEC (2 9 3 2 7 63)
OBJECT 0.5
10165-2 : 19 2 ”: IDENTIFIER -
nameBinding
9 3 2 7 65) ObjectClass
- 0.5 X
3 “Rec. X.721 ISO/IEC
I I 10165-2 : 19 b 2 ”:
/2 I III
I II 11 11 1 I I
I
objectClass
“Dnn Y 731 I ic2n/ic7 f3 Q 2 3 7 lx1 SFT T\C nR IFCT - (3.5
4 liji~5~/~~l~~~~~I~u AL J cl L I VW, ~~~N\i/Fj/EyRu,-’
packages
I I I I l-*-I I I I I I I I I/
I
II
0.5
- 0.5
5 IS-O/IEC 10589 ”: (2 13 0 1 7 91) ISIS.OutputAdjac
_ _ . _ . _ . .
encies
defaultMetricOutputAd]a
nce
ncies
(2 13 0 1 7 90) ISIS.PathMetric
6 “ISO/IEC 10589 ”:
I I I - I I o.51 I o.5 l l - l l - l l - I I I
defaultMetricPathCost
I
I I I I I I I I I I I I I I
10
---------------------- Page: 12 ----------------------
1992/Amd. 1 : 1996(E)
ISO/IEC 10589 :
OISOAIZC
Table H.3 (concluded) - destinationsystem Attribute support
Get Replace Add Remove Set to
ZaeY
default
’ L L Irr LAL 1n.--- ‘N-L S;$pStat S;$dStat S;$pStat Supp Additional
alue
v
Index Attribute template label
us
us us
identi Oft information
attribL_-
7 “ISO/IEC 10589 ”: (2 13 0 1 7 93) ISIS.OutputAdjac - 0.5 0.5
encies
delay MetricOutputAdjancen
ties
8 “ISO/IEC ? 0589 ”: (2 13 0 1 7 92) ISIS.PathMetric - 0.5 0.5
delay MetricPathCost I
- 0.5 0.5
01 7 97) ISIS.OutputAdjac
9 “ISO/IEC 10589 ”: (2 13
encies
InrmrMcatrirh ttnl rtAdianc~n 1
bI I “I I.IULI Ivvu~yu” .UJU’ ,VIl I
ties
0 “ISO/IEC 10589 ”: (2 43 0 1 7 96) ISIS.PathMetric - 0.5 0.5
1
errorMetricPathCost
1 “ISO/IEC 10589 ”: (2 13 0 1 7 95) ISISOutputAdjac - 0.5 0.5
1
encies
mwmnc~hAdrirf3 ltnl dAdjan
rnyu, I”~,.lrl.I l”Y”.yU” \.
cencies
- 0.5 0.5
(2 13 0 1 7 94) ISIS.PathMetric
12 “ISO/IEC 10589 ”:
1
expenseMetricPathCos1
13 “ISO/IEC 10589 ”: (2 13 0 1 7 88) ISIS.NAddress - 0.5
networkEntotyTitle
L
H.4.1.4 Destination area managed object
Table H.4 - destinationArea Attribute support
1 Set by I Get I Replace I Add I Remove 1 Set to 1
create
default
Stat Supp Stat Supp Stat Supp Stat Supp Stat Supp Stat Si$pAdditional
Index Attribute template label ‘Value of object Constraints and
us or-t us or-t us ort us oft us or-t us
identifier for values information
attribute
“Dr.,. V 711 I ICAllCP 13 Q 2 3 7 CFT nF 05 .----T- l-l l-l I-I I I
1 I
I
I I I I- ‘-I I I I I I I I I I
.-.-- -. .___ I
allomorphs
“Rec. X.721 1 ISO/IEC (2 9 3 2 7 63) OBJECT - 0.5
IDENTIFIER
10165-2 : 1992 ”:
nameBinding
“Rec. X.72 1 b ISO/IEC (2 9 3 2 7 65) ObjectClass - 0.5
10165-2 : 19 2 ”:
objectClass
(2 9 3 2 7 66) SET OF OBJECT - 0.5
“Rec. X.721 j ISO/IEC
10165-2 : 1992 ”: IDENTIFIER
packages
- -
“ISO/IEC 10589 ”: (2 13 0 1 7 91) ISIS.OutputAdjac - 0.5 0.5
encies
defaultMetricOutputAdjance
ncies
- 0.5 0.5
“ISO/IEC 10589 “: (2 13 0 1 7 90) ISIS.PathMetric
defaultMetricPathCost
- 0.5 0.5
” ISOA EC 10589 ”: (2 13 0 1 7 93) lSIS.OutputAdjac
encies
delay MetricOutputAdjancen
ties
“ISO/IEC 10589 ”: (2 13 0 1 7 92) ISIS.PathMetric - 0.5 0.5
t
J-l-. .L ‘-L-:-r\-&Lfi,,L
iaelayIvlerrlcralri~usi I I I l I ’ ’
I I
I - 1 1 0.5 I 1 0.5 I 1 -
0 1 7 97) IISIS.OutputAdjac
encies
I I I I I I I I
encies
ISISNAddress
0 1 7 88)
I I-I lo.51 I-I l-l I-I I-I I I
11
---------------------- Page: 13 ----------------------
OISOAEC
ISO/IEC 10589 : 1992/Amd. 1 : 1996(E)
H.4.1.5 Reachable address managed object
Table H.5 - reachableAddress Attribute support
Get Replace Add Remove Set to
::a!i:
default
I 1
Index Attribute template label Value of object C;,nwFints and Stat S$p Stat S$p Stat “,u$p Stat Si$p Stat S;ul$p Stat Supp Additional
us us us
identifier for v us us us
Ort information
attribute
1 --
“Rec. X.721 b ISO/IEC (2 9 3 2 7 50) SET OF c2
0.5
101652 : 19 2 ”: ObjectClass
allomorphs
2 “Rec. X.721 Ll ISO/IEC
(2 9 3 2 7 63) OBJECT c2 0.5
10165-2 : 19 2 ”: IDENTIFIER
nameBinding
3 “Rec. X.721 !3 ISO/IEC (2 9 3 2 7 65) ObjectClass
c2 0.5
10165-2 : 19 2 ”:
objectClass
4 “Rec. X.721 Ll ISO/IEC
(2 9 3 2 7 66) SET OF c2
0.5
10165-2 : 19 2 ”: OBJECT
IDENTIFIER
packages
5 “ISO/IEC 10589 ”: (2 13 0 1 7 121) ISIS.GraphicStri
c2 0.5
w
reachableAddressId
6
” I SO/I EC 10589” : (2 13
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.