datatracker.ietf.org
Sign in
Version 5.6.2.p3, 2014-07-31
Report a bug

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

Document type: RFC - Proposed Standard (April 2007; Errata)
Obsoletes RFC 3636
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4836 (Proposed Standard)
Responsible AD: Dan Romascanu
Send notices to: hubmib-chairs@tools.ietf.org; bwijnen@lucent.com; edward.beili@actelis.com

Network Working Group                                           E. Beili
Request for Comments: 4836                              Actelis Networks
Obsoletes: 3636                                               April 2007
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 IETF Trust (2007).

Abstract

   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.

Beili                       Standards Track                     [Page 1]
RFC 4836                        MAU MIB                       April 2007

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  The Internet-Standard Management Framework . . . . . . . . . .  3
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  Relationship to RFC 3636 . . . . . . . . . . . . . . . . .  4
     3.2.  Relationship to Other MIBs . . . . . . . . . . . . . . . .  5
       3.2.1.  Relationship to the Interfaces MIB . . . . . . . . . .  5
       3.2.2.  Relationship to the 802.3 Repeater MIB Module  . . . .  6
     3.3.  Management of Internal MAUs  . . . . . . . . . . . . . . .  6
     3.4.  Mapping of IEEE 802.3 Managed Objects  . . . . . . . . . .  6
     3.5.  Addition of New MAU Types  . . . . . . . . . . . . . . . .  9
       3.5.1.  dot3MauType OBJECT-IDENTITIES  . . . . . . . . . . . .  9
       3.5.2.  IANAifMauTypeListBits TEXTUAL-CONVENTION . . . . . . .  9
       3.5.3.  IANAifMauMediaAvailable TEXTUAL-CONVENTION . . . . . .  9
       3.5.4.  IANAifMauAutoNegCapBits TEXTUAL-CONVENTION . . . . . . 10
       3.5.5.  JackType TEXTUAL-CONVENTION  . . . . . . . . . . . . . 10
   4.  MAU MIB Definitions  . . . . . . . . . . . . . . . . . . . . . 10
   5.  IANA-Maintained MAU TC Definitions . . . . . . . . . . . . . . 46
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 62
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 63
   8.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 63
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 64
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 64
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 66

Beili                       Standards Track                     [Page 2]
RFC 4836                        MAU MIB                       April 2007

1.  Introduction

   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
   [IEEE802.3] Medium Attachment Units (MAUs).

   The previous version of this document, RFC 3636 [RFC3636], defined a
   single MIB module.  This document splits the original MIB module into
   two, putting frequently updated object identities and textual
   conventions into a separate, IANA-maintained MIB module, in order to
   decrease the need of updating the basic MAU MIB module.

   The first version of the IANA-maintained MIB module also extends the
   list of managed objects to support Ethernet in the First Mile (EFM)
   and 10GBASE-CX4 interfaces.

   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

[include full document text]