Reference record for OID 1.3.6.1.3.101.1.1.1


parent
1.3.6.1.3.101.1.1 (usmDHPublicObjects)
node code
1
node name
usmDHParameters
dot oid
1.3.6.1.3.101.1.1.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) experimental(3) snmpUsmDHObjectsMIB(101) usmDHKeyObjects(1) usmDHPublicObjects(1) usmDHParameters(1)}
  • {iso(1) org(3) dod(6) internet(1) experimental(3) snmpUsmDHObjectsMIB(101) usmDHKeyObjects(1) usmDHPublicObjects(1) usmDHParameters(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) experimental(3) snmpUsmDHObjectsMIB(101) usmDHKeyObjects(1) usmDHPublicObjects(1) usmDHParameters(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/experimental/snmpUsmDHObjectsMIB/usmDHKeyObjects/usmDHPublicObjects/usmDHParameters
  • /iso/org/dod/internet/experimental/snmpUsmDHObjectsMIB/usmDHKeyObjects/usmDHPublicObjects/usmDHParameters
  • /iso/iso-identified-organization/dod/internet/experimental/snmpUsmDHObjectsMIB/usmDHKeyObjects/usmDHPublicObjects/usmDHParameters
  • iri by oid_info
    /ISO/Identified-Organization/6/1/3/101/1/1/1

    Description by oid_info

    usmDHParameters OBJECT-TYPE SYNTAX OCTET STRING
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
    "The public Diffie-Hellman parameters for doing a Diffie-Hellman
    key agreement for this device. This is encoded as an ASN.1
    DHParameter per PKCS #3, section 9. E.g.

    DHParameter ::=SEQUENCE {
    prime INTEGER, -- p
    base INTEGER, -- g
    privateValueLength INTEGER OPTIONAL }
    Implementors are encouraged to use either the values from
    Oakley Group 1 or the values of from Oakley Group 2 as specified
    in RFC-2409, The Internet Key Exchange, Section 6.1, 6.2 as the
    default for this object. Other values may be used, but the
    security properties of those values MUST be well understood and
    MUST meet the requirements of PKCS #3 for the selection of
    Diffie-Hellman primes.
    In addition, any time usmDHParameters changes, all values of
    type DHKeyChange will change and new random numbers MUST be
    generated by the agent for each DHKeyChange object."
    REFERENCE
    "-- Diffie-Hellman Key-Agreement Standard, PKCS #3,
    RSA Laboratories, November 1993
    -- The Internet Key Exchange, RFC 2409, November 1998,
    Sec 6.1, 6.2"

    View at oid-info.com

    Description by mibdepot

    The public Diffie-Hellman parameters for doing a Diffie-Hellman
    key agreement for this device. This is encoded as an ASN.1
    DHParameter per PKCS #3, section 9. E.g.

    DHParameter ::= SEQUENCE {
    prime INTEGER,
    base INTEGER,
    privateValueLength INTEGER OPTIONAL }

    Implementors are encouraged to use either the values from
    Oakley Group 1 or the values of from Oakley Group 2 as specified
    in RFC-2409, The Internet Key Exchange, Section 6.1, 6.2 as the
    default for this object. Other values may be used, but the
    security properties of those values MUST be well understood and
    MUST meet the requirements of PKCS #3 for the selection of
    Diffie-Hellman primes.

    In addition, any time usmDHParameters changes, all values of
    type DHKeyChange will change and new random numbers MUST be
    generated by the agent for each DHKeyChange object.

    Parsed from file rfc2786-Diffie-Helman-USM-Key.mib.txt
    Company: None
    Module: SNMP-USM-DH-OBJECTS-MIB

    Description by circitor

    The public Diffie-Hellman parameters for doing a Diffie-Hellman
    key agreement for this device. This is encoded as an ASN.1
    DHParameter per PKCS #3, section 9. E.g.

    DHParameter ::= SEQUENCE {
    prime INTEGER,
    base INTEGER,
    privateValueLength INTEGER OPTIONAL }


    Implementors are encouraged to use either the values from
    Oakley Group 1 or the values of from Oakley Group 2 as specified
    in RFC-2409, The Internet Key Exchange, Section 6.1, 6.2 as the
    default for this object. Other values may be used, but the
    security properties of those values MUST be well understood and
    MUST meet the requirements of PKCS #3 for the selection of
    Diffie-Hellman primes.

    In addition, any time usmDHParameters changes, all values of
    type DHKeyChange will change and new random numbers MUST be
    generated by the agent for each DHKeyChange object.

    Parsed from file SNMP-USM-DH-OBJECTS-MIB.mib
    Module: SNMP-USM-DH-OBJECTS-MIB

    Information by oid_info

    Automatically extracted from RFC2786

    Information by mibdepot

    usmDHParameters OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS current DESCRIPTION "The public Diffie-Hellman parameters for doing a Diffie-Hellman key agreement for this device. This is encoded as an ASN.1 DHParameter per PKCS #3, section 9. E.g. DHParameter ::= SEQUENCE { prime INTEGER, base INTEGER, privateValueLength INTEGER OPTIONAL } Implementors are encouraged to use either the values from Oakley Group 1 or the values of from Oakley Group 2 as specified in RFC-2409, The Internet Key Exchange, Section 6.1, 6.2 as the default for this object. Other values may be used, but the security properties of those values MUST be well understood and MUST meet the requirements of PKCS #3 for the selection of Diffie-Hellman primes. In addition, any time usmDHParameters changes, all values of type DHKeyChange will change and new random numbers MUST be generated by the agent for each DHKeyChange object." REFERENCE " RSA Laboratories, November 1993 Sec 6.1, 6.2" ::= { usmDHPublicObjects 1 }

    Information by circitor

    usmDHParameters OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS current DESCRIPTION "The public Diffie-Hellman parameters for doing a Diffie-Hellman key agreement for this device. This is encoded as an ASN.1 DHParameter per PKCS #3, section 9. E.g. DHParameter ::= SEQUENCE { prime INTEGER, base INTEGER, privateValueLength INTEGER OPTIONAL } Implementors are encouraged to use either the values from Oakley Group 1 or the values of from Oakley Group 2 as specified in RFC-2409, The Internet Key Exchange, Section 6.1, 6.2 as the default for this object. Other values may be used, but the security properties of those values MUST be well understood and MUST meet the requirements of PKCS #3 for the selection of Diffie-Hellman primes. In addition, any time usmDHParameters changes, all values of type DHKeyChange will change and new random numbers MUST be generated by the agent for each DHKeyChange object." REFERENCE " RSA Laboratories, November 1993 Sec 6.1, 6.2" ::= { usmDHPublicObjects 1 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.3)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.3.101.1.1.1.0 usmDHParameters 0 0 None

    Brothers (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.3.101.1.1.2 usmDHUserKeyTable 1 5 This table augments and extends the usmUserTable and provides
    4 objects which exactly mirror the objects in that table with the
    t…