Definitions of Managed Objects for the Ethernet-like Interface Types
RFC 1623

Document Type RFC - Historic (May 1994; No errata)
Obsoleted by RFC 1643
Obsoletes RFC 1398
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state RFC 1623 (Historic)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      F. Kastenholz
Request for Comments: 1623                            FTP Software, Inc.
Obsoletes: 1398                                                 May 1994
STD: 50
Category: Standards Track

                   Definitions of Managed Objects for
                   the Ethernet-like Interface Types

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

   Introduction .............................................    1
   1. The SNMP Network Management Framework .................    2
   1.1 Object Definitions ...................................    2
   2. Change Log ............................................    2
   3. Overview ..............................................    3
   3.1 Relation to RFC 1213 .................................    4
   3.2 Relation to RFC 1573 .................................    4
   3.2.1 Layering Model .....................................    4
   3.2.2 Virtual Circuits ...................................    4
   3.2.3 ifTestTable ........................................    4
   3.2.4 ifRcvAddressTable ..................................    5
   3.2.5 ifPhysAddress ......................................    5
   3.2.6 ifType .............................................    6
   4. Definitions ...........................................    6
   5. Acknowledgements ......................................   16
   6. References ............................................   17
   7. Security Considerations ...............................   19
   8. Author's Address ......................................   19

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

Kastenholz                                                      [Page 1]
RFC 1623                   Ethernet-Like MIB                    May 1994

1.  The SNMP Network Management Framework

   The SNMP Network Management Framework consists of three major
   components.  They are:

      o    STD 16/RFC 1155 [3] which defines the SMI, the mechanisms
           used for describing and naming objects for the purpose of
           management.  STD 16/RFC 1212 [13] defines a more concise
           description mechanism, which is wholly consistent with
           the SMI.

      o    RFC 1156 [4] which defines MIB-I, the core set of managed
           objects for the Internet suite of protocols.  STD 17/RFC
           1213 [6] defines MIB-II, an evolution of MIB-I based on
           implementation experience and new operational
           requirements.

      o    STD 15/RFC 1157 [5] which defines the SNMP, the protocol
           used for network access to managed objects.

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

1.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.

2.  Change Log

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

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

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

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

Kastenholz                                                      [Page 2]
RFC 1623                   Ethernet-Like MIB                    May 1994

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

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

    (6)   Several minor editorial changes, spelling corrections,
          grammar and punctuation corrections, and so forth, were
Show full document text