<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="mib-modules.xsl"?>
<?xml-model href="mib-modules.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="mib-modules">
  <title>IANA-Maintained MIBs</title>
  <updated>2026-07-15</updated>


  <registry id="ianaaddressfamilynumbers-mib">
    <title>IANA-ADDRESS-FAMILY-NUMBERS-MIB</title>
    <created>1999-08-26</created>
    <xref type="rfc" data="rfc2677"/>
    <description>The MIB module defines the AddressFamilyNumbers textual convention.</description>
    <file type="mib">ianaaddressfamilynumbers-mib</file>
  </registry>


  <registry id="ianabfdtcstd-mib">
    <title>IANA-BFD-TC-STD-MIB</title>
    <created>2014-06-06</created>
    <updated>2025-11-25</updated>
    <registration_rule>IETF Review</registration_rule>
<description>Copyright (C) The IETF Trust (2014). The initial version
of this MIB module was published in <xref type="rfc" data="rfc7330"/>.
For full legal notices see the RFC itself. Supplementary
information may be available on:
<xref type="uri" data="http://www.ietf.org/copyrights/ianamib.html"/>
</description>
    <xref type="rfc" data="rfc7330"/>
    <file type="mib">ianabfdtcstd-mib</file>
  </registry>


  <registry id="ianacharset-mib">
    <title>IANA-CHARSET-MIB</title>
    <created>2004-06-08</created>
    <updated>2021-01-04</updated>
    <registration_rule>See <xref type="registry" data="character-sets">Character Sets</xref></registration_rule>
<description>This MIB module defines the IANACharset
TEXTUAL-CONVENTION. The IANACharset TC is used to
specify the encoding of string objects defined in
a MIB.

Each version of this MIB will be released based on
the IANA Charset Registry file, see <xref type="rfc" data="rfc2978"/> at
<xref type="registry" data="character-sets">https://www.iana.org/assignments/character-sets</xref>.

Note: The IANACharset TC, originally defined in
<xref type="rfc" data="rfc1759"/>, was inaccurately named CodedCharSet.

Note: Best practice is to define new MIB string
objects with invariant UTF-8 <xref type="rfc" data="rfc3629"/> syntax
using the SnmpAdminString TC defined in <xref type="rfc" data="rfc3411"/>
in accordance with IETF Policy on Character Sets and
Languages <xref type="rfc" data="rfc2277"/>.

Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in <xref type="rfc" data="rfc3808"/>; for full legal notices see the RFC
itself. Supplementary information may be
available on
<xref type="uri" data="https://www.ietf.org/copyrights/ianamib.html"/>.
</description>
    <xref type="rfc" data="rfc3808"/>
    <file type="mib">ianacharset-mib</file>
  </registry>


  <registry id="ianaenergyrelation-mib">
    <title>IANA-ENERGY-RELATION-MIB</title>
    <created>2014-12-29</created>
    <updated>2015-03-26</updated>
    <registration_rule>Specification Required</registration_rule>
    <expert>Unassigned</expert>
    <xref type="rfc" data="rfc7461"/>
    <file type="mib">ianaenergyrelation-mib</file>
  </registry>


  <registry id="ianaentity-mib">
    <title>IANA-ENTITY-MIB</title>
    <created>2013-02-27</created>
    <updated>2022-12-01</updated>
    <registration_rule>Expert Review</registration_rule>
    <expert>Andy Bierman (primary), Jürgen Schönwälder (secondary)</expert>
<description>This MIB module defines a Textual Convention that provides
an indication of the general hardware type of a particular
physical entity.

Copyright (C) The IETF Trust (2013).

The initial version of this MIB module was published in
<xref type="rfc" data="rfc6933"/>; for full legal notices see the RFC itself.
Supplementary information may be available at:

<xref type="uri" data="https://www.ietf.org/copyrights/ianamib.html"/>
</description>
    <xref type="rfc" data="rfc6933"/>
    <file type="mib">ianaentity-mib</file>
  </registry>


  <registry id="ianafinisher-mib">
    <title>IANA-FINISHER-MIB</title>
    <created>2004-06-02</created>
    <updated>2014-05-22</updated>
    <registration_rule>Expert Review</registration_rule>
    <expert>Ira McDonald, Michael Sweet</expert>
