Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
RFC 2325

Document Type RFC - Informational (April 1998; Errata)
Last updated 2014-05-22
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 2325 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       M. Slavitch
Request for Comments: 2325                      Loran Technologies Inc.
Category: Informational                                    1 April 1998

      Definitions of Managed Objects for Drip-Type Heated Beverage
                      Hardware Devices using SMIv2

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

Table of Contents

   1. Introduction ...............................................    1
   2. The SNMPv2 Network Management Framework ....................    1
   2.1 Object Definitions ........................................    2
   3. Overview ...................................................    2
   3.1 Relationship to Interface MIB .............................    2
   4. Definitions ................................................    3
   5. Acknowledgements ...........................................    6
   6. References .................................................    6
   7. Security Considerations ....................................    6
   8. Author's Address ...........................................    7
   9. Full Copyright Statement ...................................    8

1.  Introduction

   This memo defines an extension to the Management Information Base
   (MIB) for use with network management protocols in the Internet
   community.  In particular, it defines objects for the management of
   coffee-brewing and maintenance devices.

2.  The SNMPv2 Network Management Framework

   The SNMPv2 Network Management Framework consists of four major
   components.  They are:

      o    RFC 1442 [1] which defines the SMI, the mechanisms used for
           describing and naming objects for the purpose of management.

Slavitch                     Informational                      [Page 1]
RFC 2325                         CP MIB                     1 April 1998

      o    STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
           objects for the Internet suite of protocols.

      o    RFC 1445 [3] which defines the administrative and other
           architectural aspects of the framework.

      o    RFC 1448 [4] which defines the protocol used for network
           access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

2.1.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object object type is named
   by an OBJECT IDENTIFIER, an administratively assigned name.  The
   object type together with an object instance serves to uniquely
   identify a specific instantiation of the object.  For human
   convenience, we often use a textual string, termed the descriptor, to
   refer to the object type.

3.  Overview

   The COFFEE POT MIB applies to managed devices that brew, store, and
   deliver heated coffee beverages. The COFFEE POT MIB is mandatory for
   all systems that have such a hardware port supporting services
   managed through some other MIB.

   The MIB contains objects that relate to physical connections,
   configuration, storage levels, availabilty, quality of service, and
   availability.

3.1.  Relationship to Interface MIB

   The COFFEE-POT-MIB is one of many MIBs designed for layered use as
   described in the Interface MIB [5].  In most implementations where it
   is present, it will be in the lowest interface sublayer, that is, the
   COFFEE-POT-MIB represents the physical layer, providing service to
   higher layers such as the Character MIB [6].

   Although it is unlikely that a coffee port will actually be used as a
   network interface, which is the intent of the Interface MIB, the
   COFFEE-POT-MIB is closely connected to the Character MIB, which can
   share hardware interfaces with network operation, and relate to the
   RS-232 MIB [7].

Slavitch                     Informational                      [Page 2]
RFC 2325                         CP MIB                     1 April 1998

   The Interface MIB's ifTestTable and ifRcvAddressTable are not
   relevant to the COFFEE-POT-MIB.

   The COFFEE-POT-MIB is relevant for ifType values sip(31), and perhaps
   others.

   The COFFEE-POT-MIB requires the conformance groups ifGeneralGroup,
   and ifFixedLengthGroup.

   Usefulness of error counters in this MIB depends on the octet
   counters in ifFixedLengthGroup.

4.  Definitions

   COFFEE-POT-MIB DEFINITIONS ::= BEGIN

   IMPORTS
       MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
       TimeStamp, TimeInterval,
       Counter32, Integer32
Show full document text