1、STD*ITU-T RECMN X.722 AMD 2-ENGL 1777 9 48b2571 Ob44557 77b = INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.722 Amendment 2 (08197) SERIES X: DATA NETWORKS AND OPEN SYSTEM CO M M U N i CAT I O N OS1 management - Structure of Management Information Info
2、rmation technology - Open Systems Interconnection - Structure of management information: Guidelines for the definition of managed objects Amendment 2: Addition of the NO-MODIFY syntax element and guidelines extension TU-T Recommendation X.722 - Amendment 2 (Previously CCITT Recommendation) ITU-T X-S
3、ERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATION TJBLIC DATA NETWORKS Services and facilities In terface s Transmission, signalling and switching Network aspects Maintenance Administrative arrangements OPEN SYSTEM INTERCONNECTION Model and notation Service definitions Connection-mod
4、e protocol specifications Connectionless-mode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects Conformance testing INTERWORKING BETWEEN NETWORKS General Satellite data transmission systems MESSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SY
5、STEM ASPECTS Networking Efficiency Naming, Addressing and Registration Abstract Syntax Notation One (ASN.l) OS1 MANAGEMENT Systems Management framework and architecture Management Communication Service and Protocol Structure of Management Informati Management functions SECURITY OS1 APPLICATIONS Comm
6、itment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING X. 1-X. 199 X. 1 -X. 19 X.20-X.49 X.50-X.89 X.90-X. 149 X.150-X.179 X.180-X.199 X .200-X.299 X.200-X.209 X.2 1 0-X .2 1 9 X.220-X.229 X.230-X.239 X.240-X.259 X.260-X.269 X.270-X.279 X.280-X.289 X.29
7、0-X.299 X.300-X.399 X .3 00-X .349 x.350-x.399 X.400-X.499 X.500-X.599 X.600-X.699 X.600-X.629 X.630-X.649 X.650-X.679 X.680-X.699 x.700-x.799 X.700-X.709 X.710-X.719 X.72-X.729 X.730-X.799 X. 800-X.849 X.850-X.899 X.850-X.859 X.860-X.879 X.880-X.899 x.900-x.999 For further details, please refer to
8、ITU-T List of Recommendations. - STD-ITU-T RECMN X.722 AND 2-ENGL 1477 = 48b2571 Ob445b1 524 INTERNATIONAL STANDARD 10165-4 ITU-T RECOMMENDATION X.722 INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - STRUCTURE OF MANAGEMENT INFORMATION: GUIDELINES FOR THE DEFINITION OF MANAGED OBJECTS AMENDME
9、NT 2 Addition of the NO-MODIFY syntax element and guidelines extension Summary This Amendment to CCITT Rec. X.722 I ISO/IEC 10165-4, the Guidelines for Definition of Managed Objects, covers two topics. One topic of the amendment is the specification of a NO-MODIFY syntax element to the GDMO Package
10、Templates. The other topic of the amendment is a guidelines extension which describes rules for specifications of management information based on the X.700-Series to evolve to the use of ASN.1:1994 from ASN.1:1990. The guidelines extension provides a common and consistent means to do this, so that p
11、roduct developers are provided with a single way to speci use of ASN. 1 : 1994 in the Recommendations they implement. Source The ITU-T Recommendation X.722, Amendment 2 was approved on the 9th of August 1997. The identical text is also published as ISOIEC International Standard 101 65-4. ITU-T Rec.
12、X.722 (1992)/Amd.2 (1997 E) i FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommuni- cations. The IT Telecommunication Standardization Sector (ITU-T) is a permanent organ of the IT. The ITU-T is responsible for studying technical, o
13、perating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in th
14、eir turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collabora
15、tive basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implem
16、entation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development proc
17、ess. As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore str
18、ongly urged to consult the TSB patent database. O ITU 1998 All rights reserved. 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 ITU. 11 ITU-T Rec. X.722 (1992
19、)/Amd.2 (1997 E) STD-ITU-T RECMN X.722 AMD 2-ENGL 1797 Lib257L Ob1145b3 3T7 CONTENTS 1) Subclause 2.1 . 2) Subclause 8.2 . 3) Subclause 8.4.2 4) Subclause 8.4.3.2 . 5) Index . 6) New clause 9 7) New clause 10 ITU-T Rec . X.722 (1992)/Amd.2 (1997 E) Page 1 1 1 1 2 2 7 . 111 STD-ITU-T RECMN X.722 AMD
20、2-ENGL 1777 = 48b2591 Ob445b4 233 = Introduction This Amendment adds the NO-MODLFY syntax element to the attribute properties of the package template in order to clearly specify that an attribute cannot be modified in subclasses and compatible classes of the managed object class. This Amendment prop
21、oses that the use of ASN.1:1994 should not be forbidden (i.e. normative specification of ASN.1:1994 may be employed) in new and developing OS1 Systems Management standards for the following reasons: ASN.1:1994 enhancements. ASN. 1 : 1990 bugsdefects; ASN.1:1990 and ASN.1:1994 modules can be mixed an
22、d are completely compatible using the guidelines in A.2 of Rec. ITU-T X.680 1 ISOIEC 8824-1, ASN.l Specification of Basic Notation. This “mixed mode“ use of ASN.l places certain restrictions on allowed productions of both ASN.1:1990 and ASN.1:1994. If these guidelines are maintained, not only are AS
23、N.l: 1990 and ASN.1:1994 completely compatible, they are virtually indistinguishable and have identical encoding. Using these guidelines, new and developing OS1 Systems Management standards may use both ASN.1:1990 and ASN. 1 : 1994 for normative specification of syntax. This Amendment introduces con
24、ventions for the specification of ASN.l and GDMO directives in order to clearly identify specification and user options associated with ASN.l modules and GDMO templates. iv ITU-T Rec. X.722-(1992)/Amd.2 (1997 E) - - STD-ITU-T RECMN X-722 AMD 2-ENGL 1777 48b257L Ob445b5 L7T = ISOAEC 10165-4 : 1992/Am
25、d.2 : 1998 (E) INTERNATIONAL STANDARD ITU-T RECOMMENDATION INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - STRUCTURE OF MANAGEMENT INFORMATION: GUIDELINES FOR THE DEFINITION OF MANAGED OBJECTS AMENDMENT 2 Addition of the NO-MODIFY syntax element and guideline extensions 1) Subclause 2.1 inse
26、rt the following references by numerical order: - ITU-T Recommendation X.680 (1994) I ISO/IEC 8824-1:1995, Information technology -Abstract Syntar Notation One (ASN. 1): Specification of basic notation. ITU-T Recommendation X.681 (1994) 1 ISO/IEC 8824-2:1995, Information technology -Abstract Syntax
27、Notation One (ASN. 1): Information object specification. ITU-T Recommendation X.682 (1994) I ISO/IEC 8824-3:1995, Information technology -Abstract Syntax Notation One (ASN. 1): Constraint specijcation. ITU-T Recommendation X.683 (1994) I ISOAEC 8824-4:1995, Information technology -Abstract Syntax No
28、tation One (ASN. 1): Parameterization of ASN. 1 specijcations. ITU-T Recommendation X.690 (1994) I ISO/IEC 8825-1 :1995, Information technology - ASN. 1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). Encoding Rules
29、-Specification of Packed Encoding Rules (PER). - - - - - ITU-T Recommendation X.691 (1995) ISOIIEC 8825-2:1995, Information technology - ASN.1 2) Subclause 8.2 Add the following to the end of item m): (Guidelines for the Production of Equivalent ASN. 1 : 1990 and ASN. 1 : 1994 Modules are given in c
30、lause 9.) 3) Subclause 8.4.2 Add the following to this subclause, following the SET-BY-CREATE property in the propertylist. (The SET-BY-CREATE property was added in by Amendment 1): NO-MODIFY 4) Subclause 8.4.3.2 Add the following two new paragraphs before the last paragraph: The absence of the REPL
31、ACE property may be used to speciQ that an attribute cannot be replaced for instances of a class but this absence does not preclude subclasses adding the REPLACE property. The NO-MODIFY property is present to explicitly speciQ that an attribute cannot be modified (is read-only) in the class having t
32、his property and in all ITU-T Rec. X.722 (1992)/Amd.2 (1997 E) 1 ISOIEC 10165-4 : 1992/Amd.2 : 1998 (E) subclasses and in all compatible managed objects (i.e. managed objects behaving allomorphically to the class). This property is inconsistent with and shall not be present in a managed object class
33、 definition that has any of the REPLACE, GET-REPLACE, ADD, REMOVE, or ADD-REMOVE properties on the same attribute. NOTE 3 -The NO-MODIFY property is not necessarily inconsistent with the REPLACE-WITH-DEFAULT property because this operation is often used with a meaning of “reset” that can be consiste
34、nt with a managers inability to control the attributes value. NOTE 4 - Before the NO-MODIFY property was added to GDMO, the convention was to specify that property in BEHAVIOUR templates or in documents referenced in BEHAVIOUR templates. If it is desired that part of the definition of an attribute i
35、s that the attribute shall not be replaced in any class that specifies the attribute, then this constraint shall be specified in a BEHAVIOUR template referenced by the ATTRIBUTE template. 5) Index Add new index entry: NO-MODIFY 26-27 Change these index entries: BEHAVIOUR 25-26,30-32,34-35,37-40 REPL
36、ACE 14,26-27 6) New clause 9 Add a new clause 9, following 8.11.3.5: 9 Guidelines for production of equivalent ASN.1: 1994 and ASN.l: 1990 modules It is possible in developing standards, that normative ASN.1:1994 modules be provided. In order to allow the use of ASN. 1 : 1994, it is recommended that
37、 an equivalent normative ASN.1:1990 module be provided subject to the following: it has the same object identifier as the ASN. 1 : 1994 module; it is normative but the standard states that in the event of discrepancies between the ASN.1:1990 and ASN. 1 :1994 modules, the ASN. 1 : 1994 module take pr
38、ecedence; the standard states that use of ASN.1:1990 will be retained as long as needed. NOTE 1 - ISOiEC JTC 1/SC 2 i rules dictate a periodic review for renewal of the ASN. 1 : 1990 International Standards every one (1) year). National Bodies are asked to consider the above when reviewing the ASN.1
39、:1990 standards. This ensures that the ASN. 1 : 1990 standards are retained as long as needed. Also to reduce errors, it is recommended that the ASN.1:1990 module be a machine generated transformation of the ASN. 1 : 1994 module since this transformation can be easily automated. NOTE 2 - If an edito
40、r desires to use a commercial tool (e.g. made available to the standards community at virtually no cost, vendor XXXs ASN. 1 Tools) for converting ASN.1: 1994 to ASN. 1 : 1990 to reduce the possibility of errors, it has been suggested that the editor should add a comment at the top of the generated c
41、ode that says something like: - XXXASN. 1 Tools used for conversion - - from ASN.1:1994 to ASN.l:1990 - with the following Note: NOTE - Although IS0 cannot advertise that one software tool must be used as opposed to another, at present, XXX ASN.1 Tools is one of the software tools allowing the conve
42、rsion fiom ASN. 1 : 1994 to ASN. 1 : 1990. It should be noted that problems can be avoided if only the common subset of ASN. 1 : 1990 and ASN. 1 : 1994 is used. In this case, only the ASN. 1 : 1994 module needs to be included in this standard. ) ISOIIEC JTC 1/SC 21 (SC21) reaffirmed the continuation
43、 of availability of the ASN.i:1990 standards for reasons of conformance and interpretability (in SC21 N 9001 rev). SC21 requested its WGs to continue to maintain these standards. An SC21 resolution to continue maintenance will be conducted at each SC21 meeting (currently, once a year). 2 ITU-T Rec.
44、X.722-(1992)/Amd.2 (1997 E) STD-ITU-T RECMN X-722 AMD 2-ENGL 1797 m Li8b2591 lJb4115b7 T42 m ISO/IEC 10165-4 : 1992/Amd.2 : 1998 (E) 9.1 Guidelines The following guidelines must be followed: 1) A single systems management document may reference ASN.l modules from both ASN.1:1990 and ASN.1:1994. Howe
45、ver, any given module is required to completely conform to either ASN.l:1990 ur ASN. 1:1994, where directives defined in clause 10 are used to identi which version of the notation is being used in a particular module. Type and value references may be imported in an ASN. 1 : 1994 module from an ASN.
46、1 : 1990 module as long as: a) ASN. 1 : 1990 MACROS are not imported in an ASN. 1 : 1994 module; therefore one cannot create an instance of a MACRO in an ASN. 1: 1994 module. b) Identifiers for SET and SEQUENCE and CHOICE values are present. Also, type and value references may be imported in an ASN.
47、l: 1990 module from an ASN. 1: 1994 module as long as: - ASN.l :i994 CHARACTER STRING, BMPStrings, UniversalStrings, EMBEDDED PDV types are not imported. Since there is no ASN.1:1990 equivalent for these ASN.1:1994 types, their use is discouraged in ASN.l: 1994 modules which require an equivalent AS
48、N.1:1990 module. For this same reason, the use of the ASN.1:1994 Tuple type is forbidden in ASN.1:1994 modules which require an equivalent ASN. 1 : 1990 module2). NOTE 1 - If the proposed guidelines are maintained, there are no adverse implications of importing type and value references from one ver
49、sion of ASN.1 to another because equivalent constructs exist in all cases. The following ASN.1:1994 module shall be used for definitions of ASN.l information object classes that are imported into ASN. 1:1994 modules: - - SMModule Cjoint-iso-itu-i ms(9) smi(1) part4(4) asnlModule(2) 2) DEFINITIONS := BEGIN 2) 3) 4) REGISTERED-AS := TYPE-IDENTIFIER - TYPE-IDENTIFIER is defined in ISO/IEC 8824-1 und is available in any module - without the necessity for importing it and is defined as: - TYPE-IDENTIFIERR: CLASS - - Foo:= SEQUENCE (
