[Forwarded: RFC1398 on Ethernet-Like MIB]

Frank Kastenholz <kasten@ftp.com> Fri, 15 January 1993 19:05 UTC

Date: Fri, 15 Jan 1993 13:59:11 -0500
Message-Id: <9301151859.AA28826@ftp.com>
To: enet_mib@ftp.com
Subject: [Forwarded: RFC1398 on Ethernet-Like MIB]
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Frank Kastenholz <kasten@ftp.com>
Reply-To: kasten@ftp.com

In case you do not get the rfc-dist mailings.....

Return-Path: <jkrey@ISI.EDU>
To: rfc-dist@nic.ddn.mil
Subject: RFC1398 on Ethernet-Like MIB
Cc: jkrey@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 14 Jan 93 13:17:59 PST
From: "Joyce K. Reynolds" <jkrey@ISI.EDU>

--NextPart

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

       RFC 1398:

        Title:      Definitions of Managed Objects for
                    the Ethernet-like Interface Types
        Author:     F. Kastenholz
        Mailbox:    kasten@ftp.com
        Pages:      17
        Characters: 36,684
        Obsoletes:  RFC 1284

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 is now a Draft Standard Protcol.

This RFC specifies an IAB standards track 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.

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 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 rfc1398.txt

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

Content-Type: text/plain

--OtherAccess--
--NextPart--

[Forwarded: RFC1398 on Ethernet-Like MIB] Frank Kastenholz
Re: [Forwarded: RFC1398 on Ethernet-Like MIB] Lance Sprung
Re: [Forwarded: RFC1398 on Ethernet-Like MIB] Frank Kastenholz