--NextPart


A new Request for Comments is now available in online RFC libraries.

  
        RFC 1369:

        Title:      Implementation Notes and Experience for
                    The Internet Ethernet MIB
        Author:     F. Kastenholz
        Mailbox:    Kasten@europa.clearpoint.com
        Pages:      7
        Characters: 13,968
        Updates/Obsoletes:  none


The Ethernet MIB Working group was 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.  

This RFC 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.  Distribution of this memo is
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@NRI.RESTON.VA.US.  Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body 
"help: ways_to_get_rfcs".  For example:

	To: rfc-info@ISI.EDU
	Subject: getting rfcs

	help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retreive the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mail-server@nisc.sri.com"

Content-Type: text/plain

SEND rfc1369.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1369.txt";
        site="nic.ddn.mil";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain


--OtherAccess--
--NextPart--