OID reference
1.3.6.1.4.1.1206.4.2.2.2.4.1
Configuration and control parameters of the mainline lane table. A particular row of this table can be managed using the rmcMLMode-object. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1
Identification
{1 3 6 1 4 1 1206 4 2 2 2 4 1}
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Available source records contain 2 distinct definitions; some records may not include a definition.
rmcMLCtrlEntry OBJECT-TYPE
SYNTAX RmcMLCtrlEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Configuration and control parameters of the mainline lane table. A particular
row of this table can be managed using the rmcMLMode-object.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1"
INDEX { rmcMLNumber }
::={ rmcMLCtrlTable 1 }rmcMLCtrlEntry OBJECT-TYPE
SYNTAX RmcMLCtrlEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Configuration and control parameters of the mainline lane table. A particular
row of this table can be managed using the rmMLMode-object. Whether an unused
row is deleted or disabled is implementation specific."
INDEX { rmcMLNumber }
::={ rmcMLCtrlTable 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Configuration and control parameters of the mainline lane table. A particular row of this table can be managed using the rmcMLMode-object. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1
NTCIP published standard MIB annexes (reviewed modules)
Description 2
Configuration and control parameters of the mainline lane table. A particular row of this table can be managed using the rmMLMode-object. Whether an unused row is deleted or disabled is implementation specific.
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: rmcMLCtrlEntry
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rmcMLCtrlEntry",
"OBJECT-TYPE",
"SYNTAX",
"RmcMLCtrlEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Configuration and control parameters of the mainline lane table. A particular row of this table can be managed using the rmcMLMode-object. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1\"",
"INDEX",
"{",
"rmcMLNumber",
"}",
"::=",
"{",
"rmcMLCtrlTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"RmcMLCtrlEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Configuration and control parameters of the mainline lane table. A particular row of this table can be managed using the rmcMLMode-object. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1"
],
null,
null,
[
"INDEX",
[
[
0,
"rmcMLNumber"
]
]
],
null
]
}Module: N207v0214-MIB
See published definition above
{'NTCIP': ['ramp'], 'RFC-1212': ['OBJECT-TYPE']}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: The PDF prints an invalid ASN.1 module label (1207v0214-MIB). The derived transcription uses an equal-length internal parsing label; this is not an OID registration or an alteration of any numeric assignment. The original label and full PDF are retained.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP. 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 NTCIP1207v0214hj.pdf — N207v0214-MIB (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: rmcMLCtrlEntry
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rmcMLCtrlEntry",
"OBJECT-TYPE",
"SYNTAX",
"RmcMLCtrlEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Configuration and control parameters of the mainline lane table. A particular row of this table can be managed using the rmMLMode-object. Whether an unused row is deleted or disabled is implementation specific.\"",
"INDEX",
"{",
"rmcMLNumber",
"}",
"::=",
"{",
"rmcMLCtrlTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"RmcMLCtrlEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Configuration and control parameters of the mainline lane table. A particular row of this table can be managed using the rmMLMode-object. Whether an unused row is deleted or disabled is implementation specific."
],
null,
null,
[
"INDEX",
[
[
0,
"rmcMLNumber"
]
]
],
null
]
}Module: RMC-MIB1
See published definition above
{'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE']}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: TMIB-II. 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 1207v0117.pdf — RMC-MIB1 (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.1 | rmcMLNumber | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.2 | rmcMLMode | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.3 | rmcMLLeadZoneLength | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.4 | rmcMLTrailZoneLength | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.5 | rmcMLUsageMode | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.6 | rmcMLSpeedTrapSpacing | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.7 | rmcMLErraticCount | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.8 | rmcMLMaxPresence | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.9 | rmcMLNoActivity | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.10 | rmcVehicleLength | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.11 | rmcMLLeadZoneLengthV2 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.12 | rmcMLTrailZoneLengthV2 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.13 | rmcMLSpeedTrapSpacingV2 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.2.2.4.1.14 | rmcVehicleLengthV2 | 0 | 0 |