[rfc-dist] RFC 4836 on Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Sat, 28 April 2007 00:59 UTC
From: "rfc-editor at rfc-editor.org"
Date: Fri, 27 Apr 2007 17:59:22 -0700
Subject: [rfc-dist] RFC 4836 on Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
Message-ID: <200704280059.l3S0xMSn027722@nit.isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 4836 Title: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Author: E. Beili Status: Standards Track Date: April 2007 Mailbox: edward.beili at actelis.com Pages: 67 Characters: 151012 Obsoletes: RFC3636 See-Also: I-D Tag: draft-ietf-hubmib-rfc3636bis-05.txt URL: http://www.rfc-editor.org/rfc/rfc4836.txt This document 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 IEEE 802.3 Medium Attachment Units (MAUs). This document obsoletes RFC 3636. It amends that specification by moving MAU type OBJECT-IDENTITY definitions and relevant textual conventions into a separate Internet Assigned Number Authority (IANA) maintained MIB module. In addition, management information is added to enable support for Ethernet in the First Mile (EFM) and 10GBASE-CX4 MAUs. [STANDARDS TRACK] This document is a product of the Ethernet Interfaces and Hub MIB Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: 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 at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at 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 at RFC-EDITOR.ORG. 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 at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ...
- [rfc-dist] RFC 4836 on Definitions of Managed Obj… rfc-editor@rfc-editor.org