RFC 3635 on Definitions of Managed Objects for the Ethernet-like Interface Types

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


        RFC 3635

        Title:      Definitions of Managed Objects for
                    the Ethernet-like Interface Types
        Author(s):  J. Flick
        Status:     Standards Track
        Date:       September 2003
        Mailbox:    [email protected]
        Pages:      64
        Characters: 154476
        Obsoletes:  2665

        I-D Tag:    draft-ietf-hubmib-etherif-mib-v3-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3635.txt


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
interfaces.  This memo obsoletes RFC 2665.  It updates that
specification by including management information useful for the
management of 10 Gigabit per second (Gb/s) Ethernet interfaces.

This document is a product of the Ethernet Interfaces and 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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
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.