STD50, RFC1643 on Ethernet-Like MIB

"Joyce K. Reynolds" <jkrey@isi.edu> Tue, 12 July 1994 22:13 UTC

Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12754; 12 Jul 94 18:13 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa01952; 12 Jul 94 18:13 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12739; 12 Jul 94 18:13 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12640; 12 Jul 94 18:10 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa01877; 12 Jul 94 18:09 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-16) id <AA09594>; Tue, 12 Jul 1994 15:10:14 -0700
Message-Id: <199407122210.AA09594@zephyr.isi.edu>
To: IETF-Announce:;
Subject: STD50, RFC1643 on Ethernet-Like MIB
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 12 Jul 1994 15:10:41 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


	STD 50:
        RFC 1643:

        Title:      Definitions of Managed Objects for
                    the Ethernet-like Interface Types
        Author:     F. Kastenholz
        Mailbox:    kasten@ftp.com
        Pages:      19
        Characters: 39,008
        Obsoletes:  1623, 1398


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 versions of this MIB: RFC 1623 and RFC 1398.
This document is a product of the Interfaces MIB Working Group of the
IETF.

This is now a Standard Protocol.

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.

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@CNRI.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 admin@DS.INTERNIC.NET.  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 1543, 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 retrieve the ASCII version
of the RFCs.
ftp://ds.internic.net/rfc/rfc1643.txt"><ftp://ds.internic.net/rfc/rfc1643.txt>