RFC 3231 (rfc3231) - Page 2 of 29


Definitions of Managed Objects for Scheduling Management Operations



Alternative Format: Original Text Document

< Previous
Next >



RFC 3231                      Schedule MIB                  January 2002


   6 Security Considerations ......................................   23
   7 Intellectual Property ........................................   25
   8 Changes from RFC 2591 ........................................   25
   9 Acknowledgments ..............................................   26
   10 References ..................................................   26
   11 Editors' Addresses ..........................................   28
   12 Full Copyright Statement ....................................   29

1.  Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes a set of managed objects that are used to
   schedule management operations periodically or at specified dates and
   times.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC 2119].

2.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o  An overall architecture, described in RFC 2571 [RFC 2571].

   o  Mechanisms for describing and naming objects and events for the
      purpose of management.  The first version of this Structure of
      Management Information (SMI) is called SMIv1 and described in STD
      16, RFC 1155 [RFC 1155], STD 16, RFC 1212 [RFC 1212] and RFC 1215
      [RFC 1215].  The second version, called SMIv2, is described in STD
      58, RFC 2578 [RFC 2578], STD 58, RFC 2579 [RFC 2579] and STD 58, RFC
      2580 [RFC 2580].

   o  Message protocols for transferring management information.  The
      first version of the SNMP message protocol is called SNMPv1 and
      described in STD 15, RFC 1157 [RFC 1157].  A second version of the
      SNMP message protocol, which is not an Internet standards track
      protocol, is called SNMPv2c and described in RFC 1901 [RFC 1901]
      and RFC 1906 [RFC 1906].  The third version of the message protocol
      is called SNMPv3 and described in RFC 1906 [RFC 1906], RFC 2572
      [RFC 2572] and RFC 2574 [RFC 2574].








Levi & Schoenwaelder        Standards Track


< Previous
Next >


Web Standards & Support:

Link to and support eLook.org Powered by LoadedWeb Web Hosting
Valid XHTML 1.0! Valid CSS! eLook.org FireFox Extensions