ISO/IEC 9595:1991/Cor 4:1995

Information technology — Open systems Interconnection — Common management information service definition — Technical Corrigendum 4

Technologies de l'information — Interconnexion de systèmes ouverts — Définition du service commun d'informations de gestion — Rectificatif technique 4

General Information

• Status: Withdrawn
• Publication Date: 30-Aug-1995
• Withdrawal Date: 30-Aug-1995
• ICS: 35.100.70 - Application layer
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 08-Oct-1998

Relations

• Revised: ISO/IEC 9595:1998 - Information technology — Open Systems Interconnection — Common management information service
• Effective Date: 15-Apr-2008
• Corrects: ISO/IEC 9595:1991 - Information technology — Open systems Interconnection — Common management information service definition
• Effective Date: 06-Jun-2022
• Child: ISO/IEC 9595:1991 - Information technology — Open systems Interconnection — Common management information service definition
• Effective Date: 15-Apr-2008
• Consolidated By: ISO 14044:2006 - Environmental management — Life cycle assessment — Requirements and guidelines
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL STANDARD ISO/IEC 95951991
TECHNICAL CORRIGENDUM 4
Published 1995-09-1 5
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. MEXflYHAPOoHAfl OPrAHM3AUMR no CTAHAAPTM3AUMM * ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMiSSiON~MEXflYHAPOflHAR 3iiEKTPOTEXHMYECKAR KOMMCCMfl-COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
lnformation technology - Open Systems Interconnection -
Common management information service definition
TECHNICAL CORRlGENDUM 4
Technologies de l'information - Interconnexion de systèmes ouverts - Définition du service commun d'information de
Technical corrigendum 4 to International Standard ISO/IEC 9595:1991 was prepared by Joint Technical Committee
ISOJEC JTC 1, information technology,
UDC 681.3.621.39 Ref. No. ISO/IEC 9!5951991/Cor.4:1995(E)
Descriptors: data processing, information interchange, network interconnection, open systems interconnection, application layer,
communication procedure, control procedures, management.
O ISO/IEC1995
Printed in Switzerland

---------------------- Page: 1 ----------------------
ISOAEC 9595: 1991Kor.4: 1995(E)
O ISOAEC
Annex C
(informative)
Preferred implementations
C.l Introduction
Some interoperability problems have arisen due to different interpretations of the procedures specified in this International
Standard and in ISO/IEC 9596-1 : 1991.
The purpose of this annex is to recommend one consistent interpretation and to notify users that these recommendations may
become mandatory requirements in the next revisions of CMIS and CMIP.
Recommendations for preferred implementations are presented in C.2. Commentaries, rationale and associated information
are provided by subsequent clauses of this annex.
C.2 Recornmenda t ions
1
C.2.1 If the invoking CMISE-service-user requests that a management operation be performed by a single managed object
the scope of the operation indicates that only the base object is selected and the filter parameter is absent), then the
(i.e.
performing CMISE-service-user may optionally return the managed object class and managed object instance parameters in
the response.
C.2.2 If the filter parameter is present or the scope of the operation indicates anything other than the base object alone, it is
recommended that for each managed object that performs the operation, that the performing CMISE-service-user includes the
managed object class and managed object instance parameters in the response.
I
NOTE - A conformant implementation of ISO/IEC 9596-1 : 1991 (CMIP version 2) may generate a success confirmation that is
indicated by the retm of the invoke identifier alone, in response to a request to perform a management operation on a single managed
object. The invoking CMISE-sexvice-user is forewarned that this confirmation does not guarantee that the managed object performed the
operation, if a filter was specified that evaluated to false.
C.2.3 If the invoking CMISE-service-user requests that a management operation be performed by multiple managed objects
(i.e. the scope parameter specifies other than the base object alone), then it is recommended that the performing CMISE-
service-user generate a result for the final response that only contains the invoke identifier (to indicate the completion of the
entire operation). If this is the only response, then the invoking CMISE-service-user shall assume that no managed object was
selected by the scope and optional filter parameters.
*'
C.3 Managed object selection and response issues
C.3.1 Selection of a single managed object
When the base object alone is specified, the service definitions in this International Standard indicate that it is not necessary
to include the managed object class and managed object instance parameters in the success response. The rationale is that if
there is only one managed object requested to perform the operation, then there is no need to repeat its identity in the
response. In addition, the M-SET, M-ACTION and M-DELETE services do not mandate that there be a result parameter in
the success confirmation.
C.3.1.1 If no filter parameter is specified and the managed object performs the operation as requested, a success
confirmation can be indicated by the return of the invoke identifier parameter alone.
C.3.1.2 If a filter parameter is specified and the filter evaluates to TRUE, and the managed object performs the operation as
requested, a success confirmation can be indicated by the return of the invoke identifier parameter alone.
C.3.1.3 If a filter parameter is specified and the filter evaluates to FALSE, and hen
...