rfc1444.txt

<VC++网络游戏建摸与实现>源代码

          Network Working Group                                  J. Case
          Request for Comments: 1444                 SNMP Research, Inc.
                                                           K. McCloghrie
                                                      Hughes LAN Systems
                                                                 M. Rose
                                            Dover Beach Consulting, Inc.
                                                           S. Waldbusser
                                              Carnegie Mellon University
                                                              April 1993


                              Conformance Statements
                               for version 2 of the
                   Simple Network Management Protocol (SNMPv2)


          Status of this Memo

          This RFC specifes an IAB standards track protocol for the
          Internet community, and requests discussion and suggestions
          for improvements.  Please refer to the current edition of the
          "IAB Official Protocol Standards" for the standardization
          state and status of this protocol.  Distribution of this memo
          is unlimited.


          Table of Contents


          1 Introduction ..........................................    2
          1.1 A Note on Terminology ...............................    2
          2 Definitions ...........................................    3
          3.1 The OBJECT-GROUP macro ..............................    3
          3.2 The MODULE-COMPLIANCE macro .........................    4
          3.3 The AGENT-CAPABILITIES macro ........................    7
          3 Mapping of the OBJECT-GROUP macro .....................   10
          3.1 Mapping of the OBJECTS clause .......................   10
          3.2 Mapping of the STATUS clause ........................   10
          3.3 Mapping of the DESCRIPTION clause ...................   10
          3.4 Mapping of the REFERENCE clause .....................   11
          3.5 Mapping of the OBJECT-GROUP value ...................   11
          3.6 Usage Example .......................................   12
          4 Mapping of the MODULE-COMPLIANCE macro ................   13
          4.1 Mapping of the STATUS clause ........................   13
          4.2 Mapping of the DESCRIPTION clause ...................   13
          4.3 Mapping of the REFERENCE clause .....................   13
          4.4 Mapping of the MODULE clause ........................   13
          4.4.1 Mapping of the MANDATORY-GROUPS clause ............   14
          4.4.2 Mapping of the GROUP clause .......................   14
          4.4.3 Mapping of the OBJECT clause ......................   14




          Case, McCloghrie, Rose & Waldbusser                  [Page  i]





          RFC 1444      Conformance Statements for SNMPv2     April 1993


          4.4.3.1 Mapping of the SYNTAX clause ....................   15
          4.4.3.2 Mapping of the WRITE-SYNTAX clause ..............   15
          4.4.3.3 Mapping of the MIN-ACCESS clause ................   15
          4.4.3.4 Mapping of the DESCRIPTION clause ...............   16
          4.5 Mapping of the MODULE-COMPLIANCE value ..............   16
          4.6 Usage Example .......................................   17
          5 Mapping of the AGENT-CAPABILITIES macro ...............   19
          5.1 Mapping of the PRODUCT-RELEASE clause ...............   20
          5.2 Mapping of the STATUS clause ........................   20
          5.3 Mapping of the DESCRIPTION clause ...................   20
          5.4 Mapping of the REFERENCE clause .....................   20
          5.5 Mapping of the SUPPORTS clause ......................   20
          5.5.1 Mapping of the INCLUDES clause ....................   21
          5.5.2 Mapping of the VARIATION clause ...................   21
          5.5.2.1 Mapping of the SYNTAX clause ....................   21
          5.5.2.2 Mapping of the WRITE-SYNTAX clause ..............   21
          5.5.2.3 Mapping of the ACCESS clause ....................   22
          5.5.2.4 Mapping of the CREATION-REQUIRES clause .........   22
          5.5.2.5 Mapping of the DEFVAL clause ....................   23
          5.5.2.6 Mapping of the DESCRIPTION clause ...............   23
          5.6 Mapping of the AGENT-CAPABILITIES value .............   23
          5.7 Usage Example .......................................   24
          6 Extending an Information Module .......................   26
          6.1 Conformance Groups ..................................   26
          6.2 Compliance Definitions ..............................   26
          6.3 Capabilities Definitions ............................   26
          7 Acknowledgements ......................................   27
          8 References ............................................   31
          9 Security Considerations ...............................   32
          10 Authors' Addresses ...................................   32




















          Case, McCloghrie, Rose & Waldbusser                   [Page 1]





          RFC 1444      Conformance Statements for SNMPv2     April 1993


          1.  Introduction

          A network management system contains: several (potentially
          many) nodes, each with a processing entity, termed an agent,
          which has access to management instrumentation; at least one
          management station; and, a management protocol, used to convey
          management information between the agents and management
          stations.  Operations of the protocol are carried out under an
          administrative framework which defines both authentication and
          authorization policies.

          Network management stations execute management applications
          which monitor and control network elements.  Network elements
          are devices such as hosts, routers, terminal servers, etc.,
          which are monitored and controlled through access to their
          management information.

          Management information is viewed as a collection of managed
          objects, residing in a virtual information store, termed the
          Management Information Base (MIB).  Collections of related
          objects are defined in MIB modules.  These modules are written
          using a subset of OSI's Abstract Syntax Notation One (ASN.1)
          [1], termed the Structure of Management Information (SMI) [2].

          It may be useful to define the acceptable lower-bounds of
          implementation, along with the actual level of implementation
          achieved.  It is the purpose of this document to define the
          notation used for these purposes.


          1.1.  A Note on Terminology

          For the purpose of exposition, the original Internet-standard
          Network Management Framework, as described in RFCs 1155, 1157,
          and 1212, is termed the SNMP version 1 framework (SNMPv1).
          The current framework is termed the SNMP version 2 framework
          (SNMPv2).













          Case, McCloghrie, Rose & Waldbusser                   [Page 2]





          RFC 1444      Conformance Statements for SNMPv2     April 1993


          2.  Definitions

          SNMPv2-CONF DEFINITIONS ::= BEGIN

          -- definitions for conformance groups

          OBJECT-GROUP MACRO ::=
          BEGIN
              TYPE NOTATION ::=
                            ObjectsPart
                            "STATUS" Status
                            "DESCRIPTION" Text
                            ReferPart

              VALUE NOTATION ::=
                            value(VALUE OBJECT IDENTIFIER)

              ObjectsPart ::=
                            "OBJECTS" "{" Objects "}"
              Objects ::=
                            Object
                          | Objects "," Object
              Object ::=
                            value(Name ObjectName)

              Status ::=
                            "current"
                          | "obsolete"

              ReferPart ::=
                            "REFERENCE" Text
                          | empty

              -- uses the NVT ASCII character set
              Text ::= """" string """"
          END














          Case, McCloghrie, Rose & Waldbusser                   [Page 3]





          RFC 1444      Conformance Statements for SNMPv2     April 1993


          -- definitions for compliance statements

          MODULE-COMPLIANCE MACRO ::=
          BEGIN
              TYPE NOTATION ::=
                            "STATUS" Status
                            "DESCRIPTION" Text
                            ReferPart
                            ModulePart

              VALUE NOTATION ::=
                            value(VALUE OBJECT IDENTIFIER)

              Status ::=
                            "current"
                          | "obsolete"

              ReferPart ::=
                          "REFERENCE" Text
                        | empty

              ModulePart ::=
                            Modules
                          | empty
              Modules ::=
                            Module
                          | Modules Module
              Module ::=
                            -- name of module --
                            "MODULE" ModuleName
                            MandatoryPart
                            CompliancePart

              ModuleName ::=
                            modulereference ModuleIdentifier
                          -- must not be empty unless contained
                          -- in MIB Module
                          | empty
              ModuleIdentifier ::=
                            value(ModuleID OBJECT IDENTIFIER)
                          | empty

              MandatoryPart ::=
                            "MANDATORY-GROUPS" "{" Groups "}"
                          | empty





          Case, McCloghrie, Rose & Waldbusser                   [Page 4]





          RFC 1444      Conformance Statements for SNMPv2     April 1993


              Groups ::=
                            Group
                          | Groups "," Group
              Group ::=
                            value(Group OBJECT IDENTIFIER)

              CompliancePart ::=
                            Compliances
                          | empty

              Compliances ::=
                            Compliance
                          | Compliances Compliance
              Compliance ::=
                            ComplianceGroup
                          | Object

              ComplianceGroup ::=
                            "GROUP" value(Name OBJECT IDENTIFIER)
                            "DESCRIPTION" Text

              Object ::=
                            "OBJECT" value(Name ObjectName)
                            SyntaxPart
                            WriteSyntaxPart
                            AccessPart
                            "DESCRIPTION" Text

              -- must be a refinement for object's SYNTAX clause
              SyntaxPart ::=
                            "SYNTAX" type(SYNTAX)
                          | empty

              -- must be a refinement for object's SYNTAX clause
              WriteSyntaxPart ::=
                            "WRITE-SYNTAX" type(WriteSYNTAX)
                          | empty

              AccessPart ::=
                            "MIN-ACCESS" Access
                          | empty
              Access ::=
                            "not-accessible"
                          | "read-only"
                          | "read-write"





          Case, McCloghrie, Rose & Waldbusser                   [Page 5]





          RFC 1444      Conformance Statements for SNMPv2     April 1993


                          | "read-create"

              -- uses the NVT ASCII character set
              Text ::= """" string """"
          END













































          Case, McCloghrie, Rose & Waldbusser                   [Page 6]





          RFC 1444      Conformance Statements for SNMPv2     April 1993


          -- definitions for capabilities statements

          AGENT-CAPABILITIES MACRO ::=
          BEGIN
              TYPE NOTATION ::=
                            "PRODUCT-RELEASE" Text
                            "STATUS" Status
                            "DESCRIPTION" Text
                            ReferPart
                            ModulePart

              VALUE NOTATION ::=
                            -- agent's sysObjectID [3] or snmpORID [4]
                            value(VALUE OBJECT IDENTIFIER)

              Status ::=
                            "current"
                          | "obsolete"

              ReferPart ::=
                          "REFERENCE" Text
                        | empty

              ModulePart ::=
                            Modules
                          | empty
              Modules ::=
                            Module
                          | Modules Module
              Module ::=
                            -- name of module --
                            "SUPPORTS" ModuleName
                            "INCLUDES" "{" Groups "}"
                            VariationPart

              ModuleName ::=
                            identifier ModuleIdentifier
              ModuleIdentifier ::=
                            value(ModuleID OBJECT IDENTIFIER)
                          | empty

              Groups ::=
                            Group
                          | Groups "," Group
              Group ::=





          Case, McCloghrie, Rose & Waldbusser                   [Page 7]





          RFC 1444      Conformance Statements for SNMPv2     April 1993


                            value(Name OBJECT IDENTIFIER)

              VariationPart ::=
                            Variations
                          | empty
              Variations ::=
                            Variation
                          | Variations Variation