[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00

Internet Draft                                            Dan Romascanu
                                                     Lucent Technologies
                                                             10 May 1999

                 Remote Monitoring MIB Extensions for
                   Interface Parameters Monitoring

              <draft-romascanu-rmonmib-iftopn-mib-00.txt>

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.


   Copyright Notice

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

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   The document proposes an extension to the Remote Monitoring MIB [17]
   with a method of sorting the interfaces of a monitored device
   according to values of parameters specific to this interface.

   Distribution of this memo is unlimited.

Table of Contents

   Status of this Memo                                             1
   Abstract                                                        1
    1 Introduction                                                 2
    2 The SNMP Management Framework                                2
    3 Overview                                                     3

D.Romascanu               Expires November 1999                 [Page 1]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

    4 MIB Structure                                                4
    5 Limitations and Future Work                                  4
    6 Definitions                                                  5
    7 References                                                  14
    8 Intellectual Property                                       17
    9 Security Considerations                                     17
    10 Author's Address                                           18
    A Full Copyright Statement                                    18

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 defines a method of sorting the interfaces of a
   monitored device according to values of parameters specific to this
   interface.

   This memo also includes a MIB module.  This MIB module extends the
   list of managed objects specified in [17] and [18].

   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 [20].

2.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o   An overall architecture, described in RFC 2271 [1].

   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
       RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version,
       called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC
       1904 [7].

   o   Message protocols for transferring management information. The
       first version of the SNMP message protocol is called SNMPv1 and
       described in RFC 1157 [8]. A second version of the SNMP message
       protocol, which is not an Internet standards track protocol, is
       called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
       The third version of the message protocol is called SNMPv3 and
       described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].

   o   Protocol operations for accessing management information. The
       first set of protocol operations and associated PDU formats is

D.Romascanu               Expires November 1999                 [Page 2]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

       described in RFC 1157 [8]. A second set of protocol operations
       and associated PDU formats is described in RFC 1905 [13].

   o   A set of fundamental applications described in RFC 2273 [14] and
       the view-based access control mechanism described in RFC 2275
       [15].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2. A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations. The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64). Some machine readable
   information in SMIv2 will be converted into textual descriptions in
   SMIv1 during the translation process. However, this loss of machine
   readable information is not considered to change the semantics of the
   MIB.

   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 RFC2119 [16].

3. Overview

   This document continues the architecture created in the RMON MIB [17]
   and extended by the SMON MIB [18], by providing a method of ordering
   the interfaces of a device according to the value of a specific
   parameter that characterizes the interfaces.

   The need for such a technique derives from the evolution of the
   network devices - bridges / switches, routers, etc. into complex
   entities with a large number of interfaces and with many parameters
   that need to be monitored on each interface. It is common for certain
   classes of switching devices to contain hundred of ports, and for
   each port to instrument and support tens of parameters - usually
   expressed as counters - for each interface. As a result, it becomes
   impossible for applications that monitor these devices to provide a
   view that would allow the user to understand easily what is the
   status of the device, whether the behavior of a port or interface is
   in normal boundaries or not, and which are the most congested or
   problematic interfaces of the device.

   This document tries to answer this problem, by proposing a method of
   providing a sorted list of interfaces, according to programmable
   criteria. The result of applying this method will be a shorter list,

D.Romascanu               Expires November 1999                 [Page 3]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

   that includes the most significant interfaces sorted according to the
   selected criteria. One possible action that can be taken by a network
   manager could be applying to this interface a copy port operation, to
   a destination port that has a dedicated monitoring device (e.g. a
   network analyzer) connected to it. A standard MIB interface for
   performing this operation is described in [18].

4. MIB Structure

   This MIB contains one MIB group, with two tables:

    - The interfaceTopNControlTable

    - The interfaceTopNTable

   The interfaceControlTable is an RMON-style control table, allowing
   for the creation of interfaceTopN reports. The parameters specific
   for each report, like the duration of the report, the number of
   reports, start time and the characteristics of the variables that are
   sorted (absolute or 'deltas') are set in this table. An optional
   operation that is controlled from this table is the normalization of
   values of the variables, which allows for sorting of variables on the
   interfaces, despite the basic speed of the interfaces being different
   on different interfaces.

   The interfaceTopNTable provides the results in a table associated
   with the control entries.

