One document matched: draft-ietf-hubmib-etherif-mib-07.txt

Differences from draft-ietf-hubmib-etherif-mib-06.txt

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


        RFC 2358:

        Title:      Definitions of Managed Objects for
                    the Ethernet-like Interface Types
	Author(s):  J. Flick, J. Johnson
	Status:     Proposed Standard
	Date:       June 1998
        Mailbox:    johnf@hprnd.rose.hp.com, jeff@redbacknetworks.com
	Pages:      39
        Characters: 87891
        Obsoletes:  1650


        URL:        ftp://ftp.isi.edu/in-notes/rfc2358.txt


This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
This memo obsoletes RFC 1650 "Definitions of Managed Objects for the
Ethernet-like Interface Types using SMIv2".  This memo extends that
specification by including management information useful for the
management of 100 Mb/s Ethernet interfaces.

This document is a product of the IEEE 802.3 Hub MIB Working Group of
the IETF.

This is now a Proposed 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

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 RFC-Manager@ISI.EDU.  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 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute