Reference record for OID 1.3.6.1.2.1.140.2.1.1


parent
1.3.6.1.2.1.140.2.1 (pktcMtaCompliances)
node code
1
node name
pktcMtaBasicCompliance
dot oid
1.3.6.1.2.1.140.2.1.1
type
MODULE-COMPLIANCE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pktcIetfMtaMib(140) pktcMtaConformance(2) pktcMtaCompliances(1) pktcMtaBasicCompliance(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pktcIetfMtaMib(140) pktcMtaConformance(2) pktcMtaCompliances(1) pktcMtaBasicCompliance(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) pktcIetfMtaMib(140) pktcMtaConformance(2) pktcMtaCompliances(1) pktcMtaBasicCompliance(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) pktcIetfMtaMib(140) pktcMtaConformance(2) pktcMtaCompliances(1) pktcMtaBasicCompliance(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pktcIetfMtaMib(140) pktcMtaConformance(2) pktcMtaCompliances(1) pktcMtaBasicCompliance(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pktcIetfMtaMib(140) pktcMtaConformance(2) pktcMtaCompliances(1) pktcMtaBasicCompliance(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/pktcIetfMtaMib/pktcMtaConformance/pktcMtaCompliances/pktcMtaBasicCompliance
  • /iso/identified-organization/dod/internet/mgmt/mib/pktcIetfMtaMib/pktcMtaConformance/pktcMtaCompliances/pktcMtaBasicCompliance
  • /iso/org/dod/internet/mgmt/mib-2/pktcIetfMtaMib/pktcMtaConformance/pktcMtaCompliances/pktcMtaBasicCompliance
  • /iso/org/dod/internet/mgmt/mib/pktcIetfMtaMib/pktcMtaConformance/pktcMtaCompliances/pktcMtaBasicCompliance
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/pktcIetfMtaMib/pktcMtaConformance/pktcMtaCompliances/pktcMtaBasicCompliance
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/pktcIetfMtaMib/pktcMtaConformance/pktcMtaCompliances/pktcMtaBasicCompliance
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/140/2/1/1

    Description by oid_info

    pktcMtaBasicCompliance MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION
    " 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."
    MODULE -- Unconditionally mandatory groups for MTAs
    MANDATORY-GROUPS {
    pktcMtaGroup,
    pktcMtaNotificationGroup
    }
    OBJECT pktcMtaDevDhcpServerAddressType
    SYNTAX InetAddressType { ipv4(1) }
    DESCRIPTION
    " 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."
    OBJECT pktcMtaDevDnsServerAddressType
    SYNTAX InetAddressType { ipv4(1) }
    DESCRIPTION
    " 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."
    OBJECT pktcMtaDevTimeServerAddressType
    SYNTAX InetAddressType { ipv4(1) }
    DESCRIPTION
    " 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."
    OBJECT pktcMtaDevServerDhcp1
    SYNTAX InetAddress (SIZE(4))
    DESCRIPTION
    "An implementation is only required to support IPv4
    addresses. Other address types support may be defined in
    future versions of this MIB module."
    OBJECT pktcMtaDevServerDhcp2
    SYNTAX InetAddress (SIZE(4))
    DESCRIPTION
    "An implementation is only required to support IPv4
    addresses. Other address types support may be defined in
    future versions of this MIB module."
    OBJECT pktcMtaDevServerDns1
    SYNTAX InetAddress (SIZE(4))
    DESCRIPTION
    "An implementation is only required to support IPv4
    addresses. Other address types support may be defined in
    future versions of this MIB module."
    OBJECT pktcMtaDevServerDns2
    SYNTAX InetAddress (SIZE(4))
    DESCRIPTION
    "An implementation is only required to support IPv4
    addresses. Other address types support may be defined in
    future versions of this MIB module."
    OBJECT pktcMtaDevTimeServer
    SYNTAX InetAddress (SIZE(4))
    DESCRIPTION
    "An implementation is only required to support IPv4
    addresses. Other address types support may be defined in
    future versions of this MIB module."
    OBJECT pktcMtaDevProvConfigEncryptAlg
    SYNTAX PktcMtaDevProvEncryptAlg
    DESCRIPTION
    "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."
    OBJECT pktcMtaDevRealmOrgName
    SYNTAX LongUtf8String (SIZE (1..384))
    DESCRIPTION
    "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."

    View at oid-info.com

    Description by mibdepot

    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.

    Parsed from file rfc4682-IPCDN-MTA.mib.txt
    Company: None
    Module: PKTC-IETF-MTA-MIB

    Description by circitor

    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.

    Parsed from file PKTC-IETF-MTA-MIB.mib
    Module: PKTC-IETF-MTA-MIB

    Information by oid_info

    Automatically extracted from RFC4682

    Information by mibdepot

    pktcMtaBasicCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION " 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." MODULE MANDATORY-GROUPS { pktcMtaGroup, pktcMtaNotificationGroup } OBJECT pktcMtaDevDhcpServerAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION " 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." OBJECT pktcMtaDevDnsServerAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION " 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." OBJECT pktcMtaDevTimeServerAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION " 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." OBJECT pktcMtaDevServerDhcp1 SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevServerDhcp2 SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevServerDns1 SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevServerDns2 SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevTimeServer SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevProvConfigEncryptAlg SYNTAX PktcMtaDevProvEncryptAlg DESCRIPTION "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." OBJECT pktcMtaDevRealmOrgName SYNTAX LongUtf8String (SIZE (1..384)) DESCRIPTION "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." ::= { pktcMtaCompliances 1 }

    Information by circitor

    pktcMtaBasicCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION " 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." MODULE MANDATORY-GROUPS { pktcMtaGroup, pktcMtaNotificationGroup } OBJECT pktcMtaDevDhcpServerAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION " 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." OBJECT pktcMtaDevDnsServerAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION " 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." OBJECT pktcMtaDevTimeServerAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION " 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." OBJECT pktcMtaDevServerDhcp1 SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevServerDhcp2 SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevServerDns1 SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevServerDns2 SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevTimeServer SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses. Other address types support may be defined in future versions of this MIB module." OBJECT pktcMtaDevProvConfigEncryptAlg SYNTAX PktcMtaDevProvEncryptAlg DESCRIPTION "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." OBJECT pktcMtaDevRealmOrgName SYNTAX LongUtf8String (SIZE (1..384)) DESCRIPTION "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." ::= { pktcMtaCompliances 1 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Brothers (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.140.2.1.2 pktcMtaBasicSmtaCompliance 0 0 The compliance statement for S-MTA devices
    that implement PacketCable or IPCablecom requirements.

    This compliance statement appliā€¦