RFC 1623
Definitions of Managed Objects for the Ethernet-like Interface Types
RFC 1623: Definitions of Managed Objects for the Ethernet-like Interface Types 🎀
okay bestie, let's get the basics out of the way first 💅 This one is STD 50 on the Standards Track, written by F. Kastenholz of FTP Software, Inc. and dated May 1994. It's a Network Working Group doc, and it obsoletes RFC 1398. It doesn't say it updates anything.
Status of this Memo 📜
So this document is a standards track protocol spec for the Internet community, and it's asking for discussion and suggestions to make it better 🫶 For the current standardization state and status, check the current edition of "Internet Official Protocol Standards" (STD 1). 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 ...................................... 19Introduction ✨
This memo defines a chunk of the Management Information Base (MIB) that network management protocols use across the Internet community 🦋 It's specifically about objects for managing ethernet-like stuff.
This memo also includes a MIB module 💜 It fixes some minor mistakes in the earlier version of this MIB, which is RFC 1398 [15].
1. The SNMP Network Management Framework 🌸
okay so the SNMP Network Management Framework is made of three big pieces:
- STD 16/RFC 1155 [3] defines the SMI, which is the stuff used to describe and name objects for management purposes. STD 16/RFC 1212 [13] gives a more concise way to describe things, and it's totally consistent with the SMI.
- RFC 1156 [4] defines MIB-I, the core set of managed objects for the Internet suite of protocols. STD 17/RFC 1213 [6] defines MIB-II, which is basically MIB-I glowed up using implementation experience and new operational requirements 💅
- STD 15/RFC 1157 [5] defines SNMP, the protocol used for network access to managed objects.
The Framework lets people define new objects for experimentation and evaluation 🧪
1.1. Object Definitions 🍓
Managed objects are accessed through a virtual information store called the Management Information Base, or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [7] that's defined in the SMI [16]. Each object type gets named by an OBJECT IDENTIFIER, which is an administratively assigned name. The object type together with an object instance uniquely identifies one specific instantiation of the object. For human convenience, we often use a textual string, called the descriptor, to refer to the object type 🤓
2. Change Log 📝
This section lists the changes made to RFC 1398 to get to this document.
- A section describing how various parts of RFC 1573 apply to ethernet-like interfaces was added 🙌
- A minor error in the description of the TDR test was fixed 🔧
- A loopback test was defined to replace the standard loopback test that was defined in RFC 1229 🔁
- The description of dot3CollFrequencies was made a bit clearer 💡
- A new object, EtherChipset, was added. It replaces the ifExtnsChipSet object, which got removed per the Interface MIB Evolution effort 🧩
- Several minor editorial changes, spelling corrections, grammar and punctuation corrections, and so forth, were made ✏️
3. Overview 🦋
Instances of these object types represent attributes of an interface to an ethernet-like communications medium. Right now, ethernet-like media are identified by three values of the ifType object in the Internet-standard MIB:
ethernet-csmacd(6)
iso88023-csmacd(7)
starLan(11)For these interfaces, the value of the ifSpecific variable in the MIB-II [6] has the OBJECT IDENTIFIER value:
dot3 OBJECT IDENTIFER ::= { experimental 3 }The definitions here are based on the IEEE 802.3 Layer Management Specification [9], as originally interpreted by Frank Kastenholz, then of Interlan, in [10]. Anyone implementing these MIB objects should know that the IEEE document explicitly describes (in the form of Pascal pseudocode) when, where, and how various MAC attributes are measured 🔍 The IEEE document also describes the effects of MAC actions that can be invoked by manipulating instances of the MIB objects defined here.
Some of the attributes defined in [9] are already represented by previously defined objects in the Internet-standard MIB or in the Generic Interface Extensions MIB [11]. Those attributes are not redundantly represented by objects defined in this memo 🙅♀️ Stuff covered by objects in other memos includes the number of octets transmitted or received on a particular interface, the number of frames transmitted or received on a particular interface, the promiscuous status of an interface, the MAC address of an interface, and multicast information associated with an interface.
3.1. Relation to RFC 1213 🎀
This section only applies when this MIB is used together with the "old" (i.e., pre-RFC 1573) interface group.
The relationship between an ethernet-like interface and an interface in the context of the Internet-standard MIB is one-to-one. So the value of an ifIndex object instance can be used directly to identify the corresponding instances of the objects defined here 💖
3.2. Relation to RFC 1573 💜
RFC 1573, the Interface MIB Evolution, requires that any MIB which is an adjunct of the Interface MIB clarifies specific areas within the Interface MIB. Those areas were intentionally left vague in RFC 1573 so the MIB wouldn't over-constrain things and accidentally rule out managing certain media-types 🙈
Section 3.3 of RFC 1573 lists several areas that a media-specific MIB has to clarify. Each one gets its own subsection below. If you want the general intent behind these areas, go read RFC 1573 👀
3.2.1. Layering Model 🧱
This MIB does not provide for layering. There are no sublayers.
EDITOR'S NOTE: I could forsee the development of an 802.2 and enet-transceiver MIB. They could be higher and lower sublayers, respectively. All that THIS document should do is allude to the possibilities and urge the implementor to be aware of the possibility and that they may have requirements which supersede the requirements in this document.
3.2.2. Virtual Circuits 🚫
This medium does not support virtual circuits, so this area is not applicable to this MIB.
3.2.3. ifTestTable 🧪
This MIB defines two tests for media that are instrumented with this MIB: TDR and Loopback. Implementing these tests is not required. Lots of common interface chips don't support one or both of them 😭
These two tests are there as a convenience, so there's a common way to invoke the test.
Standard MIBs don't have objects for returning the results of the TDR test. Any needed objects MUST be provided in the vendor specific MIB 🚨
3.2.4. ifRcvAddressTable 📬
This table contains all IEEE 802.3 addresses, unicast, multicast, and broadcast, that this interface will receive packets for and forward up to a higher layer entity for local consumption. The format of the address, found in ifRcvAddressAddress, is the same as for ifPhysAddress.
If the interface is part of a MAC bridge, this table does not include unicast addresses that get accepted for possible forwarding out some other port. This table is explicitly not meant to be a bridge address filtering mechanism 🌉
3.2.5. ifPhysAddress 🏷️
This object contains the IEEE 802.3 address that gets placed in the source-address field of any Ethernet, Starlan, or IEEE 802.3 frames that originate at this interface. Usually it's stored in ROM on the interface hardware. Some systems may set this address via software.
If a system has several of these addresses, the designer has a tougher choice 😤 The address chosen should be the one most likely to be useful for network management (e.g. the address placed in ARP responses for systems which are primarily IP systems).
If the designer truly can not chose, using the factory-provided ROM address is suggested 🤷♀️
If the address can not be determined, an octet string of zero length should be returned.
The address is stored in binary in this object. It's stored in "canonical" bit order, which means the Group Bit is positioned as the low-order bit of the first octet. So the first byte of a multicast address would have the bit 0x01 set ✨
3.2.6. ifType 🌈
This MIB applies to interfaces that have any of the following three ifType values:
ethernet-csmacd(6)
iso88023-csmacd(7)
starLan(11)Interfaces with any of these ifType values map to the EtherLike-MIB in the same way. The EtherLike-MIB applies equally to all three types, and there are no implementation differences 💅
4. Definitions 💖
EtherLike-MIB DEFINITIONS ::= BEGIN
IMPORTS
Counter, Gauge FROM RFC1155-SMI
transmission FROM RFC1213-MIB
OBJECT-TYPE FROM RFC-1212;
-- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in RFC-1212.
dot3 OBJECT IDENTIFIER ::= { transmission 7 }
-- the Ethernet-like Statistics group
dot3StatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3StatsEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Statistics for a collection of ethernet-like
interfaces attached to a particular system."
::= { dot3 2 }
dot3StatsEntry OBJECT-TYPE
SYNTAX Dot3StatsEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Statistics for a particular interface to an
ethernet-like medium."
INDEX { dot3StatsIndex }
::= { dot3StatsTable 1 }okay bestie, we're deep in the Dot3StatsEntry era now 🦋 this is the table where every ethernet error gets its own little counter, and the counters are so specific it's kind of iconic 💅
First up is the SEQUENCE that lists all the columns in one row of the table ✨
Dot3StatsEntry ::= SEQUENCE {
dot3StatsIndex INTEGER,
dot3StatsAlignmentErrors Counter,
dot3StatsFCSErrors Counter,
dot3StatsSingleCollisionFrames Counter,
dot3StatsMultipleCollisionFrames Counter,
dot3StatsSQETestErrors Counter,
dot3StatsDeferredTransmissions Counter,
dot3StatsLateCollisions Counter,
dot3StatsExcessiveCollisions Counter,
dot3StatsInternalMacTransmitErrors Counter,
dot3StatsCarrierSenseErrors Counter,
dot3StatsFrameTooLongs Counter,
dot3StatsInternalMacReceiveErrors Counter
}The index comes first and it's the main character 🌸 It points at an ethernet-like interface, and it matches the same interface as ifIndex (the interface table's own index), so they line up perfectly 🫶
dot3StatsIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An index value that uniquely identifies an
interface to an ethernet-like medium. The
interface identified by a particular value of
this index is the same interface as identified
by the same value of ifIndex."
::= { dot3StatsEntry 1 }
dot3StatsAlignmentErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of frames received on a particular
interface that are not an integral number of
octets in length and do not pass the FCS check.
The count represented by an instance of this
object is incremented when the alignmentError
status is returned by the MAC service to the
LLC (or other MAC user). Received frames for
which multiple error conditions obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 2 }
dot3StatsFCSErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of frames received on a particular
interface that are an integral number of octets
in length but do not pass the FCS check.
The count represented by an instance of this
object is incremented when the frameCheckError
status is returned by the MAC service to the
LLC (or other MAC user). Received frames for
which multiple error conditions obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 3 }Okay the alignment and FCS counters are lowkey twins 👯♀️ they both look at frames that got mangled, the only difference is whether the frame was a whole number of octets or not 🙈 and if a frame has multiple problems, it only gets counted once, based on the error the LLC actually sees. no double dipping 💅
dot3StatsSingleCollisionFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of successfully transmitted frames on
a particular interface for which transmission
is inhibited by exactly one collision.
A frame that is counted by an instance of this
object is also counted by the corresponding
instance of either the ifOutUcastPkts,
ifOutMulticastPkts, or ifOutBroadcastPkts,
and is not counted by the corresponding
instance of the dot3StatsMultipleCollisionFrames
object."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 4 }
dot3StatsMultipleCollisionFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of successfully transmitted frames on
a particular interface for which transmission
is inhibited by more than one collision.
A frame that is counted by an instance of this
object is also counted by the corresponding
instance of either the ifOutUcastPkts,
ifOutMulticastPkts, or ifOutBroadcastPkts,
and is not counted by the corresponding
instance of the dot3StatsSingleCollisionFrames
object."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 5 }
dot3StatsSQETestErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of times that the SQE TEST ERROR
message is generated by the PLS sublayer for a
particular interface. The SQE TEST ERROR
message is defined in section 7.2.2.2.4 of
ANSI/IEEE 802.3-1985 and its generation is
described in section 7.2.4.6 of the same
document."
REFERENCE
"ANSI/IEEE Std 802.3-1985 Carrier Sense
Multiple Access with Collision Detection Access
Method and Physical Layer Specifications"
::= { dot3StatsEntry 6 }
dot3StatsDeferredTransmissions OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of frames for which the first
transmission attempt on a particular interface
is delayed because the medium is busy.
The count represented by an instance of this
object does not include frames involved in
collisions."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 7 }Single and multiple collisions are the ultimate frenemies 🫣 a frame that got collided with once is counted in one bucket, and a frame that got collided with more than once goes in the other, never both. And both of them also show up in the ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts counters, so the bookkeeping is very intentional 📊✨
The deferred transmissions one is about frames that had to wait their turn because the medium was busy 🧚 and collisions don't count toward it, because those frames already got their own spotlight 🌈
dot3StatsLateCollisions OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times that a collision is
detected on a particular interface later than
512 bit-times into the transmission of a
packet.
Five hundred and twelve bit-times corresponds
to 51.2 microseconds on a 10 Mbit/s system. A
(late) collision included in a count
represented by an instance of this object is
also considered as a (generic) collision for
purposes of other collision-related
statistics."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 8 }
dot3StatsExcessiveCollisions OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of frames for which transmission on a
particular interface fails due to excessive
collisions."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 9 }
dot3StatsInternalMacTransmitErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of frames for which transmission on a
particular interface fails due to an internal
MAC sublayer transmit error. A frame is only
counted by an instance of this object if it is
not counted by the corresponding instance of
either the dot3StatsLateCollisions object, the
dot3StatsExcessiveCollisions object, or the
dot3StatsCarrierSenseErrors object.
The precise meaning of the count represented by
an instance of this object is implementation-
specific. In particular, an instance of this
object may represent a count of transmission
errors on a particular interface that are not
otherwise counted."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 10 }
dot3StatsCarrierSenseErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times that the carrier sense
condition was lost or never asserted when
attempting to transmit a frame on a particular
interface.
The count represented by an instance of this
object is incremented at most once per
transmission attempt, even if the carrier sense
condition fluctuates during a transmission
attempt."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 11 }
-- { dot3StatsEntry 12 } is not assigned
dot3StatsFrameTooLongs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of frames received on a particular
interface that exceed the maximum permitted
frame size.
The count represented by an instance of this
object is incremented when the frameTooLong
status is returned by the MAC service to the
LLC (or other MAC user). Received frames for
which multiple error conditions obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 13 }
-- { dot3StatsEntry 14 } is not assigned
-- { dot3StatsEntry 15 } is not assigned
dot3StatsInternalMacReceiveErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of frames for which reception on a
particular interface fails due to an internal
MAC sublayer receive error. A frame is only
counted by an instance of this object if it is
not counted by the corresponding instance of
either the dot3StatsFrameTooLongs object, the
dot3StatsAlignmentErrors object, or the
dot3StatsFCSErrors object.
The precise meaning of the count represented by
an instance of this object is implementation-
specific. In particular, an instance of this
object may represent a count of receive errors
on a particular interface that are not
otherwise counted."
REFERENCE
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 16 }The late and excessive collisions are the drama queens of this table 😭 a late collision is one that shows up after the first 512 bit-times, which is 51.2 microseconds on a 10 Mbit/s system, and it still counts as a regular collision for the other stats too. The transmit and receive internal error counters are the catch-all buckets, and the spec is honest that their exact meaning is implementation-specific 🙈 so those numbers might cover errors that nothing else counts.
Also, slot 12 is intentionally empty (not assigned), and so are 14 and 15, so don't go looking for them 🌸 we'll pick this up in the next part 🎀
Okay bestie, the chipset object is up first. 🧚
dot3StatsEtherChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This object contains an OBJECT IDENTIFIER
which identifies the chipset used to
realize the interface. Ethernet-like
interfaces are typically built out of
several different chips. The MIB implementor
is presented with a decision of which chip
to identify via this object. The implementor
should identify the chip which is usually
called the Medium Access Control chip.
If no such chip is easily identifiable,
the implementor should identify the chip
which actually gathers the transmit
and receive statistics and error
indications. This would allow a
manager station to correlate the
statistics and the chip generating
them, giving it the ability to take
into account any known anomalies
in the chip."
::= { dot3StatsEntry 17 }Next up is the collision statistics group. Implementing it is optional, but it's a total must for any system that can actually meter collisions. 📊
-- the Ethernet-like Collision Statistics group
-- Implementation of this group is optional; it is appropriate
-- for all systems which have the necessary metering
dot3CollTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3CollEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A collection of collision histograms for a
particular set of interfaces."
::= { dot3 5 }
dot3CollEntry OBJECT-TYPE
SYNTAX Dot3CollEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A cell in the histogram of per-frame
collisions for a particular interface. An
instance of this object represents the
frequency of individual MAC frames for which
the transmission (successful or otherwise) on a
particular interface is accompanied by a
particular number of media collisions."
INDEX { ifIndex, dot3CollCount }
::= { dot3CollTable 1 }
Dot3CollEntry ::= SEQUENCE {
dot3CollCount INTEGER,
dot3CollFrequencies Counter
}
-- { dot3CollEntry 1 } is no longer in use
dot3CollCount OBJECT-TYPE
SYNTAX INTEGER (1..16)
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The number of per-frame media collisions for
which a particular collision histogram cell
represents the frequency on a particular
interface."
::= { dot3CollEntry 2 }
dot3CollFrequencies OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A count of individual MAC frames for which the
transmission (successful or otherwise) on a
particular interface occurs after the
frame has experienced exactly the number
of collisions in the associated
dot3CollCount object.
For example, a frame which is transmitted
on interface 77 after experiencing
exactly 4 collisions would be indicated
by incrementing only dot3CollFrequencies.77.4.
No other instance of dot3CollFrequencies would
be incremented in this example."
::= { dot3CollEntry 3 }Now the 802.3 tests and errors. The TDR test is the one that helps you find roughly how far away a cable fault is, and the doc says it's a good idea to run it more than once to double-check. Loopback is the other one, and it's only allowed when the interface is offline. 🔍
-- 802.3 Tests
dot3Tests OBJECT IDENTIFIER ::= { dot3 6 }
dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
-- TDR Test
-- The Time-Domain Reflectometry (TDR) test is specific
-- to ethernet-like interfaces with the exception of
-- 10BaseT and 10BaseF. The TDR value may be useful
-- in determining the approximate distance to a cable fault.
-- It is advisable to repeat this test to check for a
-- consistent resulting TDR value, to verify that there
-- is a fault.
dot3TestTdr OBJECT IDENTIFIER ::= { dot3Tests 1 }
-- A TDR test returns as its result the time interval,
-- measured in 10 MHz ticks or 100 nsec units, between
-- the start of TDR test transmission and the subsequent
-- detection of a collision or deassertion of carrier. On
-- successful completion of a TDR test, the result is
-- stored as the value of the appropriate instance of the
-- MIB object dot3TestTdrValue, and the OBJECT IDENTIFIER
-- of that instanceis stored in the corresponding instance
-- of ifExtnsTestCode (thereby indicating where the
-- result has been stored).
-- Loopback Test
-- Another test is the full-duplex loopback test.
-- This test configures the MAC chip and executes
-- an internal loopback test of memory, data paths,
-- and the MAC chip logic. This loopback test can
-- only be executed if the interface is offline.
-- Once the test has completed, the MAC chip should
-- be reinitialized for network operation, but it
-- should remain offline.
dot3TestLoopBack OBJECT IDENTIFIER ::= { dot3Tests 2 }
-- If an error occurs during a test, the object
-- ifTestResult (defined in RFC1573) will be set
-- to failed(7). The following two OBJECT
-- IDENTIFIERs may be used to provided more
-- information as values for ifTestCode.
-- couldn't initialize MAC chip for test
dot3ErrorInitError OBJECT IDENTIFIER ::= { dot3Errors 1 }
-- expected data not received (or not
-- received correctly) in loopback test
dot3ErrorLoopbackError OBJECT IDENTIFIER ::= { dot3Errors 2 }Last bit of the MIB: the chipset identifiers. RFC1573 ditched the interface chipset object, but these are kept around so older systems still work. Anything not listed here gets its OBJECT IDENTIFIER from other documentation, under the enterprise part of the registration tree (see RFC1155). 🌈
-- RFC1573 does away with the interface chipset object.
-- The following OBJECT IDENTIFIER definitions are
-- retained for purposes of backwards compatibility
-- with pre-RFC1573 systems.
-- 802.3 Hardware Chipsets
-- The object ifExtnsChipSet is provided in RFC1229 to
-- identify the MAC hardware used to communcate on an
-- interface. The following hardware chipsets are
-- provided for 802.3:
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD7990 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 1 }
dot3ChipSetAMD79900 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 2 }
dot3ChipSetAMD79C940 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 3 }
dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
dot3ChipSetIntel82586 OBJECT IDENTIFIER ::= { dot3ChipSetIntel 1 }
dot3ChipSetIntel82596 OBJECT IDENTIFIER ::= { dot3ChipSetIntel 2 }
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq8003 OBJECT IDENTIFIER ::= { dot3ChipSetSeeq 1 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational8390 OBJECT IDENTIFIER ::=
{ dot3ChipSetNational 1 }
dot3ChipSetNationalSonic OBJECT IDENTIFIER ::=
{ dot3ChipSetNational 2 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu86950 OBJECT IDENTIFIER ::=
{ dot3ChipSetFujitsu 1 }
dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
dot3ChipSetDigitalDC21040 OBJECT IDENTIFIER ::=
{ dot3ChipSetDigital 1 }
-- For those chipsets not represented above, OBJECT IDENTIFIER
-- assignment is required in other documentation, e.g., assignment
-- within that part of the registration tree delegated to
-- individual enterprises (see RFC1155).
END5. Acknowledgements ✨
This doc was cooked up by the Ethernet MIB Working Group, so huge props to them. 🫶
It's based on the Proposed Standard Ethernet MIB, RFC 1284 [14], which Jihn Cook of Chipcom edited. The Ethernet MIB Working Group gathered real implementation experience with the variables in RFC 1284 and used what they learned to build this revised MIB. 💜
RFC 1284 itself comes from a document by Frank Kastenholz of Interlan called IEEE 802.3 Layer Management Draft M compatible MIB for TCP/IP Networks [10]. This one got a light glow-up first from the SNMP Working Group and then from the Transmission Working Group, so it matches the current conventions for defining objects for MIB interfaces. James Davin of the MIT Laboratory for Computer Science and Keith McCloghrie of Hughes LAN Systems helped with later drafts. Marshall Rose of Performance Systems International, Inc. turned the document into its current concise format. 🎀 Anil Rijsinghani of DEC wrote the text that explains the TDR test better. Big thanks to Frank Kastenholz of Interlan and Louis Steinberg of IBM for running the experiments. 🦋
6. References 📚
Okay bestie, the reference list is where the whole RFC's receipts live, so every single one comes along for the ride 💅✨
- [1] Cerf, V., "IAB Recommendations for the Development of Internet Network Management Standards", RFC 1052, NRI, April 1988.
- [2] Cerf, V., "Report of the Second Ad Hoc Network Management Review Group", RFC 1109, NRI, August 1989.
- [3] 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.
- [4] McCloghrie K., and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1156, Hughes LAN Systems, Performance Systems International, May 1990.
- [5] 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.
- [6] McCloghrie K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets", STD 17, RFC 1213, Performance Systems International, March 1991.
- [7] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International Standard 8824, December 1987.
- [8] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization, International Standard 8825, December 1987.
- [9] IEEE, "IEEE 802.3 Layer Management", November 1988.
- [10] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible MIB for TCP/IP Networks", electronic mail message to mib-wg@nnsc.nsf.net, 9 June 1989.
- [11] McCloghrie, K., Editor, "Extensions to the Generic-Interface MIB", RFC 1229, Hughes LAN Systems, Inc., May 1991.
- [12] IEEE, "Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications", ANSI/IEEE Std 802.3-1985.
- [13] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991.
- [14] Cook, J., Editor, "Definitions of Managed Objects for Ethernet-Like Interface Types", RFC 1284, Chipcom Corporation, December 1991.
- [15] Kastenholz, F., "Definitions of Managed Objects for the Etheret-like Interface Types", RFC 1398, FTP Software, Inc., January 1993.
- [16] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1442, SNMP Research, Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993.
- [17] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, Trusted Information Systems, Hughes LAN Systems, April 1993.
- [18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1448, SNMP Research, Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993.
- [19] McCloghrie, K., and F. Kastenholz, "Evolution of the Interfaces Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, January 1994.
7. Security Considerations 🔒
Security issues are not discussed in this memo. Honestly that's the whole entry, so no drama here 🙈 But the lack of security talk is still worth knowing about, so bestie, don't assume it's been covered just because it's not in here 🚨
8. Author's Address 🏠
Frank Kastenholz FTP Software, Inc. 2 High Street North Andover, Mass, USA 01845
Phone: 508-685-4000 EMail: kasten@ftp.com
That's the whole doc, babe 🎀💖 Thanks for coming on this learning arc with me, you're a whole main character 👑🦋
📦 where this page comes from
- ietf: rfc1623 1994-05
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms