ITU-T X 734 AMD 1-1995 INFORMATION TECHNOLOGY C OPEN SYSTEMS INTERCONNECTION C SYSTEMS MANAGEMENT EVENT REPORT MANAGEMENT FUNCTION AMENDMENT 1 IMPLEMENTATION CONFORMANCE STATEMENT .pdf

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

2、NT REPORTMANAGEMENT FUNCTION!-%.$-%.4G0G0 G0G0)-0,%-%.4!4)/.G0G0#/.g) MOCS proforma;5) Apply the following changes to 3.6:Replace “term” with “terms”.Replace “system conformance statement” with the following:“a) PICS proforma;b) protocol implementation conformance statement;c) system conformance sta

3、tement.”6) Renumber 3.7 as 3.8 and insert the following new subclause:“3.7 Implementation conformance statement proforma definitionsThis Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.724 |ISO/IEC 10165-6:a) Managed Relationship Conformance Statement

4、 (MRCS);b) Management Conformance Summary (MCS);c) MCS proforma;d) MRCS proforma.”ISO/IEC 10164-5 : 1993/Amd.1 : 1995 (E)2 ITU-T Rec. X.734 (1992)/Amd.1 (1995 E)7) Add the following abbreviations to clause 4:“ICS Implementation Conformance StatementMCS Management Conformance SummaryMICS Management I

5、nformation Conformance StatementMOCS Managed Object Conformance StatementMRCS Managed Relationship Conformance StatementPICS Protocol Implementation Conformance Statement”8) Apply the following changes to 9.2:In the third paragraph, replace “annex B” with “Annex F”.9) Replace clause 13 with the foll

6、owing:“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 | Internati

7、onal 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 onemanagement operation or notification of the event fo

8、rwarding discriminator managed object specified by thisRecommendation | International Standard. The conformance requirements in the manager role for those managementoperations and notifications are identified in Table A.3 and further tables referenced by Annex A.If a claim of conformance is made for

9、 support in the agent role, the implementation shall support one or more instancesof the event forwarding discriminator managed object class identified in Table A.4.The implementation shall support the transfer syntax derived from the encoding rules specified in CCITT Rec. X.209 |ISO/IEC 8825 named

10、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 identified general anddependent conformance classes. A claim of conformance sim

11、ilar to general conformance class can be made by stating support in themanager role, the agent role, or both roles, for the event report management functional unit in Table A.2. A claim of conformancesimilar to dependent conformance class can be made by stating support for at least one of the items

12、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 definitions for which support is claimed.13.3 Management implementation conformanc

13、e statement requirementsAny MCS proforma, MICS proforma, MOCS proforma, and MRCS proforma which conforms to this Recommendation |International Standard shall be technically identical to the proformas specified in Annexes A, B, C and D preservingtable numbering and the index numbers of items, and dif

14、fering only in pagination and page headers.The supplier of an implementation which is claimed to conform to this Recommendation | International Standard shallcomplete a copy of the Management Conformance Summary (MCS) provided in Annex A as part of the conformancerequirements together with any other

15、 ICS proformas referenced as applicable from that MCS. An ICS which conforms tothis Recommendation | International Standard shall: describe an implementation which conforms to this Recommendation | International Standard; have been completed in accordance with the instructions for completion given i

16、n ITU-T Rec. X.724 |ISO/IEC 10165-6; include the information necessary to uniquely identify both the supplier and the implementation.”ISO/IEC 10164-5 : 1993/Amd.1 : 1995 (E)ITU-T Rec. X.734 (1992)/Amd.1 (1995 E) 310) Relabel Annexes A through C as E through G and insert the following annexes:Annex A

17、MCS proforma3)(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 on whether the implementation cl

18、aims 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 completing the MCS proforma to pr

19、oduce 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 | International Standard, the following co

20、mmon 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 a conditional or optional item

21、 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 | International Standard, the following

22、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 Table formatSome of the tables in

23、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 complete table reconstructed from

24、 the constituent partsshould have the following layout:_3)Users of this Recommendation | International Standard may freely reproduce 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 specifi

25、edin ITU-T Rec. X.724 | ISO/IEC 10165-6.Index First block of columns Second block of columns Etc.ISO/IEC 10164-5 : 1993/Amd.1 : 1995 (E)4 ITU-T Rec. X.734 (1992)/Amd.1 (1995 E)In this Recommendation | International Standard the constituent parts of the table appear consecutively, starting with thefi

