PKTC-IETF-MTA-MIB

        This MIB module defines the basic management object
for the Multimedia Terminal Adapter devices compliant
with PacketCable and IPCablecom requirements.
        
Copyright (C) The IETF Trust (2006).  This version of
this MIB module is part of RFC 4682; see the RFC itself for
full legal notices.
    
Source file
PKTC-IETF-MTA-MIB
Last revised
Identity
pktcIetfMtaMib
Base OID
1.3.6.1.2.1.140
Imported Objects
DOCS-IETF-BPI2-MIB docsBpi2CodeDownloadGroup (no object page) DocsX509ASN1DEREncodedCertificate
IF-MIB ifPhysAddress
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-MIB sysDescr
SNMPv2-SMI Counter32 mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the rfc MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'PKTC-IETF-MTA-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'PKTC-IETF-MTA-MIB::pktcIetfMtaMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'PKTC-IETF-MTA-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'PKTC-IETF-MTA-MIB::pktcIetfMtaMib'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (77)
.1.3.6.1.2.1.140
.1.3.6.1.2.1.140.0
.1.3.6.1.2.1.140.1
.1.3.6.1.2.1.140.1.1
.1.3.6.1.2.1.140.1.1.1
minutesUnsigned32
.1.3.6.1.2.1.140.1.1.10
.1.3.6.1.2.1.140.1.1.11
.1.3.6.1.2.1.140.1.1.12
.1.3.6.1.2.1.140.1.1.12.1
Unsigned32
.1.3.6.1.2.1.140.1.1.12.1.1
.1.3.6.1.2.1.140.1.1.12.1.2
.1.3.6.1.2.1.140.1.1.12.1.3
.1.3.6.1.2.1.140.1.1.12.1.4
.1.3.6.1.2.1.140.1.1.2
.1.3.6.1.2.1.140.1.1.3
.1.3.6.1.2.1.140.1.1.4
Unsigned32
.1.3.6.1.2.1.140.1.1.5
.1.3.6.1.2.1.140.1.1.6
.1.3.6.1.2.1.140.1.1.7
Enumeration
.1.3.6.1.2.1.140.1.1.8
.1.3.6.1.2.1.140.1.1.9
.1.3.6.1.2.1.140.1.2
.1.3.6.1.2.1.140.1.2.1
.1.3.6.1.2.1.140.1.2.10
OctetString
.1.3.6.1.2.1.140.1.2.11
OctetString
.1.3.6.1.2.1.140.1.2.12
.1.3.6.1.2.1.140.1.2.13
secondsUnsigned32
.1.3.6.1.2.1.140.1.2.14
secondsUnsigned32
.1.3.6.1.2.1.140.1.2.15
secondsUnsigned32
.1.3.6.1.2.1.140.1.2.16
Unsigned32
.1.3.6.1.2.1.140.1.2.17
OctetString
.1.3.6.1.2.1.140.1.2.18
Enumeration
.1.3.6.1.2.1.140.1.2.19
.1.3.6.1.2.1.140.1.2.2
.1.3.6.1.2.1.140.1.2.3
.1.3.6.1.2.1.140.1.2.4
.1.3.6.1.2.1.140.1.2.5
.1.3.6.1.2.1.140.1.2.6
.1.3.6.1.2.1.140.1.2.7
.1.3.6.1.2.1.140.1.2.8
.1.3.6.1.2.1.140.1.2.9
.1.3.6.1.2.1.140.1.3
.1.3.6.1.2.1.140.1.3.1
.1.3.6.1.2.1.140.1.3.2
.1.3.6.1.2.1.140.1.3.3
.1.3.6.1.2.1.140.1.3.4
Unsigned32
.1.3.6.1.2.1.140.1.3.5
.1.3.6.1.2.1.140.1.3.6
.1.3.6.1.2.1.140.1.3.6.1
Unsigned32
.1.3.6.1.2.1.140.1.3.6.1.1
OctetString
.1.3.6.1.2.1.140.1.3.6.1.2
minutesUnsigned32
.1.3.6.1.2.1.140.1.3.6.1.3
minutesUnsigned32
.1.3.6.1.2.1.140.1.3.6.1.4
.1.3.6.1.2.1.140.1.3.6.1.5
secondsUnsigned32
.1.3.6.1.2.1.140.1.3.6.1.6
millisecondsUnsigned32
.1.3.6.1.2.1.140.1.3.6.1.7
Unsigned32
.1.3.6.1.2.1.140.1.3.6.1.8
.1.3.6.1.2.1.140.1.3.6.1.9
Unsigned32
.1.3.6.1.2.1.140.1.3.7
.1.3.6.1.2.1.140.1.3.8
.1.3.6.1.2.1.140.1.3.8.1
Unsigned32
.1.3.6.1.2.1.140.1.3.8.1.1
.1.3.6.1.2.1.140.1.3.8.1.10
OctetString
.1.3.6.1.2.1.140.1.3.8.1.2
OctetString
.1.3.6.1.2.1.140.1.3.8.1.3
secondsUnsigned32
.1.3.6.1.2.1.140.1.3.8.1.4
millisecondsUnsigned32
.1.3.6.1.2.1.140.1.3.8.1.5
secondsUnsigned32
.1.3.6.1.2.1.140.1.3.8.1.6
millisecondsUnsigned32
.1.3.6.1.2.1.140.1.3.8.1.7
Unsigned32
.1.3.6.1.2.1.140.1.3.8.1.8
.1.3.6.1.2.1.140.1.3.8.1.9
Bits
.1.3.6.1.2.1.140.1.3.9
.1.3.6.1.2.1.140.1.4
.1.3.6.1.2.1.140.1.4.1
.1.3.6.1.2.1.140.2
.1.3.6.1.2.1.140.2.1
.1.3.6.1.2.1.140.2.2
Dependencies (9) 8 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (1)
Enumeration
none(0)
des64CbcMode(1)
t3Des192CbcMode(2)
aes128CbcMode(3)
aes256CbcMode(4)
Conformance Groups (2)
pktcMtaDevResetNow pktcMtaDevSerialNumber pktcMtaDevSwCurrentVers pktcMtaDevFQDN pktcMtaDevEndPntCount pktcMtaDevEnabled pktcMtaDevProvisioningCounter pktcMtaDevErrorOid pktcMtaDevErrorValue pktcMtaDevErrorReason pktcMtaDevTypeIdentifier pktcMtaDevProvisioningState pktcMtaDevHttpAccess pktcMtaDevCertificate pktcMtaDevCorrelationId pktcMtaDevManufacturerCertificate pktcMtaDevDhcpServerAddressType pktcMtaDevDnsServerAddressType pktcMtaDevTimeServerAddressType pktcMtaDevProvConfigEncryptAlg pktcMtaDevServerDhcp1 pktcMtaDevServerDhcp2 pktcMtaDevServerDns1 pktcMtaDevServerDns2 pktcMtaDevTimeServer pktcMtaDevConfigFile pktcMtaDevSnmpEntity pktcMtaDevRealmPkinitGracePeriod pktcMtaDevRealmTgsGracePeriod pktcMtaDevRealmAvailSlot pktcMtaDevRealmName pktcMtaDevRealmOrgName pktcMtaDevRealmUnsolicitedKeyMaxTimeout pktcMtaDevRealmUnsolicitedKeyNomTimeout pktcMtaDevRealmUnsolicitedKeyMaxRetries pktcMtaDevRealmStatus pktcMtaDevCmsAvailSlot pktcMtaDevCmsFqdn pktcMtaDevCmsKerbRealmName pktcMtaDevCmsUnsolicitedKeyMaxTimeout pktcMtaDevCmsUnsolicitedKeyNomTimeout pktcMtaDevCmsUnsolicitedKeyMaxRetries pktcMtaDevCmsSolicitedKeyTimeout pktcMtaDevCmsMaxClockSkew pktcMtaDevCmsIpsecCtrl pktcMtaDevCmsStatus pktcMtaDevResetKrbTickets pktcMtaDevProvUnsolicitedKeyMaxTimeout pktcMtaDevProvUnsolicitedKeyNomTimeout pktcMtaDevProvUnsolicitedKeyMaxRetries pktcMtaDevProvKerbRealmName pktcMtaDevProvSolicitedKeyTimeout pktcMtaDevProvConfigHash pktcMtaDevProvConfigKey pktcMtaDevProvState pktcMtaDevProvisioningTimer pktcMtaDevTelephonyRootCertificate
A collection of objects for managing PacketCable or
IPCablecom MTA implementations.
.1.3.6.1.2.1.140.2.2.1
A collection of notifications dealing with the change of
MTA provisioning status.
.1.3.6.1.2.1.140.2.2.2
Compliance Statements (2)

OID .1.3.6.1.2.1.140.2.1.1
The compliance statement for MTA devices that implement
PacketCable or IPCablecom requirements.

This compliance statement applies to MTA implementations
that support PacketCable 1.0 or IPCablecom requirements,
which are not IPv6-capable at the time of this
RFC publication.
Required groups
Object refinements
ObjectAccessSyntaxDescription
pktcMtaDevDhcpServerAddressType
ipv4(1)
Support for address types other than 'ipv4(1)'
is not presently specified and therefore is not
required. It may be defined in future versions of
this MIB module.
pktcMtaDevDnsServerAddressType
ipv4(1)
Support for address types other than 'ipv4(1)'
is not presently specified and therefore is not
required. It may be defined in future versions of
this MIB module.
pktcMtaDevTimeServerAddressType
ipv4(1)
Support for address types other than 'ipv4(1)'
is not presently specified and therefore is not
required. It may be defined in future versions of
this MIB module.
pktcMtaDevServerDhcp1 An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevServerDhcp2 An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevServerDns1 An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevServerDns2 An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevTimeServer An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevProvConfigEncryptAlg An implementation is only required to support
values of none(0) and des64Cbcmode(1).
An IV of zero is used to encrypt in des64Cbcmode, and
the length of pktcMtaDevProvConfigKey is 64 bits, as
defined in the PacketCable Security specification.
Other encryption types may be defined in future
versions of this MIB module.
pktcMtaDevRealmOrgName The Organization Name field in X.509 certificates
can contain up to 64 UTF-8 encoded characters,
as defined in RFCs 3280 and 4630. Therefore, compliant
devices are only required to support Organization
Name values of up to 64 UTF-8 encoded characters.
Given that RFCs 3280 and 4630 define the UTF-8 encoding,
compliant devices must support a maximum size of 384
octets for pktcMtaDevRealmOrgName. The calculation of
384 octets comes from the RFC 3629 UTF-8 encoding
definition whereby the UTF-8 encoded characters
are encoded as sequences of 1 to 6 octets,
assuming that code points as high as 0x7ffffffff
might be used. Subsequent versions of Unicode and ISO
10646 have limited the upper bound to 0x10ffff.
Consequently, the current version of UTF-8, defined in
RFC 3629, does not require more than four octets to
encode a valid code point.

