ITU-T X 736 AMD 1-1995 INFORMATION TECHNOLOGY C OPEN SYSTEMS INTERCONNECTION C SYSTEMS MANAGEMENT SECURITY ALARM REPORTING FUNCTION AMENDMENT 1 IMPLEMENTATION CONFORMANCE STATEMENT.pdf

1、ITU-T Rec. X.736 (1992)/Amd.1 (1995 E) iINTERNATIONAL TELECOMMUNICATION UNION)45G134 !MENDMENTG0G0 TELECOMMUNICATION 8 STANDARDIZATION SECTOROF ITU (04/95)$!4!G0G0.%47/2+3G0G0!.$/0%.G0G03934%-G0G0#/-5.)#!4)/.3/3)G0G0-!.!%-%.4INFORMATION TECHNOLOGY OPEN SYSTEMS INTERCONNECTION SYSTEMS MANAGEMENT: SEC

2、URITY ALARMREPORTING FUNCTION!-%.$-%.4G0G0 G0G0)-0,%-%.4!4)/.G0G0#/.“f) MOCS proforma;”5) Apply the following change to 3.7:Replace “system conformance statement” with the following:“a) PICS proforma;“b) protocol implementation conformance statement;“c) system conformance statement.”6) Renumber 3.8

3、as 3.9 and insert the following new subclause:ISO/IEC 10164-7 : 1992/Amd.1 : 1995 (E)2 ITU-T Rec. X.736 (1992)/Amd.1 (1995 E)“3.8 Implementation conformance statement proforma definitionsThis Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.724 |ISO/IE

4、C 10165-6:a) Managed Relationship Conformance Statement (MRCS);b) Management Conformance Summary (MCS);c) Management Information Definition Statement (MIDS) proforma;d) MCS proforma;e) MRCS proforma.”7) Add the following abbreviations to clause 4:“ICS Implementation Conformance Statement“MCS Managem

5、ent Conformance Summary“MICS Management Information Conformance Statement“MIDS Management Information Definition Statement“MOCS Managed Object Conformance Statement“MRCS Managed Relationship Conformance Statement“PICS Protocol Implementation Conformance Statement”8) Replace clause 13 with the follow

6、ing:“13 ConformanceImplementations claiming to conform to this Recommendation | International Standard shall comply with theconformance requirements as defined in the following subclauses.13.1 Static conformanceThe implementation shall conform to the requirements of this Recommendation | Internation

7、al Standard in the managerrole, the agent role, or both roles. A claim of conformance to at least one role shall be made in Table A.1.If a claim of conformance is made for support in the manager role, the implementation shall support at least one of thenotifications or at least one of the management

8、 operations specified in this Recommendation | International Standard.The conformance requirements in the manager role for those management operations and notifications are identified inTable A.3 and further tables referenced by Annex A.If a claim of conformance is made for support in the agent role

9、, the implementation shall support at least one of thenotifications specified in this Recommendation | International Standard. The conformance requirements in the agent roleare identified in Table A.4 and further tables referenced by Annex A.The implementation shall support the transfer syntax deriv

10、ed from the encoding rules specified in CCITT Rec. X.209 |ISO/IEC 8825 named joint-iso-ccitt asn1(1) basicEncoding(1) for the abstract data types referenced by the definitionsfor which support is claimed.NOTE Prior to the publication of this amendment, this Recommendation | International Standard id

11、entified general and dependentconformance classes. A claim of conformance similar to general conformance class can be made by stating support in the manager role, the agent role,or both roles, for the security alarm reporting functional unit in Table A.2. A claim of conformance similar to dependent

12、conformance class can be madeby stating support for at least one of the items in Tables A.3 or A.4.13.2 Dynamic conformanceImplementations claiming to conform to this Recommendation | International Standard shall support the elements ofprocedure and definitions of semantics corresponding to the defi

13、nitions for which support is claimed.13.3 Management implementation conformance statement requirementsAny MCS proforma, MICS proforma, and MOCS proforma which conforms to this Recommendation | InternationalStandard shall be technically identical to the proformas specified in Annexes A, B and C prese

14、rving table numbering andthe index numbers of items, and differing only in pagination and page headers.ISO/IEC 10164-7 : 1992/Amd.1 : 1995 (E)ITU-T Rec. X.736 (1992)/Amd.1 (1995 E) 3The supplier of an implementation which is claimed to conform to this Recommendation | International Standard shallcom

15、plete a copy of the Management Conformance Summary (MCS) provided in Annex A as part of the conformancerequirements together with any other ICS proformas referenced as applicable from that MCS. An ICS which conforms tothis Recommendation | International Standard shall: describe an implementation whi