5. Limitations and Future Work

   The objects whose values are used as criteria for sorting are
   elements in tables indexed by an InterfaceIndex type of object, as
   defined in [19] and [20]. This approach simplifies the search
   algorithm and the result table, but restricts the method to interface
   parameters. A more generic 'usrTopN' function is out of the scope of
   this document and may be the object of future investigations and
   future work.

   The values of the variables sorted in the InterfaceTopN table are
   ASN.1 Integer32 variables (Integer32, Counter, Gauge, or TimeTicks).
   This might be insufficient for higher speed interfaces. The lack of a
   'Gauge64' type of object in SMIv2, makes a straight-forward
   implementation of support for higher speed impossible.

D.Romascanu               Expires November 1999                 [Page 4]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

6. Definitions

   INTERFACETOPN-MIB DEFINITIONS ::= BEGIN

      IMPORTS
           MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, Gauge32
                   FROM SNMPv2-SMI
           RowStatus, TimeStamp, TEXTUAL-CONVENTION
                   FROM SNMPv2-TC
           rmon, OwnerString
                   FROM RMON-MIB
           rmonConformance, probeConfig
                   FROM RMON2-MIB
           MODULE-COMPLIANCE, OBJECT-GROUP
                   FROM SNMPv2-CONF;

      interfaceTopNMIB MODULE-IDENTITY
           LAST-UPDATED "9905090000Z"
           ORGANIZATION "Lucent Technologies"
           CONTACT-INFO
           "

                   Dan Romascanu
                   Lucent Technologies
                   Tel:  +972-3-645-8414
                   Email: dromasca@lucent.com"

          DESCRIPTION
                   "The MIB module for sorting device interfaces for RMON
and
                   SMON monitoring in a multiple device implementation."
           ::= { rmon 23 }

   interfaceTopNObjects       OBJECT IDENTIFIER ::= { interfaceTopNMIB 1 }
   interfaceTopNNotifications OBJECT IDENTIFIER ::= { interfaceTopNMIB 2 }
   interfaceTopNConformance   OBJECT IDENTIFIER ::= { interfaceTopNMIB 3 }

      -- The Interface Top N group is used to prepare reports that
      -- describe a list of interfaces (data sources)
      -- ordered by the values of one
      -- of the objects that apply to the interfaces of the respective
device.
      -- Those objects may be part of the standard MIBs, enterprise specific
      -- extensions MIBs, or defined by means of the Expression MIB [21].
      -- The objects must be elements in tables indexed only by an
      -- InterfaceIndex object.
      -- The objects  chosen by the
      -- management station may be sampled over a management
      -- station-specified time interval, making the report rate based.

D.Romascanu               Expires November 1999                 [Page 5]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

      -- The management station also specifies the number of interfaces
      -- that are reported.
      --
      -- The interfaceTopNControlTable is used to initiate the generation
      -- of a report.  The management station may select the parameters
      -- of such a report, such as which object, how
      -- many interfaces, and the start & stop times of the sampling.  When
      -- the report is prepared, entries are created in the
      -- interfaceTopNTable associated with the relevant
      -- interfaceTopNControlEntry.  These entries are static for
      -- each report after it has been prepared.

     interfaceTopNControlTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF InterfaceTopNControlEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
              "A table of control records for reports on the top `N'
              interfaces for the value or rate of a selected object.
              The number of entries depends on the configuration of the
