eventLogValue

Status in source: mandatory.

Names: eventLogValue

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The value of this object is set to the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable.\"",
    "::=",
    "{",
    "eventLogEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The value of this object is set to the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable."
    ],
    null,
    null,
    null,
    null
  ]
}

• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201:1996, Global Object Definitions Published December 2001 (superceded by NTCIP 1201 v02) — original PDF · Official record

  Module: GLOBAL

  See published definition above

  Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.

  Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

  Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

  Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

  Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

  Source data warning: The GLOBAL moduleMake/moduleVersion assignment closes its explicitly opened brace with a parenthesis. Normalize only that delimiter in the derived parsing copy; retain the original definition and unchanged numeric expression.

  Source data warning: The historical GLOBAL security grouping explicitly prints the parent global and suffix 5 but omits assignment braces. Reuse two adjacent whitespace bytes for those braces in the parsing copy; retain the original expression and qualify this syntactic interpretation. No numeric arc is invented or replaced.

  Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names EventLogConfigTable, while its native table or entry declaration uses eventLogConfigTable. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

  Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names EventLogEntry, while its native table or entry declaration uses eventLogEntry. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

  Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names globalmoduleTable, while its native table or entry declaration uses globalModuleTable. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

  Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names moduleTableEntry, while its native table or entry declaration uses moduleEntry. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

  Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of devices, profiles. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

  · Download NTCIP1201v0110b.pdf — GLOBAL (MIB transcription)

  Related source files and packages:

  • NTCIP 1201:1996, Global Object Definitions Published December 2001 (superceded by NTCIP 1201 v02) — original PDF
  • NTCIP 8004 v02 (2010) — normative namespace, pages 43–44
  • RFC 1155 — original SMI enterprise namespace

  Show more related files and packages

  • NTCIP8004-NEMA.mib — ITE namespace dependency
  • NTCIP8004-Transportation.mib — ITE namespace dependency

Status in source: mandatory.

Names: eventLogValue

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE—Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <DescriptiveName>Event.logValue:frame <DataConceptType>Data Element\"",
    "::=",
    "{",
    "eventLogEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE—Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <DescriptiveName>Event.logValue:frame <DataConceptType>Data Element"
    ],
    null,
    null,
    null,
    null
  ]
}

• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1103 v01, Transportation Management Protocols Published January 2009 (superceded by NTCIP 1103 v02) — original PDF · Official record

  Module: NTCIP1103v0127

  See published definition above

  Module imports

  {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Gauge', 'Counter', 'NetworkAddress', 'Opaque', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['OwnerString', 'RowStatusStatic', 'dynObjMgmt', 'profiles', 'application', 'global', 'OerString']}

  Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.

  Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

  Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004-A-2004. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

  · Download NTCIP1103v0127r-1.pdf — NTCIP1103v0127 (MIB transcription)

  Related source files and packages:

  • NTCIP 1103 v01, Transportation Management Protocols Published January 2009 (superceded by NTCIP 1103 v02) — original PDF
• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201:2005, Global Object Definitions – version 02 Published October 2005 (superceded by NTCIP 1201 v03) — original PDF · Official record

  Module: NTCIP1201-2004

  See published definition above

  Module imports

  {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['devices', 'protocols', 'profiles', 'global']}

  Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.

  Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

  Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004-A-2004. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

  · Download NTCIP1201v0232f.pdf — NTCIP1201-2004 (MIB transcription)

  Related source files and packages:

  • NTCIP 1201:2005, Global Object Definitions – version 02 Published October 2005 (superceded by NTCIP 1201 v03) — original PDF

Status in source: deprecated.

Names: eventLogValue

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Supplanted by> ISO26048-1-Log.fdLogValue (ISO 26048-1) <Informative> The replacement object uses an ITSOerString (i.e., the value is in OER and sent over SNMP with a BER wrapper as opposed to the Opaque which created a double BER wrapper). This means that the manager who requests the value must know the syntax that was encoded. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.5\"",
    "::=",
    "{",
    "eventLogEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Supplanted by> ISO26048-1-Log.fdLogValue (ISO 26048-1) <Informative> The replacement object uses an ITSOerString (i.e., the value is in OER and sent over SNMP with a BER wrapper as opposed to the Opaque which created a double BER wrapper). This means that the manager who requests the value must know the syntax that was encoded. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.5"
    ],
    null,
    null,
    null,
    null
  ]
}

• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201 v4.0.0 — ITE published 2025 edition — original PDF · Official record

  Module: NTCIP1201-GlobalReport

  See published definition above

  Module imports

  {'SNMPv2-TC': ['VariablePointer'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Opaque', 'zeroDotZero'], 'NTCIP1201-Global': ['global']}

  Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

  · Download 1201v4-0-0.pdf — NTCIP1201-GlobalReport (MIB transcription)

  Related source files and packages:

  • NTCIP 1201 v4.0.0 — ITE published 2025 edition — original PDF

Status in source: mandatory.

Names: eventLogValue

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE – Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.5 \"",
    "::=",
    "{",
    "eventLogEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE – Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.5"
    ],
    null,
    null,
    null,
    null
  ]
}

• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1103 v03, Transportation Management Protocols Published December 2016 — original PDF · Official record

  Module: NTCIP1103v0352-Report

  See published definition above

  Module imports

  {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter', 'Opaque', 'null'], 'NTCIP8004-2008': ['global']}

  Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

  Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004-2008. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

  · Download NTCIP1103v0352b.pdf — NTCIP1103v0352-Report (MIB transcription)

  Related source files and packages:

  • NTCIP 1103 v03, Transportation Management Protocols Published December 2016 — original PDF
• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1103 v02, Transportation Management Protocols Published July 2010 (superceded by NTCIP 1103 v03) — original PDF · Official record

  Module: NTCIP1103v0217-Report

  See published definition above

  Module imports

  {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter', 'Opaque', 'null'], 'NTCIP8004-A-2004': ['global']}

  Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

  Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004-A-2004. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

  · Download NTCIP1103v0217r-1.pdf — NTCIP1103v0217-Report (MIB transcription)

  Related source files and packages:

  • NTCIP 1103 v02, Transportation Management Protocols Published July 2010 (superceded by NTCIP 1103 v03) — original PDF

Status in source: deprecated.

Names: eventLogValue

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Superseded by> LOG-MIB.fdLogValue (ISO 20684-5) <Informative> The replacement object uses an ITSOerString (i.e., the value is in OER and sent over SNMP with a BER wrapper as opposed to the Opaque which created a double BER wrapper). This means that the manager who requests the value must know the syntax that was encoded. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.5\"",
    "::=",
    "{",
    "eventLogEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Superseded by> LOG-MIB.fdLogValue (ISO 20684-5) <Informative> The replacement object uses an ITSOerString (i.e., the value is in OER and sent over SNMP with a BER wrapper as opposed to the Opaque which created a double BER wrapper). This means that the manager who requests the value must know the syntax that was encoded. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.5"
    ],
    null,
    null,
    null,
    null
  ]
}

• ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP-1201 — ntcip1201-AuxIO.mib

  Module: NTCIP1201-Report

  See published definition above

  Module imports

  {'SNMPv2-TC': ['VariablePointer'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'Opaque', 'zeroDotZero'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'NTCIP1201-Global': ['global']}

  Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.

  · Download NTCIP-1201 — ntcip1201-AuxIO.mib

  Same file in ntcip1201-SNMPConfig.mib.

  Same file in ntcip1201-Security.mib.

  Same file in ntcip1201-ProfilesSTMP.mib.

  Same file in ntcip1201-NtcipTraps.mib.

Status in source: mandatory.

Names: eventLogValue

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE - Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <DescriptiveName>Event.logValue:frame <DataConceptType>Data Element\"",
    "::=",
    "{",
    "eventLogEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE - Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <DescriptiveName>Event.logValue:frame <DataConceptType>Data Element"
    ],
    null,
    null,
    null,
    null
  ]
}

• ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP-1201 — NTCIP1201-Glo.mib

  Module: NTCIP1201-2004

  See published definition above

  Module imports

  {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['devices', 'protocols', 'profiles', 'global']}

  Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.

  Source data warning: Potentially inaccurate interpretation of historical NTCIP imports: the original references NTCIP8004-A-2004, which is absent from the public repository snapshot. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

  · Download NTCIP-1201 — NTCIP1201-Glo.mib