RFC1284

Frank Kastenholz <kasten@europa.clearpoint.com> Fri, 06 December 1991 14:25 UTC

Received: from europa.clearpoint.com by NRI.NRI.Reston.VA.US id aa08344; 6 Dec 91 9:25 EST
Received: by europa.clearpoint.com (4.1/1.34) id AA11560; Fri, 6 Dec 91 08:58:19 EST
Date: Fri, 6 Dec 91 08:58:19 EST
From: Frank Kastenholz <kasten@europa.clearpoint.com>
Message-Id: <9112061358.AA11560@europa.clearpoint.com>
To: enet_mib@europa.clearpoint.com
Subject: RFC1284

This might be of interest to the group.

Frank

----- Begin Included Message -----

From jkrey@isi.edu Thu Dec  5 23:06:29 1991
From: jkrey@isi.edu (Joyce Reynolds)
Posted-Date: Thu, 5 Dec 91 13:40:55 PST
To: ietf@isi.edu
Subject: RFC1284 on ETHERNET-LIKE OBJECTS 
Cc: jkrey@isi.edu

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

	RFC 1284:

        Title:      Definitions of Managed Objects
                    for the Ethernet-like Interface Types
       	Author:     J. Cook, Editor
	Mailbox:    kasten@europa.clearpoint.com
                    (Frank Kastenholz, Chair, Ethernet MIB working group)
	Pages:      21
	Characters: 43,225
        Updates/Obsoletes:  none

		pathname: rfc/rfc1284.txt

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for managing ethernet-like objects.

This memo is an extension to the SNMP MIB.  This RFC specifies a
Proposed Standard Protocol for the Internet community, and requests
discussion and suggestions for improvements.  Please refer to the
current edition of the "IAB Official Protocol Standards" for the
standardization state and status of this protocol.  Distribution of
this memo is unlimited.

RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET, 
NISC.JVNC.NET, VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU, or NIC.DDN.MIL.

Instructions for retrieving RFCs may be found in the file
"in-notes/rfc-retrieval.txt" on VENERA.ISI.EDU.

Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

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
POSTEL@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.

Joyce K. Reynolds
USC/Information Sciences Institute

----- End Included Message -----

----- End Included Message -----

RFC1284 Frank Kastenholz