OID .1.3.6.1.2.1.140.2.1.2
The compliance statement for S-MTA devices
that implement PacketCable or IPCablecom requirements.

This compliance statement applies to S-MTA implementations
that support PacketCable or IPCablecom requirements,
which are not IPv6-capable at the time of this
RFC publication.
Required groups
Object refinements
ObjectAccessSyntaxDescription
pktcMtaDevDhcpServerAddressType
ipv4(1)
Support for address types other than 'ipv4(1)'
is not presently specified and therefore is not
required. It may be defined in future versions of
this MIB module.
pktcMtaDevDnsServerAddressType
ipv4(1)
Support for address types other than 'ipv4(1)'
is not presently specified and therefore is not
required. It may be defined in future versions of
this MIB module.
pktcMtaDevTimeServerAddressType
ipv4(1)
Support for address types other than 'ipv4(1)'
is not presently specified and therefore is not
required. It may be defined in future versions of
this MIB module.
pktcMtaDevServerDhcp1 An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevServerDhcp2 An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevServerDns1 An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevServerDns2 An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevTimeServer An implementation is only required to support IPv4
addresses. Other address types support may be defined in
future versions of this MIB module.
pktcMtaDevProvConfigEncryptAlg An implementation is only required to support
values of none(0) and des64Cbcmode(1).
An IV of zero is used to encrypt in des64Cbcmode, and
the length of pktcMtaDevProvConfigKey is 64 bits, as
defined in the PacketCable Security specification.
Other encryption types may be defined in future
versions of this MIB module.
pktcMtaDevRealmOrgName The Organization Name field in X.509 certificates
can contain up to 64 UTF-8 encoded characters, as
defined in RFCs 3280 and 4630. Therefore, compliant
devices are only required to support Organization
Name values of up to 64 UTF-8 encoded characters.
Given that RFCs 3280 and 4630 define the UTF-8 encoding,
compliant devices must support a maximum size of 384
octets for pktcMtaDevRealmOrgName. The calculation of
384 octets comes from the RFC 3629 UTF-8 encoding
definition whereby the UTF-8 encoded characters
are encoded as sequences of 1 to 6 octets,
assuming that code points as high as 0x7ffffffff
might be used. Subsequent versions of Unicode and ISO
10646 have limited the upper bound to 0x10ffff.
Consequently, the current version of UTF-8, defined in
RFC 3629 does not require more than four octets to
encode a valid code point.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.2.1.140.0.1
This INFORM notification is issued by the MTA to initiate
the PacketCable provisioning process when the MTA SNMP
enrollment mechanism is used.
It contains the system description, the current software
version, the MTA device type identifier, the MTA MAC
address (obtained in the MTA ifTable in the ifPhysAddress
object that corresponds to the ifIndex 1), and a
correlation ID.
.1.3.6.1.2.1.140.0.2
This INFORM notification may be issued by the MTA to
confirm the completion of the PacketCable provisioning
process, and to report its provisioning completion
status.
It contains the MTA MAC address (obtained in the MTA
ifTable in the ifPhysAddress object that corresponds
to the ifIndex 1), a correlation ID and the MTA
provisioning state as defined in
pktcMtaDevProvisioningState.