agent.
              The maximum number of entries is implementation
              dependent."
          ::= { interfaceTopNObjects 1 }

      interfaceTopNControlEntry OBJECT-TYPE
          SYNTAX      InterfaceTopNControlEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
                  "A set of parameters that control the creation of a
                  report of the top N ports according to several metrics."
          INDEX    { interfaceTopNControlIndex }
          ::= { interfaceTopNControlTable 1 }

      InterfaceTopNControlEntry ::= SEQUENCE {
          interfaceTopNControlIndex
              Integer32,
          interfaceTopNObjectVariable
              OBJECT IDENTIFIER,
          InterfaceTopNObjectSampleType
              INTEGER,
          interfaceTopNNormalization
              INTEGER,
          interfaceTopNNormalizationFactor
              INTEGER,
          interfaceTopNControlGeneratedReports
              Counter32,

D.Romascanu               Expires November 1999                 [Page 6]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

          interfaceTopNTimeRemaining
              Integer32,
          interfaceTopNDuration
              Integer32,
          interfaceTopNRequestedSize
              Integer32,
          interfaceTopNGrantedSize
              Integer32,
          interfaceTopNStartTime
              TimeStamp,
          interfaceTopNOwner
              OwnerString,
          interfaceTopNRowStatus
              RowStatus
      }

      interfaceTopNControlIndex OBJECT-TYPE
          SYNTAX      Integer32 (1 .. 65535)
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
                  "An index that uniquely identifies an entry in the
                  interfaceTopNControl table.  Each such entry defines
                  one top N report prepared for a probe."
          ::= { interfaceTopNControlEntry 1 }

   interfaceTopNObjectVariable OBJECT-TYPE
       SYNTAX OBJECT IDENTIFIER
       MAX-ACCESS read-create
       STATUS current
       DESCRIPTION
           "The object identifier of the particular variable to be
           sampled.

           Only variables that resolve to an ASN.1 primitive type of
           Integer32 (Integer32, Counter, Gauge, or TimeTicks) may be
           sampled.

           Only variables belonging to tables indexed uniquely by an
           object of the type InterfaceIndex may be sampled.

           Because SNMP access control is articulated entirely in terms
           of the contents of MIB views, no access control mechanism
           exists that can restrict the value of this object to identify
           only those objects that exist in a particular MIB view.
           Because there is thus no acceptable means of restricting the
           read access that could be obtained through the TopN

D.Romascanu               Expires November 1999                 [Page 7]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

           mechanism, the probe must only grant write access to this
           object in those views that have read access to all objects on
           the probe.

           During a set operation, if the supplied variable name is not
           available in the selected MIB view, or does not conform the
           other conditions mentioned above, a badValue error must be
           returned.

           This object may not be modified if the associated
           interfaceTopNControlStatus object is equal to active(1)."
       ::= { interfaceTopNControlEntry 2 }

   interfaceTopNObjectSampleType OBJECT-TYPE
       SYNTAX INTEGER {
                  absoluteValue(1),
                  deltaValue(2)
              }
       MAX-ACCESS read-create
       STATUS current
       DESCRIPTION
           "The method of sampling the selected variable for storage in
           the interfaceTopNTable.

           If the value of this object is absoluteValue(1), the value of
           the selected variable will be copied directly into the topNValue.

           If the value of this object is deltaValue(2), the value of the
           selected variable at the last sample will be subtracted from
           the current value, and the difference will be stored in
topNValue.

           This object may not be modified if the associated
           interfaceTopNControlStatus object is equal to active(1)."
       ::= { interfaceTopNControlEntry 3 }

   interfaceTopNNormalization OBJECT-TYPE
       SYNTAX INTEGER {
                  normalizationRequired(1),
                  normalizationNotRequired(2)
              }
       MAX-ACCESS read-create
       STATUS current
       DESCRIPTION
           "The method of normalization in computation of the selected
            value.

           If the value of this object is normalizationRequired(1), the
value of

D.Romascanu               Expires November 1999                 [Page 8]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

           the selected variable will be multiplied by a factor equal to the
           effective speed of the interface divided by the value of
           interfaceTopNNormalizationFactor.

           If the value of this object is normalizationNot Required(2),
           the value of the selected variable will be taken 'as is' in
           the TopN computation.

          This object may not be modified if the associated
           interfaceTopNControlStatus object is equal to active(1)."
       ::= { interfaceTopNControlEntry 4 }

   interfaceTopNNormalizationFactor OBJECT-TYPE
       SYNTAX INTEGER
       MAX-ACCESS read-create
       STATUS current
       DESCRIPTION
           "The value used for normalization if interfaceTopNNormalization
           has the value normalizationRequired(1)."
       DEFVAL { 1 }
   ::= { interfaceTopNControlEntry 5 }

   interfaceTopNControlGeneratedReports OBJECT-TYPE
       SYNTAX     Counter32
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
           "The number of reports that have been generated by this entry."
       ::= { interfaceTopNControlEntry 6 }

     interfaceTopNTimeRemaining OBJECT-TYPE
          SYNTAX      Integer32 (0..2147483647)
          MAX-ACCESS  read-create
          STATUS      current
          DESCRIPTION
                  "The number of seconds left in the report
                  currently being collected.  When this object
                  is modified by the management station, a new
                  collection is started, possibly aborting a
                  currently running report.  The new value is
                  used as the requested duration of this report,
                  which is loaded into the associated
                  interfaceTopNDuration object.

                  When this object is set to a non-zero value,
                  any associated interfaceTopNEntries shall be
                  made inaccessible by the agent.  While the value
                  of this object is non-zero, it decrements by one