16、ch conforms to this Recommendation | 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.Claims of conformance to the

17、 management information defined in this Recommendation | International Standard inmanaged object classes defined elsewhere shall include the requirements of the MIDS proforma in the MOCS for themanaged object class.”9) Add the following annexes:ISO/IEC 10164-7 : 1992/Amd.1 : 1995 (E)4 ITU-T Rec. X.7

18、36 (1992)/Amd.1 (1995 E)Annex AMCS proforma5)(This annex forms an integral part of this Recommendation | International Standard)A.1 IntroductionA.1.1 Purpose and structureThe Management Conformance Summary (MCS) is a statement by a supplier that identifies an implementation andprovides information o

19、n whether the implementation claims conformance to any of the listed set of documents thatspecify conformance requirements to OSI management.The MCS proforma is a document in the form of a questionnaire that when completed by the supplier of animplementation becomes the MCS.A.1.2 Instructions for co

20、mpleting the MCS proforma to produce a MCSThe supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction isprovided in the text which precedes each table.A.1.3 Symbols, abbreviations and termsFor all annexes of this Recommendation | Internati

21、onal Standard, the following common notations, defined in CCITTRec. X.291 | ISO/IEC 9646-2 and ITU-T Rec. X.296 | ISO/IEC 9646-7, are used for the Status column:m Mandatory;o Optional;c Conditional;x Prohibited; Not applicable or out of scope.NOTES1 c, m, and o are prefixed by “c:” when nested under

22、 a conditional or optional item of the same table;2 o may be suffixed by “.N” (where N is a unique number) for selectable options among a set of status values.Support of at least one of the choices (from the items with the same value of N) is required.For all annexes of this Recommendation | Interna

23、tional Standard, the following common notations, defined in CCITTRec. X.291 | ISO/IEC 9646-2 and ITU-T Rec. X.296 | 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).A.1.4 Tab

24、le formatSome of the tables in this Recommendation | International Standard have been split because the information is too wideto fit on the page. Where this occurs, the index number of the first block of columns are the index numbers of thecorresponding rows of the remaining blocks of columns. A co

25、mplete table reconstructed from the constituent partsshould have the following layout:In this Recommendation | International Standard the constituent parts of the table appear consecutively, starting with thefirst block of columns._5)Users of this Recommendation | International Standard may freely r

26、eproduce the MCS proforma in this annex so that it can beused for its intended purpose, and may further publish the completed MCS. Instructions for the MCS proforma are specified inITU-T Rec. X.724 | ISO/IEC 10165-6.Index First block of columns Second block of columns Etc.ISO/IEC 10164-7 : 1992/Amd.

27、1 : 1995 (E)ITU-T Rec. X.736 (1992)/Amd.1 (1995 E) 5When a table with sub-rows is too wide to fit on a page, the continuation table(s) have been constructed with indexnumbers identical to the index numbers in the corresponding rows of the first table, and with sub-index numberscorresponding to the s

28、ub-rows within each indexed row. For example, if Table X.1 has 2 rows and the continuation ofTable X.1 has 2 sub-rows for each row, the tables are presented as follows:Table X.1 TitleTable X.1 (concluded) TitleA complete table reconstructed from the constituent parts should have the following layout

29、:References made to cells within tables shall be interpreted as references within reconstructed tables. In the example,above, the reference X.1/1d corresponds with the blank cell in column G for row with Index 1, and X.1/1.2b correspondswith the blank cell in column L for row with Sub-index 1.2.A.2

30、Identification of the implementationA.2.1 Date of statementThe supplier of the implementation shall enter the date of this statement in the box below. Use the format DD-MM-YYYY.SupportIndex A B C D E F G1ab2abIndex Sub-index H I J K L1 1.1 h i j1.2 h i j2 2.1 h i j2.2 h i jSupportIndex A B C D E F G

31、 Sub-index H I J K L1 a b 1.1 h i j1.2 h i j2 a b 2.1 h i j2.2 h i jDate of statementISO/IEC 10164-7 : 1992/Amd.1 : 1995 (E)6 ITU-T Rec. X.736 (1992)/Amd.1 (1995 E)A.2.2 Identification of the implementationThe supplier of the implementation shall enter information necessary to uniquely identify the

32、implementation and thesystem(s) in which it may reside, in the box below.A.2.3 ContactThe supplier of the implementation shall provide information on whom to contact if there are any queries concerning thecontent of the MCS or any referenced conformance statement, in the box below.A.3 Identification

