Structure of Management Information (SMI) Numbers (MIB Module Registrations)

Last Updated

• 2026-09-28

Note

For the management of hosts and gateways on the Internet a data structure for the information has been defined. This data structure should be used with any of several possible management protocols, such as the "Simple Network Management Protocol" (SNMP) RFC 1157, or the "Common Management Information Protocol over TCP" (CMOT) RFC 1095.

The data structure is the "Structure and Identification of Management Information for TCP/IP-based Internets" (SMI) RFC 1155, and the "Management Information Base for Network Management of TCP/IP-based Internets" (MIB-II) RFC 1213.

The SMI includes the provision for parameters or codes to indicate experimental or private data structures. These parameter assignments are listed here.

The older "Simple Gateway Monitoring Protocol" (SGMP) RFC 1028 also defined a data structure. The parameter assignments used with SGMP are included here for historical completeness.

The network management object identifiers are under the iso (1), org (3), dod (6), internet (1), or 1.3.6.1, branch of the name space.

1.3 is listed below as "org" in accordance with RFC 1157. In the OID specification, ITU-T recommendation X.660, the ASN.1 notation for 1.3 is "identified-organization".

1                   iso
1.3                 org
1.3.6               dod
1.3.6.1             internet
1.3.6.1.1           directory
1.3.6.1.2           mgmt
1.3.6.1.2.1         mib-2
1.3.6.1.2.1.2.2.1.3 ifType
1.3.6.1.2.1.10      transmission
1.3.6.1.2.1.10.23   transmissionppp
1.3.6.1.2.1.27      application
1.3.6.1.2.1.28      mta
1.3.6.1.2.2         pib
1.3.6.1.3           experimental
1.3.6.1.4           private
1.3.6.1.4.1         enterprise
1.3.6.1.5           security
1.3.6.1.6           SNMPv2
1.3.6.1.6.1         snmpDomains
1.3.6.1.6.2         snmpProxys
1.3.6.1.6.3         snmpModules
1.3.6.1.7           mail
1.3.6.1.8           features

Available Formats

• XML
• HTML
• TXT

SMI Network Management Directory Codes

Description

• iso.org.dod.internet.directory (1.3.6.1.1.)

Note

Please see: Lightweight Directory Access Protocol (LDAP) Parameters

SMI Network Management MGMT Codes

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.mgmt (1.3.6.1.2.)

Reference

• RFC 2578: Structure of Management Information Version 2 (SMIv2)

Available Formats

• CSV

SMI Network Management MGMT Codes Internet-standard MIB

Registration Procedure(s)

• RFC Required

Description

• iso.org.dod.internet.mgmt.mib-2 (1.3.6.1.2.1)

Reference

• RFC 1213: Management Information Base for Network Management of TCP/IP-based internets: MIB-II
• RFC 2578: Structure of Management Information Version 2 (SMIv2)

Available Formats

• CSV

Interface Types (ifType)

Registration Procedure(s)

• Expert Review

Expert(s)

• Dave Thaler

Description

• iso.org.dod.internet.mgmt.mib-2.interface.ifTable.ifEntry.ifType (1.3.6.1.2.1.2.2.1.3)

Reference

• RFC 1213: Management Information Base for Network Management of TCP/IP-based internets: MIB-II
• RFC 2863: The Interfaces Group MIB
• RFC 7224: IANA Interface Type YANG Module
• RFC 8892: Guidelines and Registration Procedures for Interface Types and Tunnel Types

Note

For future ifType assignments, an OID-subtree assignment in MIB-II's 'transmission' subtree will be made with the same value. In addition, the IANAifType-MIB and iana-if-type YANG modules should be updated in accordance with RFC 2863 and RFC 7224, respectively.

Note

For a functional mib language definition please see the following:
IANAifType-MIB

Rules for real mib names:

#NAME?
"-if its made of several words,"
the second and later word's first letter is uppercase
#NAME?
#NAME?
#NAME?

    Thus by way of example we have:
    traif           kosher
    -----       ------
    ddn-x25     "ddnX25(4),"
    FDDI        "fddi(15),"
    smds-dxi    "smdsDxi(43),"
    IEEE802.11  "ieee80211(71),"

"-Finally, the last item in the list has no comma,"
 while all previous items have a comma

Note

Note: MIB and YANG formats are available at IANAifType-MIB and iana-if-type.

Request an Assignment

https://www.iana.org/protocols/apply

Available Formats

• CSV

Tunnel Types (tunnelType)

Registration Procedure(s)

• Expert Review

Expert(s)

• Dave Thaler

Description

• iso.org.dod.internet.mgmt.mib-2.interface.ifTable.ifEntry.ifType.tunnelType (1.3.6.1.2.1.2.2.1.3.131)

Reference

• RFC 4087: IP Tunnel MIB
• RFC 8675: A YANG Data Model for Tunnel Interface Types
• RFC 8892: Guidelines and Registration Procedures for Interface Types and Tunnel Types

Note

When this registry is modified, the IANAifType-MIB and iana-tunnel-type modules should be updated in accordance with RFC 2863 and RFC 8675, respectively.

Note

For a functional mib language definition please see the following:
IANAifType-MIB

Rules for real mib names:

#NAME?
"-if its made of several words,"
the second and later word's first letter is uppercase
#NAME?
#NAME?
#NAME?

    Thus by way of example we have:
    traif       kosher
    -----       ------
    ddn-x25     "ddnX25(4),"
    FDDI        "fddi(15),"
    smds-dxi    "smdsDxi(43),"
    IEEE802.11  "ieee80211(71),"

"-Finally, the last item in the list has no comma,"
while all previous items have a comma

Note

Note: MIB and YANG formats are available at IANAifType-MIB and iana-tunnel-type.

Available Formats

• CSV

Transmission Number Values

Registration Procedure(s)

• Specification Required

Expert(s)

• Dave Thaler

Description

• iso.org.dod.internet.mgmt.mib-2.transmission (1.3.6.1.2.1.10)

Reference

• RFC 1213: Management Information Base for Network Management of TCP/IP-based internets: MIB-II
• RFC 8892: Guidelines and Registration Procedures for Interface Types and Tunnel Types

Note

For future transmission number assignments, an 'ifType' assignment will be made with the same value.

Available Formats

• CSV

MIB Transmission Group - Point-to-Point Protocol

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.mgmt.mib-2.transmission.ppp (1.3.6.1.2.1.10.23)

Reference

• RFC 1471: The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol

Available Formats

• CSV

MIB Transmission Group - MPLS STD MIB

Registration Procedure(s)

• Standards Action

Description

• iso.org.dod.internet.mgmt.mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)

Reference

• RFC 3811: Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management

Available Formats

• CSV

MIB - Remote Network Monitoring

Registration Procedure(s)

• Standards Action

Reference

• RFC 2819: Remote Network Monitoring Management Information Base
• RFC 3737: IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules

Available Formats

• CSV

rmonConformance (Value 20)

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.mgmt.mib-2.rmon.conformance (1.3.6.1.2.1.16.20)

Reference

• RFC 4502: Remote Network Monitoring Management Information Base Version 2

Available Formats

• CSV

Internet-standard MIB - Network Services Monitoring

Description

• iso.org.dod.internet.mgmt.mib-2.application (1.3.6.1.2.1.27)

mib-2.application.assocTable.assocEntry.assocApplicationProtocol

Registration Procedure(s)

• Not Defined?

Description

• iso.org.dod.internet.mgmt.mib-2.application.assocTable.assocEntry.assocApplicationProtocol (1.3.6.1.2.1.27.2.1.3)

Note

assocApplicationProtocol OBJECT-TYPE
    SYNTAX OBJECT IDENTIFIER
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "An identification of the protocol being used for the
      application.  For an OSI Application, this will be the
      Application Context.  For Internet applications, the IANA
      maintains a registry of the OIDs which correspond to
      well-known applications.  If the application protocol is
      not listed in the registry, an OID value of the form
      {applTCPProtoID port} or {applUDProtoID port} are used for
      TCP-based and UDP-based protocols, respectively. In either
      case 'port' corresponds to the primary port number being
      used by the protocol."
    ::= {assocEntry 3}

Available Formats

• CSV

mib-2.application.applTCPProtoID (1.3.6.1.2.1.27.4)

Note

This registry is not in use. As per RFC 2788 the applications are designated by the duplet formed by the OID and the TCP or UDP port respectively.

-- OIDs of the form {applTCPProtoID port} are intended to be used
-- for TCP-based protocols that don't have OIDs assigned by other
-- means. {applUDPProtoID port} serves the same purpose for
-- UDP-based protocols. In either case 'port' corresponds to
-- the primary port number being used by the protocol. For example,
-- assuming no other OID is assigned for SMTP, an OID of
-- {applTCPProtoID 25} could be used, since SMTP is a TCP-based
-- protocol that uses port 25 as its primary port.

mib-2.application.applUDPProtoID (1.3.6.1.2.1.27.5)

Note

This registry is not in use. As per RFC 2788 the applications are designated by the duplet formed by the OID and the TCP or UDP port respectively.

-- OIDs of the form {applTCPProtoID port} are intended to be used
-- for TCP-based protocols that don't have OIDs assigned by other
-- means. {applUDPProtoID port} serves the same purpose for
-- UDP-based protocols. In either case 'port' corresponds to
-- the primary port number being used by the protocol. For example,
-- assuming no other OID is assigned for SMTP, an OID of
-- {applTCPProtoID 25} could be used, since SMTP is a TCP-based
-- protocol that uses port 25 as its primary port.

Internet-standard MIB - Mail Monitoring

Description

• iso.org.dod.internet.mgmt.mib-2.mta (1.3.6.1.2.1.28)

mib-2.mta.mtaGroupTable.MailGroupEntry.mtaGroupMailProtocol

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.mgmt.mib-2.mta.mtaGroupTable.MailGroupEntry.mtaGroupMailProtocol (1.3.6.1.2.1.28.2.1.24)

Reference

• Not Defined ?

Note

mtaGroupMailProtocol OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
  "An identification of the protocol being used by this group.
  For an group employing OSI protocols, this will be the
  Application Context.  For Internet applications, the IANA
  maintains a registry of the OIDs which correspond to
  well-known message transfer protocols.  If the application
  protocol is not listed in the registry, an OID value of the
  form {applTCPProtoID port} or {applUDProtoID port} are used
  for TCP-based and UDP-based protocols, respectively.  In
  either case 'port' corresponds to the primary port number
  being used by the group.  applTCPProtoID and applUDPProtoID
  are defined in [5]."
::= {mtaGroupEntry 24}

Available Formats

• CSV

SMI mib-2 snanauMIB Codes

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.mgmt.mib-2.snanauMIB (1.3.6.1.2.1.34)

Reference

• RFC 1666: Definitions of Managed Objects for SNA NAUs using SMIv2

Available Formats

• CSV

spdActions

Registration Procedure(s)

• Specification Required

Expert(s)

• Wes Hardaker

Description

• iso.org.dod.internet.mgmt.mib-2.spdmib.sdpActions (1.3.6.1.2.1.153.4)

Reference

• RFC 4807: IPsec Security Policy Database Configuration MIB

IPFIX-SELECTOR-MIB Functions

Registration Procedure(s)

• Expert Review

Expert(s)

• Unassigned

Description

• iso.org.dod.internet.mgmt.mib-2.ipfixSelectorMIB.ipfixSelectorObjects.ipfixSelectorFunctions (1.3.6.1.2.1.194.1.1)

Reference

• RFC 6615: Definitions of Managed Objects for IP Flow Information Export

Available Formats

• CSV

SMI pib PIB Codes

Registration Procedure(s)

• Standards Action

Description

• iso.org.dod.internet.mgmt.pib (1.3.6.1.2.2)

Reference

• RFC 3159: Structure of Policy Provisioning Information (SPPI)

Available Formats

• CSV

SMI Experimental Codes

Registration Procedure(s)

• Experimental RFC

Description

• iso.org.dod.internet.experimental (1.3.6.1.3)

Reference

• RFC 4181: Guidelines for Authors and Reviewers of MIB Documents
• RFC 2578: Structure of Management Information Version 2 (SMIv2)
• RFC 1155: Structure and identification of management information for TCP/IP-based internets

Available Formats

• CSV

SMI experimental PIB codes

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.experimental.experimental-pib (1.3.6.1.3.116)

Reference

• RFC 3159: Structure of Policy Provisioning Information (SPPI)

Available Formats

• CSV

SMI Private Codes

Registration Procedure(s)

• Not Defined

Description

• iso.org.dod.internet.private (1.3.6.1.4)

Reference

• RFC 2578: Structure of Management Information Version 2 (SMIv2)

Available Formats

• CSV

Private Enterprise Numbers (PENs)

Registration Procedure(s)

• First Come First Served

Description

• iso.org.dod.internet.private.enterprise (1.3.6.1.4.1)

Reference

• RFC 9371: Registration Procedures for Private Enterprise Numbers (PENs)

Note

See Private Enterprise Numbers (PENs).

SMI Security Codes (including S/MIME, PKIX and LTANS)

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.security (1.3.6.1.5)

Reference

• Not Defined ?

Available Formats

• CSV

SMI Security for Integrity Codes

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.security.integrity (1.3.6.1.5.3)

Reference

• Not Defined ?

Available Formats

• CSV

SMI Security for Confidentiality Codes

Registration Procedure(s)

• Not Defined ?

Description

• iso.org.dod.internet.security.confide (1.3.6.1.5.4)

Reference

• Not Defined ?

Available Formats

• CSV

SMI Security for Mechanism Codes

Registration Procedure(s)

• IESG Approval

Description

• iso.org.dod.internet.security.mechanisms (1.3.6.1.5.5)

Reference

• Not Defined ?

Available Formats

• CSV

SMI Security for S/MIME Mail Security (1.2.840.113549.1.9.16)

Registration Procedure(s)

• Specification Required

Expert(s)

• Russ Housley (primary), Sean Turner (secondary)

Reference

• RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group

Available Formats

• CSV

SMI Security for S/MIME Module Identifier (1.2.840.113549.1.9.16.0)

Registration Procedure(s)

• Specification Required

Expert(s)

• Russ Housley (primary), Sean Turner (secondary)

Reference

• RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group

Available Formats

• CSV

SMI Security for S/MIME CMS Content Type (1.2.840.113549.1.9.16.1)

Registration Procedure(s)

• Specification Required

Expert(s)

• Russ Housley (primary), Sean Turner (secondary)

Reference

• RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group

Available Formats

• CSV

SMI Security for S/MIME Attributes (1.2.840.113549.1.9.16.2)

Registration Procedure(s)

• Specification Required

Expert(s)

• Russ Housley (primary), Sean Turner (secondary)

Reference

• RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group

Available Formats

• CSV

SMI Security for S/MIME Algorithms (1.2.840.113549.1.9.16.3)

Registration Procedure(s)

• Specification Required

Expert(s)

• Russ Housley (primary), Sean Turner (secondary)

Reference

• RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group

Note

Value 14, "id-alg-rsa-kem," is also referred to as "id-rsa-kem-spki."

Note

Value 17, "id-alg-hss-lms-hashsig", is also referred to as "id-alg-mts-hashsig".

Available Formats

• CSV

SMI Security for S/MIME Certificate Distribution Mechanisms (1.2.840.113549.1.9.16.4)

Registration Procedure(s)

• Specification Required

Expert(s)

• Russ Housley (primary), Sean Turner (secondary)

Reference

• RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group

Available Formats

• CSV

SMI Security for S/MIME Signature Policy Qualifier (1.2.840.113549.1.9.16.5)

Registration Procedure(s)

• Specification Required

Expert(s)

• Russ Housley (primary), Sean Turner (secondary)

Reference

• RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group

Available Formats

• CSV