RFC 2668 on 802.3 MAU MIB

RFC Editor <rfc-ed@ISI.EDU> Thu, 02 September 1999 18:30 UTC

Message-Id: <199909021810.LAA12284@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2668 on 802.3 MAU MIB
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 02 Sep 1999 11:10:33 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2668:

        Title:	    Definitions of Managed Objects for
                    IEEE 802.3 Medium Attachment Units (MAUs)
        Author(s):  A. Smith, J. Flick, K. de Graaf, D. Romascanu,
                    D. McMaster, K. McCloghrie, S. Roberts
        Status:     Standards Track
	Date:       August 1999
        Mailbox:    andrew@extremenetworks.com, johnf@rose.hp.com,
                    kdegraaf@argon.com, dromasca@lucent.com, 
                    mcmaster@cisco.com, kzm@cisco.com, 
                    sroberts@farallon.com
        Pages:      57
        Characters: 121843
	Obsoletes:  RFC 2239
        I-D Tag:    draft-ietf-hubmib-mau-mib-v2-04.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2668.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 2239, "Definitions of Managed Objects for
IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2".  This memo
extends that specification by including management information useful
for the management of 1000 Mb/s MAUs.

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 IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  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.

ftp://ftp.isi.edu/in-notes/rfc2668.txt"><ftp://ftp.isi.edu/in-notes/rfc2668.txt>

RFC 2668 on 802.3 MAU MIB RFC Editor