33、 of the Recommendations | International Standards in which the managementinformation is definedThe supplier of the implementation shall enter the title, reference number and date of the publication of theRecommendations | International Standards which specify the management information to which conf

34、ormance isclaimed, in the box below.A.3.1 Technical corrigenda implementedThe supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modifythe identified Recommendations | International Standards, in the box below.A.3.2 Amendments implementedThe su

35、pplier of the implementation shall state the titles and reference numbers of implemented amendments to theidentified Recommendations | International Standards, in the box below.Recommendations | International Standards to which conformance is claimedISO/IEC 10164-7 : 1992/Amd.1 : 1995 (E)ITU-T Rec.

36、X.736 (1992)/Amd.1 (1995 E) 7A.4 Management conformance summaryThe supplier of the implementation shall state the capabilities and features supported and provide a summary ofconformance claims to Recommendations | International Standards using the tables in this annex.The supplier of the implementat

37、ion shall specify the roles that are supported, in Table A.1.Table A.1 RolesThe supplier of the implementation shall specify support for the systems management functional unit, in Table A.2.Table A.2 Systems management functional unitThe supplier of the implementation shall specify support for manag

38、ement information in the manager role, in Table A.3.Table A.3 Manager role minimum conformance requirementThe supplier of the implementation shall specify support for management information in the agent role, in Table A.4.Index Roles supported Status Support Additional information1 Manager role supp

39、ort o.12 Agent role support o.1Manager AgentIndex Systems management functional unit name Status Support Status Support Additional information1 security alarm reporting functional unit c1 c2c1: if A.1/1a then o else .c2: if A.1/2a then o else .Index Item Status Support Additional information1 Integr

40、ity violation notification c32 Operational violation notification c33 Physical violation notification c34 Security service or mechanism violation notification c35 Time domain violation notification c36 Operations on managed objects c4c3: if A.2/1a then m else (if A.1/1a then o.2 else ).c4: if A.2/1a

41、 then m else (if A.1/1a then o.2 else ).NOTE Manager role minimum conformance requires support for at least one of the items identified in this table. Support for thefunctional unit identified in Table A.2 mandates support for some of those items. Conditions c3 and c4 express both of theserequiremen

42、ts.ISO/IEC 10164-7 : 1992/Amd.1 : 1995 (E)8 ITU-T Rec. X.736 (1992)/Amd.1 (1995 E)Table A.4 Agent role minimum conformance requirementTable A.5 Logging of event recordsNOTE 1 Conformance to this Recommendation | International Standard does not require conformance to CCITTRec. X.735 | ISO/IEC 10164-6

43、.The supplier of the implementation shall provide information on claims of conformance to any of the Recommendations| International Standards summarized in the Tables A.6 to A.9. For each Recommendation | International Standard thatthe supplier of the implementation claims conformance to, the corres

44、ponding conformance statement(s) shall becompleted, or referenced by, the MCS. The supplier of the implementation shall complete the Support, Table numbersand Additional information columns.In Tables A.6 to A.9, the Status column is used to indicate whether the supplier of the implementation is requ

45、ired tocomplete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tablesor referenced items and are not changed by the value of the MCS Status column. Similarly, the Support column is usedby the supplier of the implementation to indicate completio

46、n of the referenced tables or referenced items.Table A.6 PICS support summaryNOTE 2 Conformance to the MAPDUs defined in this Recommendation | International Standard can be claimed bycompleting the corresponding tables in the MICS and MOCS annexes of the referenced Recommendations | International St

47、andards.Index Item Status Support Table reference Additional information1 Integrity violation notification c52 Operational violation notification c53 Physical violation notification c54 Security service or mechanism violation notification c55 Time domain violation notification c56 Security alarm rec

48、ord managed object class c6 c5: if A.2/1b then m else (if A.1/2a then o.3 else ).c6: if A.1/2a and A.5/1a then m else .NOTES1 Condition c6 makes it mandatory, if logging is supported, to support the event log records associated with the notificationssupported.2 The Table reference column in this tab

49、le is the notification reference of the MOCS supplied by the supplier of the managedobject which claims to import the notification from this Recommendation | International Standard.Index Status SupportAdditionalinformation1 Does the implementation support logging of event records in agent role? c7c7: if A.1/2a then o else .IndexIdentification of thedocument that includesthe PICS proformaTablenumbersof PICSproformaDescriptionConstraints andvaluesStatus SupportTablenumbersof PICSAdditionalinformation1 CCITT Rec. X.730 |ISO/I