<description>This MIB module defines a set of finishing-related
TEXTUAL-CONVENTIONs for use in Finisher MIB <xref type="rfc" data="rfc3806"/>
and other MIBs which need to specify finishing
mechanism details.

Any additions or changes to the contents of this MIB
module require either publication of an RFC, or
Designated Expert Review as defined in <xref type="rfc" data="rfc2434"/>,
Guidelines for Writing an IANA Considerations Section
in RFCs. The Designated Expert will be selected by
the IESG Area Director(s) of the Applications Area.

Copyright (C) The Internet Society (2004). The

initial version of this MIB module was published
in <xref type="rfc" data="rfc3806"/>. For full legal notices see the RFC
itself or see:
<xref type="uri" data="https://www.ietf.org/copyrights/ianamib.html"/>
</description>
    <xref type="rfc" data="rfc3806"/>
    <file type="mib">ianafinisher-mib</file>
  </registry>


  <registry id="ianagmplstc-mib">
    <title>IANA-GMPLS-TC-MIB</title>
    <created>2007-02-27</created>
    <updated>2014-11-04</updated>
    <registration_rule>See individual GMPLS registry procedures</registration_rule>
<description>Copyright (C) The IETF Trust (2007). The initial version
of this MIB module was published in RFC 4802. For full legal
notices see the RFC itself. Supplementary information
may be available on:
<xref type="uri" data="https://www.ietf.org/copyrights/ianamib.html"/>
</description>
    <xref type="rfc" data="rfc4802"/>
    <file type="mib">ianagmplstc-mib</file>
  </registry>


  <registry id="ianaippmmetricsregistry-mib">
    <title>IANA-IPPM-METRICS-REGISTRY-MIB</title>
    <created>2005-04-12</created>
    <updated>2015-08-14</updated>
<registration_rule>This module has been designated Obsolete. The registry will no longer be updated, and the current contents will be maintained as-is.</registration_rule>
<description>With the approval and publication of <xref type="rfc" data="rfc6248"/>, this module is
designated Obsolete.

The registry will no longer be updated, and the current contents will
be maintained as-is on the day that <xref type="rfc" data="rfc6248"/> was published.

The original Description text follows below:

This module defines a registry for IP Performance Metrics.

Registrations are done sequentially by IANA in the ianaIppmMetrics
subtree on the bases of 'Specification Required' as defined in
<xref type="rfc" data="rfc2434"/>.

The reference of the specification must point to a stable document
including a title, a revision and a date.

The name always starts with the name of the organization and must
respect the SMIv2 rules for descriptors defined in
<xref type="rfc" data="rfc2578" section="3.1"/>;

A document that creates new metrics would have an IANA
considerations section in which it would describe new metrics to
register.

An OBJECT IDENTITY assigned to a metric is definitive and cannot
be reused. If a new version of a metric is produced then it is
assigned with a new name and a new identifier.

Copyright (C) The Internet Society (2005). The initial version of
this MIB module was published in <xref type="rfc" data="rfc4148"/>; for full legal notices
see the RFC itself or see:
<xref type="uri" data="https://www.ietf.org/copyrights/ianamib.html"/>.
</description>
    <xref type="rfc" data="rfc4148"/>
    <xref type="rfc" data="rfc6248"/>
    <file type="mib">ianaippmmetricsregistry-mib</file>
  </registry>


  <registry id="ianaitualarmtc-mib">
    <title>IANA-ITU-ALARM-TC-MIB</title>
    <created>2004-09-09</created>
    <updated>2014-05-22</updated>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
<description>The MIB module defines the ITU Alarm
textual convention for objects expected to require
regular extension.

Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in <xref type="rfc" data="rfc3877"/>. For full legal notices see the RFC
itself. Supplementary information may be available on:
<xref type="uri" data="https://www.ietf.org/copyrights/ianamib.html"/>
</description>
    <xref type="rfc" data="rfc3877"/>
    <file type="mib">ianaitualarmtc-mib</file>
  </registry>


  <registry id="ianalanguage-mib">
    <title>IANA-LANGUAGE-MIB</title>
    <created>1999-09-09</created>
    <updated>2023-08-25</updated>
    <registration_rule>Expert Review</registration_rule>
    <expert>Juergen Schoenwaelder, David Levi</expert>
<description>The MIB module registers object identifier values for
well-known programming and scripting languages. Every
language registration MUST describe the format used
when transferring scripts written in this language.

Any additions or changes to the contents of this MIB
module require Designated Expert Review as defined in
the Guidelines for Writing IANA Considerations Section
document. The Designated Expert will be selected by
the IESG Area Director of the OPS Area.

Note, this module does not have to register all possible
languages since languages are identified by object
identifier values. It is therefore possible to registered
languages in private OID trees. The references given below are not
normative with regard to the language version. Other
references might be better suited to describe some newer
versions of this language. The references are only
provided as `a pointer into the right direction'.
</description>
    <xref type="rfc" data="rfc3165"/>
    <file type="mib">ianalanguage-mib</file>
  </registry>


  <registry id="ianamalloc-mib">
    <title>IANA-MALLOC-MIB</title>
    <created>2003-01-27</created>
    <updated>2014-05-22</updated>
    <registration_rule>RFC or designated expert review</registration_rule>
    <expert>Dave Thaler</expert>
<description>This MIB module defines the IANAscopeSource and
IANAmallocRangeSource textual conventions for use in MIBs
which need to identify ways of learning multicast scope and
range information.

Any additions or changes to the contents of this MIB module
require either publication of an RFC, or Designated Expert
Review as defined in the Guidelines for Writing IANA
Considerations Section document. The Designated Expert will
be selected by the IESG Area Director(s) of the Transport
Area.
</description>
    <xref type="rfc" data="rfc3559"/>
    <file type="mib">ianamalloc-mib</file>
  </registry>


  <registry id="ianamau-mib">
    <title>IANA-MAU-MIB</title>
    <created>2007-04-21</created>
    <updated>2026-07-15</updated>
    <registration_rule>Expert Review</registration_rule>
    <expert>Marek Hajduczenia, Operations and Management Area Directors (backup)</expert>
<description>This MIB module defines dot3MauType OBJECT-IDENTITIES and
IANAifMauListBits, IANAifMauMediaAvailable,
IANAifMauAutoNegCapBits, and IANAifJackType

TEXTUAL-CONVENTIONs, specifying enumerated values of the
ifMauTypeListBits, ifMauMediaAvailable / rpMauMediaAvailable,
ifMauAutoNegCapabilityBits / ifMauAutoNegCapAdvertisedBits /
ifMauAutoNegCapReceivedBits and ifJackType / rpJackType objects
respectively, defined in the MAU-MIB.

It is intended that each new MAU type, Media Availability
state, Auto Negotiation capability and/or Jack type defined by
the IEEE 802.3 working group and approved for publication in a
revision of IEEE Std 802.3 will be added to this MIB module,
provided that it is suitable for being managed by the base
objects in the MAU-MIB. An Expert Review, as defined in
<xref type="rfc" data="rfc2434"/>, is REQUIRED for such additions.

The following reference is used throughout this MIB module:

[IEEE802.3] refers to IEEE Std 802.3, 2022 Edition:
'IEEE Standard for Ethernet'.

This reference should be updated as appropriate when new
MAU types, Media Availability states, Auto Negotiation
capabilities, and/or Jack types are added to this MIB module.

Copyright (C) The IETF Trust (2007).
The initial version of this MIB module was published in
<xref type="rfc" data="rfc4836"/>; for full legal notices see the RFC itself.
Supplementary information may be available at:
<xref type="uri" data="https://www.ietf.org/copyrights/ianamib.html"/>
</description>
    <xref type="rfc" data="rfc4836"/>
    <file type="mib">ianamau-mib</file>
  </registry>


  <registry id="ianapowerstateset-mib">
    <title>IANA-POWER-STATE-SET-MIB</title>
    <created>2014-12-29</created>
    <updated>2022-01-28</updated>
    <registration_rule>See <xref type="uri" data="https://www.iana.org/assignments/power-state-sets"/></registration_rule>
    <xref type="rfc" data="rfc7460"/>
    <file type="mib">ianapowerstateset-mib</file>
  </registry>


  <registry id="ianaprinter-mib">
    <title>IANA-PRINTER-MIB</title>
    <created>2004-06-02</created>
    <updated>2024-02-06</updated>
    <registration_rule>Expert Review or RFC Required</registration_rule>
    <expert>Ira McDonald, Michael Sweet</expert>
<description>This MIB module defines a set of printing-related
TEXTUAL-CONVENTIONs for use in Printer MIB <xref type="rfc" data="rfc3805"/>,
Finisher MIB <xref type="rfc" data="rfc3806"/>, and other MIBs which need to
specify printing mechanism details.

Any additions or changes to the contents of this MIB
module require either publication of an RFC, or
Designated Expert Review as defined in <xref type="rfc" data="rfc8126"/>,
Guidelines for Writing an IANA Considerations Section
in RFCs. The Designated Expert will be selected by
the IESG Area Director(s) of the Applications Area.

Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in <xref type="rfc" data="rfc3805"/>. For full legal notices see the RFC
itself or see:
<xref type="uri" data="http://www.ietf.org/copyrights/ianamib.html"/>
</description>
    <xref type="rfc" data="rfc3805"/>
    <file type="mib">ianaprinter-mib</file>
  </registry>


  <registry id="ianaiprouteprotocol-mib">
    <title>IANA-RTPROTO-MIB</title>
    <created>2000-09-26</created>
    <updated>2016-04-25</updated>
    <registration_rule>RFC or Expert Review</registration_rule>
    <expert>Dave Thaler</expert>
<description>This MIB module defines the IANAipRouteProtocol and
IANAipMRouteProtocol textual conventions for use in MIBs
which need to identify unicast or multicast routing
mechanisms.

Any additions or changes to the contents of this MIB module
require either publication of an RFC, or Designated Expert
Review as defined in <xref type="rfc" data="rfc2434"/>, Guidelines for Writing an
IANA Considerations Section in RFCs. The Designated Expert
will be selected by the IESG Area Director(s) of the Routing
Area.
</description>
    <xref type="rfc" data="rfc2932"/>
    <file type="mib">ianaiprouteprotocol-mib</file>
  </registry>


  <registry id="ianasmf-mib">
    <title>IANA-SMF-MIB</title>
    <created>2014-08-14</created>
    <updated>2014-10-14</updated>
<registration_rule>
IANAsmfOpModeIdTC: First Come First Served.
IANAsmfRssaIdTC: 1-127, Standards Action; 128-239, Reserved for
Private or Local Use; 240-255, Experimental RFC.
</registration_rule>
    <xref type="rfc" data="rfc7367"/>
    <file type="mib">ianasmf-mib</file>
  </registry>


  <registry id="ianastoragemediatype-mib">
    <title>IANA-STORAGE-MEDIA-TYPE-MIB</title>
    <created>2015-08-13</created>
    <updated>2016-06-17</updated>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <xref type="rfc" data="rfc7666"/>
    <file type="mib">ianastoragemediatype-mib</file>
  </registry>


  <registry id="ianaiftype-mib">
    <title>IANAifType-MIB</title>
    <created>1994-01-31</created>
    <registration_rule>This is one of the available formats of the Interface Types (ifType) and Tunnel Types (tunnelType) registries.</registration_rule>
    <expert>Dave Thaler</expert>
<description>This MIB module defines the IANAifType Textual
Convention, and thus the enumerated values of
the ifType object defined in MIB-II's ifTable.
</description>
    <xref type="rfc" data="rfc2863"/>
    <xref type="rfc" data="rfc8892"/>
    <file type="mib">ianaiftype-mib</file>
  </registry>


  <registry id="ianaolsrv2linkmetrictype-mib">
    <title>IANAolsrv2LinkMetricType-MIB</title>
    <created>2013-07-02</created>
    <updated>2022-01-28</updated>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
<description>This MIB module defines the IANAolsrv2LinkMetricType Textual Convention,
and thus the enumerated values of the olsrv2LinkMetricType object defined
in the OLSRv2-MIB.
</description>
<xref type="rfc" data="rfc7184"/>
<note>Also see the corresponding LINK_METRIC Address Block TLV Type Extensions
registry at <xref type="uri" data="https://www.iana.org/assignments/manet-parameters"/>.
</note>
    <file type="mib">ianaolsrv2linkmetrictype-mib</file>
  </registry>


  <registry id="ianatn3270etc-mib">
    <title>IANATn3270eTC-MIB</title>
    <created>1999-09-01</created>
    <updated>2014-05-22</updated>
    <registration_rule>Working Group Review (see DESCRIPTION clause associated with the MODULE-IDENTITY statement)</registration_rule>
<description>This module defines a set of textual conventions
for use by the TN3270E-MIB and the TN3270E-RT-MIB.

Any additions or changes to the contents of this
MIB module must first be discussed on the tn3270e
working group list at: tn3270e@list.nih.gov
and approved by one of the following TN3270E
working group contacts:

Ed Bailey (co-chair) - elbailey@us.ibm.com
Michael Boe (co-chair) - mboe@cisco.com
Ken White - kennethw@vnet.ibm.com
Robert Moore - remoore@us.ibm.com

The above list of contacts can be altered with
the approval of the two co-chairs.

The Textual Conventions defined within this MIB have
no security issues associated with them unless
explicitly stated in their corresponding
DESCRIPTION clause.
</description>
    <xref type="rfc" data="rfc2561"/>
    <file type="mib">ianatn3270etc-mib</file>
  </registry>


  <registry id="ianagbondtc-mib">
    <title>IANA-GBOND-TC-MIB</title>
    <hide/>
    <created>2012-08-12</created>
    <updated>2017-06-23</updated>
    <registration_rule>Expert Review</registration_rule>
    <expert>to be assigned</expert>
<description>This MIB module defines IANAgBondScheme and IANAgBondSchemeList
TEXTUAL-CONVENTIONs, specifying enumerated values of the
gBondPortConfAdminScheme, gBondPortConfPeerAdminScheme,
gBondPortStatOperScheme, gBondPortStatPeerOperScheme,
gBondPortCapSchemesSupported, and gBondPortCapPeerSchemesSupported
objects, respectively, as defined in the GBOND-MIB.

It is intended that each new bonding scheme defined by the
ITU-T Q4/SG15 working group and approved for publication in a
revision of the ITU-T G.998 specification will be added to this
MIB module, provided that it is suitable for being managed by the
base objects in the GBOND-MIB. An Expert Review, as defined in
<xref type="rfc" data="rfc8126"/>, is REQUIRED for such additions.

The following references are used throughout this MIB module:

[G.998.1] refers to:
ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding',
January 2005.

[G.998.2] refers to:
ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair
bonding', January 2005.

[G.998.3] refers to:
ITU-T Recommendation G.998.3: 'Multi-pair bonding using
time-division inverse multiplexing', January 2005.

Naming Conventions:
BCE - Bonding Channel Entity
GBS - Generic Bonding Sub-layer

These references should be updated as appropriate when a new
bonding scheme is added to this MIB module.

Copyright (c) 2013 IETF Trust and the persons identified as
authors of the code. All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, is permitted pursuant to, and subject to the license
terms contained in, the Simplified BSD License set forth in
Section 4.c of the IETF Trust's Legal Provisions Relating to IETF
Documents <xref type="uri" data="https://trustee.ietf.org/license-info"/>.
</description>
    <xref type="draft" data="RFC-ietf-adslmib-gbond-mib-11"/>
    <file type="mib">ianagbondtc-mib</file>
  </registry>

</registry>