D.Romascanu               Expires November 1999                 [Page 9]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

                  per second until it reaches zero.  During this
                  time, all associated interfaceTopNEntries shall
                  remain inaccessible.  At the time that this object
                  decrements to zero, the report is made accessible
                  in the interfaceTopNTable.  Thus, the interfaceTopN
                  table needs to be created only at the end of the
                  collection interval.

                  If the value of this object is set to zero
                  while the associated report is running, the
                  running report is aborted and no associated
                  interfaceTopNEntries are created."
          DEFVAL { 0 }
          ::= { interfaceTopNControlEntry 7 }

      interfaceTopNDuration OBJECT-TYPE
          SYNTAX      Integer32 (0..2147483647)
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
                  "The number of seconds that this report has
                  collected during the last sampling interval,
                  or if this report is currently being collected,
                  the number of seconds that this report is being
                  collected during this sampling interval.

                  When the associated interfaceTopNTimeRemaining
                  object is set, this object shall be set by the
                  agent to the same value and shall not be modified
                  until the next time the interfaceTopNTimeRemaining
                  is set.

                  This value shall be zero if no reports have been
                  requested for this interfaceTopNControlEntry."
          ::= { interfaceTopNControlEntry 8 }

      interfaceTopNRequestedSize OBJECT-TYPE
          SYNTAX      Integer32
          MAX-ACCESS  read-create
          STATUS      current
          DESCRIPTION
                  "The maximum number of interfaces requested
                  for the Top N Table.

                  When this object is created or modified, the
                  agent should set interfaceTopNGrantedSize as close
                  to this object as is possible for the particular
                  implementation and available resources."

D.Romascanu               Expires November 1999                [Page 10]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

          DEFVAL { 10 }
          ::= { interfaceTopNControlEntry 9 }

      interfaceTopNGrantedSize OBJECT-TYPE
          SYNTAX      Integer32 (0..65535)
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
                  "The maximum number of interfaces in the
                  top N table.

                  When the associated interfaceTopNRequestedSize object is
                  created or modified, the agent should set this object as
                  closely to the requested value as is possible for the
                  particular implementation and available resources.  The
                  agent must not lower this value except as a result of a
                  set to the associated interfaceTopNRequestedSize object."
          ::= { interfaceTopNControlEntry 10 }

      interfaceTopNStartTime OBJECT-TYPE
          SYNTAX      TimeStamp
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
                  "The value of sysUpTime when this top N report was
                  last started.  In other words, this is the time that
                  the associated interfaceTopNTimeRemaining object was
                  modified to start the requested report.

                  If the report has not yet been started, the value
                  of this object is zero."
          ::= { interfaceTopNControlEntry 11 }

      interfaceTopNOwner OBJECT-TYPE
          SYNTAX      OwnerString
          MAX-ACCESS  read-create
          STATUS      current
          DESCRIPTION
                  "The entity that configured this entry and is
                  using the resources assigned to it."
          ::= { interfaceTopNControlEntry 12 }

      interfaceTopNRowStatus OBJECT-TYPE
          SYNTAX      RowStatus
          MAX-ACCESS  read-create
          STATUS      current
          DESCRIPTION
                 "The status of this row.

D.Romascanu               Expires November 1999                [Page 11]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

                 If the value of this object is not equal to
                 active(1), all associated entries in the
                 interfaceTopNTable shall be deleted by the
                 agent."
          ::= { interfaceTopNControlEntry 13 }

      -- Top "N" reports

      interfaceTopNTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF InterfaceTopNEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
                  "A table of reports for the top `N' ports based on
                  setting of associated control table entries. The
                  maximum number of entries depends on the number
                  of entries in table interfaceTopNControlTable and
                  the value of object interfaceTopNGrantedSize for
                  each entry.

                  For each entry in the interfaceTopNControlTable,
                  interfaces with the highest value of
                  interfaceTopNValue shall be placed in this table
                  in decreasing order of that rate until there is
                  no more room or until there are no more ports."
          ::= { interfaceTopNObjects 2 }

      interfaceTopNEntry OBJECT-TYPE
          SYNTAX      InterfaceTopNEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
                  "A set of statistics for an interface that is
                  part of a top N report."
          INDEX    { interfaceTopNControlIndex,
                     interfaceTopNIndex }
          ::= { interfaceTopNTable 1 }

      InterfaceTopNEntry ::= SEQUENCE {
          interfaceTopNIndex
              Integer32,
          interfaceTopNDataSourceIndex
              Integer32,
          interfaceTopNValue
              Gauge32
      }

