rfc1904.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 1,348 行 · 第 1/4 页

Network Working Group                               SNMPv2 Working Group
Request for Comments: 1904                                       J. Case
Obsoletes: 1444                                      SNMP Research, Inc.
Category: Standards Track                                  K. McCloghrie
                                                     Cisco Systems, Inc.
                                                                 M. Rose
                                            Dover Beach Consulting, Inc.
                                                           S. Waldbusser
                                          International Network Services
                                                            January 1996


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

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) 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 ......................................    3
   2. Definitions .................................................    3
   2.1 The OBJECT-GROUP macro .....................................    3
   2.2 The NOTIFICATION-GROUP macro ...............................    4
   2.3 The MODULE-COMPLIANCE macro ................................    5
   2.4 The AGENT-CAPABILITIES macro ...............................    7
   3. Mapping of the OBJECT-GROUP macro ...........................    9
   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 ............................   10
   3.5 Mapping of the OBJECT-GROUP value ..........................   10
   3.6 Usage Example ..............................................   11
   4. Mapping of the NOTIFICATION-GROUP macro .....................   11
   4.1 Mapping of the NOTIFICATIONS clause ........................   11
   4.2 Mapping of the STATUS clause ...............................   11
   4.3 Mapping of the DESCRIPTION clause ..........................   12
   4.4 Mapping of the REFERENCE clause ............................   12
   4.5 Mapping of the NOTIFICATION-GROUP value ....................   12
   4.6 Usage Example ..............................................   12
   5. Mapping of the MODULE-COMPLIANCE macro ......................   12
   5.1 Mapping of the STATUS clause ...............................   13



SNMPv2 Working Group        Standards Track                     [Page 1]

RFC 1904           Conformance Statements for SNMPv2        January 1996


   5.2 Mapping of the DESCRIPTION clause ..........................   13
   5.3 Mapping of the REFERENCE clause ............................   13
   5.4 Mapping of the MODULE clause ...............................   13
   5.4.1 Mapping of the MANDATORY-GROUPS clause ...................   13
   5.4.2 Mapping of the GROUP clause ..............................   14
   5.4.3 Mapping of the OBJECT clause .............................   14
   5.4.3.1 Mapping of the SYNTAX clause ...........................   14
   5.4.3.2 Mapping of the WRITE-SYNTAX clause .....................   15
   5.4.3.3 Mapping of the MIN-ACCESS clause .......................   15
   5.4.4 Mapping of the DESCRIPTION clause ........................   15
   5.5 Mapping of the MODULE-COMPLIANCE value .....................   15
   5.6 Usage Example ..............................................   16
   6. Mapping of the AGENT-CAPABILITIES macro .....................   16
   6.1 Mapping of the PRODUCT-RELEASE clause ......................   17
   6.2 Mapping of the STATUS clause ...............................   17
   6.3 Mapping of the DESCRIPTION clause ..........................   17
   6.4 Mapping of the REFERENCE clause ............................   17
   6.5 Mapping of the SUPPORTS clause .............................   18
   6.5.1 Mapping of the INCLUDES clause ...........................   18
   6.5.2 Mapping of the VARIATION clause ..........................   18
   6.5.2.1 Mapping of the SYNTAX clause ...........................   18
   6.5.2.2 Mapping of the WRITE-SYNTAX clause .....................   18
   6.5.2.3 Mapping of the ACCESS clause ...........................   19
   6.5.2.4 Mapping of the CREATION-REQUIRES clause ................   19
   6.5.2.5 Mapping of the DEFVAL clause ...........................   20
   6.5.2.6 Mapping of the DESCRIPTION clause ......................   20
   6.6 Mapping of the AGENT-CAPABILITIES value ....................   20
   6.7 Usage Example ..............................................   20
   7. Extending an Information Module .............................   22
   7.1 Conformance Groups .........................................   22
   7.2 Compliance Definitions .....................................   22
   7.3 Capabilities Definitions ...................................   22
   8. Security Considerations .....................................   23
   9. Editor's Address ............................................   23
   10. Acknowledgements ...........................................   23
   11. References .................................................   24

1.  Introduction

   A 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
   authentication, authorization, access control, and privacy policies.





SNMPv2 Working Group        Standards Track                     [Page 2]

RFC 1904           Conformance Statements for SNMPv2        January 1996


   Management stations execute management applications which monitor and
   control managed elements.  Managed elements are devices such as
   hosts, routers, terminal servers, etc., which are monitored and
   controlled via 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 (STD 16), 1157 (STD
   15), and 1212 (STD 16), is termed the SNMP version 1 framework
   (SNMPv1).  The current framework is termed the SNMP version 2
   framework (SNMPv2).

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 ::=



SNMPv2 Working Group        Standards Track                     [Page 3]

RFC 1904           Conformance Statements for SNMPv2        January 1996


                  value(Name ObjectName)

    Status ::=
                  "current"
                | "deprecated"
                | "obsolete"

    ReferPart ::=
                  "REFERENCE" Text
                | empty

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


-- more definitions for conformance groups

NOTIFICATION-GROUP MACRO ::=
BEGIN
    TYPE NOTATION ::=
                  NotificationsPart
                  "STATUS" Status
                  "DESCRIPTION" Text
                  ReferPart

    VALUE NOTATION ::=
                  value(VALUE OBJECT IDENTIFIER)

    NotificationsPart ::=
                  "NOTIFICATIONS" "{" Notifications "}"
    Notifications ::=
                  Notification
                | Notifications "," Notification
    Notification ::=
                  value(Name NotificationName)

    Status ::=
                  "current"
                | "deprecated"
                | "obsolete"

    ReferPart ::=
                  "REFERENCE" Text
                | empty

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



SNMPv2 Working Group        Standards Track                     [Page 4]

RFC 1904           Conformance Statements for SNMPv2        January 1996


END


-- definitions for compliance statements

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

    VALUE NOTATION ::=
                  value(VALUE OBJECT IDENTIFIER)

    Status ::=
                  "current"
                | "deprecated"
                | "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 "}"



SNMPv2 Working Group        Standards Track                     [Page 5]

RFC 1904           Conformance Statements for SNMPv2        January 1996


                | empty

    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"
                | "accessible-for-notify"
                | "read-only"
                | "read-write"