Reference record for OID 2.9.3.5.3.3


parent
2.9.3.5.3 (managedObjectClass)
node code
3
node name
coProtocolMachine
dot oid
2.9.3.5.3.3
asn1 oid
  • {joint-iso-itu-t(2) ms(9) smi(3) part5(5) managedObjectClass(3) coProtocolMachine(3)}
  • {joint-iso-ccitt(2) ms(9) smi(3) part5(5) managedObjectClass(3) coProtocolMachine(3)}
    • iri oid
  • /joint-iso-itu-t/ms/smi/part5/managedObjectClass/coProtocolMachine
  • /joint-iso-ccitt/ms/smi/part5/managedObjectClass/coProtocolMachine
    • iri by oid_info
    /Joint-ISO-ITU-T/9/3/5/3/3

    Description by oid_info

    Managed object class: "coProtocolMachine"
    View at oid-info.com

    Information by oid_info

    The connection-mode protocol machine managed object class is used to represent a protocol machine performing connection-mode communications functions within an entity.

    More information can be found in Recommendation ITU-T X.723 (November 1993)

    First Registration Authority (recovered by parent 2.9)

    K. Morino & C. Smith

    Current Registration Authority (recovered by parent 2)

    ITU-T SG 17 & ISO/IEC JTC 1/SC 6

    Brothers (8)

    OIDNameSub childrenSub Nodes TotalDescription
    2.9.3.5.3.0 communicationsEntity 0 0 Managed object class: "communicationsEntity"
    2.9.3.5.3.1 informationData 0 0 Managed object class: "communicationsInformationRecord"
    2.9.3.5.3.2 clProtocolMachine 0 0 Managed object class: "clProtocolMachine"
    2.9.3.5.3.4 sap1 0 0 Managed object class: "sap1" (service access point)
    2.9.3.5.3.5 sap2 0 0 Managed object class: "sap2" (service access point)
    2.9.3.5.3.6 singlePeerConnection 0 0 Managed object class: "singlePeerConnection"
    2.9.3.5.3.7 subsystem 0 0 Managed object class: "subsystem"
    2.9.3.5.3.8 applicationProcess 0 0 Managed object class: "applicationProcess"