OID reference

rmcMLLeadZoneLength

1.3.6.1.4.1.1206.4.2.2.2.4.1.3

Description

Indicates the detection zone length of the leading detector. A suggested usable range is 0 to 5.0 in 0.1-meters increments.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.2.2.4.1 (rmcMLCtrlEntry)
Node code: 3
Node name: rmcMLLeadZoneLength
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.2.2.4.1.3
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.2.2.4.1.3

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 1206 4 2 2 2 4 1 3}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcML(2) rmcMLCtrlTable(4) rmcMLCtrlEntry(1) rmcMLLeadZoneLength(3)}

OID-IRI notation

/1/3/6/1/4/1/1206/4/2/2/2/4/1/3
/ISO/Identified-Organization/6/1/4/1/1206/4/2/2/2/4/1/3
/ISO/3/6/1/4/1/1206/4/2/2/2/4/1/3

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/org/dod/internet/private/enterprise/1206/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/org/dod/internet/private/enterprise/nema/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/org/dod/internet/private/enterprises/1206/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/org/dod/internet/private/enterprises/nema/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
/iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/ramp/rmcML/rmcMLCtrlTable/rmcMLCtrlEntry/rmcMLLeadZoneLength
Additional combinations skipped.

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-write
Status in MIB: optional, deprecated
Default value: 30

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — NTCIP published standard MIB annexes (reviewed modules)

Value type: INTEGER
Maximum access defined by MIB: read-write
Status in MIB: optional
Allowed ranges: 0–255

Variant 2 — NTCIP published standard MIB annexes (reviewed modules)

Value type: INTEGER
Maximum access defined by MIB: read-write
Status in MIB: deprecated
Default value: 30
Allowed ranges: 0–255

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In N207v0214-MIB, the row index rmcMLNumber is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.2.2.2.4.1.3.<rmcMLNumber>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.2.2.4.1.3

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Published definitions

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

rmcMLLeadZoneLength · optional

rmcMLLeadZoneLength OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-write
STATUS optional
DESCRIPTION
"Indicates the detection zone length of the leading detector.
A suggested usable range is 0 to 5.0 in 0.1-meters increments."
REFERENCE
"See Clause A.2.1"
::={ rmcMLCtrlEntry 3 }

rmcMLLeadZoneLength · deprecated

rmcMLLeadZoneLength OBJECT-TYPE
SYNTAX    INTEGER (0..255)
ACCESS    read-write
STATUS    deprecated
DESCRIPTION
"Indicates the detection zone length of the leading detector.
This value shall be expressed in 0.1-meter increments (i.e, 40 = 4.0 meters).
A suggested usable range is 0 to 50.
<Unit> tenth of meter
<Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1.3"
REFERENCE
"See Clause A.2.1"



                                                                                    

                                                                                    
                                                                                   

DEFVAL   { 30 }
::={ rmcMLCtrlEntry 3 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

Indicates the detection zone length of the leading detector. A suggested usable range is 0 to 5.0 in 0.1-meters increments.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

Indicates the detection zone length of the leading detector. This value shall be expressed in 0.1-meter increments (i.e, 40 = 4.0 meters). A suggested usable range is 0 to 50. <Unit> tenth of meter <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1.3

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 1

rmcMLLeadZoneLength · optionalNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: optional.

Names: rmcMLLeadZoneLength

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmcMLLeadZoneLength",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"Indicates the detection zone length of the leading detector. A suggested usable range is 0 to 5.0 in 0.1-meters increments.\"",
    "REFERENCE",
    "\"See Clause A.2.1\"",
    "::=",
    "{",
    "rmcMLCtrlEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "Indicates the detection zone length of the leading detector. A suggested usable range is 0 to 5.0 in 0.1-meters increments."
    ],
    [
      "REFERENCE",
      "See Clause A.2.1"
    ],
    null,
    null,
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1207:2001, Object Definitions for Ramp Meter Control (RMC) Units Published November 2001 (superceded by NTCIP 1207 v02) — original PDF · Official record
Module: RMC-MIB1

See published definition above
Module imports
```
{'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:
Show more related files and packages
- NTCIP8004-NEMA.mib — ITE namespace dependency
- NTCIP8004-Transportation.mib — ITE namespace dependency

Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

rmcMLLeadZoneLength · deprecatedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: deprecated.

Names: rmcMLLeadZoneLength

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmcMLLeadZoneLength",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"Indicates the detection zone length of the leading detector. This value shall be expressed in 0.1-meter increments (i.e, 40 = 4.0 meters). A suggested usable range is 0 to 50. <Unit> tenth of meter <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1.3\"",
    "REFERENCE",
    "\"See Clause A.2.1\"",
    "DEFVAL",
    "{",
    "30",
    "}",
    "::=",
    "{",
    "rmcMLCtrlEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "Indicates the detection zone length of the leading detector. This value shall be expressed in 0.1-meter increments (i.e, 40 = 4.0 meters). A suggested usable range is 0 to 50. <Unit> tenth of meter <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.2.4.1.3"
    ],
    [
      "REFERENCE",
      "See Clause A.2.1"
    ],
    null,
    null,
    [
      "DEFVAL",
      30
    ]
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1207 v02, Object Definitions for Ramp Meter Control (RMC) Units Published September 2014 — original PDF · Official record
Module: N207v0214-MIB

See published definition above
Module imports
```
{'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:
- NTCIP 1207 v02, Object Definitions for Ramp Meter Control (RMC) Units Published September 2014 — original PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (13)

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.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