26、rst block of columns.When 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 sub-rows within each indexed row

27、. 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 (continued) TitleA complete table reconstructed from the constituent parts should have the following layout:References made to cells withi

28、n tables shall be interpreted as references within reconstructed tables. In the example,above, the reference X.1/1d corresponds to the blank cell in column G for row with Index 1, and X.1/1.2b corresponds tothe blank cell in column L for row with Sub-index 1.2.A.2 Identification of the implementatio

29、nA.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 Sub-index H I J K L1 a b 1.1 h i j

30、1.2 h i j2 a b 2.1 h i j2.2 h i jDate of statementISO/IEC 10164-5 : 1993/Amd.1 : 1995 (E)ITU-T Rec. X.734 (1992)/Amd.1 (1995 E) 5A.2.2 Identification of the implementationThe supplier of the implementation shall enter information necessary to uniquely identify the implementation and thesystem(s) in

31、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 of the Recommendations | Internati

32、onal 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 conformance isclaimed, in the box below

33、.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 supplier of the implementation shall

34、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-5 : 1993/Amd.1 : 1995 (E)6 ITU-T Rec. X.734 (1992)/Amd.1 (1995 E)A.4 Ma

35、nagement 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 implementation shall specify the roles that ar

36、e supported, in Table A.1.Table A.1 RolesThe supplier of the implementation shall specify support for the systems management functional units, in Table A.2.Table A.2 Systems management functional unitsThe supplier of the implementation shall specify support for management information in the manager

37、role, in Table A.3.Table A.3 Manager role minimum conformance requirementIndex Roles supported Status Support Additional information1 Manager role support o.12 Agent role support o.1Manager AgentIndex Systems management functional unit name Status Support Status Support Additional information1 event

38、 report management functional unit c1 c22 monitor event report management 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 Operations on managed objects c32 Object creation notification for event forwardingdiscriminator mana

39、ged objectc43 Object deletion notification for event forwardingdiscriminator managed objectc44 Attribute value change notification for event forwardingdiscriminator managed objectc45 State change notification for event forwarding discriminatormanaged objectc4c3: if A.2/1a then m else (if A.1/1a then

40、 o.2 else ).c4: if A.2/1a then m else (if A.2/2a then o 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 foreither of the functional units identified in Table A.2 mandates support for some of those

41、items. Conditions c3 and c4 express bothof these requirements.ISO/IEC 10164-5 : 1993/Amd.1 : 1995 (E)ITU-T Rec. X.734 (1992)/Amd.1 (1995 E) 7The supplier of the implementation shall specify support for management information in the agent role, in Table A.4.Table A.4 Agent role minimum conformance re

42、quirementTable 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.The supplier of the implementation shall provide information on claims of conformance to any of the Recommendations| Interna

43、tional Standards summarized in Tables A.6 to A.9. For each Recommendation | International Standard that thesupplier 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

44、the Support, Table numbers andAdditional information columns.In Tables A.6 to A.9, the Status column is used to indicate whether the supplier of the implementation is required tocomplete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tablesor r

45、eferenced 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 completion of the referenced tables or referenced items.Table A.6 PICS support summaryNOTE 2 Conformance to the MAPDUs defined in this Rec

46、ommendation | International Standard can be claimed bycompleting the corresponding tables in the MICS and MOCS annexes of the referenced Recommendations | International Standards.Index Item Status Support Additional information1 Event forwarding discriminator managed object class c52 Subclasses of l

47、og records associated withnotifications emitted by the event forwardingdiscriminator managed objectc6c5: if A.1/2a then m 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 notificationssup

48、ported.2 The Table reference column in this table 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 suppo

49、rt logging of event records in agent role? c7c7: if A.1/2a then o else .IndexIdentification of thedocument that includesthe PICS proformaTablenumbersof PICSproformaDescription Constraints andvaluesStatus SupportTablenumbersof PICSAdditionalinformation1 CCITT Rec. X.730 |ISO/IEC 10164-1Annex Eall tablesSM applicationcontextOBJECTIDENTIFIERmISO/IEC 10164-5 : 1993/Amd.1 : 1995 (E)8 ITU-T Rec. X.734 (1992)/Amd.1 (1995 E)Table A.7 MOCS support summaryTable A.8 MRCS support summaryTable A.9 MICS support summaryc11: if A.3/