D.Romascanu               Expires November 1999                [Page 12]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

      interfaceTopNIndex OBJECT-TYPE
          SYNTAX      Integer32 (1..65535)
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
                  "An index that uniquely identifies an entry in
                  the interfaceTopN table among those in the same
                  report.  This index is between 1 and N, where N
                  is the number of entries in this report.  Increasing
                  values of interfaceTopNIndex shall be assigned to
                  entries with decreasing values of interfaceTopNValue
                  until index N is assigned to the entry with the
                  lowest value of interfaceTopNValue or there are no
                  more interfaceTopNEntries.

                  No ports are included in a report where their
                  value of interfaceTopNValue would be zero."
          ::= { interfaceTopNEntry 1 }

      interfaceTopNDataSourceIndex OBJECT-TYPE
          SYNTAX      Integer32  (1..2147483647)
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
                  "This object identifies the index corresponding
                   to the dataSource for this entry."
          ::= { interfaceTopNEntry 2 }

      interfaceTopNValue OBJECT-TYPE
          SYNTAX      Gauge32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
                  "The value at the end of the sampling interval, or
                  the amount of change in the selected variable
                  during this sampling interval for the identified
                  interface.  The selected variable is that interfaces's
                  instance of the object selected by
                  interfaceTopNObjectVariable."
          ::= { interfaceTopNEntry 3 }

   --
   -- Notifications Section
   -- (none defined)
   --

   --
   -- Conformance Section

D.Romascanu               Expires November 1999                [Page 13]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

   --

   interfaceTopNCompliances OBJECT IDENTIFIER ::= { interfaceTopNConformance
1 }
   interfaceTopNGroups      OBJECT IDENTIFIER ::= { interfaceTopNConformance
2 }

   interfaceTopNCompliance MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
               "Describes the requirements for conformance to the
               InterfaceTopN MIB."
   MODULE  -- this module
           MANDATORY-GROUPS { interfaceTopNGroup }
        ::= { interfaceTopNCompliances 1 }

   interfaceTopNGroup OBJECT-GROUP
       OBJECTS {
          interfaceTopNControlIndex,
          interfaceTopNObjectVariable,
          interfaceTopNObjectSampleType,
          interfaceTopNNormalization,
          interfaceTopNNormalizationFactor,
          interfaceTopNControlGeneratedReports,
          interfaceTopNTimeRemaining,
          interfaceTopNDuration,
          interfaceTopNRequestedSize,
          interfaceTopNGrantedSize,
          interfaceTopNStartTime,
          interfaceTopNOwner,
          interfaceTopNRowStatus,
          interfaceTopNIndex,
          interfaceTopNDataSourceIndex,
          interfaceTopNValue
       }
       STATUS  current
       DESCRIPTION
               "A collection of objects providing interfaceTopN data for
               a multiple interfaces device."
   ::= { interfaceTopNGroups 1 }

   END

7. References

D.Romascanu               Expires November 1999                [Page 14]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

       [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
           Describing SNMP Management Frameworks", RFC 2271, Cabletron
           Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
           January 1998

       [2] Rose, M., and K. McCloghrie, "Structure and Identification of
           Management Information for TCP/IP-based Internets", STD 16,
           RFC 1155, Performance Systems International, Hughes LAN Systems,
           May 1990

       [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
           RFC 1212, Performance Systems International, Hughes LAN Systems,

       [4] M. Rose, "A Convention for Defining Traps for use with the
           SNMP", RFC 1215, Performance Systems International, March 1991

       [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
           "Structure of Management Information for Version 2 of the Simple
           Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research,
           Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
           International Network Services, January 1996.

       [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
           Conventions for Version 2 of the Simple Network Management
           Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco
           Systems, Inc., Dover Beach Consulting, Inc., International
           Network Services, January 1996.

       [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
           "Conformance Statements for Version 2 of the Simple Network
           Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc.,
           Cisco Systems, Inc., Dover Beach Consulting, Inc., International
           Network Services, January 1996.

       [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
           Network Management Protocol", STD 15, RFC 1157, SNMP Research,
           Performance Systems International, Performance Systems
           International, MIT Laboratory for Computer Science, May 1990.

       [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
           "Introduction to Community-based SNMPv2", RFC 1901, SNMP
           Research, Inc., Cisco Systems, Inc., Dover Beach Consulting,
           Inc., International Network Services, January 1996.

      [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
           "Transport Mappings for Version 2 of the Simple Network
           Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc.,
           Cisco Systems, Inc., Dover Beach Consulting, Inc., International

D.Romascanu               Expires November 1999                [Page 15]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

           Network Services, January 1996.

      [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
           Processing and Dispatching for the Simple Network Management
           Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron
           Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
           January 1998.

      [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
           for version 3 of the Simple Network Management Protocol
           (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998.

      [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
           Operations for Version 2 of the Simple Network Management
           Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco
           Systems, Inc., Dover Beach Consulting, Inc., International
           Network Services, January 1996.

      [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
           2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
           Systems, January 1998

      [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
           Control Model (VACM) for the Simple Network Management Protocol
           (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software,
           Inc., Cisco Systems, Inc., January 1998

      [16] Bradner, S., "Key words for use in RFCs to Indicate Requirement
           Levels", BCP 14, RFC 2119, Harvard University, March 1997.

      [17] Waldbusser, S., "Remote Network Monitoring Management
           Information Base", RFC 1757, Carnegie Mellon University,
           February 1995

      [18] Waterman, R., Lahaye, B., Romascanu, D., and S. Waldbusser,
"Remote
           Network Monitoring MIB Extensions for Switched Networks, Version
           1.0", Internet-Draft, February 1999

      [19] McCloghrie, K., and M. Rose, Editors, "Management Information
           Base for Network Management of TCP/IP-based internets: MIB-II",
           STD 17, RFC 1213, Hughes LAN Systems, Performance Systems
           International, March 1991.

      [20] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB
           using SMIv2", RFC 2233, Cisco Systems, FTP Software, November
           1997.

      [21] Stewart B., "Distributed Management Expression MIB",
Internet-Draft,

D.Romascanu               Expires November 1999                [Page 16]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

           February 1999

8. Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.

9.  Security Considerations

   There are a number of management objects defined in this MIB
   that have a MAX-ACCESS clause of read-write and/or read-create.
   Such objects may be considered sensitive or vulnerable in some
   network environments.  The support for SET operations in a
   non-secure environment without proper protection can have a
   negative effect on network operations.

   There are a number of managed objects in this MIB that may
   contain sensitive information. These are:
       interfaceTopNDataSourceIndex
       intefaceTopNValue

   It is thus important to control even GET access to these objects
   and possibly to even encrypt the values of these object when
   sending them over the network via SNMP.  Not all versions of
   SNMP provide features for such a secure environment.

   SNMPv1 by itself is not a secure environment.  Even if the
   network itself is secure (for example by using IPSec), even then,
   there is no control as to who on the secure network is allowed

D.Romascanu               Expires November 1999                [Page 17]


INTERNET DRAFT              InterfaceTopN MIB                   May 1999

   to access and GET/SET (read/change/create/delete) the objects in
   this MIB.

   It is RECOMMENDED that the implementers consider the security
   features as provided by the SNMPv3 framework.  Specifically, the
   use of the User-based Security Model RFC 2274 [12] and the
   View-based Access Control Model RFC 2275 [15] is RECOMMENDED.

   It is then a customer/user responsibility to ensure that the SNMP
   entity giving access to an instance of this MIB, is properly
   configured to give access to the objects only to those
   principals (users) that have legitimate rights to indeed GET or
   SET (change/create/delete) them.

10.  Author's Address

        Dan Romascanu
        Lucent Technologies
        Atidim Technology Park, Bldg. #3
        Tel Aviv, 61131
        Israel
        Tel: +972-3-645-8414
        Email: dromasca@lucent.com

   A.  Full Copyright Statement

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION

D.Romascanu               Expires November 1999                [Page 18]

INTERNET DRAFT              InterfaceTopN MIB                   May 1999

   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/