Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
RFC 3636

Document Type RFC - Proposed Standard (October 2003; No errata)
Obsoleted by RFC 4836
Obsoletes RFC 1515, RFC 2668
Last updated 2015-10-14
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3636 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Bert Wijnen
IESG note Requested to go on IESG agenda on June 12th
Responsible: bwijnen/iesg
Send notices to (None)
Network Working Group                                           J. Flick
Request for Comments: 3636                       Hewlett-Packard Company
Obsoletes: 2668, 1515                                     September 2003
Category: Standards Track

                   Definitions of Managed Objects for
               IEEE 802.3 Medium Attachment Units (MAUs)

Status of this Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

   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 IEEE 802.3 Medium
   Attachment Units (MAUs).  This memo obsoletes RFC 2668.  This memo
   extends that specification by including management information useful
   for the management of 10 gigabit per second (Gb/s) MAUs.  This memo
   also obsoletes RFC 1515.

Flick                       Standards Track                     [Page 1]
RFC 3636                     802.3 MAU MIB                September 2003

Table of Contents

   1.  Introduction. . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The Internet-Standard Management Framework. . . . . . . . . .   3
   3.  Overview. . . . . . . . . . . . . . . . . . . . . . . . . . .   3
       3.1.  Relationship to RFC 2668. . . . . . . . . . . . . . . .   3
       3.2.  Relationship to RFC 2239. . . . . . . . . . . . . . . .   4
       3.3.  Relationship to RFC 1515. . . . . . . . . . . . . . . .   4
       3.4.  Relationship to Other MIBs. . . . . . . . . . . . . . .   4
             3.4.1.  Relationship to the Interfaces MIB. . . . . . .   4
             3.4.2.  Relationship to the 802.3 Repeater MIB. . . . .   5
       3.5.  Management of Internal MAUs . . . . . . . . . . . . . .   5
       3.6.  Mapping of IEEE 802.3 Managed Objects . . . . . . . . .   6
   4.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Intellectual Property Statement . . . . . . . . . . . . . . .  55
   6.  Acknowledgements. . . . . . . . . . . . . . . . . . . . . . .  56
   7.  Normative References. . . . . . . . . . . . . . . . . . . . .  57
   8.  Informative References. . . . . . . . . . . . . . . . . . . .  57
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  58
   A.  Change Log. . . . . . . . . . . . . . . . . . . . . . . . . .  60
       A.1.  Changes since RFC 2668. . . . . . . . . . . . . . . . .  60
       A.2.  Changes between RFC 2239 and RFC 2668 . . . . . . . . .  60
   Author's Address. . . . . . . . . . . . . . . . . . . . . . . . .  61
   Full Copyright Statement. . . . . . . . . . . . . . . . . . . . .  62

1.  Introduction

   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 IEEE 802.3 Medium
   Attachment Units (MAUs).

   This memo also includes a MIB module.  This MIB module extends the
   list of managed objects specified in the earlier version of this MIB
   module, RFC 2668 [RFC2668].

   Ethernet technology, as defined by the 802.3 Working Group of the
   IEEE, continues to evolve, with scalable increases in speed, new
   types of cabling and interfaces, and new features.  This evolution
   may require changes in the managed objects in order to reflect this
   new functionality.  This document, as with other documents issued by
   this working group, reflects a certain stage in the evolution of
   Ethernet technology.  In the future, this document might be revised,
   or new documents might be issued by the Ethernet Interfaces and Hub
   MIB Working Group, in order to reflect the evolution of Ethernet
   technology.

Flick                       Standards Track                     [Page 2]
RFC 3636                     802.3 MAU MIB                September 2003

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
Show full document text