Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2
RFC 1650

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Network Working Group                                      F. Kastenholz
Request for Comments: 1650                            FTP Software, Inc.
Category: Standards Track                                    August 1994

                  Definitions of Managed Objects for
             the Ethernet-like Interface Types using SMIv2

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 ..........................................    1
   2. The SNMPv2 Network Management Framework ...............    2
   2.1 Object Definitions ...................................    2
   3. Change Log ............................................    2
   4. Overview ..............................................    3
   4.1 Relation to RFC 1213 .................................    4
   4.2 Relation to RFC 1573 .................................    4
   4.2.1 Layering Model .....................................    4
   4.2.2 Virtual Circuits ...................................    4
   4.2.3 ifTestTable ........................................    4
   4.2.4 ifRcvAddressTable ..................................    5
   4.2.5 ifPhysAddress ......................................    5
   4.2.6 ifType .............................................    6
   5. Definitions ...........................................    6
   6. Acknowledgements ......................................   18
   7. References ............................................   19
   8. Security Considerations ...............................   20
   9. Author's Address ......................................   20

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 objects for managing ethernet-like objects.

   This memo also includes a MIB module.  This MIB module corrects minor
   errors in the earlier version of this MIB: RFC 1398 [15] and also
   re-specifies that MIB in a manner which is both compliant to the
   SNMPv2 SMI and semantically-identical to the existing SNMPv1-based
   definitions.

Kastenholz                                                      [Page 1]
RFC 1650                   Ethernet-Like MIB                 August 1994

2.  The SNMPv2 Network Management Framework

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

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

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

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

      o    RFC 1448 [18] 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) [7]
   defined in the SMI [16].  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.  Change Log

   This section enumerates changes made to RFC 1398 to produce this
   document.

      (1)   The "boilerplate" was changed to reflect the new
            boilerplate for SNMPv2.

      (2)   A section describing the applicability of various parts
            of RFC 1573 to ethernet-like interfaces has been added.

      (3)   A minor error in the description of the TDR test was
            fixed.

Kastenholz                                                      [Page 2]
RFC 1650                   Ethernet-Like MIB                 August 1994

      (4)   A loopback test was defined to replace the standard
            loopback test that was defined in RFC 1229.

      (5)   The description of dot3CollFrequencies was made a bit
            clearer.

      (6)   A new object, EtherChipset, has been added. This object
            replaces the ifExtnsChipSet object, which has been
            removed per the Interface MIB Evolution effort.

      (7)   Several minor editorial changes, spelling corrections,