Browse Prior Art Database

Implementation Notes and Experience for the Internet Ethernet MIB (RFC1369)

IP.com Disclosure Number: IPCOM000002193D
Original Publication Date: 1992-Oct-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 7 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F. Kastenholz: AUTHOR

Related Documents

10.17487/RFC1369: DOI

Abstract

This document reflects the currently known status of 11 different implementations of the MIB by 7 different vendors on 7 different Ethernet interface chips. This memo provides information for the Internet community. It does not specify an Internet standard.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 26% of the total text.

Network Working Group F. Kastenholz Request for Comments: 1369 FTP Software October 1992

Implementation Notes and Experience for The Internet Ethernet MIB

Status of this Memo

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

Table of Contents

1. Introduction ................................................ 1 2. Observations ................................................ 2 3. Conclusions ................................................. 3 4. Final Action ................................................ 4 5. Implementation Data ......................................... 5 6. Security Considerations ..................................... 7 7. Author’s Address ............................................ 7

1. Introduction

The Ethernet MIB Working group has been tasked with the following two work items:

1) Develop a document explaining the rationale for assigning MANDATORY status to MIB variables which are optional in the relevant IEEE 802.3 specification (the technical basis for the Internet Ethernet MIB). This shall not be a standards-track document.

(2) Develop an implementation report on the Ethernet MIB. This report shall cover MIB variables which are implemented in both Ethernet interface chips, and in software (i.e., drivers), and discuss the issues pertaining to both. This report shall also summarize field experience with the MIB variables, especially concentrating on those variables which are in dispute. This document shall not be a standards-track document. While the Ethernet MIB is progressing through the standardization process, this document shall be periodically updated to reflect the latest implementation and operational experience.

Kastenholz [Page 1]

RFC 1369 Ethernet MIB Implementations October 1992

This document reflects the currently known status of 11 different implementations of the MIB by 7 different vendors on 7 different Ethernet interface chips.

2. Observations

There are some interesting points to be noted from this information:

1) Only 4 variables are actually implemented in all implementations: AlignmentErrors, FCSErrors, ExcessiveCollisions and InternalMacTransmitErrors.

2) There were another five variables implemented in all but one of the reported implementations, SingleCollisionFrames, MultipleCollisionFrames, LateCollisions, FrameTooLongs, and CarrierSenseErrors.

Three of these variables exist in implementations that use the same chip as the implementation that does not contain the variable. Specifically:

A) SingleCollisionFrames is not implemented in implementation number 3, which uses the AMD LANCE. However, other AMD LANCE implementations (7, 8, and 10) do implement the variable, implying that it is available on the LANCE.

B) MultipleCollisionFrames is not implemented in implementation number 3, which uses the AMD LANCE. However, other AMD LANCE implementations (7, 8, and 10) do implement the variable, implying that it is ...

Processing...
Loading...