MIBs Depot

IANAifType-MIB

Registered at
1.3.6.1.2.1.30
Last updated
2026-03-17 00:00
Organization
IANA
Revisions
2026-03-17 00:00, 2026-02-24 00:00, 2022-08-17 00:00, 2021-05-17 00:00, 2021-04-23 00:00, 2021-04-22 00:00, 2021-02-18 00:00, 2020-08-27 00:00, 2020-07-10 00:00, 2020-04-02 00:00, 2020-01-10 00:00, 2019-12-03 00:00, 2019-10-16 00:00, 2019-02-14 00:00, 2019-02-08 00:00, 2019-01-31 00:00, 2018-07-04 00:00, 2018-06-28 00:00, 2018-06-22 00:00, 2018-06-21 00:00, 2017-03-30 00:00, 2017-01-19 00:00, 2016-11-23 00:00, 2016-06-16 00:00, 2016-06-09 00:00, 2016-06-08 00:00, 2016-05-19 00:00, 2016-05-03 00:00, 2016-04-29 00:00, 2014-09-24 00:00, 2014-09-19 00:00, 2014-07-03 00:00, 2014-05-22 00:00, 2012-05-17 00:00, 2012-01-11 00:00, 2011-12-18 00:00, 2011-10-26 00:00, 2011-09-07 00:00, 2011-07-22 00:00, 2011-06-03 00:00, 2010-09-21 00:00, 2010-07-21 00:00, 2010-02-11 00:00, 2010-02-08 00:00, 2009-05-06 00:00, 2009-02-06 00:00, 2008-10-09 00:00, 2008-08-12 00:00, 2008-07-22 00:00, 2008-06-24 00:00, 2008-05-29 00:00, 2007-09-13 00:00, 2007-05-29 00:00, 2007-03-08 00:00, 2007-01-23 00:00, 2006-10-17 00:00, 2006-09-25 00:00, 2006-08-17 00:00, 2006-08-11 00:00, 2006-07-25 00:00, 2006-06-14 00:00, 2006-03-31 00:00, 2006-03-30 00:00, 2005-12-22 00:00, 2005-10-10 00:00, 2005-09-09 00:00, 2005-05-27 00:00, 2005-03-03 00:00, 2004-11-22 00:00, 2004-06-17 00:00, 2004-05-12 00:00, 2004-05-07 00:00, 2003-08-25 00:00, 2003-08-18 00:00, 2003-08-07 00:00, 2003-03-18 00:00, 2003-01-13 00:00, 2002-10-17 00:00, 2002-07-16 00:00, 2002-07-10 00:00, 2002-06-19 00:00, 2002-01-04 00:00, 2001-12-20 00:00, 2001-11-15 00:00, 2001-11-06 00:00, 2001-11-02 00:00, 2001-10-16 00:00, 2001-09-19 00:00, 2001-05-11 00:00, 2001-01-12 00:00, 2000-12-19 00:00, 2000-12-07 00:00, 2000-12-04 00:00, 2000-10-17 00:00, 2000-10-02 00:00, 2000-09-01 00:00, 2000-08-24 00:00, 2000-08-23 00:00, 2000-08-22 00:00, 2000-04-25 00:00, 2000-03-06 00:00, 1999-10-08 14:30, 1994-01-31 00:00
Namespace
standard
Source file
IANAifType-MIB
Digest
sha256:c676192edc492eb068c3aa2755991c34c061e103ddd12e6653795b3813b82a59

Description

This MIB module defines the IANAifType Textual Convention, and thus the enumerated values of the ifType object defined in MIB-II's ifTable.

Contact

Internet Assigned Numbers Authority Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Tel: +1 310-301-5800 E-Mail: iana@iana.org

Imports

FromSymbols
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMIMODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso, mib-2
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

46 module(s) in this corpus import this one.

Load order

Every file a consumer needs in order to load this module, dependencies first.

IANAifType-MIB
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC

Textual conventions

NameOIDSyntaxAccessStatus
IANAifType
TEXTUAL-CONVENTION
This data type is used as the syntax of the ifType object in the (updated) definition of MIB-II's ifTable. The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.) Interface types must not be directly added to the IANAifType-MIB MIB module. They must instead be added to the 'Interface Types (ifType)' registry at https://www.iana.org/assignments/smi-numbers. The relationship between the assignment of ifType values and of OIDs to particular media-specific MIBs is solely the purview of IANA and is subject to change without notice. Quite often, a media-specific MIB's OID-subtree assignment within MIB-II's 'transmission' subtree will be the same as its ifType value. However, in some circumstances this will not be the case, and implementors must not pre-assume any specific relationship between ifType values and transmission subtree OIDs.
current
IANAtunnelType
TEXTUAL-CONVENTION
The encapsulation method used by a tunnel. The value direct indicates that a packet is encapsulated directly within a normal IP header, with no intermediate header, and unicast to the remote tunnel endpoint (e.g., an RFC 2003 IP-in-IP tunnel, or an RFC 1933 IPv6-in-IPv4 tunnel). The value minimal indicates that a Minimal Forwarding Header (RFC 2004) is inserted between the outer header and the payload packet. The value UDP indicates that the payload packet is encapsulated within a normal UDP packet (e.g., RFC 1234). The values sixToFour, sixOverFour, and isatap indicates that an IPv6 packet is encapsulated directly within an IPv4 header, with no intermediate header, and unicast to the destination determined by the 6to4, 6over4, or ISATAP protocol. The remaining protocol-specific values indicate that a header of the protocol of that name is inserted between the outer header and the payload header. The IP Tunnel MIB [RFC4087] is designed to manage tunnels of any type over IPv4 and IPv6 networks; therefore, it already supports IP-in-IP tunnels. But in a DS-Lite scenario, the tunnel type is point-to-multipoint IP-in-IP tunnels. The direct(2) defined in the IP Tunnel MIB only supports point-to-point tunnels. So, it needs to define a new tunnel type for DS-Lite. The assignment policy for IANAtunnelType values is identical to the policy for assigning IANAifType values.
current